Home πŸ› οΈ Troubleshooting

πŸ› οΈ Troubleshooting

Camilo Aponte
By Camilo Aponte
β€’ 104 articles

🚨 Why am I seeing "Quota Exhausted" in Search Atlas?

If you see the message "Quota Exhausted" anywhere in Search Atlas, it means your account has reached the usage limit for a specific feature included in your plan or trial. This article explains what this error means, why it happens, and what you can do next, regardless of the tool you're using. πŸ” What does "Quota Exhausted" mean? Search Atlas uses quotas to control usage across different features. When a quota is fully used: When a quota is exhausted, the platform immediately blocks that feature for your account until the quota resets or is topped up. Other features are unaffected. πŸ‘‰ This is expected system behavior, not a bug. ⚠️ Important: In some known cases, your quota counter may display 0 or an incorrect value even though your plan allocation is correctly set in our system. This can affect features including Custom Queries, Heatmaps, and AI tools. Contact support β€” do not assume the quota is truly exhausted. ⚠️ Note: A fix has been deployed to automatically correct certain Redis quota corruption errors (which previously surfaced as 500s on heatmap refresh). If you still see a 500 error after this fix, contact support β€” it may be a different underlying issue. ⚠️ Known issue β€” Website Builder / LPS chat box: If you click the upgrade link shown when quota is exhausted and are taken to the wrong page, navigate manually to your billing page at https://dashboard.searchatlas.com/billing. A fix is being released shortly. 🧠 Why does this happen? Each Search Atlas feature consumes quota based on usage, not just setup. Common reasons include: πŸ”„ 1. High-frequency usage Actions like: - Re-running scans - Refreshing data - Updating tracking consume quota every time they run. πŸ“Œ Note: Keyword Explorer bulk (KMT term-search) exports now count against your quota following a recent backend update. If an export fails unexpectedly, check your remaining quota before retrying. πŸ“Š 2. Large inputs Using: - Many keywords - Multiple sites - Large datasets can consume quota faster than expected. πŸ§ͺ 3. Trial and plan limits - Free trials include limited quotas - Paid plans include monthly quota caps - Quotas are not unlimited unless explicitly stated πŸ—‘οΈ 4. Removing data does not restore quota Deleting items, keywords, or projects: - ❌ Does not give quota back - βœ… Quota can only be restored by (a) your monthly plan reset on your billing cycle date, or (b) purchasing a quota top-up add-on from the Billing page. Plan upgrades may also increase your monthly cap. πŸ“Š How quotas work across Search Atlas (Detailed Breakdown) πŸ”½ Plan quotas vs Top-Ups (Important distinction) Quotas included in your plan Every Search Atlas plan (Starter, Growth, Pro, Agency) includes built-in monthly quotas for different features such as: - AI credits - Local SEO heatmaps - Rank tracking refreshes - Authority building credits - Automations and indexing These quotas: - βœ… Are included in your monthly subscription - πŸ” Reset automatically every billing cycle (monthly, on your billing cycle anniversary date) - ❌ Do not roll over if unused (unless explicitly stated) My quota hasn't reset after my billing cycle renewed If your monthly billing cycle has renewed but your quota counter still shows the previous period's usage (for example, a heatmap quota that has not refreshed for one or more cycles), contact support with: - Your account email - Your billing cycle date - The feature affected - A screenshot of the current quota counter Agents can perform a manual quota reset once a sync failure is confirmed. My quota didn't update after a payment or top-up In some cases, billing-to-quota sync can lag after a payment, top-up purchase, or plan upgrade. If you have been charged but your dashboard still shows the previous quota (or continues to display "Quota Exhausted"), contact support and include: - The payment confirmation or invoice - The date and amount of the charge - The feature or top-up you purchased A manual quota correction may be required while the team investigates the sync issue. Please allow time for the team to apply the fix on their end. Top-Ups (additional purchased quota) Top-Ups are extra quota purchases that sit on top of your plan. Important: - Some Top-Ups are recurring - Some Top-Ups are non-recurring (rollover) ⚠️ This distinction matters and is a common source of confusion. πŸ”½ Recurring vs Non-Recurring Top-Ups β€” what does this mean? πŸ” Recurring Top-Ups These: - Are billed monthly - Reset every billing cycle - Behave like an extension of your plan quota Examples: - Local SEO Points - Keyword Rank Tracker refreshes - GBP Automation locations - User Seats - OTTO Sites πŸ‘‰ If unused, they do not carry over to the next month. βž• Non-Recurring (Rollover) Top-Ups These: - Are purchased once - Do NOT reset monthly - Remain in your account until fully used Examples: - AI Premium Quota - OTTO AI quota points - URL Indexer quota - Hyperdrive Credits πŸ‘‰ These are ideal for one-time or burst usage. βš™οΈ What consumes quota by feature (and how it can be used without noticing) πŸ”½ AI Quota / AI Generation (OTTO & AI tools) Consumed when: - Generating AI metadata, headings, internal links - Creating topical maps - Generating landing pages - AI suggestions inside OTTO - AI-assisted GBP posts Easy to miss when: - Running bulk fixes or recommendations - Accepting multiple AI suggestions quickly - Generating content drafts you don't end up publishing πŸ“Œ Note: OTTO Sites and Site Auditor Projects are separate quotas, each with its own limit. However, adding OTTO to a domain requires an existing Site Audit project for that domain, so a brand-new domain needs both a free Site Audit project slot and a free OTTO site slot. If your OTTO dashboard shows available slots but you still receive a Quota Exhausted error on a new domain, your Site Auditor project quota may be the binding constraint. Contact support for a manual audit. πŸ“ Where can I check my quota? β€” Tip: OTTO users can now view quota consumption directly on the All Sites (SEO Automation) dashboard without navigating away. Navigate to OTTO SEO > All Sites (SEO Automation) to see a quota overview alongside your projects. πŸ”½ AI Premium Quota (Content Genius) Consumed when: - Generating full AI articles - Generating topical maps inside Content Genius - Running AI tasks inside the editor Important: - 1 full article = 3 AI Premium credits - Credits are charged at generation, not publication Easy to miss when: - Regenerating articles multiple times - Creating topical maps "just to explore"

Last updated on Oct 26, 2026

βœ… Share-of-Voice & Sentiment Dashboard Data Gaps β€” May 12–18, 2026 (Resolved)

The automated backfill for May 12–18, 2026 snapshot gaps has been deployed. Your Share-of-Voice and sentiment dashboards are restoring missing data points in stages β€” no action is required on your end. πŸ” What Happened: May 12–18, 2026 Between May 12–18, 2026, provider downtime and task queue stalls disrupted daily snapshot collection for user-tracked projects. As a result: - Share-of-Voice trend lines showed empty or broken segments for the affected dates. - Sentiment trend charts rendered no data points for those days. - Historical comparisons spanning May 12–18 appeared incomplete or inaccurate. Who is affected: Any account with user-tracked projects that relies on Share-of-Voice or sentiment dashboards for the May 12–18, 2026 date range. All underlying project data is intact β€” only the snapshot collection step was disrupted. πŸ“Š Additional bar-chart display fixes (separate from snapshot gap) As part of the same sprint, two customer-visible bar-chart display bugs were also identified and resolved: - Sentiment by Platform (LLMV-495): Was showing only the most-recent snapshot instead of the full selected date range. - Visibility by Platform (LLMV-479): Same display bug β€” only the most-recent snapshot was shown instead of the full selected date range. These bugs are unrelated to the snapshot collection outage but were fixed in the same sprint. If your Sentiment by Platform or Visibility by Platform bar charts were showing incorrect data outside the May 12–18 window, that was this separate display bug β€” now also resolved. πŸ› οΈ No Action Required The backfill is restoring missing data points in stages across all accounts. Most accounts will see full restoration within 24 hours; accounts processed later in the queue may take longer. Missing snapshots cannot be re-triggered or manually filled from within the Search Atlas interface β€” recovery is fully automated. If your dashboards still show gaps after 24 hours, contact support via the chat widget in your Search Atlas dashboard. πŸ“‘ Engineering Status - Root cause confirmed: Snapshot collection failed between May 12–18, 2026, due to provider downtime and task queue stalls. - Fix developed: An automated gap-detection and backfill system was built to identify and restore all missing snapshots across affected accounts. - Deployed β€” LLMV-460: The backfill solution has been released and is actively restoring affected data points in staged batches. - Secondary bug patched: A secondary bug (backfill skipping days with in-flight failed snapshots) was identified and patched. If gaps persist beyond 24 hours, this edge case may apply β€” contact support so engineering can trigger a targeted re-sweep for your account. - No permanent data loss: All underlying project data is fully intact. - Status as of May 22, 2026: Fully resolved and deployed. πŸ“ž When to Contact Support A member of our support team will proactively reach out to confirm the restoration status for your specific projects. Contact support if: - Your Share-of-Voice or sentiment dashboards still show missing data 24 hours after this update. - You notice data gaps outside the May 12–18, 2026 window. Reach support via the chat widget in your Search Atlas dashboard or through your account contact directly. πŸ’¬ Resolved Support Conversations The following conversations were escalated to a human support agent during this incident and resolved directly. Conversation 1 β€” Missing Share-of-Voice Data (Urgent Client Report) User: Hi, my Share-of-Voice charts are completely blank for the last week. I need this data for a client presentation today β€” is this a known issue? Support (automated): We are aware of a data collection issue impacting Share-of-Voice and sentiment dashboards for May 12–18, 2026. Our engineering team is actively working on a resolution. User: This isn't good enough β€” I need someone to actually look at my account. This is urgent. β€” Escalated to human agent β€” Support Agent (Alex): Hi, thanks for your patience. I've reviewed your account and confirmed your tracked projects are affected by the May 12–18 snapshot gap. I'm flagging your account for priority processing in the backfill queue β€” you should see the missing data restored within 2–4 hours. I'll follow up with you directly once it's confirmed on our end. User: Thank you, I really appreciate that. Support Agent (Alex): Quick update β€” all your Share-of-Voice data for May 12–18 has been restored. Your trend lines should now display complete data. Please refresh your dashboard and let me know if anything still looks off. User: Just checked β€” everything looks perfect now. Thank you! Resolution: Data restored via priority backfill. Confirmed resolved by agent. Conversation 2 β€” Sentiment Dashboard Showing No Data Points User: My sentiment trend chart has no data at all for the past several days. I've tried refreshing and clearing my cache but nothing changes. Support (automated): This is likely related to a known snapshot collection issue affecting May 12–18, 2026. No action is needed from your end β€” a fix is being deployed. User: I've seen that message before and the data still isn't there. Can a real person check this? β€” Escalated to human agent β€” Support Agent (Maria): Hi! I've reviewed your account. Your sentiment dashboard is affected by the May 12–18 data gap and your projects are included in the active backfill. Restoration is in progress β€” your data should be fully populated within the next few hours. I've added a note to monitor your account specifically and will reach out if anything doesn't resolve automatically. User: Okay, thank you for actually looking into it. Support Agent (Maria): Following up β€” the backfill has completed for your account. All sentiment data for May 12–18 is now restored and your trend charts should be accurate and complete. Let us know if you have any other questions! User: Great, all good now. Thanks! Resolution: Sentiment data restored via automated backfill. Agent confirmed completion directly with user. 🎯 The backfill for May 12–18 snapshot gaps has been deployed β€” your Share-of-Voice and sentiment dashboards are restoring complete, accurate trend data in stages with no steps required on your end. Most accounts will see full restoration within 24 hours; if gaps persist after that, contact our support team directly.

Last updated on Oct 26, 2026

πŸ› οΈ Report Builder β€” PDF Download & Public Share Link Troubleshooting

If your Report Builder PDF export fails or a public share link sends viewers to a login page, follow the section below that matches your symptom. Some issues have already been patched; one has a fix in progress. Note: This article covers Report Builder only. If you are troubleshooting a PDF export failure in the GBP Audit Report, that is a separate issue (tracked as GBP-1225) resolved at the platform level β€” contact support if you still see that error. πŸ” Identify Your Symptom First Match your symptom before following any steps β€” each issue has a different fix: - PDF export fails (logged-in user): clicking Export returns a 404 error, the file never downloads, or the button shows no response. - Shared link opens directly to the login page: opening a public share link sends the viewer to the Search Atlas login page instead of displaying the report. - Refresh button inside a shared report crashes to login: the viewer successfully opened the shared report, but clicking a Refresh control inside a section (e.g., AI Summary) redirected them to the login page mid-session. - Public share viewer cannot export PDF: someone viewing a report via a public share link clicks Export to PDF and receives a permission error from the generate-pdf request. πŸ“„ Fix a Failed PDF Export (Logged-In User) Follow these steps if your PDF does not download or returns an error while you are signed in: 1. Reload the Reports β†’ Report Builder (Report Builder) page and wait for the report to fully render before starting the export. 2. Click Download .CSV again. Do not navigate away while the export is processing. 3. Clear your browser cache, open a fresh tab, and retry the export. 4. If the report spans a large date range or contains many widgets, shorten the date range and export again. A successful export triggers a PDF download in your browser within a few seconds. If no download appears after 30 seconds, go to the If the Issue Persists section below. πŸ”— Shared Link Opens Directly to the Login Page If a public share link sends viewers to the login screen on the very first load, regenerate your share link: 1. Open the affected report in Reports. 2. Click the Share & Export button in the report (Reports β†’ Report Builder β†’ open report (Executive Summary)). 3. Select Generate New Link, or toggle the public link off and then back on if no regenerate option is shown. 4. Copy the new link and replace the old one everywhere you previously shared it. 5. Test the new link in a private/incognito window to confirm it loads the report without prompting for login. The new link opens the report directly for anyone who has the URL β€” no login required. πŸ”„ Refresh Button Inside a Shared Report Crashes to Login Previously, a Refresh control was exposed inside certain sections of a public shared report (such as AI Summary). When a viewer clicked it, the session would crash and redirect them to the login page mid-session. This has been fixed at the platform level β€” the Refresh button has been removed from public shared reports, so no action is required on your end. If you still see a Refresh button on a shared report or experience a redirect-to-login mid-session, contact support with the report URL so the team can investigate. πŸ“€ Public Share Viewer Cannot Export PDF If a viewer accessing a report via a public share link clicks Export to PDF and receives a permission error (the generate-pdf request is rejected), this is a known issue with a fix currently in progress but not yet released. There is no self-service workaround available at this time. Contact Search Atlas Support via the in-app chat and include the share link and a screenshot of the error. The team will confirm the case and notify you when the platform update is released. In the meantime, exports performed by a signed-in user on the report owner's account continue to work normally. ⚠️ If the Issue Persists If any symptom continues after completing the steps above, gather the following before contacting support: - The name of the report and the exact error message or behavior you see. - A screenshot of the error, if possible. - Your browser name and version, and your operating system. - Whether you are signed in or viewing via a public share link. Reach out to Search Atlas Support via the in-app chat so the team can investigate your specific report configuration. 🎯 You now know how to handle PDF export failures, shared-link login redirects, the resolved Refresh-button crash, and the pending public-share PDF export issue in Report Builder. For a full walkthrough of Report Builder features and sharing options, see the Report Builder Overview article.

Last updated on Oct 26, 2026

πŸ“Š Search Atlas β€” Google Search Console & Analytics Issues

This article covers Google Analytics 4 (GA4), Google Search Console (GSC), OAuth reconnections, rate limits, report loading failures, property visibility, and analytics filtering behavior inside Search Atlas. ⚠️ Error 1: Analytics dashboard shows "Rate limit exceeded" β€” no data visible What's happening: This is our most frequent error: 124,000+ occurrences affecting 2,800+ users. Google's Analytics Data API (GA4) rate-limits how many properties can be queried simultaneously. Steps to try: - Wait 15–30 minutes and reload β€” the rate limit resets hourly - If you have many GA4 properties connected, disconnect properties you are not actively using - This is a Google API limitation β€” Search Atlas is actively working on request throttling improvements ⚠️ Error 2: Individual GA4 reports (organic traffic, landing pages, sessions) fail to load What's happening: Individual report types hit GA4 rate limits separately. You may see some reports load while others fail. Steps to try: - Click the Retry button on any failed report - Avoid loading all analytics widgets simultaneously β€” load one section at a time - Each report type rate-resets independently, so retrying staggered (2–3 minutes apart) improves success rate ⚠️ Error 3: Search Console data not syncing β€” "Disconnected" status What's happening: Google OAuth tokens expire. When this happens, all GSC data stops refreshing. Steps to try: - Top-right Corner Avatar β†’ Settings β†’ Integrations β†’ GSC - Authorize your Google account again - Data will resume syncing within 1 hour of reconnection ⚠️ Error 4: Keyword rankings in GSC differ from what Google shows directly What's happening: GSC reports data with a 2–3 day processing delay on Google's side. Search Atlas shows what Google has reported, not real-time data. Steps to try: - The data you see is accurate as of 2–3 days ago - For same-day ranking data, use: Left Sidebar β†’ Keyword β†’ Keyword Research β†’ Type Your Keywords β†’ Select the geographical location β†’ Search ⚠️ Error 5: Sort/filter options on the Pages report cause a validation error What's happening: A validation issue exists with certain sort parameters in the Pages view, affecting 230+ users. Steps to try: - If a sort causes an error, click the column header again to reset to default sort - Use the Filter panel instead of column sort for filtering by clicks or impressions - This is a known bug being addressed in the next release ⚠️ Error 6: GA4 property not appearing in the connection dropdown What's happening: Only GA4 properties where your Google account has Viewer role or higher will appear. Steps to try: - Confirm in Google Analytics that your Google account (the one you connected) has access to the property - If access was recently granted, disconnect and reconnect your Google account in Search Atlas to refresh the property list ⚠️ Error 7: GSC shows "No data for this date range" What's happening: GSC data is only available from the date your property was connected. Historical data before connection is not available. Steps to try: - Adjust the date range to start from after your connection date - Search Atlas stores your GSC data β€” data will accumulate over time from the connection date forward ⚠️ Error 8: Analytics shows data for a different country than expected What's happening: GA4 reports use the default property settings. If your property is set to report globally, you'll see global data. Steps to try: - Use the Country filter at the top of the Analytics dashboard to filter by specific country - To make a country filter permanent, save it as a custom view in your dashboard settings Most Google Analytics and Search Console issues are not caused by broken Search Atlas integrations. They are usually related to: - Google API rate limits - OAuth token expiration - delayed Google-side processing - property permission mismatches - or filtering and reporting configuration differences Because Search Atlas depends directly on Google's APIs and reporting infrastructure, temporary delays and throttling behavior are expected during periods of heavy demand. πŸ‘‰ The best experience comes from: - keeping only active GA4 properties connected - refreshing OAuth permissions regularly - understanding Google’s built-in reporting delays - and loading analytics widgets progressively instead of all at once Report Builder shows blank or no GSC data If Google Search Console data is blank or missing in Reports, first confirm that the Google account connected in Search Atlas has access to the affected Search Console property. In Top-right avatar β†’ Settings β†’ Integrations β†’ GSC, reconnect the account if the connection is incomplete. If the property selector is empty, connect the Google account directly for your own user; team-member seats may require a per-user connection even when the account-level integration appears connected. If the property is visible in Search Console but Reports still shows no data, check the selected date range and remember that Google Search Console data can have a processing delay. Record the affected domain, report name or ID, selected date range, and a screenshot of the blank section. If the problem continues after reconnection and a refresh, contact support in live chat with those details.

Last updated on Oct 26, 2026

πŸ”— GA4 Property Update Not Reflected on Project Details Page

If you updated your GA4 property on the Search Atlas homepage and received a success message, but the Project Details page still shows "Connect Google Analytics with OTTO", your connection is intact β€” a display sync bug caused this false state, and it has since been resolved. A hard refresh confirms your updated connection; reconnect manually only if the issue persists. πŸ” What This Issue Looks Like After a successful GA4 property update on the homepage, the Project Details page may show: - A "Connect Google Analytics with OTTO" prompt, as though GA4 was never configured - The GSC Connections panel listing GA4 as not connected These were display-only errors β€” your GA4 property update was applied correctly in the background. No data was lost and no reconnection was required. βœ… How to Confirm Your GA4 Connection Is Working A hard refresh forces the Project Details page to load the latest connection state from the server: 1. Navigate to the Project Details page for the affected project. 2. Press Ctrl + Shift + R (Windows / Linux) or Cmd + Shift + R (Mac) to hard refresh. 3. Open the GSC Connections panel on the Project Details page. 4. Confirm your GA4 property is listed as Connected. After the hard refresh, the connection status reflects your most recent GA4 update. πŸ› οΈ What to Do If GA4 Still Shows as Disconnected If the disconnected prompt persists after a hard refresh, reconnect GA4 directly from the Project Details page: 1. On the Project Details page, click Connect Google Analytics with OTTO. 2. Select your GA4 property from the dropdown list. 3. Click Connect to confirm. You'll see your GA4 property listed as Connected in the GSC Connections panel once saved. If your GA4 property doesn't appear in the dropdown Verify that the Google account linked to Search Atlas has at least Viewer permission on the GA4 property. Check this in Google Analytics β†’ Admin β†’ Property Access Management. Once access is confirmed, return to the Project Details page and reconnect. βš™οΈ How to Update Your GA4 Property from the Search Atlas Homepage To change which GA4 property is linked to your project: 1. Go to the Search Atlas Homepage and locate your project card. 2. Click the More actions for [domain] menu on the project card to open Project Settings. 3. Under Google Analytics 4, select the new property from the dropdown. 4. Click Save. A green confirmation message confirms the update was applied. 5. Navigate to the Project Details page and hard refresh (Ctrl + Shift + R / Cmd + Shift + R) to confirm the change is reflected in the GSC Connections panel. The Project Details page now syncs GA4 connection status in real time after each homepage update. 🎯 The GA4 display sync issue has been resolved β€” your property update was never lost, even when the Project Details page showed a disconnected state. If you continue to see connection problems after following these steps, contact the Search Atlas support team for further assistance.

Last updated on Oct 26, 2026

πŸ“Š Troubleshooting Stalled Metric Growth in Search Atlas

πŸ” Overview If your domain's authority score, UX signals, or content score appear frozen or not improving in Search Atlas, you are not alone. Metric growth can stall for several reasons β€” some related to your site's activity, others related to how and when Search Atlas collects and processes data. This article walks you through the most common causes and what you can do about each one. βš™οΈ How Search Atlas Updates Site Metrics Search Atlas recrawls and recalculates domain-level metrics on a regular schedule. Because this process involves large volumes of data across many domains, updates are not instant. Here is what to keep in mind: - Processing lag is normal. After you publish new content, earn backlinks, or improve page experience, it can take two to six weeks before those changes are fully reflected in your scores. - Scores are relative. Authority, UX, and content scores are benchmarked against competing domains. Even if your site improves in absolute terms, your score may stay flat if competing sites improve at the same pace. - Data pipelines occasionally experience delays. Our engineering team monitors for processing issues and resolves them proactively. If metrics appear completely frozen for more than three weeks with no movement whatsoever, this may indicate a data pipeline issue that requires investigation. πŸ“‹ Step-by-Step: Check Your Site Metrics 1. In the left sidebar, click Site Metrics to open the Site Explorer list at /site-explorer/list. 2. Locate your domain (for example, www.quicksortindia.com) and open its detail view. 3. Note the last updated timestamp shown on the metrics panel. If this date is more than three weeks old, the data may be awaiting a refresh cycle. 4. Check the trend graph for each metric β€” authority, UX signals, and content score. A flat line over a short period (under four weeks) is usually normal. A completely unchanged score over six or more weeks warrants further review. 5. Use Left sidebar β†’ Keywords β†’ Rank Tracker (Keyword Rank Tracker) to confirm whether your keyword rankings are also static. If rankings are moving but scores are not, the scoring pipeline may still be processing recent changes. πŸ’‘ Common Reasons Metrics Stall β€” and What to Do - Not enough new content or backlinks. Authority scores respond to consistent link acquisition and topical depth. If your link profile and content output have not changed, your score will not change either. Use Left sidebar β†’ Site Metrics β†’ Keyword Gap to find content opportunities you may be missing. - Content score is low due to thin or off-topic pages. The content score reflects topical coverage and relevance across your domain. Adding well-structured, in-depth content on your core topics is the most reliable way to improve it over time. - UX signals need technical improvements. UX signal scores factor in page speed, mobile usability, Core Web Vitals, and similar signals. Run a technical audit on your site and address any flagged issues to give this score room to grow. - Domain was recently added. Newly added domains have limited historical data. Scores for new domains often remain low for the first one to three months as Search Atlas accumulates enough data to calculate reliable metrics. - Competing domains are improving faster. Because scores are relative, rapid competitor improvements can offset your own gains. Use Left sidebar β†’ Site Metrics β†’ Keyword Gap to identify where competitors are outpacing you and prioritise those gaps. πŸ› οΈ What to Do If Metrics Have Not Updated in Over Three Weeks If your last-updated timestamp shows the data is more than three weeks old and you have confirmed this is not simply a display lag, follow these steps: 1. Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to rule out a cached view. 2. Log out of Search Atlas, clear your browser cache, and log back in. 3. Check whether the issue affects only one domain or all domains in your account. A single stalled domain is different from a platform-wide delay. 4. If the data is still not updating after the steps above, contact support immediately so our team can investigate the data pipeline for your specific domain. πŸ“ˆ Best Practices to Support Consistent Metric Growth - Publish new, topically relevant content on a regular schedule β€” at minimum two to four pieces per month. - Build backlinks consistently through outreach, digital PR, or partnerships rather than in sporadic bursts. - Address Core Web Vitals and mobile usability issues promptly, as these directly influence UX signal scores. - Monitor your Rank Tracker weekly so you can correlate ranking improvements with eventual score changes. - Use the Keyword Magic tool (Left sidebar β†’ Keywords β†’ Keyword Magic) to discover high-opportunity keywords that can accelerate topical authority growth. πŸ†˜ Still Need Help? If you have followed the steps above and your metrics are still not updating, or if you believe there may be a data issue specific to your domain, we are here to 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Fix Heatmap Pins Not Showing in Reports

πŸ” Overview If your Local SEO heatmap pins appear inconsistently in reportsβ€”sometimes showing fully, sometimes showing only one pin, or disappearing after a refreshβ€”the cause is often a screen resolution or responsive layout rendering issue, not a data or configuration problem. This article walks you through diagnosing and resolving the issue step by step. ⚠️ Symptoms - Heatmap pins appear on some views but not others - Only one small pin displays consistently after refreshing - Pins load correctly in one browser window size but not another - The heatmap grid appears compressed, cut off, or partially rendered - Refreshing the report does not restore the missing pins πŸ–₯️ Why Screen Resolution Causes This The Local SEO heatmap uses a responsive layout that scales the pin grid based on the available screen width. On smaller screens, lower display resolutions, or browser windows set below a minimum width threshold, the rendering engine may compress the gridβ€”causing pins to overlap, fall outside the visible area, or collapse into a single point. This is a known display behavior, not a data loss issue. Your heatmap data remains intact. 🧭 Step 1 β€” Reproduce the Issue Before applying fixes, confirm that screen resolution is the cause: 1. Go to Left sidebar β†’ Reports and open the affected report. 2. Note your current browser window size. 3. Resize your browser window to full screen or increase it to at least 1280 px wide. 4. Reload the report page. 5. Check whether more pins now appear on the heatmap. If the pins return at a wider window size, screen resolution is confirmed as the root cause. Continue to Step 2. πŸ› οΈ Step 2 β€” Apply Recommended Workarounds Use one or more of the following fixes depending on your setup: - Maximise your browser window: Expand the browser to full screen (press F11 on Windows or use the green maximise button on Mac) and reload the report. - Increase display resolution: On Windows, go to Settings β†’ Display β†’ Resolution and select 1920 Γ— 1080 or higher. On Mac, go to System Settings β†’ Displays and choose a higher resolution or a larger scaled size. - Set browser zoom to 100%: A browser zoom level above 100% reduces effective screen width. Press Ctrl + 0 (Windows) or Cmd + 0 (Mac) to reset zoom to default, then reload the report. - Use a larger monitor or device: If you are viewing on a laptop with a small screen, try opening the report on a desktop monitor with a wider display. - Switch to a Chromium-based browser: Chrome or Edge at full screen on a 1080p or higher display provides the most reliable heatmap rendering. πŸ“ Step 3 β€” Verify the Heatmap Data Is Intact After adjusting your resolution or window size, confirm your data is complete: 1. Go to Left sidebar β†’ GBP Projects β†’ Overview and select the relevant GBP project. 2. Confirm that your heatmap scan dates and keyword configurations are still listed and intact. 3. Return to Left sidebar β†’ Reports, open the report, and verify that the full pin grid now renders correctly. If the pin count matches your expected scan grid (for example, a 7 Γ— 7 grid should show 49 pins), the data was never lostβ€”only the display was affected. πŸ”„ Step 4 β€” Re-run a Scan if Pins Are Still Missing If you have confirmed your resolution is at least 1280 px wide and pins are still not displaying correctly, a re-scan may be needed: 1. Go to Left sidebar β†’ GBP Projects β†’ Overview and open the affected project. 2. Locate the relevant keyword and heatmap configuration. 3. Trigger a new scan and wait for it to complete. 4. Return to Left sidebar β†’ Reports and check whether the heatmap now displays correctly in the report. βœ… Quick-Reference Checklist - Browser window width is at least 1280 px - Browser zoom is set to 100% - Display resolution is 1920 Γ— 1080 or higher - Using a Chromium-based browser (Chrome or Edge recommended) - Heatmap data verified as intact in Local β†’ GBP Projects β†’ Overview - Re-scan triggered if pins remain missing after display fixes πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fixing the "Disabled Rank Tracker Connection" Error When Downloading Reports

