Support: Platform Bugs & Performance

🛠️ Fix Template Picker Hidden Behind Popup

🔍 Overview Some customers encounter an issue where the template picker is hidden behind a popup, making it unavailable or unclickable. ⚠️ What You Might Experience - The template picker is hidden behind a popup. - You cannot view or select a template. - Clicks on the picker do not respond as expected. 🛠️ What to Do This is a bug involving the template picker and a popup overlay. If you experience this issue, contact support for 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.

🔓 Fix Disabled Continue Button on Signup

This article covers an issue where the Continue button on a signup link is disabled. The available resolution information does not identify a confirmed cause or fix, so avoid assuming that a particular field, browser setting, or link condition is responsible. 🔍 Check the Issue 1. Open the signup link and confirm that the Continue button remains disabled. 2. Record the signup link, the exact behavior you see, and any error message displayed on the page. 3. Note the time the issue occurred and the browser and device you used. 🛠️ Next Steps 1. Because no confirmed self-service fix is available for this issue, do not rely on an unverified cause or workaround. 2. Contact support with the signup link, exact error or button behavior, timestamp, browser, device, and any relevant screenshots so the signup flow can be investigated. ✅ How to Confirm It Worked The issue is resolved when the Continue button becomes available and the signup flow advances to the next step. If it remains disabled, provide the recorded details when contacting support for further 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.

🔍 Fix Lead Capture Widget Invitation-Only Access Issue

🧭 Overview If your lead capture widget shows an Invitation Required page, the available source information does not confirm a specific configuration issue or documented fix. Use the checks below to capture the details needed for troubleshooting. ✅ What to Check 1. Open the widget as a new visitor in a private or incognito browser window. 2. Record the exact page URL and the complete message shown, including whether it says Invitation Required. 3. Note the website where the widget appears and the approximate date and time when the issue occurred. 4. Compare the result in the private window with the result for an account that has access, if available. 5. Provide these details when requesting assistance so the team can investigate the widget access issue. If the issue continues, do not assume that changing the widget or domain settings will resolve it, because no confirmed resolution steps are available in the source information. 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.

🛠️ Publication Queue Removal Bug Explained

🔍 What Is This Issue? A system bug caused some posts to be removed from the publication queue even after they had been successfully published on time. This affected customers who completed their posts within the required window but were incorrectly flagged, triggering an automated removal from the queue. If this happened to you, your post was published — the removal was a system error, not a reflection of your performance or eligibility for payment. ⚙️ Why Did This Happen? Our publication queue system uses an automated pipeline to track post status and timing. A bug in this pipeline caused the system to incorrectly remove some posts from the queue even though they had been successfully published on time. Our engineering team identified the issue and worked to resolve it. ✅ What Has Been Fixed? Our team has investigated and resolved the underlying system bug responsible for the incorrect queue removals. Affected posts were reviewed and corrected on the backend. 📋 What Should You Do If This Affected You? If your post was published on time but was removed from the queue, follow these steps: 1. Confirm your post is live by visiting the published URL or checking your connected platform (e.g., Google Business Profile). 2. Take a screenshot or note the published date and time as evidence. 3. Have your project name, the affected post details, and any relevant timestamps ready when you reach out so our team can review and correct your queue status promptly. 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.

🛠️ Fix Competitor Page Display Issues

🔍 What this article covers Search Atlas comparison pages, including Search Atlas vs Ahrefs, Semrush, Surfer SEO, and all SEO tools, are public webpages. If a page appears to have broken CSS, missing styling, or an unusual layout, the issue is usually related to cached files, browser extensions, or a temporary website asset problem. 🧹 Try these quick fixes 1. Refresh the page using a hard refresh: Ctrl + Shift + R on Windows or Command + Shift + R on macOS. 2. Open the page in a private or incognito window. 3. Try a different browser or device. 4. Disable ad blockers, privacy tools, translation tools, and other browser extensions temporarily. 5. Clear cached images and files for searchatlas.com, then reload the page. 6. Check whether the issue affects one comparison page or several. 📄 Comparison pages to check - Search Atlas vs Ahrefs - Search Atlas vs Semrush - Search Atlas vs Surfer SEO - Search Atlas vs All SEO Tools Use the page address shown in your browser when reporting a problem. This helps the team identify the affected template or page asset. 📝 What to include in a report If the issue continues after the steps above, collect the following details: - The full page URL - A screenshot or short screen recording - Your browser and operating system - Whether the issue occurs in a private window or another browser - The approximate date and time you noticed the issue - Any visible error message or missing page element ⚙️ Using Search Atlas while the page is unavailable A display issue on a public comparison page does not necessarily affect the Search Atlas platform. You can continue using the platform through the left sidebar, including Site Metrics for Site Explorer, Keyword Magic, Rank Tracker, and Keyword Gap, or Local for local SEO projects and related tools. 💬 Get help from our team If the layout remains broken after troubleshooting, share the details through the platform so the issue can be reviewed. 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.

🛠️ Fix Website 404 Errors and Network Issues

🔍 What This Article Covers If your website is displaying only the home page correctly while other pages return 404 errors or show an ERR_NETWORK_CHANGED message in your browser, this guide will help you identify the cause and resolve it — without unnecessarily removing your OTTO SEO HTML sections. ⚠️ Understanding the Symptoms Before making any changes to your site, it is important to understand what these errors mean: - 404 errors on internal pages: The server cannot find the requested page. This is usually a server, hosting, or URL configuration issue — not a Search Atlas or OTTO SEO problem. - ERR_NETWORK_CHANGED: Your local network connection changed while the browser was loading the page. This is a client-side network issue (on your device or internet connection) and is not caused by your website's content or OTTO HTML sections. 💡 Should You Remove Your OTTO HTML Sections? No. OTTO SEO HTML sections are installed in your page content and do not affect your server routing, URL structure, or network connectivity. Removing them will not fix 404 errors or ERR_NETWORK_CHANGED messages, and doing so unnecessarily will undo your SEO optimisations. Leave your OTTO HTML sections in place while you follow the troubleshooting steps below. 🛠️ Step-by-Step Troubleshooting 1. Test your network connection first. Open a different website in a new browser tab to confirm your internet connection is stable. If other sites also fail to load or behave inconsistently, the issue is with your local network — try restarting your router or switching to a different network. 2. Clear your browser cache and cookies. A stale cache can cause pages to return incorrect 404 responses. In your browser settings, clear cached images, files, and cookies, then reload the affected pages. 3. Test in a private or incognito window. Open an incognito or private browsing window and navigate directly to the pages showing 404 errors. This rules out browser extensions or cached data as the cause. 4. Try a different browser or device. If the pages load correctly in another browser or on a different device, the problem is specific to your original browser's configuration. 5. Check your website's URL structure and redirects. Log in to your hosting control panel and verify that all page URLs are correctly configured. Look for broken redirects, recently changed permalink settings, or misconfigured .htaccess rules (for WordPress sites). 6. Check for recent hosting or DNS changes. If your domain's DNS records or hosting server settings were recently changed, propagation can take up to 48 hours and may cause intermittent 404 errors on certain pages. Contact your hosting provider to confirm no configuration changes were made. 7. Review your CMS permalink settings (WordPress users). Go to Settings → Permalinks in your WordPress dashboard and click Save Changes without modifying anything. This refreshes your rewrite rules and often resolves sudden 404 errors on internal pages. 8. Verify pages exist in your CMS or Website Studio. In Search Atlas, navigate to Website Studio (left sidebar → Website Studio) and confirm that all affected pages are published and have the correct URLs assigned. Unpublished or draft pages will return 404 errors for visitors. ✅ After Troubleshooting Once your pages are loading correctly, verify that your OTTO SEO HTML sections are still present and intact. If any sections appear to be missing after cache clearing or CMS changes, you can re-apply them from within the OTTO SEO workflow. Your SEO settings and configurations are saved in Search Atlas and are not lost during network or server-side issues. 🚫 Common Mistakes to Avoid - Do not remove OTTO HTML sections as a first troubleshooting step — they are not the cause of 404 or network errors. - Do not change your URL structure or permalink settings unless you understand the impact on existing indexed pages. - Do not assume a 404 error is permanent — intermittent 404s during network changes or DNS propagation are temporary and will resolve on their own. 💬 Still Need Help? If you have followed all the steps above and are still experiencing 404 errors or connectivity issues, 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.

