Home 🚀 Getting Started

🚀 Getting Started

Camilo Aponte
By Camilo Aponte
• 30 articles

📘 Connect MCP in Claude (Desktop & Browser)

The Search Atlas MCP can be connected through Claude's Custom Connector experience. Both Claude Desktop and Claude.ai use the same MCP endpoint and authentication flow. This article walks through the connection process and explains what to expect during setup. ⚙️ Step-by-Step: Connect MCP in Claude ⚙️ Step-by-Step: Connect MCP in Claude Step 1 Open Customize in Claude. Step 2 Select Connectors. Step 3 Click Add connector. Step 4 Choose Add custom connector. Step 5 Name the connector Search Atlas. Step 6 Paste the Search Atlas MCP server URL: https://mcp.searchatlas.com/mcp/ Step 7 Click Add. Step 8 Click Connect. Step 9 Claude opens your Search Atlas account so you can grant access. Step 10 Click Authorize. Step 11 After authorization, the connector is connected and ready to use in Claude. Step 12 To verify the connection, open a Claude chat and ask: "Are you connected to my Search Atlas account?" 🔐 What Happens After You Connect Once connected, Search Atlas tools become available directly inside Claude chats. You can ask Claude to confirm the connection by opening a chat and asking, "Are you connected to my Search Atlas account?" After the connection is confirmed, you can start using your Search Atlas account through Claude. From then on, the client holds and refreshes the credential automatically. That is the supported OAuth path for customer-facing scenarios. Those actions continue to follow the same account authentication, plan entitlements, and quota rules used in the Search Atlas app. ⚠️ Troubleshooting If the connection does not complete, start with these checks from the source: Check 1 — Are you already logged into Search Atlas? If not, sign in to dashboard.searchatlas.com first, then retry the connection flow. Check 2 — Does your plan include MCP access? If MCP is not included in the plan, the OAuth flow may complete but tool calls will fail with an authorization error. Check 3 — Is the session stale or expired? Disconnect the MCP in Claude and reconnect to trigger a fresh login. Oce you complete the Claude connection flow, Claude becomes a conversational interface for the Search Atlas tools available in your account. You describe the outcome, and Claude can execute the corresponding Search Atlas actions through the MCP using your existing permissions, entitlements, and quotas.

Last updated on Oct 26, 2026

📘 How to Connect MCP (Overview)

There is a single canonical connection target and a single authentication model for the Search Atlas MCP. Everything else — which client, which plan, or which namespace — is a variation on these two basics. This article explains the connection endpoint, the recommended authentication method, and what to check if the connection fails. 🌐 Connection Endpoint The public MCP endpoint serves the full catalog of Search Atlas tools: https://mcp.searchatlas.com/mcp/ The server also exposes per-product namespaces, for example /mcp/otto/ and /mcp/local-seo-gbp/, but the root endpoint aggregates all namespaces and is what customers should use unless there is a specific reason to scope access. Common tools such as brand vault, knowledge graph, and billing are available in every namespace. 🔐 Authentication The MCP server validates credentials issued by the main Search Atlas platform. It does not issue its own credentials. OAuth is the recommended and supported path for all customer-facing scenarios. The server also accepts a Search Atlas API key via the X-API-Key header, but that path exists for scripts and server-to-server integrations where an interactive browser login is not possible. It is not recommended for regular customer use. If a customer asks which to use, steer them to OAuth. ⚙️ Connect MCP 1. Use the main endpoint: https://mcp.searchatlas.com/mcp/ 2. Add that endpoint in your MCP-compatible client, such as Claude Desktop, Claude.ai, Cursor, or ChatGPT connectors. 3. When the client starts the connection flow, complete the one-time Search Atlas login in the browser. This is the OAuth flow recommended and supported for customer-facing scenarios. 4. After you sign in, the client holds and refreshes the credential automatically. From that point forward, the MCP connection remains saved in the client. ⚠️ If the Connection Fails The three most common causes, in order: 1. You are not already logged into Search Atlas when the browser window opens. Sign in to dashboard.searchatlas.com first, then try again. 2. Your plan does not include MCP access. Check your plan entitlements — MCP access is controlled at the plan level. 3. Your session is stale or expired. Disconnect the MCP in your client and reconnect to trigger a fresh login. To connect MCP successfully, use the root Search Atlas endpoint and the OAuth login flow. Once connected, your client can access the Search Atlas tool catalog available under your account, subject to your plan entitlements and quota rules. 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.

Last updated on Oct 26, 2026

🔌 Connecting Search Atlas MCP to ChatGPT

🤖 What Is the Search Atlas MCP? The Search Atlas MCP (Model Context Protocol) server lets AI assistants connect directly to your Search Atlas data. Once connected, you can ask an AI tool to pull SEO insights, run research, and work with your project data using natural language. MCP is an open standard, so any AI client that supports remote MCP servers can connect to Search Atlas — for example, the same server can also be connected to Claude, not just ChatGPT. The current server is SearchAtlas MCP v2, which is published to public MCP registries, and it authenticates using the OAuth 2.1 standard. OAuth 2.1 support is fully live for both the Claude and ChatGPT listings, so connecting is done by signing in and approving access. ✅ ChatGPT Compatibility Requirements Before you start, it is important to know which ChatGPT plans support remote MCP connectors. A common question we hear is whether the connection works on ChatGPT Plus — and the answer depends on your plan. Connector support is offered through ChatGPT's Developer Mode and custom connector features, which are not available on every plan. - ChatGPT Plus: Remote MCP connector support on the standard Plus plan is limited and may not be available in your region or build. Many connection failures happen because the account plan does not expose the custom connector option. - ChatGPT Pro, Team, Enterprise, and Edu: These plans are far more likely to include the connector and Developer Mode settings needed to add a remote MCP server. - Free plan: Custom MCP connectors are not supported. If you do not see an option to add a custom connector in your ChatGPT settings, your current plan does not support it. In that case, the issue is on the ChatGPT side, not with Search Atlas. 🔗 How to Connect the MCP Server Follow these steps to add Search Atlas as a connector in a supported ChatGPT plan. Because the Search Atlas MCP server uses OAuth 2.1, authenticating typically means signing in and approving access rather than only pasting a static key. 1. In Search Atlas, open your account settings and locate the MCP server URL and your access token or API key. 2. In ChatGPT, open Settings and find the Connectors (or Developer Mode) section. 3. Select Add custom connector or Add MCP server. 4. Paste the Search Atlas MCP server URL exactly as shown, with no extra spaces. 5. Complete authentication when prompted. With OAuth 2.1, you may be redirected to sign in to Search Atlas and authorize access; if a token is requested instead, enter your access token. 6. Save the connector and wait for ChatGPT to confirm the connection. 7. Start a new chat and confirm the Search Atlas connector appears as an available tool. 🛠️ Troubleshooting Connection Problems If the connection fails, work through these common causes in order. - Unsupported plan: Confirm your ChatGPT plan includes custom connectors. If the option is missing entirely, upgrade to a supported plan. - Incorrect server URL: Copy the MCP URL directly from Search Atlas. A missing character or trailing space will cause the connection to fail. - Invalid or expired token: Generate a fresh access token in Search Atlas and paste it again. Tokens can expire or be revoked. - Authentication errors: Make sure you are logged into the correct Search Atlas account that has access to the data you want to use. Because authentication uses OAuth 2.1, re-running the sign-in and authorization step can clear stale sessions. - Browser or cache issues: Try connecting from a different browser, clear your cache, or disable extensions that may block requests. - Feature still rolling out: Connector support is released gradually. The SearchAtlas MCP v2 server is already published to the primary public MCP registry, but the effort to submit it across every other public MCP directory is still in progress, so it may not appear in every directory search yet — adding the MCP server URL manually always works regardless of whether the server shows up in a directory listing. 💡 Tips for a Stable Connection - Keep your access token private and treat it like a password. - Reconnect after changing your password or regenerating your token. - Use clear, specific prompts so ChatGPT calls the right Search Atlas tools. - Re-test the connector after major ChatGPT or browser updates. 🆘 Still Need Help? If you have confirmed your plan supports custom connectors and the connection still fails, our team can help review your setup. If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.

Last updated on Oct 26, 2026

🔌 Frequently Asked Questions — Integrations & Installation

