🔍 OTTO Pixel GTM Installation Not Showing Verified

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧩 Why This Happens

GTM has two separate stages: preview/debug mode and live publishing. When you test a tag in GTM Preview, it only fires in your browser session. The tag is not active on your live website until you publish the container. Search Atlas checks your live site to confirm the OTTO pixel is present, so if the container has never been published after adding the tag, the platform will always report the pixel as not installed — even though GTM preview shows it firing correctly.

This is the most common reason the OTTO pixel appears unverified after a GTM setup. It is unrelated to WordPress plugins or DNS configuration.

✅ Step 1 — Confirm the OTTO Pixel Tag Is Set Up Correctly in GTM

Before publishing, verify the tag is configured properly inside your GTM workspace.

  1. Log in to Google Tag Manager and open the workspace for the website you are connecting to Search Atlas.
  2. Go to Tags in the left sidebar and locate your OTTO pixel tag.
  3. Open the tag and confirm the pixel ID matches exactly what is shown inside Search Atlas. To find your pixel ID, go to Left sidebar → OTTO SEO → SEO Automation in Search Atlas, select your site, and follow the installation prompt.
  4. Confirm the trigger is set to All Pages (or at minimum your target pages) so the pixel fires on every visit.
  5. Save any changes if you made corrections.

📤 Step 2 — Publish the GTM Container

This is the step most commonly missed. GTM Preview mode does not make your tag live.

  1. In your GTM workspace, click the Submit button in the top-right corner.
  2. On the submission screen, select Publish and Create Version.
  3. Add an optional version name such as OTTO pixel added so you can identify this change later.
  4. Click Publish to confirm. GTM will display a version summary when the publish is complete.

Important: Do not close GTM or navigate away until you see the confirmation that the new version is live. If you leave the Submit screen without clicking Publish, the container will not update.

🔄 Step 3 — Trigger Verification in Search Atlas

Once the GTM container is published, return to Search Atlas and ask the platform to re-check the pixel.

  1. Go to Left sidebar → OTTO SEO → SEO Automation.
  2. Find your site and click Continue installation if that option is shown, or open the site's installation status panel.
  3. Click the button to re-verify or re-scan the pixel installation. Search Atlas will make a fresh request to your live site to detect the pixel.
  4. Wait up to two minutes for the check to complete. If the pixel is firing correctly on your published site, the status will update to installed.

🛠️ Step 4 — If the Pixel Is Still Not Detected

If Search Atlas still reports the pixel as not installed after publishing the GTM container, work through the following checks.

  • Clear any caching layers. If your site uses a caching plugin, a CDN such as Cloudflare, or server-side caching, purge the cache after publishing GTM. Cached pages may not include the updated GTM snippet.
  • Confirm the GTM snippet is on your site. Visit your website, right-click the page, and choose View Page Source. Search for your GTM container ID (format: GTM-XXXXXXX). If it is not present in the source, the GTM snippet itself has not been added to your site's HTML. The pixel tag inside GTM cannot fire without this base snippet.
  • Check for tag-blocking consent tools. If your site uses a cookie consent manager or tag-blocking solution, ensure the OTTO pixel tag is not being blocked by default before user consent is given. Search Atlas's verification crawler does not accept cookies, so a blocked tag will not be detected.
  • Verify the correct GTM workspace. If your GTM account contains multiple containers or workspaces, confirm you added the OTTO pixel tag to the container whose snippet is installed on the website registered in Search Atlas.

⚠️ This Is Not a WordPress Plugin or DNS Issue

If you are using GTM to install the OTTO pixel, you do not need to install a separate WordPress plugin or make any DNS changes. Those methods apply to different installation paths. If you followed the GTM route and confirmed the tag fires in preview, the steps above are the correct troubleshooting path. Switching methods mid-setup can cause duplicate tags or configuration conflicts.

💬 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.