Agent Features & Concepts

🛠️ Troubleshooting Atlas Brain Blank Page Error

🧠 Fix Atlas Brain Fetch Failures

🧠 What “Failed to fetch” means The “Failed to fetch” message usually indicates a temporary connection problem between Atlas Brain and its processing services. It does not necessarily mean your project, prompt, or account is damaged. 🔄 Try these quick fixes 1. Wait a few minutes, then submit your request again. 2. Refresh the Search Atlas platform and reopen Atlas Brain. 3. Check that your internet connection is stable. 4. Try a shorter prompt if the original request included a large amount of text, files, or images. 5. If you were using a connected tool or data source, reopen it and try again. 📚 If your history is missing A temporary loading or service error can prevent recent conversations from appearing. Refresh the page, confirm that you are in the correct workspace, and check again after a few minutes. Avoid deleting or recreating the project while the service is recovering. If the conversation still does not appear, start a new chat and briefly describe the work you were completing. Keep a copy of important prompts and responses outside Atlas Brain while troubleshooting. 🖼️ Requests involving images or tools Atlas Brain may temporarily fail when analyzing images, connecting to backend tools, or delegating work to another agent. Retry the request without the attachment or tool step first. If that works, add the image or tool request again in a separate message. ✅ When to contact support If the error continues after refreshing and retrying, note the approximate time, the request you submitted, and any connected tool or file involved. Do not include passwords or sensitive information. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Fix Report Email and Atlas Agent Issues

📧 Why reports may reach the wrong email Report emails are associated with the Search Atlas account, report configuration, or team member who created the report. If a report goes to an unfamiliar address, the recipient may be linked to an older account owner, a previous report setup, or a duplicate delivery setting. ⚙️ Check your account and team settings 1. Open the avatar menu in the top-right corner. 2. Select Team Members. 3. Review the listed members and identify the account used to create or receive reports. 4. Deactivate outdated members if appropriate, and confirm that the intended user has the correct role. Then create or resend the report from the correct account. Avoid creating duplicate report schedules while testing, as this can result in multiple emails. 📄 Troubleshoot branded PDF or HTML reports 1. Confirm that the report contains completed data before exporting or sending it. 2. Retry the report from the relevant report or content workflow. 3. Check whether the issue affects both PDF and HTML formats or only one format. 4. Verify that the brand details, logo, domain, and report sections are complete and saved before generating the file. 5. Download the file only after the platform confirms that generation is complete. If no download starts, do not assume the file was created. Atlas Agent may occasionally use unrelated domain-family data, incorrectly describe connected data sources, or confirm a download that did not occur. Review the generated report against the selected project before sharing it. 🔍 Check the report workflow For content reports, open Content in the left sidebar and select Content Genius. Use the available generation or writing action, then review the resulting report before sending it. For audits, open Content → Onpage Audit, select the relevant tab, and use Generate Report or Share. ✅ Best practices before sending - Use the intended project and domain. - Confirm the recipient account and team member. - Review report data, branding, and file format. - Test one delivery before enabling recurring reports. - Check for duplicate messages if more than one report workflow is active. 💬 Get help with a recurring failure When contacting support, include the project name, report type, file format, expected recipient, actual recipient, and the approximate time of the failed attempt. Screenshots or the generated file can also help identify the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Fix Report Recipients and Atlas Agent Issues

📬 Why reports may go to the wrong recipient Reports are sent to the recipient saved in the report or scheduled delivery settings. This address may differ from your Search Atlas account email, especially if the report was created by another user, copied from an older schedule, or configured before your account details changed. 🔍 Check the report recipient 1. Open the report or scheduled report settings. 2. Review the recipient or delivery address. 3. Replace any unfamiliar address with the email associated with the intended Search Atlas user. 4. Save the updated settings and confirm that the next delivery uses the corrected recipient. If you cannot edit the recipient, ask the report owner or an account administrator to update it. Do not rely on the sender address or the address shown in a previous report; check the current delivery settings. ⚙️ Verify your account email Confirm that you are signed in to the correct Search Atlas account and workspace. If your account email was recently changed, create or update the report schedule after the change so the latest recipient information is used. 🤖 Troubleshoot Atlas Agent failures Atlas Agent may sometimes show an incomplete response, report that a connected service is unavailable, or fail to deliver a completed result. First, refresh the page and retry the request with a shorter, more specific prompt. - Confirm that the correct project and report are selected. - Check that required Google Search Console or Google Analytics connections are active. - For large reports, request one section or metric at a time. - Wait for the task to finish before starting another identical request. - If a download is reported as complete, verify that the file actually downloaded before retrying. - For scheduled deliveries, confirm both the destination and the recipient settings. ✅ What to include when retrying State the project, report name, date range, requested action, and expected delivery destination. This helps Atlas Agent use the correct data and reduces incomplete or misdirected results. 💬 Get help from our team If the recipient cannot be changed, Atlas Agent repeatedly fails, or a report still goes to an unknown address, capture the report name and the approximate time of the attempt. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Troubleshooting Atlas Agent Playbooks

This guide helps when Atlas Agent opens but its playbooks are missing or inaccessible. What This Issue Looks Like When accessing Atlas Agent, you may find that playbooks are not listed, fail to load, or return an access error. This prevents you from using the playbooks that should be available in your workspace. Steps to Try First Before contacting support, work through the following steps. Missing or inaccessible playbooks are often caused by being logged into the wrong workspace or a stale session, which you can resolve on your own: 1. Confirm which workspace you are in. Check the workspace name shown in the platform and compare it to the workspace where your playbooks were created. If you belong to more than one workspace, switch to the correct one and reopen Atlas Agent. 2. Verify your access and plan. Confirm that your plan includes Atlas Agent, and ask a workspace owner or admin to verify that your role has permission to view playbooks. If your access was recently changed or removed, they can restore it for your account. 3. Refresh your session. Log out of the platform and log back in, or open Atlas Agent in an incognito or private browser window. This rules out a cached session preventing playbooks from appearing. 4. Verify that playbooks load. Reopen Atlas Agent and confirm that the expected playbooks are listed and open without an access or loading error. What to Have Ready When You Contact Support If the steps above do not restore access, the issue may require investigation on the backend. Please have the following information ready before reaching out so the issue can be resolved as quickly as possible: - Your workspace name - A description of what happens when you open Atlas Agent (e.g. playbooks missing, error shown, page blank) - The exact error message, if one appears - The date and time when the issue first occurred - A screenshot showing the issue, if available - Which of the steps above you already tried and what happened What to Expect Once the support team reviews your workspace and the affected playbooks, they will take the necessary steps to restore access. You should then be able to open Atlas Agent and see the expected playbooks listed without any access or loading errors. 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.

📘 Atlas Brain V2 — Complete Guide

Atlas Brain V2 is Search Atlas's artificial intelligence agent: an autonomous assistant capable of planning, executing, and deploying complete SEO, content, and digital marketing strategies. Unlike a simple chatbot, Atlas Brain V2 acts as an expert working on your behalf, connecting to every section of the platform to complete multi-step tasks without you having to handle them manually one by one. This guide covers what is new in V2, what Atlas Brain V2 can do across the platform, how to use it, the approval flow, known limitations, and the frequently asked questions included in the source document. 🆕 What's New in V2 | V1 | V2 | | --- | --- | | Chatbot with static responses | Autonomous agent with 16 specialized domains | | No real action execution | Executes, deploys, and verifies live changes | | Session-limited context | Persistent conversation history per project | | Single language model | Multi-model orchestration (Claude, GPT-4, Gemini via OpenRouter) | | No approval gates | Human-in-the-Loop flow: you approve critical actions before they run | 🔄 Your previous V1 conversations remain available in read-only mode inside the V2 interface so you can always refer back to your history. 🧩 What Can Atlas Brain V2 Do? Atlas Brain V2 combines 16 specialized agents that work in a coordinated way. Below is a full breakdown by area. ⚙️ Technical SEO (OTTO) Atlas Brain connects directly to OTTO, SearchAtlas's technical SEO engine, to analyze and fix site issues autonomously. What it can do: - Run full technical site audits (crawl, issue categorization by severity: Critical / Warning / Info) - Generate AI recommendations to fix: - Title tags and meta descriptions - Headings H1, H2, and H3 (length and structure) - Image alt text (in bulk) - OG and Twitter tags for social media - NLP terms and missing keywords - Structured FAQ content - Schema markup (JSON-LD: Article, FAQ, Product, BreadcrumbList, LocalBusiness) - Canonical tags and html lang attribute - Deploy changes to production directly from the chat (requires OTTO Pixel installed) - Roll back deployments if changes don't perform as expected - Force site recrawls to get fresh data - Detect and build Domain Knowledge Networks (DKN) for structured interlinking ⚠️ Important note: On sites built with Elementor, the agent can update title tags and meta descriptions, but cannot modify H1 tags directly, as Elementor manages that content differently. The agent will inform you of this before attempting the task. ✍️ Content Creation (Content Genius) Atlas Brain generates complete SEO articles following a structured multi-step workflow, from research through to publication. Article creation workflow: Planning — Defines objective, audience, and SEO angle Brand Vault — Applies your brand's voice, tone, and audience guidelines Research — Gathers semantic information and relevant sources Heading outline — Proposes H2/H3 structure for your approval Full generation — Writes the article with NLP terms integrated Publishing and distribution: Publish, save as draft, or schedule articles directly to WordPress Support for generic CMS connectors (Webflow, Shopify, etc.) Export articles to Google Docs for external review Schedule multiple articles with distributed publication intervals Additional tools: Create topical maps (semantic content clusters) Review and rewrite existing content with AI Score articles using the Content Grading system 📊 Keyword Research & Rank Tracking (Site Explorer + Keywords)system Atlas Brain taps into Search Atlas's keyword analysis engine to deliver actionable data. Capabilities: - Research keywords: volume, difficulty, search intent - Analyze competitor keywords and content gaps - Track historical positions for your target keywords - Monitor SERPs and ranking changes - Estimate organic traffic for any domain 📍 Local SEO Atlas Brain handles all aspects of local SEO through three specialized modules: 🏢 Google Business Profile (GBP) - Create and schedule GBP posts - Manage reviews (respond, prioritize) - Update business information (hours, categories, photos, videos) - Pull GBP analytics (impressions, clicks, calls) 🗺️ Local Rank Heatmaps - Set up geographic tracking grids by city or zone - Visualize rankings by keyword on heat maps - Get AI suggestions for high-opportunity local keywords 📇 Citations / Directories - Submit your NAP (Name, Address, Phone) to 60+ directories simultaneously - Track submission status and data consistency 🔗 Authority Building (Link Building) The agent can plan and execute multi-channel authority building campaigns. Available channels: - LinkLab — Marketplace of 50,000+ publications for guest posts - Press Releases — Create and distribute press releases with media coverage tracking - Cloud Stacks — Content distribution across cloud platforms for authority signals - Digital PR — Journalist opportunity discovery, email outreach campaigns - Wildfire Link Management — Manage outlinks and inbound backlinks 💳 Google Ads / PPC (OTTO PPC) Atlas Brain can create and activate Google Ads campaigns autonomously. Workflow: - Account and business setup - Campaign mode selection - Keyword clustering by ad group - AI-generated ad copy - Landing page configuration - Campaign activation in Google Ads 🤖 AI Visibility (AI Brand Monitoring) Monitor your brand's presence across AI-powered search engines. Platforms monitored: ChatGPT, Gemini, Perplexity, Microsoft Copilot, Grok What you can query: - Your brand's AI visibility score - Sentiment analysis of how AI models describe your brand - Share of voice vs. competitors - Sources and citations used by language models 📈 Google Search Console (GSC) Atlas Brain connects to your GSC account to surface insights directly in the chat. - Performance data: clicks, impressions, CTR, average position - Search queries driving traffic to your site - Site event analysis (ranking drops, improvements) 🏗️ Website Studio Build websites and landing pages with AI directly from the chat. - Generate complete websites from a brief - Create conversion-optimized landing pages - Clone and publish existing pages 📱 Social Hub Manage your social media presence from a single interface. Platforms: Facebook, Instagram, LinkedIn, X (Twitter) - Create and publish posts across multiple networks simultaneously - Schedule social content - Manage connected profiles and accounts 🔎 URL Indexing Accelerated URL submission to Google and Bing indexes. - Submit individual or bulk URLs - Submit full sitemaps - Check indexation status for any URL 🛠️ Step-by-Step Instructions Step 1 Access Atlas Brain V2 from the SearchAtlas dashboard in the sidebar. Step 2 You can use it in two modes: - Minimized view (side panel): for quick queries while navigating the platform - Full screen: for intensive work sessions with multiple tasks Step 3 You can switch between modes at any time without losing your conversation context. Step 4 Select or mention your project — The agent works within the context of a specific project in your account. Step 5 Type your goal in plain language — No special commands needed. Examples: - "Run a technical audit of my site and deploy the title tag fixes" - "Write an article about [topic] and save it as a draft in WordPress" - "Which of my keywords have dropped the most in the last 30 days?" Step 6 Review and approve critical actions — Before executing any operation that modifies production data (deploying changes, publishing, sending campaigns), the agent will show you an approval panel with the full details of the action. Step 7 The agent executes and reports — You'll receive real-time updates as the agent completes each step. 🔐 Tool Approval (Human-in-the-Loop) To protect your data and prevent accidental changes, certain actions require your explicit approval before running. The approval popup shows you: - What action the agent is about to execute - The specific parameters of the operation - Buttons: Approve / Decline (found under Social → Pending Approvals) ⚠️ Known Limitations | Limitation | Detail | | --- | --- | | Elementor and H1 tags | On Elementor sites, the agent cannot modify H1 tags directly; it will communicate this before attempting. | | OTTO data sync | If a site has changes deployed by OTTO, the agent needs JavaScript-rendered data to correctly detect them. | | Simultaneous sessions | Maximum 5 concurrent active sessions per user. | | Cross-chat context | The agent works with the current session's history; cross-chat memory between sessions is in development. | ❓ FAQs What happens to my Agent V1 conversations? 💡 They are available in read-only mode inside the V2 interface. You cannot continue a V1 conversation, but you can review your full history at any time. Can the agent affect my production site without my authorization? ⚡ No. Any action that modifies production data (deploying changes, publishing content, sending campaigns) requires your explicit approval via the approval panel. What language model does Atlas Brain V2 use? ✅ The agent uses Claude Sonnet 4.5 as its default model, with the ability to route to GPT-4 or Gemini depending on the task type, through OpenRouter. Does it work with any CMS platform? 💡 Yes, with native support for WordPress (publish, draft, schedule) and generic support for other CMS platforms (Webflow, Shopify, etc.) via configurable connectors. Deploying on-page SEO changes to production requires the OTTO Pixel installed on your site. Can Atlas Brain write and publish content automatically without my review? ⚡ It can, if you explicitly request it. By default, the agent presents the results of each step (heading outline, draft, etc.) before proceeding, giving you the opportunity to adjust or approve. How does Atlas Brain relate to OTTO? ✅ OTTO is the technical SEO engine. Atlas Brain is the agent that controls it. Think of OTTO as the "executing arm" and Atlas Brain as the "brain" that plans, runs OTTO, interprets results, and makes decisions based on them. Atlas Brain V2 transforms how SEO and digital marketing tasks are executed by combining planning, execution, and deployment into a single intelligent workflow. This ensures you can operate efficiently across multiple domains while maintaining full control through the Human-in-the-Loop approval system, allowing you to review and authorize critical actions before they go live. If you encounter unexpected behavior or an incorrect result, you can report it directly from the chat using the feedback icon on the agent's message, or contact the support team through the SearchAtlas chat.