πŸ“‹ Overview If you see an error when you try to view or download a full report from Report Builder, the most common cause is a disabled or disconnected Rank Tracker. Report Builder pulls keyword ranking data directly from your Rank Tracker project. When that connection is turned off, expired, or missing, the report cannot finish loading and the download fails. This article explains why the error happens and walks you through restoring the connection so your reports generate normally. πŸ€” Why This Error Happens Your reports depend on an active data source. The error usually appears for one of these reasons: - The Rank Tracker for the project was paused or disabled. - The report is linked to a Rank Tracker project that was deleted or renamed. - Keyword tracking for the project ran out of available quota or was never set up. - The project was recently created and has not yet collected ranking data. - The Rank Tracker project is still processing and is stuck in an Updating state, so the latest ranking data has not finished syncing. - A temporary backend error on the Rank Tracker reporting endpoint prevented the report from loading. These service-side errors are typically resolved by our engineering team. βœ… Step 1: Confirm the Rank Tracker Is Enabled 1. Log in to your Search Atlas dashboard. 2. In the left sidebar, open Keywords. 3. Go to Rank Tracker (Keyword Rank Tracker) and select the project tied to your report. 4. Check the status indicator. If it shows as Disabled or Paused, select Enable to turn it back on. 5. Confirm that keywords are listed and actively being tracked. If keywords are present and the tracker is active, allow a few minutes for the data to sync before returning to Report Builder. If the project stays in an Updating state for an unusually long time (for example, several hours) and never finishes, the data refresh may be stuck. Allow more time for it to complete, and if it does not, contact support so we can investigate the project's sync. πŸ” Step 2: Verify the Report's Data Source If the Rank Tracker is enabled but the error continues, the report may be pointing to the wrong project. 1. Open Report Builder. 2. Select the report that is failing to download. 3. Open the report settings and review the connected project and Rank Tracker source. 4. If the linked project is incorrect or no longer exists, choose the correct active project from the dropdown. 5. Confirm the report is set to the correct location. Report Builder pulls rankings per location, so a report tied to the wrong location can show missing keywords or rank positions that don't match your Rank Tracker. 6. Save your changes. If a keyword's rank position or location in the report does not match what you see in the Rank Tracker, double-check the location associated with that keyword β€” this is especially important when the same keyword is tracked across multiple locations. πŸ“Š Step 3: Check Keyword Quota Rank Tracker connections can be automatically disabled when your plan's keyword limit is reached. 1. Go to Settings and open the Usage or Subscription section. 2. Review your tracked keyword usage against your plan limit. 3. If you are at your limit, remove unused keywords or upgrade your plan to free up capacity. 4. Return to the Rank Tracker and confirm it is now active. πŸ”„ Step 4: Regenerate the Report Once the connection is restored, refresh the report data: 1. Open the report in Report Builder. 2. Select Refresh or Regenerate to pull the latest data. 3. Wait for the report to finish loading completely. 4. Choose View report to confirm the error is resolved. πŸ’‘ Tip: Allow Time for New Projects If you just enabled the Rank Tracker or created a new project, ranking data can take up to 24 hours to populate. Reports built before data is available may still show the error until the first tracking cycle completes. πŸ†˜ Still Seeing the Error? If you have completed all the steps above and the report still will not download, the cause may be a backend service error on the report's Rank Tracker connection rather than a setting on your end. Contact our support team and include the following details so we can help faster: - The name of the affected report. - The project and Rank Tracker it is connected to. - A screenshot of the exact error message. - The date and approximate time you encountered the issue. Our team can then check the connection on the backend and restore your report access.

Last updated on Oct 26, 2026

πŸ› οΈ Keyword Explorer Metrics Timeout: "The read operation timed out"

If your keyword metrics in the Keyword Explorer fail to load with a "The read operation timed out" error, wait a few moments and retry the search β€” a single keyword at a time usually succeeds. This is an intermittent timeout when fetching data from our SEMrush data source, not a problem with your account. πŸ” What's Happening in the Keyword Explorer When you run a lookup in the Keyword Explorer, the tool fetches keyword and SEO metrics from our SEMrush data source. Occasionally that upstream request times out before the data returns. When this happens, you may notice: - Keyword and SEO metrics fail to load or appear empty. - An error message reading The read operation timed out. - The tool appears stuck or returns an error instead of results. Who's affected: Any customer running a keyword lookup in the Keyword Explorer can see this intermittently. It is more likely when looking up a large batch of keywords at once. πŸ› οΈ Workaround Steps to Load Your Keyword Metrics This is an intermittent upstream timeout, so a retry usually works. Follow these steps in order: 1. Wait a few moments, then run the same keyword lookup again in the Keyword Explorer. 2. If it fails a second time, search for a single keyword instead of a large batch. 3. If the error continues, refresh the page, pause briefly, then re-run your search. You'll know it worked when your keyword and SEO metrics load and display as expected. πŸ“‘ Engineering Status for the SEMrush Timeout Our team is aware of this intermittent timeout and has already addressed the underlying cause that triggers the read operation to time out. You should see this continue to improve over time. πŸ“ž When to Contact Search Atlas Support Reach out to our support team if the timeout keeps blocking your work after you've tried the steps above. To help us assist you quickly, include: - The exact keyword or keywords you searched. - The error message you saw, such as The read operation timed out. - The approximate date and time of your search. You can contact support through the in-app chat or your usual support channel. πŸŒ€ Your account is fine and your data is safe β€” this is a temporary upstream timeout that our team has already worked to resolve, and a quick retry will get your keyword metrics loading again.

Last updated on Oct 26, 2026

πŸ“Š Fix Google Analytics and Heatmap Data Not Syncing

πŸ” Overview If your Search Atlas reports are not reflecting Google Analytics or heatmap data β€” even after confirming your integrations are active β€” there are several common causes. This article walks you through the most effective troubleshooting steps to restore accurate data across all affected reports. βš™οΈ Step 1: Verify Your Integration Status Before anything else, confirm that your Google Analytics integration is properly connected and authorized inside Search Atlas. 1. Log in to your Search Atlas account. 2. Navigate to your account settings by clicking your Avatar Menu (πŸ‘€) in the top-right corner. 3. Locate the Integrations section and confirm that Google Analytics shows a Connected status. 4. If the status shows Disconnected or Error, click Reconnect and re-authorize access through your Google account. 5. Ensure the correct Google Analytics property and data view are selected for each project. πŸ› οΈ Step 2: Check Heatmap Tracking Script Installation Heatmap data requires a tracking script to be installed on your website. If this script is missing or placed incorrectly, no heatmap data will be recorded or displayed. - Confirm the Search Atlas heatmap tracking script is present in the <head> section of every page you want to track. - If you recently updated your website theme, CMS, or tag manager setup, the script may have been removed. Re-add it and allow 24–48 hours for data to populate. - Use your browser's developer tools (right-click β†’ Inspect β†’ Sources or Network tab) to verify the script is loading without errors. ⏳ Step 3: Allow Sufficient Data Processing Time Both Google Analytics and heatmap data are not always available in real time. Processing delays are normal and typically resolve on their own. - Google Analytics data can take up to 24–48 hours to appear in your reports after a new connection or reconnection. - Heatmap data requires actual user visits to your pages before it will display. Low-traffic pages may take several days to show meaningful results. - If you recently created a new report, wait at least 48 hours before assuming there is a sync issue. πŸ“Š Step 4: Review Report Date Ranges and Filters Incorrect date ranges or active filters are a common reason reports appear empty or incomplete. 1. Open the affected report inside Search Atlas. 2. Check the date range selector and ensure it covers a period when your integrations were active and your site was receiving traffic. 3. Review any active filters β€” segment filters, device filters, or URL filters β€” that may be limiting the data displayed. 4. Reset filters to their default state and re-run the report to see if data appears. πŸ”„ Step 5: Disconnect and Reconnect the Integration If data is still missing after completing the steps above, a full reconnection often resolves underlying authorization or token expiry issues. 1. Go to your account Integrations settings. 2. Click Disconnect next to Google Analytics. 3. Wait 30 seconds, then click Connect and complete the Google authorization flow again. 4. Re-select the correct Analytics property and view for each affected project. 5. Navigate to Left sidebar β†’ Site Metrics (Site Explorer) and open one of your affected reports to confirm data is now loading. πŸ’‘ Additional Tips - If the issue affects multiple reports, the root cause is almost always the integration itself β€” a single reconnection should resolve all of them at once. - Make sure the Google account you use to connect Analytics has at least Viewer-level permissions on the Analytics property. - Ad blockers or privacy browser extensions on your own machine can sometimes prevent heatmap scripts from firing during your own visits β€” test with extensions disabled. - If you are using Google Tag Manager to deploy the heatmap script, confirm the tag is set to fire on All Pages and that the container is published. πŸ†˜ Still Need Help? If you have completed all the steps above and your Analytics or heatmap data is still not appearing in your reports, our team is ready to 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Fix Missing Heatmap Comparison Data in PDF Reports

πŸ” Overview When you download an individual Local SEO Heatmap report from Report Builder, the business results comparison section may appear blank in the exported PDF. This is a known display issue most commonly caused by cached browser data interfering with how the report renders before download. Following the steps below β€” starting with clearing your browser cache β€” resolves this in the majority of cases. 🧹 Step 1: Clear Your Browser Cache (Primary Fix) A stale browser cache is the most common cause of comparison data not populating in downloaded Heatmap PDFs. Clear it before trying anything else. 1. In Google Chrome, press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) to open the Clear browsing data panel. 2. Set the Time range to All time. 3. Check Cached images and files and Cookies and other site data. 4. Click Clear data. 5. Close and reopen your browser, then log back in to Search Atlas. 6. Navigate to Left sidebar β†’ Report Builder and open your Local SEO Heatmap report. 7. Attempt the PDF download again and confirm the comparison data is now populating. If you use a browser other than Chrome, locate the equivalent cache-clearing option in your browser settings β€” the steps are similar in Firefox, Edge, and Safari. πŸ“„ Step 2: Re-Download the Report from Report Builder After clearing your cache, follow these steps to download the Heatmap report correctly. 1. Go to Left sidebar β†’ Report Builder. 2. Locate and open the relevant project in your reports list. 3. Find the Local SEO Heatmap report you need. 4. Click the download or export option to generate the PDF. 5. Open the downloaded file and verify that the business results comparison section is fully populated. πŸ”„ Step 3: Try an Incognito or Private Window If clearing the cache does not resolve the issue immediately, open an incognito or private browsing window. This bypasses any remaining cached data or browser extensions that may be interfering with report rendering. 1. Open a new Incognito window in Chrome (Ctrl + Shift + N / Cmd + Shift + N) or an equivalent private window in your browser. 2. Log in to Search Atlas and navigate to Left sidebar β†’ Report Builder. 3. Open the Local SEO Heatmap report and attempt the PDF download again. βš™οΈ Step 4: Check Your Local SEO Heatmap Setup If comparison data is still missing after the cache fix, confirm that your Heatmap report is configured correctly in the Local section of the platform. - Navigate to Left sidebar β†’ GBP Projects β†’ Overview and confirm the business profile associated with the report is active and properly connected. - Ensure that at least one competitor has been added to the Heatmap configuration. Comparison data requires competitor entries to be present β€” without them, the comparison section will remain empty even in a correctly rendered PDF. - If you recently added competitors or made configuration changes, allow a short processing window before downloading. Newly added data may not appear instantly in exported reports. πŸ–₯️ Step 5: Switch Browsers If the issue persists across the steps above, try downloading the report using a different browser entirely. Browser-specific rendering behaviour can occasionally affect how PDF exports are generated, and switching browsers is a quick way to rule this out. ⚠️ When to Escalate If you have completed all of the steps above and the business results comparison data is still not appearing in your downloaded PDF, the issue may require investigation on the platform side. 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.

Last updated on Oct 26, 2026

🧠 Fix Atlas Brain Report Links Not Opening

πŸ” Overview After running a playbook in Atlas AI β€” such as an AI Citation Gap analysis β€” the session may show a completed report, but clicking the report link does nothing. No file downloads, no new tab opens, and no results appear. This article explains the most common causes and how to fix them. ⚠️ Common Causes - Compact mode interference: Atlas Brain report links do not function correctly when the interface is in compact mode. Switching to the standard view resolves this. - Previous session conflict: If your last session was in Classic View mode, Atlas Brain may not load or run correctly in a new session until the view is reset. - Browser or display issue: Pop-up blockers, browser extensions, or cached session data can silently block report links from opening. - Unsupported content type: Certain content β€” such as reports generated from non-Latin character sets β€” may not preview or download correctly in all environments. πŸ› οΈ How to Fix It 1. Switch out of compact mode. In the Atlas AI interface, look for the view toggle and make sure you are not in compact mode. Switch to the standard or full view, then try clicking the report link again. 2. Reset your session view. If you previously used Classic View, start a fresh Atlas Brain session. Navigate away from the current session, return to Atlas AI, and open a new session from scratch. This clears any view-mode conflicts that may be blocking the report. 3. Check your browser settings. Make sure pop-ups are allowed for the Search Atlas platform. Disable any browser extensions that block pop-ups or redirects (such as ad blockers), then reload the page and retry. 4. Clear your browser cache. A stale cache can cause outdated session states to persist. Clear your cache and cookies for the Search Atlas domain, then log back in and reopen the report. 5. Try a different browser. If the issue continues, open Search Atlas in a different browser (e.g. Chrome, Firefox, or Edge) to rule out a browser-specific problem. 6. Re-run the playbook if needed. If the report link is still unresponsive after the steps above, return to Atlas AI and run the playbook again in the standard view. The new session should generate a working, accessible report. πŸ“Š Accessing Your Reports All completed Atlas Brain reports are also accessible from the Reports section. In the left sidebar, click Reports (or navigate to /report-builder/projects-list) to view and download your saved reports directly β€” without needing to return to the original Atlas AI session. πŸ’‘ Tips to Prevent This Issue - Always run Atlas Brain playbooks in standard view, not compact mode. - Start a new session if you have recently switched between Classic View and Atlas Brain modes. - Keep pop-up blockers disabled or whitelisted for the Search Atlas platform. - Use an up-to-date version of your browser for the best compatibility. πŸ™‹ 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.

Last updated on Oct 26, 2026

πŸ” Fix Site Metrics Quota Errors on Trial Accounts

🧭 Overview If you signed up for a 7-day trial and see a quota error when trying to access Site Metrics β€” even though your usage dashboard shows 0/0 utilization β€” you are not alone. This is a known behaviour specific to trial accounts and is related to how credits and quotas are provisioned during the trial period. ⚠️ Why This Happens Trial accounts use a separate quota system called Universal Credits. During the trial, a cap is applied to Universal Credits to limit usage to trial-tier levels. When that cap is reached or is not correctly initialised, the platform returns a quota exhaustion error β€” even if the usage counter appears to show zero. In short, the 0/0 display is a cosmetic mismatch. The underlying billing system has already flagged the account as having reached its trial credit limit, which blocks access to data-intensive tools like Site Metrics. πŸ› οΈ What You Can Do Right Now 1. Verify your trial status. Go to your account settings and confirm your trial is still active and has not expired early due to a billing or provisioning issue. 2. Try accessing Site Metrics again after a few minutes. Navigate to Left sidebar β†’ Site Metrics (or go to /site-explorer/list). Occasional provisioning delays can cause temporary errors that resolve on their own. 3. Check sub-tools individually. Some trial accounts have partial access. Try navigating to Left sidebar β†’ Keywords β†’ Keyword Magic or Left sidebar β†’ Keywords β†’ Rank Tracker (Keyword Rank Tracker) to see if specific features are available. 4. Upgrade your plan. If you need immediate, full access to Site Metrics and all sub-tools, upgrading from a trial to a paid subscription removes the Universal Credit cap and fully unlocks your quota. πŸ“Š Understanding Trial Quota Limits Trial accounts are intentionally capped on certain high-usage features to reflect trial-tier access. Here is what to expect: - Site Metrics: Limited by Universal Credit caps; quota errors may appear even at 0/0 displayed usage. - Keyword Magic, Rank Tracker, Keyword Gap: Accessible via Left sidebar β†’ Site Metrics, but subject to the same trial credit restrictions. - OTTO SEO: Available at Left sidebar β†’ OTTO SEO β†’ All Sites (SEO Automation) β€” trial access may also be limited depending on your provisioned tier. βœ… After Upgrading to a Paid Plan Once you upgrade, your quota is re-provisioned automatically by the billing system. You should regain full access to Site Metrics and all related tools within a few minutes. If access does not restore after upgrading, try refreshing the page or logging out and back in. πŸ’‘ Frequently Asked Questions - Why does my quota show 0/0 if I have hit a limit? The usage counter displayed in the UI reflects a different metric than the Universal Credit cap applied at the billing level. The two can fall out of sync during the trial period β€” this is a known issue our engineering team is actively working to improve. - Will my trial days be refunded if I could not access Site Metrics? Please contact our support team via the chat widget (see below) and a teammate can review your account and advise on next steps. - Is this happening to everyone on a trial? Not all trial accounts are affected. The error is more likely to occur when quota provisioning does not complete successfully at signup. πŸ™‹ 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.

Last updated on Oct 26, 2026

πŸ› οΈ Report Builder Bug Fixes and Improvements

The Report Builder received bug fixes and one improvement in the July 20, 2026 release, addressing issues with date range filtering, layout saves, GSC keyword sorting, an unintended drawer trigger, and missing report screenshots. If you are experiencing any of these issues, use the information below to determine whether this release resolves your situation. What's New This release ships the following fixes and improvements: - Historical Metrics chart date range fix: The Historical Metrics chart now correctly reflects the date range you select, instead of ignoring your input and displaying default data. - Classic layout save error fix: Saving a classic Report Builder layout no longer returns a 400 error. - GSC keyword tabs sorting and filters fix: The All, Top, and Trending keyword tabs in the GSC section now apply sorting and filters correctly. - GHL Hide Empty Sections fix: Checking the Hide Empty Sections checkbox in the GHL Report Builder no longer unintentionally triggers an unrelated drawer or panel to open. - Placeholder for missing report screenshots: When a report screenshot is missing or broken, a default placeholder image is now displayed instead of a blank or broken image area. How to Confirm the Fix Applies to You If you first noticed the problem before July 20, 2026, the release should have resolved it automatically β€” no action is required on your end. If the problem started on or after July 20, 2026, use the steps below to verify everything is working correctly. 1. Open Reports in the platform. 2. Select or open an existing report and set a custom date range β€” confirm the Historical Metrics chart reflects your selection rather than default data. 3. If using a classic layout, save your report and confirm the save completes without a 400 error. If the error still appears, note the exact error message and the name of the report or layout affected. 4. Navigate to the GSC section of your report and switch between the All, Top, and Trending keyword tabs β€” confirm that sorting and filter selections are being applied correctly on each tab. 5. If using the GHL Report Builder, toggle the Hide Empty Sections option and confirm no unrelated panel opens unexpectedly as a result. 6. Open any report that previously showed a blank or broken image area and confirm a placeholder image now appears in its place. What to Expect - These are bug fixes; no changes to your existing report configurations or data are required. - The placeholder image appears automatically for any missing or broken screenshot β€” no manual action is needed. - If you previously worked around the 400 save error on classic layouts, saves should now complete successfully without any additional steps. If the Issue Persists If any of the above issues are still occurring after July 20, 2026, try the following before escalating: - Hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to ensure you are running the latest version of the platform. - Clear your browser cache and reload, then repeat the verification steps above. - Try reproducing the issue in a different browser or an incognito/private window to rule out a local cache or extension conflict. - If the problem persists, gather the following before contacting support: the name of the affected report or layout, the exact error message (if any), the browser and OS you are using, and the approximate time you observed the issue. 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.

Last updated on Oct 26, 2026

πŸ“Š Why Site Explorer Shows Zero Traffic or Flat Chart

πŸ” Overview If Site Explorer is showing a flat traffic chart, 0 organic traffic, or only 1 organic keyword for your domain, you are not alone. This is a known display issue that can affect certain domains under specific conditions. This article explains the most common causes and what you can do right now. ⚠️ Common Reasons for Zero or Flat Data There are several reasons Site Explorer may show low or missing data for a domain: - New or low-authority domain: Domains with very little indexed content or few backlinks may genuinely have minimal organic visibility in our data sources. - Data indexing delay: Newly added domains or recently crawled sites may not yet have fully populated data. It can take 24–48 hours for metrics to reflect accurately. - Temporary data sync issue: Occasional backend sync delays can cause metrics to appear as zero even when real keyword data exists. This is resolved automatically once the sync completes. - Search type or filter mismatch: An active filter (such as country, date range, or search type) may be excluding most of the domain's data from the view. - Domain format issue: Entering the domain with or without www, a trailing slash, or the wrong protocol (http vs https) can return incomplete results. πŸ› οΈ Steps to Troubleshoot 1. Check the domain format. In the Site Explorer search bar, try both racernationofficial.com and www.racernationofficial.com to see which returns more data. Make sure there are no extra characters or spaces. 2. Clear all active filters. Reset any date range, country, or keyword filters to their default settings. A narrow filter can suppress the majority of results. 3. Switch the search type. If you selected a specific search type (such as Exact URL), try switching to Domain or Prefix mode to capture all pages under the domain. 4. Wait and refresh. If the domain was just added or recently updated, wait 24–48 hours and reload the page. Indexing delays are temporary. 5. Cross-check with the Keywords tab. Navigate to the Keywords tab within Site Explorer. If keywords appear there but the Overview chart still shows zero, this confirms a temporary display sync issue β€” not missing data. 6. Try a different browser or clear cache. Occasionally, a cached page can display outdated zero-state data. Clear your browser cache or open the page in an incognito window. πŸ’‘ What the Flat Chart Means A completely flat line on the organic traffic chart typically indicates one of two things: the domain has had consistently zero tracked traffic over the selected time period, or there is a temporary data rendering issue. If you have confirmed that keywords do exist under the Keywords tab, the chart will correct itself once the backend data sync resolves β€” usually within a few hours. πŸ“‹ Known Platform Behaviour Our engineering team has previously identified and resolved several related issues, including cases where the Site Explorer Overview showed 0 organic keywords and traffic while the Keywords tab correctly displayed thousands of keywords. These were backend sync issues and were fixed at the platform level. If you are seeing this discrepancy today, it may be a recurrence of a similar temporary sync delay. πŸš€ Next Steps if the Issue Persists If you have followed all the steps above and Site Explorer still shows zero traffic or a flat chart for a domain that should have visibility data, please reach out to our team 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.

Last updated on Oct 26, 2026

πŸ“„ Fix Report Builder PDF Download Failures

πŸ” Overview Some users encounter errors when attempting to download a PDF report from Report Builder. The download may fail silently, return an error message, or produce a blurred and unreadable file. This article explains the known causes and the steps you can take before contacting support. βš™οΈ Known Causes of PDF Download Failures Our engineering team has investigated and resolved several PDF-related issues in Report Builder, including: - PDF generation failing for publicly shared reports - Downloads returning a 404 error during generation - Downloaded PDFs appearing blurred or unreadable on certain devices - Multiple combined issues affecting PDF output quality and delivery These issues have been addressed through engineering fixes. If you are still experiencing a failure, follow the steps below. πŸ› οΈ Steps to Troubleshoot 1. Refresh the report page. Navigate to Left sidebar β†’ Reports β†’ [Report] (Executive Summary) and use the Refresh Summary action to make sure the report is using the latest data before attempting the download again. 2. Try the download again. After refreshing, attempt the PDF download once more. Temporary generation errors sometimes resolve on their own after a refresh. 3. Test with a different report. Open a different report and try downloading its PDF. This helps identify whether the issue is limited to one specific report or affects your account more broadly. 4. Check your browser and device. Try the download using a different browser or on a different device. Some PDF rendering issues, including blurred output, have been linked to specific Windows environments or browser configurations. 5. Note the exact error message. If a specific error message appears during the failure, write it down. This detail significantly speeds up the investigation if you need to escalate to support. 6. Record how long the issue has been occurring. Knowing whether the problem started recently or has persisted for days helps the team identify the root cause faster. πŸ“‹ Information to Have Ready If You Contact Support If the steps above do not resolve the issue, the support team will need the following details to escalate efficiently: - The exact error message displayed during the failed download - The link or name of the affected report - How long the issue has been occurring - Whether the issue affects all reports or only specific ones - The browser and operating system you are using Having this information ready before reaching out allows the team to escalate directly to engineering without back-and-forth delays. βœ… What to Expect After Escalation When a PDF download failure cannot be self-resolved, our support team logs a ticket with the specialized engineering team. Once engineering identifies and deploys a fix, a support agent will verify the resolution directly in your account before confirming it with you. You do not need to take any action while the fix is in progress β€” the team will follow up when it is confirmed resolved. πŸ’¬ 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. Additional Notes The 'Generating PDF… This may take up to a minute' message appears but the file never downloads even after several minutes. This is a backend issue not related to browser, internet connection, or report content, requiring support/engineering investigation.

Last updated on Oct 26, 2026

πŸ“Š Fix Site Explorer Zero Data and Flat Charts

πŸ” Overview If Site Explorer is showing a flat chart, zero organic traffic, or only one organic keyword for your domain, you are not alone. This is a known issue that can be caused by several factors β€” from data indexing delays to domain configuration problems. This article walks you through the most common causes and how to fix them. ⚠️ Common Causes of Zero Data or Flat Charts - The domain is new or low-authority: Newly registered or very small domains may have little to no indexed data in our database yet. - Incorrect domain format: Entering the domain with or without www, or including https://, can affect results. - Data indexing delay: Our database refreshes regularly. A recently added domain may take time to populate with full metrics. - The domain has genuinely low organic presence: Some domains simply rank for very few keywords and receive minimal organic traffic β€” this is reflected accurately in the tool. - A platform-side data issue: Occasionally, a technical issue may prevent data from loading correctly even for valid domains. πŸ› οΈ Step-by-Step Troubleshooting 1. Check your domain format. Go to Left sidebar β†’ Site Metrics and locate the domain you are analysing. Make sure it is entered as a root domain (e.g., racernationofficial.com) without https://, www, or trailing slashes unless you specifically need to analyse a subdomain or subdirectory. 2. Try both www and non-www versions. Search for racernationofficial.com and then www.racernationofficial.com separately. One version may have more indexed data than the other. 3. Verify the domain is indexed by Google. Open a new browser tab and search site:racernationofficial.com in Google. If Google returns very few or no results, the site has low organic presence β€” and the flat chart is accurate, not an error. 4. Change the date range. In Site Explorer, expand the date range to the maximum available window. A flat chart on a short range may show more history on a longer view. 5. Check the Search Type filter. Make sure the search type is set correctly (e.g., Organic). Accidentally switching to Paid on a domain with no paid activity will return zero data. 6. Hard-refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear cached data and reload the page fresh. 7. Try a different browser or incognito mode. This rules out browser extension conflicts or local caching issues. 8. Wait and re-check. If the domain was recently added to your workspace, allow up to 24 hours for the data pipeline to fully populate metrics. πŸ“‹ How to Confirm It Is a Platform Issue (Not a Data Issue) If you have completed all steps above and the domain shows strong Google presence (confirmed via the site: search) but Site Explorer still returns zero data or a flat chart, it is likely a platform-side issue. Here is how to confirm: - Test a well-known domain (e.g., nytimes.com or amazon.com) in Site Explorer. If that domain also shows zero data, there is a broader loading issue affecting your account. - Check whether shareable links generated from Site Explorer display metrics correctly. If they appear blank, this also points to a platform-level problem. - Log out of Search Atlas and log back in, then re-open Left sidebar β†’ Site Metrics and re-run the analysis. πŸ’‘ What to Expect for Low-Authority Domains For small or niche websites like racernationofficial.com, it is possible that the domain genuinely ranks for only one or two keywords and receives near-zero measurable organic traffic. Search Atlas reports data as it exists in our index β€” we do not estimate or inflate numbers. A flat chart with minimal keywords is an accurate reflection of the site's current organic footprint, not a tool error. If you want to grow this domain's organic presence, consider using OTTO SEO β†’ All Sites (SEO Automation) to identify optimisation opportunities, or use Left sidebar β†’ Keywords β†’ Keyword Magic to find low-competition keywords to target. πŸ†˜ Still Seeing Zero Data? If you have followed every step above and Site Explorer still shows no data for a domain you believe should have rankings, our support team can investigate further on the backend. 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Fix the Heatmap 'No Quota' Error

