Support: General

⚡ Local Taxi SEO Audit and Ranking Optimization

🔗 How to Use Third-Party Content Sources with Search Atlas

🛠️ On-Page Audit Content Optimization and Publishing Workflow

🛠️ Published Post Removed From Queue Explained

🔍 What This Article Covers You published a post before its deadline, but you received an email saying the post is being removed from your queue for taking too long. This article explains why this happens, what it means for your payment, and the exact steps to take next. ⚠️ Why You Received This Email Removal emails are sent automatically when the platform does not record a Published status for a post within the expected publishing window. In many cases, the post was actually published on time — the system simply did not register it before the deadline check ran. Common causes include: - Publishing pipeline delays: posts can remain in a Publishing state longer than usual while the queue works through a backlog. - Timing detection gaps: the post went live at its destination (for example, your website or Google Business Profile), but the confirmation did not sync back to the platform before the deadline check. - Status sync lag: a short delay between the moment content goes live and the moment your dashboard updates. These are timing issues on the platform side. This email is not a judgment on the quality of your work, and it does not cancel work you have already completed. 💰 What This Means for Your Payment If your post is live and publicly visible, you will still be paid. A removal email does not reverse payment for a post that was genuinely published on time. Once our team verifies the live post, it is restored to the payment queue and processed in the normal payment cycle. To qualify, the post must be live at its assigned URL and visible to anyone visiting that link, without requiring a login. Important: do not delete the live post. Our team needs it in place to verify publication and confirm your payment. 📋 Steps to Resolve This 1. Confirm the post is live. Open the post URL in an incognito or private browser window to make sure it is publicly visible without logging in. 2. Copy the live link. Save the exact URL where the post appears, along with the date and approximate time it went live, if you have them. 3. Check the post status. Review the post in your dashboard. If it still shows Publishing, this confirms a sync delay rather than a publishing failure on your end. 4. Contact our team. Open the chat widget and share your live link so we can verify the post and restore it to the payment queue. 🛡️ How to Reduce the Chance of This Happening - Publish several hours before the deadline rather than right at the cut-off, giving the system time to register the post. - After publishing, refresh your dashboard and confirm the status changes to Published before you close the tab. - Keep a copy of the live URL for every post you publish. - If a post appears stuck in Publishing for an extended period, contact us before the deadline so we can check the queue while there is still time. 💬 Still Need Help? Have your live post link ready, along with the title of the assigned post and the removal email you received. This helps us verify publication quickly and protect your payment. 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.

📋 Using the Phase 2 SOP Template in SA-Product-Specialists

🗺️ Overview The Phase 2 Standard Operating Procedure (SOP) template is a structured guide that Product Specialists use to document and communicate key workflow steps within the sa-product-specialists channel. Posting the template correctly ensures consistent handoffs, reduces errors, and keeps the team aligned. 📌 What Is the Phase 2 SOP Template? The Phase 2 SOP template is a pre-formatted document designed to capture all critical information needed when escalating or handing off a task to the product-specialists team. It standardises how information is shared so every team member has the context they need to act quickly and accurately. The template typically includes: - Task title and description — a clear summary of what needs to be done - Current status — where the task stands at the point of handoff - Steps completed — actions already taken before escalation - Next required action — what the receiving specialist needs to do first - Priority level — urgency classification so tasks are handled in the right order - Relevant links or attachments — supporting documents, screenshots, or platform references - Assigned owner — the person responsible for completing the next step 🚀 How to Access the Phase 2 Template 1. Log in to your team's project management workspace. 2. Navigate to the sa-product-specialists channel or the designated SOP documentation space. 3. Locate the Phase 2 SOP template in the shared templates library. Your team lead or manager can share the direct link if you do not yet have access. 4. Open the template and make a copy before editing — never edit the master template directly. ✏️ How to Fill Out and Post the Template 1. Copy the template — create a new instance for each task or escalation. Do not reuse a previously filled copy. 2. Complete every field — leave no section blank. If a field does not apply, write N/A so reviewers know it was considered. 3. Be concise and specific — use plain language. Avoid internal shorthand that others may not recognise. 4. Attach supporting evidence — include screenshots, platform URLs, or relevant account IDs where applicable. 5. Set the correct priority — confirm the urgency level with the requesting manager before posting if you are unsure. 6. Post in the sa-product-specialists channel — paste the completed template directly into the channel. Do not share it as a private message unless instructed otherwise. 7. Tag the relevant team member — mention the assigned owner so they receive an immediate notification. 8. Confirm receipt — wait for an acknowledgement from the assigned specialist before closing out your involvement in the task. ✅ Best Practices - Always use the most recent version of the Phase 2 template. Check with your team lead if you are unsure whether your copy is up to date. - Post the template at the time of escalation — do not wait until the end of the day. - Keep the channel organised by using thread replies for follow-up comments rather than posting new top-level messages. - If a task is resolved before the assigned specialist acts on it, update the posted template with a RESOLVED note and a brief summary of the outcome. - Do not share internal SOP links externally with customers. The SOP is an internal coordination tool only. ⚠️ Common Mistakes to Avoid - Editing the master template — always work from a copy. - Skipping the priority field — every post must have a clearly defined urgency level. - Posting incomplete templates — a partial template creates confusion and slows resolution. - Using the wrong channel — confirm you are posting in sa-product-specialists and not a general or unrelated channel. 💬 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.

🛠️ Reset and Clean Up DKN Nodes

🔍 What Is the DKN and Why Might It Need a Reset? Your Domain Knowledge Network (DKN) is the foundation Search Atlas uses to understand your website's topical structure. It maps your content into interconnected nodes — one per page or topic — to power recommendations across Content Genius and OTTO SEO. Over time, your DKN may develop issues such as: - Duplicate or overlapping nodes — the same page is recognised as multiple distinct nodes. - Stale or poisoned keywords — node keywords carry over incorrect or mismatched data from earlier builds. - Corrupted titles — node titles contain disambiguation code that was not cleaned up automatically. - Mismatched data after a project switch — data from a previous project appears in a new project's DKN. If your DKN contains any of these problems, resetting it and rebuilding from scratch is usually the fastest way to restore accurate topical mapping. ⚠️ Before You Reset: What to Know Please read the following carefully before proceeding: - A full DKN reset is irreversible. All existing nodes, keyword assignments, and topical connections for the project will be permanently deleted. - After a reset, the DKN must be fully rebuilt. Rebuilding time depends on the size of your domain and the number of pages crawled. - Any Content Strategy work tied to existing nodes — such as briefs or cluster assignments — may be affected. Review your active content work before resetting. - Do not use the Sync with Brand Vault button on the Content Strategy page as a workaround for DKN issues. A known issue means this action can wipe DKN nodes without triggering a proper rebuild, leaving your network in an incomplete state. 🛠️ How to Request a Full DKN Reset At this time, a full DKN reset must be performed by the Search Atlas support team. There is no self-serve reset button in the platform. Follow these steps to get it done quickly: 1. Confirm which project needs the reset. Note the exact project name as it appears in Search Atlas. 2. Decide whether you need a full reset (wipe everything and rebuild from scratch) or bulk deletion of specific duplicate nodes (partial cleanup). Both options are supported. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate to connect with the support team. 4. Provide the following information: - Project name and URL - Whether you want a full reset or targeted node deletion - A brief description of the issue you are seeing (e.g., duplicate nodes, corrupted titles, stale data) 5. The team will confirm the action with you before making any changes. 🔄 How to Rebuild Your DKN After a Reset Once the reset is complete, follow these steps to rebuild a clean DKN: 1. Go to your Project Settings and verify that the correct domain and crawl settings are configured. 2. Trigger a new site crawl from the dashboard. This allows Search Atlas to rediscover your pages with fresh data. 3. Navigate to the Content Strategy section and allow the DKN to regenerate automatically as the crawl completes. 4. Once the DKN is rebuilt, review the new nodes to confirm they map correctly to your pages — look for any remaining duplicates or mismatched titles before resuming content work. ❓ Why Are Duplicate Nodes Being Created? Duplicate nodes can appear when the system has difficulty determining whether a page already exists in the network. This can happen in several scenarios: - URL variations — the same page is accessible via multiple URLs (e.g., with and without a trailing slash, or HTTP vs HTTPS), causing the crawler to treat them as separate pages. - Crawl interruptions — a previous crawl did not complete cleanly, leaving partial node data that conflicts with a new crawl. - Disambiguation code leaks — a known bug caused internal code used to differentiate similar topics to appear in node titles and keywords. This issue has been patched, and a backfill was run to clean affected data. If you still see symbols or codes in your node titles, contact support for a targeted cleanup. If you notice duplicates appearing shortly after a rebuild, check your canonical tags and redirect settings in your CMS before running another crawl. Fixing URL consistency at the source prevents the same issue from recurring. ✅ Quick Checklist Before and After a Reset - Note all active briefs and cluster assignments linked to existing nodes. - Confirm the correct project is selected before requesting a reset. - Do not use Sync with Brand Vault as a cleanup workaround. - After the reset, trigger a fresh crawl before reviewing new nodes. - Check canonical tags and redirects in your CMS to prevent duplicate nodes from reappearing. 💬 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.

