Integrations, Tools & MCP

🔧 Fix Coworker Slack Visibility and Switch Credits

🤖 Edit llms.txt and Integrate Atlas Agent

🗺️ Overview When you enable the Serve llms.txt via a virtual route option in the Search Atlas WordPress plugin, WordPress does not create a physical file on your server. Instead, it serves the content dynamically. This means you cannot edit the file through your hosting file manager or FTP — all edits must be made inside the plugin itself or through Search Atlas. ⚙️ Where to Edit llms.txt in the WordPress Plugin 1. Log in to your WordPress admin dashboard. 2. In the left sidebar, navigate to Search Atlas and open the plugin settings. 3. Select the LLMs.txt tab (or section, depending on your plugin version). 4. You will see a text editor where the current llms.txt content is displayed. 5. Make your changes directly in this editor. 6. Click Save Settings to apply your edits. Once saved, your updated content will be served automatically at yourdomain.com/llms.txt. You do not need to upload any files manually. 🤖 How to Generate a Detailed llms.txt with Atlas Agent Atlas Agent can generate a richer, more structured llms.txt file tailored to your site's content and SEO context. Follow these steps to create and retrieve that file. 1. Log in to your Search Atlas account at app.searchatlas.com. 2. From the left sidebar, click Home. 3. Click Launch Atlas Agent to open the agent interface. 4. Prompt Atlas Agent to generate an llms.txt file for your domain. For example: "Generate a detailed llms.txt file for [yourdomain.com] including all key pages and content descriptions." 5. Review the output in the agent's response panel. 6. Copy the full generated content. 🔗 Integrating the Atlas Agent Output into Your WordPress Plugin 1. Return to your WordPress admin dashboard. 2. Navigate to Search Atlas → Settings → LLMs.txt. 3. Select all existing content in the text editor and delete it. 4. Paste the content copied from Atlas Agent into the editor. 5. Click Save Settings. 6. Visit yourdomain.com/llms.txt in your browser to confirm the updated content is live. Important: Always verify the file is rendering correctly after saving. If the content reverts to default after saving, this is a known issue that was resolved in plugin version 2.6.3. Make sure your plugin is updated to at least that version. ✅ Keeping Your Plugin Up to Date Some llms.txt editing and publishing issues were tied to specific plugin versions. To avoid problems: - Keep the Search Atlas WordPress plugin updated to the latest version. - After every plugin update, re-check your llms.txt content to confirm it has not reverted. - If you publish llms.txt changes through Atlas Agent's conversational flow, verify the live file matches your intended content — earlier versions had a bug where edits persisted in the editor but the original unedited version was published to WordPress. 🛠️ Troubleshooting Common Issues - llms.txt content reverts after saving: Update the plugin to version 2.6.3 or later, then re-paste and save your content. - Changes from Atlas Agent do not appear on the live site: Manually copy the Atlas Agent output and paste it into the plugin editor, then save. Do not rely solely on the automated publish flow if you notice discrepancies. - File not accessible at yourdomain.com/llms.txt: Confirm that the Serve llms.txt via a virtual route toggle is enabled and that your permalink settings in WordPress are not set to Plain (go to Settings → Permalinks and select any option other than Plain, then save). 💬 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 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.

🛠️ Troubleshooting Search Atlas Coworker in Slack

