Troubleshooting

🔄 Fix Account Sync Issues and Golden Loops

Overview Some Search Atlas users experience account-wide sync issues where changes made by one admin are not visible to others, or where Golden Loops fail to save correctly. This article explains what to do if you encounter these problems. Step 1 — Confirm Your Workspace Access Before troubleshooting sync, verify that all team members are in the same workspace and have the correct roles assigned. Check your workspace settings to confirm that any admins who should share access are listed with the appropriate permissions. If a team member is missing, invite them and ask them to accept the invitation before testing sync again. Step 2 — Refresh and Re-authenticate Sync issues are sometimes caused by a stale browser session. Try the following before escalating: 1. Save any unsaved work. 2. Log out of your Search Atlas account completely. 3. Clear your browser cache and cookies, or try an incognito/private window. 4. Log back in and navigate to the affected area. 5. Ask the other admin to do the same on their device, then check whether changes are now visible to each other. Step 3 — Check Golden Loop Settings If a specific Golden Loop is not saving or is behaving unexpectedly, navigate to the Golden Loops section of your account. Open the Golden Loop that is not saving correctly, re-select any required settings such as the associated Project, and save again. If the issue persists after saving a second time, note the exact details of what is not persisting so you can share them when escalating. When to Escalate If the steps above do not resolve your sync issue or your Golden Loop continues to fail to save, please have the following information ready before contacting support: - Your workspace or project name - The exact behavior you are seeing (e.g., which settings are not saving, which admin accounts are affected) - Any error messages displayed on screen - The approximate time the issue first occurred 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.

🤖 Real-Time Agent Availability: What FIN Can Check

🧠 What FIN Can and Cannot Do FIN is Search Atlas's AI support assistant. It can answer product questions, guide you through features, and connect you with a human teammate — but it cannot check whether a human support agent is online at this exact moment. FIN does not have access to real-time agent schedules, shift data, or live queue status. This means if you ask "Are human agents available right now?", FIN cannot give you an accurate yes or no answer. ✅ How to Check Live Agent Availability Yourself The most reliable way to find out whether a human teammate is currently available is to open the chat widget and reach out directly. The widget reflects current support status in real time. 1. Open the chat widget inside the Search Atlas platform. 2. Initiate a conversation to see whether a human teammate is available. 3. If you want to be connected with a human teammate, type human teammate in the chat input and send the message. If a human teammate is available, you will be connected. If none are currently online, the chat will let you know and you can leave a message for follow-up. ⏰ What Happens When No Agents Are Available If no human teammates are currently online, you have two options: - Leave a message in the chat. A teammate will follow up with you as soon as one is available. - Continue with FIN for immediate help with product questions, navigation guidance, or troubleshooting steps. FIN is available 24/7 and can resolve a wide range of questions without a human agent. ❓ Why FIN Cannot Answer This Question Automatically FIN operates from a knowledge base of product documentation and support articles. It does not have a live connection to agent scheduling systems or real-time support queue data. This is why FIN will always direct you to open the chat widget and reach out directly, rather than confirming availability on your behalf. FIN is being transparent about the limits of what it can verify. 💬 Need a Human Teammate Right Now? 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 Broken Links Using Atlas Agent

🧭 What This Article Covers Atlas Agent can help you identify and fix broken links on your website through the Site Auditor tool. However, the steps to access Site Auditor may look different depending on your plan tier, user role, and current UI configuration. This article walks you through every scenario so you can get started without hitting a dead end. ✅ Before You Begin: Requirements Checklist Make sure the following conditions are met before following the steps below: - Plan tier: Site Auditor is available on Pro plans and above. If you are on a Starter plan, you will not see this tool in your sidebar. - User role: You must have Admin permissions to run a site audit and trigger Atlas Agent automations. Viewer accounts cannot initiate crawls or fixes. - Project set up: You must have at least one active project with a connected domain before Site Auditor can crawl your site. If you are unsure about your plan or role, navigate to Avatar (top-right) → Billing → Plans & Top-ups (Change Plan) to check your plan, or ask your workspace Admin to confirm your permissions. 🗺️ How to Navigate to Site Auditor Depending on your UI version, Site Auditor may appear in one of two locations: - Standard sidebar layout: In the left-hand sidebar, look for the Site Auditor option under the SEO Tools section. - Condensed or icon-only sidebar: The sidebar may be collapsed. Click the expand arrow on the left edge of the screen to reveal full menu labels, then look for Site Auditor under SEO Tools. - Top-navigation layout (some Enterprise accounts): Navigate to OTTO SEO → Site Audit → Overview (Website Overview). If you do not see Site Auditor in any of these locations, your plan may not include it. See the section below on plan access for next steps. 🚀 Running a Crawl and Using Atlas Agent to Fix Broken Links 1. Open OTTO SEO → Site Audit → Overview (Website Overview) and select the project you want to audit from the project dropdown at the top of the page. 2. Click Recrawl Site. The crawl may take a few minutes depending on your site size. 3. Once the crawl is complete, go to the Issues tab and filter by Broken Links or look for the 4xx Errors category in the issues list. 4. Select one or more broken link issues by checking the boxes next to them. 5. Click the Fix with Atlas Agent button that appears in the action bar above the issue list. 6. Atlas Agent will open a task panel on the right side of the screen. Review the suggested fixes — these may include redirect recommendations, link replacements, or removal suggestions. 7. Approve individual fixes or click Apply All to let Atlas Agent implement the recommended changes automatically. 8. After fixes are applied, re-run a crawl to confirm the broken links have been resolved. 👥 Guidance for Different User Roles Admin users have full access to Site Auditor, all crawl settings, and Atlas Agent automation. No additional steps are needed. Editor users can run crawls and use Atlas Agent to apply fixes, but cannot change the connected domain or billing settings. If a fix requires domain-level changes, flag it to your Admin. Viewer users can see audit results but cannot run new crawls or use Atlas Agent. If you need to take action on broken links, contact your workspace Admin to upgrade your role. 📋 Plan Tier Availability - Starter: Site Auditor is not included. Upgrade to Pro or higher to access this feature. - Pro: Full Site Auditor access with Atlas Agent automation for broken link fixes. - Agency and Enterprise: All Pro features plus multi-project crawls, advanced filtering, and priority processing for large sites. To upgrade your plan, go to Avatar (top-right) → Billing → Plans & Top-ups (Change Plan) and select a plan that includes Site Auditor. 🔧 Common Access Issues and Fixes - Site Auditor is missing from the sidebar: Your plan does not include this feature, or your role is set to Viewer. Check your plan and permissions in Account Settings. - The Fix with Atlas Agent button does not appear: Make sure you have selected at least one issue using the checkboxes. The button only appears when one or more issues are selected. - Crawl is stuck or shows an error: Verify your domain is correctly connected under Project Settings. If the domain requires authentication, make sure crawl credentials are saved. - Atlas Agent suggestions are greyed out: This can happen if your session has timed out. Refresh the page and re-select your issues. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix Stuck Microagent Tasks and Common Bugs