💡 Submit a Feature Request to Search Atlas

💡 Why Submit a Feature Request? Search Atlas actively collects customer ideas to shape the product roadmap. If you have a suggestion — such as wanting Website Studio thumbnails to refresh automatically over time rather than showing only the original generated image — you can submit it directly through the official product portal. Your request will be visible to the product team, and you will receive updates as its status changes. 🚀 How to Submit Your Feature Request 1. Open the Search Atlas product portal in your browser: https://portal.productboard.com/searchatlas/1-search-atlas-product-portal/tabs/3-launched 2. Browse existing ideas to check whether someone has already submitted a similar request. If so, you can upvote it to show your support. 3. If your idea does not already exist, look for the option to submit a new idea and describe your suggestion clearly. Include as much context as possible — for example, which feature is affected, what behaviour you currently see, and what you would like it to do instead. 4. When prompted, enter your email address. This is how ProductBoard notifies you when the status of your request changes, such as when it is under review, planned, or launched. ✅ What Happens After You Submit Once your request is submitted, the Search Atlas product team will review it alongside other ideas. You may see your request move through status stages such as Under Consideration, Planned, or Launched. You will receive email notifications at each stage so you can stay informed without needing to check back manually. 📋 Tips for a Strong Feature Request - Be specific: Describe exactly what you want the feature to do, not just a general improvement. - Explain the use case: Share why this change would help you or your workflow. - Include examples: If relevant, mention the tool or page where the change should apply, such as Website Studio. - Use a real email: You need a valid email address to receive status updates on your submission. 🛠️ 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.

🔍 Why Can't I Access a Search Atlas Dashboard?

🗺️ Overview If you saw a Search Atlas dashboard in a screenshot, a webinar, or shared by another user but cannot find it in your own account, you are not alone. Dashboard visibility depends on your current plan, feature rollout status, and account permissions. This article explains the most common reasons for missing dashboards and what you can do about it. 🔎 Where to Find Your Dashboards Before assuming a dashboard is missing, confirm you are looking in the right place. Here is where to find the main sections in Search Atlas: - Home Dashboard: Click Home in the top navigation bar or go to /home. - Site Explorer: In the left sidebar, click Site Metrics (Site Explorer) (URL: /site-explorer/list). From here you can navigate to sub-sections including: - Keyword Magic — Left sidebar → Keywords → Keyword Magic - Rank Tracker — Left sidebar → Keywords → Rank Tracker - Keyword Gap — Left sidebar → Keywords → Keyword Gap If you still cannot locate a specific dashboard after checking these paths, continue reading for the most likely causes. 📋 Common Reasons a Dashboard Is Not Visible 🚀 Feature Is Part of a Phased Rollout Search Atlas regularly releases new features and dashboards to customers in stages. This means a feature you see in a screenshot or announcement may not yet be available in your account. Phased rollouts allow the team to monitor performance and gather feedback before releasing to all users. If a new dashboard was announced recently, it may arrive in your account within days or weeks. 💼 Your Plan Does Not Include the Feature Some dashboards and tools are only available on specific Search Atlas plans. If the dashboard you saw was shared by a user on a higher-tier plan, it may not be included in your current subscription. To check what is included in your plan, click your profile icon and review your subscription details, or contact support to ask about an upgrade. 🔑 Account Permissions or User Role If your account is managed by an agency or another team member, your user role may restrict access to certain dashboards. An account owner or administrator can adjust permissions for individual users. Ask your account admin to review your role settings if you believe this applies to you. 🔄 Cache or Browser Issue Occasionally, a dashboard that was recently added to your plan does not appear due to a browser cache issue. Try the following steps to rule this out: 1. Log out of Search Atlas completely. 2. Clear your browser cache and cookies. 3. Log back in and navigate to the relevant section again. 4. If the problem persists, try a different browser or an incognito/private window. ⚙️ What to Do Next Follow these steps to resolve your access issue quickly: 1. Confirm the navigation path — use the paths listed above to make sure you are looking in the correct location. 2. Check your plan — review your subscription to see whether the feature is included. 3. Contact your account admin — if you are a sub-user, ask your admin to review your permissions. 4. Wait for the rollout — if the feature was recently announced, it may be on its way to your account soon. 5. Reach out to support — if none of the above explains the issue, our team can check your specific account status. 💡 Tips to Stay Up to Date on New Features - Follow Search Atlas product announcements and release notes for the latest feature updates. - Check the Search Atlas blog and webinar library where new dashboards are often previewed before a full release. - Review your plan regularly to ensure it includes the tools your workflow requires. 🛠️ 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.

📊 Understanding Site Score Drops and Traffic Discrepancies

🔍 Overview If your Search Atlas site score has dropped significantly or your reported visitor numbers look very different from what you see in Google Search Console (GSC), you are not alone. These discrepancies are common and almost always have a clear technical explanation. This article walks you through the most likely causes and what you can do about them. ⚙️ How Search Atlas Calculates Your Site Score Your site score in Search Atlas is a composite metric based on several data points pulled at the time of analysis, including: - Crawl health – broken links, redirect chains, missing meta tags, and indexability issues - Backlink profile strength – the quality and quantity of referring domains - Keyword rankings – positions tracked for your target keywords - On-page SEO signals – content quality indicators detected during the latest crawl Because these inputs are dynamic, your score can shift even if you have not made any direct changes to your site. 📉 Common Reasons for a Sudden Score Drop A dramatic drop — for example, from the low 90s to the 40s — is usually triggered by one or more of the following: - Data source refresh: Search Atlas periodically re-indexes its backlink database and ranking data. A refresh can surface newly lost backlinks or ranking drops that were not captured in the previous snapshot. - Lost referring domains: If sites that previously linked to you have removed those links or gone offline, your backlink score component will fall sharply. - Crawl errors detected: A new crawl may reveal technical issues — such as pages returning 404 errors, a misconfigured robots.txt, or a temporarily unavailable sitemap — that reduce your crawl health score. - Ranking volatility: Google algorithm updates can move your tracked keywords out of the top positions, which directly affects the ranking component of your score. - Index coverage changes: If Google has de-indexed some of your pages since the last analysis, Search Atlas will reflect that in the score. 📊 Why Traffic Numbers Differ Between Search Atlas and GSC Search Atlas estimated traffic is based on keyword rank positions multiplied by average click-through rate (CTR) models — it is a projection, not a direct measurement. Google Search Console, on the other hand, reports actual clicks delivered to your site. This means the two numbers will rarely match exactly, and that is expected. Key reasons for differences include: - Keyword sampling: Search Atlas tracks the keywords you have added to your project. If high-traffic keywords are not in your tracked list, that traffic will not appear in the estimate. - CTR model variations: Estimated traffic uses industry-average CTR curves by position. Your actual CTR may be higher or lower depending on your brand strength, rich snippets, and SERP features. - Data freshness windows: GSC data is updated daily. Search Atlas ranking data is refreshed on a scheduled crawl cycle, so there can be a lag between real-world changes and what is reflected in the platform. - Branded vs. non-branded splits: GSC captures all queries including branded searches. Search Atlas estimates are typically focused on the non-branded keywords in your tracker. 🛠️ Steps to Investigate and Resolve the Issue 1. Check your tracked keywords: Go to Left sidebar → Keywords → Rank Tracker and confirm that your most important keywords are included. Missing keywords mean missing traffic estimates. 2. Review your backlink profile: In Left sidebar → Site Metrics → Backlinks, open your site's backlink overview and filter by recently lost referring domains to see if link losses are driving the score drop. 3. Run a new site crawl: Trigger a fresh crawl from your Site Explorer dashboard to get the most current health data. Look at the crawl error report to identify any newly detected technical issues. 4. Cross-reference GSC data: Compare your GSC performance report date ranges with the Search Atlas snapshot dates. Make sure you are comparing the same time periods before drawing conclusions. 5. Check for algorithm update timing: Search public SEO news sources to see if a Google core update or algorithm change occurred around the date your score dropped. This context is important for understanding ranking shifts. 6. Verify OTTO SEO automation settings: If you are using OTTO SEO (Left sidebar → OTTO SEO → SEO Automation), confirm that automated optimisations are applied correctly and that no conflicting rules were introduced. 💡 When to Be Concerned vs. When to Wait Not every score drop requires immediate action. Use this guidance to decide your next step: - Wait and monitor if the drop coincided with a known data refresh cycle or a Google update — scores often stabilise within one to two weeks. - Investigate immediately if GSC also shows a confirmed drop in clicks and impressions during the same period, which would indicate a real-world ranking or indexing problem rather than a data discrepancy. - Audit your backlinks if the drop is isolated to your authority or backlink score component without a corresponding drop in GSC clicks. 🤝 Need More Help? If you have worked through the steps above and your site score still looks incorrect, or if you believe there may be a technical issue with your account data, 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.