Search Atlas connects to your CMS, website platforms, Google tools, and AI assistants. This article covers the most common questions about setting up and troubleshooting integrations. How do I install the MetaSync (OTTO) plugin on WordPress? 1. 1. In your WordPress admin, go to Plugins → Add New → Upload Plugin and upload the MetaSync plugin .zip provided by Search Atlas 2. 2. Install and Activate the plugin 3. 3. Click the Search Atlas logo in the WordPress sidebar → Settings → Connect to Search Atlas 4. 4. Log in with your Search Atlas credentials in the popup 5. 5. The plugin connects automatically — OTTO changes now deploy via the plugin ⚠️ If you already have the OTTO JavaScript pixel manually added to your theme, remove it after activating the plugin to avoid a duplicate installation state. Why does the MetaSync WordPress plugin show a login page after a successful sync? This typically means the OAuth session between the plugin and Search Atlas expired or was interrupted. Go to the MetaSync plugin settings in WordPress, disconnect the account, and reconnect. If the login page keeps appearing after reconnecting, try deactivating and reactivating the plugin, then reconnecting. The MetaSync plugin is causing my Elementor editor to hang. What do I do? A conflict between MetaSync and Elementor's editor can cause the editor to freeze on load. ⚠️ As a workaround: temporarily deactivate the MetaSync plugin when using the Elementor visual editor, then reactivate it when done editing. This conflict is a known issue being tracked by the engineering team. My page titles aren't deploying even though the MetaSync plugin is active. Why? If you have both the WordPress MetaSync plugin AND the Cloudflare Worker active on the same OTTO project, they may conflict. Go to OTTO SEO → Installation Guide and choose one method — either the plugin or the Cloudflare Worker. ⚠️ Disable whichever you want to stop using. Having both active simultaneously can cause either to behave unpredictably. Can I install the OTTO pixel on Squarespace, Wix, Shopify, or GoDaddy? Yes. The OTTO JavaScript pixel can be added to any CMS that allows custom code in the page header: - Squarespace: Settings → Advanced → Code Injection → Header - Wix: Settings → Custom Code → Head - Shopify: Online Store → Themes → Edit code → theme.liquid - GoDaddy: Website Settings → Advanced → Header scripts 💡 For platforms that don't support header code injection, use the Cloudflare Worker method instead. How do I connect Google Search Console to Search Atlas? Go to Settings → Integrations → Google Search Console and follow the OAuth flow. Select the GSC property (domain or URL-prefix) that matches your site. ✅ Once connected, GSC data is available across OTTO, Report Builder, and the keyword tools. How do I connect my Google Business Profile? Go to GBP Galactic → GBP Projects → Connect GBP Account. Sign in with the Google account that owns or manages the GBP locations. After authorizing, select the locations you want to manage. ⚠️ Note: view-only access is not sufficient — you need owner or manager permissions on the Google account. How do I connect the Search Atlas MCP server to Claude Desktop? 1. 1. Get your MCP API key from Avatar Menu (👤) → Settings → API Keys 2. 2. Open the Claude Desktop config file: - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - Windows: %APPDATA%\Claude\claude_desktop_config.json 1. 3. Add: "searchatlas": { "url": "https://mcp.searchatlas.com/mcp/", "headers": { "x-api-key": "your-key" } } 2. 4. Restart Claude Desktop fully 3. 5. Test by typing "List my OTTO projects" Can I connect the Search Atlas MCP to ChatGPT? No. ChatGPT uses OpenAI's own plugin/tool system, which is architecturally different from MCP. The Search Atlas MCP server does not implement OpenAI's plugin protocol. Supported AI tools: Claude Desktop, Claude Code (CLI), and Cursor. What CMS platforms can Content Genius publish to? Content Genius can publish articles directly to: WordPress (via MetaSync plugin), Website Studio, Webflow, Shopify, and Squarespace. ✅ Connect CMS destinations at Settings → CMS Connectors. How do I connect Webflow, Shopify, or other CMS platforms to Content Genius? Go to Settings → CMS Connectors and click Add Connector. Select your CMS type and follow the OAuth or API key connection flow. Once connected, the CMS appears as a publishing destination in Content Genius. How do I install the OTTO pixel on Website Studio? Go to your Website Studio Project Settings → Configuration → Header Embeddings. Paste your OTTO pixel script and save. The pixel is injected into every page's on the next publish. What does "OTTO Not Found" mean even though the Cloudflare Worker is deployed? The Cloudflare Worker is live but the UUID in the worker script may not match your OTTO project. Re-copy the exact script from OTTO SEO → Installation Guide and redeploy the worker with the new script. ⚠️ If the UUID matches but the banner persists, contact support with your domain and OTTO project ID. How do I set up GoHighLevel (GHL) white-label integration? GHL integration is provisioned through the GoHighLevel marketplace. When a GHL sub-location is created, a Search Atlas child account is created automatically under the GHL master account. Sub-accounts inherit white-label branding from the GHL parent. If GHL sub-accounts aren't appearing in your Agency Hub, check your GHL marketplace connection status and contact support. The MetaSync plugin is causing my Elementor editor to hang on loading. What should I do? A conflict between MetaSync and Elementor can cause the editor to hang indefinitely. Steps: (1) Temporarily deactivate MetaSync and test whether Elementor loads — if it does, the conflict is confirmed. (2) Ensure both MetaSync and Elementor are on their latest versions. (3) Contact Search Atlas support with your WordPress version, MetaSync version, and Elementor version — they can advise on a specific workaround. ⚠️ Do not delete MetaSync — only deactivate it while troubleshooting so your OTTO connection and data are preserved. The MetaSync WordPress plugin shows a login page even though I already connected my account. What's happening? The MetaSync authentication session expired or was cleared — this typically happens after a WordPress cache flush, a session-clearing security plugin, or a hosting-level cache reset. To re-authenticate: go to your WordPress dashboard → MetaSync plugin settings → click the Search Atlas logo → re-enter your credentials or click the re-authenticate button. ✅ If the login page reappears after every session, your WordPress site may be clearing authentication cookies — add an exception for the MetaSync auth cookie in your caching plugin settings. My page titles are not deploying — I have both the WordPress plugin and Cloudflare Worker active at the same time. Why? Running both MetaSync and the Cloudflare Worker creates a dual-install conflict — both systems try to modify the same HTML elements and can override each other. ⚠️ Use only one deployment method at a time: - MetaSync plugin only: for WordPress-managed deployment - Cloudflare Worker only: recommended when SEO crawlability by Googlebot is the priority To resolve: go to OTTO SEO → Installation Guide, choose your preferred method, and deactivate the other. If using the Cloudflare Worker, disconnect MetaSync from your SA account and deactivate it in WordPress. If using MetaSync, remove the Worker from your Cloudflare dashboard.

Last updated on Oct 26, 2026

Connecting Your Meta Account

🔗 Why Connecting Your Meta Account Matters Connecting a Meta Business ad account is the first and most important step in Meta Ads. Until your account is connected, Launchpad and Analytics remain locked and unavailable. Once connected, Meta Ads can build campaigns, generate creatives, publish ads, and pull in performance data — all in one place. 📍 Where to Find the Connect Control At the very top of Meta Ads, you'll see a Meta Ad Account control. This is the starting point for linking your account. 1. Open Ads → Meta Ads (Which ad platform do you want to see first?) from Search Atlas. 2. Locate the Meta Ad Account control at the top of the page. 3. Click it and follow the prompts to connect your Meta Business ad account. Once the connection is complete, Launchpad and Analytics will unlock automatically and your data will begin loading. ✅ What Unlocks After Connecting - Launchpad — build and publish Meta ad campaigns from brand to live ads. - Analytics — view campaign performance, insights, and reporting data pulled directly from your Meta ad account. 🔧 Troubleshooting Common Issues 🔒 Launchpad or Analytics Appears Locked or Empty This almost always means a Meta ad account hasn't been connected yet. Go to the Meta Ad Account control at the top of Meta Ads and complete the connection. 📊 Numbers Don't Match Meta Ads Manager If you notice a difference between the figures shown in Meta Ads and those in Meta Ads Manager, this is temporary. It typically happens when Meta is rate-limiting data requests. The numbers will reconcile automatically as the sync catches up — no action is needed on your end. ⏳ Insights Are Still Loading After Connecting Data loads in phases after you connect your account. If insights haven't appeared yet, give it a few minutes and then refresh the page. This is expected behavior and not a sign that something has gone wrong. 💬 Still Need Help? If you're running into an issue that isn't covered above, we're happy to help. Use the live chat in Search Atlas and type "human teammate" to connect with a real person on our support team.

Last updated on Oct 26, 2026

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

Last updated on Oct 26, 2026

🔌 Install and Set Up the WordPress Sync Plugin

