🧭 Overview

When you install the OTTO pixel through Google Tag Manager (GTM) on a proprietary or custom CMS, the Search Atlas dashboard may still show a Not Installed status even after the tag is correctly configured. This is almost always caused by aggressive server-side or CDN caching on your CMS — not a problem with GTM or the OTTO pixel code itself.

This article walks you through the correct troubleshooting path and helps you decide when to stop OTTO diagnostics and escalate to your hosting or CMS provider instead.

📌 What Is Duct Tape SEO and Why Does It Matter Here?

Duct Tape SEO is the Search Atlas onboarding and activation framework that connects your website to OTTO, our OTTO SEO automation engine. It is the layer responsible for verifying that the OTTO pixel is detected on your site before any automated SEO actions can begin.

During pixel verification, Duct Tape SEO sends detection requests to your website URL. If your CMS caches pages at the server level, those cached responses may not include the GTM container script — which means the OTTO pixel never loads in the response that Duct Tape SEO inspects, even though GTM is correctly set up on the live site.

This is why the dashboard shows Not Installed: Duct Tape SEO is reading a stale cached page, not the live rendered version of your site.

✅ Step 1: Confirm Your GTM Setup Is Correct

Before assuming a cache issue, verify that GTM itself is configured properly:

1. Log in to your GTM account and open the container linked to your site.
2. Confirm the OTTO pixel tag exists, is set to fire on All Pages, and is not paused.
3. Click Preview in GTM and enter your website URL. The GTM debug panel should show the OTTO pixel tag firing on page load.
4. Publish the container if you have made any recent changes. Unpublished changes are not live.
5. Return to Search Atlas, navigate to OTTO SEO in the left sidebar, and trigger a pixel re-check.

If the GTM preview confirms the tag is firing but the dashboard still shows Not Installed, proceed to Step 2.

🗄️ Step 2: Clear Your CMS and Server Cache

This is the most common root cause on proprietary CMS platforms. Cache must be cleared at every layer — plugin, server, and CDN — before Search Atlas can detect the pixel correctly.

Common cache locations to clear:

• CMS built-in cache: Look for a Cache, Performance, or Optimization section inside your CMS admin panel and purge all cached pages.
• Caching plugins: If you use a plugin such as WP Rocket, W3 Total Cache, LiteSpeed Cache, or a proprietary equivalent, clear all caches from within the plugin settings.
• Server-side cache: Contact your hosting provider or system administrator and ask them to purge the full page cache at the server level (Nginx, Apache, Varnish, or equivalent).
• CDN cache: If your site sits behind a CDN such as Cloudflare, Fastly, or a proprietary CDN, purge the entire cache or at minimum purge the cache for your homepage and key landing pages.

After clearing all cache layers, wait two to three minutes, then return to OTTO SEO in the left sidebar and trigger another pixel re-check.

🔍 Step 3: Verify the Pixel Is Live in a Browser

After clearing cache, manually confirm the pixel is rendering on your live site:

1. Open your website in a browser using a private or incognito window (this bypasses browser cache).
2. Open the browser developer tools (F12) and go to the Network tab.
3. Reload the page and filter requests by searching for otto or your GTM container ID (format: GTM-XXXXXX).
4. Confirm that both the GTM container script and the OTTO pixel request appear in the network log.

If you can see both requests in the browser but the Search Atlas dashboard still shows Not Installed, this confirms the cached page Duct Tape SEO is inspecting has not yet been refreshed. Repeat Step 2 and ask your hosting provider to confirm the purge was applied globally, including to any edge nodes.

🚦 When to Stop OTTO Diagnostics and Escalate

Stop running OTTO troubleshooting steps and escalate to your hosting or CMS provider when all three of the following are true:

• The GTM preview panel confirms the OTTO pixel tag is firing correctly.
• A private browser session shows the pixel loading in the network tab on your live site.
• The Search Atlas dashboard still shows Not Installed after multiple pixel re-checks.

At this point, the issue is not with OTTO or GTM. Your hosting or CMS provider needs to confirm that server-side caching, edge caching, or a reverse proxy is not serving stale responses to external crawlers and verification tools. Ask them specifically: "Can external requests from third-party tools receive a fully rendered, non-cached version of my pages?"

⚠️ Important Notes for Proprietary CMS Platforms

• Some proprietary CMS platforms cache pages separately for logged-in users versus public visitors. Ensure cache is cleared for the public, unauthenticated view of your pages.
• If your CMS uses server-side rendering (SSR) or static site generation (SSG), the GTM script must be included in the rendered HTML output — not injected only on the client side after the initial response is served.
• Some enterprise CMS platforms require a deployment or publish action to push cache changes to production. Confirm with your CMS administrator whether this step is required.

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