🔎 What Is the Pixel Disconnection Issue?
When Search Atlas runs a site audit crawl, the crawler systematically visits every page on your website. In some cases, this process can trigger a pixel disconnection — meaning the tracking pixel loses its active connection to the platform. This is a known behavior caused by the volume and speed of requests made during a crawl, which can temporarily interrupt the pixel's communication with Search Atlas servers.
If you see a disconnected pixel status, do not worry. Your data is not lost, and the issue is straightforward to resolve.
⚠️ Why Does This Happen?
There are a few common reasons why a pixel may disconnect during a site audit:
- Crawler traffic volume: The site audit sends a high number of requests in a short period. Some hosting environments or security plugins may rate-limit or block this traffic, which can interrupt the pixel.
- Caching plugins or CDN rules: Caching layers or content delivery networks may strip or block the pixel script from loading during the crawl.
- JavaScript execution issues: The pixel relies on JavaScript to fire correctly. If your site's JS is partially blocked or deferred during crawling, the pixel may not load as expected.
- Security or firewall settings: Firewalls, bot protection tools, or WAF (Web Application Firewall) rules may flag crawler requests and block associated scripts, including the pixel.
🛠️ How to Reconnect Your Pixel
Follow these steps to restore your pixel connection after a site audit:
- Navigate to OTTO SEO → SEO Automation using the left sidebar (URL: /seo-automation-v3).
- Locate the project associated with your disconnected pixel.
- Open the pixel settings for that project and copy the pixel code snippet.
- Log in to your website's backend (WordPress, Shopify, or your CMS of choice) and confirm the pixel code is present in the
<head>section of every page, or reinstall it if it was removed. - Return to Search Atlas and use the Verify Pixel option (if available) to confirm the connection has been re-established.
- Once verified, re-run your site audit to confirm everything is working correctly.
✅ How to Prevent Future Disconnections
Taking a few precautions before running a site audit can help keep your pixel connected throughout the crawl:
- Whitelist the Search Atlas crawler IP ranges in your firewall or security plugin settings so crawl requests are not blocked.
- Disable aggressive bot protection temporarily before starting a large crawl, then re-enable it once the audit is complete.
- Check your CDN settings to ensure JavaScript files — especially third-party scripts like the Search Atlas pixel — are not being stripped or blocked.
- Use a tag manager (such as Google Tag Manager) to load the pixel, which can improve reliability across different page states and crawl conditions.
- Avoid running multiple large crawls simultaneously, as this can compound the load on your server and increase the chance of a disconnection.
📊 Checking Pixel Status in Site Explorer
You can monitor your pixel status at any time by visiting Site Metrics → Site Explorer in the left sidebar (URL: /site-explorer/list). Your connected projects will display their current pixel health status here. If a project shows as disconnected, return to the steps in the section above to resolve it promptly and avoid gaps in your tracking data.
💬 Still Need Help?
If you have followed the steps above and your pixel is still showing as disconnected, or if you are unsure which part of your setup is causing the issue, we are here to help. 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.