🔗 Third-Party Integration Requests Outside Search Atlas

🧭 Overview Search Atlas is an all-in-one SEO platform built to help you research keywords, track rankings, manage local listings, and publish content — all from a single dashboard. While we are continuously expanding our feature set, some requests involve third-party platforms or workflows that fall outside the current scope of Search Atlas. A common example is porting press releases from a tool like Signal Genesys into Search Atlas or setting up media rooms for separate business entities within the platform. This article explains what is currently supported, what is not, and how to work effectively within Search Atlas for similar use cases. ✅ What Search Atlas Currently Supports Search Atlas offers a growing set of tools that can handle many content publishing and local media needs natively. Here is what is available today: - Content Publishing: Create, optimise, and publish SEO content directly within the platform using the built-in content editor and AI writing tools. - Media Library: Upload and manage media assets for your local projects by navigating to Left sidebar → Local → Media Library. - Local Posts: Publish posts to your Google Business Profile listings by navigating to Left sidebar → Local → Posts. - Local Citations: Build and manage local citations for your business entities via Left sidebar → Local → Local Citations. - Multi-location Support: Manage multiple business entities and locations under a single Search Atlas account using GBP projects at Left sidebar → GBP Projects. - Rank Tracking: Monitor keyword performance across entities via Left sidebar → Keywords → Rank Tracker. 🚫 What Falls Outside Search Atlas Scope The following requests are currently outside the scope of what Search Atlas supports: - Direct integrations with Signal Genesys or other press release distribution platforms: Search Atlas does not have a native connector to import, sync, or manage content from Signal Genesys or similar third-party PR tools. - Dedicated media room pages for separate entities: Search Atlas does not currently offer a standalone media room feature where press releases, brand assets, and media contacts are hosted for individual business entities. - Automated porting of press release content: Bulk importing formatted press releases from external platforms into Search Atlas is not supported at this time. 💡 Recommended Workarounds Even though direct integration is not available, you can still achieve similar outcomes using tools already inside Search Atlas: 1. Manually repurpose press release content: Copy your press release text from Signal Genesys and paste it into the Search Atlas content editor. From there you can optimise it for SEO, adjust headings, and publish or export it as needed. 2. Use the Media Library for brand assets: Navigate to Left sidebar → Local → Media Library to upload logos, images, and media files associated with each business entity. Organise assets per project to keep entities separate. 3. Create entity-specific GBP projects: Set up a dedicated GBP project for each business entity under Left sidebar → GBP Projects. This allows you to manage posts, citations, and reviews independently per entity. 4. Publish news updates as Local Posts: For press release-style announcements, use Left sidebar → Local → Posts to publish updates directly to each entity's Google Business Profile, keeping audiences informed without needing a separate media room. 5. Track visibility of published content: After publishing, monitor keyword rankings and organic visibility for each entity via Left sidebar → Keywords → Rank Tracker. 🗺️ Submitting a Feature Request Search Atlas is actively developed based on customer feedback. If a third-party integration or a feature like media rooms is important to your workflow, we encourage you to submit a feature request. Your feedback directly influences the product roadmap. To submit a request, open the chat widget in the bottom-right corner of the platform and describe the integration or feature you need. Our team logs all feature requests and reviews them regularly. 🛠️ 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.

🎙️ Setting Up Your Brand Voice & Tone Profile

🎯 What Is a Brand Voice & Tone Profile? A Brand Voice & Tone Profile tells Search Atlas how your brand communicates — its personality, style, and language preferences. Once set up, this profile guides AI-generated content to match your unique voice across every piece of content you create. 🛠️ How to Create a Brand Voice Profile 1. Log in to your Search Atlas account and navigate to Brand Vault from the Header (apps-grid icon) → More Features → Brand Vault. 2. Click Create New Brand Voice or select an existing brand to add a voice profile to. 3. Choose between two setup modes: - Guided Mode — Answer a short series of questions about your brand's personality, audience, and communication style. Search Atlas uses your answers to build a voice profile automatically. - Custom Mode — Manually define your tone attributes, preferred vocabulary, and writing style guidelines in freeform fields. 4. Fill in all required fields. The more detail you provide, the more accurately the AI will reflect your brand. 5. Click Save Brand Voice to store your profile. ✍️ Tips for a Strong Brand Voice Profile - Be specific about tone: Instead of "professional," try "confident and approachable, like a trusted advisor." - Add example phrases or sentences your brand commonly uses — this helps the AI match your existing content. - List words or phrases to avoid to prevent off-brand language in generated content. - Define your audience clearly so the tone resonates with the right readers. 🔍 How to Apply Your Brand Voice to Content Once your Brand Voice profile is saved, it becomes available as a selectable option inside Search Atlas content tools. When creating or editing content, go to Content → Content Genius (or Topical Maps/Content Planner) and look for the Brand Vault dropdown and select your profile. The AI will automatically adjust its output to match your defined tone and style. ⚠️ Troubleshooting: Buffering or Loading Issues If Search Atlas is showing continuous buffering while setting up or using your Brand Voice profile, try the following steps: 1. Refresh the page — A simple reload resolves most temporary loading issues. 2. Clear your browser cache and cookies — Cached data can sometimes interfere with platform performance. 3. Switch browsers — Search Atlas works best on the latest versions of Google Chrome or Mozilla Firefox. 4. Check your internet connection — A slow or unstable connection can cause buffering inside the platform. 5. Disable browser extensions — Ad blockers or privacy extensions occasionally block platform features. Try disabling them temporarily. 6. If the issue persists after all of the above, note the exact step where buffering occurs and contact our support team (see below). 💡 Frequently Asked Questions - Can I create multiple Brand Voice profiles? Yes. You can create a separate profile for each brand or client inside Brand Vault. - Can I edit a saved Brand Voice profile? Yes. Open Brand Vault, select the profile, make your changes, and save. - Why does the preview text look generic? Preview text personalisation is actively being improved. If your preview does not yet reflect your brand specifics, the full voice profile will still apply correctly when generating real content. 💬 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.

📊 Why Your Content, Authority, and UX Scores Aren't Improving