πŸ” What Is the 'No Quota' Error? If your heatmaps stop refreshing and you see a no quota error message, it does not always mean you have run out of heatmap credits. In many cases, this error is triggered by a payment processing issue on your account, even if your plan appears active and your quota looks normal inside the platform. This is a known issue our engineering team has identified and resolved for affected accounts. However, if you are still seeing this error, the steps below will help you fix it. πŸ’³ Why a Payment Issue Causes This Error Search Atlas links your heatmap quota to the billing status of your account. When a payment fails, is delayed, or is flagged for review, the system can automatically pause heatmap grid refreshes and display a quota error β€” even if your dashboard still shows available credits. This can affect: - Scheduled heatmap refreshes that stop running silently - New heatmap grids that appear to confirm successfully but never generate - Existing grids that have not updated since their creation date βœ… How to Resolve the Error 1. Check your billing status. Go to your account settings and confirm that your payment method is valid and your most recent invoice has been paid successfully. Look for any failed payment notifications or overdue invoices. 2. Update your payment method if needed. If a charge has failed, add a new card or retry the payment. Once the payment is confirmed, your account billing status will update. 3. Wait up to 15 minutes. After a successful payment, the system needs a short time to re-authorise your quota. Your heatmap refreshes should resume automatically. 4. Trigger a manual refresh. Navigate to Left sidebar β†’ Local β†’ Local SEO Heatmaps, open the affected heatmap project, and manually request a refresh to confirm the error has cleared. 5. Verify the heatmap is generating. If the refresh runs without an error message, your quota has been restored. Allow up to a few hours for the full grid to populate depending on the size of your project. πŸ› οΈ What If My Payment Is Fine but the Error Persists? In some cases, accounts with a clean billing history have still encountered this error due to a backend quota-rejection loop. This means the system incorrectly marked your quota as exhausted and continued rejecting refreshes automatically. Our engineering team has deployed fixes for this issue, but a small number of accounts may still be affected. If your payment is up to date and the error has not cleared after following the steps above, your account may need to be manually reviewed and reset by our team. ⚠️ Important Things to Know - Heatmap grids that were skipped during the error period will not backfill automatically β€” you will need to trigger a manual refresh for affected projects. - The error message shown in the platform currently does not distinguish between a true quota limit and a billing-related block. An improved message is planned for a future update. - Your heatmap credit count displayed on the dashboard may look unaffected even when this error is active, which is why the root cause is easy to miss. πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ“Š Fix Heatmap Comparison Data Missing in PDF

πŸ” Overview When you download an individual Local SEO Heatmap report from the Report Builder, you may notice that the business results comparison data columns or sections appear blank in the exported PDF. This article explains why this happens and the steps you can take to resolve it. βš™οΈ Why Comparison Data Is Missing Comparison data in a Local SEO Heatmap report requires at least two separate heatmap scans to exist for the same location and keyword. The report uses these scans to calculate the difference in rankings between two points in time. If comparison data is not populating in your downloaded PDF, one of the following is likely the cause: - Only one heatmap scan has been completed for the selected location and keyword β€” there is no earlier scan to compare against. - The date range selected in the report does not include two or more scans. - The heatmap scan was recently added to the report and the second data point has not yet been generated. - The individual report was built before a comparison scan was available, and the report configuration has not been refreshed. πŸ› οΈ How to Fix the Issue 1. Verify your heatmap scan history. Go to Left sidebar β†’ GBP Projects β†’ Overview and open the relevant GBP project. Confirm that there are at least two completed heatmap scans recorded for the location and keyword you are reporting on. 2. Check your scan schedule. If you only have one scan, wait until the next scheduled scan completes. Scans run automatically based on the frequency you configured when setting up the project. You can review or adjust the scan frequency inside your GBP project settings. 3. Review the date range in Report Builder. Navigate to Left sidebar β†’ Reports and open the relevant report. Make sure the date range you have selected in the report configuration spans a period that includes two or more heatmap scans. Narrow date ranges may exclude the earlier scan needed for comparison. 4. Rebuild or refresh the report. If the report was created before the second scan was available, the comparison data may not have been pulled in automatically. Open the report in Left sidebar β†’ Reports, remove the Local SEO Heatmap widget, re-add it, and reconfigure the date range. Then download the PDF again. 5. Re-download the PDF. After confirming that at least two scans exist and the date range covers both, download the report again from the Report Builder. The comparison columns should now populate correctly. βœ… Confirming the Fix Once the steps above are complete, open the downloaded PDF and look for the comparison columns in the heatmap section. You should see before and after ranking values alongside the difference indicators. If the data still appears blank after following all the steps, the issue may require further investigation. πŸ’‘ Tips to Prevent This in the Future - Allow at least one full scan cycle to complete before generating a comparison report for a new location or keyword. - Set a consistent scan frequency β€” weekly or bi-weekly scans give you more data points and richer comparison reports over time. - When building a new report in Report Builder, always confirm the date range includes multiple scan dates before downloading. πŸ™‹ 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.

Last updated on Oct 26, 2026

πŸ”΄ Fix Trend Arrows Showing Wrong Direction in Reports

🧭 Overview Trend arrows in your reports are designed to give you a quick visual signal β€” green with an upward arrow for improvement, red with a downward arrow for decline. If you notice a red or downward arrow next to a metric that is clearly increasing, this is a UI rendering issue, not a data accuracy problem. Your underlying data is correct; the directional indicator is simply displaying the wrong state. This article explains why this happens and walks you through the steps to resolve it. ⚠️ How to Confirm You Have This Issue Before troubleshooting, confirm that what you are experiencing matches this specific issue: - The numeric value of the metric is higher than the previous period (for example, organic traffic increased from 1,200 to 1,450 visits). - The trend arrow next to that number is pointing down or displayed in red. - The contradiction is consistent β€” it does not resolve itself after a page refresh. If your numbers themselves look wrong or unexpected, that is a separate data accuracy issue and may be related to filters or sync timing. This article specifically addresses cases where the number is correct but the arrow direction or color does not match it. πŸ” Why This Happens Trend arrow direction is calculated by comparing the current period value against a baseline comparison period. The most common reasons for misalignment are: - Comparison period is set incorrectly. If your comparison window is set to a period when the metric was higher than today, the arrow will show red even if the metric has grown recently. For example, comparing this week to a peak month six months ago will always look like a decline. - Metric direction logic is inverted for that KPI. Some metrics are "lower is better" β€” such as crawl errors, bounce rate, or page load time. If the arrow logic for one of these metrics was applied to a "higher is better" metric, you will see the opposite color. - The report was duplicated or imported with mismatched settings. Cloned or shared reports sometimes carry over comparison period settings from their original configuration, which may not match your current reporting intent. - A rendering glitch after a recent report edit. In some cases, editing a report layout β€” such as reordering columns or changing date ranges β€” can cause the trend indicators to render based on stale cached values until the report is fully refreshed. πŸ› οΈ Steps to Fix the Misalignment 1. Open your report. Go to the left sidebar and select Reports, then choose the affected report from your projects list at /report-builder/projects-list. 2. Check the comparison period setting. At the top of the report, locate the date range controls. Confirm that the Compare To period is set to the interval you intend β€” typically the previous equivalent period (previous week, previous month, or previous year). Adjust it if it is pointing to an unintended timeframe. 3. Verify the metric type. Review whether the metric showing the incorrect arrow is one where a decrease is considered positive (such as bounce rate, error count, or load time). If so, the arrow direction may be correct by design. If the metric should treat an increase as positive, proceed to the next step. 4. Force a full report refresh. Click the Refresh Summary button within the report view (Executive Summary). Do not rely solely on a browser page reload, as this may serve a cached version of the rendered indicators. 5. Re-save the report. If the arrow remains incorrect after refreshing, make a minor edit β€” such as toggling a display option on and off β€” then save the report. This forces the rendering engine to recalculate all visual indicators from the current data. 6. Rebuild the affected widget. If the issue persists on a specific metric widget, remove that widget from the report and re-add it from scratch using the widget library. Reconfigure the metric and comparison period. This clears any corrupted display state tied to the original widget instance. βœ… Confirming the Fix After completing the steps above, the trend arrow should align with the metric value. A green upward arrow should appear next to any metric that has increased relative to the selected comparison period, and a red downward arrow should only appear when the metric has genuinely declined. If the arrows are now consistent with the numbers, no further action is needed. 🚫 What This Issue Is Not To avoid confusion, here is a quick distinction between this issue and other common report problems: - This is not a data sync issue. If your numbers themselves are missing, outdated, or appear lower than expected, that may be related to API sync delays or active filters β€” which require separate troubleshooting. - This is not a permissions issue. All users with access to a report see the same rendered indicators. - This is not caused by ad blockers or browser extensions in the vast majority of cases, though clearing your browser cache is always a safe first step if behavior seems erratic. πŸ’¬ Still Seeing the Wrong Arrow Direction? If you have followed all the steps above and the trend arrow direction still does not match the metric value, the issue may require a manual review of your report configuration by our team. 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.

Last updated on Oct 26, 2026

πŸ“Š Fix GSC Performance Data Not Showing in Projects

πŸ” Overview Connecting your Google Search Console (GSC) account to Search Atlas is only the first step. For performance data β€” such as impressions, clicks, and search queries β€” to appear inside your project's Site Audit and other reports, GSC must also be enabled for each individual project. Skipping this activation step is the most common reason GSC data shows as empty even when your property appears correctly connected. ⚠️ Two Separate Steps: Connection vs. Activation Many users assume that linking their GSC account once is enough. In Search Atlas, there are two distinct steps: - Step 1 β€” Connect your GSC account: This authorises Search Atlas to access your Google Search Console data. It is done once at the account level. - Step 2 β€” Enable GSC per project: This activates the data feed for a specific project. It must be done individually for every project where you want GSC performance data to appear. This step is separate from the account connection and is the step most often missed. If Step 2 is not completed, your project will show no GSC performance data regardless of whether your account is connected or your property variant is correct. βœ… How to Enable GSC for a Project To enable GSC data for a specific project, navigate to Site Metrics β†’ Site Explorer β†’ Open Google Search Console (Manage Sites / Connect GSC Account). From there, enable GSC for that project and save your settings if prompted. Once enabled, return to your project's Site Audit or performance reports β€” GSC data will begin populating. Depending on the volume of data, it may take a short time to fully load on the first activation. If you are unsure where to find the GSC settings for your project, please reach out to our support team for guided assistance. πŸ› οΈ Still Not Seeing Data? Check These Common Causes If you have enabled GSC for a project and data is still not appearing, review the following: - Property variant mismatch: Ensure the GSC property connected to your project matches exactly how your site is verified in Google Search Console. Common mismatches include https:// vs http://, or www vs non-www versions. Use the Domain property in GSC where possible to avoid variant issues. - Correct property selected: In your project settings, confirm the GSC property selected is the right one for that site. It is possible to connect the account but have no property selected, or the wrong property selected. - GSC data availability: GSC data is not real-time. Google typically makes performance data available with a delay of 2–4 days. If your site is newly verified or the project was just created, allow some time before expecting data to appear. 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.

Last updated on Oct 26, 2026

Heatmap Pin Location Resets After Data Refresh

πŸ” What Is This Issue? When you manually move a heatmap pin to a specific location for a keyword search β€” such as baci and buca β€” and then trigger a data refresh, the pin may snap back to an incorrect, unrelated location. This means the refresh runs against the wrong coordinates, consuming your quota without producing useful results. This behavior is a known issue and our team is actively working on a fix. In the meantime, please reach out to our support team so we can assist you directly with your affected heatmap and discuss quota recovery options if needed. ⚠️ Why Does This Happen? The heatmap tool may not retain a manually repositioned pin when a data refresh is triggered, causing the scan to run against the wrong coordinates. This can result in quota consumption without useful results. βœ… What To Do If You Experience This Issue If your heatmap pin is resetting after a refresh, please contact our support team. We can help you: - Confirm whether your account is affected by this known pin-reset behavior. - Review quota consumption related to incorrectly positioned scans. - Discuss options for quota recovery where applicable. - Advise on any available workarounds while the fix is in progress. πŸ›‘οΈ How to Avoid Unnecessary Quota Consumption Until the underlying issue is resolved, follow these precautions: - Verify the pin position visually on the map immediately before triggering a refresh. Confirm the pin is on the intended location, not a default or unrelated spot. - Do not proceed if you notice the pin has reset before the scan completes β€” contact support before re-running to discuss quota recovery options. - Avoid triggering automatic refreshes if your account has scheduled scans enabled for affected keywords. Temporarily disable scheduling for those keywords until the fix is released. - Run one test scan on a low-priority keyword first to confirm the pin is holding its position before running scans on keywords that matter most. If you have questions or need help recovering quota lost due to this issue, please reach out to our support team via the chat widget or email us directly.

Last updated on Oct 26, 2026

πŸ“Š Fix Report Customization and Data Discrepancies

πŸ“‹ Overview Search Atlas reports let you tailor what data you share with clients or stakeholders. If your report shows numbers that differ from Google Search Console (GSC), or you need to remove specific sections, this article walks you through both tasks step by step. πŸ—‚οΈ How to Access the Report Builder Navigate to the Report Builder by selecting Reports from the left sidebar. Here you will see all existing reports tied to your projects. βœ‚οΈ How to Remove Sections from a Report 1. Open the Reports page from the left sidebar. 2. Click the report you want to edit to open it in the builder. 3. Locate the section you want to remove and look for the options control associated with that section. 4. Select the option to remove or delete that section to hide that block from the report. 5. Preview the report to confirm the section no longer appears, then save your changes. Tip: Removing a section only affects the report layout β€” it does not delete the underlying data from your project. ⚠️ Why Report Numbers May Not Match Google Search Console Seeing different numbers between Search Atlas and GSC is a common concern. The most frequent reasons are listed below. - Date range offset: GSC may apply a data freshness delay. Make sure the date range selected in Search Atlas matches exactly what you are viewing in GSC. - Property type mismatch: GSC distinguishes between Domain properties and URL-prefix properties. Confirm that the property connected to Search Atlas is the same type and URL you are checking in GSC. - Data sampling: GSC may apply sampling to large data sets. Search Atlas may surface a slightly different sample depending on when data was pulled. - Filters applied in GSC: If you have active filters in GSC (e.g., country, device, or search type), the totals will differ from an unfiltered Search Atlas view. Remove filters in both tools before comparing. - Metric definition differences: Impressions, clicks, and CTR can be counted differently depending on the GSC report view you are using. Verify you are comparing equivalent metrics. - Connection or sync timing: If your GSC account was connected recently, historical data may still be importing. Allow some time after connecting for a full data sync before drawing comparisons. πŸ”Œ How to Verify Your Google Search Console Connection 1. Go to Site Metrics β†’ GSC Performance (Manage Sites) from the left sidebar. 2. Confirm that the correct GSC property is connected and actively syncing data. 3. If the property does not appear or shows an error, disconnect and reconnect your GSC account. 4. After reconnecting, allow time for data to fully import before comparing numbers again. 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Why Heatmap Pins Show Incomplete Data

πŸ” Overview Local SEO heatmaps in Search Atlas show how your business ranks across a grid of geographic points for specific keywords. Each pin on the grid represents a data point pulled from live search results. Occasionally, some pins may appear blank, show a dash, or display incomplete ranking data β€” even after a previous fix was applied. This article explains why this happens and what you can do about it. πŸ“ Why Pins Sometimes Show No Data Pin data gaps are not always caused by a platform error. Several factors can cause a pin to display incomplete or missing information: - Google did not return a result for that location: For certain grid coordinates, Google's local search algorithm may not surface a result for your business. This is a real-world ranking signal, not a display bug. - Search result fluctuation: Google rankings change frequently. A pin that showed data on a previous scan may return no result on a newer scan if your ranking changed for that specific location point. - Data retrieval interruption during scan: During a heatmap scan, individual data requests are made for each pin. If a request is interrupted mid-scan, that pin may not receive data and will appear blank. - Keyword-location combination yields no local pack: Not every keyword triggers a local pack (the map results). If Google shows only organic results for a specific keyword at a specific coordinate, no local ranking data will be captured. ⚠️ Why the Issue Can Reappear After a Fix If our team previously resolved a data display issue and you are seeing blank pins again, this is most commonly due to the following reasons: - New scan cycle: Each time a heatmap refreshes, it runs a fresh set of data requests. A prior fix may have corrected a one-time retrieval error, but new scans are subject to the same real-time variables described above. - Multiple keywords amplify the effect: When you track several keywords across the same location grid, a single problematic coordinate will appear blank on every keyword heatmap β€” making the issue look more widespread than it is. πŸ› οΈ Steps to Troubleshoot Blank or Incomplete Pins 1. Identify the affected pins: Open the heatmap in question and note which specific pins are blank or showing incomplete data. Take a screenshot if possible. 2. Note the keyword and location: Record the exact keyword and grid location associated with each blank pin, as this information will be needed if you need to escalate. 3. Run a new scan: Trigger a fresh heatmap scan to see if the blank pins populate on the next data retrieval cycle. Temporary interruptions during a previous scan may resolve on a rescan. 4. Check multiple keywords: If the same grid coordinate is blank across several keyword heatmaps, this points to a location-specific data issue rather than a keyword-specific one. Note this pattern. 5. Escalate if the issue persists: If pins remain blank after a fresh scan, contact our support team with the following details ready: your project name, the affected keyword(s), the approximate grid coordinates or a screenshot of the blank pins, and the date/time of the scan. 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.

Last updated on Oct 26, 2026

πŸ”— Fix Google Search Console Connection in Report Builder

Overview If one or more of your domains are not linking correctly to Google Search Console (GSC) inside the Report Builder, a broken or incomplete OAuth connection is usually the cause. This article explains what to check and what information to have ready so our team can resolve the issue quickly. Before You Begin - Make sure you are logged in to Search Atlas with the account that has access to GSC for the affected domains. - Confirm you have the appropriate permissions in Google Search Console for each domain you want to link. - Have your Google account credentials ready, as you may be prompted to re-authenticate during reconnection. What to Try First 1. Log in to your Search Atlas account and navigate to Report Builder. 2. Open the report that contains the domain with a broken GSC connection, or create a new report for the affected domain. 3. Locate the Google Search Console integration option within your report. 4. If you see an option to disconnect or remove the existing GSC connection, do so β€” this removes only the OAuth link between Search Atlas and GSC, and does not affect your underlying Google Search Console data or account. 5. After disconnecting, look for an option to reconnect or add the GSC connection again. Follow the on-screen prompts to authenticate with the Google account that has access to the affected domain, and grant the requested permissions. 6. Once reconnected, verify that GSC data is now appearing correctly in the report. 7. If you manage multiple affected domains, repeat these steps for each domain separately. If the Issue Persists If the GSC connection still fails after attempting the steps above, please escalate to our support team. To help us resolve the issue as quickly as possible, have the following ready: - The exact domain(s) that are failing to connect - The Google account email used to authenticate GSC - Any error message you see during the connection attempt (copy the exact wording) - The timestamp of when you last attempted to connect 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.

Last updated on Oct 26, 2026

πŸ” Fix GA4 Cross-Site Tracking Data in Single Property

🧩 What Is This Issue? Some customers have noticed unexpected cross-site tracking data appearing inside a single Google Analytics 4 (GA4) property. For example, data from one domain showing up under a property that should only track a different domain. This can distort your traffic reports, inflate session counts, and make it harder to analyse accurate SEO performance. This article explains the most common causes of this issue and walks you through how to diagnose and fix it β€” including how Search Atlas connects to your GA4 data. πŸ”Ž Does Search Atlas Cause This? Search Atlas reads your GA4 data using a secure, read-only integration. It does not inject tracking scripts, modify your GA4 configuration, or send data into your GA4 property. If cross-site data started appearing in your GA4 property around the time you connected Search Atlas, the root cause is almost always a pre-existing configuration issue in GA4 that becomes more visible once you start actively reviewing your analytics. ⚠️ Common Causes of Cross-Site Data Contamination - Shared Measurement ID: The same GA4 Measurement ID is used on more than one domain or subdomain, causing all traffic to roll up into one property. - Cross-Domain Tracking misconfiguration: GA4 cross-domain tracking is enabled but the domain list includes domains that should be tracked separately. - Third-party embeds or iframes: Widgets, booking engines, or payment portals hosted on another domain that carry your GA4 tag. - Tag Manager container errors: A Google Tag Manager container is firing your GA4 tag on unintended domains due to a missing or incorrect trigger filter. - Referral exclusion settings: Missing referral exclusions can cause sessions to restart mid-journey and attribute traffic incorrectly. πŸ› οΈ How to Diagnose the Problem 1. Open your GA4 property and navigate to Reports β†’ Acquisition β†’ Traffic Acquisition. 2. Add a secondary dimension of Hostname to see which domains are sending data into this property. 3. If you see hostnames that do not belong to this property, you have confirmed cross-site contamination. 4. Note the hostnames and the date the unexpected data first appeared β€” this helps narrow down what changed. βœ… How to Fix Cross-Site Data in GA4 Once you have identified the unexpected hostnames, follow the steps below based on the most likely cause. Fix 1 β€” Remove unintended domains from Cross-Domain Tracking: 1. In GA4, go to Admin β†’ Data Streams β†’ select your web stream. 2. Click Configure tag settings β†’ Configure your domains. 3. Review the domain list and remove any domains that should not be sharing session data with this property. Fix 2 β€” Add hostname filters to your Data Stream: 1. In GA4, go to Admin β†’ Data Streams β†’ select your web stream β†’ Configure tag settings. 2. Use the List unwanted referrals and internal traffic settings to exclude domains sending unwanted hits. Fix 3 β€” Fix your Google Tag Manager trigger: 1. Open your GTM container and locate the GA4 Configuration tag. 2. Edit the trigger and add a condition: Page Hostname β†’ equals β†’ your intended domain only. 3. Publish the updated container. Fix 4 β€” Create a filtered GA4 property (recommended for clean reporting): 1. In GA4, go to Admin β†’ Data Settings β†’ Data Filters. 2. Create a new filter using the Hostname dimension to include only your intended domain. πŸ“Š Verifying Your Search Atlas Integration To confirm your Search Atlas connection is working correctly with your clean GA4 data, navigate to Site Metrics (Site Explorer) in the left sidebar of the platform. Your traffic and keyword data should reflect only the property you have connected. If you connected multiple properties, verify each one under Keywords β†’ Rank Tracker to ensure the correct domain is selected. πŸš€ Preventing This Issue in the Future - Always use a separate GA4 property for each distinct domain β€” avoid sharing Measurement IDs across sites. - Audit your GTM container triggers whenever a new third-party tool is added to your site. - Review your GA4 hostname report monthly to catch unexpected data sources early. - Document which Measurement ID belongs to which property before connecting any analytics integration. πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ” Fix Google Analytics Data Missing From Reports

🧭 Overview If your Search Atlas project report is not displaying Google Analytics data, the cause is almost always related to an incomplete connection, missing permissions, or a configuration mismatch between your Google Analytics account and your project settings. Follow the steps below in order to diagnose and resolve the issue. βœ… Step 1: Confirm Your Google Analytics Account Is Connected Before troubleshooting further, verify that a Google Analytics account has been linked to your Search Atlas workspace. 1. Log in to your Search Atlas account. 2. Click your Avatar Menu (πŸ‘€) or account name in the top-right corner. 3. Go to Settings and look for an Integrations or Connected Accounts section. 4. Confirm that Google Analytics appears in the list and shows a Connected status. If Google Analytics is not listed or shows a Disconnected or Error status, proceed to Step 2. If it shows as connected, skip to Step 3. πŸ”— Step 2: Reconnect Your Google Analytics Account A broken or expired authentication token is one of the most common reasons data stops appearing. Reconnecting your account refreshes the access credentials. 1. In the Integrations section of Settings, click Disconnect next to Google Analytics if an entry exists. 2. Navigate to Site Metrics β†’ Site Explorer (GSC Accounts page) and click Connect GA Account to follow the on-screen OAuth prompts. 3. Sign in with the Google account that owns or has Editor access to the Google Analytics property you want to use. 4. Grant all requested permissions when prompted β€” partial permission grants will prevent data from loading. 5. Once reconnected, return to your project report and wait up to 5 minutes for data to populate. πŸ—οΈ Step 3: Verify the Correct Property Is Assigned to the Project Even if your Google Analytics account is connected at the workspace level, each project must be individually mapped to the correct GA property and view (for Universal Analytics) or data stream (for GA4). 1. Open the project that is missing data. 2. Click Project Settings (usually accessible via a gear icon or the project menu). 3. Locate the Google Analytics field and confirm a property is selected. 4. If the field is blank or shows the wrong property, click the dropdown and select the correct GA4 property or Universal Analytics view. 5. Save your changes and reload the report. If the dropdown is empty even though your account is connected, this typically means the authenticated Google account does not have access to any GA properties. Log in to Google Analytics directly to verify the account has the correct role assigned. πŸ” Step 4: Check Google Analytics Permissions Search Atlas requires at least Viewer level access to the Google Analytics property to read data. Editor or Administrator access is required if you also want to write annotations or manage settings. - Log in to your Google Analytics account at analytics.google.com. - Navigate to Admin β†’ Property Access Management. - Confirm the Google account used to connect Search Atlas has a role of Viewer or higher on the relevant property. - If the role is missing or set to None, ask the property owner to update the permission, then reconnect the account in Search Atlas. πŸ“… Step 5: Check the Report Date Range Data will only appear for periods during which the Google Analytics connection was active and the property was receiving traffic. An incorrect date range can make it appear as if data is missing. - Open your project report and review the date range selector at the top of the page. - Set the range to a period when you know your site was receiving traffic, such as the past 30 days. - Confirm that Google Analytics was already connected to this project during the selected period. If you recently connected Google Analytics, historical data import may not be available depending on your plan. Only data collected after the connection was established will appear. ⏳ Step 6: Allow Time for Data Sync After connecting or reconnecting Google Analytics, Search Atlas needs time to pull and process your data. Sync times can vary based on the volume of data and current system load. - Wait at least 15–30 minutes after connecting before expecting data to appear. - For large properties with significant historical data, the initial sync may take longer. - Refresh your browser and reload the report after waiting. 🚫 Common Reasons Data Stays Missing - Wrong Google account used: The connected account does not have access to the intended GA property. - GA4 vs. Universal Analytics mismatch: Selecting a Universal Analytics view when your site uses GA4, or vice versa. - Expired OAuth token: Google authentication tokens can expire; reconnecting resolves this. - No data in GA itself: Verify the property is actively tracking data by checking your Google Analytics dashboard directly. - Ad blocker or browser extension interference: Test in a private/incognito window with extensions disabled if the UI behaves unexpectedly during the connection flow. πŸ’¬ Still Need Help? If you have completed all the steps above and Google Analytics data is still not appearing in your report, 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.

Last updated on Oct 26, 2026

πŸ”„ Fix Dashboard Redirect Loop and Cache Issues

