🧭 Overview
The OTTO pixel connects your WordPress website to OTTO SEO automation, allowing it to read and optimise your site. If the pixel fails to install or verify correctly, OTTO cannot activate. This article walks you through the most common WordPress pixel errors and how to resolve them step by step.
✅ Before You Begin
Confirm the following before troubleshooting:
- You are logged in to Search Atlas and have navigated to OTTO SEO via the left sidebar.
- You have administrator access to your WordPress dashboard.
- Your WordPress site is live and publicly accessible (not under a maintenance page or password protection).
- You know which method you are using to install the pixel: plugin, manual code insertion, or a tag manager.
⚠️ Common Errors and What They Mean
- "Pixel not detected" — Search Atlas cannot find the pixel code on your site. The code was not saved correctly or is being blocked.
- "Verification failed" — The pixel was found but returned an unexpected response. This is often a caching or conflict issue.
- "Connection timeout" — Your server did not respond in time. This may be a hosting or firewall restriction.
- "Invalid site URL" — The URL entered in Search Atlas does not match the URL where the pixel is installed. Check for www vs. non-www or HTTP vs. HTTPS mismatches.
🔍 Step-by-Step Diagnostic Procedure
- Check your pixel code is present. In your browser, open your WordPress homepage, right-click, and select View Page Source. Press Ctrl+F (or Cmd+F on Mac) and search for otto or the pixel script snippet. If it does not appear, the code has not been saved to your site.
- Verify the URL in Search Atlas matches your live site. Go to OTTO SEO in the left sidebar and confirm the domain shown matches your WordPress site URL exactly, including the correct protocol (https://) and subdomain (www or non-www).
- Clear all caches. Caching plugins (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) can serve old page versions that do not include the pixel. Clear your plugin cache, your hosting-level cache, and any CDN cache (such as Cloudflare).
- Deactivate conflicting plugins temporarily. Security plugins (Wordfence, iThemes Security) and optimisation plugins (Autoptimize, WP Fastest Cache) can strip or defer scripts. Deactivate them one at a time and re-test pixel detection after each.
- Check your theme's header file. If you installed the pixel manually, confirm the snippet is placed immediately before the closing tag in your theme's header.php file or via Appearance → Theme File Editor. Do not place it inside the body or footer.
- Test with a plugin installation. If manual installation is failing, use the Search Atlas WordPress plugin instead. Install it from WordPress Dashboard → Plugins → Add New → Upload Plugin using the plugin .zip provided by Search Atlas, activate it, and enter your API key when prompted. The plugin handles pixel placement automatically.
- Check for JavaScript errors. Open your browser's developer tools (F12), go to the Console tab, and reload your homepage. Look for any red errors that mention blocked scripts, CSP (Content Security Policy) violations, or failed network requests related to the pixel.
- Review your Content Security Policy (CSP) headers. If your host or a security plugin enforces a strict CSP, it may block the pixel script from loading. Add the Search Atlas pixel domain to your CSP allowlist. Contact your hosting provider if you are unsure how to do this.
- Re-trigger verification in Search Atlas. After making any changes, return to OTTO SEO in the left sidebar and click Verify Pixel or the equivalent re-check button to prompt a fresh detection attempt.
🔌 WordPress Plugin Settings Configuration
If you are using the Search Atlas WordPress plugin, check these settings after activation:
- API Key: Must match the key shown in your Search Atlas account settings. Copy and paste it directly to avoid typos.
- Site URL: Confirm the URL auto-populated by the plugin matches your live domain exactly.
- OTTO Pixel UUID: Ensure the correct UUID is entered in the OTTO Pixel UUID field under the Settings tab of the plugin, and that the Disable OTTO Frontend Toolbar toggle is configured as needed.
- User Role Restrictions: Some plugin configurations exclude the pixel for logged-in administrators. Test pixel detection while logged out of WordPress or in an incognito browser window.
🌐 Hosting and Server Considerations
- Maintenance mode: Plugins like SeedProd or Coming Soon Pro will block pixel detection. Disable maintenance mode before verifying.
- Firewall rules: Managed WordPress hosts (WP Engine, Kinsta, Flywheel) have built-in firewalls that can block external script verification requests. Check your host's firewall logs or temporarily whitelist Search Atlas.
- SSL/HTTPS issues: A mixed-content warning or an invalid SSL certificate can prevent the pixel from loading. Ensure your site has a valid SSL certificate and that all resources load over HTTPS.
💬 Still Need 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.