Overview Inside Search Atlas, your SEO health is measured across four pillars: Technical, Content, Authority, and UX Signals. A common point of confusion is why Content, Authority, and UX Signals scores stay flat even when you are actively working on those areas. The key distinction is that these three pillar scores are tied to your usage of Search Atlas tools rather than to work done outside the platform. How Each Pillar Is Measured Understanding what drives each score helps you take the right action in the right place. - Technical — This pillar reflects the health of your live website as measured by a direct crawl. Improvements you make to your site can be reflected here. - Content — This pillar is tied to your use of content-related tools within Search Atlas, such as the Content Editor, Topic Research, and On-Page SEO tools. To see movement in this score, incorporate these tools into your workflow. - Authority — This pillar is tied to your use of authority-building tools within Search Atlas, such as the Backlink Analysis and Link Building tools. Activity with these platform tools is what drives this score. - UX Signals — This pillar is tied to your use of relevant Search Atlas tools connected to user experience optimization, such as the Site Audit and Page Speed analysis tools. Engaging with these tools within the platform is what moves this score. Why This Distinction Matters Many customers do significant SEO work across multiple platforms and workflows. That work is valuable for your website, but the Content, Authority, and UX Signals pillar scores specifically measure activity taking place within Search Atlas tools. The platform tracks and verifies actions taken inside it, which is why these three scores respond to in-platform usage. Technical is the exception because it is measured by crawling your live site directly, so improvements you make to your site are reflected in that score regardless of where the work was done. How to Improve Each Score To improve your Content score: 1. Navigate to the Content section in your Search Atlas dashboard sidebar. 2. Open the Content Editor to create and optimize articles directly within the platform. 3. Use Topic Research to discover relevant keywords and topics before writing. 4. Run On-Page SEO analysis on your pages to get actionable recommendations. 5. Publish or save optimized content through the platform on a regular basis so your activity is tracked consistently. 6. Check your Content pillar score under Site Metrics → Site Explorer (Organic Research) → Holistic SEO Pillars over the following weeks to see the impact of your in-platform usage. To improve your Authority score: 1. Navigate via the header apps-grid icon → More Features → Backlinks (Backlink Research) in Search Atlas. 2. Use Backlink Analysis to review your current backlink profile and identify new link opportunities. 3. Track competitor backlinks through the platform to find outreach targets. 4. Log link-building activity and outreach within Search Atlas tools on a regular basis. 5. Check your Authority pillar score under Site Metrics → Site Explorer (Organic Research) → Holistic SEO Pillars periodically to track progress. To improve your UX Signals score: 1. Navigate to the Site Audit or Diagnostics section in your Search Atlas dashboard sidebar. 2. Run a full Site Audit to identify UX-related issues such as mobile usability, page speed, and Core Web Vitals problems. 3. Use the Page Speed tool to analyze specific pages and follow the platform's recommendations. 4. Re-run audits after making changes so the platform records your ongoing activity. 5. Check your UX Signals pillar score under Site Metrics → Site Explorer (Organic Research) → Holistic SEO Pillars periodically to track progress. Need Help? If you have been actively using the relevant Search Atlas tools and your pillar scores are still not moving, our team can investigate your account. Please have ready: your project name, the specific pillar score affected, the tools you have been using, and approximate dates of activity. 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.

🔗 Access the Search Atlas Knowledge Base

🌐 The Correct Knowledge Base URL The official Search Atlas Knowledge Base is located at: https://help.searchatlas.com/en/ If you have bookmarked or been directed to any other URL — such as https://intercom.help/search-atlas/en/collections/10864692-knowledge-base — that link is outdated and will return a page doesn't exist error. Please update your bookmark to the address above. 🔍 What You Can Find in the Knowledge Base The Search Atlas help center covers all major features and workflows, including: - Getting started guides and account setup - Content tools: Blog Writer, Content Genius, and more - SEO research: Site Auditor, Keyword Researcher, and Rank Tracker - Authority tools: Cloud Stacks, URL Indexer, QUEST LLM Visibility, Campaigns, Inbox, and Sent - Billing, team management, and integrations 🛠️ Troubleshooting Access Problems If you are still unable to reach the knowledge base after using the correct URL, try the following steps: 1. Clear your browser cache and cookies, then reload the page. 2. Try a different browser (Chrome, Firefox, or Edge are recommended). 3. Disable browser extensions such as ad blockers or privacy tools that may interfere with page loading. 4. Check your internet connection and confirm other websites load normally. 5. Try opening the link in a private or incognito window to rule out cached data issues. If none of the steps above resolve the issue, the help center may be temporarily unavailable. Wait a few minutes and try again. 💡 Tips for Finding Articles Quickly Once you are on the knowledge base at https://help.searchatlas.com/en/: - Use the search bar at the top of the page to enter keywords related to your question. - Browse by category to explore articles grouped by feature area. - Check the Getting Started section if you are new to the platform. 🤝 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.

🎓 Manick's SEO Course — Early Q3 Release

🗓️ Release Window Manick's new SEO course is scheduled to launch in early Q3 (July–August). We will notify all Search Atlas users via in-platform announcement and email as soon as the course goes live. No action is needed on your end — you will be informed automatically. 📚 What the Course Covers This course is designed to help marketers, agency owners, and SEO professionals get more value from Search Atlas and sharpen their overall SEO strategy. Expect in-depth lessons on: - Core SEO principles and best practices - Keyword research and topical authority building - On-page optimisation techniques - Link building strategies - Using Search Atlas tools to execute and track SEO campaigns Specific module details and the full curriculum will be published at launch. 👤 About Manick Manick Bhan is the founder and CEO of Search Atlas. He brings extensive hands-on SEO experience to this course, drawing on real-world strategies used to grow Search Atlas and help customers achieve top rankings. The course reflects his practical, results-driven approach to search engine optimisation. 🔔 How to Stay Updated You do not need to sign up separately. Updates about the course release will be shared through the following channels: - In-platform notifications — watch for the announcement banner inside Search Atlas - Email — sent to the address associated with your Search Atlas account - Search Atlas blog — release notes and course details will be published there If you have not received any notifications and believe the course has already launched, check your spam or promotions folder, then log in to Search Atlas and navigate to the apps-grid icon (More Features) in the header → Help → Explore Training Calls. ❓ Frequently Asked Questions - Is the course free? Pricing details will be confirmed at launch. We will include that information in the release announcement. - Will the course be self-paced? Yes, the course is expected to be available on demand so you can complete it at your own pace. - Do I need a specific Search Atlas plan to access it? Access details will be outlined in the launch announcement. All plan types will be considered. - Can I request a topic to be covered? You are welcome to share feedback or topic requests via the chat widget inside the platform. 🆘 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.

🔍 Why Search Atlas SEO Scores Differ From AISEO

📌 Overview If you previously tracked your SEO performance using AISEO and noticed your scores look different inside Search Atlas, you are not alone. This article explains why those scores differ and how to interpret your Search Atlas score with confidence. 🔍 Why the Scores Look Different Search Atlas and AISEO use different methodologies, data sources, and grading scales to calculate SEO scores. A score of 80%–90% in AISEO does not map directly to the same percentage in Search Atlas — they are measuring different things. Because each tool applies its own internal logic and benchmarks, scores are not directly comparable between the two platforms. ✅ Which Score Should You Trust? Search Atlas is your primary source of truth for SEO performance within the platform. A lower Search Atlas score compared to AISEO does not necessarily mean your SEO has gotten worse — it reflects that the two tools are answering different questions using different scoring approaches. Focus on tracking your Search Atlas score over time rather than comparing it to your previous AISEO scores. 🛠️ What to Do If Your Score Seems Unexpectedly Low If your Search Atlas score appears much lower than expected, here are concrete steps you can take to understand and improve it: 1. Log in to Search Atlas and open your project to review your current score and any details surfaced by the platform. 2. Review the recommendations provided. Understanding the specific recommendations provided within Search Atlas tells you exactly where to focus your effort. 3. Look at the details provided for your site rather than focusing solely on the score itself. Addressing the specific items highlighted by the tool will help produce meaningful improvements. 4. Prioritize high-impact fixes first. Address critical issues highlighted by the platform before moving on to minor optimizations. Each resolved issue will move your overall score upward. 5. Re-run your audit after making changes to confirm your score is trending upward. Because Search Atlas uses its own benchmarks, comparing your new Search Atlas score to your previous Search Atlas score — not your AISEO score — is the only meaningful way to measure progress. 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 — Dashboard & Navigation Issues