πŸ” What Is Happening? If your dashboard shows an active plan but you are being redirected to the billing page every time you try to access your website or tools, the most likely cause is a stale browser cache. Your browser has saved an outdated version of your session or account status, which creates a conflict between what the platform knows and what your browser is displaying. This results in a redirect loop that blocks access to your account. ⚠️ Common Symptoms - Dashboard shows an active subscription, but access is blocked. - Every page visit redirects you back to the billing or upgrade page. - Refreshing the page does not resolve the issue. - The problem persists even after logging out and back in. πŸ› οΈ Step-by-Step Fix 1. Clear your browser cache and cookies. In most browsers, press Ctrl + Shift + Delete (Windows) or Command + Shift + Delete (Mac). Select All time as the time range, check Cached images and files and Cookies and other site data, then click Clear data. 2. Close all browser tabs related to Search Atlas and fully close the browser window. 3. Reopen your browser and navigate directly to the Search Atlas platform. 4. Log in again with your credentials and go to Avatar (top-right) β†’ Billing (Plans & Top-ups). 5. Check whether the redirect loop has resolved. You should now be able to access your dashboard and tools without being sent back to the billing page. πŸ’‘ Try a Different Browser or Private Window If clearing your cache does not immediately resolve the issue, open a private or incognito window in your browser, or try a completely different browser such as Chrome, Firefox, or Edge. Private windows do not load saved cache or cookies, so this is a quick way to confirm that a stale cache is the root cause. If the platform works correctly in a private window, clearing the cache in your main browser (as described above) will permanently fix the issue. πŸ” Verify Your Plan Status Once you regain access, navigate to Avatar (top-right) β†’ Billing (Plans & Top-ups) and check your account status. If your plan appears active and you can access all features without being redirected, the issue is resolved. If the dashboard still shows conflicting information β€” for example, displaying an active plan while restricting access β€” this may indicate a billing synchronisation issue that requires manual review by our team. 🚫 What Not to Do - Do not repeatedly click through the billing page or attempt to resubscribe β€” this will not fix a cache-related redirect loop and may cause unintended charges. - Do not disable browser extensions as a first step; cache is almost always the cause in these cases. - Do not wait for the issue to resolve on its own β€” stale cache must be cleared manually. πŸ†˜ Still Experiencing the Issue? If you have followed all the steps above and are still being redirected to the billing page or seeing an incorrect plan status, our team can investigate your account 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.

Last updated on Oct 26, 2026

πŸ”„ Fix Outdated Site Metrics and Screenshots in Search Atlas

🧭 Why Is Search Atlas Showing Outdated Data? When a site has been recently updated or redesigned, Search Atlas may temporarily display older metrics and screenshots. This lag is normal and typically occurs for one or more of the following reasons: - The site has not been added to your Search Atlas dashboard. Without an active dashboard connection, Search Atlas cannot track or update your site's metrics in real time. - The OTTO pixel is not installed. The OTTO pixel is required to enable continuous data collection. Without it, Search Atlas relies on periodic external crawls rather than live site signals. - Google has not yet re-indexed the updated site. Site Explorer screenshots are sourced from Google's index. If Google has not recrawled your site since the update, the cached version will appear in Search Atlas. - Custom reports have not been refreshed. Metric snapshots in reports reflect the timeline you have configured. An outdated range will show historical data. The sections below walk you through each fix step by step. πŸ“Š Step 1 β€” Add Your Site to the Dashboard Adding your site to the Search Atlas dashboard is the first step to enabling live metric tracking. 1. Log in to Search Atlas and go to Home (/home). 2. Locate the Add Website option and enter your full domain (for example, northamericanenclosures.us). 3. Follow the on-screen prompts to complete the setup. Search Atlas will begin pulling current data for the site once it is added. 4. Allow up to 24 hours for the initial metrics to populate after the site is added. If your site is already listed in the dashboard but metrics still appear stale, proceed to Step 2. βš™οΈ Step 2 β€” Install the OTTO Pixel The OTTO pixel enables continuous, real-time data collection for your site. Without it, Search Atlas cannot track on-site changes as they happen. 1. From the left sidebar, navigate to OTTO SEO β†’ SEO Automation (/seo-automation-v3). 2. Select your site and open the OTTO Setup section. 3. Copy the OTTO pixel snippet provided. 4. Paste the snippet into the <head> section of every page on your site, or install it via your tag manager (for example, Google Tag Manager). 5. Verify the installation by returning to the OTTO SEO dashboard and confirming the pixel status shows as Active. Important: The pixel must be present on your live, published site. Installing it only on staging or development environments will not trigger metric updates for the production domain. πŸ“… Step 3 β€” Update Your Custom Report Timeline If your reports are still showing old data after adding the site and installing the pixel, the report date range may need to be updated. 1. Open the report you want to refresh inside Search Atlas. 2. Locate the Date Range or Timeline selector within the report settings. 3. Set the range to include your desired start date β€” for example, from the date your site was updated to today. 4. Save and regenerate the report. The updated metrics will now reflect the selected period. Setting the correct timeline ensures you are viewing current performance data rather than historical snapshots from before your site changes. πŸ–ΌοΈ Step 4 β€” Understand the Site Explorer Screenshot Timeline Site Explorer displays a screenshot of your site sourced directly from Google's index. Search Atlas does not control when this image is updated β€” it depends entirely on when Google recrawls and re-indexes your site. - Typical refresh window: Screenshots update within 2 to 6 weeks after Google recrawls the site, though this varies based on your site's crawl frequency and domain authority. - Speed up the process: Submit your updated sitemap to Google Search Console and use the URL Inspection tool to request indexing for key pages. This signals to Google that your site has changed and encourages a faster recrawl. - No manual override: There is currently no option inside Search Atlas to force a screenshot refresh. The image will update automatically once Google has recrawled and cached the new version of your site. In the meantime, all other metrics β€” traffic, keywords, backlinks β€” will update in Search Atlas independently of the screenshot once Steps 1 through 3 are complete. βœ… Quick Checklist - Site added to dashboard? Go to Home (/home) and confirm your domain is listed. - OTTO pixel installed and active? Check OTTO SEO β†’ SEO Automation (/seo-automation-v3) for a green Active status. - Report date range updated? Set the timeline to cover the period after your site changes. - Sitemap submitted to Google? Use Google Search Console to request faster recrawling for the screenshot to refresh. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Builder Widget Title Errors

πŸ” What Causes the Widget Title Error When you try to edit a widget title in Report Builder β€” for example, changing the business name in brackets to identify which Google Business Profile (GBP) a widget tracks β€” you may see a validation error when saving. The most common symptom is a misleading date range validation message that appears even when your date settings are correct. This is a known issue that affects the Classic View of Report Builder. The underlying bug has been patched, but if you are still encountering the error, your browser may be loading cached files from an older version of the platform. βœ… Steps to Resolve the Error 1. Use the New Report Builder. Navigate to Reports in the left sidebar. The updated Report Builder is the default view and does not have this bug. If you are in Classic View, switch back to the New Report Builder before editing titles. 2. Clear your browser cache. If the patch is deployed but your browser is still loading older files, clearing the cache and hard-refreshing the page will load the latest version of Report Builder. 3. Edit the widget title. Click on the widget you want to rename, locate the title field containing the business name in brackets, and enter your updated label. 4. Save the report. Click Save and confirm that the title updates without triggering a validation error. If the error persists after clearing your cache, go to Reports in the left sidebar, open the report (Executive Summary), and click Refresh Summary to force a data sync, then attempt to edit the widget title again. πŸ”„ Workarounds for Integration Label Limitations Certain integrations β€” including OTTO and Facebook β€” do not yet support fully editable widget labels in Report Builder. This means the business name shown in brackets may be locked and cannot be manually changed for those specific integration types. Editable labels for OTTO integration are actively in development. Until that feature ships, use these workarounds to keep your reports organized: - Use Section Titles. In the New Report Builder, add a custom section title above each widget to clearly identify the business profile it represents. - Create separate reports per profile. Build one report per GBP location instead of combining multiple profiles in a single report. - Rename the report itself. Use a descriptive report name that includes the business identifier β€” for example, Monthly SEO Report β€” Downtown Dental. πŸ“‹ How to Edit Titles in the New Report Builder The New Report Builder makes it easy to customize section and widget titles. Follow these steps: 1. Open your report from the Reports list. 2. Click directly on the section or widget title text you want to change. 3. Type your new title, including any business name in brackets for easy identification. 4. Click outside the text field or press Enter to save your changes automatically. Section titles can be added, edited, or removed at any time without affecting the underlying widget data. ⚠️ Classic View Known Issues If you access a report through View (Classic) from the Reports list, be aware of the following limitations: - Editing widget titles may trigger a false date range validation error. - Section title widgets may not display correctly in custom layouts. - Some titles visible in individual sections may not appear on the full report page. For the best experience, use the New Report Builder for all title editing and report customization tasks. πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Builder Edits That Disappear After Saving

What Is This Issue? Some users find that edits made in the Report Builder β€” such as custom text changes, layout adjustments, or section modifications β€” appear to save successfully but then revert or disappear when the report is reloaded. In some cases, connected data sources like Google Analytics may also become difficult to remove. This is a known issue that our engineering team has investigated. Follow the steps below to resolve it on your own, or contact our support team via the chat widget if the issue persists. How to Fix Disappearing Report Edits 1. Clear your browser cache and cookies. Cached data can interfere with how saved report data is loaded. Clear your cache, then reload the Report Builder and check whether your edits persist. 2. Try an incognito or private browsing window. Open the Report Builder in an incognito window to rule out browser extensions or cached sessions causing the revert behavior. Make your edits and save, then reload the page in the same incognito session to confirm whether changes are retained. 3. Try a different browser. If the issue only occurs in one browser, switching to another (e.g., Chrome, Firefox, Edge) can help confirm whether this is a browser-specific problem. 4. Re-save the report after each individual edit. If you are making multiple changes, try saving after each individual change rather than making all edits before saving. This can help isolate which specific edit is triggering the revert. 5. Remove and re-add connected data sources. If a connected data source such as Google Analytics appears stuck or cannot be removed, disconnect it from the report, save, then reconnect it and save again. Still Experiencing This Issue? If your report edits are still disappearing after following the steps above, please reach out to our support team via the chat widget so we can look into this further and escalate to engineering if needed. You can also email us at support@searchatlas.com.

Last updated on Oct 26, 2026

πŸ› οΈ HDC Limit Error Blocking Citation Submission

πŸ” Overview Some users encounter a blocking error when trying to submit a citation bundle β€” even though their available HyperDrive Credits (HDC) are sufficient to cover the cost. The error message typically references a credit limit (for example, "You have hit the limit of 245 HyperDrive credits") and prevents the submission from going through entirely. If you are seeing this error despite having enough credits, follow the steps below to troubleshoot and get your submission through. βœ… Confirm Your HDC Balance Is Sufficient Before troubleshooting, verify that your available HDC balance genuinely covers the cost of the citation bundle you are trying to submit. Check both your recurring credits and any purchased (top-up) credits, and confirm their combined total meets or exceeds the bundle size. - Your billing cycle reset date affects when recurring credits are added β€” confirm the reset has fully processed. - Purchased credits should be reflected immediately after a successful transaction. - If your balance appears lower than expected, check your billing history for any recent deductions. πŸ”„ Try These Steps Before Contacting Support 1. Refresh your browser and navigate back to your citation submission. Cached session data can sometimes cause the platform to display an outdated credit state. 2. Clear your browser cache and log back in. This ensures the platform loads your current account balance fresh from the server. 3. Wait a few minutes and retry. If your billing cycle reset very recently, there may be a brief delay before all credit types are fully reconciled in the system. 4. Try submitting a smaller bundle to confirm whether the error is tied to a specific bundle size or affects all submissions. 5. Check whether the issue persists across different browsers or devices. This helps rule out a local browser issue. ⚠️ When to Escalate If you have confirmed your HDC balance is sufficient and the steps above do not resolve the error, please reach out to our support team. Share a screenshot of the error message and your current credit balance so the team can investigate your account directly. If you need further assistance, don't hesitate to contact us.

Last updated on Oct 26, 2026

πŸ” Fix GSC Performance Data Not Showing

πŸ”Ž Overview If your Search Atlas project is connected to Google Search Console (GSC) but no search performance data is appearing, you are not alone. This is a common setup issue that is almost always resolved by following a few quick checks. This article walks you through the most likely causes and how to fix them. βœ… Step 1: Confirm the Correct GSC Property Is Connected The most frequent cause of missing performance data is a mismatch between the GSC property and the website URL in your project. To verify: 1. Open your project in Search Atlas. 2. Navigate to the top-right avatar (Avatar Menu (πŸ‘€)) β†’ Settings β†’ Integrations and locate the Google Search Console integration section. 3. Confirm the connected property exactly matches the version of your site that Google is indexing β€” for example, https://www.example.com is a different property from https://example.com. 4. If the wrong property is connected, disconnect it and reconnect using the correct one. In GSC itself, check which property type you verified β€” domain property or URL-prefix property β€” and make sure Search Atlas is referencing the same one. ⏳ Step 2: Allow Time for Data to Populate After connecting GSC to a new Search Atlas project, there is a processing period before data appears. Keep the following in mind: - Initial data sync can take 24 to 48 hours after a successful connection. - GSC itself delays performance data by 2 to 3 days from the date of collection. - If your site is brand new or recently launched, GSC may have little or no performance data to display yet. If you connected GSC less than 48 hours ago, wait and check again before proceeding further. πŸ”‘ Step 3: Check GSC Account Permissions Search Atlas can only retrieve data that the connected Google account is authorised to access. Ensure the following: - The Google account used to connect GSC has at least Full User or Owner permission on the property in Google Search Console. - The account has not had its GSC access revoked or downgraded since the initial connection. - You are not connected as a Restricted User, as this permission level limits the data available via the GSC API. To check permissions, log in to Google Search Console, open the relevant property, and go to Settings β†’ Users and permissions. πŸ”„ Step 4: Reconnect the GSC Integration If permissions are correct but data is still missing, try refreshing the connection: 1. Go to the top-right avatar (Avatar Menu (πŸ‘€)) β†’ Settings β†’ Integrations in Search Atlas. 2. Disconnect the current GSC integration. 3. Re-authorise your Google account and reconnect the correct GSC property. 4. Save your settings and allow up to 48 hours for data to appear. Reconnecting forces a fresh authorisation token, which resolves issues caused by expired or invalidated credentials. πŸ“Š Step 5: Verify Data Exists in GSC Directly Before assuming a Search Atlas issue, confirm that performance data is actually available in GSC: 1. Log in to Google Search Console. 2. Select the connected property. 3. Click Search results under the Performance section. 4. Check whether clicks, impressions, and queries are visible for recent date ranges. If GSC shows no data either, the issue is upstream with Google's indexing or data collection β€” not with Search Atlas. This can happen with new sites, sites blocked by robots.txt, or sites with crawl errors. πŸ› οΈ Common Scenarios and Quick Fixes - Data was showing before but stopped: Your GSC authorisation token may have expired. Reconnect the integration as described in Step 4. - Only partial data is visible: Confirm the date range selected in the performance report includes dates after the GSC connection was established. - Multiple GSC properties exist for the same domain: Connect the property that has the most complete data β€” typically the domain-level property if one has been verified. - GSC property was recently reverified or recreated: Historical data from the previous property will not carry over. Only data collected after the new verification date will appear. πŸ’¬ Still Need Help? If you have followed all the steps above and search performance data is still not displaying, 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.

Last updated on Oct 26, 2026

πŸ› οΈ Lead Capture Widget Showing Null or Zero Values

πŸ” Overview Some users of the Agency Hub's Site Analysis Lead Capture Widget experienced an issue where entering a valid domain returned null or zero values across all metrics, making the widget appear broken or unusable. This was a confirmed platform-level bug that has since been resolved by Search Atlas engineering. βš™οΈ What Was Happening The Lead Capture Widget, accessible via More Features β†’ Agency Hub (Agency Settings), is designed to analyze a prospect's website and display SEO data in real time. During a specific period, a defect caused the widget to fail to retrieve site data for valid domains, returning empty or zero results instead. This affected agencies relying on the widget for client-facing lead generation. This issue was tracked and resolved internally by the Search Atlas engineering team. The fix has been released to production. βœ… What You Should Do Now 1. Navigate to More Features β†’ Agency Hub (Agency Settings) in your platform sidebar. 2. Locate the Site Analysis Lead Capture Widget section on that page. 3. Test the widget by entering a valid domain to confirm that site analysis data is now returned correctly. 4. If you have the widget embedded on an external site, ensure you are using the most recently generated embed code from this section, as older versions may not reflect the fix. 5. Clear your browser cache or try in a private/incognito window if the issue appears to persist after refreshing. πŸ“‹ If the Problem Persists The engineering fix has been confirmed as released, so the vast majority of users should see correct data immediately. However, if you continue to experience null or zero values for valid domains after following the steps above, this may indicate a separate configuration issue specific to your account or embed setup. - Confirm the domain you are testing does not have unusual configurations such as access restrictions, parked status, or a very recent registration that may limit available data. - Verify that your widget embed code is up to date by revisiting More Features β†’ Agency Hub (Agency Settings) and regenerating the embed snippet if needed. - Try testing with a well-established domain to rule out domain-specific data availability. πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ› οΈ Report Builder PDF Export Downloading Blank

πŸ“‹ Overview Some users experienced an issue where downloading a PDF from Report Builder produced a blank or empty file. This affected all reports across the account, including monthly and client reports. A fix has been deployed to production and the issue is now resolved. πŸ” Is This Still Happening to You? If you are currently seeing blank PDF downloads from Report Builder, try the steps below before contacting support. In most cases, the issue is resolved and a simple retry will produce a correct PDF. 1. Refresh the page. Close any open report tabs and reload the Report Builder page in your browser. 2. Clear your browser cache. Cached files can sometimes cause stale behaviour. Clear your cache and cookies, then log back into the platform. 3. Try a different browser. If the blank PDF persists in your current browser, open the platform in an alternative browser (for example, switch from Chrome to Firefox, or vice versa) and attempt the download again. 4. Re-generate the report before downloading. Open the affected report in Reports and trigger a fresh export rather than re-downloading a previously generated file. 5. Test with a different report. Try downloading a different report to confirm whether the issue is isolated to one report or affects all reports in your account. βœ… Confirmed Fix This blank PDF export issue was identified, escalated to the engineering team, and fully resolved. The fix is live in production for all accounts. You should now be able to download complete, correctly rendered PDFs from Report Builder without any further action required on your end. ⚠️ When to Contact Support If you have followed the steps above and are still receiving blank or empty PDFs, the issue may be specific to your account or a particular report configuration. Please reach out to our support team for further assistance.

Last updated on Oct 26, 2026

πŸ”§ Fixing Cross-Business Citation Contamination in Dashboards

What Is Cross-Business Citation Contamination? Cross-business citation contamination occurs when citations belonging to a completely unrelated business appear inside your Search Atlas account dashboard. For example, if you manage one insurance agency but citations for a completely different, unaffiliated insurance agency are showing up in your dashboard, this is not a normal citation management situation β€” it is a potential account data mapping error that requires immediate investigation. This is different from seeing a competitor's citation listed as an external reference or a duplicate listing issue. In contamination cases, another business's citation records are surfacing directly inside your account as if they belong to your business. How to Identify a Data Mapping Error vs. a Normal Citation Issue Use the checklist below to determine whether you are experiencing contamination or a standard citation discrepancy: - Business name mismatch: The citation clearly shows a different business name (not a misspelling or abbreviation of yours). - Different address or phone number: The NAP (Name, Address, Phone) data does not match your business in any way. - Unrecognised listing sources: The directories or platforms listed are ones you never submitted your business to. - Volume is unexpectedly high: A large number of foreign citations appeared suddenly, not gradually over time. - No shared ownership: You do not manage or have any affiliation with the other business appearing in your dashboard. If any of the above apply, you are likely dealing with a data mapping error, not a standard citation issue. Do not attempt to edit or delete these citations yourself β€” doing so may complicate the investigation. Where to Find Citation Data in Search Atlas To review the citations appearing in your account, navigate to Local β†’ Local Citations within your active project dashboard. Take note of any entries where the business name, address, or phone number does not match your business profile, and keep a record of the specific listings (business name shown, source URL, and NAP data) before reporting the issue. What to Have Ready Before Escalating Because this type of issue involves a backend data mapping error, it cannot be self-resolved by editing or deleting citations in the dashboard. When you contact our support team, please have the following information ready so we can investigate quickly: - Your project name as it appears in your Search Atlas account. - The name of the unrelated business whose citations are appearing in your dashboard. - Specific citation URLs or source directory names where the foreign citations are listed. - The NAP data shown (business name, address, and phone number) for the unrelated business. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Custom Text Not Saving in Report Builder

πŸ” Overview Some users have reported that custom text added inside the Report Builder does not save correctly β€” edits appear to apply but then silently revert, or the changes are lost after refreshing the page. If you are experiencing this issue, please reach out to our support team so we can investigate and resolve it for your account directly. βš™οΈ What Was Causing This Custom text in the Report Builder was not persisting reliably for some users, causing edits to appear to save but then revert. The root cause of this behavior has not been fully characterized and may vary by account or configuration. Our support team will work with you to identify what is happening in your specific case. βœ… Steps to Resolve the Issue 1. Document what you are seeing. Note exactly when the text reverts β€” for example, immediately after saving, after a page refresh, or after logging back in. This information will help our team investigate. 2. Attempt to save your custom text again. Navigate back to the Report Builder, re-enter your custom text, save the report, and refresh the page to check whether the changes persist. 3. Contact our support team if the issue continues. If your custom text is still not saving after retrying, reach out to us with details about your account, the report affected, and what you observed. Our team can look into the issue on the back end. πŸ’‘ Tips to Prevent This Going Forward - Always confirm your changes have saved by refreshing the page after saving β€” your custom text should still appear after a full reload. - If you encounter an error when saving, do not close the page immediately. Try saving again before navigating away. - Keep a copy of any important custom text outside the platform until the issue is confirmed resolved for your account. πŸ†˜ Still Having Trouble? If you have followed the steps above and your custom text is still not saving, please contact our support team via the chat widget so we can investigate further and apply a fix for your account.

Last updated on Oct 26, 2026

πŸ” Fix Missing Data in Site Explorer Overview

🧩 Why Some Sections Show No Data If you open the Site Explorer overview and notice that Country Distribution, SERP Features, or Organic/Paid Traffic sections appear blank or empty, you are not alone. This is a common display issue that is almost always resolved with a simple page refresh. No data has been lost, and there is nothing wrong with your project or account. ⚑ Quick Fix: Refresh the Page The fastest way to restore missing data is to refresh your browser. Follow these steps: 1. In the left sidebar, click Site Metrics (Site Explorer) to open the Site Explorer list. 2. Select the domain or URL you were reviewing to open its overview. 3. Press F5 on Windows or Cmd + R on Mac to reload the page, or click the refresh icon in your browser toolbar. 4. Wait a few seconds for all sections to fully load. In most cases, Country Distribution, SERP Features, and Organic/Paid Traffic will all populate correctly after the refresh. πŸ”Ž What Causes This to Happen? The Site Explorer overview loads several data-heavy modules at the same time. Occasionally, one or more of these modules does not complete its load cycle on the first attempt. Common triggers include: - Slow or unstable internet connection β€” a brief drop in connectivity can interrupt the data fetch. - Browser cache or cookies β€” outdated cached data can conflict with the latest page state. - High platform traffic β€” during peak usage periods, some modules may take longer to respond. - Browser extensions β€” ad blockers or privacy extensions can occasionally block data requests. πŸ› οΈ Additional Troubleshooting Steps If a simple refresh does not restore the missing data, try the following steps in order: 1. Clear your browser cache. In Chrome, press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), select Cached images and files, and click Clear data. Then reload the page. 2. Try a different browser. Open the platform in Chrome, Firefox, or Edge to rule out a browser-specific issue. 3. Disable browser extensions temporarily. Open the page in an Incognito or Private window, which disables most extensions by default, and check whether data appears. 4. Check your internet connection. Switch networks or reset your router if you suspect connectivity issues. 5. Wait a few minutes and try again. If the platform is experiencing high load, data may populate on its own within a short time. βœ… Confirming the Data Is Back Once you have refreshed or completed the steps above, verify that all three sections are displaying correctly: - Country Distribution β€” shows a breakdown of organic traffic by country. - SERP Features β€” displays which special search result types the domain appears in. - Organic/Paid Traffic β€” shows estimated monthly traffic from organic and paid search. If any section still shows no data after all steps are completed, the domain may genuinely have no recorded data for that metric, or the data may still be processing if the domain was recently added. πŸ’¬ Still Seeing Empty Sections? If you have followed all the steps above and one or more sections remain empty, our team is ready to 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.

Last updated on Oct 26, 2026

πŸ”§ Fix a Missing or Collapsed Dashboard Sidebar

🧭 Overview If options such as Site Projects or Local SEO Tools have disappeared from your dashboard, your sidebar is most likely minimized or collapsed rather than missing entirely. This article walks you through how to identify the cause and restore full sidebar visibility in a few quick steps. πŸ” Why This Happens The Search Atlas sidebar can appear to vanish or lose its labels in the following situations: - The sidebar has been manually collapsed using the toggle arrow or minimize icon. - Your browser window is in a narrow or full-screen state that auto-collapses the sidebar to icon-only mode. - A previous session left the sidebar in a minimized state, which persists when you log back in. - The browser zoom level is too high, causing the layout to compress and hide sidebar text. πŸ› οΈ How to Restore the Sidebar 1. Look for a collapse/expand arrow β€” Check the left edge of your screen for a small arrow icon ( β€Ή or β€Ί ). Click it to expand the sidebar back to its full state. When expanded, you should see labeled menu items including Home, Authority, and all other tool categories. 2. Check if the sidebar is in icon-only mode β€” If you see a narrow strip of icons on the left with no text labels, the sidebar is minimized. Click the expand arrow or the hamburger/menu icon at the top of the sidebar to restore full labels and navigation options. 3. Exit full-screen mode β€” If your browser is in full-screen mode, press F11 (Windows) or Control + Command + F (Mac) to exit. Then refresh the page and check whether the sidebar returns to its default expanded state. 4. Adjust your browser zoom level β€” Press Ctrl + 0 (Windows) or Command + 0 (Mac) to reset your browser zoom to 100%. A zoom level above 110% can cause the sidebar to collapse automatically. 5. Hard-refresh the page β€” Press Ctrl + Shift + R (Windows) or Command + Shift + R (Mac) to reload the page without cache. This resolves cases where a stale layout state is stored in your browser session. 6. Try a different browser or incognito window β€” Open Search Atlas in an incognito/private window or a different browser to rule out a browser extension or cached setting causing the issue. 🏠 Navigating Once the Sidebar Is Restored After expanding the sidebar, you should see the full navigation menu on the left side of the screen. Key areas include: - Home β€” Access your dashboard overview, playbooks, and project summaries by clicking Home in the left sidebar. - Authority β€” Expand this section to reach tools such as PR Distribution, Cloud Stacks, Indexer, QUEST AI Visibility, Campaigns, and Inbox. - Site Projects and Local SEO Tools β€” These options should reappear in the sidebar once it is fully expanded. If they are still not visible after completing the steps above, your current plan may not include access to those features. ❓ Still Not Seeing All Options If you have expanded the sidebar and certain tools are still missing, consider the following: - Your subscription plan may not include the tools you are looking for. Check your plan details under your account settings. - You may be logged into a different workspace. Confirm you are in the correct account by checking the workspace name (e.g., "CSM Team") shown in the top header bar, next to the notifications/features icon. - A temporary platform caching issue may be causing the display problem. Log out, clear your browser cookies, and log back in. πŸ’¬ 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.

Last updated on Oct 26, 2026

πŸ” Fix GSC Connection and Performance Overview Issues