🛠️ Errors by Service & How to Fix Them

When a Search Atlas feature stops working, shows missing or delayed data, or appears stuck, the cause almost always traces to one specific service layer. Find your symptom below — each entry states the cause and the fastest path to resolution. 🔧 Linkgraph (Core API) 🔴 OTTO Metrics Not Updating Cause: Missing or broken background task (Celery — Search Atlas's asynchronous task processor). 1. Re-run the scan: in OTTO SEO → All Sites (SEO Automation), find the site's row and click Scan. 2. Trigger a manual recalculation: click Recalculate in the OTTO Overview panel, or go to OTTO → Settings → Recalculate Metrics. 3. If the issue persists after clicking Recalculate, wait 15–30 minutes for background tasks to complete, then refresh the page. 🔴 OTTO — AI Content Generation Stuck (Permanent Spinner) Cause: Celery worker crash left the generation flag uncleared (OTTO-1496, now resolved). The ai_gen_in_progress flag previously stayed set after a mid-generation crash, blocking new generations. Because the fix adds an automatic TTL and cleanup task, most users will never see this spinner again. If you encounter a stuck spinner on an older generation job, use the navigate-away step below as a one-time reset while the cleanup task catches up. - Navigate away from the OTTO content generation page (for example, go to the OTTO Overview tab), then return to the content generation view. This forces the UI to re-evaluate the generation status flag. - Re-trigger AI content generation. - If the spinner remains after navigating back, wait 15–30 minutes for the TTL-based cleanup task to clear the flag automatically, then refresh the page before re-triggering generation. - If the spinner recurs after navigating away and re-triggering, contact support. The underlying bug (stuck ai_gen_in_progress flag) was resolved in OTTO-1496; a recurrence may indicate a new instance of the same pattern. Reference OTTO-1496 so the support agent has context. 🔴 OTTO PPC — Ad Strength Data Stale or Missing Cause: gRPC sync failures in sync_ad_strength_for_account (PPC-1813, now resolved). Ad strength and ad quality scores in OTTO PPC stopped updating for affected accounts starting March 2026. - The backend fix has been deployed — ad strength data should now sync correctly. - Allow up to 24 hours for scores to fully re-populate after the fix. - If ad strength data is still stale or missing after 24 hours, contact support and reference PPC-1813. 🔴 OTTO PPC — Missing Weekly Campaign Performance Data Cause: Boundary condition in the weekly sync task caused campaigns to be skipped (PPC-1781, now resolved). An exact 7-day boundary in the weekly campaign performance sync silently skipped campaigns from the previous run. - New weekly syncs now capture all campaigns correctly. - If you notice gaps in weekly data prior to the fix date, contact support and reference PPC-1781 to request a backfill. 🔴 OTTO via Cloudflare — Special Character Encoding Corruption Cause: Cloudflare script encoding bug that corrupted special characters on customer sites (SPE-666, now resolved). 1. Disengage OTTO on the affected site. 2. Confirm with Search Atlas support that the updated Cloudflare script has been deployed on the Search Atlas side. 3. Reconnect the Cloudflare integration to re-engage OTTO. 🔴 OTTO — Schema Markup Generation or Deploy Failure Cause: The schema markup generator did not run, or browser-cached state is preventing deployment. 1. In the OTTO optimization dashboard, click the purple Generate button before attempting to deploy any suggested schema markup. 2. Clear your browser cache and retry the deploy. 3. If the error persists after these steps, this indicates a system-level generator failure. Open a support ticket with high priority and include the site URL and the schema type you were trying to deploy. 🔴 OTTO — Unwanted Text or Content Appearing on Site After OTTO Engagement Cause: An active deployed OTTO fix (for example, a Heading Length fix) is inserting content into the front-end of the site. 1. Go to OTTO → Deployments. 2. Identify the deployed fix responsible for the unwanted text (such as a Heading Length fix matching the affected element). 3. Undeploy that specific fix to remove the injected content from the site. 🔴 OTTO WordPress Plugin — API Key Could Not Be Verified Cause: The OTTO WordPress plugin requires two separate credentials. This error usually means only one was provided, or the values were entered in the wrong fields. 1. In Search Atlas, go to Settings → API Keys and copy your 32-character SearchAtlas API Key. Paste it into the Search Atlas API Key field in the WordPress plugin (WordPress plugin → Search Atlas → Settings). 2. Provide the second required credential — the OTTO project / site UUID — in its dedicated field in the plugin settings. Refer to the OTTO WordPress plugin setup documentation for the exact field name and where to copy the value from in Search Atlas. 3. Save the plugin settings. If the error persists, contact support with a screenshot of the plugin configuration screen. 🔴 503 / Dashboard Not Loading Cause: General gateway error at the dashboard level (upstream service unavailable or temporary network issue). 1. Refresh after 30–60 seconds. 2. Retry the action. 3. If the error persists beyond 2–3 minutes, check the Search Atlas status page or contact support with a screenshot of the error. 🔴 Tasks Stuck / Never Complete Cause: Queue mismatch or task failure. The stuck-site retry cap was increased in G3.9 — the system now makes more automatic attempts before declaring a final failure, so a task that previously appeared stuck may now self-resolve. 1. Do not re-trigger immediately. Wait at least 10–15 minutes without any manual intervention. 2. Avoid duplicate triggers while retries are in flight. 3. Re-trigger the action only after the task status changes to a final error state. 🔴 Crawl Stuck "In Progress" Cause: Timeout on a large site. 1. Reset the crawl. 2. Re-run the crawl. 3. Reduce crawl scope if the site is large. 🔴 Jobs Stop Mid-Process Cause: Memory limit exceeded (OOM — out of memory). - Retry with a smaller operation. - Avoid running multiple bulk-heavy actions simultaneously. 🔭 Site Explorer 🔴 Site Explorer Data Missing or Delayed (holistic_pillars Tasks) Cause: Database connection exhaustion affecting Site Explorer's holistic_pillars Celery tasks (SE-605, observed during the May 4 spike). Connection pool saturation caused holistic pillars tasks to fail or stall, leading to missing or delayed Site Explorer data. 1. Wait 10–15 minutes for the connection pool to recover and for queued holistic_pillars tasks to retry automatically. 2. Refresh the Site Explorer view to confirm whether the missing data has populated. 3. If data is still missing or delayed after 30 minutes, contact support and reference SE-605 so the team can confirm the task state for your project. 🎯 You now know the cause and fastest fix for the most common Search Atlas service errors. If your issue isn't listed here or persists after following these steps, contact Search Atlas support with your error details and any relevant ticket references from this guide.

📱 Fix Approval Button Hidden on iPhone

🔍 Overview Some iPhone users find that the approval button inside the Search Atlas platform appears below the visible screen area, making it difficult or impossible to tap. This is a known display issue on iOS mobile browsers. The steps below offer general workarounds you can try to access the approval button on your iPhone. 📋 Affected Area - Feature: Tool approval workflow - Affected devices: iPhone (iOS Safari and other mobile browsers) 🛠️ Workarounds to Access the Approval Button Try the following options in order. Most users are able to resolve the issue with one of these approaches. 1. Scroll down on the approval screen. After the approval prompt loads, place your finger on the screen and scroll downward. The button may simply be off-screen and reachable by scrolling. 2. Rotate your iPhone to landscape mode. Turn your device sideways to switch to landscape orientation. The wider view often brings hidden UI elements into the visible area. 3. Zoom out in your browser. Reduce the zoom level in your browser settings and reload the page, then try tapping the approval button again. 4. Request the desktop site. Most iOS browsers offer an option to load the full desktop version of a website. Enabling this forces the full desktop layout, which may position the button correctly. 5. Use a different browser. If your current browser is not working, try an alternative iOS browser. Navigate to app.searchatlas.com, log in, and retry the approval step. 6. Switch to a desktop or laptop. If none of the above options work, completing the approval action from a desktop browser is the most reliable alternative. ⚙️ Current Status This is a known usability issue on iPhone devices. No action is needed on your end beyond the workarounds above. 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.

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

🔍 Fix the 'No Website Found' Error

🧭 Overview When you try to add a website to Search Atlas and see a no website found error, it usually means Search Atlas cannot discover or verify the domain. This can happen for several reasons, from how the URL is entered to deeper issues with the domain's DNS, indexing status, or account configuration. This article walks you through a structured diagnostic process so you can identify and fix the root cause quickly. ⚠️ Common Causes of This Error - The URL is entered in an unsupported or incorrect format - The domain is not indexed by search engines - The domain has DNS configuration issues or does not resolve correctly - The website is behind a login wall, firewall, or robots.txt block - The subdomain is not recognised as a standalone trackable property - An account-level restriction is preventing site discovery ✅ Step 1: Check Your URL Format Search Atlas requires a specific URL format when adding a website. Before investigating deeper issues, confirm you are entering the URL correctly. 1. Use only the root domain or subdomain without a trailing slash. For example, enter bloomington.alloypersonaltraining.com rather than https://bloomington.alloypersonaltraining.com/. 2. Try removing the https:// or http:// prefix if you have included it. 3. If the site uses www, try both the www and non-www versions to see which is accepted. 4. If you are adding a subdomain, enter the full subdomain exactly as it appears in the browser address bar. 🌐 Step 2: Verify the Domain Resolves Publicly Search Atlas must be able to reach the domain over the public internet. If the domain does not resolve, no URL format will work. 1. Open a private or incognito browser window and navigate to the full URL of the website. 2. Confirm the site loads without redirects to an error page, login screen, or maintenance notice. 3. Use a free DNS lookup tool such as dnschecker.org and enter the domain. Check that DNS records (A record or CNAME) are present and propagated globally. 4. If the domain does not load publicly or DNS records are missing, the domain must be correctly configured before it can be added to Search Atlas. Contact your domain registrar or hosting provider to resolve DNS issues. 🔎 Step 3: Check Search Engine Indexability Search Atlas relies on search engine data to verify and populate website information. If the domain is not indexed, it cannot be discovered. 1. Open Google and search for site:bloomington.alloypersonaltraining.com (replace with your domain). 2. If no results appear, the domain may not be indexed by Google. This is a common cause of the no website found error. 3. Check the site's robots.txt file by navigating to yourdomain.com/robots.txt. If it contains Disallow: / or blocks all crawlers, search engines and Search Atlas cannot access the site. 4. If the domain is a newly registered or recently launched website, it may simply not have been crawled yet. Allow time for indexing and try adding it again after a few days. 🔒 Step 4: Check for Access Restrictions Some websites restrict access in ways that prevent Search Atlas from discovering them. - Password protection: If the site requires a login to access any pages, Search Atlas cannot verify it. Temporarily remove password protection and retry. - Firewall or IP blocking: Some hosting environments block bot traffic. Confirm that the site is accessible to crawlers by checking your hosting or CDN settings. - Cloudflare or security layers: If the domain is protected by Cloudflare or a similar service, bot challenges may block discovery. Review your security settings to allow legitimate crawlers. 🏷️ Step 5: Confirm Subdomain Handling Subdomains like bloomington.alloypersonaltraining.com are treated as separate properties from the root domain. If you are trying to track a subdomain, keep the following in mind. - Enter the full subdomain exactly as it appears, for example bloomington.alloypersonaltraining.com, not just alloypersonaltraining.com. - The subdomain must independently resolve and be publicly accessible. A subdomain that redirects to the root domain or returns a 404 error cannot be added. - Confirm the subdomain has its own content and is not simply an alias or redirect. 🛠️ Step 6: Try Adding the Website Again After working through the checks above, attempt to add the website to Search Atlas again. 1. Log in to Search Atlas and go to the Home page. 2. Select Create Project to start a new project or attempt to add a website to an existing project. 3. Enter the domain in the correct format based on what you confirmed in Step 1. 4. If the error persists after completing all checks above, take note of the exact domain you entered and the steps you have already tried. 💬 Still Seeing the Error? If you have completed all the steps above and the no website found error continues to appear, the issue may be related to an account-level restriction or a backend configuration that requires investigation 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.

🔧 Troubleshooting a Disabled Continue Button

This article helps you resolve situations where the Continue button is greyed out, unclickable, or a provided link does not let you move forward. There are several common reasons this happens, and the steps below will help you pinpoint and fix the exact cause. 🔍 Common Causes - A required field on the current page is empty or contains invalid input. - The link you received has expired or was already used. - Your account does not yet meet a prerequisite (such as completing an earlier step or verifying your email). - A browser extension or cached session is interfering with the page. 🛠️ Step-by-Step 1. Check for unfilled or invalid fields. Scroll through the entire page and look for any fields highlighted in red, marked with an error message, or left blank. Fill in or correct each one before trying again. 2. Verify the link is still valid. Links sent by email or shared for onboarding steps often expire after a set period. If you received the link more than 24–48 hours ago, request a new one through the platform or contact support using the chat widget. 3. Confirm any prerequisite steps are complete. Some steps unlock only after an earlier action is finished — for example, confirming your email address or completing an onboarding stage. Return to the beginning of the flow and check that all prior steps show a completed status. 4. Clear your browser cache and cookies. In your browser settings, clear cached data and cookies, then reload the page and try the link again. Alternatively, try opening the link in a private or incognito window. 5. Disable browser extensions. Ad blockers, script blockers, and other extensions can prevent buttons from activating. Temporarily disable them and reload the page. 6. Try a different browser. If the issue persists, open the link in a different supported browser (such as Chrome or Firefox) to rule out a browser-specific problem. ✅ How to Confirm It Worked You will know the issue is resolved when the Continue button becomes fully clickable (no longer greyed out) and pressing it advances you to the next step or page without an error. If the button was part of an emailed link, successful resolution means the destination page loads completely and you can interact with its content. If you are still on the same page after clicking, scroll up to check for any new error messages that appeared after your attempt. 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 Perform a hard refresh (Ctrl+Shift+R on Windows / Cmd+Shift+R on Mac) to clear cached state, then revisit the page from the start of the flow. Also: if you arrived via a shared/direct link, navigate to that section through the main menu instead, as skipping earlier steps can leave required state unfulfilled.

🔄 Clear Your Cache to Fix Technical Issues

🤔 Why Clearing Your Cache Helps Your browser stores copies of websites — images, scripts, and page data — in a temporary storage area called a cache. This speeds up loading times, but it can also cause problems. If your cached data is outdated or corrupted, you may experience issues such as: - Pages not loading correctly or appearing broken - Features not responding or behaving unexpectedly - Changes you made not showing up on screen - Buttons, menus, or dashboards appearing blank or misaligned - Login or session errors Clearing your cache forces the browser to download a fresh version of the page, which resolves most of these issues quickly. 🕐 When to Clear Your Cache First Before reporting a bug or contacting support, always try clearing your cache if you notice: - A feature that was working has suddenly stopped - The platform looks different from what is described in the documentation - You recently updated your account settings but the old data is still showing - You are seeing an error message after a platform update Cache clearing takes less than a minute and resolves the majority of technical issues without any further steps needed. 🌐 How to Clear Cache in Google Chrome 1. Open Chrome and click the three-dot menu in the top-right corner. 2. Select Settings. 3. Click Privacy and security in the left sidebar. 4. Select Clear browsing data. 5. Set the time range to All time. 6. Check Cached images and files. You may also check Cookies and other site data if the issue persists. 7. Click Clear data. 8. Reload the Search Atlas platform and log back in if prompted. 🦊 How to Clear Cache in Mozilla Firefox 1. Open Firefox and click the three-line menu in the top-right corner. 2. Select Settings. 3. Click Privacy & Security in the left panel. 4. Scroll to the Cookies and Site Data section and click Clear Data. 5. Check Cached Web Content and click Clear. 6. Reload the Search Atlas platform. 🧭 How to Clear Cache in Safari (Mac) 1. Open Safari and click Safari in the top menu bar. 2. Select Settings (or Preferences on older versions). 3. Click the Advanced tab. 4. Check Show Develop menu in menu bar. 5. Click Develop in the top menu bar. 6. Select Empty Caches. 7. Reload the Search Atlas platform. 🌊 How to Clear Cache in Microsoft Edge 1. Open Edge and click the three-dot menu in the top-right corner. 2. Select Settings. 3. Click Privacy, search, and services. 4. Under Clear browsing data, click Choose what to clear. 5. Set the time range to All time. 6. Check Cached images and files and click Clear now. 7. Reload the Search Atlas platform. ⚡ Quick Fix: Hard Refresh If you do not want to clear your full cache, a hard refresh bypasses the cache for a single page load. This is the fastest first step to try: - Windows / Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R A hard refresh reloads the current page while ignoring any stored cache, without affecting your other browsing data. ✅ After Clearing Your Cache Once you have cleared your cache, follow these steps to confirm the issue is resolved: 1. Close and reopen your browser. 2. Navigate back to Search Atlas and log in. 3. Return to the page or feature that was causing the issue. 4. Test the feature again to confirm it is working correctly. If the problem continues after clearing your cache and performing a hard refresh, the issue may be related to your account, a platform configuration, or a temporary service disruption. 💬 Still Experiencing Issues? If clearing your cache did not resolve the problem, our team is ready 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.

🛠️ Fix Persistent Issues in Search Atlas

🔍 Overview If you are experiencing a persistent issue in Search Atlas — something that keeps coming back no matter what you try — this guide will walk you through the most effective troubleshooting steps. Following these steps in order resolves the majority of recurring technical problems without needing to contact support. ⚙️ Step 1: Perform a Hard Refresh Cached browser data is one of the most common causes of persistent platform issues. A hard refresh forces your browser to reload all files fresh from the server. - Windows / Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R After the refresh, check whether the issue still occurs before moving to the next step. 🧹 Step 2: Clear Browser Cache and Cookies If a hard refresh does not help, clearing your full browser cache and cookies will remove any corrupted or outdated stored data that may be interfering with the platform. 1. Open your browser settings. 2. Navigate to Privacy and Security (or equivalent). 3. Select Clear browsing data. 4. Check Cached images and files and Cookies and other site data. 5. Set the time range to All time. 6. Click Clear data, then reload Search Atlas. 🌐 Step 3: Try a Different Browser or Incognito Mode Browser extensions, settings, or profiles can sometimes conflict with platform functionality. Testing in a clean environment quickly confirms whether your browser is the source of the problem. - Open a private or incognito window in your current browser and log in to Search Atlas. - Alternatively, try a different browser entirely (for example, switch from Chrome to Firefox or Edge). If the issue disappears in a clean environment, a browser extension is likely the cause. Try disabling extensions one at a time to identify the culprit. 🔌 Step 4: Check Your Internet Connection An unstable or slow connection can cause features to load incorrectly, time out, or behave unpredictably in ways that appear to be platform bugs. - Run a speed test at a site like fast.com to confirm your connection is stable. - If you are on Wi-Fi, try switching to a wired connection. - Restart your router if speeds are unusually low. 🚀 Step 5: Identify the Specific Feature or Page Narrowing down exactly where the issue occurs makes it much faster to resolve — both on your own and with our support team. Before escalating, try to note the following: - Which feature or tool is affected (for example, a specific tool or page within Search Atlas). - What action triggers the problem (clicking a button, loading a page, saving a setting). - How often it occurs and whether it happens consistently or intermittently. - Any error messages displayed — copy the exact wording if possible. - Your browser name and version, and whether you have already tried the steps above. Having this information ready will significantly speed up resolution if you need to contact support. 📞 Still Experiencing the Issue? If the steps above have not resolved your problem, our support team can investigate further. Please have the following ready when you reach out: the feature or page affected, the exact error message (if any), the steps you have already tried, and the browser and device you are using. 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.

⚡ Fix Search Atlas Buffering and Loading Issues

🔍 Overview If Search Atlas is buffering, stuck on a loading screen, or displaying unexpected errors, several common factors could be responsible — from browser settings to temporary platform issues. This guide walks you through the most effective fixes to get you back up and running quickly. ⚠️ Common Symptoms - The platform loads indefinitely without displaying content - Pages or projects are stuck in a loading state - An unexpected error screen appears on the homepage - The UI flickers or shakes while navigating - Tools such as Site Explorer return an Error 500 or fail to load results - Restricted browser pages show an infinite loader instead of a clear error message 🛠️ Step-by-Step Troubleshooting 1. Refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh. This forces the browser to reload all assets instead of using a cached version. 2. Clear your browser cache and cookies. Outdated cached data is one of the most common causes of loading problems. In Chrome, go to Settings → Privacy and Security → Clear Browsing Data, select Cached images and files and Cookies, then click Clear data. 3. Disable browser extensions. Extensions — especially ad blockers, VPNs, or script blockers — can interfere with platform requests. Open an Incognito / Private window (which disables most extensions by default) and try loading Search Atlas again. 4. Check your internet connection. Run a speed test at a site such as fast.com. A slow or unstable connection can cause requests to time out, resulting in buffering or error 524 messages. 5. Try a different browser or device. If Search Atlas loads correctly in another browser (e.g., Firefox or Edge) or on a different device, the issue is isolated to your original browser environment. 6. Check for platform-wide issues. Intermittent errors (such as ERR_FAILED 524 or Error 500) are sometimes caused by temporary server-side conditions. If multiple tools or projects are affected at the same time, the issue may resolve on its own within a few minutes. Wait a short while and try again. 7. Avoid restricted browser pages. Certain Chrome pages (such as chrome:// URLs or browser extension pages) block external scripts and can trigger an infinite loader. Always access Search Atlas through a standard browser tab using a regular https:// URL. ✅ Best Practices to Prevent Loading Issues - Keep your browser updated to the latest stable version. - Use Google Chrome or Mozilla Firefox for the best compatibility with Search Atlas. - Avoid running Search Atlas alongside resource-heavy applications that may limit available memory or bandwidth. - If you use a VPN or proxy, try disabling it temporarily — these tools can reroute traffic in ways that cause timeout errors. 📋 Information to Have Ready Before Contacting Support If the steps above do not resolve your issue, gathering the following details in advance will help our team diagnose the problem faster: - The browser name and version you are using - The specific tool or page where the loading issue occurs (e.g., Site Explorer, Homepage) - A screenshot or screen recording of the error or buffering state - Approximately when the issue started - Whether the issue happens consistently or only intermittently 💬 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.

🔄 Fix the Repeating Onboarding Screen Loop

🔍 Overview Some customers see the onboarding screen every time they log back into Search Atlas, even after completing onboarding previously. This article explains why this happens and what to do if you are affected. ⚠️ Why This Happens The repeating onboarding screen is caused by a known issue where your account's onboarding completion status is not saved correctly on the server side. This means Search Atlas cannot confirm that you have already finished onboarding, so it restarts the flow on every login. Because the root cause is a backend persistence problem, browser-side actions such as clearing your cache or switching browsers will not permanently resolve it. 🛠️ What to Do This issue requires a backend fix applied to your account. To get this resolved as quickly as possible, please escalate to our support team with the following information ready: - Your account email address — the email you use to log in to Search Atlas. - Your workspace or project name — so the team can locate your account immediately. - When the loop started — an approximate date or the earliest login where you noticed the onboarding screen reappearing. - What you have already tried — for example, whether you completed the full onboarding flow, cleared your browser cache, or tried a different browser, and what happened each time. Having this information ready will allow our team to investigate and correct your onboarding completion status on the backend without delay. ✅ How to Confirm the Issue Is Resolved After our team has applied the backend fix to your account, you should be able to: - Log in and land directly on your Search Atlas dashboard without seeing the onboarding screen. - Close your browser, reopen it, and log back in — the onboarding screen should not reappear. 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.

🔧 Fix an Onboarding Loop Blocking Dashboard Access

What Is the Onboarding Loop Issue? Some customers find themselves repeatedly redirected to the onboarding or plan-selection screen even after completing setup. This prevents access to the main dashboard and other platform features. This is a backend issue that requires our team to resolve — the information below will help you understand what is happening and how to escalate quickly. Common Symptoms - You are redirected to the onboarding screen every time you log in, even after completing setup. - After completing the onboarding steps, you are sent back to an earlier onboarding page instead of reaching the dashboard. What to Do This issue cannot be fully resolved through browser-side actions — it requires a backend correction to your account. To get unblocked as quickly as possible, please reach out to our support team and have the following information ready: - The email address associated with your Search Atlas account - The exact screen or page you are being redirected to (e.g. onboarding screen, plan-selection page) - Any error messages you see, and the date and time they first appeared Why Does This Happen? Being stuck in an onboarding loop is a known backend issue related to how your account's setup or subscription status is recorded. Our team will investigate your specific account and make the necessary corrections on the backend to restore your access to the dashboard. 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.

🔍 Finding and Accessing Missing SEO Analysis Features

Overview Some customers notice that features such as meta keywords analysis, missing keywords, semantic analysis, knowledge graph optimization, and knowledge-based trust are not immediately visible in their account. This article explains what to check and what information to have ready if you need support to resolve the issue. Why Features May Appear Missing Because the original source for this topic did not include a documented agent resolution, the exact root cause can vary. Common factors that have been reported include plan-level access restrictions, features that only appear after a site analysis has been run, or features located in a different section of the platform than expected. The actual cause in your case may differ and may require a backend review by our team. What to Check Before Escalating Work through the following checks to rule out common display or access issues: 1. Confirm a site analysis has been run. Navigate to your project and verify that a crawl or on-page analysis has been completed. Some features only populate with data after this step. 2. Check all relevant sections of the platform. Expand any collapsed submenus and switch between tabs to make sure you are not overlooking a nested section. 3. Select a specific page or URL. Some analysis features only appear when an individual URL is selected rather than the project-level overview. 4. Review your subscription plan. Go to your Avatar (top-right) → Billing (Plans & Top-ups) and confirm which features are included in your current plan, as plan-level restrictions may limit visibility. 5. Clear your browser cache or try a different browser. Client-side rendering issues can occasionally prevent features from loading correctly. If the Feature Is Still Not Visible If none of the above steps resolve the issue, our team will need to investigate on the backend. Please have the following ready when you reach out: - The exact name of the feature you cannot locate (e.g., Missing Keywords, Knowledge Graph, Semantic Analysis) - Your project name and the specific URL or page where you expected to find the feature - A screenshot or screen recording showing what you see in place of the expected feature - The date and time you first noticed the feature was missing - Your current subscription plan name 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.

⚙️ Set Up Brand Voice & Fix Buffering

What Is the Brand Voice & Tone Profile? The Brand Voice & Tone Profile is a feature inside Brand Vault that lets you define how your brand communicates — its personality, tone, and style. Once configured, this profile can be applied across content generation and ad copy tools so every output sounds consistent and on-brand. How to Set Up Your Brand Voice & Tone Profile Follow these steps to configure your Brand Voice & Tone Profile in Search Atlas: 1. Log in to your Search Atlas account and navigate to Brand Vault from the main menu. 2. Select the brand entry you want to configure, or create a new one if you have not yet added your brand. 3. Open the Brand Voice & Tone Profile section within that brand entry. 4. Fill in the tone and style fields — for example, choose a descriptor such as professional, conversational, or formal — and add any specific guidelines about how your brand communicates. 5. Save your changes. Your profile will now be available to apply when generating content or ad copy across Search Atlas tools. Once saved, look for the option to apply or select your Brand Voice profile inside content generation and ad creation tools. Selecting your profile there ensures every output reflects your configured tone and style. Why Is Search Atlas Showing Continuous Buffering? Continuous buffering — where the platform appears to load indefinitely without displaying content — is often caused by a browser cache issue, a conflicting extension, or a temporary network or session problem. Try the following steps in order before escalating: 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force the browser to reload the page without using cached files. 2. Clear your browser cache and cookies. Go to your browser settings, clear cached data and cookies for Search Atlas (or all sites), then reload the platform. 3. Try an incognito or private window. Open a new incognito/private window and log in to Search Atlas. If the platform loads correctly, a browser extension is likely interfering. 4. Disable browser extensions. If incognito resolves the issue, re-enable extensions one at a time to identify which one is causing the conflict, then disable or remove it. 5. Try a different browser. Test in a second browser (e.g. Chrome, Firefox, Edge) to determine whether the issue is browser-specific. 6. Try a different network. Switch from Wi-Fi to a mobile hotspot, or vice versa, to rule out a network or firewall issue. 7. Log out and log back in. Sign out of Search Atlas completely, clear any saved session data, and sign in again to refresh your session. If buffering persists after completing all of the steps above, the issue may require investigation by 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.

🛠️ Fix PR Publishing Failures and Resubmission Workflow

Overview If your press release (PR) failed to publish, this article explains what to do next. Because PR publishing failures can have different root causes depending on your account and submission details, our support team will need to investigate your specific case to identify the exact cause and guide you to the correct fix. What to Have Ready When You Contact Support To help our team resolve your PR publishing failure as quickly as possible, please gather the following information before reaching out: - The name or title of the PR that failed to publish. - The exact error message or status shown at the time of failure (a screenshot is helpful if available). - The date and time the submission was attempted. - Any details about the distribution channel or options you selected during submission. Having these details ready will allow our team to identify the cause of the failure and advise you on the correct resubmission steps for your situation. 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.

🔧 Fix Recurring Google Integration Disconnections

What Is Happening? Some Search Atlas users experience recurring disconnections with Google Search Console (GSC) and Google Business Profile (GBP) integrations. The connection status may flip between Connected and Not Connected repeatedly, even after attempting to reconnect. This is a known issue that may require backend investigation to resolve fully. Common Triggers While our team investigates, the following are known factors that can contribute to repeated disconnections: - OAuth token expiry or revocation: Google periodically invalidates access tokens, especially if your Google account password changed, two-factor authentication was updated, or third-party app access was revoked in your Google Account settings. - Multiple reconnect attempts in one session: Reconnecting more than once without fully completing the auth flow can corrupt stored credentials, causing the status to flip repeatedly. - Browser or cache interference: Cached sessions, browser extensions, or cookie blockers can interrupt the OAuth handshake mid-flow, leaving the connection in a broken state. - Google Account permissions changed: If the Google Account used to connect lost owner or full access rights to the Search Console property or Business Profile, Search Atlas cannot maintain a valid connection. What You Can Try Before escalating to our team, you may attempt the following general steps: 1. Revoke and re-grant access in your Google Account. Go to myaccount.google.com → Security → Third-party apps with account access, find Search Atlas, and remove it. This clears any corrupted tokens on Google's side. 2. Clear your browser cache and cookies, or open an incognito / private window. Disable any ad-blocker or privacy extensions for the duration of reconnection. 3. In Search Atlas, locate your account integrations settings and find the Google Search Console or Google Business Profile connector. 4. Disconnect the integration completely — do not skip this step even if the status already shows as disconnected. A full disconnect ensures stale credentials are cleared. 5. Reconnect once. Complete the full Google OAuth flow and grant all requested permissions. Do not click the button multiple times — wait for the redirect to complete fully before taking any other action. When the Issue Persists — What to Have Ready If disconnections continue after following the steps above, this issue requires backend investigation by our team. To help us resolve it as quickly as possible, please have the following information ready when you reach out: - The email address of the Google Account used for the integration - The name of the GSC property or Business Profile affected - The approximate date and time the disconnection first occurred or recurred - Any error messages displayed during reconnection attempts 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.

🧹 Clear Your Browser Cache to Fix Search Atlas Display Issues

If Search Atlas is behaving unexpectedly — such as pages not loading correctly, outdated content appearing, or features not responding — clearing your browser cache is a quick and effective first troubleshooting step. Cached files can sometimes become outdated or corrupted, causing display and performance issues. Follow these steps to clear your browser cache: - Open your browser settings. This is usually accessible via the menu icon (three dots or lines) in the top-right corner of your browser window. - Navigate to the Clear Browsing Data option. In most browsers, you can also reach this directly by pressing Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). - Make sure Cached images and files is selected. You may uncheck other options if you prefer to keep your browsing history and cookies intact. - Click Clear Data to remove the cached files. - Once the cache has been cleared, open a private or incognito window and navigate to Search Atlas to confirm whether the issue has been resolved. A private window ensures no old cached data is being used. If clearing the cache does not resolve your issue, try repeating the test in a different browser to rule out a browser-specific problem. If the issue persists across browsers or private windows, please reach out to us by using the live chat widget in the app to chat with a human teammate — we are happy to help investigate further.

⚡ Platform-Wide HTTP 500 Errors: What To Do

What Is an HTTP 500 Error? An HTTP 500 error means the server encountered an unexpected problem and could not complete your request. When this happens across multiple areas of Search Atlas at the same time, it typically points to a platform-wide production issue rather than a problem with your account or browser. Signs You Are Experiencing a Platform-Wide Issue - Multiple unrelated features are broken at the same time. - Actions that normally work — such as publishing, deploying, or loading dashboards — consistently return a 500 error regardless of the feature you try. - Refreshing the page or switching browsers does not resolve the problem. Steps To Take Right Now 1. Confirm it is platform-wide. Try two or three completely different sections of Search Atlas. If all of them fail with a 500 error, the issue is on the platform side. 2. Do not repeatedly retry high-volume actions. Submitting the same request many times during a server-side incident (such as deploying content or publishing posts) will not help and may cause additional errors once the platform recovers. 3. Wait a short time and refresh. Platform-wide 500 errors are treated as high-priority incidents by the Search Atlas engineering team. Fixes are applied at the server level during production deployment. Wait a few minutes, then hard-refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and try again. 4. Clear your browser cache if errors persist after a refresh. Occasionally, a cached error response can prevent you from seeing the recovered platform. Clear your cache and cookies, then reload Search Atlas. 5. Verify your work after recovery. Once the platform is back to normal, check the areas where you experienced errors to confirm everything is functioning as expected. What the Search Atlas Team Does During an Incident When a platform-wide 500 error is detected, the engineering team works to deploy a fix as quickly as possible. These errors are resolved through server-side fixes applied during production deployment, with no action required from customers. You do not need to change any settings, reconnect accounts, or modify your projects. The resolution is always applied at the platform level. When To Contact Support If errors persist after the platform has been confirmed as recovered, or if you are unsure whether a current issue is platform-wide, please contact the Search Atlas support team so we can investigate further. If you don't hear back right away, we'll get back to you as soon as possible.

🔧 Fix Lead Capture Widget Invitation-Only Redirect Issue

🧭 Overview When you embed a Lead Capture widget on your website, visitors should see a public-facing form or report — not a login or registration wall. If your current snippet is redirecting visitors to an Invitation Required registration page, your widget is pointing to the whitelabel dashboard instead of the public Lead Capture widget endpoint. This article explains how to identify and fix that configuration. 🔍 How to Tell Which Problem You Have There are two different snippets inside Search Atlas. It is easy to copy the wrong one. Before changing anything, confirm which behavior your visitors are seeing: - Public widget working correctly: Visitors land on a branded report or lead capture form with no login prompt. - Invitation-only redirect (this issue): Visitors are sent to a page that says Invitation Required or asks them to register before they can continue. This means your snippet is linking to the whitelabel dashboard URL, not the embeddable public widget. ⚠️ Why This Happens Search Atlas has two separate access points that look similar but behave differently: - Whitelabel Dashboard link — requires an invitation or account login. It is designed for clients you have explicitly invited to view their reports inside your branded portal. - Lead Capture Widget snippet — a publicly embeddable code block that lets any anonymous visitor submit their site URL, receive a report, and become a lead. No login or invitation is needed. If you copied your snippet from the whitelabel dashboard settings area rather than the Lead Capture widget settings area, visitors will always hit the invitation gate. The fix is to replace the snippet with the correct one. ✅ How to Get the Correct Public Widget Snippet 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to Lead Capture. 3. Open the Widget Settings tab (not the Dashboard or Client Access tab). 4. Locate the Embed Code section. The correct snippet will contain a script tag referencing the public widget endpoint — it will not contain a dashboard subdomain URL or an invite token. 5. Copy the full snippet exactly as shown. 6. Replace the existing snippet on your website with this new code. 7. Save and publish your page, then test by opening the page in a private/incognito browser window to confirm visitors see the public form instead of an invitation prompt. 🛠️ Quick Checklist Before You Go Live - You copied the snippet from Lead Capture → Widget Settings, not from the whitelabel dashboard area. - The snippet does not include your whitelabel subdomain (e.g., reports.yourdomain.com/invite) as the destination URL. - You tested the page in an incognito window while logged out of Search Atlas. - Visitors see the lead capture form or public report immediately — no login or registration prompt appears. 📋 Additional Configuration to Check Even with the correct snippet in place, the following settings can affect public access: - Widget visibility: Inside Lead Capture → Widget Settings, confirm the widget status is set to Active or Published. A draft or paused widget may still redirect or show an error. - Whitelabel domain routing: If your whitelabel domain and your lead capture widget share a parent domain, ensure the routing rules in your DNS or platform settings are not intercepting the widget URL and sending traffic to the client dashboard instead. - Report access toggle: Some accounts have a setting that restricts report viewing to invited clients only. If that toggle is enabled globally, it will override the public widget. Locate the access control settings under your whitelabel configuration and confirm public report access is allowed. 🔄 If the Correct Snippet Still Redirects to Invitation Page If you have replaced the snippet with the one from Lead Capture → Widget Settings and visitors are still hitting an invitation-required page, this may indicate a platform-level configuration issue rather than a snippet error. In that case: - Double-check that you saved and re-published the page after replacing the snippet. - Clear any caching on your website or CDN, as an old cached version of the page may still be serving the old snippet. - Try embedding the widget on a brand-new test page to rule out page-level conflicts. - If the problem persists on a fresh page with the correct snippet, the issue is likely a backend configuration that requires our team to investigate. 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.

🛠️ Search Atlas — General Platform Issues

Use this guide to diagnose and fix the most common Search Atlas platform errors — dashboard loading failures, stalled OTTO crawls, health score updates, data sync delays, and schema deployment issues. ⚠️ Common Issues & Fixes 🔴 Error: "Something went wrong" when loading projects or OTTO What's happening The dashboard cannot load your project data. How to fix it 1. Hard-refresh your browser: Ctrl + Shift + R (Windows) / Cmd + Shift + R (Mac) 2. Log out and log back in. 3. Try a different browser — Chrome is recommended. 4. Clear cache and cookies for dashboard.searchatlas.com. 5. If you see an error code, copy it and share it with support. After clearing cache and logging back in, the dashboard should load your projects normally. 🕷️ Error: OTTO crawl stuck on "In Progress" What's happening Your site crawl has stalled or is taking longer than expected. How to fix it 1. Wait if your site is large — sites with 10,000+ pages or heavy JavaScript can take several hours. If the crawl exceeds 6 hours without completing, proceed to the restart step. 2. Confirm your site is publicly accessible — no login walls or IP restrictions. 3. Check your robots.txt to ensure crawlers are not blocked. 4. Restart the crawl: Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site 5. If you are using Cloudflare or a WAF, whitelist crawler IPs — contact Search Atlas support to obtain the current list of crawler IP ranges to add to your firewall rules. Note: A character encoding corruption bug affecting Cloudflare-deployed OTTO scripts has been resolved and the updated script deployed to production. If you previously disengaged OTTO due to special character corruption or display issues, you can now safely reconnect your Cloudflare integration by navigating to your OTTO project's Cloudflare settings and re-enabling the worker. Contact support if you need assistance re-engaging. Once the recrawl completes, the crawl status will update from "In Progress" to a finished state. 📊 Error: OTTO health score not updating What's happening Your fixes have not been revalidated yet. How to fix it 1. Wait at least 30 minutes. 2. Trigger a manual re-crawl: Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site 3. Confirm your fixes are live on your actual site — not just in OTTO's optimization dashboard. 4. Refresh the dashboard. 5. Use "Validate Fix" on specific tasks to trigger targeted revalidation. After the re-crawl finishes, your OTTO health score will reflect the validated fixes. ➕ Error: Can't create a new project What's happening The domain format is incorrect or the domain already exists in your account. How to fix it 1. Enter the domain without the protocol: ✅ yourdomain.com ❌ https://yourdomain.com 2. Check whether the domain already exists in your projects. 3. Click Create only once to avoid duplicate submissions. 4. Verify your plan limits: Top-right Avatar → Billing → Plans & Top-ups (Billing) 5. Try incognito mode if the issue persists. Once the domain format is correct and your plan has available slots, the project will be created successfully. ⏳ Error: OTTO tasks stuck as "Pending" What's happening Approved tasks have not executed yet. How to fix it 1. Wait up to 15 minutes for the task queue to process. 2. Check Google Search Console (GSC) permissions — you must be an Owner or Full User. 3. If tasks remain pending for more than 24 hours, cancel and re-approve them. 4. Check for noindex tags that may be blocking execution. 5. Confirm your CMS integration is active. Resolving permission or integration issues typically unblocks pending tasks within minutes. 🧩 Error: Schema generation or deployment fails What's happening Schema markup is not being generated or deployed successfully to your site. How to fix it 1. Click the purple Generate button before attempting to deploy. 2. Clear your browser cache and try again. 3. If the AI Agent appears stuck while generating schema in batches, refresh the session and re-prompt. If the issue persists, contact support and include your session link. 4. If the error persists, it is a system-level issue — contact support with your project URL and an error screenshot, as engineering escalation may be required. After generating schema successfully, the Deploy button becomes active and your schema publishes to your site. 🧱 Error: OTTO deployed fix is adding unwanted content to my site What's happening A deployed OTTO fix (for example, Heading Length) is injecting content you did not intend on your front-end. How to fix it 1. Go to your OTTO project. 2. Locate the deployed fix under Optimizations or Deployments. 3. Click Undeploy on the specific fix (for example, Heading Length). Undeploying removes the change from your front-end immediately. 🚫 Error: Quota Exhausted when adding a new OTTO site What's happening You have reached the OTTO site slot limit on your current plan. OTTO site slots are tracked separately from Site Auditor Projects — having available Site Auditor Projects does not mean you have available OTTO site slots. How to fix it 1. Check your plan limits in Top-right Avatar → Billing → Plans & Top-ups (Billing). 2. Confirm whether you have available OTTO site slots (distinct from Site Auditor Projects). 3. If the dashboard count appears inconsistent with your plan, contact support. Once you free up or upgrade your OTTO site slots, you can add the new site. 🧠 Error: Atlas Brain / AI Agent shows "I'm temporarily unable to process your request" or persistent Keyword Gap Analysis errors What's happening The Atlas Brain / AI Agent service is returning an error or failing to process requests. Platform-wide Atlas Brain errors occur occasionally, are monitored by the engineering team, and are typically resolved within 48 hours. How to fix it 1. Wait a few minutes and retry. 2. Hard-refresh the browser. 3. Check the Search Atlas status page. 4. If the error is platform-wide, engineering is typically already aware. Contact support with your session link to confirm whether a known issue is active and get an estimated resolution time — this is more effective than running self-troubleshooting steps that will not resolve a platform-wide outage. If it is a platform-wide issue, the Search Atlas engineering team will resolve it — typically within 48 hours. 🏠 Error: Active Projects panel shows zero values or stale data What's happening The Active Projects panel on the dashboard homepage may display zero values until manually refreshed, while the Portfolio Summary updates automatically. How to fix it 1. Manually trigger a page refresh to repopulate the Active Projects values. 2. If a standard refresh does not update the values, hard-refresh your browser: Ctrl + Shift + R (Windows) / Cmd + Shift + R (Mac) 3. A fix for this behavior has been deployed. If the issue persists after refreshing, contact support. After refreshing, the Active Projects panel will display your current project data. 🔄 Error: Data looks outdated What's happening Data refresh cycles have not completed yet. How to fix it 1. Wait for the next scheduled refresh cycle — typically 24–48 hours. 2. Hard-refresh your browser: Ctrl + Shift + R (Windows) / Cmd + Shift + R (Mac) 3. Verify the date range filter is set correctly. 4. If data still appears outdated after a full refresh cycle, contact support with your project URL. Once the refresh cycle completes, your data will reflect the latest available information. 🎯 This guide covers the most common Search Atlas platform issues. If none of these steps resolve your problem, contact Search Atlas support with your project URL, error screenshot, and session link — the team can escalate to engineering when needed.

⚠️ Fixing Anthropic 503 Provider Access Error

🔍 What This Error Means When you see API Error: 503 [provider_access_absent], it means Search Atlas's AI gateway was temporarily unable to route your request to Anthropic's servers. The error message may say "retrying will not help" or suggest you need to request access — in most cases, neither is true. This is almost always a short-lived routing issue between Search Atlas and Anthropic's infrastructure, not a problem with your account or subscription. 🛠️ Why This Error Occurs - Temporary capacity constraints: Anthropic's infrastructure occasionally limits availability during high-demand periods, which can cause the gateway to report a failed connection. - Model-level restrictions: A specific AI model may be temporarily unavailable while others remain fully accessible. The error message can make this look like a broader access problem — but it usually is not. - Gateway routing delay: Search Atlas's AI gateway may briefly lose its path to Anthropic's API pool before recovering automatically within seconds or minutes. ✅ How to Fix It — Step by Step 1. Wait 1–2 minutes, then retry. The majority of these errors resolve on their own. Refresh the page and try your action again before doing anything else. 2. Switch your AI model to Atlas Fusion. If the error appears again, change the model to atlas-fusion using the model selector before generating content. Atlas Fusion uses a separate provider pool and is unaffected by Anthropic-specific outages — it is the fastest way to keep working without interruption. 3. Try a different content action. In Content Genius (left sidebar → Content → Content Genius), you can switch modes. For example, try Write it yourself or Rework existing article if the error appeared during a different generation flow. 4. Check Anthropic's status page. If you suspect a wider outage, visit status.claude.com to see if Anthropic is reporting any active incidents that may be affecting availability. 📋 A Note on the Error Message Wording The phrasing in this error — "retrying will not help" and "ask an operator for Anthropic access" — can be alarming, but it is often misleading. This wording was intended for a very specific edge case (a permanently blocked API key), but it can surface during temporary routing failures that have nothing to do with your account's access level. You do not need to request new permissions or contact Anthropic. If switching to atlas-fusion resolves the issue, your account is fully functional and the problem was on the provider side. 🔄 Running Bulk Content Jobs? If this error appears during a Write with AI in Bulk session, pause the batch immediately rather than retrying rapidly. Wait 60–120 seconds to allow the gateway to re-establish its connection, then resume. Rapid successive retries during an outage window can queue up failed requests and slow recovery. 💡 Best Practices to Minimise Disruptions - Keep atlas-fusion available as a backup model when working on time-sensitive content or large bulk runs. - Wait at least 60 seconds between retry attempts — this gives the AI gateway time to recover its routing path. - If the same error recurs across multiple sessions on the same day, note the time and model you were using before contacting support — this helps our team investigate faster. 🆘 Still Seeing the Error? If the error persists after switching to atlas-fusion and waiting a few minutes, our team can look into the specific instance ID shown in your error message. 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.

⚠️ Website Builder: Chat Panel Cut Off Below the Fold

The left-hand chat panel in the Website Builder currently extends beyond the visible screen height, pushing the message input box below the fold. Zoom your browser out to 80–90% to restore the full layout while our engineering team deploys a fix. 🔍 What's Happening In the Website Builder (Left sidebar → Website Studio, dashboard.searchatlas.com/website-studio), the left-hand chat panel does not fit within the visible viewport height. The message input box at the bottom of the panel is cut off below the fold, making it difficult to type and send messages without scrolling the entire page. This is a layout display issue only. It does not affect any saved content, site files, or account data. 🛠️ Workaround Steps Zooming your browser out is the most practical fix — it restores the intended layout without requiring repeated page scrolling. 1. Open the Website Builder via Left sidebar → Website Studio (dashboard.searchatlas.com/website-studio). 2. Press Ctrl + Minus (Windows/Linux) or Cmd + Minus (Mac) to zoom your browser out. 3. Continue zooming until the level reaches approximately 80–90% and the full chat panel — including the message input box — is visible on screen. 4. To reset zoom at any time, press Ctrl + 0 (Windows/Linux) or Cmd + 0 (Mac). Alternative: Scroll the page down to reach the message input box. This requires scrolling each time you want to type a new message and is less convenient than adjusting browser zoom. 📡 Engineering Status Our engineering team has shipped a fix for this issue. If you are still experiencing the problem, please clear your browser cache and refresh the page. If it persists, contact support. 📞 When to Contact Support If the zoom workaround does not resolve the issue for you, or if reducing zoom to 80% is not practical for your workflow, contact our support team. When you reach out, include your browser name and version, your screen resolution, and a screenshot if possible — this helps us address the issue faster for your account. 🌀 Our team is actively working on a permanent fix, and the chat panel will return to its correct layout automatically once it ships. Thank you for your patience — the browser zoom workaround fully restores the Website Builder experience in the meantime.

🛠️ 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.

🔐 Fix Redirect to Choose Plan Page

🧹 Clear Browser Data Start by clearing your browser cookies and cache, then try accessing the platform again. If the issue persists, open an incognito or private browsing window and log in from there. 📄 Verify Payment Status Check your email for the payment receipt or invoice from the most recent charge. Confirm that the payment was successfully processed and matches your active plan. 📞 Escalate to Support If you still get redirected to the plan selection page after clearing browser data and confirming a successful payment, 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. Provide the invoice or receipt details so we can investigate and resolve the issue on the backend.

🔄 Fix Choose-Plan Page Stuck Loading

🔍 Overview Some customers encounter a spinning loader, blank plan cards, or errors such as 'Failed to get updated profile data' or 'Network error' when reaching the choose-plan page after registration. This can happen across different browsers and devices. This article explains why this occurs and walks you through every step to resolve it. ⚠️ Common Symptoms - The choose-plan page displays an infinite spinning wheel with no plan options loading. - Error messages appear: 'Failed to get updated profile data' or 'Network error'. - The Start Free Trial button stays on 'Processing…' for 20–40 seconds before anything happens — or nothing happens at all. - The issue persists across multiple browsers, incognito/private mode, and mobile devices. 🛠️ Step-by-Step Troubleshooting 1. Wait briefly and refresh. If you just registered, the system may still be provisioning your account. Wait 60 seconds, then press F5 (or pull-to-refresh on mobile) to reload the page. 2. Clear your browser cache and cookies. Cached data from a previous session can interfere with profile loading. Clear your cache, close all tabs, and reopen the choose-plan page. 3. Try a different browser. Open the page in a different browser (for example, Chrome, Firefox, or Edge) to rule out a browser-specific conflict. 4. Disable browser extensions. Ad blockers, VPNs, and privacy extensions can block API calls that load plan data. Disable all extensions, then reload the page. 5. Check your internet connection. A weak or intermittent connection can trigger network errors. Switch networks (for example, from Wi-Fi to mobile data) and try again. 6. Use a direct login link. Navigate directly to app.searchatlas.com, log in with your registered credentials, and allow the platform to redirect you to the choose-plan page automatically. 7. Try again after 10–15 minutes. Temporary backend delays can cause profile data to be unavailable. If none of the above steps work immediately, wait a short time and try again. 💡 About the 'Processing…' Delay on Start Free Trial When you click Start Free Trial, the button may show 'Processing…' for up to 40 seconds before the checkout window opens. This is a known delay that occurs while the system prepares your trial session. Do not click the button multiple times — doing so can cause duplicate requests. Wait for the checkout to open on its own. 📋 What Our Team Can Do for You If the choose-plan page still does not load after completing all the steps above, a member of our team can manually activate your free trial so you can access the platform right away. No further action is required on your end — simply reach out and we will handle it. 🆘 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.

🛠️ Make Your Lead Widget Public

🔍 Why visitors see a login page A public lead capture widget should let visitors view the form without creating an account or signing in to your whitelabel dashboard. If the widget opens a dashboard URL and displays “Invitation Required,” the snippet is likely using a dashboard link instead of the published lead capture widget URL. ⚙️ Check your widget settings 1. Sign in to your Search Atlas platform. 2. Open the relevant agency or whitelabel settings. 3. Locate the lead capture widget for the audit or service you want to share. 4. Confirm the widget is enabled and configured for public access. 5. Save or publish the settings. 📋 Copy the public embed code After publishing the widget, copy the embed snippet provided in the widget settings. Add this code to the page where you want leads to see the form. Do not copy a dashboard URL manually or replace the widget source with a whitelabel dashboard address. 🧪 Test the public experience 1. Open the page in a private or incognito browser window. 2. Test it while logged out of Search Atlas and your whitelabel dashboard. 3. Confirm the form loads without showing a login screen or “Invitation Required” message. 4. Submit a test entry and verify that the lead appears in the expected agency location. 🚧 If the widget still requires login Check that you are using the latest embed code after saving the settings. Also verify that the widget is installed on the correct published page and that your whitelabel domain is configured correctly. If the snippet still redirects to the dashboard or falls back to a Search Atlas domain, the public widget may not yet be enabled for that account or widget type. 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.