Use this guide to diagnose and fix login failures, blank pages, unexpected logouts, locked features, and UI display problems in the Search Atlas dashboard. 🔐 Error 1: Login form doesn't respond when I click Sign In What's happening: A browser extension or cache issue is blocking the login process. Steps to try: - Hard-refresh the page. - Disable browser extensions (ad blockers, privacy tools, password managers) and try again. - Try an incognito window. - Clear cookies and cache for dashboard.searchatlas.com. - Use the Forgot Password link to reset credentials if the form consistently won't submit. 🔄 Error 2: Logged out unexpectedly in the middle of working What's happening: Your session expired or was reset due to a network interruption. Steps to try: - Log back in — your saved work is not lost. - Check that your browser doesn't clear cookies when it closes. - Ensure your browser allows cookies from searchatlas.com. - If this happens frequently, contact support — it may indicate a session configuration issue. 🔒 Error 3: A feature I expect is locked or shows an upgrade prompt What's happening: Either the feature isn't included in your plan or your account needs a session refresh after a recent upgrade. Steps to try: - Log out and log back in — plan changes require a fresh session. - Check your plan features: Click your avatar (top-right corner) → Billing (Plans & Top-ups). - Wait 10 minutes after upgrading — activation has a short delay. - If your plan shows the feature but it's still locked, contact support with a screenshot. ⚪ Error 4: Page loads blank — only white space visible What's happening: A JavaScript bundle failed to load, often triggered by a browser extension or stale cache. Steps to try: - Hard-refresh: Ctrl + Shift + R / Cmd + Shift + R. - Open in incognito mode. - Clear browser cache and reload. - Try Chrome — it's the most compatible browser for the platform. - Contact support if blank pages occur consistently across browsers. Note: If the blank screen appears specifically inside Website Builder and is accompanied by a persistent "making changes" spinner, this may indicate a platform-level issue rather than a browser-side problem. Contact support immediately with your project URL so the team can investigate server-side — support has a dedicated escalation path for Website Builder-specific blank-page incidents. ⚠️ Error 5: After a recent browser update, parts of the UI are broken What's happening: Browser updates occasionally break JavaScript rendering for complex web apps. Steps to try: - Hard-refresh to reload all JavaScript assets. - Clear full browser cache (not just cookies). - Disable recently updated extensions. - Try in a different browser to confirm it's browser-specific. - Check if the issue resolves itself after 24 hours — our team deploys compatibility fixes quickly. 🔔 Error 6: Notification or alert banners won't dismiss What's happening: The dismiss button's click handler failed, usually due to a JavaScript error. Steps to try: - Hard-refresh the page — the banner usually won't reappear. - If the banner is blocking important UI, use browser zoom-out (Ctrl + -) to see around it temporarily. - Log out and back in. - Report it to support with a screenshot — include the banner text so we can identify the source. 🔀 Error 7: Data from one project appearing in another project's view What's happening: A rare caching issue is mixing project data. Affects dashboard widgets and reports. Steps to try: - Hard-refresh the page immediately. - Log out and log back in to clear any cross-project session data. - Navigate directly to the correct project via Left Sidebar → OTTO SEO → All Sites → [Your Project Name]. - Contact support immediately — this is a data isolation issue we prioritize. 👥 Error 8: Team member can't access the account after being invited What's happening: The invite may have expired, gone to spam, or the seat limit was reached. Steps to try: - Go to Top-right Corner Avatar → Settings → Team Members (Pending Invites) and resend the invite. - Have the teammate check their spam folder. - Confirm your plan allows the number of seats you're trying to fill: Click your avatar (top-right corner) → Billing (Plans & Top-ups). - After the teammate accepts the invite, have them log out and back in to refresh permissions. - Contact support if the accepted invite shows no access — include the teammate's email address. 🌀 Most dashboard and navigation issues trace back to browser cache, extensions, session timeouts, or permission mismatches — not system failures. Work through the steps for your specific error above, and contact support if the problem persists.

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

🔍 How to Find Your Previous Chat History

This article explains what to do if you cannot locate a previous chat session inside the platform. If you have not deleted any chats but cannot find a recent conversation, follow the steps below. 🛠️ Step-by-Step 1. Open the tool where the chat took place. Navigate to the same area of the platform you were using when the conversation occurred and look for any history or session list within that tool's interface. 2. Check that you are logged into the correct account and workspace. If you belong to more than one workspace or have multiple accounts, confirm that the workspace currently shown matches the one you were using when the chat occurred. Chat history may not be visible if you are viewing a different workspace. 3. Scroll through any available session list. Older sessions may not appear at the very top. Scroll down within whatever session list is available to see if earlier conversations are listed further down. 4. If you still cannot find the session, contact support. The platform's support team can look into your account directly and advise whether the session was saved. Before reaching out, note the approximate date and time of the missing conversation and the area of the platform where it took place, as this will help the team locate it faster. ✅ How to Confirm It Worked You have successfully located your chat history when you can see a list of past sessions inside the tool you used and can open the conversation you were looking for. If you are unable to find the session after completing every step above, reach out to our support team with the details noted in step 4. 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.

🔒 Using Search Atlas With Agency-Managed Websites

🧭 Overview If your website is managed by a third-party marketing agency, you may be concerned about Search Atlas tools automatically making permanent changes without your approval. This article clarifies exactly which tools are diagnostic and read-only, which tools can execute changes, and how to safely review everything before your agency touches a single line of code. 📋 Understanding Tool Modes in Search Atlas Search Atlas tools fall into two categories: diagnostic (read-only) tools that only collect and display data, and execution tools that can apply changes to your site. Neither category makes changes automatically — execution tools always require a deliberate action from you first. - Diagnostic tools analyse your site and surface recommendations. They never modify your website. - Execution tools (such as OTTO SEO) can apply optimisations, but only after you review and explicitly approve them. No Search Atlas tool will silently push permanent changes to a live website. Every action that affects your site requires a manual trigger from an authenticated user inside the platform. 🔍 Diagnostic and Read-Only Tools The following tools are entirely read-only and safe to use on any website, including those managed by a third party. They surface data and recommendations but never write to your site. - Site Metrics — Access via Left sidebar → Site Explorer. Analyses your domain's SEO performance, backlinks, and traffic estimates. No changes are made to your site. - Keyword Magic — Access via Left sidebar → Keywords → Keyword Magic. Discovers keyword opportunities. Read-only. - Rank Tracker — Access via Left sidebar → Keywords → Rank Tracker. Monitors keyword ranking positions over time. Read-only. - Keyword Gap — Access via Left sidebar → Keywords → Keyword Gap. Compares your keyword coverage against competitors. Read-only. - Local tools — Access via Left sidebar → Local → GBP Projects. Sections including Overview, Media Library, My Tasks, Posts, Reviews, and Local Citations provide data and task management for your Google Business Profile. Changes to your GBP listing only occur when you explicitly publish or submit content within these sections. ⚙️ OTTO SEO: How Execution Works OTTO SEO is Search Atlas's AI-powered SEO automation tool. It is important to understand how OTTO applies changes before connecting it to any website managed by a third party. - OTTO generates a list of recommended SEO fixes based on a site audit. These appear as pending recommendations in your OTTO dashboard. - Recommendations are not applied automatically. You must review each one and choose to deploy it. - When you do deploy a recommendation, OTTO applies it through your connected CMS (for example, WordPress via a plugin). OTTO does not inject persistent JavaScript onto your site by itself — changes go through your CMS integration and are stored in your CMS database, just like a manual edit would be. - You can revert individual changes from the OTTO dashboard if you need to undo something after deployment. Important: Search Atlas does not use a JavaScript snippet to silently override your live site's content. Any claim that changes are applied via a temporary front-end JavaScript layer should be disregarded — changes made through OTTO are real CMS edits and should be treated as such. ✅ Recommended Workflow for Agency-Managed Sites Follow these steps to safely use Search Atlas alongside a third-party marketing agency. 1. Start with diagnostic tools only. Run a full site audit and review keyword and rank data using Site Metrics, Keyword Magic, Rank Tracker, and Keyword Gap. None of these require CMS access or affect your live site. 2. Review OTTO recommendations before connecting your CMS. You can connect your site to OTTO and let it generate recommendations without deploying anything. Review the full list of suggested fixes in the OTTO dashboard. 3. Export or share recommendations with your agency. Share the recommended fixes with your marketing agency for their review before any deployment. This keeps your agency informed and in control of their own workflow. 4. Agree on a deployment plan. Decide with your agency which recommendations they will implement manually and which, if any, you will deploy through OTTO. Avoid duplicate work. 5. Deploy in stages. If you choose to deploy through OTTO, apply changes in small batches so your agency can verify each update on the live site before the next batch is applied. 6. Use the revert option if needed. If any deployed change conflicts with your agency's work, revert it from the OTTO dashboard and notify your agency so they can implement the fix their preferred way. 💬 Key Points to Share With Your Agency - Search Atlas tools do not automatically modify a live website. - All execution actions require a logged-in user to manually approve and trigger them. - OTTO changes are applied through the CMS, not through an invisible front-end layer, so they are fully visible in your CMS edit history. - Your agency retains full control of the CMS and can review, edit, or revert any change OTTO has made directly in WordPress or whichever CMS you use. 🆘 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.