🔍 Overview Search Atlas allows you to publish and sync content directly to your WordPress website using an official plugin. The plugin is not listed in the public WordPress plugin directory, so it must be installed manually. This article walks you through the correct installation and setup process. 📦 Step 1: Download the Plugin The Search Atlas WordPress sync plugin is provided directly through the platform — you will not find it by searching the WordPress plugin marketplace. 1. Log in to your Search Atlas account. 2. Navigate to Content in the left sidebar. 3. Open any content tool, such as SEO Content Assistant or AI Content Templates. 4. Look for the WordPress integration or Publish to WordPress option within the content editor. 5. Follow the on-screen prompt to download the plugin file (a .zip file) to your computer. ⚙️ Step 2: Install the Plugin in WordPress Once you have the plugin file, install it directly through your WordPress admin dashboard. 1. Log in to your WordPress admin panel (e.g., yoursite.com/wp-admin). 2. Go to Plugins → Add New in the left menu. 3. Click Upload Plugin at the top of the page. 4. Click Choose File, select the .zip file you downloaded, and click Install Now. 5. Once installation is complete, click Activate Plugin. 🔗 Step 3: Connect WordPress to Search Atlas After activating the plugin, you need to link your WordPress site to your Search Atlas account. 1. In your WordPress dashboard, locate the newly installed Search Atlas plugin in the left menu. 2. Open the plugin settings and copy your API key or connection token. 3. Return to Search Atlas and paste the key into the CMS Connectors settings (Avatar → Settings → CMS Connectors) when prompted. 4. Save your settings. Your site should now show as connected in Search Atlas. 🚀 Step 4: Sync Content from Search Atlas With the plugin connected, you can publish or sync content directly from Search Atlas to WordPress. 1. Open a piece of content inside any Content tool (e.g., SEO Content Assistant or AI Content Templates). 2. Click the Publish or Sync to WordPress button within the editor. 3. Select your connected WordPress site from the dropdown. 4. Choose whether to save as a draft or publish immediately, then confirm. 🛠️ Troubleshooting Common Issues - Plugin not found in WordPress marketplace: This is expected. The plugin must be downloaded from inside Search Atlas and installed manually as described above. - Sync fails after installation: Double-check that the plugin is activated in WordPress and that your API key is entered correctly in the plugin settings. - Connection shows as disconnected: Try deactivating and reactivating the plugin, then re-enter your credentials. - WordPress version compatibility: Ensure your WordPress installation is up to date (version 5.0 or higher is recommended). 💡 Tips - You can connect multiple WordPress sites to one Search Atlas account — repeat Steps 1–3 for each site. - Always download the latest version of the plugin from inside Search Atlas to ensure compatibility. 🙋 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.

Last updated on Oct 26, 2026

📘 OTTO Blog Publishing to WordPress: Plugin Setup, Sync, and Visibility

If a blog post created in OTTO fails to publish to WordPress, the issue is usually related to plugin installation, plugin version, or WordPress-side settings — not OTTO itself. This article walks through installing the plugin, completing setup, syncing a post from OTTO, and understanding why a post may not appear where you expect it on your site. 📥 Installing the Search Atlas WordPress Plugin The Search Atlas plugin (internal slug metasync) is not listed in the WordPress.org plugin directory. It is installed by uploading the plugin ZIP file provided by Search Atlas. 1. Go to your WordPress Dashboard. 2. In the left sidebar, click Plugins → Add New → Upload Plugin. 3. Upload the Search Atlas plugin ZIP file. 4. Click Install Now, then click Activate Plugin. Activation is required — the plugin will not work if it is only installed. 🔄 Keeping the Plugin Updated Always run the latest version of the plugin — outdated versions are a common cause of failed syncs. If you suspect your installed version is out of date, delete and reinstall the plugin using the latest ZIP file provided by Search Atlas. 🔐 Plugin Setup (Required Before Publishing) After activation, open the Search Atlas Plugin in WordPress and confirm: - API Key is added - UUID is added - Settings are saved Then click Clear Cache, click Sync Now, and wait for the sync to complete. ✍️ How to Push a Blog Post from OTTO 1. In the left sidebar, go to Content → Content Genius (What are we writing today?) and open the article in editor mode. 2. Select Published or Draft. 3. Click Sync to Blog Post. You should see a "blog synced successfully" message. 👀 Why the Blog Post Is Live but Not Visible If the sync succeeds but you don't see the post on your blog page, this is expected WordPress behavior. Common reasons include: - The post is assigned to a different category - Your blog page only displays certain categories - Pagination hides newer posts - Theme or page builder controls visibility ✅ How to Confirm the Post Exists 1. Go to WordPress → Posts. 2. Locate the post (Draft or Published). 3. Check its category, status, and URL. If it appears here, the post was published successfully. 🔧 Changing Where the Blog Appears Post placement (category) is controlled by Search Atlas during sync. You can change the category in the sync pop-up window and match it to an existing WordPress category. This must be set each time you sync a post. ❓ FAQs How do I install the plugin? The Search Atlas plugin is not listed in the WordPress.org plugin directory. Install it by uploading the ZIP file provided by Search Atlas via Plugins → Add New → Upload Plugin. Do I need to re-sync after setup? No. Once synced successfully, re-sync is not required unless you make changes. Is this a WordPress issue or a Search Atlas issue? Publishing location and visibility are controlled by WordPress settings and categories. 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.

Last updated on Oct 26, 2026

🚀 Search Atlas Overview, GHL Compatibility & Demo

🔍 What Is Search Atlas? Search Atlas is an all-in-one SEO and digital marketing platform built for agencies, freelancers, and business owners who want to grow organic traffic and local visibility. It brings together a wide range of tools under one roof, so you don't need to juggle multiple subscriptions. Here's a snapshot of what Search Atlas includes: - OTTO SEO – An AI-powered SEO automation assistant that audits your site and deploys on-page fixes with minimal manual effort. - Local SEO Tools – Manage Google Business Profile (GBP) projects, schedule posts, respond to reviews, build local citations, and monitor performance — all from the left sidebar under Local. - Keyword Research & Rank Tracking – Find high-value keywords and monitor your rankings over time. - Site Auditor – Identify and prioritise technical SEO issues on any website. - Backlink Tools – Analyse your link profile, research competitor backlinks, and find link-building opportunities. - Content Tools – Plan, brief, and optimise content using AI-driven recommendations. - Reporting & Analytics – Build client-ready reports and track SEO KPIs from a centralised dashboard. 🔗 Does Search Atlas Work with Go High Level (GHL)? Yes — Search Atlas is compatible with websites hosted or built on Go High Level (GHL). Here is what you need to know: - Site Auditing: You can run a full technical SEO audit on any GHL-hosted website by entering the site URL in the Site Auditor. Search Atlas crawls the live site regardless of the platform it is built on. - OTTO SEO: OTTO can be connected to GHL sites. Because GHL uses its own CMS, some automated on-page deployments may require you to apply recommendations manually inside GHL, but OTTO clearly flags every suggested change so implementation is straightforward. - Local SEO: The Local tools (GBP management, citations, reviews, posts) work independently of your website platform, so GHL users benefit from these features without any limitations. - Rank Tracking & Keyword Tools: These are platform-agnostic and work fully with GHL sites. In short, Search Atlas adds a powerful SEO layer on top of Go High Level, giving GHL users capabilities that GHL alone does not provide. 🎬 Where Can I Find a Demo or Overview Video? If you or your client wants a quick visual walkthrough before committing to a purchase, here are the best places to find Search Atlas demo content: 1. Search Atlas YouTube Channel – Visit the official Search Atlas YouTube channel for product walkthroughs, feature deep-dives, and tutorial videos. Search for "Search Atlas overview" or "Search Atlas demo" to find the most relevant videos. 2. In-Platform Onboarding – After logging in, navigate to Home (left sidebar → Home, URL: /home) where onboarding guides and quick-start resources are available to help new users get oriented fast. 3. Live Demo Request – If a pre-recorded video isn't enough to convince a stakeholder, you can request a personalised live demo through the Search Atlas website or by contacting the team via the chat widget inside the platform. 💡 Quick Talking Points for Business Owners If you need to make a quick case to a business owner or decision-maker, here are the key value propositions of Search Atlas: - One platform, everything included – Replace multiple SEO tools with a single subscription. - AI-powered automation – OTTO SEO saves hours of manual optimisation work every week. - Local SEO built in – Ideal for businesses that rely on local search traffic and Google Maps visibility. - Agency-ready – White-label reporting, multi-project management, and client dashboards are all available. - Works with any website platform – Including Go High Level, WordPress, Shopify, Wix, and more. 🛠️ 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.

Last updated on Oct 26, 2026

🔌 WordPress Plugin Setup: Content Genius Without OTTO