🛠️ Fixing Backlinks Sync and Atlas Agent Project Visibility Issues

If your backlinks report is empty, your project is missing from the Atlas Agent dropdown, or premium features appear locked even though you have an active plan, these symptoms are usually connected. They typically point to a project that has not finished syncing, a verification gap, or a plan that has not fully applied to the workspace. This guide walks you through fixing each issue in order. ✅ Before You Start Most of these problems share the same root causes, so work through the checklist below first. Many cases resolve at this stage. - Confirm you are logged into the correct workspace (not a second account with the same email). - Confirm the project domain is entered correctly, including or excluding www exactly as your site resolves. - Confirm your plan shows as Active under Avatar (top-right) → Billing → Plans & Top-ups (Billing). - Clear your browser cache or try an incognito window to rule out stale data. 🔗 Issue 1: Backlinks Report Is Not Populating New backlink data is not instant. After a project is created, the initial crawl and index can take time to surface results, especially for smaller or newer domains. 🔧 Steps to Resolve 1. Open the project and go to the Backlinks report. 2. Check the date the project was created. Initial backlink data can take up to 72 hours to appear for the first time. 3. Verify the domain is entered as a root domain (for example, lfsolutions.us) rather than a full URL with a path. 4. Use the report's refresh or re-sync option if available. 5. If the report is still empty after 72 hours, the project may need a manual re-index from our side. Note the exact domain and move to the escalation steps below. A genuinely empty report can also mean the domain currently has very few or no detectable backlinks. Cross-check the domain in another report to confirm whether data exists at all. 🤖 Issue 2: Project Missing From the Atlas Agent Dropdown Atlas Agent only lists projects that are fully created, verified, and associated with your current workspace. If a project is still processing or sits in a different workspace, it will not appear. (Atlas Agent was previously named Atlas Brain; older links and saved bookmarks to /atlas-brain/ now redirect to /atlas-agent/, so both names refer to the same tool.) 🔧 Steps to Resolve 1. Return to your main project list under OTTO SEO → All Sites (SEO Automation) and confirm the project exists and shows a setup status of Active, not Deep Frozen. 2. Confirm the project lives in the same workspace you are using for Atlas Agent. Switch workspaces from the top menu if you manage more than one. 3. Complete any outstanding setup steps, such as connecting Google Search Console or verifying domain ownership. Unverified projects are often hidden from the dropdown. 4. Refresh the Atlas Agent page after setup is complete so the dropdown reloads. 5. Log out and back in to force the project list to re-sync with your account. Projects created outside Atlas Agent — for example through the main project creation flow rather than from within Atlas Agent itself — are now included in the same unified project list. A past bug that hid these externally created projects has been resolved, so logging out and back in (which triggers a fresh sync) should surface any project that belongs to your account, regardless of where it was created. If you have the opposite problem — a project you already removed elsewhere still appears in Atlas Agent and has no working delete option — this was a separate known issue that has since been fixed, and the delete action now works for these stale entries (including older records that were missing an underlying project ID). If such a leftover project still persists, contact support and we can clear the orphaned record directly. A related, now-resolved issue looked different: the project did appear in Atlas Agent, but the agent replied that it “can't access your project,” reported that backend tools weren't connecting, or suggested using another SEO tool instead of completing the task. This pointed to a backend tool-connection or sub-agent delegation failure rather than a problem with your project setup, and it has since been fixed. If you still encounter it, refresh or start a new Atlas Agent session, and report it to support — it is not something you can resolve by changing your project or workspace settings. 🔒 Issue 3: Features Remain Locked on an Active Plan When a plan upgrade does not unlock features, the entitlement usually has not propagated to your session or to the specific workspace. 🔧 Steps to Resolve 1. Go to Avatar (top-right) → Billing → Plans & Top-ups (Billing) and confirm the plan name and status both reflect your current subscription. 2. Confirm the plan is applied to the workspace you are working in. On multi-workspace accounts, an upgrade applies to one workspace at a time. 3. Fully log out, then log back in. Entitlements refresh on a new session. 4. Try an incognito window to bypass cached permission data. 5. If you upgraded very recently, allow up to 30 minutes for billing changes to sync across all tools. 🧩 Why These Issues Often Appear Together A single underlying cause, most commonly an incomplete project setup or a workspace mismatch, can trigger all three symptoms at once. A project that has not finished verifying may show no backlinks, stay hidden in Atlas Agent, and appear to lack premium access. Completing setup and confirming the correct workspace frequently clears every symptom in one pass. 📞 When to Contact Support If you have completed the steps above and the problem continues beyond the stated wait times, reach out to our team. To speed up resolution, please include: - The exact project domain (for example, lfsolutions.us). - The workspace name and your account email. - Which of the three issues you are seeing, and screenshots if possible. - The date you created the project and the date you upgraded your plan. - The troubleshooting steps you have already tried. With these details, support can verify your project status, trigger a manual re-index, confirm your plan entitlements, and clear any orphaned project records directly.

🤖 Search Atlas Agentic Onboarding: A Guided Walkthrough

The Agentic Onboarding experience in Search Atlas is designed to guide new users from first login to an actively configured, AI-powered SEO workspace. This walkthrough explains what users see, what steps can be skipped, and how the platform progressively unlocks features, credits, and automation as tasks are completed. 1️⃣ First Login & Initial Redirect 👋 The first-time user experience When a user logs into Search Atlas for the first time: - They are initially redirected to a call booking screen, where they can schedule a 1:1 onboarding session. - This step is optional and can be skipped. - Users may also see guided onboarding steps that introduce key features. This initial redirect establishes context and offers direct human support before any configuration begins. 2️⃣ Onboarding Flow & Guided Setup 🧭 Structured onboarding before full access After the initial redirect, users are taken into the guided onboarding flow. This flow introduces core setup steps required before the platform is fully activated. The onboarding sequence is designed to be followed step by step and cannot be completed randomly. Each screen explains what is being configured and why it matters, preparing the account before deep feature access. 3️⃣ Landing on the Dashboard (Pre-Completion State) ⏳ Dashboard with onboarding tasks active Once onboarding begins, users arrive at the Home in a pre-completion state. At this point, the Home displays: - Onboarding task modules - Progress indicators - Sections that are not yet fully activated This version of the Home is intentionally instructional and highlights what still needs to be completed. 4️⃣ Creating a New SEO Project 🧱 Setting up the foundation As part of onboarding, users are prompted to create a new SEO project. This includes entering project details and initiating setup. Once created, the project begins processing in the background. This step is mandatory, as all automation, reporting, and agents are tied to an active project. Search Atlas uses a task-based onboarding model: - Each section of onboarding contributes to overall completion. - Completing tasks increases: - Project readiness - Feature availability - User rewards 5️⃣ Task-Based Progress & Completion Requirements 📋 Sequential tasks that must be completed Onboarding is driven by tasks that must be completed in order. Users cannot skip required tasks to claim rewards. Each completed section unlocks the next step and moves the onboarding forward. If a task is incomplete, the system clearly indicates what remains and prevents final completion. 6️⃣ Credits, Timers, and Rewards System 💎 Understanding how rewards are earned Users earn Hyperdrive Credits for attending the 1:1 onboarding session. - Time-based bonuses may apply (for example, credits doubling within a certain window) - A visible timer shows how long bonus eligibility remains Credits are applied to the account for attending the 1:1 onboarding session. 7️⃣ Activating Automation & Agents 🤖 Turning on background execution After key onboarding tasks are completed, users can activate auto-tracking and automation. This enables Search Atlas agents to begin working in the background, running audits, syncing data, and preparing insights without manual input. This marks the transition from setup to active execution. 8️⃣ Completed Onboarding Dashboard State When all onboarding tasks are completed: - The onboarding task box disappears - Guidance prompts are removed - Credits are fully credited to the account The Home shifts into a clean, operational state, reflecting that onboarding is finished. 9️⃣ All Projects & Multi-Project Portfolio View 🏢 Managing multiple projects Users can access the All Projects, which aggregates projects into a single view. If the user has multiple projects (for example, more than five), they appear grouped as a portfolio. Projects can be opened directly from this view, making it easier to manage multiple accounts. 🔟 Inside a Project: Performance & Strategy Overview 📊 Initial project insights Opening a project brings users to a performance-focused view, including: - A snapshot of key metrics - Historical performance data - Filters for different time ranges (such as yearly or recent periods) This provides immediate context on how the project is performing. 1️⃣1️⃣ Content Strategy & Topic Suggestions 🧠 Planning content with AI support Within the project, users can begin building a content strategy. They can: - Review suggested topics - Click Suggest New Topics - Edit or refine topic ideas This step can be completed during onboarding or revisited later. 1️⃣2️⃣ Content Editing & Article Generation ✍️ Generating and refining content Once topics are selected, Search Atlas can generate articles automatically. Generated content appears directly in the interface, where users can: - Review the article - Edit the content - Approve it for further use This demonstrates AI-driven execution in action. 1️⃣3️⃣ Google Business Profile & Keyword Confirmation 📍 Local SEO setup As part of onboarding, users are guided through Google Business Profile (GBP) setup. This includes: - Reviewing suggested GBPs - Editing and confirming keyword suggestions - Providing feedback using thumbs up/down Once confirmed, local SEO tracking begins loading in the background. 1️⃣4️⃣ Background Processing & Final Navigation Options ⚙️ Agents continue working After all connections are made, agents continue processing data in the background. Users can: - Go directly to the Home - Proceed to installations - Continue working while automation runs At this stage, onboarding is complete and the platform is fully active. Search Atlas’ Agentic Onboarding is more than a setup flow, it’s a progressive journey from exploration to execution. Each step is intentionally designed to reduce friction, surface value early, and transition users into a fully operational SEO environment powered by intelligent agents. By the time onboarding is complete, the platform shifts from guidance to autonomy. Tasks disappear, automation takes over, credits are unlocked, and the Home becomes a live reflection of real performance. Whether managing a single project or an entire agency portfolio, users move forward with confidence, knowing Search Atlas is working continuously in the background. This is onboarding built not just to educate, but to activate!

🔄 Fix Atlas Brain Local Citation Submission Loop

🔍 What Is Happening If Atlas Brain appears to hard-lock your HDC plan cap and repeatedly blocks local citation submissions — even though you are on a Pro plan with credits available — this is not a true hard lock. It is a sync issue between the Atlas Brain AI agent and the API. No credits are lost and no permanent restriction is applied to your account. ✅ Method 1: Start a Fresh Atlas Brain Chat A new Atlas Brain conversation resets the session state and clears the sync error. Follow these steps: 1. Close or exit your current Atlas Brain chat entirely — do not continue in the same thread. 2. Open a brand-new Atlas Brain chat session. 3. Re-initiate your local citation submission request from the beginning in the new session. Atlas Brain will re-read your account state with a clean call and should recognise your available credits, allowing the submission to proceed normally. 🛠️ Method 2: Submit Manually Through the Local SEO Tool If the fresh chat does not resolve the issue, you can bypass Atlas Brain entirely and submit your local citation directly through the platform's local SEO tool rather than through the AI agent. Navigate to the local citation submission area within the platform and complete your submission from there without using Atlas Brain. This manual route is always available as a reliable fallback regardless of any AI agent sync state. 💡 Why This Happens Atlas Brain can encounter a mismatch when reading quota or plan data during a session. This may cause it to incorrectly report a cap or refuse a submission it should allow. Starting a new chat or using the manual tool forces a fresh data read. This is a known intermittent behaviour and does not indicate a problem with your plan or credit balance. ⚙️ Before You Try Either Method — Quick Checks - Confirm you are on a plan that includes local citation submissions and that your credit balance is not genuinely zero. - Refresh the platform page before opening a new Atlas Brain chat, to ensure your browser session is also current. - If you have multiple projects, make sure you reference the correct site when restarting your request. 🙋 Still Blocked After Trying Both Methods? 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.

🔍 Find and Publish Your Atlas Agent Campaigns

Overview If Atlas Agent helped you build ad campaigns, you may have seen references to OTTO PPC or Smart Ads in conversations or documentation. These names may correspond to features that appear under different labels in your dashboard depending on your account and plan. This article explains what to do if you cannot locate your campaigns or are unsure where to publish them. What to Do If You Cannot Find Your Atlas Agent Campaign If you are looking for a campaign created by Atlas Agent and cannot find it in your dashboard, here is what to check: - Look for an Ads or Campaigns section in your dashboard navigation. The exact label and location may vary depending on your account setup. - If you were directed to a menu item (such as Campaign Hub, Smart Ads, or OTTO PPC) that does not appear in your interface, these may be internal or legacy names for features available under a different label in your current dashboard. - Confirm that your account plan and user permissions include access to campaign management features. If you are unsure, contact your account administrator. What to Do If You Cannot Publish a Campaign If you have located your campaign but are unable to publish it, check the following: - Ensure all required campaign fields are complete. Incomplete campaigns may not have a publish option available. - Confirm you have the necessary user permissions to publish campaigns on your account. - If you still cannot publish after checking the above, note the campaign name and the approximate date it was created before reaching out for support. When to Contact Support Because campaign navigation and publishing steps can vary by account configuration, our support team can confirm the exact location of your campaigns and guide you through publishing. Before reaching out, please have the following ready: - Your project or account name - The campaign name and approximate creation date - A description of what you see (or do not see) in your dashboard, including any error messages If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Atlas Brain 'Unable to Process Request' Error

Understanding the Error If Atlas Brain is not processing requests or your schema deployments are failing, the most common cause is that your OTTO project has not been activated. Atlas Brain relies on an active OTTO project to process requests and deploy schemas to your website. Without activation, Atlas Brain cannot complete tasks for that project. Step 1 — Confirm Your OTTO Project Status Before troubleshooting anything else, verify whether your OTTO project is active: 1. Open your OTTO project for the website you are trying to work with. 2. Check whether the project is active or inactive. If it is not yet active, proceed to Step 2. 3. If the project is already active, skip to Step 3 to verify your connection settings. Step 2 — Activate Your OTTO Project If your OTTO project is not yet activated, follow these steps to activate it: 1. Open your OTTO project for the website you want to work with. 2. Locate the activation option associated with the project and enable it. 3. Wait for the activation process to complete. Once the project shows as active, return to Atlas Brain and attempt your request again. Step 3 — Deploy Your Schema After Activation With your OTTO project active, you can now deploy schemas successfully. Follow this workflow: 1. Open your activated OTTO project for the website. 2. Locate the schema-related options within the project. 3. Review the schema recommendations generated by Atlas Brain for your site. 4. Select the schemas you want to deploy and initiate the deployment. 5. Atlas Brain will push the selected schemas to your website once deployment is confirmed. If Atlas Brain still returns an error after activation, check that your website is correctly connected to OTTO and that your site credentials or integration settings are up to date. If the issue persists, please have your project name, the exact error message, and the time the error occurred ready before reaching out so our team can investigate quickly. 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.

🧠 Close Search Atlas Brain Modal to Access Dashboard

🔍 Overview Search Atlas Brain is an AI-powered assistant that opens as a modal overlay on top of the main platform. If Brain launched automatically or you opened it accidentally, the rest of the interface may appear inaccessible until you close the modal. This is expected behaviour — the modal is sitting in front of the dashboard, not replacing it. You do not need to clear your cache, perform a hard refresh, or log out to resolve this. ✅ How to Close the Brain Modal Look for a close or dismiss control on the Brain modal itself — typically a button or icon positioned on the modal panel — and click it to exit. The Brain modal should dismiss and the main dashboard will be accessible behind it. If you are unsure where the close control is located in your current version of the platform, try clicking outside the modal area (on the darkened overlay surrounding it), as some modal implementations allow dismissal this way. ⚠️ Why Cache Clearing and Incognito May Seem to Help Opening the platform in an incognito window may appear to resolve the issue because Brain does not always launch automatically in a fresh session. This can make it seem like a browser or cache problem when it is actually just a matter of the modal being open in your regular session. Clearing cache or using incognito is not necessary and will not reliably prevent Brain from opening in future sessions. 🛑 If You Cannot Dismiss the Modal If the modal cannot be closed using the controls available, please contact our support team so we can assist you directly. When reaching out, please have the following ready: - Your project name or workspace URL - A screenshot of what you are seeing - The browser and zoom level you are using - Any steps you have already tried If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔴 Fix Atlas Brain 400 Errors With OTTO SEO