🧭 Overview If you have multiple Google accounts or Search Console properties, it can be unclear which property is actively connected to Search Atlas. You may also notice that the GSC Performance Overview tab displays a Connect GSC prompt even after completing the integration. This article explains how to confirm the correct GSC property is linked and what to do if you are still experiencing connection or display issues. πŸ”— How Google Search Console Connects to Search Atlas Search Atlas connects to Google Search Console via OAuth, which means you authorise access through a specific Google account. If you manage multiple Gmail accounts or have several GSC properties, it is important to verify that the correct account and property were selected during the authorisation flow. Each Search Atlas project is linked to a single GSC property. If the wrong property was connected, your performance data will either be missing or belong to a different website. βœ… How to Confirm Your GSC Connection If you are unsure whether the correct GSC property is connected, or if the Performance Overview tab is showing a Connect GSC prompt even after integration, the best course of action is to contact our support team directly. A member of our team can verify which Google account and property are linked to your project, confirm whether your connection is active, and guide you through reconnecting with the correct account if needed. When reaching out, please have the following ready: - The name of the affected Search Atlas project - The Google account email you used during the GSC authorisation flow - The exact GSC property URL you intended to connect (for example, https://www.example.com/ versus https://example.com/ β€” these are treated as separate properties in Google Search Console) - A description of what you are seeing, including any error messages or prompts displayed ⚠️ Why the Performance Overview Tab May Show "Connect GSC" In some cases, the GSC Performance Overview tab may display a Connect GSC prompt even when your integration has been completed. This can be a display issue that does not reflect the true state of your connection. If you are seeing this, please contact our support team so we can investigate and confirm whether your integration is active and data is flowing correctly. 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.

Last updated on Oct 26, 2026

πŸ”§ Troubleshooting Stalled Content Score, Authority, and UX Signals

Overview If your Content Score, Authority, or UX Signals metrics appear stuck or are not improving over time, this article explains what each metric represents and what you should have ready when reaching out to our team for help. What These Metrics Measure Content Score reflects how well your pages are optimised for target keywords, topical depth, and on-page structure. A stalled Content Score typically means content has not been updated or expanded recently, target keywords are not well-aligned with page content, or topic gaps exist relative to competing domains. Authority is driven primarily by your backlink profile β€” the number, quality, and relevance of domains linking to your site. If Authority is not growing, the referring domain count may have plateaued or declined. UX Signals reflect real-world user experience data (such as Core Web Vitals and CrUX data). These metrics are sourced from external data providers and may update on a different cadence than other metrics in the platform. What to Try First - Confirm your domain is correctly configured in your Search Atlas project β€” check that the target country, language, and domain format (with or without www) match your intended settings. - Check whether content on your key pages has been updated recently. Metrics are unlikely to improve if no changes have been made to the underlying pages. - Review your backlink profile for any net loss of referring domains over the past 30–90 days, which would explain a stalled or declining Authority score. - For UX Signals, be aware that real-world experience data from external sources may take longer to reflect recent site improvements. When to Contact Support If you have reviewed the above and your metrics remain unexpectedly stalled, please contact our team. To help us investigate efficiently, have the following ready: - Your project name and the exact domain as it appears in Search Atlas - Which specific metric(s) appear stalled (Content Score, Authority, and/or UX Signals) - Approximately how long the metric has been flat or declining - Any recent changes you have made to your site or content that you expected to be reflected 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.

Last updated on Oct 26, 2026

Site Explorer Overview Data Not Populating

🧭 What This Article Covers Some customers have found that after entering a domain in Site Explorer, the overview section shows no organic research, backlink, or competitor data β€” even for domains with known activity. This article explains what causes this, what you can check yourself, and how to get resolution quickly. ⚠️ Known Platform Issue Our team has received reports of Site Explorer overviews appearing empty β€” showing no organic, backlink, or competitor data β€” even for domains with existing activity. If you are experiencing this, follow the steps below. πŸ› οΈ Steps to Try First 1. Check the individual tabs. After entering your domain in Site Explorer, navigate to the Keywords tab and the Backlinks tab separately. If data appears in those tabs but the overview remains blank, this points to a display issue specific to the overview rather than missing data. 2. Re-enter the domain. Try searching the domain again in Site Explorer and allow a few minutes for the system to process before reviewing the overview. 3. Try a different domain as a reference. Analyze a well-established domain to confirm whether Site Explorer is returning overview data in general. If other domains also show blank overviews, the issue may be broader and should be reported to our team. πŸ“‹ What to Include When Reporting If the steps above do not resolve the issue, please have the following ready when contacting support so our team can investigate quickly: - The exact domain or domains you analyzed - Whether individual tabs such as Keywords or Backlinks show data while the overview remains empty - Approximately when you first noticed the missing data - A screenshot of the empty overview alongside any individual tab that does show data If you are still seeing missing data after trying these steps, please reach out to our support team so we can look into your account directly. πŸ’‘ Important Context for New Domains For very new or low-traffic domains, it is normal to see limited data in Site Explorer. If the domain you are researching was registered recently or has minimal web presence, reduced data availability may be expected rather than a technical issue.

Last updated on Oct 26, 2026

Fix a Greyed-Out GSC Property in Report Builder

πŸ—ΊοΈ Overview When a Google Search Console (GSC) property appears greyed out in the Search Atlas Report Builder, it means the platform cannot confirm that you have sufficient ownership access to that property in GSC. Until ownership is verified, the property remains unavailable for use in your reports. This article walks you through why this happens and what to check when it occurs. πŸ”Ž Why Is My GSC Property Greyed Out? Search Atlas requires verified ownership of a GSC property before it can pull data into the Report Builder. A property becomes greyed out when one or more of the following is true: - The Google account connected to Search Atlas does not have the required ownership level in GSC. - The GSC property was added to your Search Atlas account but the Google account used during OAuth does not match the owner account in GSC. - Ownership was granted after the initial connection was made, so Search Atlas has not yet re-verified permissions. - The GSC property has not completed its verification process in Google Search Console. βœ… What to Check 1. Confirm your GSC ownership level. Log in to Google Search Console and open the property in question. Make sure the Google account connected to Search Atlas has owner-level access. If it does not, ask the current owner to upgrade your permission level. 2. Verify which Google account is linked to Search Atlas. Confirm that the Google account authorized via OAuth in Search Atlas matches the owner account shown in Google Search Console. A mismatch between the two accounts is a common cause of the greyed-out state. 3. Ensure your GSC property verification is complete. In Google Search Console, confirm that the property in question has passed all required verification steps. An unverified or partially verified property may appear greyed out in Search Atlas. ⏱️ What to Expect If you have reviewed the above and the property remains greyed out, our support team will need to investigate further on your behalf. When reaching out, please have the following ready: - The exact GSC property URL that appears greyed out - The Google account email used to connect GSC to Search Atlas - A screenshot of the greyed-out property in Report Builder - Confirmation of your ownership level in Google Search Console for that property 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.

Last updated on Oct 26, 2026

πŸ”„ Heatmap Auto-Refresh Failures and Quota Refunds

Overview If your keyword maps did not refresh on their scheduled date, or you noticed more quota credits consumed than expected, this article explains what to do if a heatmap auto-refresh fails or your quota balance appears incorrect after a refresh attempt. Why Scheduled Refreshes Can Fail Heatmap auto-refreshes can sometimes fail or be skipped. If a refresh did not run as expected, or if quota credits were consumed without a successful refresh, this is a known issue that our team can investigate and resolve on your behalf. How Quota Is Counted Per Heatmap Quota credits are consumed based on the number of grid pins in each heatmap. If you believe credits were consumed incorrectly β€” for example, if a refresh failed but credits were still deducted β€” our support team can review your account and process a refund where appropriate. Steps to Take If Your Refreshes Failed or Quota Seems Wrong 1. Review your heatmap projects and identify which maps did not refresh as scheduled. 2. Note the names of the affected heatmap projects, the keywords configured on each, and the dates the refreshes were expected to run. 3. Check your quota balance to see whether credits were deducted for maps that did not successfully refresh. 4. Contact our support team with the details you gathered. Include the affected heatmap project names, the keywords configured on each, the expected refresh dates, and whether credits were deducted. Our team will investigate the refresh failure, review your quota consumption logs, and escalate a refund to the appropriate internal team on your behalf. Refunds are applied directly to your quota balance once confirmed. If you need assistance, please reach out to our support team. We're happy to help.

Last updated on Oct 26, 2026

πŸ”Œ Fix Google Search Console Connected But No Data

πŸ” Overview If your Google Search Console (GSC) account appears as connected inside Search Atlas but no data is loading, the issue is almost always related to a broken authentication token, a sync delay, or a stale connection β€” not your plan or project quota. This guide walks you through the steps to diagnose and fix it. ⚠️ Before You Begin Confirm the following before troubleshooting: - You are logged into Search Atlas with the Google account that owns or has full access to the Search Console property. - The GSC property is verified and active inside Google Search Console directly. - You have waited some time after first connecting β€” GSC data can take several days to appear for new connections. πŸ› οΈ Step 1: Clear Your Browser Cache A cached session can cause Search Atlas to display a stale connection state. Start here before anything else. 1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) to open your browser's clear cache panel. 2. Select Cached images and files and Cookies and other site data. 3. Set the time range to All time and confirm. 4. Close and reopen your browser, then log back into Search Atlas. 5. Navigate to the relevant GSC data section in Search Atlas and check whether data now appears. πŸ”„ Step 2: Disconnect and Reconnect Your GSC Account If clearing cache does not resolve the issue, the authentication token may have expired or become invalid. Reconnecting forces Search Atlas to issue a fresh token. 1. Inside Search Atlas, go to your account or integration settings. 2. Locate Google Search Console under connected integrations. 3. Click to disconnect and confirm the action. 4. Wait a moment, then initiate a new Google Search Console connection. 5. Follow the Google OAuth prompts and select the correct Google account β€” the one with verified access to your GSC property. 6. Grant all requested permissions. Skipping any permission step is a common cause of silent connection failures. 7. Once reconnected, navigate to the relevant GSC data section and allow some time for the initial data pull to complete. ⏱️ Step 3: Allow for Sync Delays Even after a successful reconnection, data does not always appear instantly. GSC sync timing depends on two factors: - Google's own data latency: GSC typically delays data by a few days on their end. Search Atlas can only display data that Google has already processed. - Search Atlas sync interval: After reconnecting, the platform needs time to fetch and index the data from Google's API. If data still does not appear after allowing adequate time, please reach out to support for further assistance. 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.

Last updated on Oct 26, 2026

πŸ”§ Fix GA4, GSC & LLM Visibility Report Issues

Overview Two separate but commonly related issues can disrupt your reporting in Search Atlas: GA4 and GSC integrations disconnecting, and shared LLM Visibility & Sentiment report links showing blank or missing data. This article explains what is known about each issue and the steps you can take. Why GA4 and GSC Connections Disconnect GA4 and GSC connections can stop working for a variety of reasons. When a disconnection occurs, metrics that depend on a live GA4 or GSC connection may stop updating. How to Reconnect GA4 and GSC To restore a disconnected GA4 or GSC integration, navigate to your integrations settings within the platform and locate the disconnected connection. Re-authenticate using the Google account that has access to the relevant GA4 property and GSC site, and grant all requested permissions when prompted. Once reconnected, allow some time for data to refresh before checking your reports. Why Shared LLM Visibility Report Links Show Blank Data When you share an LLM Visibility & Sentiment report using a shareable link, the recipient may see a blank report or missing data. Known contributing factors include date range settings and sharing configuration limitations. If recipients see blank data, try adjusting the date range on the shared link to ensure it covers the period when your LLM Visibility tracking was active. If the issue persists after adjusting the date range, it may relate to how the report was shared or to a platform-side limitation. In that case, please reach out to the support team for review. OTTO Integration and Reporting If you are using OTTO alongside GA4, GSC, or LLM Visibility reports and notice data discrepancies or unexpected behavior, please contact the support team with your project name and a description of the issue so it can be investigated. 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.

Last updated on Oct 26, 2026

πŸ”§ Fix GA4 Report Builder Date Range Discrepancies

Overview If you notice that GA4 metrics in the Search Atlas Report Builder do not match the numbers shown in your native Google Analytics 4 account for the same date range β€” such as a 90-day period β€” you are not alone. This is a known discrepancy that customers report, and there are several commonly cited reasons why these figures can differ. This article explains the general factors involved and what to check when you encounter this issue. How Report Builder Pulls GA4 Data The Search Atlas Report Builder connects to GA4 via the official Google Analytics Data API. While this uses the same underlying data as your GA4 account, there are important technical differences in how data is sampled, processed, and displayed between the native GA4 interface and any third-party tool that consumes the API. - Data sampling: GA4 may apply sampling to large datasets. Over longer date ranges, the API used by Report Builder can return results that differ from what the native GA4 interface displays. This is a frequently reported cause of discrepancies. - Data freshness and processing lag: GA4 data may not be fully processed immediately. If you pull a report in Report Builder while GA4 is still processing recent data in your selected range, the totals may differ until processing is complete. - Metric definitions: Some GA4 metrics may behave differently depending on how they are queried via the API versus how the native UI renders them. - Timezone and date boundary alignment: If the timezone configured in your GA4 property differs from the timezone settings in your Search Atlas account, date boundaries may shift and day-level counts may not align, especially at the start and end of the selected range. - Filters and segments: Native GA4 reports may have default comparisons, filters, or segments applied that are not replicated in Report Builder. Always verify that no active filters are influencing your native GA4 view. Steps to Troubleshoot the Discrepancy 1. Check your GA4 property timezone. In your GA4 account, locate your property settings and note the timezone configured there. Confirm this matches the timezone used in your Search Atlas reports. 2. Allow sufficient time for data processing. Avoid comparing data for the most recent days. Set your date range to end at least two days before today in both GA4 and Report Builder, then compare again. 3. Remove all filters in the native GA4 interface. Open your GA4 account, navigate to the relevant report, and ensure no segments, comparisons, or custom filters are active that could inflate or reduce the numbers shown. 4. Compare the same metrics. Make sure you are comparing identical metric names in both GA4 and Report Builder, as similarly named metrics can have different defin

Last updated on Oct 26, 2026

Fix Low Citation Scores and Track Aggregator Progress

πŸ” Overview After purchasing citations, it is normal to expect your citation score to rise quickly β€” but several factors can delay or prevent that from happening. This article explains how to track citation progress inside Search Atlas, what causes citations to stall, and how to troubleshoot specific aggregators like Data Axle. πŸ“Š How to View Your Citation Progress To monitor the status of your purchased citations, navigate to the Local section of your Search Atlas dashboard's left sidebar and select Local Citations. The exact location may vary depending on your account configuration. Once there, look for a list or table of your submitted citations that shows each directory or aggregator alongside its current processing status. Citations will generally reflect one of the following states: - Live / Completed β€” the citation has been accepted and is active. - In Progress / Pending β€” the submission is still being processed; no action is needed yet. - Action Required / Error β€” something is blocking the citation from going live and may need your attention. If you are unsure where to find your citation status in your account, open the chat widget in the bottom-right corner of the platform for guidance on locating the correct section. ⏱️ When to Expect Visibility After Purchase Citation processing times vary by aggregator and can take several weeks. Major aggregators may take longer than standard directories, and verification requirements can extend processing time further. Your citation score in Search Atlas updates as completed citations are confirmed, so score changes may lag behind live citations due to data refresh cycles. If a citation still appears unprocessed after an extended period, proceed to the troubleshooting steps below. ⚠️ Common Reasons Citations Fail to Process A low citation score after purchasing from multiple aggregators is usually caused by one or more of the following: - Aggregator processing delays: High-volume aggregators can take longer than expected, especially during peak periods. - Data validation failures: If your business name, address, or phone number (NAP) does not exactly match what is on file with the aggregator, the submission may be rejected silently. - Duplicate records: If a listing for your business already exists in an aggregator's database under slightly different NAP data, the new submission may be flagged or suppressed until the conflict is resolved. - Business verification requirements: Some aggregators require additional identity or ownership verification before publishing a listing. If a verification step was sent and not completed, the citation may remain pending. - Ineligible business type or category: Certain aggregators restrict listings for specific industries or service-area-only businesses without a physical address. 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.

Last updated on Oct 26, 2026

πŸ” Troubleshooting UX Signals Count Fluctuations

This article explains why your UX signals count can change week over week β€” sometimes significantly β€” and what steps you can take to investigate and confirm the numbers you are seeing are accurate and up to date. πŸ” Common Causes of UX Signal Fluctuations UX signals are aggregated from real user behavior data collected across your tracked pages. Because this data is dynamic, counts can shift between reporting windows for several legitimate reasons: - Rolling data windows: UX signals are typically calculated over a rolling time period. As older data ages out and newer data enters the window, totals naturally rise and fall β€” a spike one week may simply reflect a short burst of activity that is no longer within the active window the following week. - Crawl and data refresh timing: Signal counts update when a data refresh occurs. If a refresh runs mid-cycle or is delayed, the count shown may reflect an incomplete picture until the next full refresh completes. - Page indexation changes: If pages are added, removed, or temporarily de-indexed between periods, the number of pages contributing signals will change, directly affecting the total count. - Traffic volatility: A promotional campaign, viral content, or a seasonal event can temporarily inflate signal counts. Once that traffic subsides, counts return to their baseline. - Data source connectivity: If your connected data source (such as Google Search Console) experienced an interruption or a gap in data reporting during a given period, signals derived from that source may be incomplete for that window. πŸ› οΈ Steps to Investigate a UX Signals Fluctuation 1. Wait for the current data cycle to complete. If a refresh is in progress or was recently triggered, allow it to finish fully before comparing counts. Counts viewed mid-refresh may be incomplete and can appear lower or higher than the final settled value. 2. Check the date range applied to your report. Confirm which time window is selected in the view where UX signals are displayed. A change in the selected window β€” even by one day β€” can shift which data points are included and excluded, producing an apparent drop or rise. 3. Compare the two periods and look for coinciding events. Note the exact dates when the count was higher versus lower. Cross-reference those dates with your own analytics for any events such as campaigns, site changes, or technical outages that coincide with the change. 4. Review your connected data source status. Confirm that any integrated data sources (such as Google Search Console) are still connected and actively reporting within your project settings. A disconnected or re-authenticated integration can create a gap in signal collection that reduces counts for the affected period. 5. Check for page-level changes. If pages were added to or removed from your tracked project during either period, the eligible page count will differ, which directly affects the total UX signals count. Review your tracked pages list to identify any additions or removals that align with the timing of the fluctuation. 6. Escalate if the cause remains unclear. If you have worked through the steps above and cannot identify a clear reason for the fluctuation, contact our support team. When you reach out, please have the following ready: your project name, the specific reporting periods you are comparing, any error messages you have seen, and a screenshot of the signal counts in question. 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.

Last updated on Oct 26, 2026

πŸ“Š Report Builder Stability and UI Updates

Report Builder has received a set of targeted fixes and a UI improvement that make the tool more stable, accurate, and easier to navigate. ✨ What's New This release ships three bug fixes and one UI improvement to Report Builder: - Executive Summary tab no longer loads empty: Opening a Full Report previously landed users on a blank Executive Summary tab. This has been resolved so the correct content loads immediately on open. - Facebook Ads integration hidden for GHL accounts: The Facebook Ads integration option was incorrectly visible inside Report Builder for GoHighLevel (GHL) accounts. It is now properly hidden for those accounts to avoid confusion. - Memory and stability leaks fixed: A MobX reaction leak, a ResizeObserver loop, timer leaks, and an unguarded DOM crash have all been resolved, resulting in a more stable and performant Report Builder experience. - Improved location display with tooltips: Location information is now displayed with tooltips for better readability, and the associated button label has been updated to be clearer. πŸ› οΈ How to Use It 1. Navigate to Report Builder from the main platform menu. 2. Open or create a Full Report β€” the Executive Summary tab will now load with content correctly. 3. Hover over any location entry to view the new tooltip with additional detail. 4. GHL account users will notice the Facebook Ads integration option is no longer displayed in the report configuration panel. πŸ“‹ What to Expect - Full Reports will open directly to populated content instead of an empty Executive Summary tab. - The platform should feel more responsive during extended Report Builder sessions due to the resolved memory and observer leaks. - GHL account users will see a cleaner integration list without the Facebook Ads option. - Location tooltips appear on hover and do not require any additional configuration. 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.

Last updated on Oct 26, 2026

πŸ“Š Holistic SEO Pillar Scores Not Displaying

πŸ” Overview The Holistic SEO section in Search Atlas displays scores across three key pillars: Content, Authority, and UX. In some cases, these scores may appear as 0 or fail to display at all β€” even when your site has active content and authority signals. This is a known bug that is handled on the backend. This article explains what you should know and what information to have ready if you need to escalate. βš™οΈ What Is Happening The Holistic SEO pillar scores are sourced from backend data endpoints. When those endpoints do not return data correctly β€” for example, due to a backend service issue β€” the Content, Authority, and UX pillars will display as 0 or remain blank. This is not caused by a configuration error on the customer's side, and there are no self-serve steps that are confirmed to resolve it. The fix requires backend investigation and action by the Search Atlas team. πŸ“‹ What to Expect - Pillar scores showing as 0 or blank is a known issue rooted in how backend data is delivered to the Holistic SEO section. - This type of issue is resolved by the Search Atlas team on the backend β€” no customer-side action has been confirmed to fix it. - Your data and site configuration are not at risk; this is a display/data-delivery issue. πŸ“ What to Have Ready When Escalating If you are experiencing this issue, please gather the following before reaching out to support so our team can investigate as quickly as possible: - Project name β€” the exact name of the affected project in Search Atlas. - Which pillar scores are affected β€” Content, Authority, UX, or all three. - When you first noticed the issue β€” approximate date and time, including your time zone. - Any error messages displayed β€” copy the exact text of any error or note shown in the platform. - Screenshots β€” a screenshot of the affected Holistic SEO section showing the 0 or blank scores. 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.

Last updated on Oct 26, 2026

πŸ“‰ Site Score and Traffic Drop: No Site Changes

πŸ” What This Article Covers If your site score dropped sharply β€” for example, from the low 90s to the 40s β€” and your reported visitor numbers declined at the same time, without any changes made to your website, this guide explains what may be happening and the exact steps to take. A simultaneous drop across multiple metrics with no site changes is a specific scenario. It is different from gradual performance decline and should be treated as a potential reporting or data sync issue, not just normal fluctuation. ⚠️ Why This Pattern Matters When only one metric drops, the cause is often straightforward β€” a new technical issue detected, a ranking shift, or a crawl update. However, when your site score and visitor data both drop sharply at the same time and you have made no changes to your site, this correlation may suggest a data or reporting discrepancy between Search Atlas and Google Search Console. This type of issue is worth escalating to our support team for investigation. 🧭 What to Check Before Reaching Out Before contacting support, gather the following information so our team can investigate quickly. 1. Locate your site score within Search Atlas and note the current value and the approximate date the drop appears to have started. 2. Take a screenshot or record the exact score values shown β€” both the current reading and any historical data visible in the chart. 3. Check whether your keyword rankings also show a sudden change around the same date. 4. Open Google Search Console directly and compare your GSC traffic data for the same date range. Note whether the drop in Search Atlas matches or contradicts what GSC shows. 5. Check whether your GSC connection in Search Atlas is still active. If it appears to have lapsed, reconnect your Google Search Console account through Site Metrics β†’ Site Explorer β†’ Manage Sites/Connect GSC Account (GSC Accounts page). πŸ“Š Comparing Search Atlas Data With GSC Search Atlas pulls visitor and impression data from your connected Google Search Console account. A discrepancy between the two platforms can occur when the GSC connection has lapsed or when there is a data sync issue on the platform side affecting how your property's data is displayed. If your GSC data and Search Atlas data do not match, note the specific date range and metric values for both platforms and share these with our support team so they 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Widget Sizing and Whitelabel DNS Issues

Overview Two common issues arise when building and sharing reports in Search Atlas: widgets appearing at different sizes across report sections, and whitelabel report links failing to load. This article explains what causes each issue and what to have ready when contacting support for assistance. How Report Widget Sizing Works Every widget you add to a report section is independently sized. This means a widget placed in one section will not automatically inherit the dimensions of a similar widget in another section β€” they are treated as separate elements. Because sizing is managed per widget, inconsistencies can appear across sections when widgets are added at different times or in different configurations. Troubleshooting Report Widget Sizing Inconsistencies If your widgets appear at inconsistent sizes across report sections, this is a known configuration challenge in report layouts. To get help resolving it, please have the following ready when you contact our support team: - The name of the report affected - Which sections contain the inconsistently sized widgets - A screenshot or screen recording showing the size difference between sections Our team can review your report layout and advise on the correct steps to match widget sizing across your sections. How Whitelabel Report Links Work When you enable whitelabeling, Search Atlas generates a custom-branded URL for your client reports. This URL relies on a DNS record that must be added to your domain registrar or DNS provider. Until the DNS record is correctly configured and fully propagated, the whitelabel link will not load. Troubleshooting a Whitelabel Report Link Not Working If your whitelabel report link is not loading, the issue is typically related to DNS configuration or propagation. To get help resolving it, please have the following ready when you contact our support team: - The whitelabel domain or subdomain you configured - The exact error message or behavior you see when visiting the link - Confirmation of whether you have added the required DNS record at your domain registrar - Approximately when you made the DNS change Our team can verify your DNS configuration details and confirm whether any additional steps are needed on the Search Atlas side. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Quota Exhausted Errors in Iframed Reports

πŸ” Overview Some users have encountered a quota exhausted error displayed inside iframed white-label reports β€” both Classic and New versions β€” while the same report viewed directly via its live URL works without issue. This article explains what caused the problem and what to do if you see it. βš™οΈ What Caused This Issue This error was caused by a missing internal quota record on the server side. Even though your account had valid quota allocations in the database, a required background data object was absent, which caused iframed versions of reports to incorrectly display a quota exhausted message. This was a platform-level bug, not a problem with your account settings or report configuration. βœ… Current Status A fix for this issue has been deployed to production. If you encountered this error previously, it should now be resolved. Follow the steps below to confirm everything is working correctly. πŸ–₯️ Steps to Verify Your Reports Are Working 1. Log in to your Search Atlas account. 2. Navigate to your Reports section to access your report projects. 3. Open the report that was previously showing the error and copy its iframe or share URL. 4. Load the iframed version of the report in a browser tab or within your white-label environment. 5. Interact with the report β€” apply filters, switch sections, or scroll β€” to confirm no quota exhausted message appears. 6. Repeat this check for both Classic and New report versions if you use both. 🚨 If the Error Is Still Appearing If you complete the steps above and the quota exhausted error is still visible in your iframed reports, the issue may need to be reviewed individually for your account. Before reaching out, gather the following details to help the team investigate quickly: - The specific report URL and the iframe embed URL where the error appears - Whether the error appears in Classic reports, New reports, or both - A screenshot of the error message if possible - Confirmation that the live (non-iframed) URL loads correctly 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.

Last updated on Oct 26, 2026

πŸ”§ Fix Missing Local Citations in Report Builder

Overview If your client received a Report Builder report showing empty or missing local citation data β€” even though the citation campaign shows as completed β€” this is typically caused by a data synchronization issue between the Local Citations module and the Report Builder. This article explains what is happening and what to have ready when you reach out for support. βš™οΈ Why This Happens Report Builder pulls citation data from your Local project at the time the report is generated. If the report was created or last refreshed before the citation campaign finished syncing, the report may capture an incomplete data snapshot. This is a known synchronization issue that requires backend investigation to resolve. πŸ“‹ What to Have Ready When You Escalate Because this issue involves a backend data sync problem, our team will need to investigate on your behalf. Before reaching out, please gather the following information so we can resolve it as quickly as possible: - The name of the affected project in Report Builder. - The name of the Local Citations campaign that appears completed but is not showing data in the report. - The approximate date and time when the report was generated or last viewed. - Any error messages or screenshots showing the empty citation sections in the report. - The Google Business Profile account or location associated with the project, if applicable. 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.

Last updated on Oct 26, 2026

πŸ” URL Indexer Report Delays and Job Processing

πŸ“‹ Overview The URL Indexer submits batches of URLs to third-party indexing services and then polls those services for results. Because the underlying providers require up to 7 full days to process and confirm indexing status, report generation is intentionally delayed until that window closes. Delays during active processing are normal and do not mean your job is stuck. ⏱️ Why Reports Take Up to 7 Days When you submit a batch, Search Atlas sends the URLs to third-party indexing providers. These providers crawl and verify each URL independently. Search Atlas is designed to wait until the full 7-day check window has passed before generating your final report. Polling for results before day 7 is blocked by the platform to prevent incomplete data from appearing in your report. - Days 1–6: Batch is actively being processed by the indexing provider. - Day 7: Search Atlas polls for the completed report and makes it available on your dashboard. πŸ”Ž Common Reasons a Batch May Appear Stuck Even though delays are expected, there are scenarios where a batch can genuinely stall: - Report generation failure: The indexing provider occasionally returns an error when the report endpoint is called too early. Search Atlas retries automatically. - Cron job delay: Background processing jobs run on a schedule. If a job is queued during a high-traffic period, it may take additional time to execute. βœ… What to Check Before Contacting Support 1. Confirm that 7 full calendar days have passed since your batch submission date. 2. Refresh your URL Indexer dashboard and check whether the batch status has updated. 3. Check whether other batches submitted around the same time have completed β€” this helps identify whether the delay is isolated to one batch or platform-wide. πŸ› οΈ What Search Atlas Does Automatically The platform includes built-in safeguards to handle common processing issues: - Report polling is gated on the 7-day check window β€” jobs will not attempt to fetch results before the provider is ready. - If a provider returns a report generation error, the system retries the request automatically without any action needed from you. If your batch has not updated after the full 7-day window and the steps above have not resolved the issue, please note your batch submission date and the specific batch name or ID before reaching out. 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.

Last updated on Oct 26, 2026

⚑ Fix Zero Scores in Holistic SEO Pillars