🗺️ Overview The Search Atlas WordPress plugin serves two independent purposes: syncing articles from Content Genius to your WordPress site, and powering OTTO SEO automation. These two functions are completely separate. You can install the plugin, sync your Content Genius content, and continue using RankMath for on-page SEO — all without activating OTTO. ⚙️ Step 1: Install the Search Atlas WordPress Plugin 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Add New. 3. Search for Search Atlas and click Install Now, then Activate. 4. In your WordPress admin menu, open the Search Atlas plugin settings. 5. Enter your Search Atlas API key to connect your account. You can find your API key in your Search Atlas account settings. 🚫 Step 2: Disable OTTO SEO Completely After connecting the plugin, OTTO SEO is not active by default — you must explicitly activate it. To make sure it stays off, follow these steps: 1. In your WordPress admin menu, click Search Atlas to open the plugin dashboard. 2. Locate the OTTO SEO section or toggle. 3. Confirm the OTTO toggle is set to Off or Disabled. Do not connect or activate an OTTO site during setup. 4. Leave the OTTO section without making any changes and proceed to Content Genius syncing. As long as you do not activate OTTO from either WordPress or the Search Atlas platform (Left sidebar → OTTO SEO → SEO Automation), OTTO will not interfere with your existing SEO setup. 📝 Step 3: Sync a Content Genius Article to WordPress 1. In Search Atlas, go to Left sidebar → Content → Content Genius (page title: "What are we writing today?") to open the SEO Content Assistant. 2. Open the article you want to publish or locate it in your content list. 3. Inside the article editor, click the Export or Publish to WordPress button (the exact label depends on your plan). 4. Select your connected WordPress site from the dropdown. 5. Choose to publish immediately or save as a draft, then confirm. The article — including its title, body, and meta fields — will be pushed directly to your WordPress site as a new post or page. 🛡️ Step 4: Confirm RankMath Is Unaffected RankMath and the Search Atlas plugin are compatible when OTTO is disabled. To avoid any conflicts, verify the following after syncing your first article: - Open the synced post in WordPress and confirm RankMath's meta fields (title, description, focus keyword) are editable and populated correctly. - Check that RankMath's schema markup and sitemap settings are unchanged. - If Content Genius populated a meta title or description during export, review those values inside RankMath's panel and update them if needed — RankMath will take precedence for on-page SEO delivery. There are no known conflicts between RankMath and the Search Atlas plugin when OTTO is kept disabled. The Search Atlas plugin will not overwrite RankMath settings on posts it did not export, and it will not inject schema or redirect rules while OTTO is off. ⚠️ Important: What Activating OTTO Would Change If you ever choose to activate OTTO in the future, be aware of the following before doing so: - OTTO manages on-page SEO settings, schema, and meta data site-wide. This may conflict with RankMath controlling the same fields. - Running both OTTO and RankMath simultaneously on the same posts is not recommended and can produce duplicate schema or overwritten meta tags. - If you activate OTTO, disable RankMath first, or limit OTTO's scope to avoid overlap. For the use case described in this article — Content Genius syncing only — keep OTTO deactivated and RankMath will remain your sole SEO layer. 🔁 Reconnecting or Troubleshooting the Plugin - API key not working: Double-check that the key was copied in full with no trailing spaces, and that it belongs to an active Search Atlas account. - WordPress site not appearing in Content Genius export dropdown: Go to the Search Atlas plugin settings in WordPress and re-save your API key to refresh the connection. - Synced post is missing content: Ensure your article in Content Genius is saved and not in a draft-only state before exporting. - RankMath fields are blank after sync: Content Genius exports the article body and title. Open the post in WordPress and manually complete RankMath's focus keyword and description fields. 💬 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.

Last updated on Oct 26, 2026

🔧 Install Search Atlas Tracking Code on GoDaddy

🗺️ Overview The Search Atlas tracking code lets the platform collect data from your website so you can monitor performance, rankings, and site metrics. GoDaddy's website builder and hosting environment require a specific installation approach. This article walks you through every method available on GoDaddy and helps you fix the most common problems. 📋 Before You Begin Gather the following before you start: - Access to your Search Atlas account with Owner or Admin permissions. - Login credentials for your GoDaddy account. - Knowledge of which GoDaddy product you are using: GoDaddy Website Builder (Websites + Marketing), WordPress Hosting on GoDaddy, or cPanel Hosting with a custom site. 🔑 Step 1 — Copy Your Tracking Code from Search Atlas 1. Log in to Search Atlas. 2. In the left sidebar, click Site Metrics (Site Explorer). 3. Select the property you want to track, or add a new one. 4. Open the property settings and navigate to the Tracking Code section. 5. Click Copy Code to copy the full script snippet to your clipboard. Keep this tab open — you will need the code in the steps below. 🏗️ Step 2 — Add the Code to GoDaddy (Choose Your Method) 🌐 Method A: GoDaddy Website Builder (Websites + Marketing) 1. Log in to your GoDaddy account and open your Websites + Marketing dashboard. 2. Click Edit Website to open the site editor. 3. In the left panel of the editor, click Settings (gear icon). 4. Select SEO from the settings menu. 5. Scroll down to the Header Code or Custom Scripts field. 6. Paste your Search Atlas tracking code into this field. 7. Click Save, then click Publish to push the change live. Important: GoDaddy Website Builder only supports scripts in the SEO or custom-code sections. Do not paste the code into a text block on the page — it will render as visible text instead of executing as a script. 💻 Method B: WordPress Site Hosted on GoDaddy 1. Log in to your GoDaddy account and open My Products. 2. Click Manage next to your WordPress hosting plan, then open the WordPress Admin dashboard. 3. In WordPress, go to Plugins → Add New and search for Insert Headers and Footers (by WPCode). 4. Install and activate the plugin. 5. Navigate to Settings → Insert Headers and Footers. 6. Paste your Search Atlas tracking code into the Scripts in Header field. 7. Click Save. If your theme supports a Theme Editor, you can alternatively paste the code just before the closing </head> tag in your header.php file — but using a plugin is safer because it survives theme updates. ⚙️ Method C: GoDaddy cPanel Hosting (Custom HTML Site) 1. Log in to GoDaddy and open cPanel for your hosting account. 2. Open the File Manager and navigate to your website's root folder (usually public_html). 3. Right-click your main HTML file (commonly index.html) and select Edit. 4. Locate the closing </head> tag. 5. Paste your Search Atlas tracking code on the line directly above </head>. 6. Repeat this step for every page you want to track, or use a shared include/template file if your site uses one. 7. Click Save Changes. ✅ Step 3 — Verify the Tracking Code Is Working 1. Open your live website in a browser. 2. Right-click the page and select View Page Source. 3. Press Ctrl + F (or Cmd + F on Mac) and search for a unique portion of your tracking code, such as your site ID or the script domain. 4. If you can see the code in the source, the installation was successful. 5. Return to Search Atlas and check Site Explorer after 24–48 hours for incoming data. 🛠️ Troubleshooting Common GoDaddy Issues - Code appears as visible text on the page: You pasted the script into a text or HTML content block instead of a script/header field. Remove it and follow the correct method for your GoDaddy product above. - Changes are not appearing on the live site: Make sure you clicked Publish in the GoDaddy Website Builder after saving. Saving alone does not push changes live. - No data in Search Atlas after 48 hours: Confirm the code appears in the page source using Step 3 above. Also check that you copied the full code snippet without cutting off the opening or closing script tags. - Tracking code disappears after a theme update (WordPress): If you edited header.php directly, the update overwrote your change. Use the Insert Headers and Footers plugin instead — it stores the code independently of your theme. - GoDaddy Website Builder does not show a Header Code field: Some older Websites + Marketing plans have a limited editor. Try publishing the site first, then reopening settings — the field sometimes only appears on published sites. - Script blocked by a security plugin or firewall: If you use a WordPress security plugin such as Wordfence or a CDN such as Cloudflare, whitelist the Search Atlas script domain in your security 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.

Last updated on Oct 26, 2026

☁️ Connect Your Cloudflare API Token to Search Atlas

🔍 Overview Search Atlas can connect to your Cloudflare account to automate DNS and Workers configuration for your sites. For this to work, you must supply a Custom Token with the correct permissions — not a Global API Key. This article explains the two methods for enabling site automation and how to get your Cloudflare API token set up correctly. Important: Connecting Cloudflare and installing the OTTO script are two separate methods for enabling site automation. Read the section below to understand which one applies to your setup before you begin. ⚡ Cloudflare Connection vs. OTTO Script Installation Search Atlas offers two ways to activate automation on a site. You will only ever use one of them per site — not both. - Cloudflare API connection — Use this if your domain's DNS is managed through Cloudflare. Search Atlas connects directly to Cloudflare using an API token to handle automation on your behalf. - OTTO script installation — Use this if your site is not on Cloudflare, or if you prefer to manage deployment manually. You paste a JavaScript snippet into your site's <head> tag or through a plugin such as WPCode. If you have already installed the OTTO script, you do not need to connect Cloudflare. If you connect Cloudflare, you do not need to install the OTTO script. 🔑 Use a Custom Token, Not a Global API Key Search Atlas requires a Cloudflare Custom Token. Global API Keys grant unrestricted account access and are not accepted. Always create a scoped Custom Token with only the permissions needed for Search Atlas. 🛠️ How to Create the Correct Cloudflare API Token To create an API token with the right permissions for Search Atlas, log in to your Cloudflare dashboard and navigate to the API Tokens section of your profile. From there, create a new Custom Token (rather than using a template or a Global API Key) and grant it only the permissions required for the Search Atlas integration — these typically relate to Zone and DNS management for the specific domain you are connecting. If your token is being rejected by Search Atlas, the most common causes are: - Using a Global API Key instead of a Custom Token - The token's permissions are missing required access for the domain - The token is scoped to the wrong account or zone If you are unsure which permissions to grant, or if your token continues to be rejected after verifying the above, our support team can help you confirm the correct configuration for your account. 📋 What to Have Ready When Contacting Support If you need help resolving a token rejection or setting up your Cloudflare connection, please have the following ready before reaching out: - The exact error message shown when connecting the token in Search Atlas - The domain (zone) you are trying to connect - Whether you are using a Custom Token or a Global API Key - A screenshot of the token's permission settings (with the token value itself hidden) 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.