Overview Some customers have reported a combination of issues affecting Microagent tasks, Instant Indexing setup, and Content Genius features. This article explains each known issue and sets accurate expectations for what to have ready when escalating to the support team. Stuck Microagent Tasks in PENDING Status Microagent tasks can become stuck in a PENDING state and never complete. If you see tasks marked PENDING that are not progressing, note the following details before escalating: - The name of the affected project or Content Genius document - The approximate time the task was created and how long it has been stuck - Any error messages or status indicators you see on screen Our team will need these details to investigate and manually reprocess affected tasks on the backend. Blank Service Account Email for Instant Indexing When activating Instant Indexing, some users encounter a blank service account email field. This leaves the Google Search Console (GSC) verification step incomplete and can cause the indexing status to appear contradictory. If your service account email field is still blank, this requires manual provisioning by our team. Before escalating, please have the following ready: - Your project or site name in OTTO SEO - A screenshot showing the blank service account email field - Confirmation of which GSC property you are trying to connect Known Content Genius Bugs Some reproducible bugs affecting Content Genius features have been identified. If you are experiencing issues with Content Genius — such as problems with keyword management, SEO scoring, or content generation — please escalate with the following information: - The name of the affected project and document - A description of the exact behavior you are seeing - The exact error message, if any, along with the date and time it occurred 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.

🤖 AI Agent Deep-Link Navigation Fix

A bug affecting the AI Agent's deep-link behavior has been resolved, ensuring the agent opens with the correct parameters when accessed via a direct link and clears its state properly upon closing. ✨ What's New The AI Agent now correctly reads and applies deep-link parameters when launched from a direct URL. Previously, navigating to the agent via a deep link could result in the agent failing to open in the expected state. Additionally, closing the agent now reliably clears all associated parameters, preventing stale state from persisting across sessions. 🛠️ How to Use It 1. Navigate to the AI Agent using a deep link that includes URL parameters. 2. Confirm the agent opens and reflects the correct context based on those parameters. 3. Close the agent and reopen it to verify that no residual state from the previous session carries over. 📋 What to Expect This fix is applied automatically — no configuration changes are required. The improvement affects all users who access the AI Agent via deep-link URLs. The agent will now consistently initialize with the correct parameters and reset fully on close, regardless of how it was previously accessed. 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 AI Agent Pulling the Wrong Business URL

🔍 Overview If your AI Agent is referencing the wrong website URL or business details — for example, pulling a URL from a different domain than your active project — the issue is almost always in GBP Galactic, not in your project settings or OTTO connection. The AI Agent sources business information (including your website URL) directly from GBP Galactic, not from the Google Business Profile linked inside your OTTO project. This means that even if your project is correctly connected to the right GBP profile, the AI Agent will still use whichever GBP profile is activated inside GBP Galactic. ⚠️ Why This Happens You may have two or more GBP profiles connected across different domains in Search Atlas. A common scenario looks like this: - Project A is set to ericrounds.com with its own GBP profile. - Project B is set to a different domain (for example, a service business) with a separate GBP profile. - Both GBP profiles exist inside GBP Galactic, but the wrong profile is currently activated there. Because the AI Agent reads from GBP Galactic, it will use the active profile — even if that profile belongs to a different domain than your current project. Verifying or changing your project-to-GBP linkage in OTTO will not fix this. ✅ How to Correct the GBP Profile the AI Agent Uses To resolve this issue, you need to ensure the correct GBP profile is set as active inside GBP Galactic. Navigate to Local → GBP Galactic (GBP Projects) from the left sidebar in your Search Atlas account, review the GBP profiles connected there, and make sure the profile that corresponds to your active project's domain is the one currently active. If you are unsure which profile is active or how to switch it, please reach out to the Search Atlas support team and they can update the active GBP profile on your account to match your intended domain. 🧩 Understanding the Two Separate Connections It helps to think of these as two independent systems: - OTTO project → GBP connection: This controls which GBP profile is used for SEO tasks, optimizations, and project-level reporting inside OTTO. Changes here do not affect what the AI Agent sees. - GBP Galactic → Active profile: This is the data source the AI Agent reads from when generating responses, referencing your business URL, or personalizing content. This must be set correctly and independently. Both connections can point to different profiles without triggering an error, which is why the wrong URL can appear even when your project setup looks correct. 🛠️ Quick Checklist - You have more than one GBP profile connected in Search Atlas. - Your active OTTO project is set to the correct domain. - You have opened GBP Galactic and confirmed which profile is currently active there. - The active profile in GBP Galactic matches your intended project domain. If after reviewing GBP Galactic the wrong profile is still being used by the AI Agent, contact the Search Atlas support team so they can verify and correct the active profile on your account.

🔌 Troubleshooting AI Agent Connection Errors

This article covers common steps to take when your AI agent fails to respond or returns an unexpected error message. Because AI agent connection errors can stem from a variety of account-specific or configuration-specific causes, the steps below focus on what to gather and how to get the right help quickly. What to Check First Before escalating, gather the following information so our team can identify the root cause as efficiently as possible: - The exact error message you are seeing (copy the text or take a screenshot) - The name of the AI agent or project affected - When the error first appeared and whether it is consistent or intermittent - Any recent changes made to your account, integrations, or agent configuration When to Escalate Because AI agent connection errors are often tied to specific account configurations or backend states, the most reliable path to resolution is to contact our support team directly. Please have the following ready when you reach out: - Your project name and the name of the affected AI agent - The exact error message or a screenshot - A description of when the issue started and how frequently it occurs - A note of any recent changes to your account or integrations 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.

🗂️ Onboarding Playbook Auto-Run Stability Fix

A targeted fix has been applied to the onboarding playbook auto-run flow, ensuring agent projects are properly attached and descriptions are accurately sent during automated execution. ✨ What's New The onboarding playbook auto-run feature has been updated to correctly attach the agent project and transmit the associated description when the automated flow is triggered. Previously, a mismatch in how the customer frontend communicated with the AI agent pipeline could cause the onboarding sequence to run incompletely or fail silently. This fix aligns the frontend behavior with the underlying agent infrastructure, resulting in a more reliable and consistent onboarding experience. 📋 What to Expect No action is required on your part. The fix is applied automatically in the background. Users going through the onboarding playbook auto-run will now experience a smoother, uninterrupted flow with the correct agent context loaded from the start. If you previously encountered issues with the onboarding sequence not completing as expected, those should now be resolved. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗓️ Weekend Support Hours and Agent Availability