🧠 What Is This Error? When you send a custom prompt to Atlas Brain and receive a persistent 400 error, this is almost always caused by a missing OTTO SEO project for your domain. Atlas Brain requires an active OTTO SEO project to process tool calls and generate responses. Without one, every request fails at the API level before Atlas Brain can do any work. This is not a system-wide outage. It affects only domains that have not yet been connected to an OTTO SEO project. ⚠️ Why Does This Happen? Atlas Brain uses your OTTO SEO project as its source of context — it pulls your domain data, crawl results, and SEO settings to power its responses. If no active project exists for the domain you are working with, Atlas Brain has no context to reference and returns a 400 Bad Request error instead of a response. Common situations where this occurs include: - You are using Atlas Brain for the first time on a domain that has never had an OTTO SEO project created. - A previous OTTO SEO project was deleted or disconnected from the domain. - You are testing Atlas Brain on a new domain you recently added to your account. ✅ How to Fix It: Create an OTTO SEO Project The resolution confirmed by our support team is to create an OTTO SEO project for your domain. To do this, navigate to the OTTO SEO section of the platform and create a new project for the domain you are working with. Once the project has been created and is set up for your domain, return to Atlas Brain and re-send your custom prompt. The 400 error should no longer occur. 🔍 How to Confirm the Error Is Resolved After creating the OTTO SEO project, return to Atlas Brain, select the same domain, and send a prompt. If Atlas Brain returns a response instead of a 400 error, the issue is resolved. If you still see a 400 error, confirm that the OTTO SEO project has been created for the correct domain. 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.

🤖 Atlas Agent Stuck on Working State

🔍 What Is This Issue? Atlas Agent may occasionally appear stuck on a 'working on it' message for several minutes without producing a response. This can happen even after reloading the page and is usually related to a temporary service disruption or a background processing delay. ⚠️ Common Causes - Temporary outage: Search Atlas services may be experiencing a brief interruption affecting Atlas Agent's ability to process requests. - High server load: During peak usage periods, response times may be significantly longer than usual. - Stale session: Your browser session may be holding onto an incomplete request that is no longer active. - Network interruption: A brief drop in your internet connection during a request can leave the agent in a pending state. 🛠️ Steps to Resolve the Issue 1. Wait up to 3–5 minutes. Some complex Atlas Agent tasks take longer to complete. If the agent is still unresponsive after this window, proceed to the next steps. 2. Reload the page. Press F5 (Windows) or Cmd + R (Mac) to refresh. Check whether the agent resumes or shows an updated status. 3. Clear your browser cache. A corrupted cache can cause display issues. Clear your cache and cookies, then reload the platform. 4. Try a different browser or incognito window. This rules out browser-specific issues. Supported browsers include the latest versions of Chrome, Firefox, Edge, and Safari. 5. Check your internet connection. Make sure you have a stable connection and are not behind a restrictive firewall or VPN that could interfere with platform requests. 6. Start a new Atlas Agent session. Close the current conversation and open a fresh one. Retype your request to see if the agent responds normally. 📊 How to Check for an Active Outage If none of the steps above resolve the issue, there may be an ongoing service disruption on the Search Atlas side. During an outage, Atlas Agent will be unavailable until the issue is resolved by our engineering team. Outages are typically brief and resolved within a short window. You do not need to take any action on your account — simply try again after a few minutes. 💡 Tips to Prevent This in the Future - Avoid submitting multiple Atlas Agent requests in rapid succession, as this can create queuing delays. - Keep your browser updated to the latest version for the best platform performance. - If you are working on a time-sensitive task, try submitting requests during off-peak hours for faster responses. 🙋 Still Need Help? If Atlas Agent continues to be stuck after following all steps above, our support team can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Site Recrawl Delays in Agent Hub

🔎 Overview After triggering a recrawl on a site, you may notice it does not immediately appear — or reappear — under Active Projects in the Agent Hub. This is a known delay that occurs while Search Atlas processes the new crawl data and syncs it across the platform. This article explains why it happens and what you can do to resolve it. ⚙️ Why the Delay Happens When a recrawl is initiated, Search Atlas goes through several background steps before the site is reflected in the Agent Hub: - Crawl queuing: Depending on site size and platform load, your recrawl may sit in a processing queue before it begins. - Data indexing: Once crawling is complete, the system needs time to index the updated site data before it can be surfaced in Active Projects. - Sync lag: There is a short synchronisation window between when crawl data is processed and when the Agent Hub refreshes its project list. In most cases, the site will appear in Active Projects within a few minutes to a few hours depending on the size of the site and current system load. 🛠️ Steps to Resolve the Issue 1. Wait and refresh: After a recrawl, wait at least 10–15 minutes, then hard-refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and navigate back to the Agent Hub at Left sidebar → Home → Agent Hub (URL: /home). 2. Confirm the recrawl completed: Go to Left sidebar → Site Metrics (Site Explorer) (URL: /site-explorer/list) and locate your site. Check whether the crawl status shows as completed. If it still shows as in progress or queued, the Agent Hub will not update until crawling finishes. 3. Check that the project is active: Inside the Agent Hub, confirm the project has not been paused or deactivated. A project in a paused state will not surface in the Active Projects list even after a successful recrawl. 4. Re-enter the Agent Hub: Navigate away from the Agent Hub page and return to it via Left sidebar → Home → Agent Hub. This forces the page to re-fetch the latest project data. 5. Clear browser cache: Cached data can sometimes prevent updated project status from loading. Clear your browser cache, then log back in and check Active Projects again. 📊 What to Expect After a Successful Recrawl Once the recrawl has fully completed and data has been indexed, your site will appear in Active Projects in the Agent Hub with refreshed metrics. Any previously flagged issues will be updated to reflect the current state of the site. If the project was visible before the recrawl, it should return to the same position in your Active Projects list. 💡 Tips to Avoid Future Delays - Avoid triggering multiple recrawls in quick succession on the same site — this can push your crawl further back in the queue. - Schedule recrawls during off-peak hours if your site is large, as processing times can vary based on platform load. - After initiating a recrawl, monitor the crawl status in Site Explorer before checking the Agent Hub, so you know when to expect the update. 🆘 Still Not Showing Up? If your site has not appeared in Active Projects after several hours and the recrawl shows as completed in Site Explorer, there may be an underlying issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧠 Fix Atlas Brain Report Links Not Opening

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

🛠️ End-to-End Technical SEO Fixes Using the Auto Agent

The Auto Agent lets you move beyond the slow, manual process of identifying, editing, and deploying on-page SEO fixes. Instead of reviewing reports and pushing changes by hand, you can execute technical SEO improvements end-to-end using Atlas Agent's execution engine, often in minutes. 🔍 Step 1: Initiating the Automated Audit Select the project you want to optimize and confirm that the Auto Agent is active for that project. Then start the chat with a basic prompt, no prompt engineering required. For example: Auto, show me title tag opportunities. Immediately after submission, the agent can expose its internal reasoning, showing how your natural language request is translated into a formal execution task. 📊 Step 2: Reviewing and Refining Recommendations The Auto Agent presents actionable recommendations in a structured table showing the current title tag, the recommended title tag, and the deployment status. You can instruct the agent to review and improve its own output, for example: Evaluate the quality of these title tag suggestions and present new ones if the old ones are not strong. The agent explains what it is changing and why, then presents revised recommendations, explicitly calling out what was improved compared to the previous version. 🚀 Step 3: Deployment Once recommendations are approved, deployment happens immediately. A command such as Proceed with pushing these new title tags to the pages results in the agent physically deploying approved changes to the live site, tasks that previously took days or weeks are completed in minutes. The agent confirms once updates have been successfully applied to the website. 🧩 Step 4: Executing a Full Onpage Playbook For broader optimization, the Auto Agent can run a complete Onpage Playbook, executing a comprehensive technical audit and automatically fixing priority issues across the site. The agent generates a detailed artifact outlining issues identified (title tags, meta descriptions, alt text, internal linking, and more), actions taken, and remaining optimization opportunities, along with the expected SEO impact. After completion, the system confirms that key elements have been optimized and deployed live. With the Auto Agent, technical SEO shifts from manual review and delayed execution to fast, controlled, and verifiable deployment, letting you fix issues faster, maintain strategic oversight, and scale optimization without scaling effort. 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 Competitor Projects Appear in My Project Dropdown (Atlas Brain)

If you notice projects you didn’t intentionally create appearing in your project dropdown, this behavior is expected and is caused by Atlas Brain. These projects are temporarily created so Atlas Brain can run competitor analysis and gather the data you explicitly requested. This is not a bug, not a security issue, and not an error with your account. 🧠 Why Atlas Brain Adds These Projects When you ask Atlas Brain to analyze competitors, compare domains, or run research on external sites, Atlas Brain must temporarily create internal projects to complete that analysis. Because of this, competitor sites may appear as “projects” and can show up in project dropdowns and in Activities or selection menus. This is required for Atlas Brain to function correctly. 🔁 Why They Reappear After Deletion Even if you delete these projects, they will be added again if you continue using the same playbook or ask Atlas Brain for competitor analysis again. This behavior is expected, deleting them does not prevent Atlas Brain from recreating them when needed. 👁️ Why They Appear in the Dropdown Menu The project dropdown is a global selector used by Atlas Brain. It shows all projects Atlas Brain is aware of, not just your owned websites, competitor projects are included so Atlas Brain can reference them during conversations. Because of this, the list may become long. 🧭 Should I Use or Ignore the Dropdown? You should ignore competitor projects in the dropdown, and select a project only when you want Atlas Brain to act on one of your real websites, for example, creating a blog post or applying SEO recommendations. Competitor projects do not have playbooks applied to them. ⚙️ Can My Projects Be Pinned or Shown at the Top? Currently, there is no way to reorder, pin, or prioritize projects in the dropdown. A feature request can be submitted to the product team to improve this behavior. ❓ FAQs Is this a bug or security issue? No. These projects are created intentionally by Atlas Brain. Can I permanently remove competitor projects? No. They may be recreated when Atlas Brain runs analysis. Are playbooks applied to competitor sites? No. Playbooks apply only to your valid projects. Do I need support to fix this? No. This is expected behavior and does not require support action. Competitor projects appearing in your dropdown are part of how Atlas Brain performs analysis. They can be safely ignored unless you want Atlas Brain to take action on one of your own websites. 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 — AI Agent & Atlas Brain Issues

This article covers the AI Agent chat, task execution, tool calls, and Atlas Brain behavior. ⚠️ Error 1: AI Agent shows no response after I send a message What's happening: The agent connection may have dropped or your session needs a refresh. Steps to try: - Check your internet connection — the AI Agent requires a stable, persistent connection. - Refresh the page and try a simple test message ("Hello") to check if the agent is responsive. - Log out and back in to reset your session. - Check remaining AI Agent usage: Top-right Corner Avatar → Billing → See Usage. - Contact support if the agent is completely unresponsive across different browsers. ⚠️ Error 2: Agent starts a task but stops partway through What's happening: The agent may be waiting for clarification, or a specific tool it needed was temporarily unavailable. Steps to try: - Scroll up in the chat — the agent may have asked a question or left a message explaining why it stopped. - Reply with "Continue" or answer any question the agent asked. - Rephrase the request more specifically — "Audit title tags on my homepage" works better than "Fix all SEO issues." - If the agent stopped silently, restate the task in a new message. - Contact support with the conversation transcript if the agent consistently stops at the same point. ⚠️ Error 3: Agent recommendations reference issues I already fixed What's happening: The agent is using data from a previous OTTO crawl that predates your fixes. Steps to try: - Trigger an OTTO re-crawl: Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site. - After the crawl completes, start a new AI Agent conversation — the agent loads fresh data at session start. - Tell the agent directly: "I've fixed [issue]. Please check the current crawl data." - Mark resolved tasks as complete in the OTTO task list so they don't resurface. - Confirm your fixes are live on the published URL, not just saved in drafts. ⚠️ Error 4: Agent says it performed an action but nothing changed What's happening: Some actions are queued rather than executed immediately, or a required integration is missing. Steps to try: - Check the OTTO task list for any pending approvals generated by the agent. - Hard-refresh the relevant module (Content Assistant, OTTO, etc.) to see if changes are visible there. - Ask the agent: "Please confirm the exact action you took and where I can verify it." - Check that the required integration is active — some actions require a connected CMS or GSC account. - Contact support with the specific action the agent claimed to perform and where you expected to see it. ⚠️ Error 5: Agent responses are too generic and not specific to my site What's happening: The agent needs more context — either from your prompt or from Brand Vault. Steps to try: - Be specific in every message — include your domain, target keyword, and specific goal. - Complete your Brand Vault fully: More Features → Brand Vault. - Ask data-driven questions: "Based on my current OTTO audit, what are my top 3 SEO priorities?" - Include your goals: "My goal is 20% more organic traffic in 6 months. Where should I focus?" - Test what context the agent has: "Describe my business as you understand it" — the answer reveals how much Brand Vault context is being used. ⚠️ Error 6: Agent isn't using my Brand Vault information What's happening: Brand Vault may not be linked to the current project, or Brand Vault is incomplete. Steps to try: - Verify Brand Vault has content in every section: More Features → Brand Vault. - Link Brand Vault to your project: OTTO SEO in the left sidebar → All Sites → open your project → Brand Vault. - Start a new chat session — Brand Vault context loads at session start. - Explicitly reference it, even you can type the Vault name. - Contact support if the agent returns no Brand Vault context after completing all sections. ⚠️ Error 7: Agent can't access a tool it's trying to use What's happening: The specific tool's underlying service (Keyword Research, Content Assistant, GSC) was temporarily unavailable. Steps to try: - Wait 5 minutes and ask the agent to try again. - Check if the relevant module works on its own in the dashboard. - Ask the agent: "Which tool failed? Can you try a different approach?" - Ask the agent to skip the failing step and continue with the rest of the task. - Contact support with the specific task and which step failed. ⚠️ Error 8: Complex tasks time out before completing What's happening: Multi-step agent workflows that take more than a few minutes can exceed connection timeouts. Steps to try: - Break large tasks into smaller sequential requests across separate messages. - Check if the agent left partial results — often the first few steps completed before the timeout. - Use the agent's checkpointing: "Continue from where you left off" in a new message. - For long-running jobs, ask the agent to provide a status update every few steps. - Contact support if critical multi-step tasks consistently time out at the same step. The AI Agent is not a static tool—it’s a dynamic system that depends on context, data freshness, integrations, and task clarity. Most issues arise not from failure, but from missing context, outdated data, or overly broad instructions.

🚀 Finding the MetaHub Launchpad in Search Atlas

