📖 Features & How-To

☁️🔧 Cloud Stacks

📡📣 Press Release API — Search Atlas

🤖⚙️ OTTO SEO Project Creation

🔌 WordPress Plugin Installation Guide

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

🔌 WIX OTTO Pixel Installation Guide

🧪 Search Atlas MCP Server

🔌GHL OTTO Pixel Installation Guide

🔍 Inspect and Validate the Search Atlas OTTO Pixel Manually

✉️ Connect Email with SMTP/IMAP in Search Atlas

🔄 Push OTTO Optimizations Directly Into Your CMS

🚀 Search Atlas Plugin Dashboard Updates in WordPress

This article provides a complete walkthrough of the updates introduced in the Search Atlas Plugin Dashboard within WordPress. Every section has been enhanced for clarity, functionality, and smoother SEO workflows. Below is a detailed reference of everything that has changed, what each feature does, and how to use it. In the Search Atlas (WordPress plugin) → Settings area, you'll see navigation tabs that provide consistent access to: - Settings (General) - LLMs.txt - SEO Controls - OTTO cache - Branding - Schema Markup - Search engine verification - Code snippets - Local SEO The layout emphasizes clarity and centralizes all SEO-critical tools. 🏠 Dashboard (View-Only Analytics) The Dashboard loads a read-only version of the Search Atlas performance view. Once the site is connected under Settings → One-Click Authentication, users see: - Organic performance overview - Keyword visibility - Technical health indicators - Backlink summaries This section mirrors the Search Atlas UI but cannot be edited inside WordPress. It exists to give clients quick visibility without leaving WP-Admin. 🔧 Indexation Control This tool helps prevent WordPress from indexing pages that provide no SEO value. Options include: - Date archives - Tag archives - Author archives - Format-based archives - Any unnecessary auto-generated WP taxonomy pages Toggling these improves crawl budget and prevents thin or duplicate content. 🧩 Compatibility Tools This page lists supported page builders (Elementor, Gutenberg, Divi Builder, etc.), SEO plugins (Yoast, Rank Math, All in One SEO, etc.), and caching systems (LiteSpeed Cache, etc.). Host Blocking Test: The Run Test button checks whether the hosting provider is blocking API communication between WordPress and Search Atlas. If the test fails, it indicates server-side blocking of outbound calls, allowing support to diagnose sync or connection issues quickly. Auto-Exclude URL: This interface allows users to paste specific URLs that should not receive automated optimizations from the plugin. Useful when a specific page conflicts with automatic updates, the client wants manual control over a landing page, or a page template behaves differently under plugin automation. When excluded, the plugin silently skips that URL during sync or optimization runs. 🔄 Sync Log This is a chronological log where users can see WordPress updates pushed from Search Atlas, auto-recommendations delivered, contingency posts, and completed sync tasks with timestamps. This reassures users that the plugin is communicating and applying updates correctly. When no sync events exist, you'll see a message that sync events will appear once content or pages receive new updates — this helps verify whether the plugin is properly communicating with the Search Atlas cloud. 🔁 Redirections Manager One of the most expanded areas in this update. Main Redirections View: You can add a new redirect, import redirects from other SEO plugins, and filter by status, pattern type, redirect type, or keyword search. Each redirect row displays the From URL, To URL, redirect type (e.g., 307 Temporary Redirect), pattern (Exact Match, etc.), hits, status (active/inactive), last accessed timestamp, and quick actions (Edit, Deactivate, Delete). Add Redirection: Multiple source URLs can be added with Add Another. Destination URL match types include Exact, Starts With, Ends With, Wildcard, and Regex. Redirection type options include 301 Permanent Move, 302 Temporary Move, 307 Temporary Redirect, 410 Content Deleted, and 451 Content Unavailable for Legal Reasons. You can also add an optional description and set status to Active or Inactive before clicking Save or Cancel. Import From SEO Plugins: Search Atlas can import existing redirects from Redirection, Yoast SEO / Yoast SEO Premium, Rank Math, All-in-One SEO, and Simple 301 Redirects. If a plugin isn't detected on the site, it's labeled NOT FOUND to prevent accidental imports. This feature prevents duplicate redirects and automatically migrates previous configurations. 404 Error Monitor: Shows Total 404 Errors, Total Hits, Last 24 Hours Count, and Frequent Errors Count, plus a bar graph of the most frequent 404 URLs by hit count for quick troubleshooting. 🤖 Robots.txt Editor This lets users edit their robots.txt file directly. It includes: - A live editor for the robots.txt file inside WordPress - A file status indicator showing whether a robots file exists on the server - Automatic backup history each time changes are saved - An important notes panel warning against blocking your entire site (Disallow: /), noting that changes take effect immediately (though indexing delays may occur), and that some hosting providers override robots.txt files - Quick guide cards with examples of User-agent, Disallow, Allow, and Sitemap - A Validate button that checks for common issues 🗺️ XML Sitemap Generator The XML Sitemap panel has been reorganized for clarity. Sitemap Status shows whether the sitemap is Generated or Not Generated, URLs Indexed, whether Auto-update is Enabled or Disabled, the Last Generated timestamp, and the Sitemap URL. Sitemap Actions include Generate Sitemap Now (creates or updates your sitemap.xml file in the root directory), Disable Auto-Update (when enabled, the sitemap updates automatically when posts change), and Delete Sitemap (permanently deletes the sitemap.xml file from your server). Sitemap Preview shows the first 50 lines of the sitemap, including loc URLs, lastmod timestamps, changefreq, and priority, with a View Full Sitemap link to open the live file. 🧱 Custom HTML Pages This feature allows the creation of dedicated HTML pages that bypass the WordPress theme entirely. Use cases include custom landing pages, external tool-built marketing pages, raw HTML/CSS/JS experiments, A/B test pages, and standalone utility pages. How it works: click Add New Custom HTML Page, set a page title and slug, access the Custom HTML Settings panel, enable Raw HTML Mode (auto-enabled by default), upload a complete HTML file or paste HTML directly, then click Publish. These pages do not interfere with theme-based or builder-based pages (Elementor, Divi, etc.). ⚙️ Settings Updates General — One-Click Authentication: Shows current connection status (Synced), the API key used, an option to Re-authenticate or Disconnect Account, and an authentication timestamp. This section ensures the plugin stays securely connected to Search Atlas. Google Index API Integration: Lets users upload their Google Cloud JSON key to enable automatic indexation requests. With the Google Indexing API, every time content is synced, the corresponding URL is automatically sent to Google for indexing. Includes a requirements checklist (project enabled, permissions, domain verified, service account added), a JSON upload field, a manual paste option, and step-by-step instructions to obtain the JSON file. White Label Settings: Allows agencies to rebrand and control what clients can see. A White Label Settings password is required to enable protected options — if it's missing, the system prompts you to set one. Plugin Visibility Controls let you hide the Dashboard, Settings, Indexation Control, Redirect Manager, Robots.txt, Sync Log, Compatibility, and Advanced Settings from client users. Each toggle hides the corresponding menu item in the WordPress sidebar, which is useful for agencies managing SEO for clients who shouldn't access advanced tools. White-Label Export: White-label agencies can export the plugin pre-configured with their white-label settings. After filling out all branding fields, clicking the export option generates a ZIP file of the plugin including all white-label settings. When installed on another WordPress site, the plugin loads with all branding already applied, eliminating repetitive setup for large agencies. Advanced Settings include Cache Plugin Management (clear cache for supported caching plugins such as WP Rocket, LiteSpeed, and W3 Total Cache, with a message if none are detected), Error Log Management (clear WordPress error logs to free up space), and WordPress Debug Configuration (useful for troubleshooting connectivity issues). Import Settings From SEO Plugins: Search Atlas supports importing settings from other SEO tools across indexation control, redirections, robots.txt, and XML sitemap. Each of these modules includes an Import from SEO Plugins button; clicking it opens an importer screen that detects available SEO plugins and their data, with categories marked as available when importable data is found. Optimization Preview Toolbar: A toolbar shows exactly what changes Search Atlas applies to a specific URL. It appears by default and can be disabled in plugin settings, includes a Preview Original button to view the unmodified page, and highlights which elements Search Atlas modified, such as title, meta description, and schema. Content Genius Author Sync Controls: A setting lets users choose which WordPress user roles can be synced with Content Genius when publishing content, restricting available authors to specific roles (e.g., administrators, editors) and preventing content from being assigned to unintended accounts. Light Theme Mode: A light theme has been added to improve accessibility and accommodate user preferences; users can switch themes with a toggle button. Clear Suggestions Cache: An option in Advanced Settings lets users flush the plugin's stored recommendations cache when needed. ✅ Final Notes This update to the Search Atlas WordPress plugin enhances SEO workflow visibility, debugging and troubleshooting, URL and redirection control, indexation and sitemap management, white-labeling and client-facing permissions, integration with the Google Indexing API, and full HTML-page creation within WordPress. The updated Search Atlas WordPress Plugin provides deeper control, clearer diagnostics, and more automation for SEO tasks. With tools for indexation, redirections, robots.txt, sitemaps, custom pages, indexing API, and compatibility testing, it allows site owners and agencies to manage mission-critical SEO infrastructure directly inside WordPress. 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 DNS Installation - Cloudflare API Token Tutorial

📓 Search Atlas Onboarding Guide

Getting started with Search Atlas is now smoother, faster, and more intuitive than ever. In this guide, you’ll walk through the full onboarding experience, from choosing your subscription plan, activating your free 7-day trial, scheduling your 1:1 Launch Lab session, and creating your first website project. 🚀 1. Choose Your Plan & Start Your Free 7-Day Trial When you first land on the Search Atlas subscription page, you’ll see our available plans: Starter, perfect for freelancers and solo marketers; Growth, ideal for mid-size teams managing multiple sites; Pro, built for agencies ready to scale; and Agency, for agencies that need unlimited campaigns and connections. Click “Start 7-day trial” on the plan that fits your needs. 💳 2. Complete Your Secure Checkout You’ll be redirected to Search Atlas’ secure Stripe checkout page. Here you can enter your card details, add your billing information, and choose your country. Once everything is filled in, click “Start Trial.” ✅ 3. Payment Successful After processing your card, you’ll immediately see a confirmation screen. Your 7-day free trial is now activated. 🪐 4. Access Your Exclusive 1:1 Launch Lab Session Users unlock a dedicated 1:1 onboarding session with one of our product specialists, branded the Launch Lab. During this call, we help configure your entire Search Atlas environment, connect key integrations, set up your workflows, and tailor strategies to your actual goals. Click “Select Meeting Slot” to continue. 📅 5. Choose Your Meeting Date You’ll now see the Launch Lab calendar. Select your preferred date using the calendar selector and your time zone (automatically detected), then click on the date that fits your schedule. ⏰ 6. Choose Your Meeting Time After selecting your date, you’ll be presented with all available time slots. Click “Select” on the time slot you want. 📝 7. Confirm Your Details Before finalizing your booking, complete the short confirmation form with your first name, last name, phone, and email, then click “Schedule Meeting.” 🎉 8. Your Meeting Is Scheduled Your onboarding session is confirmed. On this screen you’ll see your exact time and date, the meeting link, your selected time zone, and calendar add-options (Google, Outlook, iCloud). Click any calendar button to add the session automatically. 🌐 9. Create Your First Website Project Now you’ll be guided into your Search Atlas dashboard to create your first website project. Enter your website’s homepage URL and click “Create Project.” This will unlock keyword rank tracking, backlink monitoring, technical audits, OTTO SEO insights, content intelligence, and full Search Atlas performance reporting. Your Search Atlas workspace is now active, your onboarding meeting is scheduled, and your first project is ready to track. Over the next few days, you’ll start seeing your data populate, your insights take shape, and your growth opportunities become clear. 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.

📦 SearchAtlas Shopify Add‑on: The Complete Developer & Support Guide

The SearchAtlas Shopify Add-on connects your Shopify storefront to Search Atlas, letting you inject and verify the OTTO Pixel, run diagnostics, and sync core SEO data — all from a single, user-friendly interface. Modern Shopify apps should use theme app extensions instead of manually editing theme.liquid, and the add-on follows that best practice. 🧩 Who Uses the Add-on - Merchants and site admins install the app, enable the OTTO Pixel, and run diagnostics. - Agencies and SEOs verify that OTTO is firing, troubleshoot duplicate pixels, and monitor deployments. - Developers maintain app code, handle webhooks, and build new blocks or endpoints. 🚀 Key Features - One-click pixel injection using Shopify's ScriptTag API or theme app embeds - Automatic diagnostics that detect duplicate pixels, confirm correct load location, and run re-scans - Theme App Extension support (Online Store 2.0) — enable or disable from Customize Theme → App embeds - Secure OAuth and scoped API access to Shopify resources - Telemetry and logging for pixel fires, detection method, last scan, and error codes 📥 Getting Started Most merchants install the add-on directly from the Shopify App Store: click Install app, complete the OAuth flow, and the app injects the pixel via the theme app embed (recommended) or the ScriptTag API. Agencies distributing to multiple stores can also use a private Custom App with the same feature set, distributed via an install link. Developers can scaffold and test the add-on locally using the Shopify CLI and the official Shopify Remix app template, running a dev tunnel to authenticate and test ScriptTags and app embeds in a development store. 🏛️ How It Works After a merchant installs the app and completes OAuth, the app stores the shop token and offers a toggle to enable the OTTO Pixel. It then either creates a ScriptTag or activates an App Embed (theme app extension), so the pixel loads on every page. Search Atlas can then detect, validate, and deploy OTTO fixes. When a merchant uninstalls the app, a webhook cleans up ScriptTags and marks the Search Atlas project inactive. When a merchant publishes a new theme, Shopify turns the app embed off until it's re-enabled, so a re-check after any theme change is recommended. 🧯 Troubleshooting Pixel not firing — open your browser's developer tools, go to Network, and search for sa-dynamic-optimization. If it's missing, check whether the app embed is disabled or the ScriptTag was deleted. Duplicate pixels — look for two or more network calls to the pixel script. Choose one installation method (app embed or ScriptTag) and remove the other. CSP or blocking — some themes or proxies block external scripts; whitelist Search Atlas domains or use Shopify's hosted asset. Theme switch or publish — after publishing a new theme, re-enable the app embed, since Shopify disables it by default until you turn it back on. ❓ Merchant FAQ Why do I still see a Pixel not installed message? Re-scan in OTTO, clear your CDN cache, and make sure the app embed is on. Can I keep the pixel if I uninstall the app? It's technically possible via ScriptTag, but it's not supported — the add-on removes it on uninstall for data integrity. Why did it break when I changed themes? App embeds must be re-enabled after a theme publish. The SearchAtlas Shopify Add-on gives you a repeatable, low-maintenance way to get OTTO live on any Shopify storefront, with built-in diagnostics and duplicate protection so your pixel stays correctly installed as your theme evolves. 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.

🔗 Key Points of CMS Integrations

OTTO applies all optimizations to your site's front end only — your CMS settings and database are never modified. Understanding how JavaScript injection, visual visibility, and user targeting work lets you deploy OTTO with confidence. 🔒 No Permanent Changes to Your CMS OTTO does not alter your CMS configuration. All optimizations are applied to the front-end display only — your underlying settings and database remain untouched. 👁️ Visibility of Changes on the Page Not every OTTO change appears visually on the page: - Meta titles and descriptions — injected into the page HTML and visible when inspecting the source, but not displayed on the page itself. - Headings (H1, H2) — visible directly on the live page. ⚙️ JavaScript Dependency OTTO injects all changes through JavaScript. If the script is disabled or removed from your site, all optimizations disappear immediately. Keep the script active to maintain your changes for site visitors. There is one conditional exception: if the Disable OTTO for Logged in Users setting is enabled, logged-in users will not see OTTO's front-end changes even while the script remains fully active. See the section below for details. 🔑 Excluding Logged-In Users from Front-End Changes When Disable OTTO for Logged in Users is enabled, authenticated users — editors, admins, and any other logged-in visitors — see the original CMS output instead of OTTO's front-end changes. The script remains active and continues injecting changes for all non-authenticated visitors. When to use this setting: - You need editors or admins to preview the unmodified page without OTTO changes applied. - You want to separate the logged-in and logged-out viewing experience. How to confirm it is working: 1. Enable the setting, then reload the page while logged in — you should see the original CMS output with no OTTO-injected changes. 2. Log out and reload to confirm that non-authenticated visitors still see the optimized version. 🎯 OTTO keeps your CMS untouched by applying all changes through JavaScript at the front-end layer — meta tags appear in the source only, headings appear on the live page, and logged-in users can be excluded entirely via the Disable OTTO for Logged in Users setting. For next steps, see the OTTO Deployment guide to start applying optimizations.

📘 Search Atlas SEO WordPress Plugin — Version 2.6.1

The Search Atlas SEO plugin is the official WordPress integration for the Search Atlas platform — connecting your site to OTTO AI automation, Content Genius publishing, and a full suite of native SEO tools for metadata, schema, redirects, and media optimization. ⚙️ Requirements: PHP 8.2+ · WordPress 5.2+ 🆕 What's New in 2.6.1 Version 2.6.1 ships two headline additions on top of the 2.5.x foundation: Feature What it does Media Optimization Convert images to WebP/AVIF, enable native lazy loading, and auto-inject image dimensions — all from inside WordPress Bing Instant Indexing (IndexNow) Submit URLs to Bing automatically on publish using the IndexNow protocol Beaver Builder Sitemap Exclusion Beaver Builder template post types are automatically excluded from Search Atlas–generated sitemaps, matching legacy Rank Math behavior 🧩 Full Feature Overview 🔌 Connecting the Plugin To connect the plugin to your Search Atlas account, you need two separate credentials: - SearchAtlas API Key — a 32-character code found in the Search Atlas dashboard under Settings → API Keys. This authenticates the plugin to your overall Search Atlas account. - Project-specific Key — a separate key tied to the individual Search Atlas project you want this WordPress site to sync with. Find it on the project's settings page in the Search Atlas dashboard. Seeing an "API key could not be verified" error? This almost always means one of the two credentials is missing, swapped, or pasted from the wrong project. Confirm you've entered the 32-character SearchAtlas API Key in the API Key field and the project-specific key in the project field — not the same value in both. Once both keys are saved correctly, the plugin displays a successful connection status in your WordPress dashboard. ⚙️ OTTO — OTTO SEO Automation Engine OTTO is Search Atlas's server-side SEO engine. When OTTO Pixel is installed on your site, OTTO reads every page's SEO state, generates AI-optimized suggestions, and deploys fixes without touching your theme or database content. What OTTO manages through the plugin: - Title tags, meta descriptions, H1/H2/H3 — AI-generated and deployed per page - Open Graph and Twitter Card tags — for social media previews - Image alt text (media library) — generated and applied in bulk - NLP terms and missing keywords (page content) — semantic terms injected into the page body to improve topical relevance. Note: Bulk NLP term deployment may require multiple attempts in the current release. A fix is in progress. - FAQ schema — structured content blocks for rich snippets - Schema markup (JSON-LD) — Article, FAQ, Product, BreadcrumbList, LocalBusiness, and more - Canonical tags and html lang attributes - Internal link suggestions — strategic interlinking recommendations OTTO deployment modes: - OTTO Pixel — lightweight JavaScript snippet that applies fixes client-side (invisible to visitors, readable by search engines) - Cloudflare Worker — alternative deployment for sites using Cloudflare - OTTO Persistence — optionally writes OTTO's suggestions directly to native WordPress post meta fields (title, description, custom fields) for permanent storage OTTO Frontend Toolbar: Logged-in admins and editors see a per-page toggle in the WordPress frontend toolbar to enable or disable OTTO on specific pages without touching any settings panel. To remove a deployed fix: In your OTTO project, find the fix in the Deployed list and click Undeploy. Changes are removed from the front end immediately. ⚠️ Known issue: Atlas Brain may show WordPress plugin authentication as Pending even after the plugin shows a successful connection. This is a display sync issue under active fix; your deployment capabilities are not affected. ⚠️ Compatibility: OTTO is fully compatible with Yoast SEO, Rank Math, WP Rocket, Kinsta, and most major page builders. On Elementor sites, title tag and meta description updates deploy normally, but H1 tag updates must be made manually within Elementor. ✍️ Meta Tag Management The SEO sidebar and bulk editor give you full control over on-page metadata across every post, page, and custom post type. Per-post controls (Gutenbergsidebar): - SEO title and meta description with live character counter - Focus keyword - Canonical URL - Robots directives: noindex, nofollow, noarchive, noimageindex, nosnippet - Open Graph: title, description, image, URL, type - Twitter Card metadata Bulk editing: - Update meta titles and descriptions across hundreds of pages at once using AI-generated suggestions from Search Atlas - Primary Category Selector — when a post belongs to multiple categories, designate a primary category to control the breadcrumb path, canonical URL structure (when using /%category%/ permalinks), and sitemap URLs 🧱 Schema Markup A dedicated schema engine generates and injects JSON-LD structured data without touching your theme files. Supported schema types: - Article / BlogPosting - FAQPage - Product - BreadcrumbList - LocalBusiness - HowTo - VideoObject - Custom types via the schema editor How it works: - Override schema per post via the Gutenberg meta box - The plugin automatically deduplicates schema tags to prevent conflicts with other plugins, including Rank Math and Yoast - Validates JSON-LD output and reports errors before you publish 🔗 Redirect Manager A full redirect management system built into WordPress — no separate plugin needed. Supported redirect types: 301, 302, 307, 308 Pattern matching options: - Exact URL match - Contains (substring) - Starts with - Ends with - Regular expression (regex) Additional features: - Hit count tracking and last-accessed timestamps per redirect - Import redirects from Yoast SEO, Rank Math, or the Redirection plugin in one click - Create redirects directly from 404 error logs - Active/inactive toggle — disable rules without deleting them 🛑 404 Error Monitor The 404 Monitor automatically logs every broken URL request your site receives. - Tracks hit counts and user agents per broken URL - Sortable admin table with the most frequent errors at the top - One-click redirect creation — turn any 404 into a redirect without leaving the monitor screen - Useful for identifying broken backlinks, old content, or crawl errors discovered by Google 🤖 Robots.txt & XML Sitemap Robots.txt editor: - Edit your robots.txt virtually — works even if no physical file exists on the server - Add, remove, and validate crawl rules - Manage sitemap references - Automatic backup before any change XML Sitemap generator: - Automatically generates sitemaps for all post types and taxonomies - Splits into multiple files (up to 5,000 URLs per file) with a sitemap index - Updates automatically when content is published or modified - Exclude specific URLs from the sitemap - Fully compatible with Google Search Console submission Submit your sitemap index URL directly to Google Search Console after the plugin generates it. 🖼️ Media Optimization (New in 2.6.x) A performance module that improves Core Web Vitals scores directly from your WordPress admin. Image Format Conversion: - Convert existing images to WebP or AVIF - Enable native lazy loading on images - Auto-inject image dimensions 🎯 You now have a complete overview of what the Search Atlas SEO plugin version 2.6.1 can do. Install or update the plugin from your WordPress admin, enter your Search Atlas API Key and OTTO Pixel UUID under Search Atlas → Settings, and start deploying OTTO fixes to your live pages.

🔗 Search Atlas API Documentation

Search Atlas provides a set of APIs that allow you to interact with different parts of the platform programmatically. These APIs are designed to help you: - Automate workflows - Integrate Search Atlas into your internal systems - Interact with AI agents - Access and manage SEO-related processes You can explore the full technical reference in the official API documentation. 📍 Access the full API documentation 👉 Explore the full API reference here: ​ https://docs.searchatlas.com/#description/introduction The documentation includes: - Available endpoints by service - Authentication requirements - Request and response formats - Example payloads 🔐 Authentication All API requests require an API key. To get your key: Avatar Menu (👤) (avatar) → Settings → API Keys Then include it in your request headers: X-API-Key: your_api_key ⚙️ Available API Services & Modules The Search Atlas API includes endpoints across the following core systems: 🤖 AI Agents & Automation Interact directly with Search Atlas AI systems: - Atlas Brain (Orchestrator) → multi-agent coordination - OTTO SEO Agent → SEO optimization workflows - OTTO PPC (Ad Brain) → paid ads optimization - Content Genius → AI content generation - Website Studio → landing page and site generation - Local SEO (GBP, Heatmaps, Citations) → local visibility automation - Authority Building → link and authority workflows - Site Explorer → site analysis - Keywords Agent → keyword research workflows - LLM Visibility → AI search visibility tracking 👉 These endpoints typically use streaming responses via WebSockets, enabling real-time agent interaction. 🧩 Playbooks & Workflow Automation Manage reusable automation workflows: - List and search playbooks - Create and update playbooks - Clone or archive playbooks - Run quick-execution playbooks 👉 Designed to automate repeatable SEO and AI-driven processes. 📁 Agent Projects - Create and manage projects tied to domains - Configure location, country, and setup parameters 👉 Used as the base layer for agent-driven workflows. 💬 Sessions & Conversations - Retrieve chat sessions - Access message history - Regenerate AI responses - Share conversations 👉 Enables building custom interfaces on top of AI interactions. 📦 Artifacts & Outputs - Access outputs generated by agents - Track artifacts across sessions - Retrieve activity types and scorecards 👉 Useful for reporting, dashboards, and automation pipelines. ☁️ Signal Genesys (Content & Distribution APIs) Advanced content and distribution workflows: - Cloud Stack content generation and deployment - Press Release creation and distribution - HTML templates and publishing systems - Export and deployment tracking 👉 These APIs support large-scale content automation and syndication. 🔗 Backlink Projects - Create backlink comparison projects - Analyze competitors - Retrieve backlink datasets 👉 Designed for SEO analysis and link intelligence workflows. 🌐 Base URLs Different services use different base endpoints, such as: - https://api.searchatlas.com - https://agent.searchatlas.com - https://sa.searchatlas.com - https://backlink.searchatlas.com 👉 Each corresponds to a specific system or service. 💡 What you can do with the API Depending on the service, you can: - Automate SEO workflows - Integrate AI agents into your systems - Build custom dashboards and reporting tools - Manage projects and configurations programmatically - Trigger and monitor content or SEO processes 💡 What makes this API different Unlike traditional SEO APIs, Search Atlas APIs are designed around: - Agent-based execution (not just data retrieval) - Streaming interactions - Automation-first workflows - Multi-system orchestration This allows developers to build systems that execute SEO tasks, not just analyze them. 🧾 Summary - The API includes multiple services: AI agents, workflows, content systems, and SEO tools - Each module has dedicated endpoints and base URLs - Supports real-time agent interaction and automation - Full documentation is available online 🚀 Getting started 1. Open the API documentation 2. Generate your API key 3. Explore endpoints by module 4. Start testing with your preferred tool The Search Atlas API opens the door to a new way of working—one where SEO, content, and marketing execution are no longer manual, but programmable, scalable, and agent-driven. Whether you're integrating AI agents like OTTO and Content Genius, automating playbooks, or building custom dashboards on top of Search Atlas data, the API gives you the flexibility to turn strategy into execution. Everything you need to get started—endpoints, authentication, and examples—is available in the official documentation: 👉 https://docs.searchatlas.com/#description/introduction If you're looking to go further—automating workflows, connecting systems, or building your own tools—we’re here to support you. Start exploring, start building, and let the system do the work.

🌐 What’s Different About the Cloudflare Integration

The Cloudflare integration doesn’t change what OTTO does — it changes how reliably and securely it can do it. Normally, some CDNs (including Cloudflare) can block OTTO’s crawler or optimization scripts because of strict security, bot protection, or firewall rules. By integrating OTTO directly through Cloudflare, you guarantee that OTTO can operate without interruptions. ⚙️ How It Works When you integrate OTTO with Cloudflare: - ✅ OTTO’s crawler and optimization endpoints are automatically whitelisted. - 🔒 Firewall and bot rules no longer block OTTO’s optimization scripts. - ⚙️ Continuous crawling, monitoring, and optimization remain uninterrupted. - 📊 Data accuracy improves — OTTO sees your site exactly as Google does. 💡 Why It Matters The Cloudflare integration doesn’t introduce new SEO features — instead, it ensures that your existing OTTO functions work smoothly, safely, and consistently. You’ll experience: - Fewer data discrepancies caused by blocked requests. - Continuous tracking, even during heavy CDN caching. - Accurate optimization insights from complete crawl visibility. 🛠️ Common Scenarios Situation Without Integration With Cloudflare Integration CDN security settings block OTTO ❌ Crawler or scripts may fail ✅ OTTO whitelisted automatically OTTO data missing from dashboard ⚠️ Partial crawl detected ✅ Full crawl visibility Firewall rules limit analytics 🚫 Interrupted data sync ✅ Always-on tracking & optimization 🔍 FAQs ❓ Does Cloudflare integration add new SEO features? 💡 No — it ensures your existing OTTO features work reliably under Cloudflare’s security settings. ❓ Why would Cloudflare block OTTO? ⚡ Cloudflare’s default security rules can flag optimization scripts as automated requests. Integrating OTTO directly resolves this safely. ❓ Do I need technical access to enable it? ✅ No, OTTO automatically handles whitelisting when connected via Cloudflare integration inside your Search Atlas dashboard. Integrating OTTO with Cloudflare gives you uninterrupted, accurate, and fully secure performance, allowing OTTO to crawl and optimize your site exactly as Google would. If you need help with the setup, our support team is available via Live Chat inside your Search Atlas dashboard. 👉 Resource: Search Atlas OTTO Integration Guide

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

🛠️ Report an Issue: How to Submit Debug Information Through the Search Atlas WordPress Plugin

The Report an Issue feature in the Search Atlas WordPress plugin provides a simple, streamlined way for clients to notify our team of problems they encounter. In a few simple steps, users can include a full issue description, select the severity, and automatically attach all relevant system information we need to debug and prioritize the issue efficiently. This ensures faster troubleshooting and better visibility for the engineering team. 📌 Plugin version requirement: The Report an Issue feature requires the latest version of the Search Atlas WordPress plugin. Before submitting a report, please make sure your plugin is updated to the most recent release to ensure the feature functions correctly and to avoid known connectivity issues present in older versions. 🖥️ Step-by-Step Guide 🔧 Step 1 — Navigate to the Report a Bug Section From your WordPress dashboard, click the More Features (apps-grid icon), then select Report a Bug. Your screen will load the full reporting interface, displaying two major areas: - System Information - Report an Issue This system information is automatically included in your report to help our team debug your environment. 📝 Step 2 — Review the System Information Block Under the “System Information” section, you’ll see key details about your installation: - Website URL - Plugin version - WordPress version - PHP version - Active theme - Project UUID — a unique identifier for your Search Atlas workspace, used by our team to locate your account quickly. This data requires no action from you — it is collected automatically and securely. 🗒️ Step 3 — Enter Your Issue Description Below the System Information block, you will find the Issue Description text area. If you do not see it, scroll down past the system details panel. Here, you’ll describe: - What happened - Any error messages - Steps to reproduce the issue - Any relevant context ⚠️ The field requires at least 10 characters. If the field is empty and you try to proceed, it will show a validation warning — exactly: "Issue description must be at least 10 characters long" — and the form will not submit until the minimum is met. 🚦 Step 4 — Select the Severity Level Below the description field, choose the issue severity. Choose the level that best matches the impact of the problem: - Critical — site is down, data loss is occurring, or the plugin is completely unusable. - High — a major feature is broken or significantly impacting your workflow. - Medium — functionality is impaired but a workaround exists. - Low — cosmetic, minor, or non-blocking issue. Selecting the right severity helps our engineering team triage and prioritize your report appropriately. 👤 Step 5 — Include User Information You’ll see a checkbox labeled: Include current user information (username, email) This helps us contact you if more context is needed. 📤 Step 6 — Submit Your Report Click the Submit Report button. Once submitted: - The plugin bundles your system data, - Attaches your description, severity, and user info, - Sends everything directly to our monitoring dashboard, - And becomes available to the engineering team for triage. After submission, you will see an on-screen confirmation message indicating that your report was received successfully. If you opted to include your user information, our team may follow up by email with any additional questions or updates as the issue is investigated. 📌This ensures we can prioritize and debug issues properly. 💡 How It Works Behind the Scenes Once your report is submitted: - The issue appears automatically in our internal dashboard. - Our engineering team can see full environment details and debug context. - Each issue is tracked, organized, and prioritized for investigation. This makes the process fast, transparent, and reliable for both the user and the development team. ⚠️ Troubleshooting: If the Report Issue page does not load, throws an error, or the plugin appears to be in an unhealthy state, please contact our support team directly through your usual support channel and include your Website URL, plugin version, and a manual description of the issue so we can assist you right away. ✨ Final Notes The Report an Issue tool is designed to make communicating technical issues frictionless. Just describe what you experienced, choose a severity, and click submit, the plugin handles the rest, giving our team everything needed to investigate. If you ever need help or want to share more details, don’t hesitate to reach out. We’re here to support you!

📘 MCP for Integrations & External Systems

The MCP allows your AI assistant to trigger actions that connect Search Atlas workflows with external destinations such as CMS platforms, publishing systems, and other integrated services. This article explains what MCP integrations are, how they work, what types of actions are supported, and how to safely execute workflows that involve external systems. 🧠 What Integrations Mean in MCP In the MCP context, integrations refer to actions that: - send data outside of Search Atlas - publish or distribute content - connect with third-party platforms - trigger external workflows These are not separate tools — they are extensions of existing Search Atlas product areas (such as Content, GBP, PPC, PR) that interact with external systems. 🔍 What You Can Do Using MCP with integrations, you can: - publish content to CMS platforms (e.g., WordPress) - distribute press releases - submit data to external services (indexing, citations) - execute outreach or PR workflows - trigger actions that interact with connected accounts These actions extend beyond internal data and result in real-world changes or external outputs. About "connected accounts": Before MCP can execute any integration action, the relevant external system must be connected to your Search Atlas workspace. This typically means configuring a CMS connector (for WordPress and other CMS platforms), connecting your Google Business Profile, or authorizing the third-party service you want to publish to. CMS connections are set up via the CMS connector inside Search Atlas — without an active connector, MCP publish actions will fail even if your AI assistant successfully prepares the request. If you are unsure whether your destination is connected, check the CMS connector / integrations area in the Search Atlas dashboard before requesting a publish action. ⚙️ Step-by-Step: Execute an Integration Action Step 1 Open your MCP-connected AI assistant Step 2 Ask for an action that involves an external system Examples: - “Publish this article to WordPress” - “Submit these URLs for indexing” - “Distribute this press release” Step 3 The assistant prepares the integration action At this stage, it determines: - the destination system - the required data - whether approval is needed before execution If approval is required, the assistant will surface the prepared action for your review and wait for your confirmation before proceeding. Step 4 Review the action details This is important because integration actions may: - publish publicly - trigger external processes - consume credits or HDC Step 5 Approve the action (if required) Actions that involve: - external publishing - spending - irreversible effects may require confirmation before execution. Step 6 The MCP executes the integration The action is sent to the external system using your connected account and permissions. After execution, verify the outcome in the destination system (for example, check that the post appears in your CMS, that the press release shows as distributed, or that submitted URLs appear in their respective indexing queues). If the action does not appear as expected, see the Troubleshooting section below. 🌐 Types of Integration Actions 📰 Publishing - CMS publishing (e.g., WordPress) - scheduled content distribution Note on supported publishing paths: WordPress and other CMS publishing is supported via the Search Atlas CMS connector. Content Genius posts can be published to Website Studio sites, as well as to WordPress and through Universal CMS connectors. Please distinguish between supported CMS connectors (such as WordPress via the CMS connector) and integration paths that are still in development. 📡 Submissions - URL indexing - citation submissions - directory distribution 📣 Outreach & PR - press release distribution - outreach campaigns Note on press release indexation: Press release URLs distributed through Signal Genesys are now subject to an automated daily indexation check. After distribution, the system will periodically verify whether the released URLs have been indexed by search engines, and you can expect to see indexation status reflected in the corresponding press release report over time without needing to manually re-check each URL. 🔗 External Execution - actions that trigger systems outside Search Atlas infrastructure 📍 GBP (Google Business Profile) - GBP-related MCP actions (posts, updates, profile interactions) Note on GBP MCP responses: GBP MCP now returns responses using structured output. This means GBP-related responses are returned as predictable, schema-shaped objects rather than free-form text. If your AI assistant or downstream automation was previously parsing GBP MCP responses as plain strings, you may need to update that parsing to read the structured fields directly — most MCP-aware assistants handle this automatically. All of these are part of the broader MCP toolset interacting with external services. ⚠️ Important Behavior Differences Integration actions are different from internal actions in key ways: 1. They may be irreversible Once content is published or submitted, it may not be easily undone 2. They may require approval The MCP may pause execution and request confirmation 3. They may consume credits Depending on the action, they may use: - Search Atlas quota - Hyperdrive Credits (for premium distribution) 4. They depend on external systems Execution success may depend on: - third-party platform availability - account connection status - external API behavior 5. They may depend on plan tier or backend enablement Not every MCP endpoint is enabled for every plan or for general availability. Some endpoints (for example, certain bulk SERP endpoints such as se_bulk_serps) require explicit backend enablement and are not opened up to all accounts by default, even when your quota dashboard shows available credits. If you call one of these endpoints and receive an ACCESS_DENIED response despite having sufficient quota, this typically indicates a backend access restriction rather than a quota problem — please contact Search Atlas support so the endpoint can be reviewed for your account. 🔐 Step-by-Step: What to Check Before Running Integration Actions Step 1 Confirm the destination system is connected Example: CMS, GBP, or external platform Step 2 Check your quota or HDC balance Step 3 Understand whether the action is public or external Step 4 Review the action carefully Step 5 Approve only if you are ready to execute 📋 Plan Availability & Endpoint Access MCP integration actions are not uniformly available across all Search Atlas plans. The general guidance is: - Core publishing & submissions (CMS publish via supported connectors, URL indexing, citations): generally available to plans that include the relevant product area (Content, OTTO, Local). - Press release distribution via Signal Genesys: requires Hyperdrive Credits (HDC) and the PR distribution add-on. - GBP MCP actions: require a connected Google Business Profile on a plan that includes Local features. - Bulk SERP and other advanced/data-volume endpoints (e.g., se_bulk_serps): may require special enablement on your account even if your quota dashboard shows availability. These are not enabled by default for general MCP usage. If you are unsure whether a specific MCP endpoint is included in your plan — or if you receive an ACCESS_DENIED response despite a healthy quota balance — contact Search Atlas support with the endpoint name and the request your assistant attempted. Support can confirm whether the endpoint requires backend enablement for your workspace. 🛠️ Troubleshooting Integration Issues Issue 1 — Action fails after approval Possible causes: - external system not connected - authentication issue - API error on the third-party platform Issue 2 — Action does not execute Possible causes: - waiting for approval - insufficient quota - permission restrictions Issue 3 — Unexpected output Possible causes: - incorrect input data - incomplete instructions - mismatch between requested action and integration behavior Issue 4 — "Website not connected" error on publish, even though the site appears connected If a publishing action (for example, publishing to WordPress) fails with a "website not connected" error while the site clearly shows as connected in your Search Atlas dashboard, this is a known state mismatch between the dashboard view and the CMS connector / Atlas Brain status used by MCP. Try the following, in order: - Open the CMS connector / Atlas Brain integration for that site and confirm its status there (not just the project-level dashboard view). Reconnect or re-authorize the connector if its status is not "active". - Attempt a manual publish from the relevant Search Atlas tool (e.g., Content Genius) as a fallback. If the manual publish succeeds, the connector itself is healthy and the issue is isolated to the MCP path. - If the error persists after reconnecting and the manual publish also fails, contact Search Atlas support with the site URL, the connector status you see, and the exact error message — this is the information support needs to investigate the connection state on the backend. Issue 5 — ACCESS_DENIED with sufficient quota If an MCP call returns ACCESS_DENIED even though your quota dashboard shows enough credits, the endpoint may not be enabled for your account or plan. This is most often seen on advanced data endpoints (for example, bulk SERP endpoints). Contact support so the endpoint can be reviewed for backend enablement on your workspace. 🔁 How Integrations Fit into MCP Workflows Integration actions are typically the final step in a workflow: 1. Generate or prepare data (content, audit, campaign) 2. Review and refine 3. Execute external action (publish, submit, distribute) This ensures that external actions only happen after validation and approval. 🧠 Best Practices Review before executing Always verify content or data before publishing or submitting Use approval as a checkpoint Approval prompts are designed to prevent unintended actions Separate preparation from execution Generate and review first, then execute integrations Be aware of external impact Integration actions often have real-world visibility MCP integrations allow your AI assistant to move beyond internal workflows and interact with real-world systems. By combining preparation, review, and controlled execution, you can safely publish, distribute, and trigger external actions using the same Search Atlas capabilities, permissions, and quota rules tied to your account.

📘 MCP for Cloud Stack

Cloud Stack allows you to build and publish cloud-based structures from templates, which are used as part of SEO and link-building workflows. Through MCP, your AI assistant can create stacks, publish them, and track their status. This article explains how to create, build, and manage cloud stacks using MCP. 🧠 What You Can Do Using MCP with Cloud Stack, you can: - Create cloud stacks from templates - Build cloud stack structures - Publish cloud stacks - Track build and publication status - Monitor quota usage 👉 Cloud stacks are used as part of broader SEO workflows, particularly in link-building strategies. ✅ Prerequisites & Plan Requirements Before using Cloud Stack via MCP, please note: - MCP access to Cloud Stack tools is included in plans that have the Cloud Stack add-on or feature enabled. If you are unsure whether your plan includes Cloud Stack MCP access, contact your account manager or Search Atlas support. - Certain Cloud Stack capabilities (such as specific providers or higher-volume publishing) may be restricted by plan tier or require special enablement on your workspace. - If an MCP endpoint is not enabled for your plan, your AI assistant will return an access or permission error when invoking the tool. ☁️ Supported Cloud Providers & Templates Cloud stacks are created from provider templates. Search Atlas currently supports 15+ cloud providers, including recently added git-based and sandbox providers such as: - GitLab Pages - AWS Amplify - SourceForge - Glitch - CodeSandbox 👉 When you ask your AI assistant to create a cloud stack, you can specify which provider template to use. If you do not specify one, the assistant may list available providers or pick a default based on your workflow. ⚙️ Step-by-Step: Create a Cloud Stack Step 1 Open your MCP-connected AI assistant Step 2 Ask to create a cloud stack Examples: - “Create a cloud stack” - “Set up a cloud stack from a template” - “Create a cloud stack on GitLab Pages” (or any supported provider) Step 3 The assistant creates the stack from the chosen provider template 👉 Stacks are always created from one of the supported provider templates listed above. Step 4 Confirm stack details ⚠️ Note (upcoming change): The separate cs_create and cs_build MCP tools may be merged into a single cs_create action. Once that change ships, the Create and Build steps below may be combined into one command — your AI assistant will handle creation and build in a single step. 🏗️ Step-by-Step: Build the Cloud Stack 💡 Build vs. Publish: Building compiles and prepares the stack structure (assembling files, configuration, and template content) so it is ready to deploy. Publishing takes the built stack and makes it live/publicly accessible at its provider URL. Both steps are currently required; they may be merged into a single step pending an upcoming release. Step 1 Ask your assistant: - “Build my cloud stack” Step 2 The assistant initiates the build process Step 3 Wait for completion 👉 Building prepares the stack for publishing — the stack is not yet live at this point. 📤 Step-by-Step: Publish the Cloud Stack ⚠️ Important — publishing is potentially immediate and not easily reversible. Once a stack is published, it becomes live at its provider URL. Always review your stack content and configuration before issuing a publish command. Step 1 Ask your assistant: - “Publish my cloud stack” Step 2 The assistant prepares the publication Step 3 Approve the action (if required) When approval is triggered, your AI assistant will display a confirmation dialog or return an MCP response that requires acknowledgment before the publish call is executed. To proceed, reply with an explicit confirmation such as “Yes, publish” or click the approve button in your assistant's confirmation prompt. To cancel, reply “No” or “Cancel” — the stack will remain unpublished. Whether the approval prompt appears depends on your MCP client's configuration: some clients are configured to auto-approve tool calls, in which case the publish may execute immediately. If you want to ensure a manual approval step every time, configure your MCP client to require confirmation for Cloud Stack publish actions. Step 4 The stack is published 👉 Publishing makes the cloud stack active and accessible at its provider URL. 📊 Step-by-Step: Track Status Step 1 Ask your assistant: - “Show my cloud stack status” Step 2 The assistant retrieves status data Step 3 Review: - build status — whether the stack has been compiled and prepared for publishing (e.g., pending, in progress, completed, failed) - publication status — whether the stack is live at its provider URL (e.g., unpublished, publishing, published, error) - progress updates — incremental updates while build or publish operations are running Step 4 Interpret the result and take next steps: - If build status shows failed, ask your assistant for the error details and re-run the build after addressing the issue. - If publication status shows published, your stack is live — verify it at the provider URL. - If status appears stuck, wait a moment and ask your assistant to refresh the status. 📈 Monitoring Quota Usage Cloud Stack actions consume Search Atlas quota. To check your usage via MCP: - Ask your assistant: “Show my Cloud Stack quota” or “How much Cloud Stack quota do I have left?” - The assistant will return your current quota balance and usage for Cloud Stack operations. Quota limits depend on your plan and any add-ons. Creating, building, and publishing stacks each may consume quota, and certain providers may consume more than others. ⚠️ Note: The quota displayed in the Search Atlas dashboard may not always reflect what is accessible via MCP. If a specific endpoint is restricted on your plan, the MCP tool may return an access error even when the dashboard shows available quota. Contact support if you see a mismatch. ⚠️ Important Notes 1. Creating and building stacks may consume Search Atlas quota 2. Publishing may involve additional resource usage 3. Actions may require approval depending on execution 4. Cloud stacks are part of broader SEO workflows 5. Publishing via MCP is potentially immediate and not easily reversible — always review your stack before issuing a publish command 🔁 How This Fits Into MCP Workflows A typical workflow: 1. Create cloud stack 2. Build stack 3. Publish stack 4. Track status 👉 This supports infrastructure-based SEO execution. 🧠 Best Practices 1. Confirm configuration before building 2. Review stack content before issuing a publish command — publishing is potentially immediate 3. Monitor status after publishing 4. Use cloud stacks as part of larger SEO strategies 5. Track results alongside other SEO tools MCP for Cloud Stack allows you to create and deploy cloud-based SEO structures through conversation. By building and publishing stacks from templates, your AI assistant can execute infrastructure-level SEO actions using the same capabilities available in Search Atlas.

📘 MCP Permissions & Plan Access

MCP (Model Context Protocol) is the system that allows AI assistants to interact with Search Atlas tools on your behalf. Access to MCP tools is controlled by your Search Atlas plan and permissions. This means you can only use the tools, features, and product areas that are included in your account. MCP does not grant additional access beyond what your plan allows. 🧠 How Access Works MCP uses the same system as the Search Atlas platform: - Same authentication - Same plan entitlements - Same permission structure 👉 If you can access a feature in the Search Atlas app, you can access it through MCP. 👉 If you cannot access it in the app, MCP will not allow it. Note: Some MCP tools may not yet be publicly available even if the corresponding feature appears accessible in your Search Atlas dashboard. In these cases, you will receive an ACCESS_DENIED error that is unrelated to your plan or quota status. See the 🚫 Tools Not Yet Publicly Available section below for known examples. ⚙️ Step-by-Step: What Happens When You Use a Tool Step 1 You request an action through your AI assistant Example: - “Run a site audit” - “Create a PPC campaign” (see the ⚠️ OTTO PPC Standalone Mode section below for which PPC tools require a fully configured Search Atlas business profile) Step 2 The assistant selects the appropriate MCP tool Step 3 The MCP checks your permissions and plan access Step 4 One of two outcomes occurs: - ✅ Access granted → the action executes - ❌ Access denied → the action fails with an error. Important: an ACCESS_DENIED error does not always mean a plan or quota problem — the specific MCP tool may simply not yet be publicly enabled (see the 🚫 Tools Not Yet Publicly Available section below). Note: The error message returned may not always specify the exact reason for denial. Check your plan entitlements in the Search Atlas dashboard first; if your plan shows access but you still receive ACCESS_DENIED, the tool may not yet be publicly available via MCP — contact support for clarification. ⚠️ OTTO PPC Standalone Mode — What Works Today Some OTTO PPC tools can be used in standalone mode (with a connected Google Ads account but without a fully configured Search Atlas business profile). Others still require a complete business profile setup. Here is the current readiness status: - Reports — ✅ Available in standalone mode. Backend support for ads_account_id has shipped, so Reports can be used with only a connected Google Ads account. - Negative Keywords — ✅ Available in standalone mode with a connected Google Ads account. - Campaign Performance — ❌ Not yet available in standalone mode. The account-scoped APIs for standalone Campaign Performance have not yet been released to production. A fully configured Search Atlas business profile is currently required. - Performance Preferences — ❌ Not yet available in standalone mode. The /performance-preferences/ endpoint does not yet support standalone (ads_account_id) mode. A connected business profile remains required for this tool until the update is released. Note: Standalone support for Campaign Performance and Performance Preferences is on the roadmap. Until those updates ship to production, please configure a full Search Atlas business profile to use them. 🔍 What Determines Access Your ability to use MCP tools depends on: - Your Search Atlas plan - Enabled product areas (SEO, Content, GBP, PPC, etc.) - Available quotas and credits - Whether the specific MCP endpoint is publicly enabled for MCP access ⚠️ Common Access Issues Issue 1 — Tool is not available Cause: The feature is not included in your plan Result: The assistant cannot execute the action Issue 2a — Action fails after request (permission/plan denial) Cause: You do not have permission for that product area, or your plan does not include it Result: The MCP returns an authorization error Issue 2b — Action fails after request (endpoint not yet publicly available for MCP) Cause: The specific MCP endpoint has not yet been publicly released for MCP usage, even though the corresponding feature is accessible in the Search Atlas dashboard Result: The MCP returns an ACCESS_DENIED error that is not related to your plan or permissions. In this case, no plan upgrade will resolve the issue — contact support to confirm endpoint availability. Issue 3 — Action blocked despite access Cause: Quota is exhausted Result: The action cannot proceed until credits or quota are replenished or your billing cycle resets. 🚫 Tools Not Yet Publicly Available Some MCP tools exist on the backend but are not yet open for general MCP usage. If you call one of these tools, you will receive an ACCESS_DENIED error even if your plan, permissions, and quota are all valid. This is not a billing or upgrade issue — the tool itself is simply not publicly enabled for MCP yet. Known examples of MCP tools that are not yet publicly available: - se_bulk_serps — This endpoint is not currently publicly enabled for MCP usage. Even if your dashboard shows available Site Explorer or keyword quota, MCP calls to se_bulk_serps will return ACCESS_DENIED. This is not a plan or quota issue. No action is needed on your account. If you receive ACCESS_DENIED on one of these tools, no plan change will resolve it. Contact Search Atlas support to confirm whether a specific tool is currently publicly available, as endpoint availability changes over time. 🐞 Known Issues Known Issue — Domain-level schema deployment via MCP: When using MCP to deploy all schemas for a project, domain-level schema deployment may fail with an HTTP 400 error (otto_urls not found). Page-level schemas are unaffected. This is a known bug currently being resolved — manually deploy domain-level schemas from the Search Atlas dashboard as a workaround. ⚙️ Step-by-Step: How to Resolve Access Issues Step 1 Confirm the feature exists in your Search Atlas plan — open the Search Atlas app dashboard and check whether you can use the corresponding feature there. Step 2 Check that you have available quota Step 3 Retry the action Step 4 If the issue persists, review plan access or upgrade Step 5 If your dashboard shows available quota but you still receive ACCESS_DENIED via MCP, the endpoint may not be publicly enabled for MCP yet. Contact support to confirm whether the tool is currently available for MCP access. Quick decision checklist for ACCESS_DENIED errors: 1. Is the feature accessible in the Search Atlas app dashboard? If no, the feature is not on your plan — upgrade your plan or check quota. 2. If yes in the app but you still receive ACCESS_DENIED via MCP, the MCP tool may not yet be publicly available (see 🚫 Tools Not Yet Publicly Available) — contact support to confirm. 3. If the feature is on your plan and the tool is publicly available, check your remaining quota or credits — the action will resume when quota is replenished or your billing cycle resets. ❓ What to Do If You Receive ACCESS_DENIED If you receive an ACCESS_DENIED error from an MCP tool, follow these decision steps before assuming it is a quota or sync issue: 1. Check your dashboard. Is the feature accessible in the Search Atlas app? If no, the feature is not included in your plan — review your plan or upgrade. 2. If yes in the dashboard but ACCESS_DENIED via MCP, the tool may not yet be publicly available via MCP. Consult the 🚫 Tools Not Yet Publicly Available list above (for example, se_bulk_serps). No plan upgrade or quota change will resolve this — the endpoint is simply not yet enabled. 3. If the tool is not on the known list and you believe your plan includes it, contact Search Atlas support. Provide the tool name and the exact error so support can confirm endpoint availability or investigate further. 🔁 Key Principle 👉 MCP does not bypass permissions or plan limits. All actions strictly follow: - account permissions - plan entitlements - quota availability - whether the endpoint is publicly enabled for MCP 💬 Still Having Issues? If you've confirmed your plan, permissions, and quota but are still receiving an ACCESS_DENIED or similar error, here are your next steps: - Contact Search Atlas support chat to confirm whether the specific MCP endpoint is currently publicly available. - Review your plan and upgrade options if a feature is not included in your current plan. - Ask support for the latest list of MCP tools that are currently publicly available, as endpoint availability can change over time. MCP gives you conversational access to Search Atlas, but it does not expand your access beyond your plan. By understanding how permissions, entitlements, and endpoint availability work, you can quickly identify why an action succeeds or fails and take the appropriate next step.

📘 Approval & Safety Controls

Some MCP actions require explicit user approval before they can run. This is part of the MCP safety model and is designed to prevent irreversible, destructive, or spending actions from happening silently. The Search Atlas MCP includes metadata on certain tools that marks them as approval-required. In the source, this is described as a flag marking the tool as approval-required in the MCP tool metadata. Clients that support human-in-the-loop confirmation will surface a confirmation prompt before executing those actions. Note: The MCP approval model described in this article applies specifically to MCP tool calls. Content publishing approval (for example, article publishing in Website Studio or other linked workflows) is a separate mechanism with its own controls and is covered in its own documentation. This article explains which actions require approval, how the approval flow works, what to expect in supported clients, and how this safety layer interacts with your plan permissions and billing. 🧠 Why Approval Exists The approval system exists to protect users from actions that: - spend money - delete or destroy data - trigger irreversible operations - publish or execute something with real-world consequences The source makes this especially clear for: - purchase_credits (buying additional credits, which spends money or consumes balance) - destructive OTTO operations such as otto_delete_project (deleting an OTTO project, which removes all associated configurations and cannot be undone) In practical terms, this means MCP does not simply execute every tool call the assistant proposes. For certain high-impact actions, the assistant can prepare the action — meaning it determines the correct parameters and presents them for your review, but does not submit or execute anything — and the user must still explicitly confirm before it proceeds. 🔍 What “needs approval” Means When a tool is marked with the approval flag: - the assistant can identify the action - the client can show a confirmation prompt - execution pauses until the user approves it ⚙️ Step-by-Step: How the Approval Flow Works Step 1 You ask your AI assistant to perform an action. Examples could include: - purchasing credits - deleting a project - running another action that is destructive or spend-related Step 2 The assistant interprets your request and selects the appropriate MCP tool. At this stage, the assistant is still planning the action — determining the correct parameters and preparing them for your review. It has not submitted or executed the action yet. Step 3 The MCP checks the tool’s metadata. If the tool is marked as approval-required, the execution path changes. Instead of running immediately, the client must interrupt and request confirmation from the user. Step 4 Your MCP client displays a confirmation prompt. In supported clients, this is where you are asked to explicitly approve the action before it can continue. The source names: - Claude Desktop - Claude.ai - Claude Code Step 5 You review the action and choose whether to proceed. At this point, one of two things happens: - Approve → the action executes - Do not approve → the action does not run Step 6 If approved, the MCP executes the action using your Search Atlas account, permissions, and available quota or credits. If the action involves spending or account changes, those effects occur only after approval has been granted. 📌 Actions Most Likely to Require Approval The source explicitly calls out two broad categories: 1. Spending actions These are actions where money or premium credits are being consumed. Examples from the source include: - purchase_credits (buying additional credits, which spends money or consumes balance) 2. Destructive actions These are actions that delete or irreversibly change data. Examples from the source include: - otto_delete_project (deleting an OTTO project — removes all associated configurations and cannot be undone) - other destructive OTTO operations (anything that removes, overwrites, or irreversibly changes project data) The source also makes a broader principle clear: approval is used where execution should not happen silently because the effect is meaningful, costly, or not easily undone. 🔐 Step-by-Step: What to Do When a Prompt Appears Step 1 Read the action carefully. When your client surfaces an approval request, confirm what the assistant is about to do. This is especially important if the action affects billing, deletes data, or changes a live system. Step 2 Check whether the action is expected. Ask yourself: - Is this the action I intended? - Is this a spending action? - Is this destructive or irreversible? - Am I ready for it to happen now? The source’s safety model is designed precisely so you can stop here if the action is not what you want. Step 3 Approve only if you want the action to execute. If you approve it, the MCP continues and runs the tool. If you do not approve it, execution stops. Step 4 If needed, revise your request and try again. If the assistant prepared the wrong action, do not approve it. Instead, provide a clearer instruction and let the assistant re-plan the workflow. This keeps control in your hands before any high-impact tool runs. 🧩 How Approval Interacts with Permissions Approval does not override permissions. Even if you approve an action, the action still must satisfy all normal access controls: - your plan must include the product area - your account must have the necessary entitlement - your quota or balance must be sufficient So approval is not a bypass. It is an additional safety layer on top of the normal Search Atlas access model. Example A user could approve a PPC-related action, but if their plan does not include OTTO PPC, the action still cannot execute successfully because entitlement checks happen separately. 💳 How Approval Interacts with Billing Approval is especially important for actions that involve direct spending. The source explains that money-spending actions and premium actions can involve: - Search Atlas quotas - Hyperdrive Credits - Stripe checkout for top-ups or purchases For those cases, approval ensures: - nothing is purchased silently - the user sees the action before it runs - the user remains in control of when money is spent This is why the source specifically mentions purchase_credits as an approval-required action. Note that credit-purchase approvals are still subject to your plan’s quota rules. Plan upgrades, promotional credits, or quota changes may affect which actions you can take or how much is available to spend. For full details on quotas, plan limits, and available credits, refer to the billing and quota documentation. 🛑 Cancellation, Project Deletion & Other Workflows Outside MCP Approval Some actions that users might expect approval controls to govern are actually handled outside the MCP approval flow. In particular: - Plan cancellation does not automatically delete OTTO projects or remove on-page integrations. Those artifacts persist until they are explicitly cleaned up. - Project deletion is its own workflow, separate from the MCP approval prompt. - Pending or queued destructive actions initiated through other parts of the platform are not retroactively held by the MCP approval layer. If you are cancelling a subscription, removing on-page integrations, or deleting a project, follow the dedicated offboarding and project-deletion documentation for those workflows rather than relying on the MCP approval prompt to surface them. 🧪 What Happens in Clients That Support HITL The source names three clients that support human-in-the-loop confirmation: - Claude Desktop - Claude.ai - Claude Code In these clients, when an approval-required tool is invoked, the client displays a confirmation prompt with the action details, and execution pauses until you approve or decline. Clients that do not support confirmation prompts In clients that do not implement human-in-the-loop confirmation, approval-required tools cannot be safely executed. In those environments, those tools will either return an error or be unavailable, rather than running silently. If you encounter this, use one of the supported clients listed above to complete the action. 🔄 Related Approval Flows in Search Atlas Other Search Atlas products have their own approval-style queues that are distinct from the MCP tool approval model described in this article. These are surfaced in their own product UIs, not through MCP confirmation prompts. - OTTO PPC — Pending Review queue: The auto_pause_low_quality_keywords feature surfaces auto-paused low-quality keywords in a Pending Review queue where you can approve or reject the pause. This is a separate, product-level approval flow and is not governed by the MCP needs_approval mechanism. - Content publishing approvals: Article publishing in Website Studio and linked content workflows have their own publishing controls, separate from MCP tool approvals. If you are looking for a particular approval experience and it is not appearing as an MCP confirmation prompt, check whether it lives in one of these product-level queues instead. ⚠️ Known Issues Content Genius — context loss after content plan approval: After approving a content plan in Content Genius, the agent may lose prior conversation context in some sessions. This is a known issue currently being resolved. If this occurs, re-provide your topic, keywords, and domain to continue the workflow. This callout will be removed once the fix ships.

⚙️ Frequently Asked Questions — API & MCP Server

Search Atlas provides a REST API and an MCP (Model Context Protocol) server for developers and AI tool integrations. This article covers the most common questions. What is the Search Atlas MCP server? The Search Atlas MCP server (mcp.searchatlas.com) lets you control Search Atlas from any MCP client — including ChatGPT, Claude Desktop, and Claude Code — using natural language. It exposes over 220 tools organized by product — OTTO, GBP, PPC, Social Hub, Content Genius, Press Releases, AI Visibility (formerly LLM Visibility), heatmaps, Site Explorer, and more. Instead of logging into the dashboard, you can ask your AI assistant to run tasks directly. Where do I find my API key? Go to Avatar Menu (👤) → Settings → API Keys in the Search Atlas dashboard. Your API key is shown there. ⚠️ Keep it private — treat it like a password. Which AI tools support the MCP server? | AI Tool | MCP Support | | --- | --- | | Claude Desktop | Native — fully supported | | Claude Code (CLI) | Native — fully supported | | Cursor | Should work | | VS Code (GitHub Copilot) | Experimental, not officially tested | | ChatGPT | Supported as an MCP client | | Gemini | Not supported | How do I connect the MCP server to Claude Desktop? 1. Get your API key from Avatar Menu (👤) → Settings → API Keys 2. Open: %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) 3. Add the server config: { "mcpServers": { "searchatlas": { "url": "https://mcp.searchatlas.com/mcp/", "headers": { "x-api-key": "your-api-key-here" } } }} 1. Fully quit and relaunch Claude Desktop 2. ✅ Test: type "List my OTTO projects" How do I connect the MCP server to Claude Code CLI? Run: claude mcp add searchatlas --url "https://mcp.searchatlas.com/mcp/" --header "x-api-key: your-api-key-here" 💡 Or add the same config to your project's .claude/settings.json under mcpServers. Can I connect only specific product tools instead of all 220? Yes. Namespace-scoped endpoints expose only one product's tools. Use a JWT Bearer token (from Avatar Menu (👤) → Settings → API Keys) and set the URL to https://mcp.searchatlas.com/mcp/{namespace}/ where namespace is: otto, gbp, ppc, social-hub, content-genius, press-release, llm-visibility, local-seo-heatmaps, site-explorer, cloud-stack. What are the MCP server rate limits? 40 requests per minute per user. If exceeded, the server returns HTTP 429 with a retry-after header. Claude Desktop handles this automatically by backing off. ⚠️ If you're running batch operations, space your tool calls to stay under the limit. Where can I find the Search Atlas REST API documentation? API documentation is available at https://developers.searchatlas.com (also accessible from Avatar Menu (👤) → Settings → API Keys). Swagger/OpenAPI specs are available for all endpoints. Your Search Atlas API key authenticates all REST API calls. I'm getting a 401 Unauthorized error from the API. What should I do? Check that: (1) your API key is being sent in the correct header (x-api-key: your-key), (2) the key hasn't been regenerated — if you regenerated it, any previous key is immediately invalid, (3) you're using the production key, not a staging key. ⚠️ Regenerate your key in Avatar Menu (👤) → Settings → API Keys if needed. I'm getting a 403 Forbidden error on namespace MCP endpoints. Why? When you connect to the MCP server by signing in with your Search Atlas account (OAuth), an active subscription is required. Accounts without an active subscription are rejected with a 401 error. If you are on a trial and get a 401 when signing in, contact support. The MCP tools are appearing but returning wrong or stale data. What's happening? MCP tools call the live Search Atlas API in real time — they return the same data you would see in the dashboard. If the data looks wrong, open the Search Atlas dashboard directly and check whether the same data appears there. 💡 If the dashboard also shows the discrepancy, it's a data issue to report to support (not an MCP-specific bug). How does Search Atlas MCP authentication work technically? Two methods: - API Key (x-api-key header) — for the public /mcp/ endpoint (all tools). Generated in Settings. - JWT Bearer Token (Authorization: Bearer ...) — for namespace-scoped endpoints. Requires an active subscriber account. ⚠️ The MCP server follows MCP over Streamable HTTP with SSE. A trailing slash on the URL is required: https://mcp.searchatlas.com/mcp/ not …/mcp. How do I use the AMM Toolkit or AI agent tools with Search Atlas? The AI agent (Atlas Brain / AMM Toolkit) is accessible via API at POST https://agent.searchatlas.com/api/agent/orchestrator/ using your Search Atlas API key or JWT. Documentation for the agent API is available at Avatar Menu (👤) → Settings → API Keys → Agent API Docs. ⚠️ Note: AMM Toolkit documentation may reference older, deprecated MCP tool names — always use the tool list in the current Avatar Menu (👤) → Settings → API Keys page as the authoritative reference.

📘 MCP Endpoints & Namespaces

The recommended customer-facing endpoint is https://mcp.searchatlas.com/mcp/. This root endpoint aggregates all Search Atlas namespaces and exposes the full catalog of available MCP tools. 🌐 The Main MCP Endpoint 1. Use the root endpoint: https://mcp.searchatlas.com/mcp/ 2. Add this endpoint to your MCP-compatible client. Supported clients include Claude Desktop, Claude.ai, Cursor, and ChatGPT connectors. 3. Complete the Search Atlas login flow. Once connected, your assistant can access the Search Atlas tools available to your account, based on your plan entitlements and quotas. 🧩 What Namespaces Are The MCP also exposes per-product namespaces. Examples include /mcp/otto/ and /mcp/local-seo-gbp/. A namespace scopes access to a specific product area instead of exposing the full tool catalog. ✅ Which Endpoint Should Customers Use? Customers should use the root endpoint, https://mcp.searchatlas.com/mcp/. The root endpoint aggregates all namespaces and is what customers should use unless they have a specific reason to scope access. 🔁 Root Endpoint vs Namespace Endpoint - Root endpoint (/mcp/) — exposes every tool across every product area. Recommended for customers. - Namespace endpoint, such as /mcp/otto/ — exposes only product-specific tools plus shared common tools. Recommended only when there is a specific reason to scope access. 🧠 Shared Tools Across Namespaces Some common tools are available in every namespace, including Brand Vault, Knowledge Graph, and Billing. This means even scoped namespaces may still include shared platform-level tools. ⚠️ Important Notes - The root endpoint is the standard setup path. - Namespace endpoints exist for scoped access. - Using a namespace may reduce the available tool surface. - Customers should use the root endpoint unless instructed otherwise. For most users, the correct MCP setup is simple: use https://mcp.searchatlas.com/mcp/, complete OAuth login, and let your AI assistant access the Search Atlas tools available under your account. Namespace endpoints are only needed when access should be limited to a specific product area. 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.

📘 MCP for LinkLab

LinkLab is a publisher marketplace that allows you to browse publications, create content for placement, and complete orders. Through MCP, your AI assistant can manage the full workflow from research to checkout and tracking. This article explains how to find publications, create placements, and manage LinkLab orders using MCP. In LinkLab, a placement is a paid content slot on a third-party publication where your article will be published as a guest post or sponsored content. 🧠 What You Can Do Using MCP with LinkLab, you can: - Browse available publications - View publication details - Create articles for placement - Add placements to a cart - Complete checkout - Track order and publication status - Handle rejected publications using the AlternativesDrawer (Choose for Me / Refund HDC) 👉 LinkLab actions may involve Hyperdrive Credits (HDC) for paid placements. ⚙️ Step-by-Step: Browse Publications Step 1 Open your MCP-connected AI assistant Step 2 Ask to view available publications Examples: - “Show available publications” - “Find sites for article placements” Step 3 The assistant retrieves publication listings Step 4 Review publication details This may include: - publication information - placement opportunities 🔍 Step-by-Step: View Publication Details Step 1 Ask your assistant: - “Show details for this publication” Step 2 The assistant retrieves publication data Step 3 Review: - domain authority - pricing - niche / topical category - placement types available - publication characteristics ✍️ Step-by-Step: Create an Article for Placement Step 1 Ask your assistant to create an article and provide inputs such as a target keyword, topic, target URL, and desired word count. You can either ask MCP to generate the article from scratch or provide an existing draft for it to refine. - “Create an article for this placement targeting the keyword ‘best CRM software,’ around 800 words, linking to example.com/crm” Step 2 The assistant generates the article from the inputs you provided, or prepares the draft you supplied for placement Step 3 Review and refine content 👉 Articles are prepared specifically for placement within publications. 🛒 Step-by-Step: Add to Cart Step 1 Ask your assistant: - “Add this placement to my cart” Step 2 The assistant adds the item Step 3 Review cart contents 💳 Step-by-Step: Checkout and Purchase Step 1 Ask your assistant: - “Checkout my LinkLab cart” Step 2 The assistant prepares the checkout Step 3 Review cost and details Step 4 Approve the purchase 👉 Checkout actions involve Hyperdrive Credits (HDC) and require confirmation. Step 5 The order is completed 📊 Step-by-Step: Track Orders Step 1 Ask your assistant: - “Show my LinkLab orders” Step 2 The assistant retrieves order data Step 3 Review: - order status - publication progress - placement updates 👉 Order edit limitations: LinkLab orders are generally not directly editable after submission (for example, adding reference links or removing placeholder content). If you need a post-submission change, contact support or the fulfillment team to request the update. 🔄 Rejected Publications & the AlternativesDrawer A publication may be rejected when the publisher declines the submitted article (for example, due to editorial guidelines, niche mismatch, or content policy). When this happens, the AlternativesDrawer opens to help you resolve the placement. The AlternativesDrawer offers two one-click actions: - Choose for Me — automatically selects a comparable alternative publication and re-routes your placement to it. - Refund HDC — returns the Hyperdrive Credits used for the rejected placement back to your balance. You can trigger either action directly in the AlternativesDrawer in the UI, or by asking your MCP-connected assistant — for example, “Choose an alternative publication for my rejected placement” or “Refund HDC for the rejected placement.” 💰 HDC & Credits - When HDC are deducted: Hyperdrive Credits are charged at checkout, when the placement order is confirmed. - If a publication is rejected: the credits used for that placement become eligible for refund. You can recover them via the Refund HDC action in the AlternativesDrawer, or choose an alternative publication with Choose for Me to apply the credits to a new placement instead. - How to request a refund: Use the Refund HDC button in the AlternativesDrawer, or ask your MCP assistant (“Refund HDC for this rejected placement”). If the refund does not appear in your balance, contact support. 🛠️ Troubleshooting “Tool execution not approved” error This message means the MCP action requires your explicit approval before it can run. MCP requests confirmation for actions that affect your account — such as adding items to a cart, checking out, or spending HDC. To resolve it, approve the tool call in your AI assistant interface when the approval prompt appears (for example, click Approve or Allow on the pending MCP action). If you continue to see the error after approving, retry the request, and contact support if the issue persists. Content Genius → LinkLab bridge issues When pushing articles from Content Genius directly into a LinkLab placement, the publishing bridge may occasionally return a blocked pipeline state. If your article does not transfer or the pipeline stalls, contact support so the team can unblock the pipeline and complete the placement. ⚠️ Important Notes 1. LinkLab placements are paid actions 2. Checkout consumes Hyperdrive Credits (HDC) 3. Purchases require approval before execution 4. Orders involve external publication processes 5. Orders are generally not editable after submission — contact support for post-submission changes 6. Rejected publications can be resolved with Choose for Me or Refund HDC in the AlternativesDrawer 🔁 How This Fits Into MCP Workflows A typical workflow: 1. Browse publications 2. Select placement opportunities 3. Create article 4. Add to cart 5. Checkout 6. Track order 7. Resolve rejections via the AlternativesDrawer if needed 👉 This supports end-to-end link placement management. 🧠 Best Practices - Review publication details before purchasing - Ensure article content is accurate and relevant - Confirm costs before checkout - Monitor order status after purchase - If a publication is rejected, act quickly in the AlternativesDrawer to either re-route the placement or refund the HDC MCP for LinkLab allows you to manage article placements through conversation. From discovering publications to completing purchases and tracking results, your AI assistant can execute each step using the same capabilities available in Search Atlas, including paid placement workflows powered by Hyperdrive Credits.

📘 MCP Supported Clients & Environments

This means you are not limited to a single interface — you can connect MCP across multiple environments depending on how you prefer to work. This article explains which clients are supported, how they differ, and how MCP behaves across environments. 🧠 What "Supported Client" Means A supported client is any application that can connect to an MCP endpoint, authenticate with Search Atlas, and execute MCP tool calls. 👉 MCP is not tied to a single UI — it is a protocol-based system. 🔍 Supported Clients Search Atlas currently supports the following MCP-compatible clients: - Claude Desktop - Claude.ai - Cursor - ChatGPT connectors All of these can connect to the MCP endpoint: https://mcp.searchatlas.com/mcp/ ⚙️ Step-by-Step: Connect in Any Client Step 1. Open your MCP-compatible client. Step 2. Add a new MCP server. Step 3. Use the endpoint https://mcp.searchatlas.com/mcp/. Step 4. Start the connection. Step 5. Complete the OAuth login in your browser. Step 6. Return to the client. Your MCP connection is now active. 🖥️ How Different Clients Are Used Claude Desktop / Claude.ai — Best for conversational workflows, non-technical users, and general usage. Cursor — Best for developers working inside code editors and integrating MCP into development workflows. ChatGPT Connectors — Best for using MCP within ChatGPT-supported environments. 🔁 Same System, Different Interface Regardless of the client, the same MCP endpoint is used, the same authentication applies, the same tools are available, and the same quotas and permissions are enforced. 👉 Only the interface changes — not the capabilities. ⚠️ Important Notes 1. MCP behavior is consistent across all clients. 2. Differences are only in how actions are triggered. 3. Approval flows depend on client support (for example, Claude supports human-in-the-loop prompts). 🛠️ Troubleshooting Across Clients Issue — Works in one client but not another. Possible causes: not authenticated in that client, MCP not connected, or session expired. Step-by-step fix: 1. Reconnect MCP in the affected client. 2. Complete OAuth login again. 3. Retry the action. 🔁 Best Practice 💡 Choose your client based on workflow: use Claude for ease of use, or Cursor for development workflows. All clients behave the same once connected. MCP is designed to be flexible across environments. Whether you are working in a conversational UI or a code editor, you can access the same Search Atlas capabilities through your AI assistant, using the same permissions, quotas, and system behavior tied to your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📘 MCP Rate Limits & API Limits

The Search Atlas MCP follows the same rate limits and system constraints as the underlying Search Atlas API. This means all requests made through MCP are subject to standard API limits, including request throttling and usage constraints. 🧠 How Rate Limits Work MCP does not introduce its own rate limiting system. Instead, it relies on the existing Search Atlas API limits. 👉 Every request made through your AI assistant is processed as an API call. 👉 If too many requests are made in a short period of time, the system may temporarily block additional requests. You can view your current quota and usage status from Avatar → Billing → Plans & Top-ups (Total Quota) in your Search Atlas dashboard. For specific rate and quota thresholds applicable to your plan, refer to the Search Atlas API limits reference documentation. ⚙️ Step-by-Step: What Happens When You Hit a Rate Limit Step 1 You send multiple requests through your AI assistant Example: - Running multiple audits - Generating large batches of content - Executing repeated tool calls Step 2 The MCP forwards requests to the Search Atlas API Step 3 The API evaluates request volume Step 4 If the limit is exceeded: - The request is rejected - A rate limit error is returned (commonly a 429 error) - A 429 error can result from two distinct causes: (1) request-frequency rate limiting, or (2) plan quota exhaustion. Check your quota dashboard when you receive a 429 to determine which condition applies. 🚦 429 vs. ACCESS_DENIED: Understanding the Difference A 429 error and an ACCESS_DENIED error are not the same and should be troubleshooted differently: - 429 (rate limit / quota exhausted): Returned when your request frequency is too high or your plan quota has been exhausted. - ACCESS_DENIED: Returned when the specific MCP endpoint you are calling is not publicly enabled for your account. Some MCP endpoints are not yet publicly available for general use, so ACCESS_DENIED does not necessarily mean you have exceeded your plan quota. If you see ACCESS_DENIED despite your dashboard showing available quota, the endpoint you are calling may not be publicly enabled for MCP. Contact support to confirm whether the specific MCP tool is available on your plan. ⚠️ Common Scenarios That Trigger Rate Limits 1. Rapid repeated requests 2. Large batch operations executed too quickly 3. High-frequency automation tasks ⚙️ Step-by-Step: How to Resolve Rate Limit Errors Step 1 Stop sending new requests Step 2 Wait at least 60 seconds before retrying. For persistent 429 errors related to quota exhaustion, the limit typically resets at the start of your next billing cycle. Step 3 Retry the request Step 4 If needed, reduce request frequency 🛠️ Unexpected Quota or Limit Issues If you believe your quota usage is being over-reported or you are hitting limits unexpectedly early in a billing cycle, contact support — in some cases backend counter drift or billing-sync defects can cause incorrect quota readings that require an engineer to correct. Additionally, if your account shows a limit of 0 or is unexpectedly fully blocked despite low actual usage, this may be a plan/quota calculation defect. In that case, contact support rather than simply waiting or reducing request frequency. 🔁 Best Practices To avoid hitting rate limits: - Space out large operations - Avoid sending repeated requests in rapid succession - Break large workflows into smaller steps ⚠️ Important Notes 1. Rate limits apply equally to MCP and direct API usage 2. Limits are enforced automatically by the system 3. MCP does not override or bypass these limitsRate limits apply equally to MCP and direct API usage 4. Limits are enforced automatically by the system 5. MCP does not override or bypass these limits MCP uses the same infrastructure and protections as the Search Atlas API, including rate limits. By pacing your requests and structuring workflows efficiently, you can avoid interruptions and maintain smooth execution when working through your AI assistant.

📘 MCP for Google Business Profile (Local SEO)

Use MCP to manage your Google Business Profile (GBP) locations, content, and optimization workflows through the Local SEO product area. The MCP provides full Google Business Profile management, including locations, services, hours, attributes, categories, posts, reviews, media uploads, and audit reports. 🧠 What You Can Do Using MCP for Local SEO (GBP), you can: - Manage locations - Update categories, attributes, and services - Create and publish posts - Respond to reviews with AI-generated replies - Upload and manage media - Run audit reports - Submit and track citations ⚙️ Step-by-Step: Manage GBP Locations 📌 Step 1 Open your MCP-connected AI assistant 📌 Step 2 Ask to view your locations Examples: - “Show me my GBP locations” - “List all my business locations” 📌 Step 3 Review your locations The assistant returns your available locations and their details. 🧩 Step-by-Step: Update Categories, Attributes & Services 📌 Step 1 Ask your assistant: - “Update my GBP categories” - “Add attributes to my location” - “Update services for my business” 📌 Step 2 The assistant prepares the updates 📌 Step 3 Confirm changes (if required) 📌 Step 4 The MCP applies updates to your GBP profile 📝 Step-by-Step: Create & Publish Posts 📌 Step 1 Ask your assistant: - “Create a GBP post for my business” - “Publish a promotion post” 📌 Step 2 The assistant generates the post content 📌 Step 3 Review the draft 📌 Step 4 Approve and publish the post Posts are then pushed to your Google Business Profile. 💬 Step-by-Step: Respond to Reviews 📌 Step 1 Ask your assistant: - “Show me my GBP reviews” - “Respond to my latest review” 📌 Step 2 The assistant retrieves reviews 📌 Step 3 The assistant generates a reply 📌 Step 4 Approve the response The reply is then published to your GBP listing. 📸 Step-by-Step: Manage Media 📌 Step 1 Ask your assistant: - “Upload images to my GBP profile” - “Show my GBP media” 📌 Step 2 The assistant processes the request 📌 Step 3 Media is uploaded and associated with your listing 📊 Step-by-Step: Run GBP Audit Reports 📌 Step 1 Ask your assistant: - “Run a GBP audit for my location” 📌 Step 2 The assistant generates the audit 📌 Step 3 Review results and recommendations 🌐 Step-by-Step: Manage Citations 📌 Step 1 Ask your assistant: - “Create citations for my business” - “Submit my business to directories” 📌 Step 2 The assistant prepares citation data 📌 Step 3 Submit to selected networks 📌 Step 4 Track progress and status ⚠️ Important Notes - Actions like audits, content generation, and submissions consume Search Atlas quota - Publishing and updating existing content does not consume additional quota - Some actions may require confirmation before execution 🔁 How This Fits Together The GBP workflow through MCP typically follows: 1. Manage locations 2. Optimize categories, attributes, and services 3. Create posts and content 4. Respond to reviews 5. Upload media 6. Run audits and manage citations All actions are executed through your AI assistant using the same system as the Search Atlas platform. MCP enables full Google Business Profile management through conversation. From optimizing your listing to publishing content and managing reviews, your AI assistant can execute every step using the same tools, permissions, and quotas available in your Search Atlas account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📘 MCP for Press Releases

The Press Release system allows you to draft AI-generated releases and distribute them through the Search Atlas network. Through MCP, your AI assistant can manage the full lifecycle from writing to publication and tracking. This article explains how to generate, publish, and manage press releases using MCP. 🧠 What You Can Do Using MCP with Press Releases, you can: - Draft press releases - Generate content using AI - Select categories and distribution networks - Publish and distribute releases - Track distribution status - Monitor quota usage Premium press release distribution tiers may consume Hyperdrive Credits (HDC). ⚙️ Create a Press Release 1. Open your MCP-connected AI assistant. 2. Ask to create a press release, for example: "Write a press release for my business." 3. The assistant generates the draft. 4. Review the content. ✍️ Edit and Finalize Content 1. Ask your assistant, for example: "Edit this press release" or "Refine the content." 2. The assistant updates the draft. 3. Review the final version and ensure accuracy before distribution. 📡 Select Distribution Settings 1. Ask your assistant, for example: "Prepare this press release for distribution." 2. Specify the category and distribution network. 3. Confirm the settings. 📤 Publish and Distribute 1. Ask your assistant, for example: "Publish this press release." 2. The assistant prepares the distribution. 3. Approve the action, if required — distribution may involve external publication and potential HDC usage. 4. The press release is published. 📊 Track Distribution Status 1. Ask your assistant, for example: "Show my press release status." 2. The assistant retrieves distribution data. 3. Review publication status, distribution progress, and campaign results. ⚠️ Important Notes 1. Drafting uses AI and may consume Search Atlas quota. 2. Distribution may consume Hyperdrive Credits (HDC). 3. Publishing interacts with external networks. 4. Approval may be required before execution. 🔁 How This Fits Into MCP Workflows A typical workflow: generate the press release, edit and finalize it, select distribution settings, publish, then track results — supporting end-to-end PR execution. 🧠 Best Practices 1. Review content before publishing. 2. Choose appropriate distribution categories. 3. Monitor distribution status after publishing. 4. Use PR alongside SEO and content strategies. MCP for Press Releases allows you to manage the full lifecycle of PR campaigns through conversation. From drafting to distribution and tracking, your AI assistant can execute each step using the same capabilities available in Search Atlas, including premium distribution options where applicable. 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.

📘 MCP for Website Studio

Website Studio allows you to create projects, publish websites, and manage automation workflows connected to other Search Atlas products. Through MCP, your AI assistant can handle project creation, publishing, and synchronization tasks. This article explains how to create Website Studio projects, publish them, and manage their lifecycle using MCP. 🧠 What You Can Do Using MCP with Website Studio, you can: - Create Website Studio projects - List and manage projects - Publish websites - Monitor credit status - Sync projects with OTTO PPC - Manage automation workflows Website Studio is focused on project creation and automated website management. ⚙️ Create a Website Project 1. Open your MCP-connected AI assistant. 2. Ask to create a project, for example: "Create a Website Studio project." 3. The assistant creates the project. 4. Confirm the project details — this establishes your website project. 📋 View and Manage Projects 1. Ask your assistant, for example: "Show my Website Studio projects." 2. The assistant retrieves the project list. 3. Review the available projects. 📤 Publish a Website 1. Ask your assistant, for example: "Publish my website project." 2. The assistant prepares the publication. 3. Approve the action, if required. 4. The website is published and made live. 📊 Monitor Credit Status 1. Ask your assistant, for example: "Check my Website Studio credits." 2. The assistant retrieves credit data. 3. Review available credits and usage status. 🔄 Sync with OTTO PPC 1. Ask your assistant, for example: "Sync this project with OTTO PPC." 2. The assistant initiates synchronization. 3. Confirm the sync. 🔁 Manage Automation Workflows 1. Ask your assistant, for example: "Manage my Website Studio automation." 2. The assistant retrieves automation data. 3. Update or manage the workflows. ⚠️ Important Notes 1. Creating and publishing projects may consume credits. 2. Publishing is an external-facing action. 3. Some actions may require approval. 4. Integration with other tools depends on plan access. 🔁 How This Fits Into MCP Workflows A typical workflow: create the project, configure and manage it, publish the website, monitor credits and status, then sync with other tools. 🧠 Best Practices - Review project setup before publishing. - Monitor credit usage regularly. - Use integrations to connect workflows. - Manage automation carefully. MCP for Website Studio allows you to create and manage websites through conversation. From project creation to publishing and automation, your AI assistant can execute website workflows using the same capabilities available in Search Atlas. 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.

📘 MCP for Data Retrieval & Read-Only Actions

Read-only actions allow your AI assistant to access existing data — such as reports, backlinks, usage, and analytics — without generating new work. This article explains what read-only actions are, how they work, when to use them, and how they differ from execution-based actions. 🧠 What Read-Only Actions Are Read-only actions are MCP operations that retrieve existing data, display reports or analytics, and inspect current state (projects, campaigns, profiles). They do not create, modify, or submit anything. Because of this, they do not consume Search Atlas quota — they only consume AI assistant tokens. 🔍 What You Can Retrieve Using MCP read-only actions, you can access: - Backlink data - Keyword data - SEO reports - GBP locations and data - Campaign performance - Usage and quota information - Previously generated content These actions allow you to explore and analyze your data before deciding to execute changes. ⚙️ Retrieve Data Using MCP 1. Open your MCP-connected AI assistant. 2. Ask for data or insights, for example: "Show me my backlinks," "Check my quota," "Show my GBP locations," or "View my SEO audit results." 3. The assistant retrieves existing data — no new work is created, the MCP simply returns stored or previously generated information. 4. Review the results to analyze performance, identify issues, and plan next steps. 🔁 Use Read-Only Before Execution 1. Start with a read-only request, for example: "Show me my SEO issues." 2. Review the data. 3. Decide on the next action, for example: "Apply fixes" or "Generate recommendations." 4. Execute only after review — this ensures controlled and intentional usage. ⚖️ Read-Only vs Work-Producing Actions - Read-only actions retrieve data, do not consume quota, and are used for analysis. - Work-producing actions generate, create, or submit, do consume quota, and are used for execution. 📊 Examples - Read-only — "Show me my backlinks": uses tokens, no quota consumed. - Execution — "Build backlinks for my site": uses tokens, consumes quota. - Hybrid workflow — "Show me keyword gaps" (read-only), then "Create content for those keywords" (execution). ⚠️ Important Notes 1. Read-only actions are safe and non-destructive. 2. They do not trigger approvals in most cases. 3. They are ideal for exploration and planning. 4. They still depend on your permissions and plan access. 🧠 Best Practices - Always begin with read-only queries before executing changes. - Use read-only actions to confirm data before running high-cost actions. - Combine read-only insights with execution to guide actions. Read-only actions are the safest and most efficient way to start working with MCP. By retrieving and analyzing data first, you can make better decisions, avoid unnecessary credit usage, and execute actions with confidence using your AI assistant. 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.

📘 MCP for Account & Billing

The Account & Billing tools give your AI assistant visibility into your Search Atlas account so it can help you track subscription status, usage, and billing without you having to log in and check manually. This article explains how to check your account status, monitor usage, and review billing details through MCP. 🧠 What You Can Do Using MCP for Account & Billing, you can: - View account information - Check subscription status - Monitor quota and usage - View billing balances - Review payment-related details 👉 These tools provide visibility into your account and usage across Search Atlas. ⚙️ Step-by-Step: View Account Information Step 1. Open your MCP-connected AI assistant. Step 2. Ask for account details, for example: "Show my account information." Step 3. The assistant retrieves your account data. Step 4. Review the account details returned. 💳 Step-by-Step: Check Subscription Status Step 1. Ask your assistant: "What is my subscription status?" Step 2. The assistant retrieves your subscription data. Step 3. Review your active plan and subscription status. 📊 Step-by-Step: Monitor Usage and Quota Step 1. Ask your assistant: "Check my usage" or "Show my quota." Step 2. The assistant retrieves your usage data. Step 3. Review your quota usage and remaining credits. 💰 Step-by-Step: View Billing Balance Step 1. Ask your assistant: "Show my billing balance." Step 2. The assistant retrieves your balance data. Step 3. Review your account balance and payment status. 🧾 Step-by-Step: Review Payment Information Step 1. Ask your assistant: "Show my billing details." Step 2. The assistant retrieves your billing information. Step 3. Review payment-related data and billing records. ⚠️ Important Notes 1. Billing data is read-only through MCP. 2. Viewing account data does not consume Search Atlas quota. 3. Payments and billing changes may require action outside of MCP. 4. Data reflects your current Search Atlas account status. 🔁 How This Fits Into MCP Workflows A typical workflow looks like this: 1. Check account status. 2. Monitor quota and usage. 3. Review billing balance. 4. Confirm readiness before executing actions. 👉 This helps prevent interruptions caused by quota or billing issues. 🧠 Best Practices 1. Check quota before running large actions. 2. Monitor billing regularly. 3. Confirm subscription status when features are unavailable. 4. Use account data to plan your usage. MCP for Account & Billing gives you visibility into your Search Atlas account through conversation. By checking usage, subscription status, and billing details, your AI assistant helps you stay in control of your resources while using the platform's capabilities. 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.

🛡️ Virtual Mode and the (Virtual) Badge in the Search Atlas WordPress Plugin

When the Search Atlas WordPress plugin cannot write to the physical robots.txt file on your server, it automatically activates Virtual Mode and serves your robots.txt rules from the WordPress database instead. The (Virtual) badge in the plugin UI confirms this mode is active. 🛡️ What Virtual Mode Is Virtual Mode is a built-in fallback mechanism in the Search Atlas WordPress plugin. Instead of reading and writing a physical robots.txt file on your server's filesystem, the plugin stores and delivers your robots.txt rules directly from the WordPress database. Your robots.txt rules remain fully active in Virtual Mode — search engine crawlers receive the correct content. The only difference is where the rules live and how they are delivered. ⚡ When Virtual Mode Activates The plugin switches to Virtual Mode automatically when it detects it cannot write to the physical robots.txt file at the root of your WordPress installation. Common causes include: - The web server user (e.g., www-data or nginx) does not have write permission to the site root directory. - An existing robots.txt file is owned by a different user or set to read-only. - Your hosting environment restricts filesystem writes for security reasons — common on managed WordPress hosts such as WP Engine or Kinsta. No manual configuration is required. The plugin detects the permission state automatically and activates Virtual Mode on its first request. Note on CDN or caching layers: If a CDN or caching layer is active, ensure it is configured to pass robots.txt requests through to WordPress, or to purge the cached robots.txt after changes — otherwise crawlers may see a stale version even when Virtual Mode is working correctly. 🏷️ What the (Virtual) Badge Means When Virtual Mode is active, the Search Atlas plugin displays a (Virtual) badge next to the robots.txt section in the plugin UI. This badge confirms: - The plugin is serving your robots.txt rules from the WordPress database, not from a physical file on disk. - Rules you save in the plugin are stored in the database and delivered dynamically to search engine crawlers. - Your SEO configuration is fully active — crawlers receive the correct robots.txt content. Seeing the (Virtual) badge means your setup is working correctly in Virtual Mode. Other robots.txt panel indicators All timestamps in the robots.txt panel — including the last-modified time and backup history entries — reflect the timezone configured in WordPress Settings → General. The plugin also surfaces a validation warning when a blanket Disallow: / rule is detected, alerting administrators before they accidentally block all crawlers. (A previous bug silently suppressed this warning; it now triggers correctly after updating.) 🔍 How to Confirm Virtual Mode Is Active 1. In your WordPress admin, go to Search Atlas → Robots.txt. 2. Look for the (Virtual) badge displayed next to the robots.txt heading or status indicator. 3. If the badge is visible, Virtual Mode is active and your rules are being served from the database. 4. To verify your rules are live, visit https://yourdomain.com/robots.txt in a browser — you should see the exact rules you configured in the plugin. If your configured rules appear at that URL, Virtual Mode is working as intended. If the (Virtual) badge does not appear after saving, ensure you are running the latest version of the Search Atlas WordPress plugin — an earlier bug prevented the badge from displaying after the first page load. A plugin update or cache flush resolves it. ⚠️ (Virtual) Badge Disappearing — Known Issue (Now Fixed) A bug in the Search Atlas WordPress plugin caused the (Virtual) badge to silently disappear from the UI after the first request, even though Virtual Mode remained active and robots.txt continued to be served correctly from the database. The root cause was a strict type comparison in the plugin's robots.txt class that incorrectly evaluated the Virtual Mode state after the initial check. Symptoms of this bug - Virtual Mode was active and robots.txt rules were being delivered to crawlers correctly. - The (Virtual) badge vanished from the plugin UI after the initial page load or request. - No error or warning message appeared — the badge simply stopped showing. How to apply the fix 1. In your WordPress admin, go to Plugins → Installed Plugins. 2. Find Search Atlas and click Update if an update is available. 3. After updating, go to Search Atlas → Robots.txt and confirm the (Virtual) badge is now consistently visible. If you have already updated and the badge is still missing, contact Search Atlas support. 🔧 How to Restore Physical robots.txt Write Access If you prefer the plugin to write directly to a physical robots.txt file rather than using Virtual Mode, you need to grant the web server write permission to your site's root directory. The exact steps depend on your hosting environment. Check current file permissions 1. Connect to your server via SSH or your hosting control panel's file manager. 2. Navigate to the root of your WordPress installation — the folder containing wp-config.php. 3. Check whether a robots.txt file exists and note its owner and permissions. Grant write permission - If robots.txt already exists, set its permissions to 644 and ensure the web server user (e.g., www-data) is the owner. - If robots.txt does not exist, ensure the web server user has write permission on the site root directory so the plugin can create the file. - On managed hosts (e.g., WP Engine, Kinsta, Flywheel), filesystem write restrictions are often enforced by the platform — contact your host's support team for guidance before changing permissions. After write access is restored, the plugin automatically detects the change on the next save and exits Virtual Mode. The (Virtual) badge will no longer appear. 🎯 You now know what Virtual Mode is, when it activates, and what the (Virtual) badge signals in the Search Atlas WordPress plugin. If the badge disappeared before a recent plugin update, upgrading to the latest version restores the display — your robots.txt rules were being served correctly the entire time. For more on configuring your crawl directives, see the Robots.txt Settings in Search Atlas article.

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

📘 MCP for Report Builder

Report Builder allows you to generate custom reports using data from multiple Search Atlas product areas. Through MCP, your AI assistant can create reports, manage templates, and retrieve report outputs. This article explains how to create reports, manage templates, and retrieve reporting data using MCP. 🧠 What You Can Do Using MCP with Report Builder, you can: - Create custom reports - Use and manage report templates - Pull data from multiple product areas - Generate and retrieve reports - Manage reporting workflows Reports consolidate data across tools into a single output. ⚙️ Create a Report 1. Open your MCP-connected AI assistant. 2. Ask to create a report, for example: "Create a report" or "Generate a custom SEO report." 3. The assistant prepares the report. 4. Confirm the report setup — reports can include data from multiple product areas. 🧩 Use Report Templates 1. Ask your assistant, for example: "Show available report templates." 2. The assistant retrieves the templates. 3. Select a template. 4. Apply the template to generate the report. 📊 Generate Report Data 1. Ask your assistant, for example: "Generate report data." 2. The assistant compiles data. 3. Review the report output — data is aggregated from multiple sources. 📥 Retrieve Reports 1. Ask your assistant, for example: "Show my reports." 2. The assistant retrieves the report list. 3. Select a report. 4. Review the report details. 🔁 Manage Reports 1. Ask your assistant, for example: "Manage my reports." 2. The assistant retrieves report data. 3. Update or regenerate reports as needed. ⚠️ Important Notes - Generating reports may consume Search Atlas quota. - Viewing existing reports is read-only. - Report content depends on available data sources. - Reports combine data across multiple tools. 🔁 How This Fits Into MCP Workflows A typical workflow: select or create a report, apply a template, generate report data, review the output, then update as needed — supporting consolidated performance reporting. 🧠 Best Practices 1. Use templates for consistency. 2. Verify included data sources. 3. Regenerate reports after major updates. 4. Use reports to guide decisions. MCP for Report Builder allows you to generate and manage reports through conversation. By combining data from multiple Search Atlas tools into structured outputs, your AI assistant can help you monitor performance and track results using the same capabilities available in the platform. 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.

📘 MCP for SEO & Site Audits (OTTO)

Use MCP to run SEO audits, generate recommendations, and deploy optimizations using the OTTO product area. OTTO is the Search Atlas system for site audits, SEO recommendations, schema management, and indexing. Through MCP, your AI assistant can execute the full audit and optimization workflow on your behalf. 🧠 What You Can Do Using MCP with OTTO, you can: - Run full site audits - Generate prioritized SEO recommendations - Review issues and summaries - Edit and deploy fixes - Manage schema markup - Submit URLs for indexing ⚙️ Step-by-Step: Run an SEO Audit 📌 Step 1 Open your MCP-connected AI assistant 📌 Step 2 Ask for an audit Examples: - “Run a site audit for my website” - “Audit my domain and show me SEO issues” 📌 Step 3 The assistant creates an audit and retrieves results The MCP runs a full site audit and returns issue summaries and recommendations. 📌 Step 4 Review the results You will see: - SEO issues - priority levels - recommended fixes 🛠️ Step-by-Step: Generate SEO Recommendations 📌 Step 1 Ask your assistant: - “Generate SEO recommendations for my site” - “Show me fixes for my audit issues” 📌 Step 2 The assistant generates recommendations These are prioritized and based on your audit data. 📌 Step 3 Review the recommendations Each recommendation includes suggested actions to improve SEO performance. 🚀 Step-by-Step: Deploy Fixes 📌 Step 1 Ask your assistant: - “Apply SEO fixes to my site” - “Deploy the recommended changes” 📌 Step 2 The assistant prepares the deployment 📌 Step 3 Confirm the action (if required) Some actions may require approval before execution. 📌 Step 4 The MCP deploys the fixes Changes are applied using the same system as the Search Atlas app. 🧱 Step-by-Step: Manage Schema & Indexing 🧱 Schema Management Ask: - “Add schema markup to my pages” - “Update my site schema” The assistant can manage page-level and domain-level schema. 📥 Indexing Ask: - “Submit these URLs for indexing” - “Index my new pages” The MCP submits URLs through the indexing system. ⚠️ Important Notes - Audits, recommendations, and indexing actions consume Search Atlas quota - Deploying already-generated fixes does not consume additional quota - Some actions may require confirmation before execution 🔁 How This Fits Together The OTTO workflow through MCP follows this sequence: 1. Run audit 2. Generate recommendations 3. Review issues 4. Deploy fixes 5. Manage schema and indexing All steps are executed through your AI assistant using the same system as the Search Atlas platform. MCP allows you to manage your entire SEO audit and optimization workflow through conversation. From identifying issues to deploying fixes and indexing pages, your AI assistant can execute each step using the same tools, permissions, and quotas available in your Search Atlas account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📘 MCP for Indexer

The Indexer allows you to send batches of URLs for indexing, check submission status, and retrieve reports. Through MCP, your AI assistant can manage the full submission workflow. This article explains how to submit URLs, monitor indexing status, and manage indexing reports using MCP. 🧠 What You Can Do Using MCP with the Indexer, you can: - Submit batches of URLs for indexing - Check submission status - View submission details - Download indexing reports 👉 Indexing actions are processed through Search Atlas's indexing service, which handles submission to search engines on your behalf. ⚙️ Step-by-Step: Submit URLs for Indexing Step 1. Open your MCP-connected AI assistant. Step 2. Ask to submit URLs, for example: "Submit these URLs for indexing." Step 3. Provide the list of URLs. Step 4. The assistant submits the batch. 👉 This action requires your confirmation before it runs, since it uses indexing quota. 🔄 Step-by-Step: Check Submission Status Step 1. Ask your assistant: "Check indexing status." Step 2. The assistant retrieves the batch status. Step 3. Review submission progress and indexing updates. 📊 Step-by-Step: View Submission Details Step 1. Ask your assistant: "Show indexing details for my URLs." Step 2. The assistant retrieves detailed data. Step 3. Review individual URL status and submission results. 📥 Step-by-Step: Download Reports Step 1. Ask your assistant: "Download indexing report." Step 2. The assistant prepares the report. Step 3. Review the report data. 👉 Reports summarize indexing activity and results. ⚠️ Important Notes 1. Submitting URLs consumes Indexer quota. 2. Viewing status and reports is read-only. 3. Indexing results depend on the receiving search engine's own processing. 4. Submissions interact with external systems. 🔁 How This Fits Into MCP Workflows A typical workflow: 1. Submit URLs. 2. Monitor indexing status. 3. Review reports. 4. Repeat as needed. 👉 This supports ongoing indexing management. 🧠 Best Practices 1. Submit important or updated URLs. 2. Monitor indexing progress regularly. 3. Use reports to track results. 4. Combine with SEO workflows for best outcomes. MCP for Indexer allows you to manage URL submissions through conversation. By submitting batches, tracking status, and reviewing reports, your AI assistant can handle indexing workflows using the same capabilities available in Search Atlas. 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.

📘 MCP for Brand Vault & Knowledge Graph

Use MCP to manage your Brand Vault and Knowledge Graph, which store your business data, brand voice, and structured information used across Search Atlas tools. The Brand Vault acts as a centralized data layer that powers content generation, SEO, and automation workflows. Through MCP, your AI assistant can read and update this data directly. 🧠 What You Can Do Using MCP with Brand Vault and the Knowledge Graph, you can: - Store and manage business information - Define brand voice and tone - Provide source material for AI content generation - Maintain structured business data used across tools ⚙️ View Your Brand Data 1. Open your MCP-connected AI assistant. 2. Ask to retrieve your Brand Vault data, for example: "Show my brand information" or "What data is stored in my Brand Vault?" 3. The assistant retrieves your stored data, which may include business details, brand voice, and structured information used across the platform. ✍️ Update Brand Information 1. Ask your assistant, for example: "Update my business description in Brand Vault" or "Change my brand tone to more professional." 2. The assistant prepares the update. 3. Review the changes. 4. Confirm, if required. 5. The MCP updates your Brand Vault. 🧩 Use Brand Data in Content 1. Ask your assistant, for example: "Write content using my brand voice." 2. The assistant retrieves Brand Vault data. 3. Content is generated using your tone, your business information, and your stored sources. 🧱 How the Knowledge Graph Works The Knowledge Graph is the structured representation of your business data inside Search Atlas. It includes business identity, services and offerings, structured attributes, and supporting content. This data is used across content generation, SEO tools, and automation workflows. ⚠️ Important Notes - Updating Brand Vault data affects multiple product areas. - Content generation relies on this data for accuracy. - Changes should reflect real business information. - Some updates may require confirmation before execution. 🔁 How This Fits Together The Brand Vault workflow through MCP typically follows: store business data, define brand voice, use that data in content generation, then update it as your business evolves. All actions are executed through your AI assistant using the same system as the Search Atlas platform. 🧠 Best Practice Keep your Brand Vault accurate and complete. This ensures better AI-generated content, more consistent brand voice, and more accurate SEO and automation outputs. The Brand Vault and Knowledge Graph are the foundation of how Search Atlas understands your business. By managing this data through MCP, you ensure that every action — from content generation to SEO optimization — is aligned with your brand and business reality. 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.

📘 MCP for Digital PR

The Digital PR system enables email-based outreach to publishers and prospects. Through MCP, your AI assistant can create campaigns, manage templates, send outreach, and handle replies. This article explains how to set up outreach campaigns, manage communication, and track responses using MCP. 🧠 What You Can Do Using MCP with Digital PR, you can: - Create outreach campaigns - Build and manage email templates - Identify outreach opportunities - Schedule and send emails - Monitor inbox and replies - Manage connected email accounts ⚙️ Create an Outreach Campaign 1. Open your MCP-connected AI assistant. 2. Ask to create a campaign, for example: "Create a digital PR campaign" or "Start an outreach campaign." 3. The assistant sets up the campaign. 4. Review the campaign setup. ✉️ Create Email Templates 1. Ask your assistant, for example: "Create an outreach email template." 2. The assistant generates the template. 3. Review and refine the content — templates are used for outreach emails. 🎯 Identify Opportunities 1. Ask your assistant, for example: "Find outreach opportunities." 2. The assistant retrieves potential prospects. 3. Review the opportunities. 📤 Send Outreach Emails 1. Ask your assistant, for example: "Send outreach emails." 2. Confirm recipients and the template. 3. The assistant schedules or sends the emails. 📬 Monitor Replies 1. Ask your assistant, for example: "Show campaign replies" or "Check my outreach inbox." 2. The assistant retrieves replies. 3. Review the responses. 🔁 Manage Campaigns 1. Ask your assistant, for example: "Manage my outreach campaign." 2. The assistant retrieves campaign data. 3. Make updates. 4. Continue or adjust the campaign. ⚠️ Important Notes 1. Outreach involves external communication. 2. Email sending may require connected accounts. 3. Campaign success depends on recipient engagement. 4. Actions may consume quota depending on execution. 🔁 How This Fits Into MCP Workflows A typical workflow: create the campaign, build templates, identify prospects, send outreach, then monitor replies. This enables full outreach campaign management through conversation. 🧠 Best Practices 1. Review templates before sending. 2. Target relevant prospects. 3. Monitor replies regularly. 4. Adjust campaigns based on responses. MCP for Digital PR allows you to run outreach campaigns through conversation. From creating templates to sending emails and managing replies, your AI assistant can execute the full campaign lifecycle using the same capabilities available in Search Atlas. 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.

📘 OAuth vs API Key — Authentication Explained

The Search Atlas MCP uses credentials issued by the main Search Atlas platform. It does not issue its own authentication system. There are two supported authentication methods: OAuth (recommended) and API Key (advanced use only). This article explains how each method works, when to use them, and which one you should choose. 🔑 OAuth — Recommended for All Users OAuth is the recommended and supported authentication method for all customer-facing scenarios. 1. Add the MCP endpoint in your MCP-compatible client: https://mcp.searchatlas.com/mcp/ 2. Start the connection process in your client. 3. A browser window opens automatically. 4. Sign in to your Search Atlas account. 5. Complete the login and approval. 6. Return to your client. The connection is now saved, and the client will automatically handle credential storage and refresh going forward. 🔐 What Happens After OAuth Login Once connected, your client holds the credential and refreshes it automatically — you do not need to log in again for future sessions. All MCP actions will use your Search Atlas account, follow your plan entitlements, and respect your quota limits. ⚙️ API Key — Advanced / Programmatic Use The MCP also supports authentication using a Search Atlas API key via the X-API-Key header. This method is intended for scripts, server-to-server integrations, and non-interactive environments. Important limitations: there is no browser login flow, no automatic credential refresh, and it requires manual handling of the API key. ⚠️ Which One Should You Use? If you are a regular user, use OAuth. If you are building automation or backend integrations, use API Key. OAuth is the recommended path for all customer-facing scenarios. ⚠️ Common Issues - Authentication fails after login — this may happen if your session is expired. Disconnect and reconnect the MCP to refresh credentials. - Using API Key for normal usage — API keys are not recommended for standard usage. Switch to OAuth for a supported and smoother experience. OAuth is the standard way to connect MCP because it provides a secure, automatic, and fully supported authentication flow. API keys are available for advanced use cases, but most users should rely on OAuth to ensure a reliable connection and seamless experience. 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 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.

🛠️ Shopify CM Connector Setup, Dashboard Display Mode, and Subscription Refund

Overview This article addresses three related questions for Shopify users on Search Atlas: how to switch the backend dashboard from dark to light display mode, how to connect a Shopify store via the CMS (CM) Connector, and how to request a subscription refund. Does Search Atlas Have a Dark Mode / Light Mode Toggle? Search Atlas does not currently offer a dark mode. The dashboard is light mode only — there is no toggle, button, or settings option anywhere in the platform to switch between dark and light themes. If your Search Atlas dashboard appears dark, inverted, or incorrectly colored, the cause is almost always an external setting, not the platform itself: Chrome Auto Dark Mode 1. In Chrome, navigate to chrome://flags. 2. Search for Auto Dark Mode for Web Contents. 3. Set it to Disabled. 4. Click Relaunch to restart Chrome. 5. Reload Search Atlas — the dashboard should now display correctly in light mode. Operating System Dark Mode If your OS (Windows, macOS) is set to dark mode, some browsers inherit that preference and apply it to web content. Try disabling OS-level dark mode temporarily to confirm whether it is the source of the issue. How to Connect Your Shopify Store via the CM Connector The CMS Connector (CM Connector) in Search Atlas enables content synchronization between Search Atlas and your Shopify store, supporting blog publishing and content generation workflows. Step-by-Step Connection 1. In Search Atlas, click your avatar icon in the top-right corner and go to Settings → Integrations. 2. Locate Shopify in the integrations list and click Connect (or + Connect account). 3. You will be redirected to the Shopify OAuth authorization page — log in to your Shopify account if prompted. 4. Review the permissions requested by Search Atlas and approve the installation when prompted. 5. You will be redirected back to Search Atlas. Your Shopify store should now show as Connected in the integrations panel. Troubleshooting the CM Connector - Ensure you are logged in to Shopify as the store Owner or a staff member with app-installation permissions. - Confirm your Shopify account has the necessary permissions to install apps — refer to Shopify's documentation for plan-specific app installation requirements. - If the connection fails at the OAuth step, clear your browser cache and retry in an incognito window. - For Custom App (API key) connections, verify all required API scopes are enabled in your Shopify app settings. See the full Shopify connector troubleshooting article for the complete scope list. - If the connection continues to fail, check the Shopify CMS Connector Status article for known issues and the latest resolution status, or contact Search Atlas Support directly. After Connecting Once your Shopify store is connected, you can publish Content Genius articles directly to your Shopify blog. Navigate to Content → Content Planner, select your article, and choose your Shopify store as the destination CMS when scheduling the post. Requesting a Subscription Refund To request a refund for a Search Atlas subscription charge: 1. Open the in-app Help Widget (available at the bottom-right of every dashboard page). 2. Select Contact Support or Talk to a human to reach the support team. 3. Provide: your billing email address, the charge amount, the charge date, and the reason for your refund request. 4. If your refund request is related to a Shopify connector that did not work as expected, include documentation of the connection errors — screenshots or a screen recording will help the support team investigate faster. Approved refunds are returned to your original payment method. Processing time is determined by your bank or card issuer. Note: Refund eligibility is assessed case-by-case. Contacting support promptly after an issue is identified improves refund eligibility for recent charges. Related Articles - Troubleshooting Shopify Connector Failures in Search Atlas - Shopify CMS Connector Status in Search Atlas - CMS Connectors — How to Connect Your CMS to Search Atlas - Does Search Atlas Have Dark Mode? - How to Cancel Your Free Trial or Subscription in Search Atlas - Search Atlas Refund Approved: What to Expect

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

🚀 Export OTTO On-Page SEO Data to Rank Math

📋 What This Article Covers Many WordPress users manage their meta titles, descriptions, and other on-page elements with the Rank Math plugin. If you use OTTO in Search Atlas to generate on-page SEO recommendations, you can export that data in bulk and apply it inside Rank Math instead of editing each page manually. This guide explains how to export your OTTO on-page data and how to make sure the meta fields you need are included. If you have the Search Atlas WordPress (OTTO) plugin connected, OTTO can also sync your on-page optimizations directly into your active SEO plugin's data store when changes are saved, which can remove the need for a manual CSV import. Rank Math is a supported active SEO plugin, so with the plugin connected OTTO writes the optimized meta titles and descriptions straight into Rank Math's data store on every save. The CSV workflow described here is useful when you prefer to review and apply changes yourself, or when you are not using the plugin connection. ✅ Before You Begin Make sure you have the following ready: - An active Search Atlas account with OTTO enabled for your project. - OTTO has finished crawling your site and generated on-page recommendations. - Administrator access to the WordPress site that runs Rank Math. - The Rank Math plugin installed and activated. 📤 Step 1: Export Your OTTO On-Page Data Follow these steps inside Search Atlas to create your export file: 1. Open your project and go to the Left sidebar → Content → Onpage Audit to view all generated recommendations. 2. Review the list and confirm the pages you want to export are marked as deployed or ready. 3. Click the Export button at the top of the on-page table. 4. Choose CSV as the file format and confirm the download. The CSV file will download to your computer and contain one row per URL with the on-page fields OTTO has generated. 🔍 Why Meta Fields May Be Missing The most common reason an exported file appears to have no meta fields is that the affected pages did not have recommendations generated or deployed before the export. OTTO only includes fields it has actually produced values for. Check the following: - Recommendations not generated: If OTTO has not finished processing a page, its meta title and description columns will be empty. Wait for the crawl to complete and try again. - Suggestions generated for only top pages: A known issue with the Fix Critical On-Page SEO Issues AI playbook causes it to generate AI suggestions for only the top ~10% of pages rather than every page. Pages outside that set will export with empty meta title and description fields. A fix for this is currently awaiting release, and once it ships the playbook will generate suggestions for all pages rather than only the top set; in the meantime, confirm recommendations have been generated and deployed for the remaining pages before exporting. - Filtered view: If you applied a filter to the on-page table, the export may only reflect the visible rows. Clear all filters before exporting to capture every field. - Pending or undeployed changes: Pages with changes that are still pending may export blank values. Deploy or approve the recommendations first. - Column mismatch: When opening the CSV, confirm you are viewing the correct columns. Spreadsheet programs sometimes hide or misalign columns if the file is not imported with the right delimiter. 📥 Step 2: Map Your Columns for Rank Math Rank Math imports on-page data through its CSV Import & Export feature, which expects specific column names. Before importing, align your Search Atlas export to match the fields Rank Math recognizes: - id or url — used to match each row to the correct post or page. - rank_math_title — the SEO meta title. - rank_math_description — the meta description. - rank_math_focus_keyword — the target keyword, if available. Open your exported CSV in a spreadsheet program, rename the relevant Search Atlas columns to match the Rank Math field names above, and remove any columns Rank Math does not use. Save the file as CSV when finished. ⚙️ Step 3: Import the File into Rank Math 1. Log in to your WordPress dashboard. 2. Go to Rank Math SEO, then Status & Tools. 3. Select the Import & Export tab. 4. Scroll to the CSV Import section and upload your prepared file. 5. Match each column to the correct Rank Math field if prompted, then start the import. Rank Math will update the meta fields for each matched post. Review a few pages afterward to confirm the titles and descriptions appear correctly. 💡 Tips for a Clean Export - Always clear filters in the OTTO on-page table before exporting to ensure every field is included. - Confirm OTTO has finished crawling and generating recommendations before downloading. - Keep a backup copy of your original CSV before editing column names. - Import in smaller batches if you manage a large site, so you can spot any mapping issues early. - This export covers on-page meta fields. A full-site schema export/download (rather than page-by-page) is not yet available and is being tracked as an open feature request, so plan any schema work separately from this on-page export. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.

🔌 How to Connect Claude to Search Atlas via MCP

🧩 What Is MCP and Why Does It Matter? The Model Context Protocol (MCP) is an open standard that allows AI assistants like Claude to connect directly to external tools and data sources. By connecting Claude to Search Atlas via MCP, you can bring your SEO data, keyword insights, and site metrics directly into your Claude conversations — enabling AI-assisted workflows without switching between platforms. This integration allows Claude to query Search Atlas data on your behalf, helping you analyze keywords, review site metrics, and surface actionable SEO insights through natural language prompts. ✅ Prerequisites Before you begin, make sure you have the following in place: - An active Search Atlas account with API access enabled - Claude for Desktop installed on your machine (available from Anthropic) - Your Search Atlas API key (retrievable from Avatar Menu (👤) → Settings → API Keys) - Basic familiarity with editing configuration files on your operating system 🔑 Step 1: Retrieve Your Search Atlas API Key You will need your API key to authenticate the MCP connection between Claude and Search Atlas. 1. Log in to your Search Atlas account. 2. Navigate to Avatar Menu (👤) → Settings → API Keys. 3. Copy your key to a safe location. 4. Keep this key private — do not share it publicly or commit it to version control. ⚙️ Step 2: Configure Claude for Desktop to Use the Search Atlas MCP Server Claude for Desktop uses a configuration file to register MCP servers. Follow the steps below to add the Search Atlas MCP server. 1. Open Claude for Desktop on your computer. 2. Open the Claude for Desktop configuration file in a text editor. Refer to the official Anthropic Claude for Desktop documentation for the exact location of this file on your operating system. 3. Add the Search Atlas MCP server entry to the configuration file, providing your API key as specified in the Search Atlas MCP documentation. 4. Save the configuration file. 5. Restart Claude for Desktop to apply the changes. Refer to the official Search Atlas MCP documentation for the exact server name, command, and parameter fields required in your configuration file, as these may be updated over time. 🧪 Step 3: Verify the Connection Once Claude for Desktop has restarted, confirm that the integration is working correctly. 1. Open a new conversation in Claude for Desktop. 2. Check that Search Atlas tools are available. Refer to the Anthropic Claude for Desktop documentation for guidance on how loaded MCP tools are displayed in your version of the application. 3. Type a test prompt referencing your Search Atlas data to confirm the connection is active and returning results. 🛠️ Troubleshooting If the integration does not appear to be working after following the steps above, consider the following: - Double-check that your Search Atlas API key is entered correctly in the configuration file with no extra spaces or characters. - Ensure your Search Atlas account has API access enabled. - Confirm you are using a version of Claude for Desktop that supports MCP integrations. - Review both the Search Atlas MCP documentation and the Anthropic Claude for Desktop documentation for any version-specific setup requirements. 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 Cloudflare for OTTO

🔎 What This Integration Does​ OTTO needs a connection to your website so it can deploy SEO recommendations, such as meta tags, schema, and content updates, without you editing code by hand. Connecting through Cloudflare is one of the easiest methods because it works at the network level. Once linked, OTTO changes go live automatically, with no plugin or manual file edits required. There are two ways to set up the Cloudflare connection: the API token method covered in this guide, and a DNS-based installation method that you can choose when creating a new project. Both are selectable from the installation step in your project setup. This article focuses on the API token method. ​ ✅ Before You Begin​ Make sure you have the following ready: - An active Cloudflare account with your website added to it. - Your domain already routing traffic through Cloudflare (your nameservers point to Cloudflare). - Admin access to both your Search Atlas account and your Cloudflare account. - Permission to create an API token in Cloudflare.​ If your site is not yet on Cloudflare, add it there first and confirm it is active before continuing. 🔗 How to Connect via Cloudflare Follow these steps inside your Search Atlas dashboard: 1. Open OTTO SEO → All Sites (SEO Automation) from the left-hand menu and select your project. 2. When prompted to choose an installation method, select Cloudflare. 3. In a separate tab, log in to your Cloudflare account. 4. Go to My Profile, then API Tokens, and click Create Token. 5. Use a token template that grants Zone and Worker permissions, or follow the exact permissions listed on the Search Atlas connection screen. 6. Copy the generated API token. 7. Paste the token into the Cloudflare connection field in Search Atlas and click Connect. 8. Select the correct zone (domain) you want OTTO to manage and confirm.​ Search Atlas will verify the connection and confirm when OTTO is active on your site. If you prefer not to use an API token, you can instead choose the DNS installation method during new project creation and follow the on-screen DNS instructions. ⚙️ Activating OTTO Changes​ After the connection succeeds, OTTO deploys a lightweight script through Cloudflare. To make sure recommendations go live: - Confirm the OTTO toggle for your project is switched on. - Review the recommendations in your dashboard and approve the ones you want deployed. - Allow a few minutes for changes to apply across the Cloudflare network.​ 🛠️ Troubleshooting Common Issues​ If the connection fails or changes do not appear, check the following: - Invalid token: Recreate the API token and confirm it includes the required Zone and Worker permissions. - Wrong zone selected: Make sure you chose the exact domain you want OTTO to manage. - Site not on Cloudflare: Verify your nameservers point to Cloudflare and the domain shows as active. - Changes not visible: Clear your browser cache and Cloudflare cache, then recheck after a few minutes. - Caching plugins: Temporarily purge any third-party caches that may be serving an older version of your pages.​ 💡 Tips for a Smooth Setup​ - Use a dedicated API token for Search Atlas so it is easy to manage or revoke later. - Keep your Cloudflare account on a plan that supports Workers, as OTTO relies on them to deploy changes. - If the API token approach does not fit your setup, consider the DNS installation method available during project creation. - Re-check your connection status if you ever change your Cloudflare settings or nameservers.​ 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform and type "Human Teammate" to start a live chat with a member of our team.

⚙️ How 'Disable OTTO for Logged-in Users' Works in the WordPress Plugin

The Disable OTTO for Logged-in Users setting in the Search Atlas WordPress plugin is designed to hide OTTO-deployed titles from authenticated WordPress users. If you've enabled it and logged-in users are still seeing OTTO titles on your frontend, a confirmed bug is the cause. ⚙️ What 'Disable OTTO for Logged-in Users' Controls When OTTO deploys optimized titles to your site, it replaces the original page and meta titles on your frontend for all visitors. The Disable OTTO for Logged-in Users setting creates an exception for authenticated WordPress users. - Setting enabled: Logged-in WordPress users see the original, pre-OTTO page and meta titles on the frontend. - Setting disabled (default): All visitors — logged in or not — see OTTO-deployed titles. This is most useful for site administrators and editors who want to QA original content or compare it against OTTO's deployed version without logging out of WordPress. 🔧 How to Enable 'Disable OTTO for Logged-in Users' 1. Log in to your WordPress admin dashboard. 2. Navigate to the Search Atlas plugin settings. 3. Find the Disable OTTO for Logged-in Users toggle. 4. Turn the toggle on. 5. Click Save Changes. The setting saves immediately. Once the known issue below is resolved, logged-in WordPress users will see original titles when browsing your site's frontend. ⚠️ Known Issue: The Setting Has No Effect in the Current Plugin Version A confirmed bug (WP-313) means that enabling Disable OTTO for Logged-in Users currently has no observable effect. OTTO-deployed titles continue to appear on the frontend for logged-in users — the setting does not suppress them as intended, and deployed titles override original defaults regardless of login state. If you've enabled this setting and logged-in users are still seeing OTTO-deployed titles, WP-313 is the cause. A fix is in progress and will be included in an upcoming plugin release. 🛠️ Workarounds While WP-313 Is Being Fixed Until the fix ships, use one of these approaches to view or verify your original (pre-OTTO) titles: - Log out and open a private browsing window — this shows exactly what visitors see, including all OTTO-deployed titles, with no login state affecting the output. - Review titles in the Search Atlas dashboard — the OTTO interface displays both the original and the deployed title for each page, so you can compare them side-by-side without leaving your admin account. - Use a staging site — deploy OTTO titles on a staging copy of your site and review while logged out to QA changes safely before they affect production. 🎯 You now understand what the Disable OTTO for Logged-in Users setting is designed to do and why logged-in users may still see OTTO-deployed titles in the current plugin version. The WP-313 fix is actively in progress — reach out to Search Atlas support if you need a status update on the release timeline.

🔄 Bulk Refresh Your GSC Sites in Search Atlas

Use the Bulk Refresh feature to re-sync all Google Search Console (GSC) site lists across every GSC account connected to your Search Atlas workspace with a single click — then track the refresh status in real time from the Integrations page. 🔍 What Is a Bulk GSC Site Refresh? A bulk GSC site refresh pulls the latest list of GSC properties from every connected GSC account in your Search Atlas workspace simultaneously. Use it when: - You added new properties in GSC and want them available in Search Atlas right away. - You removed or transferred sites in GSC and need your workspace list to reflect the change. - You manage multiple GSC accounts and want all site lists updated at once. The refresh runs asynchronously — processing in the background so you can keep working while Search Atlas syncs your data from the GSC API. 🚀 How to Trigger a Bulk GSC Site Refresh 1. In Search Atlas, go to Settings → Integrations → Google Search Console. 2. Under Connected Accounts, click Refresh Sites. 3. In the confirmation dialog, click Confirm. Search Atlas immediately queues a background refresh across all connected GSC accounts. The status indicator updates to Pending to confirm the refresh has started. 📡 How to Monitor the Bulk Refresh Status After triggering the refresh, track progress directly on the Google Search Console integrations page. 1. Stay on Settings → Integrations → Google Search Console. 2. Locate the status indicator next to the Refresh Sites button. 3. Reload the page at any time to get the latest update. The indicator displays one of the following states: - Pending — the refresh is queued and will begin shortly. - In Progress — Search Atlas is actively fetching site data from the GSC API. - Completed — all GSC sites have been synced. Your updated property list is now available across Search Atlas. - Failed — one or more accounts could not sync. Follow the troubleshooting steps below. Most refreshes complete within a few minutes; larger workspaces with many connected accounts may take longer. When the status shows Completed, your full GSC site list is ready to use in all Search Atlas features. ⚠️ Troubleshooting a Failed Bulk Refresh If the status shows Failed, try these steps in order: 1. Re-authorize the affected GSC account: Go to Settings → Integrations → Google Search Console, disconnect the account, reconnect it, then click Refresh Sites again. 2. Verify GSC permissions: In Google Search Console, confirm your Google account has at least Full or Restricted access to the properties you expect to appear. 3. Retry after a short wait: Temporary GSC API outages can cause failures. Wait a few minutes, then click Refresh Sites to start a new refresh. If the refresh continues to fail after completing all steps above, contact Search Atlas Support and include the affected Google account email address and the approximate time the refresh was triggered. 🎯 You can now trigger a bulk refresh of all your GSC site lists and monitor its progress in real time from the Search Atlas Google Search Console integrations page. For help adding a new GSC account to your workspace, see How to Connect Google Search Console to Search Atlas.

📘 Understanding MCP Cost Before Running Actions

Before executing actions through MCP, you can check whether they will consume Search Atlas quota to avoid unexpected usage. This allows you to plan your actions and ensure you have enough credits before running large or resource-intensive tasks. 🧠 Why This Matters Some MCP actions: - consume quota (when work is produced) - require confirmation (for paid or irreversible actions) Checking cost beforehand helps you: - avoid failed executions - control usage - plan workflows more efficiently ⚙️ Step-by-Step: Check Cost Before Running an Action 📌 Step 1 Open your MCP-connected AI assistant 📌 Step 2 Ask about the action before executing it Examples: - “Will this action consume credits?” - “How much quota will this use?” - “Check cost before running this task” 📌 Step 3 The assistant evaluates the request It determines whether the action: - is read-only - produces work - requires quota or Hyperdrive Credits 📌 Step 4 Review the response You will be informed if the action: - consumes quota - requires approval - is free (read-only) 🔍 How MCP Determines Cost MCP follows the core rule: 👉 Quota is charged when work is produced This means: - Generating content → consumes quota - Running audits → consumes quota - Submitting data → consumes quota - Viewing data → does NOT consume quota 🔐 Approval-Based Actions Some actions require confirmation before execution, especially when they: - consume Hyperdrive Credits - trigger external systems - are irreversible or visible externally In these cases: - The assistant prepares the action - You are prompted to confirm - Execution only proceeds after approval ⚠️ Important Notes - Checking cost is a read-only action - It does NOT consume Search Atlas quota - It only uses AI assistant tokens 🔁 Best Practice Before running large workflows (audits, campaigns, content generation), always check: - your available quota - whether the action will consume credits This helps avoid interruptions and ensures smoother execution. MCP allows you to understand costs before executing actions, giving you full visibility and control over your usage. By checking costs in advance, you can confidently run tasks knowing exactly how they will impact your Search Atlas credits. 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.

🤖 Robots.txt Timestamps and WordPress Timezone Settings in Search Atlas

The Search Atlas plugin displays all timestamps in the Robots.txt editor — including the current-time indicator and backup history entries — using the timezone configured in WordPress Settings → General. If your timestamps changed after a recent plugin update, this is expected; this article helps you verify your timezone setting and resolve any display issues. 🤖 What Changed: Timestamps Now Reflect Your WordPress Timezone Before this update, every timestamp in the Search Atlas Robots.txt editor was hardcoded to UTC, regardless of your WordPress timezone setting. After the update, the plugin reads your WordPress timezone directly from Settings → General and applies it to all timestamp displays in the Robots.txt UI. No additional configuration inside Search Atlas is required. ⚙️ How to Verify or Update Your WordPress Timezone The Search Atlas plugin does not store a timezone of its own — it reads directly from WordPress core. To check or update the setting that controls your Robots.txt timestamps: 1. In your WordPress admin dashboard, go to Settings → General. 2. Locate the Timezone field. 3. Select your city or the correct UTC offset from the dropdown menu. 4. Click Save Changes. The Search Atlas Robots.txt editor will reflect the updated timezone on the next page load. No plugin settings need to be touched separately. 🕐 Where Timestamps Appear in the Robots.txt Editor Two areas inside the Search Atlas Robots.txt editor display timestamps affected by this change: - Current time indicator — shown at the top of the editor so you can confirm which timezone is active at a glance. - Backup history entries — each time you save a version of your robots.txt file, the entry is stamped with the date and time of the save, now in your WordPress timezone. Both timestamp types update automatically once your WordPress timezone is set correctly in Settings → General. 🛠️ Troubleshooting: Timestamps Still Show UTC After Updating If the Robots.txt editor still displays timestamps in UTC after updating Search Atlas, work through these steps in order: 1. Confirm your plugin version is current. In WordPress, go to Plugins → Installed Plugins and apply any pending Search Atlas update. 2. Verify your WordPress timezone is not set to plain UTC. Go to Settings → General → Timezone and select a specific city or a non-UTC offset from the dropdown. 3. Clear your page and server cache. A caching plugin or CDN may be serving a stale version of the page that still shows old UTC timestamps. 4. Hard-refresh the Robots.txt editor page. Press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac to bypass the browser cache. If timestamps remain incorrect after all four steps, contact Search Atlas support and include your current WordPress timezone setting and your Search Atlas plugin version number. 🎯 You now know how the Search Atlas plugin derives Robots.txt timestamps from your WordPress timezone setting and how to confirm everything is configured correctly. For guidance on structuring the content of your robots.txt file, see the Robots.txt Best Practices article in the Search Atlas Knowledge Base.

🔍 GSC Instant Indexing Limits and Dynamic Indexing

🚧 Why Can't I Add a Service Account for GSC Instant Indexing? Google periodically pauses new access to its Instant Indexing API when overall quota demand across all users reaches its limit. This is a restriction enforced on Google's side — it is not caused by your Search Atlas account or any configuration error you have made. When this happens, you will not be able to complete the Service Account setup for GSC Instant Indexing. The connection process will stall or fail during the authorization step. Current status: Google has paused the issuance of new Instant Indexing API access. Existing Service Accounts that were connected before the pause continue to work normally. New accounts cannot be added until Google reopens access. ⚠️ Why Isn't There a Warning in the UI? We understand this is frustrating. When quota is exhausted, customers currently receive no in-product message explaining why the Service Account setup fails — which forces an unnecessary trip to support. Our product team has logged this as a known UX gap and a UI warning is planned for a future release. Once shipped, the platform will display a clear notice when Google's Instant Indexing API quota is unavailable, so you will know immediately without needing to contact support. We appreciate your patience while this improvement is in progress. 💡 What Is Dynamic Indexing and How Does It Help? Dynamic Indexing is Search Atlas's built-in alternative to the Google Instant Indexing API. It submits your URLs for indexing through multiple channels simultaneously, reducing your dependency on any single API quota or service account. Key things to know about Dynamic Indexing: - No Service Account required. It works independently of the GSC Instant Indexing API, so the current Google quota pause does not affect it. - Multi-channel submission. Dynamic Indexing sends your URLs through several pathways at once, increasing the chance that Googlebot crawls and indexes your pages faster. - Built into Search Atlas. You do not need to configure any third-party credentials or external tools to use it. - Recommended workaround. While Google's Instant Indexing API access remains paused for new accounts, Dynamic Indexing is the recommended method to get your pages indexed promptly. ✅ Is It Safe to Deploy All 59 Links at Once? Yes, it is safe to submit all your links through Dynamic Indexing in a single batch. There is no risk of penalizing your site or triggering a spam flag by submitting multiple URLs at the same time. A few things to keep in mind before you deploy: 1. Confirm the URLs are live. Make sure every link resolves correctly and returns a 200 status code. Submitting broken or redirected URLs wastes your submission quota and slows down indexing. 2. Check for noindex tags. If a page carries a noindex directive, Google will crawl it but will not index it regardless of how it was submitted. 3. Prioritize high-value pages first. While bulk submission is supported, consider ordering your list so your most important pages appear at the top. Most indexing pipelines process submissions sequentially. 4. Allow up to 72 hours. Indexing is ultimately controlled by Google. Dynamic Indexing accelerates the process, but it does not guarantee an instant result for every URL. Once you have verified the above, go ahead and submit your full batch. There is no need to split the 59 links across multiple sessions. 🔄 How to Switch to Dynamic Indexing 1. Log in to Search Atlas and open the Authority section from the left navigation menu. 2. Select Indexer (URL Indexer). 3. Paste or upload your list of URLs. 4. Click Index URLs to deploy all links. 5. Monitor submission status in the results panel. Each URL will show its current state as Search Atlas processes the batch. 📋 Quick Reference: Instant Indexing vs. Dynamic Indexing - GSC Instant Indexing API: Requires a Google Service Account — currently unavailable for new connections due to Google quota pause. - Dynamic Indexing: No Service Account needed — available now, supports bulk submission, recommended alternative. 🙋 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 a Loveable AI Site to OTTO

🔍 Overview Loveable is an AI-powered website builder that generates and hosts websites using its own infrastructure. Because Loveable does not offer a native plugin directory or direct CMS access in the traditional sense, connecting it to Search Atlas via OTTO requires the custom installation method — which lets you add OTTO's tracking pixel manually to your site's code. This article walks you through everything you need to know to complete that connection successfully. ✅ Compatibility at a Glance - Supported: Loveable AI sites that allow custom code injection into the <head> section. - Not supported: Loveable sites where you cannot access or modify the underlying HTML. - Requirement: Your Loveable site must allow adding a custom script snippet to the site's global HTML head. ⚙️ Before You Begin Make sure you have the following ready before starting: - An active Search Atlas account with OTTO enabled. - A published website built with Loveable. - Access to your Loveable project's code editor (available inside the Loveable builder interface). 🚀 Step 1 — Add Your Site to OTTO 1. Log in to Search Atlas and go to OTTO SEO → All Sites (SEO Automation). 2. Click Create to add a new site, then enter your Loveable website's URL. 3. Once the site is created, click on it to open the site dashboard. 4. Navigate to Left sidebar → OTTO SEO → Installation Guide. 5. Click Continue installation to open the installation onboarding modal. 📋 Step 2 — Copy Your OTTO Pixel Code 1. Inside the installation onboarding modal, locate the Custom Installation option. 2. Copy the OTTO pixel snippet provided. This is a short JavaScript code block unique to your site. 3. Optionally, use the Use AI Assistant tab or click Copy AI Prompt to generate step-by-step instructions tailored to your platform — this can be especially helpful when working with AI-built sites like Loveable. 💡 Step 3 — Add the Pixel to Your Loveable Site 1. Open your project inside the Loveable builder. 2. Access the code editor or the custom code / HTML settings section of your project. In Loveable, you can typically instruct the AI assistant to inject a script into the <head> section of your site, or use any available "Custom Code" panel. 3. Paste the OTTO pixel snippet so that it loads within the <head> tags on every page of your site. 4. Save and republish your Loveable project to make the changes live. Tip: If you are unsure how to add custom code in Loveable, you can paste the OTTO pixel into Loveable's built-in AI chat and ask it to insert the script into the site's <head>. The Copy AI Prompt feature inside the OTTO installation modal generates a ready-made prompt you can use for exactly this purpose. ✅ Step 4 — Verify the Installation 1. Return to Search Atlas and go to Left sidebar → OTTO SEO → Installation Guide. 2. Click Continue installation and follow the on-screen verification steps. 3. Search Atlas will check whether the pixel is live on your site. This can take a few minutes after you republish in Loveable. 4. Once verified, OTTO will begin scanning your site. You can monitor progress under Left sidebar → OTTO SEO → Crawl Monitoring. ⚠️ Common Issues and Tips - Pixel not detected: Make sure you republished your Loveable project after adding the code. Unpublished changes will not be visible to OTTO. - Code placement: The pixel must be in the <head> section, not the footer or body, for reliable detection. - Site not scanning: Wait 5–10 minutes after a successful verification before expecting crawl data to appear. You can trigger a manual scan from Left sidebar → OTTO SEO → Overview by clicking Scan. - Loveable code access: If your Loveable plan does not include code editing features, you may need to upgrade your Loveable subscription to access custom code injection. 💬 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.

🗺️ Mapping CMS Connector IDs for Atlas Brain SEO Enhancements

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

📘 MCP for SEO Research & Backlinks

Use MCP to analyze backlinks, research competitors, and identify SEO opportunities using the Search Atlas research tools. Through MCP, your AI assistant can access backlink data, keyword insights, and competitor analysis to support your SEO strategy. 🧠 What You Can Do Using MCP for SEO research, you can: - Analyze backlinks and referring domains - Research competitors - Identify keyword opportunities - Discover content gaps - Evaluate domain authority and link profiles ⚙️ Analyze Backlinks 1. Open your MCP-connected AI assistant. 2. Ask for backlink data, for example: "Show me backlinks for my domain" or "Analyze my backlink profile." 3. The assistant retrieves backlink data. 4. Review the results, including referring domains, link sources, and backlink distribution. 🔍 Research Competitors 1. Ask your assistant, for example: "Analyze my competitors" or "Show me competitor backlink profiles." 2. The assistant gathers competitor data. 3. Review insights such as competitor domains, backlink comparisons, and SEO positioning. 🔑 Identify Keyword Opportunities 1. Ask your assistant, for example: "Find keyword opportunities for my site" or "Show keyword gaps between me and competitors." 2. The assistant analyzes keyword data. 3. Review the recommendations. 🧩 Discover Content Gaps 1. Ask your assistant, for example: "Find content gaps in my niche" or "What topics am I missing?" 2. The assistant compares your content against competitors. 3. Review the suggested topics and gaps. ⚠️ Important Notes - Data retrieval and analysis actions may consume Search Atlas quota. - Results depend on available data within the platform. - All actions follow your plan entitlements and permissions. 🔁 How This Fits Together The SEO research workflow through MCP typically follows: analyze your backlink profile, research competitors, identify keyword gaps, then discover content opportunities. All steps are executed through your AI assistant using the same tools available in the Search Atlas platform. MCP allows you to perform deep SEO research through conversation. From backlink analysis to competitor insights and keyword discovery, your AI assistant can execute each step using the same capabilities, permissions, and quotas available in your Search Atlas account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ Connect Google Tag Manager and GA4 to Search Atlas

🔍 What This Article Covers This guide explains the correct process for connecting Google Tag Manager (GTM) and Google Analytics 4 (GA4) to Search Atlas. These are two separate steps that are easy to confuse — GTM container setup happens entirely inside your GTM account, while GA4 property connection is configured inside Search Atlas. This article walks you through both clearly. ⚠️ Common Misconceptions to Avoid There is no Copy button and no tag code retrieval screen inside the Search Atlas Integrations dashboard. Search Atlas does not generate GTM snippets or tag IDs for you. If you were told otherwise, that information is incorrect. Your GTM container code (for example, GTM-PT8CD89P) comes from your own Google Tag Manager account, and your GA4 Measurement ID comes from your own Google Analytics 4 property. 📋 What You Need Before You Start - Access to your Google Tag Manager account at tagmanager.google.com - Access to your Google Analytics 4 property at analytics.google.com - Your GTM container ID (format: GTM-XXXXXXX) - Your GA4 Measurement ID (format: G-XXXXXXXXXX) - Admin or publish permissions in both Google accounts - Admin access to your Search Atlas workspace 🏗️ Step 1 — Set Up GA4 Tag Inside Google Tag Manager This step happens entirely in your GTM account. Search Atlas is not involved here. 1. Log in to tagmanager.google.com and open the container you want to use (for example, GTM-PT8CD89P). 2. In the left sidebar, click Tags, then click New. 3. Click Tag Configuration and choose Google Tag (or Google Analytics: GA4 Configuration if available in your account). 4. Enter your GA4 Measurement ID (G-XXXXXXXXXX) in the Measurement ID field. You can find this in your GA4 property under Admin → Data Streams → select your stream → Measurement ID. 5. Click Triggering and select All Pages so the tag fires on every page of your site. 6. Name the tag something clear, such as GA4 Configuration Tag, then click Save. 7. Click Submit in the top-right corner of GTM to publish your container. Without publishing, the tag will not fire on your site. 🌐 Step 2 — Add Your GTM Container Snippet to Your Website For GTM to work, the container snippet must be installed on your website. If it is already installed, skip this step. 1. In GTM, click Admin in the top navigation, then click Install Google Tag Manager. 2. Copy the two code snippets provided. Paste the first snippet as high as possible in the <head> of every page. Paste the second snippet immediately after the opening <body> tag. 3. If you use a CMS such as WordPress, use a plugin like Site Kit by Google or Insert Headers and Footers to add these snippets without editing code directly. 4. After installation, use the GTM Preview mode (click Preview in your GTM container) to confirm the container is firing correctly on your site before proceeding. 🔗 Step 3 — Connect Your GA4 Property to Search Atlas Once GTM is live on your site and your GA4 tag is publishing data, you can connect your GA4 property to Search Atlas. This is where Search Atlas configuration begins. 1. Log in to Search Atlas and click Site Metrics in the left sidebar. 2. If prompted to connect a property, follow the on-screen OAuth flow to authorise Search Atlas to access your Google Analytics account. 3. Select the GA4 property that corresponds to the site you are tracking. Search Atlas will use this connection to pull traffic and engagement data into your dashboards. 4. Once connected, data will begin populating in Site Metrics within 24–48 hours depending on your GA4 data volume. ✅ How to Verify Everything Is Working - In GTM: Use Preview mode to confirm your GA4 Configuration tag fires on All Pages with no errors. - In GA4: Go to Reports → Realtime and visit your site in a browser. You should see at least one active user appear within seconds. - In Search Atlas: Navigate to Site Metrics in the left sidebar and confirm traffic data is populating. If the property connection was recent, allow up to 48 hours for data to appear. 🛠️ Troubleshooting Common Issues - No data in Search Atlas after 48 hours: Disconnect and reconnect your GA4 property in Site Metrics using the OAuth flow. Confirm you selected the correct GA4 property (not a Universal Analytics property). - GTM container not firing on site: Double-check that both GTM snippets are installed correctly and that you have published the container (Preview mode alone does not send live data). - GA4 Realtime shows no users: Confirm the GA4 Measurement ID in your GTM tag matches the one shown in GA4 under Admin → Data Streams. - Wrong container ID: Your GTM container ID is found in GTM under Admin → Container Settings. It always starts with GTM-. 💬 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.

📘 Google Search Console Integration in Search Atlas

Connect Google Search Console to monitor your website's search performance, including keywords, impressions, and visibility. ⚙️ How to Connect 1. Go to Site Metrics → Site Explorer → GSC/Manage Sites. 2. Locate Google Search Console. 3. Click ➕ Connect GSC Account. 4. Log in to your Google account. 5. Approve permissions. 6. Select your verified property. 🎯 What You Can Do - Track keyword performance. - Monitor impressions and clicks. - Analyze search visibility. - Access SEO insights directly inside Search Atlas. ⚠️ Common Issues 1. Site not appearing — Make sure it's verified in GSC. 2. Wrong account — Use the correct Google account. 3. No data — Wait for sync or verify the property. ❓ FAQ Do I need to verify my site first? Yes, your site must be verified in Google Search Console. 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 Google Search Console and Access Sitemap Data

🌐 What This Article Covers This guide walks you through finishing a Google Search Console (GSC) URL-prefix property connection and then accessing your sitemap data inside Search Atlas. If you have already verified ownership of your property in GSC, follow the steps below to bring that data into the platform. ✅ Step 1: Verify Your URL-Prefix Property in Google Search Console Before Search Atlas can read your sitemap data, your website must be verified in Google Search Console as a URL-prefix property. If you have not done this yet, complete these steps first: 1. Go to Google Search Console (search.google.com/search-console). 2. Click Add property and choose URL prefix as the property type. 3. Enter your full website URL, including https:// (for example, https://www.yoursite.com). 4. Choose a verification method — the HTML tag method is the quickest for most users — and follow the on-screen instructions. 5. Click Verify. Once GSC confirms ownership, your property is ready to connect. Important: Make sure the URL you enter in GSC exactly matches the URL you use in Search Atlas, including whether it has or does not have a trailing slash. 🗺️ Step 2: Submit Your Sitemap in Google Search Console Submitting your sitemap tells GSC which pages to crawl and index. Search Atlas reads this sitemap data once the connection is active. 1. Inside Google Search Console, open your verified URL-prefix property. 2. In the left sidebar, click Sitemaps. 3. Under Add a new sitemap, enter your sitemap path — typically sitemap.xml or sitemap_index.xml. 4. Click Submit. GSC will begin processing the sitemap. This can take a few hours to a few days. If you are unsure of your sitemap URL, try visiting https://www.yoursite.com/sitemap.xml in a browser. Most platforms such as WordPress, Shopify, and Wix generate one automatically. 🔗 Step 3: Connect Your GSC Property to Search Atlas Once your property is verified and your sitemap is submitted in GSC, connect the property to Search Atlas: 1. In the Search Atlas left sidebar, click Site Metrics. 2. Click Analyze or open a saved project for your website. 3. Follow the on-screen prompt to connect Google Search Console. You will be asked to sign in with the Google account that has access to the verified property. 4. Select the correct URL-prefix property from the list of available properties. 5. Confirm the connection. Search Atlas will begin pulling data from GSC. Note: Only properties where your Google account has at least full user permissions in GSC will appear in the selection list. 📊 Step 4: Access Sitemap Data in Search Atlas After the GSC connection is active, your sitemap and page data become available across several areas of Site Metrics: - Site Metrics → Pages — View individual URLs from your sitemap, their index status, and performance metrics pulled from GSC. - Site Metrics → Keywords — See which search queries are driving traffic to your sitemap pages. - Site Metrics → Overview — Get a high-level summary of impressions, clicks, and crawl coverage for the connected property. Navigate to any of these sub-pages using the left sidebar: Site Metrics → [sub-page name]. ⏱️ How Long Does Data Take to Appear? Data availability depends on two factors: - GSC processing time: After you submit a sitemap, Google may take anywhere from a few hours to several days to crawl and index your pages. Search Atlas can only display data that GSC has already processed. - Search Atlas sync time: Once your GSC property is connected, Search Atlas syncs data periodically. Allow up to 24 hours after a new connection for full data to populate. If metrics appear incomplete, check your sitemap status directly in GSC under Sitemaps to confirm Google has successfully processed it. 🛠️ Common Issues and Fixes - Property not appearing in Search Atlas: Confirm your Google account has full user or owner access to the property in GSC. Viewer-level access is not sufficient. - Sitemap shows errors in GSC: Review the error details in GSC under Sitemaps and fix any broken URLs or formatting issues before re-submitting. - URL mismatch: Ensure the URL in your GSC URL-prefix property and the URL entered in Search Atlas are identical — including https://, www, and trailing slashes. - No data after 24 hours: Disconnect and reconnect the GSC property inside Site Metrics, then allow another sync cycle to complete. 💬 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.

🛠️ Reconnect Your WordPress Site to 10Web After Disconnection

If you disconnected your site from the 10Web dashboard and now can't reach WordPress admin or 10Web, you can reconnect by creating a blank WordPress site in 10Web and pointing your domain to it. 10Web detects your existing files and syncs them, so your content and OTTO connection stay intact. ✅ What disconnection actually changed Disconnecting only removed the 10Web dashboard's access to your site. It did not delete your site or your content. - Your site is still live. - The SearchAtlas plugin is still installed, active, and connected to our system. - Your WordPress files are untouched on the server. This means you are reconnecting access, not rebuilding anything. 📞 Contact 10Web support before you reconnect Before you start, message 10Web support so they can protect your existing content during reconnection. What to tell 10Web - You removed the site from the dashboard but did not delete the files. - You want to reconnect without a new WordPress installation. With this context, 10Web can guide the reconnection so there's no risk to your existing WordPress content. 🔁 Reconnect your site in 10Web Follow these steps in order to restore 10Web dashboard access to yourdomain.com. Steps to reconnect 1. Create a blank WordPress site when 10Web prompts you to. 2. Point your domain (yourdomain.com) to that new site. 3. Let 10Web detect and sync — it will recognize your existing WordPress files and pull them in. Once 10Web finishes syncing, your dashboard access is restored and your original content appears as before. 🔌 Confirm your OTTO connection is back Because the SearchAtlas plugin was never disconnected, your OTTO connection resumes automatically once 10Web dashboard access is restored. - No need to reinstall the SearchAtlas plugin. - No need to re-link OTTO manually. - OTTO reports as connected once the site is reachable through 10Web again. After reconnection, verify your OTTO connection status in the plugin dashboard. If OTTO is disabled, your schema markup may not display on the frontend even if it was previously deployed — contact support if you need to re-enable it. You'll know you're done when you can open your site in the 10Web dashboard and OTTO shows an active connection. 🧰 Troubleshooting reconnection issues If reconnection doesn't go as expected, try these steps before reaching out for further help. - If 10Web doesn't detect your files, verify file permissions and database access with 10Web support. - If syncing is stuck, check your Site Audit status in the SearchAtlas dashboard. 🎯 You've learned that disconnection only removed 10Web's dashboard access — your site, content, and SearchAtlas plugin are all intact. Reach out to 10Web support, then create a blank site and point your domain to it to reconnect, and your OTTO connection will resume on its own.

📊 Partner Reporting API: Historical Trend Data for Domain Power, Domain Rating & Domain Authority

The Partner Reporting API now includes a historical trend endpoint that returns time-series data for Domain Power (DP), Domain Rating (DR), and Domain Authority (DA). If you manage a large client portfolio, use this endpoint to track how each metric changes over time for any domain — moving beyond the previous snapshot-only model. 📋 What Changed: From Snapshots to Time-Series Data Previously, the Partner Reporting API exposed only the current (point-in-time) value for Domain Power, Domain Rating, and Domain Authority. The historical trend endpoint stores metric data across time and returns a dated series of values, so you can chart how a domain's authority scores have trended over any period covered by the Search Atlas index. 📊 The Three Metrics Available in the Trend Endpoint The endpoint returns time-series data for three domain-level metrics: - Domain Power (DP) — Search Atlas's proprietary score measuring a domain's overall SEO strength, on a scale of 0–100. - Domain Rating (DR) — A measure of the strength and quality of a domain's backlink profile within the Search Atlas index. - Domain Authority (DA) — A score reflecting a domain's likelihood to rank in organic search results, derived from multiple ranking signals. All three metrics are returned as dated data points, so you can build trend charts and identify metric movement across any queried date range. 🔑 Who Can Access This Endpoint The historical trend endpoint is available to partner accounts on Search Atlas. If you already manage client domains through the partner portal, your existing partner API credentials cover this endpoint — no additional provisioning is required. If you do not yet have partner API access, contact your Search Atlas account manager to enable it for your organization. 🚀 How to Query the Historical Trend Endpoint To retrieve historical trend data for a domain, send an authenticated request to the Partner Reporting API's trend endpoint and specify the domain and the date range you want to query. 1. Authenticate using your partner API credentials. 2. Call the historical trend endpoint, passing the target domain as a parameter. 3. Specify the start and end dates for the time range you want to retrieve. 4. The API returns a time-ordered series of DP, DR, and DA values for that domain. For the full endpoint reference — including the exact URL, required parameters, and response schema — visit the partner API documentation portal or contact your Search Atlas partner representative. 💡 Common Use Cases for Partner Portfolios Partner customers use the historical trend endpoint to: - Generate client-facing reports that show authority score improvement over a campaign period. - Detect unexpected drops in Domain Power or Domain Rating across a portfolio and flag domains for investigation. - Benchmark a client domain's growth against a competitor's historical trend data. - Feed time-series metrics into internal dashboards or business intelligence tools for automated portfolio reporting. 🎯 You now know how to access historical Domain Power, Domain Rating, and Domain Authority trends through the Partner Reporting API — use this data to power client reports and portfolio-level insights. To explore other partner API capabilities or set up automated reporting workflows, contact your Search Atlas partner representative.

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

🔍 Connect Google Search Console Properties to Search Atlas

🗺️ Overview Search Atlas integrates with Google Search Console (GSC) in two separate places: the Integrations panel and individual Projects. Connecting your GSC account in Integrations makes all your properties available to Search Atlas — but each Project must be individually linked to the specific property you want to report on. This is the most common reason customers see nine properties in Integrations yet only one appearing inside a Project's GSC module. 🔗 How the Two Connections Work Understanding the difference between these two connection points will save you time: - Integrations (account-level): This is where you authorise Search Atlas to access your Google account. All GSC properties tied to that Google account become visible here. This is a one-time setup. - Project (property-level): Each Project must be individually mapped to one GSC property. The Project only pulls data from the single property you assign to it — it does not automatically inherit all properties from your Integrations account. ⚙️ Step 1 — Verify Your GSC Account Is Connected in Integrations 1. Go to Site Metrics → Site Explorer → Open Google Search Console (Manage Sites page) and click Connect GSC Account. 2. Confirm that your Google account is connected and that all nine properties are listed and showing a healthy status. 3. If any property is missing here, log in to Google Search Console and confirm that your Google account has access to that property, then return to the Manage Sites page and reconnect your account via Connect GSC Account. 📊 Step 2 — Link a GSC Property to a Specific Project 1. From the left sidebar, go to Home and open the Project you want to configure. 2. Inside the Project, locate the GSC / GA module (sometimes labelled Google Search Console). 3. If the module shows a Connect Google Search Console prompt even though your account is already connected in Integrations, click the prompt — this simply means the property has not yet been assigned to this Project, not that your account is disconnected. 4. A property selector will appear listing all GSC properties available under your connected Google account. Select the exact property that matches this Project's website (e.g. https://example.com/ or sc-domain:example.com). 5. Save the selection. The Project will now pull GSC data exclusively from that property. 🔄 Step 3 — Repeat for Each Project If you manage nine websites and want GSC data inside each Project, you must complete Step 2 for every Project individually. Each Project stores its own property mapping independently. This design ensures that data from different websites is never mixed within a single reporting view. 💡 Common Issues and Fixes - "Connect Google Search Console" still appears after connecting: This is a known display behaviour. Click the prompt anyway — your account credentials are already stored, and clicking will take you straight to the property selector rather than asking you to re-authorise. - A property is missing from the selector inside the Project: The selector only shows properties tied to the Google account connected in Integrations. If a property belongs to a different Google account, go to Integrations, add that second Google account, and then return to the Project selector. - Data is not refreshing after linking: GSC data can take up to 24 hours to populate after a property is first linked. Use the Refresh data button on the Home screen to trigger an immediate sync where available. - Domain property vs URL-prefix property: Google Search Console offers two property types. Make sure the property type shown in the selector matches the one you verified data for inside Google Search Console itself. ✅ Quick Checklist - Google account connected in Integrations ✓ - All expected properties visible in Integrations ✓ - Correct GSC property selected inside each individual Project ✓ - Waited up to 24 hours for initial data sync ✓ 🆘 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.

🤖 Connect Search Atlas MCP and Coworker Slack Integration

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

🔗 Connect Google Integrations for Multiple Clients

🌐 Overview If you manage SEO for multiple clients, Search Atlas lets you connect separate Google Search Console (GSC), Google Analytics 4 (GA4), and Google Business Profile (GBP) accounts to each client workspace. This article explains how the company-selection step works so every client's data stays correctly linked. 🏢 How Multi-Client Google Integrations Work Search Atlas is built around a workspace-per-client model. Each client you manage has its own workspace, and Google integrations are connected at the workspace level — not at a global account level. This means you must select the correct company or property after switching into the relevant client workspace. When you authenticate with Google, you are granting Search Atlas access to all properties available under your Google account. The company or property selector then appears so you can choose exactly which GSC site, GA4 property, or GBP location belongs to the client you are currently working on. 🔍 Connecting Google Search Console and GA4 1. From the left sidebar, navigate to Site Metrics (Site Explorer) (URL: /site-explorer/list). 2. Open or create the project for the client you want to connect. 3. Click Open Google Search Console and, on the GSC Sites List page, click Connect GSC Account (or the equivalent option, Connect GA Account). 4. Sign in with the Google account that has access to the client's properties. 5. After authentication, a property selector dropdown will appear — this is where you choose the specific client site or GA4 property from the list. 6. Select the correct property and click Confirm. 7. Repeat these steps for each client by switching workspaces first. Important: If you do not see the property selector, refresh the page and reconnect. The dropdown only appears after a successful Google authentication handshake. 📍 Connecting Google Business Profile (GBP) 1. From the left sidebar, navigate to Local → GBP Projects (URL: /gbp-galactic/gbp-projects). 2. Open the GBP project for the relevant client, or create a new one. 3. Click Connect Google Business Profile. 4. Authenticate with the Google account that manages the client's GBP location. 5. A location selector will appear listing all business locations available under that Google account. 6. Select the correct business location for this client and click Confirm. Once connected, GBP data will populate across Local → Overview, Local → Reviews, and other sub-pages within that project. 💡 Tips for Managing Many Clients - Always switch workspaces first before connecting or changing a Google integration — this ensures the property is linked to the right client. - If a client's Google account is separate from yours, use the Sign in with a different account option during the Google authentication step. - You can reconnect or change a linked property at any time by returning to the same settings area and clicking Reconnect. - Each workspace stores its own integration credentials independently, so updating one client's connection will never affect another. 🛠️ WordPress Plugin Installation The Search Atlas WordPress plugin allows you to sync on-page SEO data directly from your client's website. Follow these steps to install it: 1. Log in to the WordPress admin dashboard for the client's website. 2. Go to Plugins → Add New → Upload Plugin. 3. Upload the Search Atlas plugin .zip file provided by Search Atlas. 4. Click Install Now, then click Activate. 5. Once activated, go to the plugin settings page and enter your Search Atlas API key. You can find your API key inside your Search Atlas account under your profile settings. 6. Save the settings. The plugin will now sync your site data with your Search Atlas workspace. Note: Make sure the API key you enter belongs to the same Search Atlas workspace as the client project you want to connect. Using a mismatched key is the most common reason the plugin does not sync correctly. ❓ Frequently Asked Questions - I authenticated with Google but no property selector appeared. — Refresh the page and try reconnecting. If the issue persists, make sure the Google account you used actually has access to the client's GSC, GA4, or GBP properties. - Can I connect the same Google property to multiple workspaces? — Yes, the same property can be linked to more than one workspace if needed. - The plugin installed but data is not syncing. — Verify the API key is correct and that the plugin is activated. Also check that your server can make outbound HTTPS requests. 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.

📘 Instagram Pages Integration

Connect your Instagram account to track engagement and analyze content performance from within Search Atlas. ⚙️ How to Connect 1. Go to Settings → Integrations. 2. Locate Instagram Pages. 3. Click ➕ Connect account. 4. Log in via Facebook (Meta). 5. Approve permissions. 6. Select your Instagram account. 🎯 What You Can Do 1. Track engagement metrics. 2. Analyze content performance. 3. Monitor audience interaction. ⚠️ Common Issues 1. Account not showing — Must be linked to a Facebook Page. 2. Login issues — Use the correct Meta account. 3. Permissions denied — Reconnect and approve. ❓ FAQ Do I need a business account? Yes, Instagram must be a Business or Creator account linked to a Facebook Page. 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 OTTO Pixel on Cloudflare and Custom CMS

🧭 Overview The OTTO pixel allows Search Atlas to crawl and optimize your site automatically. If your site is protected by Cloudflare, its bot protection may block Search Atlas bots by default — preventing the pixel from working correctly. This article walks you through how to whitelist Search Atlas bots in Cloudflare and how to install the OTTO pixel on a custom CMS using Google Tag Manager (GTM). ⚠️ Why Cloudflare May Block the OTTO Pixel Cloudflare's bot management and firewall features are designed to block unrecognized automated traffic. Search Atlas crawlers may be blocked before the pixel can fire, which can result in the pixel appearing unverified inside OTTO even after installation. ✅ Step 1 — Whitelist Search Atlas Bots in Cloudflare To allow Search Atlas crawlers through Cloudflare's firewall, you need to create a firewall rule (or WAF custom rule) that bypasses bot protection for Search Atlas user agents and/or IP ranges. 1. Log in to your Cloudflare dashboard and select the domain where OTTO is installed. 2. Locate the firewall or WAF rules section for your plan — the exact menu path may vary depending on your Cloudflare plan version. 3. Create a new custom rule named something like Allow Search Atlas Bots. 4. Configure the rule to match Search Atlas traffic by user agent and/or by any IP addresses that Search Atlas has provided to you, then set the action to allow or bypass bot protection for matching requests. 5. Save and deploy the rule. If your Cloudflare plan includes additional bot protection features, you may also need to review those settings to ensure verified or allowlisted bots are not being challenged. Refer to Cloudflare's official documentation for the exact steps that apply to your plan. 📦 Step 2 — Install the OTTO Pixel via Google Tag Manager If your CMS does not allow direct theme file editing (e.g., some hosted or headless platforms), use Google Tag Manager to deploy the OTTO pixel. 1. Log in to Search Atlas and locate your unique OTTO pixel code snippet within your OTTO settings area. 2. Log in to Google Tag Manager and open the container for your site. 3. Create a new tag using the Custom HTML tag type. 4. Paste the OTTO pixel code snippet into the HTML field. 5. Set the trigger so the pixel fires on every page load (e.g., an All Pages trigger). 6. Name the tag and publish your GTM container to make the pixel live. 🔍 Step 3 — Verify the Pixel Is Working After completing both steps, return to Search Atlas and check whether the OTTO pixel status updates to verified. If the pixel remains unverified, confirm that your Cloudflare allowlist rule is active and that GTM has been published with the correct trigger 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.

🔧 Install OTTO Pixel Manually on WordPress

🧭 Overview The standard way to install OTTO on WordPress is the Search Atlas (MetaSync) plugin: in WordPress open Search Atlas → Settings, paste your Search Atlas API Key, and paste your OTTO Pixel UUID. If that standard installation is not detecting correctly on your WordPress site, you can install the pixel manually using a code snippets plugin or Google Tag Manager (GTM). This article walks you through both fallback methods so OTTO can start tracking your site without delay. 🔑 Before You Begin You will need your unique OTTO pixel code. To find it: 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Open your OTTO session and go to the pixel installation section. 3. Copy the full pixel script provided — keep this tab open while you work in WordPress. 🔌 Method 1: Install via WPCode (Recommended Plugin) WPCode is the most reliable way to inject custom scripts into WordPress without editing theme files directly. 1. Log in to your WordPress admin dashboard. 2. In the left menu, go to Plugins → Add New and search for WPCode – Insert Headers and Footers. 3. Click Install Now, then Activate. 4. In the left menu, go to Code Snippets → + Add Snippet. 5. Select Add Your Custom Code (New Snippet). 6. Give the snippet a name, such as OTTO Pixel. 7. Set the code type to HTML Snippet. 8. Paste your OTTO pixel script into the code editor. 9. Under Insertion, set the location to Site Wide Header so the pixel fires on every page. 10. Toggle the snippet to Active and click Save Snippet. 11. Return to Search Atlas and click Verify Pixel to confirm detection. 🧩 Method 2: Install via Code Snippets Plugin If you prefer the Code Snippets plugin, follow these steps instead. 1. In your WordPress admin, go to Plugins → Add New and search for Code Snippets by Code Snippets Pro. 2. Click Install Now, then Activate. 3. Go to Snippets → Add New in the left menu. 4. Enter a title such as OTTO Pixel. 5. In the code editor, paste your OTTO pixel script. 6. Below the editor, change the Run snippet option to Run snippet everywhere. 7. Click the dropdown arrow next to Save Changes and select Save Changes and Activate. 8. Return to Search Atlas and click Verify Pixel to confirm detection. 📦 Method 3: Install via Google Tag Manager Use this method if your site already uses GTM or if plugin options are not available to you. 1. Log in to your Google Tag Manager account and open the container for your WordPress site. 2. In the left menu, click Tags → New. 3. Click Tag Configuration and select Custom HTML. 4. Paste your OTTO pixel script into the HTML field. 5. Click Triggering and select All Pages so the pixel fires site-wide. 6. Name the tag OTTO Pixel and click Save. 7. Click Submit in the top-right corner of GTM, add a version name, and click Publish. 8. Return to Search Atlas and click Verify Pixel to confirm detection. Note: If GTM is not yet installed on your WordPress site, install the GTM4WP plugin first, add your GTM container ID, and then follow the steps above. ✅ Confirming Successful Installation After completing any of the methods above: - Wait 1–2 minutes, then return to your OTTO session in Search Atlas. - Click Verify Pixel or refresh the pixel status. - A green confirmation message indicates the pixel is detected and tracking correctly. - If the status still shows undetected, clear your site's cache (including any caching plugins such as WP Rocket or W3 Total Cache) and try verifying again. ⚠️ Common Issues and Fixes - Pixel not detected after installation: Clear all site caches and server-side caches, then re-verify. - Script stripped by WordPress: Ensure the code type in WPCode or Code Snippets is set to HTML Snippet, not PHP. - GTM tag not firing: Confirm the container is published and GTM is correctly embedded in your site's <head>. - Pixel fires on some pages only: Check that the trigger is set to All Pages and no page exclusion rules are active. 💬 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. Additional Notes After install, a correctly installed pixel on a new project is normally detected within about 15 minutes, as Search Atlas automatically checks every 15 minutes for projects under 2 hours old. Do not reinstall during this window; multiple installations cause duplicate script conflicts. You can verify the pixel is live before the status updates without waiting.

🔗 Google Search Console Property Types for Search Atlas

🧭 Overview When integrating Google Search Console (GSC) with Search Atlas, you will be asked to select a property. GSC offers two property types: URL-prefix (for example, https://wiise.com/) and domain (for example, wiise.com). Choosing the right type affects how much data Search Atlas can access and display for your site. 📋 Understanding the Two Property Types URL-prefix property covers only the exact URL you enter, including its protocol and subdomain. For example, https://wiise.com/ would include HTTPS pages on the root domain but would not include http://wiise.com/, https://www.wiise.com/, or any subdomains such as https://blog.wiise.com/. This makes URL-prefix properties narrower in scope. Domain property covers all URLs across every protocol, subdomain, and path associated with a domain. Connecting wiise.com as a domain property gives Search Atlas visibility into http://, https://, www., and all subdomains in a single connection. This is the broader and more complete option. ✅ Search Atlas Recommendation Search Atlas recommends connecting a domain property wherever possible. Here is why: - Complete data coverage: A domain property aggregates clicks, impressions, and ranking data across all protocols and subdomains, giving you an accurate picture of your site's full organic performance. - Fewer gaps in reporting: URL-prefix properties can create blind spots if your site serves traffic across both HTTP and HTTPS, or across multiple subdomains. - More reliable rank tracking: Features in Search Atlas such as Rank Tracker and Keyword Magic benefit from having the widest possible data set to surface accurate keyword positions and trends. - Simplified management: One domain property replaces multiple URL-prefix properties you might otherwise need to create to achieve the same coverage. ⚠️ When a URL-Prefix Property May Be Appropriate A URL-prefix property can be the right choice in specific situations: - You only want to track a specific subdomain or subdirectory (for example, a blog at https://blog.wiise.com/ that is managed separately). - You do not have access to your DNS settings, which are required to verify a domain property in GSC. URL-prefix properties can be verified through alternative methods such as an HTML file upload or a meta tag. - Your organisation requires separate reporting for different sections of a site for internal or client billing purposes. 🔄 Implications of Switching Property Types If you currently have a URL-prefix property connected to Search Atlas and want to switch to a domain property, be aware of the following: - Historical data continuity: Search Atlas pulls data from whichever GSC property is connected at the time. Switching to a domain property will give you broader data going forward, but historical reports already generated under the URL-prefix property will reflect that narrower scope. - Re-verification in GSC: You must verify the domain property inside Google Search Console before connecting it to Search Atlas. Domain verification requires adding a DNS TXT record through your domain registrar or DNS provider. - Reconnection required in Search Atlas: After verifying the domain property in GSC, you will need to disconnect the existing URL-prefix property in Search Atlas and connect the new domain property. To do this, go to Left sidebar → Home and follow the GSC integration steps to select the updated property. - No data is lost in GSC: Both property types coexist independently in Google Search Console. Switching in Search Atlas does not delete or alter your existing GSC properties. 🛠️ How to Connect or Switch Your GSC Property 1. Verify your domain property (wiise.com) in Google Search Console by adding the required DNS TXT record. Refer to Google's official GSC documentation for step-by-step verification instructions. 2. Once verified, log in to Search Atlas and navigate to Left sidebar → Home. 3. Open the GSC integration settings and select the domain property (wiise.com) from the list of available properties. 4. Save your selection. Search Atlas will begin pulling data from the domain property immediately. 5. Allow up to 48 hours for data to fully populate across features such as Site Metrics, Rank Tracker, and Keyword Magic. 💡 Quick Reference - Domain property (wiise.com) — recommended for most users; covers all protocols and subdomains. - URL-prefix property (https://wiise.com/) — use only when you need isolated tracking or cannot verify via DNS. - Switching is safe and does not delete GSC data, but requires re-verification and reconnection inside Search Atlas. 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.

🔗 Access Backlink Data via Search Atlas MCP/API

🔍 Overview Many customers building custom client dashboards want to populate sections like Top Referring Domains and Recent Backlinks using the Search Atlas MCP or API. This article explains the current state of backlink data access, what tools are available, and how to work effectively with the data while improvements are in progress. 📊 What Backlink Data Is Currently Available Search Atlas provides backlink and referring domain data through the platform's Authority section. You can access this data manually by navigating to Left sidebar → Authority → Campaigns to review link-building activity, or explore related tools under the Authority menu. The following MCP tools exist for programmatic backlink access: - se_get_backlinks — intended to return backlink-level data for a target domain - se_get_referring_domains — intended to return a list of referring domains pointing to a target domain ⚠️ Known Issue: MCP Backlink Tools Returning No Data There is a known active issue where se_get_backlinks and se_get_referring_domains return no data on all tested domains. Our engineering team is actively investigating this bug. Until the fix is deployed, these two MCP tools are not reliable for populating custom dashboards. This is not a configuration error on your end. If you are calling these tools and receiving empty responses, the issue is on the platform side and is being resolved. 🛠️ Workarounds While the Fix Is in Progress While the MCP backlink tools are under repair, consider the following options to keep your custom dashboards functional: 1. Export data manually from the platform. Navigate to Left sidebar → Authority → Campaigns to review backlink campaign data. Use any available export options to pull data into your reporting workflow. 2. Use the URL Indexer for link visibility. Go to Left sidebar → Authority → Indexer (URL Indexer) to check indexation status of backlink URLs you already know about. 3. Combine with other available API endpoints. If your dashboard includes additional SEO metrics such as keyword rankings or organic traffic, those endpoints may already be functional. Build around the working data points while backlink tools are restored. 4. Monitor the platform for updates. Once the engineering fix is deployed, se_get_backlinks and se_get_referring_domains will return data as expected and you can integrate them directly into your dashboard pipeline. 🚀 What to Expect After the Fix Once the issue is resolved, you will be able to use the MCP tools as follows: - Call se_get_referring_domains with a target domain to retrieve a list of domains linking to it — ideal for populating a Top Referring Domains table in your dashboard. - Call se_get_backlinks with a target domain or URL to retrieve individual backlink records — ideal for a Recent Backlinks feed or table. Both tools are designed to return structured data that can be mapped directly to dashboard components. No additional configuration should be required once the data pipeline is restored. 💡 Tips for Building a Reliable Custom Dashboard - Build your dashboard with graceful empty states for backlink sections so incomplete data does not break the layout for clients. - Add error handling around MCP tool calls so your integration can distinguish between an empty result and a failed request. - Use caching where possible — backlink data does not change minute to minute, so storing the last successful response protects your dashboard during any future API interruptions. 🙋 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Connect WordPress to Search Atlas via OTTO Pixel

🧭 Overview The Search Atlas WordPress plugin uses a unique identifier called the OTTO Pixel UUID to link your WordPress site to your Search Atlas project. This article shows you exactly where to find that UUID and how to complete the connection. 🔍 Where to Find Your OTTO Pixel UUID The OTTO Pixel UUID is located inside the OTTO SEO section of Search Atlas, not in general project settings. Follow these steps: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). This takes you to the OTTO automation dashboard (/seo-automation-v3). 3. Locate the project that corresponds to your WordPress site (for example, causemarketing.ca). If you have not created a project for your site yet, click Create to add it. 4. Open the project by clicking on its name or the associated settings icon. 5. Inside the project view, look for the OTTO Pixel section. Your unique UUID is displayed here as a string of letters and numbers (for example, xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). 6. Click the copy icon next to the UUID to copy it to your clipboard. Important: The OTTO Pixel UUID is project-specific. Make sure you are inside the correct project before copying the UUID. ⚙️ Install and Configure the Search Atlas WordPress Plugin Once you have your UUID, follow these steps to connect your WordPress site: 1. Log in to your WordPress admin dashboard at yourdomain.com/wp-admin. 2. Go to Plugins → Add New → Upload Plugin and upload the Search Atlas plugin .zip file provided by Search Atlas. 3. Click Install Now, then Activate the plugin. 4. In the WordPress left menu, click Search Atlas to open the plugin settings. 5. Paste your OTTO Pixel UUID into the designated field. 6. Click Save to confirm the connection. After saving, return to the OTTO SEO dashboard in Search Atlas. Your site status should update to show an active connection within a few minutes. ✅ Verify the Connection Is Working To confirm that the plugin is connected correctly: - Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar of Search Atlas. - Check that your site appears under the Active tab. The dashboard shows counts such as Active 20 — your site should be included in this list once connected. - If the site still shows as inactive after five minutes, try deactivating and reactivating the plugin in WordPress, then verify the UUID was pasted without extra spaces. 🛠️ Common Issues and Fixes - Cannot find the OTTO SEO section: OTTO SEO is included in all Search Atlas plans. If the left sidebar does not show OTTO SEO, contact support via the chat widget. - No UUID is displayed inside the project: Confirm the project has been fully created and saved. Partially created projects may not yet display the OTTO Pixel UUID. - Site not switching to Active status: Clear your browser cache, then check that the UUID in WordPress matches exactly what is shown in Search Atlas — no extra characters or spaces. - Multiple sites: Each WordPress site requires its own Search Atlas project and its own unique OTTO Pixel UUID. Do not reuse the same UUID across different sites. 💬 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.

🏷️ Install the OTTO Pixel via Google Tag Manager

🔍 What Is the OTTO Pixel? The OTTO pixel is a small JavaScript snippet that allows OTTO SEO to track on-site activity and measure the impact of your optimisations. Installing it via Google Tag Manager (GTM) is the recommended method — no developer access to your site's source code is required. 🗺️ Where to Find Your OTTO Pixel Code 1. Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select the website you want to track from the site selector at the top of the page. 3. Look for the Pixel or Tracking Setup section within the OTTO dashboard. 4. Copy the full pixel snippet displayed there. It will look similar to a short JavaScript tag beginning with <script>. Important: Your pixel code is unique to your account and domain. Never use a snippet copied from another source — always retrieve it directly from your Search Atlas dashboard. ⚙️ How to Add the Pixel in Google Tag Manager 1. Log in to Google Tag Manager and open the container for the website you are tracking. 2. Click Tags in the left menu, then click New. 3. Name the tag something clear, such as OTTO SEO Pixel. 4. Click Tag Configuration and choose Custom HTML as the tag type. 5. Paste the OTTO pixel snippet you copied from Search Atlas into the HTML field. 6. Click Triggering and select All Pages so the pixel fires on every page of your site. 7. Click Save. 8. Click Submit in the top-right corner of GTM and publish your container changes. ✅ How to Verify the Pixel Is Firing Correctly - GTM Preview Mode: Before publishing, use the Preview button in GTM to open the Tag Assistant. Navigate to any page on your site and confirm the OTTO SEO Pixel tag shows as Fired in the summary panel. - Browser DevTools: Open your browser's developer tools (F12), go to the Network tab, and reload the page. Filter by the pixel domain or script name to confirm a successful request is being made. - Search Atlas Dashboard: After publishing, return to the OTTO section under OTTO SEO in Search Atlas. A green status indicator or confirmation message will appear once the pixel is detected on your site. It may take a few minutes for the status to update. ⚠️ Common Issues and Fixes - Pixel not detected after publishing: Confirm you clicked Submit in GTM — saving a tag does not publish it. Changes only go live after a version is submitted. - Pixel fires on some pages but not others: Check that the trigger is set to All Pages, not a specific page or URL pattern. - Wrong pixel code: Make sure you copied the snippet from the correct domain inside Search Atlas. Each connected site has its own unique pixel. - GTM container not installed on the site: The OTTO pixel can only fire if the GTM container snippet itself is already embedded in your website's <head> section. Verify your GTM container is live before troubleshooting the tag. 💬 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 Pixel Setup Across Whitelabel and Search Atlas Dashboards

🗺️ Overview: Two Dashboards, One OTTO Pixel Search Atlas offers two distinct dashboard environments for agencies and their clients: - Search Atlas dashboard — your main platform at app.searchatlas.com, where you manage all SEO projects, automation, and settings. - Whitelabel dashboard — a branded client-facing portal your agency configures separately, typically accessed via a custom domain. Both dashboards can interact with the OTTO pixel, but they behave differently depending on where the pixel is installed and how changes are made. Understanding this distinction prevents configuration errors and lost tracking. 🤖 What Is the OTTO Pixel? The OTTO pixel is a lightweight JavaScript snippet you place on a client's website to allow OTTO, the OTTO SEO automation engine, to read and act on that site's data. It enables on-page optimizations, crawl assistance, and automation tasks tied to that domain. The pixel is domain-specific and project-specific. Each website you connect to OTTO gets its own pixel tied to that project. 🏗️ How the Pixel Behaves Across Both Dashboards The OTTO pixel is generated and managed from the Search Atlas dashboard, regardless of whether your clients access their reports through the whitelabel dashboard. Here is how it works across both environments: - Pixel generation — always happens inside the Search Atlas dashboard under the individual project settings via Home → OTTO SEO (left sidebar), then opening SEO Automation inside it. - Whitelabel dashboard — displays project data and reports to your clients but does not independently generate or store its own pixel. It reflects the state of the underlying Search Atlas project. - Pixel installation — the snippet must be placed in the <head> of the client's website, regardless of which dashboard your client uses to view their data. ⚠️ What Happens When the Pixel Is Removed Removing the OTTO pixel from a website — whether you remove it from the site's code directly or disconnect the project inside the Search Atlas dashboard — has the following effects: 1. OTTO automation pauses — active tasks tied to that domain stop executing until the pixel is restored and reconnected. 2. Whitelabel dashboard data freezes — your client's whitelabel view will stop receiving updated automation activity for that site. Historical data remains visible, but no new OTTO actions are logged. 3. The project itself is not deleted — your project settings, previous recommendations, and history are retained in the Search Atlas dashboard. Only the live connection is broken. 🔄 How to Reconnect the OTTO Pixel If the pixel has been removed from the website or the connection was lost, follow these steps to restore it: 1. Log in to your Search Atlas dashboard at app.searchatlas.com. 2. Navigate to Home, then select OTTO SEO from the left sidebar and open SEO Automation inside it, or go directly to /seo-automation-v3. 3. Open the project for the affected website. 4. Locate the OTTO pixel snippet in the project settings panel. Copy the full snippet. 5. Paste the snippet into the <head> section of the client's website. If you use a tag manager, add it as a custom HTML tag that fires on all pages. 6. Return to the OTTO SEO page and verify the pixel status shows as Connected. This confirmation may take a few minutes after the snippet is live on the site. Once the pixel is confirmed as connected, OTTO automation resumes and the whitelabel dashboard will reflect live activity again. 🏢 Agency Workflow: Managing Pixels Across Multiple Clients Agencies managing multiple clients across both dashboards should keep the following in mind: - Each client website requires its own unique pixel. Do not reuse a pixel from one project on a different domain. - Pixel management always happens in the Search Atlas dashboard. Your clients cannot generate or reset pixels from the whitelabel dashboard. - If a client's whitelabel dashboard shows stale or missing OTTO data, check the pixel connection status in the Search Atlas dashboard first before investigating other causes. - If you rebuild or relaunch a client's website, the pixel snippet must be reinstalled manually on the new site. Migrations do not carry the pixel automatically. 🚫 Common Misdiagnosis to Avoid If you are experiencing OTTO pixel issues, it is important to identify the correct source. A disconnected or missing OTTO pixel is not related to Website Studio, which is a separate Search Atlas tool for building web pages. If you do not use Website Studio, any troubleshooting steps referencing it do not apply to your situation. Always start your diagnosis by checking the pixel connection status in the OTTO SEO section of the Search Atlas dashboard. 💬 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.

⚡ Understanding MCP Tool Availability in Claude Code

Overview If you notice fewer slash commands available inside Claude Code than you expected, you are not alone. This article explains why discrepancies in available MCP tools occur and what you can do if certain commands are not appearing for your account. Why You See Fewer Slash Commands Than Expected The slash commands visible inside Claude Code reflect the currently released subset of MCP (Model Context Protocol) tools for Search Atlas. The gap between what you may have seen previewed and what is live comes down to a few factors: - Phased rollout: Search Atlas releases MCP tools in stages. Not all tools have completed internal review and quality assurance at any given time. - Role and account access: Some tools are gated by account type, plan tier, or onboarding status. If your account has not completed a specific setup step, certain commands may not appear. What to Do If a Command Is Unavailable If a specific slash command is not available in your Claude Code session, here is what to check: 1. Confirm your Search Atlas account is fully set up and that onboarding steps have been completed. 2. Verify that your account plan or role includes access to the feature associated with that command. 3. If you have confirmed the above and the command is still missing, contact the Search Atlas support team for clarification on whether that tool has been released for your account type. How MCP Tool Integration Works in Search Atlas Search Atlas uses the Model Context Protocol (MCP) to expose platform capabilities as tools that AI agents like Claude Code can call directly. The tools that appear as slash commands in your session depend on which MCP tools have been released and which your account is authorized to access. If you need help confirming your current tool access or understanding which commands should be available for your account, contact the Search Atlas support team for assistance.

📘 LinkedIn Integration

Connect your LinkedIn account to publish content and monitor engagement from your dashboard. ⚙️ How to Connect 1. Go to Settings → Integrations. 2. Locate LinkedIn Account. 3. Click ➕ Connect account. 4. Log in to LinkedIn. 5. Approve permissions. 🎯 What You Can Do - Publish content. - Track engagement. - Monitor performance. ⚠️ Common Issues - Login issues — Ensure correct account. - Permissions denied — Approve access. - No account connected — Retry connection. ❓ FAQ Can I connect company pages? Yes. If you administer a LinkedIn Company Page, you can connect it in addition to your personal profile and choose it as a posting destination alongside or instead of your profile. 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.

🔄 Update Client Domain With OTTO Integration

🗺️ Overview When a client migrates to a new domain, you need to update their project in Search Atlas and reconnect OTTO SEO to the new domain. This article walks you through the full process so rankings, automations, and optimizations continue without disruption. ⚠️ Before You Begin Keep these points in mind before making any changes: - OTTO is domain-specific. Activations, tasks, and configurations are tied to the domain you originally connected. The domain of an existing OTTO project cannot be changed in place — to move OTTO to a different domain (including www vs non-www), you must create a new OTTO project for the new domain and install its pixel. - Save your OTTO settings first. Note down any active task categories, priorities, or custom configurations so you can reapply them after reconnecting. - Ensure the new domain is live. OTTO needs to crawl the new domain successfully, so confirm it is publicly accessible before starting. 🛠️ Step 1 — Update the Domain in Site Explorer 1. In the left sidebar, click Site Metrics (Site Explorer). 2. Locate the client's project in the list and click the three-dot menu (⋮) next to it. 3. Select Edit Project or Settings. 4. Replace the old domain with the client's new domain in the domain field. 5. Save your changes. Once saved, Search Atlas will associate all future data collection — including rank tracking and site metrics — with the new domain. 🔍 Step 2 — Verify Rank Tracker and Keyword Tools After updating the domain, confirm that your keyword tools are pointing to the correct destination: - Navigate to Keywords → Rank Tracker and confirm the tracked keywords now show the new domain in the ranking data. - Check Keywords → Keyword Magic and Keywords → Keyword Gap to ensure competitor and keyword analysis reflects the updated domain. - If any tool still references the old domain, re-enter the new domain in that tool's settings before proceeding. 🤖 Step 3 — Create a New OTTO Project for the New Domain 1. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 2. Because the domain of an existing OTTO project cannot be changed, create a new OTTO project for the new domain. 3. Install the new project's pixel on the new domain and complete the domain verification step. 4. Re-enter your WordPress or CMS credentials if prompted. ⚙️ Step 4 — Reapply Your OTTO Configuration After reconnecting, OTTO will treat the new domain as a fresh setup. Reapply any settings you noted earlier: - Re-enable your preferred task categories (e.g., title tags, meta descriptions, schema markup). - Review the task queue and approve or dismiss any newly generated recommendations. - Set your deployment preferences — automatic or manual — as needed for the client. OTTO will begin crawling the new domain and generating optimizations based on its current content and structure. ✅ Step 5 — Confirm Everything Is Working Run a quick check to make sure all tools are aligned with the new domain: - Site Explorer: Confirm the domain shown in the project list matches the client's new domain. - Rank Tracker: Verify keyword positions are being tracked for the new domain. - OTTO SEO V3 / OTTO: Confirm OTTO status shows as Connected and tasks are being generated for the new domain. 💡 Tips and Common Issues - OTTO still showing old domain tasks? Remember that an existing OTTO project's domain cannot be changed in place — make sure you have created a new OTTO project for the new domain and installed its pixel as described in Step 3. - Rank data not updating? Allow 24–48 hours for fresh crawl data and ranking updates to populate after a domain change. - Keyword Gap or Keyword Magic pulling old data? Re-run an analysis using the new domain URL to refresh results. - Domain verification failing? Confirm the new domain is publicly accessible and that your CMS credentials are correct before retrying. 💬 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.

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

🔑 Generate a Google App Password for SMTP/IMAP

📋 Overview Google App Passwords let you authorize third-party tools like OTTO PPC to send and receive email on your behalf without sharing your main Google account password. You must complete every step below exactly as described — skipping any step is the most common reason setup fails. Before you start: Google App Passwords are only available if your Google account has 2-Step Verification (2FA) turned on. If 2FA is not yet enabled, follow the steps in the Enable 2-Step Verification section first. ✅ Step 1 — Enable 2-Step Verification (if not already active) 1. Go to myaccount.google.com and sign in to the Google account you want to use for your campaign. 2. Click Security in the left-hand navigation panel. 3. Under the How you sign in to Google section, click 2-Step Verification. 4. Click Get started and follow the on-screen prompts to complete 2FA enrollment. 5. Once finished, you will see a green confirmation that 2-Step Verification is On. Return to the Security page to continue. 🔐 Step 2 — Open the App Passwords Page 1. While still on the Security page of your Google Account (myaccount.google.com/security), scroll down to the How you sign in to Google section. 2. Click 2-Step Verification to open that section. 3. Scroll to the very bottom of the 2-Step Verification page until you see the App passwords option. 4. Click App passwords. You may be prompted to re-enter your Google account password — do so to continue. Note: If you do not see App passwords, your account may be managed by a Google Workspace administrator who has disabled this feature. Contact your IT or Google Workspace admin to enable it. ⚙️ Step 3 — Create the App Password 1. On the App passwords page, enter a descriptive name in the text field to identify this password (for example: OTTO PPC SMTP). 2. Click the Create button to generate your app password. 📋 Step 4 — Copy the Generated Password 1. A dialog will appear on screen displaying a 16-character password made up of four groups of four letters (for example: abcd efgh ijkl mnop). 2. Copy the full 16-character password immediately. Use the copy button if shown, or highlight all characters manually and copy them. 3. Store this password somewhere safe — Google will not show it to you again after you close the dialog. 🔗 Step 5 — Enter the App Password in OTTO PPC 1. Return to the OTTO PPC email setup screen where you are configuring your SMTP/IMAP connection. 2. When prompted for your Gmail password, paste the 16-character app password instead of your regular Google account password. 3. Complete any remaining fields in the setup screen and save your 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.

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

📧 Connect Gmail to Authority Building Outreach

📋 Before You Begin Connecting Gmail to Search Atlas requires three things to be in place: 2-Step Verification enabled on your Google account, IMAP access turned on inside Gmail settings, and a Google App Password generated for this integration. Browser troubleshooting such as hard refresh or incognito mode will not resolve connection errors — the fix lies entirely within Gmail and Search Atlas settings. 🔧 Step 1: Enable IMAP in Gmail IMAP must be active in Gmail before Search Atlas can communicate with your inbox. 1. Open Gmail and click the gear icon in the top-right corner, then select See all settings. 2. Go to the Forwarding and POP/IMAP tab. 3. Under IMAP Access, select Enable IMAP. 4. Under Auto-Expunge, confirm that Auto-Expunge on is selected. 5. Click Save Changes. 🔑 Step 2: Generate a Google App Password An App Password is a 16-character code that lets Search Atlas access your Gmail securely without using your main Google password. 2-Step Verification must already be enabled on your account before this option appears. 1. Go to myaccount.google.com and select Security from the left-hand menu. 2. Under How you sign in to Google, click 2-Step Verification. 3. Scroll to the bottom and click App passwords. 4. Enter a name such as Search Atlas and click Create. 5. Copy the 16-character password shown on screen. Do not close this window until you have saved it — Google will not display this code again. Google Workspace users: If you do not see the App passwords option, your account is managed by an administrator. Contact your admin to enable App Passwords or generate one at the domain level. 📬 Step 3: Configure SMTP/IMAP in Search Atlas With IMAP enabled and your App Password ready, link your Gmail account inside the platform. 1. In Search Atlas, go to Authority Building in the left-hand navigation. 2. Open Campaigns and click Manage connected emails. 3. Click Add email account or the + icon. 4. Select Configure SMTP/IMAP as the connection method. 5. Fill in the connection details as follows: - Email address: your full Gmail address (e.g. name@gmail.com) - Password: paste the 16-character App Password — not your regular Gmail password - IMAP Host: imap.gmail.com | Port: 993 | Encryption: SSL/TLS - SMTP Host: smtp.gmail.com | Port: 465 | Encryption: SSL/TLS Click Save or Test connection. A successful test confirms your Gmail is connected and ready for outreach. ⚠️ Common Errors and How to Fix Them - Authentication failed / Invalid credentials: Confirm you entered the App Password, not your regular Gmail password. If unsure, delete the existing App Password in Google and generate a new one. - IMAP not enabled: Return to Gmail settings and verify IMAP is toggled on and that changes were saved. - Auto-Expunge warning: If Search Atlas reports a mailbox configuration issue, revisit Step 1 and ensure Auto-Expunge is set to on. - Connection timed out: Double-check the host addresses and port numbers listed above for typos. 💬 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.

🤖 Automating SEO & Blog Work with GHL Integration

🗺️ Overview Search Atlas gives agencies powerful tools to automate the heavy lifting of SEO, blog content, GEO (Generative Engine Optimization), and AEO (Answer Engine Optimization) — but true automation still requires some ongoing human oversight. This article explains what you can automate, what still needs your attention, how GHL (GoHighLevel) integration works, and what to expect around setup time, client capacity, and pricing. ⚙️ What You Can Automate in Search Atlas Search Atlas is built with agency workflows in mind. Here is what you can put on autopilot: - Blog content creation: Use the Content Builder to generate SEO-optimized blog posts at scale. You can schedule and publish content directly to connected WordPress sites without manual intervention for each post. - OTTO SEO automation: OTTO is Search Atlas's OTTO SEO agent. Once activated on a site, OTTO automatically identifies technical SEO issues, deploys on-page fixes, builds internal links, and handles schema markup — all without you needing to log in and action each task individually. - Rank tracking and reporting: Keyword rank tracking runs automatically in the background. You can set up white-label reports to be delivered to clients on a schedule via Left sidebar → Keywords → Rank Tracker. - GEO and AEO content: Search Atlas includes tools for optimizing content to appear in AI-generated answers and featured snippets. These optimizations can be applied in bulk across client sites. 💡 What "Not Set-and-Forget" Actually Means While Search Atlas automates the execution of many tasks, it is not a fully hands-off system. Here is what ongoing involvement looks like in practice: - Strategy and direction: OTTO and the content tools follow the SEO strategy you define. You still need to review target keywords, set content topics, and approve strategic pivots when search trends shift. - Content quality review: AI-generated blog posts should be reviewed before publishing — especially for tone, brand voice, and factual accuracy specific to each client's industry. - OTTO approvals: OTTO surfaces recommended actions and in some configurations will ask for approval before deploying significant changes. You should check in periodically to review and approve queued tasks. - Performance monitoring: Automated rank tracking gives you the data, but interpreting results and adjusting strategy based on that data still requires human judgment. - Client communication: Reporting is automated, but client conversations about strategy, results, and next steps remain your responsibility. Think of Search Atlas as a highly capable team member who executes well — you are still the account lead setting goals and reviewing outcomes. 🔗 GoHighLevel (GHL) Integration Search Atlas integrates with GoHighLevel, allowing agencies to embed Search Atlas capabilities within their GHL environment. Here is what you need to know: - White-label compatibility: Search Atlas branding is hidden within the GHL integration, so your clients see your agency's brand throughout the experience. - Local SEO restrictions: Within GHL, users can only add Local SEO data from search results — not from free-form input. This ensures data accuracy for Google Business Profile (GBP) features. - GBP Posts: Google Business Profile post management is available through the GHL integration. Links within GBP posts will direct to your configured destination, not the Search Atlas website. - OTTO SEO in GHL: OTTO SEO is accessible to GHL clients. If you encounter any pixel or tracking issues inside GHL, these are known and have been resolved — if you still see problems, contact support via the chat widget. - Plan setup for GHL clients: You will need to assign and configure plans for GHL clients separately. Make sure you have set the correct plan tier for each client before granting them access. 📝 Blog Creation at Scale For agencies managing multiple clients, Search Atlas supports bulk blog creation through the Content Builder. Here is how the workflow typically looks: 1. Connect your client's WordPress site to Search Atlas. 2. Define target keywords and content briefs using the Keyword Magic tool (Left sidebar → Keywords → Keyword Magic). 3. Use the Content Builder to generate optimized drafts in bulk. 4. Review and approve drafts, then schedule publishing directly to the connected site. 5. OTTO monitors published content and applies on-page optimizations automatically over time. 👥 Client Capacity and Pricing The number of client sites you can manage depends on your Search Atlas subscription tier. Key points to be aware of: - Site and user limits: Each plan includes a set number of connected sites and user seats. Review your current plan quotas from the top header bar → Quotas. - OTTO activations: OTTO SEO is activated per site. The number of sites where OTTO can be active simultaneously is tied to your plan. - Scaling up: If you need to add more client sites or increase capacity, you can upgrade your plan or add seats directly from your account settings. - GHL client plans: GHL clients require their own plan configuration. Pricing for GHL sub-accounts should be reviewed with the support team to ensure correct setup. 🕐 What to Expect for Setup Time Setup time varies depending on the number of clients and the complexity of your configuration. As a general guide: - Single site with OTTO: Initial connection and OTTO activation typically takes 30–60 minutes, including site audit completion. - GHL integration setup: Connecting Search Atlas to your GHL account and configuring white-label settings can take 1–3 hours depending on your GHL setup. - Bulk blog workflow: Setting up keyword research, content briefs, and the first content batch for a client usually takes 2–4 hours upfront. Subsequent batches are faster once templates and workflows are established. - Full agency onboarding (multiple clients): Plan for 1–2 days of dedicated setup time to connect all sites, activate OTTO, configure GHL, and establish your reporting cadence. 🆘 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.

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

📊 Does Search Atlas Integrate With Meta Ads

🔍 Overview Search Atlas is primarily an SEO and Google Ads automation platform. It does not act as a full Meta Ads Manager replacement, but it does offer a Meta Ads page (Which ad platform do you want to see first?) that lets you view and monitor your Meta Ads performance data directly inside Search Atlas. Understanding this distinction will help you set the right expectations and get the most out of the integration. 📋 What Search Atlas Can Do With Meta Ads Through the Meta Ads page, Search Atlas allows you to: - View your Meta Ads campaign performance data in one centralised dashboard - Monitor key metrics such as impressions, clicks, spend, and conversions - Review campaign-level and ad-set-level performance alongside your other marketing data - Use performance insights to inform your broader content and SEO strategy 🚫 What Search Atlas Cannot Do With Meta Ads Search Atlas is not a Meta Ads creation or management tool. The following actions must still be completed directly inside Meta Ads Manager: - Creating new Meta Ads campaigns, ad sets, or individual ads - Editing or pausing existing Meta Ads campaigns - Managing Meta audience targeting, budgets, or bidding strategies - Installing or configuring the Meta Pixel on your website - Running A/B tests or creative experiments For all of the above, you will need to log in to Meta Ads Manager directly at business.facebook.com. 🗺️ How to Access Meta Ads in Search Atlas Follow these steps to access your Meta Ads data inside Search Atlas: 1. Log in to your Search Atlas account. 2. In the left sidebar, click Ads to expand the section. 3. Click Meta Ads from the Ads submenu (Which ad platform do you want to see first?). 4. If your Meta Ads account is already connected, your campaign data will load automatically. If the screen is blank or shows no data, follow the troubleshooting steps below. ⚠️ Fixing a Blank Screen or 'No Data' in Meta Ads A blank screen or a no data message on the Meta Ads page is usually caused by one of the following reasons: - Meta account not connected: Your Meta Business account has not yet been linked to Search Atlas. You will need to complete the account connection flow before data can appear. - No active Meta Ads campaigns: If your Meta Ads account has no active or recent campaigns, there is no data to display. Create and run at least one campaign in Meta Ads Manager first. - Pixel not installed or firing incorrectly: If conversion tracking data is missing, verify that your Meta Pixel is installed correctly on your website via Meta Events Manager. - Data sync delay: Meta Ads data can take up to 24 hours to sync after a new connection or recent campaign activity. Try clicking Refresh data and check back later. - Insufficient account permissions: The Meta account used to connect must have Admin or Advertiser access to the relevant Meta Business account. Ask your Meta Business account admin to verify your role. ✅ Recommended Workflow for Meta Ads Users To get the best results, we recommend the following workflow: 1. Use Meta Ads Manager to create, manage, and optimise your ad campaigns, audiences, and budgets. 2. Connect your Meta Ads account to Search Atlas via Ads → Meta Ads to centralise performance reporting. 3. Use Search Atlas Smart Ads tools — including Campaign Hub, Campaign Performance, and Reports — for your Google Ads automation and to compare paid channel performance. 4. Leverage Search Atlas SEO and content tools to build organic traffic strategies that complement your paid Meta Ads efforts. 💡 Using Smart Ads for Google Ads Automation If you are looking for a platform that can create, optimise, and manage paid ad campaigns end-to-end, Search Atlas's Smart Ads suite is purpose-built for Google Ads. From the left sidebar, navigate to Smart Ads → Campaign Hub to create new campaigns, optimise existing ones, manage negative keywords, run audits, and generate reports — all without leaving Search Atlas. 🙋 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.

🔗 Migrating Site Explorer Projects from a GHL Sub-Account to a Native Search Atlas Account

When you move from a GoHighLevel (GHL) sub-account to a native Search Atlas account, your existing Site Explorer projects cannot be transferred. Each project must be recreated from scratch in the new account, and historical crawl and audit data stored in the GHL-managed account does not carry over. ⚙️ Why Site Explorer Projects Cannot Be Transferred Site Explorer projects are bound to the account in which they were created. GHL sub-accounts and native Search Atlas accounts use separate account structures with no built-in migration path between them. Project settings, crawl schedules, historical audit snapshots, and trend data all remain in the source GHL account and cannot be moved to a native account. 📊 What Data Is Lost and What You Can Save Before your GHL sub-account is closed — for example, if you are leaving an agency relationship or switching to a direct Search Atlas subscription — understand exactly what does and does not migrate. Data that does not transfer to the native account: - Past crawl snapshots and audit history - Page-level issue trends and audit score history over time - Scheduled crawl configurations and any custom crawl rules Data you can preserve manually before migrating: - Export each audit report as a CSV directly from the GHL sub-account (PDF export availability may vary by account type — contact support to confirm). - Record your crawl settings — frequency, scope, and device type — so you can replicate them quickly in the new account. 🚀 How to Recreate Your Site Explorer Projects in a Native Account Complete these steps for each domain that was active in your GHL sub-account. 1. Log in to your native Search Atlas account. 2. In the left sidebar, go to Site Metrics → Site Explorer (Site Explorer) and click New Project. 3. Enter the domain you want to audit. 4. Configure your crawl settings: crawl frequency (daily, weekly, or monthly), crawl scope (number of pages or sections to include), and device type (desktop or mobile). If you are setting up the project in a GHL context, note that the Worldwide location option is not available — select a specific country or region instead. 5. Click Recrawl Site to run the first audit under the new account. 6. Repeat for every additional domain previously managed under the GHL sub-account, adding them sequentially rather than all at once. The first crawl typically completes in 5–30 minutes depending on site size. Once it finishes, your native account has a clean baseline from which you can track all future improvements. 🚧 How to Fix a Quota Exhausted Error If you receive a Quota Exhausted error when adding projects — even when slots appear available — contact Search Atlas support. An agent can review and reset your on-page audit quota. Add projects sequentially and allow each crawl to complete before starting the next. ⚠️ Export Everything Before Your GHL Access Ends Your GHL sub-account remains active until your agency formally closes or transfers it. Export all audit reports and note all crawl configurations before that access ends — audit history cannot be retrieved after the account is closed or revoked. Tip: Before your agency closes or transfers your GHL sub-account, request at least 30 days of continued read access so you can complete all exports. Contact Search Atlas support if you need guidance on timing. 💡 What Starting with a Fresh Baseline Means for Reporting Your native account begins with no historical trend data from the GHL period. This is expected. The first crawl immediately surfaces all current site issues, so you can start measuring and tracking improvements from day one. If you need a documented record of past performance, your exported CSV (or PDF, if available) reports from the GHL account serve as your historical reference. 🎯 With your projects recreated in your native Search Atlas account, you have full ownership of your crawl data and audit history going forward. If you have questions about your account transition or need help configuring Site Explorer for the first time, contact Search Atlas support or reach out to your account manager.

🔌 Add Meta Tags to WordPress Without Third-Party Plugins

🧭 Overview Search Atlas lets you generate and apply meta titles and meta descriptions directly to your WordPress posts and pages — no need for a third-party SEO plugin like Yoast or Rank Math. This guide walks you through the full process from generating your meta tags to pushing them live on your site. ✅ Before You Start Make sure the following are in place before you begin: - Your WordPress site is connected to Search Atlas. (If not, navigate to your integrations settings and follow the WordPress connection steps.) - You have at least Editor-level access to the WordPress site you want to update. - You have a published or draft post or page ready to optimise. 📝 Step 1: Generate Your Meta Tags Search Atlas includes a built-in Meta Generator tool that creates SEO-optimised meta titles and descriptions for your content. 1. In the left sidebar, click Content, then select Meta Generator. 2. Enter the target URL or paste the content you want to optimise. 3. Add your primary keyword in the keyword field. 4. Click Generate. Search Atlas will produce one or more meta title and description suggestions. 5. Review the suggestions. A strong meta title is typically 50–60 characters, and a meta description should be 120–158 characters. 6. Click Copy next to the version you want to use, or edit it inline before proceeding. 🔗 Step 2: Apply Meta Tags to Your WordPress Post Once you have your meta title and description ready, you can push them directly to your WordPress post through the On-Page Audit tool. 1. In the left sidebar, click Content, then select On-Page Audit. 2. Enter the URL of the WordPress post or page you want to update and run the audit. 3. In the audit results, locate the Meta Title and Meta Description fields. 4. Paste or type your optimised meta title and description into the respective fields. 5. Click Push to WordPress (or the equivalent save/apply button shown for your connected site). 6. Search Atlas will write the meta tags directly to that post via the Search Atlas WordPress plugin, which must be installed and connected to your site. 🔍 Step 3: Verify the Tags Are Live After pushing your meta tags, confirm they are applied correctly: - Visit the post URL in a new browser tab and inspect the page source (Ctrl+U on Windows, Cmd+U on Mac). Search for <title> and <meta name="description" to confirm the values match what you entered. - Alternatively, re-run the On-Page Audit on the same URL. The audit will reflect the updated meta tags if they have been applied successfully. - You can also use Google's Rich Results Test or any meta tag checker tool to validate the output. 💡 Tips for Better Meta Tags - Include your primary keyword near the beginning of both the meta title and description. - Make descriptions action-oriented — tell users what they will find or gain by clicking. - Avoid duplicate meta tags across your site. Each post should have a unique title and description. - Use the Content Planner (Left sidebar → Content → Content Planner) to plan and batch-optimise meta tags across multiple pages at once. ⚠️ Troubleshooting Common Issues If your meta tags are not saving or appearing incorrectly, check the following: - WordPress connection is active: Go to your integrations settings and confirm your WordPress site shows a connected status. Re-authenticate if needed. - Conflicting plugin: If you have Yoast, Rank Math, or another SEO plugin installed, its meta fields may override the tags set by Search Atlas. Disable or uncheck meta tag management in that plugin to avoid conflicts. - Caching: Your hosting cache or a caching plugin may serve an older version of the page. Clear your site cache after pushing changes and then re-verify. - User permissions: Confirm your connected WordPress account has sufficient permissions to edit post meta fields. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 MCP Server Queries: Credits, Costs, and Quotas

🧠 Overview The Search Atlas MCP (Model Context Protocol) server lets you run keyword and domain queries programmatically — but it does not use a separate credit pool. Every MCP query draws from the exact same credit allocations you see inside the Search Atlas dashboard. Understanding which quota applies to which query type helps you plan usage and avoid unexpected shortfalls. 💳 Which Credits Do MCP Keyword Queries Use? When you run a keyword ranking query for a domain through the MCP server (for example, a query that returns 74 ranked keywords), the credits consumed come from your Keyword Lookup allocation — sometimes also referred to as the Site Explorer detail quota. This is the same pool that is drawn from when you explore keyword data inside the dashboard via Left sidebar → Keywords (Keyword Research). This is a common point of confusion. The quota to check is not the Keyword Rank Tracker allocation. The Keyword Rank Tracker quota covers tracked keywords you actively monitor over time (visible at Left sidebar → Keywords → Rank Tracker (Keyword Rank Tracker)). MCP domain keyword queries are lookups, not tracked keywords, so they pull from the Keyword Lookup pool instead. To summarise which quota applies to which action: - Keyword Lookup / Site Explorer detail quota: MCP keyword ranking queries for a domain, on-demand keyword research lookups in the dashboard. - Keyword Rank Tracker quota: Keywords you add to active rank tracking campaigns inside Rank Tracker. - Keyword Magic quota: Bulk keyword discovery queries run via Left sidebar → Keywords → Keyword Magic or the equivalent MCP call. 📊 How Many Credits Does One Query Consume? Credit consumption is based on the number of keyword rows returned, not on the number of API calls made. Each keyword row returned by a query counts as one Keyword Lookup credit. Using the example of a domain query that returns 74 keywords: - Credits consumed: 74 Keyword Lookup credits (one per keyword row returned). - If a second query for the same or a different domain returns 200 keywords, that query consumes 200 credits. - A query that returns zero results consumes zero credits. There is no flat per-call fee. You are only charged for the data rows actually returned to you. 🔄 When Do Keyword Lookup Credits Reset? Your Keyword Lookup allocation is an annual allocation, not a monthly one. The standard plan includes 5,000 Keyword Lookup credits per year. This entire pool resets once per year on your account renewal date — the anniversary of when your subscription started — not on a monthly billing cycle. Key points to remember: - Credits do not replenish every month. The full 5,000 credits are available for the entire year and reset annually. - Your renewal date may differ from your monthly payment date if you are on an annual plan billed monthly or if you started mid-cycle. - Unused credits do not roll over after the annual reset. To check your current Keyword Lookup balance and renewal date, go to your account usage or billing page inside the platform. 🖥️ MCP vs. Dashboard: No Separate Credit Pool It is important to understand that the MCP server is a programmatic interface to the same Search Atlas data — it is not a separate product with its own credits. Every query you run through the MCP server: - Draws from the same credit pools as the dashboard. - Is visible in the same usage counters you see in your account. - Counts toward the same annual or plan-level limits. This means that if you run keyword lookups both through the dashboard and through the MCP server in the same plan period, both sets of queries pull from the single shared Keyword Lookup allocation. Plan your programmatic usage accordingly, especially if your team also runs regular lookups manually through the dashboard. ✅ Quick Reference: Credit Consumption by Query Type - MCP domain keyword ranking query (e.g., 74 results): 74 Keyword Lookup credits consumed. - Dashboard Site Explorer keyword detail view: Keyword Lookup credits consumed per row. - Adding keywords to Rank Tracker: Keyword Rank Tracker credits consumed, not Keyword Lookup. - Keyword Magic bulk discovery: Keyword Magic credits consumed. - Keyword Gap analysis (Left sidebar → Site Metrics → Keyword Gap): Draws from its own respective quota, separate from Keyword Lookup. 🔍 How to Check Your Current Keyword Lookup Balance 1. Log in to your Search Atlas account. 2. Navigate to your account or subscription settings. 3. Look for the Keyword Lookup or Site Explorer Detail usage row. 4. Review the credits used, credits remaining, and the next reset date shown next to that allocation. 5. Confirm the reset date shown is your annual renewal date, not a monthly date. If the reset date shown does not match what you expect, contact support to confirm your account renewal anniversary. 💬 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.

🔌 Configure OTTO Pixel UUID and WordPress Plugin Authentication

🧭 Overview The Search Atlas WordPress plugin connects your site to OTTO SEO by verifying your API Key and a tracking pixel tied to your site's unique OTTO Pixel UUID. Authentication failures typically happen when credentials are mismatched, the site URL does not align with what Search Atlas has on record, or the UUID has not been entered manually. This article walks you through the general process to resolve these issues. 🔑 Step 1: Locate Your API Key Your API Key is found inside the Search Atlas platform. Follow these steps: 1. Log in to your Search Atlas account. 2. Navigate to Avatar Menu (👤) → Settings → API Keys. 3. Find the section related to API access or integrations. 4. Copy the API Key displayed. Keep this value ready — you will paste it into the WordPress plugin in a later step. Important: Do not share your API Key publicly. If you suspect it has been compromised, regenerate it from the same settings area and update it in the WordPress plugin immediately. 🪄 Step 2: Locate Your OTTO Pixel UUID Each website you manage in Search Atlas has a unique OTTO Pixel UUID. This identifier links the WordPress plugin to the correct OTTO SEO project. To find it: 1. Log in to your Search Atlas account. 2. Navigate to the OTTO SEO or OTTO SEO section of the platform. 3. Select the website project you are trying to connect. 4. Look for the pixel or UUID information within that project's settings or setup area. 5. Copy the UUID string displayed. Note: Each website has its own UUID. If you manage multiple sites, confirm you are copying the UUID for the specific domain you are configuring in WordPress. 🔌 Step 3: Enter Credentials Manually in the WordPress Plugin Once you have both your API Key and OTTO Pixel UUID, enter them directly into the plugin: 1. Log in to your WordPress admin dashboard. 2. Navigate to the Search Atlas plugin settings within WordPress. 3. Locate the field for your API Key and paste the value you copied in Step 1. 4. Locate the field for your OTTO Pixel UUID and paste the value you copied in Step 2. 5. Save the settings to apply the credentials. 6. Check whether the connection is confirmed. If an error appears, proceed to the troubleshooting steps below. 🌐 Step 4: Verify Your Site URL Matches A mismatch between the URL registered in Search Atlas and the URL your WordPress site reports is one of the most common causes of authentication failures. To address this: 1. Check the domain associated with your project inside the Search Atlas platform. 2. Compare it to the URL your WordPress site is using (including whether it uses www or non-www, and whether it uses http or https). 3. If there is a discrepancy, update the URL in Search Atlas or adjust your WordPress site URL so the two values match exactly. 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.

🕐 Scheduled Posts Syncing from Search Atlas to GoHighLevel

📋 Overview When you schedule a social or GBP post in Search Atlas, it is queued for publication and then synced to your connected GoHighLevel (GHL) account. This sync does not happen instantly — there is a processing window you should expect before the post appears inside GHL. ⏱️ How Long Does Syncing Take? Under normal conditions, a scheduled post created in Search Atlas will appear in GoHighLevel within a few minutes up to 1 hour after the scheduled publish time. The exact timing depends on: - Queue load: High-volume publishing periods may add a short delay to processing. - GHL API response times: Occasionally, GoHighLevel's API takes longer to acknowledge and reflect the incoming data on their end. - Post type and account configuration: Some post types or sub-account setups in GHL may surface synced content in different sections of the platform. If your post has not appeared in GHL within 2 hours of its scheduled time, this is outside the expected window and warrants further investigation. 📍 Where to Create and Schedule Posts in Search Atlas Posts are managed from Left sidebar → Local → Posts. From this screen you can create new posts, set a publish date and time, and connect your GHL integration before scheduling. 🔍 What to Check Before Contacting Support Before escalating, run through the checklist below — most delayed-sync issues are resolved at one of these steps: 1. Confirm the post status in Search Atlas: Go to Left sidebar → Local → Posts and verify the post shows a status of Scheduled or Published, not Draft or Failed. 2. Check the scheduled time and timezone: Make sure the publish time was set in the correct timezone. A mismatch between your Search Atlas account timezone and your GHL sub-account timezone is a common cause of apparent delays. 3. Verify the GHL integration is active: Confirm your GoHighLevel account is still connected and authorised. If the OAuth token has expired, posts will queue but not deliver. Reconnecting the integration and re-saving the post typically resolves this. 4. Look in the correct GHL location: Synced posts may appear under the Social Planner section of your GHL sub-account. If you are looking elsewhere in GHL, the post may already be there. 5. Wait the full 2-hour window: If the scheduled time was recent, allow the full 2 hours before treating it as a failed sync. ⚠️ Common Reasons a Post May Not Appear in GHL - The GoHighLevel integration was disconnected or the access token expired after the post was scheduled. - The post was saved as a Draft instead of being fully scheduled. - A timezone mismatch caused the post to be queued for a future time that has not yet been reached. - The GHL sub-account selected at the time of scheduling no longer matches the currently active integration. - A temporary GHL API outage delayed the handoff; these usually self-resolve within a few hours. 🔄 How to Resync or Reschedule a Post 1. Go to Left sidebar → Local → Posts. 2. Locate the affected post and open it for editing. 3. Verify all settings — GHL account, scheduled time, and timezone — are correct. 4. If the post status shows Failed, update the scheduled time to a near-future time and save it again to re-queue it for delivery. 5. Monitor the post status; it should update to Published once GHL confirms receipt. 💬 Need More Help? If you have followed all the steps above and your post still has not synced to GoHighLevel after 2 hours, our team can investigate the delivery logs directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔑 Where to Find Your UUID and API Key in Search Atlas

If you're setting up OTTO, connecting an integration, or working with a developer, you may be asked for either your UUID or your API Key. While they may sound similar, they serve very different purposes and are located in different areas of the dashboard. This guide shows you exactly where to find each one. 🆔 How to Find Your UUID (OTTO Pixel UUID) Your UUID is part of your OTTO Pixel installation script. It identifies your specific project installation. Navigate to Left Sidebar → OTTO SEO → All Sites, select your project, then open Installation Guide → Custom Installation. Custom Installation page with the OTTO Pixel script Under Step 1: Copy Your Pixel Script, you'll see a script block containing a data-uuid attribute formatted like XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. That value is your UUID. 🧠 What the UUID Is Used For It identifies your OTTO installation, connects your website to your specific project, is unique per project, and is automatically generated. You'll typically need it when verifying pixel installation, troubleshooting OTTO setup, or working with technical support. 🔐 How to Find Your API Key Your API Key is different from your UUID. It's used for integrations and external connections to Search Atlas. Navigate to Top Right → Click Your Profile Name → Settings → API Keys. API Keys panel in account settings You'll see a section titled Search Atlas API Key, with a long alphanumeric key. That string is your API Key. 🧠 What the API Key Is Used For It's used for connecting third-party tools, API-based integrations, automation workflows, and external platform connections. Your API Key is sensitive — do not share it publicly. ⚖️ UUID vs API Key — What's the Difference? The UUID is found in the OTTO Installation Guide, is project-specific, is used for pixel installation, and lives inside a script tag. The API Key is found in Account Settings, is account-level, is used for integrations, and is displayed in the API Keys panel. Quick summary: Need to install or verify OTTO? Get your UUID. Connecting an integration or using API access? Get your API Key. 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.

☁️ Cloud Stack Generation: Manual Trigger and Approval Workflow

🔍 Overview: Creation vs. Generation When you build Cloud Stacks through OTTO or directly in the Authority section, each stack passes through two distinct states: Created and Generated. These are not the same thing, and understanding the difference is the most common reason stacks appear to be "stuck" or failing. - Created — The stack record exists and your Knowledge Graph data is attached, but no AI content has been produced yet. - Generated — The AI generation button has been manually triggered, a target site has been selected, and content has been produced and accepted. A fully populated Knowledge Graph does not automatically start generation. You must manually trigger each stage of the workflow described below. 🗺️ The Full Cloud Stack Generation Workflow Follow these steps in order. Skipping any step will leave your stacks in a pending state. 1. Navigate to Cloud Stacks. Go to Left sidebar → Authority → Cloud Stacks. You will see a list of all stacks, each showing its current status. 2. Confirm your stacks are in Created status. Stacks that have not yet been generated display a status of Created or Pending Generation. This is expected and not a technical error. 3. Open the stack you want to generate. Click the stack name or its row to open the detail view. 4. Select your target site. Before generation can begin, you must choose which website this stack will be built around. Use the site selector inside the stack detail view to assign the correct domain. Generation cannot proceed without a site selection. 5. Click the AI Generation button. Once a site is selected, the Generate button becomes active. Click it to start the AI content creation process. This step must be performed manually for every stack — there is no bulk auto-trigger. 6. Review and accept the generated content. When generation completes, the platform presents the content for your review. Read through each section and click Accept to confirm the output. Stacks that are not accepted will not proceed to publishing. 7. Publish the stack. After acceptance, click Publish to make the stack live. Only published stacks contribute to your authority-building campaign. ⚡ Why Stacks Created in OTTO Require Manual Action When OTTO creates Cloud Stacks as part of an automated SEO workflow, it handles the creation stage — it populates the stack with Knowledge Graph data and queues the records. OTTO does not automatically trigger AI generation. This is intentional: the manual trigger gives you an opportunity to verify site selection and review content before HDC credits are consumed. If you see a batch of stacks in your Cloud Stacks dashboard that were created by OTTO but show no generated content, this is the expected workflow state — not a failure. Simply follow the generation steps above for each stack. 💳 Understanding HDC Credit Usage and Billing HDC (Hyperdrive Credits) are consumed at the point of generation, not at creation. This means: - Creating a stack through OTTO or manually does not deduct HDC credits. - Clicking the Generate button for a stack deducts the applicable HDC credits for that stack. - If you triggered generation for stacks beyond your plan's included HDC allocation, overage charges apply at the standard rate. If you believe your charges do not match your usage, here is how to reconcile them: 1. Go to Left sidebar → Authority → Cloud Stacks and review the status of all stacks. 2. Count the stacks showing a Generated or Published status — these are the stacks for which HDC credits were consumed. 3. Compare that number to the HDC allocation on your current Authority Plan. 4. Any stacks generated beyond your plan's included HDC count will appear as overage on your invoice. For example: if your Authority Plan includes a set HDC allocation and generation was triggered for a total that exceeds that amount, the difference is billed as overage. Review your generation history inside the Cloud Stacks dashboard to identify exactly which stacks consumed credits beyond your allocation. ✅ Quick Checklist Before Triggering Generation - Knowledge Graph is fully populated with accurate business information. - Target site is selected inside the stack detail view. - You have confirmed your remaining HDC credit balance to avoid unexpected overage charges. - You are ready to review and accept content immediately after generation completes. 🛠️ Troubleshooting Common Issues - Generate button is greyed out: A target site has not been selected. Assign a site in the stack detail view first. - Stack shows Created but no content: Generation has not been triggered. This is a workflow step, not a technical error. Click Generate. - Content is generated but stack is not live: The content review and Accept step has not been completed, or the Publish step was skipped. - Unexpected charge on invoice: Check how many stacks reached Generated status. Overage is charged per HDC consumed beyond your plan limit. 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 Website Studio Projects to WordPress via MetaSync

Overview Website Studio projects can be published directly to a self-hosted WordPress site using the MetaSync Plugin — a supported Search Atlas integration. This article explains what MetaSync is and how to get started. Because setup details vary by account and WordPress environment, the Search Atlas support team will provide you with the plugin file and guide you through the full connection and publishing process. What Is the MetaSync Plugin? MetaSync is a WordPress plugin that works with your Website Studio project and your WordPress installation. Once connected, it allows your published Website Studio project to appear on your WordPress domain without requiring manual file uploads or a separate static host. MetaSync is the recommended method when you want your Website Studio project to live on an existing WordPress domain. Before You Begin - You have an active Search Atlas account and at least one saved project in Website Studio. - You have WordPress installed with admin access. - You have the ability to install plugins on your WordPress site. Step 1 — Request the MetaSync Plugin from Support The MetaSync plugin file is provided directly by the Search Atlas support team. To request it, open the chat widget in your Search Atlas dashboard and ask a support agent for the MetaSync plugin. Have the following ready to speed up the process: - Your Search Atlas account email or project name - Your WordPress site URL - Your WordPress version (visible in your WordPress admin area) Step 2 — Install the MetaSync Plugin on WordPress Once you have received the plugin file from the support team, follow the installation instructions they provide alongside the file. Plugin installation steps can vary depending on your WordPress hosting environment, so follow the guidance given by the support agent for your specific setup. Step 3 — Connect MetaSync to Website Studio and Publish After installation, the Search Atlas support team will guide you through connecting MetaSync to your Search Atlas account and publishing your Website Studio project. Connection and publishing steps depend on your specific account and site configuration. When contacting support, have the following information ready: - Your Search Atlas project name - Your WordPress site URL - Any error messages you see (including exact wording and screenshots if possible) - The timestamp when you first encountered the issue Troubleshooting Common Issues If you encounter problems after attempting to publish — such as a white screen, MIME type errors, or a failed connection — note the exact error message displayed and contact the support team. Providing a screenshot of the error along with your project name and WordPress site URL will help the team resolve your issue as quickly as possible. If you need help at any stage of this process, reach out to our support team via the chat widget in your Search Atlas dashboard and we'll be happy to assist.

🚀 Search Atlas Setup Guide for React Projects

🧭 Overview If you have a React JS project and are unsure which Search Atlas features to prioritize, you are not alone. React sites have specific SEO challenges — including client-side rendering and dynamic content — that make certain platform tools especially valuable. This article walks you through the most impactful features, how to access month-to-month data, and where to find the heatmap so you can get the most out of your subscription. 📊 Will My Site Improve Without Actively Using the Tools? Search Atlas surfaces data and insights, but it does not automatically optimize your site on your behalf. To see month-to-month improvements, you need to actively use the platform: review recommendations, implement changes on your React project, and track results over time. Think of Search Atlas as your SEO command center — the more consistently you engage with it, the more value you unlock. 📈 How to View Month-to-Month Data Month-to-month performance data lives in the Rank Tracker and Site Explorer sections of the platform. Follow these steps to access it: 1. In the left sidebar, click Site Metrics (Site Explorer) to open your site overview at /site-explorer/list. 2. Select the property for your React project from the list. 3. Navigate to Keywords → Rank Tracker using the left sidebar sub-menu. 4. Use the date-range selector at the top of the page to compare month-over-month keyword positions, traffic estimates, and visibility trends. For keyword-level growth, also check Keywords → Keyword Magic to identify which terms are gaining or losing traction each month. 🗺️ How to Find the Heatmap The heatmap is part of the Local section of Search Atlas, which focuses on Google Business Profile (GBP) performance. To access it: 1. Click Local in the left sidebar. 2. Open your GBP project or create one if you have not done so yet. 3. Select Local SEO Heatmaps from the sub-menu to view the local visibility heatmap for your target keywords and service area. The heatmap displays a grid of geo-points showing where your business ranks for a given keyword across different locations. Review it monthly to spot gaps in local visibility and adjust your optimization strategy accordingly. 🛠️ Underutilized Tools That Are Most Helpful for React JS Projects React JS sites are often under-optimized for SEO because client-side rendering can make content invisible to search engine crawlers. The following Search Atlas tools are particularly effective for closing that gap: - Site Explorer (Site Explorer) — Audit your React site's indexed pages, backlink profile, and organic visibility. Go to Left sidebar → Site Metrics (Site Explorer) to start. Many customers overlook how much crawl and indexation data is available here. - Rank Tracker — Track keyword rankings week over week and month over month. Found at Left sidebar → Keywords → Rank Tracker. Essential for measuring whether your React rendering improvements are translating into ranking gains. - Keyword Gap — Compare your React site's keyword coverage against competitors and find terms you are missing. Navigate to Left sidebar → Keywords → Keyword Gap. This is one of the most underused tools in the platform and often reveals quick wins. - Keyword Magic — Discover new keyword clusters to target in your React app's page structure, metadata, and content. Found at Left sidebar → Keywords → Keyword Magic. - Local SEO Heatmaps (Heatmap) — If your React project serves a local audience, the heatmap at Left sidebar → Local → Local SEO Heatmaps shows exactly where you are winning and losing local search visibility. - Local Citations — Inconsistent business listings can drag down local rankings. Audit and fix them at Left sidebar → Local → Local Citations. ✅ Recommended Monthly Workflow for React Projects To build steady month-to-month improvements, follow this simple routine each month: 1. Open Site Explorer and review any new crawl issues or drops in indexed pages — React routing changes frequently cause unintended deindexation. 2. Check Rank Tracker to compare this month's keyword positions against last month. 3. Run a Keyword Gap analysis to find competitor keywords you should be targeting in your next content or metadata update. 4. If you have a local presence, open Local → Local SEO Heatmaps and review the heatmap for visibility changes in your target area. 5. Use Keyword Magic to plan new content topics or on-page optimizations for the coming month. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Search Atlas MCP Client Compatibility Explained

🧭 Overview Search Atlas MCP (Model Context Protocol) lets AI clients access Search Atlas tools and data directly inside your AI workflow. Search Atlas MCP is built for any MCP client, ChatGPT included. It authenticates via OAuth login (requires an active Search Atlas subscription) or with a Search Atlas API key sent in the X-API-Key header (from Settings → API Keys). ✅ Supported MCP Clients Search Atlas MCP works with any MCP client, including: - Claude Desktop and Claude.ai - ChatGPT - Any other client that implements the standard MCP protocol with full tool-calling support If you are using one of these clients and experiencing a connection issue, that is a separate troubleshooting topic unrelated to client compatibility. 🔐 How to Authenticate Search Atlas MCP supports two authentication methods: - OAuth login — sign in with your Search Atlas account (requires an active Search Atlas subscription). - API key — send your Search Atlas API key in the X-API-Key header. You can generate one from Settings → API Keys. If you are on a supported client and still cannot connect, please refer to the Search Atlas MCP setup and troubleshooting guide. 💬 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.

☁️ Cloud Stack Provider Deployment Status Explained

🔍 Overview When you deploy a Cloud Stack, Search Atlas pushes your content to multiple providers simultaneously. Most providers go live within minutes, but Cloudflare has a longer propagation window due to its global network architecture. Seeing Awaiting next to Cloudflare while all other providers show Live is completely normal and does not indicate a failure. This article explains each deployment status, why Cloudflare takes longer, and what steps to take if the delay exceeds the expected window. 📋 Understanding Deployment Statuses Each provider in your Cloud Stack will display one of the following statuses: - Live — The provider has successfully published your content and it is publicly accessible. - Awaiting — The deployment request has been sent and is in queue or propagating. This is a normal, expected state — not an error. - Failed — The provider encountered an error during deployment. This status requires action and is visually distinct from Awaiting. **Important:**Awaiting and Failed are two different statuses. If your Cloudflare provider shows Awaiting, your deployment is progressing normally. Do not attempt to rebuild or re-trigger the deployment while this status is active. ⏱️ Why Cloudflare Shows 'Awaiting' Longer Than Other Providers Cloudflare operates one of the largest content delivery networks in the world. When Search Atlas pushes a deployment to Cloudflare, the following happens: 1. The deployment request enters Cloudflare's provisioning queue. 2. Cloudflare validates and distributes the content across its global edge nodes. 3. DNS propagation completes and the status updates to Live. This process typically takes 15 to 45 minutes but can occasionally extend to a few hours depending on Cloudflare's network conditions. All other providers in your Stack — such as the 13 providers already showing Live on your deployment — operate on faster individual pipelines, which is why they resolve first. ✅ What To Do While Cloudflare Shows 'Awaiting' Follow these steps to confirm everything is on track: 1. Verify that the status shown is Awaiting and not Failed. The labels are clearly differentiated in the interface. 2. Check the timestamp of your deployment. If it has been less than 2 hours, no action is needed — allow propagation to complete. 3. Refresh your Cloud Stack dashboard after 30 minutes to check for a status update. 4. If the status remains Awaiting after 4 hours, proceed to the escalation steps below. Do not use any rebuild or re-deploy action while the status shows Awaiting. Triggering a rebuild during active propagation can cause duplicate deployment conflicts and further delay the process. 📊 Track Keyword Rankings While You Wait While your Cloudflare provider finishes propagating, you can begin setting up rank tracking for your domain so you are ready to monitor performance as soon as the full Stack goes live. 1. In the left sidebar, navigate to Keywords → Rank Tracker (Keyword Rank Tracker). 2. Enter your domain (e.g., hugehealthfitness.com) and add the target keywords you want to monitor. 3. Set your preferred location and search engine settings. 4. Save your configuration — tracking will begin on the next scheduled crawl cycle. Having your Rank Tracker configured in advance means you will capture baseline data immediately once all Cloud Stack providers, including Cloudflare, are fully live. 🚨 When 'Awaiting' Might Actually Be a Problem In rare cases, a status can become stuck. Look for these signs that something may require investigation: - Cloudflare shows Awaiting for more than 6 hours with no change. - The deployment timestamp shows the job was initiated more than 24 hours ago. - Other providers that were Live have reverted to a different status. If any of these conditions apply, document your Stack ID (e.g., Stack ID 24055) and the exact duration before contacting support. Do not rebuild — our team will investigate the deployment job directly. 💬 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.

📘 Shopify CMS Connector Status in Search Atlas

The Shopify CMS connector in Search Atlas previously had a known limitation caused by a change Shopify made to how API tokens are generated. That issue has since been resolved: the connector now supports an automated authentication flow, and the manual workaround described in earlier versions of this article is no longer required. This article explains what changed, how the connector authenticates today, and how to set it up. 🧠 What Changed on Shopify's Side Shopify updated its requirements for generating API access. For a period, this meant that obtaining a usable API token required manually building a cURL request, which required technical/programming knowledge and was not a simple UI-based process. ⚙️ How the Connector Authenticates Today The Shopify CMS connector now supports two authentication methods: - Client Credentials (current, recommended): an automated OAuth flow. You create a custom app in the Shopify Partner or Dev Dashboard, then provide the Client ID and Client Secret to Search Atlas. Search Atlas handles the token exchange automatically — no manual cURL request needed. - Access Token (legacy): the older admin API token still works if you already have one configured. 🛠️ Setting Up the Shopify Connector 1. In Shopify, create a custom app in your Partner or Dev Dashboard and copy the Client ID and Client Secret. 2. In Search Atlas, click your avatar in the top-right and go to Settings → CMS Connectors tab, then choose Add Connector → Shopify. 3. Select Client Credentials as the authentication method. 4. Enter the Client ID, Client Secret, and your shop domain, then save. ❓ FAQs Is the Shopify CMS connector still broken? No. The connector now supports an automated authentication flow, and the manual token workaround is no longer needed. Do I need programming knowledge to set it up now? No. Client Credentials setup only requires copying a Client ID and Client Secret from Shopify into Search Atlas. I already set up the connector using the old access token — do I need to redo it? No, the legacy access token method still works. Switching to Client Credentials is recommended but not required. 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.

🔧 Installing OTTO Tracking Code on Multiple WordPress Sites

🧭 Overview Each WordPress site you manage in Search Atlas requires its own OTTO tracking code installation. If the code is detected on your first site but not your second, the issue is likely related to placement scope, caching, or a missing site-specific snippet. This article outlines what to check when setting up OTTO on an additional WordPress site. ⚠️ Why Your Second Site May Not Be Detected Even if you followed the same steps as your first site, these are common reasons OTTO may fail to detect the tracking code on an additional WordPress site: - Wrong placement scope: The code was added to a single page or post template instead of a global, site-wide location. - Cached pages: Your WordPress cache is serving an older version of the page that does not yet include the tracking code. - Wrong tracking code used: Each site in Search Atlas has a unique tracking snippet. You must copy the code for the specific site you are configuring, not reuse the snippet from your first site. - Theme or plugin conflict: Some themes or header plugins do not inject code into every page type, leaving certain URLs unverifiable. - Code placed inside a conditional block: If the snippet is wrapped in a condition (for example, only loading on the homepage), OTTO cannot confirm site-wide installation. 📋 Before You Begin Make sure you have the following ready for each additional site: - Admin access to the WordPress dashboard for the site you are configuring. - The correct OTTO tracking code for that specific site (retrieved from Search Atlas — see steps below). - A method to inject code site-wide, such as a header injection plugin or direct access to your active theme's header template file. 🪄 Step 1 — Retrieve the Correct Tracking Code for Your Site 1. Log in to Search Atlas and open the OTTO section of the platform. 2. Locate the site you want to configure — make sure you have selected the correct site before copying any code. 3. Find the tracking code snippet for that site and copy it. Do not reuse the snippet from any other site — each snippet is unique to its domain. 📌 Step 2 — Install the Code Site-Wide on WordPress The tracking code must appear on every page of your site, not just the homepage. Use one of the following general approaches: Option A — Using a Header Injection Plugin (Recommended) 1. Install and activate a header injection plugin of your choice in your WordPress admin. 2. Locate the plugin's settings and paste the OTTO tracking code into the appropriate header scripts field. 3. Save your changes. Option B — Editing Your Theme's Header Template Directly 1. Access your active theme's header template file through your WordPress admin or via FTP/file manager. 2. Paste the OTTO tracking code before the closing </head> tag. 3. Save your changes. 🔄 Step 3 — Clear Your Cache After installing the code, clear any WordPress caching plugins, server-level caches, and CDN caches associated with the site. Cached pages may prevent OTTO from detecting the newly added snippet until the cache is refreshed. ✅ Step 4 — Verify Detection in Search Atlas Return to Search Atlas, locate the site you just configured, and trigger a new detection check. If the code is still not detected after clearing your cache, review the placement method to confirm the snippet is loading on all page types and is not wrapped in any conditional logic. 📞 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.

📘 X (Twitter) Integration in Search Atlas

Connect your X (Twitter) account to share content and track engagement from your dashboard. ⚙️ How to Connect 1. Go to Settings → Integrations. 2. Locate Twitter Account. 3. Click ➕ Connect account. 4. Log in to your X account. 5. Approve permissions. 🎯 What You Can Do 1. Share content. 2. Track engagement. 3. Monitor activity. ⚠️ Common Issues 1. Login failed — Check credentials. 2. Permissions denied — Approve access. 3. Account mismatch — Use the correct account. 4. Posts failing to send — X's API occasionally rejects requests platform-wide due to X-side access limits; if this happens, wait and retry, and contact support if it persists beyond a day. ❓ FAQ Can I post directly? Yes, once connected, you can share updates. 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.

💡 MCP Server Keyword Queries Credit Consumption Explained

🔍 Overview When you use the Search Atlas MCP server (mcp.searchatlas.com) to run keyword-related queries — such as retrieving keyword rankings for a domain — your account is charged using Universal Credits (UC). Understanding how these credits are consumed helps you plan usage and avoid unexpected quota shortfalls. 📊 How Credits Are Charged for Keyword Queries Credit consumption for keyword ranking queries through the MCP server is based on the number of results returned, not the number of queries submitted. This means: - If a domain ranking query returns 74 keywords, your account is charged for 74 rows of data. - Each keyword result row consumes 1 Universal Credit. - A single API call that returns 74 keywords will therefore deduct 74 Universal Credits from your quota. This row-based billing model replaced the previous fixed query-limit system. The credit system now reflects actual data consumption rather than the number of times you call the endpoint. 💳 What Type of Credit Is Used? Keyword queries run through the MCP server consume Universal Credits (UC). Universal Credits are a shared credit pool used across multiple Search Atlas features, including keyword research, site exploration, and other data-intensive tools. There is no separate credit bucket exclusively for MCP server calls. 🔄 When Does My Credit Quota Reset? Universal Credit quotas reset on your monthly billing cycle date — the same date your Search Atlas subscription renews each month. For example, if your billing date is the 5th of each month, your UC balance resets on the 5th. - Unused Universal Credits do not roll over to the next billing period. - If you exhaust your UC balance before the reset date, you can top up your credits from the billing page inside the platform. - Credit consumption and remaining balance are visible in your account's billing and quota section. 🛠️ How to Monitor Your Universal Credit Usage 1. Log in to your Search Atlas account. 2. Navigate to your Billing page using the Avatar Menu (👤). 3. Locate the Universal Credits section to view your current balance, total allocation, and consumption history. If quota banners or credit totals do not appear to update immediately after MCP server queries, allow a few minutes for the system to sync and then refresh the page. This is a known display latency that does not affect actual credit deduction accuracy. 💡 Tips to Manage Credit Consumption - Filter before querying: Narrow your domain or keyword parameters in the MCP request to retrieve only the results you need, reducing the number of rows returned. - Avoid duplicate queries: The MCP server includes keyword deduplication warnings — pay attention to these to prevent charging for repeated data. - Schedule large queries strategically: If you expect high-volume queries, run them shortly after your billing reset date to maximise the credit window. - Use the Rank Tracker for ongoing monitoring: For recurring keyword tracking needs, consider using Left sidebar → Keywords → Rank Tracker (Keyword Rank Tracker) inside the platform, which may be more credit-efficient than repeated MCP queries for the same data. ❓ Frequently Asked Questions Does the number of domains queried affect credit consumption? Yes. Each domain query is processed independently. If you query three domains and each returns 50 keywords, your account is charged 150 Universal Credits in total (50 per domain). What if the query returns zero results? If no keyword data is returned, no Universal Credits are deducted. Credits are only consumed for rows of data actually delivered. Can I see a breakdown of MCP server credit usage specifically? The Billing page's Activity Log tab currently shows overall UC consumption. If you need a granular breakdown by tool or query type, contact our support team via the chat widget. 🆘 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 GHL Integration Pricing and Account Migration Guide

🧭 Overview If you access Search Atlas through a GoHighLevel (GHL) sub-account, your pricing and billing are managed differently than a direct Search Atlas subscription. This article explains what changes when you use the GHL integration, how pricing is structured, and what to expect if you ever need to migrate between the two. 💰 How GHL Integration Pricing Works When you access Search Atlas through a GHL agency account, pricing is set and managed by your GHL agency, not directly by Search Atlas. This means: - Your subscription rate, plan tier, and billing cycle are determined by the GHL agency that provisioned your account. - Search Atlas does not control what your agency charges you for GHL-integrated access. - Invoices and payment for GHL-integrated accounts go through the GHL platform, not through Search Atlas billing. If you are on a direct Search Atlas plan, your billing is managed entirely within your Search Atlas account dashboard, and pricing follows the standard Search Atlas plans published on our pricing page. 📊 GHL Integration vs. Direct Plan: Key Differences - Billing owner: GHL agency (GHL integration) vs. Search Atlas directly (direct plan). - Pricing rate: Determined by your GHL agency vs. standard Search Atlas pricing tiers. - Feature access: Both paths provide access to Search Atlas tools, but available features may vary depending on the plan tier your agency has enabled for your sub-account. - Support for billing questions: GHL-integrated users must contact their GHL agency for any pricing, invoice, or plan-change queries. Search Atlas support cannot adjust or view GHL agency billing. - OTTO pixel and other tools: Work the same way regardless of which path you use to access Search Atlas. 🔄 Migrating Between GHL Integration and a Direct Plan If you want to switch from a GHL-integrated account to a direct Search Atlas subscription (or vice versa), follow the steps below. 1. Back up your data. Export any reports, saved projects, or configurations you need before making changes. 2. Contact your GHL agency. Inform them you intend to move to a direct Search Atlas plan. They will need to deprovision or disconnect your GHL sub-account access. 3. Sign up for a direct Search Atlas plan. Go to the Search Atlas website and create or log in to a standalone account with the email address you want to use going forward. 4. Reconnect your website and tools. After your new direct account is active, reconnect your website, reinstall the OTTO pixel (see the section below), and relink any integrations such as Google Search Console or Google Analytics. 5. Verify OTTO pixel status. Once reinstalled, navigate to the OTTO SEO section (shown as “OTTO SEO” or “OTTO SEO” depending on account branding) in the left sidebar (URL: /seo-automation-v3) to confirm the OTTO pixel shows as Installed. Important: Your data and settings do not automatically transfer between a GHL sub-account and a direct Search Atlas account. You will need to reconfigure projects in your new account. 🛠️ Fixing an OTTO Pixel "Not Installed" Status If the OTTO pixel shows Not Installed after you have already added it to your site, this is usually a detection delay or a placement issue. Try the following: 1. Go to the OTTO SEO section (shown as “OTTO SEO” or “OTTO SEO” depending on account branding) in the left sidebar to open the OTTO dashboard. 2. Copy the latest version of your OTTO pixel code from the dashboard. 3. Paste the pixel code into the <head> section of every page on your website, or use your CMS or tag manager to deploy it site-wide. 4. Clear your website cache and any CDN cache. 5. Wait up to 24 hours for the pixel status to update. Refresh the OTTO SEO page to check. 6. If the status still shows Not Installed after 24 hours, use a browser inspector or a tag-checking tool to confirm the script is firing on your live site. Switching from a GHL-integrated account to a direct account requires reinstalling the pixel under your new account, because each account generates a unique pixel ID. 🙋 Who to Contact for Pricing Questions - GHL integration pricing: Contact your GHL agency directly. Search Atlas support cannot view or change agency-set pricing for GHL sub-accounts. - Direct Search Atlas plan pricing: Use the chat widget inside the Search Atlas platform. - Technical issues (pixel installation, tool access, feature questions): Search Atlas support can help regardless of whether you are on a GHL or direct plan. 💬 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.

💡 Understanding GHL Integration Pricing and Discounts

🔍 Overview Search Atlas integrates with GoHighLevel (GHL) to help agencies manage SEO services for their clients. The standard GHL integration is priced at $79/month per sub-account. This article explains how that pricing works, what discount options may be available, and how to submit a request for a custom introductory rate. 📊 Standard GHL Integration Pricing By default, each GHL sub-account connected through Search Atlas is billed at $79/month. This rate applies regardless of whether the sub-account belongs to an active client or a prospect you are onboarding. There is no automatic trial or reduced rate applied at the account level. 💰 Can I Get a Discounted Rate for Prospects? Some agency owners ask whether they can offer prospects a lower introductory rate — for example, $37/month for the first 30 days — before the price increases to the standard $79/month upon conversion. This type of tiered or introductory pricing is not available as a self-serve option in the platform at this time. However, custom pricing arrangements may be considered on a case-by-case basis. To explore this, you will need to speak directly with the Search Atlas team through the in-platform chat. Here is what to prepare before reaching out: - The number of prospects you are looking to onboard at the discounted rate - The proposed introductory period (e.g., 30 days) and the price point you are requesting - Your expected conversion rate or timeline for moving prospects to full-paying clients - Your current plan and account details so the team can review eligibility ⚙️ How GHL Sub-Account Billing Works Understanding the billing mechanics can help you plan your prospect onboarding strategy: 1. Sub-accounts are billed monthly from the date they are connected to your Search Atlas workspace. 2. Each sub-account is billed independently, so adding a prospect sub-account triggers the standard monthly charge unless a custom arrangement is in place. 3. Removing a sub-account before the billing cycle renews will stop future charges, but partial-month refunds are subject to Search Atlas refund policy. 4. Upgrades and changes to a sub-account's status (e.g., prospect to active client) do not automatically change the billing rate — pricing is set at the account configuration level. 🛠️ Steps to Request a Custom Introductory Rate 1. Log in to your Search Atlas account. 2. Open the chat widget in the bottom-right corner of the platform. 3. Type human teammate to be connected with a member of our team. 4. Explain your use case — include the number of prospects, the rate you are requesting, and the intended duration of the discount. 5. The team will review your account and respond with available options. Note: Custom pricing requests are not guaranteed and are reviewed based on account standing, volume, and business context. Submitting a request does not confirm approval. 💡 Tips for Managing Prospect Costs While waiting for a custom pricing decision, here are a few ways to manage costs when onboarding GHL prospects: - Only connect sub-accounts when ready to begin active SEO work. Avoid connecting a prospect's sub-account before you need to run campaigns or audits. - Use Search Atlas reporting tools to demonstrate value to prospects quickly, which can shorten the conversion timeline and reduce the number of months billed at prospect stage. - Track your sub-account list regularly to ensure you are not paying for inactive or stalled prospect accounts. 🤝 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏠 Search Atlas Integration Options by CMS Platform

🔍 Overview Search Atlas supports content optimization across a wide range of CMS platforms, but integration capabilities vary depending on your platform. This article focuses on Lofty CMS (formerly Chime), a popular CRM and website platform used by real estate professionals. If you use Lofty, this guide explains exactly what is and is not currently possible, how JavaScript deployment works, and what to expect from the product roadmap. ⚙️ Current Integration Capabilities for Lofty CMS Search Atlas does not have a native plugin or direct backend integration with Lofty CMS. Unlike WordPress — which has a dedicated Search Atlas plugin that writes changes directly to your database — Lofty operates on a closed platform architecture that does not permit third-party plugins in the same way. The options currently available to Lofty users are: - JavaScript snippet deployment — Inject a script tag into your Lofty site's custom code section to enable on-page optimizations dynamically. - Manual CMS edits — Apply Search Atlas recommendations by hand inside the Lofty page editor. There is no automated sync between Search Atlas and Lofty at this time. Every change either requires manual entry or relies on the JavaScript method described below. 📜 How JavaScript Deployment Works The JavaScript deployment option allows Search Atlas to apply content and on-page optimizations dynamically — meaning changes are rendered in the browser when a visitor loads your page, rather than being saved directly into your CMS database. Here is what you need to understand about how this works in practice: - Persistence is conditional, not permanent. The JavaScript snippet must remain active and correctly installed in your Lofty custom code section at all times. Optimizations are applied each time a page loads, so they are only visible while the script is running. - There is a server dependency. The script calls Search Atlas servers to retrieve and apply your configured optimizations. If Search Atlas servers are unreachable, or if your subscription becomes inactive, the JavaScript-driven changes will not render. - Removing the script removes the changes. If you delete the JavaScript snippet from your Lofty site — intentionally or during a site rebuild — all dynamically applied optimizations will immediately disappear from your live pages. No residual edits are left behind in your CMS. - The script does not write to your Lofty database. Unlike a native integration, JavaScript deployment leaves no permanent footprint inside Lofty. Your Lofty page content stays exactly as you entered it in the editor. For changes you want to be truly permanent and independent of any external script, the correct approach is to apply Search Atlas recommendations manually inside the Lofty page editor. Manual edits are saved directly in Lofty and remain live regardless of your Search Atlas subscription status. 🔄 JavaScript vs. Manual Edits — Comparison - JavaScript deployment: Faster to apply across multiple pages, dynamically maintained, but dependent on the script staying active and Search Atlas servers being available. Removing the script removes all changes instantly. - Manual CMS edits: Slower to implement page by page, but changes are saved permanently inside Lofty. No external dependency once saved. Recommended for high-priority pages where stability matters most. Many Lofty users combine both methods: use JavaScript for broader site-wide optimizations and apply manual edits for key landing pages where permanence is critical. 🚫 Why Lofty API Integration Is Not Currently Supported Lofty does not offer a public-facing content API that allows third-party tools to programmatically read and write page content on your behalf. This is a platform-level limitation set by Lofty, not a Search Atlas product gap. Because no stable, documented API exists for content management within Lofty, Search Atlas cannot push edits directly into your Lofty pages the way it can with WordPress via the REST API and the Search Atlas plugin. Any suggestion that you can integrate Search Atlas changes permanently through the Lofty API is inaccurate — this path does not currently exist. If Lofty releases a content API in the future, Search Atlas will evaluate building a direct integration. Until then, JavaScript deployment and manual edits are the supported methods. 🏡 Real Estate Playbooks — Roadmap Status Search Atlas does not currently offer real estate-specific playbooks as a built-in feature. General content strategy playbooks are available within the platform, but vertical-specific playbooks tailored to real estate use cases — such as neighborhood pages, listing content, IDX optimization, and local market guides — are on the product roadmap and under active consideration. There is no confirmed release date for real estate playbooks at this time. If this is a priority for your team, we encourage you to submit a feature request through the platform so the product team can gauge demand. The more requests a feature receives, the higher it is prioritized in the development queue. ✅ Recommended Workflow for Lofty Users 1. Install the Search Atlas JavaScript snippet in your Lofty site's custom code section to activate dynamic optimizations across your site. 2. Use Search Atlas content recommendations and on-page tools to identify priority changes for your most important pages. 3. For high-value pages such as home, service area, or main landing pages, apply recommendations manually inside the Lofty editor to ensure permanent, script-independent changes. 4. Keep the JavaScript snippet active to maintain dynamically applied optimizations across the rest of your site. 5. Do not remove the snippet during site updates unless you have already manually replicated the changes inside Lofty. 💬 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.

🔍 Understanding GSC Account Prefixes: sc-domain Explained

🧩 What Is the sc-domain Prefix? When you connect a website to Search Atlas via Google Search Console (GSC), you may notice your property listed with a prefix such as sc-domain: followed by your domain name — for example, sc-domain:wetspotplumbing.com. This prefix is not an error. It is an internal tag that GSC assigns to properties that were verified and added using the Domain method, as opposed to the URL-prefix method. Search Atlas inherits and displays this label exactly as GSC reports it. - sc-domain: — the property was connected via GSC's Domain verification (covers all subdomains and protocols). - https:// or http:// — the property was connected via the URL-prefix method (covers one specific URL variant). Seeing sc-domain: in front of your domain simply confirms that your GSC property uses domain-level verification, which is actually the broader and more comprehensive of the two connection types. ✅ Is the sc-domain Prefix Causing a Problem? No. The sc-domain: prefix is not the cause of any data issue and does not break your GSC Insights reports. It is a read-only label passed directly from Google and cannot be changed inside Search Atlas. If your GSC Insights data for a property like wetspotplumbing.com appears empty or incomplete, the prefix itself is not the reason. The most common causes of missing or limited data are covered in the section below. 📍 How Location Filtering Affects Data Retrieval One of the most frequent reasons GSC Insights appears to show no data — even when the integration is working correctly — is an active location filter. Here is how it works and what to check: 1. Open Site Metrics → GSC Performance (GSC Insights) in Search Atlas and select your property from the dropdown. Confirm it shows the sc-domain: version of your domain if that is how it was verified in GSC. 2. Check the location filter. If a specific country or region is selected, GSC will only return data for queries originating from that location. If your site has limited traffic from that region, the panel may appear empty. 3. Set location to Worldwide (or the country where your site receives the most traffic) and refresh the report. This is the fastest way to confirm whether location filtering is hiding your data. 4. Check the date range. GSC data has a processing delay of 24–72 hours. If you recently connected the property, select a broader date range to allow data to populate. 5. Verify GSC permissions. The Google account used to connect GSC must have at least Full User access to the property in Google Search Console. Restricted access prevents Search Atlas from retrieving performance data. ⚙️ How to Confirm Your GSC Property Is Connected Correctly 1. Go to Settings → Integrations in Search Atlas. 2. Locate your GSC connection and confirm the property name matches what you see in your Google Search Console account — including the sc-domain: prefix if applicable. 3. If the property is listed but showing no data after following the steps above, try disconnecting and reconnecting the GSC account to refresh the data permission token. 4. After reconnecting, allow up to 24 hours for data to fully sync before investigating further. 🔄 sc-domain vs. URL-Prefix: Key Differences - sc-domain: (Domain property) — Captures data across all subdomains (www, blog, shop) and all protocols (http, https). Recommended for most websites. - URL-prefix property — Captures data only for the exact URL variant verified (e.g., https://www.wetspotplumbing.com). Other variants are tracked separately. If your GSC account contains both a domain property and a URL-prefix property for the same site, make sure you have connected the correct one in Search Atlas. Connecting the URL-prefix version of a property when most of your traffic is indexed under the domain property — or vice versa — will result in incomplete data. 💬 Still Seeing Issues? If you have followed all the steps above and your GSC Insights data is still not loading for your property, 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.

☁️ Cloudflare DNS/API Integration: How It Works

🔍 What Is the Cloudflare DNS/API Integration? The Cloudflare DNS/API integration connects Search Atlas directly to your Cloudflare account using an API token. This gives Search Atlas the ability to read and write your DNS configuration and interact with Cloudflare's edge network on your behalf — without requiring manual file uploads or plugin installations on your server. This method is designed for websites that already use Cloudflare as their DNS provider and want an automated path to technical SEO optimization. ⚙️ How to Set Up the Cloudflare DNS/API Integration Follow these steps to connect your Cloudflare account to Search Atlas: 1. Generate a scoped API token in Cloudflare: Log in to your Cloudflare dashboard, go to My Profile > API Tokens, and click Create Token. Use the Edit zone DNS template or create a custom token scoped to the specific zone (domain) you want to connect. Make sure the token has at least Zone: DNS: Edit and Zone: Zone: Read permissions. Copy the token — you will only see it once. 2. Enter the API token in Search Atlas: In Search Atlas, navigate to your site settings and select the Cloudflare DNS/API integration option. Paste the API token you generated into the designated field and save. 3. Confirm the correct zone is detected: After saving, Search Atlas will display the domain zone associated with the token. Verify that the zone shown matches the domain you intend to connect. If it does not match, check that your token is scoped to the correct zone in Cloudflare. 4. Verify the integration is active: Once connected, Search Atlas will be able to read and write your DNS configuration. Confirm the integration status shows as active or connected within your Search Atlas site settings. If you see an error, double-check the token permissions and that the token has not expired. 🔧 Troubleshooting Common Issues If the integration is not working as expected, check the following before reaching out to support: - Token permissions are too narrow: Make sure the token includes both Zone: DNS: Edit and Zone: Zone: Read at minimum. Missing permissions are the most common cause of connection failures. - Token is scoped to the wrong zone: If you manage multiple domains in Cloudflare, confirm the token is scoped to the specific zone matching the domain in Search Atlas. - Token has expired or been revoked: Cloudflare tokens can be set to expire. If the integration was working before and has stopped, regenerate the token in Cloudflare and update it in Search Atlas. - Zone does not match the domain in Search Atlas: Ensure the domain added in Search Atlas exactly matches the root domain managed in the Cloudflare zone (e.g., example.com, not www.example.com). 🚀 What to Have Ready If You Need Support If you have followed the steps above and the integration is still not connecting, please have the following ready before reaching out: - Your domain name and the Cloudflare zone it belongs to - A description of the specific behavior or feature you are asking about - Any error messages you have encountered during setup - The approximate date and time the issue started 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 Google Analytics, Tag Manager & Ads with Search Atlas

🎯 Overview When you switch SEO providers and onboard to Search Atlas and OTTO, it is essential to reconfigure your Google tracking stack carefully. Skipping steps or leaving old configurations in place can cause duplicate data, broken conversion tracking, or missed attribution. This article walks you through setting up Google Analytics 4 (GA4), Google Tag Manager (GTM), and Google Ads correctly so everything works together from day one. ⚙️ Step 1: Audit Your Existing Tracking Setup Before adding anything new, review what your previous provider may have installed: - Log in to your website's CMS or codebase and check for any hardcoded Google Analytics or GTM snippets added by your former provider. - Open Google Tag Manager and review all published tags. Look for duplicate GA4 configuration tags or old Universal Analytics (UA) tags that should be removed. - In Google Analytics, go to Admin → Data Streams and confirm only your active GA4 property is collecting data. - In Google Ads, go to Tools → Conversions and check that conversion actions are not being fired by both a legacy tag and a new one simultaneously. Remove or pause any tags, snippets, or integrations left by your previous provider before proceeding. 📊 Step 2: Set Up or Verify Your GA4 Property 1. Go to analytics.google.com and confirm you have a GA4 property (not Universal Analytics) for your website. 2. Navigate to Admin → Data Streams → Web and copy your Measurement ID (format: G-XXXXXXXXXX). 3. If you are using Google Tag Manager to deploy GA4 (recommended), do not add the GA4 snippet directly to your site — use GTM exclusively to avoid duplication. 4. In GTM, create a Google Tag using your Measurement ID, trigger it on All Pages, and publish the container. 5. Use the GA4 DebugView (Admin → DebugView) and GTM Preview mode to confirm pageviews are being recorded without duplicates. 🏷️ Step 3: Configure Google Tag Manager Cleanly A clean GTM container is critical to avoid data conflicts: - Use one Google Tag (GA4 Configuration Tag) per property. Multiple configuration tags for the same Measurement ID will inflate your session counts. - Organise all conversion and event tags under clear naming conventions, for example: [GA4] Scroll Depth or [Ads] Lead Form Submission. - Set up Tag Firing Options on sensitive tags (such as purchase events) to fire Once per page to prevent duplicate conversions. - Before publishing any changes, always use GTM Preview & Debug mode to verify tags fire exactly once on the correct trigger. 💰 Step 4: Link Google Ads and Import Conversions 1. In Google Ads, go to Tools → Conversions → New conversion action. 2. Select Import → Google Analytics 4 properties to import key conversion events (such as form submissions or purchases) directly from GA4. This is the recommended approach as it keeps conversion data consistent across both platforms. 3. Alternatively, if you prefer Google Ads tags, create a conversion action in Google Ads, copy the Global Site Tag and Event Snippet, and deploy them via GTM — never add them directly to the page if GTM is already present. 4. Set a single conversion counting method (one conversion per click) for lead-generation goals and every conversion for e-commerce purchases. 5. After setup, run a test conversion and confirm it appears in Google Ads → Conversions → All conversions within 24 hours. 🤖 Step 5: Using Google Ads Data Inside Search Atlas Search Atlas includes a dedicated Ads workspace to help you monitor and manage your paid campaigns alongside your SEO work. To access it: - In the left sidebar, go to Ads → Launchpad for an overview of your campaigns and available resources. - Use Ads → Analytics to review performance data and identify optimisation opportunities. - Explore Ads → Creative Drive, Ads → Discover, Ads → Routines, and Ads → Brands for additional campaign management tools. - If you would like guided support with your Ads setup, select Explore Training Calls from the Launchpad banner to book a session with the Search Atlas team. Note: Search Atlas displays ad data but does not directly modify your Google Ads account. All structural changes to tags and conversions should be made in Google Ads and GTM directly. ✅ Step 6: Final Checks Before Going Live Run through this checklist before considering your tracking setup complete: - No duplicate tags: Confirm GTM Preview shows each tag firing once per page load. - GA4 receiving data: Real-time report in GA4 shows active users during your test session. - Conversions verified: At least one test conversion appears in both GA4 and Google Ads. - Old provider tags removed: No legacy snippets remain in your HTML, CMS plugins, or GTM container. - GTM container published: All changes are in the live container, not just saved as a draft. 🛠️ Troubleshooting Common Issues - Duplicate sessions in GA4: You have more than one GA4 Configuration Tag firing, or the Measurement ID snippet is hardcoded in the page AND deployed via GTM. Remove one. - Conversions not showing in Google Ads: Allow up to 72 hours after the first test. If they still do not appear, check that the Google Ads conversion linker tag is present in GTM and firing on all pages. - OTTO changes not reflected in analytics: OTTO optimises on-page SEO elements; it does not modify tracking code. If tracking broke after OTTO was activated, the issue is unrelated — revisit your GTM container for conflicting tag changes. 💬 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.

🛠️ Install Search Atlas Pixel on Replit CMS

🔍 Why Your Old Platform Data May Still Appear When you migrate your website to a new platform — such as moving from Wix to Replit — Search Atlas continues tracking the domain you originally connected. If the JavaScript pixel is not installed on your new Replit site, the platform will either show stale data from your previous setup or stop collecting new data altogether. To ensure accurate tracking, you must retrieve a fresh pixel snippet from Search Atlas and install it directly in your Replit project's HTML. 📋 Before You Begin - You have an active Search Atlas account with OTTO SEO enabled. - Your Replit project is set up and your site is live or in development. - You have access to your project's main HTML file (typically index.html) inside the Replit editor. - Your domain in Search Atlas matches the domain your Replit site is published on. ⚙️ Step 1: Retrieve Your Pixel Snippet from Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation). 3. Select the project connected to your Replit website. 4. Navigate to the Pixel Installation or Site Activation section within the OTTO SEO dashboard. 5. Copy the full JavaScript pixel snippet displayed on screen. It will look similar to: <script src="https://cdn.searchatlas.com/pixel/otto.js" data-otto-uuid="YOUR\_UNIQUE\_ID">``</script> Important: Do not reuse a pixel snippet from your old Wix site. Each platform installation should use the snippet retrieved directly from your current OTTO SEO project to ensure the correct UUID is active. 🚀 Step 2: Add the Pixel to Your Replit Project 1. Open your Replit project in the Replit editor. 2. In the file tree on the left, locate and open your main HTML file — usually named index.html. 3. Paste the pixel snippet you copied from Search Atlas just before the closing </head> tag on every page you want to track. Placing it in the <head> section ensures the pixel loads as early as possible. 4. If your Replit project uses a shared layout or template file that wraps all pages (common in frameworks like Express with EJS, or similar), paste the snippet in that shared layout file instead — this way it loads site-wide automatically. 5. Save the file. ✅ Step 3: Verify the Pixel Is Firing Correctly 1. Click Run in Replit to launch your site. 2. Open your live site URL in a browser. 3. Right-click anywhere on the page and select Inspect (or press F12) to open DevTools. 4. Go to the Network tab and filter by the keyword otto or searchatlas. 5. Reload the page. You should see a successful network request to the Search Atlas pixel endpoint with a 200 status code. 6. Return to your Search Atlas OTTO SEO dashboard. Within a few minutes, the pixel status should update to Installed. If the pixel status does not update within 10–15 minutes, double-check that your snippet is placed correctly inside the <head> tags and that your Replit site is publicly accessible (not set to private). 💡 Common Issues and Fixes - Old Wix data still showing: This is expected immediately after migration. Once the new pixel is active on Replit, Search Atlas will begin collecting fresh data. Historical Wix data will remain visible but new sessions will reflect your Replit site. - Pixel not detected: Confirm your Replit project is deployed to a public URL, not just running locally. Search Atlas needs to reach the live domain to validate the pixel. - Multiple pages not tracked: If your Replit project has multiple HTML pages, ensure the snippet is added to each page's <head>, or use a shared layout/template to inject it globally. - Wrong domain connected: Verify that the domain listed in your Search Atlas OTTO SEO project exactly matches the published Replit domain (including or excluding www). 💬 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.

Edit llms.txt and Merge Atlas Agent Output

Overview This article covers how to locate and edit your llms.txt file when using the Search Atlas WordPress plugin, and how to incorporate Atlas Agent output into that file. Because the specific behavior of your setup may vary, the steps below describe common approaches — if anything does not match what you see, contact our team for guidance tailored to your configuration. Where the llms.txt File Lives When the Search Atlas WordPress plugin is configured to serve llms.txt through your domain, the content may come from a physical file in your WordPress root directory (the same level as wp-config.php) or from plugin-generated output. To check whether the file is being served, visit https://yourdomain.com/llms.txt in a browser after enabling the option in the plugin settings. If you are unsure which source your plugin is using, reach out to our support team before making edits. How to Edit the llms.txt File 1. Connect to your server using an FTP client (such as FileZilla) or your hosting provider's file manager. 2. Navigate to the root directory of your WordPress installation — this is the folder that contains wp-config.php, wp-content, and wp-admin. 3. Check whether a file named llms.txt already exists. - If it exists, open it and edit the content directly. - If it does not exist, create a new plain-text file named llms.txt in that directory. 4. Save the file and reload https://yourdomain.com/llms.txt to verify your changes are live. Important: Use a plain-text editor only (such as Notepad, VS Code, or nano). Do not use a word processor like Microsoft Word, as it may insert hidden formatting characters. Merging Atlas Agent Output into llms.txt The Atlas Agent does not write directly to your llms.txt file. To merge its output, follow these steps: 1. Retrieve the text output you want to include from the Atlas Agent within the Search Atlas platform. 2. Copy that output text. 3. Open your llms.txt file on the server using FTP or your hosting file manager, as described in the section above. 4. Paste the copied content into the file, placing it in a logical position consistent with the formatting and structure already present in the file (for example, appending it after existing entries or inserting it under a relevant section heading). 5. Save the file and verify the updated content appears at https://yourdomain.com/llms.txt. Tips for a clean merge: - Review your existing llms.txt content first so you understand its current structure before adding new content. - Avoid duplicate entries — if the Atlas Agent output overlaps with existing content, consolidate them manually. - 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 GCP Before Submitting URLs for Indexation

🧭 Overview If you see zero URLs processing in the URL Indexer — even after submitting URLs and waiting past the 96-hour window — the most common cause is a missing Google Cloud Project (GCP) connection. The URL Indexer requires an active GCP project with the Indexing API enabled and a valid service account key before any URLs can be submitted for indexation. Without this setup, submissions will not process regardless of how much time has passed. 🔍 How to Check Your Current Setup Before troubleshooting submission status or crawl delays, confirm that your GCP project is properly connected: 1. In the left sidebar, click Authority, then select Indexer (URL Indexer). 2. Look for a GCP connection indicator or a prompt to connect a Google Cloud Project. 3. If no GCP project is shown as connected, follow the steps below to set one up. ⚙️ Step 1 — Create or Select a Google Cloud Project 1. Go to the Google Cloud Console and sign in with your Google account. 2. Click the project selector at the top of the page and choose an existing project, or click New Project to create one. 3. Give your project a recognisable name (for example, SearchAtlas Indexing) and click Create. ⚙️ Step 2 — Enable the Indexing API 1. Inside your GCP project, open the left menu and go to APIs & Services → Library. 2. Search for Web Search Indexing API. 3. Click on the result and then click Enable. 4. Wait for the API to finish enabling before proceeding. ⚙️ Step 3 — Create a Service Account and Download the Key 1. Go to APIs & Services → Credentials. 2. Click Create Credentials and select Service Account. 3. Enter a name for the service account and click Create and Continue. 4. Skip the optional role and user access steps by clicking Done. 5. On the Credentials page, click your new service account, then open the Keys tab. 6. Click Add Key → Create new key, choose JSON, and click Create. The key file will download automatically — keep it safe. ⚙️ Step 4 — Grant the Service Account Access to Google Search Console 1. Open Google Search Console. 2. Select the property that matches the URLs you want to index. 3. Go to Settings → Users and permissions → Add user. 4. Enter the service account's email address (visible on the Credentials page in GCP) and set the permission to Owner. 5. Click Add. 🔗 Step 5 — Connect the GCP Project in Search Atlas 1. In the left sidebar, click Authority, then select Indexer (URL Indexer). 2. Follow the on-screen prompt to connect a Google Cloud Project. 3. Upload the JSON key file you downloaded in Step 3. 4. Once connected, you should see your GCP project listed as active. ✅ Step 6 — Resubmit Your URLs 1. Still in Authority → Indexer (URL Indexer), add the URLs you want to submit. 2. Click Index URLs and confirm the submission. 3. Processing status will update as Google's Indexing API receives and handles the requests. Allow up to 96 hours for status changes to reflect in the dashboard. ⚠️ Why Zero URLs Were Processing Before URLs submitted before a GCP project is connected are not queued — they are not held for later processing. If you submitted URLs on June 5 and no GCP project was connected at the time, those submissions did not go through. You will need to resubmit them after completing the setup steps above. ❓ Frequently Asked Questions - Can I use any GCP account? Yes, any Google account with access to Google Cloud Console can create a project. A free GCP account is sufficient. - Do I need a separate GCP project for each website? No. One GCP project with the Indexing API enabled can cover multiple websites, provided each site is added to Google Search Console and the service account is granted Owner access for each property. - What if the API is enabled but submissions still show zero? Double-check that the service account email has Owner-level access in Search Console, and that the correct JSON key file was uploaded in Search Atlas. 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.

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

🔌 Search Atlas WordPress Plugin Version and Updates

About Search Atlas WordPress Plugin Updates Search Atlas regularly releases updates to its WordPress plugin to deliver new features, performance improvements, and security patches. Keeping your plugin up to date ensures the best experience and access to the latest Search Atlas capabilities. Note: Specific version numbers, release dates, and compatibility requirements change with each release. Always refer to your WordPress admin dashboard for the most current plugin version information — static figures are not published in help articles to avoid outdated guidance reaching you. How to Check Your Current Plugin Version 1. Log in to your WordPress admin dashboard at yoursite.com/wp-admin. 2. Go to Plugins → Installed Plugins in the left navigation menu. 3. Locate Search Atlas in the list. The version number currently installed is displayed beneath the plugin name. 4. If an update is available, WordPress will show an Update now link directly below the plugin entry. How to Update the Plugin We recommend taking a full site backup before applying any plugin update. 1. Back up your site. Use your hosting provider's backup tool or a dedicated backup plugin to create a full backup of your WordPress files and database. 2. Log in to WordPress. Go to your WordPress admin dashboard at yoursite.com/wp-admin. 3. Navigate to Plugins → Installed Plugins. Find the Search Atlas plugin in the list. 4. Apply the update. If an update is available, click Update now. WordPress will download and install the latest version automatically. 5. Verify the update. After the update completes, confirm the new version number is displayed under the plugin name and test your site to ensure everything is working as expected. Compatibility and Requirements Each plugin release specifies minimum WordPress and PHP version requirements. Before updating, check the plugin's detail page in your WordPress dashboard — click the plugin name to open its details — where the compatible WordPress and PHP versions are listed. If your hosting environment does not meet those requirements, update your hosting environment first to avoid activation issues. Finding Release Notes and Changelog The WordPress plugin repository lists version history and release notes for publicly released versions. To view the changelog, visit the Search Atlas plugin page on the WordPress.org plugin directory and click the Changelog tab. Troubleshooting After an Update If the plugin behaves unexpectedly after an update, try the following steps: - Deactivate and reactivate the plugin from Plugins → Installed Plugins. - Clear any site or server-side cache and reload your site. - Confirm your WordPress and PHP versions meet the plugin's stated compatibility requirements. - If the issue persists, restore your pre-update backup to return to a stable state while you investigate. When contacting support, have the following ready: your WordPress version, your PHP version, the Search Atlas plugin version you updated from and the version you updated to, and a description of the unexpected behavior including any error messages shown. 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.

🔌 Installing Search Atlas JavaScript Pixel on Replit

🧭 Overview If you recently migrated your site to Replit and Search Atlas is still showing data from your old platform (such as Wix), the tracking pixel needs to be installed on your new Replit project. This article outlines the general approach for adding the Search Atlas JavaScript snippet to a Replit project so that data is pulled from the correct platform. ⚠️ Why Old Platform Data Still Appears Search Atlas tracks your site using a JavaScript pixel tied to your account. When you migrate to a new platform, the pixel does not automatically follow. Until the snippet is added to your Replit project and your old site is removed or the pixel is inactive there, Search Atlas will continue reading whichever source it last detected. Installing the pixel on Replit and saving your changes resolves this. 🔑 Step 1: Find Your Unique Tracking Snippet 1. Log in to your Search Atlas account. 2. Locate the JavaScript tracking snippet associated with your site within your Search Atlas account. If you are unsure where to find it, contact the Search Atlas support team for guidance on retrieving your snippet. 3. Copy the full JavaScript snippet provided — your unique identifier is already embedded in it. Do not modify any part of it. 🛠️ Step 2: Add the Snippet to Your Replit Project 1. Open your Replit project that hosts your website. 2. Locate the main HTML file for your project. This is most commonly named index.html. If your project uses a JavaScript framework, place the snippet in the appropriate location where global scripts are loaded for every page — consult your framework's documentation for the correct placement. 3. Open the HTML file and find the closing </head> tag. 4. Paste your copied Search Atlas snippet on the line directly above </head>. 5. Save your file and ensure your live site is updated with the latest changes. ✅ Step 3: Verify the Pixel Is Active After saving and deploying, return to your Search Atlas account and check that your Replit site is being detected. It may take a short time for data from the new platform to appear. If your old platform's pixel is still active, deactivate or remove it to ensure Search Atlas reads from your Replit site 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.

⚡ Connect Next.js to Search Atlas Publishing

Overview Search Atlas does not currently offer a native, built-in connector for Next.js. If your site runs on a custom Next.js backend, you can still use Search Atlas to create and optimize your content — but publishing to your Next.js project requires a manual workflow where you export content from Search Atlas and bring it into your own stack yourself. How the Workflow Works Because there is no direct Next.js integration, you will act as the bridge between Search Atlas and your Next.js application. The general approach is: 1. Create and finalize your content inside Search Atlas (blog posts, landing pages, etc.). 2. Copy or export the finished content from Search Atlas. 3. Add that content to your Next.js project through whichever data layer your stack already uses — for example, a headless CMS, a database, or a flat-file system. Search Atlas does not push content directly to Next.js, so the steps between exporting and your site going live depend entirely on your own infrastructure and deployment process. What to Prepare When Reaching Out for Help Because this workflow depends on your specific stack, our support team can help you identify the right approach for your setup. To get the most useful guidance, please have the following ready when you contact us: - A description of your current Next.js data layer (e.g., headless CMS, database, flat files) and how content is currently added to it. - The type of Search Atlas content you are trying to publish (blog posts, landing pages, product pages, etc.). - Any specific error messages or blockers you have encountered while attempting to connect the two systems. - Your Search Atlas project name and the URL of the Next.js site you are trying to publish to. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ Schema Markup Generation, Deployment, and CMS Sync

🔍 Overview Schema markup helps search engines better understand your pages and can improve how your content appears in search results. Search Atlas supports schema markup generation, a deployment workflow to push that markup to your site, and — for Webflow users — CMS sync capabilities to keep your content in sync with the platform. This article explains what is available so you know what to expect and how to get help if something is not working. 📋 Schema Markup Generation Search Atlas includes tools for generating schema markup for your pages, including support for bulk generation across multiple pages at once. If you are not sure where to access the schema generation feature or which schema types are supported for your content, our support team can point you to the right place within your account. When reaching out about schema generation, please have the following ready: - The name of the project you are working in - The URL or URLs you are trying to generate schema for - The schema type you need (e.g. Article, Product, FAQ, LocalBusiness) if known - A description of what you are seeing — including any error messages and the exact time the issue occurred 🔎 Schema Deployment Workflow Once schema markup has been generated, Search Atlas provides a workflow for deploying it to your connected site. If you are experiencing issues with the deployment process — such as schema not appearing to deploy correctly or the workflow behaving unexpectedly — please contact support so the team can review your specific setup. When reaching out about deployment, please have the following ready: - The project name and the page URL(s) affected - A description of the behavior you are seeing and when it started - Any error messages shown, with timestamps if possible 🔗 Webflow CMS Sync For users on Webflow, Search Atlas offers CMS sync capabilities that connect your Webflow CMS with the platform. If you need help setting up or troubleshooting the Webflow CMS sync integration, our support team can walk you through the process based on your account configuration. When reaching out about Webflow CMS sync, please have the following ready: - Your Webflow site URL and the project name in Search Atlas - A description of what is not working as expected - Any error messages and the time they 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 Tool and Feature Capability Map

🔍 What This Article Covers Customers often ask whether Search Atlas can handle a specific set of SEO tasks before committing to a workflow. The short answer is yes — Search Atlas includes tools that cover featured snippets, AI Overviews, competitor traffic analysis, keyword research and conversion tracking, and backlink discovery. This article maps each capability to the exact tool that handles it. 📊 Featured Snippets and AI Overviews Tracking whether your pages appear in featured snippets or Google's AI Overviews is handled by the Rank Tracker. - Navigate to Left sidebar → Keywords → Rank Tracker. - Add your target keywords and enable SERP feature tracking. - The Rank Tracker surfaces which keywords trigger featured snippets or AI Overview placements and whether your URLs are currently occupying those positions. - Use this data to identify quick-win optimisation opportunities for structured content and concise answer formatting. 🏆 Competitor Traffic Analysis Understanding how much organic traffic your competitors receive — and which pages drive it — is handled by Site Explorer. - Navigate to Left sidebar → Site Metrics (Site Explorer) (URL: /site-explorer/list). - Enter any competitor domain in the search bar. - The dashboard returns estimated organic traffic, top-performing pages, traffic trends over time, and the keywords driving those visits. - Use the Keyword Gap tool (Left sidebar → Keywords → Keyword Gap) to directly compare your keyword portfolio against one or more competitors and surface ranking opportunities you are currently missing. 🔑 Keyword Research and Conversion Mapping Finding keywords and understanding their commercial value is handled by Keyword Magic. - Navigate to Left sidebar → Keywords → Keyword Magic. - Enter a seed keyword to generate thousands of related keyword ideas with volume, difficulty, CPC, and intent data. - Filter by intent (informational, navigational, commercial, transactional) to isolate keywords most likely to convert. - CPC data acts as a conversion-value proxy — keywords with higher CPC typically indicate stronger buyer intent. - Export filtered lists directly into your Rank Tracker project to monitor performance over time. 🔗 Backlink Discovery Finding backlink opportunities — including your own link profile and competitors' inbound links — is handled by Site Explorer. - Navigate to Left sidebar → Site Metrics (Site Explorer) (URL: /site-explorer/list). - Enter your own domain or a competitor domain. - Select the Backlinks tab to view all inbound links, referring domains, anchor text distribution, and domain authority scores. - Analyse competitor backlinks to identify publishers, directories, or partners you could approach for your own link-building outreach. 🗂️ Quick Reference: Capability-to-Tool Map - Featured snippets tracking: Left sidebar → Keywords → Rank Tracker - AI Overviews tracking: Left sidebar → Keywords → Rank Tracker - Competitor traffic analysis: Left sidebar → Site Metrics (Site Explorer) - Keyword gap analysis: Left sidebar → Keywords → Keyword Gap - Keyword research and intent filtering: Left sidebar → Keywords → Keyword Magic - Keyword conversion value (CPC): Left sidebar → Keywords → Keyword Magic - Backlink discovery (your site): Left sidebar → Site Metrics (Site Explorer) - Backlink discovery (competitor sites): Left sidebar → Site Metrics (Site Explorer) 💡 Tips for Getting the Most Out of These Tools - Start with Keyword Magic to build your target keyword list, then push those keywords directly into Rank Tracker to monitor positions and SERP features together. - Run a Keyword Gap analysis against your top two or three competitors monthly to stay ahead of emerging ranking opportunities. - When prospecting for backlinks, filter competitor link profiles by Domain Rating and traffic to prioritise outreach to the highest-value referring domains first. - Combine competitor traffic data from Site Explorer with featured snippet data from Rank Tracker to identify high-traffic queries where a snippet win could deliver outsized results. 🛠️ 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.

🔌 Set Up Bing Indexing via WordPress Plugin

What Is Bing Indexing in OTTO? OTTO's Bing indexing feature uses the Bing URL Submission API to notify Bing when you publish or update content on your WordPress site, helping your content get indexed faster. This feature requires the Search Atlas WordPress plugin to be installed and connected to your Search Atlas account. Before You Begin - Your WordPress site must have the Search Atlas plugin installed and activated. - The plugin must be authenticated and connected to your Search Atlas account. - You must have an active OTTO session deployed on the target site. - Your Search Atlas plan must include OTTO access. Setting Up Bing Indexing 1. Open your OTTO session in Search Atlas and navigate to the site where the Search Atlas WordPress plugin is installed and connected. 2. Locate the Bing Indexing setting within OTTO's configuration options for your site. 3. Enter your Bing URL Submission API key. You can obtain this key from your Bing Webmaster Tools account (bing.com/webmasters). Log in to Bing Webmaster Tools and locate your API key to generate or copy it. 4. Save and enable the Bing indexing feature. Once your API key is entered and saved, OTTO will automatically submit new and updated URLs from your WordPress site to Bing via the Submission API. 5. Verify the connection is active by publishing or updating a page on your WordPress site and confirming that URL submissions are being processed through OTTO. Troubleshooting - If Bing indexing is not working, confirm your Search Atlas plugin is fully authenticated and that your OTTO session is active and deployed on the correct site. - Double-check that the Bing URL Submission API key entered in OTTO matches the key in your Bing Webmaster Tools account. - Ensure your WordPress site URL in Search Atlas matches the property verified in Bing Webmaster Tools. If you continue to experience issues, our support team is happy to help — click the chat icon in your Search Atlas dashboard to reach us.

🔌 OTTO Cache Plugin Third-Party Compatibility Guide

🧩 Overview The OTTO cache plugin installs a header script on your site to enable AI-driven SEO automation. If your site already uses a third-party caching system — such as BionicSpeed — the two layers can sometimes conflict, causing slower load times, stale pages, or script delivery issues. This article explains how those conflicts occur and walks you through a structured self-diagnosis process. ⚙️ How the OTTO Cache Plugin Works When you activate OTTO on a site, Search Atlas injects a lightweight header script into your site's HTML. This script communicates with OTTO's automation engine to apply on-page SEO changes in real time. Because the script lives in the <head> of each page, it must load before most other page elements — including cached versions served by third-party systems. If a third-party cache (like BionicSpeed) serves a fully pre-built HTML snapshot, the OTTO header script may be excluded, delayed, or duplicated, depending on how that cache layer captures and replays pages. ⚠️ Common Conflict Symptoms - OTTO changes are not appearing on the live site even after activation. - Page speed scores have dropped noticeably since installing the OTTO plugin. - The OTTO header script appears more than once in your page source. - BionicSpeed reports cache misses or unusually high bypass rates. - Your site's HTML source shows an outdated version of the OTTO script tag. 🔍 How to Test for a Cache Conflict Yourself Follow these steps in order. Each step isolates a specific part of the problem so you can pinpoint the cause quickly. 1. Check your live page source. Open your site in a browser, right-click anywhere on the page, and select View Page Source. Search for the OTTO script tag (it will reference Search Atlas or OTTO). Confirm it appears exactly once, inside the <head> tag, near the top. 2. Compare cached vs. uncached output. Load your page normally, then reload it with cache bypassed by appending a unique query string to the URL — for example, ?nocache=1. If the content or script differs between the two versions, BionicSpeed is serving a snapshot that does not include the current OTTO script. 3. Check response headers for cache status. Open your browser's Developer Tools (F12), go to the Network tab, reload the page, and click on the main HTML document. Look at the response headers for values like X-Cache: HIT or X-BionicSpeed-Cache: cached. A HIT means BionicSpeed served a stored copy — the OTTO script may not have been present when that copy was captured. 4. Temporarily disable BionicSpeed caching. Pause or disable BionicSpeed on one test page, then reload that page and check the source again. If the OTTO script now appears correctly and your SEO changes are visible, this confirms a cache layer conflict. 5. Test site speed before and after. Use a tool such as Google PageSpeed Insights to run a speed test with BionicSpeed active, then run the same test with it paused. A significant speed difference on the same page points to an integration issue rather than an OTTO script problem on its own. 🛠️ Recommended Fixes Once you have confirmed a conflict exists, use the following approaches to resolve it. - Exclude the OTTO script from BionicSpeed's cache capture. In your BionicSpeed settings, add the OTTO script URL or its containing tag pattern to the exclusion or bypass list. This tells BionicSpeed not to cache that element, so OTTO always delivers a fresh version. - Set cache rules to exclude OTTO-activated pages. If OTTO is active on specific URLs, configure BionicSpeed to bypass caching entirely for those URLs. This guarantees OTTO's real-time changes are always served to visitors. - Adjust cache expiry times. If full exclusion is not possible, reduce the cache TTL (time to live) for pages where OTTO is active. A shorter TTL means BionicSpeed refreshes its snapshot more frequently, reducing the window where an outdated OTTO script is served. - Reinstall the OTTO header script. Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3), locate the affected site, and verify the plugin installation status. If the script shows as inactive or errored, deactivate and reactivate OTTO for that site to force a fresh script injection. ✅ How to Confirm the Conflict Is Resolved 1. Re-enable BionicSpeed after applying your chosen fix. 2. Clear all BionicSpeed cached pages so fresh snapshots are captured. 3. View the page source again and confirm the OTTO script appears once, in the correct position, with no duplication. 4. Run a PageSpeed Insights test and compare results to your pre-fix baseline. 5. Verify that any OTTO SEO changes you previously activated are now visible on the live site. 📋 Important Notes - The steps above apply to BionicSpeed but follow the same logic for other third-party caching systems (WP Rocket, LiteSpeed Cache, Cloudflare, etc.). Look for cache exclusion or bypass settings in each tool. - Do not install the OTTO plugin and a conflicting caching plugin at the same network or server level without configuring proper exclusions — both systems will attempt to control how HTML is delivered to browsers. - If you update your BionicSpeed configuration, always purge the cache afterwards so stale snapshots do not persist. 💬 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.

⚡ GSC Instant Indexing, Knowledge Base & Bulk Deployment Guide

Overview After upgrading your plan, you unlock several powerful features, including GSC Instant Indexing, Knowledge Base Trust with Factual Enhancement, and bulk deployment to your live site. Dynamic Indexing is also available to any account with OTTO. This article explains what each feature does and how to get started. Because exact quota limits, reset schedules, and specific configuration options can vary by account, this article explains where to find these tools and what to have ready when you contact support if you need account-specific details confirmed. GSC Instant Indexing — Quota and Usage GSC Instant Indexing lets you submit URLs directly to Google Search Console for faster crawling and indexing. The exact monthly quota and reset schedule for your account depend on your specific plan configuration and billing cycle — these figures are not the same for every account. To check your quota and submit URLs: 1. Log in to Search Atlas and open the GSC Instant Indexing section of the platform. 2. Your current usage and remaining quota are displayed within that section — review them there before submitting. 3. Select the URLs you want to submit and follow the on-screen prompts. If your quota usage looks incorrect, submissions are not processing, or you need your exact quota limit and reset date confirmed, have the following ready before contacting support: your account name, the URLs you attempted to submit, any error messages displayed, and the approximate date and time of the issue. Knowledge Base Trust — AI Generation and Factual Enhancement Knowledge Base Trust allows the platform's AI to generate and enhance content. Factual Enhancement is a capability within this workflow that influences how the AI aligns its output with sources you have added to your Knowledge Base. To get started with Knowledge Base Trust: 1. Navigate to OTTO SEO → Knowledge Base. 2. Add your trusted knowledge sources using the options available in that section. 3. When generating content, follow the on-screen options available in that workflow to enable Factual Enhancement so the AI references your added sources. 4. Review all generated content in the review area before approving or publishing it. If you cannot locate the Factual Enhancement options, the review area, or your added sources are not appearing as expected, contact support with your account name and a description of what you see on screen. Bulk Deployment and Dynamic Indexing Bulk deployment is an additional Growth plan tool accessible within the Search Atlas platform. Dynamic Indexing is available to any account with OTTO, subject to the OTTO project being set up (and any connected indexing services). Because the exact steps to initiate these features depend on how your site connector and content projects are configured, the specific workflow will vary by account. When contacting support about bulk deployment or Dynamic Indexing, have the following ready: your account name, the name of the relevant content project or site connector, a description of the action you are trying to take, and any error messages or unexpected behavior you have observed. 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 Pixel Privacy, History, and Webflow Integration

Overview OTTO SEO automates on-page optimizations through a lightweight pixel and a no-code deployment system. This article covers the three most common questions customers ask about the OTTO pixel: what data it collects, how to review past deployments, and how OTTO behaves on Webflow sites. Note: The specific UI labels and panel names within OTTO may vary depending on your account version. If you cannot locate a section described below, reach out to our support team for the exact location in your account. What Data Does the OTTO Pixel Collect? The OTTO pixel is a small JavaScript snippet added to your website that allows OTTO to read page structure and apply SEO changes. Questions about exactly what data the pixel collects and how it is handled are best directed to our support team, who can provide details specific to your account and compliance requirements. If you have specific compliance questions about data handling, contact our support team for details relevant to your use case. How to View Previously Deployed Changes OTTO maintains a record of changes deployed to your site. To find this history, navigate to OTTO SEO → All Sites (SEO Automation) → your project → Deployment History. From there you should be able to see which pages were affected and when changes were made. If you need to undo a specific optimization, look for a toggle or option adjacent to the individual change entry. If you are unable to locate the deployment history within your project view, our support team can walk you through the exact steps for your account. OTTO and Webflow: What to Expect OTTO works with Webflow sites by injecting changes through the pixel. If you are seeing unexpected behavior or have questions about how OTTO interacts with your specific Webflow setup, our support team can review your project and advise on next steps. 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 Pixel Compatibility With Car Dealer Platforms

🔍 What Is the Search Atlas Pixel? The Search Atlas pixel is a small snippet of JavaScript code you place on your website. It tracks visitor behaviour, measures campaign performance, and helps Search Atlas deliver accurate SEO and analytics data. For the pixel to work, your website platform must allow you to add custom JavaScript to your site's pages. 🚗 Do Car Dealer Platforms Support Custom Pixels? Car dealer website platforms vary widely in how much control they give you over your site's code. Compatibility depends entirely on whether your specific platform allows third-party JavaScript snippets. Here is a general breakdown: - Compatible platforms: Platforms that let you insert custom HTML or JavaScript into the <head> or <body> of your pages will work with the Search Atlas pixel without any issues. - Partially compatible platforms: Some platforms restrict where scripts can be placed or require approval before adding third-party code. In these cases the pixel may still work, but you may need to work with your platform provider to get it installed. - Incompatible platforms: Fully closed or proprietary dealer platforms that block all custom code additions will not support the Search Atlas pixel. The most reliable way to find out is to contact your car dealer platform's support team directly and ask: "Can I add a custom third-party JavaScript pixel to my website pages?" ✅ How to Check Compatibility Before Installing 1. Log in to your car dealer website platform's admin panel. 2. Look for a section labelled Custom Code, Header Scripts, Tracking Codes, or Integrations. 3. If you find one of these sections, your platform is likely compatible. You will be able to paste the Search Atlas pixel code there. 4. If you cannot find such a section, reach out to your platform provider and ask whether they support custom JavaScript snippets or third-party tracking pixels. 🛠️ How to Install the Search Atlas Pixel on Your Website 1. In Search Atlas, navigate to Website Studio using the left sidebar (or go to /website-studio). 2. Locate the pixel or tracking code section within Website Studio and copy your unique Search Atlas pixel snippet. 3. Log in to your car dealer website platform. 4. Paste the pixel snippet into the custom code or header scripts area of your platform. 5. Save your changes and publish or update your site. 6. Return to Search Atlas and verify that the pixel is firing correctly using the built-in verification tool. ⚠️ Common Issues and How to Resolve Them - Platform requires approval for third-party scripts: Submit a request to your platform provider with the Search Atlas pixel code and explain it is an analytics tracking script. Most providers approve standard JavaScript pixels. - Pixel is installed but not detecting traffic: Confirm the snippet was placed inside the <head> tag and that it appears on all pages, not just the homepage. Clear your browser cache and test again. - Platform uses a tag manager (e.g. Google Tag Manager): If your dealer platform supports Google Tag Manager, you can deploy the Search Atlas pixel as a Custom HTML tag inside GTM instead of editing the site code directly. - Platform does not allow any custom code: Unfortunately, Search Atlas cannot override platform-level restrictions. In this situation, consider asking your platform provider about upgrading to a plan that includes custom code access, or discuss migrating to a more flexible website solution. 💡 Using Search Atlas Website Studio as an Alternative If your current car dealer platform is too restrictive, Search Atlas Website Studio (left sidebar → Website Studio) offers a fully flexible website builder where the Search Atlas pixel works natively with no setup required. This eliminates compatibility concerns entirely and gives you full control over your site's code and performance. 🙋 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. Additional Notes DealerSocket/CDK/Tekion, DealerInspire, Dealer.com (Cox Automotive), Sincro, Gubagoo/Widewail widgets (pixel goes on underlying site, not widget), WordPress dealer sites — named platform-specific instructions not present in keeper.

🔍 Using Search Atlas With Third-Party Managed Websites

🌐 Overview If your website is managed by an external marketing company or agency, you may wonder whether using Search Atlas could interfere with their work or trigger automatic changes to your site. This article explains exactly how Search Atlas interacts with third-party managed websites so you can use the platform with confidence. 📊 Does Search Atlas Automatically Change My Website? No. Search Atlas is a read-and-recommend platform by default. Simply connecting your website or running reports does not automatically publish, edit, or delete any content on your site. You remain in full control of what changes — if any — are applied. The only exception is OTTO SEO, Search Atlas's automated on-page optimisation feature. OTTO SEO can deploy changes directly to your website, but only when you explicitly activate it and approve the relevant actions. No changes are pushed without your deliberate input. 🛠️ What You Can Do Safely on a Managed Website The following Search Atlas tools are completely safe to use alongside any third-party managed website. They gather and analyse data only — nothing is written back to your site: - Site Explorer — Analyse your domain's authority, backlink profile, and organic traffic data. Navigate via Left sidebar → Site Metrics (Site Explorer). - Keyword Magic — Research keyword opportunities without touching your site. Navigate via Left sidebar → Keywords → Keyword Magic. - Rank Tracker — Monitor your keyword rankings over time. Navigate via Left sidebar → Keywords → Rank Tracker. - Keyword Gap — Compare your keyword coverage against competitors. Navigate via Left sidebar → Keywords → Keyword Gap. - GBP Projects tools — Manage Google Business Profile content, reviews, posts, and citations. Navigate via Left sidebar → GBP Projects and its sub-pages. Using any of these tools will not conflict with your marketing agency's ongoing work on your website. ⚙️ If You Use OTTO SEO on a Managed Website If you want to take advantage of OTTO SEO's automated optimisations on a website managed by a third party, we recommend the following steps before activating it: 1. Notify your marketing company — Let them know you are enabling automated on-page SEO changes so they can coordinate their own work accordingly. 2. Review OTTO SEO recommendations before deploying — OTTO SEO presents suggested changes for your approval. Take time to review each recommendation to ensure it aligns with your agency's existing content strategy. 3. Establish a change log process — Ask your agency to share a record of recent edits so that OTTO SEO deployments do not overwrite or conflict with their updates. 4. Start with a limited scope — Consider activating OTTO SEO on a small section of the site first to confirm compatibility before rolling it out site-wide. 💡 Best Practices for Agency-Managed Sites - Share Search Atlas reports and insights directly with your marketing company — the data can inform their strategy without requiring any platform access. - If your agency also needs access to Search Atlas, you can invite them as a user under your account so everyone works from the same data set. - Always confirm with your agency before enabling any feature that writes data to your website, including OTTO SEO or Local posting tools that publish content to your Google Business Profile. 🆘 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Search Atlas Global Availability, White-Label, and GHL Integration

Who Can Use Search Atlas? Search Atlas is available to agencies and individual users worldwide, including clients based in the United Kingdom, the European Union, North America, Australia, and other regions. There are no geographic restrictions that prevent you from creating an account, onboarding clients, or accessing core platform features regardless of where you or your clients are located. All Search Atlas plans support international projects. You can track rankings, audit sites, and manage content for domains targeting any country or language. UK and EU Client Support If you work with UK-based or EU-based clients, Search Atlas fully supports your workflow. Here is how to get started: 1. Log in to your Search Atlas account and navigate to Projects. 2. Create a new project and enter your client's domain. 3. When prompted to select a target location and search engine, choose the relevant UK or EU country (for example, United Kingdom – Google.co.uk or a specific EU country). 4. Set the target language to match your client's locale (for example, English – UK, French, German). 5. Save the project — rank tracking, site audits, and content tools will now operate within that regional context. This confirms that UK and EU client projects are fully supported on all plans. No additional eligibility steps are required. White-Label Capabilities Search Atlas offers white-label functionality that lets you present reports and deliverables under your own agency brand. White-label is available on eligible agency plans. To confirm whether white-label is included on your current plan or to enquire about enabling it, please reach out to the Search Atlas support team who can advise on your options. White-label reports can be shared directly with clients as branded deliverables, depending on your plan tier. GoHighLevel (GHL) Integration Search Atlas can be used alongside GoHighLevel (GHL) as part of your agency stack. A typical setup looks like this: 1. Use Search Atlas to run SEO audits, keyword research, and content creation for your clients. 2. Export reports or deliverables from Search Atlas (for example, as PDFs or data exports). 3. Import or embed those outputs into your GHL environment — for example, attaching reports to GHL contacts, opportunities, or campaigns. 4. Use GHL for client communication, CRM, and funnel management while Search Atlas handles the SEO and content side of your workflow. This complementary setup is fully supported. If you have questions about configuring Search Atlas within your GHL workflow, the support team can help. Need More Help? If you have questions about regional availability, white-label setup, or GHL integration that are not covered here, please contact the Search Atlas support team via the chat widget in your account and we will be happy to assist.

🔌 Add Meta Tags to WordPress Posts via Search Atlas

Overview Search Atlas can integrate directly with your WordPress site to help you manage meta titles and meta descriptions for your posts. This article explains the general workflow for using this integration and what to have ready if you need additional help. Before You Start Make sure the following are in place before following the steps below: - Your WordPress site is connected to Search Atlas. If it is not connected yet, click the top-right avatar → Settings → Integrations / CMS Connectors and use the WordPress integration option to connect your site. - You have at least Editor-level access to the WordPress site in question. - The post you want to update already exists in WordPress, or you are ready to create a new one. How to Add Meta Tags to WordPress Posts Once your WordPress site is connected to Search Atlas, you can manage meta titles and meta descriptions for your posts directly from within the platform. The general workflow is as follows: 1. Open the relevant tool in Search Atlas where you manage your content — such as the On-Page Audit or SEO Content Assistant — and locate the post you want to update. 2. Find the meta title and meta description fields for that post. These fields allow you to enter or edit the SEO metadata that will be applied to your WordPress post. 3. Enter your desired meta title and meta description values in the provided fields. 4. Use the available option to push or save those meta tag values to your connected WordPress site. This will update the meta title and meta description on the WordPress post without requiring a separate plugin. After pushing the changes, visit your WordPress post and verify that the meta title and meta description have been updated as expected. If the fields do not appear or the push does not work, confirm that your WordPress connection is active under the top-right avatar → Settings → Integrations / CMS Connectors. What to Have Ready When You Contact Support If the steps above do not resolve your issue, please have the following information on hand when reaching out: - The URL of your WordPress site or the specific post you want to update. - Whether your WordPress site is currently showing as connected inside Search Atlas. - A description of what you are trying to do — for example, setting a meta title, setting a meta description, or both. - Any error messages you have seen, with the exact text of the message and the time it occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Integrating Next.js Static Sites into Search Atlas

🧭 Overview Search Atlas connects to your website primarily through your public URL, which means static sites built with Next.js are generally supported — whether you use Static Site Generation (SSG), Incremental Static Regeneration (ISR), or a fully exported static build via next export. No server-side rendering is required for integration. This article covers two aspects of the original topic: connecting your Next.js site to Search Atlas and compliance certification questions that may arise during or after that process. ✅ Before You Begin Make sure the following are in place before connecting your Next.js site: - Your site is deployed and publicly accessible via a live domain (e.g., https://yoursite.com). - You have admin or owner access to your Search Atlas workspace. - You have access to your site's codebase or hosting platform if any verification steps are required. 🚀 Step 1 — Add Your Site to Search Atlas Log in to your Search Atlas account and locate the option to add a new site within your workspace. Enter your full domain URL (include https://) and proceed through the prompts shown in the platform. 🔍 Step 2 — Verify Site Ownership Search Atlas will present you with a verification method during the site setup flow. Follow the on-screen instructions provided at that step to confirm ownership of your domain. The exact verification options available to you will be displayed within the platform during setup. For Next.js sites, a common approach is to place any required verification code inside your project's <head> section — for example in pages/_document.js (Pages Router) or your root layout.tsx (App Router) — and then redeploy your site before confirming in Search Atlas. 🗺️ Step 3 — Submit Your Sitemap Next.js does not generate a sitemap automatically in all configurations. Once your site is added, submit your sitemap so Search Atlas can crawl your full page inventory: 1. Confirm your sitemap is publicly accessible (e.g., at https://yoursite.com/sitemap.xml). If you do not yet have one, the next-sitemap package is a common solution for Next.js projects. 2. In Search Atlas, locate the sitemap submission option within your site's settings in the platform. 3. Enter your sitemap URL and submit it. 📋 Compliance Certifications If your question involves compliance certifications (for example, questions about whether Search Atlas holds SOC 2, GDPR, or similar certifications, or whether your site's integration meets certain compliance requirements), this is handled on a case-by-case basis by the Search Atlas team. There are no self-serve compliance certificate downloads available in the platform at this time. When escalating a compliance certification question, please have the following ready: - The specific certification or compliance standard you are asking about (e.g., SOC 2 Type II, GDPR, ISO 27001). - Your company name and Search Atlas workspace details. - Any deadline or legal context that applies to your request. 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 Manage Google Search Console & GA4 Sites in Search Atlas

The GSC Sites List (/gsc/sites-list) lets you activate projects, assign tracking locations, and confirm GA4 connections — all from one screen in Search Atlas. Available actions include Manage Sites, Connect GSC Account, Connect GA Account, and Show Inactive. 🧭 Navigation Path Search Atlas → Left Sidebar → Site Metrics → GSC Performance → All Sites → GSC Sites List ⚙️ Manage GSC Sites Open the GSC Sites List from the left sidebar: 1. Go to Site Metrics in the left sidebar. 2. Click GSC Performance. 3. Select All Sites. 4. On the GSC Sites List screen, click Manage Sites. The Manage Sites panel opens. 📍 Choose Projects & Locations 1. Under Choose the projects you want to manage, select the site you want to activate. 2. Under Location, select the country you want to track (example: United Kingdom). 3. Toggle Status to Active. 4. Click Confirm and continue. Note: Activation and deactivation quota points are deducted only after confirmation. 📊 Verify GSC Status 1. Return to GSC Sites List. Each active site now shows the following metrics (data reflects the last 28 days by default): - Total Traffic - Avg. Position - Impressions - Organic Traffic - Active Locations A confirmation message appears: "GSC sites updated successfully, now refreshing data please wait…" 🔄 Bulk Refresh GSC Sites (Coming Soon) Status: This capability is currently rolling out. If you don't yet see the option in your account, check back shortly. The updated GSC connection flow includes a bulk refresh capability that triggers and monitors a refresh across all GSC-authorized accounts simultaneously — without updating each site individually. Trigger a Bulk Refresh 1. Open the GSC Sites List screen. 2. Click Refresh All Sites in the top-right corner. 3. Confirm the action when prompted. The refresh starts immediately across every connected GSC account. Monitor Refresh Progress The bulk refresh runs asynchronously — you can keep working while it completes. - A live progress indicator appears next to the Refresh All Sites button, showing current refresh status for each connected account. - Each site row updates as its data finishes syncing. - When complete, a success message appears: "All GSC sites refreshed successfully." If any account fails, a failure notice identifies which sites need attention. 📈 Connect Google Analytics 4 (GA4) 1. On GSC Sites List, click Connect GA Account. 2. In Google Analytics 4 Settings, confirm the message: "GA4 is connected". 3. Select the correct Property from the dropdown. 4. Click Update Settings. Note: If the project details page previously showed GA4 as not connected after a successful update, this issue has been resolved. Re-open the GSC connections panel to confirm your GA4 property now appears as connected. ⏱️ Data Availability After confirming GSC and GA4 settings: - Data may take 20–30 minutes to fully load. - Metrics may temporarily appear empty while syncing. ❓ Frequently Asked Questions Why is my GA4 connected but not showing in a project? GA4 must be confirmed at the project level inside GSC Sites List, even if it is already connected at the account level. Do I need to repeat this for every project? Yes. Each project must be activated and configured individually. Can I manage multiple sites at once? Yes. You can activate multiple sites and assign locations before clicking Confirm and continue. 🎯 You can now activate GSC projects, assign tracking locations, and connect GA4 from the GSC Sites List, with bulk refresh rolling out soon. For deeper analysis of your synced data, explore Site Metrics and GSC Performance in Search Atlas.

📝 Publish Blog Posts Directly to WordPress

🔍 Overview If your client's WordPress site shows Connected in Brand Vaults and in OTTO, but you still cannot publish or post a blog directly to WordPress from the Content tab, you are not experiencing a broken connection. You are missing one additional step: syncing WordPress inside the Content tab itself. The Brand Vaults and OTTO connections serve their own purposes and do not automatically activate the WordPress publishing integration inside the Content tab. A separate sync must be completed there before direct publishing becomes available. ⚠️ When Does This Happen? - You open a blog post or AI-generated article in the Content tab and the option to publish directly to WordPress is missing or greyed out. - WordPress shows Connected in Brand Vaults and in OTTO, but the Content tab does not recognise the site. - Attempting to post results in an error even though all other connections appear healthy. 🔗 How the WordPress Connections Work Search Atlas uses three distinct integration points for WordPress, and each one operates independently: - Brand Vaults: Stores your client's WordPress credentials and site details for use across the platform. - OTTO: Uses the WordPress connection to deploy SEO optimisations, meta updates, and schema directly to the site. - Content tab: Uses its own sync to enable direct blog publishing. This sync must be completed separately, even when the other two connections are already active. Think of it as three doors into the same house — unlocking one does not unlock the others. ✅ How to Sync WordPress in the Content Tab 1. In the left sidebar, click Content to expand the section. 2. Select any content tool, for example Content Genius or open an existing blog post in the Content Planner. 3. Once a document is open in the editor, look for the Publish or Integrations option, typically found in the top-right area of the editor toolbar. 4. Click Connect WordPress or Sync WordPress Site when prompted. 5. Select the client's WordPress site from the list. If the site was already added in Brand Vaults, it should appear here automatically. 6. Confirm the sync. The status will update to show the site is now linked to the Content tab. 7. You can now use the Publish to WordPress option to post blog content directly to the client's site. Note: You may need to complete this sync step once per client workspace or brand. After the initial sync, the connection persists for future publishing sessions. 🛠️ Troubleshooting If the WordPress site does not appear in the sync list inside the Content tab, check the following: - Confirm the site credentials are saved correctly in Brand Vaults under the correct client profile. - Make sure you are working inside the correct client workspace before attempting the sync. - Verify that the WordPress site's REST API is enabled, as Search Atlas requires it to communicate with your site. - Check that the WordPress user account used for the connection has at least Editor or Administrator permissions. If the site appears in the list but the sync fails, disconnect the site and reconnect it by re-entering the credentials in Brand Vaults, then repeat the sync steps above. 💬 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.

🛠️ MCP Tools vs Slash Commands in Claude Code: Why You See Fewer Commands

Overview If you are using MCP (Model Context Protocol) access with Claude Code and notice that the number of visible slash commands is lower than the total number of capabilities you expected, you are not missing features — you are looking at two different systems. This article explains the difference between MCP tool invocation and slash commands in Claude Code. MCP Tools vs Slash Commands: The Key Difference Many customers assume that every capability should appear as a slash command. In reality, Claude Code exposes functionality through two distinct mechanisms: - Slash commands are shortcuts you type manually in the Claude Code client. These are a curated set of commands surfaced directly in the interface. - MCP tools are invoked automatically by the agent when it determines a task requires them. They do not appear in your slash command list, but they are still active and available in the background. This is why the number of visible slash commands may appear much lower than the total number of MCP tools available. The MCP tools operate in the background and are not surfaced as typed commands in the menu. Why You May See Fewer Commands There are a few common reasons the visible command count may differ from what you expected: - MCP tools are auto-invoked, not listed: A significant portion of available capabilities are MCP tools that the agent calls automatically based on the task at hand. These will not appear in the slash command menu. - Slash commands are a separate, curated set: The slash commands visible in your client represent a distinct subset of functionality, not the full list of everything the agent can do via MCP tools. Still Have Questions? If you are unsure whether your MCP setup is working as expected or have additional questions about how tools and commands are configured for your account, use the chat icon in the bottom-right corner of the platform and type human teammate to be connected with a member of our team and we will be happy to help. Additional Notes Candidate specifies ~20 slash commands is expected/correct, names examples (/help, /clear, /cost), mentions 60+ MCP tools, and gives step-by-step usage: describe task in plain English, e.g. 'Run a technical site audit for example.com'; Claude auto-selects the tool; tool-call notification appears in thread.

🔧 Install OTTO Pixel on GoDaddy Website Builder

🧭 Overview GoDaddy Website Builder (also called GoDaddy Websites + Marketing) does not allow you to paste code directly into the <head> section of your site. This is a platform limitation — not an issue with your OTTO pixel. This article walks you through the correct workaround so the pixel installs and verifies successfully. ⚠️ Before You Start - Make sure OTTO is activated for your project inside Search Atlas. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3) and confirm your site is connected. - Copy your unique OTTO pixel code from the OTTO dashboard. You will need it in the steps below. - Note: GoDaddy Website Builder is different from a WordPress site hosted on GoDaddy. If you have WordPress, you can paste the pixel into the <head> directly or use a plugin. 🛠️ Method 1 — Use GoDaddy's Built-In Tracking Code Field GoDaddy Website Builder has a dedicated field for third-party tracking codes. This is the recommended path for OTTO pixel installation. 1. Log in to your GoDaddy account and open your Website Builder editor. 2. In the editor, click Settings (the gear icon, usually in the top navigation bar). 3. Select Website Settings, then choose the GoDaddy Insight / Analytics or Tracking Codes tab. The exact label may vary depending on your GoDaddy plan. 4. Paste your full OTTO pixel code into the tracking code field. 5. Click Save, then Publish your site to push the changes live. Once published, GoDaddy injects this code into the <head> automatically on every page. You do not need to add it page by page. 🛠️ Method 2 — Use a GoDaddy HTML Section Block If your GoDaddy plan does not include a tracking code field, you can use an HTML section block as an alternative. This places the pixel in the page body rather than the head, which is still functional for OTTO tracking. 1. Open your Website Builder editor and navigate to the page you want to track. 2. Click Add Section and search for an HTML block or Custom Code block. 3. Drag the block to the very top of the page, above all other content. 4. Paste your OTTO pixel code inside the HTML block. 5. Repeat for any additional pages you want to track, or check if your theme supports a global footer/header section where you can add it once. 6. Click Save and Publish. Important: Placing the pixel in the page body instead of the <head> may cause a short delay in tracking page events. OTTO will still receive data, but the pixel fires slightly later in the page load sequence. This is expected behaviour for this method. ✅ How to Verify the Pixel Is Working 1. After publishing, wait 10–15 minutes before checking pixel status. 2. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open your site's OTTO dashboard. 3. Look for a green Pixel Active indicator. If it shows as pending, wait up to 24 hours — GoDaddy's CDN can take time to fully propagate published changes. 4. Visit your live website in a browser, then return to OTTO and refresh the dashboard. An active pixel will register your visit as a confirmed signal. Do not run browser-based head-section diagnostics on a GoDaddy Website Builder site. Because GoDaddy manages the code injection on their servers, standard inspect-element checks may not show the pixel in the expected location. The OTTO dashboard confirmation is the reliable verification method. ⏱️ GTag and Data Population Timeline If OTTO is also collecting Google Tag (GTag) data alongside the pixel, keep these timelines in mind: - Pixel confirmation: 10 minutes to 24 hours after publishing. - First GTag data in Reports: Allow 48–72 hours after pixel activation. Go to Reports in the left sidebar (or /report-builder/projects-list) to view incoming data once it populates. - If no data appears after 72 hours, revisit the steps above and confirm your site was published — saving in the editor alone is not enough. ❓ Common Issues - I don't see a Tracking Codes tab in Settings. This field is available on most GoDaddy Websites + Marketing paid plans. If you are on a free or legacy plan, use Method 2 (HTML block) instead. - The pixel shows as inactive after 24 hours. Confirm the site was published after you saved the pixel code. Unpublished changes are not visible to OTTO. - I have multiple pages and Method 2 is time-consuming. Check if your GoDaddy theme includes a global header or footer section — adding the pixel there once will apply it site-wide. 💬 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.

🔌 What Is MCP and Where to Find It

🧩 What Is MCP? MCP stands for Model Context Protocol. It is an open standard that allows AI assistants and external tools to connect directly to platforms like Search Atlas and perform actions on your behalf — such as retrieving data, managing settings, or triggering account-level operations — through a secure, structured connection. Think of MCP as a bridge between an AI agent (for example, Claude, Cursor, or another MCP-compatible client) and your Search Atlas account. Instead of copying and pasting data manually, an AI agent uses an MCP connection to read and interact with Search Atlas in real time. 🔑 How MCP Differs from a Standard API Key Both MCP connections and standard API keys allow external tools to access your Search Atlas data, but they work differently: - Standard API key: A static credential you embed in code or third-party integrations. It authenticates requests but does not carry session context or support interactive, multi-step workflows. - MCP connection: A dynamic, session-aware protocol designed specifically for AI agents. It supports back-and-forth interactions, tool calls, and structured responses that an AI model can act on directly. MCP connections are better suited for automated workflows that require multiple sequential actions. Use a standard API key when integrating Search Atlas data into a custom script or third-party app. Use an MCP connection when you want an AI assistant to operate Search Atlas tools on your behalf interactively. 🗺️ Where to Find MCP Connections in Search Atlas MCP connection setup and authentication are managed from within your Search Atlas account settings area. Because the exact location of MCP connection options may vary depending on your plan and the current dashboard layout, please contact our support team via the chat widget so they can confirm the correct navigation path for your account and verify that MCP access is included in your current subscription. To get the fastest resolution, please have the following ready when you reach out: - Your Search Atlas account email or project name - Your current subscription plan - A description of what you are trying to connect (e.g., which AI agent or tool you are using) - Any error messages or authentication failures you have encountered, including the exact wording and any timestamps ⚙️ When and Why to Use MCP MCP connections are most useful in the following situations: - AI-assisted SEO workflows: Connect an AI agent to Search Atlas so it can pull keyword data, check rankings, or analyse site metrics without manual exports. - Automated reporting: Let an AI agent query Search Atlas tools and compile results into a report automatically. 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.

⚡ Verify Google Instant Indexing Submissions in Search Atlas

What Is Google Instant Indexing? Google Instant Indexing allows Search Atlas to notify Google immediately when a page is published or updated, rather than waiting for Googlebot to crawl it on its own schedule. This speeds up the time it takes for your pages to appear in search results. There are two separate things to verify: submission confirmation (did Search Atlas successfully send the request to Google?) and indexing status (did Google actually index the page?). This article explains what each means and how to get help confirming both. Understanding the Difference: Submission vs. Indexing A confirmed submission means Search Atlas delivered a ping to Google's Indexing API on behalf of your page. It does not guarantee that Google has indexed the page — that decision is made entirely by Google based on its own quality and crawl signals. Because of this distinction, it is normal for a page to show a successful submission in Search Atlas while still not appearing in Google's index immediately. Google typically processes Indexing API requests within hours to a few days, but timing is not guaranteed. What to Have Ready Before Contacting Support Because Google Instant Indexing submission tracking and indexing status details are tied to your specific account and property configuration, a support teammate can investigate and confirm the exact status of your submissions. To get the fastest resolution, have the following ready when you reach out: - The exact URL or URLs you submitted via Google Instant Indexing. - The date and approximate time you submitted them. - The name of the Search Atlas project or site the URLs belong to. - Whether your Google Search Console property is connected and active in Search Atlas. - Any error messages or unexpected statuses you have seen in your account. While You Wait: Check Google Search Console Directly You can independently check whether Google has indexed a specific URL using Google Search Console, which is the authoritative source for indexing status: 1. Log in to Google Search Console and select the property that matches your site. 2. Use the URL Inspection tool and enter the exact URL you want to check. 3. Review the coverage and indexing status Google reports for that URL. If Google Search Console shows the page is not indexed, note the reason provided — this information will also be helpful for the support team. 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 Avatar Menu (👤) 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.

🕐 Understanding Search Atlas to GoHighLevel Scheduled Post Sync Timing

🔍 Overview When you schedule a post in Search Atlas and publish it to GoHighLevel (GHL), the post does not appear in GHL immediately after scheduling. Search Atlas sends the post to GoHighLevel at the exact date and time you set — not the moment you click Schedule. This is expected behavior, not a bug. ⏱️ How Sync Timing Actually Works Here is what happens step by step after you schedule a post in Search Atlas: 1. You set a future publish date and time in Search Atlas and confirm the schedule. 2. Search Atlas stores the post internally and queues it for the scheduled date and time. 3. At the scheduled date and time, Search Atlas initiates the sync and pushes the post to your connected GoHighLevel account. 4. GoHighLevel receives the post and it becomes visible in your GHL calendar or social planner — typically within 1 to 5 minutes of the scheduled time. If you check GoHighLevel 30 minutes — or even several hours — after scheduling, the post will not be visible yet. It will only appear once the scheduled date and time has passed. 📋 Common Reasons a Post Appears to Be Missing in GHL - The scheduled time has not arrived yet. This is the most frequent cause. The post exists in Search Atlas but will not push to GHL until the scheduled moment. - Time zone mismatch. Your Search Atlas account time zone and your GoHighLevel account time zone may differ. A post scheduled for 9:00 AM in one time zone may not appear in GHL until that time converts correctly. - The GHL integration is disconnected. If the connection between Search Atlas and GoHighLevel was interrupted after scheduling, the post cannot sync at the scheduled time. - The post was saved as a draft, not scheduled. Only posts with a confirmed scheduled date and time will sync. Draft posts remain in Search Atlas only. - A sync error occurred at publish time. Occasional API errors between Search Atlas and GoHighLevel can prevent a specific post from syncing. These are logged and can be retried. ✅ What to Check Before Contacting Support 1. Confirm the scheduled date and time has passed. Open Search Atlas, locate your post in the content calendar or post queue, and verify the scheduled timestamp. If it is still in the future, the post is working correctly — wait until that time. 2. Check your time zone settings. In Search Atlas, go to your account settings and confirm your time zone matches the time zone set in your GoHighLevel account. Mismatched time zones are the second most common cause of apparent delays. 3. Verify the GoHighLevel integration is active. Navigate to your Search Atlas integrations settings and confirm that your GoHighLevel connection shows a green or active status. If it shows an error or disconnected state, reconnect it and reschedule the post. 4. Check GHL social planner and calendar views. Sometimes posts appear in one view (such as the calendar) but not another (such as the list view). Check both to confirm the post is genuinely missing. 5. Look for a failed sync notification. Search Atlas will surface a sync error in the post status if the push to GHL failed at the scheduled time. If you see a failed status, use the retry option on that post. 🔄 How to Retry a Failed Sync 1. Open Search Atlas and locate the post that failed to sync. 2. Check the post status — it will display a failed or error indicator if the sync did not complete. 3. Select the post and choose the Retry Sync option. 4. Confirm the retry. Search Atlas will attempt to push the post to GoHighLevel again immediately. 5. Allow up to 5 minutes, then check your GoHighLevel social planner to confirm the post has appeared. ⚠️ What Not to Do While Waiting for a Scheduled Post - Do not delete and recreate the post — this resets the schedule and may create duplicate entries in GHL once the original syncs. - Do not disconnect and reconnect the GHL integration while posts are scheduled — this can interrupt queued syncs. - Do not change the scheduled time repeatedly — each change requeues the post and can add processing time. 💬 Still Need Help? If your post's scheduled time has passed, your time zones match, and the integration is active — but the post still has not appeared in GoHighLevel — our team can investigate the specific sync log for your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔁 Golden Loops Social Media, Claude MCP, and Option Selection

🌀 What Are Golden Loops? Golden Loops is a Search Atlas automation framework that chains AI-powered tasks together into repeatable workflows. You can use Golden Loops to generate, schedule, and publish content across multiple channels — including social media — with minimal manual effort. 📱 Using Golden Loops with Social Media Golden Loops can integrate with social media publishing as part of your automated content workflows. This allows you to automate content creation and queue posts across your connected social accounts. The exact configuration steps and available options within the Golden Loops interface depend on your account setup. Because the specific UI paths and settings for social media integration are not yet fully documented, we recommend reaching out to our support team directly so they can walk you through the correct setup for your account. Before contacting support, it helps to have the following ready: - The name of the Golden Loop you are working with (or want to create) - The social platforms you want to connect or post to - A description of the behavior you are trying to set up or the error or unexpected result you are seeing 🔌 Connecting Claude MCP to Search Atlas Claude MCP (Model Context Protocol) is a connection method that allows the Claude AI model to interact with Search Atlas tools and data. When integrated with Golden Loops, this can give Claude the context it needs to produce more accurate, platform-aware outputs during content generation. Because the verified configuration steps for connecting Claude MCP within Golden Loops are not yet fully documented, we recommend contacting our support team for guided assistance. When you reach out, please have the following information ready: - Your Search Atlas project name - The specific Golden Loop or workflow you are trying to configure - The exact step where you are getting stuck, or any error message you are seeing (including the full text and any timestamp) - Whether you already have an Anthropic API key or are still setting one up This will allow our team to provide the most accurate and up-to-date guidance for your setup. 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.

🔗 Third-Party Integration Requests Outside Search Atlas

🧭 Overview Search Atlas is an all-in-one SEO platform built to help you research keywords, track rankings, manage local listings, and publish content — all from a single dashboard. While we are continuously expanding our feature set, some requests involve third-party platforms or workflows that fall outside the current scope of Search Atlas. A common example is porting press releases from a tool like Signal Genesys into Search Atlas or setting up media rooms for separate business entities within the platform. This article explains what is currently supported, what is not, and how to work effectively within Search Atlas for similar use cases. ✅ What Search Atlas Currently Supports Search Atlas offers a growing set of tools that can handle many content publishing and local media needs natively. Here is what is available today: - Content Publishing: Create, optimise, and publish SEO content directly within the platform using the built-in content editor and AI writing tools. - Media Library: Upload and manage media assets for your local projects by navigating to Left sidebar → Local → Media Library. - Local Posts: Publish posts to your Google Business Profile listings by navigating to Left sidebar → Local → Posts. - Local Citations: Build and manage local citations for your business entities via Left sidebar → Local → Local Citations. - Multi-location Support: Manage multiple business entities and locations under a single Search Atlas account using GBP projects at Left sidebar → GBP Projects. - Rank Tracking: Monitor keyword performance across entities via Left sidebar → Keywords → Rank Tracker. 🚫 What Falls Outside Search Atlas Scope The following requests are currently outside the scope of what Search Atlas supports: - Direct integrations with Signal Genesys or other press release distribution platforms: Search Atlas does not have a native connector to import, sync, or manage content from Signal Genesys or similar third-party PR tools. - Dedicated media room pages for separate entities: Search Atlas does not currently offer a standalone media room feature where press releases, brand assets, and media contacts are hosted for individual business entities. - Automated porting of press release content: Bulk importing formatted press releases from external platforms into Search Atlas is not supported at this time. 💡 Recommended Workarounds Even though direct integration is not available, you can still achieve similar outcomes using tools already inside Search Atlas: 1. Manually repurpose press release content: Copy your press release text from Signal Genesys and paste it into the Search Atlas content editor. From there you can optimise it for SEO, adjust headings, and publish or export it as needed. 2. Use the Media Library for brand assets: Navigate to Left sidebar → Local → Media Library to upload logos, images, and media files associated with each business entity. Organise assets per project to keep entities separate. 3. Create entity-specific GBP projects: Set up a dedicated GBP project for each business entity under Left sidebar → GBP Projects. This allows you to manage posts, citations, and reviews independently per entity. 4. Publish news updates as Local Posts: For press release-style announcements, use Left sidebar → Local → Posts to publish updates directly to each entity's Google Business Profile, keeping audiences informed without needing a separate media room. 5. Track visibility of published content: After publishing, monitor keyword rankings and organic visibility for each entity via Left sidebar → Keywords → Rank Tracker. 🗺️ Submitting a Feature Request Search Atlas is actively developed based on customer feedback. If a third-party integration or a feature like media rooms is important to your workflow, we encourage you to submit a feature request. Your feedback directly influences the product roadmap. To submit a request, open the chat widget in the bottom-right corner of the platform and describe the integration or feature you need. Our team logs all feature requests and reviews them regularly. 🛠️ Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ How to Install the Search Atlas Tracking Pixel

🔍 What Is the Search Atlas Pixel? The Search Atlas tracking pixel is a small snippet of code you place on your website. It allows OTTO SEO to collect on-site data, power automation features, and accurately report your site's SEO performance. Without the pixel installed correctly, OTTO cannot activate fully. 📋 Before You Begin Make sure you have the following ready before installing the pixel: - Admin or editor access to your website's code, CMS, or tag manager - Your unique pixel snippet — found inside your OTTO SEO dashboard - A clear understanding of which installation method suits your site (see below) 🚀 Step 1 — Find Your Pixel Snippet 1. Log in to Search Atlas and navigate to your OTTO SEO dashboard. 2. Select the site you want to set up. 3. Follow the on-screen setup steps until you reach the pixel installation step. 4. Copy the pixel code snippet displayed on screen — this code is unique to your site. ⚙️ Step 2 — Choose Your Installation Method There are three supported ways to install the pixel. Choose the one that matches how your website is managed. 💡 Method A — Direct Code Installation (Recommended) This method works for most websites where you can edit the HTML source or use a CMS plugin to inject code into the <head> section. 1. Open your website's theme editor, CMS settings, or custom HTML section. 2. Navigate to the global <head> tag — this code must appear on every page of your site. 3. Paste your pixel snippet immediately before the closing </head> tag. 4. Save and publish your changes. 5. Return to the OTTO SEO dashboard and check your setup status to verify the pixel has been detected. Important: If your site uses Next.js, React Server Components, or lazy-loading frameworks, ensure the pixel loads at the top-level document level rather than only inside a client-side component, so it can be detected correctly. 💡 Method B — Google Tag Manager (GTM) Installation Use this method if your site already uses GTM to manage tracking scripts. 1. Log in to your Google Tag Manager account and open the container for your website. 2. Click Tags in the left menu, then click New. 3. Click Tag Configuration and select Custom HTML. 4. Paste your Search Atlas pixel snippet into the HTML field. 5. Click Triggering and select All Pages as the trigger. 6. Name the tag (e.g., Search Atlas Pixel) and click Save. 7. Click Submit in the top-right corner of GTM to publish your container. 8. Return to the OTTO SEO dashboard and check your setup status to confirm the pixel has been detected. 💡 Method C — GoHighLevel (GHL) Installation Use this method if your site is hosted or managed through GoHighLevel. 1. Log in to your GoHighLevel account and open the relevant site or funnel. 2. Navigate to the site or funnel settings and locate the section where you can add custom scripts or tracking codes to the <head> of your pages. 3. Paste your Search Atlas pixel snippet into that field. 4. Save your changes and ensure the snippet is set to load on all pages. 5. Return to the OTTO SEO dashboard and check your setup status to confirm the pixel has been detected. 🛠️ Troubleshooting If the pixel is not being detected after installation, check the following: - Confirm the pixel snippet is placed inside the <head> section and loads on every page of your site, not just the homepage. - If using GTM or GHL, make sure you have published or saved your changes — unpublished containers will not fire the pixel. - Clear your site's cache after installing the pixel, as cached pages may serve an older version of your code. - If you continue to see a detection issue, note your site URL and any error messages shown in the dashboard before reaching out for support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🔄 Reconnect One GSC Property Safely

🧭 Overview If you deleted permissions or revoked access for a specific Google Search Console (GSC) property — such as Pulsebiohacking — you only need to reconnect that one property. Search Atlas manages each GSC connection independently, so re-authenticating a single property will not affect your other connected accounts. This article explains what to have ready so the affected property can be reconnected quickly without disrupting the rest of your GSC connections. ⚠️ Before You Reach Out - Confirm you are signed into the correct Google account that owns or has access to the specific GSC property you want to reconnect. - Make sure the old permissions for that property have already been fully revoked from your Google account, or are simply inactive on the Search Atlas side. - You do not need to disconnect or re-authenticate any of your other GSC properties — this process is scoped to a single property only. 🔑 Step 1: Gather the Required Information Before reaching out, have the following ready so your request can be actioned without delays: - The exact name of the disconnected GSC property (for example, Pulsebiohacking). - The Google account email address that owns or has verified access to that property in Google Search Console. - Approximately when the connection broke or permissions were revoked. 🔄 Step 2: Request the Property Reconnection The reconnection of the affected property is handled on the platform side. Have the details gathered above ready so the process can be completed without touching any of your other GSC connections. Be ready to: - Confirm which Google account should be used to authenticate the specific property being reconnected — especially important if you manage multiple Google accounts. - Confirm that you are happy to grant the necessary permissions for that property only. ✅ Step 3: Verify After Reconnection 1. Once the property has been reconnected, open the project for the affected property and confirm that GSC data is loading correctly. 2. Spot-check two or three of your other connected properties to confirm their data is unaffected and their connections remain intact. 🛡️ Why Your Other Connections Are Not Affected Search Atlas manages each GSC property connection independently. Reconnecting one property creates a new authentication scoped only to that property, leaving all other connections completely untouched. 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.

🔧 Installing OTTO Tracking on a Website Studio Site

If you built your site from scratch in Website Studio and want to track it with OTTO, you do not need a separate plugin or integration. Website Studio includes a built-in option for adding custom scripts directly in the project settings, and this is where your OTTO tracking script goes. Where to Find the Setting Open your project in Website Studio and navigate to the project settings area. Look for a section dedicated to custom scripts or code embeddings — this is where you can inject code into your site's page header. How to Install the OTTO Script Within the custom scripts or embeddings section of your project settings, locate the field for header code — this is where scripts injected into the page's <head> belong. Tracking pixels such as OTTO are meant to go in the header area rather than the footer. To install OTTO, copy the OTTO tracking script from your OTTO project and paste it into the header code field in your Website Studio project settings, then save your changes. What to Expect This is a general-purpose custom code field rather than a dedicated, one-click OTTO integration. There is no automatic site detection step for Website Studio the way there might be for some other platforms, so double-check that the full script tag is pasted correctly before saving. Once saved, OTTO will begin tracking the site the same way it does on any other website where the script has been added to the header. 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.

⚡ Publishing AI Content to Custom Backends

Overview Search Atlas natively supports WordPress, Webflow, Shopify, and Squarespace as one-click CMS connectors. If your project runs on a custom backend — such as Next.js, Express, or another Node.js framework — you may want to publish AI-generated content automatically to that backend. This use case involves connecting Search Atlas content output to a custom or headless backend. Because the exact integration steps depend on your specific stack and account configuration, this is something our team will need to assist you with directly. What to Prepare Before Reaching Out To help our team resolve your integration request as quickly as possible, please have the following ready when you contact us: - Your project name as it appears in Search Atlas - The backend framework or technology you are using (for example, Next.js, Express, custom Node.js server) - A description of what you are trying to achieve — for example, automatically publishing articles to your database, triggering builds, or pushing content to a headless CMS layer - Any error messages or failed responses you have encountered, including the exact error text and timestamps - What you have already tried, so our team does not suggest steps you have already taken What Our Team Can Help With A human teammate can review your account, confirm which integration options are available for your setup, and walk you through the correct configuration steps specific to your backend environment. 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 GoDaddy Blog Publishing via Universal CMS

🌐 What Is the Universal CMS Connector? The Universal CMS Connector is a Search Atlas feature that lets you publish blog content directly to website platforms that are not natively integrated — including sites built and hosted on GoDaddy. Instead of copying and pasting content manually, you can push published articles straight from Search Atlas to your GoDaddy blog. ✅ Before You Begin Make sure you have the following ready before starting the setup: - An active Search Atlas account with content publishing access. - A live GoDaddy website with a blog section enabled. - Admin access to your GoDaddy account. - Your GoDaddy site's public URL (e.g., https://yourdomain.com). 🛠️ Setting Up the Universal CMS Connector for GoDaddy The exact steps to connect GoDaddy to Search Atlas via the Universal CMS Connector depend on your specific account configuration and GoDaddy's platform capabilities. Because the setup flow can vary, please use the chat widget below to be connected with a team member who can walk you through the correct process for your account and confirm whether the integration is supported for your GoDaddy setup. When reaching out, please have the following information ready: - Your Search Atlas account email or project name. - The full URL of your GoDaddy website (e.g., https://yourdomain.com). - The GoDaddy product you are using (e.g., Website Builder, WordPress on GoDaddy, or a custom hosting plan). - Any error messages or steps you have already attempted. ⚠️ Common Issues to Note - GoDaddy platform type matters: The Universal CMS Connector setup may differ depending on whether your GoDaddy site runs on GoDaddy's own Website Builder, WordPress, or another platform. Please confirm this before reaching out so our team can advise accurately. - Admin access required: Make sure you have full admin access to both your Search Atlas account and your GoDaddy account before beginning any integration steps. - Site URL format: Always include https:// when providing your site URL to avoid connection errors. 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.

📅 Why Scheduled Posts Don't Appear in WordPress Immediately

🔍 Overview If you've scheduled blog posts in Search Atlas and can't find them in your WordPress CMS, you're not alone. This is one of the most common points of confusion for new users, and the good news is that nothing is broken. This article explains exactly how Search Atlas handles scheduled content and what to expect at each stage. ⚙️ How the Search Atlas Publishing Pipeline Works Search Atlas and WordPress are two separate systems. When you schedule a blog post in Search Atlas, the post lives inside the Search Atlas publishing pipeline — not inside WordPress. Search Atlas holds the post, manages its scheduled date and time, and then pushes the content directly to WordPress at the moment of publication. This means: - Scheduled posts will not appear in your WordPress dashboard as draft or scheduled posts before their publish time. - WordPress only receives the post after the scheduled date and time has passed and Search Atlas has successfully pushed it. - Once published, the post will appear in WordPress as a published post, not as a scheduled one. This is intentional by design. Search Atlas acts as the single source of truth for your content queue, giving you a centralised place to manage, edit, and approve posts before they go live — without cluttering your WordPress drafts. 📋 What You'll See in Search Atlas Before Publication While your posts are waiting to publish, you can track them inside the Search Atlas platform. Look for your scheduled posts within the blog or content scheduling section of Search Atlas, where each post will show a status reflecting its current stage in the pipeline — for example, whether it is queued, awaiting approval, successfully published, or encountered an issue during publishing. If your workspace uses an approval workflow, be aware that posts still pending approval will not be pushed to WordPress even if a scheduled date has been set. Make sure all required approvals are completed before the scheduled publish time. ✅ Steps to Take If Your Post Has Not Appeared in WordPress 1. Log in to Search Atlas and navigate to the blog or content scheduling area. Locate the post in question and check its current status. 2. Confirm that the scheduled date and time have already passed. If the time has not yet come, the post has not been pushed to WordPress yet — this is expected behaviour. 3. If your workspace requires approvals, verify that the post was fully approved prior to its scheduled publish time. A post that was not approved will not be sent to WordPress. 4. Check that the correct WordPress site is connected to your Search Atlas account. If the WordPress connection was interrupted or not configured, the post cannot be delivered. You may need to reconnect your WordPress site in your account settings. 5. If the post shows a failed or error status, note the exact error message or status label shown, as well as the post name and scheduled time. This information will help our team investigate quickly. 🔗 Verifying Your WordPress Connection A common reason posts do not appear in WordPress is a disrupted connection between Search Atlas and your WordPress site. To check this, go to your Search Atlas account settings and look for the WordPress or CMS integration section. Confirm that your site is listed and shows an active, connected status. If it appears disconnected or missing, follow the on-screen prompts to reconnect it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Connect HubSpot CMS to OTTO SEO

🌐 Overview Search Atlas integrates with HubSpot CMS through OTTO SEO, allowing you to push SEO recommendations — including page titles and meta descriptions — directly to your live pages. Once connected, you eliminate manual copy/paste workflows and let OTTO handle implementation automatically through its CMS integration and direct content deployment capability. ⚙️ How the Integration Works OTTO SEO connects to your HubSpot CMS via a site activation. After activation, OTTO audits your pages and surfaces recommendations that can be deployed directly to HubSpot without manual editing inside HubSpot itself. The exact deployment options and controls available to you will depend on your account configuration — our support team can walk you through the specific steps for your setup. 🚀 Getting Started — Activate OTTO SEO for Your HubSpot Site To begin using OTTO's CMS integration with HubSpot, you will need to activate OTTO for your HubSpot site from within the Search Atlas platform. During activation, you will be prompted to connect your HubSpot domain and grant the necessary permissions so OTTO can read and write page metadata. If your HubSpot site does not appear as an available property during this step, you will need to connect your HubSpot domain first before proceeding. Once activation is complete, OTTO will crawl your site and generate SEO recommendations. The time this takes varies depending on the size of your site. 🛠️ Deploying SEO Recommendations to HubSpot After activation, OTTO surfaces SEO recommendations — such as page title rewrites and meta description updates — that can be deployed directly to your HubSpot CMS. You can choose to deploy recommendations individually or in bulk, depending on how much control you want over the process. A controlled review option is available if you prefer to approve changes before they go live rather than having them applied automatically. Because the exact names of buttons, tabs, and settings in OTTO may vary or be updated, we recommend the following approach if you encounter difficulty locating a specific control: 1. Log in to Search Atlas and navigate to the OTTO SEO section of the platform. 2. Locate your activated HubSpot site within OTTO. 3. Look for deployment or recommendation controls associated with that site — these will allow you to review and push changes directly to HubSpot. 4. If you cannot find a specific setting or the integration does not behave as expected, contact our support team with your project name and a description of what you are trying to do, so we can provide exact, up-to-date guidance for your account. 🛟 When to Contact Support If you are unable to locate the HubSpot CMS integration options, your site is not appearing after activation, or recommendations are not deploying as expected, our team can assist. Please have the following ready when you reach out: - Your Search Atlas project or site name - The HubSpot domain you are trying to connect - A description of the step where you are getting stuck or the exact error message you see 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 Pixel Integration With Lofty.com

🌐 Overview Search Atlas can integrate with websites built on Lofty.com through a tracking pixel. This article explains how the integration works, what it can and cannot do automatically, and whether Search Atlas needs access to your Lofty.com editor. 🔍 What Is the Search Atlas Pixel? The Search Atlas pixel is a small snippet of JavaScript code that you place in your website's header or footer. Once installed, it allows Search Atlas to track site performance data and connect your Lofty.com website to your Search Atlas dashboard. The pixel is used for: - Tracking visitor behavior and traffic sources - Connecting your site to Search Atlas reporting tools - Enabling certain automated SEO features tied to your domain 🛠️ How to Add the Pixel to Your Lofty.com Website Lofty.com's website editor allows you to inject custom code into your site's header. Follow these steps to install the Search Atlas pixel: 1. Log in to your Search Atlas account and locate your pixel code. You can find this inside your account settings or within the relevant Search Atlas tool that requires tracking. 2. Copy the full pixel code snippet provided by Search Atlas. 3. Log in to your Lofty.com account and open your website editor. 4. Navigate to your site's Settings or Header/Footer Code section — the exact location may vary depending on your Lofty.com plan and editor version. 5. Paste the Search Atlas pixel code into the header code field. 6. Save your changes and publish your site. 7. Return to Search Atlas and verify the pixel is detected on your domain. If Lofty.com does not provide a custom code injection field on your current plan, you may need to upgrade your Lofty.com subscription or contact Lofty.com support directly to enable this feature. ✍️ Does Search Atlas Need Access to My Lofty.com Editor? This is one of the most common questions about this integration. The short answer is: it depends on the feature you want to use. Here is a breakdown by use case: - Pixel tracking only: No editor access is required. You install the pixel yourself by pasting the code into your Lofty.com header settings. Search Atlas does not need login credentials or direct access to your editor for this. - Automated page editing: If you want Search Atlas to automatically update or optimize existing pages on your Lofty.com site, you would need to grant access or use a supported integration method. Lofty.com is a closed proprietary platform, which means Search Atlas cannot push content changes directly unless Lofty.com supports a compatible API or plugin connection. - Automated blog creation: Similarly, for Search Atlas to publish blog posts automatically to your Lofty.com site, a direct integration between the two platforms must be supported. At this time, Lofty.com does not offer an open API or native Search Atlas plugin, so fully automated publishing to Lofty.com is not available. Content created in Search Atlas would need to be manually copied and published in your Lofty.com editor. 📋 What You Can Do With the Pixel on Lofty.com Even without a full two-way integration, connecting your Lofty.com site via the pixel gives you access to valuable Search Atlas features, including: - Monitoring your site's SEO performance inside Search Atlas - Tracking keyword rankings using Left sidebar → Keywords → Rank Tracker - Identifying keyword opportunities using Left sidebar → Keywords → Keyword Magic - Reviewing competitive keyword gaps using Left sidebar → Keywords → Keyword Gap ⚠️ Important Limitations to Know - Search Atlas cannot log in to or control your Lofty.com editor on your behalf without explicit access being granted by you. - Lofty.com's closed platform architecture limits the degree of automation available compared to open platforms like WordPress. - Any content generated by Search Atlas tools (such as AI-written blog posts) will need to be manually transferred into your Lofty.com editor until a deeper integration is available. 💬 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 Generated Articles to Webflow CMS

🌐 Overview Search Atlas lets you publish AI-generated articles directly to your Webflow CMS without leaving the platform. This guide walks you through connecting your Webflow site and pushing finished content live in just a few steps. 🔗 Step 1: Connect Your Webflow Account Before you can publish, you need to link Search Atlas to your Webflow site. You only need to do this once. 1. From the top-right avatar (Avatar Menu (👤)), go to Settings and select Integrations. 2. Find the Webflow card and click Connect. 3. You will be redirected to Webflow. Log in and grant Search Atlas the requested permissions. 4. Select the Webflow site you want to publish to, then click Authorize. 5. You will be returned to Search Atlas. A green Connected status confirms the integration is active. ✍️ Step 2: Open Your Generated Article Once your Webflow account is connected, navigate to the article you want to publish. 1. Go to Content (What are we writing today?) in the left-hand navigation. 2. Locate your finished article in the article list and click its title to open the editor. 3. Review the content and make any final edits before publishing. 📤 Step 3: Publish to Webflow With your article open and ready, follow these steps to send it to your Webflow CMS. 1. Click the Publish button in the top-right corner of the editor. 2. From the publishing options, select Webflow. 3. Choose the Collection within Webflow where the article should be saved (for example, your Blog Posts collection). 4. Map the article fields — such as Title, Body, and Slug — to the corresponding fields in your Webflow collection. 5. Toggle Publish to Webflow on if you want the item to go live immediately, or leave it off to save it as a draft in Webflow. 6. Click Confirm to push the article. A success notification will confirm the article has been sent to your Webflow CMS. You can verify it by logging in to Webflow and checking the relevant collection. ⚠️ Common Issues and Fixes - Connection error during authorisation: Make sure you are logged in to the correct Webflow account before clicking Connect. If the error persists, disconnect and reconnect the integration. - Collection not appearing in the dropdown: Ensure the Webflow site has at least one CMS Collection set up. Collections must exist in Webflow before they appear in Search Atlas. - Fields not mapping correctly: Field names in Search Atlas must match the field types in your Webflow collection. For example, the Body field requires a Rich Text field type in Webflow. - Article saved as draft instead of published: Check that the Publish to Webflow toggle was switched on before confirming. You can also publish the item manually inside the Webflow editor. 💡 Tips for a Smooth Workflow - Set up your Webflow CMS Collection structure before generating articles to ensure field mapping goes smoothly. - Use the Slug field to control the article URL in Webflow. Search Atlas auto-generates a slug from the title, but you can edit it before publishing. - If you manage multiple Webflow sites, you can switch the connected site at any time from the top-right avatar (Avatar Menu (👤)) > Settings > Integrations. 🛠️ 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.

🔌 Extract and Use OTTO Pixel Code on Any Website

🧩 What Is the OTTO Custom Integration Pixel? OTTO's custom integration pixel is a small JavaScript snippet that lets you connect OTTO to any website — even platforms that don't support WordPress plugins or direct integrations. Once the code is placed on your site, OTTO can deliver its on-page SEO recommendations automatically. This method works on platforms such as Squarespace, Wix, Webflow, Shopify, custom-built HTML sites, and any other CMS that allows you to inject code into the site's <head> or footer section. 🗺️ Where to Find Your OTTO Pixel Code 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Locate the website project you want to connect and open it. 4. Within the project, look for the section related to website connection or integration options. The exact label may vary — if you are unsure which option to select, contact the support team for guidance on your specific account view. 5. Once you locate the pixel code for your project, copy the full JavaScript snippet to your clipboard. Note: Each website project has its own unique pixel code. Do not share or reuse a pixel between different website projects — doing so will cause tracking and automation errors. 📋 How to Add the Pixel to Your Website Once you have copied your pixel code, you need to paste it into your website. The exact steps depend on your platform, but the goal is always the same: place the script inside the <head> section of every page on your site. General steps (apply to most platforms): 1. Open your website platform's admin panel or settings area. 2. Navigate to the section that allows you to add custom code, scripts, or header injections. This is often labelled Custom Code, Header Code, Inject Scripts, or Advanced Settings. 3. Paste the copied OTTO pixel code into the head code field. 4. Save or publish your changes. 5. Return to Search Atlas and check whether your website project now shows as connected. If connection is not confirmed, ensure the script was pasted into the head section and that your changes were published. 🛠️ Platform-Specific Quick Reference - Squarespace: Settings → Advanced → Code Injection → paste into the Header field. - Wix: Settings → Custom Code → Add Custom Code → select "Head" and "All Pages". - Webflow: Project Settings → Custom Code → Head Code section → paste and publish. - Shopify: Online Store → Themes → Edit Code → open theme.liquid → paste before the closing </head> tag. - Custom HTML site: Open each page's HTML file and paste the pixel code inside the <head> tags, then re-upload or redeploy the files. 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 Pixel Installation After Whitelabel Domain Updates

🧭 Overview When you update your whitelabel domain in Search Atlas, any previously installed OTTO pixels tied to your old domain may stop reporting as active. The pixel code is domain-specific, so a domain change typically requires obtaining a fresh pixel code and reinstalling it. If you are working inside HighLevel (GoHighLevel), this article explains what to do and what information to have ready. ⚠️ Why Your OTTO Pixel Shows as Not Installed After a whitelabel domain update, the pixel code previously installed on your site may no longer be recognized as valid because it was associated with your previous domain. Any site still carrying the old pixel code may show a not installed status because: - The old pixel references your previous domain and may no longer be valid. - Search Atlas may not be able to verify ownership or activity through a domain it no longer recognizes as yours. - HighLevel sites can cache scripts, which may cause the status to appear stuck even after an update. Obtaining your updated pixel code and reinstalling it is typically required after a domain change — this is expected behavior, not a bug. 🛠️ How to Reinstall the OTTO Pixel After a Whitelabel Domain Change Because the exact steps for retrieving an updated pixel code may vary depending on your account setup, we recommend the following approach: 1. Log in to Search Atlas and navigate to the OTTO SEO or OTTO section of your dashboard. 2. Open the OTTO workspace for the relevant client or project. 3. Locate the OTTO Pixel area within your workspace settings and retrieve the current pixel code associated with your updated whitelabel domain. 4. Copy the full pixel script that appears. 5. In HighLevel, open the site or funnel where the pixel needs to be installed and paste the new pixel code into the appropriate tracking code field at the site or funnel level. 6. Save your changes and allow time for the status to update in Search Atlas. If you are unsure where to find the pixel code in your dashboard or how to add it in HighLevel, please reach out to our support team with your project name, your old and new whitelabel domain names, and a description of where the pixel is currently showing as not installed. This will allow us to confirm the correct steps for your specific setup. 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.

🔗 GoHighLevel Integration: Features and Limitations Explained

🔍 Overview Search Atlas offers a GoHighLevel (GHL) integration that brings select tools directly into the GHL environment. However, the GHL integration does not include every feature available in the full Search Atlas platform. This article clarifies what is and is not available so you can plan your workflow accordingly. ✅ Features Available in the GoHighLevel Integration The GoHighLevel integration supports a subset of Search Atlas features. Not all tools from the full platform are replicated in the GHL environment. If you are unsure whether a specific feature is available in GHL, the safest approach is to log in to your full Search Atlas account and test access there. 🚫 Features NOT Available in the GoHighLevel Integration Several core Search Atlas features are not accessible through the GHL integration. Most notably: - Backlink purchasing is not available through GoHighLevel. There is no backlink package purchasing, no link-building order functionality, and no access to backlink marketplace tools within the GHL integration. Any claim that backlinks can be purchased via GHL is incorrect. - Backlink analysis tools — Tools for reviewing your backlink profile or identifying backlink gaps are not part of the GHL integration. - Authority-building tools — Various authority and campaign-related features available in the full platform are not accessible through GHL. - Agency whitelabel settings — Whitelabel configuration options are not available through the GHL integration. If any of these features are critical to your workflow, you must access them directly through your Search Atlas account at the full platform URL. 🛒 How to Purchase Backlinks in Search Atlas Backlink purchasing is only available inside the full Search Atlas platform. To access backlink tools and packages, log in to your Search Atlas account directly and navigate to the Backlinks section of the platform. From there you can review backlink options and explore available link-building packages. You cannot initiate or complete backlink purchases from within GoHighLevel. 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 Your OTTO Pixel From WordPress to Showit

🔍 Overview If you are moving your website from WordPress to Showit, you need to transfer your OTTO SEO pixel to the new platform. The pixel must be active on your live site for OTTO to crawl your pages, apply optimisations, and track results. This guide walks you through removing the pixel from WordPress and installing it on Showit. 🛠️ Step 1 — Retrieve Your OTTO Pixel Script Before touching WordPress, grab your pixel script from the Search Atlas platform so you have it ready. 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Select the project that is connected to your website. 3. Locate the OTTO pixel code — it is displayed in the setup or installation section of the OTTO SEO dashboard. 4. Copy the full script tag and paste it somewhere safe, such as a text file on your desktop. Cannot find the original script? Your pixel script is always available inside the OTTO SEO dashboard for your project. If it is not visible, 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 who can retrieve it for you. 🗑️ Step 2 — Remove the OTTO Plugin From WordPress Running the pixel on two platforms at the same time can cause duplicate signals and inaccurate data. Deactivate and remove it from WordPress first. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Find the Search Atlas plugin (menu: Search Atlas → Settings) and click Deactivate. 4. Once deactivated, click Delete to remove the plugin entirely. 5. Confirm the deletion when prompted. If you added the pixel manually via a header/footer plugin or your theme's custom code area, remove that code snippet as well before proceeding. ✅ Step 3 — Verify WordPress No Longer Fires the Pixel Before installing the pixel on Showit, confirm your WordPress site is no longer loading the script. - Visit your WordPress site (or a cached version if WordPress is still live). - Right-click the page and choose View Page Source. - Use Ctrl + F (or Cmd + F on Mac) and search for otto or your pixel script snippet. - If no results appear, the pixel has been successfully removed. 🚀 Step 4 — Add the OTTO Pixel to Showit Showit allows you to inject custom scripts into your site's header, which is exactly where the OTTO pixel needs to go. 1. Log in to your Showit account and open your site in the Showit designer. 2. Click on Site Settings (the gear icon or settings menu). 3. Navigate to the Custom Code or Header Code section. 4. Paste your OTTO pixel script into the Header field so it loads on every page of your site. 5. Save your changes and publish your Showit site. Important: Make sure you paste the script into the global header area — not a page-specific area — so OTTO can detect and optimise all pages on your domain. ✅ Step 5 — Confirm the Pixel Is Active on Showit After publishing, verify the pixel is firing correctly on your new Showit site. - Visit your live Showit website. - Right-click and choose View Page Source. - Search for otto to confirm the script appears in the page source. - Return to the OTTO SEO section in Search Atlas and check that OTTO shows your site as connected and active. It may take a few minutes after publishing for Search Atlas to detect the pixel on your new domain. If the status does not update within 30 minutes, try clearing your Showit site cache and refreshing the OTTO SEO dashboard. ⚠️ Common Issues - Pixel not detected after install: Confirm the script is in the global header, not a single-page code block. Re-publish your Showit site after making changes. - Duplicate pixel firing: Ensure the WordPress plugin and any manual code snippets have been fully removed before going live on Showit. - Cannot locate pixel script: Your pixel is always retrievable from the OTTO SEO dashboard in Search Atlas. Look for the installation or setup prompt within your project. 💬 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. Additional Notes If your script is missing, was lost during the migration, or is not displayed in the dashboard, you can generate a fresh one: Inside OTTO SEO, open your website project settings and look for a Reconnect, Reset Connection, or Generate Script option.

⚡ Integrate Search Atlas APIs with Custom Dashboards

Overview This article explains how to connect Search Atlas features — citation submission, GBP Projects, Smart Ads, and OTTO — into a custom dashboard so you can manage multiple salon locations from a single interface without conflicts. Generate Your API Key Every API call requires a personal API key scoped to your account. To find your API credentials, log in to Search Atlas and navigate to your account settings where API key management is available. Copy your key and store it securely as an environment variable inside your project — never hard-code it in source files. For the exact location of API key settings and any current endpoint documentation, refer to the official Search Atlas API documentation available within your account. Citation Automation via Aggregator Networks Search Atlas supports citation submission across major aggregator networks, helping push your business data to directories at scale. To integrate citation automation into your dashboard: - Consult the Search Atlas API documentation for the current citation submission endpoints, required fields, and any available bulk or batch options for multiple locations. - For each salon location, ensure your business data (name, address, phone, category, and website) is complete and consistent before submitting. - After submission, use the status-checking endpoint described in the API documentation to monitor propagation progress. Note that directory propagation can take a number of weeks — extended processing states are normal and do not necessarily indicate a failure. For specific endpoint paths, payload requirements, credit costs, and any applicable bulk discounts, refer to your Search Atlas API documentation. GBP Projects for Multi-Location Workflows GBP Projects let you group salon locations so that reporting, keyword tracking, and OTTO actions stay isolated per client. To set up a multi-location workflow: 1. Inside Search Atlas, create a separate GBP Project for each salon brand or ownership group. Refer to the Search Atlas interface or documentation for the current navigation path to GBP Projects. 2. Each project will have its own identifier accessible via the API. Store these IDs in your dashboard configuration to scope all API calls — citation submissions, OTTO actions, and reporting — to the correct project. 3. Avoid assigning the same location to multiple active OTTO configurations simultaneously, as this can cause conflicts. Use your project IDs to keep each location's automation isolated. OTTO and Smart Ads Integration When integrating OTTO and Smart Ads into a custom dashboard, use the project and location identifiers returned by the Search Atlas API to ensure actions apply to the correct salon location. Consult the Search Atlas API documentation for current endpoint details and parameters. 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.

🔗 Configurable Integration Connection Request Sharing

Search Atlas now supports configurable sharing of integration connection requests, giving you greater control over how third-party integrations are managed and delegated across your workspace. ✨ What's New Integration connection request sharing is now fully configurable. Previously, the sharing behavior for integration connection requests followed a fixed process. With this update, you can define exactly how connection requests are shared — whether across team members, sub-accounts, or client workspaces — so the process adapts to your operational setup rather than the other way around. 🛠️ How to Use It 1. Navigate to the Integrations section in your platform settings. 2. Select the integration for which you want to configure connection request sharing. 3. Open the Connection Request Sharing settings for that integration. 4. Choose your preferred sharing configuration and define who can send or receive connection requests. 5. Save your changes — the new sharing behavior takes effect immediately. 📋 What to Expect Once your configuration is saved, all new integration connection requests will follow the sharing rules you have defined. Existing active integrations already connected to your account will remain unaffected. Sharing configurations apply at the workspace level, so changes will be reflected consistently across all relevant integrations. Only users with the appropriate role permissions will be able to view or modify these sharing 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.

🔌 API Access, Quotas, and Plan Eligibility

🗺️ Overview API access at Search Atlas is not limited to Enterprise or higher-tier plans. Every plan — including Starter — includes API access. This article explains exactly which APIs are available on each plan and what monthly quota limits apply. ✅ Which Plans Include API Access? All Search Atlas pricing plans include API access: - Starter — API access included - Growth — API access included - Pro — API access included - Agency — API access included You do not need to upgrade to an Enterprise plan to use the Search Atlas API. Quota limits and available endpoints vary by plan tier, as detailed below. 📊 Monthly API Quota Limits by Plan Each plan comes with a set monthly quota. The following limits apply across core API types: - Starter — Base-level quotas suitable for individual use and testing - Growth — Increased quotas to support growing teams and campaigns - Pro — Higher limits for advanced users managing multiple projects - Agency — Maximum quotas designed for agencies with high-volume needs The table below outlines specific monthly quota limits for key API types: - Competitor Gap API - Growth: 200,000 requests/month - Pro: 500,000 requests/month - Agency: 1,000,000 requests/month - Content Gap API - Growth: 200,000 requests/month - Pro: 500,000 requests/month - Agency: 1,000,000 requests/month Starter plan quotas for these specific APIs may differ. If you are on the Starter plan and need confirmation of your exact limits, 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. 🔍 Content Gap and Competitor Gap API Availability Both the Content Gap API and Competitor Gap API are available on the following plans: - Growth — Both APIs available - Pro — Both APIs available - Agency — Both APIs available If you are on the Starter plan and want to confirm whether Content Gap or Competitor Gap API endpoints are enabled for your account, 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. 📋 Quick Reference: Plan Comparison - Starter — API access: Yes | Content Gap API: Confirm with support | Competitor Gap API: Confirm with support | Quota: Base level - Growth — API access: Yes | Content Gap API: Yes | Competitor Gap API: Yes | Quota: 200,000/month per API - Pro — API access: Yes | Content Gap API: Yes | Competitor Gap API: Yes | Quota: 500,000/month per API - Agency — API access: Yes | Content Gap API: Yes | Competitor Gap API: Yes | Quota: 1,000,000/month per API ⚡ How to Access Your API Credentials 1. Log in to your Search Atlas account. 2. Click your avatar in the top-right corner and select Settings. 3. Select API Keys or Integrations from the settings menu. 4. Copy your API key and review your current usage and remaining quota for the month. 🔄 What Happens When You Reach Your Quota? Once your monthly API quota is reached, requests to the affected endpoints will return an error until your quota resets at the start of the next billing cycle. To avoid interruptions: - Monitor your usage regularly in the API settings dashboard. - Consider upgrading to a higher plan if you consistently approach your limit. - Contact our team to discuss custom quota options if your needs exceed Agency-level limits. 🆙 Upgrading Your Plan If your current plan quota is not sufficient, you can upgrade directly from your account dashboard. Click your avatar in the top-right corner, select Billing, and open the Plans & Top-ups tab (Billing) to view available options and upgrade instantly. 💬 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 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.

⚡ Automate SEO Audits with GoHighLevel and Make

Overview This article covers automating SEO audit workflows by connecting GoHighLevel, the Search Atlas API, Make (formerly Integromat), and Claude. Because the exact configuration steps — including API endpoints, UI navigation paths, module names, and parameter names — vary depending on your specific Search Atlas plan and the versions of each platform you are using, we are not able to provide a verified step-by-step walkthrough here. To get accurate, up-to-date guidance for your setup, we recommend the following: - Search Atlas API documentation: Log in to your Search Atlas account and locate the API or Developer section to find the correct endpoints, authentication methods, and available parameters for triggering and retrieving site audits. - Make (Integromat) help center: Refer to Make's official documentation for instructions on creating webhook triggers, HTTP request modules, and flow control modules within a scenario. - GoHighLevel support: Check GoHighLevel's documentation for how to configure forms and outbound webhooks so that form submissions can trigger external workflows. - Anthropic / Claude API documentation: Review Anthropic's developer docs for the correct endpoint and authentication approach for sending audit results to Claude for analysis. What to Prepare Before Contacting Support If you need help from our team to set up or troubleshoot this integration, please have the following ready: - Your Search Atlas plan name (API access is included on every plan, including Starter) - The exact error message or unexpected behavior you are encountering, with a timestamp - The names of the Make modules or GoHighLevel workflow steps where the issue occurs - Any request/response logs or screenshots that show what is being sent and received 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.

🔌 Access Brand Voice Analysis via API

🧭 Overview Brand Vault stores your agency's brand identity details, including the Brand Voice Analysis — a structured breakdown of your brand's tone, style, and messaging guidelines. If you need to retrieve this data programmatically (for example, to integrate it into your own workflows or tools), the Search Atlas API gives you direct access. This article explains how to authenticate, find your Brand ID, and call the correct endpoint to retrieve Brand Voice Analysis data for any brand in your workspace, such as creativeblue.agency. 🔑 Step 1: Get Your API Key Before making any API calls, you need a valid Search Atlas API key. 1. Log in to your Search Atlas account. 2. Navigate to Settings → API Keys. 3. Copy your API key and store it securely. Treat it like a password — do not share it publicly. 🏷️ Step 2: Find Your Brand ID Every brand in Brand Vault has a unique Brand ID. You need this ID to query the correct brand's Voice Analysis. 1. Open Brand Vault from the header apps-grid icon → More Features → Brand Vault. 2. Select the brand you want to access (for example, creativeblue.agency). 3. Check the URL in your browser — the Brand ID appears as a unique identifier in the URL path (for example, /brand-vault/brands/abc123xyz). 4. Copy and save this ID for use in your API request. Alternatively, you can list all brands in your workspace by calling the brands list endpoint and matching by brand name. 📡 Step 3: Call the Brand Voice Analysis Endpoint Once you have your API key and Brand ID, use the following request structure to retrieve the Brand Voice Analysis: - Method: GET - Endpoint:/api/v1/brand-vault/brands/{brand_id}/voice-analysis - Header:Authorization: Bearer YOUR_API_KEY - Content-Type:application/json Replace {brand_id} with the ID you copied in Step 2, and YOUR_API_KEY with your actual API key. 📦 Step 4: Understand the Response A successful response returns a JSON object containing the brand's voice analysis fields. Common fields include: - tone — the overall tone of the brand (e.g., professional, conversational, authoritative) - style_guidelines — specific writing style rules for the brand - vocabulary — preferred and avoided words or phrases - audience — the target audience description - messaging_pillars — core themes and value propositions You can use individual fields from this response to dynamically apply the brand voice in your own content pipelines or AI workflows. ⚙️ Using Dynamic Field-Based Preview The API supports field-based filtering, so you can request only the specific voice attributes you need rather than retrieving the entire analysis object. Append a fields query parameter to your request to specify which fields to return. - Example: ?fields=tone,vocabulary,audience - This reduces payload size and speeds up integration, especially when embedding brand voice into real-time content generation tools. ⚠️ Common Issues and Fixes - 401 Unauthorized: Your API key is missing or incorrect. Double-check it in Settings → API Keys. - 404 Not Found: The Brand ID is wrong or the brand has been deleted. Re-confirm the ID from Brand Vault. - 403 Forbidden: Your account role may not have API access enabled. Contact your workspace admin to verify permissions. - Empty voice analysis fields: Brand Voice Analysis is generated after a brand profile is fully set up. Make sure the brand in Brand Vault has completed its onboarding and analysis steps. 💡 Best Practices - Store your API key as an environment variable — never hardcode it in your source code. - Cache Brand Voice Analysis responses if you query the same brand frequently to avoid unnecessary API calls. - Use the fields parameter to retrieve only what you need, keeping responses lightweight. - If you manage multiple brands (like an agency), loop through your brands list endpoint to batch-retrieve voice data for all clients. 🙋 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.

🔄 Brand Vault Refresh Cycle and Content Propagation

🗂️ Overview Brand Vault is Search Atlas's central source of truth for your brand information, tone, and guidelines. When you update or delete content inside Brand Vault, those changes do not take effect instantly across all AI-generated outputs. Understanding the refresh cycle helps you plan edits and set the right expectations for when new content will reflect your latest changes. ⏱️ How Often Does Brand Vault Refresh? Brand Vault operates on a periodic refresh cycle, not a real-time sync. After you make changes — including editing sections, deleting information, or adding new brand guidelines — the platform's backend indexing and crawling processes need time to re-ingest and propagate the updated content. - Typical refresh window: 3 to 4 days from the time changes are saved. - There is no manual trigger to force an immediate refresh. The process runs automatically in the background on a scheduled basis. - Until the refresh completes, AI-generated content such as queries run through Content Genius may still reference the previous version of your Brand Vault data, including sections you have already deleted. 🔍 Why Does Deleted Content Still Appear? When you delete a section in Brand Vault, the change is saved to your account immediately. However, the AI tools that generate content rely on an indexed snapshot of your Brand Vault data rather than reading it live at the moment of each query. This snapshot is rebuilt during each periodic refresh cycle. This means: - Deleted or edited content remains in the active snapshot until the next refresh completes. - Any content generated before the refresh will reflect the old snapshot, even if your edits were saved days prior. - Once the 3–4 day refresh window passes and the new snapshot is indexed, all subsequent AI outputs will use your updated Brand Vault information. 📍 Where to Find and Edit Brand Vault To review or update your Brand Vault content, navigate to: Header apps-grid icon → More Features → Brand Vault. All edits made here are queued for the next scheduled refresh cycle. ✅ Best Practices for Timing Your Updates To get the most predictable results from Brand Vault updates, follow these recommendations: 1. Make all edits in one session. Consolidate your Brand Vault changes rather than making incremental edits across multiple days. This reduces the risk of partial data being indexed mid-cycle. 2. Plan for a 3–4 day lead time. If you are preparing for a new campaign or major content push, update Brand Vault at least four days before you intend to generate content. 3. Avoid generating critical content immediately after edits. If you run a query in Content Genius right after updating Brand Vault, the output will still reflect the previous snapshot. Wait for the refresh window to pass first. 4. Review generated content manually in the short term. During the refresh window, check AI-generated outputs against your latest Brand Vault changes and manually remove or adjust any outdated information that has carried over. 5. Keep a record of your edit dates. Noting when you made key changes helps you calculate when the refresh is likely to complete and when it is safe to rely fully on new AI outputs. 🧩 How the Backend Indexing Process Works When Brand Vault data is refreshed, the platform performs a background crawl and re-indexing of all stored brand content. This process ensures that guidelines, tone, deleted sections, and new additions are accurately captured in the snapshot used by AI tools like Content Genius. Because this crawl covers your entire Brand Vault — not just the sections you changed — it takes time to complete thoroughly and consistently across the platform. This design prioritises accuracy and consistency in AI outputs over real-time propagation. A fully indexed snapshot produces more reliable, on-brand content than a live read that could capture a Brand Vault in a partially edited state. 💬 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.

🛠️ Connect Shopify via Cloudflare Worker to Search Atlas

🔍 Overview If your Shopify store uses Cloudflare as a proxy (for example, a custom domain pointed through Cloudflare), you cannot install Search Atlas using the standard Shopify app method alone. Instead, you need to deploy a Cloudflare Worker that intercepts requests and injects the Search Atlas script before pages are served to visitors. This guide walks you through the full setup. ⚙️ How It Works When a visitor lands on your Shopify store, the request passes through Cloudflare before reaching Shopify's servers. A Cloudflare Worker sits in that path and can modify the HTML response — in this case, injecting the Search Atlas tracking and optimization script into every page automatically. This ensures Search Atlas receives accurate data and can serve optimized content without modifying your Shopify theme manually. ✅ Before You Begin Make sure you have the following ready before starting: - Access to your Cloudflare account with the zone for your Shopify domain - Your Search Atlas project created and your site added inside the Search Atlas platform - Your Search Atlas script snippet — available inside your project settings - A Cloudflare plan that supports Workers (the Free plan includes Workers) 🚀 Step 1 — Create a Cloudflare Worker 1. Log in to your Cloudflare dashboard. 2. Navigate to the Workers section of your account. 3. Create a new Worker and give it a recognizable name (for example, search-atlas-injector). 4. Save or deploy the Worker with a placeholder script — you will replace the script content in the next step. ✏️ Step 2 — Add the Worker Script Once your Worker is created, open its editor and replace the default script with logic that does the following: - Intercepts every incoming request to your Shopify domain. - Fetches the original HTML response from Shopify. - Injects your Search Atlas <script> tag (copied from your Search Atlas project settings) just before the closing </head> tag in the HTML. - Returns the modified HTML to the visitor with the original response headers preserved. Because the exact script depends on your specific Search Atlas project snippet and your Cloudflare Worker runtime version, our support team can provide you with a ready-to-paste Worker script tailored to your setup. To get it, please have the following ready when you reach out: - Your Shopify store domain (the custom domain routed through Cloudflare) - Your Search Atlas project name - Your Search Atlas script snippet (found in your project settings) - Your Cloudflare Workers plan (Free, Pro, etc.) 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.

🗑️ Deleting Files and Using Bulk Delete in Search Atlas

🔍 What Does Deleting a File Actually Do? When you delete a file inside Search Atlas, it is removed only from Search Atlas — specifically from the Media Library within the platform. Deleting a file here does not delete the image or asset from your live website, your hosting server, or any other platform. Your website content remains completely untouched. Think of the Search Atlas Media Library as a workspace for managing your local business media assets. Removing a file from this workspace simply clears it from your Search Atlas account. Nothing on your live site is affected. 📂 Where to Find Your Files All uploaded files are stored in the Media Library. To access it: 1. In the left sidebar, click Local. 2. Select Media Library from the sub-menu. Here you can view, manage, and delete individual or multiple files. 🗂️ How to Delete a Single File 1. Navigate to Left sidebar → Local → Media Library. 2. Locate the file you want to remove. 3. Click the delete icon (trash can) associated with that file. 4. Confirm the deletion when prompted. The file will be removed from your Search Atlas Media Library immediately. Your website is not affected. ✅ How to Delete Multiple Files at Once Search Atlas supports bulk deletion so you can clean up your Media Library efficiently without removing files one by one. 1. Navigate to Left sidebar → GBP Projects → Media Library. 2. Select the files you want to delete by clicking the checkbox next to each file. To select all visible files at once, use the Select All checkbox at the top of the list. 3. Once your files are selected, click the Delete Selected button that appears. 4. Confirm the bulk deletion when prompted. All selected files will be removed from your Search Atlas account. No changes will be made to your live website. ⚠️ Important Things to Know Before You Delete - Deletions are permanent within Search Atlas. Once a file is removed from the Media Library, it cannot be recovered from within the platform. Make sure you no longer need the file before confirming. - Your website stays safe. Deleting files in Search Atlas does not remove any content from your live website or hosting environment. - Bulk delete applies only to selected files. Only files you have checked will be removed — unselected files are never affected. - Re-uploading is always possible. If you delete a file by mistake, you can re-upload it to the Media Library at any time. 💡 Best Practices for Managing Your Media Library - Regularly review your Media Library and remove outdated or unused assets to keep it organised. - Use bulk delete when cleaning up after a campaign or replacing a large set of images. - Before deleting, confirm the file is no longer needed in any active posts or tasks within the platform. 🛠️ 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.

🔗 Site Audit API Integration via Make.com with Dynamic Report Retrieval

Overview This article explains how to integrate the Search Atlas Site Audit API with Make.com (formerly Integromat) so you can automate site audit workflows and retrieve reports dynamically without logging into the platform manually each time. What You Will Need - An active Search Atlas account with Site Audit access - Your Search Atlas API key (found in Avatar Menu (👤) → Settings → API Keys) - A Make.com account - The project ID or project name for the site audit you want to retrieve Step 1: Locate Your API Key and Project ID 1. Log in to Search Atlas and navigate to Avatar Menu (👤) → Settings → API Keys. 2. Copy your API key from the API Keys page. 3. Open the Site Audit tool and open the project you want to automate. Note the project ID — you will need this when configuring your Make.com scenario. Step 2: Set Up an HTTP Request Module in Make.com 1. Log in to Make.com and create a new scenario. 2. Add an HTTP request module as your action step. 3. Set the appropriate request method for the endpoint you are calling — refer to the Search Atlas API documentation for the correct method and endpoint URL. 4. Enter the Site Audit API endpoint URL, including your project ID as a parameter. 5. In the Headers section, add your API key in the format specified by the Search Atlas API documentation. Step 3: Parse and Use the Report Data 1. After the HTTP module runs, add a module to parse the JSON response and extract the audit report fields you need. 2. Map the parsed data to any downstream modules in your scenario — for example, to log results or notify your team when an audit completes. 3. Optionally, configure a schedule trigger in Make.com to run the scenario automatically at your preferred interval. Need Help with Specific Details? Because API endpoint names, required parameters, and authentication formats may change, always refer to the official Search Atlas API documentation for the most accurate and up-to-date instructions. If you encounter an error, note the exact error message, your project ID, and the endpoint you are calling — this information will help our team assist you quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Disconnect Your Google Ads Integration

🔍 Overview If you no longer want Search Atlas to access your Google Ads account, you can disconnect the integration at any time. Removing the connection stops Search Atlas from syncing your Google Ads data and prevents any further actions being taken on your behalf. This guide walks you through the exact steps to do so. ⚙️ Before You Disconnect Keep the following in mind before removing your Google Ads integration: - Active campaigns will not be paused or deleted — disconnecting only removes Search Atlas's access; your Google Ads campaigns continue running in Google independently. - OTTO PPC features will stop working — any automation or optimisation tasks powered by the Google Ads connection will no longer function after disconnection. - You can reconnect at any time — simply go through the Google Ads connection flow again when you are ready. 🛠️ How to Disconnect Google Ads 1. Log in to your Search Atlas account. 2. Click on your account avatar or Avatar Menu (👤) in the top-right corner of the platform. 3. Navigate to Settings. 4. Select the Integrations section from the settings menu. 5. Locate the Google Ads integration card. 6. Click the Disconnect button next to the Google Ads connection. 7. A confirmation prompt will appear — review the message and click Confirm to complete the disconnection. Once confirmed, Search Atlas will immediately revoke its access to your Google Ads account. The integration card will update to show a disconnected status. 🔐 Revoke Access in Google as Well (Recommended) Disconnecting from within Search Atlas removes access on our side. For a complete removal, we recommend also revoking the Search Atlas app permission directly in your Google account: 1. Go to myaccount.google.com. 2. Select Security from the left-hand menu. 3. Scroll to Third-party apps with account access and click Manage third-party access. 4. Find Search Atlas in the list and click Remove access. This ensures no residual permissions remain on Google's side. ❓ Frequently Asked Questions - Will disconnecting delete my Google Ads data inside Search Atlas? — Historical data already synced may be retained in your account for reporting purposes, but no new data will be pulled after disconnection. - Will my Google Ads campaigns be affected? — No. Your campaigns, ad groups, and budgets remain completely unchanged inside Google Ads. - Can I reconnect a different Google Ads account? — Yes. After disconnecting, you can connect any Google Ads account by returning to the Integrations settings and following the connection flow. - I don't see a Disconnect button — what should I do? — Ensure you have the correct user permissions in Search Atlas. Only account owners or admins can manage integrations. If the button is still missing, contact support via the chat widget. 💬 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. Additional Notes 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.

🔍 Rank Math and OTTO SEO Schema Compatibility

🧩 Can Rank Math and Search Atlas Work Together? Yes — Rank Math and Search Atlas are compatible and can run on the same WordPress site at the same time. Search Atlas does not require you to uninstall Rank Math. However, when OTTO SEO deploys schema markup on your site, it can conflict with schema that Rank Math is also generating for the same pages. Running duplicate schema can confuse search engines and reduce the effectiveness of your structured data. The good news is that this conflict is easy to resolve by disabling Rank Math's schema output while keeping all other Rank Math features active. ⚙️ How to Prevent Schema Conflicts with OTTO SEO To avoid duplicate schema output, disable Rank Math's built-in schema module while keeping everything else active. This lets OTTO SEO take full ownership of structured data while Rank Math continues to handle meta tags, sitemaps, and other SEO features. 1. Log in to your WordPress dashboard. 2. Open the Rank Math plugin settings from the WordPress admin menu. 3. Locate the schema or structured data feature within Rank Math's module settings. 4. Disable that schema module. 5. Save your changes. Once the Rank Math schema module is disabled, OTTO SEO will be the sole source of structured data on your site. All other Rank Math features — including meta descriptions, Open Graph tags, and the sitemap — will continue to work normally. ✅ Quick Checklist: Rank Math + OTTO SEO Setup - Rank Math installed: No need to remove it — keep it active. - Rank Math schema module: Disable this to prevent duplicate structured data. - OTTO SEO schema: Enable and deploy through the OTTO SEO 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.

🌐 Connect Your Search Atlas Domain to Wix

🔍 Overview If you want your Search Atlas landing page to be accessible via a custom URL, you will need to complete two main tasks: update the URL slug inside Landing Page Studio and connect your domain so that it points to your landing page. This article explains what each task involves and what to prepare. Because the exact steps depend on your specific account configuration, contacting support is the recommended path to complete this setup correctly. ✏️ Step 1: Change Your Landing Page URL Slug The URL slug is the part of your web address that comes after your domain — for example, /brooklyn in yourdomain.com/brooklyn. 1. Log in to Search Atlas and open Landing Page Studio. 2. Select the landing page you want to update. 3. Look for the URL or slug setting within your landing page configuration options. 4. Enter your desired slug and save your changes. Note: If you cannot locate the URL slug setting, open the chat widget in the bottom-right corner of the platform and type human teammate — have your landing page name ready so the team can guide you directly to the correct location in your account. 🌍 Step 2: Connect Your Custom Domain To serve your Search Atlas landing page from your own domain, you need to connect that domain inside Search Atlas and update your DNS records with your domain registrar. 1. Log in to Search Atlas and go to your account settings to find the domain connection options. 2. Follow the on-screen instructions to add your domain — Search Atlas will provide the DNS record details you need to enter at your registrar. 3. Log in to your domain registrar (for example, GoDaddy, Namecheap, or Cloudflare) and navigate to your DNS Management section. 4. Add the DNS record exactly as provided by Search Atlas. 5. Save the record and allow time for DNS changes to propagate, then return to Search Atlas to verify the connection is active. If you are unsure which DNS records are required for your specific setup or cannot find the domain connection option in your account, contact support with your domain name and registrar details ready. ⚠️ Step 3: Understand Wix Subdomain Limitations If your Wix site is on a free Wix plan, your site URL follows the format username.wixsite.com/sitename. Wix does not allow third-party services to add DNS records pointing to free Wix subdomain URLs. This means: - You cannot connect a Search Atlas landing page directly to a free Wix subdomain URL. - To use a fully custom domain, you must own that domain and manage its DNS settings through your own domain registrar. If you are unsure whether your current setup supports a custom domain connection, or if you run into any errors during the process, the support team can review your account and walk you through the correct 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.

🌐 Wix Integration: Automatic vs. Manual SEO Implementation

🔍 Overview Search Atlas connects with Wix to help you optimize your site for search engines. However, due to limitations in the Wix platform itself, not all OTTO SEO suggestions can be applied automatically. This article explains what you should know about Wix integration limitations and how OTTO SEO credits work with your Wix site. ⚙️ How the Wix Integration Works When you connect your Wix site to Search Atlas, the integration allows our platform to read your site's structure, pages, and existing metadata. This enables our AI to analyze your content and generate targeted SEO suggestions. However, Wix operates on a closed, proprietary platform that restricts third-party tools — including Search Atlas — from directly writing changes back to your site in many cases. This means Search Atlas functions primarily as an analysis and recommendation engine for Wix sites, rather than a fully automated implementation tool. ✅ What May Be Applied Automatically on Wix Depending on your Wix site configuration and the page types involved, some SEO changes may be pushed automatically through the Search Atlas integration. Automatic implementation is subject to what Wix's API permits for your specific pages and account setup. If you are unsure whether automatic implementation is available for a specific page or field on your site, please reach out to our team for clarification before generating suggestions. ✏️ What May Require Manual Implementation on Wix Because of Wix's platform restrictions, many SEO changes cannot be applied automatically by Search Atlas. In these cases, Search Atlas provides you with the recommended changes, and you apply them directly inside your Wix Editor or Wix dashboard. The types of changes that may need to be made manually depend on how Wix exposes access for your particular site and page types. Our suggestions include instructions to help guide you through the process inside Wix. 💳 How OTTO SEO Credits Are Used If you have questions about how OTTO SEO credits are consumed in relation to the Wix integration — for example, when credits are charged and what actions they apply to — our support team can clarify this based on your specific plan and usage. Please reach out before generating a large batch of suggestions if you have concerns about credit consumption. 📋 What to Have Ready When You Contact Us To help our team assist you as quickly as possible, please have the following information ready: - Your Search Atlas project name or the URL of your Wix site - The specific page type you are working with (e.g., standard page, blog post, dynamic page) - A description of the suggestion or action you attempted and what happened - Any error messages you encountered, including exact wording 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: Audit Data Endpoint Reference

🧭 Overview The Search Atlas API lets you pull audit data programmatically using an MCP (Machine Client Protocol) token. This article explains how to locate your MCP token and where to find the official endpoint mapping for audit data categories such as Holistic SEO Pillars, AI Search Visibility, keywords, geo-distribution, and SERP features. 🔑 Step 1: Retrieve Your MCP Token Before calling any endpoint, you need a valid MCP token tied to your Search Atlas account. 1. Log in to your Search Atlas account. 2. Navigate to your account settings area, where API credentials and integrations are managed. 3. Locate the section for API token generation and copy your MCP token from there. 4. Store the token securely (for example, as an environment variable), as it is a sensitive credential. Your token must be included in every API request as a Bearer token in the Authorization header: Authorization: Bearer <your_mcp_token> If you cannot locate the token generation option in your account, or if your account does not yet have API access enabled, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with our team for assistance. 🗺️ Step 2: Find the Correct Endpoint and Field Mapping for Audit Data The specific endpoint paths and response field names for each audit data category (including Holistic SEO Pillars, AI Search Visibility, keyword data, geo-distribution, and SERP features) are documented in your account's official API reference. To access the correct and up-to-date mapping: - Log in to your Search Atlas account and look for an API Documentation or Developer Reference section within the platform. - Each audit category will have its own dedicated endpoint entry listing the path, required parameters (such as your project ID), and all available response fields. - Use your project ID (visible in the URL or project settings when a project is open) as the identifier when constructing API requests for a specific audit. If the API documentation section is not visible in your account, your plan may not include API access, or it may need to be enabled — open the chat widget in the bottom-right corner of the platform and type human teammate to confirm your access level with our team. ⚠️ Before You Escalate If you are experiencing an issue with API access or endpoint mapping, please have the following ready when contacting support: - Your Search Atlas account email or username - The name of the project you are trying to pull audit data for - The exact error message or response you are receiving (including any HTTP status codes) - The audit data category you are trying to access (e.g., Holistic SEO, AI Search Visibility) 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.

🗑️ Permanently Delete a Project in Search Atlas

🔍 Overview Deleting a project in Search Atlas permanently removes it and all associated data from your account. This action cannot be undone, so it is important to review what will be lost before proceeding. ⚠️ Before You Delete Keep the following in mind before permanently deleting a project: - All data is permanently lost. Tracked keywords, rank history, reports, and settings tied to the project will be deleted and cannot be recovered. - The action is irreversible. There is no archive or recycle bin — once deleted, the project is gone. - Consider alternatives. If you only need to pause tracking or free up a project slot temporarily, check whether pausing or reassigning the project is an option instead. 🗂️ How to Delete a Project To delete a project, navigate to your list of projects within Search Atlas. Locate the project you want to remove, open its settings or options menu, and look for the option to delete the project. You will typically be shown a confirmation prompt before the deletion is finalized — read the warning carefully before confirming, as the action cannot be undone. If you are looking to remove a Local (Google Business Profile) project, navigate to your Local or GBP projects section, find the relevant project, and follow the same process of accessing its options and selecting the delete action. If you are unsure where to find these options in the current version of the platform, our support team can walk you through the exact steps for your account. ✅ After Deletion Once a project is deleted, you will notice the following: - The project no longer appears in your project lists. - Any project slot previously used by the deleted project may become available for a new project, depending on your plan. - Historical data, tracked keywords, and reports for the deleted project are no longer accessible. 💬 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.

🔗 Search Atlas Integration Parity: Webflow vs Wix

🌐 Overview: Search Atlas and Website Platforms Search Atlas is a platform-agnostic SEO tool, meaning its core features work independently of whichever website builder you use. Whether your site is built on Webflow or Wix, you can connect it to Search Atlas and access the same suite of research, tracking, and reporting tools. That said, integration parity between Webflow and Wix is an important topic for customers managing multiple sites or considering a platform switch. This article explains what "integration" means in the context of Search Atlas, where feature coverage is consistent, and where minor differences may exist. 🔍 What "Integration" Means in Search Atlas Search Atlas does not require a plugin or app marketplace installation on your website builder. Integration primarily works in two ways: - Domain connection: You add your website's domain to Search Atlas, and the platform pulls in data from that domain — regardless of whether it is hosted on Webflow, Wix, or any other builder. - OTTO SEO: Search Atlas's AI-powered SEO automation tool, OTTO, can connect to your site to apply on-page optimisations. The method of connection and the depth of on-page access may vary depending on the platform. 📊 Features That Work Identically on Both Platforms The vast majority of Search Atlas features are data-driven and require only your domain URL, making them fully consistent across Webflow and Wix sites. These include: - Site Explorer: Accessible via Left sidebar → Site Metrics (Site Explorer), this section provides full keyword and competitive data for any domain, including Webflow and Wix sites. - Keyword Magic: Navigate to Left sidebar → Keywords → Keyword Magic to research keywords for your site regardless of platform. - Rank Tracker: Track keyword rankings for Webflow or Wix domains under Left sidebar → Keywords → Rank Tracker. - Keyword Gap: Compare your site's keyword coverage against competitors at Left sidebar → Keywords → Keyword Gap — works with any domain. - Local SEO tools: All features under Left sidebar → Local → GBP Projects — including Overview, Media Library, My Tasks, Posts, Reviews, and Local Citations — are platform-independent and function identically for Webflow and Wix sites. ⚙️ Where Platform Differences May Occur While research and reporting features are fully consistent, on-page automation through OTTO SEO can behave differently depending on how much access each website platform grants to external tools. - Wix: Wix provides structured access through its ecosystem, which allows OTTO to interact with on-page elements more directly in supported configurations. - Webflow: Webflow's architecture gives developers greater control over site structure. OTTO's integration capabilities with Webflow depend on how the site is set up, and some automation actions may require manual implementation of OTTO's recommendations rather than automated application. In practical terms, this means the recommendations OTTO generates are identical for both platforms, but how those recommendations are applied to your site may differ based on what each platform allows. ✅ Best Practices for Both Platforms 1. Connect your domain in Search Atlas by adding your Webflow or Wix site URL to your project. 2. Use Site Explorer and Rank Tracker to monitor performance — these work fully and equally on both platforms. 3. Review OTTO SEO recommendations carefully. For Webflow sites, plan to implement some suggestions manually within the Webflow editor if automated application is not available for your setup. 4. Use the Local → GBP Projects section for any local SEO work — all tools here are platform-independent. 🛠️ Staying Up to Date on Integration Changes Search Atlas actively develops and expands its integration capabilities. Feature parity between platforms is a priority for the product team, and improvements are rolled out regularly. Check the Search Atlas changelog or in-app announcements for the latest updates on OTTO and platform integrations. 💬 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.

📥 Export OTTO AI Suggestions for Webflow Integration

🔍 Overview When you deploy title, meta, or on-page suggestions through OTTO, Search Atlas keeps a record of every accepted change. If you manage your site in Webflow or another external CMS, you can export these deployed suggestions as a reference file — so you always have an accurate, up-to-date record of what was applied and can update your pages directly. This article explains how to locate and download your deployed AI suggestions from the OTTO project dashboard. 🧭 Before You Begin Make sure you have at least one active OTTO project with deployed suggestions. If your project shows no deployed items, the export will be empty. You can confirm deployment status by reviewing your suggestions list inside the project. 📋 How to Export Your Deployed AI Suggestions 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) to open your project dashboard. 2. Locate the project you want to export from within your project list. 3. Look for the export or download option associated with that project. The exact label or icon may vary depending on your account view — look for a download or export control near the project entry. 4. Click the export control. Search Atlas will generate and download a file containing your AI Suggestions record for that project. 5. Open the downloaded file. It contains your suggestion data — including deployed titles, meta descriptions, and other on-page recommendations — formatted for easy reference. 6. Use this file as your source of truth when updating pages directly inside Webflow or any other external CMS. 📂 What the Export May Include - Page URLs — the exact pages OTTO generated suggestions for - Suggestion type — for example, title tag, meta description, heading - Suggested content — the AI-generated text that was accepted and deployed - Deployment status — confirms which suggestions were applied This gives you a portable record you can hand off to a developer, import into a spreadsheet, or reference while making edits inside Webflow. 💡 Tips for Webflow Users - Run your export after each OTTO optimization session so your Webflow pages stay in sync with the latest deployed suggestions. - If you manage multiple sites, repeat these steps for each project separately. Each project has its own export. - If you cannot locate the export option in your dashboard, a member of our team can walk you through the exact steps for your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📝 Post Blogs to Your Webflow Site from Search Atlas

🌐 Webflow vs. Website Studio: Know the Difference Search Atlas supports two distinct publishing workflows. It is important to identify which one applies to your site before you begin. - Native Webflow sites — Sites built and hosted directly on Webflow (for example, aidquest.com). Content is managed inside the Webflow CMS and published through the Webflow editor or API. - Website Studio sites — Sites built using Search Atlas's own Website Studio builder. These use a one-click deployment workflow managed entirely within Search Atlas. This workflow does not apply to native Webflow sites. If your site was created on Webflow and you are simply using Search Atlas to generate content, follow the steps in this article. Do not use the Website Studio deployment instructions, as they are unrelated to your setup. ✅ Step 1: Ensure Your Webflow Site Has a Blog Collection Set Up Before you can publish any blog posts, your Webflow site must have a CMS Collection configured for blog content. If you have not done this yet, set one up inside your Webflow account by following Webflow's official documentation. You will need a collection with fields for your post content, and a collection page template so that each post has a live URL on your site. You only need to complete this setup once. Once the collection exists, you can add new posts at any time without repeating this process. ✍️ Step 2: Generate Your Blog Content in Search Atlas Use the content generation tools in Search Atlas to create your blog article. Once your article is complete, review and finalise all edits directly within Search Atlas before transferring the content to Webflow. 🔁 Step 3: Transfer Content to Webflow CMS Search Atlas does not currently offer a direct one-click publish integration with native Webflow CMS collections. Once your content is ready in Search Atlas, you will need to copy it and paste it into the appropriate fields within your Webflow CMS collection item, then publish from within Webflow. If you are unsure how to add items to your Webflow CMS collection, refer to Webflow's official help documentation for guidance specific to your site setup. 📌 Need Help With This Workflow? Because the exact steps for connecting Search Atlas content to a native Webflow site can vary depending on your Webflow setup, our support team can help you identify the right approach for your specific configuration. Please have the following ready when you reach out: - Your Webflow site URL - A description of how your blog collection is currently structured in Webflow (or whether one exists yet) - The specific step or action where you are getting stuck 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 Pixel Plugin vs Script Installation Guide

🧭 Overview The Otto pixel connects your website to Search Atlas so Otto can track performance and automate SEO tasks. There are two ways to install it: the WordPress plugin method and the script-based method. While the plugin is the quickest option, it can conflict with certain WordPress themes and plugins — most commonly causing issues on checkout pages. This article explains both methods, their limitations, and how to switch to the script method if you experience issues. ⚠️ Why the Plugin Method Can Cause Conflicts The Otto WordPress plugin injects the tracking pixel by hooking into WordPress's loading sequence. On some sites this can interfere with other plugins or theme scripts, particularly on checkout pages. Common symptoms include: - Checkout page failing to load or displaying incorrectly - Page elements breaking or becoming unresponsive after plugin activation If you activated the Otto pixel plugin and immediately noticed issues on your checkout page, the plugin method is likely conflicting with your existing setup. The fix is to switch to the script-based installation. ✅ Which Installation Method Should You Use? Use the following guidance to choose the right method for your site: - Plugin method — Suitable for simple WordPress sites with few third-party plugins and no custom checkout flow. - Script method — Recommended for sites with complex checkout pages or any site where the plugin method causes visual or functional issues. When in doubt, the script method is the safer and more universally compatible choice. It gives you more direct control over where and how the pixel loads, which can prevent conflicts with other scripts on the page. 🛠️ How to Switch to the Script Installation Method 1. Log in to Search Atlas and locate your unique Otto pixel script from within the platform. Your pixel script will be a short JavaScript snippet associated with your account. 2. Return to your WordPress dashboard and deactivate the Otto pixel plugin under Plugins → Installed Plugins. Do not delete it yet — wait until you confirm the script method is working. 3. Paste the Otto pixel script into your site's <head> section. You can do this using your theme's built-in header settings or a script management plugin that allows you to insert code into the page head. 4. Save your changes and reload your checkout page to confirm the conflict is resolved and the pixel is loading correctly. If you are unsure where to find your Otto pixel script in the platform, or if you need help identifying the right place to paste it in your WordPress setup, our support team can guide you through the process. 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 OTTO Pixel on Your Shopify Theme

🔍 What Is the OTTO Pixel? The OTTO Pixel is a small tracking snippet that connects your Shopify store to OTTO SEO inside Search Atlas. Installing it allows OTTO to read your site's data, identify SEO opportunities, and deploy optimisations directly to your pages. 📍 Where to Find Your OTTO Pixel Code The OTTO Pixel code is located inside the OTTO SEO section of your Search Atlas dashboard. Follow these steps to locate it: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. The URL will change to /seo-automation-v3. 3. If you have not yet activated OTTO for your site, you will be prompted to set up a new OTTO session. Complete the setup steps to reach your OTTO dashboard. 4. Once inside your OTTO dashboard, look for the Pixel Installation or Connect Your Site option. Your unique Pixel code snippet will be displayed here. 5. Click Copy to copy the full snippet to your clipboard. 🛒 How to Add the OTTO Pixel to Your Shopify Theme Once you have copied your Pixel code, follow these steps to install it on your Shopify store: 1. Log in to your Shopify Admin at your-store.myshopify.com/admin. 2. In the left sidebar, go to Online Store → Themes. 3. Next to your active theme, click the three-dot menu (⋯) and select Edit code. 4. In the file explorer on the left, open the Layout folder and click theme.liquid. 5. Locate the closing </head> tag in the file. Paste your OTTO Pixel snippet immediately before this tag. 6. Click Save in the top-right corner. The Pixel is now live on every page of your Shopify store. OTTO will begin collecting data within a few minutes. ✅ How to Verify the Pixel Is Working After installation, return to your OTTO dashboard in Search Atlas. You should see one of the following: - A green status indicator or "Pixel Detected" confirmation message. - Site data beginning to populate in your OTTO dashboard within 5–10 minutes. If the status still shows as undetected after 10 minutes, double-check that you saved the theme.liquid file and that the snippet was pasted before the closing </head> tag, not after it. ⚠️ Common Issues and Quick Fixes - Cannot find the Pixel code: Make sure you have completed the OTTO onboarding flow inside OTTO SEO. The Pixel code only appears after a site session has been created. - Editing the wrong theme: Ensure you are editing your active (published) theme, not a draft or unpublished theme. - Changes not saving: Shopify may time out after periods of inactivity. Re-open theme.liquid, paste the snippet again, and save immediately. - Pixel not detected after installation: Clear your browser cache, reload the Search Atlas dashboard, and wait a few more minutes for the signal to register. 💬 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 Integration with Google Tag Manager: React + Vite Setup Guide

Overview Otto, Search Atlas's OTTO SEO automation bot, can be connected to your website through Google Tag Manager (GTM) instead of a direct script embed. This approach works well for React + Vite sites — such as political candidate websites — where modifying the base HTML manually can be complex. Step 1: Retrieve Your Otto Script Snippet Log in to your Search Atlas account and navigate to your project. Locate your unique Otto script snippet within your project settings — copy the full script tag, including the opening and closing <script> tags. Step 2: Install the GTM Container in Your React + Vite Project If you have not already done so, install your GTM container snippet in your React + Vite project. Place the GTM container snippet in the <head> section of your site's base HTML file, and the GTM <noscript> snippet immediately after the opening <body> tag. Save and redeploy your project so the changes take effect. Step 3: Add Otto as a Custom HTML Tag in GTM Once GTM is live on your site, create a new tag to inject the Otto script: 1. Open Google Tag Manager and select your container. 2. Click Tags in the left menu, then click New. 3. Under Tag Configuration, choose Custom HTML. 4. Paste your Otto script snippet into the HTML field. 5. Under Triggering, select All Pages (or your preferred trigger) so Otto fires on every page load. 6. Name the tag (e.g., Otto – Search Atlas) and click Save. Step 4: Publish Your GTM Container After saving your tag and triggers, click Submit in GTM to publish the container. Without publishing, your changes will not be live on the website. Step 5: Confirm Otto Is Running After publishing, return to your Search Atlas project and confirm that Otto is active. If you are unsure whether Otto is crawling your site correctly after the GTM setup, reach out to the support team for confirmation. 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.

Brand Voice Analysis API Reference for Developers

Overview Search Atlas supports programmatic access to Brand Voice Analysis data stored in your Brand Vault via the Search Atlas API. This is useful for integrating voice guidelines into your own tools, automating content workflows, or pulling analysis results into external platforms. This article covers what you need to get started, including authentication, what to have ready, and how to reach our team for confirmed endpoint details specific to your account configuration. Authentication All Search Atlas API requests require authentication via a Bearer token. To locate or manage your API credentials, log in to Search Atlas, click your Avatar (top-right), then go to Settings → API Keys / Integrations to find your API key. If you are unable to locate your API key, our team can walk you through generating one. What to Prepare Before Making API Requests To successfully integrate Brand Voice Analysis data into your workflows, gather the following before you begin or before reaching out for support: - Your API key — retrieved from your Search Atlas account Settings as described above - Your Search Atlas account email or workspace name - The name or ID of the Brand Vault you want to access programmatically — you can find this by opening the Brand Vault inside the platform and noting the name you assigned it - Your intended use case — for example, pulling data into an external tool, automating a content workflow, or building a direct integration - Any error messages or HTTP status codes you have already encountered, if applicable - The programming language or HTTP client you are using (for example: Python, Node.js, cURL) How API Requests Are Structured When making requests to the Search Atlas API for Brand Voice Analysis data, follow these general steps: 1. Include your API key as a Bearer token in the Authorization header of every request. 2. Target the Brand Voice Analysis endpoint associated with your specific Brand Vault. Because exact endpoint paths depend on your account configuration and may be updated, confirm the current endpoint path with our team before building your integration. 3. Submit a GET request (or the request method confirmed for your endpoint) and parse the JSON response, which will contain the Brand Voice Analysis fields associated with your Brand Vault. 4. If you receive an HTTP error (such as 401 Unauthorized or 404 Not Found), verify that your API key is valid and that the Brand Vault name or ID in your request matches what is configured in your account. Common Issues and How to Resolve Them - 401 Unauthorized: Your Bearer token is missing, expired, or incorrect. Regenerate your API key in Settings and update your request headers. - 404 Not Found: The Brand Vault identifier in your request does not match any vault in your account. Double-check the name or ID against what is shown in the platform. - Empty or unexpected response: Confirm that Brand Voice Analysis has been run for the Brand Vault you are querying. If no analysis exists yet, run it from within the platform first, then retry your API request. Next Steps If you need the confirmed endpoint path, full request format, or complete response schema for your specific account, our team can provide verified technical documentation. Have your account email, Brand Vault name, use case, and any error messages ready to speed up the process. 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 OTTO from WordPress to Wix

🧭 Overview If you have moved your website from WordPress to Wix, you can transfer OTTO to your new site by deactivating the WordPress plugin and installing OTTO on Wix. This process does not create a new OTTO session and does not incur any additional charges, provided you are migrating to the same URL. ⚠️ Before You Begin - Make sure your Wix site is live and accessible at its final URL. - Have access to your WordPress admin dashboard and your Wix account. - Log in to your Search Atlas account at app.searchatlas.com. 🔌 Step 1: Deactivate the Search Atlas Plugin on WordPress 1. Log in to your WordPress admin dashboard. 2. In the left sidebar, go to Plugins → Installed Plugins. 3. Find the Search Atlas plugin in the list (menu Search Atlas → Settings). 4. Click Deactivate beneath the plugin name. 5. Once deactivated, click Delete to fully remove the plugin from your WordPress site. Deactivating and deleting the plugin removes OTTO's connection to your WordPress site and stops the pixel from loading on those pages. 🗑️ Step 2: Remove the OTTO Pixel from WordPress (If Added Manually) If you added the OTTO pixel to your WordPress site manually — for example, through a header script plugin or your theme's custom code area — you must also remove that script. 1. In your WordPress admin dashboard, navigate to the location where you inserted the OTTO pixel code (for example, Appearance → Theme File Editor or your header/footer plugin settings). 2. Locate the OTTO pixel script tag. 3. Delete the script and save your changes. If you are unsure where the pixel was added, search your theme files or any active header/footer plugins for the OTTO script snippet. 🌐 Step 3: Install OTTO on Your Wix Site 1. Log in to your Wix account and open your site's dashboard. 2. Follow the Wix-specific OTTO installation steps to add the OTTO pixel to your Wix site. Search Atlas provides a dedicated video walkthrough for this — see the Wix Installation Video linked in your Search Atlas dashboard under OTTO SEO → All Sites (SEO Automation). 3. After installing the pixel, return to your Search Atlas dashboard and navigate to OTTO SEO → All Sites (SEO Automation). 4. Confirm that OTTO is connected and actively running on your Wix site by verifying the site URL shown in the OTTO panel matches your Wix domain. 💰 No Additional Charges for Same-URL Migrations If your Wix site uses the same URL as your previous WordPress site, you will not be charged again for OTTO. Your existing OTTO session transfers to the new site automatically once the pixel is correctly installed on Wix and the old WordPress connection is removed. If your Wix site is on a different URL than your WordPress site, a new OTTO session will be required. Contact support via the chat widget if you are unsure whether your migration qualifies. ✅ Verify OTTO Is Working on Wix 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation). 2. Check that the connected site URL reflects your Wix domain. 3. Confirm the OTTO status indicator shows as active or connected. 4. Visit your live Wix site and use your browser's developer tools (Right-click → Inspect → Network tab) to confirm the OTTO pixel is firing correctly. 🛠️ Troubleshooting - OTTO still shows as connected to WordPress: Ensure you have fully deleted the Search Atlas plugin and removed any manually added pixel scripts from WordPress. - OTTO is not connecting on Wix: Double-check that the pixel code was pasted into the correct location in Wix. Refer to the Wix installation video for exact placement instructions. - Unsure whether your URL qualifies for a no-charge migration: Reach out via the chat widget before making changes so our team can confirm your eligibility. 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 CMS Integration and Content Deployment Guide

What Is OTTO CMS Integration? OTTO SEO can connect directly to your website's CMS (Content Management System), allowing it to read your existing pages and push SEO changes — such as updated page titles, meta descriptions, and on-page content — without requiring you to manually copy and paste anything. This makes implementing SEO recommendations faster and significantly reduces room for human error. Supported CMS Platforms OTTO supports direct integration with a range of CMS platforms, enabling it to read your pages and apply SEO recommendations automatically. The specific platforms supported may vary depending on your account configuration and the current state of OTTO's integrations. If you are unsure whether your CMS is supported, or if you cannot locate the integration option within your project settings, please reach out to our support team who can confirm compatibility for your setup. Connecting Your CMS to OTTO To connect your CMS, navigate to Avatar Menu (👤) → Settings → CMS Connectors within Search Atlas. From there, you can select your CMS platform and follow the authentication steps to grant OTTO the access it needs. Once connected, OTTO will be able to surface recommendations tied directly to your live pages. If you do not see your CMS listed or encounter any issues during the connection process, our support team can assist you directly. Deploying SEO Changes Once your CMS is connected, you can review and approve OTTO's recommendations from within Search Atlas and push them directly to your site without leaving the platform. Always review changes before deploying — while OTTO's suggestions are data-driven, you remain in full control of what gets published. Applying SEO Changes Manually (Unsupported CMS) If your CMS is not yet supported for direct integration, you can still use OTTO's on-page recommendations and apply them manually within your CMS. View the recommendations generated for your site inside Search Atlas, then implement each suggested change (such as updated page titles or meta descriptions) directly in your CMS's editing interface. If you are unsure how to locate a specific recommendation or how to apply it in your CMS, our support team can walk you through the process. 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.

☁️ Create Cloud Stacks Using OTTO Knowledge Bases

🔍 Overview Cloud stacks let you publish authoritative, interlinked content across the web to strengthen your domain's authority signals. When you create a cloud stack inside an OTTO project, you can power the content with that project's existing knowledge base — keeping everything relevant and on-brand. This article explains what you need to know before contacting our team for guided assistance with this workflow. 🧭 Before You Begin Make sure the following conditions are met before you start: - You have an active OTTO project set up inside Search Atlas. - That OTTO project already has a knowledge base created and populated with your business information. - You have access to the Cloud Stacks section within Search Atlas. 🛠️ Creating a Cloud Stack Within an OTTO Project Creating a cloud stack that uses an OTTO project's knowledge base involves navigating to the Cloud Stacks section of Search Atlas and associating the cloud stack with your chosen OTTO project so that the project's knowledge base powers the generated content. Because the exact steps and available options in this workflow depend on your account configuration and the current state of the platform, our support team can walk you through the process in real time and confirm the correct settings for your specific setup. 📋 What to Have Ready When You Reach Out To get the fastest help, please have the following information on hand before contacting support: - The name of the OTTO project you want to use for the cloud stack. - Confirmation that the knowledge base for that project has been created and populated. - A description of where in the workflow you are getting stuck or have a question (for example, project selection, content settings, or any error messages you see). - Any exact error messages displayed on screen, including timestamps if available. 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 Gmail and Set Up Google Ads Integration

📋 Overview Connecting a Gmail account to Search Atlas allows you to link your Google Ads data directly to the platform. This enables you to view ad performance alongside your organic SEO metrics in one place. The process is completed through the Integrations section inside Search Atlas settings and requires a Google account with access to the Google Ads account you want to connect. 🔑 Before You Begin - Make sure you are logged in to Search Atlas. - Have the Gmail address ready that is associated with your Google Ads account. - Confirm that your Google account has access to the Google Ads account you want to connect. Read-only access is sufficient to view data, but Standard or Admin access is required for Search Atlas to make changes to campaigns. - If you are connecting a new Gmail account that does not yet have a Google Ads account, you will need to create one at ads.google.com first before completing this setup. 🛠️ Step 1 — Open Integrations in Settings 1. Log in to your Search Atlas account. 2. Navigate to Settings using the Avatar Menu (👤) in the top-right corner of the platform. 3. In the Settings menu, navigate to the Integrations section. 📧 Step 2 — Add Your Gmail Account 1. Inside the Integrations section, locate the Google integration area. 2. Look for the option to connect or add a Google account and click it. 3. Follow the Google authentication flow to sign in with the Gmail account you want to connect and grant the necessary permissions. 4. Once authentication is complete, you will be returned to the Integrations section. Your connected Gmail address should now appear under the Google integration. 📊 Step 3 — Link Your Google Ads Account 1. Once your Gmail account is connected, Search Atlas will detect any Google Ads accounts associated with that Gmail address. 2. Follow any on-screen prompts to complete linking the Google Ads account to your Search Atlas workspace. ✅ Step 4 — Verify the Connection 1. After completing setup, return to the Integrations section to confirm that your Google account appears as connected. 2. Navigate to the relevant section of Search Atlas where Google Ads data is displayed to confirm that your campaign data is loading correctly. 3. It may take a few minutes for data to fully sync after a new connection is established. ➕ Connecting Multiple Gmail Accounts If you need to connect more than one Gmail account, return to the Integrations section and repeat the steps above for each additional account. Each connected Gmail address will appear separately under the Google integration. 🔧 If You Run Into Issues If you encounter any difficulty connecting your Gmail account or linking your Google Ads account, please have the following information ready before reaching out: the Gmail address you are trying to connect, any error message displayed on screen, and the step at which the process stopped or failed. 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.

🏷️ GTM-Compatible Dynamic Optimization Script Setup

Overview Search Atlas provides a dynamic optimization script that you can deploy through Google Tag Manager (GTM). In some cases, the script format used may not pass GTM's built-in validation, which can prevent you from publishing the tag. This article explains what to check and how to get assistance resolving GTM script validation issues. Why the Script May Fail GTM Validation GTM runs a syntax and security validation check on all Custom HTML tags before publishing. Depending on the script format provided, GTM's validation engine may flag the script and block publishing. If you encounter a validation error when attempting to publish a Custom HTML tag containing the Search Atlas dynamic optimization script, this is a known compatibility consideration that our team can help resolve. What to Try in GTM If you are experiencing GTM validation errors with your Search Atlas dynamic optimization script, try the following general troubleshooting steps: 1. Confirm you are using a Custom HTML tag type in GTM — other tag types may not support injected third-party scripts correctly. 2. Check that the script content you have pasted is complete and not truncated. 3. Ensure your trigger is configured (typically a Page View trigger on All Pages). 4. Click Save, then attempt to Submit again to republish. If the validation error persists after these checks, the specific script format you are using may need to be adjusted. Contact the Search Atlas support team with the details below so they can provide the correct script format for GTM. What to Have Ready When Escalating To help our team resolve your GTM validation issue quickly, please have the following information ready: - The exact error message displayed in GTM when validation fails. - The script content you are attempting to use (or a description of where you obtained it in your Search Atlas account). - Your GTM container ID. - The URL of the website where the script is being deployed. 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 Confirm Deployed Changes Reach Shopify

This article explains exactly what happens when you click deploy in Search Atlas, and how to confirm that your changes have actually been written to your Shopify store — not just saved within the platform. If you have been unable to locate the integration settings or are unsure whether your updates went live, the steps below will help you verify both. 🔍 Common Causes of Confusion - 'Deployed' within Search Atlas vs. live on Shopify: In Search Atlas, a 'deployed' status means the platform has sent the changes to your connected Shopify store. It does not simply mean the changes were saved or staged inside Search Atlas. However, the update only appears live on Shopify if the integration is active and authenticated correctly at the time of deployment. - Broken or disconnected integration: If the Shopify connection was disconnected, re-authenticated, or the access token expired after you deployed, the changes may show as deployed in Search Atlas but never reached Shopify. - Propagation delay: Shopify may take some time to reflect metadata or content changes after a successful push. 🛠️ Step-by-Step 1. Open your project settings in Search Atlas and navigate to the integrations or connected apps section for your site. Locate your Shopify connection and confirm its status is active and authenticated — if it shows any error or requires re-authentication, that is likely why your changes did not reach Shopify. 2. If the connection requires re-authentication, reconnect your Shopify store by following the on-screen prompts before attempting to deploy again. 3. Once the integration is confirmed active, return to the page or content item you deployed and review its current deployment status inside Search Atlas to determine whether the push completed successfully or encountered an error. 4. If a previous deployment shows a failed or partial status, re-deploy the affected pages or content items while the Shopify integration is confirmed active. 5. After deploying, allow some time for Shopify to process the incoming changes before checking the result. ✅ How to Confirm It Worked - Check Shopify directly: Log in to your Shopify admin, navigate to the affected product, page, or blog post, and confirm the updated title, meta description, or content is visible there. This is the definitive confirmation that the change reached Shopify — not the status inside Search Atlas alone. - Check the deployment status inside Search Atlas: The item should display a status indicating the deployment completed. A status that appears stuck or shows an error indicates the push did not complete successfully. - Visit the live URL: Open the published Shopify URL in a browser and verify the updated content appears as expected on the live page. 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.

🔗 Webflow CMS Dynamic Fields and Metadata Mapping

🌐 Overview When you connect Search Atlas to Webflow CMS, you can use dynamic field tokens to automatically populate your content fields and control how SEO metadata — title, description, and canonical URL — is written to your Webflow collection items at publish time. This article explains what is currently supported and what to expect during the mapping process. 📋 Dynamic Field Tokens and SEO Metadata Mapping Search Atlas supports dynamic tokens that can be inserted into mapped text fields and resolved automatically when content is published to Webflow CMS. These tokens cover core content values such as the article body (HTML), title, URL slug, featured image URL, and featured image alt text. At publish time, Search Atlas also maps SEO metadata — including the SEO title, meta description, and canonical URL — to the corresponding fields configured in your Webflow CMS collection. The canonical URL is typically constructed from your connected Webflow site domain combined with the resolved slug value. If you have additional Webflow CMS fields beyond those covered by the supported tokens, you may need to populate them manually inside Webflow after publishing, as not all custom fields can be dynamically resolved. 🛠️ If Your Field Mapping Is Not Working as Expected Webflow CMS field mapping and metadata behaviour is configured at the backend level and may require investigation by our team if something is not resolving correctly. If you are experiencing unexpected behaviour — such as SEO metadata not appearing in Webflow, tokens not resolving, or fields not populating on publish — please reach out so our team can review your specific setup. To help us investigate as quickly as possible, please have the following ready: - The name of the Webflow site and CMS collection you are publishing to - The specific field or token that is not behaving as expected - The exact error message or unexpected output you are seeing - A timestamp or example of a recent publish attempt that demonstrates the issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Upload Image Assets and Connect IndexNow in Search Atlas

Overview This article covers two common setup tasks in Search Atlas: uploading image assets to your Brand Vault and connecting IndexNow to submit URLs to Bing. Both steps help strengthen your brand presence and improve how quickly your content is discovered by search engines. How to Upload Image Assets to Brand Vault Brand Vault is your central hub for storing and managing brand-related assets, including logos, images, and other visual content. Uploading your image assets ensures Search Atlas can use them across reports, content, and brand monitoring features. To upload image assets to Brand Vault: 1. Log in to your Search Atlas account and navigate to Brand Vault via the apps-grid icon in the header → More Features → Brand Vault. 2. Inside Brand Vault, look for the image or asset upload area within the dashboard. 3. Use the upload option (or drag and drop your file) to select your image file(s) from your device. 4. Once the upload completes, your images will appear in the Brand Vault library and will be available across Search Atlas tools that reference brand data. Note: If you are unsure where the image upload area is located within Brand Vault, open the chat widget in the bottom-right corner of the platform and type human teammate — a member of our team can walk you through the exact steps for your account. Tip: Keep your brand images organised and up to date in Brand Vault to ensure consistency across all Search Atlas tools that pull brand data. How to Connect IndexNow for Bing IndexNow is a protocol that lets you instantly notify search engines like Bing when your content is published or updated. Connecting it through Search Atlas removes the wait for Bing to crawl your site organically. To set up IndexNow: 1. Log in to your Search Atlas account. 2. Navigate to Settings in the left-hand navigation menu. 3. Within Settings, look for the IndexNow or integrations area. 4. Follow the on-screen steps to connect IndexNow, entering your website domain when prompted. Before you start: Have your website domain ready, as you will need to enter it during the connection process. Note: If you cannot locate the IndexNow setup option within Settings, open the chat widget in the bottom-right corner of the platform and type human teammate — a member of our team can confirm the exact location for your account and plan. What Happens After Setup After completing both steps, your Search Atlas account will be connected to Bing for URL submission via the IndexNow protocol, and your Brand Vault will contain the image assets needed to power your brand features across the platform. 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.

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

📊 Site Explorer Exports and API Access by Plan

📋 Overview Search Atlas offers different levels of data access depending on your subscription plan. This article explains exactly which export formats and API features are available at each tier, so you can make the most of your Site Explorer data. 🗂️ Export Formats: CSV vs. PDF Site Explorer data can be exported in two formats, but availability depends on your plan: - PDF exports — Available on all plans, including Starter. Use PDF exports to save snapshots of your Site Explorer reports for sharing or archiving. - CSV exports — Available on Growth plans and above. CSV files give you raw, structured data you can manipulate in spreadsheets or import into other tools. If you are on the Starter plan and need CSV exports, consider upgrading to the Growth plan to unlock this feature. 🔌 API Access by Plan Tier API access allows you to pull Search Atlas data programmatically into your own tools, dashboards, or workflows. API access is available on every plan, including Starter — you do not need to upgrade to create an API key or call the API. Create your key in Settings → API Keys → Generate new key. 🧭 How to Export Site Explorer Data 1. In the left sidebar, click Site Metrics (Site Explorer) to open the Site Explorer section. 2. Select the site or report you want to export. 3. Click the Export button in the top-right area of the report. 4. Choose your preferred format — PDF (all plans) or CSV (Growth and above). 5. Your file will download automatically to your device. If the CSV option does not appear in your export menu, your current plan does not include CSV exports. 🔑 How to Access the API 1. Log in to your Search Atlas account. 2. Navigate to your Account Settings by clicking your Avatar Menu (👤) in the top-right corner. 3. Select API or Integrations from the settings menu. 4. Copy your unique API key and refer to the Search Atlas API documentation to get started. If the API section is not visible in your settings, your current plan does not include API access. 📊 Quick Plan Comparison - Starter — PDF exports only, no API access - Growth — CSV exports included, API access included - Pro and above — CSV exports included, API access included with higher quotas ⬆️ How to Upgrade Your Plan To unlock CSV exports or API access, you can upgrade your plan directly from your account: 1. Click your Avatar Menu (👤) in the top-right corner of the platform. 2. Go to Billing or Subscription. 3. Select the plan that meets your needs and follow the on-screen steps to upgrade. Changes take effect immediately after upgrading, so you can start exporting CSVs or using the API right away. 💬 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.

🔗 Mapping SEO Metadata to Webflow CMS Fields

🗺️ Overview When you publish SEO metadata from Search Atlas to a Webflow CMS collection, the values for title tag, meta description, and canonical URL are not written directly into Webflow's built-in SEO fields by default. Instead, Search Atlas maps these values to custom CMS collection fields that you define inside Webflow. This article explains how that mapping works and what you need to set up on both sides. ⚙️ How the Mapping Works Webflow CMS collections support custom text fields that you can create and name yourself. Search Atlas uses these custom fields as the target for SEO metadata sync. The mapping process has two parts: 1. You create dedicated custom fields in your Webflow CMS collection (for example, SEO Title, SEO Meta Description, and Canonical URL). 2. Search Atlas maps its output values to those fields during the sync, so the correct metadata is written into each field for every CMS item. Once the fields are mapped, any SEO metadata generated or approved inside Search Atlas is pushed directly into the matching Webflow CMS field for each page or collection item. 🛠️ Step 1 — Create Custom Fields in Webflow Before configuring the mapping in Search Atlas, make sure your Webflow CMS collection has the necessary fields. The general approach is: 1. Open your Webflow project and navigate to the CMS panel. 2. Select the collection you want to sync SEO metadata to. 3. Add a plain text field for each metadata type you want to manage: - A field for the SEO title (for example, named SEO Title or Meta Title). - A field for the meta description (for example, Meta Description). - A field for the canonical URL if you need canonical management (for example, Canonical URL). 4. Save your collection changes. Important: These are custom fields you create — they are separate from Webflow's native built-in SEO title and description fields that appear in the page settings panel. You must also connect these custom fields to the appropriate Webflow page template bindings if you want them rendered in the <head> of your live pages. 🔍 Step 2 — Configure the Field Mapping in Search Atlas Once your Webflow CMS fields are ready, you will need to configure the mapping inside Search Atlas so the platform knows which custom Webflow field corresponds to each metadata type (SEO title, meta description, and canonical URL). Because the exact navigation steps for this configuration depend on your account setup and the current state of the Webflow integration, we recommend contacting our support team to confirm the correct steps for your specific site and workflow. To get help completing the mapping configuration, please have the following ready when you reach out: - Your Webflow site name and the name of the CMS collection you are syncing. - The exact names of the custom fields you created in Step 1. - A description of any error messages or unexpected behavior you are seeing. 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.

🔗 Map CMS Connector IDs to Project Domains

🗺️ What Are CMS Connector IDs? When you connect a CMS (such as WordPress or another supported platform) to Search Atlas, the system assigns each connection a unique numeric Connector ID. Features like OTTO use these IDs internally to route SEO enhancements to the correct site. If you need to know which ID belongs to which domain, you will need to retrieve the correct account-specific mapping. ⚠️ Why This Can Be Confusing The platform may surface multiple numeric IDs in certain contexts, and some of these can belong to unrelated system-level projects rather than your own connected domains. This means you cannot always rely on an automatically generated list to be accurate without verification. 🛠️ How to Get Your Correct ID-to-Domain Mapping Because CMS Connector IDs are account-specific and must be retrieved from verified internal records, the recommended way to get an accurate mapping is to contact the Search Atlas support team. Our team can look up your account, identify each Connector ID, and provide you with the confirmed list — for example, in the format 1780 = valueinvestmentpartners.com, 1656 = webuynova.com, and so on for each connector in your account. 1. Gather the Connector IDs you need to map. Before reaching out, note down all the numeric IDs you have seen referenced in your account or in any OTTO setup instructions. 2. Contact the support team. Reach out and type human teammate to be connected with a member of our team. 3. Share your Connector IDs with the agent. Provide the list of IDs and ask for the confirmed domain mapping for your account. The agent will look up and verify each ID against your connected projects. 4. Save the mapping for future reference. Once you receive the confirmed list, keep a record of it. You can use this mapping whenever OTTO or another feature asks you to specify a Connector ID for a particular domain. 📋 How to Use the Mapping Once You Have It After you have your confirmed ID-to-domain list, you can reference it any time you need to direct OTTO SEO enhancements or other automation to a specific site. Simply match the numeric ID to the domain you want to target before submitting a configuration or scan request. This ensures changes are applied to the correct connected property. 🔍 Tips to Avoid Confusion - Always use the mapping provided directly by the support team rather than relying on IDs that appear in general system screens, as those may include unrelated project entries. - If you add or remove a CMS connection in the future, request an updated mapping to make sure your records stay accurate. - When setting up OTTO for a site, confirm the Connector ID before initiating a scan or enhancement run to prevent changes being applied to the wrong property. 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 Gmail to Digital PR Campaigns

Overview Search Atlas Digital PR campaigns support connecting an email account to send outreach emails. You can pick from a list of built-in email providers, or choose + Add a provider and enter SMTP and IMAP settings manually (host, port, and encryption: STARTTLS, SSL/TLS, or None). Custom providers use email and password login only (no OAuth), and the credentials are tested before the mailbox is linked. This article explains how to connect a Gmail account to your campaigns, though Gmail is not required. Supported Email Types - Gmail addresses ending in @gmail.com (personal Gmail accounts or Google Workspace accounts where Gmail powers the mailbox) - Other listed email providers - Any other email provider via the + Add a provider option, using manual SMTP and IMAP configuration If your business email is not Gmail-based, you can connect it by picking your provider from the list, or by choosing + Add a provider and entering your SMTP and IMAP settings manually. How to Connect Your Gmail Account 1. Navigate to the Digital PR Campaigns area of the platform. 2. Open an existing campaign or create a new one. 3. Locate the email account or sender connection section within the campaign settings. 4. Choose the option to connect or add a Gmail account. 5. A Google sign-in window will appear. Sign in with the Gmail address you want to use for outreach. 6. Grant Search Atlas the requested permissions to send email on your behalf. 7. Once authorised, your Gmail address will appear as the connected sender for that campaign. Once connected, you can monitor replies and track sent outreach emails from within the campaign or inbox area of the platform. Setting Up a Gmail Address for Business Outreach If you currently use a custom domain email for your business, the easiest approach is to create a dedicated Gmail account specifically for outreach — for example, yourbusiness.outreach@gmail.com. You can still reference your business name and branding in the email signature and display name within the campaign settings. Alternatively, if your organisation uses Google Workspace and your custom domain email is powered by Gmail (meaning you sign in through Google), that account may be supported. Try connecting it using your Google Workspace credentials during the Gmail connection step. If the account authenticates successfully, it can be used for Digital PR outreach. 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 Content via API to Your Loveable Site

Overview Search Atlas supports publishing content directly to your Loveable site via an API connection. This allows you to push AI-generated articles and optimized pages from Search Atlas straight to your live site without manually copying and pasting content. How to Publish Content to Your Loveable Site via API Loveable is a no-code website builder. Publishing content from Search Atlas to a Loveable site via API requires a specific configuration that depends on your Loveable project's setup. Because the exact steps vary based on how your Loveable project is configured, our support team can walk you through the process directly. To get the fastest resolution, please have the following ready before reaching out: - Your Loveable project name or URL - The type of backend connected to your Loveable project (if any) - Any API credentials or keys you have already generated for your project - A description of what you have tried so far and any error messages you have seen (including exact error text and timestamps) Troubleshooting Common Issues - Authentication errors: Double-check that your API key or access token is entered correctly and has not expired in your backend service. - Content not appearing: Verify that your Loveable project's backend is active and that the correct endpoint URL was used. - Publish attempt fails with no error: Note the exact timestamp of the failed attempt and any error codes shown, as this information will help our team diagnose the issue quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🔗 Connect Google Ads and Meta Ads Accounts

Overview To unlock Smart Ads features in Search Atlas, you must first connect your advertising accounts. Both Google Ads and Meta Ads are connected through the Integrations tab in your account settings. This article explains the general process for connecting both platforms. Before You Begin - To create and manage campaigns from Search Atlas, you need Standard or Admin access to the Google Ads account (read-only access cannot make changes), and admin access to the Meta Ads account you want to connect. - For Google Ads, ensure you are signed into the correct Google account in your browser before starting. - For Meta Ads, have your Facebook login credentials ready. - You can connect multiple ad accounts across both platforms. How to Connect Your Google Ads Account 1. Navigate to the Integrations tab in your Search Atlas account settings. 2. Locate the Google Ads section and initiate the connection. 3. A Google authentication window will appear. Sign in with the Google account that has access to your Google Ads account. 4. Grant the requested permissions when prompted. 5. Once authenticated, select the Google Ads account or manager account you want to link and complete the connection. Once connected, you can verify the connection status at any time by returning to the Integrations tab. How to Connect Your Meta Ads Account 1. From the Integrations tab, locate the Meta Ads section and initiate the connection. 2. A Meta (Facebook) login window will open. Enter your credentials and log in. 3. Review the permissions Search Atlas is requesting and approve them when prompted. 4. Select the Meta ad account you want to manage and complete the connection. Your Meta Ads account will then be linked and ready to use within Search Atlas's ad features. If You Run Into Issues If you are unable to connect your Google Ads or Meta Ads account, or if the Integrations tab is not behaving as expected, please reach out to our support team. Have the following ready to help us assist you faster: - The name or ID of the ad account you are trying to connect - The platform (Google Ads or Meta Ads) - A description of what happens when you attempt to connect (e.g., any error messages or unexpected behavior) 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.

📧 Email Provider Support for Outreach Campaigns

🔍 Overview Search Atlas has shipped multi-provider email support for outreach campaigns. This update expands the range of email providers that can be used when running outreach campaigns inside the platform. This article summarises what has changed and what you can expect from this feature update. ✅ What Changed Multi-provider email support for outreach campaigns is now available. This means users are no longer limited to a single email provider when connecting an account for outreach campaign sending. 🛠️ What You Can Do Right Now To take advantage of the expanded email provider support, navigate to the outreach campaigns area of the platform and follow the email connection prompts to connect your preferred email provider account. 📬 Need Help Getting Set Up? If you encounter any issues connecting your email provider or setting up your outreach campaigns, please reach out to our support team for assistance. 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 Overview and Go High Level Compatibility

What Is Search Atlas? Search Atlas is an all-in-one SEO and digital marketing platform designed to help agencies, marketers, and business owners grow their online visibility. It brings together a wide range of tools under one roof so you can manage your entire SEO workflow without switching between multiple subscriptions. Core capabilities include tools for local SEO, content creation, site auditing, backlink research, rank tracking, and client reporting. Does Search Atlas Work with Go High Level (GHL) Websites? Search Atlas may be compatible with websites built and hosted on Go High Level, but compatibility with specific features can vary. If you have questions about how your GHL site will work with a particular Search Atlas feature, our team can help clarify before you purchase. Where Can I Learn More Before Buying? Search Atlas provides demo videos and other pre-sales resources you can access before purchasing. Search for Search Atlas on YouTube to find official walkthrough videos, feature demos, and tutorials covering the platform. 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 GA4 to a Different Property

Overview If your Search Atlas account is pulling data from the wrong Google Analytics 4 property — for example, showing metrics for a different domain than the one you manage — our support team can help you get the correct property connected. This article explains what to have ready and how to escalate so the issue is resolved as quickly as possible. What This Issue Looks Like You may notice that the GA4 data appearing in Search Atlas belongs to a different business or domain than your own. This typically happens when a wrong GA4 property was selected during the initial integration setup. Before You Reach Out To help our team resolve this quickly, please have the following information ready: - The name of the project in Search Atlas where the incorrect GA4 property is connected. - The correct GA4 Property Name and Property ID (a nine-digit number) that should be connected. You can find these in your Google Analytics dashboard under Admin → Property Settings. - The Google account email address that has access to the correct GA4 property. - A brief description of what domain or business the current (wrong) integration is showing data for. What to Expect Once you reach out, a member of our team will review your integration settings and work with you to disconnect the incorrect property and ensure the right one is connected. No historical data in Search Atlas is deleted during this process. 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 Migrate from SE Ranking to Search Atlas

This guide explains how to set up Search Atlas and configure tracking, reporting, and OTTO SEO when moving from SE Ranking. How do I set up a Search Atlas project? Create a project 1. Log in to your Search Atlas account, scroll down in the main Dashboard, and click + Create new. 2. Enter your domain, select the target country, and optionally enter primary keywords for tracking. 3. Add or remove recommended keywords and add your main competitors. You can change both options later. Connect Google Search Console 1. Click Site Metrics > All Sites > Connect GSC Account. Click on Site Metrics > All Sites > Connect GSC Account. 2. Authorize access and connect your verified property. 3. After GSC is connected, go to Manage Sites. 4. In the slider showing imported GSC properties, which are disabled by default, find your domain and click Enable. A slider will appear showing all imported GSC properties (they are disabled by default). Find your domain and then click Enable. Connect Google Analytics 4 1. From your GSC Performance dashboard, click Connect Google Analytics 4. 2. Select your GA property or connect your GA4 account. Authorize access and connect your verified property. 3. Once enabled, Search Atlas will link keyword data, impressions, CTR, and engagement metrics automatically. 4. You can use publicly shareable links for fast access to verification if needed. How do I export SE Ranking audit data and set up a Search Atlas site audit? You do not need to import site audit data from SE Ranking. Search Atlas automatically performs fresh technical scans with actionable insights using the Site Auditor. Export a content audit from SE Ranking 1. Use the Website Audit Tool to scan your site, then go to Website Audit > Crawled Pages to view URLs and content-related metrics such as word count, title, description, and status code. se ranking website audit 1 2. Click the Columns tab to select the metrics to include. Click Export and choose your preferred file format, such as CSV. 3. In Google Sheets, go to File > Import, upload the exported file, and click Import Data to view and work with your content inventory. se ranking website audit 2 sheet Set up a site audit in Search Atlas 1. Go to OTTO & Audit > All Audits > Site Auditor. 2. Enter your domain and configure the crawling features: - User agent (use Search Atlas bot recommends for best accuracy) - Number of pages to crawl (default is 100) - Adjust crawl speed (default is 20 pages per second) - Set crawl frequency (default is every 7 days) 3. Run a full scan to launch the crawl across all pages under that domain. Bulk auditing (Pro Plan Feature) For agencies or multi-site audits, go to Update Sites in Bulk and paste multiple domains to queue audits simultaneously. How do I export SE Ranking ranking history and track keywords in Search Atlas? Export rankings from SE Ranking 1. Go to Rankings > Detailed and select the project to export data from. 2. Use filters to choose the search engine, location, and date range if needed. 3. Click the Export button in the top-right corner and choose your preferred format (CSV, XLSX, or PDF). se ranking export keyword history data 1 4. Download the file to your device for further analysis or migration. Track keywords in Search Atlas 1. Go to Keywords > Keyword Rank Tracker. 2. Enter your domain or target page and specify the target location (country, state, city, county, or province). 3. For example, track rankings for searchatlas.com in Las Vegas, Nevada. 4. Click Start Tracking and connect your Google Business Profile (GBP), if applicable. Enter the name of your project, description, language, and keyword refresh interval (Daily, Weekly, Monthly, or Custom). 5. Search Atlas will automatically recommend keywords. Select from the recommendations or paste keywords manually from the SE Ranking sheet. Search Atlas will automatically recommend keywords, and you can choose between selecting them or pasting keywords manually from the SE Ranking sheet. How do I export local rankings and set up a GBP project? You do not need to import data from SE Ranking because Search Atlas connects with your Google Business Profile (GBP) to automatically draw all of the information. You can still export the Local SEO information for further consultation. Export local rankings from SE Ranking 1. Go to Local Marketing > Local Rankings and select your project. 2. Choose the required time period from the calendar and press the Export button in the top-right corner. 3. Choose whether to download the data in .XLSX or .CSV format. se ranking export Local Rankings data Connect your GBP and select your business 1. Go to Local SEO > Connect GBP and link your verified listing. Go to Local SEO > Connect GBP, and link your verified listing. 2. Authorize access and connect your verified property. 3. Search by business name, Place ID, business URL, or import via email invitation. 4. Click + Save to create your local SEO project. Configure the heatmap 1. After GBP is connected and the project is saved, go to Local SEO > Local SEO Heatmap. After GBP is connected and the project saved, go to Local SEO > Local SEO Heatmap. 2. Add the keywords to track, choose circle or rectangle to define the tracking area, and set the radius. Recommendations: - 3–5 miles → Use 3 layers or grids - 10–25 miles → Use 4–5 layers or gridsThe bigger the mile radius, the more layers or grids you should use. This recommendation increases grid density for wider coverage. 3. Schedule refresh intervals and choose specific times when your business is open. Avoid midnight or off-hours, as this may show lower ranks than actual performance. Schedule refresh intervals and choose specific times when your business is open 4. Click on the pins to omit unnecessary ones (e.g., uninhabited areas) to save quota and avoid skewed average ranks. Click on the pins to omit unnecessary ones (e.g., uninhabited areas) to save quota and avoid skewed average ranks. Edit existing reports 1. Click on an existing project and click on the top of the page. Click on an existing project and click on the top of the page. 2. A timeline will be available to check ranking progress over time. Click on Edit heatmap to change the configuration. Compare competitors 1. To analyze how the business compares its rankings against each competitor in the area, click on an individual pin you want to target. Local SEO heatmap showing casino keyword ranking score with colored pins for good, medium, and bad search visibility across nearby cities 2. A list of local competitors will appear for the same keyword and pin. Click on Compare to choose which one to compare. A list of local competitors will pop up for the same keyword and pin. 3. Your business and the selected competitor will be compared side by side. Move the camera, zoom out, and zoom in to analyze the region. Configure the Heatmap step 7 Set up Local Rank Tracker 1. Go to Keywords > Keyword Rank Tracker. Go to Keywords > Keyword Rank Tracker 2. Enter the business’ website or target page, select the exact location being targeted, and click Start Tracking. 3. Set the device preference, language, frequency, custom naming, and description of campaigns or view. 4. Add the local keywords from your SE Ranking sheet. Add multiple locations If you have multiple businesses for the same project, click + Add New Location to track keywords for multiple locations in one report (e.g., Las Vegas and New York) and assign different keyword sets to each. Add Multiple Locations How do I export SE Ranking reports and create reports in Search Atlas? There is no direct way to import reports from SE Ranking into Search Atlas. You can create equivalent reports in Search Atlas using the Report Builder. Export a report from SE Ranking 1. Go to the Report Builder and select your project. 2. In the report settings menu: - Choose the project to report on. - Set the date range (e.g., today, last 7 days, last month). - Select the export format: PDF, XLS, or HTML. - Choose a vertical or horizontal layout. - Pick your preferred language (from nine available options). 3. After configuring the report, click Export to generate the file. 4. Download the report and send it manually via email as needed. se ranking data report download Create a report in Search Atlas 1. Go to Report Builder > Report List. 2. Choose the location, date range, and report widgets, such as: - AI Summaries - Site Explorer - OTTO SEO - Orders & Tasks - Google Analytics data - Google Search Console data - Facebook Ads - Google Ads - Google Business Profile - Keyword Rank Tracking 3. Schedule the automated reporting by adding recipients, selecting the email frequency (weekly, monthly, or quarterly), and choosing the day of the week the report will be sent. 4. Choose between Default Layout and Custom Layout, and create the report. Customize the report 1. After creating the report, click Configure Report to change the Integrations, Scheduled emails, and Layout. 2. In Layout, customize the report. 3. Click Add custom text to add your own text or HTML, including branding such as a logo, banner, and links. 4. Scroll down and click and drag each metric to the report. You can choose where to add the report. Scroll down and click and drag each metric to the report. You are free to choose any place to add the report. Add AI Summaries 1. In Integrations, you can add the AI Summary Overview. 2. These are automated overviews that highlight key points of your report to help you and your clients understand the results. These are automated overviews that quickly highlight the key points of your report, making it much easier for both you and your clients to understand the results. Create a Local SEO report 1. Click Configure Report and go to the Local SEO and GBP Section. 2. Integrate as many Local SEO projects and GBP Accounts as necessary for the report. 3. The previously configured heatmap for each Local SEO project will be added to the report automatically. The heatmaps are customizable. The previously configured heatmap for each Local SEO project will be automatically added to the report. They are fully customizable. 4. GBP data will be added to the report automatically. Each metric is customizable. The GBP data will be automatically added to the report. Each metric is fully customizable. Share the report After configuring your report, download it as a .PDF, or share it via Share URL or Get iFrame Code. IFrame Code is an HTML element that allows you to embed another HTML page within your own. Set up white-label reporting 1. Go to Agency White Label and set your custom dashboard URL and logo. Go to Agency White Label and set your custom dashboard URL and logo. 2. When you share your report via Shareable URL, it will display your logo and URL. How do I enable automated SEO optimization with OTTO SEO? With Search Atlas, you can set up OTTO SEO, the AI agent that automates nearly every SEO task, including technical audits, on-page optimization, link building, content creation and optimization, Local SEO and GBP optimization, and more. Obs: You need to complete the Site Audit on your project before activating OTTO. Set up OTTO SEO 1. Go to Projects > + Add a Website. Go to Projects > + Add a Website 2. Select one of your projects that doesn’t have OTTO installed, or add a new website. 3. Select the GSC and GBP, and add your business details. 4. Proceed with the tutorial to install OTTO. Next, proceed with the tutorial to install OTTO. Install OTTO on another CMS 1. Go to OTTO & Projects > Installation Guide. Short tutorials are available for: - Google Tag Manager - WordPress - Shopify - Webflow - Squarespace - ClickFunnels - Wix - GoHighLevel (GHL) - Custom InstallationInstalling OTTO on another CMS Install OTTO SEO on WordPress 1. Go to your WordPress dashboard and open the Plugins section. Search for “Search Atlas” in the plugin directory. Click Install Now, then activate the plugin. otto installation wordpress step1 2. Copy the API key provided during setup. Open the Search Atlas plugin settings by clicking the Search Atlas logo in the left-hand menu. Go to General Settings. Paste the API key into the Search Atlas API Key field and continue. otto instalation wordpress step 3 3. Copy the code provided in the next step. Return to your WordPress dashboard and open the plugin settings again. In General Settings, check the Enable OTTO box. Paste the code into the OTTO Pixel UUID field and save changes. otto instalation wordpress step 5 4. OTTO SEO now runs inside WordPress, automating fixes and SEO updates across your site. Configure OTTO SEO See the tutorial on configuring OTTO Autopilot and settings. How do I use the Search Atlas onboarding resources? Watch tutorial videos Search Atlas offers step-by-step tutorials on YouTube to help you set up reports, dashboards, and automations. Book a 1:1 onboarding session During your trial, you can schedule a 1:1 onboarding session directly from the dashboard. A product expert can help you customize your setup, connect integrations, and configure OTTO SEO for automation. Follow the 7-Day Email Campaign When you start your free trial, you’ll receive a 7-day onboarding email sequence. Each email walks you through a core feature. Use the technical documentation Access the technical docs via the Help Center for detailed instructions on using every tool. The documentation is searchable and regularly updated. For further assistance, reach out via live chat.

🔗 Publishing AI Content to a Custom PHP Backend

🧭 Overview Search Atlas does not support direct webhook creation for custom PHP websites. This is expected behaviour — the webhook option in the publishing settings is reserved for supported third-party platforms. If you are running a custom PHP backend, you can still publish AI-generated content automatically using one of two integration methods described in this article. ⚙️ Choose Your Integration Method Before you begin, determine how your PHP site stores content: - Database storage — your site uses MySQL, MariaDB, or another database to store posts and pages. - File storage — your site writes content to flat files such as HTML, Markdown, or JSON files on the server. Both methods use the Search Atlas REST API to retrieve published content. The difference lies in how your PHP script handles and stores the data once it is received. 🔑 Step 1 — Generate Your API Key 1. Log in to Search Atlas, click your Avatar, and open Settings. 2. Navigate to API Keys. 3. Click Generate New Key and copy the key to a safe location. 4. Note your Organisation ID displayed on the same page — you will need it in later steps. 📡 Step 2 — Set Up the PHP Integration Script Create a new PHP file on your server, for example fetch-content.php. This script will request your published content from the Search Atlas API and store it on your site. Base API request structure: - Endpoint: https://api.searchatlas.com/v1/content/published - Method: GET - Required headers: Authorization: Bearer YOUR_API_KEY and X-Organisation-ID: YOUR_ORG_ID - Optional query parameter: ?since=TIMESTAMP to retrieve only content published after a specific date and time. Your PHP script should perform an HTTP request to this endpoint using cURL or a library such as Guzzle, then decode the JSON response and process each content item. 🗄️ Step 3A — Store Content in a Database If your PHP site uses a database, follow these steps after retrieving the API response: 1. Connect to your database using PDO or MySQLi. 2. For each content item in the response, check whether a record with the same content_id already exists in your posts table. 3. If the record exists, run an UPDATE statement to refresh the title, body, slug, and updated timestamp. 4. If the record does not exist, run an INSERT statement to create a new row. 5. Map the following API response fields to your table columns: title, body_html, slug, meta_description, published_at, and content_id. 📁 Step 3B — Store Content as Flat Files If your PHP site uses file-based storage, follow these steps after retrieving the API response: 1. Define a target directory on your server where content files will be saved, for example /var/www/html/content/. 2. For each content item in the response, construct a file name using the slug field and your preferred extension, such as my-article-slug.html. 3. Write the body_html value to the file using file_put_contents(). This will create the file if it does not exist or overwrite it if it does. 4. Optionally, write a companion JSON file for each piece of content containing the title, meta description, and published date for use by your templating layer. ⏱️ Step 4 — Automate With a Cron Job Because webhooks are not available for custom PHP backends, you will use a scheduled cron job to poll the API at regular intervals and keep your site up to date. 1. Open your server's crontab by running crontab -e in the terminal. 2. Add a new line to run your script on your preferred schedule. For example, to run every 15 minutes use: */15 * * * * php /var/www/html/fetch-content.php 3. Save the crontab. Your server will now automatically check for new or updated content and publish it to your site. 4. To retrieve only new content on each run, store the timestamp of the last successful fetch and pass it as the since query parameter in each API request. ✅ Step 5 — Test the Integration 1. Publish a test article from the Search Atlas content editor. 2. Manually run your PHP script from the terminal to confirm it fetches the article without errors. 3. Verify the article appears in your database table or file directory as expected. 4. Check that the cron job runs on schedule by reviewing your server logs after the next scheduled interval. 🚫 Common Issues and Fixes - 401 Unauthorised error — Confirm your API key is correct and has not expired. Regenerate it in Settings if needed. - Empty response from API — Ensure at least one article has been published in Search Atlas and that your Organisation ID is correct. - Cron job not running — Verify the PHP binary path in your cron command by running which php in the terminal and updating the crontab accordingly. - Duplicate content in database — Confirm your upsert logic is checking against the content_id field, not the title or slug, which may change. 💬 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.

🔍 Verify Search Atlas Tracking Scripts

🔍 What You Are Verifying Search Atlas may use Google Tag Manager (GTM) and a dynamic optimization script to load tracking or optimization features on your website. Verification confirms that the expected code is present, loads successfully, and is connected to the correct project. A GTM container ID, such as GTM-TCCS243, identifies a Google Tag Manager container. The ID alone does not prove that the container belongs to Search Atlas. Confirm its ownership and tags in the Google Tag Manager account used for your site. 🛠️ Check the Website Source 1. Open the published version of your website in a private browser window. 2. Right-click the page and select View page source, or use your browser’s developer tools. 3. Search for the GTM container ID, such as GTM-TCCS243. 4. Search for terms related to Search Atlas, OTTO, optimization, or the project’s tracking script. 5. Check several important page types, including the homepage, a service page, and a contact or conversion page. The code may be injected through a CMS, a plugin, a tag manager, or another deployment method. It may not appear in the original HTML if it is added after the page loads. 📊 Check Loaded Scripts 1. Open your browser’s developer tools and select the Network tab. 2. Reload the page with the developer tools open. 3. Filter requests by js, gtm, script, or a recognizable Search Atlas or OTTO term. 4. Open matching requests and review the request URL, status code, and initiator. 5. Confirm that the request returns successfully, normally with a 200 status, and is not blocked by the browser, consent tool, firewall, or content security policy. Do not rely on a script name alone. Review where the script loads from and whether the request is associated with the correct website and project. 🏷️ Verify the GTM Container 1. Sign in to the Google Tag Manager account that manages the website. 2. Open the container matching the ID found on the site. 3. Review the container name, account ownership, workspaces, tags, triggers, and published version. 4. Use GTM Preview mode to confirm that the expected tags fire on page load and on the relevant visitor actions. 5. Check that the container is published and that no duplicate or outdated container is also installed. If the GTM account is managed by another agency or vendor, ask the account owner to confirm whether the container and tags were installed for Search Atlas. ⚙️ Confirm the Dynamic Optimization Script Dynamic optimization code can be loaded directly or through GTM, so its location may differ between sites. Compare the script and its request behavior with the installation details for the correct Search Atlas project. Confirm that: - The script is installed on the intended domain. - The project and domain are correctly matched. - The script loads after consent requirements are met, when applicable. - The script is not duplicated by the CMS, GTM, or another optimization tool. - It is not being removed, modified, or blocked by caching, security, or performance tools. 🚨 Troubleshoot Recurring Issues - Code appears only sometimes: Test in a private window, clear site and CDN caches, and check whether a consent banner changes script loading. - GTM is present but tags do not fire: Use GTM Preview mode and review triggers, blocking rules, consent settings, and the published version. - Requests are blocked: Check browser console errors, security headers, firewall rules, and ad or script-blocking extensions. - Changes are not visible: Confirm that the correct environment is published and purge applicable browser, plugin, and CDN caches. - Multiple scripts are present: Remove duplicate installations only after confirming which deployment is active and supported. - Site behavior changed unexpectedly: Temporarily document the affected URL, time, browser, and console or network error before changing code. ✅ Record Verification Results For recurring investigations, record the website URL, affected page types, GTM container ID, script or request URL, timestamp, browser, consent state, and any console or network errors. This information helps identify whether the issue is caused by installation, publishing, caching, blocking, or project 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.

🔌 Custom CMS Integration and OTTO Pixel Setup

🗺️ Overview Search Atlas currently offers a pre-configured native integration for Contentful. If your site runs on a different CMS — such as Flexo, a headless CMS, or a fully custom-built system — you can still connect it using the manual or API-based setup path described in this article. This article also explains the difference between OTTO Pixel status states, which is a common source of confusion after installation. ❓ Why Is Only Contentful Available in the Integration Menu? Contentful is the only CMS with a one-click native connector in Search Atlas at this time. This is because native integrations require platform-level API agreements and validated data-mapping configurations that are built and tested by our engineering team before release. Support for additional CMS platforms is on our roadmap. In the meantime, any CMS that allows you to inject custom scripts or access a public API can be connected using the manual setup steps below. 🛠️ How to Integrate a Custom CMS (e.g., Flexo) Follow these steps to connect a non-Contentful CMS to Search Atlas: 1. Install the OTTO Pixel script. Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). Open the OTTO setup panel and copy your unique Pixel script tag. 2. Paste the script into your CMS. In your CMS admin panel, locate the section that controls global HTML output — this is typically called Head Scripts, Custom Code, or Site Settings → Head. Paste the Pixel script before the closing </head> tag so it loads on every page. 3. Publish or deploy the change. Save and publish your changes. If your CMS uses a build or deploy pipeline (common in headless setups), trigger a new build so the script appears in the live HTML output. 4. Verify the script is live. Open your website in a browser, right-click anywhere on the page, and select View Page Source. Search for your Pixel script tag to confirm it is present in the rendered HTML. 5. Return to OTTO and check the Pixel status. Go back to Left sidebar → OTTO SEO → All Sites (SEO Automation) and refresh the OTTO panel. Status should update within a few minutes of the script being detected on your live site. If your CMS does not support direct script injection, contact your CMS provider or developer to request access to global head injection. Most modern CMS platforms, including headless and custom-built ones, support this capability. 📡 OTTO Pixel Status Definitions After installing the Pixel, you may see one of the following status labels in the OTTO panel. Each means something different: - Not Installed — The Pixel script has not been detected on your site. The script is either missing, not yet published, or placed in a location that prevents it from loading on all pages. - Engaged — Search Atlas has made contact with your domain and the setup process has been initiated, but the Pixel script has not yet been confirmed as active on your live pages. This often appears immediately after you begin the OTTO setup, before the script is deployed. - Installed — The Pixel script has been detected loading on your site. Search Atlas can now begin crawling and collecting data from your pages. - Verified — The Pixel has been detected, confirmed across multiple page loads, and OTTO has successfully completed its initial site scan. This is the fully active state and means OTTO is running normally. **Key point:**Engaged does not mean the Pixel is working. It only means the setup flow was started. You must reach Installed or Verified status for OTTO to function correctly. 🔍 How to Troubleshoot an 'Engaged but Not Installed' Status If your OTTO status shows Not Installed and does not progress to Installed, work through the following checks: - Confirm the script is in the live HTML. Use View Page Source (not browser DevTools Elements panel, which can show injected code) to check the raw HTML your server delivers. Search for your Pixel tag. - Check that the script loads on all pages, not just one. The Pixel must be present site-wide. If it only appears on the homepage, OTTO cannot fully verify installation. - Confirm the page is publicly accessible. OTTO cannot detect the Pixel on pages behind a login, staging password, or IP restriction. Test on your public-facing production URL. - Clear your CMS cache and CDN cache. Many CMS platforms and CDNs aggressively cache page output. After adding the Pixel, purge all caches so the updated HTML is served to external requests. - Wait up to 10 minutes and refresh the OTTO panel. Status checks do not happen in real time. Allow a short window after deployment before concluding there is a problem. - Re-copy and re-paste the Pixel script. If you manually typed or edited the script tag, it may contain a typo. Return to the OTTO setup panel, copy the script fresh, and replace the existing one in your CMS. 💬 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.

🔧 OTTO Installation UUID Configuration by CMS

🧭 What Is the OTTO UUID and Why Does It Matter? When you activate OTTO SEO on your website, Search Atlas generates a unique identifier called a UUID (Universally Unique Identifier). This UUID must be installed on your site so OTTO can communicate with your pages, apply SEO automations, and track implementation status. Without the UUID correctly placed, OTTO cannot deploy changes to your site. Navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) to find your UUID. It will appear during the OTTO onboarding flow or inside your active OTTO project settings. Copy it before following the steps below. ⚙️ WordPress Installation Use one of the two methods below depending on your access level. Method 1 — Header/Footer Plugin (Recommended) 1. Install and activate a plugin such as Insert Headers and Footers from the WordPress plugin directory. 2. Go to Settings → Insert Headers and Footers. 3. Paste the following code into the Scripts in Header field, replacing YOUR_UUID_HERE with your actual UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save. 2. Visit your homepage, right-click, select View Page Source, and confirm the meta tag appears inside the <head> section. Method 2 — Theme functions.php 1. In your WordPress dashboard go to Appearance → Theme File Editor. 2. Open functions.php. 3. Add the following code before the closing ?> tag, replacing YOUR_UUID_HERE with your UUID: function otto_uuid_meta() { echo '<meta name="otto-site-verification" content="YOUR_UUID_HERE" />'; } add_action( 'wp_head', 'otto_uuid_meta' ); 1. Click Update File and verify in page source. 🛍️ Shopify Installation 1. From your Shopify admin, go to Online Store → Themes. 2. Next to your active theme, click Actions → Edit Code. 3. Under Layout, open the file named theme.liquid. 4. Locate the opening <head> tag and paste the following line directly after it, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save. 2. View your storefront source to confirm the tag is present inside <head>. 🏪 Magento 2 Installation 1. Log in to your Magento Admin Panel. 2. Go to Content → Design → Configuration. 3. Click Edit next to your active store view. 4. Expand the HTML Head section. 5. In the Scripts and Style Sheets field, add the following, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> 1. Click Save Configuration. 2. Flush the Magento cache under System → Cache Management → Flush Magento Cache. 3. Verify the tag appears in your page source. 💻 Custom HTML / Headless / Any Other CMS If your site is built on a custom stack, a headless CMS (such as Webflow, Next.js, Nuxt, or similar), or any platform not listed above, the installation method is the same — place the UUID meta tag inside the <head> element of every page, or at minimum on your homepage. Add this tag, replacing YOUR_UUID_HERE with your UUID: <meta name="otto-site-verification" content="YOUR_UUID_HERE" /> - Webflow: Go to Project Settings → Custom Code and paste into the Head Code field. - Wix: Go to Settings → Custom Code, add the tag to the Head section and apply to All Pages. - Next.js / Nuxt: Add the meta tag inside your global <Head> component so it renders on every route. - Squarespace: Go to Settings → Advanced → Code Injection and paste into the Header field. ✅ How to Validate Your UUID Installation 1. Open your website in a browser and navigate to your homepage. 2. Right-click anywhere on the page and select View Page Source (or press Ctrl+U / Cmd+U). 3. Press Ctrl+F / Cmd+F and search for otto-site-verification. 4. Confirm the meta tag is present and your UUID value is correct. 5. Return to Search Atlas at Left sidebar → OTTO SEO → SEO Automation and check your OTTO project status — it should update to Connected within a few minutes. ⚠️ Common Issues and Fixes - Tag not appearing in source: A caching plugin or CDN may be serving a cached version. Clear all caches and check again. - OTTO still shows as disconnected: Allow up to 10 minutes after installation for the verification to complete. If the issue persists, double-check that the UUID matches exactly what is shown in your OTTO project settings — no extra spaces or characters. - Multiple store views (Magento): Repeat the configuration steps for each store view that OTTO should manage. - Headless CMS with server-side rendering: Ensure the meta tag is rendered in the initial HTML response, not injected only by client-side JavaScript, as OTTO reads the raw page source. 💬 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.

Manage, Remove, or Disable GSC Properties

🗺️ Overview If you connected your Google account to Search Atlas and see more Google Search Console (GSC) properties than you need, or are encountering an Access Forbidden error on a project, this article explains what to expect and how to get the right help quickly. 🔍 Why Are Multiple GSC Properties Showing? When you connect a Google account to Search Atlas, the platform may import GSC properties that your Google account has access to. If your Google account has access to several properties, more than one may appear in Search Atlas — even if you only intend to work with one. You can request removal or management of properties you do not need to keep your workspace tidy. 🗑️ How to Remove or Manage an Unwanted GSC Property There is no self-serve option to remove or disconnect a GSC property directly from within Search Atlas. Removing a property requires a backend action by our support team, because properties are tied to your connected Google account at the account level and cannot be unlinked from the workspace interface alone. To have a property removed or disconnected, please have the following information ready when you contact our support team so we can action this for you promptly: - The name or URL of the GSC property you want removed or disabled - Your account email and workspace name - Whether you want the property fully removed or simply hidden from your workspace Note: Removing a property from Search Atlas does not delete it from Google Search Console. It only disconnects it from your Search Atlas workspace. 🚫 Fixing the "Access Forbidden" Error on Your Project The Access Forbidden error means your user account does not currently have the required permission level to open a specific project or property. This is a separate issue from GSC property management. If you encounter this error, here is what you should do: 1. Confirm with your workspace owner or administrator that your account has been granted access to the relevant project. 2. Ask the workspace owner to review your role and permissions and update them if necessary. 3. Once your permissions have been updated, try accessing the project again. If the error persists after your permissions have been reviewed and corrected, contact our support team. When you reach out, please have the following ready: - The name of the project or GSC property showing the error - The exact error message you see on screen - Your account email and workspace name - The name of the workspace owner or administrator who manages your permissions 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.

Choosing Your Website Platform for OTTO SEO Deployment

Overview Search Atlas integrates with three website platforms: GoHighLevel (GHL), WordPress, and Search Atlas Website Studio. Each works differently with OTTO SEO, and the right choice depends on your priorities around vendor independence, management simplicity, and how SEO improvements are applied. This article explains the key differences so you can make an informed decision. How OTTO SEO Deploys Changes OTTO SEO can apply optimizations in different ways depending on the platform you use. The method of deployment affects how changes are stored and what happens if your Search Atlas connection or subscription changes. Understanding this distinction is an important factor when evaluating which platform fits your needs. WordPress: Plugin-Based OTTO Deployment WordPress with the Search Atlas WordPress plugin is a strong choice if you want a direct integration between OTTO SEO and your website's content management system. How it works: After installing the Search Atlas plugin on your WordPress site and connecting it to your Search Atlas account, OTTO can push SEO optimizations — such as meta titles and descriptions, schema markup, canonical tags, and image alt text — through the plugin to your WordPress site. Key benefits: - WordPress is open-source and self-hostable, giving you significant control over your hosting environment. - The plugin provides a direct connection between Search Atlas and your site's CMS. - You retain ownership and portability of your website and its content. Management considerations: WordPress requires you to manage hosting, plugin updates, and site security independently. This adds some operational overhead compared to fully hosted options, but gives you flexibility and control. Website Studio: All-in-One Simplicity Search Atlas Website Studio is a fully hosted website builder built directly into the Search Atlas platform, offering a streamlined experience for users who want everything managed in one place. How it works: Because Website Studio is part of the Search Atlas ecosystem, OTTO SEO and your website are managed within the same platform. This eliminates the need to configure a separate CMS or install additional plugins. Key benefits: - Everything — your website, SEO management, and OTTO deployment — is handled within a single platform. - No separate hosting setup or plugin management is required. - Ideal for users who want a simplified, unified workflow. Management considerations: Because Website Studio is hosted within Search Atlas, your site is tied to your Search Atlas subscription. This is a trade-off to consider if vendor independence is a priority for you. GoHighLevel (GHL): Integration via Search Atlas GoHighLevel can be connected to Search Atlas, allowing OTTO SEO to work alongside your GHL-hosted websites. How it works: Search Atlas connects to your GoHighLevel account to enable SEO management through the Search Atlas platform. This allows you to use OTTO SEO features for sites hosted in GHL. Key benefits: - Suitable for agencies or users already using GoHighLevel as their primary platform. - Allows you to manage SEO through Search Atlas without migrating your existing GHL sites. Management considerations: Because GHL is a third-party platform, the behavior of the integration depends on how Search Atlas and GHL communicate. Contact the Search Atlas team for the most current details on what is supported for your specific GHL setup. Choosing the Right Platform When deciding which platform to use with OTTO SEO, consider the following: - If you want a self-hosted, open-source environment: WordPress with the Search Atlas plugin offers the most independence. - If you want a single, all-in-one platform: Website Studio keeps everything within Search Atlas. - If you are already using GoHighLevel: The Search Atlas integration allows you to use OTTO SEO without moving to a new CMS. 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.

💡 Submit a Feature Request to Search Atlas

💡 Why Submit a Feature Request? Search Atlas actively collects customer ideas to shape the product roadmap. If you have a suggestion — such as wanting Website Studio thumbnails to refresh automatically over time rather than showing only the original generated image — you can submit it directly through the official product portal. Your request will be visible to the product team, and you will receive updates as its status changes. 🚀 How to Submit Your Feature Request 1. Open the Search Atlas product portal in your browser: https://portal.productboard.com/searchatlas/1-search-atlas-product-portal/tabs/3-launched 2. Browse existing ideas to check whether someone has already submitted a similar request. If so, you can upvote it to show your support. 3. If your idea does not already exist, look for the option to submit a new idea and describe your suggestion clearly. Include as much context as possible — for example, which feature is affected, what behaviour you currently see, and what you would like it to do instead. 4. When prompted, enter your email address. This is how ProductBoard notifies you when the status of your request changes, such as when it is under review, planned, or launched. ✅ What Happens After You Submit Once your request is submitted, the Search Atlas product team will review it alongside other ideas. You may see your request move through status stages such as Under Consideration, Planned, or Launched. You will receive email notifications at each stage so you can stay informed without needing to check back manually. 📋 Tips for a Strong Feature Request - Be specific: Describe exactly what you want the feature to do, not just a general improvement. - Explain the use case: Share why this change would help you or your workflow. - Include examples: If relevant, mention the tool or page where the change should apply, such as Website Studio. - Use a real email: You need a valid email address to receive status updates on your submission. 🛠️ Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏆 How to Connect Trophy Content

This guide explains how to split trophy content into focused chunks and associate those chunks with the correct site. 📍 Where to Find It Open OTTO SEO → Knowledge Base to manage trophy content. Use OTTO SEO → All Sites to choose the site you want to connect. 🛠️ Step-by-Step 1. Open OTTO SEO → All Sites and select the site that should use the content. 2. Open OTTO SEO → Knowledge Base. 3. Split the trophy content into separate, focused chunks. Keep each chunk centered on one topic, question, instruction, or group of closely related facts. 4. Create or add each chunk in the Knowledge Base, using a clear title and the complete text for that topic. 5. Associate every chunk with the site you selected. Check the site name before saving so the content is not connected to a different project. 6. Save the entries and repeat the process for the remaining chunks. ✅ How to Confirm It Worked Confirm that each chunk appears in the Knowledge Base and shows the intended site association. Then return to OTTO SEO → All Sites, select that site, and run a scan. The scan should complete without an association error, confirming the site can process the connected content. 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 Custom-Coded Websites to Search Atlas

🔍 Who This Article Is For This guide is for customers who run a custom-coded website — built with Node.js, Next.js, or a similar framework and hosted on platforms like cPanel — who are seeing zero SEO scores for content and UX signals in Search Atlas after migrating away from a CMS-based platform such as GoHighLevel, WordPress, or Webflow. Without a native CMS connector, Search Atlas cannot automatically pull or push content to your site. This article explains why scores drop to zero and outlines the general approaches available to restore full SEO visibility and content publishing. ⚠️ Why Your SEO Scores Are Showing Zero Search Atlas calculates content and UX signal scores by reading published, crawlable content on your live website. When you migrate from a platform with a native connector (like GoHighLevel) to a custom-coded build, two things typically break: - No CMS connector: Search Atlas can no longer sync or verify published content automatically. - OTTO Pixel may be missing or misconfigured: Without the tracking pixel installed on your new build, OTTO SEO cannot collect UX signals such as engagement and on-page behaviour. Both issues must be resolved independently. The sections below cover what to prepare and what to communicate to the support team so your account can be properly configured. ✅ Step 1 — Reinstall the OTTO Pixel on Your Custom Build Even on a custom Node.js or Next.js site, the OTTO Pixel can be installed manually by adding the pixel script to your site's global HTML template or layout file. Because the exact navigation path to retrieve your pixel script may vary based on your account configuration, contact the support team to confirm the correct steps for your setup and to obtain your unique pixel snippet. When you reach out, have the following ready: - Your Search Atlas project name or domain - The framework your site is built on (e.g., Next.js, Node.js with EJS) - Whether you have access to edit your site's root layout or HTML template file Once the pixel script is added to your site's <head> and deployed, UX signal collection will resume within 24–48 hours of real visitor traffic. 📝 Step 2 — Choose a Content Publishing Workflow Because your site has no CMS, you need an alternative method to create, optimise, and publish content that Search Atlas can score. The right approach depends on your technical setup and goals. Contact the support team to identify which workflow is available for your account and how to get it configured correctly. When reaching out, be prepared to share: - Your project name and the domain of the custom-coded site - The platform or framework the site is built on - A brief description of how content is currently added to the site (e.g., hardcoded HTML files, a temp 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.

🔗 Connecting Search Atlas to Data Warehouse Platforms

🌐 Overview Many teams want to pipe Search Atlas data — including AI visibility metrics — into data warehouse or analytics platforms such as Power My Analytics, BigQuery, Looker Studio, or similar tools. This article explains what is currently supported, what limitations exist, and how to get your data flowing in the meantime. 🤖 What the Search Atlas MCP Integration Does (and Does Not Do) Search Atlas offers an MCP (Model Context Protocol) integration designed to connect the platform with AI assistants like Claude. This integration lets AI tools query your Search Atlas data conversationally — for example, pulling keyword rankings, AI visibility scores, or backlink data directly inside an AI chat interface. However, the MCP integration is not built for ETL pipelines or data warehouse ingestion. It is not designed to: - Push data automatically into platforms like Power My Analytics, BigQuery, or Snowflake - Act as a native connector or data source within third-party analytics dashboards - Schedule recurring data syncs to an external warehouse If you are trying to use the MCP connection as a bridge into Power My Analytics or a similar platform, this workflow is not currently supported and will not produce reliable results. 📦 Current Options for Getting Search Atlas Data into a Data Warehouse While a native connector for Power My Analytics does not yet exist, you have several practical paths available today. Option 1 — Manual CSV Export and Upload 1. Navigate to the relevant report inside Search Atlas (for example, a keyword tracking table or AI visibility report). 2. Use the export option available within that report to download your data as a CSV file. 3. Upload or import the CSV into your data warehouse or analytics platform using that platform's standard import workflow. 4. Repeat on whatever cadence your reporting requires (daily, weekly, etc.). This is the most reliable method available right now and works with any platform that accepts flat-file imports, including Power My Analytics. Option 2 — Request a Native Connector Search Atlas actively develops new integrations based on customer demand. If Power My Analytics or another data warehouse platform is critical to your workflow, submitting a formal connector request is the fastest way to move it up the roadmap. See the section below for how to do this. Option 3 — Use the MCP Integration for Ad Hoc AI Queries If your goal is to analyze Search Atlas data with AI — rather than store it in a warehouse — the MCP integration with Claude is well suited for that use case. You can ask natural-language questions about your rankings, AI visibility, and backlink data without exporting anything. This does not replace a data warehouse workflow, but it may cover your analytical needs depending on your objectives. 📋 How to Request a Native Connector for Power My Analytics or Another Platform 1. Go to Home using the left sidebar. 2. Locate the Submit action on the Home dashboard. 3. Describe your integration request clearly — include the platform name (e.g., Power My Analytics), your use case (e.g., daily AI visibility data sync to a data warehouse), and any technical requirements you are aware of. 4. Submit the request. The Search Atlas product team reviews all submissions and prioritizes based on demand volume. The more detail you provide about your workflow and the business impact, the more useful your submission will be for the team evaluating it. 📤 Tips for Manual Exports While You Wait for a Native Connector - Export consistently: Set a recurring reminder to export on the same schedule your warehouse expects fresh data, so reports stay accurate. - Label your files clearly: Include the date range and report type in the file name (e.g., ai-visibility-2026-08-01-to-2026-08-07.csv) to avoid confusion when uploading multiple files. - Check field mapping: When importing into Power My Analytics or a similar tool, confirm that column headers from the Search Atlas export match the field names your destination platform expects. Rename columns in the CSV before uploading if needed. - Combine with other sources: Data warehouse platforms like Power My Analytics are designed to blend multiple data sources. Your Search Atlas CSV exports can sit alongside Google Analytics, Google Search Console, or paid media data for a unified view. 🔍 Refreshing Your Data in Search Atlas Before exporting, make sure you are working with the most current data available. Go to Home using the left sidebar and select Refresh data to trigger an update across your active projects. This ensures your CSV export reflects the latest rankings and AI visibility figures. 🆘 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.

🤖 MCP Tools vs Slash Commands in Claude Code

🔍 What This Article Covers If you attended the Search Atlas AI summit, you may have seen a demo featuring 60+ AI-powered tools. When you open Claude Code, however, you only see around 20 items listed — and /onboard-client is nowhere to be found. This article explains exactly why, and how to access every tool available to you. ⚡ The Two Types of Tools: A Critical Distinction There are two completely separate categories of tools in the Search Atlas AI ecosystem. Confusing them is the most common source of frustration, so understanding this distinction will clear up everything. - Slash commands — These are built-in Claude Code shortcuts that you type manually. You trigger them yourself by typing a forward slash. Examples include /help, /clear, and /cost. Claude Code ships with roughly 20 of these commands, and that number is expected and correct. - MCP tools — These are the 60+ Search Atlas-powered capabilities (keyword research, site audits, content creation, SERP analysis, and more). You do not type a slash command to use them. Instead, you simply describe what you want in plain language during your conversation and the AI model automatically selects and invokes the right MCP tool on your behalf. MCP tools are never listed as slash commands. They run silently in the background when the model determines they are needed. No manual loading, syncing, or selection is required. 💬 How to Use MCP Tools in Claude Code Because MCP tools are invoked automatically through natural language, using them is straightforward. You do not need to remember command names or a special syntax. 1. Open Claude Code and confirm that your Search Atlas MCP server connection is active. 2. Start a new conversation and describe your task in plain English. For example: "Run a technical site audit for example.com" or "Find keyword opportunities for a blog post about home insurance." 3. Claude Code will automatically detect which MCP tool is appropriate and execute it. You will see a tool-call notification in the conversation thread when a tool is being used. 4. Review the results returned directly in the conversation. You can ask follow-up questions or request additional actions in the same thread. There is nothing else to install, enable, or unlock. If your MCP server connection is active, all 60+ tools are already available and ready to be called by the model. 📋 Why You See ~20 Items in the Slash Command List When you type / in Claude Code, the autocomplete panel shows only Claude Code's native built-in commands. This list will always contain roughly 20 items regardless of how many MCP tools are connected. This is intentional behavior — MCP tools are a completely different integration layer and are not surfaced in that panel. Seeing ~20 slash commands does not mean your MCP tools are missing, broken, or incomplete. 🌐 Where to Find /onboard-client /onboard-client is not part of the MCP toolset and is not available inside Claude Code. It is a dedicated feature of the Search Atlas AI Agent web interface, which is a separate product accessed at https://agent.searchatlas.com. To use /onboard-client and similar workflow commands: 1. Navigate to https://agent.searchatlas.com in your browser. 2. Log in with your Search Atlas credentials. 3. Type /onboard-client directly in the AI Agent chat interface. The AI Agent web interface and Claude Code are complementary tools with overlapping but distinct feature sets. Features specific to the web interface will not appear in Claude Code, and vice versa. ✅ Quick Reference Summary - ~20 slash commands in Claude Code — Normal and expected. These are Claude Code's built-in utilities. - 60+ MCP tools — Available in Claude Code via natural language conversation. Not listed as slash commands. - /onboard-client — Only available at https://agent.searchatlas.com. Not part of Claude Code or the MCP toolset. - To trigger an MCP tool — Just describe your goal in plain language. The model handles the rest automatically. 🛠️ Troubleshooting: MCP Tools Not Responding If you describe a task and the model does not appear to be using any MCP tools, check the following before escalating: - Confirm your Search Atlas MCP server is listed as connected in your Claude Code MCP settings panel. - Make sure you are using a Claude model that supports tool use (Claude 3.5 Sonnet or later is recommended). - Try rephrasing your request to be more specific about the outcome you want. Vague prompts are less likely to trigger a tool call. - Check that your Search Atlas account has an active subscription with API access enabled. 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.

🛠️ Exclude OTTO Pixel from Cloudflare Route Paths

🔍 Overview When you deploy the OTTO pixel via a Cloudflare Worker, the Worker runs on every route it is assigned to. Simply adding a route with no Worker attached is not enough to exclude a path — Cloudflare does not treat an empty route as a block rule. This article explains the correct method to prevent the OTTO pixel from loading on specific paths, such as yopki.com/app/*, while keeping it active on the rest of your site. ⚙️ How Cloudflare Worker Routes Work Cloudflare matches Worker routes using a pattern list. When a request comes in, Cloudflare checks your route patterns in order and runs the first matching Worker it finds. Key behaviours to understand: - A route with no Worker assigned does not override a broader route that has a Worker assigned. - More specific routes do not automatically take priority — order and correct configuration matter. - The only reliable way to skip the Worker for a path is to add an exclusion check inside the Worker script itself, or to restructure your routes carefully. 🚀 Method 1 — Add a Path Exclusion Inside the Worker Script (Recommended) This is the most reliable approach. Edit your OTTO Worker script to check the incoming request path and skip pixel injection for any excluded paths. 1. Log in to your Cloudflare dashboard and go to Workers & Pages. 2. Select the Worker that serves the OTTO pixel. 3. Click Edit Code to open the Worker editor. 4. At the very beginning of your fetch handler, add a path check like the example below: Example logic (add before any pixel injection code): - Get the URL from the incoming request. - If the pathname starts with /app/ (or any other path you want to exclude), return a plain fetch(request) — passing the request through without modification. - Otherwise, continue with normal pixel injection. In plain terms, your Worker should do the following: if the path matches an excluded pattern, pass the request through untouched; if it does not match, run the pixel injection as usual. 1. Click Save and Deploy after making your changes. 2. Test by visiting your excluded path (e.g. yopki.com/app/dashboard) and confirm the OTTO pixel script no longer appears in the page source. 🗺️ Method 2 — Restructure Cloudflare Routes If you cannot edit the Worker script directly, you can restructure your Cloudflare routes. This method requires careful ordering. 1. In your Cloudflare dashboard, go to Workers & Pages → your Worker → Triggers → Routes. 2. Remove any existing broad route such as yopki.com/* that covers your entire site. 3. Add specific routes that cover only the paths where you want the pixel active. For example: - yopki.com/blog/* → assign your OTTO Worker - yopki.com/ → assign your OTTO Worker - yopki.com/shop/* → assign your OTTO Worker 4. Do not add a route for yopki.com/app/* at all — if no route matches that path, no Worker runs. 5. Save your changes and test the excluded path to confirm the pixel is absent. Important: Method 2 requires you to explicitly list every path where the pixel should appear. If you add new sections to your site later, remember to add matching routes. Method 1 is generally easier to maintain. ✅ Verifying the Exclusion Is Working After applying either method, follow these steps to confirm the pixel is excluded correctly: - Open your browser and navigate to a URL on the excluded path, for example yopki.com/app/login. - Right-click the page and select View Page Source. - Search for otto or the pixel script tag. It should not appear on excluded paths. - Next, visit a page where the pixel should still be active and confirm it does appear in the source. - In Search Atlas, go to the left sidebar and click OTTO SEO, then open SEO Automation to access the OTTO dashboard and verify that tracked pages are still reporting data correctly. ⚠️ Common Mistakes to Avoid - Adding an empty route is not an exclusion. A Cloudflare route with no Worker attached does nothing to block another Worker that matches the same path via a different route pattern. - Wildcard routes are greedy. A route like yopki.com/* will match yopki.com/app/anything. You must handle exclusions explicitly. - Caching can delay changes. After updating your Worker or routes, allow up to two minutes and try a hard refresh (Ctrl + Shift + R or Cmd + Shift + R) before concluding a change has not worked. 💬 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.

🔌 Install OTTO Pixel on WordPress via ZIP

🧭 Overview If the OTTO Pixel plugin link in Search Atlas is not working, the instructions page is unavailable, or the WordPress plugin directory does not return a result, you can install OTTO Pixel manually using a ZIP file upload. This method works on any self-hosted WordPress site and produces the same result as the standard installation. ⏰ When to Use This Method - The plugin download link inside Search Atlas is broken or unresponsive. - The OTTO Pixel plugin is temporarily under review in the WordPress plugin directory. - You cannot find the plugin by searching inside your WordPress dashboard. - The in-platform instructions page returns an error or does not load. 📥 Step 1 — Obtain the OTTO Pixel ZIP File The official ZIP file can be obtained directly from the Search Atlas support team, independent of the WordPress plugin directory. 1. Log in to your Search Atlas account and navigate to the OTTO setup section for the website you want to connect. 2. If a download option is visible on the OTTO setup or WordPress connection page, use it to save the ZIP file to your computer. 3. If no download option is available, open the chat widget in the bottom-right corner of the platform and type human teammate — a team member will send you the direct download link immediately. 4. Save the file to your computer. Do not unzip the file — WordPress requires the compressed ZIP for upload. 🖥️ Step 2 — Upload the ZIP File to WordPress 1. Log in to your WordPress admin dashboard (typically yoursite.com/wp-admin). 2. In the left WordPress menu, go to Plugins → Add New. 3. Click the Upload Plugin button at the top of the page. 4. Click Choose File and select the OTTO Pixel ZIP file you downloaded. 5. Click Install Now and wait for the upload to complete. 6. Once installation is confirmed, click Activate Plugin. 🔗 Step 3 — Connect OTTO Pixel to Your Search Atlas Account 1. After activation, return to Search Atlas and navigate to the OTTO setup page for your website. 2. Follow the on-screen instructions to enter your pixel key or connection credentials into the plugin settings as directed. 3. Save your settings and refresh the Search Atlas page to confirm the connection status has updated. 4. If the connection does not update or you are unsure which credentials to use, contact the support team for guidance. 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.

🚀 Deploy Blog Posts to Your Hostinger Website

🔍 Overview If you have created blog posts inside Search Atlas and need to publish them to a website hosted on Hostinger (for example, a client site like bkroofingandgutters.com), you have two main options. You can either use Search Atlas's Website Studio to manage and deploy content directly, or you can manually copy the content into Hostinger's website editor. This article walks you through both approaches. ⚙️ Option 1: Publish via Website Studio (Recommended) Website Studio is the built-in site management tool inside Search Atlas. If your client's Hostinger site is connected to Website Studio, you can publish blog posts directly from the platform. 1. In the left sidebar, click Website Studio. 2. Select the website you want to publish to (for example, bkroofingandgutters.com). If the site is not listed, see the section below on connecting a Hostinger site. 3. Navigate to the Blog or Pages section within Website Studio. 4. Go to Content → Content Genius (What are we writing today?) and click Write an article, Rework existing article, or Restore article, or open an existing draft you have already created. 5. Paste or write your blog content, add a title, meta description, and any images. 6. When ready, click Publish. The post will go live on the connected Hostinger site. 🔗 Connecting a Hostinger Site to Website Studio Before you can deploy content, the Hostinger-hosted website must be connected to Search Atlas. Follow these steps: 1. Log in to your Hostinger account and open the control panel for the relevant website. 2. In the left sidebar of Search Atlas, click Website Studio. 3. In the Website Studio (What will we get done today?) page, click Import Site and enter the domain name (for example, bkroofingandgutters.com). 4. Follow the on-screen instructions to verify domain ownership. This typically involves adding a DNS TXT record or installing a plugin, depending on the site's CMS (for example, WordPress). 5. Once verified, the site will appear in your Website Studio dashboard and you can begin publishing content. Note: If the Hostinger site is built on WordPress, installing the Search Atlas WordPress plugin is the fastest way to connect it. Download the plugin from within Website Studio and upload it via the WordPress admin panel under Plugins → Add New → Upload Plugin. 📋 Option 2: Manually Copy Content into Hostinger If you prefer not to connect the site to Website Studio, or if the connection is still being set up, you can manually copy blog posts into Hostinger's editor. 1. Open your completed blog post inside Search Atlas (for example, from the Content tool or wherever you drafted it). 2. Copy the full text, headings, and any HTML formatting. 3. Log in to your Hostinger account and go to the website's content management area (for example, WordPress admin or Hostinger's Website Builder). 4. Create a new blog post or page and paste the content. 5. Add your featured image, meta title, and meta description. 6. Preview the post, then click Publish. 💡 Tips for a Smooth Deployment - Images: Download any images from Search Atlas before copying content manually, then re-upload them in Hostinger to ensure they load correctly. - Meta data: Always fill in the SEO title and meta description in Hostinger to preserve the optimisation work done in Search Atlas. - Slugs: Match the URL slug to the one recommended in Search Atlas for consistency. - Preview before publishing: Use Hostinger's preview feature to check formatting before the post goes live. 🛠️ Troubleshooting Common Issues - Site not appearing in Website Studio: Make sure the domain has been verified and that any required DNS changes have fully propagated (this can take up to 48 hours). - WordPress plugin not connecting: Confirm the plugin is activated and that the API key entered matches the one shown in your Search Atlas account settings. - Formatting looks broken after pasting: Use the plain-text paste option in Hostinger's editor, then re-apply headings and bold text manually to avoid carrying over unwanted styles. 💬 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 Pixel Integration: Website Studio vs WordPress

🗺️ Overview: Two Integration Paths, One Pixel OTTO uses a tracking pixel to monitor your site and power its SEO automation. However, the way the pixel is installed depends entirely on where your site is built and managed. There are two separate integration paths: - WordPress sites — pixel is deployed via a WordPress plugin integration - Website Studio sites — pixel is deployed via header code embedding inside the Website Studio builder These paths are independent. A pixel active on a WordPress site does not automatically register as active inside Search Atlas, and vice versa. Understanding which path applies to your site is the first step to resolving any status discrepancy. 🔌 Path 1: WordPress Integration If your live site runs on WordPress, the OTTO pixel is connected through a dedicated WordPress plugin. The general process involves installing the appropriate Search Atlas / OTTO plugin, connecting it to your OTTO project, and ensuring the pixel code is correctly applied across your site. Once the plugin is active and the pixel is correctly configured, return to Search Atlas and open your OTTO project to check whether the pixel status has updated to Active. If it does not, see the troubleshooting section below. 🏗️ Path 2: Website Studio Integration If you are building or managing your site inside Search Atlas Website Studio, the WordPress plugin is not used. Instead, the pixel is embedded directly in the site's header code through the Website Studio builder. Within Website Studio, open your project for the relevant domain and add your OTTO pixel code to the site's header code area. Once the code has been added, publish your site — the pixel will not be live until the site has been published. After publishing, return to your OTTO project in Search Atlas and allow some time for the pixel status to update to Active. ⚠️ Why Your Pixel Status May Differ Between Platforms This is the most common source of confusion. Here are the scenarios that cause a status mismatch: - WordPress plugin active, Search Atlas still shows Inactive: The pixel code may not have been applied correctly through the plugin, or there may be a delay before Search Atlas can detect it. - Website Studio code added, but pixel still Inactive: The most common cause is that the site has not been published after adding the pixel code. Changes made inside Website Studio — including header code additions — only take effect on the live site after you explicitly publish them. - Pixel active in one path but not the other: Remember that these are two entirely separate integration paths. Activating the pixel via the WordPress plugin has no effect on a Website Studio project, and vice versa. Confirm which path your domain is actually using. 🛠️ Troubleshooting Pixel Status Issues If your pixel status is not updating as expected, use the checklist below to identify the cause: - Confirm whether your domain is hosted on WordPress or inside Website Studio — apply the correct path for your setup. - For Website Studio: verify that you have published the site after adding or updating the pixel code. - For WordPress: verify that the plugin is active and that the pixel code has been saved within the plugin settings. - Allow sufficient time after publishing or saving for the pixel status to propagate before rechecking in your OTTO project. If you have confirmed the correct path, published your changes, and the pixel status still does not update, escalate to our support team. When you do, please have the following ready: your project name, the domain in question, which integration path you are using (WordPress or Website Studio), and any relevant timestamps for when you made changes. 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 the OTTO Pixel on WordPress Sites

🧩 What Is the OTTO Pixel? The OTTO pixel is a small tracking script that connects your WordPress site to Search Atlas. It allows OTTO to read your site's on-page data and apply SEO automations directly. Until the pixel is confirmed active, OTTO's automation features will remain limited. 📋 Before You Begin - You have admin access to your WordPress site. - You are logged in to Search Atlas and have navigated to OTTO SEO → SEO Automation in the left sidebar (URL: /seo-automation-v3). - You have your Search Atlas API key and OTTO Pixel UUID ready to copy from the dashboard. 🛠️ How to Install the OTTO Pixel on WordPress 1. Install the Search Atlas (MetaSync) plugin on your WordPress site. 2. In WordPress, open Search Atlas → Settings. 3. Paste your Search Atlas API key into the API key field. 4. Paste your OTTO Pixel UUID. 5. Save your changes. The plugin will handle the pixel installation automatically. The raw JavaScript code snippet is only needed for non-WordPress platforms or alternative installs such as Google Tag Manager. ⏳ Why the Status Still Shows "Not Installed Correctly" This is expected behaviour — not an error. After you install the pixel, Search Atlas needs time to detect and verify the script across your site. For new projects, automatic checks run every 15 minutes, so detection typically happens within about 15 minutes from the moment the pixel goes live. During this window, the dashboard will continue to display the "OTTO Pixel is not installed correctly" message even when installation was completed perfectly. Please do not reinstall the pixel or make further changes during this period. Multiple installations can cause duplicate script conflicts that will require you to start over. ✅ How to Confirm the Pixel Is Live Before the Status Updates You can verify the pixel is on your site right now without waiting for the dashboard to update: 1. Open your WordPress site in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (Windows) or Cmd + F (Mac) and search for otto or the first few characters of your pixel code. 4. If the script appears in the source, your installation is correct. The dashboard status will catch up within about 15 minutes on a new project. 🔄 What to Do After 15 Minutes - Refresh the OTTO SEO → SEO Automation page in Search Atlas. - If the status has changed to active or connected, no further action is needed. - If the status still shows an error after about 15 minutes and the pixel code is not visible in your page source, move on to the troubleshooting steps below. 🔧 Troubleshooting a Genuinely Failed Installation If the pixel code is not found in your page source after about 15 minutes, work through these checks: - Caching: WordPress caching plugins (e.g., WP Rocket, W3 Total Cache) may serve old pages. Clear your site cache and check the page source again. - Theme updates: If your theme was recently updated, the header.php edit may have been overwritten. Re-paste the pixel or switch to a plugin-based installation method. - Plugin conflicts: Temporarily deactivate security or optimisation plugins that may strip unrecognised scripts from the <head> tag, then check the page source. - Correct placement: Confirm the pixel is placed before </head> and not inside the <body> or footer section. - Multiple pixel copies: Search your page source for more than one instance of the script. Remove duplicates and leave only one copy. 💬 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.

🛠️ Clear Stale WILDFIRE Links

🔍 Why removed links may remain WILDFIRE links can remain visible after removal when an older payload is still cached, stored by the plugin, or present in rendered site code. Freezing or deactivating a project may stop new changes, but it does not always immediately remove links already published. ✅ Check the site first 1. Open the affected page in a private browser window. 2. View the page source and search for the WILDFIRE link or anchor text. 3. Clear your website, CDN, and WordPress cache, then check the page again. 4. Confirm whether the link is still present in the page source, not only in the browser view. If the link remains in the page source after caching has been cleared, the stale payload requires platform-side cleanup. 🧹 Request a force purge Search Atlas support can review the project and request a force purge or re-push of the WILDFIRE payload. Include the site URL, affected page URLs, link destinations, and whether the project is active, frozen, or unsubscribed. Do not manually edit unknown database keys or run unverified WP-CLI commands. The correct cleanup method depends on the project state and plugin version, and unsupported changes can create additional site issues. 🚫 Disable WILDFIRE account-wide If you want WILDFIRE disabled for all sites, state this clearly in your request. Account-wide disabling is separate from removing stale links, so ask for both actions if needed: - Disable WILDFIRE for the account. - Force-purge existing stale WILDFIRE payloads. - Re-push the corrected plugin configuration where required. 📍 Where to review OTTO SEO Open AI SEO from the left sidebar, then select OTTO SEO. Use All Sites to review project status, or open Overview to scan and manage OTTO settings. These screens help confirm whether a site is active or frozen, but they may not remove an already published stale payload. 💬 Get help with cleanup 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 DNS Cloudflare API Token Setup Guide

🔍 Overview When installing OTTO via Cloudflare, it is essential to use an account-level API token — not a personal API token. Using a personal token may show a "Connected" status in Search Atlas, but OTTO will not complete installation on your site. This article walks you through creating the correct token so your OTTO installation works immediately. ⚠️ Why Personal API Tokens Do Not Work Cloudflare offers two types of API tokens: - Personal API tokens — scoped to individual user profiles and found at dash.cloudflare.com/profile/api-tokens. These do not grant the account-level permissions required for OTTO to deploy its worker scripts. - Account-level API tokens — created from within your Cloudflare account dashboard. These provide the necessary permissions for worker creation and script deployment, which OTTO requires to install correctly. Even though Search Atlas may display "Connected" with a personal token, the underlying worker deployment will silently fail. Always use an account-level token to ensure full functionality. 🛠️ How to Create a Cloudflare Account-Level API Token 1. Log in to your Cloudflare account at dash.cloudflare.com. 2. From the top navigation, select the account you want to connect to OTTO (not your user profile). 3. In the left sidebar, click Manage Account, then select API Tokens. 4. Click Create Token. 5. Choose Create Custom Token to configure the required permissions manually. 6. Under Permissions, add the following: - Account — Workers Scripts — Edit - Account — Workers Routes — Edit - Zone — Zone — Read - Zone — DNS — Edit 7. Under Account Resources, set the token to apply to your specific account. 8. Under Zone Resources, select All zones or the specific zone (domain) where OTTO will be installed. 9. Click Continue to Summary, review your settings, then click Create Token. 10. Copy the generated token immediately — Cloudflare will only display it once. 🚀 How to Connect the Token in Search Atlas 1. In Search Atlas, navigate to Left sidebar → OTTO SEO. 2. Open or create the OTTO project for your domain. 3. When prompted for your Cloudflare credentials, paste the account-level API token you just created. 4. Complete the connection flow. Search Atlas should display "Connected" and OTTO should begin installing on your site immediately. ✅ How to Confirm OTTO Installed Successfully After connecting with the correct token, verify the installation was successful by checking the following: - The OTTO status in your project shows as Active (visible under Left sidebar → OTTO SEO). - The Cloudflare Workers section of your account shows a new worker script deployed by OTTO. - Your website loads correctly with no disruption to DNS or page performance. 💡 Common Mistakes to Avoid - Using a personal API token — always create the token from the account dashboard, not your user profile page. - Missing permissions — ensure all four permission sets (Workers Scripts, Workers Routes, Zone Read, DNS Edit) are included. Missing any one of them can prevent deployment. - Wrong zone scope — if the token is scoped to the wrong zone, OTTO cannot access your domain. Double-check the zone resources during token creation. - Token copied incorrectly — the token is shown only once. If you missed copying it, delete it and generate a new one. 💬 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 instantly connected with a member of our team.

📘 Using Search Atlas with 10Web AI Website Builder (WordPress)

Using Search Atlas with a WordPress site built on the 10Web AI Website Builder is a supported and effective setup for SEO. While 10Web provides strong performance and infrastructure, Search Atlas adds an automated SEO execution layer that handles content, metadata, schema, and ongoing optimization. This article explains how the two platforms work together and how to configure them for optimal SEO results. 🧠 How 10Web and Search Atlas Work Together 🏗️ 10Web (Infrastructure Layer) 10Web provides: - High-performance hosting - Strong PageSpeed scores (often 90+) - Built-in performance and caching tools This creates a solid technical foundation for SEO. 🤖 Search Atlas (Execution Layer) Search Atlas adds: - Automated SEO execution - Content publishing and optimization - Technical SEO fixes and schema deployment The Search Atlas WordPress plugin (v3) acts as the bridge between Search Atlas and your 10Web-built site. ✅ Key Advantages of Using Search Atlas on 10Web When combined, the platforms cover different but complementary SEO needs: - One-Click Publishing Generate long-form content in Search Atlas and publish directly to WordPress with SEO tags preserved. - Automated Technical Fixes Automatically identifies and resolves issues such as: - 404 errors - Broken links - Metadata gaps - Advanced Schema Deployment Deploys advanced schema (FAQ, Article, etc.) that may not be handled natively by 10Web. - Google Search Console Visibility View GSC data for specific URLs directly inside the WordPress dashboard. ⚙️ Recommended Setup for Best SEO Results Follow this configuration path for optimal performance: Step 1 — Install and Sync the Plugin Install the Search Atlas WordPress plugin and connect it using your API key. Step 2 — Migrate Existing SEO Data If the site previously used plugins like Yoast or RankMath, use the plugin’s one-click import to migrate existing SEO data into the Search Atlas system. Step 3 — Set Up OTTO SEO Enter your OTTO Pixel UUID in the plugin settings (Search Atlas → Settings, under the OTTO Server-Side Rendering section) to enable real-time SEO optimizations. Step 4 — Build Topical Authority Use the Topical Map Creator to plan service-area or niche content, then generate drafts using Search Atlas AI tools. 🔧 Compatibility Notes - Search Atlas is cache-aware - Fully compatible with modern builders like Elementor (used by 10Web) - Does not overwrite existing Yoast configurations - Designed to run alongside 10Web performance tools without slowing down the site ⚠️ To avoid conflicts: - Avoid overlapping SEO plugin features - Assign one primary tool per SEO function (meta tags, schema, etc.) - Check the site’s <head> for duplicate meta or schema injections ❓ FAQs ❓ Does Search Atlas work with 10Web AI sites? Yes. It works well with WordPress sites built on 10Web. ❓ Will it conflict with 10Web or Elementor? No. Search Atlas is designed to be compatible with modern builders and caching systems. ❓ Does Search Atlas overwrite existing SEO plugins? No. It complements existing setups and does not overwrite Yoast configurations. ❓ Is this recommended for optimal SEO? Yes. The combination provides both performance (10Web) and automated SEO execution (Search Atlas). Using Search Atlas with a 10Web-built WordPress site is a recommended setup for scalable, automated SEO. 10Web handles infrastructure and speed, while Search Atlas handles ongoing SEO execution and optimization.

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

🛑 Stop False-Positive Domain Verification Emails

What Is Happening? Some customers receive repeated emails warning that their domain is blocked, even though their domain is fully operational and no real issues are present. This is a known false-positive in the domain verification system. The background process that runs periodic domain health checks can, in certain cases, fail to record a completed result — leaving the domain in an unresolved state. The next scheduled check then re-triggers the warning email instead of recognising the domain as healthy. Why Does This Happen? The false-positive emails are caused by an issue in the backend DNS verification worker, not by any actual problem with your domain or DNS configuration. Because the root cause is inside the platform's backend systems, it cannot be resolved through changes on your end. Our engineering team must investigate and clear the verification state directly. What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Your domain name — the exact domain that is receiving the false-positive warning emails. - Your project or account name — so our team can locate the correct account record. - A screenshot or copy of the warning email — including any error message or reference code shown in the email. - The approximate date the emails started — this helps our team identify which verification cycle triggered the issue. - Confirmation that your domain is functioning normally — for example, that your site is live and accessible. You do not need to make any changes to your DNS records or domain settings. Our team will handle the fix on the backend once they have confirmed the false-positive state. 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 the OTTO Pixel in Captivate Hub

🧭 Overview The OTTO Pixel is a small tracking script that allows OTTO to monitor your site's SEO performance and automate optimizations. If your website is built on Captivate Hub and your domain is registered with GoDaddy, you only need to install the pixel inside Captivate Hub. You do not need to touch your GoDaddy account — GoDaddy is only your domain registrar and does not host your site content. 🔍 Step 1: Find Your OTTO Pixel Code 1. Log in to your Search Atlas account. 2. Navigate to the OTTO or SEO section of your account where pixel or tracking settings are available — the exact location may vary depending on your plan and account configuration. 3. Select the project connected to your Captivate Hub website. 4. Locate your OTTO Pixel script for that project. 5. Copy the full pixel script to your clipboard. The code is a short <script> tag and is unique to each site (it carries that OTTO project's own ID via data-uuid), so each site needs its own snippet from its own Installation Guide — do not share it. 🖥️ Step 2: Open the Code Injection Area in Captivate Hub 1. Log in to your Captivate Hub account. 2. From the main dashboard, click on the website or hub you want to track. 3. Look for a Settings area within the hub editor — the exact label and location may vary depending on your Captivate Hub plan and version. 4. Within Settings, look for an option related to custom code or code injection — the exact label depends on your Captivate Hub plan and version. 5. You should see a text area for code that loads in the <head> section of your pages. 📋 Step 3: Paste and Save the Pixel 1. Click inside the code area designated for the <head> section. 2. Paste the OTTO Pixel script you copied from Search Atlas. 3. Make sure the code appears on its own line and is not merged with any other scripts already present. 4. Save or publish your changes to apply them. Check whether your Captivate Hub plan requires you to republish your site before changes go live. ✅ Step 4: Confirm the Pixel Is Working 1. Return to Search Atlas and navigate back to the section where your OTTO Pixel settings are located. 2. Check the installation status for your project. 3. If the pixel is not yet detected, wait a few minutes and refresh — it can take a moment for Captivate Hub to propagate the published change before Search Atlas can confirm the pixel is active. ⚠️ Do I Need to Change Anything in GoDaddy? No. GoDaddy is only responsible for pointing your domain name to your Captivate Hub site. It does not control the content or code on your pages. All pixel installation work happens entirely inside Captivate Hub. 🛟 Still Need Help? If you are unsure where to find the custom code or code injection area in your specific Captivate Hub plan, or if the pixel does not appear to be detected after following these steps, our team can help you locate the correct settings and verify the installation. When reaching out, please have the following ready: your project name in Search Atlas, the URL of your Captivate Hub site, and a description of where you are stuck or any error you are seeing. 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 Pixel on Shopify: GTM vs Native Installation

Overview If your OTTO pixel appears to fire correctly in Google Tag Manager (GTM) but the OTTO dashboard still shows it as undetected, you may be experiencing a limitation of GTM-based deployments on Shopify. This article explains the general difference between GTM and native installation approaches and what to do if you need help resolving detection issues. GTM vs Native Installation on Shopify There are two common ways to deploy the OTTO pixel on a Shopify store: - GTM-based installation: The pixel is loaded through a Google Tag Manager container. This method can introduce additional layers between the pixel and the page, which may affect how reliably the pixel is detected. - Native installation: The pixel code is added directly to your Shopify theme files. This approach typically provides a more direct and consistent load of the pixel on every storefront page. If you are currently using GTM and the OTTO dashboard is not detecting your pixel, switching to a native installation may resolve the issue. For the exact steps to complete either type of installation on your specific Shopify setup, our support team can walk you through the process. What to Have Ready When You Contact Support To help our team resolve your pixel detection issue as quickly as possible, please have the following information ready: - Your Shopify store URL - The installation method you are currently using (GTM or native) - A description of what the OTTO dashboard shows for your pixel status - Any error messages or screenshots related to the pixel detection issue If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📰 Accessing Publishers via Publication.media Marketplace

🔍 Overview Search Atlas integrates with Publication.media, an independent publisher marketplace where you can browse and connect with publishers for content placements and link-building opportunities. Because Publication.media is a separate platform, it requires its own login — even if you are already signed into Search Atlas. This article explains why a separate account is needed, what to expect when you click a publisher link, and how to get up and running quickly. ❓ Why Am I Being Redirected to a Login Page? When you click on a publisher link inside Search Atlas, you are taken directly to Publication.media. This redirect is expected behaviour and is not a bug or an error with your Search Atlas account. Publication.media is an independent marketplace platform. It maintains its own user database and authentication system, which is separate from Search Atlas. Your Search Atlas credentials do not carry over automatically, so you will need to log in to — or register for — a Publication.media account before you can interact with publishers. 🚀 How to Get Started with Publication.media 1. Inside Search Atlas, click the publisher link or marketplace entry you want to explore. You will be redirected to the Publication.media login page. 2. If you already have a Publication.media account, enter your credentials and log in. 3. If you do not have an account yet, click Sign Up on the Publication.media login page and complete the registration process. Registration is free. 4. Once logged in to Publication.media, you will have full access to publisher profiles, pricing, and placement options. 5. Return to Search Atlas at any time to continue your SEO workflow — your two accounts operate side by side. 💡 Key Things to Remember - Two separate accounts are required: one for Search Atlas and one for Publication.media. - The redirect is intentional: clicking a publisher link will always take you to Publication.media, regardless of your Search Atlas login status. - Your accounts are not linked automatically: use the same email address for both platforms if you want to keep things organised, but this is not mandatory. - Publication.media manages its own support: for questions specific to publisher listings, pricing, or orders placed on Publication.media, consult their own help resources after logging in. 🛠️ Troubleshooting Common Issues - Forgot your Publication.media password? Use the Forgot Password link on their login page to reset it. This cannot be done from within Search Atlas. - Publisher link not loading? Make sure your browser allows pop-ups and redirects from Search Atlas, then try clicking the link 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. Additional Notes These two accounts are not linked automatically. You must register on publication.media yourself, using whichever email address you prefer. It does not need to match your Search Atlas email.

🔗 Connect Zoom to Your Search Atlas Workspace

🌐 Overview Search Atlas supports a native Zoom integration that connects your Zoom account to the platform's AI Agent, Chat, Notes, Calendars, and Phone features. Once connected, Zoom becomes a supported data connector across your workspace, allowing seamless collaboration and communication without switching tools. ✅ Before You Begin - You must have an active Zoom account (free or paid). - You need admin or owner-level access in your Search Atlas workspace to manage integrations. - Make sure your browser zoom level is set to 100%. Non-standard zoom levels (for example, 80% or 125%) can cause the integrations panel to become unresponsive or hidden. Reset browser zoom with Ctrl + 0 (Windows) or Cmd + 0 (Mac). 🔌 How to Connect Zoom 1. Log in to your Search Atlas account. 2. Navigate to your workspace Settings panel (typically accessible from your Avatar Menu (👤) or sidebar menu). 3. Locate the Integrations section. 4. Find Zoom in the list of supported connectors. 5. Click Connect next to the Zoom option. 6. A Zoom authorisation window will open. Sign in with your Zoom credentials and click Allow to grant the required permissions. 7. Once authorised, Zoom will appear as Connected in your integrations list. 🤖 What the Zoom Integration Enables After connecting, Zoom works as a supported connector across the following Search Atlas features: - AI Agent — the AI can reference and act on Zoom meeting data and events. - Chat — Zoom conversations can surface within your workspace communication layer. - Notes — meeting notes and transcripts can be pulled into your workflow. - Calendars — Zoom events sync with your connected calendar view. - Phone — Zoom Phone data is accessible within the platform where supported. 🛠️ Troubleshooting Common Issues - Integrations panel not visible: Reset your browser zoom to 100% using Ctrl + 0 (Windows) or Cmd + 0 (Mac), then reload the page. - Zoom not appearing in the connectors list: Clear your browser cache, reload the page, and confirm you are on the latest version of your browser. - Authorisation fails: Ensure you are logged into the correct Zoom account and that your Zoom plan supports third-party app integrations. - Integration shows as disconnected after saving: Try disconnecting and reconnecting Zoom, then refresh your browser. 💡 Tips for Best Results - Use a Zoom Business or Pro plan to unlock the full range of connector features, including Phone and advanced Calendar sync. - If your organisation uses Zoom SSO, make sure your IT team has whitelisted Search Atlas as an approved third-party app. - Revisit the Integrations panel periodically to confirm Zoom remains connected, especially after Zoom password or security changes. 💬 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.

⚡ Consolidating or Merging Search Atlas Projects

Overview Search Atlas does not currently support a one-click merge or direct combination of two separate projects. If you need to consolidate data from multiple projects into one, you will need to do so manually. This article explains what to prepare and how to approach the process. Why Direct Merging Is Not Supported Each Search Atlas project is treated as an independent workspace. Because of this, a native merge feature is not available at this time. Consolidation must be done by manually re-adding or transferring data from your secondary project into your primary project. Before You Begin: What to Gather Before attempting any consolidation — or if you need to escalate to our team — have the following ready: - The names of both projects you want to consolidate, as they appear in your account. - The primary domain for each project — confirm which will become your single source of truth. - A list of features and data active in both projects (e.g., tracked keywords, competitor comparisons, local SEO assets) so you know what needs to be transferred. - Your rank history preference — decide which project's historical data you want to preserve, since history from the secondary project cannot be automatically carried over. - Team member access details — confirm who has edit permissions on both projects before making changes. General Consolidation Approach Because there is no automated merge tool, the general workflow is: 1. Identify your primary project — the one you will keep and work from going forward. 2. Note all data and settings in your secondary project that you want to retain, including tracked keywords, competitor comparisons, local SEO details, keyword groupings, and any custom configurations. 3. Manually re-add that data into your primary project — go into the relevant sections of your primary project and recreate or re-enter the data from your secondary project. 4. Recreate any settings or configurations from the secondary project that cannot be transferred, such as tracked keyword groupings, local SEO details, or custom tags. 5. Verify your primary project has all the data you need before deleting or archiving the secondary project. Note that historical rank tracking data from the secondary project cannot be merged into the primary project's history. Only data that you manually re-enter will carry over. When to Contact Support If you are unsure how to transfer a specific type of data between projects, or if you encounter any issues during the consolidation process, our team can guide you through the steps specific to your account setup. Please have both project names and a description of the data you are trying to consolidate ready before reaching out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Configure Integration Connection Request Sharing

Integration connection request sharing is now fully configurable, giving you greater control over how your team and collaborators interact with connected integrations across your account. ✨ What's New You can now define exactly how integration connection requests are shared within your account. This update introduces configurable sharing settings that let you control which users or collaborators can view, receive, or act on connection requests for third-party integrations. Previously, this behavior was fixed and could not be adjusted — now it adapts to your team's structure and workflow needs. 🛠️ How to Use It 1. Navigate to the Integrations section within your platform settings. 2. Select the integration for which you want to adjust connection request sharing. 3. Open the Connection Request Sharing configuration panel. 4. Choose your preferred sharing option — such as restricting access to specific users or enabling sharing across your entire team. 5. Save your changes to apply the new configuration immediately. 📋 What to Expect Once updated, all new connection requests for the configured integration will follow your selected sharing rules. Existing active connections will not be impacted by this change. Sharing options available to you may vary based on the integration type and your account's permission level. Account administrators are encouraged to review these settings to ensure alignment with your team's access and collaboration policies. 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.

🔗 Meta Ads Lead Forms and WhatsApp Sync Explained

📌 Overview Search Atlas Smart Ads lets you build and manage Meta ad campaigns directly from the platform. However, two specific scenarios — lead form ads with a WhatsApp destination and re-syncing manually edited campaigns — have known limitations you should be aware of before launching or modifying campaigns. 🚫 Why You Can't Create Lead Form Ads with a WhatsApp Destination When creating a Meta campaign in Search Atlas, you may want to combine an Instant Form (lead form with no landing page) with a WhatsApp destination so that leads flow directly into a WhatsApp conversation. This combination is currently not supported in Search Atlas Smart Ads. Here is why this limitation exists: - Meta treats WhatsApp as a Click-to-Message destination, which uses a different campaign objective and ad format than Instant Form lead generation. - Search Atlas currently supports standard lead form ads (Instant Forms) and click-based destinations separately, but cannot combine them in a single ad set through the platform. This is a known product limitation. Until support is expanded, you will need to create campaigns that require both an Instant Form and a WhatsApp destination directly in Meta Ads Manager outside of Search Atlas. ✅ Workaround: Build This Campaign Type in Meta Ads Manager If your campaign requires both an Instant Form and a WhatsApp destination, you will need to create it directly in Meta Ads Manager for now. Once the campaign is live, you can still use Search Atlas to monitor performance, even if you cannot create or edit it directly from the platform. 🔄 Why Search Atlas Loses Sync with Manually Edited Campaigns If you create a campaign in Search Atlas and then make changes directly in Meta Ads Manager — such as adjusting targeting, budgets, placements, or ad creative — Search Atlas may no longer reflect those changes accurately. Here is what causes it: - Search Atlas maintains its own campaign state based on what was configured and published through the platform. Changes made outside the platform are not automatically pulled back into Search Atlas. - Two-way API synchronization between Search Atlas and Meta has known constraints — edits made in Meta Ads Manager may not be reflected in Search Atlas in real time or at all. To avoid sync issues, make all campaign edits from within Search Atlas whenever possible. If you have already made changes in Meta Ads Manager and are experiencing sync problems, please contact our support team and have the following information ready: - The name of the affected campaign - The date and type of changes made in Meta Ads Manager - Any error messages or discrepancies you are seeing 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 or Update the Search Atlas WordPress Plugin Manually

The Search Atlas WordPress plugin (MetaSync) may not always appear in the WordPress.org plugin directory. When that happens you can still install or update it yourself, because the plugin ZIP file is available inside your Search Atlas dashboard. You do not need to wait for the team to send it. How do I get the plugin ZIP file? 1. Sign in to your Search Atlas dashboard. 2. In the left sidebar, open OTTO SEO, then Installation Guide. 3. In the manual WordPress installation steps, use the Download the plugin step to download the ZIP file. 4. Save the file to your computer. Do not unzip it. WordPress needs the ZIP format. How do I install or update the plugin from the ZIP file? We recommend a full backup of your site files and database first. 1. Sign in to your WordPress admin dashboard. 2. Go to Plugins, then Add New, then Upload Plugin. 3. Choose the ZIP file and click Install Now. 4. If WordPress tells you the plugin is already installed, choose the option to replace the current version with the uploaded one. 5. Activate the plugin if it is not already active. 6. Go to Plugins, then Installed Plugins, and check the version number under the plugin name. What if my plugin is outdated and my host reports a security notice? Download the latest ZIP file as described above and install it over the current version. After the update, check the version number again. If your host still reports a notice for the new version, reach our team through live chat and tell us the plugin version shown on your site and the text of the notice.

🛠️ How to Confirm Shopify Changes Are Live

This article explains the difference between a change being deployed within Search Atlas and that change actually appearing on your live Shopify storefront — and shows you exactly how to confirm the update went through. 🔍 What "Deployed" Actually Means In Search Atlas, deployed means the change has been pushed from Search Atlas to your connected Shopify store. It does not mean the change is only saved inside Search Atlas. However, a successful deploy inside Search Atlas does not always guarantee the update is immediately visible on your live Shopify page — sync delays, caching, or a broken connection can prevent the change from appearing. 🛠️ Step-by-Step 1. Check the deployment status in Search Atlas: Locate the change you made in your Search Atlas project and confirm whether it shows a successful or unsuccessful deployment state. If the deployment did not complete successfully, the change has not yet been written to Shopify. 2. Verify your Shopify connection is active: In your Search Atlas project, review your Shopify integration settings to confirm the connection is active and authenticated. An expired or disconnected integration can cause a deploy to appear complete inside Search Atlas while nothing is actually written to Shopify. 3. Check your live Shopify page directly: Open your Shopify storefront in a browser tab. Use Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to perform a hard refresh, bypassing any browser cache. Navigate to the specific page where the change should appear and confirm whether the updated content is present. 4. Review Shopify's activity or edit history: In your Shopify Admin, check your theme's edit history or relevant activity logs to see whether a change was recorded at the time you deployed from Search Atlas. This can help confirm whether data was received by Shopify. 5. If the deployment appeared successful but Shopify still shows the old content: Try re-deploying the change from within your Search Atlas project. If the problem persists, disconnect and reconnect the Shopify integration, then re-deploy. ✅ How to Confirm It Worked The change is live when the following are both true: - The deployment status in Search Atlas indicates the change was successfully pushed. - Your live Shopify page (hard-refreshed) displays the updated content exactly as written. If either of these checks fails, the change has not fully propagated and you should follow step 5 above before reaching out for support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🌐 Website Studio Wix Integration and Feature Roadmap

What Is Website Studio? Website Studio is Search Atlas's built-in website builder. It lets you create and manage web pages directly within the Search Atlas platform without leaving your workflow. Does Website Studio Connect with Wix? Website Studio and Wix are separate platforms. The specifics of what is currently supported — including any syncing, publishing, or integration capabilities between the two — have not been confirmed in detail. If you are trying to use a particular integration capability and are unsure whether it is supported, our team can clarify based on your specific use case. What Features Are Coming Soon? The Search Atlas team is actively working on expanding Website Studio's capabilities. Because this area is actively evolving, specific feature details and timelines are not yet confirmed. Our support team can share the latest information relevant to your use case. What to Have Ready When You Contact Support To help our team give you the most accurate and relevant information, please have the following ready: - Your Search Atlas project name or account email - A description of the specific Website Studio or Wix integration capability you are trying to use or understand - Any error messages or unexpected behavior you have encountered, including approximate timestamps 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 Google Search Console and Boost Content Score

🔍 Overview This article covers two common tasks: (1) adding your website as a property in Google Search Console (GSC) and connecting it to Search Atlas, and (2) improving your Content Value/Parameter score in OTTO from a low baseline (around 29–31/100) to 70 or higher. Follow both sections in order for the best results. 🌐 Step 1 — Add Your Site to Google Search Console If your site is not yet verified in GSC, complete these steps first. 1. Go to Google Search Console at search.google.com/search-console and sign in with your Google account. 2. Click Add property in the top-left dropdown. 3. Choose Domain as the property type. Enter your domain without a prefix — for example, balancedlifetherapy.com. Using the Domain type covers all subdomains and both HTTP and HTTPS versions automatically. 4. Click Continue. Google will display a DNS TXT record. 5. Copy the TXT record and add it to your domain's DNS settings through your domain registrar (such as GoDaddy, Namecheap, or Cloudflare). The exact steps vary by registrar, but you are typically looking for a DNS Management or Advanced DNS section. 6. Return to GSC and click Verify. DNS propagation can take a few minutes to up to 48 hours, so verify as soon as possible and retry if it does not confirm immediately. Once Google confirms ownership, your property is active and GSC will begin collecting data. 🔗 Step 2 — Connect or Reconnect GSC to Search Atlas After your site is verified in GSC, link it to Search Atlas so the platform can pull your performance data. 1. In Search Atlas, navigate to Site Metrics → Site Explorer using the left sidebar. 2. Click Open Google Search Console to reach the Manage Sites page. 3. Click Connect GSC Account and sign in with the same Google account used to verify the property. 4. Select balancedlifetherapy.com (or your domain) from the list of verified properties and confirm. 5. If you previously had a connection that broke, look for a Reconnect or Refresh button in the same GSC dashboard section and click it. This re-authorises the connection without requiring you to re-verify ownership in Google. 6. Wait a few minutes, then refresh the page. Search Atlas will begin importing impressions, clicks, and ranking data from GSC. Tip: If your domain does not appear in the property list during Step 4, confirm that the Google account you signed in with has Owner or Full User permission on the GSC property. 📈 Step 3 — Understand Your Content Value Score The Content Value/Parameter score in OTTO reflects how well your on-page content is optimised across key SEO parameters — including keyword usage, structure, readability, internal linking, and metadata completeness. A score of 29–31/100 means most of these parameters are partially or fully unmet. Scores are calculated per page and rolled up at the site level. To see which parameters are dragging your score down, open OTTO and select the specific page or URL you want to improve. ✅ Step 4 — Raise Your Content Score to 70+ Work through the following areas to push your score above 70. OTTO will update the score in real time as you apply changes. 1. Optimise your target keyword placement. Make sure your primary keyword appears in the page title, the first paragraph, at least one H2 heading, and naturally throughout the body. OTTO highlights missing placements directly in the editor. 2. Complete your metadata. Write a unique, descriptive meta title (50–60 characters) and meta description (140–160 characters) that include the target keyword. Pages with missing or duplicate metadata receive a significant score penalty. 3. Improve content length and depth. Thin content scores poorly. Review OTTO's recommended word count for your topic and expand sections that are too short. Add supporting subtopics that OTTO identifies as relevant to your keyword cluster. 4. Fix heading structure. Use a single H1 per page and organise content with H2 and H3 subheadings. OTTO flags pages with broken or missing heading hierarchies. 5. Add internal links. Link from this page to at least two or three relevant pages on your site, and ensure other relevant pages link back to it. Internal linking is one of the fastest wins for content score. 6. Include semantic keywords. OTTO provides a list of related terms and entities to include. Aim to cover at least 80% of the suggested terms without forcing them unnaturally into the copy. 7. Resolve any flagged issues. Check the OTTO task list for specific warnings — such as missing image alt text, duplicate content flags, or slow page speed — and resolve each one. Each resolved task contributes directly to the score. After applying changes, click Re-analyse or Refresh Score in OTTO to see your updated Content Value score. Most sites reach 70+ after addressing metadata, keyword placement, and semantic coverage together. 💡 Quick-Reference Checklist - Domain property added and verified in Google Search Console - GSC connected (or reconnected) inside Search Atlas - Primary keyword in title, first paragraph, and at least one H2 - Meta title and meta description written and within character limits - Content length meets OTTO's recommendation for the topic - Heading hierarchy is logical (one H1, multiple H2/H3) - At least two internal links added to and from the page - 80%+ of OTTO's semantic keyword suggestions covered - All OTTO flagged issues resolved 🆘 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.

🔄 CMS SYNC & Publishing Platform Strategy Guide

🧭 Overview Search Atlas offers a native CMS SYNC integration with WordPress, which changes how you should think about where to publish your articles. This guide walks you through the differences between Shopify and WordPress for content publishing, how CMS SYNC fits into your workflow, and how to make the right platform choice for your SEO strategy. 🐦 Fixing Twitter Card Metadata Before choosing a publishing platform, ensure your Twitter Card metadata is correctly configured. Twitter Cards require the following meta tags in your page <head>: - twitter:card — set to summary, summary_large_image, or another supported type. - twitter:title — matches your article's primary title. - twitter:description — a concise summary under 200 characters. - twitter:image — a publicly accessible image URL, minimum 144×144 px. On WordPress, an SEO plugin such as Yoast or Rank Math handles these tags automatically under the Social settings for each post. On Shopify, Twitter Card tags are included in most themes by default, but you may need to edit your theme.liquid file or install a third-party SEO app if tags are missing or incorrect. Always validate your tags using the Twitter Card Validator after making changes. ⚖️ Shopify Blog vs. WordPress: Key Differences Both platforms can host blog content, but they serve different primary purposes and have distinct SEO capabilities. - Shopify Blog is built for e-commerce first. Its blogging feature is functional but limited — you get basic post creation, tags, and author fields. Customising URL structures, schema, or metadata requires theme edits or paid apps. - WordPress is purpose-built for content management. It offers granular control over SEO metadata, URL slugs, schema markup, internal linking structures, categories, and taxonomies — all essential for a strong content strategy. If your primary goal is publishing articles at scale to drive organic traffic, WordPress consistently provides more flexibility and SEO control than Shopify's blog module. 🔗 What Is CMS SYNC and How Does It Work? CMS SYNC is a Search Atlas feature that pushes content you create or optimise inside the platform directly to your connected WordPress site — no copy-pasting required. Here is how the workflow operates: 1. Connect your WordPress site to Search Atlas via the Avatar Menu (👤) (avatar) → Settings → CMS Connectors. 2. Write or optimise your article inside Search Atlas using the Content Editor or AI writer. 3. When your content is ready, select Publish via CMS SYNC. 4. Search Atlas pushes the article to your WordPress site as a draft or live post, depending on your settings. 5. All formatting, headings, and metadata configured inside Search Atlas are preserved on publish. CMS SYNC significantly reduces the time between content creation and live publishing, and keeps your Search Atlas content data linked to live performance metrics. ⚠️ CMS SYNC Limitations to Know - CMS SYNC is currently supported for WordPress only. There is no native sync to Shopify, Webflow, Wix, or other CMS platforms at this time. - Images must be hosted or accessible via URL before syncing — very large media files may require manual upload to your WordPress media library. - Custom post types or heavily modified WordPress themes may require minor adjustments after the first sync to ensure correct display. - Republishing an already-synced article will overwrite the existing WordPress post — always review before re-syncing. 📊 SEO Implications by Platform Platform choice has a direct impact on your SEO outcomes. Consider the following: - WordPress + CMS SYNC gives you full control over title tags, meta descriptions, Open Graph tags, Twitter Cards, canonical URLs, structured data, and XML sitemaps. This level of control is critical for competitive content strategies. - Shopify Blog is well-suited for product-adjacent content — how-to guides tied to your catalogue, buying guides, or brand storytelling — where the primary conversion goal is the product page rather than organic traffic growth. - WordPress sites consistently allow faster iteration on on-page SEO because changes are made in a single interface without theme dependencies. ✅ Which Platform Should You Use? Recommended Use Cases - Use WordPress with CMS SYNC if: your strategy centres on scaling organic traffic through blog content, you want to manage your entire content lifecycle inside Search Atlas, or you need precise metadata and schema control. - Use Shopify Blog if: you operate a Shopify store and want simple, on-brand content that supports your product pages, and your content volume is low enough that manual publishing is not a bottleneck. - Use both if: you run a Shopify store but also maintain a WordPress subdomain or separate domain for your content hub. In this case, publish all editorial content to WordPress via CMS SYNC, and keep Shopify blog posts limited to store-specific announcements or product updates. 🚀 Getting Started with CMS SYNC 1. In Search Atlas, go to Settings → CMS Connectors. 2. Enter your WordPress site URL and generate an API connection using the Search Atlas WordPress plugin. 3. Test the connection with a draft post before syncing live content. 4. Return to any article in your Content Editor and use the Publish button to sync directly to WordPress. 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 Pixel Compatibility with Website Platforms

🧩 What Is the Search Atlas Pixel? The Search Atlas pixel is a small JavaScript snippet you place on your website. It tracks visitor behaviour, conversion events, and campaign performance — feeding data back into your Search Atlas dashboard so you can measure ROI accurately. Whether the pixel works on your site depends on whether your website platform allows custom JavaScript or third-party tracking scripts. 🚗 Car Dealer Platforms — Compatibility Overview Car dealership websites are often managed by specialist automotive platforms. Pixel acceptance varies by provider. The table below summarises the most common platforms and their compatibility status. - DealerSocket / CDK Digital (now Tekion): Supports third-party pixels via the Tag Manager section in the admin panel or through a dedicated script injection field. Custom JavaScript is permitted on most package tiers. - DealerInspire: Allows third-party tracking scripts. You can add the Search Atlas pixel in the site's global header/footer script area. Contact your DealerInspire account rep if the option is not visible — it may need to be enabled on your account. - Dealer.com (Cox Automotive): Supports pixel installation through their third-party tag management interface. Access is usually available in the Settings → Tracking & Analytics section of your Dealer.com dashboard. - Sincro (formerly Digital Air Strike): Permits custom scripts. Use the script injection option in the platform's admin area or request placement assistance from Sincro support. - Gubagoo / Widewail / other chat/lead widgets: These are add-ons, not full CMS platforms. The pixel must be placed on the underlying site platform, not inside these widgets. - WordPress-based dealer sites: Fully compatible. Install the pixel via a header plugin (e.g., Insert Headers and Footers) or directly in the theme's <head> section. If your platform is not listed above, the key question to ask your platform provider is: "Can I add a custom JavaScript snippet to the global header or footer of my site?" If the answer is yes, the Search Atlas pixel will work. 📋 General Platform Compatibility — Other Common Providers - Shopify: Add the pixel under Online Store → Themes → Edit Code → theme.liquid before the closing </head> tag, or use the Custom Pixel feature under Settings → Customer Events. - Wix: Use the Marketing Integrations → Custom Code section in the Wix dashboard. Paste the pixel in the Head section, set it to load on All Pages. - Squarespace: Go to Settings → Advanced → Code Injection and paste the pixel into the Header field. - Webflow: Open Project Settings → Custom Code → Head Code and paste the pixel there. Publish after saving. - Search Atlas Website Studio: Fully compatible and natively integrated. No manual pixel installation is needed if you built your site inside Search Atlas. Navigate to the left sidebar and select Website Studio (URL: /website-studio) to manage your site settings. ⚙️ How to Find and Copy Your Search Atlas Pixel 1. Log in to your Search Atlas account. 2. Navigate to the relevant project or campaign dashboard. 3. Locate the Tracking or Pixel settings section within your project. 4. Copy the full JavaScript snippet provided. 5. Paste it into the global header of your website platform (before the closing </head> tag) following the steps for your specific platform above. 6. Save and publish your changes. 7. Return to Search Atlas and use the pixel verification tool (if available) to confirm the pixel is firing correctly. 🚫 What If My Platform Doesn't Allow Custom Scripts? Some platforms — particularly highly managed or white-labelled automotive platforms — restrict custom JavaScript for security or compliance reasons. If your provider does not allow script injection, here are your options: - Ask your platform provider for a tag manager integration. Many restricted platforms still allow Google Tag Manager (GTM). If GTM is permitted, you can deploy the Search Atlas pixel as a custom HTML tag inside GTM without touching the site's code directly. - Request an exception from your provider. Some platforms can whitelist specific third-party domains. Provide them with the Search Atlas pixel domain and ask if they can permit it. - Use UTM parameters as an alternative. If pixel placement is not possible, you can still track campaign performance using UTM parameters on your ad URLs. This provides session-level data inside Search Atlas without requiring a pixel on your site. - Switch to Search Atlas Website Studio. If you have flexibility over your website infrastructure, building or migrating your site to Search Atlas Website Studio (left sidebar → Website Studio, URL: /website-studio) removes all compatibility concerns, as tracking is built in natively. ✅ Quick Compatibility Checklist - Does your platform allow custom JavaScript in the site header or footer? - Does your platform support Google Tag Manager? - Do you have admin-level access to your website's code or settings? - Has your platform provider confirmed they do not block third-party tracking domains? If you answered yes to any of the first three questions, the Search Atlas pixel can be deployed on your site. 💬 Need Help With Your Specific Platform? 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 Confirm SEO Changes Are Live on Shopify

This article explains the difference between a change being marked as deployed inside Search Atlas and that change actually appearing on your live Shopify storefront — and gives you a clear way to confirm which has happened. 📍 What 'Deployed' Means When Search Atlas marks a change as deployed, it means the platform has attempted to write that change to your Shopify store via the integration. However, there are a few reasons the updated value may not yet be visible on your live site or in Google Search results. 🛠️ Steps to Verify Your Changes 1. Check your OTTO SEO automation dashboard in Search Atlas and confirm that the specific change (e.g., title tag or meta description) shows a deployed status. 2. Go directly to the affected page or product in your Shopify Admin and open the record. Manually check whether the title, meta description, or other field now shows the new value you set in Search Atlas. 3. If the field in Shopify Admin does not yet reflect the change, it is possible there is a sync delay between Search Atlas and Shopify. Wait a short time and check again. 4. If the field in Shopify Admin does match the new value but the change is not yet visible in Google Search results, allow 1–14 days for Google to re-crawl and re-index the page. You can speed this up by submitting the URL for re-indexing through Google Search Console. ✅ How to Confirm It Worked You have two independent checkpoints to confirm a change is truly live: - Shopify Admin check: Navigate to the affected page or product in your Shopify Admin. If the title tag, meta description, or other field displays the new value you set in Search Atlas, the write was successful. - Live page source check: Visit the live Shopify URL in a browser, right-click, and choose View Page Source. Search for the <title> tag or meta name="description" entry. If the new value appears there, your change is live to visitors and search engines. If both checkpoints still show the old value, the deployment did not complete as expected. In that case, please reach out to support and have the following ready: your project name, the specific page or product affected, the change you attempted to deploy, and the approximate date and time you made the change. 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.

⚡ Signal Genesys External API Press Release Automation

Overview The Signal Genesys External API allows you to automate press release creation and publishing directly within Search Atlas. This article explains what to prepare, what to expect, and how to escalate effectively if you encounter issues. Because this is a backend-assisted integration, some steps — such as credential provisioning, entity linking, and endpoint configuration — require the support team to complete setup on your account before you can proceed. What to Prepare Before You Start Before contacting the support team to enable the Signal Genesys External API integration, gather the following information. Having this ready will allow the team to configure your account in a single interaction: - Your Search Atlas account email address — used to locate your account and assign API credentials. - The name of the project or integration you are building — helps the team provision the correct access scope. - The entity name you plan to associate with press releases — entities must exist and be linked to your account before API submissions will succeed. - Any error messages already encountered, including the exact error text and the timestamp of the failed request. Authentication Setup Signal Genesys API requests require authentication credentials tied to your Search Atlas account. These credentials are not self-provisioned — they are assigned by the support team based on your plan and integration requirements. To initiate this process: 1. Log in to your Search Atlas account and navigate to Avatar → Settings → API Keys to confirm whether an API key or token is already present. 2. If no credential is visible, open the chat widget and request API access. Provide your account email, project name, and intended use case so the team can assign the correct credential type. 3. Once credentials are issued, store them securely. The team will confirm the exact authentication header or parameter format required for your account configuration. Entity Management Every press release submitted via the API must be associated with a valid entity in your Search Atlas workspace. Entity linking is managed on the backend. If you receive a validation error related to an entity, this typically means one of the following: - The entity does not yet exist in your account and needs to be created by the support team. - The entity exists but is not linked to the correct workspace or project. - The entity name or identifier in your API request does not match the value stored on your account. When escalating an entity error, have ready: your account email, your organisation name, the exact error message returned by the API, and the timestamp of the failed request. The support team will identify which of the above applies and resolve it on the backend. Publishing a Press Release Once your credentials and entity are confirmed, press release submission via the External API follows this general flow: 1. Review the API documentation or developer resources available inside your Search Atlas account dashboard. These resources contain the endpoint path, required parameters, and accepted field values specific to your account configuration. 2. Construct your API request using the credentials issued to you. Include the entity identifier, press release content fields, and any distribution or variant parameters documented for your account. 3. Submit a test request before going live. Capture the full API response, including the status code, any error codes, and the response body. 4. If the test response indicates a configuration issue — such as an unrecognised entity, an invalid parameter, or an authentication failure — escalate to support with your account email, a description of the workflow you are automating, and the full error response including timestamps. Endpoint paths and required field names are account-specific and provided directly by the support team during onboarding. Do not share your API credentials in any support conversation. Credit Usage Credits may be deducted when a press release is submitted via the API. To avoid unexpected deductions: - Confirm with the support team how many credits a single API submission consumes on your plan before running bulk submissions. - Use test mode or a staging environment if one is available for your account, so that exploratory submissions do not consume production credits. - If you notice an unexpected credit deduction after a submission, note the press release ID or submission timestamp from the API response before escalating. When reporting a credit discrepancy, provide your account email, the press release ID or submission timestamp, and the credit balance before and after the deduction if visible in your dashboard. Status Tracking After a press release is submitted, its publishing status is returned in the API response and may also be visible in your Search Atlas dashboard. Common status values include submitted, processing, published, and failed. If a submission enters a failed or stuck state, escalate with the press release ID, the status value returned, and the timestamp of the original submission so the support team can investigate the backend workflow. 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 Use Third-Party Content Sources with Search Atlas

Search Atlas does not currently offer a native, one-click integration with third-party content curation tools like UpContent. This article explains how you can still bring external content into your Search Atlas workflow without waiting for a direct integration. 🔍 Common Causes Customers searching for an UpContent integration (or similar tools such as Curata, Feedly, or RSS-based sources) encounter this gap because Search Atlas manages content creation and optimization internally through Content Genius rather than pulling from external curation platforms via an API connection. 🛠️ Recommended Workaround Because there is no direct integration, the confirmed approach is to manually bring your external content into Search Atlas: 1. Export your content from the third-party tool. In UpContent (or your preferred curation platform), locate the article or content piece you want to use and copy the full text, or export it as a plain-text or HTML file. 2. Open Content Genius. Navigate to the Content Genius section within your Search Atlas platform. 3. Start a content session for existing content. Look for an option that allows you to work with or import content you already have, rather than generating new content from scratch. The exact label may vary depending on your account or platform version. 4. Paste your external content. Copy the text from your third-party source and paste it into the content editor field. 5. Set your target keyword and settings. Enter the primary keyword you want the content optimized for, configure any additional settings as available, then run the optimization to let Content Genius analyze and enhance the imported text. 6. Review and edit the output. Once processing completes, review the suggestions and recommendations. Accept, modify, or reject changes as needed before publishing. ✅ What to Expect When this approach works successfully, your pasted content should appear in the Content Genius editor and be processed against the target keyword you entered. If you encounter an option or step that does not match what is shown in your account, the interface may differ — contact support for guidance specific to your account setup. 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 Pixel on Webflow: Limitations and Cloudflare Workaround

🔍 Overview OTTO SEO makes on-page changes by injecting optimised content directly into your site. On platforms like WordPress and Shopify, OTTO connects at the source level — meaning edits land in the actual page content and persist reliably. On Webflow, this source-level integration is not currently available, which limits what OTTO can do out of the box. This article explains why that limitation exists, what OTTO can still accomplish on Webflow, and how a Cloudflare Worker can serve as a practical workaround to extend OTTO's reach. ⚙️ Why Webflow Has Client-Side Limitations OTTO's pixel operates client-side on Webflow, meaning it runs in the visitor's browser after the page has already loaded from Webflow's servers. This creates two key constraints: - No source-level writes: OTTO cannot push changes directly into Webflow's CMS or page structure the way it can on WordPress or Shopify. - Rendering dependency: Changes injected client-side may not be visible to all search engine crawlers, since some crawlers do not fully execute JavaScript before indexing. As a result, certain OTTO optimisations — such as rewriting heading tags, updating meta content at render time, or modifying body copy — have limited or no effect on Webflow sites when relying solely on the pixel. 🗺️ Is a Source-Level Webflow Integration on the Roadmap? A native source-level fix for Webflow — comparable to the WordPress or Shopify integrations — is not currently on the active roadmap. Webflow's closed hosting architecture does not expose the same server-side hooks that other CMS platforms provide, making a direct equivalent technically complex to deliver. We continue to evaluate platform integrations based on customer demand and technical feasibility. If this is important to your workflow, please share your feedback through the chat widget (details at the bottom of this article) so our team can log it as a feature request. 🚀 Cloudflare Worker: The Recommended Workaround If your Webflow site is proxied through Cloudflare, you can use a Cloudflare Worker to intercept and modify page HTML before it is delivered to the browser or crawler. This approach effectively moves OTTO's changes server-side, giving you similar behaviour to a native CMS integration. Here is how the solution works at a high level: 1. Your domain is proxied through Cloudflare — traffic passes through Cloudflare before reaching visitors. 2. A Cloudflare Worker is deployed on your zone — this is a lightweight script that runs at Cloudflare's edge network. 3. The Worker fetches OTTO's optimised output and injects it into the HTML response before the page is served, making the changes visible to crawlers and browsers alike. 4. Search engines receive fully rendered, optimised HTML — no JavaScript execution required on their end. ✅ What the Cloudflare Worker Approach Enables - Meta title and description updates that are crawler-visible - Heading tag modifications applied at the response level - Body copy changes that do not rely on JavaScript rendering - Behaviour closer to a source-level integration without requiring Webflow CMS access 📋 Prerequisites Before You Begin - Your Webflow site's domain must be proxied through Cloudflare (orange cloud enabled in your Cloudflare DNS settings). - You need access to a Cloudflare account with Workers enabled (available on the free plan and above). - Your OTTO pixel must already be installed on your Webflow site. To verify, go to Left sidebar → OTTO SEO → Installation Guide and confirm the pixel is active. 🛠️ Setting Up the Cloudflare Worker The exact Worker script will depend on how your OTTO configuration is structured. Follow these steps to get started: 1. Log in to your Cloudflare dashboard and select the zone (domain) connected to your Webflow site. 2. Navigate to Workers & Pages and create a new Worker. 3. Contact the Search Atlas support team (see below) to receive the Worker script template tailored to your OTTO site configuration. Our team will provide the script and your site-specific parameters. 4. Paste the script into the Worker editor and deploy it. 5. Add a Worker Route that maps the Worker to your domain (e.g., yourdomain.com/*). 6. Return to Left sidebar → OTTO SEO → Overview in Search Atlas and run a new Scan to verify that OTTO's changes are now being picked up correctly. ⚠️ Important Considerations - The Cloudflare Worker approach requires ongoing maintenance if your Cloudflare or Webflow configuration changes. - Worker execution adds a small amount of latency at the edge — this is typically negligible but worth monitoring via Cloudflare's analytics. - This workaround does not give OTTO write access to your Webflow CMS; it only modifies the HTML delivered to the end user and crawler at the network edge. 💬 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.

🛠️ How to Publish the Correct Article Version to WordPress

This article helps you resolve a situation where the original, unedited Content Genius article was published to your WordPress blog instead of the modified version you worked on inside Search Atlas. The steps below walk you through locating the correct version of your article and re-publishing it properly. 📍 Where to Find It Navigate to Left sidebar → Content → Content Genius. This is where all your generated and modified articles are stored before publishing. 🛠️ Step-by-Step 1. Go to Left sidebar → Content → Content Genius to open your article list. 2. Locate the article that was incorrectly published. Look for the article title you originally generated and subsequently modified. 3. Open the article and carefully confirm you are viewing the modified version — this is the one containing your edits, not the original AI-generated draft. Review the content on screen to verify your changes are present before proceeding. 4. Once you have confirmed the correct, modified version is open and displayed, use the Publish to WordPress option within the article editor to send this version to your WordPress blog. Do not re-open a previously saved draft from WordPress, as that may pull the original version again. 5. If you are unsure which version is active, compare the article text side-by-side with your WordPress blog post to identify discrepancies, then overwrite the WordPress post using the publish action from within Content Genius. ✅ How to Confirm It Worked After publishing, navigate to your WordPress blog and open the post that was previously showing the wrong version. Read through the content and confirm that your Search Atlas edits — such as structural changes, keyword additions, or rewritten sections — are now visible in the live post. If the post still shows the original unmodified text, return to Content Genius, verify the modified version is fully loaded and saved, and repeat the publish step. A successful publish will reflect all changes you made inside the Content Genius editor. 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.

🛠️ Pixel Removal, Investigations & Refund Requests

🔍 Overview If you are experiencing unexpected traffic drops and have an open investigation with our team, we understand how stressful this can be. This article explains how to remove the Search Atlas tracking pixel from your site, what to expect during an active investigation, and how to request a refund if your issue remains unresolved. 🛠️ How to Remove the Search Atlas Pixel You can remove the Search Atlas pixel from your website at any time. The steps depend on how it was originally installed. If you added the pixel manually to your site's code: 1. Log in to your website's CMS or hosting file manager. 2. Open the file where the pixel snippet was placed — typically the site-wide header or footer template (e.g., header.php, a theme file, or a tag manager container). 3. Locate the Search Atlas pixel script. It will be a short <script> tag referencing Search Atlas or a tracking domain provided during setup. 4. Delete the entire script snippet. 5. Save the file and clear your site's cache. 6. Verify removal by viewing your page source (Ctrl+U or Cmd+U) and confirming the script is no longer present. If you installed the pixel via Google Tag Manager (GTM): 1. Log in to your GTM account and open the relevant container. 2. Navigate to Tags and locate the Search Atlas pixel tag. 3. Click the tag, select Delete, and confirm. 4. Click Submit to publish the updated container. If you used a WordPress plugin or third-party integration: 1. Go to your WordPress dashboard and open Plugins. 2. Deactivate and delete any plugin that was used to inject the Search Atlas pixel. 3. Clear your site cache after removal. 📊 Understanding the Investigation Process When a traffic issue is reported, our team opens a formal investigation to identify the root cause. Here is what typically happens during this process: - Initial review (24–48 hours): Our team examines your account data, pixel activity, and any reported anomalies. - In-depth analysis: Complex cases — particularly those involving significant traffic drops or potential data conflicts — require deeper review across multiple data sources, and timing varies by case complexity. - Resolution and update: Once findings are confirmed, our team contacts you with a summary and any corrective actions taken. If your investigation has been open for more than 5 business days without a meaningful update, you are entitled to escalate the case and request a resolution timeline or a refund consideration. 💡 What to Do If Your Investigation Is Taking Too Long If your case has been open for over a week and you are continuing to experience traffic loss, take the following steps: 1. Remove the pixel immediately using the steps above to eliminate any potential ongoing impact to your site. 2. Document your traffic data — take screenshots from Google Analytics, Google Search Console, or any other analytics platform showing the drop and its timeline. 3. Contact our support team through the live chat widget and reference your investigation case or ticket number so the team can prioritise your escalation. 💰 How to Request a Subscription Refund Search Atlas reviews refund requests on a case-by-case basis. You may be eligible for a full or partial refund if: - Your issue was directly caused by a Search Atlas product or pixel and remained unresolved for an extended period. - You experienced measurable harm (such as verified traffic loss) during an active investigation. - You request the refund within a reasonable timeframe after identifying the issue. To submit a refund request: 1. Open the live chat widget inside the Search Atlas platform. 2. Type human teammate to connect with a support agent. 3. Provide your account email, a brief description of the issue, your investigation case reference (if available), and any supporting evidence such as traffic screenshots. 4. Our team will review your request and respond with a decision as soon as possible; response time varies by case complexity. Note: Refunds are not automatically issued when an investigation is opened. You must submit a formal request via chat for our team to begin the review process. 🚀 Preventing Future Issues To minimise the risk of tracking conflicts or unexpected traffic changes going forward: - Only install the Search Atlas pixel on pages where tracking is required. - Avoid running multiple conflicting tracking scripts from different SEO platforms simultaneously. - Regularly audit your tag manager containers and remove any unused or outdated scripts. - Monitor your site's performance weekly in Google Search Console to catch drops early. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📝 Publish Articles With CMS Options

🧭 Choose a publishing option Search Atlas supports several ways to move your articles from creation to publication. Choose the option that matches your workflow: - WordPress: Publish articles directly to a connected WordPress site. - CMS Connector: Connect your supported CMS and send article content to your publishing workflow. - Content Genius Studio: Create, edit, and prepare articles, then export the finished content for publishing in your CMS. ✍️ Create an article in Content Genius 1. Open Content in the left sidebar. 2. Select Content Genius. 3. Choose Write an article, Generate, or Write it yourself. 4. Review and edit the article before publishing or exporting it. 🚀 Publish to WordPress or a connected CMS If your WordPress site or CMS Connector is connected, use the publishing option available in your article workflow. Confirm the destination, review the content, and publish or send it to your CMS according to the displayed prompts. Connection availability can depend on your account setup and the CMS integration you use. If a direct publishing option is not shown, export the article and upload it through your CMS. 📤 Export and publish manually When direct publishing is unavailable, copy or export the completed article from Content Genius Studio. Then open your CMS, create a new article, paste the content, add any required images or metadata, and publish it there. Before publishing, check the title, headings, links, formatting, featured image, author, category, and URL slug in your CMS. 🔄 Start a new topic when needed If a conversation changes from API or app-token questions to CMS publishing, restate the new goal clearly: “I want to publish an article. What CMS options are available?” A new conversation can also help reset the context. The relevant answer should focus on WordPress, CMS Connector, and Content Genius Studio—not the previous API topic. 💬 Get help in the platform 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.

🛠️ Shopify Admin API Scopes for OTTO via Pipedream

🔍 Overview When you connect Shopify to OTTO through Pipedream, you create a Shopify app that gives OTTO permission to read and update parts of your store. These permissions are called Admin API scopes. If a scope is missing, OTTO cannot apply some SEO changes. If you grant too many, you give access you may not need. This article lists the scopes we recommend for full SEO functionality and explains how to enable them. 📋 Recommended Scopes for Full SEO Functionality For product metadata, page content, and structured data, enable the following scopes. You can paste this comma-separated list into any field that accepts one: read_products,write_products,read_product_listings,read_content,write_content,read_online_store_pages,write_online_store_pages,read_themes,write_themes,read_files,write_files,read_metaobjects,write_metaobjects,read_online_store_navigation,write_online_store_navigation,read_locales,read_translations,write_translations Please note that Shopify occasionally renames or adds scopes, so the list inside your OTTO setup screen is always the most current. If the two differ, follow the setup screen. 🧩 What Each Scope Group Does - Products (read_products, write_products, read_product_listings): lets OTTO read and update product titles, descriptions, SEO titles, meta descriptions, image alt text, and product metafields. - Content and pages (read_content, write_content, read_online_store_pages, write_online_store_pages): lets OTTO update page content, blog posts, and the SEO fields on them. - Themes (read_themes, write_themes): lets OTTO add structured data (schema markup) and other on-page elements to your theme files. - Files (read_files, write_files): lets OTTO work with images and other files, such as updating image details. - Metaobjects (read_metaobjects, write_metaobjects): lets OTTO read and write custom content structures that some themes use for SEO data. - Navigation (read_online_store_navigation, write_online_store_navigation): lets OTTO manage URL redirects and menu links, which helps fix broken pages. - Languages (read_locales, read_translations, write_translations): lets OTTO handle SEO content on multilingual stores. Skip these if your store uses a single language. ⚙️ How to Enable the Scopes 1. In your Shopify admin, open Settings, then Apps and sales channels. 2. Open the area for developing or building apps and create a new app. Shopify has been moving app creation to its Dev Dashboard, so the menu names may differ slightly for your store. 3. Open the app's Admin API configuration. 4. Select each scope from the list above. You can use the search box to find them quickly. 5. Save the configuration and install the app on your store. 6. Copy the Admin API access token. Shopify usually shows it only once, so store it somewhere safe. 7. In Pipedream, connect your Shopify account using your store name and the access token, then finish the connection in OTTO. 🔄 Changing Scopes After Setup If you need to add or remove a scope later, update the scopes in your Shopify app and reinstall or re-approve the app so the change takes effect. Then reconnect or refresh the Shopify account in Pipedream. Shopify does not apply new scopes to an existing access token until the update is approved. 🛡️ Security Tips - Never share your access token in public places or screenshots. - If you think a token has been exposed, rotate it in Shopify and update it in Pipedream. - If you do not need a feature, such as translations, leave those scopes off. 🧯 Troubleshooting - OTTO cannot update product SEO fields: check that write_products is enabled and the app has been reinstalled after any scope change. - Structured data is not appearing: confirm read_themes and write_themes are enabled. - Page or blog changes are not applied: confirm write_content and write_online_store_pages are enabled. - Redirects are not being created: confirm write_online_store_navigation is enabled. - Connection fails in Pipedream: check that the store name is correct and that you copied the full access token without extra spaces. 💬 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 instantly connected with a member of our team.

🚀 Publish Website Studio Pages to WordPress via MetaSync

🗺️ Overview If Atlas Brain recommends that your new service pages live inside your domain (for example, yourdomain.com/services/page-name), you can publish them directly into your existing WordPress site using the MetaSync folder option in Website Studio. This method adds pages under a subfolder of your domain without replacing your homepage, removing your existing content, or moving your site to a subdomain. 📋 Before You Start Make sure the following are in place before publishing: - You have an active Website Studio project with at least one completed page. - Your WordPress site is connected to Search Atlas via MetaSync (the Search Atlas WordPress plugin must be installed and authenticated). - You have WordPress admin credentials available in case re-authentication is needed. - You have decided on the subfolder path where the pages will live (for example, /services/ or /locations/). 🛠️ How to Publish Pages Using the MetaSync Folder Option 1. Open Website Studio from the left-hand navigation inside Search Atlas. 2. Select the project that contains the page or pages you want to publish. 3. Click the Publish button in the top-right corner of the editor. 4. In the publishing modal, select MetaSync — WordPress (Folder) as your publish destination. This option publishes pages as posts or custom pages nested under a subfolder on your existing domain. 5. Choose the connected WordPress site from the dropdown. If your site does not appear, verify that the MetaSync plugin is installed and that the connection is active under Settings → Integrations. 6. Enter the subfolder path where the page should be published (for example, /services/roof-repair/). This determines the URL the page will live at on your domain. 7. Review the page title and URL slug, then click Publish to WordPress. 8. Once publishing is confirmed, visit the URL in a browser to verify the page is live and your existing homepage and other WordPress content are unaffected. ✅ What the MetaSync Folder Option Does (and Does Not Do) It is important to understand exactly how this publish method works so you can set the right expectations: - It adds pages inside your existing WordPress site under the subfolder path you specify — your homepage and existing pages remain untouched. - It does not replace your WordPress theme or layout for existing pages. Only the newly published Studio page uses the Website Studio design. - It does not require a subdomain. Pages are published directly under your root domain (for example, yourdomain.com/services/new-page). - It does not affect your WordPress navigation menus automatically. If you want the new page to appear in your menu, add it manually inside WordPress under Appearance → Menus. ⚠️ Common Issues and How to Fix Them - Published page redirects to the homepage: This is a known WordPress permalink conflict. Go to your WordPress dashboard, navigate to Settings → Permalinks, and click Save Changes (no changes needed — just saving flushes the rewrite rules). Then revisit the published URL. - WordPress site not appearing in the publish dropdown: The MetaSync plugin may have lost its authentication token. Go to Settings → Integrations → MetaSync in Search Atlas and reconnect your site. - Page published but not indexed: Check that the page is not set to noindex inside Website Studio's page settings, and that your WordPress site is not set to discourage search engines under Settings → Reading. - Subfolder path already in use by another WordPress page: Choose a unique slug that does not conflict with existing WordPress pages or posts. Duplicate slugs can cause one page to override the other. 💡 Tips for Best Results - Plan your subfolder structure before publishing multiple pages. A consistent structure (for example, /services/[city]/[service-name]) makes future management and internal linking easier. - After publishing, add an internal link from your WordPress homepage or relevant existing pages to the new Studio page to pass authority and improve crawlability. - Use the Preview option in Website Studio to review the final design before publishing to your live site. 💬 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.

🔄 Migrate OTTO Pixel from WordPress to Showit

🧭 Overview If you are moving your website from WordPress to Showit, you will need to remove the OTTO plugin from your WordPress site and add the OTTO tracking pixel directly to your Showit project. This article walks you through each step, including how to find or regenerate your OTTO script if you no longer have it. 🗑️ Step 1: Remove the OTTO Plugin from WordPress Before installing OTTO on Showit, remove it cleanly from your WordPress site to avoid duplicate tracking or conflicts. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the OTTO AI plugin in the list. 4. Click Deactivate, then click Delete to fully remove it. 5. Confirm the deletion when prompted. Once the plugin is removed, OTTO will stop tracking activity on your WordPress site. Your OTTO configuration and settings inside Search Atlas are not affected. 🔑 Step 2: Retrieve Your OTTO Tracking Script To install OTTO on Showit, you need your unique OTTO pixel script. You can find this inside the Search Atlas platform at any time. 1. Log in to Search Atlas. 2. In the left sidebar, navigate to OTTO SEO → Installation Guide. 3. Select the website project that you are migrating. 4. Look for the pixel script displayed on the OTTO SEO → Installation Guide page. 5. Copy the full pixel script displayed there. It will look similar to a short JavaScript snippet. If you cannot locate the script or the option is not visible, follow the regeneration steps below. 🔁 Step 3: Regenerate Your OTTO Script (If Needed) If your script is missing, was lost during the migration, or is not displayed in the dashboard, you can generate a fresh one. 1. Inside OTTO SEO, open your website project settings. 2. Look for a Reconnect, Reset Connection, or Generate Script option. 3. Follow the on-screen prompts to generate a new pixel script for your domain. 4. Make sure the domain entered matches your Showit website URL exactly, including whether it uses www or not. 5. Copy the newly generated script before closing the panel. If you do not see any of these options, contact support using the instructions at the bottom of this article and a teammate will generate the script for you directly. 🎨 Step 4: Install the OTTO Pixel on Showit Showit does not use plugins. Instead, you add tracking scripts through the Showit site settings. Follow these steps carefully. 1. Log in to your Showit account at showit.co. 2. Open your site in the Showit app. 3. Click the Site Settings icon (gear icon) in the top toolbar. 4. Select the Header Code tab. 5. Paste your OTTO pixel script into the Header Code field. This ensures the script loads on every page of your site. 6. Click Save. 7. Publish your site by clicking the Publish button so the changes go live. The OTTO pixel will now be active on your Showit website and will begin collecting data automatically. ✅ Step 5: Verify the Pixel Is Working After publishing your Showit site, confirm that OTTO is tracking correctly. - Return to Search Atlas → OTTO SEO and open your project. - Check the connection status indicator next to your site. It should show as Connected or Active within a few minutes. - Visit your live Showit website in a browser and then refresh the Search Atlas dashboard to confirm activity is being recorded. - If the status remains disconnected after 10–15 minutes, double-check that the script was pasted into the Header Code field and that your site was republished on Showit. ⚠️ Common Issues and Tips - Wrong domain: If your OTTO script was originally generated for a WordPress domain (for example, mysite.wordpress.com) and your Showit site uses a different URL, you must regenerate the script with your correct Showit domain. - Script not in header: Placing the script in the footer instead of the header can delay tracking. Always use the Header Code field in Showit. - Site not published: Changes in Showit only go live after you click Publish. Saving alone is not enough. - Caching: If you use a CDN or caching layer in front of your Showit site, clear the cache after publishing so the new script loads for all visitors. 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 OTTO Pixel on GoHighLevel AI Studio

📌 Before you begin OTTO pixel installation on GoHighLevel AI Studio may not be automatic. GoHighLevel’s platform detection can miss a pixel added through its embed layer, so you may need to add the pixel manually and allow time for OTTO to detect it. Make sure you can edit the correct GoHighLevel site or sub-account and access the OTTO pixel code in Search Atlas. 🔧 Add the pixel to GoHighLevel AI Studio 1. In Search Atlas, open the project that matches your GoHighLevel site and locate its OTTO pixel code or installation instructions. 2. In GoHighLevel, open the AI Studio site you want to connect and find the site’s embed or custom code settings. 3. Add the OTTO pixel code using GoHighLevel’s embed layer. Follow GoHighLevel’s instructions for where to place site-wide code, if available. 4. Save your changes and publish or update the site so the pixel is present on the live pages. 🔍 Check whether OTTO detects the pixel Return to Search Atlas and check the project’s pixel or installation status. Detection may not happen immediately, so allow some time for OTTO to scan the live site, then check again. If the pixel is still not detected, confirm that the code was saved in the correct site or sub-account, that the site was published, and that the pixel appears on a live page. A successful installation may still be missed by the scanner when the code is added through GoHighLevel’s embed layer. 👥 Bring in a teammate You can involve a teammate who has access to the GoHighLevel site to help add or check the embed code. Coordinate with them to confirm which site or sub-account is being updated, and ask them to publish the change before you check detection in Search Atlas. 💬 Get help with detection If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🌐 Media Room Domain Migration: Update Your Embed Codes and URLs

🌐 What Changed Signal Genesys Media Room and embed integration URLs moved to new domains. If your Media Room or embed integration was set up before this change, links and embedded content pointing to the old domains will stop working until you update them. 🔗 The URL Changes - Hosted Media Room pages: URLs that used to look like yourbrand.mediaroom.app now use yourbrand.media-room.app (for example, https://yourbrand.media-room.app/). - Embed integrations: embed codes that referenced brandassets.app now need to reference embedassets.app instead. ✅ How to Fix a Media Room That Stopped Displaying Press Releases If press releases aren't showing up on your Media Room page even though everything looks correctly configured (media room enabled, PRs toggled to show, reports present), this domain change is the most common cause. To fix it: - Update any links or references on your website that point to the old mediaroom.app address to the new media-room.app address. - If you have an embed integration (an iframe or embedded widget rather than a hosted page), grab a fresh copy of the embed code from your Integration Channel and replace the old snippet on your site — the old brandassets.app reference in an outdated snippet won't resolve correctly anymore. This applies whether you have one Media Room or several across multiple client sites — each one with an outdated link or embed code needs to be updated individually. 🧭 A Note on Signal Genesys vs. Search Atlas Media Rooms are a Signal Genesys feature, surfaced through your Search Atlas dashboard. This domain change is specific to Signal Genesys's own hosting infrastructure, separate from Search Atlas's own Authority Building or Digital PR features. 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.

⚙️ Managing SearchAtlas Changes in GHL

🔍 Understand how GHL and SearchAtlas work together GoHighLevel (GHL) is the client delivery platform, while SearchAtlas provides SEO analysis, recommendations, reporting, and optimization tools. Changes made in SearchAtlas do not automatically change every setting in GHL. Likewise, changes to a client's website, domain, or GHL account may require you to review the related SearchAtlas project. 📝 Before making changes 1. Confirm the client, website, and GHL sub-account you are working on. 2. Record the requested change and its expected outcome. 3. Confirm that you have the required access to both SearchAtlas and the client's GHL account. 4. Check whether the change affects tracking, website content, local listings, keywords, or reporting. 🌐 Handle website or domain changes When a client changes their domain, website, or page structure in GHL, open the corresponding project in SearchAtlas and take the following steps: 1. Go to Projects in the left navigation and select the client's project. 2. Check the Project Settings to confirm the tracked URL matches the client's current live domain. If the domain has changed, update the tracked URL to the new domain so that all subsequent data is collected against the correct site. 3. After updating the URL, open the Site Auditor and run a new crawl. Review the crawl results for broken links, redirect chains, or missing pages that may have resulted from the migration. 4. Open the Rank Tracker and confirm that the keyword list still targets pages on the new domain. Update any page-level targets that now point to old URLs. 5. If the client moved to a new domain and you need to preserve the historical data separately, create a new project for the new domain rather than overwriting the existing one. Keep the original project in read-only reference mode so historical comparisons remain available. 📊 Review SEO data after updates After a significant website or GHL change, review the following areas in SearchAtlas before confirming the work is complete: - Rank Tracker: Check whether tracked keywords show ranking changes consistent with the site update. Look for any keywords that dropped to "not ranking" — this may indicate a page was removed or a URL changed without a proper redirect. - Site Auditor: Confirm the crawl error count has not increased. Pay particular attention to 404 errors and redirect issues introduced by the change. - Organic Keywords report: Review whether indexed pages and estimated traffic have shifted in the direction expected from the change. - Reporting dashboard: Update any client-facing reports to reflect the change date so that data before and after the update can be distinguished clearly. 📍 Review local SEO information For clients using GHL with local SEO services, review their local SEO settings separately from website settings: 1. Open the client's GBP (Google Business Profile) project in SearchAtlas and confirm the business name, address, phone number, and website URL are still accurate following any GHL account changes. 2. Check the Local Citations section for any listings that reference the old domain or outdated contact details, and flag them for correction. 3. Review any pending review-response tasks or local recommendation items and confirm they are still relevant after the change. ✅ Confirm and communicate changes 1. Verify that the requested change is reflected in the appropriate SearchAtlas project settings, crawl data, and rank tracking targets. 2. Note the date the website or domain changed in any client-facing report so historical data is interpreted correctly. 3. Tell the client what was reviewed, what was updated, and whether any follow-up crawl or ranking check is scheduled. 4. If you encounter an error updating a project URL, cannot run a new crawl, or are unsure which project corresponds to the correct GHL sub-account, contact support with the client name, website URL, GHL sub-account name, the specific change requested, and the exact error message or screen where you are stuck. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🗂️ OTTO Category Dropdown: Supported Post Types Explained

🔍 Overview OTTO's category dropdown for auto-sync currently supports three WordPress post types out of the box: Blog, Procedures, and Locations. If your WordPress site uses custom post types — such as articles, resources, events, or any other non-standard type — these will not appear in the dropdown by default. This is a platform limitation, not a configuration error on your end. 📋 Supported Post Types in OTTO Auto-Sync The following post types are natively recognised by OTTO's category dropdown: - Blog — Standard WordPress blog posts - Procedures — Typically used by medical or service-based sites - Locations — Used for multi-location business pages Any WordPress post type outside this list — including custom post types registered by themes, plugins, or custom code — is not currently supported natively in the dropdown. ❓ Why Custom Post Types Don't Appear OTTO's auto-sync category selector maps to a predefined set of post type identifiers. When WordPress registers a custom post type (for example, articles), OTTO does not automatically detect or list it because the dropdown is not dynamically populated from your WordPress post type registry. This means refreshing categories, clearing cache, or reconnecting your CMS integration will not resolve the missing post type — those steps only apply to standard supported types. ⚙️ How to Work Around Custom Post Type Limitations If your content lives in a custom post type, you have two practical options to bring it into OTTO's auto-sync workflow: 1. Remap your content to a supported post type. In WordPress, you can reassign existing custom post type content to the standard post type (which maps to Blog in OTTO). This may require a plugin such as Post Type Switcher or a small code change. Once content is under a supported post type, it will be available in OTTO's dropdown immediately. 2. Request custom post type mapping. Search Atlas can enable custom post type support for your account on a case-by-case basis. To request this, 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. Provide the exact slug of your custom post type (for example, articles) and a member of our team will confirm whether mapping is available for your plan. 🛠️ Steps to Verify Your Current CMS Post Type Slug Before reaching out, confirm the exact slug OTTO would need to map. Follow these steps in WordPress: 1. Log in to your WordPress admin dashboard. 2. Navigate to Settings → Permalinks and save (this flushes rewrite rules and confirms post type slugs are active). 3. Go to any post in your custom post type and check the URL structure — the segment after your domain root is typically the post type slug (for example, yoursite.com/articles/post-name indicates the slug is articles). 4. Alternatively, if you have access to your theme's functions.php or a custom plugin file, search for register_post_type — the first argument is the slug. Note this slug exactly as it is case-sensitive. 🔗 Where to Find OTTO Auto-Sync Settings To access the category dropdown and auto-sync options in OTTO: 1. In the left sidebar, click OTTO SEO. 2. Click All Sites (SEO Automation). 3. Open your individual project. 4. Navigate to the Auto-Sync or Category settings panel within the OTTO dashboard. 5. The dropdown will display only the three supported post types listed above. If your custom post type has been successfully mapped by the Search Atlas team, it will appear in this list after the mapping is applied to your account. ✅ Quick Reference - Blog, Procedures, Locations — supported natively, no action needed. - Custom post types (e.g. articles) — not supported by default; use remapping or request account-level mapping. - Refreshing categories or clearing cache — will not add custom post types to the dropdown. - CMS reconnection — will not add custom post types to the dropdown. 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.

🧾 API Press Release Billing and Distribution Explained

📋 Overview When you submit a press release through the Search Atlas API, charges and distribution follow a specific sequence. This article outlines what to expect and what information to have ready if you need support. 💳 Questions About Charges If you are unsure whether your press release has been charged, or when a charge is applied during the submission process, our support team can look up the status of your order directly. To help us investigate quickly, please have the following ready: - Your press release ID or order reference - The API request details (endpoint used, timestamp of submission) - Any confirmation or error messages returned by the API 🔄 Questions About Refunds If you believe a refund should have been issued for a failed or incomplete press release distribution, our team will need to review the order on our end. Please be prepared to share: - The press release ID - The date and time of the original submission - Any error messages or failure notices you received ⚠️ Questions About Source Page Errors If your press release returned a source page error during syndication, our support team can help identify the cause. When reaching out, include: - The exact error message returned - The URL or domain included in your API request - The timestamp of the failed submission 📞 Need Help? Because the specifics of API press release billing, refunds, and distribution errors depend on your individual order details, a member of our team will need to review your case directly. Please gather the relevant information listed above before reaching out so we can assist you as efficiently as 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.

🔒 WordPress Plugin Read-Only Mode Explained

🔍 What Is Read-Only Mode? The Search Atlas WordPress plugin can be placed into read-only mode by the account owner or agency managing your Search Atlas workspace. In this state, certain settings, SEO fields, and plugin configurations are visible but cannot be edited directly inside WordPress. This is a deliberate access control feature, not a bug or technical error. 💡 Why Does Read-Only Mode Exist? Read-only mode exists to protect SEO configurations set by an agency, consultant, or team administrator. Common reasons your plugin may be locked include: - Your account is managed by an agency that has restricted editing to prevent accidental changes. - An administrator has enabled privileged access controls to ensure only authorised users can modify SEO output settings. - Specific features or SEO fields have been individually disabled by your account owner using per-feature access switches. This protects the integrity of your SEO strategy and prevents conflicting changes from multiple users. ⚙️ What Is Affected by Read-Only Mode? When read-only mode is active, you may notice the following limitations inside your WordPress plugin: - Search Atlas settings panels appear greyed out or unclickable. - Meta titles, meta descriptions, and other SEO fields cannot be edited from the WordPress dashboard. - Some plugin features or toggles are hidden or disabled entirely. - Changes attempted within the plugin do not save or are reverted. Your site continues to benefit from all active SEO configurations — you simply cannot modify them from within WordPress while the restriction is in place. 🛠️ How to Regain Editing Access If you need to edit Search Atlas settings inside WordPress, follow these steps: 1. Identify who manages your Search Atlas account. If you are working with an agency or a team administrator, they control access permissions for the plugin. 2. Contact your account owner or agency. Request that they adjust your access level or temporarily disable read-only mode for your user role. 3. Ask them to review per-feature switches. Individual features can be re-enabled selectively, so your administrator may be able to unlock only the specific fields you need without removing all restrictions. 4. Make edits directly in the Search Atlas platform. Many SEO settings can be managed from your Search Atlas dashboard at app.searchatlas.com, which may not be subject to the same restrictions as the WordPress plugin interface. 👤 Information for Account Owners and Administrators If you are the account owner and have locked yourself out of editing, or if you need to adjust access permissions for your team or clients, you can manage these settings from within the Search Atlas platform. Look for plugin access controls and MetaSync permission settings in your workspace configuration. You can enable or disable editing access per user and control which SEO fields the plugin outputs on a per-feature basis. 📊 Frequently Asked Questions Is my SEO data still active while the plugin is in read-only mode? Yes. Read-only mode only prevents editing. All published SEO configurations, meta data, and plugin outputs continue to function normally on your site. Can I tell if read-only mode was intentionally enabled? If your plugin settings are greyed out and you did not make this change yourself, it was most likely enabled by your account owner or agency. Reach out to them directly to confirm. Will upgrading my Search Atlas plan remove the restriction? No. Read-only mode is an access control decision made by your account administrator, not a plan-level limitation. Only your administrator can change it. 🆘 Still Need Help? If you are unsure who manages your account, cannot reach your administrator, or are experiencing an unexpected lock-out, our support team is here to 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.

🔍 Site Explorer Exports and API Access Explained

Overview This article addresses common questions about export options in Site Explorer and how to get API access. Site Explorer Export Formats Site Explorer supports CSV and XLS export for most of its core reports, including backlink data, organic keywords, and traffic overviews. To export a report: 1. Navigate to Site Explorer inside your Search Atlas account. 2. Open the specific report you want to export (for example, Backlinks or Organic Keywords). 3. Look for an export or download option within the report view. 4. Click it to download the data as a CSV or XLS file to your device. If you do not see an export option in a particular report, CSV or XLS export may not be available for that specific view, or your current plan may not include export access for that report. In that case, upgrading your plan may unlock additional export options. API Access by Plan Tier API access is available on every plan, including Starter — no upgrade is needed. To get your API key: 1. Go to Settings → API Keys. 2. Click Generate new key. You can also regenerate or revoke existing keys from the same API Keys tab. Getting Accurate Plan and Feature Details Because plan features and export capabilities can be updated as Search Atlas evolves, the most reliable way to confirm what is currently available to you is to: - Review your current plan details inside the platform under the top-right avatar → Billing (Plans & Top-ups). - Check in-platform announcements or the product changelog for the latest feature updates. 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.

🔄 Push Website Studio Updates to WordPress with MetaSync

❓ Can I Push Website Studio Updates Live to WordPress? Yes. When the MetaSync plugin is installed and connected to your Search Atlas account, you can make updates in Website Studio and send them to your WordPress site, so you don't have to copy and paste changes into WordPress by hand. This article explains how the connection works, how to push your updates, and what to check if changes don't appear on your live site. 🔌 What the MetaSync Plugin Does MetaSync is the Search Atlas plugin for WordPress. It creates a secure link between your WordPress site and your Search Atlas project. Once linked, Search Atlas can send approved updates to your site. - Connects your accounts: links your WordPress site to the correct Search Atlas project. - Receives updates: accepts changes you approve or publish from Search Atlas. - Keeps your site in sync: helps the content in Search Atlas match what is live on your website. ✅ Before You Start Check the following to avoid most common issues: - You have administrator access to your WordPress site. - Your site is already added as a project in Search Atlas. - The MetaSync plugin is installed, activated, and updated to the latest version. - Your site is publicly reachable and not in maintenance mode or behind a password. 🛠️ How to Connect MetaSync to Your Site 1. Log in to your WordPress dashboard. 2. Go to Plugins and install the Search Atlas MetaSync plugin, or upload it if you received a file from Search Atlas. 3. Click Activate. 4. Open the plugin settings and follow the prompts to connect it to your Search Atlas account. 5. Return to Search Atlas and confirm that your project shows as connected. Menu names can vary slightly depending on your plugin version and WordPress theme. 🚀 How to Push Website Studio Updates to WordPress 1. Open your project in Search Atlas and go to Website Studio. 2. Make your edits, such as updating text, headings, or page details. 3. Review your changes carefully. Once pushed, they will be visible to visitors. 4. Select the option to publish or push your changes to your connected WordPress site. 5. Wait a moment for the update to finish, then open the page on your live site to confirm it. Tip: Make a backup of your WordPress site before pushing large changes. Most hosting providers offer one-click backups. 🔍 Changes Not Showing Up? Try These Fixes - Clear your cache: caching plugins, your host's cache, or a CDN may show an older version. Clear all caches and reload the page in a private browser window. - Check the connection: make sure the plugin is still active in WordPress and your project shows as connected in Search Atlas. Reconnect if needed. - Update the plugin: older versions may not sync properly. Update MetaSync to the latest version. - Review security settings: firewalls or security plugins can block incoming updates. Check whether they are blocking the connection and allow it if so. - Check page type and ownership: if a page is built with a custom page builder or a locked template, some changes may not apply as expected. - Confirm the right site: make sure you are pushing to the correct project, especially if you manage several websites. 💡 Best Practices - Push a small update first to confirm everything works before making bigger changes. - Avoid editing the same page in WordPress and Website Studio at the same time, since one set of changes could overwrite the other. - Keep WordPress, your theme, and your plugins up to date. - Always check the live page after pushing. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🌐 Change Your Otto Connected Domain Without Deletion

🔍 Overview Otto projects are tied to a connected domain at the time of setup. If you need to change that domain — for example, switching from islandcardio.com to island-cardio.com — you cannot modify the domain in-place. Otto does not currently support editing a connected domain after a project has been created. However, you can replace the domain quickly using the steps below, and your core project settings are straightforward to restore. ⚠️ Before You Begin - Changing a connected domain requires disconnecting the existing domain and reconnecting the correct one. - Any deployed Otto automations (meta tags, schema, redirects, etc.) tied to the old domain will no longer be managed by Otto once that domain is removed. - If the old domain is still live and indexed, review your SEO settings before disconnecting to avoid unintended changes to your site. - You will need access to your website's backend or CMS to re-verify the new domain. 🔄 How to Change Your Connected Domain 1. Go to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Open the Otto project that has the incorrect domain connected. 3. Locate the connected domain at the top of the project dashboard and click Disconnect Domain (or the equivalent remove/unlink option shown in your interface). 4. Confirm the disconnection when prompted. The project will enter an unconnected state — your project history and configuration remain saved. 5. Click Connect Domain (or Add Domain) and enter the correct domain — for example, island-cardio.com. 6. Follow the on-screen verification steps to confirm ownership of the new domain. This typically involves adding a DNS record or a verification tag to your site. 7. Once verified, the new domain will be active and Otto will begin analysing it. 8. Review your automation settings and re-deploy any fixes or optimisations that were previously applied to the old domain. 📋 What Is Retained vs. What Resets - Retained: Your Otto project name, connected GSC and GA4 accounts (if re-linked), and your subscription seat. - Resets: Previously deployed on-site changes are no longer tracked under the new domain. Otto will run a fresh audit against the new domain and surface a new set of recommendations. - Action required: If you had approved and deployed automations on the old domain, you will need to review and re-deploy the relevant fixes under the new domain's audit results. 🛡️ Handling Compromised or Overtaken Domains If you are changing domains because your original domain has been compromised, hacked, or taken over by a third party, take these additional steps: - Disconnect the compromised domain from Otto immediately to prevent Otto from deploying any further changes to a site you no longer control. - Do not reconnect the compromised domain even temporarily — connect your new or restored domain directly. - Revoke any API access or site verification tokens associated with the old domain through your DNS provider and Google Search Console. - After connecting the new domain, run a full Otto audit to establish a clean baseline for the replacement domain. 💡 Tips for a Smooth Domain Switch - If both domains (old and new) are live simultaneously during a migration, connect the destination domain and let Otto audit it before the old domain is retired. - Keep a record of the automations that were active on the old domain so you can prioritise re-deploying them on the new one. - After switching, allow 24–48 hours for Otto to complete its initial crawl and populate recommendations for the new domain. 🆘 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.

🌐 Add a Subdomain as a Separate Search Atlas Project

🧭 Overview If your main domain (for example, yoursite.com) is already set up in Search Atlas with OTTO activated, and your WordPress blog lives on a subdomain (for example, blog.yoursite.com), you can add that subdomain as a completely separate project. This lets you track performance, run SEO workflows, and optionally activate OTTO independently for the subdomain — without affecting your main domain's configuration. ✅ Before You Begin - Confirm the subdomain is live and publicly accessible. - Know the full subdomain URL you want to add (for example, blog.yoursite.com). - Have admin access to your Search Atlas account. - Note that each project uses a slot from your plan's domain allowance. Check your current plan if you are unsure how many domains you have available. ➕ Step 1: Create a New Project for Your Subdomain 1. Log in to your Search Atlas account. 2. Locate the project or domain management area within the platform (typically accessible from the main navigation or dashboard). 3. Look for an option to add or create a new project. 4. In the domain field, enter your full subdomain URL — for example, blog.yoursite.com. Do not enter the main domain here. 5. Complete any additional setup fields such as project name, target country, and preferred search engine. 6. Confirm the new project to save your settings. Your subdomain now exists as its own independent project. Any data tracked, keywords added, or OTTO actions taken on this project will be separate from your main domain project. 🤖 Step 2: Activate OTTO on Your Subdomain (Optional) If you want OTTO to manage on-page SEO for your WordPress subdomain, you can activate it independently for that project. OTTO on the subdomain will not interfere with OTTO already running on your main domain. 1. Switch to your new subdomain project using the project selector at the top of the platform. 2. Navigate to the OTTO section from your dashboard. 3. Follow the standard OTTO activation steps for your subdomain project. 4. Once activated, OTTO will only apply changes and recommendations to the subdomain project. Important: Each domain or subdomain with OTTO activated counts as a separate OTTO seat. If your plan includes a limited number of OTTO activations, make sure you have an available seat before proceeding. 📊 Step 3: Set Up Tracking for Your Subdomain Once your subdomain project is created, configure tracking to start collecting meaningful data. - Rank Tracker: Navigate to the Rank Tracker section within your subdomain project and add the keywords you want to monitor for the subdomain specifically. - Site Metrics: Ensure your subdomain project is selected so that all site metrics data is collected and displayed separately from your main domain. ❓ If You're Not Sure Where to Start If you are unsure which area of the platform to use for adding a new project or domain, or if you encounter any unexpected behavior when trying to set up your subdomain, our support team can walk you through the exact steps for your account and plan. When reaching out, please have the following ready: - Your main domain name already set up in Search Atlas - The full subdomain URL you want to add as a separate project - Your current plan details (so the team can confirm domain slot availability) - Any error messages or unexpected behavior you 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.

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

🔁 OTTO Pixel IDs Across Multiple PRO Versions

🔍 Overview Each OTTO pixel ID is unique and permanently tied to the PRO workspace where it was first generated. If you install a website in one PRO version and then try to add the same website to a different PRO version, you cannot reuse or overwrite the existing pixel ID. A brand-new pixel ID will be generated for that second workspace instead. Understanding this behavior will help you plan your workspace setup and avoid confusion when managing multiple PRO accounts or client projects. 🧩 How OTTO Pixel IDs Work When you connect a website to OTTO for the first time, Search Atlas generates a unique pixel ID specifically for that website within your current PRO workspace. This pixel ID is the identifier that links your site's data to your workspace. - One pixel ID per workspace per website: Each PRO workspace issues its own pixel ID for a given domain. - Pixel IDs are not transferable: A pixel ID created in Workspace A cannot be moved to, reused in, or overwritten by Workspace B. - Workspace isolation: Data collected under one pixel ID stays within that workspace. It will not carry over if you generate a new pixel ID for the same domain in another workspace. ⚠️ What Happens When You Add the Same Website to Another PRO Version If you attempt to install a website that already has an OTTO pixel in one PRO workspace into a second PRO workspace, the following will occur: 1. Search Atlas detects the domain as new within the second workspace. 2. A fresh, unique pixel ID is generated for that workspace. 3. You will need to replace the pixel code on your website with the new pixel ID if you want the second workspace to collect data. 4. Any historical data tied to the original pixel ID remains in the first workspace and is not accessible from the second. In short, you cannot overwrite an existing OTTO pixel ID from another workspace. The two pixel IDs will exist independently, and only the one currently installed on your website will collect data. 🛠️ Recommended Workaround If you need to manage a website under a different PRO version, follow these steps: 1. Go to the left sidebar and select OTTO SEO, then open SEO Automation (URL: /seo-automation-v3) inside the PRO workspace where you want to add the site. 2. Create a new project for the domain in that workspace. 3. Copy the new OTTO pixel ID that is generated for this workspace. 4. Update the pixel code on your website by replacing the old pixel ID with the new one. 5. Verify that the new pixel is firing correctly before removing or archiving the project in the original workspace. Important: Once you switch the pixel on your website to the new ID, the original workspace will stop receiving data for that domain. Make sure you export or note any reports you need from the first workspace before making the switch. 📋 Key Rules to Remember - OTTO pixel IDs are workspace-specific and cannot be shared or transferred between PRO versions. - Adding the same domain to multiple workspaces simultaneously is technically possible, but only the pixel ID installed on your website will actively collect data. - Historical data does not migrate between workspaces when you switch pixel IDs. - Always update the pixel code on your website after switching workspaces to ensure accurate data collection. 💬 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.

🔧 Cloudflare API Token Permissions for Clearview

🌐 Overview Connecting Clearview to your Cloudflare account requires a Cloudflare API token with specific permissions. A common issue customers encounter is searching for a Workers Routes permission that no longer exists in the current Cloudflare dashboard. This article explains exactly which permissions to select and how to create the token correctly using the updated Cloudflare UI. ⚠️ Common Mistake: Workers Routes Permission Older versions of the Clearview integration guide referenced a Workers Routes permission inside Cloudflare's token creation screen. Cloudflare has since redesigned their token creation interface, and this permission label no longer appears. If you have been searching for it, that is why the setup has been failing. You do not need a Workers Routes permission — follow the steps below to configure the correct permissions. ✅ Required API Token Permissions When creating your Cloudflare API token for the Clearview integration, you must include the following permissions: - Zone — DNS — Edit: Allows Clearview to read and update DNS records on your domain. - Zone — Zone — Read: Allows Clearview to identify and access your Cloudflare zone (domain). These two permissions are sufficient for the integration to function. Do not add unnecessary permissions, as this can cause authorisation errors. 🛠️ How to Create the API Token 1. Log in to your Cloudflare dashboard at dash.cloudflare.com. 2. Click your Avatar Menu (👤) in the top-right corner and select My Profile. 3. Navigate to the API Tokens tab on the left sidebar. 4. Click Create Token. 5. Scroll down and select Create Custom Token by clicking Get started. 6. Give your token a recognisable name, such as Clearview Integration. 7. Under Permissions, add the following two permission rows: - Row 1: Select Zone — DNS — Edit - Row 2: Click Add more, then select Zone — Zone — Read 8. Under Zone Resources, set the scope to Include — Specific zone and select the domain you are connecting to Clearview. 9. Click Continue to summary, review the permissions, then click Create Token. 10. Copy the token immediately — Cloudflare will only show it once. 🔗 How to Enter the Token in Search Atlas 1. Open the Search Atlas platform and navigate to the Clearview integration settings. 2. Paste your Cloudflare API token into the designated field. 3. Click Connect or Save to complete the integration. 4. Wait a few moments for the connection to verify. A green confirmation indicator means the integration is active. 🚨 Troubleshooting: Authorisation Failed (cf_10000) If you see an error message referencing Cloudflare API Authorization failed or error code cf_10000, this usually means one of the following: - The token was created with missing or incorrect permissions — recreate it using the steps above. - The token was scoped to the wrong zone — ensure the correct domain is selected under Zone Resources. - The token was not copied in full — return to Cloudflare, revoke the old token, and generate a new one. After fixing the token, return to the Clearview integration settings in Search Atlas, remove the old token, paste the new one, and reconnect. 💬 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.

🔌 Using Search Atlas with SiteGround Speed Optimizer

🧩 Compatibility Overview The Search Atlas WordPress plugin is fully compatible with SiteGround Speed Optimizer. You can safely disable LiteSpeed Cache and switch to SiteGround Speed Optimizer without affecting how Search Atlas functions on your site. The two plugins do not conflict, and no special configuration is required to make them work together. 🔄 How to Switch from LiteSpeed Cache to SiteGround Speed Optimizer Follow these steps to migrate cleanly and avoid any temporary performance gaps on your site. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate LiteSpeed Cache and click Deactivate. 4. Once deactivated, click Delete to remove LiteSpeed Cache entirely. This prevents any settings conflicts. 5. If SiteGround Speed Optimizer is not yet installed, go to Plugins → Add New, search for SiteGround Speed Optimizer, then click Install Now and Activate. 6. Open SiteGround Speed Optimizer settings and configure caching, minification, and image optimization according to your preferences. 7. Confirm the Search Atlas plugin is still active under Plugins → Installed Plugins. No reconfiguration is needed. ✅ What Continues to Work Normally After switching caching plugins, all Search Atlas features continue to operate without interruption. This includes: - On-page SEO analysis and audits - Content scoring and recommendations - Keyword tracking and reporting - Any data syncing between your site and the Search Atlas platform SiteGround Speed Optimizer handles front-end performance independently from Search Atlas, so there is no functional overlap between the two plugins. ⚠️ Things to Keep in Mind - Clear your cache after completing the switch. Residual LiteSpeed Cache data can occasionally cause pages to load outdated assets. In SiteGround Speed Optimizer, go to Supercacher → Flush Cache to clear everything. - Test your site after the migration. Load a few key pages and confirm they render correctly and that no console errors appear. - Avoid running two caching plugins simultaneously. Having both LiteSpeed Cache and SiteGround Speed Optimizer active at the same time can cause caching conflicts, slow load times, or broken page layouts. Always deactivate one before activating the other. - If your hosting plan is on SiteGround, SiteGround Speed Optimizer is the recommended caching solution and is optimised for that hosting environment. 🛠️ Troubleshooting After the Switch If you notice any unexpected behaviour after switching plugins, try the following: 1. Clear the SiteGround Speed Optimizer cache and reload your site. 2. Temporarily deactivate SiteGround Speed Optimizer and check whether the issue persists. This helps isolate the cause. 3. Re-check that Search Atlas is still active and that your API connection to the platform is intact by logging in to Search Atlas and confirming data is still populating as expected. 4. If pages look broken, check for minification conflicts. In SiteGround Speed Optimizer, try disabling CSS Minification or JavaScript Minification one at a time to identify the source. 💬 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.

🛠️ Signal Genesys External API Technical Reference

📋 Overview The Signal Genesys External API allows you to programmatically manage press releases, entities, media assets, and distribution channels from within your own workflow. This article covers the key technical areas customers most commonly ask about, including entity configuration, release publishing, credit management, image handling, request validation, and response schema details. Because the full technical specification for the Signal Genesys External API — including verified endpoint paths, required and optional field names, parameter flags, credit deduction logic, and behavioral rules — is not publicly documented in a single reference, the details for your specific implementation may vary. Our team can confirm the exact specifications that apply to your account and integration. 🏷️ Configuring Entities Entities represent the brand, person, or organisation associated with a press release. If you have questions about which fields are required for entity configuration, how entity updates affect previously published releases, or how to reference entities across multiple releases, please reach out to our team with the following information ready: - Your Signal Genesys account name or project identifier - The specific entity type you are working with (e.g. brand, person, or organisation) - A description of the behaviour or error you are experiencing, including any exact error messages and timestamps 📤 Publishing Releases Publishing a press release through the API involves submitting a validated payload. Common questions in this area include draft versus published states, how distribution channel variants are handled on re-submission, batch submission behaviour, and indexation tracking. To get accurate guidance for your integration, please have the following ready when you contact us: - Your Signal Genesys account name or project identifier - The endpoint and request method you are using - The exact error message or unexpected behaviour you observed, including timestamps - A sanitised version of your request payload (remove any sensitive credentials before sharing) 💳 Understanding and Managing Credits Credits govern how many releases you can publish. If you have questions about when credits are deducted, how draft versus published states affect your credit balance, or how to track remaining credits, our team can confirm the exact rules that apply to your account plan. Please have the following ready: - Your Signal Genesys account name - The specific action you took (e.g. publishing, re-submitting to additional channels) and the credit change you observed - Any relevant timestamps 🖼️ Image Management, Request Validation, and Response Schemas For questions about uploading and referencing images in release payloads, understanding validation error responses, or interpreting API response schemas, the specifics depend on your API version and account configuration. When escalating these questions, please include: - Your Signal Genesys account name or project identifier - The API version or integration type you are using, if known - The exact validation error message or response body you received, including timestamps 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 and Install OTTO Pixel on Squarespace

🧩 What Is the OTTO Pixel? The OTTO Pixel is a small tracking script that connects your Squarespace website to Search Atlas. Once installed, it allows OTTO to collect on-site data and power AI-driven SEO automation for your site. There are two parts to this process: finding your unique OTTO Pixel UUID script in Search Atlas, and then adding it to your Squarespace site. Both steps are covered below. 📍 Step 1: Find Your OTTO Pixel UUID Script Your OTTO Pixel script is unique to your website. Follow these steps to locate it inside Search Atlas: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → SEO Automation (URL: /seo-automation-v3). 3. Select the website project you want to track. 4. Look for the OTTO Pixel or Pixel Setup section on the dashboard. This section displays your unique UUID tracking script. 5. Click Copy to copy the full script to your clipboard. The script will look similar to this: <script src="https://pixel.searchatlas.com/otto.js?uuid=YOUR-UNIQUE-ID"></script> Important: Your UUID is unique to your account and website. Do not share it publicly or use another site's UUID. 🌐 Step 2: Add the OTTO Pixel to Your Squarespace Site Squarespace allows you to inject custom code through its built-in Code Injection feature. This is the correct method for adding the OTTO Pixel to a Squarespace website. 1. Log in to your Squarespace account and open the website where you want to install the pixel. 2. In the left panel, go to Settings. 3. Under the Website section, click Advanced. 4. Click Code Injection. 5. In the Header field, paste the full OTTO Pixel script you copied from Search Atlas. 6. Click Save in the top-left corner. The pixel is now active on every page of your Squarespace site. No additional steps are needed per page. ✅ Step 3: Verify the Pixel Is Working After saving, confirm the pixel is firing correctly: - Return to OTTO SEO → SEO Automation in Search Atlas (/seo-automation-v3). - Check the OTTO Pixel status indicator for your website project. It may take a few minutes to reflect an active status after installation. - Visit your Squarespace website in a browser and reload the page to trigger the pixel. - If the status updates to Active or Connected, your installation is complete. ⚠️ Common Issues and Tips - Script not saving: Make sure you are pasting the script into the Header field, not the Footer or Page Header fields, and that you click Save before leaving the page. - Status still showing as inactive: Allow up to 10 minutes and then reload the Search Atlas dashboard. Clear your browser cache and revisit your Squarespace site to re-trigger the pixel. - Using a Squarespace Developer template: If your site uses a custom Developer Mode template, you may need to add the script directly to the <head> tag in your template files instead of using Code Injection. - Do not use WordPress instructions: Code Injection in Squarespace is different from WordPress plugin or theme methods. The steps above are specific to Squarespace only. 💬 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.

💬 Managing Live Chat Sessions and Workflow Messages

🗺️ Overview If you are setting up or testing a new workflow for a client, it is important to know how to properly close an active chat session and validate that your messages are working as expected. This article walks you through both actions so your workflow testing runs smoothly. 💬 How to Close an Active Chat Session When you have finished a conversation in the live chat widget — whether it was a real support interaction or a test session — you can close it at any time. Follow these steps: 1. Locate the live chat widget in the bottom-right corner of the Search Atlas platform. 2. Open the active chat session you want to close. 3. Look for the close or end conversation option within the chat window (usually a small X icon or a menu option inside the widget). 4. Confirm the closure when prompted. The session will be marked as resolved and removed from your active queue. Note: Closing a chat session does not delete the conversation history. Previous messages remain accessible for reference. 🛠️ Testing a New Workflow Message for a Client Before launching a workflow message to a client, it is good practice to test it internally to make sure the content, formatting, and triggers behave as expected. Here is how to do that: 1. Navigate to Coworker using the left sidebar, or go directly to /coworker in your browser URL. 2. Select the workflow or message sequence you are building or editing for the client. 3. Use the built-in preview or test option within the workflow editor to simulate how the message will appear to the recipient. 4. Review the message content, variables, and any conditional logic to confirm everything displays correctly. 5. If the workflow includes automated triggers, verify that the trigger conditions match the intended client scenario before activating. 6. Once validated, save and activate the workflow for the client. ✅ Best Practices for Workflow Validation - Use a test account or sandbox client profile whenever possible to avoid sending unfinished messages to real clients. - Label test sessions clearly so team members know a conversation is part of a workflow test and not a live client issue. - Close test chat sessions promptly after validation is complete to keep your support queue clean and accurate. - Document your workflow changes with a brief internal note so your team stays aligned on what was updated and why. ❓ Frequently Asked Questions Can another team member close a chat session I started? Yes, any team member with the appropriate permissions can close an open session from within the platform. Will closing a test chat affect the client's live workflow? No. Closing a chat session only resolves that specific conversation. It does not modify or deactivate any workflow you have set up for the client. What if the workflow message does not trigger correctly during testing? Double-check the trigger conditions and any dynamic variables inside the Coworker workflow editor. Make sure all required fields are filled in and that the client profile used in the test matches the expected trigger criteria. 🙋 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.

🔗 Connect GSC and Analytics to Search Atlas Projects

🧭 Overview Connecting Google Search Console (GSC) and Google Analytics to your Search Atlas projects unlocks performance data directly inside the platform. If your GSC property dropdown appears empty or your Analytics accounts have been disconnected, this article walks you through what to check and how to escalate if needed. ⚠️ The Most Common Mistake: Wrong Starting Page The most frequent reason the GSC property dropdown appears empty is that customers attempt to connect GSC from the wrong location. The connection must be made from the top-right avatar (Avatar Menu (👤)) → Settings → Integrations. If you start from the wrong page, the dropdown will show no properties even if your Google account is fully authorised. ✅ How to Connect Google Search Console to a Project 1. Click the top-right avatar to open the Avatar Menu (👤), then go to Settings → Integrations. 2. On the Integrations page, locate the Google Search Console connection area. 3. Follow the on-screen prompts to authorise your Google account if you have not done so already. 4. Once authorised, the property dropdown will populate with all GSC properties available in the connected Google account. Select the property that matches your project's domain. 5. Confirm the connection using the available option on that page. Important: If you navigate to the general projects list page and try to edit the connection from there, the property dropdown will remain empty. Always open the individual project first. ✅ How to Connect Google Analytics to a Project 1. Open the specific project by clicking into it from your projects list. Confirm you are on the project overview page. 2. Locate the Google Analytics connection area on the same overview page. 3. Follow the on-screen prompts to authorise your Google account when asked. 4. Select the correct Analytics account, property, and data stream from the dropdowns that appear. 5. Confirm the connection using the available option on that page. 🔄 Why Was My Google Analytics Account Disconnected? Google Analytics accounts can become disconnected for several reasons. The most common causes are: - Google OAuth token expired or revoked: If you removed Search Atlas from your Google account's authorised apps, or if the token expired, the connection will drop. - Google account password changed: Changing your Google account password can invalidate active tokens for connected third-party apps. - Google account permissions changed: If your access level to the Analytics property was reduced or removed by an admin, the connection may break. In all of these cases, reconnecting from the top-right avatar (Avatar Menu (👤)) → Settings → Integrations using the steps above should restore the connection. 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.

☁️ Cloudflare Setup Guide Now Updated

We've updated the Cloudflare installation guide to reflect the latest changes to Cloudflare's token-creation interface, making it easier to connect your site without confusion or mismatched steps. ✨ What's New The Cloudflare setup guide inside the platform has been revised to align with Cloudflare's revamped token-creation UI. If you've previously found the steps unclear or noticed that the instructions didn't match what you were seeing on Cloudflare's side, the guide now accurately reflects the current experience — so you can complete your integration with confidence. 🛠️ How to Use It 1. Navigate to the OTTO SEO section of your platform. 2. Locate the Cloudflare integration setup option. 3. Follow the updated step-by-step guide to create your Cloudflare token and complete the connection. 📋 What to Expect The core integration process remains the same — only the on-screen instructions have been updated to match Cloudflare's current interface. If you completed this setup previously, no action is required 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.

🔌 Disconnect Your Google Ads Account Integration

🔍 Overview If you no longer want Search Atlas to access your Google Ads data, you can disconnect the integration at any time. This article explains how to remove the connection and how to get help if needed. 🛠️ How to Disconnect Google Ads Follow these steps to disconnect your Google Ads integration: 1. Log in to your Search Atlas account. 2. Click on Settings in the main navigation. 3. Navigate to the Integrations section. 4. Locate Google Ads in the list of connected accounts. 5. Select the option to disconnect or remove the Google Ads integration. 6. Confirm the action when prompted to complete the disconnection. Once the steps are complete, your Google Ads integration will be removed from Search Atlas. 🔄 Reconnecting Google Ads Later If you want to restore the integration in the future, return to Settings and navigate to the Integrations section. From there you can reconnect your Google Ads account and re-authorise access through your Google account. 💡 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.

🔍 Holistic SEO Pillars API Endpoint Reference

Overview If you are looking to retrieve Holistic SEO Pillars audit data programmatically via the Search Atlas API, this article explains what you need to know about finding the correct endpoint and parameters for your request. Why This Article Exists Customers have contacted support specifically to ask for the API endpoint and parameter details needed to pull Holistic SEO Pillars audit data. The exact endpoint path and parameter names are not documented in a single publicly indexed location, which is why this gap exists. Because the specific endpoint details are not confirmed in available source material, the steps below explain how to get this information directly and what to have ready when you reach out to the team. Step 1: Locate Your API Key All Search Atlas API requests require authentication with your API key. To find your API key: 1. Log in to your Search Atlas account. 2. Navigate to your account settings area within the platform. 3. Look for the section related to API access or developer credentials. 4. Copy your API key — you will need to pass this as an authentication credential in every request. Step 2: Find the Holistic SEO Pillars Endpoint The Holistic SEO Pillars audit data is available through the Search Atlas REST API. However, because the exact endpoint path and required parameter names have not been publicly confirmed in available documentation, we recommend the following: 1. Check the Search Atlas API Documentation accessible from within your account dashboard for any reference to Holistic SEO Pillars or Site Audit endpoints. 2. If the endpoint is not listed there, contact the support team directly — a support agent can provide you with the confirmed endpoint URL, required parameters, and an example request. 3. When you reach out, have your project name, the domain you are auditing, and your intended use case ready so the team can give you the most accurate endpoint details. Step 3: What to Have Ready To get a working API call as quickly as possible, prepare the following before reaching out: - Your project name as it appears in your Search Atlas account - The domain associated with the Holistic SEO Pillars audit you want to query - The type of data you need (e.g., full audit results, specific pillar scores, historical data) - Any error message or response code you have already received if you attempted a request - The request you already tried, including the endpoint path and any parameters you used 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 Understand Marketplace Publisher Listings and Tabs

This article explains common sources of confusion when browsing publisher listings in the Marketplace — specifically, discrepancies in the number of publishers shown under a category, and uncertainty about which tab you are viewing. If you are seeing fewer publishers than expected or are unsure whether you are looking at the right section of the Marketplace, the steps below will help you investigate and escalate effectively. 🔍 Common Causes of the Discrepancy - You may be on the wrong tab. The Marketplace contains multiple tabs (for example, one for publishers available for placement and one for campaigns you are managing). Confirm you are viewing the correct tab for your use case before drawing conclusions about the number of listings visible. - Filters may be narrowing your results. Category filters such as a Domain Authority minimum threshold will limit the publishers displayed. A publisher whose score sits at or near the boundary of a filter range may appear or disappear depending on how the filter is applied. - Publisher scores and listings can change over time. A publisher may have qualified for a tier at the time they were listed, but their metrics may have since shifted. This can cause apparent discrepancies between what a category label suggests and what is currently shown. 🛠️ What to Check Before Escalating 1. Navigate to the Marketplace section of the platform and confirm which tab is currently active. Make note of the exact tab name you are on. 2. Check whether any filters are applied to your current view (such as Domain Authority range or category). Note the exact filter values in use. 3. If a specific publisher appears to be missing or seems out of place, note the publisher's name and the category or tier you expected to find them in. 4. If the issue persists after checking your tab and filter settings, prepare the following information before reaching out to support: the publisher name(s) involved, the category or tier you are browsing, any filter values you have set, and a description of what you expected to see versus what is displayed. ✅ How to Confirm the Issue You will know the discrepancy is worth escalating when: (1) you have confirmed you are on the correct tab; (2) you have verified that no filters are unintentionally restricting your results; and (3) the publisher count or listing you expect is still not appearing. At that point, gathering the details listed above will allow our team to investigate the specific discrepancy on the backend. 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.

Staging to Production Migration: GSC Connection Guide

Should You Set Up on Staging or Production First? Search Atlas recommends completing your initial setup on your production environment whenever possible. This ensures that the domain Search Atlas tracks matches the property verified in Google Search Console (GSC), which helps prevent authentication mismatches and data gaps. If your workflow requires staging setup first — for example, to test tracking before a site launch — that is supported, but you must reconnect your GSC account after pushing to production. The authentication is tied to the domain and environment at the time of connection, so it does not carry over automatically. What Happens to Your GSC Connection During Deployment? When you push from staging to production, your GSC connection will likely break. This is expected behavior and not a bug. Staging and production URLs are treated as separate properties in GSC, and the authorization state stored by Search Atlas becomes invalid when the domain changes. Until you reconnect, Search Atlas will not be able to pull GSC data for your production site. Recommended Setup Order 1. Launch your production site and verify ownership of the production domain inside Google Search Console. 2. Log in to Search Atlas and navigate to Site Metrics → Site Explorer → Manage Sites/Connect GSC Account (GSC Accounts page). 3. Connect GSC using your production property (see the steps below). 4. Allow some time for data to begin populating from your production domain. If you have already connected GSC on staging and have now deployed to production, skip straight to the reconnection steps below. How to Connect or Reconnect Your GSC Account 1. Log in to Search Atlas and navigate to Site Metrics → Site Explorer → Manage Sites/Connect GSC Account (GSC Accounts page). 2. If a previous GSC connection exists, remove the stale staging connection before proceeding. 3. Initiate a new GSC connection and complete the OAuth authorization flow. Make sure you select the Google account that has access to your production GSC property. 4. Once connected, Search Atlas will automatically import every verified GSC property that the connected Google account has access to. Unverified properties are not imported. 5. Allow some time for production data to begin syncing. If you are unsure which Google account holds access to your production GSC property, check your GSC account directly at search.google.com/search-console before initiating the connection in Search Atlas. 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 User Refresh and MCP Data Access

🗺️ Overview This article covers two common questions about Search Atlas integrations: how to refresh the list of WordPress users available for content publishing, and what analytics data can be accessed through the Model Context Protocol (MCP) for Claude. Both topics are handled separately below. 👤 Refreshing WordPress Users for Content Publishing When you connect a WordPress site to Search Atlas, the platform pulls in a list of authors and users from that site. If you add new WordPress users after the initial connection, you will need to manually refresh the list so Search Atlas recognises them for content publishing assignments. ✅ Prerequisites - An active WordPress site connected to Search Atlas via the WordPress integration. - The Search Atlas plugin installed and activated on your WordPress site. - Administrator-level access on both your WordPress site and your Search Atlas account. - Any new users you want to appear must already exist in WordPress before you refresh. 🔧 How to Refresh WordPress Users The exact location of the WordPress user refresh option may vary depending on your account configuration. To find and use it: 1. Log in to your Search Atlas account. 2. Go to your integrations or settings area and open your WordPress integration. 3. Look for a refresh or re-sync option associated with your connected WordPress site and select it. 4. Search Atlas will re-fetch the user list from your WordPress site. This typically completes within a few seconds. 5. Once the refresh is complete, your updated user list will be available when assigning authors to content tasks and publishing workflows. Note: If a user does not appear after refreshing, confirm that the user account exists and is active in WordPress, and that the Search Atlas plugin has the correct API credentials to communicate with your site. If you are unsure where to find the refresh option in your account, please reach out to our support team for step-by-step guidance. 📊 GA4 and Google Ads Data Through MCP for Claude The Search Atlas MCP (Model Context Protocol) integration allows Claude to access analytics and advertising data from your connected accounts. Because the specific data fields and reports available through MCP can vary by account configuration and may be updated over time, we recommend contacting our support team to confirm exactly which GA4 and Google Ads data points are accessible for your setup and how to use them in custom client reporting workflows. 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.

🚀 Create Cloud Stacks via API with OTTO

Overview Cloud Stacks can be created within OTTO projects using knowledge bases via the Search Atlas API. This article explains what you will need and how to get started. Because the exact endpoint details, required payload fields, and navigation paths vary based on your account configuration, our team can walk you through the precise steps for your setup. What You Need Before You Start - A Search Atlas account with an active OTTO project - Your OTTO Project ID (found within your Search Atlas account) - Your Knowledge Graph ID (linked to the OTTO project, found within your Search Atlas account) - Your Search Atlas API key (found in Avatar Menu (👤) → Settings → API Keys) - An API client capable of sending HTTP requests How to Find Your OTTO Project ID and Knowledge Graph ID Your OTTO Project ID and Knowledge Graph ID are available within your Search Atlas account when you open the relevant OTTO project. In many cases, these IDs appear in the page URL when you are viewing that project. If you are unsure where to locate them, our support team can help you identify the correct values for your account. Authentication Every API request to Search Atlas must be authenticated using your Search Atlas API key. Include your API key as a Bearer token in the Authorization header of each request. Never share your API key publicly. You can locate your API key in Avatar Menu (👤) → Settings → API Keys. Sending Your API Request To create a Cloud Stack via the API, you will need to send an authenticated request that references your OTTO Project ID and Knowledge Graph ID. The specific endpoint URL, required JSON payload fields, and exact parameter names for Cloud Stack creation are confirmed in the Search Atlas API documentation available in your account portal. We recommend consulting that documentation for the most accurate and up-to-date details. Need Help Getting Started? If you are unsure of your OTTO Project ID, Knowledge Graph ID, or the correct API endpoint and payload structure for your account, our team is here to help. When reaching out, please have the following ready: - Your OTTO project name - The knowledge base you intend to use - Any error messages or response codes you have received - The API client you are using 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.

🔗 Webflow CMS Metadata Mapping and Sync Explained

📋 Overview When you publish content from Search Atlas to a Webflow CMS collection, SEO metadata fields — including the page title, meta description, and canonical URL — may not sync as expected. This article explains what is known about Webflow CMS metadata mapping behavior, what to expect, and how to escalate if you encounter issues. 🗂️ About Webflow CMS Metadata Sync Some customers have reported that SEO metadata fields (such as meta title, meta description, and canonical URL) do not behave the same way as standard content fields during a Webflow CMS publish from Search Atlas. If you are experiencing unexpected results with metadata syncing to your Webflow CMS collection, this is a known area of investigation. Because the root cause of metadata mapping and sync issues in Webflow CMS integrations is handled at the backend level, there are no confirmed self-serve steps that reliably resolve this issue. Attempting to reconfigure field mappings on your own may not fix the problem if the underlying sync behavior is the cause. 🛠️ What to Have Ready When Escalating If you are experiencing metadata mapping or sync issues with your Webflow CMS integration, please gather the following before reaching out to our team so we can investigate as quickly as possible: - Your Webflow CMS collection name and the specific metadata fields (e.g., meta title, meta description, canonical URL) that are not syncing correctly. - The exact content item or items affected — including the article or page name and any relevant URLs. - A description of the behavior you are seeing — for example, whether fields are appearing blank, showing incorrect values, or not updating after a publish. - The timestamp of when you last attempted to publish and observed the issue. - Any error messages displayed in the Search Atlas interface during or after publishing. 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 Public GHL Domain Anytime

🔍 What Is the Public GHL Domain? Every Search Atlas account built on GoHighLevel (GHL) comes with a permanent public domain assigned at the time of account creation. This domain exists regardless of whether you have connected a custom domain. It acts as a fallback URL and is always accessible, even if your custom domain expires or is disconnected. If you have always used a custom domain, your public GHL domain runs quietly in the background. You may never have seen it — but it is there. ⚠️ Why Settings > Domains Won't Show It Many users navigate to Settings > Domains expecting to see all their domains in one place. However, this section only displays domains you have manually connected to your account. Your default public GHL domain is not listed here because it is assigned at the platform level, not configured by you. 📋 How to Find Your Public GHL Domain Because the exact location of the public GHL domain within the GHL interface can vary depending on your account setup, the most reliable way to retrieve it is to contact our support team. To get help as quickly as possible, have the following ready before reaching out: - Your GHL sub-account name or ID - The custom domain currently connected to your account (if any) - A brief description of why you need the public GHL domain (e.g., fallback URL, DNS troubleshooting) A member of our team will locate your permanent public GHL domain and share it with you directly. ✅ Once You Have the Domain Once you have identified your public GHL domain, paste it into a new browser tab and press Enter to confirm it loads correctly. Copy and save it somewhere accessible for future reference, as it serves as a permanent fallback URL independent of any custom domain 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.

🔧 Fix an Incorrect Shopify Store Connection in Publish

Overview If the wrong Shopify store is showing in your Publish menu — for example, you see dahingplants.com but need grandeplants.com — this means a different store was connected at some point during setup. This article explains why this happens and how to get it resolved quickly. Why the Wrong Store Appears This usually happens for one of the following reasons: - A different Shopify account was logged in when the connection was first authorised. - The OAuth authorisation flow was completed on the wrong store's admin page. - Multiple Shopify stores exist under related accounts and the wrong one was selected during setup. The good news is this is fully reversible — the incorrect store can be disconnected and the correct one reconnected. How to Fix a Wrong Shopify Store Connection Because the exact steps for disconnecting and reconnecting a Shopify store in the Publish menu depend on your specific account configuration, a member of our support team will need to walk you through the process or make the change on your behalf. To get this resolved as quickly as possible, please have the following information ready before reaching out: - Your Search Atlas project name - The incorrect store domain currently showing in the Publish menu (e.g., dahingplants.com) - The correct store domain you want to connect (e.g., grandeplants.com) - A screenshot of the Publish menu showing the wrong store, if possible Having these details ready will allow a teammate to identify your account immediately and action the store switch without delay. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚧 Ad Studio MCP Agency Workflow Blockers Explained

Overview If you are using the Ad Studio MCP (Model Context Protocol) to automate agency workflows, you may encounter limitations that affect multi-account analytics and creative deployment. This article explains what is happening and what to have ready when contacting our team. What Is Happening Customers using the Ad Studio MCP for agency workflows involving multiple ad accounts have reported gaps in analytics data and creative deployment functionality. What This Affects - Multi-account analytics queries run through the MCP - Creative deployment tasks automated via MCP What You Should Do Now Because these are platform-level limitations rather than configuration issues, there are no self-serve steps that will fully resolve the gaps at this time. To get help as quickly as possible, please have the following ready when you contact our team: - The name of the ad account or accounts where you are experiencing the issue - A description of the specific MCP action or query that is producing unexpected results (e.g., analytics not returning, creative not deploying) - Any exact error messages or unexpected responses you have received - The approximate date and time when you first noticed the problem Having this information ready will allow our team to investigate your specific case and escalate it appropriately. 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.

🛠️ Project Deletion and Open Pull Requests

📌 What happens when you delete a project? Deleting a Search Atlas project removes the project and its associated data from Search Atlas. This action does not delete pull requests that were already created in your connected Git provider. 🔀 What happens to an open pull request? An open pull request remains in your Git provider, such as GitHub, GitLab, or Bitbucket. You can still review, approve, merge, or close it there. However, after the Search Atlas project is deleted, Search Atlas can no longer monitor or manage that pull request. Project-specific status updates, recommendations, and future changes will no longer be available for the deleted project. ⚠️ Before deleting your project - Review all open pull requests associated with the project. - Decide whether to merge or close each pull request in your Git provider. - Save any project information or results you may need later. - Confirm that deleting the project is intentional, as project deletion may not be reversible. ✅ Recommended approach 1. Open your Git provider and review the project’s open pull requests. 2. Merge approved changes or close pull requests you no longer want. 3. Return to Search Atlas and delete the project only after completing your review. 💬 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 instantly connected with a member of our team.

Intercom Plugin Version Information

📌 Current plugin version Search Atlas does not publish a specific Intercom plugin version number in this article. To find the current version of the Intercom plugin used with Search Atlas, contact our support team directly — a teammate can confirm the exact version number tied to your account or integration setup. 🔍 What to have ready when you reach out To help our team answer your version question as quickly as possible, please have the following information on hand before contacting support: - Your Search Atlas account name or registered email address. - The platform or environment where the Intercom plugin is installed (for example, WordPress, Shopify, or a custom integration). - Any version number currently shown in your plugin or integration settings, if visible. - Any error messages or unexpected behavior you are experiencing that may be related to the plugin version. 💬 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 instantly connected with a member of our team.

🏷️ Fix Sender Name Showing User Instead of Agency

🔍 What This Issue Looks Like You have white label enabled, but some messages still say "from Jordan" (or another team member's name) instead of your agency name. Customers usually notice this in three places: - System emails, such as invitations, notifications, and reports - The WordPress pixel or plugin setup steps - Other messages that mention who the sender is This is frustrating when you are presenting the platform as your own brand. The steps below explain why it happens and how to fix it. 🧠 Why It Happens White label settings control your brand elements, such as your agency name, logo, and branded areas of the platform. However, some messages may still use the name on the user profile of the person who sent the invite or set up the account. If that profile name is a personal name, it can appear as the sender instead of your agency. Other common causes include: - The agency or brand name field in the white label settings is empty or incomplete - White label changes were saved but not yet refreshed in your browser - The message was sent before you updated your settings (sent emails never change) - An older version of the WordPress plugin is installed on the site ✅ Step 1: Check Your White Label Settings 1. Log in to the platform with your agency owner or admin account. 2. Open your White Label settings (usually found in your account or workspace settings). 3. Confirm your agency or brand name is filled in exactly as you want it to appear. 4. Confirm your logo and any other branding fields are saved. 5. Click Save, then refresh the page to make sure the changes stuck. 👤 Step 2: Update the Profile Name If the personal name still appears, update the profile of the user who sends the emails or runs the setup: 1. Open your Profile or account settings. 2. Find the First name and Last name fields. 3. Change them to your agency name, or to a format such as "Your Agency Team". 4. Save your changes. This is a quick workaround because many messages use the profile name of the sending user. Remember that this changes the name for that user everywhere, so you may prefer to use a shared or team-style account for client-facing actions. 🔌 Step 3: Check the WordPress Pixel Setup If the wrong name appears while installing the pixel in WordPress: - Make sure you are logged in to the platform with the account that has white label enabled. - Update the Search Atlas plugin to the latest version, if you use the plugin method. - Clear your browser cache, or try a private browsing window, and open the setup again. - Check that the profile name from Step 2 has been updated, since the setup screens may display the connected user's name. 📧 Step 4: Send a Test Changes only apply to new messages. Emails that were already sent will keep the old sender name. 1. Trigger a new system email, for example by sending a fresh team invitation to a test address. 2. Check the sender name in the inbox. 3. Check your spam folder if it does not arrive within a few minutes. 💡 Tips to Avoid This in the Future - Complete all white label fields before inviting clients or team members. - Use an agency-branded profile name for the account that handles client onboarding. - Test a new invitation after any branding change. - Keep the WordPress plugin up to date. 🙋 Still Seeing the Wrong Name? Some sender names are set by the platform and may not be editable from your settings. Our team can review your account and check whether the change can be applied for you. To help us resolve it quickly, have these details ready: - Where the wrong name appears (system email, WordPress pixel setup, or elsewhere) - A screenshot showing the name - The email address of the user who sent or set up the item - The approximate date and time the message was sent If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛍️ Manage WooCommerce Product Indexing

🎯 Choose the right indexing action For a discontinued product, use noindex when the page should remain available to customers but should not appear in search results. Use a redirect or removal when the product page no longer provides value. Avoid blocking the URL in robots.txt if you want search engines to process the noindex instruction. ⚙️ Set the global Products rule To apply one indexing rule to WooCommerce products, open your SEO settings in WordPress and locate the section for Products or Product post types. Set products to index or noindex, then save the change. The exact menu name can vary depending on the SEO plugin connected to your WordPress site. This global setting is best for applying the same rule to all products. Check a product page afterward and confirm that its robots directive matches the setting. 📝 Update selected products in bulk 1. In WordPress, open Products. 2. Select the discontinued products you want to update. 3. Choose Edit from the Bulk actions menu and select Apply. 4. Change the available SEO or visibility fields provided by your SEO plugin, then save the updates. WordPress bulk editing does not always include a robots or noindex field. If that option is unavailable, update the products through your SEO plugin’s individual product settings, or use the plugin’s supported bulk editor. Do not rely on an OTTO SEO or Page Explorer workflow unless those controls are visibly available in your account. 🔍 Check that products are noindex 1. Open a product in WordPress and view its SEO settings. 2. Confirm the product is set to noindex, if that is your intended rule. 3. Open the public product URL and inspect its page source or use a robots-checking tool. 4. Look for a robots directive containing noindex. Allow time for search engines to recrawl the pages. A noindex directive does not remove a URL immediately from search results. ✅ Recommended approach for discontinued items - Keep the page and set it to noindex if customers may need product information. - Redirect it to a closely related replacement if one exists. - Return a proper 404 or 410 response when there is no useful replacement and the page should be removed. - Remove discontinued URLs from XML sitemaps where your SEO plugin provides that option. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🚀 Content Velocity and IP Whitelisting

🚀 What is Content Velocity? Content Velocity helps you publish content consistently and build topical coverage over time. A steady publishing pace can support your SEO strategy without creating sudden traffic or crawling spikes. 🛡️ Why whitelist Search Atlas IPs? Your CDN, firewall, or security tool may block automated Search Atlas requests. Whitelisting our current IP addresses helps Content Velocity operate reliably and prevents security rules from interrupting processing. 📋 Find the current IP list Use the official Search Atlas IP list here: https://bots.searchatlas.com/ip_list.txt Always use this live list rather than copying IP addresses into your configuration permanently. Search Atlas may update the list, so review it periodically and update your allowlist when needed. ⚙️ Add the IPs to your CDN or firewall 1. Open your CDN, web application firewall, hosting firewall, or security platform. 2. Find the IP allowlist, trusted IPs, or firewall rules section. 3. Add every IP address shown in the official Search Atlas list. 4. Save or publish the rule changes. 5. Confirm that your rules allow Search Atlas requests while keeping other protections enabled. 🔍 Troubleshoot Content Velocity issues If Content Velocity is delayed or cannot access your site, check that your allowlist includes the latest IP list and that no separate security layer is blocking requests. - Review CDN and firewall event logs for blocked Search Atlas requests. - Check rate limits, bot protection, CAPTCHA, and geo-blocking rules. - Make sure your site is available to authorized Search Atlas requests. - After changing rules, retry the Content Velocity action and monitor the result. ✅ Keep your configuration current IP addresses can change as Search Atlas infrastructure is updated. Bookmark https://bots.searchatlas.com/ip_list.txt and review it whenever Content Velocity behavior changes or your security configuration is updated. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔗 Connect Shopify with CMS Connectors

🛍️ Before you begin Make sure you have administrator access to both your Search Atlas account and Shopify store. Keep your Shopify store address available, including the .myshopify.com domain. 🔌 Connect Shopify 1. Sign in to Search Atlas. 2. Open Coworker from the left sidebar. 3. Select the Connectors tab. 4. Choose Shopify from the available CMS connectors. 5. Enter your Shopify store address when prompted, then select Connect. 6. Review the requested permissions and approve the connection in Shopify. 7. Return to Search Atlas and wait for the connector status to show as connected. ✅ Verify the connection Open Coworker → Connectors and confirm that Shopify is listed as connected. If Search Atlas displays a project or store selection, choose the Shopify store you want to use and save your selection. After connecting, allow time for Search Atlas to retrieve your store data. Refresh the connector page if the status does not update immediately. 🛠️ Troubleshoot connection issues - Confirm that you used the store’s .myshopify.com address rather than a customer-facing domain. - Check that you are signed in to the correct Shopify account and have administrator permissions. - Remove extra spaces from the store address and try again. - If Shopify opens in another browser tab, complete the authorization there before returning to Search Atlas. - Return to Coworker → Connectors and refresh the page to check the latest status. - If the connector is already linked to another Search Atlas project, disconnect it there before connecting it to a new project. 🔄 Reconnect or update Shopify To refresh an existing connection, open Coworker → Connectors, select the Shopify connector, and follow the authorization prompts again. Reauthorization can resolve expired permissions or changes to your Shopify account. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Install OTTO Pixel on GHL Websites

📌 Why this workaround is needed GoHighLevel (GHL) websites may not support installing the OTTO pixel through the standard site settings. You can work around this by adding the pixel to the website or funnel’s custom tracking code. 🔍 Copy the OTTO pixel 1. In Search Atlas, open AI SEO → OTTO SEO. 2. Open the relevant project and locate the OTTO pixel or installation instructions. 3. Copy the complete pixel code. Do not edit or remove any part of the code. ⚙️ Add the pixel in GHL 1. Sign in to GoHighLevel and open the relevant sub-account. 2. For a website, go to Sites → Websites and open the website settings. For a funnel, open Sites → Funnels and select the funnel. 3. Open the site, funnel, or step settings and find the Head tracking code, Custom code, or similar field. 4. Paste the complete OTTO pixel code into the head section. 5. Save the settings and publish the website or funnel. 🧪 Verify the installation 1. Open the live GHL page in a private browser window. 2. Use the OTTO installation check in Search Atlas, if available, and run the check again. 3. If the pixel is not detected, confirm that you pasted it into the head section of the published page, not only into the visual page editor. 4. Clear your browser cache and any site caching, then republish the page. ✅ Important checks - Install the pixel on every page or funnel step that should be monitored. - Make sure the code is added to the live domain, not only a GHL preview URL. - Do not place the code inside visible page content. - If the website uses multiple domains, repeat the installation for each domain. - Allow time for Search Atlas to detect a newly published pixel. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔌 MCP Capabilities for Scheduling Social Posts

💡 Overview The Search Atlas MCP (Model Context Protocol) connection lets an AI assistant such as Claude work with your Search Atlas account. Customers often ask two things: whether posts that were already written elsewhere can be pushed into the Search Atlas scheduler, and what data Claude can pull or submit. This article explains how to find out what your connection supports, what to expect for each data type, and what to do if a capability is not available to you. Important: The MCP only offers the actions (called tools) that Search Atlas has enabled for your account and connection. This list can change as we release updates, so the most reliable source is the live tool list in your own Claude session. Steps to check it are below. 🔍 Check What Your Connection Can Do Before you plan a workflow, confirm which tools are available to you: 1. Open Claude and make sure the Search Atlas MCP connector is turned on for your conversation. 2. Ask: What Search Atlas tools do you have access to? 3. Review the list. Look for tools related to reporting data, social posts, scheduling, and images. 4. Ask Claude to describe what each relevant tool can read, create, or change. If a tool for an action is not in the list, Claude cannot perform that action through MCP. In that case, use the manual steps described later in this article. 📅 Scheduling Already-Written Posts If you already have social posts written, whether by Claude or by another tool, you can use Claude to prepare them for Search Atlas. Whether Claude can submit and schedule them directly depends on whether a social posting or scheduling tool appears in your tool list. If a scheduling tool is available: 1. Make sure the social profiles you want to post to are connected in Search Atlas. 2. Give Claude the post text, any image, the target profile, and the date and time you want. 3. Include your time zone so the schedule is not shifted. 4. Ask Claude to confirm the details back to you before it submits anything. 5. After submission, open the Search Atlas scheduler and check that each post appears with the correct profile, date, time, and image. If no scheduling tool is available: - Ask Claude to format your posts so they are ready to copy, with the text, hashtags, and suggested posting times laid out clearly. - Paste or upload the posts into the Search Atlas social scheduler manually. 📊 What Claude Can Pull When the related data sources are connected to your Search Atlas account, Claude can typically use MCP to read information for analysis and reporting. Exact coverage depends on your plan, your connected accounts, and the tools enabled for you. - Google Analytics (GA): traffic and engagement data, if GA is connected to your project. - Google Search Console (GSC): search performance data such as queries, clicks, impressions, and pages, if GSC is connected. - Google Business Profile (GBP): profile and performance information, if your profile is connected. - Social posts: posts that exist in Search Atlas, such as drafts and scheduled items, where a tool exposes them. - Images: images stored in or attached to your Search Atlas content, where a tool exposes them. If a data source is not connected in Search Atlas, Claude cannot retrieve data from it. Connect the account in the platform first, then start a new Claude conversation so the latest connection is picked up. 📤 What Claude Can Submit Submitting data is more limited than reading it. Whether Claude can create or change something depends on whether a write-enabled tool exists for it. Depending on your connection, this may include: - Creating or updating social post drafts - Scheduling posts to connected social profiles - Attaching images to posts Anything not listed as an available tool should be treated as unsupported through MCP. Reporting sources such as GA and GSC are generally used for reading, not for making changes. ✅ Best Practices - Start with a test: Schedule one post first and verify it in the scheduler before sending a full batch. - Be specific: Give Claude the profile name, date, time, time zone, and image for each post. - Ask for a summary: Have Claude list what it plans to submit and confirm it before it acts. - Verify afterward: Check the scheduler to confirm everything was saved as expected. - Keep posts within platform limits: Each social network has its own character and image rules, so ask Claude to follow them. 🛠️ Troubleshooting - Claude says it cannot schedule posts: A scheduling tool may not be enabled for your connection. Use the manual scheduler as a workaround. - Data is missing or empty: Confirm the data source is connected in Search Atlas and that you selected the right project. - Posts do not appear in the scheduler: Check that the right social profile is connected, then ask Claude what the tool returned after submission. - Images are not attached: Confirm the image is available to Claude and meets the size and format rules for the social network. - Tools seem outdated: Disconnect and reconnect the MCP connector, then start a new conversation. 🤝 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Let us know which tools Claude lists for you and what you are trying to schedule, so we can confirm what is available for your account.

🔗 Connecting Google Search Console and Cloudflare

❓ The Short Answer Google Search Console (GSC) and Cloudflare are two separate tools. Connecting GSC to Search Atlas does not require a Cloudflare account. You only need Cloudflare if your website already uses it, or if you choose a setup method that relies on it. - Google Search Console: shares your search performance data (clicks, impressions, rankings) with Search Atlas. - Cloudflare: is a website and DNS service. It is only relevant for certain site setup or deployment options. 🌐 Which Site Address Should I Enter? Enter the site address exactly as it appears in your Google Search Console account. GSC uses two property types, and the format differs slightly: - Domain property: shown without a prefix, for example example.com. - URL-prefix property: shown with the full address, for example https://www.example.com/. Include the https:// and any www, and keep the trailing slash. If the address does not match your GSC property, the connection may fail or show no data. 🔍 How to Find Your Property in Google Search Console 1. Sign in to Google Search Console with the Google account that manages your website. 2. Click the property selector in the top-left corner of the page. 3. Find your website in the list and note exactly how it is written. 4. Copy that address and use it when connecting in Search Atlas. If your website is not listed, you need to add and verify it in Google Search Console first. Search Atlas can only connect to properties your Google account already has access to. 🔌 How to Connect Google Search Console in Search Atlas 1. Open the Google Search Console connection prompt in your Search Atlas project. 2. Click the option to connect and sign in with the Google account that has access to your property. 3. Approve the permissions Google asks for so Search Atlas can read your search data. 4. Select the property that matches your website address. 5. Save or confirm the connection and wait a few minutes for your data to begin syncing. ☁️ Do I Need a Cloudflare Account? It depends on how your website is set up: - Your site already uses Cloudflare: you already have an account. Sign in with it if a setup step asks for Cloudflare access. - Your site does not use Cloudflare: you do not need one just to connect Google Search Console. Only create one if you choose a setup method that requires it. - You are not sure: ask whoever manages your domain or hosting whether your DNS runs through Cloudflare. Search Atlas does not need a Cloudflare account to read your Google Search Console data. If a Cloudflare step appears during setup, follow the on-screen instructions for that step, or ask our team to confirm whether it applies to you. 🛠️ Troubleshooting Common Issues - My site does not appear in the list: confirm you are signed in with the correct Google account and that the property is verified in GSC. - The connection fails: check that the address matches your GSC property exactly, including https://, www, and the trailing slash. - No data is showing: new connections can take some time to sync. Newly added GSC properties may also need several days before Google has data to share. - I am not sure whether I use Cloudflare: check with your web developer or hosting provider before creating a new account, because a second account can cause confusion. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔗 How Long Link Laboratory Orders Stay In Progress

🔍 What "In Progress" Means When you submit an order in Link Laboratory, it moves through several stages. In Progress means your order was received and is being worked on. A publisher or our fulfillment team is reviewing, preparing, or placing your link. It does not mean the order is stuck or has been missed. The status changes to a completed status once your link is live and the order is finished. ⏱️ How Long Does an Order Stay In Progress? There is no single timeframe that applies to every order. The time an order stays In Progress depends on the type of placement you ordered and the site where it will be published. Some placements are quick, while others need more steps, such as content creation, editorial review, and publisher approval. The most reliable way to know what to expect is to check the estimated turnaround time shown for your specific order or listing in Link Laboratory. This is the timeframe your order should be measured against. 📌 What Affects the Timeline Several factors can make one order finish faster than another: - Publisher review time: Some sites approve content within a day or two, while others take longer. - Content requirements: Orders that need new content written take longer than orders using content you already provided. - Editorial feedback: If a publisher asks for edits, the order stays In Progress until the changes are made and approved. - Order volume: Busy periods can add extra processing time. - Weekends and holidays: Publishers and teams may not work on these days, so turnaround is often counted in business days. - Order details: Missing or unclear information, such as the target URL or anchor text, can slow things down. 🧮 How to Estimate When Your Order Should Finish Follow these steps to work out whether your order is still within the expected window: 1. Open Link Laboratory in your Search Atlas account and go to your orders. 2. Find the order and note the submission date. For example, if you submitted the order on Sep 20, count from that date. 3. Check the estimated turnaround time listed for that order or placement. 4. Add that turnaround to your submission date, counting business days if the turnaround is given in business days. 5. Compare the result with today's date. If today is before that date, your order is still within the normal window. ✅ What You Can Do While You Wait - Check your order details to make sure all required information is complete and correct. - Watch for notifications in the platform. If the team or publisher needs something from you, you will see it there. - Avoid resubmitting the same order. A duplicate can cause confusion and may delay the original. - Allow extra time if your order falls over a weekend or holiday period. 🚩 When to Contact Support It's a good idea to reach out if: - Your order has stayed In Progress longer than the estimated turnaround time shown for it. - The status hasn't changed and you haven't received any update from the team. - You think something is wrong with the order details, such as the wrong URL or anchor text. To help us look into it quickly, have these details ready: - The order name or ID - The submission date (for example, Sep 20) - The target URL and the placement you ordered - A short description of what you're seeing 💬 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 instantly connected with a member of our team. 💡 Quick Summary - In Progress means your order is being actively worked on. - Timelines vary by publisher, placement type, and content needs. - Check the estimated turnaround for your order and count from your submission date. - If your order goes past that estimate, contact us through the chat widget with your order details.

🔍 How to Find Publication Orders for New Websites

📌 Overview When you add a new website to your Search Atlas account, it is set up as its own project. Publication orders are linked to the specific website they were placed for, so an order for one domain will not appear under another. This article explains where to look for the first order on a newly added website and what to check if you cannot see it. ❓ Why You May Not See an Order Yet Customers who add a new website often ask where their first order is. These are the most common reasons it is not visible: - You are viewing a different website. Orders are shown per website, so the order list may be filtered to another domain in your account. - No order has been placed yet. Adding a website does not automatically create a publication order. An order is created only after one is placed or started for that site. - The order is still being processed. Newly placed orders can take some time to appear with an active status. - You are in a different account or workspace. If you manage more than one account, the order may sit under the one it was placed in. 🧭 Step-by-Step: Locate Your Order 1. Log in to your Search Atlas account. 2. Use the website or project selector to choose the newly added domain. Make sure the domain name shown matches the site you are looking for. 3. Open the section of the platform where your publications or orders are listed for that website. 4. Check any filters, such as status or date range, and clear them so all orders are visible. 5. Look for the order by date, status, or order number. If you have a confirmation message, compare the details against the list. 6. Repeat these steps for each newly added website, since every domain has its own order list. 📋 Understanding Order Statuses Once you find an order, its status tells you where it is in the process. Common stages include: - Pending: The order has been received and is waiting to begin. - In progress: Work on the order has started. - Published: The content or placement is live. - Completed: The order is finished and any final details are available to review. If your order is still pending, give it a little time before assuming something is wrong. Processing times can vary depending on the type of order. 🔄 Multiple Websites in One Account If you have added several websites, such as two or more new domains at once, keep these tips in mind: - Check each website separately. An order for one domain does not appear under another. - Confirm each domain was added correctly, with no typos in the name. - Keep track of which website each order was meant for, especially if you placed the orders around the same time. - If an order was placed for the wrong website, let our team know so we can help. ✅ Quick Checklist Before Contacting Support - I selected the correct website in the platform. - I cleared all filters on the order list. - I checked whether an order was actually placed for this website. - I confirmed I am logged in to the right account or workspace. - I waited a reasonable time after placing the order. 💬 What to Share When You Need Help If you have gone through the steps above and still cannot find your order, our team can look into it for you. To speed things up, have these details ready: - The exact domain name of each website you added. - The approximate date you added the site or placed the order. - The type of order you expected, such as a content publication. - Any order number or confirmation message you received. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 💡 Tips to Avoid This Issue in the Future - After adding a website, confirm it appears in your website selector before placing an order. - Save your order confirmation so you can refer to it later. - Check the order list soon after placing an order to confirm it was recorded. - When managing several domains, switch to the correct site before opening your orders.

🔍 WooCommerce Index Checkbox and Bulk Indexing Guide

On a WooCommerce product page, the Search Atlas plugin section includes a checkbox labeled Index - Allow search engines to index this page. This article explains what it does, when to keep it checked, and how to handle many products at once. ✅ What the Index Checkbox Does The Index checkbox tells search engines whether a page may appear in search results. - Checked: Search engines are allowed to index the page, so it can appear in results such as Google. - Unchecked: The page is marked as "noindex", which asks search engines to keep it out of search results. Unchecking the box does not delete or hide the page. Visitors can still reach it with a direct link. It only affects search engine visibility. 🤔 Should the Box Be Checked? For most product pages you want customers to find through search, yes, keep it checked. If a product page is unchecked, it generally will not bring in organic search traffic. Good candidates to keep checked: - Active product pages you want to rank - Product category pages with useful, unique content - Blog posts and landing pages that support your store Pages you may want to leave unchecked: - Cart, checkout, and My Account pages - Thank-you or order confirmation pages - Duplicate, test, or placeholder products - Discontinued products you do not want showing in search 🛒 How to Check or Change the Setting on One Product 1. In your WordPress dashboard, go to Products and open the product you want to edit. 2. Scroll down to the Search Atlas section on the product edit screen. 3. Check or uncheck Index - Allow search engines to index this page. 4. Click Update to save your changes. If you use a page builder or caching plugin, clear your site cache after saving so the change shows up on the live page. ⚡ Turning On Indexing for Many Products If you have a lot of products, opening each one is slow. Here are the best ways to handle it: - Check the Search Atlas plugin settings first. Look for site-wide or default indexing options for products and other content types. Setting a default there is usually the fastest approach. - Try WordPress bulk edit. On the Products list, you can select several products and choose Bulk Edit. Fields added by plugins do not always appear there, so if the Index option is not shown, this method will not work for this setting. - Ask our team about a bulk update. If you do not see a bulk option and you have many products, our team can tell you the best way to apply the change across your store. Before applying any bulk change, decide which pages should stay unchecked, such as cart and checkout, so you do not index them by accident. 🔎 How to Confirm a Page Is Allowed to Be Indexed 1. Open the product page on your live site. 2. Right-click the page and choose View Page Source. 3. Search for the word noindex. 4. If you find it, the page is still set to stay out of search results. If you do not, the page is allowed to be indexed. You can also use the URL Inspection tool in Google Search Console to see how Google views a specific page. ⏳ Why a Checked Page May Still Not Appear in Search Checking the Index box allows indexing, but it does not guarantee it. Search engines still decide whether and when to include a page. Common reasons a page is not showing yet: - It is new. It can take days or weeks for search engines to discover and index a page. - WordPress is discouraging indexing site-wide. In WordPress, go to Settings and then Reading, and make sure "Discourage search engines from indexing this site" is not checked. - Another plugin or setting is adding noindex. SEO or security plugins may override page-level settings. - The page is blocked elsewhere. A robots.txt rule or password protection can keep search engines out. - The content is thin or duplicated. Search engines may skip pages with little unique value. 💡 Best Practices - Keep the Index box checked for every product and category page you want to earn traffic. - Leave utility pages like cart and checkout unchecked. - Review the setting after importing products or changing themes, since defaults can change. - Recheck a few key pages after any bulk change. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔄 Verify Site Connection and Sync WordPress Pages

🔍 Overview Two questions come up often: Is my website connected to Search Atlas? and When I publish a new page in WordPress, do I have to sync it manually? This article explains how to check your connection and what to expect when you add new pages. ✅ How to Check Whether Your Site Is Connected Use these quick checks to confirm that your domain is connected to OTTO. 1. Log in to your Search Atlas account. 2. Open the project or site selector and look for your domain in the list. If it appears, a project exists for it. 3. Open the OTTO section for that project and check the connection or installation status. An active, connected status means OTTO can see your site. 4. Confirm that pages from your site are listed in the OTTO page or URL view. If you see your pages there, the connection is working. If your domain is missing, or the status shows as not connected, not detected, or pending, follow the steps in the next section. 🛠️ What to Do If Your Site Is Not Connected - Check the domain: Make sure the project uses the exact version of your domain that your site loads on, including www or non-www and https. - Re-run the setup: Open the OTTO setup for your project and follow the connection steps for WordPress again. - Clear your caching: If you use a caching plugin or a CDN, clear the cache after installing or updating the connection. Old cached pages can hide the change. - Check for conflicts: Security plugins and firewalls can sometimes block the connection. Temporarily review their settings if the status does not update. - Refresh the status: After making changes, wait a few minutes and reload the OTTO page to see the updated status. 🔄 Do New WordPress Pages Sync Automatically? In most cases, you do not need to do anything. Once your WordPress site is connected, OTTO discovers new pages by scanning your site. When you publish a new page directly in WordPress, it should show up in your dashboard after OTTO's next scan. Keep these points in mind: - Published pages only: Drafts, private pages, and pages hidden from search engines may not appear. - Allow some time: New pages may not appear instantly. Give it some time before you assume something is wrong. - Pages must be reachable: The page needs to load publicly, without a login or password, and should be linked from somewhere on your site, such as your menu or sitemap. 📥 How to Make a New Page Show Up Faster 1. Publish the page in WordPress and open its live URL in a private browser window to confirm it loads. 2. Make sure the page is included in your XML sitemap. Most SEO plugins add new pages automatically. 3. Clear your site cache so the live version of the page is visible. 4. Return to the OTTO page list in Search Atlas and refresh. If your project has a rescan, refresh, or sync option, use it. 5. Check again after some time. If the page is still missing, move on to the troubleshooting section. ⚠️ Troubleshooting: A New Page Is Not Appearing - Check the page status: Confirm it is set to Published, not Draft, Pending, or Private. - Check the noindex setting: If your SEO plugin has the page set to noindex, it may be excluded. - Check the URL: Make sure you are looking for the correct address, since a changed permalink creates a different URL. - Check the connection: Go back to the connection checks above and make sure the status is still active, especially after a theme change, plugin update, or site migration. - Check redirects: If the page redirects to another address, OTTO may list the final destination instead. 💡 Best Practices - Re-check your connection status after major site changes, such as a new theme, a migration, or a change of caching or security plugins. - Keep your sitemap enabled and up to date. - Link new pages from other pages on your site so they are easy to find. - Review your OTTO page list after publishing so you can start optimizing new pages quickly. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Find the Correct OTTO UUID for Shopify

📌 What Is an OTTO UUID? A UUID is a unique ID that links your website to your OTTO project in Search Atlas. It is a long string of letters and numbers separated by dashes, for example: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Every OTTO project has its own UUID. If the UUID on your Shopify store does not match the one for that project, Search Atlas cannot verify the install. It shows "Wrong UUID" or "Your script is using the wrong UUID," and in the newer install flow it says it found an old OTTO code that belongs to another project. ⚠️ Why You See the Wrong UUID Error This error usually has a simple cause. The most common ones are: - Copied from the wrong project: If you manage more than one website or store, you may have copied the UUID from a different OTTO project. - Copied from an old install: You may have reused a UUID from a previous setup, a test project, or a deleted project. - Extra spaces or missing characters: A space at the start or end, or a missing character, makes the UUID invalid. - Different store domain: Creating the OTTO project for a different domain than your Shopify store, such as a myshopify.com address instead of your live custom domain, does not by itself make the UUID wrong. The UUID must still match this project. A script hosted on the wrong Search Atlas or white-label domain is reported separately as "Wrong Domain." - Old code left in place: A previous OTTO snippet is still in your theme alongside the new one. 🔍 How to Find Your Correct UUID 1. Log in to your Search Atlas account. 2. Open OTTO SEO and select the project for the Shopify store you want to install on. Check that the project name and domain match your store exactly. 3. Open the install or setup instructions for that project and choose Shopify as your platform. 4. Find the UUID shown in the install instructions or in the install code for that project. 5. Use the copy button to copy the full OTTO script shown for that project. If you copy the UUID out of it by hand, select the whole string with no spaces before or after it. Tip: Always copy the UUID directly from the project you are installing on. Do not reuse one from an email, a note, or another store. 🛠️ How to Install the UUID on Shopify Follow the install instructions shown in your OTTO project. If they ask you to add the OTTO code to your Shopify theme, these are the general steps: 1. In your Shopify admin, go to Online Store and then Themes. 2. Next to your live theme, click the three-dot menu and choose Edit code. 3. Open the theme file your OTTO instructions point to (usually the main theme layout file). 4. Check whether an older OTTO snippet is already there. If so, remove it so only one OTTO snippet remains. 5. Paste the new code exactly as shown in your project, with your correct UUID inside it. 6. Click Save. Make sure you are editing your live theme. If the code is in an unpublished or duplicate theme, OTTO will not detect it on your store. ✅ How to Check That the UUID Is Correct - Compare the UUID in your Shopify theme with the UUID in your OTTO project, character by character, or paste both into a text editor to compare them side by side. - Confirm there are no leading or trailing spaces and no extra quotation marks or characters. - Confirm the OTTO project domain matches the store domain customers see. - Return to the OTTO install page and run the install check again. Allow a few minutes after saving, as changes may take time to appear. 🔄 If You Manage Multiple Stores Each store needs its own OTTO project and its own UUID. Never use one store's UUID on another store. Before you install, double-check the project name and domain at the top of the install page, and keep a simple list of which UUID belongs to which store. 🧰 Still Seeing the Error? Work through this quick checklist: - Did you copy the UUID from the correct project? - Is the code saved in your live Shopify theme? - Is there only one OTTO snippet in the theme? - Does the UUID have no extra spaces or missing characters? - Have you waited a few minutes and cleared your browser cache before rechecking? If you have checked all of these and the error remains, it may be a mismatch we need to look at on our side, such as a project created under a different domain. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve it faster, tell us your store domain and the name of the OTTO project you are installing on.

🔗 Connect GSC to an OTTO Shopify Subdomain Project

🔍 Overview A Shopify store can run on a subdomain, such as store.yourdomain.com, while the main website uses yourdomain.com. If you manage them as separate OTTO projects, check that the GSC property you connect covers the intended website and is available in your Search Atlas account. 🤔 Why This Happens Google Search Console supports Domain properties, which include subdomains, and URL-prefix properties, which cover a particular protocol, hostname, and optional path. Choose a property that covers your OTTO project's address. Evidence: Google’s property documentation. - A project for store.yourdomain.com needs a GSC property that covers that subdomain. - A root-domain URL-prefix property does not cover your store subdomain. A root Domain property does cover it, but Search Atlas's automatic matching may not select that property for a subdomain project. A property already connected elsewhere is not, by itself, evidence that it cannot be selected. - If no accessible GSC property covers the subdomain, create one or request access to an existing property. A parent Domain property may already provide coverage even if you have never added a separate subdomain property. - Connect a Google account with access to the property. Ownership is not required simply for the property to be listed; users with other supported access levels can also see it. 📋 Understanding GSC Property Types GSC offers two types of properties. Knowing the difference makes it easier to choose the right one. - Domain property: Appears as yourdomain.com and covers the root domain plus all subdomains, with both http and https. It requires DNS verification. - URL-prefix property: Appears as a full address, such as https://store.yourdomain.com/, and covers URLs beginning with that prefix, including pages beneath it. Other protocols and hostnames are excluded. Verification options include an HTML tag or file, where supported by your hosting platform. A URL-prefix property such as https://store.yourdomain.com/ provides reporting scoped to that HTTPS subdomain. Search Atlas's automatic matching looks for the project hostname in active property URLs, so a property explicitly containing the subdomain can help it find a match. Evidence: gsc/app/searchconsole/api/v2/views.py:4162–4167. 🛠️ Step 1: Check Whether the Subdomain Exists in GSC 1. Sign in to Google Search Console with the same Google account you plan to connect to Search Atlas. 2. Open the property drop-down at the top left. 3. Look for https://store.yourdomain.com/ in the list. 4. If the subdomain property is already available and verified, continue to connecting it in Search Atlas. Otherwise, add and verify the property using the following instructions. ➕ Step 2: Add and Verify the Subdomain Property 1. In the GSC property drop-down, click Add property. 2. Choose URL prefix and enter the full subdomain address, for example https://store.yourdomain.com/. Make sure the address matches your live store exactly, including https. 3. Follow the verification method Google suggests. Common options include adding a DNS record at your domain provider or adding an HTML tag to your Shopify theme. 4. Click Verify. Once Google confirms ownership, the property is ready to use. If using HTML-tag verification, add Google's verification meta tag inside the head element of the live Shopify theme, typically in layout/theme.liquid, and save your changes before verifying. If using DNS verification, allow time for the record to propagate before retrying. Keep the verification tag or DNS record in place after verification. 🔗 Step 3: Connect the Property in Search Atlas 1. Open your Shopify subdomain project in Search Atlas. If you have not created it yet, add a new OTTO project using the full subdomain address, such as store.yourdomain.com. 2. Go to the GSC connection step in the project settings or setup. 3. Sign in with the Google account that owns the subdomain property. 4. Select the subdomain property (for example, https://store.yourdomain.com/) from the list. 5. Save your selection and confirm the connection shows as active. ⚠️ Common Issues and Fixes - The root domain is not selectable: This is expected if the root domain is already connected to another project or does not match the subdomain project. Select the subdomain property instead. - The subdomain property is missing from the list: Add and verify it in GSC (Step 2), then disconnect and reconnect your Google account in Search Atlas to refresh the list. - The wrong Google account is connected: Sign out of Google, then reconnect using the account that owns the property. - Your account has restricted access: Make sure your Google account is a verified owner of the property, not just a user with limited permissions. - Verification keeps failing: Double-check that the address matches your live store, including https and any trailing slash, and that the DNS record or HTML tag was added correctly. - No data appears right after connecting: A newly added GSC property takes time to collect data. Check back after a few days. 💡 Best Practices - Use one GSC property per OTTO project so your data stays organized. - Keep the root domain project and the subdomain project connected to their own matching properties. - Always enter the subdomain exactly as it appears in your browser when your store loads. - Keep the verification record or tag in place. Removing it can disconnect your property from GSC. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔄 Switching From GHL to Vercel in Search Atlas

🔍 Overview If you moved your website from GoHighLevel (GHL) to Vercel, your Search Atlas project still points to the old setup until you update it. This guide shows you how to disconnect the GHL integration, connect your site on Vercel, and make sure OTTO and your CMS connection work on the new site. The process takes about 10 to 20 minutes. Allow extra time if you need to change files in your website code. 📝 Before You Start Have the following ready so the switch goes smoothly: - Your live Vercel site URL. Use the final domain (for example, yourdomain.com), not a temporary preview link. - Access to your Vercel account and the project that hosts your site. - Admin access to your Search Atlas project. - Confirmation that your domain now points to Vercel. If your domain still loads the old GHL site, finish the domain change first. Tip: Keep your old GHL account active until the new site is confirmed working. That way you can compare pages if something looks different. 🔌 Step 1: Disconnect the GHL Integration Remove the old connection first so Search Atlas does not try to publish or optimize through GHL. 1. Log in to Search Atlas and open the project for your website. 2. Go to the project's integrations or CMS connection settings. 3. Find the GoHighLevel (GHL) connection in the list. 4. Select the option to disconnect or remove it, then confirm. 5. Refresh the page and check that GHL no longer appears as an active connection. Disconnecting does not delete your Search Atlas project, keyword data, or reports. It only stops the link to GHL. 🚀 Step 2: Connect Your Vercel Site Next, connect the website that now lives on Vercel. 1. In the same integrations or CMS connection area, choose to add a new connection. 2. Select Vercel from the list of platforms. If Vercel is not listed, choose the option for a custom or other website setup and follow the instructions shown. 3. Enter your live website URL exactly as it appears in the browser. 4. Follow the on-screen prompts to authorize Search Atlas. You may be asked to log in to Vercel and approve access to the project that hosts your site. 5. Save the connection and wait for the status to show as connected. If your project has more than one domain, such as a www and a non-www version, use the main version your visitors see. ⚙️ Step 3: Set Up OTTO on the New Site OTTO needs to be active on your Vercel site to apply SEO updates. Your old GHL setup does not carry over automatically. 1. Open OTTO SEO inside your Search Atlas project. 2. Check the installation status for your site. If it shows as not installed or not detected, follow the install instructions shown for your site. 3. If the instructions include a script or code snippet, add it to your Vercel project as directed, then redeploy the site so the change goes live. 4. Return to OTTO and select the option to re-check or verify the installation. Important: If you previously added an OTTO snippet to your GHL site's tracking code or header, do not copy it over unless the new instructions tell you to. Using an outdated snippet can stop OTTO from working properly or cause duplicate changes. ✅ Step 4: Confirm Everything Works Run through this quick checklist: - The Vercel connection shows as connected in your Search Atlas project. - The GHL connection is removed. - OTTO shows your site as installed or active. - Your site loads correctly on your main domain. - A page you expect OTTO to update shows the change after it is published and the page is refreshed. Changes can take a few minutes to appear. If you use caching or a CDN, the update may take a little longer. 🛠️ Troubleshooting Common Issues - Vercel will not connect. Check that you are logged in to the correct Vercel account and that you have permission to access the project. Team projects may require an owner or admin to approve access. - The URL is not accepted. Use the full live domain without extra paths. Make sure it loads in your browser without errors. - OTTO still shows as not installed. Make sure you redeployed your Vercel project after adding any code. Then clear your cache and run the verification again. - Changes are not showing on the site. Wait a few minutes, hard refresh the page, and check that you are viewing the live domain instead of a preview link. - Old GHL data still appears. Confirm that your domain points to Vercel and no longer to GHL. DNS changes can take time to spread. - Page content looks different after the move. If titles, descriptions, or URLs changed during migration, rerun a site audit in Search Atlas to catch new issues. 💡 Best Practices After Migrating - Keep your URLs the same where possible. If any changed, set up redirects in Vercel so you do not lose rankings. - Submit your sitemap again in Google Search Console after the move. - Run a fresh site audit in Search Atlas to check for broken links, missing tags, and other issues. - Monitor rankings for a few weeks so you can spot and fix any drops early. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To help us resolve your request faster, mention your domain name and which step you got stuck on.

🔌 Connecting a Sanity Headless CMS Site to Search Atlas

🔍 Quick Answer Sanity is a headless CMS. It stores and manages your content but does not build or host the pages visitors see. Your website's front end (often built with Next.js, Nuxt, Astro, Gatsby, or similar) does that. Because of this, Search Atlas works with the live website your Sanity content powers, rather than with the Sanity Studio itself. Sanity sites are usually set up differently from Webflow, and the experience is not identical. The sections below explain what that means in practice. 🧩 How Sanity Differs From Webflow Webflow is an all-in-one platform, so one connection can reach your content, page settings, and published pages. A headless setup splits these into separate parts: - Sanity holds your content (text, images, fields). - Your front-end code decides how that content becomes HTML pages, including title tags, meta descriptions, schema, and links. - Your hosting provider (such as Vercel or Netlify) serves the finished pages to visitors. Search Atlas can only change what it can reach. On a headless site, many SEO elements are controlled by your front-end code, so some changes may need a developer's help. ⚖️ What to Expect Compared to Webflow - Site audits, rank tracking, keyword research, and reporting: These rely on your public website, so they work the same way whether your site runs on Sanity, Webflow, or anything else once your domain is added to a project. - On-page optimization with OTTO SEO: This depends on how OTTO is installed on your site. Headless sites usually need the installation done on the front end, so a developer is typically involved. - Direct publishing or editing of CMS content: Do not assume this works the way it does with Webflow. Content stored inside Sanity is generally edited in Sanity Studio, so content created in Search Atlas may need to be copied into Sanity manually or through your developer's own workflow. - One-click connection: Sanity is not a Search Atlas CMS connector. CMS Connectors (Settings, CMS Connectors) covers platforms such as WordPress, Webflow, Shopify, and Contentful, and Sanity is not one of them. There is no one-click Sanity connection. In short, you can get most of the research, monitoring, and analysis value from Search Atlas with a Sanity site. Automated on-site changes and publishing depend on your front-end setup. 🛠️ How to Get Started 1. Log in to Search Atlas and create a new project for your website using your live domain (for example, www.yoursite.com), not your Sanity Studio URL. 2. Open Settings, then CMS Connectors, and review the platforms offered. Sanity is not listed. Do not expect a custom or non-listed website option there. To use OTTO on the live site, install the OTTO pixel instead. 3. Follow the on-screen instructions. For OTTO SEO, this usually means adding a provided code snippet or setting to your site so it can apply optimizations. 4. Share the instructions with your developer. They will typically add the snippet in your front-end project's global layout or head section, then deploy the site. 5. Return to Search Atlas and confirm the OTTO pixel is detected on the live domain. 6. Wait for the first crawl or audit to finish, then review the results in your project dashboard. ✅ Tips for a Smooth Setup - Use the exact public URL your visitors see, including the correct www or non-www version. - Make sure your site is published and not password-protected or blocked from crawlers while Search Atlas scans it. - If your site uses server-side rendering or static generation, redeploy after adding any code so the change goes live. - Test in a staging environment first if your team uses one. - Keep a note of which SEO fields (titles, descriptions, schema) are stored in Sanity and which are set in code. This helps you decide where each recommendation should be applied. 🧯 Troubleshooting - Connection will not verify: Confirm the snippet is on the live site (not just in a local or preview build) and that your latest deployment has finished. - Changes do not appear on the page: Your hosting provider may be caching older pages. Clear the cache or trigger a fresh deployment, then check again. - Recommendations do not match what is in Sanity: Search Atlas reads the final page. If a field is overridden in your front-end code, update it in the code or the matching Sanity field. - Audit shows missing pages: Check that your sitemap is up to date and that pages are not blocked by robots settings. 💬 Need Help? Every Sanity project is built a little differently, so a quick conversation can save time. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🚫 Why Your Website Was Rejected in Publication Media

📌 Overview If you see a Rejected status next to your website in the Publication Media dashboard, it means the site did not pass our review for publication placements. This is usually fixable. This article explains the most common reasons for a rejection, how to check what applies to your site, and what to do next. ❓ What Does 'Rejected' Mean? Publication Media sites are reviewed before they can be used for content placements. A rejection means the site did not meet one or more quality or eligibility requirements at the time of review. It does not necessarily mean your site is bad. It may mean something needs to be corrected, completed, or improved before it can be approved. Note: Requirements can change over time and may vary by publication type or category. The reasons below are the most common ones, but your dashboard is the best place to see what applies to your specific site. 🔎 Common Reasons a Website Is Rejected - Low-quality or thin content: The site has very few pages, mostly short posts, or content that looks copied, auto-generated, or unfinished. - Limited or no organic traffic: The site has little to no visible search traffic, which makes it harder to deliver value to advertisers or content partners. - Site not indexed or hard to crawl: Search engines cannot find or read the site's pages. This can happen if the site is blocked by a robots.txt file, a noindex tag, or a password page. - Site not accessible: The website is down, loads very slowly, shows errors, or is still under construction or showing a 'coming soon' page. - Spammy or risky signals: The site has excessive ads, suspicious outbound links, many pop-ups, or signs of a past penalty or hacked content. - Restricted or unsupported topics: The site focuses on topics that are not accepted for placements, such as adult content, gambling, or other restricted categories. - Not enough niche focus: The site covers too many unrelated topics, so it is not a clear fit for any single category. - Incomplete or inconsistent details: The submitted information is missing, mistyped, or does not match the live site, such as the wrong domain, language, or category. - Duplicate submission: The same domain was already submitted or already exists in the system. - Missing trust pages: The site lacks basic pages such as About, Contact, or Privacy Policy, which signal that it is a real, maintained website. 🛠️ How to Find Out Why Your Site Was Rejected 1. Open the Publication Media dashboard in the platform. 2. Find the website with the Rejected status. 3. Look for any note, label, or message shown next to the status. It may explain which requirement was not met. 4. Open your website in a browser and check the points listed in the section above. 5. Write down the domain name, the date you submitted it, and take a screenshot of the status. This will help if you need to contact us. ✅ Quick Self-Check Before You Resubmit - Your website loads quickly and without errors on desktop and mobile. - Your key pages are visible to search engines, with no accidental noindex tag or blocked crawling. - Your site has several pages of original, useful content on a clear topic. - Your site has About, Contact, and Privacy Policy pages. - You have removed any spammy ads, pop-ups, or low-quality outbound links. - The domain, language, and category you submitted match your live site. - Your site is not already listed under another submission. 🔁 How to Resubmit After Fixing Issues 1. Fix the items you identified in the checklist above. 2. Wait for your changes to go live and, if you changed indexing settings, give search engines some time to pick them up. 3. Return to the Publication Media dashboard and check whether a resubmit or re-review option is available for your site. 4. If it is not available, submit the corrected site again with accurate details. 5. Check the status again after the review period. 💡 Tips to Improve Your Chances of Approval - Publish consistently: Regularly updated sites look more trustworthy and active. - Stay focused: A site with a clear niche is easier to categorize and approve. - Build real visibility: Improve your content and SEO basics so your site can earn organic traffic over time. - Keep details accurate: Make sure the information in your submission matches your live site exactly. 💬 Still Not Sure Why It Was Rejected? If your dashboard does not show a clear reason, or you have fixed the issues and the site is still rejected, our team can look into it with you. Have your domain name, submission date, and a screenshot of the rejected status ready so we can help faster. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔐 Google Workspace OAuth Client ID for Digital PR

🔍 Overview Digital PR connects to your Google mailbox through Google sign-in (OAuth) so you can send and manage outreach emails from Search Atlas. If your company uses Google Workspace, your administrator may have blocked third-party apps by default. In that case, the connection fails until the admin marks the Search Atlas app as trusted. Admins often ask for the exact OAuth Client ID so they can trust the correct app. This article explains how to find that ID, how to trust it, and how to fix common errors. 🆔 About the Search Atlas OAuth Client ID The Client ID is a unique identifier Google assigns to an app. Because it is a security-sensitive setting, you should always confirm it with our team rather than copy it from an unofficial source. A Search Atlas teammate can give you the verified Client ID for the Digital PR email integration through live chat (see the last section). You can also see the Client ID in your own Google Workspace records. The next section shows you how. 🧭 How to Find the Client ID in Google Workspace If a user has already tried to connect their mailbox and was blocked, Google records the attempt. A Workspace admin can find the Client ID this way: 1. Sign in to the Google Admin console as a super admin. 2. Go to Reporting, then Audit and investigation, then OAuth log events. 3. Filter by the user who tried to connect, or by the app name Search Atlas. 4. Open the matching event and note the Client ID and the app name shown. Menu names can change slightly over time. If you can't find these options, search the Admin console for OAuth log events. ✅ How to Trust the App in Google Workspace Once you have the Client ID, follow these steps: 1. Sign in to the Google Admin console as a super admin. 2. Go to Security, then Access and data control, then API controls. 3. Select Manage Third-Party App Access. 4. Click Configure new app, then choose OAuth App Name Or Client ID. 5. Paste the Client ID provided by Search Atlas and click Search. 6. Select the matching app and click Select. 7. Choose the organizational units or groups that should be able to use the app. Choose the whole organization if you are unsure. 8. Set the access level to Trusted and confirm. Changes can take some time to apply. In some cases it can take up to 24 hours, though it is usually much faster. 🔄 Reconnect Your Mailbox in Search Atlas After the admin has trusted the app, the user should reconnect their email: 1. Sign in to Search Atlas and open Digital PR. 2. Open the email connection settings and choose to connect your Google account. 3. Sign in with your Workspace email address. 4. Review the permissions on Google's consent screen and click Allow. If you previously saw an error, sign out of other Google accounts or use a private browser window to avoid choosing the wrong account. 🛠️ Troubleshooting Common Issues - "App blocked" or "Access blocked" message: The app has not been trusted yet, or the setting has not finished applying. Check the app's access status in Manage Third-Party App Access and wait a little while. - Admin can't find the app by Client ID: Check that the ID was copied in full with no extra spaces. If the app still doesn't appear, the ID may be incorrect, so ask our team to confirm it. - Trusted, but still blocked for some users: The app may be configured only for certain organizational units or groups. Make sure the affected user belongs to one of them. - Wrong account selected: Make sure the user signs in with the Workspace email they want to send from. - Permissions were declined: Reconnect and allow all requested permissions. Digital PR can't send or track outreach without them. 💡 Tips for IT Administrators - Verify the Client ID and app name in the OAuth log before you trust anything. - Limit access to the teams that need Digital PR if your policy requires it. - Review third-party app access periodically as part of your security checks. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. To speed things up, tell us that you need the Digital PR OAuth Client ID for Google Workspace, and include any error message you see.