🧭 Overview
If Search Atlas is not detecting your site pixel — even though another tool confirms it is present in your page header — the issue is almost always related to how and when the pixel loads, or how the site auditor is able to access your site. This article walks you through the most common causes and how to fix them.
🔍 Why Your Pixel May Not Be Detected
Search Atlas scans your page to verify the pixel during the site audit process. Several factors can prevent a successful detection even when the pixel is technically installed:
- Pixel loads after the page renders (deferred or async loading): If your pixel fires via JavaScript after the initial page load, the auditor may finish scanning before the pixel becomes visible in the DOM.
- Tag Manager delays: Pixels deployed through Google Tag Manager or similar tools may not fire during automated scans because trigger conditions (e.g., user interactions, consent acceptance) are not met.
- Consent Management Platform (CMP) blocking: If your site uses a cookie consent banner, the pixel may be blocked until a user accepts cookies — something an automated scanner cannot do.
- Caching layers serving a pixel-free version: CDN or server-side caching may serve a cached page that was rendered before the pixel was installed.
- Geo-blocking or bot protection rules: Firewalls, Cloudflare bot-fight mode, or geo-restrictions may block the Search Atlas scanner before it can read your page content.
- Pixel placed outside the
<head>tag: The auditor specifically looks for the pixel in the page head. A pixel placed only in the body or footer may not be found.
⚙️ How to Resolve Pixel Detection Issues
- Confirm placement in the
<head>tag: Open your page source (right-click → View Page Source) and confirm the Search Atlas pixel snippet appears inside the<head>section, not just in the body. - Switch to direct (non-GTM) installation: Temporarily install the pixel directly in your site's theme or template header file, bypassing Tag Manager, to rule out trigger-condition issues.
- Disable or configure your CMP for the pixel: Whitelist the Search Atlas pixel in your Consent Management Platform so it loads without requiring user consent, or set it to fire in the pre-consent category.
- Purge your CDN and server cache: After installing or adjusting the pixel, clear all caching layers so the scanner receives a fresh version of your page.
- Whitelist the Search Atlas crawler: In your firewall or bot-protection settings, allow automated scanners to access your site. If you use Cloudflare, temporarily disable Bot Fight Mode and retest.
- Re-run the site audit: After making changes, navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and trigger a fresh audit to allow Search Atlas to re-scan your site.
⏱️ Resolving Site Auditor Timeout Errors
A timeout occurs when the Search Atlas auditor cannot finish crawling your site within the allowed time window. This is separate from pixel detection but often happens alongside it. Common causes and fixes include:
- Slow server response times: If your server takes more than a few seconds to respond, the auditor may time out. Use a performance tool such as Google PageSpeed Insights to check your Time to First Byte (TTFB) and address hosting or server issues.
- Large or complex pages: Pages with excessive scripts, large images, or hundreds of DOM elements take longer to process. Optimise page performance to reduce load time.
- Bot-blocking rules timing out the connection: Some security configurations do not outright block the crawler but cause it to hang until the connection drops. Review your firewall logs for dropped or stalled connections from scanning IP ranges.
- Crawl budget exhaustion on very large sites: If your site has thousands of pages, the auditor may not complete within a single session. Contact support (see below) to discuss crawl configuration options.
✅ Quick Checklist Before Contacting Support
- Pixel is confirmed in the
<head>tag via View Page Source - Cache has been fully purged after pixel installation
- Tag Manager triggers and CMP consent rules have been reviewed
- Firewall and bot-protection settings allow automated scanners
- A fresh audit has been re-run from Left sidebar → OTTO SEO → SEO Automation
- Server response time is under 2 seconds
💬 Still Seeing the Issue?
If you have worked through all the steps above and the pixel is still not being detected or the auditor continues to time out, our team can investigate your specific site configuration directly. 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.