Last updated on Oct 26, 2026

🔌 Search Atlas API authentication and endpoint configuration for Google Apps Script

Overview You can connect Google Apps Script to Search Atlas by making authenticated HTTP requests to the Search Atlas API. This requires your API key and the correct endpoint URL. Step 1: Locate your Search Atlas API key 1. Log in to your Search Atlas account. 2. Navigate to your account settings or profile area to find your API key. 3. Copy the API key — you will use this to authenticate all requests. Step 2: Configure authentication in Google Apps Script Search Atlas uses API key-based authentication. In your Google Apps Script project, pass your API key as a header in each request: - Header name: X-API-KEY - Header value: YOUR_API_KEY (the key itself, with no "Bearer" prefix) Example setup in Google Apps Script: 1. Open your Google Apps Script project at script.google.com. 2. Use the UrlFetchApp.fetch() method to make HTTP requests. 3. Set the headers option to include your X-API-KEY header with your API key. 4. Set the method option to match the required HTTP method for your endpoint (e.g., GET or POST). Step 3: Use the correct API endpoint Use the base API URL provided in your Search Atlas account documentation or onboarding materials. Append the specific endpoint path for the data or action you need (for example, keyword data, project data, or backlink data). Troubleshooting common issues - 401 Unauthorized: Double-check that your API key is correct and that it is sent in the X-API-KEY header with no "Bearer" prefix and no extra spaces. - 403 Forbidden: Most often the API key was missing, invalid, or revoked. Check that the key is sent in the X-API-KEY header (not as a Bearer token), that you copied the full key, and that it has not been regenerated or revoked in Settings → API Keys. If the response is a Cloudflare error page (for example Error 1010), the request was blocked by our security layer before reaching Search Atlas — contact support with the Cloudflare Ray ID, the time of the request, and the endpoint you called. Your plan does not cause this error. - Endpoint not found: Verify the endpoint path matches what is documented in your Search Atlas account — check for typos or version mismatches in the URL. When to contact support If you are unable to resolve your authentication or endpoint issue, please have the following ready before reaching out: your project name, the exact error message returned by the API, the endpoint URL you are calling, and a timestamp of when 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.

Last updated on Oct 26, 2026

🔌 Search Atlas API Setup for Third-Party Integrations

🗺️ Overview Search Atlas provides programmatic access to its data through a REST API, allowing you to integrate Search Atlas with third-party tools and platforms such as Manus AI. This article explains how to get started with the Search Atlas API. 🔑 Step 1: Find Your API Key 1. Log in to your Search Atlas account. 2. Navigate to your account settings area. 3. Locate the API credentials section to find and copy your unique API key. Treat this key like a password — do not share it publicly. 📄 Step 2: Access the Official API Documentation For accurate, up-to-date details on base URLs, available endpoints, authentication formats, request parameters, and response structures, refer to the official Search Atlas API documentation. The documentation is the authoritative source for all technical specifications needed to build a working integration. If you are unsure where to find the API documentation, or if you cannot locate your API credentials in your account settings, reach out to the support team directly — they can point you to the correct documentation and confirm the authentication method and endpoint structure for your use case. 🔗 Step 3: Connect to Your Third-Party Tool Once you have your API key and have reviewed the official documentation, you can configure your third-party tool (such as Manus AI or any HTTP client) using the credentials and endpoint details provided in that documentation. When setting up your integration, have the following ready: - Your Search Atlas API key - The specific endpoint(s) you need (from the official docs) - The authentication header format specified in the official docs - Any required query parameters for the data type you are requesting 🛠️ Troubleshooting & Escalation If you encounter errors when making API requests or cannot locate your API key, please have the following information ready before contacting support: - The exact error message or HTTP status code you are receiving - The endpoint or integration you are trying to use - The name of the third-party tool or platform you are connecting - A timestamp of when the issue 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.

Last updated on Oct 26, 2026

🔌 Connect Search Atlas MCP to Claude via OAuth

🧭 Overview The Search Atlas MCP (Model Context Protocol) connector lets you use Search Atlas tools — such as keyword research, site audits, and OTTO insights — directly inside Claude. This guide explains what OAuth authorization is, what to do if your tools are not appearing after connection, and how to get further help from our team. 🔑 What Is OAuth Authorization for MCP? OAuth is the secure login method that links your Search Atlas account to Claude. Without completing this step, Claude cannot access your Search Atlas tools, even if the MCP server appears to be connected. You must authorize the connection through your Search Atlas account before any tools become available. ⚙️ How to Connect Search Atlas MCP to Claude The exact steps to add and authorize the Search Atlas MCP connector depend on the version of Claude you are using. Follow the instructions provided in Claude's own documentation or setup wizard for adding an MCP server. When prompted, log in with your Search Atlas credentials and approve the permissions requested to grant Claude access to your Search Atlas tools. If you are unsure where to begin, our support team can walk you through the process for your specific Claude setup. 🛠️ Troubleshooting: Search Atlas Tools Not Showing Up Problem: Authorization was not completed - If the OAuth flow was interrupted or you closed the browser before finishing, disconnect the Search Atlas MCP connector and restart the authorization process from the beginning. Ensure you complete all steps without closing the browser tab during any redirects. Problem: You are on a free or limited plan - MCP tool access requires an active Search Atlas subscription. If your account is on a free trial or a limited allowance plan, authenticated tool requests may be blocked. Check your plan status inside your Search Atlas account and upgrade if needed, then retry the connection. Problem: Tools still do not appear after authorization - Disconnect the connector entirely, log out of both Claude and Search Atlas, then log back in and repeat the authorization flow. If the issue persists, contact our support team with the details listed below. 📋 What to Have Ready When Escalating If you have tried the steps above and tools are still not appearing, please have the following information ready before contacting support: - Your Search Atlas account email and the plan you are subscribed to - The exact error message or behavior you are seeing (e.g., tools not listed, authorization page not loading, connector showing as disconnected) - The version or interface of Claude you are using (e.g., Claude.ai, API, desktop app) - A timestamp or approximate time when 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.

Last updated on Oct 26, 2026

🔌 GSC Activation, Project Sync & Bulk Indexing Setup

🗺️ Overview To use bulk indexing in Search Atlas, you must first complete the Google Search Console (GSC) OAuth activation. Bulk indexing features only become available after a successful GSC connection. This article explains what is required at each stage so you can self-serve or escalate effectively. ✅ Prerequisites - A Google account with Owner or Full User permissions on the GSC property you want to connect. - An active Search Atlas account with at least one project created. - Pop-ups allowed in your browser for the OAuth consent screen. 🔐 Step 1: Activate Your GSC Connection Navigate to the GSC integration area within your Search Atlas account settings. From there, initiate the Google OAuth flow by choosing the Google account that has access to your GSC properties, then grant Search Atlas the requested permissions to read your GSC data. Once the OAuth flow completes successfully, your GSC connection will be confirmed on the settings page. Important: If the OAuth pop-up does not open, check that your browser is not blocking pop-ups for the Search Atlas domain, then try initiating the connection again. 📂 Step 2: Sync Your GSC Projects After your GSC connection is confirmed, trigger a property sync from the integration settings. Search Atlas will import all GSC properties associated with your connected Google account. Once the sync completes, your imported properties will be available to link to your Search Atlas projects. If a property you expect is missing, verify that the connected Google account holds Owner or Full User access to that property directly in Google Search Console, then run the sync again. 📊 Step 3: Access Bulk Indexing Features Bulk indexing becomes available only after at least one GSC property is successfully connected and synced. If you attempt to access bulk indexing before completing Steps 1 and 2, you will be prompted to connect GSC first. Once your GSC property is linked to a project, navigate to the bulk indexing section of that project to begin submitting URLs for indexing. 🛠️ If You Get Stuck If your GSC connection is not completing, your properties are not appearing after a sync, or bulk indexing features remain unavailable after following the steps above, please have the following ready when you reach out: - The Google account email used for the OAuth connection - The GSC property URL(s) you are trying to connect - A description of where in the process you are getting stuck (e.g., OAuth pop-up not appearing, sync completing but properties missing, bulk indexing section not unlocking) - Any error messages displayed on screen 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.