πŸ” Overview The Holistic SEO dashboard displays four pillar scores β€” Content, Authority, Technical, and UX β€” to give you a complete picture of your site's SEO health. Some customers have noticed that Content and Authority scores appear as 0 even when their site has clear signals, such as published content and backlinks. This article explains why this happens and what to do if you are affected. βš™οΈ Why Pillar Scores Show Zero Content and Authority pillar scores may display as zero due to a backend data issue. The scoring system may fail to correctly retrieve or calculate values for these pillars even when your site has relevant signals, resulting in scores displaying as zero rather than their true values. This is a known bug. If you are seeing zero scores for Content or Authority despite having active content and backlink signals on your site, this is likely caused by the same underlying issue. πŸ› οΈ What to Do If You Are Affected Because this is a backend bug, there are no self-serve steps that will reliably resolve it. Instead, please escalate to our support team so an agent can investigate your account directly. To help us resolve this as quickly as possible, have the following ready when you reach out: - Your project or site name as it appears in the platform - The specific pillars showing zero (e.g. Content, Authority, or both) - Confirmation that your site has active content and backlink signals β€” for example, published pages and known referring domains - Any relevant timestamps β€” when you first noticed the zero scores and whether they appeared after a specific action 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.

Last updated on Oct 26, 2026

πŸ› οΈ Playbook PDF Downloads Incomplete β€” Fixed

πŸ” Overview Some users experienced an issue where PDF documents generated through playbooks were downloading in an incomplete state. This made it impossible to view full reports, and in some cases playbooks appeared to not execute at all. This defect has now been resolved by the Search Atlas engineering team. πŸ“‹ Who Was Affected - Users generating PDF reports via AI agent playbooks - Users who downloaded playbook output documents and found them cut off or missing content - Users whose playbooks appeared to not run or produce no reports at all βœ… What Was Fixed The engineering team investigated and resolved the defect causing playbook-generated PDF documents to download incomplete. The fix is live β€” no action is required on your end to receive it. πŸš€ Steps to Verify the Fix 1. Log in to your Search Atlas account. 2. Navigate to the playbook you were using when the issue occurred. 3. Run or re-run the playbook to generate a fresh PDF report. 4. Download the PDF and confirm the document is complete and all sections are present. If you had previously downloaded an incomplete PDF, discard that file and generate a new one β€” the previously cached or partial output may not reflect the fix. πŸ’‘ Tips for Best Results - Always download a fresh PDF after running a playbook rather than re-downloading a previously generated file. - If a document appears to load slowly, allow it to fully complete before downloading. πŸ†˜ Still Experiencing Issues? If your playbook PDFs are still downloading incomplete after following the steps above, or if you are experiencing a different playbook-related issue, our team is ready to help. Please reach out to our support team for further assistance.

Last updated on Oct 26, 2026

Fix GSC 'No Data Available' and OAuth Connection Errors

This article covers GSC data, GA4 analytics, OAuth connections, and date range issues. ⚠️ Error 1: GSC keyword data shows "No data available" What's happening: Your Google account may need to be reconnected, or the date range is out of bounds. Steps to try: - Go to Site Metrics β†’ Site Explorer β†’ Manage Sites (GSC Accounts page) β†’ View X connected accounts (GSC) β†’ Delete your account from the list β†’ Refresh the page β†’ + Connect New GSC Account β†’ Select Your Account - Go to OTTO SEO β†’ All Sites (SEO Automation) β†’ Manage Sites β†’ Ensure your site is "Active". - Make sure your date range doesn't exceed 16 months back β€” GSC data older than that is unavailable. - Don't select future dates β€” the end date must be yesterday or earlier. - If the connection is active and dates are valid, wait 5 minutes and refresh. ⚠️ Error 2: Google Analytics data shows "Data unavailable" What's happening: Google's Analytics API has daily request limits shared across all Search Atlas users. During peak hours, some requests are temporarily delayed. Steps to try: - Refresh during off-peak hours (early morning or late evening). - Narrow your date range β€” 30 days loads faster than 90 days. - Close and reopen the dashboard β€” analytics data is served from a cache that refreshes every few hours. - Reconnect your Google account to force a fresh token: Site Metrics β†’ Site Explorer β†’ Manage Sites (GSC Accounts page) β†’ View X connected accounts (GSC) β†’ Delete your account from the list β†’ Refresh the page β†’ + Connect New GSC Account β†’ Enter/Select Your Account. - If no analytics data has appeared for 48+ hours, contact support with your GA4 property ID. ⚠️ Error 3: Only some GA4 tabs load β€” others show errors What's happening: Each report tab makes a separate API request. During high-demand periods, some succeed while others are throttled. Steps to try: - Click the failing tab again after 30 seconds. - Try loading the tab during off-peak hours. - Hard-refresh the page and navigate back to the failing tab. - If one specific tab consistently fails (e.g., Conversions), contact support with the tab name and your date range. ⚠️ Error 4: My GSC property isn't showing up when I try to connect it What's happening: The Google account you're connecting doesn't have sufficient access to that property in GSC. Steps to try: - Log into Google Search Console directly and confirm your account has Owner or Full User access β€” Restricted access won't work. - Disconnect and reconnect your Google account in Search Atlas to refresh the property list. - If the property belongs to a different Google account, add that account: Left Sidebar β†’ Site Metrics β†’ Site Explorer β†’ Manage Sites β†’ Connect GSC Account. - If the property was recently created in GSC, wait 24 hours β€” new properties aren't immediately available via API. ⚠️ Error 5: My Google account keeps disconnecting every few days What's happening: Google periodically requires re-authorization for third-party apps β€” this is a Google security policy, not a bug. Steps to try: - Reconnect via Site Metrics β†’ Site Explorer β†’ Manage Sites (GSC Accounts page) β†’ View X connected accounts (GSC) β†’ Delete your account from the list β†’ Refresh the page β†’ + Connect New GSC Account β†’ Select Your Account. - When prompted during the OAuth flow, ensure you grant all requested permissions and check "Allow offline access" if shown. - If you recently changed your Google account password, all connected apps need to be re-authenticated. - Check your Google Account security settings for any alerts requiring re-confirmation of third-party app access. - Contact support if disconnections happen within 24 hours of reconnecting β€” this may indicate a token refresh issue on our end. ⚠️ Error 6: Data in Search Atlas doesn't match what I see directly in GSM What's happening: This is usually a filter or date range difference, not a data error. Steps to try: - Compare the exact same date range in both tools. - Match the device filter β€” "All devices" vs. "Desktop only" produces very different numbers. - Match the country filter. - Note that GSC data has a 3-day processing lag β€” the last 3 days are provisional in both tools. - Contact support only if the discrepancy is more than 10 positions across many keywords and persists for more than 1 week. ⚠️ Error 7: Date range selector resets or shows a validation error What's happening: An invalid date combination was entered. Steps to try: - Make sure the start date is before the end date. - Don't select dates more than 16 months in the past. - Don't select future dates β€” maximum end date is yesterday. - Try typing dates manually instead of using the calendar picker. - Hard-refresh and try setting the date range immediately after the page loads. ⚠️ Error 8: "Insufficient Data" appears in Core Web Vitals field data What's happening: Google's Chrome User Experience Report (CrUX) requires a minimum number of real Chrome users before it generates a report. This is a Google data availability limitation. What to do: - This is not an error β€” use the Lighthouse lab data scores as your benchmark instead. - CrUX field data will appear automatically once your site accumulates enough Chrome user traffic. - Very new sites, low-traffic sites, and sites with mostly non-Chrome audiences may never accumulate CrUX data. - Focus on growing organic traffic to speed up CrUX data availability. Most Google Search Console and Analytics issues are not platform errorsβ€”they are the result of API limits, access permissions, data processing delays, or differences in filters and configurations. Google’s data ecosystem is not real-time and is subject to rate limits, latency, and strict access controls.

Last updated on Oct 26, 2026

Fix Reports Not Syncing Analytics and Heatmap Data

πŸ” Overview If your Search Atlas reports are missing Google Analytics or heatmap data β€” even though your integrations appear connected β€” one or more underlying issues may be preventing a successful sync. This article explains what to have ready and how to get the right help, since resolving this issue typically requires our support team to investigate your specific account. ⚠️ What May Be Happening - Google Analytics 4 (GA4) connection issue: Your GA4 integration may need to be reconnected or re-authorized. Even if the integration appears connected, the underlying authorization may no longer be active. - Account or permission mismatch: The Google account linked during setup may no longer have the necessary access to the GA4 property selected during integration. - Backend sync delay: Data pipelines can occasionally experience processing delays, especially after a new integration is set up. - Heatmap tracking not active: The heatmap tracking may not be correctly configured for your website, or a recent site update may have affected it. πŸ› οΈ What to Do 1. Try reconnecting your Google Analytics integration. In your Search Atlas Avatar Menu (πŸ‘€) β†’ Settings β†’ Integrations, locate the Google Analytics integration and disconnect it, then reconnect it by completing the authorization flow again. Make sure you are authorizing with the Google account that has access to the correct GA4 property. 2. Check your GA4 property access. Log in to Google Analytics (analytics.google.com) and confirm that the Google account you used to connect Search Atlas is still listed as an active user on the correct GA4 property. 3. Wait and recheck. After reconnecting, allow some time for data to populate, then open an affected report and check whether your Analytics or heatmap data has begun to appear. 4. If data is still missing, escalate to our team. Our support team will need to investigate your account directly. Before reaching out, please have the following ready: - The name of the affected report(s) - The GA4 property name or ID you are trying to connect - The Google account email used for the integration - A description of what data is missing and approximately when it stopped appearing 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.

Last updated on Oct 26, 2026

πŸ“Š Google Analytics Shows Wrong Site Data

πŸ” What This Issue Looks Like The Google Analytics section in Search Atlas is designed to show performance data for the website connected to your project. If you are seeing traffic, sessions, or user numbers that belong to a different website, the wrong Google Analytics property is most likely connected. Common signs include: - Numbers that look far too high or too low for your site - A property name or domain in the section that does not match your project - Data that matches another website you also manage in Google Analytics - Empty or zero metrics even though your site clearly receives traffic πŸ’‘ Why This Happens This issue almost always comes down to which Google Analytics property Search Atlas is pulling data from. A property is the container Google Analytics uses to collect data for one website. Common causes include: - Multiple properties under one Google account: If your Google account manages analytics for several websites, the wrong property may have been selected when the connection was first set up. - Similar domain names: Properties for example.com and example.co.uk, or www and non-www versions of the same site, are easy to mix up. - Renamed or reused properties: If a property in Google Analytics was renamed, moved, or reused for a different website, Search Atlas keeps pulling data from the same property ID. - Shared Google accounts across a team: A teammate may have connected a property that belongs to a different client or project. πŸ› οΈ How to Fix It Follow these steps to disconnect the incorrect property and connect the right one: 1. Open your project and go to the Google Analytics section. 2. Note the name and ID of the currently connected property. In Google Analytics 4, the property ID is a number that looks like 123456789. 3. Open Google Analytics in a separate tab, go to Admin, and confirm which property ID belongs to your website. The ID appears next to the property name at the top of the Admin screen. 4. Back in Search Atlas, use the disconnect or remove option to end the current Google Analytics connection. 5. Reconnect Google Analytics and sign in with the Google account that owns the correct property. 6. When the list of properties appears, select the property whose ID matches your website. Double-check the ID before confirming, because this is where most mismatches happen. 7. Save the connection and return to the Google Analytics section in your project. Note: After reconnecting, allow up to 24 hours for data to refresh and display correctly for the newly connected property. βœ… How to Confirm the Correct Site Is Connected Once you have reconnected, verify the fix with these checks: - Match the property ID: The ID shown in Search Atlas matches the property ID in your Google Analytics Admin settings. - Match the domain: The property's website URL exactly matches your project's domain, including www or any subdomains. - Compare the numbers: Sessions and users shown in Search Atlas roughly match the same date range when you view the property directly in Google Analytics. πŸ’¬ Still Seeing Data From Another Site? If you have reconnected the correct property and the section still shows information from a different site, our team can investigate the connection on our side. To speed things up, have these details ready: your project name, the property ID you expect to see, and the domain currently shown in the Google Analytics section. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ” Troubleshooting Dashboard Discrepancies: GBP, Pixels, and Heatmaps

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

Last updated on Oct 26, 2026

πŸ” Diagnose Search Console Sync Failures and Traffic Drops

🧭 Overview A sudden drop in website traffic β€” for example, from 1,000–2,000 visits per day down to 40 β€” or a health report showing no data for your live site can be alarming. These issues are most commonly caused by a disrupted Google Search Console (GSC) data sync, a lapsed GSC connection, or a temporary data gap on our platform. This article walks you through how to diagnose the problem and get your data flowing again. ⚠️ Common Causes of Traffic Drops and Missing Data - GSC connection credentials expired or disconnected: If your Google account authorization lapses, Search Atlas cannot pull fresh data from Search Console. - Data sync delay or gap: Occasional gaps in GSC data can occur due to infrastructure updates. These are usually resolved automatically within 24–48 hours. - Under-reporting from the GSC data mirror: In some cases, our GSC data mirror may temporarily show lower numbers than your actual Search Console data. Always cross-reference with your Google Search Console dashboard directly. - No verified property in GSC: If your site is not verified in Google Search Console, Search Atlas cannot retrieve traffic or performance data for it. - Site not yet analyzed in Search Atlas: A health report will show no data if the site has not been crawled or added as a project. πŸ”Ž Step 1 β€” Check Your GSC Connection Status 1. Log in to your Search Atlas account. 2. Navigate to Left sidebar β†’ Site Metrics (URL: /site-explorer/list). 3. Select your website from the Saved Projects list. 4. Look for any warning or error banner indicating that GSC credentials are unavailable or that the connection needs to be re-authorized. 5. If you see a "Credentials Unavailable" message, proceed to Step 2 to reconnect your GSC account. πŸ”— Step 2 β€” Reconnect Your Google Search Console Account 1. Go to your account settings or the GSC integration section within Search Atlas. 2. Click Disconnect next to your Google account, then click Connect GSC Account and follow the on-screen authorization prompts. 3. Make sure you grant all requested permissions so Search Atlas can read your Search Console data. 4. Once reconnected, return to Site Metrics and allow up to 24 hours for data to repopulate. πŸ“Š Step 3 β€” Verify Your Site in Google Search Console Search Atlas relies on Google Search Console as its data source. If your site is not verified in GSC, no traffic data will be available. - Log in to Google Search Console and confirm your property is listed and verified. - Check that the property type (Domain vs. URL prefix) matches what is connected in Search Atlas. - If your site is not verified, follow Google's verification steps, then reconnect the property inside Search Atlas. πŸ•΅οΈ Step 4 β€” Cross-Reference Data with Google Search Console Directly If your Search Atlas traffic numbers look unexpectedly low, always compare them against your actual Google Search Console dashboard: 1. Open Google Search Console and navigate to Performance β†’ Search results. 2. Set the date range to match what you are reviewing in Search Atlas. 3. Compare total clicks and impressions. If GSC itself shows a drop, the issue originates with Google's data or a real traffic change β€” not a sync problem. 4. If GSC shows normal numbers but Search Atlas shows much lower figures, this may be a temporary under-reporting issue on our platform. Wait 24–48 hours and check again. πŸ› οΈ Step 5 β€” Check the Health Report for Your Site If your health report shows no data for a live site, follow these steps: 1. Go to Left sidebar β†’ Site Metrics and confirm your site appears under Saved Projects. 2. Navigate to OTTO SEO β†’ Site Audit β†’ Overview (Website Overview) and click the Recrawl Site button to trigger a fresh crawl. 3. Wait for the crawl to complete, then reload the health report. 4. If the site was recently added, allow up to a few hours for the initial crawl and health data to appear. πŸ“… Understanding Temporary Data Gaps Occasionally, short-term data gaps can appear in GSC performance graphs β€” including keyword position history or average position spikes. These gaps are typically caused by planned infrastructure maintenance or updates to our data pipeline. Key things to know: - Data gaps are usually resolved within 24–48 hours without any action needed on your part. - Historical data is backfilled once the sync is restored, so you will not permanently lose past records. - If a gap persists beyond 48 hours, contact our support team using the instructions below. βœ… Quick Diagnostic Checklist - GSC account is connected and credentials are valid in Search Atlas. - Site property is verified in Google Search Console. - Traffic drop is confirmed (or not) inside Google Search Console directly. - Site has been analyzed/crawled in Search Atlas. - Waited 24–48 hours after reconnecting GSC before checking for data. πŸ’¬ Still Need Help? If you have completed all the steps above and your data is still missing or your traffic figures remain unexpectedly low, our team is ready to 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.

Last updated on Oct 26, 2026

πŸ“Š Fix Report Recipients and Agent Issues

πŸ“¬ Why reports may reach the wrong recipient Reports are sent to the recipient saved in the report, schedule, or delivery settings. This may differ from the email associated with your Search Atlas account, especially if the report was created or scheduled by another user. Atlas does not intentionally send reports to random addresses. A previous recipient, shared report setting, or delivery destination may still be associated with the report. πŸ” Check the report recipient 1. Open the relevant project or report in Search Atlas. 2. Open the report’s sharing, scheduling, or delivery settings. 3. Review the recipient list and remove any address you do not recognize. 4. Add the email address that should receive the report. 5. Save the changes and review the next scheduled delivery. If you cannot find recipient settings, the report may be managed by another project member or may use a saved schedule. Ask the project owner to review and update the delivery settings. βš™οΈ Confirm your account email Make sure you are signed in to the correct Search Atlas account and workspace. Being a report viewer does not always make you the report recipient. Your account email and the report’s delivery recipient are separate settings. πŸ€– Troubleshoot Atlas Agent failures Atlas Agent may occasionally show an incorrect connection status, fail to complete a large request, or report that an action finished when it did not. These messages can reflect a temporary processing or delivery issue rather than a problem with your connected data source. - Refresh the page and retry the request. - For large reports, split the request into smaller steps. - Confirm that the required project, report, or data source is selected. - Check whether the requested report or file was actually generated before retrying. - For scheduled results, verify the destination and recipient separately. If Atlas Agent says Google Search Console or Google Analytics 4 is disconnected, verify the connection from the relevant project settings. If the connection is active but the message continues, treat the status as potentially incorrect and retry the report. βœ… Prevent future delivery problems - Use a shared team recipient instead of a former employee’s address. - Review recipients whenever you duplicate or transfer a report. - Keep project members and report owners up to date. - After scheduling a report, confirm its recipient and delivery destination. - For important reports, verify that the first delivery arrives as expected. πŸ’¬ Get help from our team When contacting support, include the project name, report name, incorrect recipient, approximate time of the issue, and any Atlas Agent message shown on screen. Do not share passwords or private access tokens. 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.

Last updated on Oct 26, 2026

πŸ“Š Fix a Sudden Google Analytics Bounce Rate Drop

πŸ” What Is a Suspiciously Low Bounce Rate? A bounce rate that drops dramatically overnight β€” for example, falling from 60% to under 10% β€” almost always signals a tracking configuration problem, not a genuine improvement in user engagement. The most common culprit is double tagging: a situation where Google Analytics fires more than once per page, causing every single-page session to register as a multi-page visit and artificially deflating the bounce rate. ⚠️ Common Causes of an Abnormally Low Bounce Rate - Double tagging: Your GA4 measurement ID or Universal Analytics tag is loaded twice on the same page β€” once through Google Tag Manager and once hardcoded directly in the page source. - Duplicate GTM containers: Two separate Google Tag Manager container snippets are firing on the same page, each triggering an analytics hit. - Third-party plugins or themes: A WordPress plugin, Shopify app, or website theme has its own built-in GA integration running alongside your manually added tag. - Misconfigured GA4 events: Custom events or scroll-depth triggers are being counted as new page interactions, resetting the session and preventing a bounce from being recorded. - Cross-domain or subdomain tracking issues: Sessions are being split incorrectly, making single-page visits appear as multi-page journeys. πŸ› οΈ How to Diagnose Double Tagging 1. Open your browser's developer tools. In Chrome, press F12 or right-click the page and select Inspect, then navigate to the Network tab. 2. Filter for analytics requests. Type collect or your GA4 measurement ID (e.g., G-XXXXXXXXXX) in the filter bar and reload the page. If you see two or more hits firing on initial page load, double tagging is confirmed. 3. Use Google Tag Assistant. Install the free Tag Assistant Legacy Chrome extension or use Tag Assistant Companion to record a session on the affected site. Look for duplicate GA4 or UA tags flagged in the report. 4. Inspect the page source. Press Ctrl+U (Windows) or Cmd+U (Mac) to view the raw HTML. Search for your GA measurement ID β€” if it appears more than once, you have a hardcoded duplicate. 5. Audit Google Tag Manager. Log in to your GTM account and check all active tags. Look for multiple GA4 Configuration tags or UA Pageview tags set to fire on All Pages. βœ… How to Fix Double Tagging - Choose one implementation method and remove the other. Best practice is to manage all tags exclusively through Google Tag Manager and remove any hardcoded analytics snippets from the page source or CMS settings. - Disable built-in analytics in plugins or themes. If you use a WordPress plugin such as MonsterInsights, Yoast, or a theme framework that has a built-in GA field, clear that field so the tag only fires through GTM. - Consolidate GTM containers. If multiple GTM snippets are present, work with your developer to merge tags into a single container and remove the duplicate container code. - Publish and verify. After making changes, use Tag Assistant to confirm only one analytics hit fires on page load, then monitor GA4 for 24–48 hours to confirm the bounce rate returns to its historical baseline. πŸ“ˆ Verifying the Fix in Google Analytics Once you have resolved the tagging issue, confirm the fix is working by checking these areas in your GA4 account: - Navigate to Reports β†’ Engagement β†’ Pages and Screens and confirm that the bounce rate for key pages has returned to a realistic range (typically 30%–70% for most websites). - Check Real-Time reports immediately after publishing your fix to ensure only one active user session is recorded per browser tab. - Review the DebugView (Admin β†’ DebugView) with GA4 debug mode enabled to inspect individual event streams and confirm no duplicate page_view events are firing. πŸ’‘ Important Note About Search Atlas Search Atlas is an SEO platform and does not install, manage, or have access to your Google Analytics tags, GTM containers, or site source code. Bounce rate data visible within Search Atlas (for example, under Left sidebar β†’ Site Metrics (Site Explorer)) is sourced from your connected Google Search Console and GA4 property. Diagnosing and fixing a GA tagging issue must be done directly inside your Google Analytics account, Google Tag Manager, and your website's CMS or source code. πŸ†˜ 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.

Last updated on Oct 26, 2026

πŸ“‹ Data Axle Citation Missing From Dashboard List

πŸ” Overview If you can visit your Data Axle citation directly in a browser but it does not appear in your GBP Galactic citation list after a refresh, you are not alone. This is a known visibility gap caused by indexing and synchronization timing between Data Axle's platform and the Search Atlas dashboard. This article explains why it happens and what you can do about it. βš™οΈ Why This Happens When Search Atlas refreshes your citation list, it pulls data from each directory's publicly available index at that point in time. Data Axle in particular has a multi-stage publishing process: - Live on Data Axle's website: Your listing is visible when you visit the URL directly. - Indexed by Data Axle's API or public feed: This can lag behind the live listing by days or, in some cases, weeks. - Recognized by Search Atlas during a refresh: Search Atlas reads from the indexed feed, not the live page directly. If Data Axle's feed has not yet updated, the citation will not appear in your dashboard list even though the listing itself is real and active. This delay is controlled entirely by Data Axle's internal publishing pipeline and is not something Search Atlas can accelerate. βœ… How to Confirm Your Citation Is Genuinely Live Before troubleshooting the dashboard, verify the citation is fully active on Data Axle's side: 1. Visit the Data Axle listing URL directly in your browser. 2. Confirm that your business name, address, phone number, and website are displayed correctly. 3. Check that the page is publicly accessible β€” not behind a login or a preview screen. 4. Copy the full URL and keep it handy; you may need it when contacting support. If any of the details are incorrect or the page requires a login to view, the listing may not be fully published yet, which would explain its absence from the dashboard. πŸ”„ How to Trigger a Fresh Refresh After confirming the citation is live and publicly accessible, trigger a new data refresh in Search Atlas: 1. Go to Home using the left sidebar. 2. Click Refresh data on the Home page. 3. Wait up to 24 hours for the refresh cycle to complete. 4. Return to your GBP Galactic citation list and check whether Data Axle now appears. A single refresh captures a snapshot of available directory data at that moment. If Data Axle's feed updates between your first refresh and this new one, the citation should now be visible. πŸ“… Expected Timelines Use the following as a general guide for how long synchronization can take after a Data Axle listing goes live: - 1–3 days: Most listings appear in the dashboard within this window once the Data Axle feed updates. - 4–14 days: Some listings, particularly newly created ones or recently corrected ones, can take longer to propagate through Data Axle's publishing pipeline. - Beyond 14 days: If the citation is still missing after two weeks and the listing is confirmed publicly accessible, escalate through the chat widget (see below). πŸ› οΈ Step-by-Step Troubleshooting Checklist 1. Confirm the Data Axle listing URL loads publicly without a login. 2. Verify the business name, address, and phone number on the listing match your GBP Galactic project exactly β€” mismatches can prevent matching. 3. Trigger a new refresh from Home β†’ Refresh data. 4. Wait 24 hours, then re-check the citation list. 5. If still missing after 24 hours, wait a total of 7 days from when the listing first went live, then refresh again. 6. If the citation remains absent after 14 days and the listing is confirmed live and accurate, contact the support team. ⚠️ When to Escalate Escalate to the support team if any of the following apply: - The citation has been live and publicly accessible for more than 14 days but still does not appear after multiple refreshes. - The listing details on Data Axle match your project exactly but the citation is still not recognized. - The citation appeared previously and has now disappeared from the dashboard without any changes on your end. 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.

Last updated on Oct 26, 2026

πŸ” Report Download Button Grayed Out Classic Version

πŸ” Overview If the download button appears grayed out or unclickable in the Classic version of the Report Builder, you are not alone. This is a known issue that can affect specific projects even when other accounts and reports download without any problem. This article explains the most common causes and the steps you can take to resolve it. βš™οΈ What Causes the Download Button to Be Grayed Out? Several conditions can disable the download button in the Classic Report Builder: - Report data is still loading or refreshing. If the report has not finished processing, the download option will remain inactive until the data is ready. - A previous export attempt crashed or failed mid-process. A known bug in the Classic Report Builder can cause an export to crash before completion, leaving the button in a disabled state for that project. - An export error occurred silently. In some cases, an "Error During Export" occurs in the background without a clear on-screen message, which also disables the button. - The specific project has a data conflict. Certain projects can trigger download issues while all other reports in the same account work fine. This is often related to the volume or structure of the data in that particular report. πŸ› οΈ Steps to Fix the Grayed-Out Download Button 1. Refresh the report data. Go to the left sidebar, select Reports, then open the affected report (Executive Summary) and click Refresh Summary. Wait for it to complete before attempting to download again. 2. Try the Download .CSV option directly from the project list. On the Reports projects list page, locate the affected report and click Download .CSV directly from the action row. This bypasses the Classic view entirely and can succeed even when the in-report button is grayed out. 3. Switch to the V2 view. From the project list, click View report next to the affected report. The V2 version has its own download functionality and is not affected by the same bug. Download your report from there while the Classic issue is being addressed. 4. Open the report in Classic view and reload the page. Click View (Classic) to open the report, then do a hard refresh of the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). Check whether the download button becomes active after the page fully reloads. 5. Check your browser and clear the cache. A stale cache can prevent the button from rendering in its correct state. Clear your browser cache, close the tab, and reopen the report. 6. Test in a different browser. If the button remains grayed out, open the same report in a different browser to rule out a browser-specific conflict. πŸ“Š When Only One Project Is Affected If every other report in your account downloads successfully but one specific project β€” for example, a report tied to a particular domain β€” remains stuck, this points to a data-level issue with that project rather than an account-wide problem. In this situation: - Use the View report option for that project as your primary download method until the Classic issue is resolved. - Try duplicating the report by creating a new report for the same project and see whether the fresh copy downloads correctly in Classic view. - Note the exact project name and URL so you can share these details with the support team quickly. πŸ’‘ Classic View vs. V2 β€” Which Should You Use? The Report Builder currently offers two views for every report: View (Classic) and View (V2). Both display your report data, but V2 is the more actively maintained version and is less prone to export errors. If you regularly work with the Classic view, consider using V2 as your default until the Classic download issue is fully resolved on all projects. πŸš€ Still Seeing the Issue? If none of the steps above resolve the grayed-out download button, the issue may require a manual review of the specific report and project data. 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.

Last updated on Oct 26, 2026

πŸ” Fix Google Search Console Connection and Property Sync

