## **🧭 Overview**

The **No EO Pixel Found** error means Search Atlas cannot detect the EO Pixel on your WordPress site after the plugin has been installed. In most cases, completing the standard setup resolves this. However, if you have already installed the plugin, updated PHP, and followed all setup steps, a secondary layer of issues — such as plugin conflicts, caching, or initialization timing — may be preventing detection. This article walks you through every advanced troubleshooting path.

## **✅ Confirm the Basics First**

Before moving to advanced steps, verify the following are already in place:

- The Search Atlas WordPress plugin is installed and **activated** (not just installed).
- Your site is running **PHP 7.4 or higher**.
- You are connected to the correct WordPress site in your Search Atlas dashboard under **Account Menu → Settings → CMS Connectors**.
- The plugin was authorized using the correct Search Atlas account credentials.

If any of these are incomplete, resolve them first. If all are confirmed and the error persists, continue below.

## **🗂️ Step 1: Clear All Caches**

Caching is the most common reason the EO Pixel is not detected even after a successful install. The pixel may be present in your live code but invisible to the scanner because an old cached version of your page is being served.

1. Log in to your WordPress admin dashboard.
2. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache), open its settings and select **Clear All Cache** or **Purge Everything**.
3. If your hosting provider offers server-level caching (common with SiteGround, WP Engine, Cloudways, Kinsta), log in to your hosting control panel and clear the server cache from there as well.
4. If you use a CDN such as Cloudflare, log in and purge the cache for your entire domain.
5. Return to Search Atlas and attempt to reconnect your site.

## **⚡ Step 2: Check for Plugin Conflicts**

Another active plugin may be interfering with how the EO Pixel is injected into your page's HTML. Security plugins, firewall plugins, and script optimization tools are frequent causes.

1. In your WordPress admin, go to **Plugins → Installed Plugins**.
2. Temporarily deactivate all plugins **except** the Search Atlas plugin. To do this safely, use a staging environment if one is available.
3. After deactivating other plugins, clear your cache again (Step 1) and retry the connection in Search Atlas.
4. If the connection succeeds, reactivate your other plugins **one at a time**, testing after each activation to identify the conflicting plugin.
5. Common conflicting plugin categories include: security firewalls (e.g., Wordfence, iThemes Security), script managers (e.g., Autoptimize, Asset CleanUp), and HTML minifiers.

If you identify a conflicting plugin, check its settings for options that block or defer third-party scripts, and whitelist the Search Atlas plugin or its associated scripts.

## **🛡️ Step 3: Check for Theme or Script Optimization Issues**

Some WordPress themes and page builders (e.g., Elementor, Divi, Beaver Builder) apply their own script management or output buffering that can strip or delay pixel injection.

- Temporarily switch your theme to a default WordPress theme (e.g., **Twenty Twenty-Four**) and test the connection again.
- If your theme uses a child theme, deactivate the child theme and test with the parent theme only.
- Disable any **JavaScript deferral or concatenation** settings in your theme's performance options and retest.

## **⏱️ Step 4: Allow for Initialization Race Conditions**

In some environments, there is a brief delay between plugin activation and the pixel becoming detectable on the live page. This is known as an initialization race condition. Search Atlas needs to scan a fully rendered, live version of your page — not a cached or partially loaded one.

1. After activating the plugin and clearing all caches, wait **at least 5 minutes** before attempting to reconnect in Search Atlas.
2. Visit your site's homepage in a private/incognito browser window to confirm it loads without errors.
3. Use a tool such as **CTRL+U** (View Page Source) in your browser to search for **EO Pixel** or the Search Atlas script tag in your raw HTML. If visible in the source, the pixel is present and the issue is likely on the detection side; proceed to Step 5.
4. If the pixel is **not visible in the page source**, the plugin is not injecting it correctly — return to Steps 2 and 3.

## **🌐 Step 5: Verify Site Accessibility and SSL**

Search Atlas must be able to reach your site externally to verify the pixel. Certain server configurations can block this.

- Confirm your site is publicly accessible (not under maintenance mode or behind a login wall).
- Ensure your site uses a valid **SSL certificate** (HTTPS). Sites with mixed content warnings or expired SSL certificates may cause detection failures.
- If your site uses a **robots.txt** file that blocks all crawlers, temporarily allow access and retry.
- If your hosting plan restricts external HTTP requests (some managed hosting environments do this), contact your host to confirm outbound and inbound requests are permitted.

## **🔄 Step 6: Reinstall the Plugin**

If none of the above steps resolve the issue, a clean reinstall of the Search Atlas plugin can clear corrupted installation files.

1. In WordPress, go to **Plugins → Installed Plugins**, deactivate, and then **delete** the Search Atlas plugin.
2. In Search Atlas, go to **Account Menu → Settings → CMS Connectors** and disconnect the existing site entry if present.
3. Reinstall the plugin fresh by uploading the latest .zip version from your Search Atlas dashboard via WordPress → Plugins → Add New → Upload Plugin.
4. Complete the authorization flow again using your Search Atlas credentials.
5. Clear all caches and wait 5 minutes before testing the connection.

## **📋 Information to Have Ready When You Escalate**

If you have completed all steps above and the error persists, our team will need the following information to investigate further. Please gather this before reaching out:

- Your WordPress version and PHP version.
- Your hosting provider name and plan type.
- A list of active plugins at the time of the error.
- A screenshot of the Search Atlas **Account Menu → Settings → CMS Connectors** screen showing the error.
- A screenshot or copy of your page source (CTRL+U on your homepage) showing whether the EO Pixel script tag is present or absent.
- Whether your site uses a CDN or WAF (Web Application Firewall), and which provider.

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.