📋 Overview We know questions don't always wait until Monday. This article explains when live support agents are available on weekends, what response times to expect, and how to get help any time of day, including outside of staffed hours. 🤔 Are Agents Available on Weekends? Yes. Our support team offers live coverage on both Saturday and Sunday. Weekend hours are shorter than our weekday schedule, so response times may be slightly longer, but you can still reach a live agent for time-sensitive issues. ⏰ Weekend Support Hours Live weekend support is available during the following window: - Saturday: Reduced-hours live coverage, from 8 a.m. to 5 p.m. - Sunday: Reduced-hours live coverage, from 8 a.m. to 5 p.m. 🔍 How to Check Current Availability The fastest way to confirm whether an agent is online right now is to check directly in the product: 1. Log in to your Search Atlas account. 2. Click the chat icon in the lower-right corner of the screen. 3. Look at the chat header. It will show either an "Agents are online" status or the next time live support resumes. 💬 What to Expect on Weekends Weekend coverage is designed to keep you moving on urgent matters. Here is what typically happens: - During staffed hours: A live agent responds in chat, usually within a few minutes during quieter periods and longer during peak times. - Outside staffed hours: No action required from your side. It enters our queue and is answered when the next agent comes online, often first thing the following morning. - Complex issues: Some requests need a specialist who works standard weekday hours. In those cases, a weekend agent will gather details and escalate so the right person can follow up on the next business day. 🆘 Getting Help Any Time Even when live agents are offline, you have several self-service options that resolve many common questions instantly: - Knowledge Base: Search our help center for step-by-step guides on setup, billing, integrations, and troubleshooting. - In-app chat messages: Leave a detailed message with screenshots so an agent can respond quickly once online. - Live chat: Type human teammate in the chat widget in the bottom-right corner of the platform to be connected with a member of our team. ⚡ Tips for a Faster Response To help us resolve your issue on the first reply, please include: - The account or workspace name associated with your request - A clear description of what you were trying to do - The exact error message, if any - A screenshot or screen recording when relevant ❓ Frequently Asked Questions Do weekend agents handle the same issues as weekday agents? Weekend agents handle most account, product, and troubleshooting questions. A small number of specialized requests may be scheduled for follow-up during weekday hours. Will I lose my place in line if I message after hours? No. Messages sent outside staffed hours stay in the queue and are answered in order once agents return. Are hours different on public holidays? Yes. Holiday coverage may differ from a standard weekend. The in-app chat always reflects the current schedule. ✅ Summary Live support is available on both Saturday and Sunday during reduced hours, and you can confirm exact availability at any moment through the in-app chat. Outside staffed hours, your messages are queued and our knowledge base is available around the clock, so you are never without a way to get help. Additional Notes If you specifically need a person, type human teammate in the chat window. The automated assistant handles many common questions instantly; explicitly requesting a human routes you to a live agent when one is available.

🎯 The 9 Golden Loop Marketing Families and What Each One Delivers

🎯 The 9 Marketing Families Search Atlas currently runs 174 live Golden Loops across 9 marketing families. You choose which families to activate — it's never all-or-nothing. Each one runs the same signal → recommend → approve → ship → measure cycle, tailored to that part of your marketing: - CRM + Email (44 loops) — lifecycle and relationship marketing from first touch through retention. - Meta Ads (27 loops) — paid social health, creative, audiences, and timing in one rhythm. - SEO + AI Search (24 loops) — technical health, content, and visibility across search and answer engines. - Google Ads (22 loops) — search demand, spend, conversion quality, and landing-page alignment. - Website + CRO (19 loops) — page health, conversion friction, and experiments that improve the site. - Local + GBP (18 loops) — local presence, listings, reviews, and location-level visibility. - Authority + PR (11 loops) — trust, authority, citations, and earned distribution. - ChatGPT Ads (5 loops) — emerging paid discovery with measured, approval-aware learning. - LinkedIn (4 loops) — professional audience signals and human-reviewed presence. 📊 What to Expect, Family by Family Results vary by family and by account. Here's what's been documented so far — we're sharing real numbers where we have them, and being upfront where we don't, rather than giving a generic answer. Meta Ads Results A Day Parting loop more than cut CPA in half — a 57% reduction — in one documented account. Google Ads Results An always-on agent keeps spend inside an efficiency band and auto-adjusts budget in response to performance. SEO + AI Search Results One account saved 9 days and 17 hours on tag, meta, and header deployments; across a broader cohort, 6,203 ranking positions were gained, with one page jumping 72 positions in 3 days. Website + CRO Results Customers have used this for an agentic website rebuild applying CRO best practices; we don't yet have a documented before/after metric to share for this specific family. Local + GBP Results The goal is improved map ranking and phone call volume; one documented case reported a "massive improvement" in visibility, though not yet with a specific percentage. Authority + PR Results One 90-day campaign produced 5,000+ editorial placements, 12,000 press releases, and 75,000 cloud-stack deployments — roughly $2M in campaign value. LinkedIn Results Works by turning one piece of content (like a blog post) into multiple assets that get posted automatically; we don't yet have a documented engagement metric to share. CRM + Email Results We don't yet have a documented outcome case to share for this family. ChatGPT Ads Results We don't yet have a documented outcome case to share for this family. Across all 174 live loops, customers running Golden Loops have seen up to 90% faster content turnaround, 35% higher rankings, 80% less manual work, and 70% fewer SEO errors, once a channel is fully running on its own. We'll update this article as more documented per-family results become available. 🧭 Related Reading For what a Golden Loop is and the cycle it runs, see our overview article. For how approvals and safety controls work, see our article on the Golden Loops approval model. 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 Photo Count Restriction Errors

🔍 What Is Happening When you launch Atlas Agent to automatically create content such as Press Releases or Cloud Stacks, the Agent pulls all images stored in your Brand Vault and attempts to attach them to the content it is building. If the total number of images in your Brand Vault exceeds the limit the automated system can attach to a single piece of content, the Agent stops and returns a photo count restriction error. This is a known behaviour in the automated pipeline. Your Brand Vault data is safe and nothing has been deleted or corrupted. The error only affects automated content generation — it does not reflect a problem with your account or your images themselves. ✅ Why Manual Creation Still Works When you create a Press Release or Cloud Stack manually, you choose which images to attach at the time of creation. Because you are selecting a smaller set of images rather than attaching the entire Brand Vault automatically, the photo count limit is never reached and the content is created successfully. ⚙️ How to Work Around This Issue Until a permanent platform fix is fully rolled out, the most reliable workaround is to reduce the number of images in your Brand Vault so it stays within the limit the Atlas Agent can handle automatically. Follow the steps below: 1. Audit your Brand Vault images. Review all images currently saved in your Brand Vault and identify any that are duplicates, outdated, or not needed for automated content generation. 2. Remove excess images. Delete or archive images you do not need the Agent to use automatically, keeping only the core brand images you want attached to generated content. 3. Retry Atlas Agent. Once the image count is reduced, go to Left sidebar → Content → Content Genius and relaunch Atlas Agent to generate your Press Release or Cloud Stack. 4. Use manual creation as an immediate alternative. If you need content right away and cannot reduce your Brand Vault images immediately, use the manual creation flow inside Left sidebar → Content → Content Genius to select only the images you need and complete your content without hitting the restriction. 📋 Key Facts to Know - Your Brand Vault images and all account data remain completely safe — this error does not cause any data loss. - The photo count restriction is triggered by the total number of images in your Brand Vault, not by the size or format of the images. - Manual content creation is a fully supported alternative and produces the same output as the automated Agent flow. - Engineering has addressed related Brand Vault sync issues in recent platform updates, and improvements to the automated image-handling pipeline are ongoing. 💡 Tips to Prevent This in the Future - Keep your Brand Vault lean by storing only the images you actively use for content generation. - Regularly review and remove any images that were uploaded for one-off projects and are no longer needed. - If you add a large batch of images to your Brand Vault, test Atlas Agent on a small content task immediately afterwards to confirm the count is still within limits before running bulk generation. 🙋 Still Seeing the Error If you have reduced your Brand Vault images and Atlas Agent is still returning a photo count restriction error, or if you are unsure how many images are within the allowed limit, our team can investigate your specific account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Atlas Agent Error Affecting Playbook Functionality