🔍 What Is the MetaHub Launchpad? The MetaHub launchpad is your central starting point for accessing MetaHub tools and features within Search Atlas. If you are having trouble finding it, this article will walk you through exactly where to look. 🗺️ Where to Find the MetaHub Launchpad The MetaHub launchpad is accessible directly from the Ads section of the platform. Follow these steps: 1. Log in to your Search Atlas account. 2. Look at the left sidebar and click Ads (Which ad platform do you want to see first?). 3. On the Ads page, you will see a collection of playbooks and quick-launch options — the MetaHub launchpad is located here. 4. Browse the available playbooks or use the quick-action buttons to enter MetaHub from this view. 💡 Quick Tips for Navigation - Bookmark the Home page: Navigating to /home in your browser will take you directly to the launchpad area. - Use the sidebar: The left sidebar is your primary navigation tool throughout Search Atlas. If you ever feel lost, returning to Home in the sidebar will reset your starting point. - Refresh your data: If the launchpad does not display as expected, use the Refresh data button available on the Home page to reload the latest information. - Launch Atlas Agent: From the same Home page, you can also launch the Atlas Agent to get guided assistance navigating the platform. ⚠️ Common Reasons You Might Not See It - Wrong section selected: Make sure you have clicked Ads in the left sidebar and not another section such as Content or Reports. - Account permissions: Access to certain launchpad features may depend on your account plan or user role. If a feature appears locked or missing, your plan may not include it. - Browser cache: Try a hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) if the page is not loading correctly. 🛠️ 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.

🧠 Why Your Search Atlas Dashboard Looks Different

If your Search Atlas dashboard suddenly looks different, missing sections, or the screen is entirely taken over by Atlas Brain, don't worry, nothing is broken and nothing has been removed. 👀 What's happening This usually means Atlas Agent (the floating assistant accessible via its icon shown on every page) is open in full-screen mode. This can happen if you clicked the expand/maximize icon within the Atlas Brain panel, or if Atlas Brain launched in an expanded state automatically. When Atlas Brain is maximized, it temporarily covers: - The left navigation - Your avatar and account options - Other dashboard sections This can make it seem like the dashboard changed or that you can't access the main page. 🛠️ How to return to your normal dashboard 1. Look at the top-right corner of the Atlas Brain panel inside the Search Atlas interface (not the browser tab or window close button) 2. Find the X (close) icon on the Atlas Brain window 3. Click the X to exit full-screen mode Your standard Search Atlas dashboard will appear immediately. Note: if a separate minimize or collapse icon is visible alongside the X, use that to preserve your Atlas Brain session and conversation context — the X may close Atlas Brain entirely rather than simply exiting full-screen mode. If you are unsure which icon does what in your current view, hover over each to see its tooltip before clicking. ⚠️ If Atlas Brain is stuck loading or spinning If Atlas Brain appears frozen or shows a spinning loader for more than a few minutes, this is a separate technical issue and not the same as the full-screen display state described above. A known spinning issue in Website Studio was investigated and addressed, but if you are still experiencing this, please contact support with your account details so engineering can investigate further. In the meantime: - Wait briefly to confirm it isn't a temporary load delay - Try a hard refresh (Ctrl+Shift+R on Windows/Linux, or Cmd+Shift+R on Mac) - If the issue persists, please contact support — closing the window will not resolve a genuine stuck state 🔌 If Atlas Brain shows your CMS connector as disconnected If Atlas Brain shows your CMS connector as disconnected even though your WordPress plugin is active, this may be a display error. Your connection may actually be working correctly in the backend. Contact support to verify — do not disconnect and reconnect, as this may interrupt article syncing. 🆕 Recent Atlas Brain UI updates Note: If you see a new-looking Atlas Brain login or registration screen with a chat conversation visible in the background, this is an intentional recent design update — your account and data are unaffected. 🔎 Good to know - Nothing was updated, removed, or reset - The full-screen view is a display state, not a technical issue - No permissions or access were changed - You can reopen Atlas Brain anytime when you need it - If Atlas Brain reports an unexpected connection status (for example, a CMS connector showing as disconnected), the underlying connection may still be active — please contact support to verify before re-configuring your integrations - No data has been lost or changed — this is purely a display/navigation state ✨ In short: If the dashboard looks different, you're just viewing Atlas Brain in full screen. Close it to return to your usual layout—no extra troubleshooting required. If Atlas Brain is frozen or spinning, reach out to support.

🧠 Fix Stuck Atlas Brain Competitor Research Playbooks

🔍 Overview Atlas Brain playbooks can sometimes stall or produce incomplete results during competitor research runs. Because the exact steps to resolve this depend on your specific setup and account configuration, our support team will need to look into this directly with you. What to Have Ready When You Contact Support To help our team investigate and resolve your stalled competitor research playbook as quickly as possible, please have the following details ready before reaching out: - The name of the playbook that is stalling - The project name or workspace where the playbook is saved - The step or stage where the playbook stops or produces incomplete output - Any error messages displayed, copied exactly as they appear on screen - The timestamp of when the issue first occurred - Whether the issue happens consistently or only on certain runs Having these details ready will allow our team to identify the root cause and take the appropriate action on your account without unnecessary back-and-forth. 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.

Atlas Brain Expansion Update – Restore Native Interface View

🔍 What Changed in the Recent Update A recent Search Atlas update introduced an expanded view for Atlas Brain, the platform's AI assistant. When this mode is active, Atlas Brain occupies a larger portion of the workspace, which can cause the left sidebar tools and other navigation elements to appear hidden or inaccessible. If you logged in and were greeted by a large white screen with the Atlas Brain prompt front and center — and your usual navigation was gone — this is related to the Atlas Brain UI expansion update, not a bug or account issue. ⚠️ Symptoms You May Be Experiencing - A large white screen displaying only the Atlas Brain chat prompt - The left sidebar (tools navigation) appears hidden or inaccessible - The interface looks different from what you saw previously - You cannot navigate to other tools while Atlas Brain is in its expanded state 🛠️ How to Return to the Native Interface Try the following steps to exit the Atlas Brain expanded view and restore your standard Search Atlas layout: 1. Refresh the page (press F5 or Ctrl+R / Cmd+R) — reloading the platform can reset the view to the standard layout. 2. Log out and log back in — signing out and back into your Search Atlas account may restore the native interface view. 3. Try a different browser or clear your cache — sometimes a cached state can persist the expanded view. Clearing your browser cache or switching browsers can help. If none of these steps restore your layout, please reach out to our support team and have the following ready to help us resolve this quickly: - Your Search Atlas account email or project name - A screenshot of what your current screen looks like - Approximately when the view change first appeared (date and time if possible) 🔄 About the Atlas Brain Expanded View The expanded Atlas Brain view is a feature introduced in a recent platform update. If your layout has shifted unexpectedly as a result of this update, our support team can help you return to the standard native view where all sidebar tools and navigation are fully accessible. 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.

Resume Paused Atlas Brain AI Sessions

Why Did My Atlas Brain Session Pause? Atlas Brain AI sessions can pause if your computer restarts or your browser closes while a session is in progress. If your session has been interrupted, the steps below will help you get ready to resolve this with our support team as quickly as possible. Before You Begin Make sure you have the following ready before reaching out: - Your Search Atlas account email address. - The name or description of the paused session. - The workspace or project the session was created under (if you manage multiple workspaces). - Approximately when the session was interrupted (date and time). - Any error message or unexpected behavior you noticed before or after the pause. What to Try First Before contacting support, try the following basic checks: 1. Log back in to Search Atlas. Go to app.searchatlas.com and sign in using the same account credentials you used when the session was created. 2. Confirm you are in the correct workspace. Sessions are tied to the specific workspace and account that created them. If you manage multiple workspaces, make sure you have selected the right one. 3. Refresh your browser. A simple page refresh can sometimes restore visibility of a session that was interrupted. 4. Open Atlas Brain. Navigate to Atlas Brain within the platform and check whether your session is still listed or accessible. 5. If your session does not reappear, gather the details listed in the section above and contact our support team — a support agent will be able to investigate and help restore your session. Tips for Avoiding Interrupted Sessions - Name your sessions clearly. Before starting a new AI task, give it a descriptive name so it is easy to identify if you need to reference it later. - Allow sessions to reach a stopping point before closing. When possible, let an active session complete its current step before restarting your computer or closing your browser. - Keep your connection stable. Running Atlas Brain sessions on a stable internet connection reduces the risk of unexpected interruptions. 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.

The Agent and Project Hub: Search Atlas's New Home Screen

With the launch of Search Atlas Brain, the Search Atlas interface has been completely redesigned around an agent-first, action-led philosophy. The new home screen, called the Agent and Project Hub, replaces the traditional dashboard view and puts execution at the center of your workflow. Accessing the Agent & Project Hub The Agent and Project Hub is the new default homepage for Search Atlas. Users who prefer the previous experience can switch to Classic (Home → Classic) by using the Agent Hub toggle in the top-left corner of the interface. Design Philosophy The Hub was designed to solve a common problem: marketers and agencies often spend more time hopping between tools and reports than actually executing work. The new home screen: - Serves as the central homepage for all Search Atlas activity - Eliminates fragmented workflows and tool-hopping - Encourages immediate action instead of passive reporting - Is designed for clear momentum and easy re-entry between sessions What You'll See on the Hub The Hub displays scrollable project tiles for every site in your portfolio. Each tile gives you an at-a-glance view of the project's health and active work. Per-Project Tile Information - Auto Score — Overall project health rating - Traffic snapshots — Recent organic and paid performance - Active local strategies — Local SEO campaigns in progress - Ad campaign structure and performance — Current PPC activity Four-Pillar Grades Each project is graded across the four pillars of digital marketing performance: - Authority — Backlink profile and domain strength - Content — Content quality, coverage, and freshness - Technical SEO — Site health and crawlability - User & behavior signals — Engagement and conversion indicators Access to Traditional Reports For users who still want to dig into traditional metrics, the Hub provides quick access to Portfolio Summary views and detailed reports. You get the speed of action-led navigation without losing access to the deep data Search Atlas is known for.

🔍 Fix a Missing Project in Agent Hub

🧭 Overview If you have projects in Search Atlas but one or more do not appear in the Agent Hub project list, there are several self-serve steps you can try to resolve the issue before reaching out to support. 🔎 Why a Project May Not Appear A project missing from the Agent Hub project list is typically not related to account permissions or access restrictions. If the project is visible in your main Search Atlas dashboard, your account access is intact. The root cause is generally something within the Agent Hub setup for that specific project, but the precise reason varies by case. ✅ Self-Serve Steps to Try First Before contacting support, work through the following steps in order: 1. Refresh the Agent Hub page. Navigate away from Agent Hub and return to it, or do a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to rule out a browser display issue. 2. Check the project in your main Search Atlas dashboard. Confirm the project is active and fully set up there. If it was recently created, allow a few minutes for it to propagate to Agent Hub before checking again. 3. Verify your project count. Count the total number of projects visible in your Search Atlas dashboard and compare that to what appears in Agent Hub. Note the discrepancy so you can report it accurately if escalation is needed. 4. Log out and log back in. Sign out of Search Atlas entirely, clear your browser cache, then sign back in and recheck Agent Hub. 5. Try a different browser or incognito window. This helps rule out browser extension or cache conflicts affecting what projects load in Agent Hub. If the project still does not appear after completing all of the steps above, the issue likely requires a backend investigation by our support team. 📋 What to Have Ready When You Contact Support To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact name of the missing project as it appears in your Search Atlas dashboard. - The total number of projects in your Search Atlas account and how many are currently visible in Agent Hub. - Approximately when you first noticed the project was missing. - Whether the project is newly created or was previously visible in Agent Hub and has since disappeared. - Any error messages you may have seen, with the exact wording. - Confirmation of which self-serve steps above you have already completed. 🚫 What This Issue Is Not A missing project in Agent Hub is not caused by deactivated accounts, incorrect permissions, or access restrictions. If you can see the project in the main Search Atlas dashboard, your account access is fine. 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.

🗂️ Add Multiple Client Sites to Agent Hub

🔍 Overview Agent Hub displays only the sites that meet specific setup requirements. If you manage multiple clients but see only a handful of active projects, some of your sites may not yet have completed the necessary setup steps. ⚠️ Why Some Sites May Be Missing from Agent Hub Not all sites in your account automatically appear as active projects in Agent Hub. A site typically needs to have the required setup completed before it will show up. If you are seeing fewer sites than expected, the setup status of those sites is the most likely cause. ✅ Prerequisites for a Site to Appear as an Active Project Before a client site will show up as an active project in Agent Hub, make sure each of the following is in place: - The site has been added to your Search Atlas account as a project. If a site has not been created as a project yet, it will not appear in Agent Hub regardless of other settings. - OTTO SEO has been activated for the site. Agent Hub surfaces sites that have OTTO enabled. Sites without an active OTTO connection will not appear. 🚀 Steps to Add Multiple Client Sites to Agent Hub Follow these steps for each client site you want to appear as an active project in Agent Hub: 1. Log in to your Search Atlas account and navigate to your list of projects. 2. Confirm each client domain has been added as a project. If a site is missing, create a new project for that domain before proceeding. 3. Open the project for the client site and check whether OTTO SEO has been activated. If it has not been activated, enable OTTO for that project. 4. Return to Agent Hub and verify that the site now appears as an active project. 5. Repeat for each additional client site until all expected projects are visible in Agent Hub. 💡 Tips for Managing Multiple Sites Efficiently - If you are adding many sites at once, work through them in batches and confirm each site's setup status before moving to the next. - If a site still does not appear in Agent Hub after completing all setup steps, double-check that the project was created correctly and that OTTO has been fully activated for that project. - When contacting support, have the affected domain names and your account details ready so the team can assist you quickly. 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.

Edit llms.txt and Merge Atlas Agent Output

Overview This article covers how to locate and edit your llms.txt file when using the Search Atlas WordPress plugin, and how to incorporate Atlas Agent output into that file. Because the specific behavior of your setup may vary, the steps below describe common approaches — if anything does not match what you see, contact our team for guidance tailored to your configuration. Where the llms.txt File Lives When the Search Atlas WordPress plugin is configured to serve llms.txt through your domain, the content may come from a physical file in your WordPress root directory (the same level as wp-config.php) or from plugin-generated output. To check whether the file is being served, visit https://yourdomain.com/llms.txt in a browser after enabling the option in the plugin settings. If you are unsure which source your plugin is using, reach out to our support team before making edits. How to Edit the llms.txt File 1. Connect to your server using an FTP client (such as FileZilla) or your hosting provider's file manager. 2. Navigate to the root directory of your WordPress installation — this is the folder that contains wp-config.php, wp-content, and wp-admin. 3. Check whether a file named llms.txt already exists. - If it exists, open it and edit the content directly. - If it does not exist, create a new plain-text file named llms.txt in that directory. 4. Save the file and reload https://yourdomain.com/llms.txt to verify your changes are live. Important: Use a plain-text editor only (such as Notepad, VS Code, or nano). Do not use a word processor like Microsoft Word, as it may insert hidden formatting characters. Merging Atlas Agent Output into llms.txt The Atlas Agent does not write directly to your llms.txt file. To merge its output, follow these steps: 1. Retrieve the text output you want to include from the Atlas Agent within the Search Atlas platform. 2. Copy that output text. 3. Open your llms.txt file on the server using FTP or your hosting file manager, as described in the section above. 4. Paste the copied content into the file, placing it in a logical position consistent with the formatting and structure already present in the file (for example, appending it after existing entries or inserting it under a relevant section heading). 5. Save the file and verify the updated content appears at https://yourdomain.com/llms.txt. Tips for a clean merge: - Review your existing llms.txt content first so you understand its current structure before adding new content. - Avoid duplicate entries — if the Atlas Agent output overlaps with existing content, consolidate them manually. - 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.

🔧 Fixing Atlas Agent 400 Errors and Keyword Data

