Getting Started with Atlas Agent

🔎 How to Find Previous Chat

This guide helps you locate a previous chat and check why it may not appear in your available history. 📍 Where to Find It Open Coworker from the left sidebar. 🛠️ Step-by-Step 1. Open Coworker from the left sidebar. 2. Review the available conversation history and look for the chat using its topic or approximate date. 3. Confirm that you are signed in to the same account and workspace where you originally started the conversation. 4. If the conversation is not listed, refresh the page and check the history again. 5. If it still does not appear, the chat is not currently available in that account or workspace. Contact a human teammate for help checking the conversation. ✅ How to Confirm It Worked The fix is confirmed when your previous chat appears in Coworker and its messages load when opened. If it remains absent after checking the correct account and workspace, it cannot be confirmed as recovered from the available history. 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.

🤖 Connect Search Atlas MCP and Coworker Slack Integration

🔍 What Is Search Atlas MCP? Search Atlas MCP (Model Context Protocol) is a standardized connection layer that lets external AI agents and automation tools — such as Manus, Claude, or custom AI workflows — communicate directly with your Search Atlas data and features. By connecting an AI agent to Search Atlas MCP, you give it access to SEO tools, site metrics, keyword research, and more, all without leaving your preferred automation environment. 🤖 What Is the Search Atlas Coworker? The Search Atlas Coworker is an AI agent built into the platform. It can receive instructions, execute SEO tasks, and report back results. The Coworker is designed to work across messaging platforms, including Slack, so you can delegate tasks conversationally without logging into the dashboard for every action. Think of the Coworker as your always-on SEO assistant — you assign tasks in plain language, and it handles the execution using your connected Search Atlas account data. ⚙️ How to Connect Search Atlas MCP to an AI Agent (e.g. Manus) 1. Locate your MCP credentials: Log in to Search Atlas, then navigate to Settings → API Keys to find or create your Search Atlas API key. Alternatively, you can authenticate via OAuth login (an active subscription is required). Keep these credentials private. 2. Open your AI agent platform: In Manus (or your chosen agent), go to the integrations or tools section and select the option to add a custom MCP server or external tool connection. 3. Enter your MCP details: Paste your Search Atlas MCP endpoint URL and provide your Search Atlas API key via the X-API-Key header (or authenticate via OAuth login). Save the connection. 4. Test the connection: Run a simple test query (for example, ask the agent to retrieve keyword data for a domain) to confirm the connection is live and returning results. 5. Assign permissions: Ensure the operations your agent needs (such as reading keyword rankings or pulling site metrics) are enabled for your account tier. Some operations may require a specific plan level. Important: If you see JWT authentication errors or the agent connects but returns no output for completed tasks, this is a known issue currently being investigated by the engineering team. See the troubleshooting section below for next steps. 💬 How to Use the Search Atlas Coworker in Slack 1. Connect Slack to your Search Atlas account: From your Search Atlas dashboard, navigate to the Coworker or Integrations section and follow the prompts to authorize your Slack workspace. 2. Invite the Coworker bot to a channel: In Slack, invite the Search Atlas Coworker bot to the channel where you want to use it (type /invite @Search Atlas Coworker and select the bot from Slack's autocomplete). 3. Assign tasks in plain language: Mention the bot and describe the task you need. For example: @SearchAtlasCoworker run a keyword gap analysis for example.com vs competitor.com. 4. Review task output: The Coworker will post results directly in the Slack channel once the task is complete. Complex tasks may take a few minutes. 5. Iterate and refine: You can follow up in the same thread with additional instructions to refine the output or assign a new related task. ✅ Best Practices for Using the Coworker - Be specific with instructions: The more detail you provide (target domain, competitor URLs, target keywords, location), the more accurate the output. - Use dedicated channels: Create a focused Slack channel for SEO tasks to keep outputs organized and easy to reference. - Check task status: If you do not receive output after several minutes, re-send the request or check whether the Coworker is still processing a previous task. - Keep credentials secure: Never share your Search Atlas API key in public Slack channels or with unauthorized team members. 🛠️ Troubleshooting Common Issues - Authentication error when connecting MCP: Double-check that you copied the full API key without extra spaces. If the error persists, generate a new API key from Settings → API Keys and reconnect. This is a known issue under active investigation. - Agent connects but returns no output: This is a known bug affecting some accounts where Slack task and job completions return empty responses. Our engineering team is actively working on a fix. In the meantime, try reassigning the task or testing the same request via the Search Atlas dashboard directly. - Required operations not permitted: If your AI agent can see Search Atlas MCP but cannot execute certain operations, your account permissions may need to be updated. Contact support using the method below. - Coworker bot not responding in Slack: Confirm the bot was successfully invited to the channel and that your Slack integration is still authorized in Search Atlas settings. Re-authorizing the connection often resolves this. 📞 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.

🏠 Home / Agent Hub: Overview

The Home page (also called the Agent Hub) is the first screen you see when you log in to Search Atlas. It's your personalized command center for talking to the Atlas AI agent, launching SEO playbooks, and keeping an eye on every project in your portfolio. What can I do from Home? Type a request directly into the Atlas Agent prompt at the top of the page to ask the AI agent to take an action on your behalf — for example, launching a playbook or creating a project. Below the prompt, the Recommended Playbooks panel surfaces ready-to-run SEO playbooks you can launch with one click. How do I check my portfolio's performance? The Portfolio Summary section gives you a quick read on how your sites are trending, with tabs for Trending Up, Stable, and Trending Down. Use these to spot which projects need attention. How do I manage individual projects? The Active Projects list on the Home page (Hi, CSM. What will we get done today?) shows every project you're tracking. Each project card includes an AI Score broken down into Content, Authority, Technical, and UX Signals sub-scores, along with connection status for Search Analytics, Local/GBP, and Smart Ads. From here you can create a new project, connect a Google Business Profile, or create a new ad campaign directly from the relevant project card. If you can't find what you're looking for, our support team is available via live chat in the bottom-right corner of the platform.

🗺️ Mapping CMS Connector IDs for Atlas Brain SEO Enhancements

🔍 Overview Atlas Brain can automatically push SEO enhancements—such as title tags, meta descriptions, and on-page content updates—directly to your website through a CMS Connector. To make sure those enhancements land on the correct site, Atlas Brain needs to know which CMS Connector ID matches each project. This article explains what a CMS Connector ID is, how to find it, and how to map it so your enhancements are delivered accurately. 🔌 What Is a CMS Connector ID? A CMS Connector is the secure link between Search Atlas and your content management system (for example, WordPress, Shopify, or Webflow). Each connector you create is assigned a unique CMS Connector ID. This ID acts like an address: it tells Atlas Brain exactly which connected website should receive a given SEO enhancement. If you manage more than one website—or multiple connectors for the same domain—each one has its own ID. Mapping the correct ID prevents enhancements from being sent to the wrong site. ✅ Before You Begin - Make sure you have at least one CMS Connector already installed and connected. If you have not set one up yet, install the connector for your CMS first. - Confirm you have admin or owner access to the relevant Search Atlas project. - Have a list of the websites you plan to connect so you can match each one to its connector. 🪪 Step 1: Locate Your CMS Connector IDs Follow these steps to find the ID for each connector: 1. Log in to your Search Atlas dashboard. 2. Go to Settings in the left-hand navigation menu. 3. Select CMS Connectors from the Settings menu. 4. Review the list of connected sites. Each entry displays the connector name, the linked domain, and its unique CMS Connector ID. 5. Copy the ID for the connector you want to use. We recommend keeping a short reference list that pairs each domain with its ID. 💡 Tip: Confirm You Have the Right Connector If you see several connectors with similar names, check the linked domain and connection status (it should show as Active or Connected). Matching the domain is the most reliable way to confirm you have the correct ID. 🗺️ Step 2: Map the Connector ID in Atlas Brain Once you have the correct ID, map it so Atlas Brain knows where to send enhancements: 1. Open Atlas Brain from your dashboard. 2. Go to Settings and select the SEO Enhancements (or Auto-Publishing) configuration. 3. Find the field labeled CMS Connector or Connector ID (Avatar → Settings → CMS Connectors). 4. Select the connector from the dropdown, or paste the CMS Connector ID you copied earlier. 5. Confirm that the mapped domain matches the website you want to optimize. 6. Click Save to apply the mapping. ✔️ Step 3: Verify the Mapping After saving, run a quick check to make sure enhancements will flow to the right place: - Use the Test Connection button if it is available. A successful test confirms the connector is reachable. - Push a single, low-risk enhancement (such as a meta description update) and confirm it appears on the correct site. - Review the enhancement or activity log to confirm the change was applied to the expected domain. 🌐 Managing Multiple Connectors If you run several websites, keep these best practices in mind: - Use clear connector names. Rename each connector to match its domain so it is easy to identify at a glance. - Map one connector per project. Each Atlas Brain configuration should point to a single connector to avoid cross-publishing. - Document your IDs. Maintain a simple table that lists each domain and its CMS Connector ID for quick reference during setup or audits. 🛠️ Troubleshooting I can't find a CMS Connector ID This usually means a connector has not been installed yet, or it is not fully connected. Return to Settings > CMS Connectors and confirm the connector status shows as Active. Reinstall or reconnect if needed. Enhancements are going to the wrong site Open your Atlas Brain settings and confirm the mapped Connector ID matches the intended domain. If two connectors have similar names, verify the linked domain rather than relying on the name alone. The connector shows as disconnected Reauthorize the connection from Settings > CMS Connectors. After reconnecting, re-verify that the Connector ID in Atlas Brain still matches the correct site. WordPress connector shows as Connected but enhancements are not being applied A known issue was identified where the WordPress CMS connector could display a Connected status even when the Search Atlas plugin was deactivated or otherwise failing. Do not rely solely on the status shown in Search Atlas—also verify in your WordPress admin panel that the Search Atlas plugin is active and running correctly. If the plugin is inactive, reactivate it and then recheck the connector status in Search Atlas. WordPress connector authentication shows as PENDING in Atlas Brain A known display issue was identified where Atlas Brain could show a WordPress plugin's authentication status as PENDING even though the plugin was successfully authenticated on the WordPress side. If you encounter this, disconnect and reconnect the plugin from Settings > CMS Connectors to force a status refresh. 🙋 Need More Help? If enhancements still do not appear after verifying your mapping, contact Search Atlas support and include the affected domain and its CMS Connector ID. This helps our team resolve the issue quickly.

🗺️ How to Locate Playbooks in Atlas Agent

This article helps you when you cannot find the Playbooks feature inside Atlas Agent. Because the Atlas Agent interface is actively evolving, the location of Playbooks may not always be immediately obvious, and the feature may be in a different place depending on your workspace configuration or account access level. 🛠️ How to Find Playbooks in Atlas Agent Playbooks are located on the Home page of the Atlas Agent interface, within the Recommended Playbooks section in the main content area. To navigate to them: 1. Open Atlas Agent from your Search Atlas dashboard. 2. In the left sidebar, click Home (the page titled Hi, CSM. What will we get done today?). 3. In the main content area, locate the Recommended Playbooks section, where you can view, create, and manage your existing playbooks. 4. If you do not see the Recommended Playbooks section, scroll down within the Home page in case it is below the visible area. 5. If Recommended Playbooks is still not visible after checking the full Home page, it is possible the feature is not yet enabled for your workspace or requires a different access tier. In that case, contact our support team with your workspace name and a description of what you see — our team can confirm availability and enable it for your account if applicable. ✅ What to Expect In most cases, navigating to Home in the left sidebar of Atlas Agent and locating the Recommended Playbooks section in the main content area will take you directly to the feature. If the section is missing entirely from your Home page, our support team will verify whether Playbooks is enabled for your account and assist you in getting access. Please have your workspace name ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔔 Set Up Search Atlas Coworker Slack Integration

🧭 Overview The Search Atlas Coworker Slack Integration lets agencies receive SEO task updates, OTTO notifications, and scheduled job alerts directly inside Slack. Once connected, your team can monitor activity across multiple client websites without switching between platforms. ✅ Before You Begin - You must have a Search Atlas account with at least one active project. - You need Slack workspace admin permissions — or ask your workspace admin to complete the authorization step. - Each client website should be set up as a separate project inside Search Atlas for best results. ⚙️ Step 1: Open Coworker Settings 1. Log in to Search Atlas. 2. In the left sidebar, click Coworker (URL: /coworker). 3. Click Refresh setup status to make sure your account is fully up to date before connecting. 🔗 Step 2: Connect Your Slack Workspace 1. Inside the Coworker panel, open Connectors to locate the Slack integration. 2. Click Enable to begin the Slack authorization flow. 3. You will be redirected to Slack. Sign in to the workspace you want to connect. 4. Review the permissions requested and click Allow to grant access. 5. Once authorized, you will be returned to Search Atlas and your Slack workspace will show as connected. Note: If Slack asks for admin authorization even though you are already the workspace admin, try refreshing your browser and clicking Enable again. If the prompt persists, have a workspace admin complete the authorization once — this is a known issue currently under review. 📁 Step 3: Assign Slack Channels to Client Projects For agencies managing multiple client websites, Search Atlas supports per-project Slack channels so each client's notifications stay organized and separate. 1. After connecting Slack, go back to the Coworker panel. 2. In the left sidebar, go to Coworker → Channels (Project Channels). 3. Use the synced projects dropdown to select a client project. 4. Assign a dedicated Slack channel to that project (create a new channel in Slack first if needed, e.g. #client-acme-seo). 5. Repeat this for each client project. This setup ensures that OTTO actions, SEO task completions, and job alerts for each client are delivered only to that client's designated channel. 🗓️ Step 4: Create Scheduled Jobs Scheduled jobs automate recurring SEO tasks and push status updates to Slack on your chosen schedule. 1. In the Coworker panel, click Create scheduled job. 2. Select the project (client website) the job applies to. 3. Choose the task type — for example, an OTTO audit run or an SEO task batch. 4. Set the frequency (daily, weekly, etc.) and confirm the linked Slack channel. 5. Save the job. Updates will now post to Slack automatically on schedule. 🔔 Step 5: Manage Notifications - To clear your notification feed, click Mark all as read inside the Coworker panel. - Individual notification preferences can be adjusted per project channel, so high-priority clients can receive more frequent alerts. - OTTO task completions and SEO recommendations will appear as Slack messages in the assigned channel, including a summary of actions taken. 💡 Tips for Agencies - Use a naming convention for Slack channels (e.g. #sa-clientname-seo) to keep dozens of client channels easy to find. - Add relevant team members to each client Slack channel so account managers receive the right updates. - Review scheduled jobs weekly to ensure tasks are running and no authorization issues have interrupted the connection. - If you need to reconnect Slack after a workspace change, click Refresh setup status in Coworker first, then re-enable the integration. 🛠️ Troubleshooting - Slack asks for admin authorization repeatedly: This is a known issue. Ensure you are logged into the correct Slack workspace as admin, then retry. If it continues, contact support via the chat widget below. - Notifications not appearing in a channel: Confirm the project is correctly mapped in Project Channels and that the Slack bot has been invited to that channel (type /invite @Search Atlas Coworker inside the channel). - Scheduled job not running: Click Refresh setup status in Coworker. If the job shows an error, delete it and recreate it with the same settings. 💬 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.

🏢 How to Add Multiple Client Sites as Active Projects in Agent Hub

📋 Overview Agent Hub is your central workspace for managing SEO automation across your client sites. If you manage multiple clients and need to add or activate several sites as active projects in Agent Hub, the number of projects you can activate at one time depends on your current subscription plan. Agencies or users who need to activate more client sites than their default plan allows will need to work with our support team to get the correct configuration applied to their account. 🚀 What This Process Involves Activating multiple client sites as projects in Agent Hub is a supported use case, particularly for agencies. The process involves confirming how many active project slots your plan includes, identifying which client sites need to be activated, and having our team apply the correct settings or plan changes to your account so all sites appear as active projects in your workspace. 🛠 What to Have Ready Before Reaching Out To help our team resolve this as quickly as possible, please gather the following information before contacting support: - Domain URLs of every client site you want to activate as a project - Total number of projects you need to have active simultaneously - Your current subscription plan (visible via the top-right avatar menu → Billing) - Your workspace or account name so our team can locate your account immediately - Any error messages or unexpected behavior you encountered while trying to add or activate projects, including exact wording and when it occurred - Screenshots of any error screens or the current project list in Agent Hub, if available Having all of the above ready will allow our team to review your account configuration, confirm your plan's project limits, and activate the correct sites without delay. 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.

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

🤖🧠 Search Atlas Brain Overview

The Search Atlas Brain is an AI operating system for digital marketing introduced by the Search Atlas team. It is designed to act as a coordination layer for everything that drives growth, transforming Search Atlas into a truly holistic, AI-driven marketing platform. Rather than functioning as another reporting dashboard, the Brain is built as an execution engine, one that fixes issues, improves performance, and runs complex workflows correctly at scale. This marks a fundamental shift in how SEO, PPC, content, authority, and local optimization are executed. 🎯 Core Purpose & Design Philosophy Most SEO and PPC tools stop at identifying problems. They generate reports, alerts, and suggestions, but execution is still manual. Search Atlas Brain was built to solve this gap. Instead of running reports, interpreting data, creating tasks, delegating work, and hoping execution matches strategy, the Brain executes continuously. This changes the unit of leverage: one person no longer manages tasks, one person manages systems. Agencies can now scale execution using AI rather than scaling headcount, allowing results to compound faster and more consistently. 🧠 An SEO-First Intelligence System (Not a General AI) Search Atlas Brain is not a general-purpose AI like ChatGPT. It is an SEO-first intelligence layer built entirely around your business data. The Brain maintains full context by connecting to your website and first-party data, Search Atlas keyword, backlink, and traffic indexes, SERPs and competitive landscapes, Google Search Console, Google Business Profile (GBP), Google Analytics 4 (GA4), and site audits and project data within Search Atlas. At its core is a semantic search engine built around your business, which crawls and indexes homepage and service pages, knowledge base and blog content, social media profiles, and local GBP data. Users can also upload additional context, including client onboarding transcripts, voice recordings, and PDFs and documentation. This allows the Brain to understand not just what to do, but why. The Brain is trained on over a decade of LinkGraph agency experience, including 5,000+ real-world case studies, proven execution patterns, and best practices refined across thousands of campaigns. This enables the system to fix sites, generate content, optimize ads, and refine performance with real operational intelligence. 🧩 Specialized Agents & Playbooks Search Atlas Brain is the central coordination layer, but execution is handled by specialized agents, each trained to do one thing exceptionally well. Agents manage execution across Onpage Optimization (Auto Technical SEO), Content Strategy & Generation (blogs, landing pages), Local SEO & GBP Optimization (citations, profile updates, heatmaps), Authority & Link Building (outreach, prospecting, cloud stacks), Paid Search / PPC (ad creation, optimization, deployment), and Client Reporting. Agents operate using Playbooks, standardized workflows that encode how an agency actually works. Playbooks define what “good” looks like, include control points for human approval, allow niche-specific behavior, and enable consistent execution at scale. For new users, Search Atlas provides pre-built playbooks based on workflows executed thousands of times. Advanced users can customize them to match internal SOPs, publishing cadence, risk tolerance, and quality standards. 🖥️ Agent-First UI & The New Home Screen The Search Atlas interface has been completely redesigned around the Brain, adopting an agent-first, action-led philosophy. The new home screen is accessed via Left sidebar → Home (page title: "Hi, CSM. What will we get done today?"; tab: Agent Hub). Users familiar with Classic Mode can access it via the Agent Hub toggle in the top-left corner. It serves as the new homepage for Search Atlas, eliminates fragmented workflows and tool-hopping, and encourages immediate action instead of passive reporting. The Hub shows scrollable project tiles for all sites. Each tile displays an Auto Score, traffic snapshots, active local strategies, ad campaign structure and performance, and four-pillar grades: Authority, Content, Technical SEO, and User & behavior signals. For users who need traditional metrics, the Hub also provides quick access to Portfolio Summary views and reports. 💬 Chat-Driven Interaction & Prompting The core interaction model of Search Atlas Brain is chat-driven execution. Users interact via a single prompt box, with no prompt engineering required. The system ingests simple prompts, partial instructions, and high-level ideas. A built-in dictation feature lets users speak strategy into existence. Before execution, users select the project and the agent brain (Auto, Authority, Local, etc.). The system retains context across chats, allowing agents to apply learned preferences over time. 🔍 Transparency, QA & Control Every interaction is fully transparent. The agent exposes how it translates natural language into a formal work order, acts as a built-in quality assurance layer, and challenges unsafe or low-quality actions before deployment. Execution control features include Concurrent Execution (run multiple agents side by side across projects), Choose Your Own Adventure (for complex tasks, agents propose phased plans and ask for approval), Risk Assessment & Safety (sensitive changes, such as GBP name or phone updates, are flagged as high-risk and require confirmation), Fulfillment Orchestration (the agent deploys changes directly — titles, content, GBP updates, links), and a Playbook Review Interface (users can inspect playbooks to see what will happen, where approvals are required, and how much autonomy is involved). ⚡ Speed, Scale & Continuous Execution What once took days or weeks, technical audits, fixes, optimization, can now be executed in minutes. Users can run authority building while fixing technical SEO, generate content while optimizing local profiles, and scale execution across multiple projects simultaneously. The platform is designed around projects and continuous execution, eliminating fragmentation and ensuring users always know what’s running and what’s next. 🤖 How Quota Consumption Works with Agents As of mid-2026, agents now draw from their own dedicated AI Agent credit allowance in addition to the quota consumed by the underlying product they trigger (for example, the Content product for article creation, or Site Audit / OTTO for a site audit). Search Atlas meters agent usage against this allowance, and once it is fully used, further agent requests are blocked until the allowance renews or is increased. If you are unexpectedly seeing an agent-credit error while other product quotas still show available balance, this is expected behavior under the current metering system, not a bug. 🚀 The Agentic Future of Search Atlas Search Atlas Brain represents a fundamental shift: from dashboards to systems, from manual work to continuous execution, from task management to orchestration. The Brain continues to evolve with multimodal capabilities, expanded knowledge base access, deeper playbook customization, and ongoing agent improvements based on real usage. Search Atlas Brain enables teams to operate systems, not tasks. By combining deep contextual intelligence, specialized agents, transparent execution, and an agent-first UI, it allows agencies and marketers to scale results faster, without scaling headcount. 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.

Connect Search Atlas Coworker to Slack

What the "Admin Needs to Set Up Atlas" Message Means If you open the Search Atlas Coworker app in Slack and see a message that an admin needs to set it up, the app has not been installed and authenticated for your Slack workspace yet. You do not need an invitation from the Search Atlas dashboard to use it. Step 1: Install the App for Your Workspace (Admin, Once) A Slack workspace admin (or whoever installs apps in your workspace) installs and authenticates the Search Atlas Coworker app once for the whole workspace. Until that is done, nobody in the workspace can use it. For the exact installation steps, see the Search Atlas Coworker installation guide. Step 2: Sign In With Your Own Search Atlas Account (Every User) After the workspace is set up, each person connects their own Search Atlas account: 1. In the main Slack message box, type /atlas-login. 2. Click the Sign in to Search Atlas button that appears (only you can see it). 3. Sign in with your Search Atlas account. No admin invitation is needed for this step. Search Atlas Coworker Slack Commands Type these in the main Slack message box, not as a thread reply: - /atlas-login — shows a Sign in to Search Atlas button so you can sign in or switch accounts. - /atlas-status — shows whether Atlas is set up for your workspace and whether you are signed in, with a button to sign in or reconnect if needed. - /atlas-logout — signs you out of Search Atlas and disconnects your personal connected tools. - /atlas-new-session — starts a fresh conversation in the current channel or thread, clearing what Atlas remembers from it. - /atlas-help — lists the available commands. Common Mistakes to Avoid - Typing a command inside a thread. Slack only runs slash commands from the main message box. - Reinstalling the app to fix a sign-in problem. If the workspace is already set up, run /atlas-login again instead. - Waiting for a dashboard invite. Once the workspace is set up, /atlas-login is all you need. 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.

🤖 Getting Started with Search Atlas Coworker in Slack

Atlas is Search Atlas's AI Search Atlas Coworker that lives right inside Slack. Talk to it in plain language — from "what's new in AI this week?" to "run a full SEO audit on my site" — and it researches, analyzes, builds reports, and (with your approval) takes action across Search Atlas and the apps you already use. Think of it as a teammate you message in Slack. 🧩 What Atlas Can Do 1. Answer questions and research anything, including the live web. 2. Go deep on SEO and marketing using the full Search Atlas toolset. 3. Work across your connected apps — CRM, analytics, ads, code, CMS, and more. 4. Build reports and files (HTML or PDF) and hand you a download link. 5. Run tasks on a schedule with Routines. 6. Read images you share, like a screenshot of a page. 🚀 Install Atlas in Slack 1. Add Atlas to your workspace. A Slack admin authorizes the Atlas app for your workspace. For the exact steps, see the Search Atlas Coworker installation guide. 2. Connect your Search Atlas account. The first time you talk to Atlas, sign in to link your Search Atlas account — this powers the SEO and marketing tools and tells Atlas who you are. Use /atlas-login any time you need to sign in or switch accounts. 3. Start talking. Open a direct message with Atlas, or invite it to a channel and @mention it. 💡 Tip: you can get something useful back in your very first message — no setup script required. 🔗 Connect Your Apps Atlas works with the tools you already use. To connect an app: 1. Ask Atlas in plain language, e.g. "connect my HubSpot", or open the Atlas app's Home tab in Slack. 2. Atlas replies with a secure connect button. Click it. 3. Sign in and approve access on the app's own standard authorization screen. 4. You're returned to Slack, and Atlas confirms the connection. A few things to know: - Connect one app at a time. If you need several, start them one by one. - Each app is authorized separately — connect only what you need, and you can disconnect any app at any time. - Connections can be Personal (only you can use them) or, if you're an admin, Shared so one connection works for everyone in the workspace. Supported Connectors | Category | Connectors | | --- | --- | | Advertising | Meta Ads · Google Ads · TikTok Ads · OpenAI Ads (advertise in ChatGPT) | | SEO | Google Search Console | | Analytics | Google Analytics (GA4) | | Communication | Slack | | Developer Tools | GitLab · GitLab (Self-Managed) · GitHub · Vercel | | Web / CMS | Webflow · WordPress (self-hosted) · WordPress.com | | CRM | HubSpot | | Custom | Custom MCP server (connect your own remote MCP server) | Note: Webflow and WordPress.com connect via managed OAuth. For apps not listed above (like Notion, ClickUp, or Asana), a Custom MCP server connection lets you point Atlas at your own MCP endpoint. SearchAtlas's own tools — Google Business Profile, OTTO, content generation, rank tracking, Website Studio, and more — are built-in capabilities and work without a separate connection step. 🔐 Access and Permissions — What Atlas Needs - A Search Atlas account — powers the SEO/marketing tools and identifies you. - The Atlas app installed in your Slack workspace (done once by an admin). - Per-app access you grant yourself. For each connected app you approve access on that app's standard sign-in screen. You choose what to allow, and you can disconnect any app at any time. - Atlas stays in your lane. It only works in channels you're a member of, and it only uses your own connected accounts — it can't see a teammate's calendar or data unless they connect their own (or an admin shares a connection). - Actions and approval. Atlas can act in your connected apps. Admins control whether actions run automatically or require per-action approval — configured in the /coworker hub, per connector and per tool. You can set any connection or specific action to require your approval before it runs. ⚙️ Check and Manage Your Settings You manage Atlas with a few simple commands, typed directly in the Slack message box: | Command | What it does | When to use it | | --- | --- | --- | | /atlas-login | Sign in or switch your Search Atlas account | First-time setup, switching accounts, or after a session expires | | /atlas-logout | Sign out of Search Atlas and disconnect your personal connected tools | Changing accounts | | /atlas-status | Show whether Atlas is set up and whether you are signed in, with a button to sign in or reconnect | Atlas isn't responding as expected or you're unsure you're signed in | | /atlas-new-session | Start a fresh conversation | The conversation feels stale or off-track | | /atlas-help | Show what Atlas can do | You want a reminder of Atlas's capabilities | You can also just ask in plain language — for example, "what are my connections?" to see what's connected, or "pause all routines" to pause your scheduled tasks. Routines can also be managed from the Automations area of your Search Atlas dashboard. 🔄 Routines — Scheduled Automations A Routine is a task you ask Atlas to run on a schedule. Here's how to set one up: 1. Describe what you want and when, in plain language. For example: - "Every morning at 9am, summarize what's new in AI and post it here." - "Each day, give me a rank-tracking update for my top keywords." - "Every hour, post our Google Ads spend and conversions to this channel." 2. Review and confirm. Atlas shows you a summary of the Routine — the task, the schedule, and where it will post results — before saving it, so you can check everything first. 3. Atlas runs it on schedule and posts the result where you chose — the current channel or a DM — automatically, even when you're offline. 4. Manage or pause any time by asking Atlas (for example, "pause all routines"), or from the Automations area of your Search Atlas dashboard. 📈 Capabilities at a Glance SEO & marketing (SearchAtlas depth): site audits and health scores, OTTO on-page automation, keyword research and rank tracking, content generation and topical maps, Google Business Profile, Google Ads and Meta Ads, digital PR and press releases, link building, local SEO heatmaps, AI-search (LLM) visibility, Search Console and analytics reporting, and building or editing landing pages with Website Studio. Everyday work: answer questions, research the live web, read screenshots you share, draft and generate documents, build HTML/PDF reports with a download link, and — with your approval — take actions in your connected apps. Memory: Atlas remembers context within a channel (shared with that channel's members) and keeps your private DMs and threads to you. ✅ Tips for Best Results - One goal per thread keeps answers sharp. - Talk like you would to a colleague — plain language works. - You're always in control — admins can configure approval requirements per connector and tool. Need a hand? You can reach us through live chat right here. If you'd like to talk to a person, just type Human teammate in the chat and we'll connect you with one of our team.

🔗 Connecting Your Search Atlas Account to Search Atlas Coworker

Before Search Atlas Coworker can pull your SEO data or take actions in Search Atlas, your account needs to be linked. This is a one-time step per user. How the Connection Works The first time you ask Search Atlas Coworker a Search Atlas question (for example, "What are my top ranking keywords this week?"), it will detect that your account is not yet connected and walk you through the authorization flow directly in Slack. Step-by-Step: Linking Your Account 1. Open a DM with the Search Atlas Coworker bot in Slack (or @mention it in a channel). 2. Send any Search Atlas question, or type /atlas-login in the main Slack message box. 3. Search Atlas Coworker will reply with a Sign in to Search Atlas button. Click it. 4. You will be redirected to Search Atlas. Log in if prompted, then click Authorize. 5. Return to Slack. Search Atlas Coworker will confirm the connection and answer your original question. Verifying Your Connection You can confirm your account is linked at any time by typing /atlas-status in the main Slack message box. Search Atlas Coworker will show whether you are signed in and, if not, give you a button to sign in or reconnect. Reconnecting After a Session Expiry If your OAuth session expires, Search Atlas Coworker will prompt you to re-authorize the next time you send a Search Atlas request. Follow the same authorization steps above. Your previous settings and routines are not affected. Disconnecting Your Account To remove the connection, ask Search Atlas Coworker: "Disconnect my Search Atlas account." You can also revoke access directly from your Search Atlas account settings under Connected Apps.