Onboarding

🔌 WordPress Plugin Setup and OTTO Licensing Explained

🔌 Install the WordPress Sync Plugin Manually

🔍 Why You Can't Find the Plugin in WordPress The Search Atlas WordPress Sync Plugin may not appear in the WordPress.org plugin directory at certain times. This is a known, temporary situation. If you search for Search Atlas inside your WordPress dashboard under Plugins → Add New and see no results, do not worry — you can install the plugin manually using a ZIP file provided directly by the Search Atlas support team. 📥 Step 1: Get the Plugin ZIP File Because the plugin may not be listed in the public WordPress directory, you will need to obtain the latest plugin ZIP file directly from the Search Atlas team. Contact our support team using the chat widget in the bottom-right corner of the platform and request the current manual download link for the WordPress Sync Plugin. A teammate will provide you with the correct, up-to-date file. Once you have the ZIP file saved to your computer, do not unzip or extract it — WordPress requires the compressed ZIP format for manual installation. ⚙️ Step 2: Upload the Plugin to WordPress 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Add New. 3. Click the Upload Plugin button at the top of the page. 4. Click Choose File and select the .zip file you received from the Search Atlas team. 5. Click Install Now. 6. Once the installation completes, click Activate Plugin. 🔗 Step 3: Connect the Plugin to Search Atlas After activating the plugin, you will need to connect it to your Search Atlas account. The exact steps for locating your API key and entering it into the plugin settings may vary depending on your plugin version. The Search Atlas support team can walk you through the connection steps specific to your setup when they provide the ZIP file. 🛠️ Troubleshooting Upload Errors If you see an error during the ZIP upload, it is usually caused by one of the following: - File size limit: Your hosting provider may restrict upload size. Contact your host or increase the upload_max_filesize value in your PHP configuration. - Permissions issue: Ensure your WordPress user account has administrator-level permissions. - Corrupted file: Re-download the ZIP file from the link provided by the support team and try again. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

WordPress Plugin Setup and Organic Keywords Guide