Overview If you are seeing a Request failed: 400 error while using the Atlas Agent on content tasks, or if your keyword data is not loading correctly, this article will walk you through the most common causes and how to resolve them quickly. These errors are typically caused by expired sessions, stale cache data, API timeouts, or a temporary backend issue — none of which reflect a problem with your account or subscription. What Does a 400 Error Mean? A 400 (Bad Request) error occurs when the platform cannot process the request sent by your browser or session. In the context of the Atlas Agent and content analysis tools, this usually means one of the following: - Your session has expired or become invalid mid-task - The browser has cached outdated authentication or request data - A temporary backend service interruption is affecting API responses - A request timed out before the server could respond correctly - Your SSO (Single Sign-On) token has expired and needs to be refreshed Step-by-Step Troubleshooting Follow these steps in order. Most customers resolve the issue within the first two or three steps. 1. Refresh the page. Reload the page in your browser and retry your Atlas Agent task or keyword data request. This resolves temporary communication errors caused by brief API timeouts. 2. Clear your browser cache and cookies. Stale cached data is a leading cause of 400 errors. Access your browser's settings and clear cached files and cookies, then reload the platform and sign back in. The exact steps vary by browser — refer to your browser's help documentation if needed. 3. Sign out and sign back in. Go to your account menu and select Sign Out. Wait 30 seconds, then sign back in. This refreshes your session token and resolves the majority of authentication-related 400 errors. 4. Re-authenticate via SSO if applicable. If your organisation uses Single Sign-On, your SSO token may have expired without triggering a visible logout. Sign out completely, then log back in through your SSO provider to obtain a fresh token before returning to Search Atlas. 5. Try a different browser or incognito window. Open an incognito or private window (or a different browser entirely) and sign in to Search Atlas. If the Atlas Agent and keyword data load correctly in this context, the issue is isolated to a browser extension, cached data, or a profile-specific setting in your main browser. 6. Disable browser extensions. Ad blockers, privacy tools, and script blockers can interfere with API requests. Temporarily disable extensions, reload the platform, and retry your task. If Keyword Data or SEO Rankings Are Still Not Showing If the 400 error clears but your keyword data or SEO ranking informa 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 Search Atlas Coworker Handles Your Data & Permissions

This article explains what data Search Atlas Coworker can access, how your credentials are stored, and what controls are available for your team. What Data Search Atlas Coworker Can See Search Atlas Coworker only accesses data from services you have explicitly connected: - Search Atlas — your account's SEO data, projects, keywords, reports, and connected GSC properties - Connected third-party apps — only the data within the permissions you granted during the OAuth flow Search Atlas Coworker does not have access to Slack message history, other team members' DMs, or any service you have not authorized. How Credentials Are Stored OAuth tokens for connected apps are stored securely and are never visible in Slack conversations. Search Atlas Coworker will never display your credentials, API keys, or tokens in chat. If you need to rotate credentials, disconnect and reconnect the app. Conversation Data Messages you send to Search Atlas Coworker are used to fulfill your request and may be retained temporarily to maintain context within an active conversation. Search Atlas Coworker does not use your conversations to train AI models. User Controls vs. Admin Controls - Individual users — can connect and disconnect their own accounts and apps, create and manage their own routines, and control which data Search Atlas Coworker accesses on their behalf - Workspace admins — can configure which channels Search Atlas Coworker can post in, pre-authorize certain connector actions for all users, and revoke access at the workspace level See Managing Search Atlas Coworker Permissions (for Workspace Admins) for the full admin configuration guide. Revoking Access To fully disconnect Search Atlas Coworker from your Search Atlas account, ask it: "Disconnect my Search Atlas account" or revoke access in your Search Atlas account menu (avatar) under Settings → Integrations. Revoking access stops all data access immediately, including active routines.

🛡️ Managing Search Atlas Coworker Permissions (for Workspace Admins)

Workspace admins have additional controls over how Search Atlas Coworker behaves across your Slack workspace. This article covers what admins can configure and how. What Admins Can Control - Which Slack channels Search Atlas Coworker is allowed to post in - Whether connector actions require per-request approval or are pre-authorized - Revoking Search Atlas Coworker access for specific users or across the entire workspace - Managing Search Atlas Coworker access for teams with multiple Search Atlas sub-accounts Channel Permissions By default, Search Atlas Coworker can only post in channels it has been explicitly invited to. To add or remove Search Atlas Coworker from a channel: - Add: invite Search Atlas Coworker to the channel using /invite @Search Atlas Coworker - Remove: remove Search Atlas Coworker from the channel using /remove @Search Atlas Coworker or via the channel's member settings Pre-Authorizing Connector Actions Search Atlas Coworker can act in connected apps automatically or require user approval — depending on workspace settings. The default behavior is controlled by the Run connector actions without asking toggle in Workspace Settings (in the Search Atlas Coworker dashboard or in Slack under Apps → Atlas Agent → Home → Workspace Settings). As a workspace admin, you can also require approval for specific tools per connector — or grant always-allowed status for trusted tools. To configure pre-authorized actions, contact Search Atlas support or access the Search Atlas Coworker settings from the left sidebar → Coworker → Settings. Revoking Access for a User If a team member leaves or you need to revoke their Search Atlas Coworker access: 1. In the Search Atlas admin panel, go to Team > Users. 2. Select the user and click Revoke Search Atlas Coworker Access. 3. The user's Search Atlas connection and any connected apps they authorized will be disconnected immediately. Their routines will be paused. Revoking Workspace-Wide Access To remove Search Atlas Coworker from your entire Slack workspace, uninstall the Search Atlas Coworker app from your Slack workspace settings under Apps > Manage Apps. All user connections, routines, and connector authorizations will be terminated. Managing Multi-Account or Agency Setups If your team works across multiple Search Atlas sub-accounts, each user links their own Search Atlas account individually. Contact Search Atlas support if you need workspace-level account mapping for your agency setup.

🗺️ Navigating the New Search Atlas Agentic Homepage

🔍 Overview Search Atlas recently launched a redesigned Agentic Homepage that changes how you access the Dashboard, Hub, and core tools. If the layout looks unfamiliar or you cannot locate the sections you need, this article walks you through the new structure and provides direct navigation paths to get you back on track quickly. 🖥️ Understanding the New Layout The Agentic Homepage replaces the previous Dashboard with a streamlined, project-focused interface. The main navigation now lives in the left sidebar, which organises all tools into clearly labelled sections. The traditional Dashboard and Hub views may now appear as entry points within specific sidebar sections rather than as standalone top-level pages. If your screen looks different from what you expect, use the steps below to orient yourself. 🧭 How to Navigate Using the Left Sidebar All major tools are accessible directly from the left sidebar. Here are the primary sections and how to reach them: - Site Metrics — Click Site Metrics in the left sidebar to reach your project overview and SEO data (/site-explorer/list). From here you can access: - Keyword Magic — Left sidebar → Keywords → Keyword Magic - Rank Tracker — Left sidebar → Keywords → Rank Tracker (Keyword Rank Tracker) - Keyword Gap — Left sidebar → Site Metrics → Keyword Gap - Local — Click Local in the left sidebar, then select GBP Projects to manage your local SEO projects (GBP Projects) (/gbp-galactic/gbp-projects). Sub-sections include: - Left sidebar → Local → Overview - Left sidebar → Local → Media Library - Left sidebar → Local → My Tasks - Left sidebar → Local → Posts - Left sidebar → Local → Reviews - Left sidebar → Local → Local Citations If the left sidebar is not visible, try widening your browser window or scrolling to the far left of the screen. The sidebar may be collapsed on smaller screens. ✅ Step-by-Step: Recovering Your Navigation 1. Refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full reload and clear any cached layout issues. 2. Check for a collapsed sidebar. Look for a small arrow icon or a hamburger menu (☰) on the left edge of your screen. Click it to expand the sidebar. 3. Navigate directly by URL. If the sidebar is loading but tools are missing, go directly to a known section: - Site Metrics list: /site-explorer/list - Local projects: /gbp-galactic/gbp-projects 4. Switch to a supported browser. Search Atlas works best on the latest versions of Google Chrome or Microsoft Edge. If you are using Firefox, Safari, or an older browser version, some layout elements may not render correctly. Update your browser or switch to Chrome and reload the platform. 5. Disable browser extensions. Ad blockers and script-blocking extensions can interfere with sidebar rendering. Temporarily disable extensions, then reload the page. 6. Clear your browser cache and cookies. Go to your browser settings, clear cached images and cookies for the Search Atlas domain, then log back in. 7. Try an incognito/private window. This rules out extension conflicts and stale session data. Open an incognito window, log in to Search Atlas, and check whether the layout loads correctly. 🔐 Check Your Account Permissions Some sections of the Agentic Homepage are visible only to users with the appropriate role or active subscription features. If a sidebar section is missing entirely, consider the following: - Confirm with your account administrator that your user role has access to the section you need (for example, Local tools require a Local plan or add-on). - Ask your admin to review your permissions under the account settings and ensure the correct features are enabled for your profile. - If you recently upgraded or changed your plan, log out and log back in to refresh your session permissions. 🌐 Browser Compatibility For the best experience with the new Agentic Homepage layout, use the following: - Recommended browsers: Google Chrome (latest), Microsoft Edge (latest) - Minimum screen resolution: 1280 × 720 pixels - JavaScript: Must be enabled — the sidebar and homepage rely on JavaScript to render correctly - Zoom level: Keep your browser zoom between 80% and 100%. Higher zoom levels can push the sidebar off-screen 🚀 Alternative Entry Points If you still cannot reach a specific tool, use these direct paths as alternative entry points while your main navigation is being resolved: - Go to Site Metrics via the left sidebar to access all keyword and ranking tools. - Go to Local → GBP Projects via the left sidebar to access all GBP and local citation tools. - Use your browser's address bar to type the direct URL path for the section you need (see the URLs listed earlier in this article). 💬 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.

🤖 Specialized Agent Roles and Capabilities

Atlas Agent operates as an execution engine by delegating marketing work to specialized AI agents. This agent-based architecture is fundamental to the platform's ability to handle complex, multi-step execution while scaling results at the speed of AI. Rather than relying on a single, general-purpose system, Atlas Agent uses focused agents, each designed to excel at a specific function. 🧩 The Specialized Agent Model Execution inside Atlas Agent is handled by specialized agents, each trained to do one thing exceptionally well. These agents leverage the Search Atlas platform backbone, including embedded business logic, proven best practices, and platform-level automation, allowing them to orchestrate multi-step, complex workflows while maintaining consistency and reliability. You should distinguish between the general Atlas Agent, used for broader queries, reports, exploration, or new account onboarding, and specialized agents, required for executing specific tasks, Playbooks, or workflows (for example, the Auto Agent, Authority Agent, and Local Agent). When execution matters, engage the agent designed for that specific function. 🧠 Key Agent Roles - Onpage Optimization (Auto Agent): Handles technical SEO fixes, including page titles, meta descriptions, and heading structure. - Content Strategy and Generation: Manages content strategy, AI generation of articles and landing pages, and webpage creation. - Local and GBP Optimization: Executes local campaigns, builds citations, optimizes Google Business Profiles, and deploys fixes for services and attributes. - Authority and Link Building: Runs outreach and link-building campaigns, including prospecting, press release generation, and cloud stack creation. - Paid Search (PPC): Creates, launches, and continuously optimizes paid search campaigns. - Reporting and Research: Manages client reporting and executes keyword, traffic, and competitive research. 🛡️ The Agent as a Quality Assurance Layer Specialized agents play a role in quality control and risk management, acting as a QA layer over both implementation and recommendations before deployment. Agents can challenge suggestions generated by the platform's core AI: you can prompt an agent to re-evaluate the quality of recommendations, and it can generate improved alternatives and explain what was changed. Agents are trained with risk-aware safeguards, particularly in sensitive areas such as local SEO, where high-risk changes (business name, phone number) require explicit verification to avoid GBP reverification issues, while low-risk changes (services, attributes) are executed safely without unnecessary friction. ⚡ Scaling Execution Through Concurrency You are encouraged to open multiple agentic windows side by side, letting multiple specialized agents work simultaneously across different projects or marketing dimensions. For example, while one agent builds authority through outreach, another can fix technical SEO issues or optimize local SEO at the same time. 🧭 Operational Guidance Always ensure the agent you select matches the task: use the Authority Agent for press releases or link building, the Content Agent for content generation, and the Auto Agent for technical SEO fixes. If you submit a request to the wrong agent, the system will state what that agent cannot do and guide you to the correct one. Specialized agents are the mechanism that allows Atlas Agent to function as a true execution engine, combining focused expertise, built-in QA, risk-aware safeguards, and concurrent execution. 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.

🧠 Atlas Brain Mode: Navigation and Billing Access

🔍 Overview Atlas Brain is a focused AI mode within Search Atlas that transforms the dashboard into a dedicated content-research interface. While Atlas Brain is active, the standard navigation elements — including the top-right profile avatar dropdown — may be hidden or inaccessible. This is by design, but it can make it difficult to find your billing page or account settings if you are not aware of this behaviour. If you attempted to open your account dropdown and it did not appear, you may be operating inside Atlas Brain mode. This article explains what Atlas Brain is, how to recognise it, and how to exit it so you can reach your account settings and billing page. 🧩 What Is Atlas Brain? Atlas Brain is an immersive AI research environment built into the Search Atlas platform. When active, it replaces the standard dashboard layout with a focused interface designed for deep content and SEO research tasks. A key characteristic of Atlas Brain mode is that standard navigation elements — including the account dropdown — may not behave as expected while this mode is active. Because the account dropdown may be inaccessible in this mode, actions such as managing your subscription, viewing invoices, or accessing team settings cannot be completed until you exit Atlas Brain. 🚪 How to Exit Atlas Brain Mode To leave Atlas Brain and restore full dashboard navigation, you will need to exit the Atlas Brain interface and return to the main Search Atlas dashboard. Because the exact exit control depends on your current view within Atlas Brain, here is what to try: - Look for a button, link, or icon within the Atlas Brain interface that is labelled something like Back, Exit, or Dashboard and click it to return to the standard layout. - If no such control is visible, try clicking on any top-level navigation item that is still accessible to navigate away from the Atlas Brain environment. - If neither of the above works, contact our support team (see below) and let them know you are unable to exit Atlas Brain mode — they can guide you through the specific steps for your account. Once you are back on the standard dashboard, confirm that the account dropdown is accessible again before proceeding to billing. 💳 How to Access the Billing Page Billing is managed through the Billing page, accessed via the avatar in the top-right (Billing). After successfully exiting Atlas Brain and returning to the standard dashboard, use the account navigation to locate your Account Settings, then find the billing or subscription-related section to view your plan, invoices, and payment details. If the account dropdown or billing area is still inaccessible after exiting Atlas Brain, try refreshing the page and attempting the steps above again. If the problem persists, our support team can assist you directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧠 Agentic SEO: Preparing the Web for the Era of LLMs and AI Agents