Last updated on Oct 26, 2026

🔑 Create a Cloudflare API Token With Correct Permissions

🌐 What Is a Cloudflare API Token? A Cloudflare API token is a secure credential that allows third-party tools — like Search Atlas — to interact with your Cloudflare account on your behalf. Unlike your global API key, tokens are scoped to specific permissions, making them safer and easier to manage. Search Atlas uses your Cloudflare API token to read and update DNS records, which is required for certain site verification and SEO workflows. 🛠️ Step-by-Step: Create Your API Token 1. Log in to your Cloudflare dashboard at dash.cloudflare.com. 2. Click your Avatar Menu (👤) in the top-right corner and select My Profile. 3. In the left sidebar, click API Tokens. 4. Click the Create Token button. 5. Select Create Custom Token at the bottom of the template list. 6. Give your token a recognisable name, such as Search Atlas Token. 7. Under Permissions, add the required permissions listed in the next section. 8. Under Account Resources, set the scope to Include — All accounts, or select your specific account. 9. Under Zone Resources, set the scope to Include — All zones, or select the specific zone you want Search Atlas to access. 10. Click Continue to Summary, review the settings, then click Create Token. 11. Copy the token immediately — Cloudflare will only show it once. Store it somewhere safe before closing the page. ✅ Required Token Permissions When setting up your custom token, you must add the following permissions exactly as listed. Missing or incorrect permissions will prevent Search Atlas from connecting to your account. - Zone — DNS — Edit: Allows Search Atlas to read and update DNS records for your zone. - Zone — Zone — Read: Allows Search Atlas to read zone-level settings and metadata. To add each permission, click Add permission in the Permissions section, select the correct category, resource, and access level from the dropdown menus. Note: If Search Atlas prompts you for additional permissions during setup, follow the on-screen instructions — the exact requirements may vary depending on the workflow or feature you are configuring. 🔗 Connect Your Token to Search Atlas 1. Log in to your Search Atlas account. 2. Navigate to the section of the platform where you are setting up Cloudflare integration (for example, site verification or domain connection). 3. When prompted, paste your copied API token into the Cloudflare token input field shown on screen. 4. Confirm or save the entry as directed by the on-screen prompt. Search Atlas will validate the token automatically. If validation fails, double-check that the token permissions match those listed above and that the Zone Resources scope includes the correct domain. If the issue persists, please note the exact error message and the domain you are trying to connect before reaching out for support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🔌 WordPress Plugin Setup and OTTO Licensing Explained

Overview If you want to use a subdomain (for example, blog.yourdomain.com) as a WordPress CMS publishing endpoint in Content Genius, you need to connect it through the Search Atlas WordPress plugin. This article explains how OTTO licensing applies to subdomains and what to have ready when our team helps you complete the setup. How the WordPress Plugin Authenticates The Search Atlas WordPress plugin authenticates by establishing a connection between your WordPress installation and your Search Atlas account. The general steps are: 1. Install and activate the Search Atlas plugin on your WordPress site. 2. Follow the on-screen prompts inside your WordPress dashboard to link the plugin to your Search Atlas account. 3. Once the connection is confirmed, the site becomes available as a publishing destination in Content Genius. If the connection does not complete or you encounter an error during setup, note the exact error message and the domain you are trying to connect — you will need this information when contacting support. Connecting a Subdomain as a Publishing Endpoint Content Genius lets you publish content directly to a WordPress site, including subdomains. To use a subdomain like blog.yourdomain.com as your CMS endpoint: 1. Make sure the Search Atlas plugin is installed and authenticated on the subdomain's WordPress installation (not just the root domain). 2. Each WordPress installation — root domain or subdomain — must have the plugin installed and authorized separately, because each is treated as a distinct site connection. 3. Once the subdomain's plugin connection is complete, it will become available as a publishing destination in Content Genius. If the subdomain does not appear as an available destination after completing the plugin setup, contact our team and have the following ready: the exact subdomain URL, your Search Atlas account email, and any error messages you have seen. OTTO Licensing and Subdomains A common question is whether connecting a subdomain requires a separate OTTO license. OTTO licensing requirements depend on which features you intend to use on that subdomain. If you are unsure whether your current license covers your subdomain configuration, or if you are seeing unexpected prompts related to OTTO when setting up your subdomain connection, please reach out to our team with your account details and subdomain URL for clarification. 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.

Last updated on Oct 26, 2026

🔗 Connecting LinkedIn Company Pages to Search Atlas

🔎 Overview When connecting LinkedIn through the Search Atlas integrations area, you may notice that only your personal LinkedIn profile appears — even if you are a Super Admin of a LinkedIn company page. This is a known limitation that our team is aware of and working to address. This article explains what is happening. Because this issue requires investigation on a case-by-case basis, we recommend contacting our support team directly so an agent can assist you with connecting your LinkedIn company page. ⚠️ How LinkedIn Differs from Other Platforms Unlike Facebook and Instagram, which allow you to select a business page or account after completing authentication, LinkedIn does not support choosing a Company Page post-authentication. This means posts will go to the personal profile used during the OAuth flow — not to any company page — even if your account holds admin permissions on that page. There is no in-app workaround available to redirect posts after the connection has been established. 🔍 What Is Happening The integrations area currently has a limitation that can prevent LinkedIn company pages from appearing or connecting correctly during the OAuth flow. The connection flow prioritises your personal LinkedIn profile, which means company pages may not surface automatically even when you have the correct admin permissions. Common reasons a LinkedIn company page may not connect include: - Your personal LinkedIn account does not hold the required admin permissions on the company page - You are logged in to a different LinkedIn account than the one associated with the company page - A known frontend limitation is affecting how pages are displayed during the connection flow 🛠️ Steps to Try 1. Confirm you are logged in to the correct LinkedIn account — make sure the LinkedIn account you use during the OAuth connection in Search Atlas is the same account that has admin access to the target company page. If you are unsure, log out of LinkedIn in your browser entirely, then log back in with the correct account before proceeding. 2. Verify your permissions on the LinkedIn company page — LinkedIn requires your personal account to hold admin-level access on the company page before it can be authorised through OAuth. Confirm that your account is listed as an admin on the company page. If it is not, have the page owner grant you admin access before attempting to reconnect. 3. Disconnect your existing LinkedIn connection in Search Atlas — navigate to the integrations area, find your current LinkedIn connection, and disconnect it completely. This clears any cached OAuth token that may be locking the connection to your personal profile. 4. Reconnect LinkedIn from the integrations area — with the correct LinkedIn account active in your browser, initiate the OAuth flow again from the Search Atlas integrations area and complete the authorisation process. 🙋 Still Not Working? Because connecting a LinkedIn company page can depend on account-specific permissions and platform behaviour, this issue is best resolved with direct assistance. Please open the chat widget in the bottom-right corner of the platform and type human teammate to reach our support team, and an agent will help you complete the connection.

Last updated on Oct 26, 2026

🛠️ Install the Search Atlas MCP Server

🔌 What is the Search Atlas MCP server? The Search Atlas MCP server lets supported AI tools, such as Claude, connect to Search Atlas capabilities through the Model Context Protocol (MCP). 🔑 Before you begin - Make sure Claude is installed and available from your terminal. - Have an active Search Atlas API key ready. - Replace YOUR_SEARCHATLAS_API_KEY_HERE with your actual API key before running the command. ⚙️ Install MCP in Claude Open your terminal and run the following command: claude mcp add --transport http searchatlas https://mcp.searchatlas.com/mcp/ --header "X-API-KEY: YOUR_SEARCHATLAS_API_KEY_HERE" Use standard quotation marks exactly as shown. Do not include the placeholder text, brackets, or curly quotation marks around your API key. ⚙️ Install MCP in Codex Codex uses the same server and the same API key as Claude. Add this to your Codex config file, ~/.codex/config.toml (or .codex/config.toml inside a trusted project): [mcp_servers.searchatlas] url = "https://mcp.searchatlas.com/mcp/" http_headers = { "X-API-KEY" = "YOUR_SEARCHATLAS_API_KEY_HERE" } Replace YOUR_SEARCHATLAS_API_KEY_HERE with your actual Search Atlas API key. Keep the key out of any config file you commit to a repository. Then start a new Codex session and ask it to use the Search Atlas MCP connection. 🔄 Reconnect after installation 1. Close and reopen Claude, or reconnect the MCP server from your Claude settings. 2. Start a new conversation. 3. Ask Claude to use the Search Atlas MCP connection. 🧪 Fix authentication errors If Claude rejects your credentials, run the installation command again with the correct API key, then reconnect Claude. Authentication commonly fails when the API key is expired, copied with extra spaces, or entered with curly quotation marks. - Confirm that the key is active in Search Atlas. - Copy the key again without leading or trailing spaces. - Use the exact server URL: https://mcp.searchatlas.com/mcp/. - Make sure the header name is exactly X-API-KEY. ✅ Confirm the connection After reconnecting, ask Claude to perform a Search Atlas action that your account supports. If the request succeeds, the MCP server is installed and authenticated. 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.