Overview If you are working on a WordPress site in Search Atlas, installing the Search Atlas WordPress plugin is optional but recommended. It unlocks deeper on-page data, content optimization features, and faster data syncing. Missing organic keywords in a project is a separate, common issue usually related to setup steps or data population timelines. This article walks you through both topics. Do You Need the WordPress Plugin? The Search Atlas WordPress plugin is not required to use core SEO features such as rank tracking, keyword research, or site metrics. However, installing it provides the following advantages: - Direct content optimization from within the WordPress editor - Faster on-page audit data syncing - Easier publishing workflows when using the Content Genius tool - Real-time SEO scoring inside WordPress without switching tabs If your site runs on WordPress and you want the full Search Atlas experience, follow the installation steps below. How to Install the Search Atlas WordPress Plugin 1. Log in to your WordPress admin dashboard at yoursite.com/wp-admin. 2. In the left WordPress menu, go to Plugins → Add New → Upload Plugin. 3. Choose the Search Atlas plugin .zip file provided by Search Atlas (the plugin is not listed in the WordPress plugin directory). 4. Click Install Now, then click Activate. 5. Once activated, open the Search Atlas plugin settings from your WordPress dashboard. 6. Enter your Search Atlas API key. To find your API key, log in to Search Atlas and navigate to your account settings area. 7. Save your settings. The plugin will verify the connection. Your WordPress site is now connected to Search Atlas. Data will begin syncing within a few minutes. How to Add Your WordPress Site as a Project Even with the plugin installed, you must add your domain as a project inside Search Atlas for organic keyword data to appear. 1. In Search Atlas, navigate to the project or site management area. 2. Add your domain as a new project or select an existing one. 3. Enter your full domain URL (for example, https://jamutech.com) and complete the setup steps. 4. Make sure the domain matches the URL on your live WordPress site exactly, including https:// and any subdomains. Why Are No Organic Keywords Showing? If your project shows zero organic keywords, there are several likely causes: - New project, data still loading: After adding a domain, it can take time for organic keyword data to populate. Allow up to 24–48 hours before expecting full data. - Domain not yet added as a project: Organic keyword data only appears once a domain has been properly added and configured as a project in Search Atlas. - Domain mismatch: If the domain entered in your project does not exactly match your live site's URL, data may not appear correctly. If you have completed setup and keyword data is still not appearing after 48 hours, please reach out to our support team through the chat widget in the Search Atlas dashboard so we can investigate further.

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

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

🔌 WordPress Plugin Authentication for Multi-Client Agencies

Overview When managing SEO for multiple clients, you can install the Search Atlas WordPress plugin on each client's site and authenticate it securely — whether you use your own agency credentials or have clients authenticate themselves. This article outlines the key considerations to help you choose the workflow that fits your setup. Personal Email vs. Client Email: Security Clarification A common concern for agencies is whether logging in with a personal Search Atlas email during plugin authentication creates a security risk for the client's site. Here is what you need to know: - Authentication only links the plugin to a Search Atlas account — it does not grant that account any WordPress admin access to the client's site. - Using your agency email is safe and common. It simply tells the plugin which Search Atlas workspace to sync data with. - If you prefer separation, you can have each client log in with their own Search Atlas credentials instead. - No client data is exposed to other projects in your workspace unless you explicitly share it. Choose whichever approach matches your client relationship and internal processes — both are fully supported. Before You Begin - You have WordPress admin access to the client's site. - You have a Search Atlas account (agency or client credentials ready). - The Search Atlas WordPress plugin .zip file provided by Search Atlas is ready to upload via WordPress → Plugins → Add New → Upload Plugin. Connecting the Plugin to Search Atlas The general process involves installing the Search Atlas WordPress plugin on the client's site, then completing the authentication flow using either your agency Search Atlas credentials or the client's own Search Atlas credentials. Once authenticated, ensure the correct project is selected so data syncs to the right client workspace. Tip for client-initiated setup: If you prefer the client to handle authentication themselves, you can install and activate the plugin first, then share their Search Atlas login credentials with them and ask them to complete authentication and project selection. If You Run Into Issues Because the source information for this topic is limited, our support team can provide more specific guidance for your agency's configuration. Have the following ready when you reach out: the client site URL, the Search Atlas account email used for authentication, and a description of the specific issue or error encountered. 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.

📊 GHL SEO Dashboard Overview

Whether you’re running campaigns, optimizing landing pages, or tracking local search performance, you shouldn’t have to switch between tools to understand your SEO. That’s why the new SEO Tab inside Go High Level brings powerful, enterprise-grade SEO capabilities directly into your workflow. From technical audits and AI-powered fixes to content tools and local heatmaps, this integration gives you complete visibility—and control—over how your site performs in search. No exports, no guesswork. Just data, insights, and fixes, all in one place. 🧭 What’s Inside the SEO Tab? Go High Level (GHL) users now have a built-in SEO tab—giving you access to audits, AI recommendations, content tools, and local heatmaps without leaving your dashboard. The SEO Tab contains three main sections: - Site Projects - Local SEO - Settings 🛠️ Site Projects 🔍 Overview Tab Get a complete SEO snapshot of your domain, including: - Domain Power, Backlinks, Keywords - Organic Traffic, Paid Traffic - Site Audit Health (including number of crawled pages and total issues) - Backlinks Data: Historical totals, types, and attributes - Keyword Analytics: Includes graphs and tables with: - Search Intent - Traffic - Monthly Volume - CPC - Difficulty - Ranking URL 🤖 AI Recommendations AI Recommendations This tab is where we will address the technical issues identified in your Site Audit. Technical Fixes are broken down into the following categories: ● Title Tags ● Meta Descriptions ● Missing Image Alt Text ● Meta Keywords ● Headings Length ● Canonical Link ● Open Graph ● Twitter Card ● Miscellaneous Each category will have two view tabs. Issues and Fixed issues for easier viewing. The tab will have four columns: ● URL: Where the issue is detached. ● Current Value: The current value for that issue. Not optimized based on SEO best practices. ● Recommended Fix: AI-recommended fix for the technical issue based on SEO best practices. ● Action: Button to deploy or roll back the fix. To deploy a change based on our AI recommendations, you click on the button in the Action column. 📍 Local SEO Use local Heatmaps to track Google Business Profile (GBP) rankings by keyword on a map view. Dashboard Columns: - Business Name - Average Rank - Keywords Tracked - Rating - ➕ Add / Remove Keywords buttons 🔧 Step-by-Step Instructions 1. Access Local Heatmaps 🟣 Step 1. In the left sidebar, click Local. 🟣 Step 2. Under LOCAL SEO TOOLS, click Local SEO Heatmap. 2. First screen (business list + import options) 🟡 Step 3. When the Local SEO Heatmap page opens, the user sees the “Manage your local business” screen with the list of businesses. If the user already has a GBP connected, the business appears in the list. 🟡 Step 4. If the user does not have a GBP connected, they must use the controls visible at the top of the page: - Choose Business Name / Place ID / Place URL - Type in the field Find a local business by business name… - Click Search They may also select: - Import from Google Business Profile - Import Heatmaps 3. Managing an added business 🗂️ Step 5. In the business list, each row displays a View button and a three-dot menu ( … ). To delete a business: - Click … - Click Delete 🗂️ Step 6. To open a heatmap for a business, click View. 4. Heatmap setup screen (after clicking View) 🔍 Step 7. The user is now on the Local SEO Heatmap setup view, where the business name appears at the top (e.g., “Windy City Tax Relief”). Here, the user can add keywords in the Enter a keyword(s) field. 🔍 Step 8. The user can click Smart Suggest for keyword suggestions. 🔍 Step 9. The user can use the dropdown filters located directly below the keyword bar: - Heatmap shape (Circle / Rectangular) - Layers (1–7 layers) - Distance (e.g., 2 miles, 3 miles) - Refresh cadence (Run Once, Refresh Daily, Refresh Weekly, Refresh Bi-weekly, Refresh Monthly, Refresh Monthly with date selector) - Time (e.g., 9 AM) 5. Editing an existing heatmap 📝 Step 10. When a business already has heatmap data, the list shows two actions in the … menu: - Edit heatmap - Delete Or the user may click View to open the map. 6. Heatmap view (full map) 🗺️ Step 11. In the full heatmap view, the left side shows the score panel (with the donut chart and pin breakdown), and the right side displays the map. 🗺️ Step 12. The user can click Edit heatmap at the top to adjust settings. 🗺️ Step 13. Hovering over the date at the top of the heatmap expands additional details and scan info. ⭐ Additional Interaction Clicking on a star (ranking pin) on the map 🌟 Step 14. When the user clicks a star on the map, a pop-up opens showing the competitor list and ranking information for that specific pin. 🌟 Step 15. In that pop-up, clicking Compare opens the two-column Local SEO Showdown view, which displays the user’s business on the left and the selected competitor on the right. 🗑️ To Delete a Heatmap 🗑️ Step 16. In the business list, click …. 🗑️ Step 17. Click Delete. 📊 View & Compare Results: - Click the GBP name to see the heatmap - Use the dropdown to switch between keywords - Click any pin to see the top competitors at that location - Use “Local SEO Showdown” for side-by-side competitor map comparison - Click “Get PDF” to download 🕒 View previous versions by clicking the date above the report (if refresh cadence was set). 🗑️ To delete a Heatmap: - Click ... next to the report - Select Remove ⚙️ SEO quotas and usage 📊 View your SEO quotas and usage When hovering over the Quota indicator at the top of the interface, the user can view their SEO quotas and usage, including: - Site Audit - AI Suggestions - Site Explorer - Heatmap Quota - Keyword Rank Tracker - Content Genius - Articles & Target Keywords - Content Planner - Onpage Audit - GSC & GBP Projects The quota panel (Avatar → Billing → Plans & Top-ups) shows: - Total Quota - Recurring - Non-Recurring - Top Up button Depending on the screen, the panel may also display: - Current quota consumption. - Projected next month's usage. - A note that each location pin on the heatmap costs one quota. - A breakdown for Circle and Grid heatmap shapes. 💡 Advanced SEO Dashboard (via “Launch Advanced SEO”) 👉 Login to Advanced SEO Access the full suite of SEO features, including Site Audit, Content Genius, Keyword Tools, GBP Management, and Reporting—directly from your dedicated dashboard. 🔬 Site Audit Tools 1. Overview 2. Page Explorer 3. Content Velocity 4. Domain-Level View 5. Technical Issues 6. Page Pruning 7. Site Visualization 8. Email Alerts 9. Live Monitoring ✍️ Content Tools Create or manage web content with Content Genius. Export finished work as HTML for direct upload to your site. Tools include: - Content Genius - Onpage Audit - Topical Maps - Content Planner - Meta Generator - AI Templates - Content Rewriting 📈 Site Metrics Get SEO performance reports with data on: - Topical Dominance - Keywords - Pages & Subdomains - Ranking Changes - Backlinks & Competitors - Google & Facebook Ads 🔑 Keyword Tools 1. Keyword Research 2. Keyword Magic Tool 3. Rank Tracker 4. Keyword Gap Analysis 🏢 GBP Galactic Manage your Google Business Profile: - Auto Posting - Task Management - Reviews & Q&A - Local SEO Heatmaps - Local SERPs 📋 Reports Builder Create automated reports for SEO projects from your dashboard. With GHL’s built-in SEO dashboard, your team gets more than just reports—you get an actionable strategy hub. Audit your pages, deploy AI fixes, plan content, and track local rankings without leaving the platform. This isn't just a new tab—it’s your SEO command center. Start using it today to turn insights into impact and make smarter, faster SEO decisions where it matters most: right inside your client workflows.

🔔 Understanding the WordPress Plugin Impersonation Message

🧐 What Is This Message? When configuring the Search Atlas WordPress plugin, you may see the following notice at the top of your screen: "You are currently impersonating another user. Changes made may affect their account." This message is a standard WordPress security notice — it is not an error, and it does not mean anything has gone wrong. It simply lets you know that the currently active session in your browser is operating under a different user account than your own. 💡 Why Does This Happen? This notice typically appears in one of the following situations: - Support or agency access: A Search Atlas support team member, agency administrator, or colleague has temporarily logged into your WordPress site to assist with configuration or troubleshooting. - User-switching plugins: Your WordPress site has a user-switching plugin installed (such as the popular "User Switching" plugin), and an admin on your site has used it to switch into another account. - Shared admin sessions: You or another admin on your team switched user accounts without fully logging out first. In all cases, WordPress displays this banner as a transparency measure so that any active user is aware of who is performing actions on the site. ⚙️ Does It Affect the Plugin Configuration? It can — but only if you or another person actively makes changes while the impersonation session is active. Here is what to keep in mind: - Any settings saved inside the Search Atlas WordPress plugin during an impersonation session will be saved under the impersonated account's permissions. - If the impersonated account has the correct WordPress role (Administrator), plugin configuration will proceed normally. - If the impersonated account has insufficient permissions, some settings may not save correctly. To avoid any unintended changes, do not modify plugin settings while this banner is visible unless you are confident about which account is active and what permissions it holds. ✅ What Should You Do? 1. Check who is impersonating: The banner usually includes a link or name indicating which account is active. Review this information before making any changes. 2. End the impersonation session: If you did not intend to be in an impersonation session, look for a "Switch back" or "Return to your account" link within the banner or your WordPress admin bar and click it to restore your original session. 3. Re-open the plugin settings: Once you are back in your own account, navigate to the Search Atlas plugin settings in your WordPress dashboard and verify that your configuration is correct. 4. Disable user-switching if not needed: If no one on your team intentionally uses account switching, consider deactivating any user-switching plugins on your site to prevent this banner from appearing unexpectedly. 🔒 Is My Account Safe? Yes. This message is a built-in WordPress protection feature, not a sign of a security breach. It exists specifically to make impersonation visible so that site owners are always informed when actions are being taken under a different account. If you did not authorise anyone to access your WordPress site and you see this message unexpectedly, we recommend reviewing your WordPress user accounts and resetting passwords as a precaution. 🛠️ Still Have Questions? 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.

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

🗺️ Configure Geographic Targeting and Bulk WordPress Sync

About This Topic This article covers configuring geographic targeting and bulk WordPress sync in Search Atlas. These settings control which service area your AI-generated content is scoped to and how content is pushed to your connected WordPress site. Because the exact steps for configuring geographic targeting and bulk WordPress sync depend on your specific account setup and the current state of the Search Atlas interface, our support team will need to walk you through the correct workflow for your situation. Before Contacting Support — What to Have Ready To help our team resolve your configuration question as quickly as possible, please have the following information ready when you reach out: - Your project or campaign name — the specific project where you are trying to configure settings. - The geographic area you are trying to target — for example, a specific city, county, or region. - What you have already tried — any settings you have already changed or saved. - Any exact error messages — copy the full text of any error or unexpected result you are seeing. - The timestamp of when the issue occurred, if relevant. Having these details ready will allow our team to identify your configuration issue and provide the correct steps without unnecessary back-and-forth. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Trigger SEO Audits via API with Make

🌐 Overview This guide explains how to set up an automation workflow where a GoHighLevel form submission triggers a Search Atlas site audit via the Search Atlas API through Make (formerly Integromat), waits for the audit to complete, retrieves the report, and emails the results to your client. This is ideal for agencies that want to deliver SEO reports as part of a lead generation or onboarding funnel. 🛠️ What You Need Before Starting - A Search Atlas account with API access enabled - Your Search Atlas API key (found via Account Menu → Settings → API Keys) - A Make account with an active scenario - A GoHighLevel form connected to Make via webhook - An email service connected in Make (e.g., Gmail, SMTP, or SendGrid) ⚙️ Step 1 — Connect Your GoHighLevel Form to Make 1. In Make, create a new scenario and add a webhook-based trigger module. 2. Copy the webhook URL generated by Make. 3. In GoHighLevel, open your form settings and paste the webhook URL into the appropriate webhook or automation notification field. 4. Submit a test entry from your form to confirm Make receives the payload, including the contact's website URL and any other fields you plan to pass to the Search Atlas API. 🚀 Step 2 — Trigger a Site Audit via the Search Atlas API 1. In Make, add an HTTP request module after your webhook trigger to call the Search Atlas API. 2. Configure the request method, endpoint URL, authentication, and request body according to the Search Atlas API documentation (available inside your account). The documentation will specify the exact endpoint, required parameters, and how to pass your API key. 3. Map the website URL captured from the GoHighLevel form submission to the appropriate parameter defined in the Search Atlas API documentation. 4. Run the module and confirm a successful response. Note any identifier returned in the response that you will need to check audit status in the next step — consult the API documentation for the exact response schema. ⏳ Step 3 — Wait for the Audit to Complete Site audits may take some time to complete depending on the size of the site. Use Make's available flow-control and HTTP modules to periodically check the audit status endpoint defined in the Search Atlas API documentation until the audit is finished. 1. Add an HTTP request module using a GET request to the audit status endpoint specified in the Search Atlas API documentation, passing the identifier from Step 2. 2. Use Make's available delay and flow-control modules to pause between status checks and avoid rate limiting. 3. Once the API response indicates the audit is complete (refer to the Search Atlas API documentation for the exact status values), proceed to retrieve the full report. 📊 Step 4 — Retrieve and Email the Report 1. Add another HTTP request module to call the report retrieval endpoint specified in the Search Atlas API documentation, passing the audit identifier. 2. Parse the response data as needed using Make's built-in tools to extract the report details you want to include in your email. 3. Add an email module (e.g., Gmail, SMTP, or SendGrid) and map the report data to the email body, subject line, and recipient address captured from the GoHighLevel form submission. 4. Run the full scenario end-to-end with a test submission to confirm the report is delivered successfully. 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.

🔄 Switch Websites and Remove UUID in WordPress Plugin

🗺️ Overview If you need to stop tracking one website and start fresh with a different one, you can do this by removing your current site from Search Atlas and clearing the UUID (User ID) from the WordPress plugin. This guide walks you through every step so you can get your new site connected quickly and correctly. ⚠️ Before You Begin Please review the following before making any changes: - Data will not carry over. Rankings, keyword data, and site metrics associated with your current website will no longer be accessible once the site is removed. - WordPress admin access is required. You will need to log in to the WordPress dashboard of the site where the Search Atlas plugin is installed. - Plan limits apply. Adding a new website counts against your plan's site allowance. Verify you have an available slot before proceeding. 🛠️ Step 1: Remove the Current Website from Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click Site Metrics (Site Explorer). 3. Locate the website you want to remove from your site list. 4. Click the settings or options icon next to the site name. 5. Select Remove Site (or Delete Site) and confirm the action when prompted. Once confirmed, the site will be removed from your Search Atlas account and will no longer appear in your Site Explorer dashboard. 🔌 Step 2: Remove the UUID from the WordPress Plugin The UUID (Unique User ID) links your WordPress site to your Search Atlas account. You must clear this value before connecting a new site — otherwise the plugin will still attempt to sync with your old account data. 1. Log in to the WordPress admin dashboard of the site where the Search Atlas plugin is installed. 2. In the WordPress left menu, navigate to Search Atlas (or the plugin settings page). 3. Open the plugin's Settings tab (general). 4. Locate the OTTO Pixel UUID field. 5. Clear (delete) the existing value from that field so it is completely blank. 6. Click Save or Update Settings to apply the change. The plugin is now disconnected and ready to be linked to a new Search Atlas site. 🚀 Step 3: Connect Your New Website 1. Return to your Search Atlas account. 2. In the left sidebar, click Site Metrics (Site Explorer). 3. Click Add New Site and enter the URL of your new website. 4. Once the site is added, go to the plugin's Settings page in Search Atlas and copy the new UUID generated for this site. 5. Go back to your WordPress admin dashboard, open the Search Atlas plugin settings, paste the new UUID into the OTTO Pixel UUID field (Settings tab / general), and click Save. Your new website is now connected. Allow a short period for data to begin populating in your Search Atlas dashboard. ✅ Verify the Connection To confirm everything is working correctly: - In Search Atlas, go to Left sidebar → Site Metrics (Site Explorer) and check that your new site appears in the list. - In WordPress, open the Search Atlas plugin settings and confirm the UUID field shows the new value — not blank and not the old ID. - Check that the plugin status shows as Connected or Active. ❓ Frequently Asked Questions Can I undo removing a website? No. Once a site is removed from Search Atlas, its historical data cannot be restored. Make sure you want to proceed before confirming the deletion. Do I need to uninstall the WordPress plugin? No. You only need to clear the UUID field. The plugin itself can remain installed on the site. What if the UUID field is greyed out or locked? This may indicate a permissions issue or a plugin conflict. Try deactivating other plugins temporarily, or contact support using the instructions below. 💬 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.

🔌 Connect Your Website via WordPress Plugin

🗺️ Overview Connecting your website to Search Atlas unlocks site tracking, rank monitoring, and on-page optimization tools. This guide walks you through every step: installing the WordPress plugin, locating your credentials, and completing the connection inside Search Atlas. 📋 Before You Begin - You have an active Search Atlas account and are logged in. - You have admin access to your WordPress dashboard. - Your website is live and publicly accessible. ⚙️ Step 1 — Add Your Website in Search Atlas 1. In the left sidebar, click Site Metrics (Site Explorer). 2. On the Site Explorer page, click Add New Website or the + button. 3. Enter your full website URL (e.g., https://yoursite.com) and click Save. 4. Your new website will appear in the list. Click on it to open the site dashboard. 🔑 Step 2 — Locate Your API Key and UUID 1. Click your account avatar or profile icon in the top-right corner of the platform. 2. Go to Account Settings or Integrations. 3. Find the API Key and your website's UUID. The UUID is unique to each connected website. 4. Copy both values — you will paste them into the WordPress plugin in the next step. Keep this tab open for reference. 🛠️ Step 3 — Install the Search Atlas WordPress Plugin 1. Log in to your WordPress admin dashboard (yoursite.com/wp-admin). 2. In the left menu, go to Plugins → Add New. 3. In the search bar, type Search Atlas and press Enter. 4. Locate the official Search Atlas plugin in the results and click Install Now. 5. Once installed, click Activate to enable the plugin. 🔗 Step 4 — Configure the Plugin with Your API Key and UUID 1. After activation, a Search Atlas menu item will appear in your WordPress left sidebar. Click it. 2. In the plugin settings page, paste your API Key into the API Key field. 3. Paste your website's UUID into the UUID field. 4. Click Save Settings or Connect to finalize the link. 5. A success confirmation message will appear when the connection is established. ✅ Step 5 — Verify the Connection in Search Atlas 1. Return to your Search Atlas account and navigate to Site Metrics (Site Explorer) in the left sidebar. 2. Click on your website in the list to open its dashboard. 3. You should see data beginning to populate. Note that some metrics — such as rank tracking — may take up to 24 hours to display fully. 💡 Tips and Troubleshooting - Plugin not visible after activation? Try clearing your WordPress cache and refreshing the admin page. - Connection error? Double-check that your API Key and UUID are copied correctly with no extra spaces. - UUID not found? Each website you add to Search Atlas has its own UUID. Make sure you are copying the UUID for the specific site you are connecting — not a different property. - Website behind a firewall or password protection? Temporarily allow external access during setup, then re-apply restrictions after the connection is confirmed. 💬 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.

🛠️ Search Atlas Plugin Incompatibility With Enfold Avia Builder

🔍 Overview If you are using the Search Atlas WordPress plugin alongside the Enfold theme and its built-in Avia Builder, you may find that you cannot type text into any field on your website. This is caused by a known conflict between the Search Atlas plugin and Enfold/Avia Builder. A fix for this incompatibility has been identified and deployed by the Search Atlas engineering team. If you are still experiencing this issue, follow the steps below. ✅ Is This Your Issue? You are likely affected if all of the following are true: - You have the Search Atlas plugin installed and active on your WordPress site. - Your WordPress theme is Enfold and you use the Avia Builder page editor. - You are unable to type letters or text into fields on your website's front end or within the builder. - The problem disappears when you deactivate or uninstall the Search Atlas plugin. ⚙️ What Caused This? The Search Atlas engineering team confirmed that a specific incompatibility existed between the Search Atlas plugin and the Enfold theme's Avia Builder. This conflict interfered with keyboard input across the site. A fix was developed, reviewed, and deployed to resolve this. 🚀 Steps to Resolve 1. Update the Search Atlas plugin. Log in to your WordPress admin dashboard, navigate to the Plugins section, and check whether an update is available for the Search Atlas plugin. If an update is available, install it immediately, as it contains the fix for this incompatibility. 2. Reactivate the plugin if you disabled it. If you deactivated or uninstalled the Search Atlas plugin as a workaround, reinstall it from the WordPress plugin repository or your account, then activate it. 3. Clear your WordPress and browser cache. After updating, clear any caching plugins you use as well as your browser cache to ensure the latest version of the plugin is fully loaded. 4. Test your site. Open a page that uses Avia Builder and confirm you can now type into text fields normally. 💡 If the Issue Persists If you have updated the plugin and are still unable to type on your site, our team will need to investigate further. To help us resolve this as quickly as possible, please be ready to provide: - Your WordPress admin login credentials (shared securely through the chat). - The version of the Search Atlas plugin currently installed. - The version of the Enfold theme you are using. - A screen recording or description of exactly where and when the typing issue occurs. 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.

⚡ WordPress Plugin PHP Compatibility and Content Sync Alternatives

Overview The Search Atlas WordPress plugin requires a minimum PHP version to function correctly. If your hosting provider runs an older or unsupported PHP version, the plugin may not install or work as expected. This article explains how to check compatibility and how to continue working with your content if the plugin cannot be installed. PHP Version Compatibility Before installing the Search Atlas WordPress plugin, confirm the PHP version your hosting environment is running. You can usually find this information in your hosting control panel (e.g., cPanel, Plesk) under PHP Configuration or Software Settings. If your host is running an unsupported PHP version, the plugin will not be compatible. In that case, we recommend one of the following steps: - Upgrade your PHP version — Most hosting providers allow you to switch PHP versions from the control panel at no extra cost. Check your host's documentation or support resources for guidance on upgrading. - Contact your hosting provider — If you are unsure how to upgrade, ask your host's support team to update your PHP version on your behalf. - Use an alternative content sync method — If upgrading PHP is not possible, you can still use Search Atlas to create and manage content and then transfer it to WordPress manually. Alternative Method: Copy and Paste Content Manually You can write and optimise content fully inside Search Atlas and then manually transfer it to WordPress without the plugin. 1. Use the relevant Search Atlas content tools to create or optimise your content within the platform. 2. Once your content is complete, select and copy the text from the Search Atlas editor. 3. Paste it directly into the WordPress block editor or classic editor on your site. 4. Apply headings, formatting, and meta details as needed within WordPress before publishing. This method requires no plugin and works regardless of your hosting PHP version. When to Contact Support If you are unsure which PHP version your host requires, or if you encounter errors when attempting to install the plugin, please reach out to our team. When escalating, have the following ready: - Your current PHP version (found in your hosting control panel) - The exact error message displayed when attempting to install the plugin - Your WordPress version - Your hosting provider's name 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.

📦 Get the Latest Website Migration Skills Package

🗺️ Overview The Website Migration skills package is a ZIP file containing structured skill folders you load into Claude (via your MCP client or directly). This article explains what each package version contains, when the migration-template-builder Stage 4 skill was introduced, and how to get the most up-to-date package. 📋 Skills Package Version History Use the table below to identify your package version and confirm which skills are included. - v1.4 (released 2026-06-23) — 6 skill folders: migration-site-audit, migration-gap-analysis, migration-redirect-mapper, migration-content-classifier, migration-risk-assessor, migration-qa-checker. Does not include migration-template-builder. - v1.5 (released 2026-06-27) — 7 skill folders: All six skills above, plus migration-template-builder (Stage 4). This is the version documented in the current HTML walkthrough. If your ZIP is dated 2026-06-23 or shows only six folders, you have v1.4. The Stage 4 migration-template-builder skill does not exist in that version — it was added four days later in v1.5. No amount of reloading or reconnecting your MCP client will make it appear, because it is simply not present in that file. ⬇️ Download the Current Skills Package 1. Log in to Search Atlas and go to Home (left sidebar, URL: /home). 2. Open the Features menu by clicking Open features menu in the top area of the Home page. 3. Locate the Website Migration Skills package card and click Download Latest ZIP. 4. Confirm the downloaded filename shows v1.5 (or higher) and the date 2026-06-27 or later before proceeding. 🔄 Replace Your Old Skills Folder 1. Unzip the newly downloaded package to a local folder. 2. Verify the folder now contains seven skill subfolders, including migration-template-builder. 3. In your MCP client (or Claude project settings), remove or replace the reference to the old v1.4 skills directory with the path to your new v1.5 folder. 4. Reload your MCP client session so Claude picks up the updated skill set. 5. Confirm migration-template-builder is available by asking Claude to list loaded skills or by starting a Stage 4 task in the HTML walkthrough. ✅ Verify the Stage 4 Skill Is Active After reloading, run a quick check to make sure everything is in order: - Ask Claude: "Which website migration skills do you have loaded?" — the response should list all seven skills, including migration-template-builder. - Cross-reference with the HTML walkthrough Stage 4 section; the skill name and input fields should now match exactly. - If Claude still does not list the Stage 4 skill, double-check that your MCP client is pointing to the new folder path and that the reload completed without errors. ❓ Frequently Asked Questions - Why did the walkthrough describe a skill my ZIP didn't have? The HTML walkthrough was updated on 2026-06-27 to document v1.5 features. If you downloaded the ZIP before that date, you received v1.4, which predates the walkthrough update. - Can I add the missing skill manually? No. Skill folders have internal dependencies and schema files. Always download the full official package to avoid compatibility issues. - Will my existing migration projects be affected? No. Upgrading the skills package only adds new capabilities; it does not alter data from projects already completed with earlier skills. - Where can I see which version I have without unzipping? The ZIP filename includes the version number and release date, for example website-migration-skills-v1.4-2026-06-23.zip. 💬 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.

⚡ Share OTTO Plugin Credentials Without Outlook

Overview When you add the OTTO pixel plugin to your website, Search Atlas provides an Email my developer button to quickly share installation credentials. However, this button opens Microsoft Outlook by default. If your team uses Gmail, Slack, or any other communication tool, the button may not work as expected. This article shows you how to manually retrieve your UUID and API Key, and share them with your developer through any channel you choose. Where to Find Your OTTO Plugin Credentials 1. Log in to Search Atlas and navigate to the OTTO section of your dashboard. 2. Locate your OTTO workspace and find the area where your plugin credentials are displayed. 3. You will see two key credentials: - UUID — your unique site identifier - API Key — the authentication key required by the plugin 4. Copy each value by highlighting the text and pressing Ctrl + C (Windows) or Cmd + C (Mac). Why the 'Email My Developer' Button May Not Work The Email my developer button uses a mailto: link, which automatically opens your operating system's default email client. If Outlook is not installed or configured on your device, the button may not function as expected. This is a browser and OS limitation — not a Search Atlas error. The solution is to share the credentials manually, as described below. How to Manually Share Credentials With Your Developer Once you have copied your UUID and API Key, you can share them through any method your team uses. Follow these steps to put together everything your developer needs: 1. Copy your UUID from your OTTO dashboard credentials area. 2. Copy your API Key from the same area. 3. Open your preferred communication tool — for example, Gmail, Slack, Microsoft Teams, or a project management app. 4. Compose a message or task for your developer and include the following information: - UUID: [paste your UUID here] - API Key: [paste your API Key here] - Plugin name: OTTO SEO (available in the WordPress plugin directory) 5. Ask your developer to install the OTTO SEO plugin on your WordPress site and enter the UUID and API Key when prompted during setup. If You 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.

🛠️ WordPress Plugin & Cloudflare Setup Order

🔍 Why Timing Matters Search Atlas offers two ways to implement tracking and site optimizations: the WordPress plugin and a Cloudflare CDN integration. Both methods are powerful on their own, but running them simultaneously can cause dashboard errors, duplicate data, or conflicting configurations. Following the correct sequence ensures a smooth transition with no data gaps or broken settings. ⚠️ What Happens If You Use Both at Once Activating Cloudflare while the WordPress plugin is still running may cause: - Dashboard errors or missing metrics in Search Atlas - Duplicate script injections on your site - Conflicting cache rules between the plugin and Cloudflare's CDN layer - Inaccurate reporting due to overlapping data sources To avoid these issues, always follow the step-by-step order below. ✅ The Correct Setup Sequence 1. Log in to your WordPress admin panel. Navigate to Plugins → Installed Plugins and locate the Search Atlas plugin. 2. Deactivate the WordPress plugin. Click Deactivate and wait for the page to confirm the plugin is no longer active. Do not delete it yet — you may want to keep it available in case you need to roll back. 3. Clear your WordPress cache. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache), purge all cached files before proceeding. 4. Log in to your Search Atlas dashboard. Navigate to the Cloudflare integration settings inside the platform. 5. Connect your Cloudflare account. Follow the on-screen prompts to authorise the connection and select the correct domain. 6. Verify the Cloudflare integration is active. Confirm that your domain shows a Connected status in the Search Atlas dashboard before making any further changes. 7. Test your site. Visit your website and check that pages load correctly and no console errors appear in your browser's developer tools. 💡 Tips for a Smooth Transition - Do not reactivate the WordPress plugin after connecting Cloudflare. The two methods serve the same function and do not need to run together. - If you manage multiple WordPress sites, repeat this process for each domain individually — do not connect all sites at once. - Allow up to 24 hours for Cloudflare's DNS propagation to complete fully after connecting. Some metrics in your dashboard may appear delayed during this window. - Keep a note of your plugin settings before deactivating, in case you need to reference any custom configurations later. 🔄 Rolling Back to the WordPress Plugin If you need to switch back to the WordPress plugin for any reason, reverse the process: disconnect the Cloudflare integration in your Search Atlas dashboard first, then reactivate the plugin in WordPress. Never enable both at the same time. 🙋 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.

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

📘 The Definitive Migration Guide: Moving from Legacy SEO Plugins to Search Atlas

The biggest bottleneck in modern SEO is no longer creativity or strategy, it is execution. Most marketing teams operate across systems that were never designed to communicate with one another. Nowhere is this disconnect more obvious than between SEO platforms and content management systems. Audits live in one tool, recommendations in another, and execution happens manually inside WordPress, often across multiple plugins that do not agree with each other. The Search Atlas WordPress Plugin changes this dynamic. It acts as a direct execution bridge, transforming WordPress from a passive content host into a native execution surface connected to Search Atlas. 🧩 Eliminating Plugin Fragmentation For years, the standard WordPress SEO stack has been fragmented: one plugin for titles and meta descriptions, another for XML sitemaps, another for schema, and separate plugins for redirects, robots.txt, caching, and indexing. These tools frequently conflict with one another, and updates in one plugin can break functionality in another. Most external SEO platforms can identify issues but cannot actually fix them inside WordPress, forcing teams to manually reimplement changes. The Search Atlas WordPress Plugin replaces this fragmented stack with a single, unified environment where strategy, execution, and visibility live together. 🚀 The Migration Experience Migrating to Search Atlas does not require rebuilding your site or losing SEO history. The plugin includes a dedicated migration module that pulls existing data directly from legacy SEO tools such as Yoast, RankMath, and All in One SEO. One click imports your existing titles, meta descriptions, and core SEO configurations directly into the Search Atlas plugin. Existing 301 and 404 redirects can also be imported, with redirect history preserved, so separate redirect plugins can be removed. There is no site rebuild, no loss of historical rankings, and no manual re-entry required. 🧠 WordPress as a Native Execution Surface Once connected, the plugin allows Search Atlas to push changes directly into the WordPress database rather than only overlaying them at runtime. This includes titles and meta descriptions, schema, page-level structural updates, and indexing and sitemap changes. Because changes are stored server-side, they are visible inside WordPress, editable by your team, readable by Google and LLMs, and cache-aware and persistent. ⚡ Indexing, Cache Control, and Technical Stability The plugin includes one-click Bing IndexNow integration, programmatic sitemap updates, and automatic submission of changes to search engines. It also provides intelligent cache clearing across WordPress cache, plugin-level cache, and other supported caching tools, preventing updates from being trapped behind stale cache layers. Full robots.txt management and sitemap generation are handled inside the plugin, removing the need for external SEO plugins to manage crawl directives. 🧾 Full Visibility, Logs, and Control Every action taken through the plugin is tracked and visible. Sync logs show what changes were made, when they were deployed, and which pages were affected. Compatibility and diagnostics tools let you view supported page builders and plugins, run configuration checks, and review error logs. A built-in Report an Issue tool sends full environment context directly to the WordPress plugin development team. 🎨 White Label and Secure Access For agencies, the plugin supports full white-labeling, including renaming the plugin, custom branding (name, colors, fonts), custom descriptions and author fields, password-protected access, and secure single sign-on between Search Atlas and WordPress. By consolidating technical SEO into a single execution environment, the Search Atlas WordPress Plugin ensures all optimizations remain visible and editable, cache conflicts are minimized, and strategy and deployment happen as one continuous workflow. Modern SEO demands more than analysis. By migrating from legacy SEO plugins to Search Atlas, teams eliminate tool conflict, reduce manual overhead, and unlock a fully agentic execution model, without sacrificing stability, history, or control. 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.

🚀 Revolutionizing Browser-Based SEO: the Search Atlas Chrome Extension V3

While the Search Atlas dashboard is where strategy lives, most SEO work happens directly in the browser: analyzing SERPs, auditing pages, and exploring competitor sites. The Search Atlas Chrome Extension brings fast, accurate, actionable SEO data directly into Google Chrome, turning everyday browsing into a real-time SEO workflow. 🧭 Landing on a Page: Immediate Context As soon as you land on a webpage with the extension enabled, a small status indicator appears under the Search Atlas icon showing the page's crawlability: green means the page is indexable and followable, red means the page is marked no-index, and a split indicator means no-index but follow. This lets you instantly detect issues, such as production pages accidentally left on no-index, before you even open the extension. ⚡ Mini Toolbar If enabled, a mini toolbar appears at the top of the page, giving you immediate access to URL Rating and Domain Rating, backlinks and referring domains, organic traffic, and Domain Power, along with quick access to settings. You can disable the toolbar entirely or add specific sites to an exclusion list. 📊 Opening the Extension: Page Summary Clicking the Search Atlas icon opens the on-page summary, a fast technical health check. It shows your heading structure (including missing or duplicated H1s), title tag and meta description with character count guidance, canonical tag configuration, robots meta directives, word count, and detected page language. From here you can also download the page's robots.txt and sitemap in one click. 🧩 Deep Analysis via Tabs For deeper inspection, the extension offers specialized tabs: a Headings tab showing the complete H1 through H6 hierarchy, a Link Status tab with a full link-level audit (internal and external links, anchor text, follow status, and placement, exportable as a CSV), an Image Audit tab surfacing missing alt text and titles, a Schema Markup tab presenting schema in a clean, toggle-based layout, and a Social Metrics tab previewing Open Graph and X (Twitter) cards. 🔁 Transition to the Dashboard When you are ready to go deeper, click Go to Dashboard. The current URL or domain is sent to Site Explorer, a full report runs automatically, and you gain access to historical traffic trends, keyword rankings, backlink profiles, and the economic value of organic traffic. 🔍 SERP-Level Analysis The extension also works directly inside Google Search results, showing keyword difficulty, average monthly search volume, cost per click, and authority metrics for every ranking domain. ⚙️ Extension vs Dashboard Use the Chrome Extension when you want to quickly audit a live page, analyze competitors while browsing, validate indexability and on-page structure, or evaluate SERPs without leaving Google. Use the Search Atlas dashboard when you need to run full site audits, analyze historical trends, manage projects and campaigns, or deploy fixes at scale. The extension and the dashboard are designed to work together. If the Search Atlas dashboard is your strategic command center, the Chrome Extension is your real-time execution layer out in the field. 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.

🔌 WordPress Plugin and Cloudflare CDN: Simultaneous Setup Guide

🧭 Overview You can use the Search Atlas WordPress plugin and Cloudflare CDN at the same time. The most important thing to get right is when you deactivate or reactivate the WordPress plugin relative to your Cloudflare CDN setup. Getting this order wrong is the most common reason customers see dashboard errors or data gaps when running both methods together. ⚠️ The Core Issue: Plugin Deactivation Timing The original question behind this article is specifically about when to deactivate the WordPress plugin during a Cloudflare CDN setup. Based on confirmed customer resolutions, the key guidance is: - Do not deactivate the WordPress plugin before your Cloudflare CDN setup is fully complete. If you deactivate the plugin too early — before Cloudflare is fully connected and your domain is proxying correctly — Search Atlas loses visibility into your site during that window, which can cause data gaps or dashboard errors. - Keep the plugin active throughout the Cloudflare setup process. Only consider deactivating or switching methods after Cloudflare is confirmed to be working end-to-end. - If you are not switching away from the plugin and simply want to run both simultaneously, there is no need to deactivate the plugin at any point — leave it active while you complete the Cloudflare CDN connection. ✅ Recommended Approach 1. Leave the WordPress plugin active while you begin your Cloudflare CDN setup. 2. Complete your Cloudflare connection — point your domain's DNS records to Cloudflare's nameservers and confirm the domain is proxying correctly inside your Cloudflare account. 3. Verify your Search Atlas dashboard is loading and syncing data correctly before making any changes to the plugin. 4. Only after confirming Cloudflare is fully working, decide whether you want to keep both methods running together or deactivate the plugin. If you are unsure which is right for your setup, contact our team before deactivating. 🔍 What to Check If You Already Deactivated the Plugin Too Early If you deactivated the WordPress plugin before Cloudflare was fully set up and are now seeing dashboard issues, here is what to do: - Reactivate the WordPress plugin from your WordPress admin area. - Confirm your Cloudflare setup is complete and the domain is proxying correctly. - Allow some time for data to resync, then check your Search Atlas dashboard again. - If data gaps or errors persist after reactivating, contact support with your site URL, the approximate time you deactivated the plugin, and a description of what you are seeing in the dashboard. 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.

🔌 Install and Set Up the OTTO WordPress Plugin

🧩 What Is the OTTO WordPress Plugin? OTTO is Search Atlas's AI-powered SEO automation tool. The OTTO WordPress plugin connects your WordPress site directly to the Search Atlas platform, allowing OTTO to deploy on-page SEO optimizations — such as title tags, meta descriptions, schema markup, and more — automatically, without manual edits inside WordPress. 📋 Before You Begin - You have an active Search Atlas account with OTTO enabled. - You have admin access to your WordPress site. - Your WordPress site is publicly accessible (not in maintenance mode or behind a login wall). ⚙️ Step 1: Activate OTTO for Your Site in Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 3. Click Create or select an existing site. 4. Enter your website URL and follow the on-screen prompts to create an OTTO session for your site. 5. Once the session is created, you will see a unique OTTO Connection Key on the setup screen. Copy this key — you will need it in Step 3. 🔽 Step 2: Install the Search Atlas Plugin on WordPress 1. Log in to your WordPress admin dashboard. 2. In the left menu, go to Plugins → Add New. 3. In the search bar, type Search Atlas. 4. Locate the official Search Atlas plugin in the WordPress admin plugin list and click Install Now. 5. Once installation is complete, click Activate. Alternatively, you can download the plugin file directly from Search Atlas and upload it via Plugins → Add New → Upload Plugin. 🔗 Step 3: Connect the Plugin to Your Search Atlas Account 1. After activating the plugin, go to Search Atlas → Settings in your WordPress left menu. 2. Paste the OTTO Connection Key you copied from Search Atlas into the connection field. 3. Click Connect. 4. A confirmation message will appear indicating that your site is successfully linked to your Search Atlas account. ✅ Step 4: Verify the Connection in Search Atlas 1. Return to your Search Atlas account, go to OTTO SEO in the left sidebar, and open SEO Automation. 2. Your site's status should now show as Connected. 3. OTTO is now ready to deploy SEO optimizations to your WordPress site. 🚀 Step 5: Deploy OTTO Optimizations With the plugin connected, you can return to the OTTO SEO section in Search Atlas at any time to review and deploy OTTO's recommended SEO tasks. When you approve and deploy a task, OTTO will automatically apply the changes to your live WordPress site through the plugin — no manual edits required. 🛠️ Troubleshooting Common Issues - Plugin not found in WordPress: Try searching for "Search Atlas" in the WordPress admin plugin list. If it still does not appear, contact support to get the direct plugin download link. - Connection Key not working: Make sure you copied the full key without extra spaces. Keys are session-specific — if you created a new OTTO session, generate a fresh key. - Site shows as Disconnected: Deactivate and reactivate the plugin in WordPress, then re-enter your connection key. - Changes not appearing on the live site: Clear your WordPress cache and any CDN cache after deploying optimizations. 💬 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.

🔌 Connect Node.js or Next.js to Search Atlas

🗺️ Overview Search Atlas supports direct publishing integrations with platforms like WordPress, Webflow, and Shopify through its built-in connector UI. If your site runs on a custom Node.js or Next.js backend, a native connector will not appear in the platform — this is expected behavior, not a bug. This article explains what to do if you want to use Search Atlas AI tools with a custom Node.js or Next.js project, and how to get the right guidance from our team. ✅ What Is Supported Out of the Box - Search Atlas has native, built-in connectors for select platforms (e.g. WordPress, Webflow, Shopify). - Custom backends — including Node.js and Next.js projects — do not have a dedicated connector in the platform UI. - Whether a custom integration is possible for your specific setup depends on your account plan and technical configuration. 📋 What to Prepare Before Contacting Support To get accurate guidance as quickly as possible, please have the following information ready when you reach out: - Your Search Atlas account email and plan type. - A brief description of your Node.js or Next.js project (e.g. how it is hosted, whether it is a headless CMS setup, and what you are trying to publish). - What you have already tried within the Search Atlas platform (e.g. which connector options you explored). - Any error messages or unexpected behavior you have encountered, including the exact wording and when it occurred. A member of our team will review your setup and confirm what integration options, if any, are available 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.

🔍 Set Up White-Label Domains with GoHighLevel

🔍 Overview Search Atlas allows agencies to host reports and dashboards under a custom branded domain using GoHighLevel (GHL) as the CMS layer. If your white-label domain link is not working, it typically means one or more steps in the DNS or platform configuration are incomplete. This article walks you through the general process for resolving white-label domain issues with GoHighLevel integration. ✅ Before You Begin Make sure you have the following ready before configuring your white-label domain: - Admin access to your GoHighLevel account - Access to your domain registrar (e.g., GoDaddy, Namecheap, Cloudflare) to manage DNS records - Admin access to your Search Atlas account - Your chosen subdomain or root domain (e.g., reports.youragency.com) ⚙️ Step 1: Add Your Domain in GoHighLevel Log in to your GoHighLevel account and locate the domain management area. Add the domain or subdomain you want to use for white-labeling. GoHighLevel will provide DNS records you must add to your domain registrar. Copy these DNS values before proceeding to the next step. 🛠️ Step 2: Update DNS Records at Your Registrar Log in to your domain registrar and navigate to the DNS management section for your domain. Add the DNS record(s) provided by GoHighLevel, using the host/subdomain prefix and target value it specifies. Save your changes and allow time for DNS propagation — this can take anywhere from a few minutes to 48 hours depending on your registrar and TTL settings. Before moving on, confirm that your subdomain resolves correctly to the GoHighLevel target. 🔗 Step 3: Connect Your Domain Inside Search Atlas Once DNS has propagated, you will need to complete the white-label domain configuration inside Search Atlas to activate your branded domain. Log in to your Search Atlas account with admin credentials and locate the white-label domain settings within the platform. Enter the domain or subdomain you configured in GoHighLevel and save your settings. Test your white-label domain link to confirm it loads your branded reports or dashboard without errors. Because the exact configuration steps inside Search Atlas may vary depending on your account setup, our support team can guide you through this process directly. When reaching out, please have the following ready: - Your Search Atlas account email and agency name - The exact domain or subdomain you are trying to connect (e.g., reports.youragency.com) - Confirmation that DNS has propagated, including the target your subdomain resolves to - The exact error message you are seeing and when it first appeared 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.

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

⚡ Search Atlas API workflow for automated SEO audits

Overview The Search Atlas API allows you to programmatically interact with your SEO audit data and integrate it into your own workflows or reporting tools. Common use cases include scheduling automated audits, pulling audit results into external dashboards, and chaining audit data with other tasks in your pipeline. Setting up an automated SEO audit workflow To build an automated SEO audit workflow with the Search Atlas API, follow these general steps: 1. Obtain your API key. Log in to your Search Atlas account, navigate to your account or developer settings, and locate your API key. Keep this key secure and include it in the authorization header of every API request. 2. Identify the project you want to audit. Each audit is tied to a specific project in your Search Atlas account. Note the project name or ID you intend to target with your API calls. 3. Trigger an audit via the API. Use the appropriate API endpoint to initiate an SEO audit for your project. Pass your project identifier and any required parameters in the request body according to the API documentation. 4. Poll for audit completion. Audits may take time to complete. Use the status endpoint (if available) to poll for completion, or set up a webhook if the API supports callback notifications when the audit finishes. 5. Retrieve and process the results. Once the audit is complete, call the results endpoint to fetch the audit data. Parse the response in your preferred programming language and route the data into your dashboard, reporting tool, or downstream workflow. 6. Schedule recurring audits. To automate audits on a schedule, use a task scheduler (such as cron, a cloud scheduler, or a workflow automation tool) to call the audit trigger endpoint at your desired frequency. Troubleshooting common issues If you encounter problems with your API workflow, check the following: - Confirm your API key is valid and included correctly in the request headers - Verify that the project name or ID in your request matches an existing project in your account - Review any error messages or HTTP status codes returned by the API — these usually indicate whether the issue is with authentication, request formatting, or account limits - Check whether your account plan includes API access and whether you have remaining API call quota 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.

🔍 Find Your Search Atlas Project UUID

🗺️ What Is a Project UUID and Why Do You Need It? A UUID (Universally Unique Identifier) is a unique alphanumeric string assigned to every project in Search Atlas. It looks like this: a1b2c3d4-e5f6-7890-abcd-ef1234567890. You may need it when contacting support, using the Search Atlas API, or troubleshooting a specific project such as RevRocket. 🧭 Method 1: Find the UUID Directly in the URL This is the fastest method and works in most cases. 1. Log in to Search Atlas and go to Left sidebar → OTTO SEO → Overview. 2. Click the project card you want (e.g., RevRocket) to open the project dashboard. 3. Look at the browser address bar. The URL will contain a long string of characters — that is your project UUID. For example: app.searchatlas.com/seo-automation-v3/a1b2c3d4-e5f6-7890-abcd-ef1234567890?category=... 4. Copy the UUID segment between /seo-automation-v3/ and ?category=.... 🛠️ Method 2: Use Browser Developer Tools (Network Tab) Use this method if the UUID does not appear directly in the URL bar. 1. Navigate to Left sidebar → OTTO SEO → Overview and open your project (e.g., RevRocket). 2. Open your browser's developer tools by pressing F12 on Windows/Linux or Cmd + Option + I on Mac. Alternatively, right-click anywhere on the page and select Inspect. 3. Click the Network tab at the top of the developer tools panel. 4. Make sure Fetch/XHR is selected in the filter row just below the tab bar. If you do not see any requests, press F5 or Cmd + R to reload the page. 5. Click on any request in the list that references your project. Look at the Request URL in the Headers panel on the right — it will contain the UUID as part of the endpoint path (e.g., /api/projects/a1b2c3d4-e5f6-7890-abcd-ef1234567890/). 6. Copy the UUID string — it always follows the pattern of 8-4-4-4-12 alphanumeric characters separated by hyphens. ✅ Quick Tips - Each project has its own unique UUID — make sure you have the correct project open before copying. - The UUID is the same regardless of which page or tab you are on within a project. - If you have multiple projects (e.g., RevRocket and others), open each one individually to retrieve its specific UUID. - UUIDs do not change over time, so you can save it for future reference. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔀 Why OTTO Plugin Creates Redirects Automatically

🔍 Overview Some Search Atlas customers notice that the OTTO WordPress plugin creates redirect rules on their website without an explicit manual instruction. This article explains what is happening and what to do if you experience this. ⚙️ What Is Happening OTTO is an AI-powered SEO automation tool. When it is active on a site, it is designed to apply on-page and technical SEO improvements automatically. However, we have received reports that the OTTO WordPress plugin is creating redirect rules that customers did not authorise or expect. If you are experiencing this issue, you are not alone — our team is aware of reports of this behaviour. 📋 What to Do Right Now Because this issue may require backend investigation, the most reliable next step is to contact our support team directly so we can look into your specific site. When you reach out, please have the following information ready: - Your Search Atlas project or site name — the name of the site where unexpected redirects are appearing. - Examples of the redirects created — the specific URLs being redirected, if you can locate them. Having this information ready will allow our team to investigate your case as quickly as possible and minimise disruption to your site. ⚠️ Important Note If you are concerned about further unauthorised changes to your site, you may consider temporarily deactivating the OTTO WordPress plugin from your WordPress admin dashboard while our team investigates. This will stop OTTO from applying any further automatic changes to your site. 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.

🔌 WordPress SEO Plugin Compatibility and Auto-Detection

🧩 Overview If you already use a WordPress SEO plugin alongside the Search Atlas WordPress plugin, questions may arise about how the two interact and whether any manual configuration is needed. The Search Atlas plugin is built with compatibility and automatic detection in mind, so that it can work within existing WordPress SEO setups. 🔍 How Automatic Detection Works The Search Atlas WordPress plugin includes automatic detection functionality designed to identify other active SEO plugins on your WordPress installation. This detection helps the plugin adjust its behaviour to avoid conflicts. The specific details of how detection is applied in your environment may vary — if you have questions about a particular configuration, our support team can advise. ⚙️ Do You Need to Manually Select Your SEO Plugin? In most cases, the automatic detection feature is intended to handle compatibility without requiring you to manually configure which SEO plugin is active. If you are unsure whether your current setup requires any additional steps, or if you notice unexpected behaviour after installing the Search Atlas plugin, contact support with the following details ready: - The name and version of your existing WordPress SEO plugin(s) - The version of the Search Atlas plugin you have installed - A clear description of the issue or behaviour you are seeing - Any error messages shown in your WordPress dashboard or browser console ⚠️ Plugin Conflicts and What to Do If you believe there is a conflict between Search Atlas and another active SEO plugin, gather the information listed above before reaching out. Our team will be able to review your specific setup and advise on the best course of action. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Supported plugins: Yoast SEO (free/premium), Rank Math, All in One SEO (AIOSEO), The SEO Framework. If using an unlisted plugin, auto-detection may not apply — monitor for duplicate meta output. Auto-detection prevents duplicate meta tags and defers to detected plugin for meta titles/descriptions; Search Atlas features (content optimisation, keyword tracking, reporting) continue fully.

📘 Connect Your Integrations in Search Atlas

Integrations allow you to connect your external platforms (Google, Facebook, LinkedIn, and more) to Search Atlas so you can manage performance, insights, and campaigns from a single dashboard. All integrations follow the same connection flow and can be accessed in one place. ⚙️ Where to Find Integrations 1. Click your avatar (top-right corner) 2. Go to Settings 3. Select Integrations (a sibling tab of Team Members) Here you’ll see all available services you can connect. 🔗 How to Connect Any Integration 1. Go to Settings → Integrations 2. Find the service you want to connect 3. Click ➕ Connect GBP Account (for Local → GBP Projects), Connect GSC Account, or Connect GA Account (for Site Metrics → GSC Performance) 4. A secure login popup will open 5. Enter your credentials 6. Approve permissions 7. Your account will be connected automatically 🔌 Available Integrations You can connect: - 🔍 Google Search Console - 📍🏢 Google Business Profile - 📊 Google Analytics - 📣 Google Ads - 📘 Facebook Ads - 👍 Facebook Pages - 📸 Instagram Pages - 🐦 X (Twitter) - 💼 LinkedIn ⚠️ Common Issues 1. Popup not opening → Enable popups or disable blockers 2. Wrong account → Log out and retry 3. Permissions denied → Reconnect and approve access 4. “No account connected” → Connection not completed Connecting your integrations centralizes your data and unlocks the full power of Search Atlas. The more connected your stack is, the more actionable your insights become.

🔌 WordPress Plugin Dashboard Is Read-Only by Design

🔍 Overview The Search Atlas WordPress plugin dashboard is intentionally read-only. This means the buttons and settings you see inside the plugin are for viewing data only — they are not designed to accept edits or changes directly. This is expected behaviour, not a bug. All changes to your SEO settings, content, and configurations must be made inside the main Search Atlas dashboard at your Search Atlas account. The plugin then reflects those changes on your WordPress site. ❓ Why Are the Plugin Dashboard Buttons Not Working? If you click buttons inside the WordPress plugin dashboard and nothing happens — or the controls appear greyed out or unresponsive — this is because the plugin interface is designed to display your Search Atlas data, not to let you edit it. ✅ Where to Make Your Changes To make changes that will apply to your WordPress site: 1. Log in to your Search Atlas account. 2. Navigate to the relevant tool or section where you want to make a change. 3. Make and save your changes inside the Search Atlas dashboard. 4. Your WordPress site will reflect the updated settings via the plugin. You do not need to take any additional action inside the WordPress plugin itself after saving changes in the main dashboard. 🔄 How the Plugin and Dashboard Work Together Think of the Search Atlas WordPress plugin as a display layer that connects your WordPress site to your Search Atlas account. The Search Atlas dashboard is where all SEO logic, configurations, and content settings are managed. The WordPress plugin reads those settings and applies them to your site. Any data shown inside the plugin dashboard is for reference only. 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.

🗺️ Migrate Sitemap Exclusion Settings From Yoast

🔍 Overview When switching from Yoast SEO to Search Atlas, one common step is recreating your sitemap exclusion rules. In Yoast, you can toggle off specific post types and taxonomies — such as author pages, category pages, and tag pages — so they are excluded from the XML sitemap. Search Atlas gives you the same control through its sitemap settings inside the WordPress plugin. This article explains what to prepare and how to get the right settings configured. ⚙️ Before You Begin Make sure the following prerequisites are in place before adjusting sitemap settings: - The Search Atlas WordPress plugin is installed and activated on your site. - You are logged in to your WordPress admin dashboard. - You have already deactivated Yoast SEO (or at minimum disabled the Yoast sitemap feature) to avoid duplicate sitemaps conflicting with each other. - You have a note of which URL types were excluded in Yoast — check your old Yoast settings under Yoast SEO → Search Appearance → Content Types and Taxonomies before fully removing the plugin. 🛠️ How to Exclude URL Types From Your Sitemap in Search Atlas To replicate your Yoast sitemap exclusion rules inside the Search Atlas plugin, follow these general steps: 1. Log in to your WordPress admin dashboard. 2. In the left-hand menu, click Search Atlas to open the plugin settings. 3. Navigate to the Sitemap section within the plugin. 4. Within the sitemap settings, locate the controls for post types (e.g. author pages, custom post types) and disable or exclude each type you do not want included in your sitemap. 5. Similarly, locate the controls for taxonomies (e.g. category pages, tag pages, custom taxonomies) and disable or exclude each one you want removed from the sitemap. 6. Save your settings once all exclusions are configured. 7. After saving, verify your sitemap by visiting yoursite.com/sitemap.xml and confirming that the excluded URL types no longer appear. The exact names of controls and settings may vary depending on your plugin version. If you cannot locate the relevant options, reach out to our support team with your plugin version number and a description of which URL types you need to exclude. 📋 Common Yoast Exclusions and Their Search Atlas Equivalents Use the table below as a quick reference when recreating your exclusions: - Yoast: Author archives set to "noindex" → Search Atlas: Find the author pages or author archives option within the sitemap settings and disable it. - Yoast: Categories excluded from sitemap → Search Atlas: Find the categories option under the taxonomy-related sitemap controls and disable it. - Yoast: Tags excluded from sitemap → Search Atlas: Find the tags option under the taxonomy-related sitemap controls and disable it. - Yoast: Custom post type excluded → Search Atlas: Find the corresponding custom post type within the sitemap settings and disable it. If you are unsure which settings correspond to your specific Yoast exclusions, have the following ready when contacting support: your plugin version, the URL types you need to exclude, and a screenshot or description of what you currently see in the Search Atlas sitemap settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 White-Label Integration with GHL: Setup, GMB Support, and UK Eligibility

Search Atlas offers a full white-label integration with GoHighLevel (GHL), allowing agencies to deliver SEO reporting and tools under their own brand. This article answers the most common questions about GHL integration, white-label capabilities, Google Business Profile (GMB) support for non-GHL clients, and eligibility for UK-based accounts. 🤝 Does Search Atlas Integrate with GHL? Yes. Search Atlas has a dedicated white-label integration built for agencies using GoHighLevel. This integration allows you to embed Search Atlas reporting and tools directly into your GHL sub-accounts, giving your clients a seamless, branded experience without ever seeing the Search Atlas name. - White-label branding: Your logo, colors, and domain are applied throughout the client-facing experience. - Sub-account syncing: Reports and quotas are managed per GHL sub-account. - Simplified settings: GHL accounts have a streamlined Integrations page — unrelated integrations (like Slack) and internal references are automatically hidden to keep the interface clean for your workflow. If you are migrating from another white-label provider (such as Vendasta) into GHL, our team has dedicated migration support to ensure your client data, reports, and quotas transfer correctly. ⚙️ How to Set Up White-Label for GHL To configure white-label settings for your agency: 1. In the header, click the apps-grid icon → More Features → Agency Hub. 2. Configure your branding details, including logo, domain, and color scheme. 3. Set up your account Quotas to manage usage across client sub-accounts. 4. If you need to top up usage, visit Go to billing to add more Bulk Analysis URLs or Backlink Research credits as needed. Once configured, your GHL clients will only see your branded interface — Search Atlas operates entirely behind the scenes. 📍 Can I Use Search Atlas for Non-GHL Clients Needing GMB Help? Absolutely. Search Atlas is not limited to GHL-connected clients. If you manage clients who need help with their Google Business Profile (GMB) — including local SEO optimization, listing management, and review tracking — you can use Search Atlas tools independently of GHL. - You can create and manage reports for any client through Reports in the left sidebar, regardless of whether they are connected via GHL. - Local SEO tools, including GMB-focused reporting, work the same for both GHL and non-GHL client accounts. - You are not required to use GHL to access any core Search Atlas features — GHL is simply an optional white-label delivery method for agencies already using that platform. 🇬🇧 Is Search Atlas Available for UK-Based Clients? Yes. Search Atlas fully supports UK-based clients and campaigns. There are no regional restrictions preventing you from setting up reports, tracking rankings, managing backlinks, or optimizing Google Business Profiles for clients located in the United Kingdom. - You can create location-specific reports for UK clients the same way you would for any other region. - Local SEO and GMB tools support UK addresses, postal codes, and local search data. - White-label GHL integration works the same regardless of your agency's or client's country of operation. 🛠 Troubleshooting Common GHL Issues If you experience any of the following, our team has already resolved similar issues and can help quickly: - Incorrect quota display: Some GHL plans previously showed inaccurate quota counts for certain items — this has been corrected, but if you still see discrepancies, our team can review your account. - Unrelated integrations appearing: Slack and other non-GHL integrations should not appear on your Settings page if you are on a GHL account. If you still see these, let us know. - Outdated domain references: Some GHL accounts previously saw references to internal Search Atlas domains on the Integrations page — these have been removed for a cleaner white-label experience. 💬 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.

🔄 Switch Websites in Search Atlas WordPress Plugin

🗺️ Overview If you want to stop tracking one website in Search Atlas and start fresh with a different one, you need to complete two steps: remove the existing website from your Search Atlas account, and clear the UUID (unique identifier) from the Search Atlas WordPress plugin on your old site. Because the exact steps vary depending on your account setup, our support team will walk you through this process directly. ❓ What Is a UUID and Why Does It Matter? When you connect a WordPress site to Search Atlas, the plugin stores a UUID (Universally Unique Identifier) that links your WordPress site to your specific Search Atlas account. If you want to connect a different website, you must remove this UUID from the plugin — otherwise the old connection remains active and your new site may not link correctly. ⚠️ Before You Begin - Make sure you have Administrator access to the WordPress site you are disconnecting. - Export or save any data from Search Atlas that you want to keep before removing the website from your account. - Have your new website URL ready to add after the process is complete. 🪜 What the Process Involves Switching websites in the Search Atlas WordPress plugin requires two main actions: 1. Removing the existing website from your Search Atlas account on the platform side. 2. Clearing the UUID stored in your Search Atlas WordPress plugin on the old site, so the plugin is no longer linked to your account. Once both steps are complete, you can connect your new website to Search Atlas and set up the plugin on the new site. Because the exact steps within the platform and plugin depend on your account configuration, our support team will guide you through each action to ensure the switch is completed correctly. 📋 What to Have Ready When You Contact Support - The URL of the website you want to disconnect - The URL of the website you want to connect - Your Search Atlas account username or email - Confirmation that you have Administrator access to the WordPress site you are disconnecting If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Search Atlas WordPress Plugin Impersonation Message Explained

Overview When configuring the Search Atlas WordPress plugin, you may see a message related to impersonation. This article explains what that message means and what steps to take next. What Does This Message Mean? An impersonation message in the Search Atlas WordPress plugin indicates that the session currently connected to your plugin may be associated with an account other than your own. This can happen during or after a support or onboarding interaction where account access was involved. If you are seeing this message, it is important to pause any configuration work until the situation is clarified, to ensure that any changes you make are applied to the correct account. What You Should Do Because the exact cause of the impersonation message can vary depending on your account setup and recent activity, the best course of action is to contact the Search Atlas support team directly. A support agent will be able to review your account, explain why the message is appearing, and guide you through the correct next steps for your specific situation. When you reach out, please have the following information ready: - Your Search Atlas account email address - The name of the WordPress site where you are seeing the message - A description of what you were doing in the plugin when the message appeared - Any screenshot of the message if possible 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.

🔗 Reconnect Search Atlas After Anthropic Cloud Migration

🧭 Overview If you recently switched or migrated your Anthropic Cloud account, your existing Search Atlas connection will be lost because the Model Context Protocol (MCP) configuration is tied to your account credentials. To restore the integration, you need to re-add the Search Atlas MCP URL inside your Anthropic Cloud account settings. 🔑 What Is the Search Atlas MCP URL? Search Atlas connects to Anthropic Cloud via a Model Context Protocol (MCP) endpoint. This URL tells Anthropic Cloud where to find and communicate with the Search Atlas toolset. When you change your Anthropic account, this connector is not carried over automatically — you must add it again manually. The Search Atlas MCP URL is: https://mcp.searchatlas.com/mcp/ ⚙️ How to Restore the Connection To restore your Search Atlas connection after an Anthropic Cloud account migration, you will need to re-add the Search Atlas MCP URL to your new Anthropic Cloud account. The exact navigation steps may vary depending on your Anthropic Cloud interface, so follow the MCP connector setup flow within your account settings and enter the MCP URL above when prompted for a server or integration endpoint. If you are unsure where to locate the MCP connector setup in your Anthropic Cloud account, please reach out to our support team (see below) and have the following ready: - Your Search Atlas project or workspace name - Confirmation of which Anthropic Cloud account (email address) you migrated to - Any error message you see when attempting to connect ✅ Verifying the Integration Is Working After adding the MCP URL in your new Anthropic Cloud account, confirm the connection is working by testing an AI-powered feature in Search Atlas. If responses populate correctly, the integration has been restored. If the connection still fails, double-check that the MCP URL was entered exactly as shown above with no trailing spaces or extra characters. ⚠️ Common Issues After Account Migration - Multiple Anthropic accounts: Make sure you are logged into the correct new account when adding the MCP URL. Connectors added to the wrong account will not link to your Search Atlas workspace. - MCP URL added but still not connecting: Try removing the entry and re-adding it. Occasionally a partial save during initial setup can cause the connection to fail silently. 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.

🚀 WordPress Domain Migration With SEO Preservation

🗺️ Overview Migrating a WordPress site to a new domain is one of the most SEO-sensitive tasks you can perform. Done correctly, you retain rankings, backlink equity, and indexed pages. This article walks you through the full process — from pre-migration data export to post-migration validation inside Search Atlas — and covers common project setup errors you may encounter along the way. 📦 Step 1: Export Your Current URL and Metadata Inventory Before touching anything on your site, capture a full snapshot of your existing SEO data. This gives you a baseline to compare against after migration and helps you catch any missing pages or broken metadata. 1. In Search Atlas, go to Left sidebar → Site Metrics → Pages. 2. Use the Filters and Columns options to display URL, page title, and meta description for all indexed pages. 3. Click History to save the current state as a reference point. 4. Export the data using the export option in the toolbar and save the file locally as your pre-migration inventory. Keep this file. You will re-run the same export after migration to compare old URLs against new ones and confirm no pages were lost. ⚙️ Step 2: Prepare Your WordPress Site for Migration Complete these steps inside WordPress and your hosting environment before changing any DNS settings. - Install your new domain on the destination server and verify it loads correctly before proceeding. - Clone your WordPress database and files to the new domain using a plugin such as Duplicator or All-in-One WP Migration, or via a manual export from phpMyAdmin. - Update Site URL settings: In WordPress, go to Settings → General and update both the WordPress Address and Site Address fields to the new domain. - Run a database search-and-replace to update all internal links and image paths. Use a tool such as Better Search Replace to replace every instance of the old domain with the new one in the database. - Test the new domain thoroughly — check pages, images, forms, and any third-party integrations — before going live. 🔗 Step 3: Set Up 301 Redirects on Your Old Domain 301 redirects tell search engines that your content has permanently moved. This is the single most important step for preserving SEO equity. 1. Add a wildcard 301 redirect in your old domain's .htaccess file (Apache) or server configuration (Nginx) that points every old URL to its exact equivalent on the new domain. 2. For example, olddomain.com/blog/post-slug should redirect to newdomain.com/blog/post-slug — not just to the homepage. 3. Test a sample of redirects using an HTTP status checker before submitting anything to Google. 4. Submit your new XML sitemap to Google Search Console under the new domain property. Also submit a Change of Address request in Google Search Console to accelerate the transition. 📊 Step 4: Add Your New Domain to Search Atlas and Validate Once the new domain is live and redirects are confirmed, add it as a project in Search Atlas and run a fresh analysis. 1. Go to Left sidebar → Site Metrics → All Sites and click Analyze. 2. Enter your new domain URL and start the analysis. 3. Once the project is saved, navigate to Site Metrics → Pages and export a new URL and metadata inventory. 4. Compare this export against your pre-migration snapshot to confirm all pages are present and metadata is intact. 5. Use Site Metrics → Position Changes to monitor keyword ranking changes over the following weeks. 🛠️ Fixing Common Project Setup Errors Some customers encounter validation errors when setting up a new project or connecting platform integrations. Here are the most common causes and fixes. - LinkedIn profile validation error: This typically occurs when the URL entered does not match the expected format. Make sure you are entering a full, public LinkedIn profile or company page URL (for example, https://www.linkedin.com/company/your-company-name). Personal profile URLs with custom slugs may not validate — try using the standard format. Also confirm the profile is set to public visibility. - Domain not resolving during project setup: If you add a domain before DNS propagation is complete, the platform may return an error. Wait 24–48 hours after a domain change before adding the new domain as a project. - Duplicate project warning: If the old domain was already saved as a project, the new domain will create a separate entry. This is expected behaviour. You can archive the old domain project once migration is complete by managing it under Site Metrics → All Sites. - Sitemap errors during crawl: If your sitemap was regenerated during migration, ensure the sitemap URL is correct and publicly accessible. Update the sitemap URL inside the project settings if needed. ✅ Post-Migration SEO Checklist - All old URLs return a 301 redirect to the correct new URL. - New XML sitemap is submitted to Google Search Console. - Change of Address request submitted in Google Search Console. - New domain added and analyzed in Search Atlas Site Metrics. - Pre- and post-migration URL inventories compared — no missing pages. - Keyword rankings monitored weekly for the first 60 days. - Backlinks pointing to the old domain are tracked and outreach prioritised for high-value links. 💬 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.

🗺️ WordPress Sitemap Management with RankMath

Overview If your WordPress sitemap has a duplicate homepage, contains pages it shouldn't (like your site's header or footer templates), or is missing pages you expect to see, the fix lives inside your RankMath SEO plugin settings — not inside Search Atlas. This article walks you through each issue step by step. Fix a Duplicate Homepage in the Sitemap A homepage typically appears twice because WordPress registers it under two different URLs — the root URL (yourdomain.com/) and a static front page (yourdomain.com/home/). RankMath may include both. 1. In your WordPress dashboard, go to Settings → Reading. 2. Confirm Your homepage displays is set to A static page, and the correct page is selected as the Homepage. 3. Open your RankMath Sitemap settings and review the options that control which URLs are included. Disable or adjust any setting that causes both the root URL and the static front page to be added simultaneously. 4. Open your sitemap at yourdomain.com/sitemap_index.xml and verify the homepage appears only once after saving. If you previously had a page titled "Home" that is no longer your front page, set that old page to Draft or apply a noindex tag via RankMath's per-page settings to remove it from the sitemap. Remove Header and Footer Pages from the Sitemap WordPress themes that use block-based or full-site editing (FSE) sometimes register header and footer templates as individual pages, and RankMath may pick them up. There are two general approaches to exclude them. Option 1 — Noindex the page (recommended): 1. Open the page in the WordPress editor. 2. Locate the RankMath SEO meta box or sidebar panel for that page. 3. Find the Robots Meta setting and set it to No Index. 4. Save or update the page. RankMath will automatically remove noindexed pages from your sitemap. Option 2 — Exclude the post type entirely: 1. Go to your RankMath Sitemap Settings. 2. Locate the tab or section for the relevant post type (e.g., Pages). 3. Disable sitemap inclusion for any post type that only contains template pages you never want indexed. Note: Noindex removes the page from both the sitemap and search engine indexes. If you only want to hide a page from the sitemap without fully noindexing it, consult the RankMath documentation for the specific toggle or option available in your version of the plugin. Diagnose Missing Pages in the Sitemap If a page you expect to see is absent from your sitemap, work through the following checks: - Confirm the page is Published (not Draft, Pending, or Private). - Open the page in the WordPress editor and check that RankMath's Robots Meta setting is not set to No Index. - Verify that the page's post type is enabled for sitemap inclusion in your RankMath Sitemap Settings. - Clear any sitemap cache inside RankMath, then re-check yourdomain.com/sitemap_index.xml. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Search Atlas 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.

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

🔌 Integrating Search Atlas with Third-Party Website Builders

🧩 How Search Atlas Integrates with Your Website Search Atlas uses a pixel-based integration model to connect with your website. This means a small snippet of tracking code — called a pixel — is placed once in the <head> section of your website's HTML. Once installed, Search Atlas can begin monitoring your site's performance data automatically. This approach works with virtually any website platform, including Lofty.com, WordPress, Squarespace, Wix, Webflow, and other third-party website builders that allow custom code in the page header. 🔐 Does Search Atlas Need Access to My Website Editor? No. Search Atlas does not require direct access to your website editor, your Lofty.com account, or any backend credentials. All features — including site performance tracking, automated content recommendations, and blog creation workflows — operate through the pixel connection and the Search Atlas platform itself. You remain in full control of your website at all times. Search Atlas never modifies your pages, publishes content, or changes settings directly inside your editor. 🛠️ How to Install the Search Atlas Pixel on Lofty.com To connect your Lofty.com website to Search Atlas, you need to place the Search Atlas pixel in the global <head> tag of your site. This ensures the pixel loads on every page automatically — you only need to add it once. 1. Log in to your Search Atlas account and navigate to Left sidebar → Site Explorer. 2. Select your website project or create a new one if you have not added your site yet. 3. Locate your unique tracking pixel snippet within the site settings panel and copy it to your clipboard. 4. Log in to your Lofty.com account and open your website editor. 5. Navigate to your site's global header settings. In Lofty.com this is typically found under Website Settings → Custom Code → Header Code (the exact label may vary based on your Lofty plan or template). 6. Paste the Search Atlas pixel snippet into the header code field. 7. Save and publish your changes. 8. Return to Search Atlas and allow up to 24 hours for data to begin populating in your dashboard. ✅ What Works After the Pixel Is Installed Once your pixel is active, Search Atlas can deliver the following without requiring any further access to your website editor: - Site performance tracking — monitor rankings, traffic trends, and technical health from the Site Explorer section. - Keyword insights — use Left sidebar → Keywords → Keyword Magic and Left sidebar → Keywords → Rank Tracker to research and track keywords relevant to your site. - Keyword Gap analysis — identify opportunities versus competitors via Left sidebar → Keywords → Keyword Gap. - Content creation workflows — build and optimise blog drafts and page content inside Search Atlas. You then copy or export finished content and publish it yourself inside Lofty.com. Search Atlas generates content recommendations and drafts within its own platform. Publishing that content to your live website is always a manual step you control inside your own editor. ⚠️ Common Setup Questions What if Lofty.com does not show a custom code or header field? Some Lofty plans restrict custom code insertion. Check your plan level in Lofty's account settings or contact Lofty's support team to confirm whether your plan supports header code customisation. Search Atlas requires this capability to function on any third-party builder. Can I place the pixel on just one page? Placing the pixel only on a single page limits tracking to that page alone. For full site monitoring, always add the pixel to your global header so it loads site-wide. How do I confirm the pixel is working? After 24 hours, return to Left sidebar → Site Explorer in Search Atlas. If data is populating, the pixel is active. If the dashboard still shows no data after 48 hours, double-check that the snippet was saved in the correct header field and that your pages have been published. 💬 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.

🔌 Publish Search Atlas Content to Loveable via API

🗺️ Overview If your Loveable site does not support the OTTO Pixel, you can still publish content directly from Search Atlas using the Search Atlas REST API. This guide walks you through the full workflow: generating your API key, retrieving your content, and posting it to your Loveable site programmatically. 🔑 Step 1: Generate Your Search Atlas API Key Before you can make any API calls, you need a valid API key from your Search Atlas account. 1. Log in to Search Atlas and go to your Account Settings (click your avatar in the top-right corner). 2. Navigate to the API or Integrations tab. 3. Click Generate API Key. 4. Copy the key and store it securely. You will not be able to view it again after leaving the page. All API requests must include this key in the request header as Authorization: Bearer YOUR_API_KEY. 📄 Step 2: Retrieve Your Content from Search Atlas Once authenticated, use the content endpoint to fetch the article or page you want to publish. Endpoint: - Method: GET - URL: https://api.searchatlas.com/v1/content/{content_id} - Header: Authorization: Bearer YOUR_API_KEY Replace {content_id} with the ID of the piece of content you want to publish. You can find the content ID in the URL when you open any article inside the Search Atlas platform. Example response fields you will use: - title — The page or article title. - body_html — The full HTML content of the article, ready to post. - meta_description — The SEO meta description. - slug — The recommended URL slug for the page. 🌐 Step 3: Post the Content to Your Loveable Site Loveable supports custom content publishing through its own project API. You will use the content retrieved in Step 2 as the payload for your Loveable API call. 1. Log in to your Loveable account and open your project settings to locate your Loveable Project API Key and Project ID. 2. Construct a POST request to the Loveable content endpoint. The exact endpoint path is defined in your Loveable project's API documentation, but a typical structure is: https://api.lovable.dev/projects/{project_id}/pages 3. Set the request headers to include both your Loveable API key and Content-Type: application/json. 4. Build the JSON body using the fields returned by Search Atlas in Step 2. A standard payload looks like this: - title: value from Search Atlas title field - content: value from Search Atlas body_html field - slug: value from Search Atlas slug field - meta_description: value from Search Atlas meta_description field Send the POST request. A successful response from Loveable will return a 201 Created status and the URL of the newly published page. 🤖 Step 4: Automate the Workflow (Optional) If you want to publish content at scale without repeating these steps manually, you can automate the full pipeline using a tool like Zapier, Make (formerly Integromat), or a custom script. 1. Set a trigger — for example, when a new article is marked as ready inside Search Atlas. 2. Use an HTTP action to call the Search Atlas GET endpoint and retrieve the content. 3. Map the response fields to a second HTTP action that posts to your Loveable project endpoint. 4. Log the Loveable response URL so you have a record of every published page. This approach lets you publish dozens of pages without any manual copy-paste steps. ⚠️ Common Issues and Fixes - 401 Unauthorized: Your API key is missing or incorrect. Double-check the Authorization header in both your Search Atlas and Loveable requests. - 404 Not Found: The content ID or Loveable project ID is wrong. Verify both values in their respective platform settings. - 422 Unprocessable Entity: A required field in the Loveable payload is missing or formatted incorrectly. Confirm that title and content are always included. - Content appears unstyled in Loveable: Loveable may need you to link your site's CSS stylesheet separately from the content body. Check your Loveable theme settings. 💬 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.

🔌 WordPress Plugin Compatibility and Auto-Detection Explained

🧩 Overview If you use a WordPress SEO plugin such as Yoast SEO, Rank Math, or All in One SEO, you do not need to remove or disable it before installing the Search Atlas WordPress Plugin. Search Atlas is designed to work alongside other SEO plugins and automatically detects which one you have active on your site. 🔍 How Auto-Detection Works When the Search Atlas WordPress Plugin is activated, it scans your WordPress environment and identifies any active, compatible SEO plugin. This detection happens automatically in the background — no setup steps or manual input are required from you. Once detected, Search Atlas adjusts its behaviour to avoid conflicts with the other plugin. This means: - Duplicate meta tags are prevented automatically. - Search Atlas defers to the detected plugin for on-page SEO fields it already manages, such as meta titles and meta descriptions. - Features unique to Search Atlas — including content optimisation, keyword tracking, and reporting — continue to function fully regardless of which SEO plugin is active. ✅ Supported SEO Plugins Search Atlas auto-detection is compatible with the most widely used WordPress SEO plugins, including: - Yoast SEO (free and premium) - Rank Math - All in One SEO (AIOSEO) - The SEO Framework If you are using a plugin not listed above, Search Atlas will still activate normally. However, automatic conflict resolution may not apply, and you should monitor your site for any duplicate meta output. ⚙️ Is There a Manual Configuration Option? At this time, there is no setting inside the Search Atlas WordPress Plugin that lets you manually specify which SEO plugin you are using. Detection is fully automatic. You do not need to select or name your other plugin anywhere in the Search Atlas interface. If auto-detection does not appear to be working correctly — for example, if you notice duplicate meta tags in your page source — try the following steps: 1. Deactivate and then reactivate the Search Atlas WordPress Plugin from your WordPress Plugins screen. This triggers the detection process again. 2. Confirm that only one other SEO plugin is active at a time. Running two third-party SEO plugins simultaneously alongside Search Atlas can cause detection issues. 3. Clear your WordPress and server-side caches after reactivating the plugin. 4. Check your page source (right-click a page and select View Page Source) and search for duplicate og:title or description meta tags to confirm whether a conflict exists. 🚫 Do I Need to Disable My Other SEO Plugin? In most cases, no. You can keep your existing SEO plugin active. Many customers run Yoast SEO or Rank Math alongside Search Atlas without any issues. Your existing SEO plugin settings, metadata, and configurations will remain intact. You may choose to disable your other SEO plugin if: - You want to use Search Atlas as your sole on-page SEO management tool. - You are experiencing persistent meta tag conflicts that reactivation does not resolve. - Your site speed audit flags redundant plugin overhead as a performance concern. If you decide to switch fully to Search Atlas for on-page SEO, export or document your existing meta titles, meta descriptions, and schema settings from your current plugin before deactivating it, so nothing is lost during the transition. 💬 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.

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

🔌 Reconnect Your Yesly Integration

Overview If your Yesly integration has become disconnected — whether during an active support session or after a session was closed — our team can help you get it reconnected. Because the reconnection process for Yesly integrations is handled with agent assistance, this article explains what to expect and how to get help quickly. What to Know Reconnecting a Yesly integration is something our support team can assist you with directly. If your integration is showing as disconnected or stopped syncing, no data is lost — the connection simply needs to be restored. This can happen mid-session or at any point after a support interaction has ended. In either case, you do not need to start a new process from scratch; the team can pick up where things left off. What to Have Ready When You Contact Support To help our team reconnect your Yesly integration as quickly as possible, please have the following information ready: - Your Search Atlas account email address - The name of the workspace or project where the Yesly integration should be active - A brief description of when the disconnection occurred (e.g., during a support session, after a password change, or at an unknown time) - Any error messages you may have seen, including the exact wording if possible Next Steps Once you reach out, a member of our team will verify your integration details and restore the connection on your behalf. You will be notified once the integration is active again and syncing normally. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 How to Connect UpContent to LinkedIn via Search Atlas

This article explains how to use UpContent alongside Search Atlas to share curated third-party content to LinkedIn. Because there is no native UpContent integration built into the Search Atlas platform, the workflow relies on a manual hand-off process. The steps below give you the clearest path to move content from UpContent into a LinkedIn post. 🔍 Common Causes of Confusion Customers often expect a one-click UpContent sync inside Search Atlas. That direct integration does not exist today. Instead, UpContent is used as a content discovery and curation tool, and you bring that content into your LinkedIn workflow manually. The steps below make that process concrete and repeatable. 🛠️ Step-by-Step 1. Log in to UpContent and open the collection or topic feed that contains the article or piece of content you want to share. 2. Copy the article URL from the content item you have selected in UpContent, along with any accompanying text you want to use in your post. 3. Open LinkedIn in a new browser tab and navigate to your profile or your company page, depending on where you want to post. 4. Start a new post on LinkedIn using the post creation option available on your feed or company page. 5. Paste the article URL into the LinkedIn post composer and add any caption or commentary you want to accompany the link. 6. Select your audience and publishing options as needed within LinkedIn's post composer. 7. Publish or schedule your post using the options available in LinkedIn's post composer. ✅ How to Confirm It Worked After posting, navigate directly to your LinkedIn profile or company page and locate the post in your activity feed to confirm it published successfully with your intended content and link. 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.

🗂️ WordPress SEO Setup: A 12-Step Checklist for Website Owners

Why a Structured WordPress SEO Checklist Matters Launching a WordPress site without a clear setup process often leads to technical SEO problems that are costly to fix later — slow load times, insecure connections, poor URL structures, and disorganized content. Following a structured checklist from the start ensures your site is built on a solid foundation before you publish a single piece of content. Step 1: Select a Hosting Provider Your hosting environment directly affects your site's speed, security, and overall SEO performance. Managed WordPress hosting is the recommended choice for most WordPress users because providers configure the server environment specifically for that CMS. When evaluating hosting providers, consider the following factors: - Storage and bandwidth: Ensure the plan provides enough resources to store your files and handle your expected traffic without throttling. - Speed and optimization: Server response time is a core ranking factor. Slow hosting undermines even well-optimized content. - Security features: Look for DDoS protection, malware scanning, encryption support, and automatic backups. - Managed updates: Managed WordPress hosts typically handle core updates and technical maintenance on your behalf. - Customer support: Responsive, knowledgeable support reduces downtime and resolves issues faster. Step 2: Register Your Domain Name Your domain name is your site's address on the internet. It is separate from your hosting account, which stores your actual files. Both are required to run a WordPress website. Choose a domain name registrar that is authorized by ICANN (Internet Corporation for Assigned Names and Numbers). When selecting a registrar, consider pricing, ease of use, customer support quality, and domain management tools. Best practices for domain selection include: - Search for availability across multiple extensions (.com, .net, .org) if your preferred name is taken. - Keep the domain short, memorable, and relevant to your brand or topic. - Enable domain privacy protection to shield your personal contact information from public WHOIS records. - Choose a registration period that makes sense for your commitment to the project — longer terms often cost less annually. - Verify your contact information after registration, as registrars typically require email confirmation. Step 3: Install WordPress WordPress can be installed manually or through automated tools. Local development tools handle installation automatically and are useful for building and testing sites before going live. Manual installation involves downloading the WordPress package, creating a database, configuring a settings file, uploading files via FTP, and running the installation script. Regardless of method, ensure your server meets WordPress's minimum requirements for PHP version and database type before beginning. Step 4: Install a Content Delivery Network (CDN) A CDN distributes your static website assets (images, scripts, stylesheets) across servers in multiple geographic locations. When a visitor loads your site, the CDN serves files from the server closest to them, reducing latency and improving load times globally. Faster load times contribute directly to better Core Web Vitals scores, which are a confirmed Google ranking factor. For WordPress, CDN integration is typically handled through a dedicated plugin that connects your site to your chosen CDN provider. Step 5: Acquire and Activate an SSL Certificate SSL (Secure Sockets Layer) encrypts the connection between your server and your visitors' browsers. Sites with SSL display https:// in the URL and a padlock icon in the browser address bar. HTTPS is a confirmed (though lightweight) Google ranking signal, and browsers actively warn users when they visit non-HTTPS pages. Many managed hosting providers offer free SSL certificates through services like Let's Encrypt. After installing the certificate, ensure WordPress is configured to serve all pages over HTTPS and that no mixed content errors exist. Step 6: Choose a WordPress Theme Your theme controls how your site looks and, importantly, how it performs. Theme quality has significant SEO implications because bloated or poorly coded themes can slow page load times and introduce accessibility issues. WordPress themes generally fall into these categories: - Block themes: Built for the full-site editor introduced in WordPress 5.9, offering maximum flexibility with the block-based editing system. - Classic themes: Use the traditional PHP template system and the Customizer for design control. - Hybrid themes: Combine elements of both classic and block-based approaches. When choosing a theme, prioritize performance (measured with tools like PageSpeed Insights), accessibility compliance, mobile responsiveness, and active maintenance from the developer. Step 7: Customize Your Theme After selecting a theme, configure its design settings to match your brand. Block themes use the Site Editor for full-site customization. Classic themes use the Customizer. More advanced visual customization is possible through page builder plugins, though these can add code overhead that affects performance. Keep customizations focused on usability and readability. Well-structured layouts, clear typography, and logical navigation all contribute to positive user experience signals that influence SEO. Step 8: Install an SEO Plugin A dedicated SEO plugin extends WordPress's default functionality to cover on-page optimization, technical SEO settings, XML sitemaps, structured data, and more. Search Atlas offers a WordPress plugin that connects your site to its broader suite of SEO tools, including OTTO SEO for automated optimization tasks and Site Auditor for ongoing technical health monitoring. Step 9: Activate Automated SEO Assistance Once your SEO plugin is in place, configuring automated SEO support saves significant time. OTTO SEO, available through Search Atlas, handles ongoing technical fixes, on-page improvements, and content optimization tasks. Automated SEO tools are particularly valuable for site owners managing multiple pages or multiple client sites. Step 10: Configure Categories and Tags WordPress uses categories and tags as its primary content taxonomy system. Properly structured taxonomies help search engines understand your site's topic architecture and improve internal linking and crawlability. Best practices for categories and tags: - Categories should represent your broadest content topics. Every post should belong to at least one category. Avoid creating too many top-level categories — a flat, manageable structure is easier for both users and crawlers. - Tags should represent specific subtopics or themes that appear across multiple posts. Avoid creating a unique tag for every post, as this creates thin, duplicate-prone archive pages. - Optimize category and tag archive pages with unique descriptions and relevant on-page content rather than leaving them as empty default index pages. - Consider applying a noindex directive to tag archives if they produce thin or low-value pages. Step 11: Configure Permalink Settings Permalinks are the permanent URLs for your pages and posts. WordPress allows you to customize the URL structure through its Settings menu. The default numeric URL format (e.g., /?p=123) provides no SEO value and is difficult for users to understand. Best practices for permalink configuration: - Use the Post name structure (/sample-post/) for clean, readable, keyword-relevant URLs. - Set your permalink structure before publishing content. Changing it after publishing creates broken links and requires redirects. - Keep URLs short, descriptive, and free of stop words where possible. - After changing permalink settings, save them — WordPress automatically regenerates your .htaccess file to support the new structure. Step 12: Create and Publish Optimized Content With your technical foundation in place, content creation is the ongoing work of SEO. Every page and post you publish should be built around a clear target keyword, organized with proper heading hierarchy (H1, H2, H3), and written to satisfy the search intent behind that keyword. Key content optimization principles: - Use your primary keyword naturally in the title, first paragraph, at least one subheading, and the URL slug. - Write meta titles and meta descriptions that accurately reflect the page content and encourage clicks from search results. - Add descriptive alt text to all images for accessibility and image search visibility. - Link internally to related content on your site to distribute authority and help users navigate. - Structure long-form content with clear subheadings so users and crawlers can scan the page efficiently. Tools like Content Genius within Search Atlas can assist with content planning, keyword integration, and on-page optimization guidance as you build out your content library. Maintaining Your WordPress SEO Over Time The 12 steps above establish your foundation, but SEO is an ongoing process. Regularly audit your site for technical issues using a tool like Site Auditor, track keyword rankings with Rank Tracker, and monitor your overall domain authority. Staying proactive with maintenance prevents small issues from compounding into larger ranking problems. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🔌 Connect OTTO to Your Webflow Site Successfully

🧭 Overview Connecting OTTO to a Webflow site is different from a WordPress setup. Webflow does not support plugins, so you must add the OTTO tracking code manually — either through Google Tag Manager (GTM) or a JavaScript Pixel embedded directly in your site settings. Using both methods at the same time is the most common cause of connection failures on Webflow. This article walks you through the correct setup, explains how to identify and fix the GTM vs. JavaScript Pixel conflict, and covers Google Search Console (GSC) connection troubleshooting specific to Webflow. ⚙️ How to Access OTTO In Search Atlas, open the left sidebar and click OTTO SEO. From the OTTO SEO dashboard, select or create the project you want to connect, then follow the steps below. 🚦 Choose One Connection Method Only Before you add any code to Webflow, decide which method you will use. Installing both causes a conflict that prevents OTTO from verifying your site. - Google Tag Manager (GTM): Best if you already use GTM on your site or manage multiple tracking scripts. You add one GTM container snippet to Webflow and fire the OTTO pixel as a tag inside GTM. - JavaScript Pixel (direct embed): Best if you do not use GTM. You paste the OTTO script directly into your Webflow site settings under the custom code section. Pick one method and make sure the other is completely removed before testing the connection. 📋 Method 1 — Connect via JavaScript Pixel (Direct Embed) 1. In Search Atlas, go to OTTO SEO and open your project's OTTO connection settings. Copy the OTTO JavaScript Pixel snippet provided. 2. In Webflow, open your project and go to Site Settings → Custom Code. 3. Paste the OTTO snippet into the Head Code field. 4. Click Save Changes, then publish your Webflow site. 5. Return to Search Atlas and click Verify Connection in the OTTO setup panel. Important: If you previously added OTTO through GTM, remove that GTM tag before publishing. Having the pixel fire from both GTM and the direct embed will cause a duplicate-signal conflict and the verification will fail. 📋 Method 2 — Connect via Google Tag Manager 1. In Search Atlas, go to OTTO SEO and open your project's OTTO connection settings. Copy the OTTO JavaScript Pixel snippet. 2. In your GTM workspace, create a new tag. Set the tag type to Custom HTML and paste the OTTO snippet into the HTML field. 3. Set the trigger to All Pages and save the tag. 4. In Webflow, go to Site Settings → Custom Code and confirm the GTM container snippet (the one starting with GTM-) is present in the Head Code field. This is your GTM container only — do not add the OTTO pixel snippet here as well. 5. Publish your Webflow site, then submit and publish your GTM container. 6. Return to Search Atlas and click Verify Connection in the OTTO setup panel. 🔍 Diagnosing the GTM vs. JavaScript Pixel Conflict If OTTO still shows as unverified after following either method, a dual-installation conflict is likely the cause. Check for it by following these steps: 1. In Webflow, go to Site Settings → Custom Code and review the Head Code and Footer Code fields. If you see both a GTM container snippet and a standalone OTTO JavaScript snippet, you have a conflict. 2. Inside GTM, open your container and search for any existing OTTO or Search Atlas tags. If you find one there while also having the pixel in Webflow's custom code, that confirms the conflict. 3. Remove the version you are not using, publish your Webflow site (and your GTM container if applicable), then click Verify Connection again in Search Atlas. 🔗 Fixing the GSC Connection on Webflow If your Google Search Console property is not connecting, this is usually a separate verification issue unrelated to the OTTO pixel conflict. Follow these steps: 1. In Google Search Console, confirm you have added a property for your Webflow domain and that verification is complete. Webflow users most commonly verify via the HTML tag method or the Google Analytics integration. 2. In Search Atlas, go to your project settings and reconnect GSC by selecting your verified property from the dropdown. If your property does not appear, click Reconnect Google Account and re-authorise access. 3. Make sure the Google account you used to connect GSC in Search Atlas is the same account that owns the GSC property. A mismatch here will prevent the property from appearing. 4. After confirming the property is visible and selected, save your project settings and allow up to 15 minutes for data to populate. ✅ Quick Checklist Before Contacting Support - Only one OTTO connection method (GTM or JavaScript Pixel) is active — not both. - Your Webflow site has been published after any code changes. - Your GTM container has been submitted and published if using the GTM method. - Your GSC property is fully verified in Google Search Console. - The Google account connected in Search Atlas matches the GSC property owner. - You clicked Verify Connection in the OTTO panel after completing all changes. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Remove OTTO Pixel and Search Atlas from WordPress

🔍 Overview If you need to remove the OTTO Pixel or any Search Atlas integration from a WordPress website — for example, when offboarding a client or switching setups — this guide walks you through every step. Following the process below ensures no tracking code, plugin connection, or authentication token is left behind. 🧩 Step 1: Deactivate OTTO SEO for the Site Before removing any code or plugins, you should deactivate OTTO SEO for the relevant site inside Search Atlas. This prevents the platform from attempting to push further changes to the site. 1. Log in to your Search Atlas account. 2. Navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar (or go to /seo-automation-v3). 3. Locate the site you want to disconnect. 4. Click the site's settings or options menu and select Deactivate OTTO (or toggle OTTO off for that site). 5. Confirm the deactivation when prompted. Once deactivated, OTTO will stop sending instructions or updates to the connected WordPress site. 🔌 Step 2: Remove the Search Atlas / OTTO Plugin from WordPress The OTTO Pixel and Search Atlas integration are typically installed on WordPress via a dedicated plugin. You need to deactivate and delete this plugin directly inside WordPress. 1. Log in to the WordPress admin dashboard for the site (e.g., yourdomain.com/wp-admin). 2. Go to Plugins → Installed Plugins in the left WordPress menu. 3. Find the plugin named Search Atlas or OTTO SEO. 4. Click Deactivate. Wait for the page to reload. 5. Once deactivated, click Delete to remove the plugin files entirely. 6. Confirm deletion when prompted by WordPress. Deleting the plugin removes its files and stops the pixel from firing on the site's pages. 🧹 Step 3: Verify No Pixel Code Remains In some setups, the OTTO Pixel tracking snippet may have been added manually to a theme or via a tag manager rather than through the plugin. Check the following locations to make sure no residual code remains. - Theme header/footer files: In WordPress, go to Appearance → Theme File Editor (if available) and inspect header.php and footer.php for any Search Atlas or OTTO script tags. - Functions.php: Check the theme's functions.php file for any wp_enqueue_script calls or inline scripts referencing Search Atlas or OTTO. - Google Tag Manager or other tag managers: If GTM is used on the site, log in to the GTM container and remove any Search Atlas or OTTO Pixel tags. - Other SEO or header plugins: Plugins such as Insert Headers and Footers may contain the pixel snippet. Review and delete any Search Atlas code stored there. 🔑 Step 4: Revoke the WordPress Site Connection in Search Atlas After removing the plugin, disconnect the site from your Search Atlas account to keep your workspace clean and prevent any reconnection attempts. 1. Return to Search Atlas and go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Find the site in your site list. 3. Open the site's options and select Disconnect Site or Remove Site. 4. Confirm the removal. The site will no longer appear in your OTTO dashboard. If the site also appears under Site Metrics (left sidebar), navigate there and remove or untrack the site from your account as needed. ✅ Step 5: Confirm the Removal is Complete Once all steps are done, run a quick final check to make sure everything has been cleaned up properly. - Visit the live website and open your browser's developer tools (F12). Go to the Network tab, reload the page, and search for any requests to Search Atlas or OTTO domains. There should be none. - Confirm the plugin no longer appears in the WordPress Plugins list. - Confirm the site no longer appears as an active OTTO site inside Search Atlas. 💡 Common Questions What if I cannot access the WordPress admin? If you have lost access to the WordPress dashboard, you will need to remove the plugin files via FTP or your hosting control panel's file manager. Navigate to wp-content/plugins/, locate the Search Atlas or OTTO plugin folder, and delete it. Will removing the plugin affect my site's SEO? Deactivating the plugin stops OTTO from managing on-page SEO. Any changes OTTO previously made — such as updated meta titles or structured data — will remain on the site unless you manually revert them. Can I reconnect later? Yes. You can reconnect a site at any time by reinstalling the plugin and authenticating it again through the OTTO SEO → All Sites (SEO Automation) section of Search Atlas. 🆘 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.

🔌 Otto SEO Plugin Impersonation Warning Explained

🔍 What Is This Warning? When you access the Search Atlas dashboard through the Otto SEO plugin inside WordPress, you may see a yellow or blue banner at the top of the screen that reads: "You are currently impersonating another user." This message can look alarming, but it is completely normal. It is not a sign that your account has been compromised, that someone else has accessed your data, or that your permissions have changed in any way. 💡 Why Does This Message Appear? The Otto SEO plugin connects your WordPress site directly to your Search Atlas account using a secure integration layer. When the plugin loads the Search Atlas dashboard inside WordPress, the system uses a technical process called session bridging to authenticate your access seamlessly — without requiring you to log in again through a separate browser tab. Because this authentication method differs slightly from a standard direct login, Search Atlas detects the session as an internal handoff and displays the impersonation banner to be transparent about how your session was initiated. This is standard, expected behaviour for any dashboard access that originates through the Otto SEO plugin. In short: the warning is the platform doing its job correctly, not an indication of a problem. ✅ What This Warning Does NOT Mean - Your account has not been accessed by another person. - Your permissions have not been modified or restricted. - Your data is not at risk or visible to an unauthorised party. - You are not locked out of any features. 🛠️ Can I Still Use the Dashboard Normally? Yes, absolutely. The impersonation warning does not limit what you can do inside Search Atlas. While the banner is visible, you retain full access to your account and can: - View and manage all your projects and campaigns. - Run and review SEO audits, keyword research, and reports. - Use Otto SEO automation features via Left sidebar → OTTO SEO → SEO Automation. - Edit settings, update content, and make any changes you would normally make. Your session is fully functional. Simply dismiss the banner if your interface allows it, or ignore it and continue working as normal. 📋 When Will I See This Warning? You will only see this message when you open the Search Atlas dashboard directly through the Otto SEO plugin inside your WordPress admin panel. If you log in to Search Atlas at its standard URL in a regular browser tab, the banner will not appear. The warning is tied entirely to the plugin integration pathway — not to your account type, role, or subscription level. 🔒 Is My Account Secure? Yes. The session bridging process used by the Otto SEO plugin is encrypted and authenticated through Search Atlas's standard security protocols. No third party gains access to your account as a result of this integration. The word "impersonating" is a technical term used internally to describe a system-initiated session — it does not mean another human being is viewing or controlling your account. 🆘 Need More Help? If the banner is appearing outside of the WordPress plugin context, or if you notice any unexpected changes to your account data or permissions, please reach out to our team right away. 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.

🛠️ OTTO Setup and Cloudflare Whitelisting Requirements

🔍 Overview When setting up OTTO, Search Atlas's AI-powered SEO automation tool, some websites are protected by Cloudflare — a popular security and content delivery network. This article explains whether access to a client's Cloudflare account is required and what steps may be needed to ensure OTTO can work properly on Cloudflare-protected sites. ⚙️ Is Cloudflare Access Required to Set Up OTTO? In most cases, you do not need direct access to a client's Cloudflare account to set up and activate OTTO. OTTO deploys optimizations directly through the connected website, so the standard setup process works independently of Cloudflare. However, if a client's Cloudflare security settings are configured to block or challenge automated requests, OTTO's ability to crawl, deploy changes, or verify implementations may be affected. In these situations, a Cloudflare whitelisting step becomes necessary. 🚦 When Whitelisting Is Needed You may need to whitelist Search Atlas in Cloudflare if you notice any of the following: - OTTO fails to crawl or index the site during setup - Deployments are not applying correctly to the live website - The site returns security challenge pages (e.g., CAPTCHA or "Checking your browser") when OTTO attempts to access it - Cloudflare's Bot Fight Mode or Super Bot Fight Mode is enabled on the client's account - Custom WAF (Web Application Firewall) rules are blocking automated traffic ✅ How to Whitelist Search Atlas in Cloudflare To allow OTTO to function without interference, ask your client (or log in if you have access) to complete the following steps in their Cloudflare dashboard: 1. Log in to the Cloudflare dashboard and select the relevant domain. 2. Navigate to Security → WAF → Tools. 3. Under IP Access Rules, add Search Atlas IP addresses with the action set to Allow. Contact our support team via the chat widget for the current list of IP addresses to whitelist. 4. If Bot Fight Mode is enabled, go to Security → Bots and consider temporarily disabling it during the initial OTTO setup, or create a bypass rule for Search Atlas traffic. 5. Save all changes and re-attempt the OTTO setup or crawl. 📋 Best Practices When Working With Client Sites - Ask about Cloudflare upfront: During onboarding, confirm whether the client's site uses Cloudflare and whether any strict bot protection rules are in place. - Request limited access if needed: You do not need full admin access — read access to security settings and the ability to add IP allowlist rules is sufficient. - Document the changes: Keep a record of any whitelisting rules added so they can be reviewed or removed if the client's security requirements change. - Re-enable security rules after setup: If Bot Fight Mode was disabled temporarily, remind the client to re-enable it once OTTO is fully configured and verified. 🚀 Accessing OTTO in Search Atlas To get started with OTTO, navigate to OTTO SEO in the left sidebar of your Search Atlas dashboard, then open SEO Automation inside it, or go directly to /seo-automation-v3. From there you can connect a website, run the initial site audit, and begin deploying OTTO optimizations. 💡 Summary Cloudflare access is not always required to set up OTTO, but it becomes necessary when a client's security configuration actively blocks automated traffic. Whitelisting Search Atlas IPs and adjusting bot protection rules are the most common solutions. When in doubt, check Cloudflare settings early in the onboarding process to avoid delays. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ WordPress Malware Response and Site Remediation

🔍 Overview If you've noticed a suspicious script, unexpected redirect, or unfamiliar code appearing on your WordPress site — particularly in the footer, header, or theme files — this article will help you understand what's happening and how to respond. Search Atlas and the OTTO SEO plugin do not inject unauthorized scripts or malicious code of any kind. If suspicious code has appeared on your site, the cause is almost certainly a compromised WordPress installation, theme, plugin, or hosting account. ⚠️ Is the Suspicious Script Related to Search Atlas or OTTO? No. The OTTO SEO plugin communicates exclusively with Search Atlas servers to manage SEO tasks such as schema markup, internal linking, and on-page optimizations. It does not modify your site's footer with third-party scripts, inject advertising code, or communicate with any domain outside of Search Atlas infrastructure. If you see an unfamiliar script in your footer or elsewhere, the most likely causes are: - A compromised WordPress plugin or theme (including nulled or outdated software) - Unauthorized access to your WordPress admin account or hosting control panel - A vulnerability in your WordPress core installation - Malicious code injected through your hosting server or database 🛠️ Immediate Steps to Take 1. Take your site offline or enable maintenance mode to prevent visitors from being exposed to malicious content while you investigate. 2. Change all passwords immediately: WordPress admin accounts, FTP/SFTP credentials, hosting control panel, and your database password. 3. Revoke and regenerate API keys for any third-party services connected to your site, including your Search Atlas API key if it was stored in plain text anywhere. 4. Notify your hosting provider. Most hosts have a security team that can scan your server environment and isolate the infection at the server level. 🔬 How to Identify the Malicious Code Use the following steps to locate and remove the suspicious code: 1. Scan with a WordPress security plugin. Install and run a reputable scanner such as Wordfence, Sucuri Security, or MalCare. These tools compare your core files against known-clean versions and flag anomalies. 2. Check recently modified files. Via FTP or your host's file manager, sort files by last-modified date. Malware often modifies wp-config.php, functions.php, index.php, or .htaccess. 3. Inspect your database. Use phpMyAdmin to search for suspicious strings such as eval(base64_decode, <script src= pointing to unknown domains, or document.write in your wp_options or wp_posts tables. 4. Review installed plugins and themes. Deactivate and delete any plugins or themes you do not recognize, any that have not been updated in over a year, or any obtained from unofficial sources. 🧹 Cleaning and Restoring Your Site 1. Restore from a clean backup if you have one dated before the infection. This is the fastest and most reliable remediation method. Confirm the backup is clean before restoring. 2. Reinstall WordPress core files. From your WordPress dashboard, go to Dashboard → Updates and click Re-install version X.X.X. This overwrites core files without affecting your content. 3. Replace theme and plugin files with fresh downloads from wordpress.org or the original developer. Do not reuse existing files that may be infected. 4. Clean your database manually by removing any injected scripts found during your inspection. 5. Implement a Web Application Firewall (WAF) such as Cloudflare or Sucuri to block future intrusion attempts. ✅ After Cleanup: Hardening Your WordPress Site Once your site is clean, take these steps to reduce the risk of reinfection: - Keep WordPress core, all themes, and all plugins updated at all times. - Use strong, unique passwords and enable two-factor authentication (2FA) on your WordPress admin account. - Limit login attempts using a plugin or your WAF rules. - Remove unused themes and plugins entirely — deactivated plugins can still be exploited. - Set correct file permissions: 644 for files and 755 for directories. - Move wp-config.php one directory above your WordPress root if your host supports it. - Schedule regular automated backups stored off-server (e.g., Amazon S3, Google Drive). 🔗 Verifying OTTO Is Working Correctly After Remediation After cleaning your site, verify the OTTO SEO plugin is functioning as expected by navigating to OTTO SEO → All Sites (SEO Automation Projects) in the left sidebar of your Search Atlas dashboard. Confirm that your site is connected, tasks are running normally, and no error messages appear. If OTTO was deactivated during cleanup, simply reactivate it from your WordPress plugin manager — no reconfiguration is needed as long as your API key is intact. 💬 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.

🔌 Connect to Search Atlas via API

🔍 Overview Search Atlas provides API access so you can connect your own tools, scripts, and workflows directly to your account data. To get started, you need to generate an API key from your account settings and use it to authenticate your requests. 🗝️ Step 1: Generate Your API Key 1. Click your avatar in the top-right corner of the platform. 2. Select Team Members from the dropdown menu. 3. In the settings page, navigate to the API Keys tab. 4. Click Generate New API Key. 5. Copy your key immediately and store it securely — it will not be shown again in full after you leave the page. ⚠️ Keep Your API Key Secure Your API key grants programmatic access to your Search Atlas account. Follow these best practices to protect it: - Never share your key in public repositories, forums, or support tickets. - Store it in environment variables or a secrets manager — not hardcoded in your source code. - If you suspect your key has been compromised, return to the API Keys tab and regenerate it immediately. 🔗 Step 2: Authenticate Your API Requests Once you have your API key, include it as a header in every request you send to the Search Atlas API. Use the following format: - Header name:X-API-KEY - Header value:YOUR_API_KEY (the key itself, with no "Bearer" prefix) Replace YOUR_API_KEY with the key you copied from the API Keys tab. All requests must be made over HTTPS. 📋 Step 3: Review Available Endpoints The Search Atlas API exposes endpoints for retrieving data across various platform features. To explore what is available: - Refer to the official Search Atlas API documentation linked inside the platform for a full list of supported endpoints, request parameters, and response formats. - Use the endpoint reference to identify the specific data you want to pull — such as keyword metrics, backlink data, or content reports. - Test your requests using a tool like Postman or cURL before integrating them into your production code. 👥 Managing API Keys for Your Team If you manage multiple team members, each user can generate their own API key from the API Keys tab in their account settings. This allows you to: - Assign individual keys per team member or integration for easier auditing. - Revoke access for a specific user without affecting the rest of your team. - Track which integrations are active by reviewing the keys listed in your account. 🛠️ Common Issues and Fixes - 401 Unauthorized error: Double-check that your API key is correct and that it is sent in the X-API-KEY header, not as a Bearer token. - 403 Forbidden error: 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. - Key not working after regeneration: The old key is invalidated immediately when you regenerate. Make sure you have updated the key in all integrations and environment variables. - No API Keys tab visible: Only account admins can generate API keys by default. Ask your account admin to grant you the appropriate permissions or generate a key on your behalf. 💡 Tips for a Smooth Integration - Respect rate limits to avoid having your requests throttled. The API documentation specifies the allowed number of requests per minute for your plan. - Handle API errors gracefully in your code by checking the HTTP status codes returned with each response. - Use descriptive labels when generating keys (if supported) so you can identify which integration each key belongs to. 🙋 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.

🔌 WordPress Plugin Installation Guide

Managing SEO across WordPress can be complex, especially when juggling multiple plugins, snippets, and manual updates. The official Search Atlas WordPress plugin streamlines this process by integrating directly into your WordPress dashboard. With one installation, you can enable OTTO Server-Side Rendering (SSR) for speed and reliability, manage Schema for structured data, and configure Meta Descriptions without leaving WordPress. This plugin ensures your site remains optimized, fast, and consistent with the broader Search Atlas ecosystem. 🔑 Step 1: Authenticate WordPress With Search Atlas (One-Click Login) 1️⃣ In WordPress, go to: ​Search Atlas → Settings 2️⃣ In General Configuration, click: ​Connect to Search Atlas 3️⃣ A login pop-up opens → sign in to your Search Atlas account. 4️⃣ After authentication, you’ll see a green banner: ​Authentication Successful 5️⃣ Click Reload Now 6️⃣ When the Settings screen reloads, these fields auto-populate: - Search Atlas API Key - Plugin Auth Token (with a Refresh Token button) - OTTO Pixel UUID This confirms the plugin is fully linked to your project. 🛠️ Step 2: Configure OTTO, Schema, and Meta Settings On the same Search Atlas → Settings screen, you'll find the OTTO Server-Side Rendering section, which groups the fields below. OTTO is activated by connecting the plugin and entering the OTTO Pixel UUID (there is no global on/off toggle here). (Optional) Disable OTTO for Logged-in Users When this setting is enabled, OTTO will not inject optimized content while you are logged into WordPress. This is useful when: - You want to preview or edit your original content inside WordPress - You do not want to see OTTO-rendered content while working in the admin environment - You are troubleshooting visual differences between original vs. optimized content When this toggle is off, OTTO will render optimized content for all visitors, including logged-in admins. Changes take effect immediately after toggling — no Save button required. All settings are saved instantly after toggling. 🧰 Step 3: Advanced Settings (Cache Clearing, Debug Tools) If using the Search Atlas plugin, you can clear all WordPress cache plugins from one place: 1️⃣ WordPress sidebar → Search Atlas 2️⃣ Click Settings 3️⃣ Upper-right → open Settings dropdown → Advanced 4️⃣ Scroll to Error Logs 5️⃣ Find Cache Plugin Management 6️⃣ Click Clear All Cache Plugins UI messages include: - “No cache plugins detected.” - “This will clear cache from WP Rocket, LiteSpeed, W3 Total Cache, and all other detected cache plugins.” This is essential after enabling OTTO, updating themes, or installing the Pixel. 🚀 Step 4: Activate OTTO in Search Atlas Now switch back to Search Atlas. 1️⃣ Left Sidebar → OTTO SEO → All Sites. 2️⃣ Click your WordPress site. 3️⃣ Turn on the Engage OTTO toggle. 4️⃣ Click Scan Your domain (e.g., https://yourdomain.com) will appear automatically in the field. 5️⃣Verify the domain, then click Run Diagnostics. OTTO will begin scanning your site for the installed Pixel. During this stage, you’ll see the message: “Running Diagnostics… ​We’re checking the selected page for any OTTO implementation issues. This might take a few seconds — hang tight! A detailed report will be ready shortly.” This confirms that OTTO is checking your site for the Pixel across your environment. The scan may take a couple of minutes — this is normal. ⏳ If the status remains red after the scan: Wait 3–5 minutes to allow the Pixel to fully propagate across your domain. Then refresh the OTTO SEO dashboard, and the status should update once the Pixel is detected. That’s it! The OTTO Pixel is now live on your WIX site, powering automated insights and performance boosts for your SEO strategy. Make sure to revisit the diagnostics panel anytime to ensure your tracking is running smoothly. ⚠️ First-Time Installation Note — Initial Crawl (Up to 24 Hours) After a new connection, OTTO performs a full-site crawl. You may temporarily see: - “Site processing is still in progress.” - “Waiting for data…” - “No crawl data available yet.” - “Pixel detected — awaiting first scan results.” This is normal and may take up to 24 hours. If more than 24 hours pass: 1️⃣ Go to OTTO SEO → All Sites. 2️⃣ Click Scan → Run Diagnostics. 3️⃣ Select Re-run Crawl. 4️⃣ Wait 10–15 minutes and refresh. If everything is correct, the status updates to: 🟢 OTTO Engaged Your Pixel, SSR, Schema, and Meta automation are all active. 🔎 Understanding Your OTTO Installation Diagnostics Results After you click Scan → Run Diagnostics, OTTO inspects your website to verify Pixel installation, detect duplicates, confirm UUID validity, and validate deployed SEO fixes. Below is what each possible status means and what you should do next: ❌ 1. “OTTO not detected.” What does it mean: OTTO couldn’t find your Pixel script in the live HTML for the scanned URL. Why does it happen: - Pixel not installed - Pixel added to the wrong theme/template - Installed on staging but not production - Installed on a different domain variant (www vs non-www / http vs https) What to do: Reinstall the Pixel using the correct installation guide, then wait 3–5 minutes for the status to update after saving changes. ❌ 2. “Your script is using an incorrect UUID.” What does it mean: A Pixel exists, but the UUID doesn’t match the one assigned to your site. Why does it happen: - Pixel copied from another project - Duplicate site setup - Wrong script was pasted into the template - Old Pixel copied before regenerating a new one What to do: Replace the script with the correct Pixel UUID from your Installation Guide. Then wait up to 3 minutes for OTTO to re-check the installation. ⚠️ 3. “Duplicate Installation Detected.” What does it mean: OTTO found more than one Pixel on your site. Possible duplicates: - JavaScript Integration duplicated - WordPress Plugin + JavaScript script at the same time - Multiple manual Pixels installed across templates - Pixel is installed in both global and page-level injectors What to do: Remove the extra instances and leave only one valid Pixel. Once fixed, wait 3 minutes for the system to update. 🟡 4. “OTTO is disengaged.” What does it mean: Your Pixel may be installed, but OTTO is not turned on for this site. What to do: Return to the OTTO dashboard → click Engage OTTO → re-run Scan → Run Diagnostics. 🟢 5. “Deployed Fixes Verification — OK”. What does it mean: OTTO confirms that on-page fixes (meta tags, headings, titles, etc.) have been properly deployed and rendered in the live HTML. This means everything is functioning normally. ⚠️ 6. “Some deployments were not identified in our scan. What does it mean: At least one of the fixes OTTO attempted to deploy did not appear in your rendered HTML during the verification pass. Why does it happen: - Cache not cleared - CDN is still serving an old version - Fix deployed but not published - Plugin conflict (WordPress only) - JavaScript rendering delay What to do: Click View Issue to see which page or tag failed → then re-run Scan after clearing cache. 🟣 7. The Purple Banner (First-Time Installations). If this is your first Pixel installation, you may also see: - “Site processing is still in progress.” - “Waiting for data…” - “No crawl data available yet.” - “Pixel detected — awaiting first scan results.” This is normal. OTTO’s first crawl can take up to 24 hours, depending on site size and CMS. If more than 24 hours pass → go to ​Scan → Run Diagnostics → Re-run Crawl. 🧠 How to Confirm Your Plugin Is Fully Connected Inside Search Atlas → OTTO SEO → All Sites, your site should show: 🟢 OTTO Engaged**.** 🟢 Pixel installed correctly. 🟢 Crawler returning metrics. The Search Atlas WordPress plugin eliminates the need for extra code snippets or multiple SEO tools by centralizing everything in one place. With features like SSR for speed, Schema for visibility, and Meta automation for consistency, your site is always aligned with SEO best practices. By connecting WordPress and Search Atlas, you establish a robust foundation for scaling your digital strategy while maintaining a simple and intuitive workflow. 👉 For a step-by-step walkthrough, watch this Loom video: ​ Search Atlas WordPress Plugin Installation Guide

📘 CMS Connectors — How to Connect Your CMS to Search Atlas

The CMS Connectors dashboard in Search Atlas allows you to create a secure, authenticated connection between your CMS (Content Management System) and Search Atlas. This connection ensures accurate content detection, metadata syncing, and enables direct publishing from Content Genius into your CMS. CMS Connectors do not replace installing the Search Atlas Pixel, nor do they perform marketing automation or plugin tasks. Each tool serves a different purpose (explained below). ⚙️ Step-by-Step Instructions Step 1 — Navigate to the CMS Connectors Section In the top-right corner of Search Atlas, click your Avatar (👤). 1. Select Settings. 2. In the left-hand menu, click CMS Connectors. Path: Avatar (👤) → Settings → CMS Connectors You’ll see all connected domains and available integrations. Step 2 — Open the Add Connector Interface Click + Add Connector at the top right. This opens the panel where you can configure a new integration. Step 3 — Add a Connector Choose New domain if this domain has not yet been added to Search Atlas, or Existing domain if it already appears in your Search Atlas account but has not yet had a CMS Connector configured for it. - For a new domain: enter the full URL (e.g., https://www.example.com). - Click Next to continue. Step 4 — Select the Platform Choose the CMS platform you want to connect. Supported platforms include: - Contentful - Drupal - GoHighLevel - HubSpot - Joomla - Magento - Salesforce - Shopify - Wix - WordPress After selecting your platform, follow the connector flow for that specific system. You will typically be prompted to enter API credentials or authorize OAuth access to complete the connection. 🔌 What CMS Connectors Are For CMS Connectors are designed to: ✔️ Authenticate your CMS inside Search Atlas This gives Search Atlas secure access to validated content and metadata. ✔️ Improve the accuracy of content scanning Some CMS platforms restrict public crawlers; connectors ensure correct reading of canonical versions. ✔️ Enable domain-level configuration Certain metadata and structured fields require authenticated CMS access. ✔️ Enable direct publishing from Content Genius Send drafts, published articles, and updates directly into your CMS from inside Search Atlas. ✔️ Sync metadata between Search Atlas and your CMS Keep titles, descriptions, and supported SEO fields aligned between platforms. 🧩 What CMS Connectors Enable Inside Search Atlas The primary functional purpose of CMS Connectors is enabling Content Genius → CMS publishing. Once connected, Content Genius can: - Publish articles directly to your CMS - Create drafts - Insert SEO metadata fields supported by each CMS - Upload content through a secure authenticated API This eliminates manual copy–paste workflows and speeds up the publishing process. Atlas Brain dependency: Atlas Brain relies on an active CMS Connector to publish content and deploy SEO elements such as schemas and NLP terms. If the connector's sync state is impaired, these features may silently fail or report false success statuses — even when the dashboard appears healthy. 📌 What CMS Connectors Do NOT Do CMS Connectors do not provide general-purpose automation inside your CMS, and do not replace native marketing or publishing tools. They cannot: - Send email marketing campaigns - Trigger CRM or marketing automation - Create newsletters - Manage forms, funnels, or CRM objects - Build landing pages - Replace plugins or native CMS extensions - Replace the Search Atlas Pixel - Perform engagement tracking of any kind Their single scope is: 👉 Allow Content Genius to publish and synchronize content directly with your CMS. All other CMS-native functions remain fully within your CMS. 🛠️ Troubleshooting Dashboard shows 'disconnected' or a '+' Add symbol despite an active connection: If the CMS Connectors dashboard shows a disconnected status or a '+' Add symbol despite your CMS being connected, the underlying connection may still be active. Try refreshing the page or contacting support to verify backend connection status before attempting to re-authenticate. 'Website not connected' error when publishing from Content Genius or Atlas Brain: If Atlas Brain or Content Genius reports a website not connected error during publishing despite the connector appearing active, try manually publishing the article as a workaround and contact support to investigate the backend connection state. Known Issue — Atlas Brain reports CMS as disconnected: Atlas Brain may occasionally report your CMS as disconnected even when the connector is functioning. This is a display/sync issue. Contact support to confirm backend connectivity rather than re-creating the connector, as doing so may cause duplicate connections. 🆚 CMS Connector vs Pixel vs Plugin Integration Type Purpose (Real) What It Actually Does What It Does NOT Do CMS Connector Secure authentication + content publishing • Connects your CMS to Search Atlas via API • Enables Content Genius → CMS publishing (drafts, updates, metadata) • Improves metadata and content detection accuracy • Enables 1-Click publish-to-CMS from Content Genius ✘ Does not track user behavior ✘ Does not replace Pixel ✘ No analytics, no automations, no CRM tasks ✘ Does not send emails / marketing campaigns OTTO Pixel Tracking, SEO automation & site intelligence • Tracks engagement, CTR, scroll depth, GBP signals, heatmap data • Activates OTTO SEO real-time audits & automated fixes • Enables Google Search Console sync & instant indexing • Powers issue detection, redirects, link fixes & technical scoring ✘ Does not publish to CMS ✘ Does not authenticate CMS ✘ Does not replace plugins Plugin (e.g., WordPress) On-site SEO tooling inside CMS • Provides on-page SEO scoring UI • Injects schema helpers / structured data • Adds content suggestions & AI Content Genius bridge • Displays on-site warnings and fixes inside CMS editor ✘ No tracking (needs Pixel) ✘ No CMS authentication (needs Connector) ✘ No engagement analytics ✘ Does not publish automatically without connector 💡 FAQs ❓ Do I need a separate connector for each domain? ✅ Yes. Each unique domain requires its own connector setup. ❓ Can I switch platforms later? ⚡ You can remove and reconfigure connectors at any time, but switching platforms requires a new setup. ❓ Is my data secure during connection? 🛡️ All data transferred through connectors is encrypted and managed securely via your account authentication. ❓ Where can I manage my existing connectors? 💡 All active CMS connections are visible and manageable in the CMS Connectors dashboard under Settings → CMS Connectors.

🏛️ SearchAtlas Shopify Add-on: Architecture Overview for Developers

🏛️ SearchAtlas Shopify Add-on: Architecture Overview for Developers Understanding how the SearchAtlas Shopify Add-on is structured under the hood is essential for developers who need to maintain the codebase, build extensions, debug production issues, or audit data flows. This article breaks down every core component, explains how they interact, and maps the complete data flow from installation to pixel firing. 🔍 🔄 High-Level Flow At a high level, the add-on follows a linear setup and activation flow that connects the Shopify store to the SearchAtlas backend. Here is how each stage connects: 🔄 Step 1 — Install: The merchant installs the app, triggering the OAuth flow. The app stores the shop identifier and access token securely. Note that the connection experience is driven by the Connector Gateway API (CGW), which provides a unified frontend UI for both OAuth and API-key authentication types. Developers building or debugging the connection flow should treat the Connector Gateway as the source of truth for connection state and auth handshakes. 🔄 Step 2 — Enable OTTO Pixel: The merchant toggles the pixel on from the Settings UI. The app then chooses an injection method based on the active theme: if the storefront is running an Online Store 2.0 compatible theme, the app activates a theme app embed; if the theme is a legacy or non-OS 2.0 theme, the app falls back to registering a ScriptTag via the Shopify ScriptTag API. Developers can predict the path by checking the theme's OS 2.0 compatibility flag via the Shopify Themes API before debugging which injection method was used. 🔄 Step 3 — Pixel Active: The OTTO Pixel loads on every storefront page. The SearchAtlas backend can now detect, validate, and deploy OTTO-powered SEO fixes. Note that OTTO AI recommendations are generated via an AI model routing layer — requests are routed through OpenRouter to Gemini Flash Lite. Developers debugging the recommendation generation pipeline should be aware that latency, rate limits, and prompt behavior are influenced by this routing layer. 🔄 Step 4 — Diagnostics: The merchant or agency runs a diagnostic scan from the admin UI. At a high level, the app makes an authenticated request to the SearchAtlas Diagnostics API with the shop context, processes the structured response, and surfaces results in the admin UI. This article describes the diagnostics step at a high level — for the full endpoint specification, request payload schema, and response structure, refer to the SearchAtlas Diagnostics API reference documentation. 🔄 Step 5 — Uninstall: If the merchant removes the app, a webhook triggers cleanup — ScriptTags are removed and the project is marked as paused in SearchAtlas. A paused project means: project data is retained (not deleted), active OTTO SEO fixes are no longer served because the pixel is gone, but recommendations and historical data are preserved. On reinstall, the project can be resumed without data loss by re-linking the shop identifier to the existing project. 🧩 Core Components The add-on is composed of five distinct components, each with a specific responsibility. Understanding what each component does helps you know where to look when debugging or extending the system. The five components are: the Admin App (Remix), the Theme App Extension, the ScriptTag API Injector, the Diagnostics Engine, and the Webhooks layer. The Admin App orchestrates everything: it handles OAuth, drives the Settings UI, and decides whether the Theme App Extension or the ScriptTag API Injector is used to deploy the pixel. The Diagnostics Engine runs validation against the live pixel regardless of which injection method was used, and the Webhooks layer keeps the data store and SearchAtlas project state in sync with Shopify lifecycle events. 🖥️ Admin App (Remix) 🖥️ This is the central control plane of the add-on. It handles OAuth authentication, renders the Settings UI, processes diagnostic requests, displays the log viewer, and processes the app uninstall webhook. 🖥️ Located in the /app/routes/settings.* directory in the Remix project structure. 🎨 Theme App Extension (Online Store 2.0) 🎨 This is the preferred pixel injection method for any Shopify store running an Online Store 2.0 compatible theme. 🎨 The app embed inserts the OTTO Pixel script directly into the page head globally — merchants can enable or disable it from Customize Theme → App Embeds without touching any code. 🎨 Optional app blocks provide per-template control for merchants who need more granular placement. 📜 ScriptTag API Injector (Fallback / Legacy Themes) 📜 For stores running older or custom themes that do not support Online Store 2.0, the ScriptTag API injector automatically registers a hosted JavaScript file to load on every storefront page. 📜 This method requires no code edits from merchants but is considered a legacy fallback — the theme app extension should always be preferred when available. 🩺 Diagnostics Engine 🩺 The Diagnostics Engine is responsible for validating that the OTTO Pixel is correctly installed and functioning. It communicates with the SearchAtlas API and performs several automated checks. 🩺 Duplicate pixel detection — identifies cases where the pixel fires more than once per page load. 🩺 CSP / blocked script checks — detects Content Security Policy rules that may be preventing the pixel from loading. 🩺 UUID mismatch checks — verifies that the pixel identifier matches the expected project configuration in SearchAtlas. 🔗 Webhooks 🔗 The add-on listens for two key Shopify webhook events that affect pixel state and project status. 🔗 app/uninstalled — triggers removal of all registered ScriptTags and marks the associated SearchAtlas project as paused. 🔗 Theme publish/update — triggers a re-validation of the theme app embed state to confirm the pixel is still active after a theme change. ⚠️ Do Not Manually Inject the OTTO Pixel ⚠️ Important: Merchants and developers should not manually paste the OTTO Pixel script into Shopify theme files (theme.liquid, layout files, or any template). Manual injection is unsupported and has been observed to cause 9+ theme errors, conflicts with the official ScriptTag/Theme App Embed injection paths, and duplicate pixel firing that breaks diagnostics. ⚠️ The only supported installation paths are: (1) toggling the pixel on via the app's Settings UI, which automatically uses the ScriptTag API or theme app embed depending on the theme, or (2) enabling the app embed from Customize Theme → App Embeds for Online Store 2.0 themes. ⚠️ If automated installation fails or you need assisted installation, contact SearchAtlas support rather than editing theme files. Support can verify the connection, manually register the ScriptTag, or assist with theme app embed activation. 🛠️ Troubleshooting: OAuth & Connection Failures 🛠️ OAuth token exchange failures — If the Shopify store connection fails during the install or reinstall flow, the most common causes are: an interrupted OAuth handshake, expired or revoked access tokens, or DNS resolution errors when the Connector Gateway attempts to reach the shop's myshopify.com domain. 🛠️ DNS resolution errors — In rare cases, the backend cannot resolve the Shopify domain during the token exchange. This typically surfaces as a generic connection error in the Connections UI. A retry after a few minutes resolves most transient DNS issues. 🛠️ If self-service reinstallation does not resolve the issue, contact SearchAtlas support for backend-assisted connection. Support can manually complete the token exchange, verify the Connector Gateway state, and link the shop to the correct SearchAtlas project without requiring the merchant to repeat the OAuth flow. 🗄️ Data Store The add-on persists a small but critical set of data to support pixel management, diagnostics, and session continuity. The following fields are stored per shop: 🗄️ Shop identifier and access token — stored securely after OAuth completion to authenticate all subsequent API calls to Shopify. 🗄️ Pixel status — whether the OTTO Pixel is currently enabled or disabled for the store. 🗄️ Last diagnostic date — timestamp of the most recent diagnostics scan result. 🗄️ ScriptTag IDs — stored so they can be cleaned up accurately on uninstall or when switching to a theme app embed. 🗄️ Theme extension IDs — stored to track and re-validate embed state when themes are published or updated. 📊 Simplified Data Flow Summary 📊 Install: Store shop and access_token after OAuth completes. 📊 Enable Pixel: Create ScriptTag OR activate theme app embed → store the resulting IDs. 📊 Run Diagnostics: Hit SearchAtlas API with shop context → return structured results to the admin UI. 📊 Uninstall: Receive webhook → delete ScriptTags → mark SearchAtlas project as paused. 💡 Architecture Best Practices 💡 Always use the theme app extension as the primary injection method — it is more resilient to theme updates and does not require merchant code edits. 💡 Store ScriptTag and extension IDs at creation time — without them, cleanup on uninstall becomes unreliable and can leave orphaned scripts on the storefront. 💡 Handle the theme publish webhook — theme updates can silently disable app embeds; re-validating on publish prevents silent pixel loss in production.

🛠️ WordPress Plugin Setup: Elementor, OTTO Activation, and Local Business Configuration

This article shows you how to configure the SearchAtlas WordPress plugin end to end: resolve the greyed-out Parent field when syncing, switch your page builder to Elementor, activate OTTO, and enter Local Business data so it stops showing as blank. ✅ Prerequisites: Sync Content Genius to WordPress Before configuring post types, page builders, or OTTO, make sure your Content Genius article is synced to WordPress. Connecting your CMS is not enough on its own — you must also complete the synchronization step, which is a blocker many users hit. Steps to sync Content Genius to WordPress 1. Open the article in Content Genius. 2. Click the Synchronization status indicator. 3. Click the Not synced bar. 4. Provide the required author and category, then confirm. Once synced, you can proceed with the configuration steps below. 🔄 Why the Parent Field Is Greyed Out When Syncing Articles The Parent field only applies when you publish content as a WordPress Page. It stays greyed out for blog posts because posts do not support parent-child hierarchy. How to enable the Parent field 1. Open your sync settings for the article. 2. Change the post type from Post to Page. 3. Save the sync settings. Once the post type is set to Page, the Parent field becomes editable and you can assign a parent page. 🎨 How to Switch from Gutenberg to Elementor You choose your page builder at publish time inside Content Genius, so each article can use Gutenberg or Elementor. Steps to publish with Elementor 1. Open the article in Content Genius. 2. Click Publish. 3. In the Page Builder dropdown, select Elementor. 4. Confirm and publish. Your article now renders with Elementor instead of Gutenberg in WordPress. 🚀 How to Activate OTTO in the WordPress Plugin OTTO settings are server-side, so there is nothing to toggle manually inside the plugin. Once your OTTO project is activated, its settings sync to your site automatically. Steps to activate OTTO 1. Open the OTTO dashboard. 2. Follow the installation guide to activate your OTTO project. After activation, OTTO settings sync to your WordPress site automatically — no further plugin configuration is required. Because OTTO configuration is server-side rather than plugin-side, you do not enable individual fields inside WordPress. If OTTO sync does not complete Sync typically completes within a few minutes of activation. If it stalls, re-open the OTTO dashboard, confirm the project is active, and trigger a manual re-sync. If fields remain stale after that, contact support. 📍 How to Set Up Local Business Data (Blank Local Business Fix) Local Business data appears blank because it is not pulled from Brand Vault. Brand Vault data is content-focused, so you must enter Local Business information manually in the plugin. Complete this step whenever your Local Business fields render empty on your site. Enter your Local Business information 1. Open the SearchAtlas plugin in WordPress. 2. Go to the Local Business section in the plugin settings. 3. Enter your Local Business details (such as business name, address, and contact information) and save. Whitelist SearchAtlas IPs to fully sync To let Local Business data sync completely, whitelist the SearchAtlas IP addresses on your firewall or CDN. - Get the current IP list: bots.searchatlas.com/ip_list.txt - Whitelisting on Cloudflare: Cloudflare whitelisting guide Once the IPs are whitelisted, your Local Business data syncs and the fields populate correctly. 🟣 What the Purple SearchAtlas Widget Does (and What Happens If You Disable the Plugin) The purple SearchAtlas widget is tied to the plugin. If you disable the plugin, the widget and its features turn off, but your data is preserved. - Disabling the plugin: turns off plugin features and hides the purple widget — your saved data stays intact. - Re-enabling the plugin: restores all features and brings the widget back. You can safely disable and re-enable the plugin without losing your configuration. ⚠️ Known Issues and Workarounds - Duplicate H1 / title appears twice (WP-429, awaiting release): If your article title appears twice on the rendered post, this is a known Content Genius → WordPress sync issue. A fix is awaiting release; as a temporary workaround, remove the duplicate heading in WordPress after publishing. - Only headings sync, body text missing (CG-103, awaiting release): If your published article shows only headings or an outline but missing body text, this is a known post-publishing/draft verification sync issue. A fix is awaiting release — wait for the upcoming fix or contact support to resync the content. 🧩 OTTO Persistence Caveats If OTTO persistence is enabled, OTTO fields may not update when the incoming value matches the staging copy (WP-410, WP-372). If you notice stale SEO plugin fields — such as RankMath, Yoast, or AIOSEO meta descriptions — refresh the sync or review your OTTO persistence settings. 🎯 You now know how to sync Content Genius to WordPress, enable the Parent field by publishing as a Page, switch to Elementor in Content Genius, activate OTTO from its dashboard, and manually enter and sync Local Business data by whitelisting SearchAtlas IPs. Finish by whitelisting the IPs above, then re-check your Local Business section to confirm the fields populate.