🔍 Overview Some customers have experienced errors with Atlas Agent that prevent playbooks from running correctly. This article explains what caused the issue, what has been fixed, and what to do if you are still affected or would like to request compensation for the disruption. ⚙️ What Was Causing the Issue Several bugs affecting Atlas Agent were identified and have since been resolved by our engineering team. The confirmed issues included: - Atlas Agent failing in certain browsers that lacked full support for required browser features - Errors appearing when browsing all agent sessions or opening existing sessions - Unhelpful or raw error messages being surfaced to users instead of clear, readable ones - The tags field not functioning correctly when creating a new playbook All of the above have been marked as resolved. If you encountered any of these symptoms, the underlying cause has been fixed. ✅ Steps to Take If You Are Still Seeing Errors 1. Refresh your browser and clear your cache. Some error states can persist in the browser after a fix has been deployed. 2. Switch to a supported, up-to-date browser. One confirmed bug was specific to browsers missing certain modern browser capabilities. Using the latest version of Chrome, Edge, or Firefox is recommended. 3. Navigate back to Atlas Agent. Go to Left sidebar → Content → Content Genius and launch Atlas Agent from there to start a fresh session. 4. Retry your playbook. Open or create a playbook and test whether it runs successfully. If you were previously unable to use the tags field when creating a playbook, this should now be functional. 5. If errors persist, contact our support team. If you are still experiencing issues after following the steps above, our team needs to know so your case can be escalated. 💡 About Compensation for This Issue We understand that instability in a tool you rely on is frustrating. If Atlas Agent errors caused significant disruption to your workflow, you may be eligible for compensation. Our support team has the ability to escalate affected cases for review, and compensation has been offered to customers impacted by this bug. To be considered, you will need to contact us through the chat widget so your account can be reviewed and your case submitted for Tier 2 approval. Compensation decisions are made on a case-by-case basis. 🚀 What Our Team Did to Resolve This When this issue was first reported, our support team took the following actions: - Confirmed the bug was high priority and actively being worked on by developers - Logged affected customers so their cases were tracked - Escalated cases for compensation review through our internal process - Verified with customers once the fix was confirmed live If you reported this issue and have not yet heard back about compensation, please reach out through chat so we can follow up on your case. 📞 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix AI Agent Edits on Pillar Blog Pages

🔍 Overview Some customers have reported that the Website Studio AI agent declines to make edits — such as adding internal links — to pillar blog pages, even when the same prompt worked successfully before. This article explains what is known about this issue and what to have ready when reaching out for support. ⚠️ Why This Happens This is a known bug affecting the Website Studio AI agent when working on pillar blog pages. The root cause has not been fully confirmed, but reported symptoms include the agent refusing edit actions or failing to respond as expected on pillar page types. Because the underlying cause is being investigated on the backend, there are no verified self-serve steps that reliably resolve the issue. 📋 What to Have Ready When You Escalate To help our team investigate and resolve this as quickly as possible, please have the following information ready before reaching out: - Project name: The exact name of the Website Studio project where the issue occurred. - Pillar page URL: The specific page URL where the AI agent refused to make edits. - Prompt used: The exact prompt or instruction you entered into the AI agent when the failure occurred. - What you expected vs. what happened: A brief description of the intended edit and the agent's actual response (e.g., error message, refusal text, or no response). - Timestamp: The approximate date and time when the issue occurred, including your timezone. 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 Domains in Your Golden Loops Workbook

Overview If one or more domains are missing from your Golden Loops workbook — for example, they do not appear in your domain list or you cannot run reports for them — this is typically a backend configuration issue that requires our team to investigate and resolve on your behalf. What This Means Missing domains in a Golden Loops workbook are not always something you can fix through the platform interface alone. In many cases, the root cause involves how domains are configured or associated with your workbook on the backend. Our support team will need to look into your specific account setup to identify and correct the problem. What to Expect Once you reach out, a member of our team will review your account, identify why the domains are not appearing in your workbook, and make the necessary backend adjustments. You do not need to attempt to reconfigure your workbook manually before contacting us. What to Have Ready When You Escalate To help our team resolve this as quickly as possible — especially if you are working against a deadline — please have the following information ready when you contact us: - Your account email address — the email associated with your Search Atlas account. - The exact domain URLs that are missing — for example, seoraleigh.net. List every domain that should appear but does not. - The name of the specific workbook where the domains are missing. - Any deadline or urgency context — let us know if you have a time-sensitive client deliverable so we can prioritize accordingly. - Any error messages or unexpected behavior — describe exactly what you see (or do not see) when you access the workbook. 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 AI Agent Technical Errors Quickly

