Search Atlas Help Center

🔍 Verify OTTO Pixel Installation on WordPress + GTM

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

If you see the message 'OTTO Pixel is not installed correctly' inside the OTTO dashboard, it means our system could not detect a valid Pixel signal from your website. This can happen even when the WordPress plugin is active and your GTM container is published. This guide walks you through a structured diagnostic process to identify and fix the exact cause.

⚠️ Before You Begin

Confirm the following are already in place before proceeding:

  • The Search Atlas WordPress plugin is installed and activated on your site.
  • Your GTM container is published (not just saved in draft).
  • You are checking the correct domain — the one connected to your OTTO campaign.

🪜 Step 1 — Identify Your Installation Method

The OTTO Pixel should only be installed through one method at a time. Using both the WordPress plugin and a GTM tag simultaneously is the most common cause of this error. Determine which method you are relying on:

  • WordPress Plugin only — The plugin injects the Pixel directly into your site's code. No GTM tag is needed.
  • GTM only — The Pixel fires through a GTM tag. The WordPress plugin's Pixel output should be disabled or the plugin should not be handling Pixel injection.

If both methods are active at the same time, the signals can conflict and cause verification to fail. Choose one method and disable the other before continuing.

🔎 Step 2 — Verify the Pixel Is Firing in Your Browser

This is the most reliable way to confirm whether the Pixel is actually loading on your site. Follow these steps:

  1. Open your website in Google Chrome.
  2. Right-click anywhere on the page and select Inspect.
  3. Click the Network tab at the top of the DevTools panel.
  4. In the filter bar, type otto or your Pixel ID to filter requests.
  5. Reload the page.
  6. Look for a network request that matches your OTTO Pixel ID. If you see it fire with a 200 status code, the Pixel is loading correctly.
  7. If no request appears, the Pixel is not firing — continue to Step 3.

Pro tip: You can also use the Google Tag Assistant Chrome extension to confirm your GTM container is loaded and which tags are firing on the page.

🏷️ Step 3 — Check Your GTM Tag Configuration

If you are using GTM as your installation method, verify the tag is set up correctly:

  1. Open your GTM workspace and locate the OTTO Pixel tag.
  2. Confirm the tag type is Custom HTML and contains the full Pixel script provided in the Search Atlas platform.
  3. Check the trigger — it should fire on All Pages (Page View) unless you have a specific reason to limit it.
  4. Open GTM Preview Mode and load your website. Confirm the OTTO Pixel tag appears under Tags Fired on page load.
  5. If the tag appears under Tags Not Fired, your trigger is not configured correctly — update it to fire on All Pages and re-publish the container.
  6. After any changes, click Submit in GTM to publish the updated container. Saving alone does not push changes live.

🔌 Step 4 — Check for Plugin or Script Conflicts

Certain WordPress configurations can block the Pixel from loading:

  • Caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache) — Clear all caches after any change and confirm the Pixel is not being stripped from cached pages.
  • Cookie consent or privacy plugins — Tools like Cookiebot or Complianz can block third-party scripts until a user consents. Test the Pixel in a browser session where consent has been granted, or temporarily whitelist the Pixel script.
  • Script optimization plugins — Plugins that defer, delay, or combine JavaScript (such as Autoptimize) can interfere with GTM or direct Pixel loading. Exclude GTM or the Pixel script from optimization rules.
  • Security or firewall plugins — Wordfence or similar plugins may block external script calls. Check your firewall logs for blocked requests related to the Pixel.

📹 Step 5 — Record a Verification Video If the Issue Persists

If you have completed Steps 1–4 and the error message remains, the fastest way to get a resolution is to record a short screen video. This allows our team to see exactly what is happening in your setup and pinpoint the cause immediately. Your video should show:

  1. Your WordPress plugin settings page confirming the plugin is active.
  2. Your GTM workspace showing the tag, trigger, and that the container is published.
  3. The GTM Preview Mode session on your live site showing which tags fired.
  4. The browser Network tab filtered for your Pixel ID after a page reload.
  5. The OTTO dashboard showing the error message.

A 2–3 minute recording covering these screens gives our support team everything needed to diagnose the issue without back-and-forth delays.

✅ Step 6 — Re-run Pixel Verification in Search Atlas

Once you have made any changes, return to the platform to trigger a fresh check:

  1. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3).
  2. Open your OTTO campaign and navigate to the Pixel settings section.
  3. Click Verify Pixel or the equivalent re-check button to run a new detection scan.
  4. Wait up to 5 minutes for the system to confirm the signal before re-checking the status.

💬 Still Seeing the Error?

If you have followed every step above and the Pixel is still not verifying, our team can review your video recording and configuration directly. 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.