Search Atlas Help Center

🛠️ OTTO Pixel Not Detected on Dealer.com Sites

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

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

If your site runs on the Dealer.com CMS and the OTTO Pixel shows as not installed inside Search Atlas, this is a known platform-specific detection issue. It does not necessarily mean the pixel is missing from your site — it means Search Atlas cannot verify it through its standard detection method due to how Dealer.com renders and serves its pages.

⚙️ Why This Happens

Dealer.com is an automotive-focused CMS that uses a heavily managed hosting and rendering environment. This setup can prevent external tools from reading page source code in the standard way. As a result, even when the OTTO Pixel script is correctly placed on your site, Search Atlas may still report its status as not detected.

Common reasons the pixel goes undetected on Dealer.com sites include:

  • Deferred or async script loading: Dealer.com often loads third-party scripts after the initial page render, which can cause detection checks to miss the pixel entirely.
  • Restricted page source access: Dealer.com's infrastructure may block or limit external crawlers from reading the full HTML output of a page.
  • Tag Manager conflicts: If the pixel is deployed via a Tag Manager container rather than hardcoded into the page template, it may not appear during a standard source scan.
  • CDN or proxy caching: Dealer.com uses content delivery networks that may serve cached versions of pages without the pixel present in every response.

✅ How to Confirm the Pixel Is Actually Installed

Before escalating, verify the pixel is live on your site using these steps:

  1. Open your site in a browser (e.g., www.polestarfortlauderdale.com).
  2. Right-click anywhere on the page and select Inspect (or press F12) to open browser DevTools.
  3. Go to the Sources or Network tab and search for otto or your unique pixel ID.
  4. Alternatively, use the Elements tab and press Ctrl+F (or Cmd+F on Mac) to search for the pixel script tag.
  5. If the script appears, the pixel is installed correctly — the issue is limited to how Search Atlas detects it remotely.

🚀 Steps to Request Manual Pixel Verification

Because automated detection may not work reliably on Dealer.com sites, Search Atlas supports a manual verification process. Follow these steps:

  1. Log in to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (or go to /seo-automation-v3).
  2. Locate the OTTO Pixel status for your site and take a screenshot showing the not detected status alongside your domain name.
  3. Open the chat widget in the bottom-right corner of the platform and type human teammate.
  4. Share your domain, the screenshot, and confirmation that your site uses Dealer.com as the CMS.
  5. Our team will manually confirm pixel activity on the backend and update your account status accordingly.

💡 Best Practices for Dealer.com Pixel Installation

To give the OTTO Pixel the best chance of being detected automatically in future scans, work with your Dealer.com account representative to ensure:

  • The pixel script is placed in the section of every page template, not just the homepage.
  • The script loads synchronously where possible, rather than being deferred or set to async-only.
  • If using Google Tag Manager, confirm the GTM container itself fires on all pages and that the OTTO Pixel tag has no restrictive trigger conditions.
  • Any cookie consent or privacy tools are configured to allow the pixel to load for users who accept analytics cookies.

🙋 Still Seeing Issues?

If you have confirmed the pixel is on the page but Search Atlas still reports it as undetected after following the steps above, our support team can investigate further. 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.

Additional Notes

The only confirmed fix is to delete the existing pixel and reinstall it from scratch. Delete the existing OTTO Pixel entry (do not re-save/update it), generate a new pixel, remove the old script from Dealer.com, paste the new script, and allow about 15 minutes for status to update on a new project (automatic checks run every 15 minutes for projects under 2 hours old).