If Atlas isn't behaving as expected, this guide walks through the most common issues and how to fix them. Work through the steps for your situation — and if you're still stuck, you can reach a person any time (see the last section). 💬 Atlas Isn't Responding or Posting in a Channel 1. Make sure it's a regular channel. Atlas can't post in Slack Connect or externally-shared channels — try a regular public or private channel, or a direct message instead. 2. Invite Atlas to the channel by typing /invite @Search Atlas Coworker and selecting the bot from Slack's autocomplete. 3. Confirm you're a member of the channel — Atlas only works in channels you belong to. 4. To isolate the issue, try the same request in a direct message with Atlas. If it works there, the problem is specific to the channel. 🔗 Problems Connecting or Using an App You connected an app but Atlas says it isn't connected. Ask Atlas again — the connection sometimes needs a moment to register. If it persists, ask Atlas to reconnect the app in plain language (for example, "reconnect my HubSpot") or manage the connection from the Atlas app's Home tab in Slack. 1. The connect link shows a "pipedream.com" address. This is expected and safe — it's the secure sign-in step. Go ahead and approve the connection. 2. You're connecting several apps. Connect them one at a time rather than asking for several in a single message. 3. All your connected apps suddenly stop working (but Search Atlas tools still work). This is usually a temporary connection-service hiccup. Wait 5–10 minutes and try again. ✅ Atlas Isn't Completing an Action (Calendar Event, Publishing, etc.) 1. If your workspace is configured to require approval, Atlas shows an approval card before completing the action. If you expected a confirmation prompt but didn't see one, check Workspace Settings → Permissions → Run connector actions without asking in the Search Atlas Coworker dashboard to verify approval is turned on for that connector or tool. 2. After it runs, verify the result in the app itself (for example, check your calendar or your CMS) to confirm it went through. 3. If it still doesn't complete, try the request again. 4. Publishing to WordPress: both WordPress.com and self-hosted WordPress are supported. Make sure the connection is authorized (for self-hosted, this may use an application password). 🔄 A Routine Ran Multiple Times or Didn't Run 1. Ask Atlas to "pause all routines." 2. Delete the affected routine. 3. Recreate the routine you want, describing the task and schedule again. 💡 Atlas's Answers or Behavior Seem Off 1. An action worked once and failed the next time. Try it again — many of these are temporary. If it keeps failing for the same action, reach out to us. 2. Atlas says Slack isn't connected when you ask it to summarize a channel. Rephrase the request explicitly, for example: "Use my Slack connection to summarize #channel-name." 3. A very long answer looks garbled. Ask Atlas for a shorter version, e.g. "Can you give me a shorter version?" 4. Atlas refers to the wrong person. Make sure you've signed in with /atlas-login. 5. A button's label looks cut off. You can type your choice directly in the message box instead of clicking the button — Atlas accepts typed responses. ⏳ Atlas Seems Slow or Unresponsive While Atlas is working, it shows an hourglass on its own message. Complex requests — like a full site audit — can take up to around 90 seconds, so give it a moment. If nothing comes back after a few minutes, try the request again. ⌨️ A Slash Command Shows as Plain Text and Nothing Happens Type the command directly in the main Slack message box, not as a reply inside a thread. If it still shows as plain text, retype it in the Slack app. 💬 Still Need Help? 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.

Atlas Brain Looping and WordPress Plugin 505 Error

Overview Some users have experienced two related issues: Atlas Brain AI campaigns entering a loop and applying incorrect fixes instead of resolving the flagged problem, and the Search Atlas WordPress plugin returning a 505 error when attempting to authenticate or sync. This article explains what these issues mean and what you can do when you encounter them. What These Issues Look Like - Atlas Brain looping: The AI campaign fixer runs continuously and applies the wrong fix rather than correctly resolving the issue identified in your campaign. - WordPress plugin 505 error: When linking the Search Atlas plugin to your WordPress site, the connection fails with a 505 server error, preventing authentication and data sync. What to Do Both of these issues — Atlas Brain looping in an AI campaign and the WordPress plugin returning a 505 sync error — require investigation on the Search Atlas side to identify and apply the correct fix for your account. There are no self-service steps that reliably resolve either issue without support involvement. If you are experiencing either or both of these issues, please contact our support team right away so we can look into the root cause and resolve it for you. You can reach us by clicking the chat icon in your Search Atlas dashboard. Please include the following information when you reach out: - A description of which issue you are experiencing (Atlas Brain looping, plugin 505 error, or both). - The name of the affected campaign or the WordPress site URL. - Any error messages or screenshots you are able to capture.