Last updated on Oct 26, 2026

🔌 WordPress Plugin Setup for Content Sync

🧭 Overview To publish or sync content from Search Atlas directly to your WordPress site, you need to install the official Search Atlas WordPress plugin. The plugin is not available in the WordPress.org plugin directory — it is installed by uploading the plugin ZIP file provided by Search Atlas. 🔍 Getting the Correct Plugin The Search Atlas WordPress plugin is not listed in the WordPress.org plugin directory. To install it, you must upload the plugin ZIP file provided by Search Atlas. - Current plugin name: Search Atlas Contact the Search Atlas support team to obtain the plugin ZIP file for your account. 📦 Installing via Manual ZIP Upload Because the plugin is not available in the WordPress plugin directory, it must be installed manually using the ZIP file provided by Search Atlas. 1. Once you have the plugin ZIP file, log in to your WordPress admin panel. 2. Go to Plugins → Add New → Upload Plugin. 3. Click Choose File, select the ZIP file, and click Install Now. 4. After installation completes, click Activate Plugin. 🔗 Connecting the Plugin to Search Atlas After activation, you must connect the plugin to your Search Atlas account. The plugin settings page will prompt you for the credentials or key needed to establish the connection. If you are unsure where to find your connection credentials, contact the support team for guidance specific to your account. 1. In your WordPress admin panel, find Search Atlas in the left sidebar menu. 2. Open the plugin settings page. 3. Enter the required connection credentials as prompted and save. 4. A confirmation message will indicate whether the connection was successful. 🛠️ Troubleshooting Common Sync Errors If the plugin is installed and connected but content still will not sync, work through the checks below. - Plugin not visible after installation: Confirm the plugin was activated, not just installed. Go to Plugins → Installed Plugins and verify its status shows as Active. - Connection not savi 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.

Last updated on Oct 26, 2026

🔌 Official Search Atlas MCP Integrations

✅ Official repository ownership Search Atlas maintains an official MCP server repository, and only repositories published and maintained by Search Atlas itself should be treated as official. Community forks, look-alike repositories, and personal projects are not officially supported. To find the current official repository, refer to the setup materials published through official Search Atlas documentation or confirm with the Search Atlas support team before configuring anything. 🤖 Supported AI clients Which MCP clients are officially supported can change over time, so always verify support for your specific client in the official Search Atlas MCP setup materials. Before configuring a client such as Claude, ChatGPT, or Codex, confirm that official Search Atlas documentation covers that integration rather than relying on third-party tutorials or community configurations. 🛠️ Official setup resources Always use the README and documentation published by Search Atlas for installation instructions, required credentials, supported tools, and configuration examples. Avoid setup guides from unofficial sources. Before configuring an MCP client, confirm that you are following the current official instructions and using the correct Search Atlas credentials. Never paste credentials into unofficial configuration files or third-party services. 🔎 How to identify approved repositories 1. Confirm the repository is maintained under Search Atlas's official GitHub presence, not a personal account or an unrelated organization. 2. Check that the repository documentation identifies Search Atlas as the owner or maintainer. 3. Use setup instructions linked from official Search Atlas documentation or the repository itself. 4. Be cautious with repositories that use similar names, promise clients that official documentation does not mention, or request credentials through unrelated services. 5. When in doubt, treat a fork or personal repository as community-maintained unless Search Atlas explicitly identifies it as official. 6. If you are still unsure which repository is official, contact the Search Atlas support team to confirm before configuring anything. 💬 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.

Last updated on Oct 26, 2026

🚀 Staging vs Production Setup and GSC Connection