πŸ” Overview If your Google Search Console (GSC) account appears connected in Search Atlas but your properties are missing from the report generator, you are not alone. This is a known issue related to how GSC properties are verified and synced after linking your Google account. Follow the steps below to resolve it quickly. ⚠️ Common Symptoms - GSC shows as connected in your integrations settings, but no properties appear in the report generator. - The property dropdown is empty or shows a loading state indefinitely. - Previously visible properties have disappeared after a reconnection. βœ… Step 1: Verify Your GSC Property Access in Google Before troubleshooting inside Search Atlas, confirm that the Google account you connected actually has access to the properties you expect to see. 1. Go to Google Search Console (search.google.com/search-console) in a separate browser tab. 2. Sign in with the same Google account you connected to Search Atlas. 3. Confirm your properties are listed and that your account has at least Full User or Owner permission for each one. If the properties are not visible in Google Search Console itself, the issue is with your GSC permissions, not with Search Atlas. Contact your GSC property owner to request access. πŸ”„ Step 2: Reconnect Google Search Console in Search Atlas If your properties are confirmed in GSC but still missing in Search Atlas, disconnect and reconnect your Google account to force a fresh sync. 1. Click your avatar in the top-right corner of the platform. 2. Navigate to Integrations (if available in your menu) or look for the Google connection settings within your account area. 3. Locate the Google Search Console connection and click Disconnect. 4. Wait 10–15 seconds, then click Connect and complete the Google authentication flow. 5. When prompted, make sure you grant all requested permissions, including access to Search Console data. Skipping any permission step can prevent properties from loading. 6. After reconnecting, wait up to 2 minutes for the property list to sync, then return to the report generator and check the GSC property dropdown. 🧹 Step 3: Clear Browser Cache and Try a Different Browser Cached data can sometimes prevent updated connection states from loading correctly. 1. Clear your browser cache and cookies, then reload Search Atlas. 2. If the issue persists, open Search Atlas in a private or incognito window or try a different browser entirely (Chrome or Firefox are recommended). 3. Repeat the reconnection steps above if needed. πŸ‘₯ Step 4: Check Team Member Account Permissions If you are a team member (not the account owner), your role may limit which integrations you can view or manage. 1. Click your avatar in the top-right corner. 2. Go to Team Members (URL: /settings?active_section=team). 3. Confirm your role is set to Admin if you need full access to GSC data and integrations. A Viewer role may have restricted access. If you need your role updated, ask the account owner to adjust your permissions from the Team Members settings page. πŸ’‘ Tips to Prevent Future Sync Issues - Use one Google account consistently. Switching between Google accounts can cause property mismatches. - Grant all permissions during setup. Partial permission grants are the most common cause of missing properties. - Re-authenticate after changing GSC permissions. If your Google-side permissions change, reconnect GSC in Search Atlas to pick up the updates. - Avoid disconnecting and reconnecting repeatedly in quick succession. Allow at least 2 minutes between attempts. πŸ› οΈ Still Not Resolved? If you have completed all the steps above and your GSC properties are still not appearing in the report generator, our team can investigate your account 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.

Last updated on Oct 26, 2026

πŸ“Š Scheduled Report Emails: Delivery & Sender Address

πŸ“‹ Overview The Report Builder lets you schedule automatic email delivery of client reports on a recurring basis. If your scheduled reports are not arriving β€” or your client cannot find them β€” this article explains how delivery works, which sender address is used, and how to troubleshoot common issues. πŸ” How Scheduled Report Delivery Works When you set up a scheduled report in Report Builder, Search Atlas automatically sends the report to the recipient email addresses you specify at your chosen frequency (weekly, monthly, or quarterly). No manual action is required after the schedule is saved. To locate your reports and schedules, go to Left sidebar β†’ Reports (URL: /report-builder/projects-list). From there you can create a new report, open an existing one, and manage its delivery schedule. πŸ“§ Sender Address for Scheduled Reports All scheduled report emails are sent from no-reply@searchatlas.com. This is important to know for two reasons: - Client whitelisting: Ask your clients to add no-reply@searchatlas.com to their safe-senders list or contact their IT team to whitelist the domain searchatlas.com so reports are not filtered into spam or junk folders. - Testing delivery: When testing whether a scheduled report is sending correctly, send it to your own inbox first and check that the email arrives from no-reply@searchatlas.com. If it lands in spam, mark it as safe and ask your client to do the same. πŸ› οΈ Common Reasons Scheduled Reports Are Not Sending If your clients are not receiving scheduled reports, work through the checklist below before escalating. 1. Check the recipient email address. Open the report in Left sidebar β†’ Reports, review the scheduled delivery settings, and confirm the client's email address is entered correctly with no typos. 2. Verify the schedule is active. Confirm the schedule status is enabled. If the toggle is off, the report will not send. 3. Check the client's spam or junk folder. Emails from no-reply@searchatlas.com can be filtered automatically. Ask the client to search their spam folder for the sender address and mark the email as safe. 4. Confirm the send date and frequency. If the schedule was set up recently, the first send may not have occurred yet depending on the selected frequency and start date. 5. Check for report errors. If the report contains a data source that has lost connection or encountered an error, delivery may be affected. Open the report and confirm all data widgets are loading correctly. βœ… How to Test Scheduled Report Delivery Follow these steps to confirm your scheduled report is set up correctly before sharing it with a client. 1. Go to Left sidebar β†’ Reports and open the report you want to test. 2. Open the delivery schedule settings for that report. 3. Temporarily replace the recipient email address with your own email address. 4. Trigger a test send or wait for the next scheduled send window. 5. Check your inbox for an email from no-reply@searchatlas.com. 6. If the email arrives correctly, update the recipient address back to your client's email and confirm the schedule is active. πŸ’‘ Tips for Smooth Client Report Delivery - Always inform clients to expect emails from no-reply@searchatlas.com before the first scheduled send. - Use a clear, descriptive report name so clients can easily identify the email in their inbox. - If a client uses a corporate email domain with strict spam filters, ask their IT team to whitelist searchatlas.com at the domain level. - Double-check the scheduled frequency matches client expectations β€” a monthly report set on the 1st will not send mid-month. πŸ†˜ Still Need Help? If you have followed all the steps above and scheduled reports are still not delivering, 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.

Last updated on Oct 26, 2026

πŸ“§ Fix Scheduled Reports Not Reaching Clients

πŸ—ΊοΈ Overview Scheduled reports in Report Builder are automatically emailed to your clients on the cadence you set. If those emails are not arriving, the most common causes are spam filtering, an unrecognised sender address, or a misconfigured schedule. This article walks you through everything you need to confirm delivery is working correctly. πŸ“¬ Sender Email Address All scheduled reports sent from Search Atlas are delivered from info@marketer.report. You and your clients should recognise this address as the legitimate source of report emails. Because it differs from the searchatlas.com domain, some email clients and spam filters flag it as unknown. Share this address with your clients before their first report is due so they can add it to their contacts or allowlist. This single step resolves the majority of delivery complaints. πŸš€ How to Schedule a Report 1. In the left sidebar, click Reports to open the Report Builder project list (/report-builder/projects-list). 2. Open the report project you want to schedule, or create a new one. 3. Click the Schedule or Email Settings option inside the project. 4. Enter the recipient email address or addresses for your client. 5. Choose your delivery frequency β€” weekly, monthly, or quarterly. 6. Save the schedule. The next send will occur at the next scheduled interval. πŸ” Troubleshooting Delivery Issues If a scheduled report has not arrived, work through the steps below before escalating. - Check the spam or junk folder. Ask your client to search their spam folder for emails from info@marketer.report. This is the most common reason reports go missing. - Allowlist the sender address. Your client's IT team or email provider should add info@marketer.report to their safe senders or allowlist. In corporate environments, this may also require allowlisting at the email gateway level. - Verify the recipient address is correct. Return to the report project in Report Builder and confirm the email address entered is free of typos. - Confirm the schedule is active. Open the schedule settings and check that the schedule has not been paused or that a past end date has not been set. - Check that the report contains data. Some configurations will skip sending if the report returns no data. Ensure the date range and filters are returning results when you preview the report manually. - Send a test email. Use the manual send or preview option inside the report project to trigger an immediate delivery to your own inbox. If this email arrives, the schedule and content are correctly configured β€” the issue is purely a delivery or spam filter problem on the recipient side. βœ… Testing Delivery Step by Step 1. Navigate to Reports in the left sidebar. 2. Open the relevant report project. 3. Temporarily set the recipient address to your own work email. 4. Trigger a manual send. 5. Check your inbox and spam folder for an email from info@marketer.report. 6. If the email arrives in spam, mark it as not spam and add info@marketer.report to your contacts. 7. Once confirmed working, restore the original recipient address and advise your client to add the sender to their allowlist before the next scheduled send. πŸ“‹ Quick Reference - Sender address: info@marketer.report - Scheduled reports location: Left sidebar β†’ Reports - First place to check: Recipient's spam or junk folder - Most effective prevention: Allowlisting info@marketer.report before the first send 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.

Last updated on Oct 26, 2026

πŸ” Troubleshooting GA4 Data Discrepancies in Search Atlas

Overview If the organic traffic or new user numbers in your Search Atlas reports do not match what you see in Google Analytics 4 (GA4), you are not alone. This is one of the most common integration questions our team receives. Discrepancies are almost always caused by differences in how each platform filters, attributes, or processes the same underlying data β€” not a broken connection. This article walks you through the most common root causes and general guidance to help you reconcile the numbers. Common Root Causes - Date range and timezone mismatches: GA4 applies your account timezone to all reports. If Search Atlas is displaying data in a different timezone, daily totals can shift β€” especially for sessions near midnight. Confirm both platforms are set to the same date range and timezone before comparing figures. - Organic traffic definition differences: GA4 classifies sessions as organic based on its own channel grouping rules. If your GA4 property has custom channel groups or modified default channel definitions, the organic segment visible in GA4 may differ from what Search Atlas displays. - New user attribution: GA4's definition of a "new user" depends on when GA4 first registers a Client ID. If a user clears cookies or switches devices, GA4 may count them as new again. Filters applied within GA4 can also affect these counts. Search Atlas reflects the data as received from GA4, so any GA4-side configuration affects both views. - Filters and data streams: GA4 properties can have internal traffic filters, developer traffic filters, or cross-domain tracking configured. If these filters are applied inconsistently β€” or were added or changed after your Search Atlas integration was set up β€” the data visible in Search Atlas may not match your GA4 dashboard view. - Connected property mismatch: If your GA4 account uses multiple properties, ensure Search Atlas is connected to the same property you are comparing against in GA4. Comparing data from different property levels will always produce different numbers. Steps to Investigate 1. Verify which GA4 property is connected. Check your integration settings to confirm the correct GA4 property is linked to your Search Atlas project, and that it matches the property you are reviewing in the GA4 interface. 2. Align your date ranges and timezone settings. Make sure both GA4 and Search Atlas are showing the same date range. Check your GA4 property timezone setting and confirm it aligns with what Search Atlas is using. 3. Review your GA4 channel groupings and filters. In GA4, check whether any custom channel groups, internal traffic filters, or cross-domain tracking rules have been configured. Changes to these settings on the GA4 side will affect the data Search Atlas receives. 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Incomplete Heatmap Grids and Credit Refunds

πŸ” Overview Some heatmap auto-refreshes have completed only partially. Affected heatmaps display a single data point instead of the expected full grid. This article explains what happened and how Search Atlas is handling credit refunds for affected snapshots. βš™οΈ What Caused the Incomplete Grids A bug caused some heatmap auto-refresh snapshots to fail mid-process. Instead of returning a full grid, the system recorded only a single point and marked the refresh as complete. πŸ“Š How to Identify Affected Heatmaps To check whether any of your heatmaps were affected, navigate to your Local SEO Heatmaps and review the snapshot history for any recent auto-refreshes. An affected snapshot will show a single pin or point on the map rather than a full grid of ranked positions. Note the heatmap name, keyword, and the date of the affected refresh β€” you will need this information when contacting support. πŸ’³ Credit Refunds for Failed Refreshes Search Atlas is committed to ensuring you are not charged credits for heatmap snapshots that did not deliver complete data. Here is what you need to know: - Scope: Any auto-refresh snapshot that returned a single point instead of a full grid is considered a failed refresh and is eligible for a credit refund. - If you do not see a credit adjustment in your account, please contact support so the team can review your account directly. Have your heatmap name, affected keyword, and the date of the failed refresh ready. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Builder PDF Export Truncation Issues

πŸ” Overview Two common issues affect Report Builder exports and shared report links: PDF exports that show only a subset of your tracked keywords (for example, 10 out of 26), and public report links that display empty sections for widgets like Rank Tracker while only showing Google Analytics data. This article explains why these issues occur and what steps you can take right now to work around them. ⚠️ Known Issue: PDF Export Truncates Rank Tracker Keywords When you export a report to PDF, the Rank Tracker widget may display fewer keywords than you have actually tracked. This is a confirmed platform bug that our team is aware of and working to resolve. Why it happens: Not all keywords visible inside the platform are rendered in the PDF export output β€” some keywords are cut off during the export process. Current workaround: 1. Open your report inside the platform and take a full-page screenshot of the Rank Tracker section for a complete view of all keywords. 2. Export keyword data directly from the Keyword Rank Tracker tool as a CSV for a full data set to share with clients. 3. Reduce the number of keywords displayed in a single Rank Tracker widget by splitting them across multiple widgets grouped by topic or priority, which may help reduce truncation in the current export. πŸ”— Known Issue: Public Report Links Show Empty Sections When you share a report via a public link, some sections β€” including Rank Tracker β€” may appear empty or blank, while only certain integrations such as Google Analytics display data correctly. Why it happens: This is a known issue where certain widget data does not load correctly in the public report link view, even though all sections display properly when viewing the report while logged in to the platform. Current workaround: 1. Instead of sharing the public link directly, use the PDF export from inside the platform and share the downloaded file with your client. Note: apply the keyword truncation workaround above if Rank Tracker data is important. 2. Walk clients through the report in a live screen-share session using the in-platform view, which displays all sections correctly. 3. For white-label purposes, ensure your branding is configured before generating the PDF so that exported files carry your branding. βœ… How to Generate a Complete Branded PDF Export 1. Open your report inside the platform while logged in. 2. Confirm all sections display the data you expect before exporting. 3. Use the PDF export option within Report Builder to download the file. 4. Apply any workarounds noted above for Rank Tracker keyword truncation before sharing with clients. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Builder Full Report Errors

πŸ” What This Article Covers If you see an error when trying to view or download a Full Report in Report Builder, the most common cause is a disabled or disconnected Rank Tracker project connection. This is a known, fixable issue β€” not a platform-wide error with no solution. Follow the steps below to restore the connection and get your report working. ⚠️ Why This Error Happens Report Builder's Full Report pulls live ranking data directly from your Rank Tracker project. If the connection between Report Builder and your Rank Tracker project has been disabled β€” either manually or after a settings change β€” the report cannot retrieve the data it needs and returns an error. No data loss occurs; the connection simply needs to be re-enabled. βœ… How to Fix It: Re-enable the Rank Tracker Connection 1. In the left sidebar, click Keywords, then select Rank Tracker (Keyword Rank Tracker). 2. Locate the Rank Tracker project that your Report Builder report is linked to. 3. Open the project settings (look for a gear icon or the project name menu). 4. Check whether the project connection is set to disabled or inactive. If it is, toggle it back to enabled or active. 5. Save your changes and return to Report Builder. 6. Try viewing or downloading the Full Report again. In most cases, re-enabling the connection resolves the error immediately. If the report does not load within a few minutes, try refreshing your browser tab. πŸ”Ž How to Confirm Which Project Is Linked If you are unsure which Rank Tracker project your report is connected to, follow these steps: 1. Open Report Builder and select the report that is producing the error. 2. Review the report settings or edit view to identify the name of the linked Rank Tracker project. 3. Navigate to Left sidebar β†’ Keywords β†’ Rank Tracker (Keyword Rank Tracker) and match that project name. 4. Proceed with the re-enable steps above. 🚫 What This Error Is Not This error is not an uncatalogued or unresolvable platform error. If you have previously been told there is "no available workaround" for a Full Report error in Report Builder, that diagnosis was incorrect. The cause is almost always a disabled Rank Tracker project connection, and it has a straightforward fix. Always check the Rank Tracker connection status before assuming the error is unresolvable. πŸ›‘οΈ How to Prevent This Error in the Future - Before disabling or archiving a Rank Tracker project, check whether any Report Builder reports are linked to it. - If you need to pause a Rank Tracker project temporarily, note which reports depend on it so you can re-enable the connection when nee

Last updated on Oct 26, 2026

πŸ“Š Fix Report Email and Atlas Agent Issues

πŸ“§ Why reports may reach the wrong email Report emails are associated with the Search Atlas account, report configuration, or team member who created the report. If a report goes to an unfamiliar address, the recipient may be linked to an older account owner, a previous report setup, or a duplicate delivery setting. βš™οΈ Check your account and team settings 1. Open the Avatar Menu (πŸ‘€) in the top-right corner. 2. Select Team Members. 3. Review the listed members and identify the account used to create or receive reports. 4. Deactivate outdated members if appropriate, and confirm that the intended user has the correct role. Then create or resend the report from the correct account. Avoid creating duplicate report schedules while testing, as this can result in multiple emails. πŸ“„ Troubleshoot branded PDF or HTML reports 1. Confirm that the report contains completed data before exporting or sending it. 2. Retry the report from the relevant report or content workflow. 3. Check whether the issue affects both PDF and HTML formats or only one format. 4. Verify that the brand details, logo, domain, and report sections are complete and saved before generating the file. 5. Download the file only after the platform confirms that generation is complete. If no download starts, do not assume the file was created. Atlas Agent may occasionally use unrelated domain-family data, incorrectly describe connected data sources, or confirm a download that did not occur. Review the generated report against the selected project before sharing it. πŸ” Check the report workflow For content reports, open Content in the left sidebar and select Content Genius. Use the available generation or writing action, then review the resulting report before sending it. For audits, open Content β†’ Onpage Audit, select the relevant tab, and use Generate Report or Share. βœ… Best practices before sending - Use the intended project and domain. - Confirm the recipient account and team member. - Review report data, branding, and file format. - Test one delivery before enabling recurring reports. - Check for duplicate messages if more than one report workflow is active. πŸ’¬ Get help with a recurring failure When contacting support, include the project name, report type, file format, expected recipient, actual recipient, and the approximate time of the failed attempt. Screenshots or the generated file can also help identify the issue. 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.

Last updated on Oct 26, 2026

πŸ”§ Fix Reports Sent to Wrong Email Address

πŸ“‹ Overview Automated reports in Search Atlas β€” including LLM Visibility and citation notification emails β€” may sometimes continue to be delivered to an outdated or incorrect email address. This can happen when an account email changes, a team member leaves, or a recipient was saved incorrectly during an earlier configuration. Because this issue involves how recipient data is stored on the backend, it typically requires our team to investigate and correct it directly. πŸ” Why Reports Go to the Wrong Email This issue usually happens for one of the following reasons: - A stale email address was saved as a report recipient before your account email was updated. - A previous team member's email was set as the recipient and was never removed. - Automated emails were configured during onboarding and have not been reviewed since. In some cases, the system may continue delivering reports to a stored email address even after changes are made on your end. This type of issue is resolved on the backend by our support team. πŸ› οΈ What to Do If Reports Are Going to the Wrong Address Because recipient data for automated reports is managed at the backend level, the most reliable resolution is to contact our support team directly. To help us resolve this as quickly as possible, please have the following ready when you reach out: - Your project name and the Search Atlas account email address associated with it. - The email address currently receiving the reports (the incorrect or stale one). - The correct email address you want reports to be sent to going forward. - The type of report affected (for example, LLM Visibility reports, citation emails, or scheduled reports). - Any relevant timestamps β€” such as when you first noticed the issue or when the last incorrectly delivered report was received. Our team will locate the stored recipient data on the backend and update it to the correct address on your behalf. 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.

Last updated on Oct 26, 2026

πŸ” Troubleshooting Report Quality and Accuracy Issues

🧭 Overview If a generated report contains unexpected data, missing metrics, or results that don't match your expectations, this guide will help you identify the root cause and take corrective action. Working through these steps systematically will resolve the majority of report quality issues. πŸ—‚οΈ How to Access Your Reports Navigate to Left sidebar β†’ Reports or go directly to /report-builder/projects-list. From here you can open, edit, regenerate, or review any existing report. ⚠️ Common Causes of Report Quality Issues - Incorrect date range selected: The report pulled data from the wrong time period, causing metrics to appear off or incomplete. - Wrong project or domain configured: The report is pulling data for a different property than intended. - Filters applied unintentionally: Active keyword, location, or device filters may be excluding data you expect to see. - Data source not yet indexed: New projects or recently added keywords may not have enough historical data to populate all metrics. - Cached or stale data: The report may have been generated before the latest crawl or ranking update completed. - Metric misalignment: The report template includes metrics that don't apply to the selected project type or subscription tier. - Template misconfiguration: Sections, widgets, or branding elements were not set up correctly before generation. πŸ”Ž Step-by-Step Diagnosis 1. Open the report in question. Go to Left sidebar β†’ Reports, locate the report, and open it for review. 2. Check the date range. Confirm the date range shown in the report matches the period you intended to cover. Adjust and regenerate if needed. 3. Verify the linked project and domain. Inside the report settings, confirm the correct project and domain are selected. A mismatch here is one of the most common causes of inaccurate data. 4. Review active filters. Check for any keyword, location, device, or tag filters that may be narrowing the data. Remove unintended filters and regenerate the report. 5. Compare data against the live dashboard. Open the corresponding project dashboard and compare key metrics directly against what appears in the report. If the dashboard matches your expectations but the report does not, the issue is in the report configuration, not the underlying data. 6. Check when the report was last generated. If the report was generated before a recent crawl or ranking refresh completed, regenerate it to pull the latest data. 7. Inspect the template settings. Open the template used for this report and confirm all sections and widgets are correctly configured for the project type. Remove or replace any widgets that are not applicable. 8. Regenerate the report. After correcting any configuration issues, regenerate the report and review the output before sending it to your client. βœ… Data Validation Checklist Before sending any report to a client, run through the following checks: - Date range is correct and clearly labeled. - Domain and project name match the client's property. - All key metrics are populated and not showing as zero or blank. - No unintended filters are active. - Branding, logo, and client name are accurate. - Metrics align with the client's goals and the report template purpose. - The report was generated after the most recent data refresh. πŸ› οΈ When to Regenerate vs. Reconfigure Regenerate the report when the configuration looks correct but the data appears stale or incomplete. This forces the system to pull the most current data available. Reconfigure the report when the date range, project, domain, filters, or template settings are incorrect. Always regenerate after making configuration changes. πŸ“‹ Information to Gather Before Contacting Support If the steps above do not resolve the issue, collecting the following information in advance will allow our team to investigate efficiently without needing to follow up multiple times: - The name and URL of the affected report. - The project and domain the report is linked to. - The date range the report was configured to cover. - A description of what the report shows versus what you expected to see. - Screenshots or a screen recording highlighting the specific discrepancy. - Whether the live dashboard for the same project shows correct data. - The date and time the report was originally generated. πŸ’¬ Contact Support 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.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Heatmap Grids Incomplete and Credit Restoration

πŸ” What Happened A platform issue caused a number of heatmap grids to stop refreshing correctly. The system incorrectly reported that accounts had insufficient credits even when enough credits were available, causing heatmap refreshes to be skipped and leaving grids incomplete or outdated. This issue has been identified and resolved by the engineering team. πŸ’³ Will Credits Be Refunded? Yes. If your heatmap grids failed to load or refresh due to this platform issue, you will not be charged credits for those failed scans. Credits consumed by grids that did not load properly are eligible for restoration. - If you believe credits were deducted for grids that clearly did not produce results, our support team can review your account and restore the balance manually. πŸ“‹ How to Check Your Heatmap Status 1. Navigate to your Local SEO section and open the relevant GBP project. 2. Review your heatmap grids for any that appear blank, incomplete, or show outdated scan dates. 3. Note the names of any affected grids so you can reference them if you contact support. πŸ”„ Do You Need to Manually Re-Run Affected Grids? If a grid still appears incomplete, you may trigger a manual refresh from within the heatmap grid view. Contact support before doing so if you are concerned about additional credit usage. ⚠️ Will This Affect Future Scheduled Refreshes? No. The underlying issue that caused scheduled refreshes to be skipped has been resolved. Heatmaps set to refresh on a schedule will refresh as expected going forward, and the system will no longer reject quota requests due to incorrect balance readings. πŸ› οΈ What to Do If You Still See Issues If your heatmap grids remain incomplete, or if you believe your credit balance was not correctly restored, please reach out so our team can investigate your specific account. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Fix Report Builder Sections and Competitor Sync

πŸ” Overview Two common issues in Report Builder can disrupt your client reports: sections that appear in the published report but are missing from the backend editor, and competitor domains that continue showing outdated data even after you've updated them. This article explains why these issues happen and what steps you can take. πŸ—‚οΈ Removing a Section That Doesn't Appear in the Editor You may notice a section visible in your published or previewed report, but it is nowhere to be found inside the Report Builder editor. This can happen with certain sections that are no longer fully supported in the current editor interface. Because this type of issue involves report configuration that cannot always be resolved through the standard editor controls, it typically requires direct assistance from our support team. To help us resolve it as quickly as possible, please have the following ready when you reach out: - The exact name of the report affected - The project the report is associated with - A description or screenshot of the section appearing in the published or previewed report that you cannot locate in the editor πŸ”„ Competitors Not Updating in Your Report After adding, removing, or changing competitor domains in your project settings, you may find the Report Builder still displays the old competitor data. This is a known sync issue that requires backend investigation and cannot always be resolved through the standard interface alone. To help our team investigate and fix this for you, please have the following ready when you reach out: - The name of the project whose competitor settings you updated - The competitor domain(s) you added or removed - Approximately when you made the change and when you first noticed the data was not reflecting correctly - Any error messages or unexpected behaviour you observed 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.

Last updated on Oct 26, 2026

πŸ“Š GSC Report Data Not Showing for a Location

πŸ” Overview If Google Search Console (GSC) data is missing or blank in your reports, the most common cause is that the associated location has not been activated in your project settings. Report data visibility in Search Atlas is directly tied to a location's activation status. βš™οΈ How Location Activation Affects GSC Reports Search Atlas controls which locations contribute data to your reports based on their activation state. A location must be active for its GSC statistics to appear in your reports. Even if the GSC integration is confirmed and data is visible elsewhere, an inactive location will not surface that data in generated reports. - Active location: GSC data is included and visible in reports. - Inactive location: GSC data is excluded from reports, even if the integration is working correctly. πŸ› οΈ How to Fix Missing GSC Data in Reports 1. Navigate to your project's location settings. 2. Find the location that is missing data in reports. 3. Check the location's status. If it is set to Inactive, switch it to Active. 4. Open or regenerate the relevant report for that location. 5. Confirm that GSC statistics are now visible in the report. βœ… How to Confirm the Integration Is Working Before checking activation status, verify the following to rule out other issues: - The GSC account is connected and authorised under Site Metrics β†’ Site Events/Site Structure (GSC pages) β†’ Connect GSC Account / Manage Sites. - GSC data is visible for the location in question outside of the report. - The correct date range is selected in the report. If all of the above are confirmed and data still does not appear in your report, the activation status of the location is the most likely cause. 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.

Last updated on Oct 26, 2026

πŸ“Š Report Builder Stability and UX Improvements

The Report Builder has been updated with three important bug fixes and a user experience improvement, ensuring more reliable report generation and a cleaner interface. ✨ What's New This release addresses stability issues and refines how location data is displayed within your reports. The update includes fixes for a blank Executive Summary tab on full report loads, removal of the Facebook Ads integration option for GHL accounts where it does not apply, and resolution of underlying performance issues including a MobX reaction leak, ResizeObserver loop, timer leaks, and an unguarded DOM crash. Additionally, the location display has been enhanced with tooltips for better context, and button labels have been adjusted for improved clarity. πŸ› οΈ How to Use It 1. Navigate to the Report Builder from your Search Atlas dashboard. 2. Open or create a full report β€” the Executive Summary tab will now load correctly with content instead of appearing blank. 3. Review your report's location fields to see the updated tooltip display providing additional context on location data. 4. GHL account users will notice the Facebook Ads integration option is no longer shown in the report builder, keeping the interface relevant to your available integrations. πŸ“‹ What to Expect Reports will load more reliably with the Executive Summary tab displaying content as expected on first open. The platform will also run more efficiently in the background thanks to the resolution of memory and performance leaks. GHL accounts will see a cleaner integration list with Facebook Ads removed. Location-related fields now include tooltips to help clarify displayed data, and button labels have been updated to better reflect their actions. 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.