🔍 What Is This Error? If you see a message like "Sorry, there was an error processing your message" or the AI Agent stops responding mid-task, you have encountered a temporary technical error. These errors can occur when the agent tries to process a request, apply on-page fixes, or retrieve content details. The good news: most of these errors are transient and resolve quickly with a few simple steps. ⚠️ Common Situations Where This Happens - The AI Agent returns an error immediately after you send a message. - The agent starts a task — such as deploying on-page fixes — and then stops with an error. - Post details or content previews fail to load and show a technical error instead. - The agent appears to abandon your request without completing it. 🚀 How to Fix the Error 1. Refresh the page. Open OTTO SEO → All Sites (SEO Automation) from the left sidebar and reload your browser tab. This clears temporary session issues that can interrupt agent tasks. 2. Retype your request. Start a new message to the AI Agent. Do not copy and paste the previous message — rephrase it slightly and try again. 3. Wait one to two minutes. Occasional spikes in platform load can cause brief errors. Waiting a short time before retrying usually resolves this. 4. Check your browser. Clear your browser cache or try a different browser (Chrome or Edge recommended). Browser extensions can sometimes interfere with the agent. 5. Try a different task scope. If the error happens on a specific page or fix, try applying the action to a different URL first to confirm the issue is not isolated to one piece of content. 🔄 Why These Errors Occur AI Agent errors are typically caused by one of the following: - Temporary server timeouts — the agent's request takes longer than expected and the connection resets. - Tool availability changes — occasionally, an internal tool the agent relies on is updated or temporarily unavailable, causing the agent to stop mid-task. - Session expiry — long inactive sessions can cause the agent to lose context, resulting in a failed response. Our engineering team actively monitors error patterns and deploys fixes rapidly. Known issues related to agent errors have already been resolved as part of ongoing platform improvements. ✅ What to Do If the Error Persists If you have followed the steps above and the AI Agent continues to return errors, gather the following information before reaching out to support — it helps our team investigate faster: - The exact error message you see on screen. - The task or request you were trying to complete. - The URL or page the agent was working on. - The approximate time the error occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤝 How to Get Support: Understanding Agent Availability and Contacting Our Team

Many customers reach out asking whether a specific support agent is available or who is currently online. While we understand you may have had a great experience with a particular team member, support at Search Atlas works as a shared team. This means you don't need to wait for one person to be available to get fast, expert help. This article explains how our support staffing works and how to get your issue resolved as quickly as possible. 👥 How Support Staffing Works Our support team operates as a unified group rather than relying on individual agents. Here's what that means for you: - No single point of contact required. Any available agent can access your account history and pick up where a previous conversation left off. - Shared notes and context. Every conversation is documented, so you won't have to repeat your full story if a different agent assists you. - Coverage across hours. Because the team rotates and covers different shifts, requesting a specific person by name can sometimes delay your help if that person is offline, on another case, or out of office. In short: the fastest path to a solution is to describe your issue, not to request a specific agent. 💬 How to Reach Support You can contact the Search Atlas support team through any of the following channels: - In-app chat: Click the chat icon in the bottom corner of your dashboard to start a conversation. Once the chat bot answers, type: "Human Teammate". This is the only way available to contact support. ⚡ How to Get Help Faster The single biggest factor in a quick resolution is a clear description of your issue. When you start a conversation, please include the following details instead of (or in addition to) asking who is available: 1. What you are trying to do. Example: "I'm trying to publish a page through the OTTO SEO tool." 2. What is happening instead. Example: "The page shows an error when I click Publish." 3. Where it's happening. Note the specific tool, project, or page, and include a URL if possible. 4. Any error messages. Copy the exact text or attach a screenshot. 5. What you've already tried. This helps us skip steps you've ruled out. Providing these details up front lets the first available agent begin solving your problem immediately, rather than spending the first few messages gathering background. ✅ Example: A Strong Support Request "Hi, I'm trying to connect my Google Search Console account in the Site Explorer, but after I authorize access I get a 'Connection failed' message. I'm using the project named 'Main Website.' I've already tried reconnecting twice and clearing my browser cache. Here's a screenshot of the error." A request like this gives any agent everything they need to help right away. 🙋 Can I Request a Specific Agent? You're always welcome to mention that you previously worked with a particular team member, and we'll do our best to route your conversation to them if they're available. However, please keep in mind: - That agent may be offline, assisting other customers, or off for the day. - Waiting for one person can slow down your resolution. - Any agent can fully access your case and continue your prior conversation. If continuity matters for a complex, ongoing issue, simply reference your previous ticket or conversation number, and the next agent can review the full history. 🕒 Support Availability Our team is available during published support hours, which you can find in your account dashboard and on our Help Center contact page. If you reach out outside of these hours, your message will be queued and answered by the next available agent. For urgent account or billing matters, please flag the priority clearly in your first message. ❓ Frequently Asked Questions Is a specific agent working right now? We don't share individual staff schedules, but the support team is always staffed during business hours. Start a conversation and the next available agent will assist you. Will I have to explain my issue again to a new agent? No. All conversations are documented, so any agent can review your history and continue without you repeating yourself. What if my issue is urgent? State that it's urgent at the start of your message and include all relevant details so we can prioritize and act quickly. 🔑 Key Takeaway You don't need to wait for a specific agent to get expert help. The fastest way to resolve your issue is to clearly describe what you need, and the next available member of our team will take care of you.

🛠️ AI Agent Orchestrator: Website Building Routes to Wrong Tool

When you ask the AI Agent to build a website, it should open Website Studio automatically. In some cases, the agent opens Cloud Stack instead — or skips the action entirely when your request is phrased in past tense. ⚙️ Why the AI Agent Selects the Wrong Tool The AI Agent Orchestrator reads the phrasing of your request to decide which tool to open. Two patterns trigger incorrect routing: - Cloud Stack opens instead of Website Studio: Certain keyword combinations in your prompt match the Cloud Stack routing rule before the Website Studio rule is evaluated. - No action is taken: Past-tense phrasing — for example, "I built a website" or "I was creating a site" — signals to the agent that the task is already complete, so it skips launching any tool. 💡 How to Phrase Website Building Requests Correctly Use present-tense, action-oriented language so the AI Agent routes to Website Studio. - Use: "Build a new website" or "Create a website" - Use: "Open Website Studio" or "Start a new site in Website Studio" - Avoid: "I built a website" or "I was building a site" — past tense causes the agent to treat the task as done - Avoid: vague phrases like "work on my site" without specifying the action you want taken Naming the tool explicitly — for example, "Use Website Studio to create a site" — ensures correct routing regardless of other wording in your message. 🛠️ What to Do If Cloud Stack Opens Instead of Website Studio 1. Close or dismiss the Cloud Stack panel that opened. 2. Return to the AI Agent chat. 3. Re-enter your request using present-tense phrasing — for example: "Build a new website in Website Studio." Website Studio will open on your next prompt and you can begin building immediately. ⚠️ Known Issue Status This routing behavior has been identified and resolved by the Search Atlas engineering team. If you are still seeing Cloud Stack open for website building requests after rephrasing your prompt, contact Search Atlas support so the team can investigate your specific account. 🎯 You now know why the AI Agent may open Cloud Stack instead of Website Studio and how present-tense phrasing gets you to the right tool every time. If the issue persists after rephrasing, reach out to Search Atlas support for hands-on assistance.

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

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

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

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

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

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

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

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

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

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

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

📊 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 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 Playbook 403 Errors and OTTO Deployment Issues