💬 How to Close a Test Chat Conversation

🔍 What Happened? If you were testing the live chat widget inside the Search Atlas platform and your conversation was accidentally escalated to a support teammate, don't worry — this is a common occurrence. When certain keywords or actions are triggered during a test, the system may automatically route the conversation to a human agent. This article explains what to expect, how the conversation gets closed, and how to avoid accidental escalations during future tests. ⚙️ Why Did My Test Get Escalated? The chat widget is designed to detect when a customer needs human support. The following actions can trigger an automatic escalation: - Typing phrases like human teammate, agent, or help - Sending multiple messages in quick succession - Interacting with certain bot prompts that are mapped to escalation flows Because these triggers are intentional safety features, even a test conversation can be routed to a live teammate if any of these conditions are met. ✅ How to Close an Accidentally Escalated Conversation If your test conversation was escalated and you need it closed, follow these steps: 1. Open the chat widget in the bottom-right corner of the platform. 2. Type a short message explaining that this was a test, for example: "This was a test conversation — please close this chat." 3. A teammate will acknowledge your message and close the conversation on their end. 4. You will receive a confirmation once the conversation has been marked as resolved. There is no negative impact on your account when a test conversation is escalated. Our team is happy to close it for you without any follow-up required. 🛠️ How to Avoid Accidental Escalations When Testing If you need to explore the chat widget's behaviour without triggering a live escalation, keep the following tips in mind: - Avoid escalation keywords — do not type phrases like human teammate, talk to someone, or agent during a test. - Keep messages neutral — use placeholder text that does not match any escalation triggers. - Test during off-peak hours — if an accidental escalation does occur, our team will still respond, but off-peak times may reduce any confusion. - Notify the team in advance — if you plan to run a structured test, let a teammate know beforehand so they can monitor without escalating. ❓ Frequently Asked Questions Will this affect my account or support history? No. Accidental test conversations are noted and closed without any impact to your account standing or support metrics. Can I delete the test conversation from my history? Conversation history is managed by our support team. If you would like a test conversation removed from your record, simply ask a teammate when requesting the closure. What if the chat widget is not responding? Try refreshing the page. If the issue persists, the widget may be temporarily unavailable. Wait a few minutes and try again. 💬 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.

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

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

🔧 Troubleshooting Invalid Order on Upsell Packs

If you're seeing an "invalid order" error when trying to add an upsell pack (such as the Search Secrets pack for $97), the issue is almost always a mismatch between your current subscription state and the pack requirements. This guide walks you through the exact details our support team needs to resolve it quickly. 🔍 Common Causes - Subscription tier incompatibility: The pack may require a specific plan level. - Existing active pack: You may already have the pack or a conflicting add-on on your account. - Payment method issue: Your card on file may be expired or declined. - Proration conflict: A mid-cycle billing change is failing to calculate correctly. 🛠️ Step-by-Step 1. Capture the exact error message: Take a screenshot or copy the full text of the error, including any order or reference number displayed. The exact wording helps our team identify the root cause. 2. Check your current subscription: Review your current plan details from the top-right avatar → Billing (Plans & Top-ups tab) to confirm which tier you're on. 3. Verify your payment method: Within your billing area, confirm your card is valid, not expired, and has sufficient funds for the $97 charge. 4. Clear cache and retry: Hard-refresh the page (Ctrl+F5 or Cmd+Shift+R), then attempt the purchase one more time to rule out a session or caching issue. 5. Escalate with full details: If the error persists, contact support (below) and include: the exact error message text, your current plan name, the name of the pack you're trying to add, and a timestamp of the attempt. ✅ How to Confirm It Worked Once the order processes successfully, you should see a confirmation screen with an order number and a successful payment receipt emailed to your account address. Additionally, when you return to Billing (via the top-right avatar), the upsell pack (e.g., Search Secrets) should appear as an active add-on under your subscription or billing details. If neither of these happens, the order did not go through. 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.

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

⚡ Acting on Search Atlas Audit Recommendations

Overview When Search Atlas audits your site or local presence, it surfaces a prioritised list of recommendations. Each recommendation maps to a specific tool inside the platform. This article explains the five most common audit recommendation areas and how to act on each one. Keyword Filtering and Exporting If your audit recommends refining your keyword strategy, the Keyword Manager is your starting point. Navigate to the keyword management area of the platform, where you can filter keywords by metrics such as search volume, keyword difficulty, intent, or CPC. Once you have narrowed down the view you need, use the export option to download your filtered list as a CSV file. Exported keyword lists can be shared with your content team or imported into other tools for further planning. Organising Keywords into Clusters Audit recommendations around content gaps or topical authority often point to keyword clustering. Clusters group related keywords so you can plan content that covers an entire topic rather than individual terms. Inside the keyword management area, select the keywords you want to group and use the clustering feature to organise them — either manually or by letting Search Atlas group them by semantic similarity. Assign the resulting cluster to a project or content brief. Working from clusters helps you avoid keyword cannibalism and ensures each page you create serves a clear topical purpose. Enabling FAQ and HowTo Schema Markup If your audit flags missing structured data, you can add FAQ or HowTo schema directly from your OTTO project without editing any code. Navigate to OTTO SEO → All Sites → [your project] → Overview → Onpage Optimizations (OTTO Grader) and look for the schema markup options. Select the relevant pages, choose the schema type you need, fill in the required fields — questions and answers for FAQ, or ordered steps for HowTo — and apply the changes. Once deployed, you can verify the schema using Google's Rich Results Test to confirm eligibility for enhanced search features. Setting Up Directory Listings Audit recommendations related to local visibility often include expanding your presence across business directories. Search Atlas manages this under the Local section of the platform. Open your local project and look for the directory or listings management area, where you can connect to and sync your business information across major directories. Keeping your Name, Address, and Phone number (NAP) consistent across directories is critical for local search rankings. Building Local Citations and Authority Beyond directory listings, your audit may recommend building local citations to strengthen authority. Inside your local project, look for citation-building options that allow you to submit or manage your business profile across additional platforms. Prioritise directories and platforms that are relevant to your industry and location for the greatest impact on local authority. 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.

🔍 Identifying Search Atlas Dynamic Optimization Code Snippet

🧩 Overview If you notice an unfamiliar script on your website and want to know whether it belongs to Search Atlas, this article explains exactly what to look for. The Search Atlas dynamic optimization snippet has specific, identifiable markers that make it easy to confirm at a glance — no login or account details required. 🔎 Key Identifiers of the Search Atlas Snippet The Search Atlas dynamic optimization script contains three reliable signatures. If all three are present, the code belongs to Search Atlas. - Element ID: The script tag includes the attribute id='sa-dynamic-optimization'. This unique ID is only assigned by Search Atlas and will not appear in third-party scripts. - Domain reference: The snippet loads resources from or communicates with the domain dashboard.atlascoremarketing.com. Look for this domain in the src attribute or within the script body. - Base64-encoded loader pattern: The snippet uses a base64-encoded string to load its core script. You will see a long string of characters using only letters, numbers, +, /, and = padding — this is the encoded loader. It is typically assigned to a variable or passed directly into a script initialisation call. 📋 How to Locate the Snippet on Your Website 1. Open your website in a browser and right-click anywhere on the page, then select View Page Source or Inspect. 2. Press Ctrl + F (Windows) or Cmd + F (Mac) to open the search bar within the source view. 3. Search for sa-dynamic-optimization. If the snippet is present, this term will highlight immediately. 4. Confirm the surrounding code also references dashboard.atlascoremarketing.com and contains a base64-encoded string as described above. 5. If all three identifiers are present, the script belongs to Search Atlas dynamic optimization. ✅ Quick Reference: What the Snippet Looks Like Below is a summary of the three markers to check side by side: - **id attribute:**id='sa-dynamic-optimization' - **Domain:**dashboard.atlascoremarketing.com - Loader format: A base64-encoded string (long alphanumeric sequence ending in one or two = characters) You only need to find one of these to begin your investigation, but all three will be present in a legitimate Search Atlas snippet. If any identifier is missing or the domain is different, the script may belong to another service. ⚠️ What If the Script Does Not Match These Identifiers? If the script on your site does not include id='sa-dynamic-optimization', does not reference dashboard.atlascoremarketing.com, and does not contain a base64-encoded loader, it is not a Search Atlas dynamic optimization snippet. In that case, check with your developer or review your tag manager to identify the service that injected it. 🗑️ Removing or Managing the Snippet If you have confirmed the snippet belongs to Search Atlas and wish to manage or remove it, the setting is controlled from within your Search Atlas dashboard. Changes to dynamic optimization are applied at the account level and will reflect on your site after the next page load. If you are unsure which setting controls the snippet, your developer or the Search Atlas support team can point you to the right location. 💬 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.