Search is no longer consumed exclusively by humans. Modern search engines and AI systems, particularly Large Language Models (LLMs) and autonomous agents, must interpret, summarize, and reason about the web at scale. In this environment, relying on raw HTML alone is increasingly inefficient and error-prone. Schema is no longer a "nice to have." It has become core infrastructure for making websites understandable, reliable, and trustworthy to machines. Search Atlas approaches schema not as static markup, but as a pre-computed understanding layer that prepares the web for agentic search. ⚙️ Pre-Computing Understanding for Machines Search engines and LLMs face a fundamental problem: inferring structure from unstructured HTML is expensive, slow, and ambiguous. To understand a single page, machines must infer: - What the page represents - Which entities exist - How those entities relate to each other - What information is factual versus contextual Schema solves this by acting as pre-computed structure. Instead of forcing machines to guess, schema explicitly defines: - Page purpose - Entity relationships - Content types - Business, product, or service context This dramatically reduces the cost of information retrieval for both traditional search engines and AI systems. 🧩 Reducing Ambiguity and Hallucinations in AI Search AI agents are far less tolerant of ambiguity than humans. When information is implicit or loosely structured, LLMs are more likely to: - Misinterpret context - Combine unrelated facts - Produce hallucinated outputs Explicit structured data: - Reduces cognitive load for machines - Provides non-negotiable factual anchors - Lowers hallucination risk - Increases confidence in downstream reasoning In an AI-driven search landscape, schema directly contributes to answer quality, not just visibility. 📊 First-Party Data Layered Over Technical Audits Unlike static schema plugins, Search Atlas does not treat schema in isolation. The system layers first-party data directly over technical audits, including: - Google Search Console performance - GA4 engagement metrics - Revenue and conversion data (where available) This allows teams to answer a critical question: 👉 Which pages actually matter most from an economic and business perspective? By combining crawl intelligence with real performance data, Search Atlas enables: - Priority-based schema deployment - Smarter technical decisions - Focus on pages that drive revenue, not just traffic 🧱 Machine-Readable Quality as Core Infrastructure In the era of AI search, schema is no longer cosmetic. Many AI systems: - Do not fully render HTML - Do not execute JavaScript reliably - Prefer immediate, structured signals Schema becomes a quality signal for machines that may never "see" a page the way a browser does. Well-structured schema tells AI systems: - This page is intentional - This information is verified - This content is trustworthy - This entity is well-defined Five years ago, schema was an enhancement. Today, it is foundational infrastructure for machine readability. 🚀 Why Search Atlas Is Fundamentally Different Traditional schema tools are: - Template-based - Static - Hard-coded - Brittle - Blind to context Search Atlas delivers dynamic, context-aware schema that adapts to each page's purpose, entity relationships, and real-world performance signals — rather than applying one-size-fits-all markup templates. This means schema that is always relevant, always accurate, and always aligned with how AI systems expect to consume structured information on the modern web. 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.

🤖 Resume Paused Atlas Brain AI Sessions Easily

🔍 Why Did My Atlas Brain Session Pause? Atlas Brain AI sessions may pause or appear interrupted after a computer restart, browser closure, or unexpected disconnection. If you encounter this situation, our support team can look into the session state for your account and guide you through the correct steps to continue your work. 📋 What to Have Ready Before Contacting Support To help our team resolve this as quickly as possible, please have the following information ready: - Your Search Atlas account email address - The name or project associated with the Atlas Brain session you want to resume - The approximate date and time when the session paused or was interrupted - A brief description of what the Atlas Brain agent was working on when it stopped ⚠️ What to Expect Because Atlas Brain session recovery depends on the specific state of your account and agent task at the time of interruption, the exact steps to resume your session may vary. A member of our support team will review your session details and provide instructions tailored to your situation. Do not attempt to restart or duplicate the session before speaking with support, as this may affect the ability to recover your previous 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.

📊 Why Classic Dashboard and Agent Hub Show Different Scores

🔍 Overview If you've noticed that your SEO scores or OTTO scores look different between the Classic Dashboard and the Agent Hub, you're not seeing a bug. These two views are built for different purposes and may display different values for the same site. This article explains what to do when you spot a discrepancy and which view to rely on. 🏗️ What Each View Is Designed For Classic Dashboard is your site-level workspace. It gives you a detailed view of a single website's SEO health, OTTO activation status, and optimization progress for that specific domain. Agent Hub is your portfolio-level command center. It is designed to help you monitor and manage multiple websites at a glance across your entire portfolio. ✅ Which View to Trust When the scores shown in Classic Dashboard and Agent Hub do not match, use the following guidance: - For site-specific decisions — such as checking OTTO task progress, reviewing optimization status, or diagnosing SEO issues on a single domain — rely on the Classic Dashboard. It reflects the most up-to-date data for that individual site. - For portfolio-level monitoring — such as comparing relative performance across multiple sites or identifying which sites need attention — use Agent Hub. Treat its scores as directional indicators rather than precise per-site figures. 🔄 What to Do When You See a Discrepancy 1. Open the affected site directly in Classic Dashboard to view its current SEO and OTTO scores. 2. Compare those values against what Agent Hub is displaying for the same site. 3. If Classic Dashboard shows the expected score and Agent Hub does not, wait and check Agent Hub again later — portfolio views may not reflect recent changes immediately. 4. If Classic Dashboard itself is showing an unexpected score after a recent crawl or OTTO activation, allow time for the data processing cycle to complete, then reload the page. 5. If the discrepancy persists in Classic Dashboard or you believe the score is incorrect, note the project/site name, the score values shown in each view, and the date and time you observed the issue, then contact support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧠 Understanding Atlas Brain Schema Deployment Results

🔍 Overview When Atlas Brain completes a schema scan, you may notice that the number of deployed schemas is lower than the total number of schemas listed. This is expected behavior, not a technical error. Understanding the difference between Found schemas and Suggested schemas explains why this happens. 📂 Found vs Suggested Schemas: What's the Difference? Found schemas are schemas that Atlas Brain detects already existing on your website during its initial scan. These schemas are live on your pages and were added either manually, by a plugin, or through a previous deployment. Because they are already present, Atlas Brain does not deploy them again — this avoids creating duplicate structured data on your pages. Suggested schemas are new schemas that Atlas Brain recommends adding to your pages based on its analysis. These are schemas your site does not currently have. When you run a deployment, Atlas Brain installs only the Suggested schemas — the ones that are genuinely missing from your pages. 📊 Why Your Numbers Don't Match The total schema count shown in Atlas Brain includes both Found and Suggested schemas combined. Your deployment count reflects only the Suggested schemas that were successfully installed. Here is a simple breakdown of what each number means: - Total schemas listed: All schemas identified across your site, including ones already present (Found) and ones recommended for addition (Suggested). - Deployed schemas: The Suggested schemas that Atlas Brain successfully added to your pages during deployment. - The difference: The Found schemas — already live on your site before Atlas Brain ran. These are skipped to avoid duplication. A successful deployment status confirms that all Suggested schemas were installed correctly. The gap between total and deployed does not indicate an error. ✅ How to Confirm Everything Deployed Correctly 1. Open Atlas Brain from your Search Atlas dashboard. 2. Locate your most recent deployment and check its status. 3. Review the schema breakdown to see how many schemas are labeled Found versus Suggested. 4. If you want to verify schemas on a specific page, use the Google Rich Results Test (search.google.com/test/rich-results) to confirm all structured data is rendering correctly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Classic View Toggle Unclickable in Agent Hub

🔍 Overview Some users found that the Classic view toggle in the left sidebar under Home → Classic could not be clicked, making it impossible to switch back to Classic mode. This was caused by a full-screen loading overlay that appeared while playbooks were loading, blocking interaction with the toggle button. This issue has been identified, tracked, and resolved by the Search Atlas engineering team. If you encountered this problem before, the fix is now live and you should be able to use the toggle normally. ⚠️ What Was Happening When the Agent Hub homepage loaded, a full-screen playbook loading overlay would sometimes appear and remain on top of the page. This overlay blocked click interactions with the Classic view toggle, even though the button was visible on screen. The result was a toggle that looked active but could not be selected. Additional related issues that were fixed at the same time include: - Non-clickable areas on the Classic and Agent Hub toggle button on the homepage - Classic mode toggle not appearing at all for some Classic View users - Homepage connector and scheduled job rows being unresponsive to clicks ✅ What To Do Now 1. Refresh your browser to make sure you are running the latest version of the platform. 2. Navigate to the Agent Hub homepage. 3. Try clicking the Classic view toggle again to switch between views. 4. If the toggle responds and switches the view as expected, the fix is working correctly for your account. 🔄 If the Toggle Is Still Unresponsive In rare cases, a cached version of the page may still cause the issue to appear. Try the following before contacting support: - Hard refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). - Clear your browser cache and cookies, then reload the platform. - Try a different browser or an incognito/private window to rule out a browser-specific conflict. - Check whether the issue occurs on a different device or network. If none of these steps resolve the problem, the issue may be account-specific and will need to be reviewed by our team. 💬 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 Atlas Brain Fetch Errors

If you are seeing a 'failed to fetch' error in Atlas Brain, this article covers general troubleshooting steps you can take and what information to collect if the issue needs to be escalated to our team. General Troubleshooting Steps 1. Refresh the page. A simple page refresh can resolve temporary connection issues between your browser and the Atlas Brain service. 2. Clear your browser cache and cookies. Stale browser data can sometimes interfere with requests. Clear your cache, reload the platform, and try your prompt again. 3. Try a different browser or incognito mode. This helps rule out browser extensions or cached sessions as the cause. 4. Test with a simple prompt. Enter a basic prompt (e.g., 'Summarize my latest project') to see whether the error occurs regardless of prompt complexity. 5. Check your internet connection. Intermittent connectivity can cause fetch errors. Confirm your connection is stable before retrying. 6. Log out and back in. Signing out of the platform and signing back in can refresh your session and resolve authentication-related fetch errors. If the Error Persists If the 'failed to fetch' error continues after trying the steps above, the issue may require investigation by our engineering team. Please have the following information ready when you reach out so we can diagnose the problem quickly: - Exact error message — the full text of the error you see, including any codes or details. - Timestamps — when the error started and whether it happens every time or only intermittently. - Prompt details — the type of prompt or input you were using when the error appeared. - Browser information — your browser name and version, and whether you tried other browsers. - Project context — the project name or workspace where the error is occurring. - Recent changes — any recent changes to your account, projects, or connected data sources. Providing these details upfront will help our team reproduce the issue and identify a root cause faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix Missing Projects in Agent Hub Portfolio List

Overview If a project is visible in other parts of the platform but missing from your Agent Hub portfolio list, you are not alone. This is a known sync issue that can affect projects in your account. Your project data is not lost — this is a display issue between the two interfaces. Why This Happens The Agent Hub portfolio list and other platform views pull project data differently. In some cases, a project may not immediately surface in the Agent Hub portfolio list, even when it is fully configured and working elsewhere in the platform. This is a sync gap between the two interfaces, not a loss of data or project configuration. What to Do If Your Project Is Missing Because this is a backend sync issue, our support team will need to look into your specific account to resolve it. To help us do that as quickly as possible, please have the following ready when you reach out: - The exact name of the project that is missing from Agent Hub - Confirmation of whether the project is visible in other parts of the platform - The approximate date and time you first noticed the project was missing - Your account email or workspace name What Will Not Be Affected This issue is a display sync problem. Your underlying project data and configurations remain intact regardless of whether the project appears in the Agent Hub portfolio list. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Fix Atlas Agent 400 Errors in Content Genius

Overview When using Atlas Agent inside Content Genius, you may encounter a "Request failed: 400" error. This can occur during various content workflows. Because the root cause of this error requires investigation on the backend, our support team will need to look into your specific case to identify and resolve it. What Is Happening A 400 error from Atlas Agent indicates that a request was rejected or could not be processed. The underlying reason can vary and is not always visible from the platform interface. This is a known error type that our team investigates on a case-by-case basis. What to Try While You Wait - Refresh the page. Reload Content Genius and attempt your action again — a fresh page load can sometimes clear transient errors. - Try a different browser or incognito window. Open the platform in a private/incognito window or a different browser to rule out browser-specific issues. - Clear your browser cache. Outdated cached data can occasionally interfere with platform requests. Clear your cache, then reload and try again. What to Have Ready When You Contact Support To help our team investigate as quickly as possible, please have the following information ready before reaching out: - The exact error message you see (e.g. "Request failed: 400") - The name of the article or project you were working on in Content Genius - The specific action you were performing when the error appeared - The approximate date and time the error occurred (including your timezone) - Any steps you already tried to resolve it 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.

🔍 Atlas Agent Meta Description Verification Explained

🧭 Overview Atlas Agent audits your pages and flags SEO issues, including missing or incomplete meta descriptions. In some cases, customers have noticed that the agent flags a page as having an incomplete meta description even when the full meta tag is present in the page source. This article explains why that happens and what you can do about it. ⚙️ How Atlas Agent Fetches Metadata When Atlas Agent inspects a page, it attempts to retrieve live metadata directly from the published URL. In some cases, the version of the meta description the agent reads may not match what is present in the full live HTML source. The specific technical reasons for this behavior are confirmed by our team on a case-by-case basis. 🚩 Why a Page Gets Flagged Incorrectly Atlas Agent may flag a blog page or any other page with an incomplete meta description warning even when the tag exists in full. The most common cause is that the agent is reading a version of the description that does not reflect the complete raw meta tag value. If you have verified your meta description is present and correct in the live page source, the flag may represent a detection discrepancy rather than a real SEO problem on your page. ✅ How to Confirm Your Meta Description Is Correct Before raising a concern, verify the actual state of your live meta description using these steps: 1. Open your browser and navigate to the published page URL. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) and search for meta name="description". 4. Check the content="" attribute to confirm the full description is present and correctly written. 5. If the tag is complete in the source but Atlas Agent still flags it, the issue is likely a detection discrepancy — not a real SEO problem on your page. 🛠️ What to Do When the Flag Appears Incorrect If Atlas Agent flags a meta description that you have confirmed is complete and correct in the live page source, you do not need to alter your actual meta description. If the flag persists or you are unsure whether the flag reflects a real issue, please reach out to our support team with your project name, the affected page URL, and a screenshot of your page source showing the meta description tag so we can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix an OTTO Project Missing from Atlas Brain

🔍 Overview If your OTTO project is active but does not appear in Atlas Brain or the playbook, you will not be able to add it or run on-page SEO fixes through Atlas Brain. This is a known sync issue that requires a manual resync from the Search Atlas team. The steps below will help you confirm the issue, attempt a self-service refresh, and gather everything needed so support can resolve it as quickly as possible. ⚠️ What Causes This Issue This problem occurs when an OTTO project exists in the OTTO projects list but fails to sync into Atlas Brain automatically. As a result, the project is missing from Atlas Brain, and you cannot run playbook fixes or on-page SEO tasks for that domain. This is a platform-level sync issue and is not caused by anything you have done incorrectly. ✅ How to Confirm You Are Affected - Your website domain is listed as an active project in OTTO. - The same project does not appear when you open Atlas Brain. - You cannot run playbook fixes or on-page SEO tasks for that domain through Atlas Brain. 🛠️ Steps to Take 1. Verify the project is active in OTTO. Check that your domain is listed and active in your OTTO projects. If it is not active, activate it before proceeding. 2. Check Atlas Brain for the project. Open Atlas Brain and look for your domain. Confirm it is genuinely missing and not simply hidden by a search term or filter. 3. Do not attempt to re-add the project. Trying to add the same project again will return a Request failed: 400 error because the backend already has a record of it. Additional re-add attempts will not resolve the issue and may complicate the fix. 4. Perform a hard browser refresh. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full reload of the page. Then recheck Atlas Brain to see whether the project now appears. 5. Clear your browser cache and log out, then log back in. Clear your browser cache, log out of Search Atlas, log back in, and navigate to Atlas Brain again. This ensures you are not viewing a stale cached version of the project list. 6. Try a different browser or incognito window. Open Search Atlas in a different browser or in a private/incognito window and check Atlas Brain. If the project appears there, the issue is isolated to your browser environment. If it is still missing, the problem is a backend sync issue. 7. Contact support for a manual resync. If the project remains missing after completing the steps above, the fix requires a backend resync that only the Search Atlas team can trigger. Reach out to our support team and share your domain URL along with confirmation that the project is active in OTTO but missing from Atlas Brain. The support team will escalate to a specialist who can perform the resync. To reach us, open the chat widget in the bottom-right corner of the platform and type human teammate. 📋 What Happens After You Contact Support Once you report the missing project, the support team will escalate the issue to a specialist who can trigger a manual resync. In the confirmed case, the resync was completed quickly and the customer confirmed the project appeared in Atlas Brain immediately afterward. You do not need to recreate the project or make any changes to your OTTO setup. 📝 Information to Have Ready - Your domain URL as it appears in OTTO. - Confirmation that the project is active in OTTO but not visible in Atlas Brain. - Which browsers or devices you already tried, and whether the project appeared in any of them. If you need further help, open the chat widget in the bottom-right corner of the platform and type human teammate. Additional Notes Gather before contacting support: the exact domain/project name, a screenshot or description of the 400 error received when attempting to re-add, and your account email or workspace identifier.