🔍 Overview Two related issues can interrupt your SEO automation workflow: a 403 permission error when launching a playbook (such as Create Press Release), and OTTO deployment changes not rendering on your WordPress site after the playbook runs. This article explains what these issues look like and what information to have ready so our team can resolve them for you quickly. ⚠️ Understanding the 403 Permission Error A 403 error means the system has blocked an action because it does not recognise you as having the required permission. This error can appear when attempting to run a playbook and will prevent the playbook from starting. Because this is a backend issue, our support team will need to investigate your specific account configuration to identify the cause and apply a fix. When contacting support, please have the following ready: - The exact name of the playbook you were trying to run (e.g. Create Press Release). - The exact error message you received, including any error code shown on screen. - The date and time the error occurred. - Whether this playbook was created by you or shared from another account. 🚀 Why OTTO Changes Are Not Showing on Your WordPress Site After OTTO deploys changes, you may find that those changes do not appear on your live WordPress site. Symptoms can include changes appearing to apply inside Search Atlas but not rendering on the live site, or being prompted repeatedly to approve the same deployment action. Because this is a backend issue, our team will need to review your account and site configuration directly. When contacting support, please have the following ready: - Your project or site name as it appears in Search Atlas. - A description of the specific changes OTTO was deploying (e.g. page type, content type). - The date and time you first noticed the issue. - Any error messages or status indicators shown in the platform. - Confirmation of which WordPress site is affected (URL). ✅ In the Meantime While awaiting a fix, you can take the following steps: - Clear your browser cache and any caching plugin active on your WordPress site, then check your live pages again to rule out a display cache issue. - Verify that the OTTO plugin is active and up to date in your WordPress dashboard under Plugins. - Check that your WordPress connection to Search Atlas has not been interrupted by reviewing your connected sites settings. 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 OTTO Deployment and Playbook Errors on WordPress

🔍 Overview If your OTTO SEO suggestions are not deploying to your WordPress site, or if the Atlas playbook returns a 403 or 400 error during preview, this article explains what may be happening and what to have ready when you contact our team for assistance. ⚙️ What May Be Causing This OTTO deployment and playbook preview errors on WordPress trial sites can stem from a number of underlying causes, including plugin connectivity issues, caching conflicts, or an incomplete site authorisation. Because these errors often require backend investigation to diagnose correctly, our support team will need to look into the specifics of your setup directly. 📋 What to Have Ready When You Escalate To help our team resolve your issue as quickly as possible, please gather the following before reaching out: - The exact error message you are seeing (e.g., 403 Forbidden, 400 Bad Request, or any other on-screen text). - The name of your WordPress project or trial site as it appears in Search Atlas. - The timestamp of when the error first occurred or the most recent occurrence. - A brief description of the action you were taking when the error appeared (e.g., running a playbook preview, deploying suggestions, scanning the site). - Any caching or third-party plugins you have active on the WordPress site (e.g., WP Rocket, Google Tag Manager). - Screenshots of the error if available. Having this information ready will allow our team to investigate your specific configuration without delays. 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 Internal Links Not Added by Content Playbook

🔍 Overview When you run the Content-Build Internal Links playbook, you may receive a completion report but find that no internal links were actually inserted into your target pages. This article explains the most common causes and the steps you can take to fix the issue. ⚠️ Why This Happens The internal links playbook relies on data stored in your BrandVault to identify which URLs to link to. If that data is missing, incomplete, or not yet populated, the agent has nothing to work with and will silently skip the insertion step — even though the task is marked as complete. The most common root causes are: - Empty internal links fields in BrandVault — The agent requires populated URL and anchor-text data. If these fields are blank, no links are inserted. - No valid page paths detected — The playbook needs resolvable page paths. URLs that are missing, malformed, or return errors are ignored. - Article Refinement conflict — If you requested internal links through an Article Refinement step rather than a dedicated internal-links step, the links may not be inserted correctly. - Stale or cached project data — Occasionally, outdated project data causes the playbook to act on old information. 🛠️ How to Fix It 1. Check your BrandVault internal links fields. Navigate to your BrandVault settings and confirm that the internal links section contains valid URLs and corresponding anchor text. Every URL must be a complete, working path. 2. Refresh your project data. Go to Left sidebar → Home → [project] (Executive Summary) and click Refresh Summary. Wait for the refresh to complete before re-running the playbook. 3. Re-run the internal links playbook. After confirming BrandVault data is populated and your project data is fresh, open your playbook and run the Content-Build Internal Links step again. Check the target pages once the completion report appears. 4. Avoid using Article Refinement as a substitute. If you need internal links inserted, use the dedicated internal-links playbook step rather than requesting them through an Article Refinement prompt. These are separate processes and produce different results. 5. Verify page paths are valid. Review the URLs listed in your BrandVault and confirm each one resolves correctly. Remove or correct any broken, redirected, or incomplete paths. ✅ How to Confirm Links Were Added After re-running the playbook, open each target page in the Content Builder and review the body content for inserted anchor links. Do not rely solely on the completion report — always inspect the page content directly to verify the links are present. 🚫 Known Limitations - The agent does not insert links if all internal link fields in BrandVault are empty. There is no partial insertion — it is all or nothing based on available data. - Links requested through Article Refinement follow a different insertion path and may not be added even if BrandVault data is complete. Use the dedicated playbook step instead. - Newly added BrandVault URLs may take a moment to be recognised. Always refresh project data before running the playbook after making BrandVault changes. 💬 Still Need Help? If you have followed all the steps above and internal links are still not being inserted, 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 Stuck Payments and Playbook Execution Issues

Overview Two separate issues can sometimes affect your Search Atlas experience at the same time: a payment page that stays stuck on "Processing" without completing, and a playbook that won't execute for a website. This article explains what to expect and what information to have ready when you contact our team for help. Payment Page Stuck on Processing If your payment page has been showing "Processing" for an extended period — in some cases several days — without completing or confirming your transaction, this is a known issue that requires backend investigation by our team. What causes this? The payment may appear unresolved on your end even if a charge has already been applied. Our team needs to manually verify your payment status and unlock your account if needed. What to Do If Your Payment Is Stuck 1. Do not attempt the payment again — submitting a second payment while the first is unresolved may result in a duplicate charge. 2. Check your email inbox for a receipt or confirmation email. If you received one, your payment likely went through successfully. 3. Check your bank or card statement to confirm whether a charge has been applied. 4. Contact our support team with the following information so we can resolve this quickly: - Your account email address - The approximate date and time the payment was initiated - A screenshot of the stuck payment page if available Playbook Not Running for a Website If you are trying to run a playbook for a specific website and it appears to hang or never start, this is a separate known issue that requires investigation by our team — it is not related to your payment or subscription status. What to Do If Your Playbook Is Stuck Because this issue requires backend action to resolve, please contact our support team and have the following ready: - The name of the website or project the playbook is associated with - The exact name of the playbook you are trying to run - The date and time you first noticed the issue - Any error message or status indicator displayed on screen (exact wording if possible) Our team will investigate and take the necessary action to get your playbook running again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Atlas Agent 'I Need a Message' Error