🗺️ Overview Two of the most common setup questions from new Search Atlas customers are: should I start on staging or production? and how do I connect my Google Search Console (GSC) account? This article answers both clearly so you can get up and running without delays. 🏗️ Staging vs Production: Which Should You Set Up First? The short answer is: always set up Search Atlas on your production site first. Here is why this matters and what each option means in practice. - Production is your live, public-facing website. This is where real users visit, real traffic is measured, and real SEO signals are generated. Search Atlas tools — including OTTO SEO, rank tracking, and site audits — are designed to work against live data. - Staging is a private copy of your site used for testing before changes go live. Because staging environments are typically blocked from search engines (via noindex tags or password protection), data collected there will not reflect your actual SEO performance. Setting up on production first ensures that your GSC data, backlink profiles, keyword rankings, and site audit results are accurate and actionable from day one. ✅ When Staging Can Be Useful While production is always the primary setup target, staging has a limited role in your workflow. You may use a staging environment to: - Preview and test OTTO SEO code changes before applying them to your live site. - Validate structured data or schema markup implementations. - Test site speed improvements before deploying to production. Important: Never connect your GSC property to a staging URL. GSC only captures meaningful data for verified, publicly indexed properties. Connecting a staging URL will result in missing or misleading data. 🔗 How to Connect Your Google Search Console Account Connecting GSC to Search Atlas links your real organic search data — impressions, clicks, average position, and indexed pages — directly to your dashboard. Follow these steps: 1. Log in to your Search Atlas account and navigate to Site Metrics → Site Explorer. 2. Click Open Google Search Console to reach the Manage Sites page. 3. Click Connect GSC Account and sign in with the Google account that has access to your GSC property. 4. Select the correct GSC property from the dropdown. Make sure you select the production URL (e.g., https://yourdomain.com), not a staging or subdomain variant. Once connected, Search Atlas will begin pulling your GSC data. It may take up to 24 hours for the full data set to populate in your dashboard. ⚠️ If GSC Says to Reach Out to Support In some cases, the GSC connection screen will display a message instructing you to contact support. This typically happens when: - Your Google account does not have Owner or Full User permissions on the GSC property. - The GSC property has not been verified in Google Search Console yet. - There is a conflict with a previously connected Google account on your Search Atlas workspace. - Your Search Atlas plan requires a manual authorization step for GSC integration. Before reaching out, check the following in your Google Search Console account: 1. Go to Google Search Console → Settings → Users and permissions. 2. Confirm that the Google account you are using to connect has Owner or Full User access to the property. 3. Confirm that the property is verified and shows data (not a newly added, unverified property). 4. Return to Search Atlas and retry the connection using that verified Google account. If the issue persists after following these steps, our team can resolve it for you quickly. 🛠️ Quick Troubleshooting Checklist - Wrong property selected: Make sure you pick the exact property format that is verified in GSC (e.g., domain property vs. URL-prefix property). - Multiple Google accounts: If you manage several Google accounts, ensure your browser is logged in to the correct one before authorizing. - GSC data delay: New connections can take up to 24 hours to reflect data. Check back the following day before troubleshooting further. - Staging URL connected by mistake: Disconnect the staging property and reconnect using your production URL. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Last updated on Oct 26, 2026

🛠️ Connect Your Shopify Store to Search Atlas

🔍 Overview Connecting your Shopify store to Search Atlas lets OTTO SEO audit, monitor, and automate SEO improvements directly on your site. Some users encounter an issue where the script verification step does not complete as expected after installation — this is a known bug that requires our team to investigate on the backend. 📋 What This Issue Looks Like You may experience one or more of the following: - The script appears to be installed on your Shopify store, but Search Atlas does not confirm detection - Attempting to re-verify does not produce any visible change or confirmation - OTTO SEO does not begin its crawl even after installation steps are completed ⚙️ What Is Happening This is a bug-category issue. The underlying cause is not a configuration error on your end — it relates to how Search Atlas communicates with your Shopify store during the verification step. Resolving it requires our team to review your site's connector state and script detection on the backend. 🔧 What to Have Ready Before Escalating To help our team resolve this as quickly as possible, please have the following information available when you reach out: - Your Shopify store URL (e.g., yourstore.myshopify.com) - The site name as it appears inside your OTTO SEO account - A brief description of where in the installation process the issue occurred - Any error messages or on-screen text you saw during verification (screenshots are helpful) - The approximate date and time you first encountered the issue ✅ What to Expect Once our team reviews your connector configuration and script detection status on the backend, they will confirm whether the script is being detected correctly and take any necessary action to complete verification. You do not need to reinstall or modify your theme while waiting — our team will advise if any change is needed on your end. 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.

Last updated on Oct 26, 2026

🔗 Install the GHL Connector

🎯 What the GHL connector does The GoHighLevel (GHL) connector lets Search Atlas publish and manage blog content in your GHL account. It requires permission to create or update posts, read existing posts, check slugs, and access blog categories and authors. 🔧 Install the connector 1. Sign in to Search Atlas. 2. Open the project where you want to connect GHL. 3. Open the GHL connector installation or integrations flow. 4. Sign in to your GHL account when prompted. 5. Select the correct GHL location or sub-account. 6. Review the requested permissions and approve the connection. 7. Return to Search Atlas and confirm that the connector shows as connected. 🔐 Required permissions Depending on your GHL account version, the permission names may differ from the names shown in Search Atlas documentation. Grant the permissions that match these capabilities: - Create Blog Post: create new blog posts. - Update Blog Post: update existing blog posts. - Check Blog Post Slug: check whether a blog slug is available. - View Blog Post Categories: read blog categories. - View Blog Authors: read blog authors. - blogspostreadonly: read existing posts. - blogslistreadonly: list available posts. 🧩 If the scopes are missing Some GHL accounts do not display these exact scope names in Private Integrations. This is expected when GHL presents permissions using newer labels, grouped permissions, or a different app type. 1. Check that you are creating or authorising the connector in the correct GHL location, not only at the agency level. 2. Look for grouped permissions related to blogs, posts, content, authors, categories, or read and write access. 3. Select the closest available permissions that allow both reading and writing blog posts. 4. Save the integration, then restart the Search Atlas connection flow. 5. If no blog-related permission is available, ask a GHL account administrator to review your user role and location permissions. ✅ Confirm the connection After installation, verify that Search Atlas can select the intended GHL location and access blog posts, categories, and authors. A successful connection should allow Search Atlas to create or update a test post without a permission error. 🛠️ Troubleshoot connection errors - Confirm that the correct GHL location is selected. - Reconnect the integration after changing permissions. - Make sure the GHL user approving access has administrator rights or equivalent integration permissions. - Remove an incomplete or duplicate private integration before trying again. - Check that the connector is connected to the same Search Atlas project you are using for publishing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

🔌 Search Atlas Plugin Installation and Knowledge Base Coverage Setup

Overview This article covers what to do if you are experiencing issues with the Search Atlas plugin installation or with your site's knowledge base coverage setup. If you are running into a problem in either of these areas, the steps below explain how to escalate efficiently so our team can resolve it quickly. What This Issue Involves Customers reaching out about this topic typically encounter one or more of the following: - Difficulty installing or activating the Search Atlas plugin on their site - The plugin not connecting correctly to their Search Atlas account or project - Redirect rules not behaving as expected after plugin setup - A knowledge base coverage score that is not improving or appears lower than expected - Pages that appear missing or uncrawled within their project What to Have Ready Before Contacting Support Because plugin installation and knowledge base coverage issues often require our team to review your specific project configuration directly, the fastest path to resolution is to reach out with the following information prepared: - Your project name or the domain associated with the affected site - A description of the specific symptom you are seeing (e.g., plugin not activating, coverage score not updating, redirects not working) - Any exact error messages displayed on your screen, copied verbatim - The timestamp of when the issue first occurred or was last observed - Screenshots of the problem if available, as these help our team identify the issue faster Having these details ready when you contact support allows our team to investigate your account and project settings directly and provide a resolution without unnecessary back-and-forth. Next Steps If you are experiencing any of the issues described above, please reach out to our support team so we can look into your account and guide you through the correct setup for your specific configuration. 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.

Last updated on Oct 26, 2026

🔗 Unified Connector Scope and Permission Setup

The connector setup flow has been redesigned to unify scope selection, permission configuration, and team creation into a single, streamlined wizard — making it faster and clearer to connect your accounts from the start. ✨ What's New The new Connector Unified Scope/Permission UX brings together three previously separate steps — selecting your connector scope, configuring permissions, and creating a team — into one cohesive guided wizard. Instead of navigating multiple screens or settings pages, you are now walked through each step in sequence within a single interface. The create-team step is now embedded directly in the connect wizard, so your team is set up automatically as part of the connection process without any additional navigation required. 🛠️ How to Use It 1. Navigate to Site Metrics → Site Explorer in the left sidebar. 2. Click Connect GSC Account (or Connect GA Account) to launch the new unified wizard. 3. Select the desired scope for your connector when prompted. 4. Review and confirm the required permissions in the next step. 5. Complete the Create Team step to finalize your setup — all within the same wizard flow. 6. Click Finish to activate your connector with the configured settings. 📋 What to Expect The wizard guides you linearly through each step, so you cannot skip scope or permission selection before reaching team creation. Existing connectors already configured are not affected by this change. If you exit the wizard before completing all steps, your progress will not be saved and you will need to restart the connection flow from the beginning. 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.

Last updated on Oct 26, 2026

☁️ Cloud Stack Project Requirements and Target URL Setup

Overview When setting up a Cloud Stack in Search Atlas, one of the most common questions is whether you need a saved project before you can get started. This article explains what we know about the project requirement and how to get the right information for your specific setup. Do You Need a Saved Project to Run a Cloud Stack? Based on confirmed resolutions from our support team, a saved project is not required to run a Cloud Stack. You can enter a target URL directly without needing to link the Cloud Stack to an existing project in your account. If you do have a saved project, you may be able to use it during setup to associate your Cloud Stack activity with that project — but this is optional, not mandatory. What to Do If You Are Unsure About Your Setup Because Cloud Stack configuration details can vary depending on your account and the current state of the platform, the safest way to get accurate guidance for your specific situation is to contact our support team directly. When you reach out, please have the following ready: - The target URL you want to use for your Cloud Stack - Whether you have an existing saved project you want to associate with it - Your Search Atlas account email or project name - A description of any error or unexpected behaviour you are encountering This will allow our team to give you fast, accurate guidance without 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.

Last updated on Oct 26, 2026

🔗 How to Reconnect Wix With an API Key

🔍 Why Search Atlas Asks for a Wix API Key The API key lets Search Atlas securely connect to your Wix site, so it can publish and update content on your behalf. Reconnecting is usually needed when the original connection expired, the key was deleted or changed in Wix, or permissions were modified. The key is created inside your Wix account, not in Search Atlas. This guide walks you through creating it and entering it in the right place. ✅ Before You Start - Make sure you can sign in to the Wix account that owns the site you want to connect. - You must be the account owner or have permission to manage API keys. If you cannot see the API Keys page, ask the site owner to follow these steps or to upgrade your access. - Keep the Search Atlas tab open so you can paste the key as soon as you have it. 🔑 Step 1: Generate Your API Key in Wix 1. Log in to your Wix account. 2. Open your Account Settings (usually found by clicking your profile picture in the top-right corner). 3. Select API Keys from the menu. 4. Click Generate API Key. 5. Give the key a clear name, such as Search Atlas, so you can recognize it later. 6. Choose the permissions the key should have. Grant access to the content areas you want Search Atlas to work with, such as your blog and site content. If you are unsure, select the permissions related to content and publishing for the site you are connecting. 7. Confirm the key applies to the correct site if Wix asks you to choose one. 8. Click Generate Key. Important: Wix usually shows the full key only once. Copy it right away and keep it somewhere safe until you have pasted it into Search Atlas. 🆔 Step 2: Find Your Site ID (If Requested) Depending on the connection screen, Search Atlas may also ask for your Wix Site ID. To find it: 1. Open your site's dashboard in Wix. 2. Look at the web address in your browser. 3. Copy the long string of letters and numbers that appears after dashboard/. That is your Site ID. 🔗 Step 3: Enter the Key in Search Atlas 1. Go back to Search Atlas and open the Wix connection screen that asked you for the API key. 2. Paste the API key into the field provided. 3. If a Site ID field appears, paste your Site ID there as well. 4. Click the button to save or connect. 5. Wait for the confirmation message that your Wix site is connected. Once connected, your Wix CMS connector should show as active and you can continue publishing as usual. 🛠️ Troubleshooting Common Problems - The key is rejected as invalid: Check for extra spaces at the beginning or end of the pasted key. Copy it again from the original source. If you no longer have the key, generate a new one in Wix. - I closed the Wix page before copying the key: Generate a new key and use that one. You can delete the unused one from the API Keys page. - The connection succeeds but publishing fails: The key may be missing permissions. Create a new key with broader content and publishing permissions, then reconnect. - I cannot find the API Keys page in Wix: Your Wix user role may not allow it. Ask the account owner to generate the key for you. - It worked before and then stopped: The key may have been deleted, regenerated, or may have expired in Wix. Generate a new one and reconnect. - I have more than one Wix site: Make sure the key and Site ID match the site you want to connect in Search Atlas. 🔒 Keeping Your API Key Safe - Treat the key like a password. Do not share it in public places or screenshots. - Use one dedicated key for Search Atlas so you can manage it separately. - If you think a key has been exposed, delete it in Wix and create a new one, then update Search Atlas. - If you delete the key in Wix, the connection will stop working until you reconnect with a new one. 💬 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026