🧭 Overview
After installing the OTTO pixel on a WordPress site via the Search Atlas (MetaSync) WordPress plugin, the Search Atlas dashboard may still show the pixel status as Not Installed. Generic HTML debugging steps rarely solve this. The most common cause on WordPress is a missed plugin setting — specifically the Enable meta description toggle — which must be active for the pixel to be detected correctly.
Follow the checklist below in order before contacting support.
✅ Step 1: Confirm the Search Atlas (MetaSync) Plugin Is Configured
- In WordPress, install and activate the Search Atlas (MetaSync) plugin.
- In the WordPress admin, go to Search Atlas → Settings.
- Paste your Search Atlas API Key (or connect with One-Click Authentication) and paste your OTTO Pixel UUID. The plugin then handles the pixel automatically — you do not need to paste the JavaScript snippet on WordPress. (The code snippet is intended for non-WordPress platforms or alternative installs such as Google Tag Manager.)
- To confirm the pixel is loading, open any page on your site, right-click, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for otto or the first few characters of your pixel ID. If you cannot find it, revisit the plugin settings before continuing.
⚙️ Step 2: Enable the 'Enable Meta Description' Setting (Most Common Fix)
This is the single most frequently missed step on WordPress and the primary reason the OTTO pixel fails to register even when the code appears to be present.
- In your WordPress admin panel, navigate to Settings and open the configuration page for your active SEO plugin (for example, Rank Math, Yoast SEO, All in One SEO, or The SEO Framework).
- Locate the setting labelled Enable meta description (exact wording may vary slightly by plugin) and make sure it is turned on.
- Save your changes.
- Return to the Search Atlas dashboard under OTTO SEO and click Recheck Pixel Status or reload the page after one to two minutes.
Why this matters: The OTTO pixel relies on meta description output to confirm correct page-level integration. If your SEO plugin suppresses meta descriptions globally, the pixel verification check cannot complete, and the dashboard will continue to report the pixel as not installed — regardless of whether the snippet code is physically present in the page source.
🔍 Step 3: Check for Plugin or Theme Conflicts
- Temporarily switch to a default WordPress theme (such as Twenty Twenty-Four) and recheck pixel status in Search Atlas.
- If that resolves the issue, re-activate your original theme and identify which theme feature or child-theme customisation is stripping the
<head>output. - If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), purge all caches after any configuration change, then recheck.
- If you use a CDN or a proxy service such as Cloudflare, ensure that HTML minification or script optimisation is not removing or deferring the pixel snippet.
🛡️ Step 4: Verify No Security Plugin Is Blocking Output
- Security plugins such as Wordfence or iThemes Security can block or modify
<head>content. Temporarily disable them one at a time and recheck pixel status after each. - If your site uses a Content Security Policy (CSP), confirm that the OTTO pixel domain is included in your allowlist.
🔄 Step 5: Force a Fresh Pixel Status Check
- After completing any configuration change, clear your browser cache and open your website in a private or incognito window to ensure you are viewing the live, uncached version.
- In Search Atlas, navigate to OTTO SEO and trigger a pixel recheck. Allow up to about 15 minutes for the status to update, since automatic pixel checks run every 15 minutes for projects under 2 hours old.
- If status remains Not Installed after confirming every step above, proceed to the quick reference checklist below before contacting support.
📋 WordPress Pixel Installation Checklist
- Search Atlas (MetaSync) plugin installed and configured with API Key and OTTO Pixel UUID at Search Atlas → Settings
- Enable meta description toggled ON in your active SEO plugin — this is the most common blocker
- All caches purged after every configuration change
- CDN or Cloudflare HTML optimisation not stripping the snippet
- Security plugins not blocking output
- No Content Security Policy preventing the pixel domain
- Pixel status rechecked in Search Atlas after each fix attempt
💬 Still Showing as Not Installed?
If you have worked through every step above and the pixel status still shows Not Installed, our team can review your specific site configuration. 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.