What Is This Error? When you type a message into Atlas Agent and see the response "I need a message to respond" instead of a normal reply, the agent is not recognising your input. This is a known issue where Atlas Agent's text input becomes blocked, preventing normal interactions. What Causes This Error? This error has been identified as a persistent blocker affecting text input in Atlas Agent. When it occurs, every message you type triggers the same error response, with no successful interactions possible. This is not something that can be resolved through browser-level adjustments on your end — it requires review and action by our team. What to Do When You See This Error If Atlas Agent is returning "I need a message to respond" to every message you send, contact our support team right away. To help us resolve this as quickly as possible, please have the following information ready before you reach out: - Your project name or workspace name - The exact error message you are seeing - The date and time the error first appeared - Confirmation of whether the error occurs on every message you send If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Slack Coworker Bot Connection Issues

🔍 Overview After reinstalling or reconnecting the Slack integration, some users find that the Coworker bot stops responding in channels and DMs, the dashboard still shows Slack as Not Connected, and the bot cannot read thread history — even when Slack reports the required scopes are granted. This is a backend gateway mapping issue that requires our team to resolve on your account. ⚠️ Why This Happens When the Slack app is reinstalled, Slack issues a new OAuth token and workspace ID. If the platform's internal gateway mapping is not updated to point to this new token, the connection appears broken from the Search Atlas side even though Slack itself shows the app as installed. A stale mapping also blocks thread history access because the bot cannot authenticate its read requests correctly. Resolving this mapping requires a backend correction by our support team. 🛠️ What to Do Because this issue involves a backend gateway mapping that cannot be corrected from the user interface, please escalate to our support team. To help us resolve your issue as quickly as possible, have the following information ready before reaching out: - Your Search Atlas workspace or project name - The exact error message you see, if any (for example, the 'Not Connected' status message or any error shown during the OAuth flow) - The timestamp of when the issue started or when you last attempted to reconnect Slack - Whether you have already attempted to remove and reinstall the Slack app, and if so, approximately when - Your Slack workspace name so our team can locate the relevant gateway mapping on the backend 💡 What to Expect Once our team receives the above details, we will correct the gateway mapping on the backend so that the new OAuth token and workspace ID are properly registered. After the fix is applied, the Coworker bot should resume responding in channels and DMs, and thread history access will be restored. You do not need to take any additional action in Slack or Search Atlas unless our team instructs you to. 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 the 400 Error in Agent Hub Custom Prompts

🔍 What This Error Means A 400 error in Agent Hub means the request your custom prompt sent could not be processed by the system. It is not a problem with your account or with Agent Hub itself. Instead, it usually points to something in the way the custom prompt is written or configured. This is why playbooks keep working while your custom prompt fails. Playbooks are pre-built and validated by Search Atlas, so their structure, variables, and formatting are already correct. A custom prompt is created from scratch, which means a small formatting or input issue can cause the request to be rejected. ⚙️ Common Causes of the 400 Error Most 400 errors with custom prompts come from one of the following: - Prompt is too long: Very long prompts can exceed the allowed input size and be rejected. Prompts that go over the character limit are a confirmed cause of this error, especially when they contain long or detailed instructions. - Unsupported characters: Pasting from another program can add hidden symbols, smart quotes, or formatting that the system cannot read. - Empty or missing fields: A required field, such as a target URL or keyword, was left blank. - Broken variables: A placeholder or variable was edited incorrectly, so the system cannot fill it in. - Invalid links: A URL in the prompt is misspelled, incomplete, or missing the https:// prefix. 🛠️ How to Fix It Work through these steps in order. Most customers resolve the error within the first few checks. 1. Shorten your prompt: Remove any text that is not essential and keep your prompt within the character limit. Keep instructions clear and direct. 2. Retype instead of pasting: If you copied the prompt from a document or email, retype it directly into Agent Hub to strip out hidden formatting. 3. Check all required fields: Make sure every field the prompt needs is filled in correctly and nothing is left blank. 4. Review your variables: Confirm that any placeholders match the format used in working playbooks. Do not change the surrounding symbols. 5. Verify your links: Make sure each URL is complete, correctly spelled, and begins with https://. 6. Test with a simple prompt: Enter a short, basic prompt to confirm the error is tied to your original wording and not a wider issue. 💡 Tips to Prevent Future Errors A few habits will help your custom prompts run smoothly every time: - Start from a playbook: Use a working playbook as a template, then adjust it gradually to fit your needs. - Build in small steps: Add one instruction at a time and test as you go, so you can quickly spot what causes a problem. - Keep prompts focused: Clear, concise prompts are less likely to trigger errors and produce better results. - Avoid special formatting: Stick to plain text and avoid pasting styled content from other tools. 💬 Still Seeing the Error? If you have tried these steps and the 400 error continues, our team is ready to help. If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team. Sharing the exact prompt you used will help us resolve the issue faster.

🔧 Fix Coworker Slack Visibility and Switch Credits

Overview Two common questions arise together: Coworker not appearing inside the Search Atlas Slack integration, and how to switch from legacy credits to Universal Credits. This article explains what is happening, what to have ready when you contact support, and what to expect during your credits migration. Why Coworker Is Not Visible in Slack If Coworker is not appearing as expected within your Slack integration, our team investigates these cases on a per-account basis and will need to take action on the backend to resolve it. When contacting support about this issue, please have the following ready: - Your Search Atlas account email or workspace name. - The exact behavior you are seeing (e.g. Coworker not appearing, unable to connect, an error message — include the exact wording if possible). - The timestamp of when you first noticed the issue. Universal Credits Migration If you need to switch from legacy credits to Universal Credits or have questions about your credits balance after a migration, our team can assist with the transition on the backend. When contacting support about credits migration, please have the following ready: - Your Search Atlas account email or workspace name. - Whether you currently see a legacy credits balance and approximately how many credits remain. - Any error message or unexpected behavior you encountered during the migration process, including exact wording and timestamp. 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 Slack Coworker Off-Brand Content