🛠️ Project Missing From Atlas Agent Playbooks

🔍 Overview Some users have reported that a project they added to their account is visible in Site Explorer but does not appear in the Atlas Agent playbooks window, making it impossible to run playbooks for that project. In some cases, this same underlying sync issue can also cause additional symptoms such as backlink reports or other data tabs showing no data, or growth-plan features appearing locked. ⚙️ Is This a Known Issue? Yes. Missing projects in the Atlas Agent playbooks window is a known issue that the Search Atlas support team has investigated and resolved for affected users. The fix requires a backend correction applied by the support team to your specific account — it cannot be resolved by changing any setting on your end. ✅ Steps to Try First Before reaching out, try the following basic troubleshooting steps: 1. Hard-refresh your browser. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to clear cached data and reload the latest version of the platform. 2. Try a different browser or incognito window. This rules out browser extensions or locally cached data as the cause of the missing project. 3. Log out and log back in. Sign out of your Search Atlas account completely, then sign back in. This ensures your session reflects the latest project data. 4. Verify the project is active. Confirm the project is still listed and active in your account. If it was recently added or modified, allow a few minutes for the platform to sync. 5. Open Atlas Agent and check the playbooks window again. Navigate to the Atlas Agent and look for your project in the playbooks window. 📋 What to Do If the Problem Persists If your project is still missing from the Atlas Agent playbooks window after completing the steps above, please contact our support team. A support agent will apply a backend fix to your account so the missing project appears correctly in the Atlas Agent playbooks window. This is the confirmed resolution for this issue and our team can typically get it sorted for you quickly. To help our team diagnose and fix the problem as fast as possible, please have the following information ready when you reach out: - The exact project URL or domain that is missing (for example, www.example.com). - Confirmation that the project is visible in Site Explorer. - A note about any additional symptoms you are experiencing, such as backlink reports showing no data or growth-plan features appearing locked. - A screen recording or screenshot showing the project is absent from the Atlas Agent playbooks window. To get in touch, open the chat widget in the bottom-right corner of the platform and type human teammate — we're happy to help.

Atlas Agent 'Page Does Not Exist' Error Fix

What This Article Covers After working in Atlas Agent, some users find that returning to a previous session — or browsing all sessions — triggers a 'page does not exist' error, even after refreshing the browser or clearing the cache. This article explains why this happens and what steps to take. What Causes This Error This error is associated with a known platform-side bug that affects how Atlas Agent loads existing chat sessions and the Browse All sessions view. When this occurs, previously created sessions cannot be retrieved correctly, resulting in a broken page instead of your saved work. Because this is a backend issue, standard browser-level fixes alone may not fully resolve it — the Search Atlas support team will need to investigate and restore access to the affected session on your behalf. Steps to Take If You See This Error 1. Note the session name or the report you were working on. This detail is the most important piece of information you can provide, as it allows the support team to locate the affected session quickly and restore your access. 2. Do not attempt to recreate the session from scratch before contacting support, as the original session data may still be recoverable on the backend. 3. Contact the Search Atlas support team and share the session name and any relevant details (e.g., when the error first appeared, what you were doing at the time). The support team will investigate the backend state of your session and restore access where possible. What to Expect Because this is a known bug requiring backend investigation, the support team will review your specific session and work to restore access. Resolution timelines depend on the complexity of the session state, but the team will keep you updated throughout the process. Tips to Avoid Issues in the Future - Keep your browser updated to the latest stable version for the best compatibility with the platform. - If Atlas Agent behaves unexpectedly after a long working session, save or export your work before closing the tab. Still Seeing the Error? If you are still encountering the 'page does not exist' error, please reach out to our support team with your session name and details so we can investigate and restore your access. You can contact us through the Search Atlas Help Center or by starting a new conversation with the support team.

🛠️ Atlas Brain Niche Field Not Saving via API

🔍 Overview Some users have reported that after updating the niche field inside default_ai_settings through the API, the new value does not persist. Instead, the field returns null when queried. This is a known platform bug that has been identified, escalated, and resolved by the Search Atlas engineering team. ⚙️ What Causes This Issue This problem was caused by a bug in Atlas Brain that prevented the niche field from being written and retained correctly when updated via the API. The field would appear to accept the new value, but it would not save, and subsequent reads would return null. This affected Brand Vault niche field updates made through the API integration. ✅ Current Status The engineering team has confirmed that this bug has been fully resolved. The fix was prioritized, developed, reviewed, and released. If you experienced this issue before the fix was deployed, your niche field may still show null and will need to be set again. 🚀 Steps to Resolve 1. Retry your API update. Now that the underlying bug is fixed, attempt to update the niche field via the API again using the same request you used previously. 2. Verify the value persisted. After submitting the update, retrieve the record via a follow-up API read request to confirm the niche field now returns your intended value rather than null. 3. Re-enter the value manually if needed. If the field still shows null after retrying the API update, try setting the niche field directly within the platform as a temporary measure while you confirm the API call is formatted correctly. 4. Check your API request format. Ensure the niche value is being passed correctly within the default_ai_settings object in your request payload. A malformed or missing field key can cause the value to be silently dropped. 💡 Tips to Prevent This Going Forward - After any API update to settings fields, always perform a follow-up read request to confirm the value was saved as expected. - If a field returns null unexpectedly after an update, treat this as a signal to retry the request or contact support — it may indicate a transient issue rather than an error in your code. - Keep your API integration up to date, as platform fixes may occasionally require that previously failed operations be retried. 📞 Still Seeing the Issue? If the niche field continues to return null after following the steps above, this may indicate a different underlying problem specific to your account or project. If you need further assistance, reach out to our support team and a member of our team will be happy to help.

🔍 OTTO Project Missing from Atlas Brain Index

Overview If your OTTO project appears to exist in the backend but is missing from the Atlas Brain search bar or project list, and attempting to re-add it returns a Request failed: 400 error, this is a known indexing issue. Because the project already exists in the system, the platform blocks duplicate additions — but the project also fails to surface correctly in Atlas Brain. This requires a manual fix from the Search Atlas team. What Causes This Issue This issue occurs when an OTTO project becomes out of sync between the backend and the Atlas Brain search index. The project record exists in the database, so re-adding it triggers a 400 error (duplicate entry), but it is not registered in the index Atlas Brain uses to display and search projects. This prevents Atlas Brain from connecting to the project or delegating tasks to it correctly. How to Resolve It Because this issue involves a backend index mismatch, it cannot be fixed through the platform interface alone. To get the issue resolved as quickly as possible, follow these steps: 1. Confirm the project exists: Verify that your OTTO project (for example, brittanyelise.com) is visible in your OTTO section and is listed as active. Make a note of the exact domain or project name. 2. Do not attempt to re-add the project: Trying to add the same project again will return a Request failed: 400 error because the backend already has a record of it. Additional re-add attempts will not resolve the issue and may complicate the fix. 3. Gather the following information before contacting support — having these details ready will allow the team to locate and re-register your project in the Atlas Brain index as quickly as possible: - The exact domain or project name (for example, brittanyelise.com) - A screenshot or description of the 400 error you received when attempting to re-add the project - Your account email or workspace identifier 4. Submit a support request by opening the chat widget in your Search Atlas dashboard (click the chat icon in the bottom-right corner) or emailing the support team directly. Paste the information you gathered in the previous step into your message so the team can prioritize and action your request without needing a follow-up. 5. What happens next: Once the support team receives your details, they will manually re-register the project in the Atlas Brain index. This resolves the mismatch and makes the project appear correctly in Atlas Brain search and the project list. Most cases are resolved within one business day. If you do not hear back within 24 hours, reply to your original support thread to follow up. If you have any questions or need further assistance, please contact our support team and we'll be happy to help.

🛠️ How Atlas Brain Routes AI Requests — and What Causes Errors in Atlas Agent

🛠️ How Atlas Brain Routes AI Requests — and What Causes Errors in Atlas Agent Every task you send to Atlas Agent passes through Atlas Brain — the AI routing engine that selects, calls, and returns results from external AI model providers. When Atlas Brain encounters a problem at the routing layer, Atlas Agent displays an error message. While many of these errors are transient and resolve within minutes, some may persist for 24–48 hours during platform incidents — if an error continues for more than 30–60 minutes, contact support rather than waiting. Understanding how this routing works helps you interpret errors faster, choose the right next step, and know when to wait versus when to contact support. 🧠 What Is Atlas Brain? Atlas Brain is the core AI engine that powers Atlas Agent. It acts as an intelligent dispatcher sitting between your request and the external AI models that fulfill it. Every Atlas Agent response you receive has been routed, processed, and returned by Atlas Brain. Without a functioning Atlas Brain connection, Atlas Agent cannot complete any task. Atlas Brain is not a single AI model — it is a routing and orchestration layer that manages connections to multiple external AI model providers simultaneously, selecting the best available model for each request type. 🔀 How Request Routing Works Step by Step ➡️ Step 1 — Task received: You submit a task to Atlas Agent. Atlas Agent captures your input and forwards it to Atlas Brain. ➡️ Step 2 — Model selection: Atlas Brain evaluates the task type and selects the most appropriate external AI model provider for that specific request. ➡️ Step 3 — Provider API call: Atlas Brain sends the request to the selected provider's API endpoint and waits for a response. This is the step where failures occur. ➡️ Step 4 — Response delivered: The provider's output is processed by Atlas Brain and returned to Atlas Agent as your completed result. Under normal conditions this entire flow completes in seconds. An error surfaces when Step 3 fails — Atlas Brain cannot reach the provider, the provider returns an error, or the target model no longer exists at the expected endpoint. ⚠️ The Three Root Causes of Atlas Brain Routing Failures 🔧 Provider-side maintenance: External AI providers occasionally take their APIs offline for planned or emergency maintenance windows. Atlas Brain detects the unavailability immediately and returns an error rather than leaving your request in a permanent pending state. These outages are typically brief — most resolve within two to five minutes — and Atlas Brain resumes automatically once the provider is back online. 🚦 Rate limits: AI providers enforce usage ceilings on their APIs. If Atlas Brain reaches a provider's rate limit during a period of high demand, requests temporarily fail until the rate window resets. Like maintenance outages, this is a transient condition that self-resolves without any action on your part. ❌ Provider infrastructure failures: Unexpected faults — regional outages, degraded APIs, or transient network issues on the provider's infrastructure — can interrupt the connection between Atlas Brain and the provider. These are outside Search Atlas's direct control and resolve when the provider restores service. They typically appear as intermittent failures rather than a complete outage. 🔴 Model removal or renaming (the most impactful cause): When an AI provider retires, renames, or restructures a model, Atlas Brain's routing configuration still points to the old endpoint — which no longer exists. This causes every request to fail immediately and consistently, not just occasional requests, because the model is permanently gone. This failure type does not self-resolve. It requires the Search Atlas engineering team to update the routing configuration and deploy a replacement model. 🔁 What the Failure Pattern Tells You ⏱️ Intermittent pattern — the error appears on some requests but not all, and clears within two to ten minutes. This almost always indicates a transient provider issue: maintenance, a rate limit reset, or a brief infrastructure fault. Waiting and retrying is the correct response. Self-service troubleshooting steps resolve these cases. 🔴 Persistent pattern — the error fires on every single request from the start and does not recover after ten or more minutes. This strongly indicates a routing misconfiguration, most commonly a retired or renamed model on the provider side. No browser-side troubleshooting step will resolve this. The fix must be applied on the routing layer by the engineering team. Identifying which pattern you are experiencing is the single most useful piece of information you can provide when contacting the Search Atlas support team. 👷 How the Search Atlas Engineering Team Monitors and Responds 🔍 For transient provider failures: Atlas Brain's monitoring detects elevated error rates automatically. The engineering team watches provider status pages and internal signals. No code change is needed — Atlas Brain resumes routing automatically once the provider recovers. 🔧 For routing misconfigurations: When a model is retired or renamed, engineers update the routing configuration to replace the broken endpoint with an active equivalent. This fix is packaged and deployed as part of a regular engineering release. Until the fix is live, all requests routed to the affected model will continue to fail. 📢 Active incidents affecting Atlas Brain are published on the Search Atlas status page at status.searchatlas.com. Checking this page is the fastest way to confirm whether a known issue is already under active investigation before contacting support. 💡 Key Takeaways for Atlas Agent Users ✅ Intermittent errors are almost always provider-side and self-resolve — wait two to three minutes and retry before taking any other action. ✅ Persistent errors that fire on every request require an engineering fix — clearing your cache or switching browsers will not help. Contact the Search Atlas support team directly so they can identify the affected model and escalate to engineering. ✅ Your account, your data, and your Search Atlas settings are never affected by Atlas Brain routing failures. These errors are fully isolated to the request execution layer and carry no risk of data loss or account impact.

🤖 Atlas Agent: "I'm Temporarily Unable to Process Your Request" — Troubleshooting Guide

When Atlas Agent displays "I'm temporarily unable to process your request," a backend service interruption stopped Atlas Brain from completing your task — nothing you did caused it. Follow the steps below to get back on track within minutes. 🔍 What This Error Means Atlas Brain — the AI engine that powers Atlas Agent — routes your requests to external AI model providers. When a provider is temporarily unavailable due to maintenance, rate limits, or a routing failure, Atlas Brain cannot complete your task and shows this message: "I'm temporarily unable to process your request — this is a hiccup on my end, not anything you did. Please try again in a few minutes. If it's still not working, our support team can help." This error originates entirely on Atlas Brain's side. Your inputs, your account, and your data are not affected. Before troubleshooting, identify which variant you are seeing: - Intermittent — the error recovers within minutes. The self-service steps below will resolve it. - Persistent — the error fires on every request and does not recover after 5–10 minutes. This usually indicates a backend routing misconfiguration. Skip ahead to the support contact section — clearing your cache, switching browsers, or waiting will not help. 🔧 How to Fix the Error Follow these steps in order if the error appears intermittently. Most users are unblocked after step 2. If the error fires on every single request, these steps will not help — go directly to the support contact section below. 1. Wait 2–3 minutes. Most provider outages are brief. Atlas Brain resumes automatically once the provider recovers. 2. Refresh the page and re-submit your request to Atlas Agent. You should see a normal response. 3. Clear your browser cache if the error continues: open your browser settings, clear cached files and cookies for the Search Atlas domain, log back in, then retry. 4. Open an incognito window or switch to a different browser to rule out a local extension or session conflict. After completing these steps, Atlas Agent should respond normally. If the error persists beyond 10 minutes, or if it has been occurring on every request from the start, see the section below. ⏱️ If the Atlas Agent Error Persists Beyond 10 Minutes A prolonged error — especially one that fires on every single request without ever recovering — may indicate a wider service disruption or a backend routing issue that requires an engineering fix. Take these additional steps: - Check the Search Atlas status page at status.searchatlas.com for any active incidents affecting Atlas Agent or Atlas Brain. - Verify your internet connection — an unstable connection can cause requests to fail before they reach Atlas Brain. - Log out and log back in to Search Atlas to refresh your session token, then retry Atlas Agent. If the error remains after completing these steps — or if it was firing on every request from the beginning — contact the Search Atlas support team using the section below. Routing misconfigurations cannot be resolved from the user side and require the engineering team to swap or restore the affected model. 📞 How to Contact Search Atlas Support About the Atlas Agent Error If Atlas Agent still shows the error after you have followed all the steps above — or if the error has been firing on every request from the start, indicating a backend routing issue — the Search Atlas support team can investigate your specific account and session and escalate to engineering if needed. Include the following details when you reach out to speed up the investigation: - Your Search Atlas account email address - The date and approximate time (include your time zone) when the error first appeared - Whether the error occurs on every message you send or only intermittently — this helps the team distinguish a transient provider hiccup from a backend routing issue - A screenshot or copy of the exact error message - The task or prompt you submitted to Atlas Agent when the error occurred - Your browser name and version (for example, Chrome 124 on Windows 11) Reach support via the chat widget inside Search Atlas typing "Human Teammate". The team will confirm receipt and begin investigating right away. 🛠️ Technical Background: What Causes This Error in Atlas Brain Atlas Brain routes your requests to external AI model providers. When a specific model is temporarily unavailable — due to provider-side maintenance, rate limits, or a routing failure on the provider's infrastructure — Atlas Brain cannot fulfil the request and returns the temporary error message to Atlas Agent. In some cases, a specific model may be removed or renamed by the provider, which causes the error to fire on every request until the engineering team swaps in a replacement model on the routing layer. The Search Atlas engineering team actively monitors these failures and deploys fixes as part of regular releases. If you encountered this error, it is very likely already under investigation. 🎯 You now know what triggers the Atlas Agent temporary error and the exact steps to resolve it. If the issue continues after following all the steps above, reach out to Search Atlas support chat, typing "Human Teammate", with your session details and the team will get you unblocked. For a full overview of what Atlas Agent can do, see the Atlas Agent Overview.