🛠️ Handling Unspecified Technical Issues Effectively

🎯 Why Describing Your Issue Matters When you reach out for support, the more clearly you describe your problem, the faster our team can identify the root cause and provide a solution. Vague or incomplete descriptions — even when escalated to a human teammate — can lead to delays, repeated back-and-forth, and conversations that end without resolution. This article walks you through how to identify and communicate your technical issue effectively before or during a support conversation. 🧩 Common Reasons a Problem Goes Unresolved - The issue was not described beyond a general feeling that something is wrong. - Only a term or concept was asked about (for example, asking what a CMS is) without connecting it to the actual problem being experienced. - The conversation moved to agent escalation before the core issue was identified. - No specific feature, page, or action was mentioned. If any of these sound familiar, the steps below will help you reframe your request so it leads to a real resolution. 🔍 How to Identify Your Underlying Issue Before contacting support or requesting a human teammate, take a moment to answer these questions: 1. What were you trying to do? For example: publishing content, connecting a CMS, running an automation, or reviewing a report. 2. What happened instead? Describe the unexpected result — an error message, missing data, a button that did not respond, or a feature that behaved differently than expected. 3. Where in the platform did it happen? Note the specific section. For example, OTTO SEO is accessed from the left sidebar under OTTO SEO → All Sites (SEO Automation) at the URL /seo-automation-v3. 4. When did it start? Was this the first time you tried this action, or did it work before? 5. What have you already tried? Refreshing the page, reconnecting an integration, retrying a step — include anything you attempted. 💬 What to Say When You Request an Agent When you open the chat widget and type human teammate, it helps our team enormously if you lead with a brief summary of your issue. Use this simple format: - I was trying to: [describe the action] - What happened: [describe the unexpected result or error] - Where: [name the feature or section, e.g. OTTO SEO, Site Auditor, Link Builder] - What I already tried: [any steps you already took] Example: "I was trying to publish an AI-generated article from the OTTO SEO section, but the publish button is greyed out and nothing happens when I click it. I refreshed the page and retried, but the issue persists." This level of detail allows our teammate to jump straight into troubleshooting rather than spending time gathering basic information. 📖 A Note on Definitions vs. Technical Problems Our support team is here to solve problems inside the Search Atlas platform. If you ask about a general concept — such as what a CMS (Content Management System) is — that is a helpful starting point, but it is not the same as reporting a technical issue. A CMS is any platform used to create, manage, and publish digital content, such as WordPress, Webflow, or Shopify. Search Atlas integrates with CMS platforms to streamline content publishing directly from the platform. If you were asking about a CMS because you are having trouble connecting one to Search Atlas, or because a CMS-related step in a workflow is not working, that is the technical issue worth describing. Sharing that context ensures the conversation moves toward a real fix. ✅ Quick Checklist Before Escalating - I can name the feature or section where the issue occurred. - I can describe what I was trying to do and what happened instead. - I have noted any error messages or unexpected behavior I observed. - I have tried at least one basic troubleshooting step (e.g. refresh, retry, re-login). - I am ready to share my account details if asked. Running through this checklist before or during a chat conversation significantly increases the chance of resolving your issue in a single interaction. 🙋 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.

🏆 How to Publish Trophy Content to a Client Site

This article explains how to connect your trophy content to a client site and publish it successfully. If you have been unable to locate the right section, the steps below will guide you to the exact location and confirm that your content has been published correctly. 📍 Where to Find It Trophy content publishing is managed within the OTTO SEO section of the platform. To get there, navigate to Left sidebar → OTTO SEO → Overview. From the Overview page you can access your connected sites and their associated content publishing options. 🛠️ Step-by-Step 1. In the left sidebar, click OTTO SEO to open the OTTO SEO section. 2. Select Overview from the sub-navigation that appears. 3. Locate the client site you want to publish trophy content to. If the site has not been connected yet, click Create to add a new site, or use Continue installation under Left sidebar → OTTO SEO → Installation Guide to complete the connection for an existing site. 4. Once the site is connected and OTTO is active, click Engage OTTO on the Overview page for that site. 5. Within the site's OTTO dashboard, locate the trophy content you want to publish. Select the piece of content and follow the on-screen prompts to push it to the connected client site. 6. Confirm that the target site's credentials and publishing permissions are correctly configured — if the publish option is greyed out or missing, return to Installation Guide and complete any outstanding installation steps. ✅ How to Confirm It Worked After publishing, verify success by checking the following: - Return to Left sidebar → OTTO SEO → Overview and open the client site. The published content should appear with a status reflecting it has been sent to the site (e.g., a published or live indicator). - Visit the client website directly in a browser and confirm the trophy content is visible on the expected page. - If you use Left sidebar → OTTO SEO → Site Audit → Page Explorer, the newly published page should appear in the page list for that site, confirming it has been indexed by the crawler. 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.

🌙 Does Search Atlas Have Dark Mode?

Dark Mode Is Not Currently Available The Search Atlas dashboard does not have a dark mode at this time. There is no toggle, button, or setting anywhere in the platform that activates a dark theme. Where to Check You may have looked in the following places — none of them contain a dark mode option: - Settings (Avatar → Settings): controls profile, alerts, integrations, and white-label options — no appearance or theme section. - Dashboard toolbar or top navigation: no theme switcher is present. - Account or billing pages: focused on plan and payment management only. Workaround If you prefer a darker interface while using Search Atlas, you can use a browser-level dark mode extension as an unofficial workaround. Third-party extensions are not supported by Search Atlas and may affect how some UI elements are displayed. Feature Requests If dark mode is important to your workflow, you can submit feature requests through our support channel; the team reviews all submissions when planning future updates.

🛠️ Search Atlas Troubleshooting Hub

Search Atlas is a powerful platform built on interconnected systems: SEO data, AI workflows, automation engines, integrations, and real-time insights. When everything is working together, results compound quickly. But when something breaks—or simply doesn’t behave as expected—it can interrupt your workflow, delay outcomes, and create confusion. This troubleshooting hub is designed to eliminate that friction.

📊 Authority Pillar Score Dropped to Zero

🔍 What Happened Some users noticed their Authority pillar score dropping suddenly to 0/100 inside the Holistic SEO Pillars section, even though no changes were made to their site or settings. This was caused by a known bug affecting how the Holistic SEO Pillars calculate and display Authority, Content, and UX scores after a weekly analysis or recrawl. The engineering team has since resolved the underlying issues. 📊 Where to Check Your Score You can view your Holistic SEO Pillars scores by navigating to the Holistic SEO Pillars section of the platform. Your Authority, Content, and UX pillar scores are displayed on this page. If you are still seeing a score of 0, follow the steps below. 🛠️ What to Do If Your Score Still Shows 0 1. Refresh the page. A simple browser refresh can clear a display glitch and load the most current data. 2. Wait and check again. Score calculations can take some time to complete. Allow a few minutes, then reload the page to see if the Authority score has been restored. 3. Check back after the next scheduled analysis. Because the bug was tied to weekly analysis and recrawl processing, scores may update automatically once the next analysis cycle runs. 💡 Why This Happened The bug was triggered during the processing of weekly analysis and recrawl data, causing the Authority pillar score — and in some cases the Content and UX scores — to drop to 0 despite no changes being made to the site. Your data was not lost — the drop was a display and calculation error only. The engineering team has since resolved the underlying issues. ✅ Confirmed Resolution The known bugs causing Authority pillar scores to drop to 0 have been marked as resolved. If your score has returned to its expected range, no further action is needed. 🚀 Still Seeing a Score of 0? If you have followed the steps above and your Authority pillar score remains at 0, this may indicate a separate issue specific to your account or site configuration. If you need further assistance, please reach out to our support team so we can investigate further.

