If your Site Audit project shows a "Crawl has failed" status with zero HTTP buckets after several days, or if OTTO cannot detect your installed pixel, this article explains the most common causes and the steps you can take to resolve them.
Site Audit project stuck on "Crawl has failed" with no data after 5 or more days
OTTO backend returns a 404 error for your project even though the pixel script appears in your page's raw HTML
OTTO pixel scan starts but never completes, leaving your project without a deployment verdict
CMS type shown as "Undetected" even for platforms like Shopify, GoHighLevel, or HubSpot
Manual reprocessing appears stuck with target pages not crawled and no suggestions generated
Several distinct issues can cause these symptoms. Understanding which one applies to your situation will help you choose the right fix.
Redirect interference: If your domain has redirect chains (for example, HTTP to HTTPS, or www to non-www), the crawler may follow loops or dead ends and fail to index any pages, resulting in zero HTTP buckets.
Pixel scan timeout: A known platform issue can cause pixel scans on certain projects to start and then never finish. This prevents OTTO from confirming whether your script is active and blocks the deployment verdict.
CMS fingerprinting gaps: OTTO previously had difficulty identifying Shopify, GoHighLevel, and HubSpot sites automatically. A fix for this has been shipped, but older projects created before the fix may still show an undetected CMS.
GTM-based installations: If you installed the OTTO pixel via Google Tag Manager rather than directly in your HTML, detection can take between 10 and 15 minutes after GTM fires on a live page visit. Checking too soon will show the pixel as undetected even when installation is correct.
Backend project mismatch: In rare cases, the project UUID stored in Search Atlas becomes out of sync with the backend service, causing 404 responses even when the pixel is genuinely present in your raw HTML.
Verify your pixel installation. Open your website in a browser, right-click, and select View Page Source. Search for the OTTO script tag. If you do not see it in the raw HTML, reinstall the pixel by navigating to OTTO SEO in Search Atlas and following the installation instructions for your site.
Check for redirect chains. Use a free redirect-checker tool to confirm your domain resolves cleanly to a single final URL without unnecessary hops. If redirect chains exist, fix them at the server or DNS level before re-running the crawl.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.