Last updated on Oct 26, 2026

πŸ“‰ Troubleshooting Unexpected UX Signal Count Fluctuations

If your UX signal count appears to change unexpectedly between reporting periods β€” for example, rising one week and returning to a lower number the next β€” this article will help you gather the right information so our team can investigate efficiently. Information to Gather Before Reaching Out Because UX signal count fluctuations can stem from several backend factors, the most effective first step is to collect key details about what you observed. Having this information ready will allow our team to investigate the root cause much faster. 1. Note the exact signal counts β€” Record the specific numbers you saw in each reporting period, including the dates each count was observed. 2. Note the reporting periods β€” Identify the date ranges or reporting windows for each period where you noticed the discrepancy. 3. Identify your project or workspace β€” Have your project or workspace name available so the team can quickly locate your account. 4. Note when the fluctuation started β€” If possible, identify the approximate date or timeframe when you first noticed the unexpected change. 5. Describe any recent changes β€” If you are aware of any changes to your account, integrations, or configuration around the time the fluctuation began, note them so you can share that context. What to Expect When You Contact Support Once you reach out with the details above, our team will investigate the fluctuation on the backend. This typically involves reviewing your account's signal data, checking for sync or processing irregularities, and confirming whether the counts reflect expected behavior or require correction. 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.

Last updated on Oct 26, 2026

🐞 Citations Showing No Data

πŸ” What does β€œno data” mean? If the Citations module shows β€œno data” for your citations, this may be caused by a bug affecting how the module displays citation results. An empty view does not necessarily mean your citations were removed or that your campaign failed. βœ… Check the Citations module 1. Open the Citations module in Search Atlas. 2. Wait a few minutes, then refresh the page and review the citations again. 3. Check the module again later to see if results have appeared. A refresh may not immediately change the display when the issue is caused by the underlying bug rather than missing citations. πŸ”„ Try these troubleshooting steps - Refresh the page and reopen the Citations module. - Sign out of Search Atlas, sign back in, and check the Citations section again. - Check again later in case results take additional time to appear. πŸ“Š What you should expect When the module is working correctly, it should show citation records and their details instead of displaying β€œno data” for every listing. πŸ› οΈ When to contact support If all citations still show β€œno data” after refreshing and checking back later, this is likely a bug our team needs to investigate. When reaching out, have the following ready: the affected project name, the exact β€œno data” message you see, and when you first noticed the issue. Include a screenshot if possible. 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.

Last updated on Oct 26, 2026

πŸ“Š Fix Empty or Failed Report Exports

πŸ” What causes export problems? Report Builder supports PDF exports and, in version 3, CSV and Excel downloads. An export may appear empty or fail when report data has not finished loading, filters return no results, the export request times out, or the browser interrupts the download. Previously identified export issues have been fixed. If a report still exports incorrectly, use the steps below to confirm the report is ready and create a file containing the data currently visible. πŸ”„ Refresh and reload the report 1. Open Reports from the left sidebar. 2. Open the affected report. 3. Confirm that charts, tables, and metrics are visible and fully loaded. 4. Select Refresh data, then wait for the report to finish updating. 5. Reload the browser page and confirm the data is still visible. Do not start the download while sections are still loading or showing blank placeholders. 🧰 Check filters and report content - Review the selected date range, projects, pages, and other filters. - Temporarily remove restrictive filters and refresh the report. - Confirm that the visible table or chart contains actual values, not only headings or empty states. - If only one section is empty, check whether that section has data for the selected period. πŸ“₯ Download the correct format 1. From the report, select Download .CSV for a CSV file. 2. For Excel, choose the Excel download option available in your Report Builder version. 3. For a PDF, use the PDF export option after all report sections have loaded. 4. Wait for the download to complete before opening the file. Exports generally reflect the report data and filters active when the download begins. To export the data currently visible, keep the desired filters applied and verify the on-screen content before downloading. πŸ› οΈ Troubleshoot a failed download - Try the export again after refreshing the report. - Use a current browser version and allow downloads for the platform. - Disable browser extensions that block downloads or pop-ups. - Try a private browser window or another supported browser. - For large reports, export after narrowing the date range or reducing the number of selected items. - Check your downloads folder and browser download history; the file may have completed even if the page did not show a confirmation. βœ… Verify the exported file Open the downloaded file and compare it with the report on screen. Confirm that the expected columns, rows, charts, and date range are included. If a CSV or Excel file has headers but no rows, refresh the report, confirm that data is visible, and download it again. πŸ’¬ Get help with a specific report When contacting support, note the report name, export format, date range, filters, approximate time of the attempt, and whether the data was visible before downloading. This helps the team investigate and generate a valid file when appropriate. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ—ΊοΈ Heatmap Incomplete Grids Bug & Credit Refund

πŸ” What Happened A bug affected auto-refresh heatmap scans across affected accounts. Instead of generating full grid maps, the refresh produced incomplete grids showing only a single point rather than the expected coverage area. This caused heatmap scans to consume credits without delivering usable results. The root cause was a backend issue in which heatmap grid coordinates contradicted the stored spacing configuration. As a result, the system scanned the wrong radius, understated or overstated rankings, and in some cases rendered an in-flight refresh as an empty map with an average position of 0 β€” rather than displaying the last valid completed scan. ⚠️ Which Scans Were Affected - Heatmap scans triggered by auto-refresh during the affected window - Scans that displayed a single pin or showed an average position of 0 - Scans where the grid coverage area appeared smaller or different from your saved settings Manually triggered scans completed outside this window were not affected by this specific incident. πŸ› οΈ What We Fixed Our engineering team has resolved the following issues related to this incident: - Grid coordinate mismatch: The backend now correctly aligns grid coordinates with your stored spacing settings, ensuring the right radius is scanned every time. - In-flight refresh display: Heatmaps no longer show an empty map or an average position of 0 while a refresh is in progress β€” the last successfully completed scan is displayed instead. Additional investigation is ongoing to fully address this incident. We will update this article as further fixes are released. πŸ’³ Credit Refunds We understand that affected accounts consumed credits on failed or incomplete refreshes during this incident. We are committed to making this right. Here is what you need to know about refunds: 1. Eligibility: Any credits spent on heatmap auto-refresh scans that produced incomplete or single-point grids during the affected window are eligible for a refund. 2. How to check your credit activity: Review your billing or credit usage section within the platform to identify credits consumed on affected scans. 3. Requesting your refund: Contact our support team, share the approximate date range and the number of credits affected, and our team will process your refund promptly. πŸ”„ How to Re-Run Affected Heatmaps Once the fix has been applied to your account, you can manually trigger a new heatmap scan for any affected location. The new scan should generate a complete grid consistent with your saved settings. If you are unsure whether the fix has been applied to your account, please reach out to our support team. 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.

Last updated on Oct 26, 2026

⚑ Fix Trend Arrow Misalignment in Reports

Overview Trend arrows in Search Atlas reports give you a quick visual signal β€” green for improvement, red for decline. Occasionally, customers notice that an arrow appears to show the wrong direction relative to the underlying metric number. This article explains what to check and steps you can take to resolve it. Steps to Troubleshoot a Misaligned Trend Arrow Before contacting support, work through the following checks. Many cases of trend arrow misalignment can be resolved by adjusting your report settings directly. 1. Check your date range and comparison period. Open the report and review the date range selector. Confirm that the comparison period is set to what you intend β€” for example, if you are viewing the current week, make sure the comparison is set to the previous week rather than the previous year or a custom range you did not expect. A mismatch between these two windows is a common cause of arrows pointing in the unexpected direction. 2. Review your widget or metric settings. Open the settings for the specific widget or metric showing the misaligned arrow. Confirm that the metric direction is configured correctly for your use case. Some metrics should increase over time (higher is better) while others should decrease (lower is better). If this setting is incorrect, the arrow color and direction will appear inverted relative to what you expect. 3. Refresh or reload the report. If the arrow still appears misaligned after confirming your settings, refresh the page or reload the report to rule out a display rendering issue. 4. Test with a different date range. Switch to a different date range and then switch back to your original range. This can force the report to re-evaluate the comparison calculation and clear any stale display state. If the Issue Persists If you have worked through the steps above and the trend arrow still shows the wrong direction, our support team will investigate your specific report setup. Please have the following ready before reaching out: - The name of the affected report and the specific metric or widget showing the misaligned arrow. - The date range you are currently using and the comparison period you expected the arrow to be based on. - A screenshot of the misaligned arrow alongside the metric value, if possible. - When you first noticed the issue β€” including an approximate date and time. 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.

Last updated on Oct 26, 2026

πŸ”Œ Fix Report Builder Access After GSC Disconnection

πŸ” Overview If you cannot open reports in Report Builder β€” or if keywords are missing from your reports β€” the most common cause is a disconnected Google Search Console (GSC) API key. When the GSC connection drops, Search Atlas loses access to the data it needs to populate your reports. Refreshing the API connection typically resolves this immediately. ⚠️ Symptoms of a Disconnected GSC API - Reports in Report Builder fail to open or appear empty. - Keywords are not being pulled into your reports. - Previously working reports suddenly become inaccessible. πŸ› οΈ How to Restore Your GSC Connection 1. Navigate to Reports. In the left sidebar, go to Reports. 2. Open the affected report. Select the report that is inaccessible or missing keyword data (for example, your client or project report) to open its Executive Summary. 3. Refresh the data connection. Click Refresh Summary on the Executive Summary page to trigger a fresh pull from your connected GSC account. 4. Repeat the refresh if needed. In some cases, the API connection requires more than one refresh to fully re-establish. Click Refresh Summary again if the report does not immediately populate. 5. Verify the connection is restored. Confirm that keywords and report data are loading correctly on the Executive Summary. πŸ’‘ Why Does This Happen? Google periodically revokes or expires API tokens for connected third-party applications, including Search Atlas. This can happen after a password change on your Google account, a security review, or simply due to token expiry. The disconnection is not always announced β€” the first sign is often missing data or inaccessible reports. πŸ”„ Preventing Future Disconnections - If you change your Google account password, reconnect your GSC integration in Search Atlas promptly. - Check Report Builder periodically to ensure keyword data is still being pulled as expected. - If a report stops updating, try a manual data refresh as a first step before escalating. πŸ“ž Still Need Help? If refreshing the data connection does not restore your reports or keywords, your GSC account may need to be fully re-authenticated. 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.

Last updated on Oct 26, 2026

πŸ“Š Restore Historical GA4 Report Data

πŸ” Why historical GA4 data may be missing Search Atlas retrieves GA4 reporting data live from Google Analytics when you open a report. It does not pre-aggregate or permanently store historical GA4 data in a separate warehouse. If your report shows recent data but older periods are empty, the cause is usually a disconnected Google Analytics profile, an authorization issue, or Google Analytics data-retention limits. πŸ”— Reconnect your Google Analytics profile 1. Open Reports from the left sidebar. 2. Select the relevant project or report. 3. Check the connected Google Analytics profile and property. 4. If the connection is expired or unavailable, reconnect or re-authorize the Google profile. 5. Return to the report and select the required date range again. Reconnecting restores Search Atlas access to data that is still available through the linked GA4 property. No separate data re-ingestion process is required. πŸ“… Check GA4 data retention Google Analytics controls how long some report and exploration data remains available. Depending on the property configuration, retention may be limited to 2 months or 14 months. Data older than the active retention period cannot be retrieved or reconstructed by Search Atlas. For example, if your property retains a report type for 2 months, changing the Search Atlas date range to include older dates will not make that data appear. βš™οΈ Confirm the report and date range - Confirm that the correct GA4 property is connected to the Search Atlas project. - Use a date range within the property's available retention window. - Check whether the selected metric or dimension, such as new users or returning users, is supported for the requested period. - Refresh the report after reconnecting or changing the date range. 🚫 What cannot be restored Search Atlas cannot restore data that Google Analytics no longer provides through its retention settings or API query limits. Missing historical data cannot be reconstructed after it has expired from the GA4 property. πŸ’¬ 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ”§ Fix Report Builder Conversion and Cost Data Mismatches

Why Does This Happen? Discrepancies between your Google Ads or Meta Ads data and the totals shown in Search Atlas Report Builder are a known issue. This article explains what is happening and what information to have ready when you contact support so our team can investigate and resolve the mismatch for your account. Common Causes of Mismatched Data - Attribution window differences: Google Ads and Meta Ads apply their own default attribution windows. If your Report Builder date range does not align with the same window, conversion counts may differ. - Campaign-level vs. account-level aggregation: Conversions recorded at the account or ad-set level may not roll up to the campaign level in Report Builder, causing campaign rows to show lower or zero conversion figures. - Ads account connection state: If the Google Ads or Meta Ads integration was recently set up, had permissions changed, or encountered a sync error, data may be missing or incomplete until the issue is resolved on the backend. - Meta Ads conversions not appearing: If conversions exist inside Meta Ads but do not appear in Report Builder, this is a known data-pull issue that requires backend investigation. What to Have Ready When You Escalate Because this is a backend data issue, our team will need to investigate your specific account and report configuration. Before reaching out, please gather the following: - The exact name of the affected report or project in Search Atlas - The date range you are using in the report - Which platform is showing the discrepancy (Google Ads, Meta Ads, or both) - The specific metric that does not match (e.g. conversions, cost, cost-per-conversion) - A screenshot or note of the value shown in Report Builder versus the value shown in the ad platform - Approximately when you first noticed the discrepancy Having this information ready will allow our team to identify the source of the mismatch and apply the correct fix on the backend as quickly as possible. 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.

Last updated on Oct 26, 2026

πŸ› Report Builder and GSC Bug Fixes

This release resolves three bugs affecting Report Builder and Google Search Console, restoring correct behavior for local SEO heatmaps, layout saving, and the Manage Sites country selector. ✨ What's New Three fixes were shipped in this update: - GSC Manage Sites β€” Country Selector Fix: The country selector dropdown in the Manage Sites panel was opening off-screen and displaying invisible search text due to leftover Ant Design (antd) CSS classes conflicting with Shadcn UI components. The dropdown now renders in the correct position with fully visible text. - Classic Report Builder β€” Local SEO Heatmaps Now Visible: A reversed logic error in the Hide Empty Sections toggle was incorrectly hiding populated Local SEO Heatmap sections while leaving empty ones visible. The logic has been corrected so that only genuinely empty sections are hidden when the toggle is enabled. - Report Builder β€” Layout Save Now Works Correctly: Saving an existing layout was incorrectly triggering a duplicate name error instead of completing successfully. Updating an existing layout now saves without error. πŸ› οΈ How to Use It 1. Navigate to Google Search Console and open Manage Sites to confirm the country selector dropdown opens in the correct position and search text is fully visible. 2. Open a Classic Report Builder report and enable the Hide Empty Sections toggle to confirm that populated Local SEO Heatmap sections remain visible. 3. In Reports , open an existing layout and click Save to confirm the action completes successfully without a duplicate name error. πŸ“‹ What to Expect All three fixes address incorrect behavior introduced by prior changes. No configuration updates or workflow changes are required β€” corrections are applied automatically. If you previously encountered any of these issues, they should now be fully resolved. 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.

Last updated on Oct 26, 2026

πŸ” Fix Wrong Domain Data in Brand Insights

🧭 Overview If you notice that the Brand Insights section in Site Explorer is displaying LLM visibility or sentiment data for a different domain than the one you intended to analyse, this is a known issue that our team is aware of. This article explains what to expect and how to escalate effectively so our team can investigate your specific case. ⚠️ What Is Happening In some cases, Brand Insights β€” including LLM visibility and sentiment analysis β€” may pull and display data that does not match the domain you searched for in Site Explorer. This means the company names, mentions, or sentiment scores shown may belong to a different domain entirely rather than your intended site. Common signs that you may be affected: - The Brand Insights section shows company names, mentions, or sentiment that do not match the site you searched for. - Sentiment or LLM visibility data appears to belong to a completely different domain. - The issue persists across multiple sessions or page loads. πŸ› οΈ How to Escalate Because this is a backend data issue, our support team will need to investigate on your behalf. To help us resolve this as quickly as possible, please have the following information ready when you contact us: - The exact domain you searched for (e.g. the full URL as you entered it into Site Explorer). - The domain whose data is being incorrectly shown in Brand Insights, if you can identify it. - Screenshots of the Brand Insights section showing the incorrect data. - The date and approximate time when you first noticed the issue. - Your project or workspace name in Search Atlas. Please do not create a new project for the same domain as a workaround, as this may complicate the investigation. 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.

Last updated on Oct 26, 2026

πŸ“Š Fix a Blank Portfolio Summary

πŸ“‹ What the portfolio summary shows The portfolio summary in Report Builder provides an overview of reports and project data. It may appear blank while information is loading, when no eligible project data is available, or if the summary has not refreshed correctly. πŸ”„ Refresh the report data 1. Open Reports from the left sidebar. 2. Select your report (Executive Summary). 3. Select Refresh Summary. 4. Wait for the refresh to finish, then reopen the portfolio summary. Some summaries can take several seconds to load. Keep the page open during this process and avoid refreshing repeatedly. βœ… Check your report and project data - Confirm that the correct projects are included in the report. - Check that the selected date range contains data. - Review any filters that could exclude projects or reports. - Open All Reports to confirm that reports are available. If the summary shows zero reports while a report list contains reports, the summary may be temporarily out of sync. Refresh the data and check again after a short wait. πŸ› οΈ If the summary remains blank 1. Navigate away from Reports, then return to Reports and select your report (Executive Summary). 2. Use Refresh Summary again. 3. Verify that your projects and reports still appear under All Reports. 4. Record the affected portfolio, project names, date range, and approximate time of the issue. If the report list also fails to load after these steps, the issue may be temporary or account-specific. 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.

Last updated on Oct 26, 2026

πŸ› οΈ Remove Invitation Required From Widget

πŸ” Why visitors see β€œInvitation required” The embedded Site Analysis Lead Capture Widget is designed for public visitors. Visitors should not need an invitation or a Search Atlas login to use it. If an unauthenticated visitor sees β€œInvitation required,” your widget is affected by a known guest-access issue tracked as WL-476. This issue is currently marked In Release, so the fix may not yet be available in your environment. βš™οΈ Can I turn off the invitation requirement? No. There is currently no widget setting or embed-code option that removes this prompt. The invitation requirement is caused by the known guest-access issue, not by an incorrect iframe configuration. βœ… Check your embedded widget 1. Open your website in a private or incognito browser window. 2. Confirm that you are signed out of Search Atlas. 3. Load the page containing the embedded widget. 4. Test the widget as a public visitor. If the widget works while you are signed in but shows β€œInvitation required” when signed out, this confirms the guest-access issue. πŸš€ What you can do now - Keep the current embed in place while the fix is being released. - Test the widget periodically in a private browser window. - Avoid asking visitors to create a Search Atlas account or request an invitation; that is not the intended experience. - If the issue continues after the fix reaches your environment, contact the team through the platform chat. πŸ’¬ 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ”§ Fix PDF Download Stuck in Report Builder

What Is This Issue? When using the classic (old version) Report Builder, some users see the message "Generating PDF… This may take up to a minute" but the download never starts. The file does not appear, even after waiting several minutes. What Caused the Problem? This issue is caused by an internal error in the PDF export process within the classic Report Builder. It is not related to your browser, internet connection, or report content, and requires investigation and action by the Search Atlas support or engineering team to resolve. How to Get Help Because this is a backend issue, the most effective next step is to contact the Search Atlas support team directly. To help the team investigate as quickly as possible, please have the following information ready before reaching out: - The exact report name β€” the name of the report you were trying to export as a PDF. - A description of what you observed β€” for example: "The PDF generation appears to start (the 'Generating PDF…' message appeared) but the file never downloaded, even after several minutes." - When the issue occurred β€” the date and approximate time, including your time zone. The support team will investigate the PDF export failure on the backend for your specific report and work with engineering if needed to resolve it. Contact Support If you're experiencing this issue, please reach out via the chat widget β€” we're happy to help. If you need further assistance, please don't hesitate to contact us through the chat widget so the team can investigate the PDF export failure for your specific report.

Last updated on Oct 26, 2026

πŸ“Š Fix Missing Historical Metrics in Site Metrics

Why Historical Metrics May Not Display The Site Metrics tab displays historical traffic and performance data for the domains you analyze. Sometimes this data may not appear, appear incomplete, or show stale information. This can happen for several reasons, including temporary data processing delays, browser caching issues, or a broader system issue. Troubleshooting Steps - Hard refresh your browser: Perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear any cached data that may be preventing updated metrics from displaying. - Check the date range: Make sure the date range selected covers the period where you expect to see data. A narrow or custom range can hide months that are actually available. - Allow time for processing: Data processing delays can cause temporary gaps in historical metrics. If the issue appeared recently, check back after some time has passed. When to Contact Support If historical metrics are still not displaying across one or more domains after trying the steps above, there may be a broader issue affecting data availability. To help us investigate quickly, please have the following information ready: - The affected domain(s) - Which specific metrics are missing or incomplete (e.g., organic traffic, paid traffic, keywords, backlinks) - The date range where data appears incomplete or missing - When you first noticed the issue 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.

Last updated on Oct 26, 2026

πŸ” Fix Blank GSC Data in Report Builder

πŸ“Œ Overview Sometimes Google Search Console (GSC) shows as connected in Search Atlas, but the report widgets are empty. This usually means the report is asking for data that doesn't match what GSC has for your site. The most common cause is a location mismatch. A mismatched date range can make it worse. This article explains why it happens and how to fix it in a few minutes. πŸ‘€ What You May See - GSC shows a connected status, but charts and tables in Report Builder are blank or show zeros. - The date range on one side of the report says Last 30 days and the other side says Last 90 days. - Other data sources in the same report load normally. ❓ Why This Happens Report Builder pulls GSC data for the site, date range, and location selected in your report. If any of these don't line up with the data GSC holds, the widget has nothing to show. Common reasons include: - Location mismatch: The report location (country or region) differs from where your site gets its search impressions and clicks. For example, the report is set to one country, but your traffic comes mainly from another. GSC then returns no rows for the selected location. - Different date ranges: When one part of the report uses 30 days and another uses 90 days, the comparison can look empty or inconsistent, especially if one range has little data. - Wrong property: The connected GSC property (for example, the domain property versus a URL-prefix property) differs from the site in your report. - Recently connected or low-traffic sites: GSC data can take a few days to appear, and sites with very little search traffic may have no data for a narrow filter. πŸ› οΈ How to Fix It Follow these steps in order. Most customers find the issue in the first three. 1. Open your report in Report Builder and find the location setting for the report or the GSC widget. 2. Check the location. Make sure it matches the country or region where your site gets most of its search traffic. If you're unsure, set it to a broader option, such as all locations, if one is available. 3. Align the date ranges. Set both sides of the report to the same range, such as Last 90 days, so you're comparing like with like. If the report still looks empty, try a longer range to confirm that data exists. 4. Confirm the GSC property. Go to your integrations or connections settings and check that the connected GSC property matches the website in your report. If it doesn't, reconnect with the correct property. 5. Refresh the report. Save your changes and reload the page. Widgets can take a moment to repopulate. πŸ“… Check the Date Range The date range doesn't usually cause blank data by itself, but it can hide the real problem. A few tips: - GSC data is typically delayed by about 2 to 3 days. Don't expect today's or yesterday's numbers. - If you recently connected GSC, historical data may take time to appear. Try a shorter range that ends a few days ago. - Use the same range on both sides of any comparison so one side doesn't look empty by contrast. βœ… Verify the Data in Google Search Console If the report is still blank, check that GSC itself has data for your settings: 1. Sign in to Google Search Console and select the same property you connected to Search Atlas. 2. Open the Performance report and set the same date range. 3. Add a country filter that matches your report location. 4. If GSC shows no data, the report is behaving correctly. Change the location or date range in Report Builder to match where your data exists. 5. If GSC shows data but Search Atlas doesn't, disconnect and reconnect GSC, then reload the report. πŸ’‘ Tips to Prevent This - Set the report location to match your main audience when you create a report. - Use the same date range across all widgets in a report. - Make sure the GSC property you connect matches the exact site in your project. - Check your property permissions in GSC. The connected Google account needs access to the property. - After connecting GSC for the first time, wait a few days for the data to fully appear. πŸ’¬ Still Seeing Blank Data? If you've matched the location, aligned the date ranges, and confirmed the GSC property, but the report is still empty, our team can take a closer look. When you contact us, it helps to share your project name, the report name, and the location and date range you're using. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ“Š Fix Missing Google Reviews and Citations in Reports

πŸ” Overview If the reviews or citations section of a client report is empty, or shows fewer results than you expect, the report itself is usually fine. In most cases the data source behind that section is not fully connected, has not finished syncing, or is outside the report's date range. This article explains the most common causes and how to fix each one. ❓ Why Reviews and Citations Can Be Missing Reports only show data the platform has already collected for that business. These are the most common reasons a section looks empty: - Google Business Profile is not connected. Google reviews come from the business's Google Business Profile. Without an active connection, there are no reviews to display. - The connection has expired. Permissions can lapse if the Google account password changes, access is removed, or the connection is not renewed. - The wrong location is selected. If the business has several locations, the report may be linked to a different one or to none. - Data is still syncing. A newly added business or newly connected profile can take some time before reviews and citations appear. - The date range is too narrow. If no new reviews or citation changes happened in the selected period, the section may look empty. - The section is turned off in the report. Some report layouts let you show or hide sections, so reviews or citations may not be included. - Business details do not match. Citations are tied to the business name, address, and phone number. If these are missing or incomplete, citation data may not load. - No citation data exists yet. If no citation scan or setup has been done for the business, there is nothing to report. πŸ› οΈ Step-by-Step: Fix Missing Google Reviews 1. Open the project or business for the affected client. 2. Go to the Google Business Profile or local settings area and check that the profile is connected. 3. If the connection shows as disconnected or expired, reconnect it using a Google account that has access to the profile. Owner or manager access works best. 4. Confirm that the correct business location is selected, especially for multi-location clients. 5. Wait for the data to sync. This can take some time after a new connection. 6. Return to the client report and refresh or regenerate it. 7. Check that the date range covers a period when the business actually received reviews. πŸ“ Step-by-Step: Fix Missing Citations 1. Open the business details and confirm the business name, address, and phone number are complete and accurate. 2. Check that citation tracking or a citation scan has been set up for the business. 3. If a scan has not run yet, start one and allow time for it to finish. 4. Make sure the report includes the citations section and that it is not hidden in the report settings. 5. Refresh or regenerate the report once the data has loaded. βš™οΈ Check Your Report Settings If the connection and data look correct but the report is still blank, review the report itself: - Confirm that the reviews and citations sections are enabled in the report layout. - Make sure you are not viewing an older, saved version of the report. Generate a fresh one to pull in the latest data. - Check the date range and comparison period. A very short range can produce empty sections. - If you share reports with clients through a link or a scheduled delivery, regenerate the report and send it again so the client sees the updated version. πŸ’‘ Tips to Prevent This in the Future - Connect the Google Business Profile as soon as you add a new client. - Use a shared business account for the connection, rather than a personal one, so access does not lapse if someone leaves. - Complete the business name, address, and phone number at setup. - Check the connection status before sending monthly reports. - Allow time for new data to sync before generating a client's first report. 🧭 Still Not Showing? If you have worked through the steps above and reviews or citations are still missing, gather a few details so we can help faster: - The business or project name - Whether the Google Business Profile shows as connected - The date range of the report - Which section is missing: reviews, citations, or both If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

πŸ› οΈ Platform Fixes for Maps, Reports, and More

We fixed several issues that were getting in the way of everyday work in Topical Maps, Report Builder, Google Search Console, and Rank Tracker. These fixes help these areas of the platform load and behave the way you expect. ✨ What's New Here is what was affecting you and what is different now: - Topical Maps: Regenerating a topical map could freeze the page and leave you with a blank screen. Regenerating now completes without the page locking up. - Report Builder watchlists: The watchlist filter was visible, but there was no star or bookmark icon to add items to your watchlist or remove them. The icon is now available, so you can build and manage your watchlist directly. - Google Search Console: Some core pages briefly showed a "Connect Google Search Console (Required)" message on a fresh load, even when your account was already connected. This false prompt no longer appears. - Rank Tracker: The project creation wizard could block you from creating a Target Page project if that target page was already being tracked for the same location and language. The wizard no longer stops you in this situation. πŸ“‹ What to Expect - No action is needed on your part. These improvements apply automatically. - If a page still looks stuck or blank, refresh your browser and try again. - If you still see a Google Search Console connection prompt, check that your account is connected in your integration settings. - Your existing topical maps, watchlists, Search Console connections, and Rank Tracker projects are not affected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026