🧠 Search Atlas Troubleshooting Guide (Diagnosis Layer)

This guide helps you identify and understand issues across Search Atlas services. ⚠️ Scope: This article covers diagnosis only — it does not contain resolution steps. Once you have identified the issue category, proceed to the relevant fix guide or escalation path. It answers: - What is happening? - Where is it happening? - Why is it happening? Before fixing anything, this is your diagnosis layer. 🧭 How to Use This Article Use this when: - A user reports an issue - A feature is not behaving as expected - You need to classify the problem before escalating 🛠️ Support Tool Health: The Intercom FIN / Search Atlas Connector instability issue (QP-5196) has been resolved. If FIN responses seem incorrect or incomplete, re-verify connector health before relying on its answers to diagnose customer issues. 🔍 SYSTEM DIAGNOSIS MAP 🧠 Root Categories ⚙️ Infrastructure Failures - Database unavailable - Redis down - Service unreachable - Memory crashes 👉 Symptoms: - 503 errors - Timeouts - Data not loading 👉 Next step: For resolution steps, see the Infrastructure Fix Guide or escalate via the Infrastructure / Platform engineering channel. 🔄 Async / Queue Failures - Celery tasks missing - Jobs stuck or never completed - Crawls not finishing 👉 Symptoms: - Spinners forever - “In progress” stuck - No visible error 📌 Known instance: The Atlas Brain indefinite spinner during analysis (LPS-442) is a confirmed example of this pattern — if you see it, check this category first. Note: this is distinct from the Atlas Brain 'no connection' freeze pattern, where the UI may report a false 'Success' state while the underlying deployment fails (see Atlas Brain / Website Studio section below). Both fall under async/queue failures but have different diagnostic indicators and escalation paths. 📌 Site Audit / OTTO sync note: Site Audit and OTTO now use the QP notify-data-change API (OTTO-2082). If data sync issues appear in these modules, verify notify-data-change pipeline health in addition to standard Celery/queue checks. 💳 Credit consumption note: Repeated automatic retries caused by connection errors can consume user credits. If a customer reports unexpected credit depletion, check for correlated Atlas Brain connection errors and retry loops in the same timeframe; if confirmed, escalate to the credits refund team with evidence of retry loops for manual credit restoration. Do not advise customers to re-run the tool until the underlying connection error is resolved. 👉 Next step: For resolution steps, see the Async / Queue Fix Guide or escalate via the relevant service's engineering channel (Linkgraph, Atlas Brain, or Data Pipelines). 🔗 External Dependency Failures - Gemini / OpenAI limits - SEMRush unavailable (now fetched asynchronously via Celery tasks per SE-536 — failures may surface as stuck jobs rather than immediate errors; check the Async/Queue Failures category in parallel) - DataForSEO throttling 👉 Symptoms: - Missing data - AI not generating - Partial outputs 👉 Next step: For resolution steps, see the External Dependency Fix Guide or escalate via the Data Pipelines engineering channel. 🖥️ Frontend / UI Failures - React errors - Graphs not rendering - reCAPTCHA issues - Billing Modal Freeze — The Add Payment Method modal may enter an indefinite loading state after clicking Add Card, with no error shown and no card added. This is a known frontend issue (QPB-697). Do not advise the customer to retry repeatedly; escalate to the billing team. - Press Release / Signal Genesys Publish Blocked by Image Validation — If a customer cannot publish and sees inline image errors in Step 3, the cause is an unsupported image format (WEBP, AVIF, HEIC, BMP, TIFF, ICO) or a corrupt/mislabelled file. This is expected validation behavior as of AB-970, not a system failure. 👉 Symptoms: - White screens - Broken UI elements - Actions not working 👉 Next step: For resolution steps, see the Frontend Fix Guide or escalate via the Frontend engineering channel. 🔀 Inter-Module Pipeline / Bridge Failures - API bridges between modules (e.g., Content Genius → Link Lab) can enter a blocked state - Actions complete on one side but do not propagate to the target module - Reference escalation: 215474220017778 👉 Symptoms: - Source module reports success - Target module never receives the handoff - No visible error in either module 👉 Next step: Escalate to engineering with pipeline telemetry data for the affected modules. 🧩 SERVICE-LEVEL DIAGNOSIS 🔧 Linkgraph (Core API) 🔴 Most Critical Patterns - Metrics not updating → queue issue - 503 errors → DB connection exhaustion - Jobs stuck → Celery worker version mismatch or task queue not processing (workers running an outdated task signature, or queue is backed up / not consuming — observable as tasks staying in PENDING/RECEIVED without progressing) - Crawls stuck → timeout on large sites 👉 Insight: Linkgraph issues are usually backend or queue-related 🤖 Content Assistant 🔴 Most Critical Patterns - AI not generating (hard failure) → Gemini quota (429) - AI reports success but output not applied (silent failure) → backend sync issue; UI may show 'Success' while generated content is not persisted or activated - Content incomplete → keyword service failing - JSON errors → malformed LLM output 👉 Insight: Most failures come from external AI dependencies, but watch for silent successes where the UI confirms an action that did not actually take effect on the backend. 🧠 Atlas Brain / Website Studio 🔴 Most Critical Patterns - Infinite spinner during analysis (LPS-442) → queue/async failure; see Async/Queue Failures category. Diagnostic indicator: UI shows a persistent spinner with no status update. Distinct from the 'no connection' freeze pattern below. - 'No connection' freeze with false success states → backend connection drop causing NLP terms and schema deployment to fail silently while the UI displays 'Success' (escalation 215474307923656). Diagnostic indicator: UI confirms an action that did not propagate to the backend. Different diagnostic path and escalation than LPS-442. - CMS Connector State Mismatch — Atlas Brain may display a disconnected status even when the connector is active on the backend (cases 215474386800374, 215474258075754). Verify via backend admin before advising the customer to reconnect. - AI Agent Schema/NLP Deployment Sync Failure — Success status displayed but terms not activated (case 215474307923656). Check backend sync state. This may require manual deployment and engineering escalation (reference pattern: SPE-692 / AIAGENT-1904). - Publish Blocked by False Disconnection Error — Atlas Brain reports website not connected despite the site being active (cases 215474258075754, 215474386800374). Verify connection state on backend before advising reconnection or manual publish workaround. - Unexpected credit depletion → connection errors can trigger URL Indexer or other jobs to retry automatically and burn credits (case 215474438977629); correlate with Atlas Brain or connector error events, and escalate to the credits refund team if retry loops are confirmed. 👉 Insight: Atlas Brain failures often present as successful UI states masking backend faults — always verify actual backend state before trusting the UI. 🖥️ Customer Frontend 🔴 Most Critical Patterns - Login issues → reCAPTCHA - Graphs missing → null data - App crashes → chunk load errors - Billing Modal Freeze (QPB-697) → Add Payment Method modal hangs after clicking Add Card with no error and no card added; escalate to the billing team rather than advising retries. 👉 Insight: Frontend errors are usually data-state or loading timing issues 🔍 Keyword Explorer 🔴 Most Critical Patterns - No keyword data → ClickHouse failure - Missing enrichment → SEMRush unavailable - Slow results → DataForSEO limits 👉 Insight: This service depends heavily on external data pipelines 🔗 Backlink App 🔴 Most Critical Patterns - Data not loading → DB issues - No major user-facing errors → mostly infra/logging 🧠 KEY INSIGHT 👉 Most issues are not bugs They are: - System limits - Dependencies - Scale problems 🔑 Golden Rule Before fixing anything: 👉 Ask: Is this: UI, Data, Queue, Infrastructure, or Inter-Module Pipeline? ➡️ Next Steps After Diagnosis Once you have classified the issue: - Match the category to the relevant fix guide or runbook - Apply P-level severity classification (P0–P3) based on customer impact and scope - Escalate through the appropriate engineering channel (Linkgraph, Atlas Brain, Frontend, Data Pipelines, or Billing) with the diagnosis category, observed symptoms, and any referenced ticket IDs (e.g., LPS-442, SE-536, SPE-692, QP-5196, QPB-697, OTTO-2082, AB-970) - Hand off to the on-call engineer using the standard escalation protocol if the issue is P0/P1 or customer-blocking