🤖 Search Atlas Coworker — Frequently Asked Questions

🤖 Search Atlas Coworker — Frequently Asked Questions 🔌 Which apps can I connect to Coworker? Coworker currently supports 16 connectors across several categories: - Advertising: Meta Ads, Google Ads, TikTok Ads (coming back soon — the Connect button is temporarily unavailable), and OpenAI Ads (advertise in ChatGPT) - SEO: Google Search Console - Analytics: Google Analytics (GA4) - Communication: Slack - Developer Tools: GitLab, GitLab (Self-Managed), GitHub, Vercel - Web / CMS: Webflow, WordPress (self-hosted), WordPress.com - CRM: HubSpot - Custom: Custom MCP Server — point Coworker at your own MCP server to extend its reach Your Search Atlas tools — including Google Business Profile, OTTO, rank tracking, Website Studio, Digital PR, local SEO heatmaps, and AI/LLM visibility — connect automatically through your Search Atlas account. No separate connector step is needed for these. 🔍 Can Coworker connect to Notion, Jira, Asana, ClickUp, Figma, Gmail, or Stripe? None of these are native connectors today. If you run your own MCP server for any of these tools, you can point Coworker at it using the Custom MCP Server connector — that is the supported path for any tool not in the native catalog above. ⚠️ I see a Connect button for Amazon Ads, Microsoft Ads, or TikTok (non-ads). Can I use those? These connectors are not yet available. If you see a Connect button for them, that is a known display issue in the UI — the underlying integration has not been built yet. We'll update the app when these become available. ✅ Does Coworker ask for my approval before taking an action? Approval behavior is fully configurable by your admin. In the /coworker hub, approvals can be turned on or off per connector and per individual tool action — so some actions can run automatically while others require your sign-off first. You or your admin can always require approval for any specific connection or action. 💬 Where do I see approval confirmation cards? Approval cards render inside Slack and Microsoft Teams. If you are chatting with Coworker from a ClickUp channel, the visual approval card does not currently display there — this is a known limitation for ClickUp channel users only. 💬 Which chat channels can I use to talk to Coworker? Slack and Microsoft Teams are both fully supported. ClickUp is also a supported chat channel for conversations with Coworker, though approval cards are not yet rendered there (see above). 🔄 I connected an app but the hub still shows it as "Not Connected." What's wrong? This is a display refresh issue — your connection is almost certainly fine. Try refreshing the page or closing and re-opening the /coworker hub. The connection itself is intact even when the status badge is slow to update. 🚨 A connector shows "Needs Attention" but gives no details. What should I do? This is a known display limitation — Coworker doesn't yet surface a detailed reason in all cases. Start by trying to reconnect the app. If the message persists after reconnecting, contact support so we can investigate directly. ✏️ I asked Coworker to publish, send, or edit something, but nothing happened. Is that normal? Write and publish actions (editing a live page, sending a message, publishing content) do not complete successfully in 100% of cases yet — read operations like summaries and reports are solid. If an action didn't seem to take effect, verify directly in the target app and reach support if the change truly didn't go through. 📊 Can I trust the numbers Coworker reports, like keyword counts or ad spend? Coworker is a fast, convenient summary layer — it is generally accurate, but can occasionally over- or under-report on some integrations. For high-stakes financial or reporting decisions, always double-check the figures against the source report in the connected app. 💳 Does using Coworker cost extra credits per action? No. Coworker does not charge additional credits for the actions it takes. Usage is absorbed by your Search Atlas plan — there is no per-action billing. 🔒 Can Coworker see my teammates' private messages or channels? No. Coworker can only see your own connected accounts and the Slack or Teams channels it has been explicitly added to. It cannot access teammates' private DMs, channels it hasn't been invited to, or any message history that predates its access. 🔗 When I connect Webflow or WordPress.com, the page redirects to a pipedream.com URL. Is that safe? Yes — this is completely expected and intentional. The pipedream.com URL is part of the deliberate design of the connect flow for those integrations, not a bug or an unfinished page. It is safe to proceed through that page to complete your connection. 📣 Coworker isn't responding in my Slack Connect channel. Why not? Coworker cannot post or take actions in Slack Connect channels — channels shared between two separate companies or organizations. This is a Slack platform restriction, not a Search Atlas limitation. Use a regular channel within your own workspace, or send Coworker a direct message instead. ⏱️ Coworker went quiet mid-conversation and now it won't respond. What happened? If a conversation is inactive for around 5 minutes, the session can end silently without any disconnect notice. Simply @mention or message Coworker again to start a fresh session and pick up where you left off. 📎 Can I attach files like PDFs or spreadsheets for Coworker to read? Coworker can read and understand images (such as screenshots), but cannot yet process other file types like PDFs, Word documents, or spreadsheets. For now, paste the relevant text content directly into the chat instead of attaching those file types. 🗓️ My scheduled Routine didn't run at the time I set. Is something broken? Timezone-aware scheduling for Routines is still being rolled out, so a Routine may not always fire at the exact local time you configured. If precise timing matters for your use case, check when the Routine actually ran and adjust the scheduled time accordingly. 🎯 Coworker seems to stall when I give it a lot of tasks at once. How should I structure my requests? For the best results, give Coworker one goal per message. Asking it to do several unrelated things in a single message can cause it to stall rather than work through them one by one. 💱 Coworker is showing my ad spend in dollars, but my account bills in a different currency. Is that right? This is a known display limitation — Coworker can currently show amounts with a $ symbol even when your connected ad account bills in a different currency, such as COP. Always confirm the actual currency directly in the source platform before making any financial decisions. 🔀 Coworker's response came out garbled or weirdly formatted. What should I do? Very long responses can occasionally come out with formatting issues or garbled text. Just ask Coworker to redo the answer or make it shorter — that is usually enough to get a clean response. Still have a question? Start a chat with us — and type "human teammate" at any time to be connected with a real person on our support team.

🤖 What Can Search Atlas Coworker Do?

Search Atlas Coworker is your AI assistant inside Slack and Microsoft Teams. Instead of switching to the Search Atlas dashboard, you can ask Search Atlas Coworker questions and give it instructions directly from chat — and it uses your real Search Atlas data to respond. SEO & Digital Marketing Search Atlas Coworker has full access to your Search Atlas account and can help you with: - Keyword research — find keywords, check search volume, analyze keyword gaps - GSC performance — check rankings, impressions, clicks, and page performance - Site audits — run audits and get a summary of critical issues - OTTO suggestions — review and apply on-page SEO recommendations - Content grading — evaluate content against top-ranking pages - Local SEO & GBP — check local rankings, heatmaps, and Google Business Profile status - Backlinks & authority — check your link profile and find new opportunities - AI Visibility (formerly LLM Visibility) — see how AI search engines reference your brand - Google Ads & PPC — review campaign performance and get recommendations Connected Apps Connect your CRMs, analytics platforms, and other tools to Search Atlas Coworker via OAuth. Once connected, Search Atlas Coworker can query data and take actions in those apps without leaving Slack. See Connecting Third-Party Apps to Search Atlas Coworker for setup instructions. Automated Reports (Routines) Ask Search Atlas Coworker to set up recurring tasks — for example, posting a weekly GSC summary to your #seo-team channel every Monday morning. No dashboard visit required. See Setting Up Automated Reports with Search Atlas Coworker for details. Web Search & Image Analysis - Web search — Search Atlas Coworker can look up current information outside your Search Atlas data when needed - Image analysis — drop a screenshot into Slack and Search Atlas Coworker can interpret it and answer questions about it What Search Atlas Coworker Cannot Do - Modify your Search Atlas account settings or billing - Access Slack message history, member directories, or private channels it was not invited to - Take actions in connected apps without your approval (unless a workspace admin has pre-authorized specific actions)

⏰ Setting Up Automated Reports with Search Atlas Coworker (Routines)

Routines let you schedule recurring reports and tasks that Search Atlas Coworker runs automatically and posts to a Slack channel or DM on your chosen schedule — no manual check-ins required. What You Can Automate - Weekly GSC performance summaries posted to your team channel - Daily ranking changes for your top keywords - Monthly site audit reports - Scheduled alerts when specific metrics change significantly - Any recurring request you would otherwise send Search Atlas Coworker manually How to Create a Routine Just describe what you want in plain language. Examples: - "Every Monday at 9am, post a summary of last week's GSC performance to #seo-team." - "Every day at 8am, send me the top 10 ranking changes for my tracked keywords." - "On the first of each month, run a site audit and post the critical issues to #website." Search Atlas Coworker will confirm the details of the routine and show you an approval card summarizing what it will do, when, and where it will post the results. Reviewing and Approving the Routine The approval card shows: - The task Search Atlas Coworker will perform - The schedule (frequency, time, and timezone) - The Slack channel or DM where results will be posted Click Approve to activate the routine. The first run will happen at the next scheduled time. Managing Existing Routines You can manage your routines at any time by asking Search Atlas Coworker: - "Show me my active routines." — lists all running automations - "Pause my weekly GSC report." — suspends a routine without deleting it - "Delete my daily ranking report." — permanently removes the routine - "Change my Monday GSC report to Fridays at 5pm." — updates the schedule Timezone Search Atlas Coworker uses the timezone of your Slack workspace by default. You can specify a different timezone when creating a routine: "Every Monday at 9am New York time."

⚖️ Search Atlas Coworker vs. the Search Atlas Dashboard — When to Use Which

Search Atlas Coworker and the Search Atlas dashboard use the same data, but they are optimized for different workflows. Here is a quick guide to help you choose the right tool for the job. Use Search Atlas Coworker When You Want To… - Get a quick answer without navigating the dashboard ("What are my top keywords right now?") - Share a report with your team in Slack without exporting anything - Set up recurring automated reports that run without your involvement - Ask a follow-up question mid-conversation ("And how did that compare to last month?") - Work across multiple tools in one place (Search Atlas + your CRM + Slack, all in one thread) - Get a plain-language summary of a complex report Use the Search Atlas Dashboard When You Want To… - Do deep analysis across large datasets (bulk keyword exports, multi-site audits) - Edit or configure settings (campaign setup, account preferences, billing) - Use visual tools like heatmaps, charts, and side-by-side comparisons - Perform bulk actions (approve multiple OTTO recommendations at once, bulk keyword adds) - Access features not yet available in Search Atlas Coworker (Website Studio, full Report Builder, etc.) Summary - Search Atlas Coworker — conversational, fast, great for quick lookups, sharing, and automation - Dashboard — structured, visual, best for deep analysis and bulk configuration Most power users combine both: use Search Atlas Coworker for daily check-ins and team updates, and the dashboard for weekly deep dives and campaign management.

🕷️ Whitelisting the Search Atlas Crawler & Accessing kgraph for Agentic Certification

Whitelist the Search Atlas crawler in your firewall or security plugin so site audits run without interruption. If you are completing the Agentic Mastery certification, this article also includes the updated kgraph URL. 🔒 Search Atlas Crawler IP Addresses Search Atlas uses the following IP addresses to crawl and monitor websites. Whitelist all 20 addresses to ensure site audits complete successfully. - 168.151.102.206 - 161.123.88.40 - 161.123.75.228 - 161.123.90.214 - 161.123.81.184 - 168.151.116.203 - 168.151.138.43 - 161.123.105.249 - 161.123.77.229 - 161.123.107.109 - 161.123.77.171 - 161.123.90.252 - 209.95.170.40 - 168.151.116.237 - 161.123.78.218 - 161.123.104.45 - 161.123.85.66 - 161.123.82.188 - 209.95.171.24 - 161.123.83.48 ☁️ How to Whitelist the Search Atlas Crawler in Cloudflare Cloudflare is the most widely used CDN (Content Delivery Network). If your site runs behind Cloudflare, its firewall may block the Search Atlas crawler. Follow these steps to add the Search Atlas IP addresses to your Cloudflare allowlist. 1. Log in to your Cloudflare account. 2. Click the Firewall icon, then select the Tools tab. 3. Under IP Access Rules, enter each Search Atlas IP address from the list above. 4. Set the action to Whitelist. 5. Select the domain you want the Search Atlas crawler to access. 6. Click Add. Once all IP addresses are added, the Search Atlas crawler can access your site for monitoring and audits. For more detail on Cloudflare's IP Access Rules, see Cloudflare's support documentation. If you are still unable to run a site audit after whitelisting, contact our support team via the in-dashboard chat (Monday–Friday, 9 am–6 pm PST), or book a software demo with our team. 🔌 How to Whitelist the Search Atlas Crawler in WordPress Security Plugins If your site uses a WordPress security plugin rather than Cloudflare, follow the steps for your plugin below. WordFence 1. In the WordPress menu, go to WordFence → Firewall → All Firewall Options. 2. Paste the Search Atlas IP addresses into the Allowlisted IP addresses that bypass all rules field. 3. Click Save Changes. Stop Bad Bots 1. In the WordPress menu, go to Block Bad Bots → Settings. 2. Select the Whitelist tab. 3. Paste the Search Atlas IP addresses into the IP Whitelist field. 4. Click Save Changes. Blackhole for Bad Bots In the Blackhole for Bad Bots plugin settings, add each Search Atlas IP address to the plugin's whitelist field and save. The crawler will be allowed through on your next audit. 🧠 Accessing kgraph for Agentic Mastery Certification If you are completing the Agentic Mastery certification and the kgraph link on Day 2 does not load, the legacy URL kgraph.searchatlas.com has been deprecated. Use the updated URL instead: https://kgraph.labs.searchatlas.com/ If you still cannot access the kgraph subdomain after switching to the new URL, contact Search Atlas support via the in-dashboard chat and our technical team will assist you. 🎯 You can now unblock the Search Atlas crawler for site audits and reach the kgraph training environment. For additional troubleshooting, refer to the Whitelisting Search Atlas Bot article if the steps above do not resolve your issue.