🔍 Why Coworker Content Goes Off-Brand The Slack Coworker AI generates daily article ideas and can draft full articles on request. However, if it lacks clear brand guidelines, target keywords, and topic context, it may produce content that misses the mark — wrong tone, incorrect keywords, or entirely unrelated subject matter. This usually happens for one of three reasons: - No brand voice configured: The AI has no reference for your tone, style, or audience. - Missing keyword targeting: The AI guesses at keywords instead of using the ones you intend. - Lost context mid-conversation: Long Slack threads can cause the AI to drift from the original topic. The good news is that each of these issues is preventable with a few setup steps. ⚙️ Set Up Brand Voice in Content Genius Before asking the Slack Coworker to write articles, make sure your brand voice and content settings are configured in the platform. This gives the AI a consistent reference point for tone, audience, and style. 1. Navigate to Content → Content Genius from the left sidebar. 2. Open a new or existing project under Generate or Write an article. 3. Fill in the brand voice fields: describe your target audience, preferred tone (professional, casual, authoritative, etc.), and any style notes the AI should follow. 4. Specify your primary and secondary keywords so the AI knows what to optimize for. 5. Save your settings before requesting articles through Slack. Once these settings are saved, the Slack Coworker pulls from them when generating content, which dramatically reduces off-brand output. 💡 Provide Clear Context in Slack When you reply to a daily idea message and ask the Coworker to write an article, the more context you provide, the better the result. Follow these guidelines: - Reference the specific idea: Instead of saying "write it," say "write the article about [exact topic from the idea]." - Restate your target keyword: Include the keyword you want the article to target so there is no ambiguity. - Keep conversations short: Start a fresh Slack thread for each article request to prevent context drift. - Specify article type: Tell the Coworker if you want a listicle, how-to guide, thought leadership piece, or news commentary. For example, instead of "Write this one", try: "Write a 1,200-word how-to article about off-road caravan maintenance targeting the keyword 'off-road caravan tips' for a South African audience." 📊 Review and Rework Generated Articles Even with proper setup, always review AI-generated content before publishing. If an article comes back off-brand or with the wrong keywords, you can refine it directly in the platform: 1. Navigate to Content → Content Genius. 2. Select Rework existing article. 3. Paste the generated content and provide specific instructions on what needs to change (tone, keywords, structure, etc.). 4. Click generate to receive a revised version. This gives you a second pass with more explicit guidance, which typically resolves quality issues. ✅ Recently Fixed Known Issues Our team has resolved several bugs that contributed to off-brand and inaccurate Slack Coworker output. If you experienced any of the following, they should no longer occur: - Context loss: The Coworker would lose the original topic mid-thread and generate completely unrelated content (for example, writing about skincare instead of off-road caravans). This has been fixed. - Hallucinated responses: When asked to write news jacking articles, the AI would sometimes share unrelated account details or meeting schedules. This has been resolved. - Slack formatting errors: Emoji shortcodes rendered as literal text and bold formatting appeared incorrectly. Formatting now renders properly in Slack. If you still encounter any of these issues after the fixes, let us know so we can investigate further. 🚀 Best Practices for Consistent Results - Update brand voice settings quarterly or whenever your messaging strategy changes. - Use Content Genius for complex articles that require detailed keyword targeting — it offers more controls than the Slack quick-write flow. - Avoid stacking multiple requests in a single Slack thread. One topic per thread keeps the AI focused. - Always verify keywords in the generated output against your intended targets before publishing. 💬 Still Getting Off-Brand Content? If you have followed the steps above and the Slack Coworker is still producing inaccurate or off-brand content, there may be an account-specific configuration issue we can help resolve. 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 WordPress Connector Errors in Atlas Coworker

🔍 Overview If your WordPress site appears as Active in Atlas Coworker but returns an error such as "The operation wordpress-get-current-user is not available for wordpress" when you attempt to run operations, your connector is in a broken state. This is a known issue affecting WordPress and custom-MCP connectors in Coworker, and it does not automatically resolve on its own. This article explains what causes the error, which sites are affected, and the steps you can take right now to restore functionality. ⚠️ What This Error Means An Active status only confirms that a connection record exists — it does not guarantee the connector is fully functional. The error message indicates that the gateway routing between Coworker and your WordPress site is broken, meaning Coworker cannot execute any WordPress operations through that connector, even though the connection appears healthy on screen. Common symptoms include: - Connection status shows Active but all WordPress operations fail immediately. - Error messages reference operations such as wordpress-get-current-user, wordpress-get-posts, or similar WordPress actions being unavailable. - Bulk publish or content operations do nothing or return instant errors. 🌐 Does This Affect All My WordPress Sites? Not necessarily. Each WordPress connector is independent, so the issue is tied to the specific site where the error appears. However, if you connected multiple WordPress sites around the same time using the same workflow, it is worth checking each one individually, as the underlying routing problem can affect any connector created through the broken setup flow. To check your other sites, navigate to Coworker in the left sidebar and review each WordPress connection. Attempt a test operation on each one to confirm whether it succeeds or returns a similar error. 🛠️ Steps to Resolve the Error 1. Go to Coworker. In the left sidebar, click Coworker. 2. Locate the affected connection. Find the WordPress site that is returning the error (for example, longislandcustomblinds.com). 3. Remove the broken connector. Disconnect or delete the existing WordPress connection for that site. Do not simply reconnect on top of the existing record — the old broken record must be removed first. 4. Reconnect your WordPress site. Use the connector setup flow to add the site again from scratch. Follow all prompts through to completion. Ensure you reach the final confirmation step — an incomplete setup is one of the most common causes of this error. 5. Test the connection immediately after reconnecting. Run a simple operation, such as fetching the current user or retrieving a post, to confirm the connector is working before relying on it for bulk tasks. 💡 Tips to Prevent This Issue - Complete the full setup flow. Do not close the connector window or navigate away before the setup confirms completion. Partial connections can appear Active while being non-functional. - Use the direct connector setup link. If the AI Agent or an in-platform prompt gives you a WordPress connection link that leads to an unexpected page, do not use it — navigate to Coworker manually via the left sidebar instead. - Avoid white-label domain URLs during setup. If your workspace is accessed via a white-label domain, connector setup redirects may fail. Use the primary Search Atlas platform URL when connecting WordPress sites. - Check each site individually. If you manage multiple WordPress sites in one workspace, test each connector separately after any reconnection to confirm all are working. 🔄 Current Status The Search Atlas engineering team has identified the root causes behind broken WordPress connectors in Coworker and fixes are actively in development. These include improvements to the connector setup flow, resolution of gateway routing errors, and cleanup of incomplete connection records. You do not need to wait for the fix to be deployed — following the reconnection steps above will restore functionality for your site now. 🙋 Still Need Help? If you have followed the steps above and your WordPress connector is still returning errors, or if you are unsure whether additional sites in your workspace are affected, our team can investigate your specific connection records 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.

🔌 Troubleshooting AI Agent Connection Errors on Send

This article helps you understand what to do if you encounter a connection error when submitting a prompt in an AI-powered area of the platform. Because the specific steps that resolve this error may vary depending on your account and environment, the best path forward is to reach out directly so our team can investigate and fix it for you. 📍 Where This Occurs The connection error typically surfaces after you submit a prompt in an AI-powered content area of the platform. The same error is returned regardless of what you type, which indicates a session or agent connectivity issue rather than a problem with your prompt itself. 🛠️ 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 name of the project or workspace you were working in when the error occurred - The exact error message you see on screen (copy the full text if possible) - The date and approximate time when the error first appeared - The browser and operating system you are using - Whether the error appears consistently on every prompt submission, or only sometimes ✅ What Happens Next Once you contact our team with the details above, a member of our support team will investigate the connection issue on the backend and work to restore normal function for your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Any recent changes made to your account, integrations, or agent configuration