Search Atlas Help Center

🔍 Troubleshooting Dashboard Discrepancies: GBP, Pixels, and Heatmaps

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

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

If your Search Atlas dashboard shows Not Connected for Google Business Profile (GBP), missing heatmap data, or undetected pixels — even after completing setup — this article explains why these discrepancies occur and how to resolve them across single or multiple domains.

🚀 Installing the OTTO Pixel on an Astro + Tailwind CSS Site

Astro sites require the OTTO Pixel to be placed in a layout file that wraps all pages. Follow these steps:

  1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) via the left sidebar (/seo-automation-v3).
  2. Select your property and copy your unique OTTO Pixel script.
  3. In your Astro project, open your base layout file — typically src/layouts/BaseLayout.astro.
  4. Paste the pixel script inside the <head> tag, before the closing </head>.
  5. Because Tailwind CSS is purely a styling framework, it does not interfere with script execution. No additional changes are needed for Tailwind.
  6. Deploy your updated site and allow up to 24 hours for the dashboard to reflect the connection.

⚠️ Why the Dashboard Shows "Not Connected" After Setup

A Not Connected status does not always mean setup failed. Common causes include:

  • Propagation delay: DNS and script detection can take up to 48 hours to register, especially for new domains or recently updated configurations.
  • Cached page versions: If your site uses SSG (static site generation), as Astro does by default, the pixel may not appear on cached pages until a full rebuild and redeploy is triggered.
  • Script blocked by browser extensions or CSP headers: Content Security Policy rules on your server may silently block the pixel from firing.
  • GBP verification lag: Google Business Profile verification status can take 24–72 hours to sync with the Search Atlas dashboard after Google confirms ownership.

✅ How to Verify Your Pixel Is Firing Correctly

Before assuming the pixel is missing, confirm it is active using your browser's developer tools:

  1. Open your live website in Google Chrome.
  2. Press F12 to open DevTools, then click the Network tab.
  3. Reload the page and type otto or your pixel ID in the filter bar.
  4. If the pixel is firing, you will see a network request with a 200 status code.
  5. If no request appears, check the Console tab for script errors or blocked resource warnings.
  6. If you see a CSP error, update your server's Content-Security-Policy header to allow the OTTO Pixel domain.

🗺️ Heatmaps Not Displaying After Pixel Installation

Heatmap data requires a minimum number of page visits to render. If heatmaps appear blank or unavailable, verify the following:

  • The pixel has been confirmed as firing (see the verification steps above).
  • The page has received at least 30–50 unique visits since the pixel was installed. Heatmaps will not populate below this threshold.
  • The heatmap is being viewed for the correct URL. Query strings and trailing slashes can cause URL mismatches — check that the URL in the dashboard exactly matches the live page URL.
  • Your site is not blocking the pixel on specific page types, such as password-protected or noindex pages.

🌐 Managing Pixel and GBP Status Across Multiple Domains

When managing 10 or more domains, discrepancies are more likely due to inconsistent deployment or domain-level configuration differences. Use this bulk verification approach:

  1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open each property in sequence.
  2. For each domain, run the browser Network tab check described above on the homepage and at least one inner page.
  3. Create a simple spreadsheet listing each domain, pixel status (firing / not firing), GBP connection status, and last verified date.
  4. For domains showing Not Connected after 48 hours, re-copy the pixel from the dashboard and re-deploy — do not reuse a previously copied script, as tokens can expire.
  5. For GBP properties, confirm that the Google account connected to Search Atlas has Owner or Manager access to each GBP listing. Viewer access is not sufficient for verification.
  6. Re-initiate GBP verification within Search Atlas for any property that has been connected for more than 72 hours but still shows as unverified.

⏱️ Domain-Specific Propagation Delays

Not all domains propagate at the same speed. Factors that extend detection time include:

  • New domains registered within the past 30 days
  • Recent nameserver or DNS changes
  • CDN configurations (Cloudflare, Fastly, etc.) that serve cached HTML without the updated pixel
  • Astro's static output mode, which requires a full rebuild to update deployed HTML files

If a domain has been fully deployed and verified but still shows incorrectly after 72 hours, proceed to the escalation step below.

💳 GBP Charges: When to Dispute vs. Investigate

If you notice unexpected GBP-related charges in your account, use the following guidance before disputing:

  • Investigate first if the charge appeared within 7 days of connecting or verifying a GBP property — this is normal billing tied to new service activation.
  • Investigate first if the dashboard shows a property as connected but you do not recognise it — it may be a domain added under a team member's session.
  • Dispute if a property shows Not Connected in the dashboard for more than 72 hours and you have confirmed the pixel is firing and GBP access is correct, yet a charge is still present.
  • Document your browser Network tab results and screenshots of the dashboard status before contacting support, as this will speed up resolution.

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