Troubleshooting: WordPress Plugin Issues

🛠️ Fix WordPress CMS Sync Failures with AIOSEO

🛠️ How to Fix WordPress Blog Display After Plugin Conflict

🛠️ Fix Search Atlas & Rank Math Meta Tag Conflicts

🛠️ MetaSync/OTTO Plugin CPU Exhaustion Incident Guide

🛠️ Fix OTTO and Rank Math Meta Conflicts

🔌 Disable OTTO Dynamic SEO in WordPress Plugin

🔧 How to Fix a Fatal WordPress Plugin Conflict

🔧 Fix WordPress MetaSync Sync Issues

🔎 Understand the issue If MetaSync is not detected or your site is not syncing, confirm that MetaSync is installed and active on your WordPress site. ✅ Check MetaSync 1. Open your WordPress admin dashboard. 2. Go to your installed plugins. 3. Find MetaSync and confirm that it is installed and active. 🚀 Use the OTTO script instead If MetaSync is not detected or cannot be installed, use the OTTO script as an alternative connection method. 1. Open the OTTO installation instructions in Search Atlas. 2. Copy the OTTO script provided for your site. 3. Add the script to your WordPress site as instructed. 4. Save the changes and check whether your site is detected. If the issue continues, confirm that the script was added correctly and that the site is still accessible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 WP OTTO Plugin Import Feature Unavailable

🔍 Overview After installing the WP OTTO plugin on your WordPress site, you may see a message indicating that the import feature is unavailable. This article explains what to do when this occurs. ✅ What You Can Do The import feature cannot be used while it is unavailable. Do not rely on the import process until the issue is resolved. If you contact support, have your WordPress site details, the exact message shown, and the time the issue occurred ready so the team can investigate the plugin 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.

🔌 Fix WordPress OTTO Connection and Authentication Issues

🔍 Overview If your WordPress site is not connecting or authenticating with OTTO SEO, this guide walks you through the correct installation process, common causes of failure, and how to verify a successful connection. 📋 Before You Begin Make sure you have the following ready before starting: - An active Search Atlas account with OTTO SEO access - Administrator access to your WordPress site - The Search Atlas OTTO SEO plugin installed on your WordPress site 🛠️ Step 1 — Install the OTTO SEO WordPress Plugin 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Add New and search for Search Atlas OTTO SEO. 3. Click Install Now, then click Activate. Important: The plugin does nothing on its own. It must be connected to an active Search Atlas account to function. Activating the plugin without completing the connection steps below will result in no data being processed. 🔗 Step 2 — Connect Your WordPress Site in Search Atlas 1. In Search Atlas, go to Left sidebar → OTTO SEO → Installation Guide for the full, up-to-date connection walkthrough. 2. If you are adding a new site, go to Left sidebar → OTTO SEO → All Sites and click Create. 3. When prompted to add a connector, select WordPress as your CMS type. 4. Follow the on-screen prompts to generate your unique connection credentials. 🔑 Step 3 — Authenticate the Plugin on Your WordPress Site 1. In your WordPress admin dashboard, navigate to the Search Atlas OTTO SEO plugin settings page. 2. Enter the connection credentials provided in the Search Atlas platform (from Step 2). 3. Click Save or Connect to submit your credentials. 4. Return to Search Atlas and go to Left sidebar → OTTO SEO → Overview. If the connection was successful, your site status will update and you can click Scan to begin processing. ⚠️ Common Reasons the Connection Fails - Incorrect credentials: Copy and paste the connection credentials directly from the Search Atlas platform — do not type them manually to avoid typos. - Plugin not activated: The plugin must be both installed and activated in WordPress before authentication can succeed. - Caching plugin interference: If your site uses a caching plugin (e.g., WP Rocket, W3 Total Cache), clear your cache after saving the plugin credentials and try again. - WordPress REST API blocked: Some security plugins or server configurations block the WordPress REST API. Check that the REST API is accessible, as OTTO uses it to communicate with your site. - User role permissions: Ensure the WordPress account used during setup has Administrator privileges. - Outdated plugin version: Go to Plugins → Installed Plugins in WordPress and confirm the OTTO SEO plugin is up to date. ✅ How to Verify a Successful Connection - Go to Left sidebar → OTTO SEO → Overview in Search Atlas. - Your site should appear with an active status and options to Scan or manage your OTTO deployment. - If the site still shows as disconnected after completing all steps, wait 2–3 minutes and refresh the page, as the pull-based connection check may take a moment to update. 💬 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.

🛠️ Fix WordPress Blog Changes Not Showing

🔍 Why changes may not appear Search Atlas may show a blog update as deployed while the live page still displays an older version. This usually happens because of page caching, a plugin or theme overriding the content, or the live URL differing from the page that was updated. ✅ Check the live page first 1. Open the published blog post URL in a private or incognito browser window. 2. Refresh the page and confirm that you are viewing the correct URL, including the preferred version of the domain. 3. View the page source or use your browser’s inspect tools to confirm whether the updated H1 and image are present in the HTML. If the change appears in the page source but not visually, the theme, CSS, or a page builder may be changing how the content is displayed. 🧹 Clear WordPress and site caches Clear all active cache layers, then test the page again. Check your WordPress caching plugin, hosting cache, CDN, and browser cache. If your site uses a CDN, purge the specific page or cache zone when possible instead of only refreshing your browser. 📝 Troubleshoot an H1 that does not update - Confirm the post has one visible H1 on the published page. - Check whether the theme generates the H1 from the post title instead of the edited content. - Review page-builder templates, custom fields, and theme settings that may replace the standard post heading. - Make sure the update was applied to the published post, not a draft, revision, or staging copy. - Check the live URL again after clearing caches. Some themes display a title outside the main post content. In that case, changing content inside the editor may not change the heading shown by the theme. 🖼️ Fix a duplicated featured image A duplicated image commonly appears when the theme automatically displays the featured image and the same image is also inserted at the top of the post content. - Remove the repeated image from the post body if the theme already displays the featured image. - Check theme or page-builder settings for an automatic featured-image block. - Review image blocks, reusable blocks, and custom fields that may add the same image again. - Clear caches and reload the published URL after saving the change. If the image is duplicated only on the live page, inspect the theme template or page-builder layout rather than adding another content edit. 🚀 Confirm deployment status 1. Open the relevant deployment or fix record in Search Atlas. 2. Confirm that the target WordPress site and exact post URL are correct. 3. Allow the deployment to finish before testing the page. 4. Verify the live page, rather than relying only on a successful deployment message. A successful deployment confirms that Search Atlas sent the change. It does not always mean that every cache, theme template, or WordPress output layer has refreshed. 💬 Get help If the live page still does not match the deployed change after checking the URL, caches, theme, and page builder, capture the page URL and the affected 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.

🛠️ Troubleshoot OTTO WordPress Connections

🔍 Check the connection status Start in OTTO SEO from the left sidebar, then open Installation Guide. Confirm that the WordPress site is connected to the correct Search Atlas project and that OTTO shows an active installation. If you manage several sites, open each affected project separately. A connection can succeed on one site while another has different WordPress permissions, plugins, caching, or configuration. ⚙️ Verify the WordPress setup 1. Confirm that the WordPress site is live and accessible without a maintenance or password-protection page. 2. Log in with an account that has administrator permissions. 3. Confirm the OTTO plugin is installed and activated on the intended WordPress site. 4. Make sure the site URL in WordPress matches the site added to Search Atlas, including HTTPS and the correct domain version. 5. Temporarily disable security, firewall, or maintenance settings that may block plugin requests, then test the connection again. 🔑 Refresh authentication If the connection remains unresolved, return to OTTO SEO → Installation Guide and restart the connection process. Use the current installation details generated for that project rather than reusing an older API key or setup link. Do not connect the same WordPress installation to a different project unless that is intentional. An old connection, API key, or project identifier can cause OTTO to appear installed while data is linked to another project. 🔄 Resolve syncing and caching issues - Clear WordPress, hosting, CDN, and browser caches. - Check whether a security plugin or hosting firewall is blocking REST API requests or outgoing connections. - Confirm that WordPress can communicate with external services and that the server is not blocking plugin requests. - Update WordPress and the OTTO plugin when updates are available. - After making changes, wait a few minutes and refresh the Installation Guide before testing again. 🧩 Check project and site matching When OTTO reports an unexpected installation state, verify that the WordPress site is connected to the intended Search Atlas project. This is especially important when projects were duplicated, renamed, migrated, or connected more than once. Review the affected project in Site Metrics from the left sidebar and confirm that the domain and project details match the WordPress site. Avoid repeatedly reinstalling OTTO until the project match is confirmed. 🚫 If the connection still fails 1. Disconnect or deactivate the existing OTTO installation only if the Installation Guide provides that option. 2. Remove obsolete OTTO plugin connections from the affected WordPress site. 3. Clear caches and reconnect using the Installation Guide for the correct project. 4. Test the site in an incognito browser window and confirm the OTTO status again. If several sites work but one or two do not, compare the affected sites with a working site. Focus on differences in WordPress administrator access, domain format, security plugins, hosting, caching, and project assignment. 💬 Get help from our team Before contacting support, note the affected project, WordPress site URL, connection status, recent changes, and any error message. Screenshots can also help identify 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.

🛠️ Fix WordPress OTTO Plugin Integration Errors

🔍 What This Article Covers If your Search Atlas WordPress plugin displays an 'OTTO not found' error during integration, this guide walks you through the most common causes and how to fix them quickly. Follow each section in order until the issue is resolved. ✅ Before You Begin: Prerequisites Make sure the following conditions are met before troubleshooting: - You have an active Search Atlas account with OTTO SEO enabled. - You have administrator access to your WordPress site. - Your WordPress version is 5.6 or higher. - The Search Atlas WordPress plugin is installed and activated. ⚙️ Step 1 — Verify OTTO Is Activated in Search Atlas The most common cause of the 'OTTO not found' error is that OTTO SEO has not been activated for your site inside the Search Atlas platform. 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 3. Confirm that your target website is listed and that OTTO has been activated for it. If you see a prompt to activate OTTO, complete that process first. 4. Once activated, return to your WordPress dashboard and retry the integration. 🔑 Step 2 — Check Your API Key Connection An incorrect or missing API key will prevent the plugin from locating your OTTO instance. 1. In your WordPress admin panel, go to Search Atlas → Settings. 2. Locate the API Key field and confirm it is not empty. 3. In Search Atlas, go to your account settings and copy your API key. 4. Paste the key into the WordPress plugin settings and click Save Changes. 5. After saving, click the Test Connection button (if available) to verify the link is successful. 🌐 Step 3 — Confirm Your Site URL Matches OTTO links to a specific domain. If the URL registered in Search Atlas does not exactly match your WordPress site URL, the integration will fail. - In Search Atlas under OTTO SEO V3, check the domain listed for your OTTO activation. - In WordPress, go to Settings → General and compare the WordPress Address (URL) and Site Address (URL) fields. - Both values must match the domain in Search Atlas exactly — including whether www is present and whether the site uses https. - If there is a mismatch, update the domain in Search Atlas or correct your WordPress URL, then retry. 🔄 Step 4 — Update or Reinstall the Plugin An outdated or corrupted plugin file can also trigger this error. 1. In WordPress, go to Plugins → Installed Plugins. 2. Check whether an update is available for the Search Atlas plugin. If so, update it now. 3. If no update is available and the error persists, deactivate and delete the plugin. 4. Get the latest Search Atlas plugin .zip from Search Atlas (the plugin is not listed in the WordPress plugin directory). 5. Reinstall and reactivate the plugin, then re-enter your API key and save. 🛡️ Step 5 — Check for Plugin or Firewall Conflicts Security plugins, caching tools, or server firewalls can block the API requests the plugin needs to communicate with Search Atlas. - Temporarily deactivate any security or firewall plugins (such as Wordfence or iThemes Security) and test the integration again. - Clear your site's cache using your caching plugin or hosting control panel, then retry. - If your hosting provider has a Web Application Firewall (WAF), ask them to whitelist outbound requests to the Search Atlas API domain. - Re-enable your security plugins once the integration is confirmed working. 💡 Quick Reference: Common Causes and Fixes - 'OTTO not found' error → OTTO is not activated in Search Atlas for that domain. Activate it under OTTO SEO V3 first. - Connection fails after entering API key → API key is incorrect or copied with extra spaces. Re-copy and paste carefully. - Integration works on staging but not production → The domain registered in Search Atlas does not match the live site URL. - Error returns after updating WordPress → Plugin may need updating to maintain compatibility. Check for a plugin update. 🆘 Still Seeing the Error? If you have followed all the steps above and the 'OTTO not found' error still appears, our support team can investigate your specific account 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 OTTO Plugin Errors and Missing Projects

🔍 Overview After installing the OTTO plugin on your website, you may encounter a few common issues: an 'otto not found' error, projects that seem to disappear from your Search Atlas dashboard, or no active projects appearing on the homepage. This article walks you through the most likely causes and how to resolve each one quickly. ⚙️ Step 1: Verify the OTTO Plugin Is Installed Correctly The 'otto not found' error almost always means the plugin was not fully activated or is not communicating with Search Atlas. Follow these steps to confirm your installation: 1. Log in to your WordPress admin panel and go to Plugins → Installed Plugins. 2. Confirm the OTTO SEO plugin is listed and its status shows Active. If it shows Inactive, click Activate. 3. If the plugin is not listed at all, reinstall it. Go to Plugins → Add New → Upload Plugin, upload the plugin .zip provided by Search Atlas, install it, and then activate it. 4. After activation, return to your Search Atlas dashboard and navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). Check whether your site now appears as a connected project. If the plugin is active but the error persists, deactivate it, wait 30 seconds, then reactivate it to force a fresh connection handshake. 🔑 Step 2: Reconnect Your Site With the Correct API Key A broken or missing API key is a common reason the plugin cannot locate your OTTO project. To check this: 1. In your WordPress admin panel, open Search Atlas → Settings. 2. Paste your Search Atlas API Key into the designated field. 3. Paste your OTTO Pixel UUID. 4. Click Save and refresh the page. The connection status should update to Connected. Make sure there are no extra spaces before or after the API key when pasting it — this is a frequent cause of authentication failures. 📊 Step 3: Restore Missing Projects in the Dashboard If your projects have disappeared from the Search Atlas web version, this is typically caused by one of the following: - Workspace mismatch: Confirm you are logged in to the correct workspace. Click your account name in the top-right corner and verify the active workspace matches the one where your projects were created. - Browser cache: Clear your browser cache and cookies, then hard-refresh the page (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac). - Session timeout: Log out of Search Atlas completely, log back in, and navigate to OTTO SEO → All Sites (SEO Automation) to see if your projects reload. Projects are tied to your workspace and account — they are never permanently deleted by a plugin installation. If they are not visible after the steps above, the issue is almost certainly a workspace or session problem. 🚀 Step 4: Confirm Active Projects Appear on the Homepage The Search Atlas homepage displays a summary of your active projects. If this section appears empty after setup: 1. Navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3) and confirm at least one project exists and has a status of Active. 2. If a project exists but shows a Pending or Disconnected status, complete the reconnection steps in Step 2 above. 3. Once a project is confirmed active, return to the homepage. Active projects should populate within a few seconds. If the page still appears empty, perform a hard-refresh. 🌐 Step 5: Trigger or Re-run a Site Audit Crawl After successfully connecting the plugin, you may need to manually trigger your first site audit crawl so Search Atlas can begin collecting data: 1. Go to OTTO SEO in the left sidebar, then open Site Audit → Overview (Website Overview). 2. Click Recrawl Site if a previous crawl appears stalled or incomplete. 3. Crawl times vary depending on site size. Small sites typically complete within a few minutes; larger sites may take longer. Do not close the tab while the crawl is in progress. Once complete, your audit data will be available inside the project dashboard. 💡 Quick Troubleshooting Checklist - Plugin active? Confirm in WordPress → Plugins → Installed Plugins. - API key correct? Re-paste at Search Atlas → Settings in WordPress — no extra spaces. - Right workspace? Check account switcher in top-right corner. - Browser cache cleared? Hard-refresh after clearing. - Crawl started? Manually trigger from OTTO SEO → Site Audit → Overview (Website Overview) using the Recrawl Site button. 🙋 Still Need Help? If you have followed all the steps above and are still experiencing issues, If you need further assistance, open 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 OTTO WordPress Plugin Sync Issues

Overview When OTTO SEO deploys fixes — such as schema markup, heading tag updates, or site audit recommendations — those changes are sometimes marked as Deployed inside Search Atlas but do not appear on your live WordPress site. This article explains the most common causes and what to do next. How OTTO Deploys Changes to WordPress OTTO SEO communicates with your WordPress site through the Search Atlas WordPress plugin. When you apply a fix inside OTTO, the platform sends the change to your site via this plugin. If the connection between OTTO and your WordPress installation is broken or misconfigured, changes will be recorded as deployed in Search Atlas but will never reach your live site. Step 1 — Verify the WordPress Plugin Is Installed and Active 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Confirm that the Search Atlas plugin is listed and its status shows Active. 4. If the plugin is missing, download the plugin .zip from your Search Atlas account and install it in WordPress → Plugins → Add New → Upload Plugin. 5. If the plugin is inactive, click Activate. Step 2 — Check for Caching Conflicts Even when changes are successfully deployed, caching layers can prevent them from appearing on the live site. Try clearing your caches, including any WordPress caching plugin, your hosting-level cache, any CDN cache, and your browser cache. After clearing caches, revisit the affected pages on your live site and check whether the changes are now visible. Step 3 — Escalate to Our Support Team Because deployment sync issues between OTTO and your live WordPress site may require backend investigation, please reach out to our team with the following details ready: - Your WordPress site URL - The specific OTTO fixes that are showing as deployed in Search Atlas but are not appearing on the live site - Any error messages 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.

🔌 Fix 'No EO Pixel Found' Error in WordPress

🧭 Overview The No EO Pixel Found error means Search Atlas cannot detect the EO Pixel on your WordPress site after the plugin has been installed. In most cases, completing the standard setup resolves this. However, if you have already installed the plugin, updated PHP, and followed all setup steps, a secondary layer of issues — such as plugin conflicts, caching, or initialization timing — may be preventing detection. This article walks you through every advanced troubleshooting path. ✅ Confirm the Basics First Before moving to advanced steps, verify the following are already in place: - The Search Atlas WordPress plugin is installed and activated (not just installed). - Your site is running PHP 7.4 or higher. - You are connected to the correct WordPress site in your Search Atlas dashboard under Account Menu → Settings → CMS Connectors. - The plugin was authorized using the correct Search Atlas account credentials. If any of these are incomplete, resolve them first. If all are confirmed and the error persists, continue below. 🗂️ Step 1: Clear All Caches Caching is the most common reason the EO Pixel is not detected even after a successful install. The pixel may be present in your live code but invisible to the scanner because an old cached version of your page is being served. 1. Log in to your WordPress admin dashboard. 2. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache), open its settings and select Clear All Cache or Purge Everything. 3. If your hosting provider offers server-level caching (common with SiteGround, WP Engine, Cloudways, Kinsta), log in to your hosting control panel and clear the server cache from there as well. 4. If you use a CDN such as Cloudflare, log in and purge the cache for your entire domain. 5. Return to Search Atlas and attempt to reconnect your site. ⚡ Step 2: Check for Plugin Conflicts Another active plugin may be interfering with how the EO Pixel is injected into your page's HTML. Security plugins, firewall plugins, and script optimization tools are frequent causes. 1. In your WordPress admin, go to Plugins → Installed Plugins. 2. Temporarily deactivate all plugins except the Search Atlas plugin. To do this safely, use a staging environment if one is available. 3. After deactivating other plugins, clear your cache again (Step 1) and retry the connection in Search Atlas. 4. If the connection succeeds, reactivate your other plugins one at a time, testing after each activation to identify the conflicting plugin. 5. Common conflicting plugin categories include: security firewalls (e.g., Wordfence, iThemes Security), script managers (e.g., Autoptimize, Asset CleanUp), and HTML minifiers. If you identify a conflicting plugin, check its settings for options that block or defer third-party scripts, and whitelist the Search Atlas plugin or its associated scripts. 🛡️ Step 3: Check for Theme or Script Optimization Issues Some WordPress themes and page builders (e.g., Elementor, Divi, Beaver Builder) apply their own script management or output buffering that can strip or delay pixel injection. - Temporarily switch your theme to a default WordPress theme (e.g., Twenty Twenty-Four) and test the connection again. - If your theme uses a child theme, deactivate the child theme and test with the parent theme only. - Disable any JavaScript deferral or concatenation settings in your theme's performance options and retest. ⏱️ Step 4: Allow for Initialization Race Conditions In some environments, there is a brief delay between plugin activation and the pixel becoming detectable on the live page. This is known as an initialization race condition. Search Atlas needs to scan a fully rendered, live version of your page — not a cached or partially loaded one. 1. After activating the plugin and clearing all caches, wait at least 5 minutes before attempting to reconnect in Search Atlas. 2. Visit your site's homepage in a private/incognito browser window to confirm it loads without errors. 3. Use a tool such as CTRL+U (View Page Source) in your browser to search for EO Pixel or the Search Atlas script tag in your raw HTML. If visible in the source, the pixel is present and the issue is likely on the detection side; proceed to Step 5. 4. If the pixel is not visible in the page source, the plugin is not injecting it correctly — return to Steps 2 and 3. 🌐 Step 5: Verify Site Accessibility and SSL Search Atlas must be able to reach your site externally to verify the pixel. Certain server configurations can block this. - Confirm your site is publicly accessible (not under maintenance mode or behind a login wall). - Ensure your site uses a valid SSL certificate (HTTPS). Sites with mixed content warnings or expired SSL certificates may cause detection failures. - If your site uses a robots.txt file that blocks all crawlers, temporarily allow access and retry. - If your hosting plan restricts external HTTP requests (some managed hosting environments do this), contact your host to confirm outbound and inbound requests are permitted. 🔄 Step 6: Reinstall the Plugin If none of the above steps resolve the issue, a clean reinstall of the Search Atlas plugin can clear corrupted installation files. 1. In WordPress, go to Plugins → Installed Plugins, deactivate, and then delete the Search Atlas plugin. 2. In Search Atlas, go to Account Menu → Settings → CMS Connectors and disconnect the existing site entry if present. 3. Reinstall the plugin fresh by uploading the latest .zip version from your Search Atlas dashboard via WordPress → Plugins → Add New → Upload Plugin. 4. Complete the authorization flow again using your Search Atlas credentials. 5. Clear all caches and wait 5 minutes before testing the connection. 📋 Information to Have Ready When You Escalate If you have completed all steps above and the error persists, our team will need the following information to investigate further. Please gather this before reaching out: - Your WordPress version and PHP version. - Your hosting provider name and plan type. - A list of active plugins at the time of the error. - A screenshot of the Search Atlas Account Menu → Settings → CMS Connectors screen showing the error. - A screenshot or copy of your page source (CTRL+U on your homepage) showing whether the EO Pixel script tag is present or absent. - Whether your site uses a CDN or WAF (Web Application Firewall), and which provider. If you need further assistance, open 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 'Pixel Not Connected' in WordPress Plugin

🔍 Understanding the 'Pixel Not Connected' Error After installing the Search Atlas WordPress plugin and authorizing it via your WordPress login, you may see a Pixel Not Connected status. This typically means the plugin has been authenticated but the tracking pixel has not yet been verified or properly linked to your Search Atlas account. Follow the steps below to resolve this. ✅ Step 1: Confirm the Plugin Is Installed and Active 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the Search Atlas plugin and confirm its status shows Active. If it shows Inactive, click Activate. 🔑 Step 2: Re-Authorize the Plugin Connection Authorization via WordPress login alone does not always complete the pixel handshake. You must also connect your site from within the Search Atlas platform. 1. Log in to your Search Atlas account. 2. In the left sidebar, click Site Metrics (Site Explorer). 3. Locate your website in the list, or add it if it has not been added yet. 4. Follow any prompts to reconnect or verify your site. This step triggers the pixel verification process. 🛠️ Step 3: Verify the Pixel Is Firing on Your Site Even when the plugin is active, a caching layer or conflicting plugin can prevent the pixel from loading correctly on your site's front end. - Clear your WordPress cache — if you use a caching plugin such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, purge all cached files after activating the Search Atlas plugin. - Clear your CDN cache — if your site runs through Cloudflare or another CDN, purge the CDN cache to ensure the updated page code is served. - Check for plugin conflicts — temporarily deactivate other plugins one at a time to identify any that may be blocking the pixel from loading. - Disable minification — some optimization plugins that minify or combine JavaScript files can interfere with pixel scripts. Temporarily disable JS minification and retest. 🌐 Step 4: Check Your Site's URL Format A mismatch between the URL registered in Search Atlas and the actual URL of your WordPress site is a common cause of pixel connection failures. - Make sure the URL in Search Atlas matches your site exactly — including whether it uses www or non-www, and http or https. - If your site recently moved to HTTPS or changed its primary domain, update the URL in Search Atlas to reflect this. 🔄 Step 5: Reinstall the Plugin If the steps above do not resolve the issue, a clean reinstall of the plugin often clears corrupt configuration data. 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. Deactivate and then Delete the Search Atlas plugin. 3. Reinstall the plugin by uploading the latest plugin .zip provided by Search Atlas via Plugins → Add New → Upload Plugin. 4. Activate the plugin and complete the authorization flow again. 5. Return to Site Explorer in Search Atlas and check whether the pixel status has updated to Connected. ⏱️ Allow Time for Status to Update After completing authorization and verifying the pixel is present on your site, the Pixel Not Connected status may take up to 15–30 minutes to refresh inside the Search Atlas platform. Visit a few pages on your site to generate pixel activity, then return to Site Explorer to recheck the status. 💬 Still Seeing the Error? If you have followed all the steps above and the pixel is still showing as not connected, If you need further assistance, open 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 OTTO Pixel WordPress Sync Issues

🔍 Overview The OTTO Pixel WordPress plugin links your website to Search Atlas so OTTO SEO can read your site data and apply optimizations. When the plugin shows Synced inside WordPress but Search Atlas still cannot detect it, a configuration or connectivity issue is preventing the two systems from communicating. This guide walks you through every fix, step by step. ✅ Before You Begin Confirm the following before diving into deeper troubleshooting: - You are logged in to Search Atlas and viewing the correct project/domain. - The OTTO Pixel plugin is active (not just installed) in your WordPress dashboard under Plugins → Installed Plugins. - You installed the plugin using the unique pixel key generated inside Search Atlas — not a generic copy. 🛠️ Step 1 — Verify Your Pixel Key Each domain in Search Atlas has its own unique pixel key. Using the wrong key is the most common cause of sync failures. 1. In Search Atlas, go to OTTO SEO → SEO Automation (left sidebar, URL: /seo-automation-v3). 2. Select your website and open the OTTO SEO panel. 3. Locate your Pixel Key and copy it exactly — including any hyphens or uppercase letters. 4. In WordPress, go to Search Atlas (WP menu) → Settings and paste the key into the OTTO Pixel UUID field. 5. Click Save Changes, then return to Search Atlas and wait up to 60 seconds for detection. 🔄 Step 2 — Deactivate, Reinstall, and Reactivate A corrupted plugin installation can cause silent sync failures even when WordPress reports the plugin as active. 1. In WordPress, go to Plugins → Installed Plugins. 2. Click Deactivate next to OTTO Pixel, then click Delete. 3. Return to Search Atlas and copy your pixel key again (see Step 1). 4. Reinstall the OTTO Pixel plugin by uploading the latest .zip version provided in Search Atlas via Plugins → Add New → Upload Plugin. 5. Enter your pixel key, save, and activate the plugin. 6. Check Search Atlas for detection — allow up to 2 minutes. 🌐 Step 3 — Check for Firewall or Security Plugin Conflicts Security plugins and server-level firewalls sometimes block the outbound requests the OTTO Pixel plugin needs to reach Search Atlas servers. - Wordfence, Sucuri, iThemes Security: Temporarily disable the firewall rules or whitelist Search Atlas domains (searchatlas.com and its subdomains). - Cloudflare: Set your domain's security level to Essentially Off temporarily and retest. If detection succeeds, add a firewall rule to allow traffic to/from Search Atlas. - Hosting-level firewalls (e.g., SiteGround, WP Engine): Contact your host or check your control panel to whitelist outbound requests to Search Atlas. After whitelisting, reactivate your security settings and recheck Search Atlas for detection. ⚙️ Step 4 — Confirm PHP and WordPress Requirements The OTTO Pixel plugin requires a minimum environment to run correctly. - PHP version: 7.4 or higher (PHP 8.x recommended). - WordPress version: 5.8 or higher. - HTTPS: Your site must be served over HTTPS. An SSL certificate must be active and valid. You can check your PHP version at WordPress Dashboard → Tools → Site Health → Info → Server. If your environment is below these minimums, contact your hosting provider to upgrade. 🧹 Step 5 — Clear All Caches Cached responses can prevent the plugin's verification handshake from completing. 1. Clear your WordPress caching plugin cache (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) — look for a Clear Cache or Flush Cache button in the plugin settings or admin toolbar. 2. Clear your Cloudflare or CDN cache if applicable. 3. Clear your browser cache and try reloading Search Atlas in a private/incognito window. 4. Return to Search Atlas and check for detection once more. 📋 Step 6 — Test in a Staging or Default Theme Environment Theme functions or other plugins occasionally interfere with pixel output. To isolate the issue: - Temporarily switch to a default WordPress theme (e.g., Twenty Twenty-Four) and recheck detection in Search Atlas. - Disable all plugins except OTTO Pixel, then recheck. Re-enable plugins one at a time to identify any conflict. If detection succeeds after switching themes or disabling plugins, you have identified the conflicting item. Reach out via chat (see below) and share the conflicting plugin or theme name so our team can advise further. 💡 Still Not Working? If you have completed all steps above and Search Atlas still does not detect the OTTO Pixel, there may be a server-level or account-level issue that requires manual investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you open the chat, please share: your domain URL, a screenshot of your OTTO Pixel plugin settings page in WordPress, and the name of any security plugins or CDN services active on your site. This helps our team resolve your issue as quickly as possible.

⚡ OTTO WordPress Installation and 'Not Found' Fix

Overview This article covers how to install OTTO on your WordPress site, create and configure a Topical Map, generate articles from it, and resolve the "OTTO not found" error that can appear even after your API key appears to have synced and the UUID field is populated. Installing OTTO on WordPress 1. Log in to your Search Atlas account and navigate to the OTTO section. 2. Copy your API key from the Search Atlas dashboard. 3. In your WordPress admin panel, go to Plugins → Add New → Upload Plugin, upload the plugin .zip provided by Search Atlas, then install and activate it. 4. In your WordPress admin panel, go to Search Atlas → Settings and paste your API key into the Search Atlas API Key field. 5. Save your settings and confirm that the UUID field is populated — this indicates a successful connection between your WordPress site and your Search Atlas account. Setting Up a Topical Map and Generating Articles 1. In Search Atlas, navigate to the Topical Maps tool and create a new map for your target topic or domain. 2. Review the suggested topic clusters and select the articles you want to generate. 3. Assign the Topical Map to your connected WordPress site within the OTTO settings. 4. Initiate article generation and monitor progress from your Search Atlas dashboard. Resolving the 'OTTO Not Found' Error If you see the "OTTO not found" error after the API key sync appears successful and the UUID field is populated, work through the following steps in order: 1. Confirm the plugin is fully activated: In WordPress, go to Plugins → Installed Plugins and verify the OTTO plugin shows as "Active" — installed but not activated will still show a UUID without establishing a live connection. 2. Check for plugin conflicts: Temporarily deactivate other plugins one at a time to identify whether a third-party plugin is interfering with the OTTO connection. Security, caching, and firewall plugins are common sources of conflict. 3. Verify REST API accessibility: OTTO relies on the WordPress REST API. If a security plugin or server-level rule is blocking REST API requests, the connection will fail. Check with your hosting provider or temporarily disable REST API restrictions to test. 4. Clear all caches: Clear your WordPress cache plugin, server-side cache, and any CDN cache, then retry the connection. 5. Re-enter your API key: Copy a fresh API key from your Search Atlas account, re-paste it into the OTTO plugin settings, save, and confirm the UUID repopulates. When to Escalate If you have worked through all of the steps above and the error persists, please have the following ready when you contact support so the issue can be resolved as quickly as possible: - Your Search Atlas account email or project name - The WordPress site URL where OTTO is installed - A description of which step is failing and what you have already tried - The exact error message (e.g., "OTTO not found") and any error codes displayed - A screenshot of your OTTO plugin settings page showing the API key and UUID fields - The names and versions of any other active WordPress plugins - The timestamp of when the issue first occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 WordPress OTTO Plugin Setup and Duplicate Script Fix

🧭 Overview When you activate OTTO through the Search Atlas WordPress plugin, OTTO automatically injects its JavaScript onto your site. If you previously added the OTTO pixel script manually — or if you have an older version of the plugin installed — both scripts can run at the same time. This duplicate causes a persistent OTTO JavaScript has been detected warning inside the OTTO SEO dashboard. This article walks you through the correct setup process and shows you how to eliminate the conflict. ⚙️ Step 1: Install or Confirm the Search Atlas WordPress Plugin 1. Log in to your WordPress admin panel. 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. 4. If the plugin is already installed, go to Plugins → Installed Plugins and confirm it is active and updated to the latest version. 5. Navigate to the plugin settings and connect it to your Search Atlas account using your API key. Your API key is available under your Search Atlas account settings. 🗑️ Step 2: Remove Any Manually Added OTTO Pixel Scripts If you previously connected OTTO by pasting a JavaScript snippet directly into your site, that manual script must be removed. Leaving it in place will cause the duplicate detection warning. Check these common locations for the old script: - Theme header or footer files: In your WordPress admin, go to Appearance → Theme File Editor and open header.php or footer.php. Look for any script tag referencing Search Atlas or OTTO and delete it. - Functions.php: Open functions.php in the Theme File Editor and remove any wp_enqueue_script or inline script block related to OTTO. - Third-party script manager plugins: If you use a plugin such as Insert Headers and Footers, WPCode, or similar, open that plugin and delete any saved OTTO script snippets. - Google Tag Manager: If you deployed the OTTO pixel through GTM, log in to your GTM workspace, find the OTTO tag, and either pause or delete it. After removing every instance of the manual script, save all changes. ✅ Step 3: Verify OTTO Activation in Search Atlas 1. Log in to Search Atlas and go to OTTO SEO using the left sidebar. 2. Select the website you are working on. 3. Confirm that OTTO is activated and that the WordPress plugin is shown as the connected deployment method. 4. If OTTO is not yet activated, click Activate OTTO and follow the on-screen prompts. The plugin will handle script injection automatically once activated. 🧹 Step 4: Purge All Caches Even after removing the old script, cached versions of your pages may still serve the duplicate code. You must clear every cache layer before the warning will disappear. Clear caches in this order: 1. WordPress caching plugin: Go to your caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache) and click Clear All Cache or the equivalent option. 2. Cloudflare or CDN cache: If your site runs behind Cloudflare or another CDN, log in and purge the full cache for your domain. 3. Server-level cache: If your host provides a server cache (such as Nginx FastCGI cache or a hosting panel cache), clear it through your hosting control panel. 4. Browser cache: In your browser, open DevTools (F12), go to the Network tab, check Disable cache, and reload your site. Alternatively, do a hard refresh with Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac). 🔍 Step 5: Confirm the Warning Is Resolved 1. Return to OTTO SEO in Search Atlas. 2. Refresh the page and check whether the OTTO JavaScript has been detected warning is still displayed. 3. If the warning is gone, your setup is complete and OTTO is running correctly through the plugin. 4. If the warning persists, open your browser's DevTools, go to the Sources or Network tab, and search for duplicate OTTO or Search Atlas script references loading on your site. Identify which file or plugin is still serving the old script and repeat Step 2 for that source. ⚠️ Common Mistakes to Avoid - Keeping both connection methods active at the same time. Use either the WordPress plugin or the manual pixel — never both. - Forgetting to clear the CDN cache. A Cloudflare or CDN cache can serve stale pages for hours. Always purge the CDN after making script changes. - Editing theme files without a child theme. Changes to parent theme files are overwritten on theme updates. Use a child theme or a code snippet plugin to ensure your edits persist. - Leaving old GTM tags active. GTM tags are easy to overlook. Double-check your GTM workspace even if you believe you removed the pixel locally. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix WordPress CMS Sync Errors After Reinstall

🔍 Overview Some customers find that the CMS sync for their domain continues to show an error even after uninstalling, reinstalling, and activating the latest version of the Search Atlas WordPress plugin. This article explains why that can happen and what to do next. ⚠️ Why This Happens A standard plugin reinstall does not always clear the underlying connection state on the platform side. The sync error may persist due to a stale or broken connection tied to your domain that requires a backend reset — something that cannot be resolved through the WordPress dashboard alone. 🛠️ What You Can Try First 1. Fully delete the plugin — do not just deactivate it. In your WordPress dashboard go to Plugins, deactivate the Search Atlas plugin, then click Delete to remove it completely. 2. Reinstall the plugin. Go to Plugins → Add New → Upload Plugin, upload the Search Atlas plugin .zip provided by Search Atlas, install the latest version, and activate it. 3. Attempt to reconnect your domain. Follow the standard reconnection flow in Search Atlas for your WordPress site and check whether the sync error clears. 📋 When to Escalate If the sync error persists after the steps above, the issue is likely a stale connection state on the backend that requires action from our engineering team. This is not something you can resolve from your WordPress dashboard or your Search Atlas account settings. When you contact support, please have the following ready: - Your domain name (the exact URL showing the sync error) - The exact error message displayed (a screenshot is helpful) - Confirmation that you have already deleted and reinstalled the plugin - Any timestamp of when the error first appeared or when you last attempted a reconnect If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Troubleshooting Plugin Conflicts: WP Rocket, Sucuri, LiteSpeed Cache, W3 Total Cache, and Divi Compatibility with Search Atlas

Some WordPress users — especially agencies, developers, and SEOs — use advanced performance or security plugins such as WP Rocket, Sucuri WAF/CDN, LiteSpeed Cache, or page builders like Divi. While powerful, these tools can sometimes conflict with Search Atlas's plugin or JavaScript snippet integration. This guide summarizes common issues and workarounds for advanced setups. If you're experiencing problems with Search Atlas not displaying, not injecting properly, or behaving inconsistently, this article is for you. ⚠️ Important — Do not use both integration methods at the same time: Do not use both the Search Atlas WordPress plugin and the JS snippet simultaneously. Duplicate installations have been reported to generate hundreds of duplicate form entries in Website Studio. Choose one integration method only. Note: Search Atlas can be integrated in two ways — via the official WordPress plugin or via the JavaScript snippet (pixel/manual script). Some of the conflicts below apply only to one integration path, so each entry indicates whether it affects the plugin, the JS snippet, or both. 🔍 Common Compatibility Issues and Fixes Tool Common Conflict Suggested Fix Applies To WP Rocket JS snippet is delayed or blocked Use Delay JS execution and exclude Search Atlas script JS snippet Sucuri WAF/CDN Cached version blocks dynamic JS Bypass cache for admin and plugin routes; clear cache after install. In the Sucuri dashboard, navigate to Firewall → Cache → Cache Exceptions and add your site's admin and plugin asset paths. Alternatively, enable Development Mode temporarily during initial setup. Both LiteSpeed Cache Can block plugin rendering Disable cache for logged-in users or plugin-specific URLs Plugin W3 Total Cache Object cache prevents plugin load Temporarily disable object caching during setup Plugin 🎨 Divi-Specific Notes Applies to: JS snippet integration. Issue: When inserting the Search Atlas JS snippet via Divi's Theme Options or Page Settings, the script may be sanitized or ignored. Solution: Use a plugin like Insert Headers and Footers or WPCode to inject the script at the site-wide <head> level. These plugins are generally more reliable for inserting custom code than theme options, but if OTTO changes still do not appear after correct injection, contact support — some builder configurations require backend intervention. 🧩 Using the Official Search Atlas WordPress Plugin Applies to: Plugin integration. We recommend using the native Search Atlas plugin provided by Search Atlas for a more stable and optimized experience. When to prefer the plugin over the JS snippet: - You want a managed integration that handles CMS connector syncing and updates automatically. - You are publishing content from Search Atlas into WordPress. - Your theme or page builder (such as Divi) sanitizes custom scripts inserted via theme options. Installation steps: 1. In WordPress, go to Plugins → Add New → Upload Plugin and upload the Search Atlas plugin .zip file provided by Search Atlas. 2. Install and activate the plugin. 3. Connect the plugin to your Search Atlas account using the API key from your dashboard. 4. Clear all caching layers (WordPress, CDN such as Sucuri, and browser) after activation. Tips: - Disable caching and minification during plugin activation. - After setup, clear all layers of cache: WordPress, CDN (Sucuri), and browser. - Avoid using both the JS snippet and the plugin at the same time unless advised by support. ⚠️ Known issue: Duplicate form entries when both integrations are active If both the Search Atlas plugin and the JS snippet are installed simultaneously, the integration may register the same form repeatedly, producing hundreds of duplicate entries in Website Studio → Forms. To avoid this, choose only one integration method. If you have already encountered duplicates, deactivate one of the integrations and contact support to help clean up the duplicate records. 🧭 Known issue: Site navigation menu fully expanded after plugin activation In some themes, activating the Search Atlas WordPress plugin may cause the public-facing site's navigation menu to render fully expanded. While our engineering team works on a permanent fix, you can apply a CSS override via Appearance → Customizer → Additional CSS to restore the intended menu behavior. When filing a support ticket, please include your active theme name so we can reproduce and track the issue. 🔌 Known issue: Atlas Brain shows CMS connector as disconnected despite active plugin If the CMS Connectors dashboard or Atlas Brain displays a "+" or disconnected state even though the plugin is installed and WordPress publishing works correctly, this may be a display bug. Before reinstalling the plugin, contact support to verify the backend connection status — in most reported cases the connection is healthy and only the UI indicator is stale. 📌 Note on JS Snippet Deprecation Applies to: JS snippet / pixel / manual script integration. Some users have asked whether the JavaScript snippet will be deprecated in the future. As of now, there is no official deprecation notice, but the plugin is the preferred integration method going forward. OTTO crawler and pixel/manual script installs: If you are using the pixel/manual script installation and see that Site Audit still reports original page titles rather than OTTO-deployed titles, this may indicate a known crawling issue. Ensure JS rendering is enabled in your project settings and contact support if titles remain stale after a recrawl. 🛠️ Still Need Help? If you're running a custom setup or using advanced server-level tools, we'd love to hear from you. Our team is actively collecting edge cases like this to improve both documentation and product compatibility. 💡 This article is part of our advanced user documentation. If you're an agency or technical user with performance tools, caching layers, or custom themes, this guide will help ensure Search Atlas works optimally in your stack. We'll continue updating this article based on new cases and user contributions.

🔌 Fix WordPress Plugin Sync & Pixel Errors

🔍 Understanding the Sync Status Discrepancy It can be confusing when your WordPress dashboard shows the Search Atlas plugin as active and synced, yet the OTTO SEO panel reports it as not installed correctly. These two status indicators pull data from different sources, so they can fall out of sync. The WordPress side confirms the plugin is installed and running on your server, while OTTO verifies a live, authenticated connection to your specific website property inside Search Atlas. The most common causes of this mismatch are: - The plugin was installed on the wrong WordPress site (e.g., a staging or subdomain URL that does not match your OTTO website property) - The Search Atlas pixel or API key inside the plugin settings was not saved correctly - A caching layer or security plugin is blocking the pixel verification request - The plugin was updated or reactivated after the initial connection, resetting the authentication token - Your website's server returned an error during OTTO's last verification check ✅ Step-by-Step: Verify Your Plugin Configuration 1. Confirm the correct website URL. In Search Atlas, go to your OTTO dashboard and note the exact domain associated with your website property (including or excluding www must match precisely). 2. Check the plugin is active on that domain. Log into the WordPress admin for that specific domain. Go to Plugins and confirm the Search Atlas plugin status shows Active. 3. Re-enter your API key. Inside WordPress, navigate to Search Atlas → Settings. Copy your API key fresh from your Search Atlas account settings and paste it into the plugin field. Click Save Changes. 4. Trigger a manual re-sync. After saving, look for a Sync Now or Verify Connection button within the plugin settings and click it. Wait 30–60 seconds for the handshake to complete. 5. Return to OTTO and refresh. Go back to your OTTO SEO dashboard in Search Atlas, refresh the page, and check whether the installation status has updated to Connected. 🛡️ Resolve Caching & Security Plugin Conflicts Security plugins such as Wordfence or iThemes Security, and caching plugins such as WP Rocket or W3 Total Cache, can sometimes block the outbound pixel request or serve a cached version of your site that does not include the Search Atlas pixel. Try the following: - Clear all site caches — purge server cache, CDN cache (e.g., Cloudflare), and any WordPress caching plugin cache. - Temporarily whitelist Search Atlas — in your security plugin, add Search Atlas domains to your allowlist, then re-run the sync. - Disable then re-enable the plugin — deactivate the Search Atlas plugin in WordPress, save, then reactivate it. This forces the pixel script to be re-injected into your page templates. - Check for JavaScript errors — open your website in a browser, right-click and select Inspect → Console, and look for any script-blocking errors related to the Search Atlas pixel. 🔑 Locate Your API Key in Search Atlas If you are unsure where to find your API key, follow these steps: 1. Log into your Search Atlas account. 2. Click your profile icon in the top-right corner and select Account Settings. 3. Navigate to the Integrations or API Keys tab. 4. Copy the key and paste it into the Search Atlas WordPress plugin settings as described above. Important: Each website property in Search Atlas may use a unique key. Make sure you copy the key associated with the exact domain you are configuring — do not reuse a key from a different property. 🔄 When to Re-install the Plugin If the steps above do not resolve the issue, a clean re-installation often clears any corrupted configuration data: 1. In WordPress, go to Plugins → Installed Plugins, deactivate the Search Atlas plugin, then click Delete. 2. Go to Plugins → Add New → Upload Plugin, upload the Search Atlas plugin .zip file provided by Search Atlas, and install it. 3. Activate the plugin and immediately enter your API key in Search Atlas → Settings before navigating away. 4. Save your settings, trigger the sync, and verify the connection status in OTTO. 💡 Tips to Keep Your Plugin Synced - Avoid installing the plugin on staging environments using the same API key as your live site — this can cause verification conflicts. - After any WordPress core update or theme change, revisit the plugin settings to confirm the pixel is still rendering on your pages. - If you migrate your site to a new host or domain, disconnect the old property in Search Atlas and create a new one with the updated URL before re-syncing. 🙋 Still Seeing a Sync Error? If you have followed every step above and your plugin still shows as not installed correctly in OTTO, our team can investigate the server-level handshake logs on your behalf. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Syncing WordPress to Publish Content

Seeing WordPress marked as connected in your Brand Vault and OTTO, yet still unable to publish a blog post directly to your client's site? This is usually caused by a missing or incomplete sync between your Search Atlas project and the WordPress destination. This guide walks you through checking the connection and publishing successfully. 🧩 Why the Connection Shows But Publishing Fails A WordPress site can appear connected in your Brand Vault and in OTTO while the Content tab still lacks an active publishing link. The Brand Vault and OTTO connections handle site-level integrations, but publishing a blog post requires the WordPress destination to be selected and synced within the Content tab itself. If this final step is missing, the publish button will not push your post to the live site. ✅ Confirm Your WordPress Prerequisites Before publishing, make sure the following are in place: - Plugin installed: The Search Atlas (or OTTO) WordPress plugin must be installed and activated on the client's site. - Correct site URL: The connected domain must match the exact URL of the site you want to publish to, including the correct www or non-www version. - User permissions: The connected WordPress account must have Administrator rights so it can create and publish posts. - Active API key: Confirm the API key or connection token has not expired or been regenerated on the WordPress side. 🔄 Sync WordPress in the Content Tab Follow these steps to link and sync your site for publishing: 1. Open your project and go to the Content tab. 2. Select the article or blog post you want to publish. 3. Click the Publish or Publishing Settings option. 4. Under the destination or integration menu, choose WordPress. 5. Select the correct WordPress site from the dropdown. If it is not listed, click Refresh or Reconnect to pull the latest connections. 6. Once the site appears, confirm it shows a Connected or Synced status inside the Content tab. 7. Click Publish to send the post directly to WordPress. 🛠️ Troubleshooting a Failed Publish If publishing still does not work after syncing, try these steps in order: - Reconnect the site: Go back to the Brand Vault, disconnect WordPress, then reconnect it and repeat the sync in the Content tab. - Update the plugin: An outdated plugin can block publishing. Ask the client to update it to the latest version. - Check the post status: Ensure the post is not stuck in draft or missing a required field such as a title or slug. - Clear the destination cache: Refresh the destination dropdown so it loads current site data instead of a cached entry. - Verify a single connection: Duplicate WordPress connections can cause conflicts. Remove any extra or outdated links so only the correct site remains. 🚀 Confirm the Post Went Live After publishing, verify success by doing the following: 1. Return to the Content tab and check that the post status changed to Published. 2. Open the client's WordPress dashboard and confirm the post appears under Posts. 3. Visit the live URL to make sure the content displays correctly. If the status remains stuck or shows an error, note the exact message displayed, as this helps identify the cause quickly. 💬 Still Need Help? If you have completed these steps and still cannot publish to your client's WordPress site, we are happy 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.

🔌 Search Atlas — CMS Integration Issues (WordPress, Shopify, Drupal, Contentful)

🔌 Search Atlas — CMS Integration Issues This article covers content sync, authentication, image handling, and field mapping for WordPress, Shopify, Drupal, and Contentful integrations. ⚠️ Error 1: Content isn't syncing to my CMS What's happening: The CMS connection may have lapsed or the connected user account lacks publishing permissions. Steps to try: 1. Check connection status: Top-right Corner Avatar → Settings → CMS Connectors → [Your CMS Domain] → Connection Status. Reconnect if it shows Disconnected. 2. Confirm the connected account has the right role: - WordPress: Administrator (Editor and Author accounts cannot connect the plugin) - Shopify: App must have write_content permission — reinstall the app if needed - Drupal: User must have content creation and publishing permissions - Contentful: Management API Token must have content management (read/write) scope on the target space and environment 3. Test a single article manual sync before attempting bulk sync. 4. After reconnecting, wait 5 minutes before syncing. 5. Contact support with the CMS type, error message, and article title. 🖼️ Error 2: Images appear broken in the CMS after syncing What's happening: Image URLs are relative or in a format the target CMS doesn't support. Steps to try: 1. Ensure all images in your Search Atlas content use full absolute URLs starting with https://. 2. Shopify: Convert WebP images to JPEG or PNG — older Shopify themes don't support WebP. 3. WordPress: Resize images over 8MB before syncing — that's the WordPress default upload limit. 4. Upload images directly to the Search Atlas media library first, then reference them from there. 5. Contact support with the image URL and CMS type, plus a screenshot of the broken image. 🚫 Error 3: Shopify sync returns 'Forbidden' or 'Permission Denied' What's happening: The Search Atlas Shopify app needs to be reinstalled to refresh permissions. Steps to try: 1. Reinstall the Search Atlas Shopify app from the Shopify App Store — this is the most reliable fix. 2. After reinstalling, go to Top-right Corner Avatar → Settings → CMS Connectors → [Your CMS] → Shopify → Reconnect. 3. In Shopify Admin → Apps → [Search Atlas App] → Permissions, confirm write_content is listed. 4. Wait 5 minutes after reinstalling before attempting a sync. 5. Contact support with your Shopify store URL and the exact error from the sync log. 🔄 Error 4: Direct CMS edits are being overwritten by Search Atlas syncs What's happening: Search Atlas is configured as the primary editor — syncs overwrite CMS versions. Steps to try: 1. Make all edits in Search Atlas Content Assistant, then sync — treat Search Atlas as your primary editor. 2. Look for a Sync Lock or Exclude from Sync option in the article settings to protect specific articles. 3. Pause auto-sync while editing in the CMS: Top-right Corner Avatar → Settings → CMS Connectors → [Your CMS Domain] → Disconnect. 4. Contact support to ask about enabling 'CMS as source of truth' mode if you primarily edit in your CMS. 📝 Error 5: Formatting (headings, bold, lists) is stripped after syncing in WordPress What's happening: The content format setting may be set to Plain Text instead of HTML. Steps to try: 1. For WordPress Gutenberg: try enabling 'Classic Block' format in sync settings. 2. Verify the content format is set to HTML, not Plain Text. 3. Re-sync the affected article and inspect the output in the WordPress block editor. 🔑 Error 6: Contentful connector fails with 'Invalid or expired Management API Token' What's happening: Previously, a backend bug (internal ref: CG-1641) caused the Contentful connector to reject valid Management API Tokens with an 'Invalid or expired Management API Token' error during setup. This bug has been resolved by the engineering team and the connector is now working as expected. Steps to try: 1. Retry connecting Contentful: Top-right Corner Avatar → Settings → CMS Connectors → Contentful → Connect. If you previously created a failed connection, remove it first and start fresh. 2. Generate (or reuse) a Contentful Management API Token from Contentful → Settings → API keys → Content management tokens. Personal Access Tokens or Content Delivery API keys will not work. 3. Ensure the token has access to the correct Space and Environment you intend to sync to, and that the token has not been revoked. 4. Paste the token into Search Atlas and complete the Space/Environment selection. 5. Run a single-article test sync before attempting bulk syncs. 6. If you still see 'Invalid or expired Management API Token' after the fix, contact support with: your Contentful Space ID, Environment, the timestamp of the failed attempt, and confirmation that the token was generated as a Content Management token. Note: If you opened a ticket about this error prior to the fix, please retry the connection — no further action is required from the Search Atlas side.

🔍 Fix Yoast Meta Description Detection Discrepancy

🧩 Why the Discrepancy Happens If Page Issues flags your page as missing a meta description while On-Page Audit shows one is present, the most common cause is a conflict with the Yoast SEO plugin. Yoast can output meta description tags differently depending on how it is configured, which may cause one tool to detect the tag while the other does not. Specifically, Yoast sometimes conditionally renders the meta description based on page type, template settings, or its own snippet preview logic. This inconsistency in how the tag is delivered in the page's HTML can confuse detection tools that crawl or parse the page at different times or in different contexts. 🛠️ How Each Tool Detects Meta Descriptions Understanding how each tool works helps clarify why they can produce different results: - Page Issues crawls your live URL and parses the raw HTML response to check for a <meta name="description"> tag in the <head> section. - On-Page Audit (found at Left sidebar → Content → On-Page Audit) performs a deeper content analysis that may render JavaScript or interpret the page differently, catching tags that a basic crawl might miss. Because these tools use different detection methods, a meta description that is injected dynamically or rendered conditionally by Yoast may appear in one tool but not the other. ✅ Steps to Resolve the Conflict 1. Verify the meta description in your page source. Open your live page in a browser, right-click, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for meta name="description". Confirm the tag exists in the raw HTML and contains the correct content. 2. Check your Yoast settings for that page. In your WordPress dashboard, open the page editor and scroll to the Yoast SEO meta box. Ensure the Meta description field is filled in and that the snippet preview shows the expected text. If the field is blank, Yoast will not output a tag. 3. Disable Yoast's advanced snippet settings if applicable. Some Yoast configurations suppress meta descriptions on archive pages, paginated pages, or pages set to noindex. Confirm the page is set to index and that no Yoast template is overriding the description output. 4. Clear your site cache. After making any changes in Yoast, clear your WordPress cache plugin (e.g. WP Rocket, W3 Total Cache) and your CDN cache if applicable. Stale cached pages can cause detection tools to read outdated HTML. 5. Re-run the On-Page Audit. Navigate to Left sidebar → Content → On-Page Audit, enter your page URL, and run a fresh audit. This gives Search Atlas updated data after your Yoast changes. 6. Re-check Page Issues. After the cache is cleared and the audit is re-run, allow Page Issues to recrawl your site or manually trigger a recheck. The two tools should now agree on the meta description status. ⚠️ When to Use On-Page Audit as the Source of Truth If your page source confirms the meta description is present and correctly formatted, treat the On-Page Audit result as the more reliable indicator. Page Issues uses a lightweight crawl that may not always account for how Yoast conditionally renders tags. The On-Page Audit performs a more thorough analysis and is better suited for diagnosing actual on-page SEO issues. 💡 Best Practices to Prevent Future Conflicts - Always write a unique meta description directly in the Yoast snippet editor for every important page rather than relying on auto-generated descriptions. - Avoid using multiple SEO plugins simultaneously (e.g. Yoast and All in One SEO). Duplicate meta tags or conflicting outputs are a common source of detection discrepancies. - After updating Yoast settings or upgrading the plugin, clear all caches and re-run your audits in Search Atlas to ensure data stays current. - Use Left sidebar → Content → Meta Generator to create optimised meta descriptions for your pages and paste them directly into Yoast for consistent, high-quality output. 💬 Still Seeing a Discrepancy? If you have followed all the steps above and the two tools still disagree, there may be a plugin-specific configuration or theme conflict that requires a closer look. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix WordPress Elementor Content Sync Issues

Overview When syncing content from Search Atlas to a WordPress site that uses Elementor, you may notice formatting inconsistencies, broken images, or content that does not appear as expected. This guide explains why these issues occur and what to do about them. Why Sync Issues Happen with Elementor Elementor is a page builder that stores content in its own custom data structure rather than in WordPress's standard post editor (the Block Editor or Classic Editor). When Search Atlas syncs content, it writes to the standard WordPress content field. If your page was built or last saved in Elementor, the two content sources can conflict, causing: - Formatted text appearing as plain or stripped-down content - Images missing or displaying broken links - Headings, bullet points, or spacing not rendering correctly - Content appearing in the wrong section of the page What to Do When You Experience These Issues Because the source topic for this article reflects a known compatibility issue between Search Atlas content sync and Elementor-managed pages, the specific resolution steps may vary depending on your WordPress setup, Elementor version, and how your pages are structured. If you are experiencing formatting or image problems after syncing, please reach out to our support team so we can review your specific configuration and guide you through the correct steps. When contacting support, it helps to have the following ready: - The name or URL of the WordPress page where the sync issue occurred - A description of what the content looks like after syncing (e.g., broken images, missing formatting, plain text) - Whether the page was built or last edited using Elementor or the standard WordPress Block Editor - Any error messages displayed during or after the sync attempt - The approximate date and time the sync was performed If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Plugin Duplicates and Deployment Status

Overview Two of the most common WordPress plugin issues Search Atlas customers encounter are duplicate information appearing in the plugin and deployment statuses showing items as undeployed when they have already been deployed. What to Have Ready Before Escalating Because the specific causes and confirmed resolution steps for these issues need to be verified by our support team, please gather the following information before reaching out: - Your project name in Search Atlas where the issue is occurring. - A description of the duplicate data you are seeing — for example, which items are duplicated and where they appear in the plugin. - The exact deployment status shown for the affected items (e.g., the label or status text displayed on screen). - Any error messages displayed in the plugin or on your WordPress dashboard — copy the exact text. - The timestamp or date when you first noticed the issue. - Your WordPress site URL and the version of the Search Atlas plugin you have installed. A support team member will be able to review your account, confirm the root cause, and walk you through the correct resolution steps for your specific situation. If you need further assistance, open 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 Search Atlas Plugin PHP Incompatibility Error

What Is This Error? When you activate the Search Atlas WordPress plugin on a server running an outdated version of PHP, WordPress may display a critical error or a blank white screen, making your site temporarily inaccessible. This happens because newer versions of Search Atlas require a minimum PHP version to run correctly. What to Do When You See This Error Because the specific PHP version requirement and the exact steps to resolve this error can vary depending on your hosting environment and your version of the plugin, we recommend taking the following general approach and then reaching out to our team for confirmation: 1. Deactivate the plugin. If your WordPress admin dashboard is still accessible, go to Plugins → Installed Plugins and deactivate Search Atlas. If your dashboard is inaccessible due to the error, contact your hosting provider — they can deactivate the plugin at the server level to restore access to your site. 2. Check your current PHP version. Log in to your hosting control panel and locate the PHP version setting. If you are unsure where to find this, your hosting provider's support team can confirm your current PHP version and how to change it. 3. Upgrade your PHP version. Work with your hosting provider to upgrade PHP to a version compatible with Search Atlas. Your hosting provider can complete this upgrade and advise on any compatibility considerations for your other plugins and themes. 4. Re-activate Search Atlas. Once your PHP version has been updated, go to Plugins → Installed Plugins in your WordPress dashboard and click Activate next to Search Atlas. 5. Verify the site is working. Visit your website and confirm the error is resolved. Then log in to Search Atlas and check that the plugin is connected correctly. Before You Upgrade PHP Upgrading PHP can affect other plugins and themes on your site. It is good practice to take a few precautions: - Back up your site before making any server-level changes. - Check compatibility of your other plugins and themes with the new PHP version before upgrading. - Test on a staging environment first if your site is business-critical. Need Help Confirming the Right PHP Version? If you are unsure which PHP version is required for your specific version of Search Atlas, or if you have followed the steps above and are still seeing errors, please reach out to our support team with the following information ready: your current Search Atlas plugin version, your current PHP version, and the exact error message 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.

🔧 Fix WordPress Plugin Dashboard and Google Instant Indexation Issues

Overview Two common issues reported with the Search Atlas WordPress plugin are unresponsive dashboard buttons and Google Instant Indexation failing to connect or configure. If you are experiencing either of these problems, our support team will need to investigate your specific setup to identify and resolve the root cause. Unresponsive Dashboard Buttons If buttons inside the Search Atlas plugin dashboard are not responding or appear frozen, this is a known issue that may affect certain WordPress environments. Because the cause can vary between setups, our team will need to review your case directly. When reaching out, please have the following ready: - Your WordPress site URL - The exact button or area of the dashboard that is unresponsive - Any error messages visible on the page - A description of when the issue first appeared and any recent changes made to your site Google Instant Indexation Connection Failures If Google Instant Indexation is not connecting or the configuration is not completing, this is also a known issue that requires investigation by our support team. Please have the following ready when you contact us: - Your WordPress site URL - The exact step at which the connection or configuration fails - Any error messages displayed during the process - A description of the steps you have already attempted If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix WordPress CMS Sync Not Implementing Changes

🔍 Overview When WordPress CMS sync is enabled, changes you make in Search Atlas — such as meta titles, descriptions, and content updates — should automatically apply to your connected WordPress site. If those changes are not going live, the steps below outline what our support team recommends checking. ✅ Before You Begin Confirm the following before troubleshooting: - You have administrator access to your WordPress site. - The Search Atlas WordPress plugin is installed and active. - You are logged in to Search Atlas with an account that has sufficient permissions. 🛠️ Step 1 — Verify the Plugin Is Active Confirm that the Search Atlas WordPress plugin is installed and enabled on your site. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the Search Atlas plugin and confirm it shows as Active. 4. If it is deactivated, click Activate. 🔑 Step 2 — Check Your API Key Connection Confirm that the API key entered in the Search Atlas plugin settings in WordPress matches the key in your Search Atlas account. An incorrect or outdated key can prevent changes from syncing. 1. Retrieve your API key from your Search Atlas account settings. 2. In your WordPress admin, open the Search Atlas plugin settings. 3. Re-enter or confirm the API key and save your changes. 4. Attempt a sync again to see if the issue is resolved. 🚨 If the Issue Persists If you have worked through the steps above and WordPress CMS sync is still not applying your changes, please reach out to our support team. To help us investigate, please have the following ready: your WordPress site URL, the name of the Search Atlas account, a description of the specific changes not being applied, and any error messages 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.

🛠️ Fix WordPress Plugin Performance Issues

🔍 Overview The Search Atlas WordPress plugin is designed to run efficiently in the background, but in some configurations it can contribute to slower page load times. This article helps you identify whether the plugin is contributing to a slowdown and explains what information to gather before escalating to our team for investigation. ⚡ Common Causes of Plugin-Related Slowdowns Before diving into troubleshooting, it helps to understand what typically causes a WordPress plugin to slow down a site: - Conflicting plugins: Another active plugin may be interfering with how Search Atlas processes data on the page. - Outdated plugin version: Running an older version of the Search Atlas plugin can introduce inefficiencies that have since been fixed. - Shared or low-resource hosting: Hosting environments with limited CPU or memory can amplify the performance impact of any active plugin. - Heavy page builders or themes: Resource-intensive themes can compound the load added by plugins. 🧪 Step 1 — Confirm the Plugin Is the Source Before making any changes, verify that the Search Atlas plugin is actually responsible for the slowdown. 1. Use a free tool such as GTmetrix or Google PageSpeed Insights to run a baseline speed test on your site with the plugin active. 2. Temporarily deactivate the Search Atlas plugin from your WordPress dashboard under Plugins → Installed Plugins. 3. Run the same speed test again and compare the results. 4. If load times improve significantly with the plugin deactivated, the plugin is a contributing factor and you should proceed to the steps below. 🔄 Step 2 — Update the Plugin Always ensure you are running the latest version of the Search Atlas plugin. Updates frequently include performance improvements and bug fixes. 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. If an update is available for Search Atlas, click Update Now. 3. After updating, clear your site cache and run another speed test to check for improvement. 📋 Step 3 — Gather Information for Escalation Because WordPress plugin performance issues often require backend investigation by our team, it is important to collect the following details before reaching out so we can investigate as quickly as possible: - Your site URL: The full URL of the affected WordPress site. - Plugin version: The exact version of the Search Atlas plugin currently installed (visible under Plugins → Installed Plugins). - Speed test results: Screenshots or URLs from GTmetrix or Google PageSpeed Insights showing the slowdown, ideally with the plugin both active and deactivated. - When the issue started: Note the approximate date and time you first noticed the performance degradation. - Other active plugins: A list of any other plugins running on your site at the time of the issue. - Hosting environment: Your hosting provider and plan type (e.g., shared, VPS, managed WordPress). - Any recent changes: Note any updates, installations, or configuration changes made around the time the slowdown began. Our team will use this information to investigate the root cause and identify the appropriate fix for your 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.

🔧 Fix WordPress REST API Blocked by Hosting Firewall

Overview When Content Assistant displays a vault not connected error during content generation or publishing, the most common cause is not a WordPress configuration issue — it is a firewall or Web Application Firewall (WAF) rule set by your hosting provider that blocks requests to the /wp-json/ REST API endpoint before they ever reach WordPress. This article explains why this happens and walks you through general steps to resolve it. Why This Happens Search Atlas Content Assistant communicates with your WordPress site through the WordPress REST API. All requests are sent to a URL that ends in /wp-json/. Many hosting providers run server-level firewalls or WAF rules that inspect incoming traffic and can block these requests automatically — even when your WordPress REST API settings appear correct inside WordPress itself. Common reasons a hosting firewall blocks REST API requests include: - The firewall treats automated API calls as suspicious bot traffic. - A security rule flags requests that do not originate from a browser. - WAF rulesets block access to /wp-json/ as a hardened security measure. - The hosting control panel has a security setting enabled that restricts REST API access. Because the block happens at the server level, disabling or re-enabling the REST API inside WordPress will not fix the problem. How to Confirm This Is the Cause Before changing any settings, confirm that the REST API endpoint is being blocked at the hosting level: 1. Open a new browser tab and go to https://yourdomain.com/wp-json/ (replace with your actual domain). 2. If you see a JSON response listing WordPress routes, the REST API is reachable and the issue is elsewhere. 3. If you see an error response or a generic hosting error page, your hosting provider firewall may be blocking the endpoint. 4. You can also use your browser's developer tools (Network tab) to check the HTTP response code returned for the /wp-json/ URL. General Fix: Whitelist the REST API in Your Hosting Firewall The steps below apply to most hosting providers. Log in to your hosting control panel and look for a section related to Security, Firewall, or WAF. 1. Locate the firewall or WAF settings for your domain. 2. Find any rule that blocks or restricts access to /wp-json/ or REST API requests. 3. Add a whitelist or allow rule for the path /wp-json/* so all REST API sub-routes are permitted. 4. Save your changes and wait a few minutes for the settings to take effect. 5. Return to Content Assistant and attempt to reconnect your vault or retry publishing. If the Issue Persists If you have reviewed your hosting firewall settings and the vault connection error continues, please have your domain name, hosting provider name, and any error messages ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚨 Fake DMCA Notices Targeting Search Atlas / Metasync Plugin Users

🔍 What Is This Notice? Some Search Atlas and Metasync WordPress plugin users have received emails or notices claiming to be a DMCA copyright infringement complaint targeting their website URLs because of the Metasync or Search Atlas SEO plugin. These notices typically warn that your site is violating copyright law and demand you take immediate action — such as removing the plugin, paying a fee, or clicking a link. These notices are not legitimate. They are a known scam specifically designed to target users of the Metasync and Search Atlas plugins. Search Atlas has no affiliation with these messages, and you are not in violation of any copyright law by using our plugin. ⚠️ How to Recognise the Scam Fake DMCA notices targeting Metasync or Search Atlas plugin users typically share one or more of these characteristics: - They reference your specific website URLs and mention the Metasync or Search Atlas plugin by name to appear credible. - They demand urgent action — such as removing the plugin within 24–48 hours or facing legal consequences. - They include a link to "dispute the claim" or "resolve the issue" — these links may lead to phishing pages or malware. - They request payment to settle the alleged infringement. - The sender's email domain does not belong to an official copyright authority, law firm, or Search Atlas. - The notice is sent to multiple URLs on your site simultaneously. ✅ What You Should Do 1. Do not click any links in the notice. Links in these scam emails may lead to phishing sites or trigger malware downloads. 2. Do not pay any fees. No legitimate DMCA action related to the Metasync or Search Atlas plugin will ever require a payment to a third party. 3. Do not remove the plugin based solely on this notice. Your use of the Search Atlas or Metasync plugin is fully licensed and lawful. 4. Mark the email as spam or phishing in your email client and delete it. 5. Report the email to your email provider using their built-in phishing or abuse reporting tools. 6. If you received the notice through your web host or a contact form, notify your hosting provider that a scam notice was submitted so they can log it. 🛡️ Why You Are Safe Using the Plugin The Search Atlas SEO plugin and the Metasync WordPress plugin are proprietary products developed and maintained by Search Atlas. All intellectual property rights belong to Search Atlas. Users who install and use the plugin through official channels — the WordPress plugin directory or their Search Atlas account — are fully licensed to do so. There is no copyright infringement involved in normal use of the plugin. Scammers deliberately target users of popular or niche plugins to make their claims appear plausible. The specificity of mentioning your URLs or the plugin name by name is a social-engineering tactic, not evidence of a real legal issue. 🔒 How to Verify a Legitimate Search Atlas Communication If you ever receive a notice and are unsure whether it genuinely comes from Search Atlas, use the following checks: - Official Search Atlas communications come only from verified Search Atlas email domains. If the sender's domain looks unfamiliar or misspelled, treat the message as fraudulent. - Log in to your Search Atlas account directly at the official URL. Any real account-level notices will appear inside the platform — not only by email. - Search Atlas will never contact you through a third-party copyright enforcement body to demand plugin removal or payment. 📋 Guidance for the FIN AI Agent If a customer reports receiving a DMCA or copyright infringement notice that mentions the Metasync plugin, the Search Atlas SEO plugin, or their website URLs in connection with either product, apply the following response logic: - Immediately reassure the customer that this is a known scam and they are not in legal jeopardy. - Do not tag the query as a WordPress Plugin support issue. Tag it as: security_scam / fake_dmca / metasync_plugin. - Direct the customer to this KB article for full guidance. - If the customer is distressed or requests human confirmation, route to a human teammate via the chat widget. - Do not escalate without a substantive answer. This article provides the complete resolution. Escalation is only needed if the customer reports clicking a link, submitting credentials, or making a payment — in which case flag as urgent and connect them with a human teammate immediately. 💬 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.

🔌 Fix WordPress Plugin Unengaged Status & Errors

🔍 What Does "Unengaged" Mean? When your Search Atlas WordPress plugin shows an Unengaged status, it means the plugin is installed on your site but has not successfully established an active, verified connection with your Search Atlas account. This is different from a failed installation — the plugin is present, but the handshake between your site and Search Atlas is incomplete. ⚠️ Common Causes of the Unengaged Status - Incorrect API key or token: The credentials entered during setup do not match your Search Atlas account. - Plugin version mismatch: An outdated version of the plugin may not communicate correctly with the Search Atlas platform. - Caching interference: Server-side or plugin-based caches can block the authentication request from completing. - Conflicting plugins: Security plugins, firewall plugins, or other SEO tools can intercept or block outbound API calls. - PHP or server restrictions: Some hosting environments restrict external HTTP requests, preventing the plugin from reaching Search Atlas servers. - WordPress site URL mismatch: If your WordPress address and site address settings differ, authentication may fail silently. 🛠️ Step-by-Step Troubleshooting 1. Verify your API credentials. In Search Atlas, go to Settings > Integrations > WordPress and copy your API key. In your WordPress dashboard, navigate to Search Atlas Plugin > Settings, paste the key, and save. Double-check there are no extra spaces before or after the key. 2. Update the plugin. Go to WordPress Dashboard > Plugins > Installed Plugins, find Search Atlas, and click Update if a newer version is available. Always use the latest version to ensure compatibility. 3. Deactivate, then reactivate the plugin. In Installed Plugins, click Deactivate next to Search Atlas, wait 10 seconds, then click Activate again. Re-enter your API key and save. 4. Clear all caches. Purge your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) and clear your hosting provider's server cache. Then retry the connection. 5. Check for plugin conflicts. Temporarily deactivate security or firewall plugins such as Wordfence, iThemes Security, or All In One WP Security. Attempt to authenticate again. If it works, whitelist the Search Atlas domain in your security plugin settings and re-enable it. 6. Confirm your WordPress URL settings. In WordPress Dashboard > Settings > General, ensure the WordPress Address (URL) and Site Address (URL) fields are identical and use the correct protocol (https:// if SSL is enabled). 7. Test external HTTP requests. Ask your hosting provider whether outbound HTTP requests to external APIs are allowed. Some managed hosting plans restrict this by default. Request that they whitelist Search Atlas API endpoints if needed. 8. Reinstall the plugin cleanly. Deactivate and delete the plugin, then download the latest version from Search Atlas and reinstall it via Plugins > Add New > Upload Plugin. Re-enter your credentials after reinstallation. ✅ How to Confirm the Plugin Is Now Engaged After completing the steps above, return to your Search Atlas dashboard and navigate to Settings > Integrations > WordPress. Your site should now display a green Engaged status. If you see this, the connection is active and data will begin syncing automatically. 💡 Tips to Prevent Future Issues - Always keep the Search Atlas plugin updated to the latest version. - After any major WordPress core update, re-check the plugin status in Search Atlas. - Avoid using multiple SEO plugins simultaneously, as they can conflict with each other. - If you migrate your WordPress site to a new domain or host, re-authenticate the plugin immediately after the move. 🆘 Still Showing Unengaged? If you have followed all the steps above and the plugin still shows an Unengaged status or persistent errors, our team is ready 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.

🛠️ Fix WordPress Hero Image Sync and Duplication Issues

🔍 Overview When you publish a blog post from Search Atlas directly to WordPress, you may notice two things: a second hero image appearing in the published post that you never added, and the blog URL not appearing immediately in your Search Atlas dashboard. These are known issues related to the WordPress integration. This article explains what to expect and how to get help resolving them. 🖼️ Duplicate Hero Image After Publishing Some users experience a duplicate hero image appearing in their published WordPress post after sending content from Search Atlas. This is a known bug in the WordPress integration. The content itself is not corrupted, but the extra image may affect the appearance of your post. Because the root cause involves the integration between Search Atlas and your WordPress environment, the fix requires investigation by our support team. To help us resolve this quickly, please have the following ready when you reach out: - The exact URL of the affected WordPress post. - The name of the article or project in Search Atlas. - A screenshot showing the duplicate image as it appears on the published post. - The date and approximate time you published the post from Search Atlas. ⏱️ Blog URL Not Appearing in Search Atlas After Publishing After publishing, some users find that the live blog URL does not appear in their Search Atlas dashboard right away. This is a known sync issue tied to the WordPress integration. In many cases it resolves on its own, but if the URL remains missing, our team will need to investigate. When contacting support about this issue, please have the following ready: - The name of the article or project in Search Atlas. - The WordPress site URL where the post was published. - The date and approximate time you published the post. - Confirmation of whether the post is live and publicly accessible on your WordPress site. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix WordPress Content Sync and Publishing Failures

🔍 Overview Search Atlas can connect directly to your WordPress site to publish and manage content. When a sync appears successful but content still fails to publish, the issue may stem from a misconfigured connection, a WordPress plugin conflict, or insufficient user permissions. This article describes the types of issues that can cause WordPress content sync and publishing failures in Search Atlas and explains what information to have ready when contacting our support team. ⚙️ Step 1 — Verify Your WordPress Connection A successful sync indicator does not always mean the connection is fully functional. Confirm that your WordPress integration is correctly configured by checking the following: - Locate the WordPress integration settings within Search Atlas and confirm that the site URL entered matches your WordPress site exactly — including the correct protocol (http:// or https://) — with no trailing slash errors. - Re-enter your WordPress credentials or API key and save the connection to refresh it. - If you are using the Search Atlas WordPress plugin, confirm it is installed, activated, and running the latest version inside your WordPress dashboard. 🔐 Step 2 — Check WordPress User Permissions Search Atlas publishes content using the WordPress user account linked during setup. If that account lacks sufficient permissions, publishing may fail even when the sync reports no errors. - Log in to your WordPress admin dashboard. - Locate the user account connected to Search Atlas and verify it has adequate publishing rights. - Save any changes and attempt to publish again from Search Atlas. 🛠️ Step 3 — Check for Plugin or REST API Conflicts WordPress publishing through Search Atlas relies on the WordPress REST API. Security plugins, firewall plugins, or misconfigured server settings can block REST API requests, causing silent publishing failures. 1. In your WordPress dashboard, review your installed plugins and consider temporarily deactivating any security or firewall plugins to test whether they are blocking the connection. 2. Attempt to publish a piece of content from Search Atlas again. 3. If publishing succeeds after deactivating a plugin, re-enable your plugins one at a time to identify which one is causing the conflict. 4. Once identified, configure that plugin to allow requests from Search Atlas, then re-enable it. You can also check whether your WordPress REST API is accessible by visiting yoursite.com/wp-json/ in a browser. If you see a JSON response, the API is active. If you see a blank page or error, the API may be disabled or blocked — contact your hosting provider in that case. 🔁 Step 4 — Retry the Sync and Escalate if Needed After making any of the corrections above, retry publishing from Search Atlas. If the issue persists, our support team can investigate further. To help us resolve your case as quickly as possible, please have the following ready: - The name of the Search Atlas project or workspace affected - The WordPress site URL you are trying to connect - A description of the exact error message or behavior you are seeing (including any error codes if shown) - The approximate date and time the issue started - A note on whether the Search Atlas WordPress plugin is installed and its current version If you need further assistance, open 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 OTTO Plugin Error 403 and Performance Issues

🔍 Overview If you are sending blog posts to your WordPress site using the Search Atlas OTTO plugin and encountering an Error 403, or noticing your website slowing down and content being duplicated, this article will help you identify the cause and resolve the issue quickly. ⚠️ What Is Error 403? A 403 Forbidden error means your WordPress site is actively blocking the request sent by the OTTO plugin. This is a permissions or security issue on the receiving server — not a problem with Search Atlas itself. Common causes include: - Security plugins (e.g., Wordfence, iThemes Security, Sucuri) blocking plugin API requests - Web Application Firewalls (WAF) flagging automated POST requests as suspicious - Incorrect API credentials or an expired connection between Search Atlas and your WordPress site - IP restrictions on your hosting server that block external services - User role permissions — the connected WordPress user account may lack sufficient rights (Administrator role required) 📉 Why Is My Site Performance Degrading? Performance degradation typically occurs when the OTTO plugin repeatedly retries a failed request. Each failed attempt can trigger multiple database writes or cache-clearing routines on your WordPress site, resulting in: - Increased server load and slower page response times - Duplicate posts or metadata appearing in your WordPress database - Excessive entries in your WordPress error logs Resolving the root cause of the 403 error will stop the retry loop and restore normal site performance. 🛠️ How to Fix Error 403 Step by Step 1. Check your security plugin settings. Temporarily disable your security plugin (e.g., Wordfence) and retry sending a post. If it succeeds, whitelist the Search Atlas IP ranges or the OTTO plugin within your security plugin's settings. 2. Review your WAF rules. Log in to your hosting control panel or WAF dashboard and look for recently blocked requests from Search Atlas. Add an exception rule to allow traffic from the OTTO plugin. 3. Reconnect your WordPress site in Search Atlas. Navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3), find your connected site, disconnect it, and reconnect using fresh API credentials. Ensure the WordPress user account you are connecting has Administrator role permissions. 4. Verify your WordPress REST API is enabled. The OTTO plugin communicates via the WordPress REST API. Go to your WordPress dashboard and confirm the REST API is not disabled by a plugin or theme. You can test this by visiting yoursite.com/wp-json/ — if it returns a JSON response, the API is active. 5. Check for IP restrictions. Contact your hosting provider and ask whether external API calls from third-party services are blocked. Request that they whitelist Search Atlas outbound IP addresses if necessary. 6. Remove duplicate content. If duplicate posts were created during the retry loop, go to your WordPress dashboard, navigate to Posts → All Posts, filter by date, and manually delete any duplicates. Consider using a database cleanup plugin to remove orphaned metadata. ✅ How to Confirm the Issue Is Resolved After completing the steps above, verify that everything is working correctly: - Navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and attempt to publish or update a post to your site - Confirm the post appears correctly in your WordPress dashboard without duplicates - Monitor your site speed for 10–15 minutes to confirm server load has returned to normal - Check your WordPress error logs to confirm no new 403 errors are being recorded 🚫 How to Prevent This from Happening Again - Always use an Administrator-level WordPress account when connecting your site to Search Atlas - After installing or updating a security plugin, re-verify that the OTTO plugin connection is still working - Avoid running multiple automated publishing tasks simultaneously to reduce server load - Periodically review your WAF and firewall logs to catch any newly blocked requests early 💬 Still Need Help? If you have followed all the steps above and are still experiencing Error 403 or performance issues, If you need further assistance, open 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 Search Atlas WordPress Site Crash After Plugin Activation

Overview If your WordPress site crashes or shows a critical error immediately after activating the Search Atlas plugin, the most likely cause is a PHP version incompatibility. Running the plugin on an unsupported PHP version can cause a fatal error and may take your site offline. This article walks you through confirming the root cause, recovering your site, and safely re-activating the plugin once your environment meets the requirement. Root Cause The Search Atlas WordPress plugin requires a minimum PHP version to function correctly. If your hosting environment runs an older PHP version than required, WordPress will throw a fatal error when the plugin initialises, making your site inaccessible through the browser. Step 1 — Check Your Current PHP Version Before making any changes, confirm which PHP version your server is running. The exact steps depend on your hosting provider. Common options include: - Hosting control panel (e.g., cPanel, Plesk): Look for a PHP or software configuration section within your control panel. Your hosting provider's documentation will show you exactly where this is located. - Managed WordPress hosting dashboards (e.g., Kinsta, WP Engine, SiteGround): Check your site's settings or environment section. Refer to your host's support documentation for the exact location. - No panel access: Contact your hosting provider directly and ask them to confirm the PHP version your site is running. If your PHP version does not meet the plugin's minimum requirement, that is the cause of the crash. Proceed to Step 2. Step 2 — Recover Your Site (If It Is Currently Down) Because the WordPress admin dashboard may be inaccessible when a fatal error is active, you may need to deactivate the plugin directly on the server. You can do this using FTP, SFTP, or your hosting provider's file manager tool. 1. Connect to your server using an FTP/SFTP client or open the file manager available in your hosting control panel. 2. Navigate to your WordPress plugins directory (typically found within the wp-content/plugins/ folder). 3. Locate the Search Atlas plugin folder. 4. Rename or remove the folder so that WordPress can no longer load the plugin. WordPress will automatically deactivate a plugin when its folder is no longer accessible. 5. Reload your website in a browser. Your site should now be accessible again. Once your site is back online, log in to your WordPress admin dashboard to confirm the plugin is shown as inactive. Step 3 — Upgrade Your PHP Version Contact your hosting provider and request that they upgrade your PHP version to one that meets the Search Atlas plugin's minimum requirement. Most managed hosting providers can do this quickly, and many allow you to change the PHP version yourself through their contro If you need further assistance, open 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 SEO Plugin Conflicts Causing Wrong Meta Descriptions

🧭 Overview If Search Atlas is displaying a meta description that does not match what is actually live on your page, the cause is often a third-party SEO plugin conflict. Plugins such as Yoast SEO, Rank Math, and Airlift can override the meta descriptions managed by Search Atlas, creating a mismatch between what Search Atlas reads and what is actually served on your page. This article explains why this happens and how to resolve it. ⚙️ Why This Happens Search Atlas writes meta descriptions directly to your pages. However, several popular SEO plugins also control meta description output and may take priority over changes made by other tools. When multiple plugins try to manage the same meta field, one overrides the other — and Search Atlas ends up reading stale or incorrect data. Common plugins that cause this conflict include: - Yoast SEO — manages its own meta description output and can conflict with other tools - Rank Math — similarly manages meta output independently and may suppress changes made by other tools - Airlift — a performance and SEO plugin that may interfere with meta tag output - Any other plugin that outputs custom meta description tags The result is that your live page serves the plugin's meta description while Search Atlas reflects a different value, making it appear as though Search Atlas is showing incorrect information. It is reading the value it last wrote or retrieved, while a plugin is overriding it on the front end. 🔍 How to Confirm a Plugin Conflict 1. Open your page in a browser and right-click anywhere on the page, then select View Page Source. 2. Press Ctrl + F (or Cmd + F on Mac) and search for meta name="description". 3. Check whether the description shown in the source code matches what you set in Search Atlas. 4. If they differ, look just above or below the tag for a comment or plugin signature indicating which plugin is controlling the output. 🛠️ How to Resolve the Conflict Choose the approach that best fits your setup: Option 1 — Disable meta description output in the conflicting plugin (recommended) 1. Log in to your WordPress dashboard. 2. Navigate to the settings of the conflicting plugin and look for an option to disable or turn off meta description output. 3. Save your changes and re-check your page source to confirm that Search Atlas is now controlling the meta description. Option 2 — Remove or deactivate the conflicting plugin 1. If you do not rely on the conflicting plugin for other functionality, consider deactivating it entirely from your WordPress plugins list. 2. After deactivating, clear any caches and verify your page source again. Option 3 — Contact the plugin's support team If you are unsure how to disable meta description output within a specific plugin, reach out to that plugin's support team for guidance on preventing it from overriding external meta description values. If you need further assistance, open 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 OTTO WordPress Plugin 'Not Detected' Error

Why OTTO Shows 'Not Detected' After installing the Search Atlas WordPress plugin, OTTO communicates with your site using automated monitoring requests. If your site runs behind Cloudflare or another bot-protection service, those requests may be blocked before OTTO can verify the connection. This causes the Not Detected status to persist even when the plugin is correctly installed. Step 1: Confirm the Plugin Is Installed Correctly 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins and confirm Search Atlas is listed and Active. 3. If the plugin is inactive, click Activate and recheck OTTO in your Search Atlas dashboard. 4. If the plugin is missing, reinstall it from your Search Atlas dashboard and repeat activation. Step 2: Whitelist the Search Atlas Bot in Cloudflare If the plugin is active but OTTO still shows Not Detected, Cloudflare is most likely blocking the monitoring requests. The most effective fix is to whitelist Search Atlas traffic in your Cloudflare settings. Because the specific IP addresses used by Search Atlas may change, open the chat widget in the bottom-right corner of the platform and type human teammate to request the current IP list before completing these steps. 1. Log in to your Cloudflare dashboard and select the domain connected to your WordPress site. 2. Locate your firewall or bot-protection settings and add an Allow rule for the Search Atlas IP addresses provided by our support team. 3. Check whether any bot-blocking features on your Cloudflare account are set to block automated or non-browser traffic, and create an exception for Search Atlas if so. 4. Review any active custom firewall rules that may block automated requests to your domain, and pause or adjust rules that could be interfering. 5. Save all changes and allow time for settings to propagate before rechecking OTTO. Step 3: Re-verify the Connection in Search Atlas 1. Return to your Search Atlas dashboard and locate your connected site. 2. Check the OTTO status to confirm it has updated. 3. If the status remains Not Detected after completing the Cloudflare steps, proceed to the section below. Other Firewall and Hosting Configurations Cloudflare is the most common cause, but other configurations can also block OTTO. Check the following if the issue persists after the Cloudflare steps. - Security plugins (e.g. Sucuri or Wordfence): Add the Search Atlas IP addresses (provided by our support team) to the allowlist in your security plugin settings. - Hosting-level firewalls: Some managed hosting providers apply their own bot-blocking rules. Contact your host and ask them to whitelist the Search Atlas IP addresses. - Staging or subdomain sites: Ensure the plugin is installed and active on the correct domain that is connected to 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.

🔧 Fix WordPress Plugin Authentication Credentials Error

Overview The 'authentication credentials not provided' error appears when the Search Atlas WordPress plugin cannot verify your account credentials during a diagnostic run. This usually means the connection between your WordPress site and Search Atlas has broken or was never fully established. Because the source of this error can vary by site configuration, the steps below cover the most common areas to check. Work through them in order before escalating. Step 1: Verify Your API Key Before changing any plugin settings, confirm that the API key linked to your site is still valid. 1. Log in to your Search Atlas dashboard. 2. Navigate to your account or integration settings and check whether an API key exists and is active. 3. If the key appears inactive, expired, or missing, generate a new one from within the dashboard. 4. Copy the key carefully — do not rely on a previously copied value. An invalid or expired key is a common cause of authentication failures that persist even after reconnection attempts. Step 2: Reconnect the Plugin If your key is active but the error continues, try fully disconnecting and reconnecting the plugin. 1. In your WordPress admin panel, open the Search Atlas plugin settings. 2. Remove or clear the currently stored API key. 3. Paste the fresh key you copied from the dashboard into the appropriate field and save. 4. Wait a minute, then run diagnostics again to see whether the error clears. Step 3: Check for Security Plugin or Server-Level Conflicts Security plugins and server-level firewalls can block the requests the Search Atlas plugin sends during authentication. - Temporarily deactivate any security or firewall plugins and run diagnostics again to see if the error disappears. - If diagnostics pass with those plugins off, re-enable them one at a time to identify the conflict, then adjust that plugin's settings to allow Search Atlas traffic. - Contact your hosting provider to confirm that outbound requests to Search Atlas servers are not being blocked at the server or firewall level. - Check whether your site's REST API is accessible — if it is disabled or restricted, the plugin will not be able to authenticate. Step 4: Clear Cached Credentials Stale cached data can cause the plugin to send outdated credentials. Clear your WordPress site's cache (including any object cache or page cache) and your browser cache, then attempt to reconnect the plugin and run diagnostics again. Step 5: Escalate if the Error Persists If you have worked through all of the steps above and the 'authentication credentials not provided' error still appears, the issue likely requires investigation by our support team. To help us resolve it as quickly as possible, please have the following ready when you reach out: - Your WordPress site URL - The exact error message displayed during diagnostics - A list of any active security or firewall plugins - Details of any recent changes to your site or hosting 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.

🔌 Fix Duplicate Plugin Warnings in Search Atlas

🧐 Why Duplicate Warnings Appear Search Atlas detects a duplicate when your WordPress site sends two separate tracking signals at the same time. This happens when both installation methods are active simultaneously: - The Search Atlas WordPress plugin — installed and active in your WordPress dashboard - The manual tracking script — added directly to your theme files, a header/footer plugin, or Google Tag Manager Because each method independently reports data to Search Atlas, the platform flags the account as a duplicate to prevent inflated metrics and reporting errors. Simply clearing cache or running a scan will not remove the warning unless the underlying duplicate installation is fully resolved first. 🗑️ Step 1 — Remove One Installation Method You only need one active installation method. Choose the option that best fits your workflow and fully remove the other. Option A: Keep the WordPress plugin, remove the manual script 1. Log in to your WordPress dashboard. 2. Navigate to Appearance → Theme File Editor (or open your child theme's header.php file). 3. Locate the Search Atlas tracking script — it typically begins with a comment such as <!-- Search Atlas --> or contains your unique site token. 4. Delete the entire script block and save the file. 5. If you added the script via a header/footer plugin (e.g., Insert Headers and Footers, WPCode), go to that plugin's settings and delete the Search Atlas script entry. 6. If you used Google Tag Manager, open your GTM workspace, find the Search Atlas tag, and either pause or delete it, then publish the updated container. Option B: Keep the manual script, remove the WordPress plugin 1. Log in to your WordPress dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the Search Atlas plugin. 4. Click Deactivate, then click Delete and confirm. 5. Verify no plugin files remain under wp-content/plugins/search-atlas/ via FTP or your hosting file manager if needed. 🗄️ Step 2 — Clear Your Cache After removing one installation method, clear all cache layers so the change is reflected immediately. Follow the steps for your environment: - WP Rocket: Go to Settings → WP Rocket and click Clear Cache. - W3 Total Cache: Go to Performance → Dashboard and click Empty All Caches. - LiteSpeed Cache: Go to LiteSpeed Cache → Dashboard and click Purge All. - WP Super Cache: Go to Settings → WP Super Cache → Delete Cache. - Cloudflare: Log in to Cloudflare, select your domain, go to Caching → Configuration, and click Purge Everything. - SiteGround (SG Optimizer): Go to SG Optimizer → Supercacher and click Flush Cache. - WP Engine: In your WP Engine portal, click Flush All Caches from the site's overview page. - Kinsta: In the Kinsta dashboard, select your site, go to Tools, and click Clear Cache. If you are unsure which caching layer is active, clear caches at the plugin level, the hosting level, and the CDN level to be thorough. ✅ Step 3 — Verify the Duplicate Warning Is Resolved Clearing cache alone does not confirm the fix. Complete these verification steps to ensure the duplicate warning is fully removed: 1. Log in to Search Atlas and open the affected client account. 2. Check whether the Duplicate label is no longer displayed next to the account name. Allow up to 10–15 minutes for the platform to re-evaluate the installation after cache is cleared. 3. Go to your WordPress site's front end and open your browser's developer tools (F12 → Network tab or Sources tab). Reload the page and search for Search Atlas in the loaded scripts. Confirm only one instance of the tracking script or plugin output is present. 4. Return to Search Atlas, navigate to the affected account's settings, and run a fresh site scan if the option is available. Confirm the scan completes without a duplicate flag. 5. If you manage multiple client accounts, repeat steps 1–4 for each account showing the duplicate label, as each WordPress site requires its own fix. ⚠️ Common Mistakes to Avoid - Deactivating the plugin without deleting it — an inactive plugin can still register with the platform in some configurations. Always delete it if you are switching to the manual script method. - Clearing only one cache layer when multiple are active — caches stack, so an old cached page can still serve duplicate scripts. - Assuming the warning clears instantly — the platform may take up to 15 minutes to update after the duplicate is resolved. 💬 Still Seeing the Duplicate Warning? If you have followed all the steps above and the duplicate label persists after 15 minutes, there may be a secondary script injection point (such as a page builder, third-party plugin, or server-side include) that is not yet resolved. If you need further assistance, open 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 Yoast Noindex Settings After Search Atlas Import

🧭 Overview When you import your Yoast SEO data into the Search Atlas plugin, most settings transfer automatically. However, in some cases, pages that were previously set to noindex in Yoast may appear to lose that setting after the import. This article explains why this happens and how to fix it. ⚠️ Why This Happens The most common cause is a known issue with how Yoast stores advanced robots directives. Yoast saves these settings in a WordPress database field called _yoast_wpseo_meta-robots-adv. In some installations, this field contains an array instead of a plain text string. When Search Atlas runs its import process (import_yoast_indexation()), it expects this field to be a string. If it receives an array instead, the import step fails silently and the noindex directive is not applied in Search Atlas — leaving those pages indexable. This affects only the advanced robots directives (such as noindex applied via Yoast's Advanced tab per post or page). Standard on/off indexing controlled through Yoast's main SEO settings may import correctly. 🛠️ How to Fix Affected Pages Follow these steps to manually restore noindex settings for any pages that were affected after the import. 1. Identify affected pages: Review your site for pages that should be noindex. You can cross-reference your original Yoast settings or use a crawl tool to find pages that are now being indexed unexpectedly. 2. Open the Search Atlas plugin in WordPress: Log in to your WordPress admin dashboard and navigate to the Search Atlas plugin settings. 3. Go to the affected post or page: Open the individual post or page editor in WordPress. 4. Locate the Search Atlas SEO meta box: Scroll down to the Search Atlas SEO section below the content editor. 5. Set the robots directive to noindex: In the Search Atlas SEO Meta Box (MetaSync plugin), note that no Robots/No-Index control is available; only a Disable SEO Meta Box toggle exists. 6. Save the page: Click Update or Publish to save your changes. 7. Repeat for all affected pages: Go through each page that needs the noindex tag restored and apply the same steps. ✅ How to Verify the Fix After saving, confirm that the noindex tag is being applied correctly: - Visit the page in your browser and view the page source (right-click → View Page Source). - Search for noindex in the source code. You should see a meta tag such as: <meta name="robots" content="noindex"> - If your site uses the X-Robots-Tag HTTP header instead of a meta tag, use a tool like Google's URL Inspection tool or a browser extension to check response headers and confirm the noindex directive is present. 🔄 Re-Running the Import If you have a large number of affected pages, you may want to re-run the Yoast import from within the Search Atlas plugin after the underlying data issue is resolved. Before doing so: - Ensure your Search Atlas plugin is updated to the latest version, as a fix for this import bug has been released. - Back up your WordPress database before re-importing to avoid overwriting any settings you have already corrected manually. - After updating the plugin, navigate to the Search Atlas import settings and run the Yoast data import again. The updated import process handles non-string values in the robots field correctly. 🚫 A Note on X-Robots-Tag HTTP Headers If your site's noindex directives were set via the X-Robots-Tag HTTP header rather than a standard meta tag, these are managed at the server or plugin level and are separate from Yoast's per-post settings. Search Atlas does not currently raise a distinct warning when noindex is set only via this method. Check your server configuration or any additional plugin managing HTTP headers to ensure this directive is still active after your migration. 💡 Best Practices Going Forward - After any plugin migration or data import, audit your most important noindex pages to confirm directives are in place. - Keep the Search Atlas plugin updated to benefit from the latest import compatibility fixes. - Use Google Search Console's URL Inspection tool periodically to spot any pages that should not be indexed. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Search Atlas Conflicts With Rank Math

🔍 Overview Some customers notice issues with the Rank Math WordPress plugin — such as schema editor errors or broken SEO settings — and disrupted Google Search Console or Google Analytics connections shortly after installing the Search Atlas WordPress plugin. This article explains why this happens and how to resolve it quickly. ⚙️ Why This Happens Search Atlas and Rank Math are both powerful SEO tools, and when they run on the same WordPress site, they can compete over certain resources. Known conflict triggers include overlapping plugin functionality, Google integration interference, and script loading issues in the WordPress admin environment. ✅ How to Resolve the Conflict Follow these steps in order. Most customers resolve the issue after completing Steps 1 and 2. 1. Disable overlapping schema features in one plugin. Choose which plugin will own your schema output — Search Atlas or Rank Math — and disable schema generation in the other. Refer to your chosen plugin's official documentation for the exact setting location, as menu paths may vary by version. 2. Reconnect your Google integrations. After adjusting schema settings, disconnect and reconnect your Google Search Console and Google Analytics accounts in both plugins, one at a time. Reconnect Search Atlas first, confirm the data loads, then reconnect Rank Math. 3. Deactivate plugins one by one to isolate conflicts. If the Rank Math settings panel is still broken, temporarily deactivate Search Atlas, clear your browser cache, and reload the Rank Math editor. If it works, the conflict is confirmed. Re-enable Search Atlas and contact support for further guidance. 4. Check for plugin and WordPress core updates. Outdated plugin versions are a common trigger for compatibility issues. Update both Search Atlas and Rank Math to their latest versions, then update WordPress core if an update is available. 5. Clear caching layers. If you use a caching plugin (e.g., WP Rocket, W3 Total Cache) or a CDN, purge all caches after making any changes. Stale cached files frequently cause errors to persist even after the root conflict is resolved. 🚫 What to Avoid - Do not run two SEO plugins with identical features both fully active at the same time without disabling the overlapping functionality in one of them. - Do not attempt to authenticate the same Google account in both plugins simultaneously without first disconnecting one, as this can cause token conflicts. If you need further assistance, open 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 Search Atlas Plugin Performance Slowdown

🔍 Overview Some users notice a drop in website performance after installing the Search Atlas WordPress plugin. This is a known issue our engineering team investigates on a case-by-case basis. This article explains what may be happening and how to escalate so our team can identify and resolve the root cause for your specific setup. ⚙️ What May Be Causing the Slowdown The Search Atlas plugin communicates with the Search Atlas platform to sync content, metadata, and SEO signals. Under certain configurations, this communication can introduce latency. Potential contributing factors include: - Conflict with other active plugins — some plugins may interfere with plugin scripts, causing repeated uncached requests. - Hosting environment limitations — shared hosting with limited server resources or slow external request handling can amplify any added load. - Outdated plugin version — older versions may include less efficient data-handling routines. - Excessive post volume — sites with a very large number of posts may experience heavier sync operations. 🚀 What to Try Before Escalating 1. Update the plugin to the latest version. In your WordPress dashboard, go to Plugins → Installed Plugins, find Search Atlas, and click Update if an update is available. 2. Check your PHP memory limit. Review your hosting account's server settings or contact your hosting provider to confirm your current PHP memory limit and request an increase if needed. 3. Check for plugin conflicts. Temporarily deactivate other active plugins and retest your site speed to determine whether a conflict is contributing to the slowdown. 4. Run a speed test before and after each change. Use a site speed testing tool to measure the impact of each adjustment individually so you can isolate the cause. 📋 How to Escalate This Issue Because this is a bug-category issue, our support team will need to investigate your specific environment. To help us resolve this as quickly as possible, please have the following ready when you contact us: - Your WordPress site URL - The exact version of the Search Atlas plugin you are running - The names and versions of any other active plugins, particularly caching or performance plugins - Your PHP memory limit and hosting provider name - A speed test report showing the slowdown - The approximate date and time when you first noticed the performance drop If you need further assistance, open 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 Divi Theme CSS Conflicts With Search Atlas Plugin

🔍 Overview Some customers using the Search Atlas WordPress plugin alongside the Divi theme have reported visual conflicts, including unexpected changes to text styles, header and footer rendering, and carousel behaviour. This article explains why these conflicts occur and what to prepare when reaching out to our team for help. ⚙️ Why This Conflict Happens The Search Atlas plugin injects CSS to support its on-page SEO features. Divi also outputs a large volume of its own inline styles and scripts. In some configurations, these stylesheets can interfere with each other, causing: - Font sizes or text styles changing unexpectedly across pages - Header and footer elements rendering incorrectly - Divi carousels or sliders behaving erratically or breaking entirely - Layout shifts on pages that use Divi's Visual Builder This is a CSS specificity and load-order conflict — it occurs because both tools compete to apply styles to the same HTML elements. 🛠️ Before Escalating: Steps to Try 1. Update both the Search Atlas plugin and Divi to their latest versions. Compatibility improvements are released regularly. Always start here before making any other changes. 2. Deactivate the Search Atlas plugin temporarily. Go to WordPress Admin → Plugins, deactivate the Search Atlas plugin, and reload the affected page. If the design issue disappears, the conflict is confirmed. Note this result — it will help our team diagnose the issue faster. 3. Clear all caches after any change you make. Cached stylesheets are a common reason a fix appears to have no effect. Clear any server-side or CDN cache you have in place before testing. 📋 How to Escalate to Our Team Because this is a confirmed bug category, our team will need to investigate your specific environment. To help us resolve this as quickly as possible, please have the following ready before you contact us: - Your WordPress version and the exact version numbers of both the Search Atlas plugin and the Divi theme - The URL(s) of the affected page(s) where the conflict is visible - A description of the visual issue — e.g. which elements are broken (fonts, carousel, header/footer) and when it started - Screenshots or a screen recording showing the conflict - Result of the deactivation test — whether disabling the Search Atlas plugin resolved the visual issue - A list of any other active plugins that interact with your site's front-end CSS or caching If you need further assistance, open 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 "Disallow: /" Warning in the Search Atlas WordPress Plugin

The Search Atlas WordPress plugin flags a Robots.txt "Disallow: /" warning when your robots.txt file contains a rule that blocks all search engine crawlers from your entire website — a single misconfigured line that can silently remove every page from Google search results. Follow the steps below to locate and remove the rule in under two minutes. 📌 Version requirement: This warning requires Search Atlas WordPress plugin version 2.4 or later. A detection bug in earlier versions (fixed May 2026, WP-322) prevented the warning from firing even when Disallow: / was present. Update the plugin before relying on this check. ⚠️ What the "Disallow: /" Warning Means Your robots.txt file tells search engines which pages they are allowed to crawl. The line Disallow: / under a User-agent directive instructs every crawler — including Googlebot — to stay off your entire website. The Search Atlas WordPress plugin flags this as a critical warning because one misconfigured line can de-index your whole site without any visible error in WordPress itself. Common causes include: - A site left in development or staging mode — WordPress automatically writes Disallow: / when the "Discourage search engines" checkbox is enabled under Settings → Reading. - A manually edited robots.txt file containing a leftover or accidental rule. - A third-party plugin or theme that wrote an overly broad rule during initial setup. Removing the rule restores full crawl access immediately. Previously de-indexed pages may take several days to weeks to reappear in Google search results as Googlebot re-crawls the site. 🔍 How to Find the Source of Your Robots.txt in WordPress Your robots.txt file is publicly accessible at https://yourdomain.com/robots.txt. Replace yourdomain.com with your actual domain. For WordPress Multisite or subdomain installs, check robots.txt at the root domain level, not the subsite URL. In WordPress, one of three sources controls its content: - WordPress core setting — Settings → Reading → "Discourage search engines from indexing this site" checkbox. - SEO plugin — Tools such as Yoast SEO, Rank Math, or All in One SEO generate and manage robots.txt from their own settings panels. - Physical file — A static robots.txt file in your site's root directory, editable via FTP, cPanel File Manager, or SSH. Identify which source applies to your site, then follow the matching fix below. 🛠️ How to Fix the "Disallow: /" Warning in WordPress Choose the method that matches how your robots.txt is managed. Fix via WordPress Settings (most common) 1. In your WordPress admin dashboard, go to Settings → Reading. 2. Find the checkbox labeled "Discourage search engines from indexing this site". 3. Uncheck the box. 4. Click Save Changes. WordPress removes the Disallow: / line automatically. Visit https://yourdomain.com/robots.txt in your browser to confirm the line no longer appears. Fix via an SEO Plugin 1. Open your SEO plugin's robots.txt editor — for example, Yoast SEO → Tools → File Editor, or Rank Math → General Settings → Edit robots.txt. 2. Find any line that reads Disallow: / under a User-agent: * block. 3. Delete the line entirely, or replace it with Disallow: (an empty value) to permit full crawl access. 4. Save the file. The updated rule takes effect immediately for all new crawl requests. Fix via a Physical File (FTP or File Manager) 1. Connect to your server using FTP, SSH, or your hosting control panel's File Manager. 2. Open the file robots.txt located in your site's root directory. 3. Delete the line Disallow: /, or change it to Disallow: to allow all crawling. 4. Save and upload the file. Confirm the change at https://yourdomain.com/robots.txt before re-running the Search Atlas audit. ✅ How to Verify the Fix in the Search Atlas WordPress Plugin After editing your robots.txt, confirm the warning is cleared directly in the Search Atlas WordPress plugin: 1. In your WordPress admin dashboard, go to OTTO SEO → Site Audit → Overview (Website Overview). 2. Click the Recrawl Site button to start a fresh scan. 3. Open the Robots.txt section in the audit results — the "Disallow: /" warning should no longer appear. A clean result in the Robots.txt section confirms search engines can crawl your site. If the warning persists, check whether a second source — a plugin or a physical file — is overwriting your robots.txt with the same rule. 💡 Robots.txt Best Practices to Prevent Future Warnings - Reserve Disallow: / for local or staging environments only — it must never appear in a live production site's robots.txt. - Use targeted disallow rules to block specific folders (e.g., Disallow: /wp-admin/) rather than blanket restrictions. - Audit after every site migration. WordPress often retains the "Discourage search engines" checkbox state when a staging site is cloned to production. - Re-run the Search Atlas Site Audit after major plugin updates, theme switches, or server migrations to catch robots.txt regressions early. Following these habits protects your site from accidental crawl blocks before they affect your rankings. 🎯 You now know what the Search Atlas "Disallow: /" warning signals, where the rule originates in WordPress, and how to remove it. Re-run the Site Audit to confirm your robots.txt is clean — then explore the Search Atlas Site Audit overview to identify and resolve any other critical SEO issues on your site.

🔍 Fix Empty On-Page Audit Results After Plugin Install

🧩 Why This Happens After installing the Search Atlas WordPress plugin, it is common to see empty or blank values in your on-page audit dashboard. This does not mean the audit failed — it usually means one or more setup steps were not completed correctly. ✅ What to Have Ready When Contacting Support Because empty on-page audit results after plugin installation require backend investigation to diagnose, our team will need the following information to look into your specific case: - The exact URL you are trying to audit - The domain registered in your Search Atlas plugin settings - The date and time you first noticed the empty results - Any error messages displayed in the plugin settings or audit dashboard (copy the exact text) - A screenshot of the empty audit result, if possible Having these details ready will allow our team to identify the root cause and resolve it as quickly 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.

🔧 Fix WordPress Plugin One-Click Authentication Failures

Overview If you have already installed the Search Atlas JavaScript code on your WordPress site but the one-click authentication button still fails, you are not alone. This is a known issue related to WordPress plugin authentication and OTTO integration. This article explains what to prepare and how to get it resolved quickly. Why Does This Happen? One-click authentication failures after JavaScript installation are typically related to how the Search Atlas WordPress plugin connects with OTTO. Installing the JavaScript snippet and authenticating the plugin are two separate steps, and completing one does not automatically complete the other. Common situations where authentication fails: - The one-click button does not complete the connection even though the JavaScript snippet is already on the site. - The plugin was installed or updated but the OTTO integration was not fully configured afterward. - A caching layer or server configuration is interfering with the authentication request. What to Try First Because the specific steps to resolve this issue depend on your account configuration and OTTO setup, the most reliable path is to work directly with the Search Atlas support team. Before reaching out, gather the following so your request can be handled as quickly as possible: - The domain of the WordPress site where the plugin is installed. - A description of exactly what happens when you click the one-click authentication button (e.g., error message, spinner that never completes, page reload with no change). - Whether you have already attempted any manual authentication steps in the plugin settings. - Any recent changes to your site, such as caching plugin updates, server migrations, or JavaScript snippet modifications. What to Expect Once a support agent reviews your account, they will be able to identify whether the issue is related to your OTTO configuration, plugin settings, or another factor, and will walk you through the exact steps needed for your setup. Manual authentication using your API key is a fully supported alternative path if the one-click button cannot be made to work. If you need further assistance, open 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 Persistent Redirects After Disabling Plugin Rules

🔍 Why Does the Redirect Still Happen? When you deactivate a redirect rule in the Search Atlas plugin, the rule is removed from the plugin's configuration immediately. However, a 301 redirect is cacheable by design — browsers, CDNs, hosting servers, and edge networks are all permitted to store and serve a 301 response without checking the origin server again. This means the redirect can continue firing even after the rule no longer exists, because a cached copy is being served from one or more layers in the delivery chain. Common sources of a cached redirect include: - Browser cache — your own browser or a visitor's browser has stored the 301 locally - CDN or proxy cache — services like Cloudflare, Fastly, or a hosting-level proxy cache the response at the edge - Server-level page cache — caching plugins (e.g. WP Rocket, W3 Total Cache, LiteSpeed Cache) or server software (Nginx, Apache) may have cached the redirect response - Search Atlas backend cache — in some configurations, redirect responses routed through Search Atlas infrastructure may be held in a short-lived cache 🛠️ Step-by-Step: Clear the Redirect From Every Layer 1. Confirm the rule is deactivated in Search Atlas. Go to the Search Atlas plugin → Settings tab and turn on the Disable Redirection toggle to disable the feature. Save your changes. 2. Clear your browser cache. In Chrome or Edge, open Settings → Privacy and Security → Clear Browsing Data and select Cached images and files. In Firefox, go to Settings → Privacy and Security → Clear Data. Alternatively, open the URL in a private/incognito window to test without any local cache. 3. Purge your caching plugin or server cache. If you use WP Rocket, LiteSpeed Cache, W3 Total Cache, or a similar plugin, navigate to its dashboard and click Purge All or Clear All Cache. If your host provides a server-level cache (e.g. SiteGround, WP Engine, Kinsta), log in to your hosting dashboard and clear the cache there as well. 4. Purge your CDN cache. If your site runs behind Cloudflare or another CDN, log in to your CDN dashboard and purge the specific URL or purge everything. Refer to your CDN provider's documentation for the exact steps to clear a cached URL. 5. Test with a redirect checker. Use a tool such as httpstatus.io or redirectdetective.com to trace the redirect chain for the affected URL. If the 301 no longer appears, the cache has been cleared successfully. If it still appears, note which server or IP address is returning the redirect — this helps identify which cache layer is still holding the response. 6. Wait for TTL expiry if needed. If you cannot manually purge a particular cache layer, the redirect will eventually stop once the cached entry's TTL (time to live) expires. TTL values vary by CDN and server configuration but are typically between a few minutes and 24 hours. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Troubleshooting Meta Description Sync Issues WordPress

🧭 Overview If meta descriptions you have edited in Search Atlas are not appearing in your WordPress backend editor, this is a known issue that our team needs to investigate on a per-account basis. The root cause can vary depending on your site setup, and the resolution requires a manual review by a support agent. What to Do Because the exact cause of meta description sync failures depends on your specific WordPress environment and account configuration, there is no single self-serve fix that applies to all cases. The most effective step you can take right now is to contact the Search Atlas support team directly so an agent can look into your integration and resolve the issue for you. When you reach out, please have the following information ready so the team can investigate quickly: - The name of the Search Atlas project you are working in. - The URL of the WordPress site where meta descriptions are not appearing. - The specific page or post URL(s) where the meta description is missing from the backend editor. - The exact meta description text you entered in Search Atlas. - Any error messages or unusual behavior you have noticed in either Search Atlas or your WordPress dashboard. - The date and approximate time when you last attempted the update. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin Pixel Not Connected Error

Overview After installing the Search Atlas WordPress plugin and completing the authorization flow, some users see a "pixel not connected" status message. Because the source of this issue can vary by site configuration, our support team will need to investigate your specific setup to identify and resolve the root cause. What This Article Covers This article explains what the error means and helps you prepare the information our team needs to resolve the issue as quickly as possible. It does not contain self-serve troubleshooting steps, because the correct resolution depends on details that must be reviewed by a support teammate. What "Pixel Not Connected" Means This status message indicates that Search Atlas has not been able to confirm that the pixel is active and communicating correctly on your site. This can occur for a number of reasons related to your WordPress environment, and diagnosing it requires a review of your account and site configuration. What to Have Ready Before Contacting Support To help our team resolve this as quickly as possible, please gather the following information before reaching out: - The website URL (property) showing the "pixel not connected" status in your Search Atlas account. - The WordPress version your site is running. - The version of the Search Atlas plugin currently installed. - Confirmation of whether you completed the authorization step after installing the plugin. - Any error messages displayed in the plugin settings page or in the Search Atlas platform, copied exactly as they appear. - The date and approximate time when you first noticed the status message. If you need further assistance, open 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 OTTO Plugin UUID Configuration Errors in WordPress

🔍 What Is a UUID Mismatch Error? When you connect the OTTO SEO plugin to your WordPress site, it relies on a Universally Unique Identifier (UUID) to link your site to the correct Search Atlas project. If this UUID does not match the one associated with your project — for example, your Jade project — the OTTO pixels will fail to fire correctly and display a configuration error. This mismatch is one of the most common reasons OTTO pixels show errors inside WordPress. The good news is that it is straightforward to diagnose and fix. ⚠️ Common Causes of a UUID Mismatch - Copy-paste errors: The UUID was entered incorrectly when setting up the plugin, such as missing characters or including extra spaces. - Wrong project selected: The UUID copied belongs to a different Search Atlas project, not the one intended for this site. - Plugin reinstallation: The plugin was reinstalled or reset without re-entering the correct UUID. - Multiple sites or projects: Managing several sites can lead to UUIDs being swapped between projects accidentally. - Outdated plugin version: An older version of the OTTO plugin may not read or store the UUID correctly. 🔎 How to Find Your Correct UUID in Search Atlas 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 3. Select the project you want to connect — for example, your Jade project. 4. Locate the OTTO Setup or Connect Site section within that project. 5. Copy the UUID displayed. Make sure you copy the full string with no extra spaces before or after it. 🛠️ How to Fix the UUID in Your WordPress Plugin 1. Log in to your WordPress admin dashboard. 2. In the left menu, navigate to the Search Atlas plugin → Settings → General tab. 3. Find the field labelled OTTO Pixel UUID. 4. Clear the existing value completely. 5. Paste the correct UUID you copied from Search Atlas. 6. Click Save or Update Settings. 7. Return to Search Atlas and refresh the OTTO SEO page to confirm the OTTO pixels are now active and showing no errors. ✅ How to Verify the Connection Is Working - In Search Atlas, go to OTTO SEO and open your project. The OTTO status indicator should show as Connected or Active. - In WordPress, check the OTTO plugin dashboard for any remaining error messages. If the UUID is correct, errors should clear within a few minutes. - Check that OTTO pixels are being detected on your site pages as expected. 💡 Best Practices to Prevent Future UUID Errors - Always copy the UUID directly from Search Atlas rather than typing it manually. - Keep a secure note of each project's UUID alongside its corresponding domain so you can reference it quickly. - After reinstalling or updating the OTTO plugin, verify the UUID is still correctly saved in the settings. - If you manage multiple WordPress sites, double-check that each site has its own unique project UUID and they have not been swapped. - Keep the OTTO plugin updated to the latest version to ensure compatibility with Search Atlas. 🆘 Still Seeing Errors? If you have followed all the steps above and the UUID mismatch error persists, there may be a deeper configuration issue with your project or plugin installation. If you need further assistance, open 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 Plugin Installation – Projects Not Showing in Dashboard

🔍 Overview After installing the OTTO plugin on your WordPress site, you may encounter one or more of the following symptoms: - An 'otto not found' error message in the plugin - Projects disappearing from the Search Atlas web dashboard - No active projects visible on the homepage These issues are almost always caused by an incomplete setup. The most common missing step is that a site audit crawl has not been run, which is required to link your site to OTTO and populate your projects in the dashboard. This article walks you through the complete troubleshooting flow from start to finish. ✅ Step 1: Confirm Your API Key Is Connected An incorrect or missing API key is the first thing to rule out. 1. In your WordPress admin panel, go to Search Atlas → Settings (Search Atlas API Key). 2. Locate the field where your API key is entered. 3. Log in to Search Atlas and navigate to Account Menu → Settings → API Keys to retrieve your API key. 4. Copy the key and paste it into the OTTO plugin settings field. 5. Save your settings and confirm that the plugin shows a successful connection status. If the connection status shows an error after saving, double-check that you copied the full key with no extra spaces. 🗂️ Step 2: Verify Your Project Exists in Search Atlas The OTTO plugin links to a project in your Search Atlas account. If no project exists for your domain, OTTO has nothing to connect to. 1. Log in to Search Atlas and navigate to the left sidebar → OTTO SEO. 2. Check whether your website appears as an active project in the list. 3. If your site is not listed, create a new project for your domain using the option provided in that section. Once your project exists, return to the OTTO plugin in WordPress and confirm it is mapped to the correct project. 🕷️ Step 3: Run a Site Audit Crawl (Critical Step) This is the most frequently missed step and the root cause of projects not appearing in the dashboard. OTTO requires a completed site audit crawl to activate your project and make it visible. Without it, the dashboard will appear empty even if everything else is configured correctly. 1. Log in to Search Atlas and navigate to the left sidebar → OTTO SEO. 2. Select your project from the list. 3. Locate the Site Audit section within the project. 4. Start a new site audit crawl using the option available in that section. 5. Wait for the crawl to complete. Depending on the size of your site, this may take a few minutes. Once the crawl finishes, your project will be fully activated and will appear on the Search Atlas homepage and in the OTTO plugin dashboard. Return to WordPress and reload the OTTO plugin to confirm the connection is now showing correctly. If you need further assistance, open 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 No-Index Pages After RankMath Migration

🔍 Why This Happens When you remove RankMath and import your SEO data into Search Atlas, RankMath's no-index settings can carry over during the migration process. This means pages and posts that should be publicly indexed may arrive in Search Atlas flagged as no-index, preventing search engines from crawling and ranking them. This is a known migration behaviour. The good news is you can resolve it in bulk without editing each page individually. ⚙️ Step 1 — Identify Affected Pages 1. In the left sidebar, click Site Metrics (Site Explorer) to open the Site Explorer. 2. Look for a filter or column related to indexability or no-index status. 3. Apply the No-Index filter to display only the affected URLs. 4. Review the list to confirm which pages should actually be indexed. 🚀 Step 2 — Bulk-Update the Indexing Status 1. While the no-index filter is active, select all affected pages using the Select All checkbox at the top of the list. 2. Look for the Bulk Actions or Edit option in the toolbar above the list. 3. Choose Set to Index (or the equivalent indexing option) from the bulk actions menu. 4. Confirm the action when prompted. Search Atlas will update the indexing status for all selected pages at once, saving you from making changes one by one. ✅ Step 3 — Verify the Changes 1. Clear the no-index filter and reload the page list. 2. Spot-check several previously affected URLs to confirm their status now shows as Index. 3. If any pages are still showing as no-index and should not be, repeat the bulk-update steps for those remaining URLs. 💡 Tips to Prevent This in Future Migrations - Audit before importing: Before completing a plugin migration, export your current page list from RankMath and review which pages are already flagged as no-index. Remove incorrect flags at the source first. - Test with a small batch: When migrating a large site, import a small subset of pages first and check their indexing status in Search Atlas before proceeding with the full import. - Check custom post types: No-index flags from RankMath often affect custom post types and archive pages. Make sure to include these in your post-migration audit, not just standard posts and pages. 🙋 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.

🛠️ Rank Math Compatibility and Deployment Troubleshooting

🔍 Overview Search Atlas is a powerful SEO platform that works alongside WordPress SEO plugins like Rank Math. While the two tools can coexist, there are important differences in how they handle on-page optimizations. Understanding this relationship will help you avoid conflicts and ensure your changes are deployed correctly to your site. ⚙️ How Search Atlas and Rank Math Interact Search Atlas does not directly integrate with Rank Math. Each tool manages SEO data independently, which means changes made in Search Atlas are not automatically synced to Rank Math, and vice versa. Specifically, you should be aware of the following: - Meta titles and descriptions: Rank Math controls these fields inside WordPress. If Rank Math is active, its meta settings will take priority over any conflicting values on the page. - Schema markup: Both tools can output schema. Running both simultaneously may produce duplicate or conflicting schema, which can negatively impact your search appearance. - Canonical tags: If Rank Math is managing canonicals, edits made elsewhere may be overridden on the front end. 🚀 Deploying Optimizations Correctly To ensure your Search Atlas recommendations are applied accurately to your site, follow these steps: 1. Identify which tool owns each element. Decide whether Rank Math or Search Atlas will be the source of truth for meta tags, schema, and canonicals. Avoid letting both tools control the same element. 2. Apply content recommendations manually. Use the content suggestions from Search Atlas — such as keyword placement, heading structure, and body copy improvements — and apply them directly inside your WordPress page or post editor. 3. Update meta data inside Rank Math. If Rank Math is active on your site, update your meta title and meta description directly within the Rank Math panel in the WordPress editor. Do not rely on Search Atlas to push these values automatically. 4. Disable duplicate features in Rank Math. If Search Atlas or another tool is handling schema, turn off the corresponding schema feature inside Rank Math to prevent conflicts. Navigate to Rank Math → Schema settings in your WordPress dashboard and disable any overlapping schema types. 5. Verify changes on the live page. After applying updates, use a browser or an SEO audit tool to inspect the live page source and confirm your meta tags, schema, and canonical tags are rendering as expected. 💡 Best Practices for Using Both Tools Together Following these best practices will help you get the most out of Search Atlas while keeping Rank Math running smoothly: - Use Search Atlas for keyword research, content briefs, rank tracking, and site-wide SEO analysis. - Use Rank Math for on-page WordPress-level controls such as meta fields, redirects, and sitemaps. - Perform a content audit after applying Search Atlas recommendations to confirm no Rank Math settings are overriding your changes. - Keep both plugins and platform accounts updated to benefit from the latest compatibility improvements. 📊 Checking Your Keyword and Ranking Data After deploying your optimizations, you can monitor performance directly inside Search Atlas: - To track keyword rankings, go to Left sidebar → Keywords → Rank Tracker. - To research new keyword opportunities, go to Left sidebar → Keywords. - To identify keyword gaps between your site and competitors, go to Left sidebar → Keywords → Keyword Gap. Allow 24–72 hours after deploying changes before evaluating ranking shifts, as search engines need time to recrawl and reindex updated pages. 🆘 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.

🔌 CMS Integration (WordPress, Shopify, Contentful)

This article covers: - WordPress publishing - Shopify blog publishing - Contentful integrations - image synchronization - authentication failures - content type mismatches - CMS API permissions - encoding issues - and publish synchronization delays. CMS publishing workflows depend on: - external CMS APIs - OAuth or application passwords - media accessibility - correct permissions - active content models - and stable synchronization between SearchAtlas and third-party platforms. Because these workflows involve external systems, temporary delays and authorization issues are common. ⚠️ Error 1: WordPress content push failing — posts not appearing in WordPress What's happening The most common cause is an expired, revoked, or invalid WordPress Application Password. Additional causes include: - security plugins blocking API access - REST API restrictions - incorrect user permissions - or WordPress caching conflicts. Steps to try 1. Go to: WordPress → Settings 2. Generate a new Application Password in WordPress: Users → Your Profile → Application Passwords 3. Update the password in Search Atlas. 4. Confirm the connected WordPress user has Editor or Administrator permissions. 5. Verify the WordPress REST API is publicly accessible. 6. Disable security plugins temporarily to test connectivity. 7. Confirm your domain uses the correct HTTPS protocol. 8. Retry publishing a smaller test article first. 9. Check whether WordPress caching plugins delay post visibility. 10. Contact support if publishing still fails after reconnecting credentials. Important Notes - Application Passwords can become invalid after password resets or security changes. - Many WordPress security plugins block external publishing by default. ⚠️ Error 2: Shopify publish rejected — "requires merchant approval for write_content scope" What's happening Shopify requires explicit merchant approval before apps can publish blog content. This error appears when: - write_content permissions were never approved - permissions changed - or the Shopify app authorization became outdated. Steps to try 1. Open Shopify Admin. 2. Go to: Apps → SearchAtlas App → Permissions 3. Approve the write_content scope. 4. Disconnect and reconnect Shopify inside SearchAtlas. 5. Confirm you are logged in as the Shopify store owner. 6. Verify the app still appears under active installed apps. 7. Retry publishing after reauthorization. 8. Test with a small draft article first. 9. Confirm the target Shopify blog exists and is active. 10. Contact support if permissions appear approved but publishing still fails. Important Notes - Shopify permission scopes are controlled entirely by Shopify security policies. - Reauthorization often refreshes missing scopes automatically. ⚠️ Error 3: Article image fails Shopify validation — "image is invalid" What's happening Shopify rejects images when: - files exceed size limits - unsupported formats are used - images are corrupted - or source URLs are inaccessible. Steps to try 1. Convert images to JPG or PNG format. 2. Keep image size under 20MB. 3. Avoid unsupported WebP formats on older Shopify stores. 4. Confirm image URLs load publicly in-browser. 5. Replace externally blocked image URLs. 6. Re-upload the image directly into SearchAtlas. 7. Compress oversized images before publishing. 8. Avoid hotlinking from restricted domains. 9. Test publishing with a single image first. 10. Contact support if valid images continue failing Shopify validation. Important Notes - Shopify validates image accessibility before importing. - Publicly accessible URLs are required. ⚠️ Error 4: Contentful connection fails — "Space endpoint not found" What's happening This error occurs when: - the Space ID is incorrect - the API token is invalid - the wrong API token type is used - or the Contentful space no longer exists. Steps to try 1. Go to: Settings → CMS Connectors (Contentful) 2. Re-enter the correct Space ID. 3. Generate a new Content Management API token. 4. Confirm you are using the Management API token — not the Delivery API token. 5. Verify the Contentful space still exists. 6. Confirm your account has access to that space. 7. Disconnect and reconnect Contentful integration. 8. Retry publishing after reconnection. 9. Test the connection with a simple content entry first. 10. Contact support if endpoint validation still fails. Important Notes - Delivery tokens cannot publish content. - Management tokens are required for write operations. ⚠️ Error 5: Contentful content type not found — publish fails What's happening Search Atlas can only publish into active Contentful content types. Publishing fails when: - the content type is still draft - the API ID is incorrect - or the selected content type does not exist. Steps to try 1. Open Contentful → Content Model. 2. Confirm the content type is activated and published. 3. Verify the API ID matches exactly. 4. Re-select the content type inside SearchAtlas. 5. Confirm required fields exist inside the model. 6. Ensure field validations are not blocking publishing. 7. Test publishing a minimal content entry. 8. Republish the content type after edits. 9. Refresh the Contentful integration connection. 10. Contact support if valid content types still fail recognition. Important Notes - Display names and API IDs are different. - SearchAtlas uses the API ID internally. ⚠️ Error 6: CMS database connection refused (UCMSI service unavailable) What's happening The CMS Integration service occasionally restarts or temporarily loses connectivity. This can interrupt: - publishing - synchronization - and API communication. Steps to try 1. Wait 5–10 minutes and retry. 2. Refresh the CMS Integration dashboard. 3. Retry publishing a small draft article. 4. Confirm your CMS credentials are still valid. 5. Check whether all CMS integrations are affected or only one. 6. Disconnect and reconnect the CMS integration. 7. Retry during off-peak hours. 8. Save/export your content locally before retrying. 9. Check whether the CMS itself is operational. 10. Contact support if the service remains unavailable longer than 15 minutes. Important Notes - Most UCMSI outages self-recover automatically. - Content is usually preserved even when publishing fails. ⚠️ Error 7: Published article contains garbled special characters What's happening Character encoding mismatches between: - SearchAtlas (UTF-8) - databases - CMS rendering engines - or imported legacy content can corrupt: - bullets - apostrophes - em dashes - smart quotes - and accented characters. Steps to try 1. Confirm your CMS database uses UTF-8MB4 encoding. 2. Verify your WordPress installation uses UTF-8MB4. 3. Re-save the affected article manually. 4. Avoid copy-pasting from Word documents directly. 5. Remove malformed hidden characters before publishing. 6. Test publishing a short clean-text article first. 7. Disable problematic legacy plugins temporarily. 8. Check whether the issue only affects imported content. 9. Compare the rendered article source code. 10. Contact support with examples of broken characters if the issue persists. Important Notes - Shopify and Contentful usually handle encoding automatically. - Legacy WordPress databases are more prone to encoding mismatches. ⚠️ Error 8: Content pushed to CMS but images are missing What's happening Images referenced by inaccessible or broken URLs cannot be fetched by the CMS during publishing. This commonly occurs when: - images are private - temporary URLs expire - media libraries are disconnected - or hotlinked assets are blocked. Steps to try 1. Open every image URL directly in-browser. 2. Confirm each image loads publicly without authentication. 3. Replace broken URLs before publishing. 4. Upload missing images directly into your CMS media library. 5. Avoid temporary CDN URLs. 6. Re-upload images inside SearchAtlas. 7. Publish a test article containing one image first. 8. Check whether image-hosting firewalls block external requests. 9. Verify media permissions inside Shopify or WordPress. 10. Contact support if images consistently fail despite being publicly accessible. Important Notes - CMS platforms must be able to fetch media externally. - Private or expiring URLs are the most common cause of missing images. They are usually related to: - expired credentials - missing API permissions - CMS security restrictions - inaccessible media assets - encoding mismatches - or external CMS validation rules. In many cases, the publishing system is functioning correctly — the external CMS environment is preventing synchronization from completing successfully. 👉 Stable CMS publishing workflows depend heavily on: - valid API credentials - publicly accessible media - correct permission scopes - UTF-8-compatible environments - active content models - and reliable synchronization between Search Atlas and the connected CMS platform.

🔍 Meta Descriptions Not Showing in WordPress

🧭 Overview If you have updated a meta description inside Search Atlas but do not see the change reflected in your WordPress backend editor, you are not alone. This is one of the most common questions our customers ask, and the good news is that it has a straightforward explanation. 💡 Why This Happens Search Atlas writes meta descriptions directly to your page's HTML output — the live, published version of your site — rather than to the WordPress database field that your theme or SEO plugin (such as Yoast SEO or Rank Math) displays inside the block editor or classic editor. As a result, the meta description field inside the WordPress backend may appear blank or still show the old value, even though your updated meta description is already live and visible to search engines. The two systems store this data independently, so a change in one place does not automatically update the other. ✅ How to Confirm Your Meta Description Is Live Before making any manual changes, verify that Search Atlas has successfully applied your meta description to the published page: 1. Open a new browser tab and navigate to the published URL of the page. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (Windows) or Cmd + F (Mac) to search for meta name="description". 4. Check that the content value matches the meta description you set in Search Atlas. If your updated meta description appears in the page source, it is live and working correctly. Search engines read the page source, not the WordPress editor field. 🛠️ What to Do If You Want Both in Sync If it is important to you that the WordPress backend editor also reflects the meta description, you can manually copy the value from Search Atlas and paste it into the corresponding field in your WordPress SEO plugin. This keeps both systems aligned without affecting how the page performs in search. 1. In Search Atlas, go to Left sidebar → Content → On-Page Audit and open the relevant page. 2. Locate the meta description field and copy the text. 3. Log in to your WordPress backend and open the page or post editor. 4. Scroll to your SEO plugin section (e.g., Yoast SEO or Rank Math) and paste the meta description into the meta description field. 5. Save or update the page in WordPress. Note: Pasting the value into WordPress does not override what Search Atlas has already applied. The live output on your site is controlled by Search Atlas via the connected integration. ⚙️ How Search Atlas Applies Meta Data Search Atlas uses its WordPress plugin integration to inject optimised meta tags at the point of page rendering. This means the meta description is applied dynamically when the page loads, ensuring search engines always receive the most up-to-date value you have set inside Search Atlas. The WordPress editor simply does not have visibility into this layer, which is why the discrepancy appears. 🚫 Common Misconceptions - The change did not save: If you can see the updated value in your Search Atlas dashboard and it appears correctly in the page source, the change has saved and is working. - The old description will be shown to Google: Google reads the rendered page source. As long as the correct value is in the source, your updated meta description is what Google sees. - Clearing cache will fix the blank field in WordPress: Clearing your site cache can help with display issues on the front end, but it will not populate the meta description field inside the WordPress editor, as that field is separate from the Search Atlas integration. 📊 Where to Manage Meta Descriptions in Search Atlas You can create and edit meta descriptions from two locations inside Search Atlas: - Left sidebar → Content → On-Page Audit — audit and optimise meta descriptions for existing pages. - Left sidebar → Content → Meta Generator — generate bulk or individual meta descriptions using AI. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress MetaSync Plugin Authentication Failures

🔍 Overview When connecting your WordPress site to Search Atlas using the MetaSync plugin, you may encounter an Authentication Failed error or a blank/spinning popup that prevents the connection from completing. This article walks you through the most common causes and how to fix them. ⚙️ Before You Begin Make sure you have the following ready: - Admin access to your WordPress dashboard - Admin access to your Search Atlas account - The latest version of the MetaSync plugin installed and activated 🛠️ Step 1 — Verify Your OTTO SEO Setup The MetaSync plugin requires an active OTTO SEO setup linked to your site before authentication can complete. If OTTO has not been configured, the plugin cannot verify your account. 1. Log in to your Search Atlas account. 2. Navigate to OTTO SEO from the main menu. 3. Confirm that your WordPress site's domain is listed and that OTTO has been activated for it. 4. If your site is not listed, add it and complete the OTTO setup before proceeding. 🔑 Step 2 — Regenerate Your API Key A corrupted or outdated API key is a common cause of authentication failures. Regenerating the key often resolves the issue. 1. In Search Atlas, go to Settings → API Keys (or your account/profile settings). 2. Locate your existing API key and select Regenerate or Create New Key. 3. Copy the new API key immediately — it will only be shown once. 4. In your WordPress dashboard, go to Search Atlas → Settings. 5. Paste the new API key into the API Key field and save. 6. Click Connect and wait for the authentication popup to complete. 🌐 Step 3 — Check for a 500 Error in the Authentication Popup If the authentication popup returns a 500 error instead of a success message, this indicates a server-side verification issue. Try the following: - Clear your browser cache and cookies, then retry the connection in a fresh browser window. - Disable any browser extensions (especially ad blockers or privacy tools) that may interfere with the popup. - Try a different browser to rule out a local browser issue. - Ensure your WordPress site is publicly accessible and not behind a maintenance mode plugin or firewall that blocks external API requests. 🔒 Step 4 — Confirm Your Site Allows External API Requests The MetaSync plugin communicates with Search Atlas servers to verify your API key. If your hosting environment blocks outbound requests, authentication will fail. - Check with your hosting provider that outbound HTTPS requests on port 443 are not blocked. - If you use a security plugin (e.g., Wordfence, iThemes Security), temporarily disable it and retry the connection. - If you use a firewall or CDN (e.g., Cloudflare), make sure Search Atlas API endpoints are not being blocked or rate-limited. - Ensure your WordPress site has a valid SSL certificate — authentication will not complete over HTTP. 🔄 Step 5 — Reinstall the MetaSync Plugin If none of the steps above resolve the issue, reinstalling the plugin clears any corrupted plugin files that may be causing the failure. 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. Deactivate and then Delete the MetaSync plugin. 3. Download the latest version of the MetaSync plugin from your Search Atlas account or the WordPress plugin repository. 4. Upload and activate the plugin. 5. Re-enter your API key and attempt the connection again. ✅ Confirming a Successful Connection A successful connection will display a confirmation message inside the MetaSync plugin settings page, and your site will appear as connected in your Search Atlas dashboard. Once connected, data sync between WordPress and Search Atlas will begin automatically. 💬 Still Need Help? If you have followed all the steps above and are still seeing an authentication error, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When reaching out, please share the following to help us investigate faster: - Your WordPress site URL - The exact error message or screenshot you are seeing - Your WordPress version and MetaSync plugin version - Any security plugins or firewall tools active on your site

🛠️ WordPress Plugin Troubleshooting Guide

The Search Atlas WordPress Plugin automatically handles API key configuration, plugin authentication, OTTO Pixel UUID injection, Server-Side Rendering (SSR), and OTTO communication with your site. If auto-configuration fails, use this guide to manually configure credentials and resolve common OTTO status errors. ⚠️ When to Use This Guide Use this guide only if you have installed the Search Atlas WordPress Plugin and see one of the errors below. Match the message to where it appears in the UI. In your OTTO dashboard: - "OTTO Not Detected" - "OTTO is disengaged" — only follow this guide if OTTO disengaged on its own without user action. If your team disengaged it intentionally, re-engage from the OTTO dashboard and monitor for re-deployment. - Missing deployed fixes or no crawl data In the WordPress plugin panel: - "Your script is using an incorrect UUID" - "Incorrect site token" - "API key could not be verified" In OTTO diagnostics / scan results: - "Duplicate Installation Detected" — if OTTO shows as installed but project UUIDs do not match, this may be a known platform bug (WP-343) rather than a true duplicate. Open a support ticket with your project UUID and site URL for engineering review (see Section 2). - Pixel Not Detected Note: Do not use this guide if your installation method is manual script, GTM, Shopify, GHL, Cloudflare Worker, or any other non-WordPress method. 🛠️ 1. Confirm the Plugin Is Installed Correctly ✔ Step 1 — Activate the Plugin Go to WordPress → Plugins. Search for Search Atlas SEO – Premier SEO Plugin. Confirm the status shows Active. If not, click Activate. ✔ Step 2 — Verify Authentication Go to WordPress → Search Atlas → Settings. Confirm all four of the following are present: - Green banner: Authentication Successful - Search Atlas API Key: auto-filled - Plugin Auth Token: auto-filled - OTTO Pixel UUID: auto-filled If any field is blank, click Connect to Search Atlas and complete authentication again. ⚠️ Known issue (AIAGENT-1905 — awaiting release): If Atlas Brain shows authentication status as PENDING but the WordPress plugin panel shows Authenticated, this is a known display mismatch. Do not re-enter or reset your credentials — re-authenticating repeatedly can break a working setup. Contact support and reference AIAGENT-1905 (include screenshots of both the plugin panel and the OTTO dashboard / Atlas Brain status) to confirm your actual authentication state. ⚠️ "API key could not be verified" error — Two separate values are required, and they are not interchangeable: - SearchAtlas API Key — a 32-character alphanumeric code found under Settings → API Keys in your Search Atlas dashboard. - Site Token — found in OTTO → Settings. Paste each value into its respective field in the WordPress plugin panel. Entering the wrong value in either field (for example, a license key, account password, or swapping the API Key and Site Token) triggers this error. ⚠️ If credentials are confirmed correct and the error persists, this may be a known platform-level bug (ref: WP-331). Open a support ticket with your site URL, the last 4 characters of your API Key, and your Site Token so engineering can investigate. When both credentials are confirmed, the green Authentication Successful banner appears and all fields auto-fill. 🗺️ 2. Verify OTTO Pixel Settings (Critical) Go to WordPress Admin → Search Atlas → Settings. ✔ Confirm the OTTO Pixel UUID Is Populated If the UUID field is blank, click Connect to Search Atlas again to re-authenticate and populate it automatically. ⚠️ Known issue (WP-343 — awaiting release): A platform bug can cause OTTO to display as Installed even when the project UUID does not match the UUID detected on the site. If you have confirmed the UUID values are mismatched but OTTO still shows as Installed, this is a bug — contact support rather than continuing to troubleshoot locally. ✔ Disable "OTTO for Logged-in Users" Toggle Disable OTTO for Logged-in Users to OFF during troubleshooting. If this is ON, OTTO will not load while you are logged in, producing false negatives in your tests. ✔ Disable Schema Markup (Optional) ✔ Enable Meta Description (Optional) Important: Do not add any OTTO Pixel script manually to your theme, header.php, or GTM. When the plugin is active, no manual pixel injection is needed — the plugin handles it automatically. ⚠️ If OTTO is adding unexpected content to your site (e.g., unwanted heading text or other injected content), go to OTTO → Deployed Fixes, identify the responsible fix by name (e.g., Heading Length), and click Undeploy. The injected content will be removed immediately. When all required settings are confirmed, OTTO can deploy fixes and the pixel UUID will match your OTTO project. ✅ 3. Confirm the Pixel Actually Loads (No Cache Interference) ✔ Step 1 — Log Out of WordPress The pixel does not load for logged-in users when the Disable OTTO for Logged-in Users toggle is enabled. Log out before testing to avoid a false negative. ✔ Step 2 — Inspect the Page Source Open your homepage, then right-click and select View Page Source. Press Ctrl+F (Windows) or Cmd+F (Mac) and search for: sa-dynamic-optimization - Found: The pixel is loading correctly. No further action needed in this section. - Not found: Proceed to Sections 4 and 5 to resolve firewall blocks and cache interference. ⚠️ 4. Whitelist the Search Atlas Crawler If your firewall or bot-protection plugin blocks the Search Atlas crawler, OTTO will show "Not Installed" even when the plugin is configured correctly. Whitelist the crawler in each active security tool below. Cloudflare Go to Dashboard → Security → Bots and turn OFF: - Bot Fight Mode - Super Bot Fight Mode WordFence Go to WordPress Admin → WordFence → Firewall → Options. Set Web Application Firewall Status to Disabled (temporary). Stop Bad Bots Go to WP Admin → Block Bad Bots → Settings. Disable Block All Bots, or add the following to the whitelist: Search Atlas Bot (https://www.searchatlas.com/) Blackhole for Bad Bots Add the following to the whitelist: Search Atlas Bot (https://www.searchatlas.com/) Shield Security Go to WP Admin → Shield → IP Rules → User Agent Rules and add to the whitelist: Search Atlas Bot (https://www.searchatlas.com/) After whitelisting the crawler in all active security tools, trigger a new OTTO scan to confirm the crawler can now reach your site. 🔵 5. Clear ALL WordPress Caches Caching is the most common cause of pixel dete 🎯 Once authentication is confirmed, the OTTO pixel is detected, and your crawler is whitelisted, OTTO should be fully operational and deploying fixes to your site. If errors persist after completing every section, contact Search Atlas support with your site URL, project UUID, and screenshots of all error messages for engineering review.

🔧 Fix WordPress Blog Sync Failures in Search Atlas

🔍 Overview If your WordPress blog sync was working previously but has recently stopped, the most common cause is an outdated MetaSync plugin installed on your WordPress site. Search Atlas now blocks older plugin versions to ensure secure and reliable syncing. This article walks you through diagnosing and fixing the issue. ⚠️ Common Symptoms - Sync fails despite a previously successful connection - You see a "plugin needs an update" error or warning inside Search Atlas - Blog posts are not appearing or updating in the Content Assistant - Images are broken after a recent WordPress plugin update - REST API route errors are displayed during sync ✅ Step 1 — Update the MetaSync Plugin The most important step is making sure you have the latest version of the MetaSync plugin installed on your WordPress site. 1. Log in to your WordPress admin dashboard (e.g., yoursite.com/wp-admin). 2. Navigate to Plugins → Installed Plugins. 3. Locate the MetaSync by Search Atlas plugin. 4. If an update is available, click Update Now. 5. Wait for the update to complete, then return to Search Atlas. Note: If you clicked an update link inside Search Atlas and were taken to the wrong page previously, this has been fixed — the link now routes you directly to your WordPress login page. 🔁 Step 2 — Re-Attempt the Sync Once the plugin is updated, retry the sync from within Search Atlas. 1. Open the Content Assistant in Search Atlas. 2. Navigate to the blog or content piece you want to sync. 3. Click the Sync to WordPress button. 4. Confirm the sync completes without errors. If the sync succeeds, no further action is needed. If it fails again, continue to the steps below. 🛠️ Step 3 — Check Your WordPress REST API Search Atlas uses the WordPress REST API to communicate with your site. If the REST API is blocked or misconfigured, syncing will fail even with an updated plugin. - Visit yoursite.com/wp-json/ in a browser. You should see a JSON response. If you see an error or a blank page, your REST API may be disabled. - Check if a security plugin (e.g., Wordfence, iThemes Security) is blocking REST API access for unauthenticated requests. - Temporarily disable any caching plugins and retry the sync. - Ensure your WordPress permalink settings are not set to Plain — go to Settings → Permalinks and choose any option other than Plain, then click Save. 📁 Step 4 — Verify Subpath or Subdirectory Deployments If your WordPress site is installed in a subdirectory (e.g., yoursite.com/blog/), you need to confirm the base path is correctly configured in Search Atlas. - In Search Atlas, go to your WordPress integration settings. - Confirm the site URL includes the full subpath (e.g., https://yoursite.com/blog). - Save your settings and retry the sync. Search Atlas now supports base path and slug configurations for subpath deployments, so ensure your URL reflects the exact installation location of WordPress. 🖼️ Step 5 — Fix Broken Images After a Plugin Update If images in your synced content appear broken after updating the MetaSync plugin, follow these steps: 1. Open the affected blog post in the Content Assistant. 2. Re-sync the post to WordPress using the Sync to WordPress button. 3. Check the post on your WordPress site to confirm images are loading correctly. 4. If images remain broken, try re-uploading them manually through the WordPress Media Library and updating the post. ❌ A Note on Backlink Data Accuracy If you have noticed backlink data appearing incorrect or invalid for a domain in Search Atlas (such as referring domains showing unexpected links), please be aware that backlink databases are updated on a regular crawl cycle. Data shown at any given moment reflects the most recent crawl. If you believe specific backlink data is inaccurate, document the affected domain and the links in question, then contact our support team for investigation. 💬 Still Need Help? If you have followed all the steps above and your WordPress sync is still failing, our team is ready to assist. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛡️ Fix WordPress Sync Blocked by Cloudflare WAF

🔍 What Is This Error? When Search Atlas attempts to sync or publish content to your WordPress site, our servers send requests to your site's API. If Cloudflare's Web Application Firewall (WAF) is active on your domain, it may identify these requests as suspicious and block them — returning a cloudflare_blocked error in the platform. This is one of the most common reasons WordPress sync fails. The good news is that it can be resolved quickly inside your Cloudflare dashboard without disabling your firewall entirely. ⚙️ How to Fix the Cloudflare Block Follow these steps to whitelist Search Atlas traffic in Cloudflare so sync can complete successfully. 1. Log in to your Cloudflare dashboard at cloudflare.com and select the domain connected to your WordPress site. 2. Go to Security → WAF in the left-hand navigation menu. 3. Click on Tools (or IP Access Rules depending on your Cloudflare plan). 4. Create a new Allow rule for Search Atlas IP ranges. Contact our team via the chat widget (see below) to request the current list of IP addresses used by Search Atlas sync services. 5. Alternatively, use a Custom WAF Rule to allow requests that include the Search Atlas user-agent string or target the /wp-json/ REST API endpoint from our servers. 6. Save the rule and make sure it is set to Allow, not Challenge or Block. 7. Return to Search Atlas and retry the WordPress sync from the platform. 🔎 Alternative: Use a Page Rule to Bypass WAF If you prefer not to modify WAF rules directly, Cloudflare Page Rules offer a simpler bypass option for the WordPress REST API path. 1. In your Cloudflare dashboard, go to Rules → Page Rules. 2. Click Create Page Rule. 3. In the URL field, enter your site's REST API path, for example: yourdomain.com/wp-json/* 4. Set the action to Disable Security. 5. Save and deploy the rule. This tells Cloudflare to skip WAF checks for all REST API requests on that path, which is where Search Atlas communicates with your WordPress site. 🛠️ Check the Search Atlas WordPress Plugin In addition to the Cloudflare fix, make sure the Search Atlas WordPress plugin is correctly installed and authenticated on your site. A blocked or timed-out connection can sometimes look similar to a firewall error. - Log in to your WordPress admin panel and navigate to Plugins → Installed Plugins. - Confirm the Search Atlas plugin is active and up to date. - If the plugin shows an authentication error, deactivate it, then reactivate it and complete the authorization flow again from within the Search Atlas platform. - Once reauthorized, retry the sync. ✅ Confirm Sync Is Working After applying the Cloudflare fix and verifying the plugin status, test the connection: 1. Inside Search Atlas, go to the WordPress Sync section. 2. Select your WordPress website from the site selector. 3. Attempt to publish or sync a piece of content. 4. If the sync completes without a cloudflare_blocked error, the issue is resolved. If the error persists after following all steps above, the block may be coming from an additional security layer such as a server-level firewall, a separate security plugin (for example Wordfence or Sucuri), or a hosting provider firewall. Check those settings as well. 💡 Tips to Prevent This in the Future - Whenever you update or change your Cloudflare security settings, re-test the WordPress sync to ensure access is still permitted. - If you migrate your WordPress site to a new domain or host, reconnect the Search Atlas plugin and recheck firewall rules for the new environment. - Keep the Search Atlas WordPress plugin updated to ensure compatibility with the latest sync improvements and authentication methods. 🙋 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.

🔧 Fix OTTO Pixel UUID Sync Issues in WordPress

Overview The OTTO Pixel UUID is a unique identifier that connects your WordPress site to your Search Atlas project. When the UUID fails to sync correctly, OTTO cannot activate or apply SEO changes to your site. This article explains what to check if you are experiencing UUID synchronization issues between your WordPress site and your Search Atlas project. What to Check First If your OTTO Pixel UUID is not syncing correctly between your WordPress site and Search Atlas, try the following steps: 1. Confirm you are using the correct UUID. Open your Search Atlas dashboard and locate the OTTO Pixel UUID for the specific project you are working with. Make sure you are not using a UUID from a different project. 2. Re-copy and re-enter the UUID. Copy the UUID directly from Search Atlas, then paste it into the UUID field in your Search Atlas WordPress plugin settings and save. Avoid copying from formatted documents, as this can introduce invisible characters. 3. Clear your caches. After updating the UUID, clear your WordPress plugin cache, any active caching plugins, and your browser cache, then check whether the sync resolves. 4. Ensure your Search Atlas WordPress plugin is up to date. An outdated plugin version may affect how the UUID is handled. Check for available plugin updates in your WordPress admin panel and install them if present. If the Issue Persists If you have followed the steps above and the UUID still fails to sync, our support team can investigate further. When reaching out, please have the following ready: - The name of the Search Atlas project you are trying to connect - The OTTO Pixel UUID you are using (or a screenshot of the UUID field in your plugin) - A description of exactly what you see — for example, whether the plugin shows an error, no status, or a mismatch message - Any steps you have already tried If you need further assistance, open 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 Deactivate/reinstall step: In WordPress, go to Plugins → Installed Plugins, click Deactivate then Delete next to OTTO Pixel, copy pixel key again from Search Atlas (OTTO SEO → All Sites (SEO Automation) → [Site] → Installation Guide), reinstall plugin, re-enter key. Also: after saving, wait up to 60 seconds for Search Atlas to detect the connection.

🔌 Fix WordPress Connector Gateway API Errors

🔍 What This Error Means If your WordPress connection shows a status of Active but you see an error such as 'operation wordpress-get-current-user is not available', the connection has lost its ability to communicate with the Search Atlas gateway. This typically means the link between Search Atlas and your WordPress site has broken at the API level, even though the dashboard still displays the connection as healthy. This is a known issue that can affect one or more WordPress sites connected within the same workspace. ⚠️ Does This Affect All My WordPress Sites? Not necessarily, but it can. Each WordPress connection in your workspace operates independently, so the error may be isolated to a single site. However, if the underlying cause is workspace-level (for example, a plugin sync failure or a gateway registration problem), multiple connected sites can be affected at the same time. We recommend checking all your WordPress connections when you encounter this error. 🛠️ Common Causes - The Search Atlas WordPress plugin was deactivated, removed, or is outdated on your WordPress site. - A plugin sync failure caused the site to drop out of the gateway registry, making its operations unavailable. - The connection token expired or became invalid after a WordPress update or site migration. - A previous reconnection attempt appeared successful in the dashboard but did not fully re-register the site with the API gateway. ✅ Step-by-Step Fix 1. Check the Search Atlas plugin on your WordPress site. Log in to your WordPress admin panel, go to Plugins, and confirm the Search Atlas plugin is installed, active, and up to date. If it is deactivated, reactivate it. If it is missing, reinstall it from your WordPress plugin library or via the instructions in your Search Atlas account. 2. Delete and reconnect the WordPress connector in Search Atlas. In your Search Atlas workspace, navigate to Avatar → Settings → Integrations (or CMS Connectors). Find the affected WordPress connection, click the options menu, and select Delete. Once removed, click Add Connection and reconnect your WordPress site from scratch. This forces a full re-registration with the API gateway. 3. Run a test connection. After reconnecting, use the Test Connection option to confirm the gateway can reach your site and that all operations are available. A successful test will show a green status with no errors. 4. Repeat for each affected site. If you have multiple WordPress sites in your workspace showing the same error, delete and reconnect each one individually. Do not assume a successful reconnect on one site resolves the others. 5. Retry your publishing or sync action. Once all connections test successfully, return to the content or task that originally triggered the error and try again. 💡 How to Prevent This in the Future - Keep the Search Atlas WordPress plugin updated whenever a new version is released. - Avoid deactivating the plugin on your WordPress site without first disconnecting it inside Search Atlas. - After any WordPress update or site migration, run a test connection in Search Atlas to confirm the API gateway link is still healthy. - If you transfer a WordPress site to a new host or change its domain, delete and reconnect it in Search Atlas rather than relying on the existing connection. ❓ Still Seeing the Error? If you have followed all the steps above and the error persists, or if the connector appears grayed out and cannot be deleted or reconnected, there may be a deeper configuration issue that requires investigation by our 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. Additional Notes Because the root cause is at the platform level, it requires investigation by the Search Atlas team. Gather: exact error message, failing operation name, WordPress site URL, date/time error first appeared, screenshots. Open chat widget and type 'human teammate' to reach support.

🔌 Fix Otto Duplicate Installation and Plugin Conflicts

🧭 Overview If Search Atlas reports that Otto is not installed while you are also seeing a duplicate installation warning, there is a conflict between two sources of the Otto tracking code on your site. This usually happens when the Otto snippet has been added both manually (via a code snippet plugin or theme file) and through the official Otto WordPress plugin. This article walks you through diagnosing the conflict and reaching a clean, working installation. 🔍 Step 1: Check Otto's Status in Search Atlas Before making any changes to your WordPress site, confirm what Search Atlas currently detects. 1. Log in to your Search Atlas account. 2. Navigate to the Otto or OTTO SEO section of the platform. 3. Review the Otto connection status shown on the page — it should indicate whether Otto is detected on your site. 4. Note the current status before proceeding, so you can confirm whether your changes resolve the issue. ⚠️ Step 2: Understand Why the Conflict Happens A duplicate installation warning means Search Atlas has found more than one copy of the Otto tracking code firing on your site. Common causes include: - The Otto WordPress plugin is active and the Otto code snippet was also pasted manually into your theme files. - A code snippet plugin is injecting the Otto script separately from the official plugin. - A previous plugin installation was deactivated but not deleted, leaving residual code behind. - A caching layer is serving an old version of the page that still contains the old snippet. 🛠️ Step 3: Remove the Duplicate Code Source You need to keep only one source of the Otto code — the official Otto WordPress plugin. Remove all other instances. 1. Log in to your WordPress admin panel. 2. Go to Plugins → Installed Plugins and check whether the Search Atlas plugin is listed and Active (you can access its settings via Search Atlas → Settings). If it is not active, activate it now before proceeding. 3. Check your theme files (via the Theme File Editor or an FTP/file manager client) for any manually added Otto tracking code or references to your Otto site key. Delete any such block and save the file. 4. Open any active code snippet plugins and search for snippets that include the Otto tracking script. Disable and delete those snippets. 5. If you use a page builder or a tool with custom header or footer code injection fields, check those fields and remove any Otto script you find there as well. 🔄 Step 4: Clear Your Site Cache After removing the duplicate code, clear all caching layers to ensure Search Atlas re-evaluates a clean version of your pages. 1. Clear the cache in your WordPress caching plugin, if you use one. 2. Clear any server-side or CDN cache associated with your site. 3. Reload your website in a browser (using a hard refresh) to confirm the cached version is no longer served. ✅ Step 5: Verify the Otto Plugin Is Working Once all duplicate sources have been removed and caches cleared, return to Search Atlas and check the Otto connection status again. It should now reflect a single, active installation. If the status has not updated, wait a few minutes and refresh the page, as detection may take a short time to propagate. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin UUID Error After Project Recreation

🧭 Overview If your Search Atlas WordPress plugin is showing an incorrect UUID error even though the UUID in your plugin settings matches the one shown in your Search Atlas dashboard, the issue is almost certainly caused by project deletion and recreation. When a project is deleted and a new one is created, the old UUID can leave behind an orphaned cache or backend state — causing the plugin to reject an otherwise valid UUID. This article walks you through the exact steps to clear that stale state and restore the connection. ⚠️ Why This Happens The standard UUID mismatch fix (copy-pasting the correct UUID) works when the two values genuinely differ. However, if you have recently deleted a project and recreated it, the new project receives a brand-new UUID. Even though you update the plugin with the new UUID, the plugin or platform backend may still be holding a cached reference to the old, now-deleted project. This causes the incorrect UUID error to persist despite both values appearing identical. ✅ Before You Begin Confirm the following before proceeding: - You have deleted a project in Search Atlas and created a replacement project. - You have already copied the new project UUID into your WordPress plugin settings. - The UUID shown in the plugin settings and the Search Atlas dashboard are visually identical. - The incorrect UUID error is still appearing. If all four points are true, follow the steps below. 🛠️ Step-by-Step Fix 1. Confirm the correct UUID in Search Atlas. Log in to Search Atlas and navigate to the project you want to connect. Copy the full UUID exactly as shown — including any hyphens. Do not copy from a saved note; always copy directly from the dashboard to avoid invisible characters. 2. Deactivate the Search Atlas WordPress plugin. In your WordPress admin panel, go to Plugins → Installed Plugins, find the Search Atlas plugin, and click Deactivate. 3. Clear all plugin data and cache. After deactivating, click Delete on the Search Atlas plugin. When prompted, confirm that you want to delete the plugin and its data. This removes any locally stored UUID cache or stale configuration tied to the old project. 4. Clear your WordPress site cache. If you are using a caching plugin such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, purge all caches now. Also clear any server-level or CDN cache if applicable. 5. Reinstall the Search Atlas WordPress plugin. Download the latest version of the plugin from your Search Atlas dashboard or the WordPress plugin repository, and install it fresh. 6. Enter the new UUID. During setup, paste the UUID you copied in Step 1 into the plugin's UUID field. Save your settings. 7. Verify the connection. Check that the plugin status shows as connected and that the incorrect UUID error no longer appears. 🔄 If the Error Still Persists In rare cases, the stale backend state may need to be cleared on the Search Atlas side rather than the WordPress side. Try the following additional steps: - Disconnect and reconnect the project. Inside Search Atlas, navigate to your project settings and look for an option to disconnect or reset the WordPress integration, then reconnect it. - Wait 5–10 minutes. After reconnecting, backend cache propagation can take a few minutes. Refresh both the plugin settings page and the Search Atlas dashboard before testing again. - Try a different browser or incognito window. Browser-level caching can sometimes display outdated UUID values. Always confirm the UUID from a fresh session. 🚫 Common Mistakes to Avoid - Do not reuse UUIDs from deleted projects. Each new project generates a unique UUID. The old UUID is permanently invalidated when the project is deleted. - Do not update the UUID without deactivating the plugin first. Simply overwriting the UUID field in an active plugin may not flush the cached value. - Do not skip the cache-clearing step. This is the most frequently missed step and the primary reason the error continues after an apparent fix. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin Authentication Errors

🔍 Overview If your Search Atlas WordPress plugin is showing an authentication error, a login screen after a successful sync, or an API key verification failure, this guide walks you through the most common causes and fixes. Follow the steps in order before reaching out to support. ⚠️ Common Symptoms - Authentication failed or timed out after authorizing the plugin - The plugin dashboard shows a login page even though sync completed successfully - The error message: "The API key could not be verified" - A 500 error appears in the API key authentication popup 🛠️ Step 1 — Regenerate Your API Key An expired or invalid API key is the most frequent cause of authentication failures. To generate a fresh key: 1. Log in to your Search Atlas account. 2. Navigate to Settings → API Keys. 3. Click Generate New Key and copy the key immediately — it will not be shown again. 4. In your WordPress admin panel, go to Search Atlas → Settings. 5. Paste the new API key and click Save. Important: If you previously had an old key saved in the plugin, make sure to fully replace it rather than appending to it. 🔄 Step 2 — Re-Authorize the Plugin Sometimes the plugin loses its connection after a timeout or a platform update. Manually re-authorizing resets the session: 1. In your WordPress admin panel, go to Search Atlas → Settings. 2. Click Disconnect or Log Out if the option is available. 3. Clear any cached credentials by deactivating the plugin, then reactivating it from the Plugins page. 4. Re-enter your API key and complete the authorization flow. 🌐 Step 3 — Check for Server or Hosting Conflicts Some hosting environments block outbound API requests or enforce aggressive caching, which can interrupt authentication. Try the following: - Disable caching plugins temporarily (e.g., WP Rocket, W3 Total Cache) and attempt authentication again. - Check your firewall or WAF rules — ensure requests to Search Atlas API endpoints are not blocked. Ask your hosting provider if outbound HTTPS calls are restricted. - Confirm your PHP version is 7.4 or higher, as older versions can cause unexpected failures during API handshakes. - Increase PHP timeout limits if your server has a very low execution time setting (under 30 seconds). The authentication handshake may time out before completing. 🔁 Step 4 — Update or Reinstall the Plugin Running an outdated version of the Search Atlas plugin can cause compatibility issues with the current API. To update: 1. In your WordPress admin panel, go to Plugins → Installed Plugins. 2. Check if an update is available for Search Atlas and click Update Now. 3. If no update is available but issues persist, deactivate and delete the plugin, then reinstall the latest version from your Search Atlas account or the WordPress plugin directory. 4. After reinstalling, re-enter your API key and re-authorize. 🖥️ Step 5 — Clear Browser and WordPress Cache A cached login state can cause the plugin dashboard to show a login page even after a successful sync. This is a display issue, not an authentication failure: - Clear your browser cache and cookies, then reload the WordPress admin panel. - If you use a caching plugin, purge all cached pages. - Try opening the plugin in a private or incognito browser window to rule out session conflicts. ✅ When Everything Looks Correct but Still Fails If you have completed all the steps above and authentication still fails — especially if a 500 error appears in the authentication popup or regenerating the API key does not resolve the issue — this may indicate a platform-side bug that requires investigation by our engineering 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. When you reach out, please share the following to speed up the resolution: - Your Search Atlas account email - The exact error message or screenshot - Your WordPress version and PHP version - Your hosting provider name - Steps you have already tried from this guide

🔧 Fix a Broken WordPress Contact Form

🧭 Overview If your WordPress contact form suddenly stopped working — especially after a site change, plugin update, or on a specific date — this guide walks you through the most common causes and fixes. If you have already tried troubleshooting before or reported this issue previously without resolution, skip to the Escalate to Our Team section at the bottom. Persistent or account-specific issues require hands-on investigation that goes beyond standard self-service steps. ⚠️ Before You Begin Keep these points in mind before attempting any fixes: - If you have already reported this issue to support and it remains unresolved, do not repeat the same troubleshooting steps. Escalate directly using the instructions at the end of this article. - Note the exact date the form stopped working. A specific break date (such as March 31) often points to a plugin update, hosting change, or server-side configuration change that occurred on or around that day. - Back up your site before making any changes. 🔍 Common Causes of a Broken Contact Form WordPress contact forms most often break due to one of the following reasons: - A plugin conflict — a recently updated or newly installed plugin is interfering with your form plugin. - A caching issue — cached pages are serving outdated form markup or blocking nonce validation, which is a WordPress security token required for form submissions. - A hosting or server change — PHP version updates, mail server configuration changes, or firewall rules can silently break form submissions. - An SSL or HTTPS mismatch — forms submitting over HTTP on an HTTPS site will fail. - Email delivery failure — the form itself may be working, but submission confirmation emails are being blocked or filtered as spam. 🛠️ Troubleshooting Steps Work through these steps in order. After each step, test your form by submitting a test entry. 1. Check for recent plugin or theme updates. Go to your WordPress dashboard and review your update history. If a plugin was updated around the date the form broke, try deactivating it temporarily to see if the form recovers. 2. Clear all caches. Clear your WordPress caching plugin cache, your browser cache, and if your site uses a CDN (such as Cloudflare or BunnyCDN), purge the CDN cache as well. Stale cache is one of the most common causes of form nonce errors. 3. Test with all plugins deactivated. Deactivate every plugin except your form plugin and retest. If the form works, reactivate plugins one at a time to identify the conflict. 4. Switch to a default WordPress theme temporarily. Theme code can interfere with form scripts. Switch to Twenty Twenty-Four or another default theme and test the form 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.

🔧 Fix Recurring 403 Error on WordPress Plugin Sitemap

🛠️ Root Cause The 403 error occurred because the plugin previously generated static sitemap files on disk. On certain server configurations (especially nginx), file permissions or rewrite rules prevented public access to these files after updates, triggering a 403 Forbidden response. 🚀 Permanent Solution The engineering team has released a fix that switches sitemap generation to virtual-only mode with regenerate-on-miss. This eliminates static file writes entirely — sitemaps are now served dynamically via WordPress rewrite rules, bypassing file permission issues. 1. Log in to your WordPress admin dashboard. 2. Navigate to the Plugins page and locate the Search Atlas plugin. 3. If an update is available, click Update Now to install version 2.6.11 or later. 4. After updating, visit your sitemap URL (typically /sitemap.xml) to confirm it loads without a 403 error. No additional configuration is required — the virtual-only mode activates automatically upon update. ✅ Verification Once updated, the sitemap should return a valid XML response with HTTP 200. You can also verify in Google Search Console that the sitemap is fetched successfully. 📋 Related Improvements This fix also resolves related issues where sitemaps returned 404 on the frontend despite showing as generated in admin, and prevents plugin activation from causing 404s on all pages except the home page. 💬 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.

🛠️ Fix Missing WordPress Plugin Element Removal Checkbox

🔍 Overview When managing your website through the Search Atlas WordPress plugin, you may notice that a checkbox previously used to remove a specific plugin element has disappeared. This is a known UI behaviour that occurs under certain conditions. This article explains why it happens and walks you through the steps to restore and use the checkbox successfully. ❓ Why Does the Checkbox Disappear? The element removal checkbox is conditionally displayed based on the current state of your plugin settings and the detected elements on your page. The checkbox may no longer appear if: - The target element has already been removed or is no longer detected on the page. - A settings save or page refresh has caused the UI to re-evaluate which controls are relevant. - The plugin has been updated and the interface has changed slightly. - Your browser has cached an outdated version of the plugin admin panel. 🛠️ How to Restore the Element Removal Checkbox Follow these steps in order to bring the checkbox back and remove the desired plugin element from your website. 1. Clear your browser cache. An outdated cache is the most common cause. In your browser settings, clear cached images and files, then reload the WordPress admin panel. 2. Deactivate and reactivate the Search Atlas plugin. In your WordPress dashboard, go to Plugins > Installed Plugins, deactivate the Search Atlas plugin, wait a few seconds, then reactivate it. This resets the plugin state and often restores missing UI elements. 3. Navigate back to the correct settings screen. Go to the Search Atlas plugin settings page where the element removal option was previously displayed. Some controls only appear when you access the specific sub-section they belong to rather than the top-level settings page. 4. Check whether the element is still present on your site. Visit the front end of your website and confirm the element you want to remove is still visible. If it has already been removed, the checkbox will not appear because there is nothing left to act on. 5. Re-save your plugin settings. On the relevant settings screen, click Save or Save Changes without making any other edits. This forces the plugin to re-evaluate your configuration and redisplay all applicable controls, including the element removal checkbox. 6. Disable conflicting plugins temporarily. Another active plugin may be interfering with the Search Atlas admin interface. Temporarily deactivate other plugins one by one, refreshing the page after each, to identify any conflicts. ✅ Confirming the Element Has Been Removed Once the checkbox is visible again and you have selected it: - Click Save or Save Changes to apply the removal. - Visit the front end of your website in a new private or incognito browser window to confirm the element no longer appears. - If you use a caching plugin (such as WP Rocket or W3 Total Cache), purge your site cache after saving to ensure visitors see the updated version of your pages. 🚫 Still Not Seeing the Checkbox? If you have completed all of the steps above and the element removal checkbox is still missing, it is possible that: - Your version of the Search Atlas plugin is outdated. Go to Plugins > Installed Plugins and check for available updates. - A theme or custom code on your site is hiding the admin panel element. - The feature requires a specific plan or permission level that may not be active on 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.

🛠️ Fix Critical WordPress Plugin Issues Fast

🔍 Why Details Matter When Reporting Plugin Issues When a WordPress plugin stops working correctly, the speed of resolution depends almost entirely on the information you provide upfront. Vague reports such as "the plugin is broken" make it difficult for our team to diagnose the problem, which leads to longer back-and-forth exchanges and slower fixes. This article walks you through exactly what to capture and how to report it effectively. ⚠️ Common Signs of a Critical Plugin Issue Before reaching out, confirm you are experiencing one or more of the following: - The Search Atlas WordPress plugin fails to install, activate, or update - Data is not syncing between your WordPress site and the Search Atlas platform - The plugin causes a white screen, fatal error, or site crash after activation - Settings saved in the plugin are not being retained - The plugin dashboard is blank, missing data, or displays an error message - Conflict with another plugin or theme causes unexpected behavior 📋 Information to Gather Before Reporting Collecting the right details before you contact support dramatically reduces resolution time. Please have the following ready: 1. WordPress version: Found in your WordPress admin under Dashboard → Updates. 2. Search Atlas plugin version: Found under Plugins → Installed Plugins. Note the version number listed beneath the plugin name. 3. PHP version: Found under Tools → Site Health → Info → Server. 4. Exact error message: Copy the full text of any error or warning displayed on screen. Do not paraphrase — the exact wording matters. 5. Steps to reproduce: Write down the precise sequence of actions that trigger the issue (e.g., "I clicked Save Settings, then navigated to the Keyword Tracker tab, and the page went blank"). 6. When it started: Note the date and time the issue first appeared, and whether anything changed around that time (update, new plugin, hosting change). 7. Screenshots or screen recordings: Visual evidence helps our team see exactly what you are seeing. 8. Active plugins list: Go to Plugins → Installed Plugins and note which plugins are active. This helps identify conflicts. 9. Hosting environment: The name of your hosting provider (e.g., WP Engine, SiteGround, Cloudways). 🧪 Quick Troubleshooting Steps to Try First Before escalating, try these steps — they resolve the majority of plugin issues: 1. Deactivate and reactivate the plugin: Go to Plugins → Installed Plugins, deactivate Search Atlas, then reactivate it. 2. Update the plugin: Check for and install any available updates. 3. Clear your cache: Clear both your WordPress site cache and your browser cache, then reload the page. 4. Switch to a default theme: Temporarily switch to a default WordPress theme (e.g., Twenty Twenty-Four) to rule out a theme conflict. 5. Disable other plugins temporarily: Deactivate all plugins except Search Atlas to check for a plugin conflict. Reactivate them one by one to identify the culprit. 6. Check Site Health: Go to Tools → Site Health and review any critical issues flagged by WordPress. 🚀 How to Escalate Effectively If the steps above do not resolve the issue, escalate immediately — but come prepared. When you open a support conversation, include everything from the checklist in the section above. The more specific you are, the faster our team can act. A report that says "After updating to plugin version 3.2.1 on WordPress 6.5, clicking the Sync button on the Content Planner page returns a 500 Internal Server Error. This started on June 10 and my host is WP Engine." will be prioritised and resolved far more quickly than a general report of something being broken. ⏱️ Understanding Escalation Timeouts Our support team follows up on open issues within a set window. If a conversation is escalated as critical but no specific details are provided, the ticket may time out while our team waits for the information needed to investigate. To prevent this: - Respond promptly to any follow-up questions from our team - Include all required details in your very first message - Mark your issue as critical only when it is causing site downtime or complete loss of plugin functionality If your ticket has timed out and your issue is still unresolved, please reopen a conversation and include the full details outlined above. 💬 Contact 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.

🔧 Fix WordPress Plugin "Unable to Sync" Error

Overview The "Unable to sync with your WordPress site" error appears when the Search Atlas plugin cannot establish or maintain a stable connection between your WordPress installation and the Search Atlas platform. This article explains what to check and what information to have ready so our team can resolve your issue as quickly as possible. Before You Begin Confirm the following baseline requirements are met before escalating: - You are using the latest version of the Search Atlas WordPress plugin (check your WordPress dashboard under Plugins → Installed Plugins). - Your WordPress site is publicly accessible (not under maintenance mode or password protection). - Your hosting account is active and your site is loading without errors. What to Try First 1. Deactivate and reactivate the Search Atlas plugin. In your WordPress dashboard, go to Plugins → Installed Plugins, deactivate the Search Atlas plugin, then reactivate it and attempt to sync again. 2. Re-enter your connection credentials. In Search Atlas, disconnect your WordPress site and reconnect it by re-entering your site URL and credentials exactly as required. Make sure there are no extra spaces or typos. 3. Check for plugin conflicts. Temporarily deactivate all other active plugins, then attempt to sync. If syncing succeeds, reactivate your other plugins one at a time to identify which one is causing the conflict. 4. Confirm your site is reachable over HTTPS. Make sure your site loads correctly in a browser without any SSL warnings or certificate errors, as connection issues can prevent syncing. When Contacting Support If the steps above do not resolve the issue, please have the following ready so our team can investigate efficiently: - Your WordPress site URL - The exact error message displayed (a screenshot is helpful) - The version of the Search Atlas plugin you are running - A list of any other active plugins on your WordPress site - The name of your hosting provider If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix WordPress Sync Errors Across Multiple Sites

🧭 Overview If you see a "We're unable to sync with your WordPress site" error when publishing articles from Search Atlas, the cause is usually stale cache data, outdated WordPress plugins, or an OTTO task that needs to be redeployed. This guide walks you through the correct resolution steps in order. 🔌 Step 1: Update Your WordPress Plugins Outdated plugins are a common cause of sync failures, especially after Search Atlas releases platform updates. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Check for any available updates, particularly the Search Atlas or OTTO plugin. 4. Click Update Now for each plugin that has a pending update. 5. Repeat this step for every WordPress site that is showing the sync error. 🗑️ Step 2: Clear Your WordPress Plugin Cache Cache stored by your WordPress caching plugin can block the sync connection even after plugins are updated. 1. Open your caching plugin (for example, WP Rocket, W3 Total Cache, or LiteSpeed Cache) and clear all cached data using the option available in that plugin. 2. Repeat for every site that is experiencing the error. ⚙️ Step 3: Request an OTTO Redeployment After updating plugins and clearing cache, the OTTO task associated with the affected site or article project needs to be redeployed to re-establish a clean connection with your WordPress site. If you are not sure how to trigger an OTTO redeployment for your specific setup, or if the option is not visible in your account, contact our support team directly so they can initiate the redeployment on your behalf. When reaching out, please have the following ready: - The name of the affected WordPress site or project in Search Atlas - The exact error message you are seeing - The approximate date and time the error first occurred - Whether the error is affecting one site or multiple sites ✅ Confirming the Fix After completing all three steps, attempt to publish or sync the affected article again. If the error no longer appears, the issue has been resolved. If you are managing multiple WordPress sites, confirm the fix on each site individually. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

Fix WordPress Admin Bar False Positive Redirects

What Is This Issue? If your Site Auditor report flags pages as containing redirect links — but you inspect those pages and the listed URLs are nowhere to be found — you are likely experiencing a WordPress admin bar false positive. For example, the audit may report that /aim-tools/ contains a link redirecting to /about, but when you view the page in a browser or check its source code, that link does not exist. This is a known issue and does not indicate a real problem with your page content. How to Recognise This Symptom - Site Auditor lists redirect issues on multiple pages across your site. - The flagged URLs (e.g. /about, /wp-admin/, dashboard links) are not present in the visible page content or HTML source. - The same set of redirect URLs appears repeatedly across many different pages. - The flagged links often point to WordPress admin, profile, or navigation destinations. Root Cause: The WordPress Admin Bar When a user is logged into WordPress while a site crawl runs, WordPress automatically renders the admin toolbar at the top of every page. This toolbar contains links to areas such as the dashboard, your profile, site settings, and custom menus. Search Atlas's Site Auditor crawls pages the same way a browser would. If the crawler visits your site while a WordPress session is active, it reads the admin bar as part of each page's HTML. Any redirecting links inside that toolbar get attributed to every page the crawler visits — even though those links are not part of your actual page content. This is not a bug in Site Auditor. The crawler is accurately reporting what it finds in the page HTML. The issue is that the admin bar should not be visible to the crawler at all. How to Fix It Choose one of the following remediation methods based on your setup. Option 1: Ensure the Crawler Visits Pages While Logged Out (Recommended) 1. Log out of your WordPress account completely. 2. Open a private or incognito browser window and confirm the admin bar is no longer visible on your site's front end. 3. Return to Search Atlas and navigate to your project's Site Auditor. 4. Trigger a fresh crawl of your site. 5. Review the crawl results after the crawl completes. The false positives should no longer appear. This is the most reliable fix because it removes the admin bar from the crawled HTML entirely. Option 2: Hide the Admin Bar for Non-Admin Users or Bots If your site must remain logged in during crawls, or if you use a crawl user account, you can suppress the admin bar programmatically. Add the following code to your theme's functions.php file or a site-specific plug If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Connector Gateway Routing Errors

🔍 What Is This Error? If your WordPress connection shows a status of Active but test operations such as wordpress-get-current-user fail with a message indicating the operation is not available for WordPress, you are experiencing a gateway routing error. The connector may appear authenticated correctly, yet the test operation cannot be completed. This is a platform-level issue and cannot be resolved through user-side steps alone. ⚙️ Why Does This Happen? This error occurs at the gateway routing level within the WordPress connector. Even when the connection status shows Active, specific test operations can fail due to a routing problem that is not visible from the connector settings screen. Because the root cause is at the platform level, it requires investigation and action by the Search Atlas team. 📋 What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please gather the following before reaching out: - The exact error message you are seeing (e.g. the full text stating the operation is not available) - The name of the failing operation (e.g. wordpress-get-current-user) - Your WordPress site URL associated with the connector - The date and approximate time when the error first appeared - Any screenshots of the error message or connector status screen If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

SA Plugin Breaking WordPress Navigation Menu

Overview Some WordPress sites experience a navigation menu that becomes fully expanded or visually broken immediately after activating the Search Atlas (SA) plugin. Deactivating the plugin restores the menu, which confirms the plugin is involved. This appears to be a plugin-related conflict, though the exact underlying cause may vary by site configuration. This article explains how to immediately restore your site, steps you can try to resolve the conflict yourself, and how to escalate if self-serve steps do not fully resolve the issue. Is This Your Issue? You are likely experiencing this issue if all of the following are true: - You recently installed or activated the Search Atlas WordPress plugin on a site. - The site's navigation menu is unexpectedly expanded, distorted, or broken in appearance. - Deactivating the SA plugin immediately restores the navigation menu to normal. - Reactivating the plugin causes the problem to return. Self-Serve Steps to Restore Your Site and Resolve the Conflict Follow these steps in order. Many users are able to reduce or resolve the conflict without needing to keep the plugin deactivated. 1. Deactivate the Search Atlas plugin from your WordPress admin panel by going to Plugins → Installed Plugins, locating Search Atlas, and clicking Deactivate. This immediately restores your navigation menu and keeps your site functional for visitors while you troubleshoot. 2. Confirm the fix by visiting your site's front end and verifying the navigation menu appears correctly after deactivation. If it does, the SA plugin is confirmed as contributing to the issue. 3. Check for plugin conflicts by temporarily deactivating all other plugins except Search Atlas, then reactivating them one at a time. If the menu breaks again when a specific plugin is reactivated alongside Search Atlas, that combination is likely the source of the conflict. Note which plugins are active when the problem occurs and include this information if you need to contact support. 4. Switch to a default WordPress theme temporarily (such as Twenty Twenty-Three) to determine whether your active theme is contributing to the conflict. If the menu displays correctly with Search Atlas active and a default theme in use, the conflict may be theme-specific. Contact your theme developer with these findings. 5. Document what you observe — including your theme name, active plugins, and WordPress version — so you can provide full context if you need to escalate. When to Contact Support If you have worked through the steps above and the navigation menu remains broken whenever the Search Atlas plugin is active, please reach out to the Search Atlas support team. Share the details you gathered — your theme, active plugins, and WordPress version — so the team can investigate and escalate to engineering if needed. To get help, use the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin Connection Timeout Issues

🔍 Overview When adding a new project and connecting your WordPress site to Search Atlas, the plugin may time out during installation or fail to authenticate. This article explains what causes the issue and how to resolve it by regenerating your API key and reauthenticating the plugin. ⚠️ What Causes This Issue This timeout or authentication failure typically occurs when the API key used by the WordPress plugin becomes invalid or revoked. This can happen after account changes, reconnection attempts, or a platform update. Once the key is no longer valid, the plugin cannot complete the handshake with Search Atlas, causing it to stall or time out. 🛠️ How to Resolve It 1. Regenerate your API key. Log in to your Search Atlas account and navigate to your account or API settings. Locate your existing API key and regenerate it to create a new, active key. Copy the new key carefully. 2. Reconnect the plugin in WordPress. Log in to your WordPress admin dashboard. Navigate to the Search Atlas plugin settings. Remove or disconnect the existing API key, then enter the newly generated key and save. This reauthenticates the plugin with your Search Atlas account. 3. Test the connection. Once the new key is saved, attempt to complete the project setup in Search Atlas. The plugin should now connect without timing out. 4. Confirm everything is working. Verify that your WordPress project appears correctly in Search Atlas and that the plugin is active and communicating as expected. 💡 Tips to Avoid This in the Future - If you ever revoke or regenerate your API key for any reason, always update it in the WordPress plugin immediately to prevent authentication failures. - Avoid clicking the connect or authenticate button multiple times during setup — repeated attempts can create conflicting key records and worsen the timeout issue. - If the connection fails after a fresh key entry, wait a few minutes before retrying, as key propagation can occasionally take a moment. 🚨 If You Still See a 500 Error In some cases, the authentication popup may return a 500 error even after regenerating the API key. This is a known issue currently being investigated by the engineering team. If regenerating the key does not resolve the problem for you, please do not attempt multiple additional regenerations, as this can make the issue harder to diagnose. If you need further assistance, open 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 Blog Sync Failure Troubleshooting Guide

🔍 What This Error Means When you see the message "We're unable to sync with your WordPress site. Check your configuration or reach out to support", it does not always mean your WordPress setup is misconfigured. In many cases, the issue is caused by a temporary platform-side problem — not something you have done wrong. Past incidents have been traced to an invalid or expired API key on the Search Atlas side, which blocks the publish-to-WordPress process entirely. Our engineering team has resolved multiple occurrences of this and continues to monitor for recurrences. ✅ Step 1: Confirm Your WordPress Connection Is Healthy Before assuming a platform issue, verify that your WordPress environment is set up correctly: - Log in to your WordPress admin dashboard and confirm the MetaSync plugin is installed and active. The current supported version is v2.6.10 or later. - Check that your WordPress REST API is accessible and not blocked by a security plugin or firewall rule. A rest_forbidden error in your browser console or server logs indicates a permissions or plugin conflict on the WordPress side. - Confirm that the user account connected to Search Atlas has sufficient permissions to publish posts via the REST API. 🔄 Step 2: Try a Hard Refresh If your connection looks healthy, perform a hard refresh of the Search Atlas platform in your browser (typically Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and attempt the sync again. This rules out a stale browser session as the cause. 📝 Step 3: Retry Publishing From Content Genius Navigate to Left sidebar → Content → Content Genius and attempt to publish or sync your article again. If the error persists after a hard refresh and the MetaSync plugin is confirmed active, the issue is likely on the platform side rather than your configuration. ⚙️ Step 4: Understand Platform-Side Causes Several known platform-side issues can trigger this error message: - Invalid or expired API key — An internal API key used by Search Atlas to communicate with WordPress becomes invalid, blocking all publish requests with a 400 error. This has been the root cause in multiple incidents and is resolved by our engineering team without any action required from you. - Empty response from WordPress — In some cases, WordPress returns an empty response body, causing a processing error on the Search Atlas side. This is also handled internally. - Temporary service disruption — Occasionally, a broader platform issue affects multiple users simultaneously. Our team monitors for these and deploys fixes as quickly as possible. None of these causes require changes to your WordPress site or MetaSync plugin when your configuration is confirmed healthy. 🛠️ Step 5: What To Do If the Error Persists If you have confirmed that your MetaSync plugin is active and your WordPress permissions are correct, and the sync still fails after retrying: 1. Note the exact error message displayed on screen. 2. Record the date and time you experienced the failure. 3. Check whether other team members on your account are experiencing the same issue — this helps confirm whether it is account-specific or platform-wide. 4. Contact our support team using the instructions below so we can investigate your account directly and file an internal ticket if needed. 💡 Key Things To Remember - A sync failure error does not always mean your WordPress or plugin configuration is broken. - Hard-refreshing the platform does not resolve platform-side API key issues — only our engineering team can do that. - The MetaSync plugin must be version v2.6.10 or later for compatibility. - REST API access must be enabled and not blocked by WordPress security settings. 💬 Still Seeing the Error? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress CMS Sync Failures

🔍 What This Article Covers If you have connected WordPress to Search Atlas and your content is not publishing or syncing correctly, this guide will walk you through the most common causes and the exact steps to resolve them. We will also explain how to escalate to our engineering team if standard troubleshooting does not fix the problem. ⚙️ How WordPress CMS Sync Works Search Atlas connects to your WordPress site through the Search Atlas plugin. When you publish or update content from Content Genius (Left sidebar → Content → Content Genius), Search Atlas sends that content to WordPress using an authenticated connection. If that connection breaks or WordPress rejects the request, the sync fails and your changes will not appear on your site. ⚠️ Common Reasons Sync Fails WordPress sync issues typically fall into one of these categories: - Plugin authentication failure — The connection token between Search Atlas and your WordPress site has expired or was revoked. - WordPress plugin outdated — You are running an older version of the Search Atlas plugin that is no longer compatible. - Security plugin blocking requests — A firewall, security plugin, or server-level rule is blocking Search Atlas API requests. - Missing or changed credentials — Your WordPress admin password, application password, or site URL has changed since the initial connection. - Server timeout or resource limits — Your WordPress server is rejecting long-running requests, which can happen with large articles or bulk publishing. 🚀 Step-by-Step Troubleshooting Follow these steps in order. After each step, try syncing a single article to see if the issue is resolved. 1. Verify your WordPress site URL — In Search Atlas, go to your CMS connection settings and confirm the site URL matches exactly what you see in your browser, including https:// and no trailing slash. 2. Update the Search Atlas plugin — Log in to your WordPress admin dashboard, navigate to Plugins, and make sure the Search Atlas plugin is updated to the latest version. If an update is available, install it and reconnect. 3. Re-authenticate the connection — Disconnect WordPress from within Search Atlas, then reconnect it fresh. This generates a new authentication token and resolves most stale-credential issues. 4. Check for security plugin interference — Temporarily disable any WordPress security or firewall plugins (such as Wordfence, Sucuri, or Cloudflare WAF), then attempt a sync. If it succeeds, whitelist the Search Atlas plugin or API endpoints in your security tool. 5. Test with a simple article — Create a short test article in Content Genius and try publishing it. If a simple article publishes but a larger one does not, the issue is likely a server timeout. Contact your hosting provider to increase PHP max_execution_time and memory_limit. 6. Check WordPress permalinks — In WordPress admin, go to Settings → Permalinks and click Save Changes even if you have not modified anything. This refreshes WordPress rewrite rules and can resolve hidden routing issues. 📊 How to Confirm Sync Is Actually Working After completing the troubleshooting steps, do not rely solely on the success message inside Search Atlas. Open your WordPress site in a new browser tab and verify that: - The article appears in your WordPress Posts or Pages list. - The title, body content, and meta description match what you published. - The published date and author are correct. - Any images or media included in the article uploaded successfully. If Search Atlas shows a success message but the content is missing or incomplete in WordPress, the sync is partially failing. Proceed to the escalation steps below. 💡 What We Fixed Recently Our engineering team has resolved several known issues related to WordPress sync. If you experienced problems in the past and were told they were fixed but the issue persists, it is possible that a different root cause is now in play. Recent fixes include: - Plugin authentication failures that prevented Content Genius and Content Sync from connecting to WordPress independently of OTTO. - Silent sync failures — the system previously did not always surface errors when a sync failed. It now reports failures clearly so you and our team can act on them. - Brand Vault errors — some sync attempts failed with "No brand vault found" due to a data configuration issue. This has been corrected. Because multiple issues shared similar error messages, it was possible for one fix to resolve your case while a separate, underlying issue remained. If you are still seeing problems, the fastest path to resolution is the escalation process below. 🛠️ Escalating to Engineering If you have completed every troubleshooting step above and WordPress sync is still not working, our engineering team needs specific information to investigate efficiently. When you contact support, provide the following: - Your WordPress site URL. - The version of the Search Atlas plugin installed on your WordPress site. - The exact name of the article or articles that failed to sync. - The date and time (including your timezone) of the most recent failed sync attempt. - A screenshot of any error message you see, either in Search Atlas or in WordPress. - The name of any security plugins running on your WordPress site. With this information, our team can trace the exact request, identify where it is failing, and push a fix or configuration change. 💬 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.

Fix WordPress Plugin Connection and Missing Meta Data

🔍 Overview If your WordPress plugin appears connected in Search Atlas but keeps reverting to Disconnected, or your blog pages are missing meta titles and descriptions, you are likely experiencing a known sync issue between the Search Atlas platform and the WordPress plugin. This article explains what causes the problem and what to do next. ⚠️ Why This Happens There are two related issues that can occur together or independently: - False "Connected" status: Search Atlas may display your WordPress connector as Connected even when the plugin has been deactivated, uninstalled, or is failing. The platform does not always re-validate the live plugin state in real time. - Missing meta data: Because the connection status is not accurate, meta titles and descriptions that should be synced from your WordPress pages may not appear in Search Atlas — even though everything looks fine on the surface. 🛠️ What to Expect This is a known bug that may require investigation and action from our support team. The connection reverting and missing meta data issues are related and typically need to be resolved on the backend. Our team will need to look into the specific state of your WordPress connector to identify the root cause and apply a fix. 📋 What to Have Ready When You Contact Support Please reach out and have the following information ready so we can investigate quickly: - Your project name in Search Atlas - The WordPress site URL associated with the connector - The exact status message shown in your connector settings (e.g. "Connected", "Disconnected", or any error text) - A description of which pages are missing meta titles or descriptions - Approximately when the issue started or when you first noticed the status reverting If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix WordPress CMS Sync Still Failing

What Is Happening Your WordPress CMS sync may stop working again even after a previous support ticket was marked as solved. This is a known recurring issue where the sync appears resolved but continues to fail silently. Because the root cause requires investigation on the backend, this is not something that can be fully resolved through self-serve steps alone. What to Expect Our team will need to look into your specific account and WordPress connection to identify why the sync is failing again. The issue may be related to authentication, a connector state, or a backend configuration — but confirming the exact cause requires access to your account data. How to Escalate Effectively To help our team resolve this as quickly as possible, please have the following ready when you reach out: - The name of the WordPress site or project affected by the sync failure. - Any error message you are seeing, copied exactly as it appears. - The date and approximate time when the sync stopped working again. - Confirmation of whether the issue started immediately after the previous ticket was closed or after some time had passed. - Your Search Atlas account login details. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Content Deployment Sync Failures via AI Agent

🔍 Overview When deploying content to WordPress sites through the Search Atlas AI Agent, you may receive a "deployed" confirmation but find that no new pages or posts appear in your WordPress admin dashboard. This article explains why this happens and walks you through the steps to verify your deployment and get your content live. ⚠️ Why This Happens Several known issues can cause the AI Agent to report a successful deployment when content has not actually been published to WordPress: - The AI Agent may confirm deployment without verifying whether the content is live on your site. - An incorrect or duplicate WordPress connection link may be used, bypassing your existing CMS connector. - WordPress cache is not purged after deployment, making it appear as though no content was published even when it was. - Metadata fields such as category and author may be silently ignored during publishing, causing the post to fail validation or save in an unexpected state. - HTML heading styles may not be applied correctly, which can affect how content is saved or rendered in certain page builders such as Elementor. ✅ Step-by-Step: Verify and Resolve Your Deployment 1. Check your WordPress admin dashboard directly. Log in to each affected WordPress site and navigate to Posts or Pages. Filter by All statuses, including Draft and Pending, to confirm whether the content exists in any state. 2. Check your CMS connector in Search Atlas. Go to your Account Menu → Settings → CMS Connectors and confirm that the correct WordPress site is connected. If a duplicate or incorrect connection exists, remove it and reconnect using the official connector. 3. Purge your WordPress cache manually. If your site uses a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), navigate to the plugin settings and clear the cache. Then reload your WordPress admin to check for new content. 4. Re-deploy the content through the AI Agent. After confirming your CMS connector is correct and your cache is cleared, return to the AI Agent and redeploy the affected pages or posts. Watch for any error messages during the process. 5. Verify category and author assignment. After deployment, open each newly created post in WordPress and confirm that the correct author and category have been assigned. If these fields are blank, update them manually or adjust your deployment settings before re-publishing. 6. Review heading styles if using Elementor. If your site uses Elementor, open the deployed content in the Elementor editor and check that headings (H1, H2, H3) are rendering correctly. Re-apply heading styles if needed before publishing through Elementor. 🔗 Reconnect Your WordPress CMS Connector If the steps above do not resolve the issue, your WordPress connection may need to be reset entirely. Follow these steps: 1. In Search Atlas, navigate to Settings and open the CMS Connectors section. 2. Locate the affected WordPress site and select Disconnect. 3. Re-add the site using the correct WordPress URL and authentication credentials. 4. Test the connection by deploying a single piece of content before attempting a bulk deployment. 💡 Best Practices to Prevent Future Sync Failures - Always verify content in your WordPress admin after deployment, especially for bulk publish operations. - Limit bulk deployments to small batches (three to five posts at a time) until you have confirmed the connection is stable. - Clear your WordPress cache after every deployment session. - Ensure that category IDs and author IDs exist in WordPress before deploying content that references them. - If you use a page builder such as Elementor, test a single post deployment first to confirm compatibility before publishing at scale. 🆘 Still Seeing the Issue? If you have followed all the steps above and your content still does not appear in WordPress after deployment, our team can investigate your specific connector configuration and deployment logs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Troubleshooting Yoast SEO Fields Missing After Search Atlas Plugin Install

This article explains why Yoast SEO fields may disappear or become inaccessible after installing the Search Atlas WordPress plugin, and walks you through the steps to restore full Yoast functionality including indexing controls. 🔍 Common Causes When the Search Atlas plugin is activated alongside Yoast SEO, the following issues can cause fields to go missing: - Plugin conflict: Both plugins may attempt to control the same meta fields or SEO output, causing one to suppress the other's interface elements. - OTTO SEO activation: If OTTO SEO features are enabled within Search Atlas, they may take over on-page SEO management, which can hide or override Yoast's meta fields in the post editor. - Script or asset loading conflict: The Search Atlas plugin may interfere with how Yoast loads its editor sidebar components in WordPress. 🛠️ Step-by-Step 1. Check whether OTTO SEO is active for your site. Inside your Search Atlas project, open your site's settings and look for an OTTO SEO section. If OTTO SEO is currently enabled and managing on-page SEO for your WordPress site, it may be intentionally suppressing Yoast fields to avoid conflicts. Decide which tool you want to manage on-page SEO — you should only run one at a time. 2. Disable OTTO SEO on-page control if you prefer Yoast. In your Search Atlas project settings, locate the OTTO SEO configuration area and turn off any option that pushes meta tags, titles, or indexing directives directly to your WordPress site. Save your changes. 3. Deactivate and reactivate the Search Atlas plugin in WordPress. In your WordPress admin panel, go to Plugins → Installed Plugins, deactivate the Search Atlas plugin, then reactivate it. This forces both plugins to reinitialise and can resolve asset loading conflicts. 4. Check Yoast SEO plugin status. Still in Plugins → Installed Plugins, confirm that Yoast SEO is active and up to date. If a pending update is available, apply it before testing further. 5. Open a post or page in the WordPress block editor. Navigate to Posts → All Posts (or Pages), open any existing entry, and check whether the Yoast SEO sidebar panel now appears on the right-hand side or at the bottom of the editor screen. 6. Restore indexing control in Yoast if fields are visible again. Within the Yoast SEO panel on a post or page, click the Advanced tab to access the robots meta settings. Confirm that your preferred indexing directives (index/noindex, follow/nofollow) are set correctly for each page type you need to control. 7. If fields are still missing, test with only Yoast SEO active. Temporarily deactivate the Search Atlas plugin and reload the post editor. If Yoast fields reappear, this confirms a direct plugin conflict. Re-enable Search Atlas and contact support to report the specific pairing so the team can investigate further. ✅ How to Confirm It Worked You will know the issue is resolved when all of the following are true: - The Yoast SEO meta box or sidebar panel is visible when editing a post or page in WordPress — it should display tabs for SEO, Readability, and (if applicable) Schema and Social. - The Advanced tab inside the Yoast SEO panel shows the robots meta dropdown, allowing you to set indexing and follow directives without the field being greyed out or hidden. - Changes you save in Yoast (such as a custom meta title or a noindex instruction) are reflected correctly when you inspect the page source or use a browser SEO extension — confirm the relevant tag appears in the page with your intended value. - No duplicate or conflicting robots meta tags appear in the page source that would indicate both Yoast and OTTO SEO are outputting directives simultaneously. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress Plugin Disconnection and Deployment Sync Failures

🔍 Overview If your Search Atlas WordPress plugin icon is showing red, or your OTTO SEO deployments are not saving or persisting to your WordPress site, this guide walks you through the most common causes and how to fix them quickly. ⚠️ Why Is the WordPress Plugin Showing Red? A red plugin status means Search Atlas has lost its authenticated connection to your WordPress site. This is usually caused by one of the following: - A WordPress core, plugin, or theme update that reset REST API permissions - A security plugin (such as Wordfence or iThemes Security) blocking the Search Atlas REST API route - A hosting-level firewall or CDN rule interfering with authentication requests - An expired or revoked application password on the WordPress side - A caching layer serving stale authentication responses 🛠️ How to Reconnect the WordPress Plugin 1. Log in to your Search Atlas account and navigate to Settings > Integrations > WordPress. 2. Locate the disconnected site. You will see a red indicator next to the connector. 3. Click Reconnect and follow the on-screen authentication prompts. 4. When redirected to your WordPress admin, confirm that the Search Atlas application password is active under Users > Your Profile > Application Passwords. If you see an old or duplicate entry, revoke it and allow Search Atlas to generate a new one. 5. Return to Search Atlas and verify the connector status has changed to green (connected). 6. If the status still shows red after reconnecting, clear any full-page or object caches on your WordPress site (via your caching plugin or hosting control panel) and attempt reconnection again. Tip: If you use a security plugin, temporarily disable it during reconnection and then add the Search Atlas REST API route (/wp-json/search-atlas/) to the allowlist before re-enabling it. 💾 Why Won't My Deployment Save or Persist? Even after a successful reconnection, some customers find that OTTO SEO deployments — such as Knowledge Based Trust and Factual Enhancement optimisations — appear to save in the platform but do not persist on the live WordPress site. This is a sync issue between Search Atlas and your CMS. Common reasons this happens include: - The WordPress connector was reconnected but the CMS sync was not re-enabled for the project - A REST API route error prevented the deployment payload from being written to WordPress - A caching or CDN layer returned a cached version of the page, making it appear the changes were not applied - The WordPress user account linked to the connector has insufficient permissions (must be Administrator role) ✅ How to Fix Deployment Sync Failures 1. Confirm your WordPress connector is showing green in Settings > Integrations > WordPress. If it is not, complete the reconnection steps above first. 2. In Search Atlas, open your OTTO SEO project and navigate to the deployment in question (e.g., Knowledge Based Trust and Factual Enhancement Issues). 3. Check that CMS Sync is toggled on for the project. If this setting was off, enable it and re-deploy. 4. Click Deploy again. Wait at least 60 seconds before checking your live site, as sync operations can take a short time to propagate. 5. Purge all caches on your WordPress site — including page cache, object cache, and any CDN cache — then reload the page to confirm the changes are live. 6. Verify the WordPress account used in the connector has Administrator privileges. Go to WordPress Admin > Users and confirm the role assigned to the connected account. 7. If you still see a wp_client_error in the platform after following these steps, check your hosting provider's error logs for blocked REST API requests and whitelist the Search Atlas IP range if required. 🚫 Common Mistakes to Avoid - Do not revoke the Search Atlas application password manually unless you intend to fully reconnect — doing so will immediately break the sync. - Do not assume a green connector status means sync is active. Always verify the CMS Sync toggle is enabled at the project level. - Do not check for deployed changes before clearing your cache — cached pages will always show the old content. 💬 Still Need Help? If you have followed all of the steps above and the plugin is still disconnected or deployments are still not persisting, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔐 Fix WordPress Plugin Password Reset Email Failures

🧩 Overview The Search Atlas WordPress plugin includes a white-label (WL) protection feature that lets you password-protect your plugin settings from end clients. If you set a white-label password without configuring a recovery email, or if your server's mail function is misconfigured, the password reset email may fail silently — leaving you locked out with no error message. This article explains why this happens, how to regain access, and what information to provide if you need our team to investigate your installation. ⚠️ Why the Password Reset Email Fails The password reset function inside the WordPress plugin requires a valid sender email address to dispatch the recovery message. When no sender email is configured — or when your WordPress hosting environment has a restricted or broken wp_mail() setup — the system silently drops the email without showing you an error. Common causes include: - No recovery email was entered when the white-label password was first created - Your WordPress hosting provider blocks outgoing mail from the server - A third-party SMTP plugin is misconfigured or conflicting - The sender from_email value is empty or invalid in your WordPress settings Note: Our engineering team is actively working on replacing the current password reset flow with a single-use recovery link to eliminate this issue in a future release. 🛠️ How to Recover Access to White-Label Settings Follow these steps in order to regain access as quickly as possible. 1. Check your recovery email inbox and spam folder. If a recovery email was configured, the reset message may have landed in spam or been delayed by your mail server. 2. Verify your WordPress mail setup. Install a plugin such as WP Mail SMTP to confirm that your site can send email at all. Send a test email from Settings → WP Mail SMTP → Tools → Email Test. 3. Check your SMTP credentials. If you use a third-party SMTP service (Gmail, SendGrid, Mailgun, etc.), confirm the credentials are correct and the connection is active. 4. Ensure a valid From address is set. Go to Settings → General in WordPress and confirm the Administration Email Address field contains a real, deliverable address. This value is used as the sender when no custom from_email is defined. 5. Retry the password reset from the white-label login screen once your mail configuration is confirmed working. 🔑 If You Are Still Locked Out If the steps above do not restore access, our support team can investigate your installation directly. To do this, you will need to grant temporary access to your WordPress site. Please prepare the following before contacting support: - A temporary WordPress Administrator account created specifically for our team — do not share your own credentials - The WordPress admin URL (e.g., https://yoursite.com/wp-admin) - The username and password for the temporary account - A brief description of when the issue started and any error messages you have seen How to create a temporary admin account: 1. Log in to your WordPress dashboard. 2. Go to Users → Add New. 3. Enter a username (e.g., searchatlas-support) and a secure temporary password. 4. Set the role to Administrator. 5. Click Add New User to save. Once our team has resolved the issue, delete this temporary account immediately from Users → All Users. ✅ How to Prevent This Issue in the Future - Always enter a valid recovery email address before saving a white-label password in the plugin settings. - Test your WordPress mail function regularly using a dedicated SMTP plugin. - Keep the Search Atlas WordPress plugin updated so you receive the upcoming single-use recovery link improvement as soon as it is released. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔒 WordPress Plugin 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.

🔄 Fix WordPress CMS Sync Toggle Errors

🔍 Overview When connecting your WordPress site to Search Atlas via the CMS sync toggle, you may encounter a stuck loading circle, a "No WP website found" error, or a generic sync failure. This article walks you through the most common causes and how to resolve them step by step. ⚙️ Prerequisites Before You Begin The CMS sync feature only works with WordPress sites that have the official Search Atlas WordPress plugin installed and activated. Before troubleshooting, confirm the following: - The Search Atlas WordPress plugin is installed and active on your WordPress site. - The domain you are trying to sync exactly matches the domain registered in your Search Atlas project (including or excluding www). - Your WordPress site is publicly reachable and not in maintenance mode, staging lockdown, or behind a firewall that blocks external API requests. 🛠️ Step 1 — Verify the Plugin Is Installed Correctly 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Confirm the Search Atlas plugin is listed and its status shows Active. 4. If the plugin is deactivated, click Activate and wait 30 seconds before retrying the sync in Search Atlas. 5. If the plugin is not installed, download it from your Search Atlas account, upload it via Plugins → Add New → Upload Plugin, and activate it. 🔗 Step 2 — Check Your Project Domain Matches 1. In Search Atlas, navigate to your project settings and note the exact domain listed (e.g., hoardrescue.com vs. www.hoardrescue.com). 2. Compare this to the domain shown in your WordPress admin under Settings → General → Site Address (URL). 3. If there is a mismatch, update the domain in your Search Atlas project to match WordPress exactly, or adjust the WordPress site URL accordingly. 😴 Step 3 — Reactivate a Sleeping Project If your Search Atlas project has been inactive for an extended period, it may have been put to sleep automatically. A sleeping project cannot complete a CMS sync and will return a generic error or leave the toggle stuck on loading. 1. Open Search Atlas and go to the Home page via the left sidebar. 2. Locate your project and click Refresh data to wake it. 3. Wait up to two minutes for the project to fully reload. 4. Return to the CMS sync toggle and try again. 🔄 Step 4 — Retry the CMS Sync Toggle 1. Navigate to your project in Search Atlas. 2. Locate the Sync to CMS toggle. 3. If the toggle is stuck on a loading circle, refresh the entire page using your browser (do not just click the toggle again). 4. After the page reloads, click the toggle once and wait up to 60 seconds for the connection to establish. 5. A successful sync will turn the toggle green and display a confirmation message. 🚫 Common Error Messages and What They Mean - "No WP website found" — Search Atlas cannot detect the plugin on your domain. Re-check that the plugin is active and the domain matches exactly. - Generic sync error / no message shown — This is often caused by a sleeping project or a temporary server timeout. Follow Step 3 to wake your project, then retry. - Toggle spins indefinitely — A page refresh usually resolves this. If it persists after refreshing and retrying, the issue may require investigation by our team. ✅ Quick Checklist - Search Atlas plugin installed and active in WordPress - Domain in Search Atlas project exactly matches WordPress site URL - WordPress site is publicly accessible (not in maintenance or staging mode) - Project is not sleeping — refresh data if unsure - Page was refreshed before retrying the toggle 💬 Still Having Trouble? If you have completed all the steps above and the sync toggle is still failing or stuck, our team can investigate your specific domain and 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.

🔧 Fix WordPress Reconnection Failures and Understand Credits

Overview Two common questions arise together: your WordPress site shows as disconnected in Search Atlas despite the plugin being active, and you want to understand how credits work across your account. This article explains what to expect and what information to have ready so our team can resolve both issues for you as quickly as possible. Why Your WordPress Site May Show as Disconnected A known issue can cause the Search Atlas dashboard to display an incorrect or outdated connection status for your WordPress site. The connector may show a disconnected state even after you have attempted to reconnect the plugin, or the status may not update as expected. Because this issue involves backend work, it typically requires a member of our team to investigate and correct the connection. Common symptoms include: - Your WordPress site appears disconnected in the dashboard even though the plugin is active. - Reconnection attempts do not resolve the displayed status. What to Have Ready When You Escalate Because resolving a WordPress reconnection failure requires a backend action by our team, please have the following information ready before reaching out: - Your site URL — the exact WordPress site address shown in your Search Atlas account. - Your Search Atlas account username or login. - A description of what you have already tried — for example, whether you have deactivated and reactivated the plugin in your WordPress admin panel. - Any error messages displayed — copy the exact wording of any error codes or status messages you see on screen. - Timestamps — when the disconnection was first noticed and when any reconnection attempts were made. How Credits Work in Search Atlas If you have questions about how your credits are managed within your account, our support team can review your specific account details and provide a clear breakdown. Please have your account login ready to share with our team when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ WordPress Plugin Timeout Behind Cloudflare (Manual Installation Fix)

If you're getting a timeout error while installing the Search Atlas WordPress plugin behind Cloudflare, this guide walks you through the working fix. 🚨 The Problem A user attempting to install the Search Atlas plugin experienced a timeout error, even though the server was behind Cloudflare, external calls were allowed, no IP restrictions were configured, all other WordPress plugins were disabled, and cache had been cleared. Despite standard troubleshooting, the timeout persisted. 🧠 Why This Happens When your WordPress server is behind Cloudflare (or another CDN, WAF, or security layer), automated API calls during plugin setup may fail because the inbound callback the plugin relies on to complete authentication gets silently blocked — by a Cloudflare WAF rule, "I'm under attack" mode, an IP allowlist, or a "coming soon" page. Even with no explicit IP restrictions visible to you, the automated setup can still fail silently this way. ✅ The Working Solution: Manual Plugin Connection Instead of relying on automatic setup, manually connect the plugin using your API credentials. Step 1 — Open the Search Atlas Plugin in WordPress. In your WordPress dashboard, go to WordPress Admin → Search Atlas Plugin → Settings. Step 2 — Paste Your API Key. In the API Key field, paste your assigned API key and save. Step 3 — Add the OTTO Pixel UUID. Below the API Key field, paste the provided UUID into the OTTO Pixel UUID field and save. Step 4 — Purge All Caches. This is critical: clear your WordPress cache, server cache, Cloudflare cache, and any object caching layers, then wait 30–60 seconds. Step 5 — Click Sync. After clearing cache, click Sync Plugin. If successful, the plugin will connect and your dashboard will load normally. 🔑 Where to Find Your UUID and API Key in Search Atlas Your UUID is embedded inside your OTTO Pixel script. Navigate to Left Sidebar → OTTO SEO → All Sites, select your project, then open its Installation Guide → Custom Installation. Under Step 1: Copy Your Pixel Script, you'll see a script block with your OTTO pixel — inside the script tag, look for a data-uuid attribute set to a value such as 87a7de3c-6f0e-4269-8518-df74976bb97c. That value is your UUID. It's unique per project, used to identify your OTTO installation, and automatically generated. Custom Installation page showing the OTTO Pixel script Your API Key is located in account-level settings. Navigate to Top Right → Click your Profile Name → Settings → API Keys. You'll see a section titled Search Atlas API Key with a long alphanumeric key. That is your API Key. It's account-level (not project-specific), used for integrations and external connections, and sensitive — do not share it publicly. API Keys panel in account settings ⚠️ Important Difference The UUID is found in the OTTO Installation Guide, is project-specific, and is used for pixel installation — it appears inside a script tag. The API Key is found in Account Settings, is account-level, and is used for API integrations — it's listed under the API Keys panel. 🎉 Expected Result You should now see your Search Atlas dashboard, confirm the plugin shows as connected, and no longer receive timeout errors. 🛠 If It Still Doesn't Work Check PHP memory limits, max_execution_time, firewall or WAF rules, and CDN request timeout settings. If needed, escalate to support with a short screen recording, server environment details, and hosting provider information. If you're running WordPress behind Cloudflare or another CDN and seeing timeouts, manual setup is the fastest resolution path. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress CMS Sync False Detection Error

🔍 What Is This Error? When you attempt to sync content to your WordPress site through Search Atlas, you may see a message stating "No WordPress website found" even though the Search Atlas WordPress plugin is installed and active. This false detection error can also cause your PR Distribution job to stall at 50% progress. This is a known issue currently being resolved by our engineering team. In the meantime, follow the steps below to get your sync working again. ✅ Step 1: Verify the Plugin Is Installed and Active 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins → Installed Plugins. 3. Confirm the Search Atlas plugin is listed and its status shows Active. 4. If the plugin is deactivated, click Activate and wait a few seconds before retrying the sync. 🔑 Step 2: Re-Authenticate the Plugin Authentication issues between the plugin and your Search Atlas account are a common cause of false detection errors. Follow these steps to refresh the connection: 1. Inside your WordPress admin, open the Search Atlas plugin settings page. 2. Disconnect and then reconnect your Search Atlas account by re-entering your API credentials or re-authorising via the provided login flow. 3. Save the settings and confirm the plugin shows a connected status. ⚙️ Step 3: Retry the CMS Sync in Search Atlas 1. Go to OTTO SEO → SEO Automation (All Sites) in the left sidebar (or navigate to /seo-automation-v3). 2. Locate the page or task where the sync failed. 3. Toggle Sync to CMS off, wait five seconds, then toggle it back on. 4. Monitor the progress indicator. The sync should now advance past the point where it previously stalled. 📋 Step 4: Check for PR Distribution Job Stalls If your PR Distribution job is stuck at 50% progress, this is directly linked to the CMS sync failure. Once the sync error is resolved using the steps above, the job should resume automatically. If it does not resume within a few minutes: - Refresh the page and check the job status again. - If the job remains at 50%, cancel it, resolve the sync issue first, and then resubmit the PR Distribution job. 🚫 Common Mistakes to Avoid - Do not install duplicate versions of the Search Atlas plugin — remove any older copies before reinstalling. - Do not use a caching plugin that may block the plugin's authentication requests. Temporarily disable caching and retry if issues persist. - Ensure your WordPress site is publicly accessible and not in maintenance mode, as Search Atlas cannot detect a site that is offline or behind a maintenance screen. - Confirm your WordPress site URL in Search Atlas exactly matches your actual site URL, including whether it uses www or not, and http vs https. 💡 Why Does This Happen? The false detection error occurs when Search Atlas is unable to receive a valid response from your WordPress plugin during the connection check. This can be caused by plugin authentication timeouts, URL mismatches, server configuration issues, or a temporary bug in the sync process. Our team has already shipped fixes for several cases of this error, and further improvements are in active development. 🆘 Still Seeing the Error? If you have followed all the steps above and the CMS sync still fails, our team can investigate your specific site configuration 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. When you reach out, please have the following ready to speed up the investigation: - Your WordPress site URL as entered in Search Atlas - A screenshot of the error message and the plugin settings page - The name of any caching or security plugins active on your site

🔌 Fix WordPress Plugin Authentication and Sync Errors

🔍 Overview Some users experience errors when connecting the OTTO WordPress plugin to Search Atlas or when publishing and syncing content. Common symptoms include a persistent "API key could not be verified" warning, a 500 Internal Server Error during authentication, or articles failing to publish with an error shown in the Search Atlas dashboard. These issues are typically caused by backend authentication conflicts or plugin configuration problems that can often be resolved by following the steps below. 🛠️ Step 1 — Clear All Caches Cached data is one of the most common causes of plugin authentication failures. Before anything else: 1. Clear your WordPress site cache completely, including any caching plugins (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache). 2. Clear your browser cache and perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). 3. If you use a CDN (such as Cloudflare), purge the CDN cache as well. 🔄 Step 2 — Reinstall and Reauthenticate the Plugin If clearing the cache does not resolve the issue, reinstall the OTTO WordPress plugin and reconnect it to your Search Atlas account: 1. In your WordPress admin panel, deactivate and delete the existing OTTO plugin. 2. Download the latest version of the plugin from Search Atlas and reinstall it. 3. Generate a fresh API key from your Search Atlas account settings and enter it in the plugin's authentication field. 4. Save your settings and test the connection again. Important: If you previously generated an API key using the V2 key generation flow, generate a new key and use that instead, as older keys may no longer authenticate correctly with the plugin. ⚙️ Step 3 — Redeploy the OTTO Task If authentication succeeds but content still fails to sync or publish, try redeploying your OTTO task. Navigate to Left sidebar → OTTO SEO → Overview and trigger a new scan or redeploy for the affected site. This refreshes the connection between OTTO and your WordPress installation. 📊 Step 4 — Verify Your Plugin Version Running an outdated version of the OTTO WordPress plugin can cause authentication and sync failures. Confirm that you are using the latest available version. If an update is available in your WordPress dashboard, apply it before retesting. 🚨 When These Steps Do Not Work The authentication and sync errors described in this article have, in some cases, been caused by backend issues on the Search Atlas side. Engineering teams have previously deployed fixes for: - API key validation failures returning a 400 INVALID_ARGUMENT error that blocks WordPress publishing. - The WordPress connector appearing grayed out or returning a wp_client_error on sync even after a successful reconnect. - 500 Internal Server Error responses during plugin authentication. If you have completed all the steps above and the issue persists, this may indicate a backend problem that requires engineering investigation. In that case, do not continue retrying — escalate promptly so the team can identify and resolve the root cause. 💬 Contact 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. To help the team investigate quickly, have the following ready before you reach out: - A screen recording (such as a Jam recording) showing the error you are experiencing. - The exact error message displayed in Search Atlas or WordPress. - Your WordPress site URL and the plugin version you have installed.

🛠️ Fix WordPress Plugin Fatal Errors and OTTO Pixel Alerts

🔍 Overview Some customers encounter a fatal error when activating the Search Atlas WordPress plugin, or see an alert after adding the OTTO pixel snippet to their theme header. This article explains the most common causes and how to fix them so you can connect your site and start using OTTO SEO. ⚠️ Fatal Error on Plugin Activation If you see a message like "Plugin could not be activated because it triggered a fatal error", the most common causes are: - PHP version incompatibility — The plugin requires PHP 8.0 or higher. PHP 7.4 (including 7.4.33) is no longer supported and will cause a fatal error on activation. - Outdated plugin version — Versions prior to 2.6.11 contain a known bug involving an undefined constant that triggers a fatal on activation. - Conflict with page builder themes — Certain themes such as Divi can trigger HTTP render fatal errors due to a conflict with the OTTO pixel class. ✅ How to Fix the Activation Fatal Error 1. Upgrade PHP to 8.0 or higher. Log in to your hosting control panel (e.g., cPanel, Plesk, or your host's dashboard) and change your PHP version. If you are unsure how to do this, contact your hosting provider. 2. Install the latest plugin version. Delete the current Search Atlas plugin from your WordPress admin panel, then download and install the latest version from the WordPress plugin repository or your Search Atlas dashboard. Versions 2.6.11 and above include fixes for the undefined constant fatal error. 3. Deactivate conflicting plugins or themes temporarily. If you use Divi or another heavy page builder, try activating the Search Atlas plugin with the default WordPress theme active to isolate the conflict. The render fatal error affecting Divi sites has been patched in recent plugin releases — ensure you are on the latest version. 4. Clear any caching layers. After updating PHP or the plugin, clear your server cache, object cache, and any CDN cache before retrying activation. 🚨 OTTO Pixel Snippet Alert in the Platform After you add the OTTO pixel code to your theme header, you may see an alert inside the Search Atlas platform. This usually means one of the following: - The pixel endpoint (/wp-json/otto-seo/v1/pixel) is not yet available — this can happen if the plugin did not activate successfully or if you are running an older plugin version. - The pixel code was added to the wrong location in your theme, or a caching plugin is serving a stale version of your header. - A memory exhaustion issue on very large pages is preventing the pixel from rendering correctly. ✅ How to Fix the Pixel Alert 1. Confirm the plugin is active and up to date. In your WordPress admin panel, go to Plugins → Installed Plugins and verify the Search Atlas plugin is active and shows the latest version number. 2. Check the pixel endpoint. In your browser, visit https://yourdomain.com/wp-json/otto-seo/v1/pixel (replace with your actual domain). If you see a valid JSON response, the endpoint is live. If you get a 404, the plugin is not active or the REST API is blocked — check your permalink settings under Settings → Permalinks and re-save them. 3. Verify pixel placement. The snippet must be placed inside the tag of your theme. In most themes, this is done via Appearance → Theme File Editor → header.php, or through a dedicated header/script injection field in your theme settings. 4. Purge all caches. After confirming placement, purge your caching plugin (e.g., WP Rocket, W3 Total Cache), server-side cache, and CDN cache so the updated header is served immediately. 5. Check server memory. If your site has very large pages, the plugin's HTML processing may hit PHP memory limits. Increase WP_MEMORY_LIMIT in your wp-config.php file to at least 256M, or ask your hosting provider to raise the PHP memory limit. 📊 Verify the Connection in Search Atlas Once the plugin is active and the pixel is in place, confirm everything is working: 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Check that your WordPress site shows as connected and that OTTO SEO is enabled for your domain. 3. If the alert persists after completing all steps above, wait 5 minutes and refresh the page — propagation can take a short time. 💡 Quick Reference: Requirements Checklist - PHP version: 8.0 or higher - Plugin version: 2.6.11 or higher (latest recommended) - Pixel endpoint: /wp-json/otto-seo/v1/pixel must return a valid response - Pixel placement: inside the tag of your theme header - PHP memory limit: 256M or higher recommended - Permalinks: re-save after any plugin reactivation 🙋 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.

🔄 Update & Fix WordPress Plugin Sync

🔌 Updating the Search Atlas WordPress Plugin Keeping the plugin updated is the most important first step — many sync issues are resolved automatically once you're on the latest version. 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins → Installed Plugins. 3. Locate Search Atlas SEO or OTTO SEO in the list. 4. If an update is available, click Update Now. 5. Once complete, confirm the plugin displays the latest version number. 🛠️ Fixing WordPress Sync Issues If changes aren't syncing between Search Atlas and your WordPress site, work through the steps below in order. Many issues are resolved before reaching the final step. 1. Confirm the plugin is up to date — always verify you're running the latest version before troubleshooting further (see section above). 2. Re-authenticate the connection — in your WordPress admin, open the Search Atlas plugin settings and re-enter or refresh your API key to re-establish the connection between your site and Search Atlas. 3. Verify the OTTO pixel is installed and active — the OTTO pixel must be firing correctly on your site for deployments to render. Check that it hasn't been accidentally removed or blocked. 4. Clear all caches — stale cache layers are a common cause of sync delays. Clear each of the following: - Your WordPress caching plugin (e.g. WP Rocket, W3 Total Cache, LiteSpeed Cache) - Your CDN cache (e.g. Cloudflare, Fastly) - Your browser cache 5. Trigger a fresh re-sync — redeploy from Search Atlas and check the live page to confirm changes appear correctly. 6. Check for plugin conflicts — temporarily deactivate other SEO or caching plugins that may be overriding or interfering with Search Atlas changes, then test the sync again. ✅ Before Contacting Support If sync still fails after completing all steps above, please have the following information ready when you reach out — it will help our team resolve your issue faster: - Your domain URL - A clear description of what isn't syncing (e.g. meta tags, content changes, schema) - The plugin version currently installed - Any caching plugins or CDNs active on your site If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Diagnose OTTO Plugin Slowdown and Form Redirect Issues

🔍 Overview Some customers have reported two related symptoms after installing the OTTO WordPress plugin: noticeable website slowdown and forms that only submit successfully when routed through an OTTO redirect URL. These issues are often connected and can usually be resolved by working through the steps below. ⚙️ How the OTTO Plugin Works The OTTO plugin integrates directly with your WordPress site to apply on-page SEO optimizations automatically. To do this, it hooks into WordPress core processes, including page rendering and URL handling. In certain configurations — particularly on shared hosting or sites with conflicting plugins — these hooks can create performance bottlenecks or interfere with how forms process their action URLs. 🩺 Step 1: Confirm the Plugin Is the Root Cause Before making any changes, isolate whether OTTO is responsible for the symptoms. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins and temporarily deactivate the OTTO plugin. 3. Test your site speed using a tool such as Google PageSpeed Insights or GTmetrix. 4. Test each affected form by submitting a test entry. 5. If performance improves and forms work correctly with OTTO deactivated, the plugin interaction is confirmed as the source. Important: Deactivating the plugin temporarily will pause OTTO's automated SEO actions. Reactivate it as soon as your testing is complete. 🐌 Step 2: Troubleshoot Website Slowdown If OTTO is confirmed as a contributor to slowdown, the most common causes are: - Plugin conflicts: Another active plugin (especially caching, page builder, or security plugins) may be conflicting with OTTO's rendering hooks. - Hosting resource limits: Shared or entry-level hosting plans may not have enough PHP memory or execution time to run OTTO alongside other plugins smoothly. - Large page counts: Sites with thousands of pages may experience higher processing load during OTTO's optimization cycles. To address slowdown, try these steps: 1. Deactivate all non-essential plugins one at a time, testing speed after each deactivation to identify any conflict. 2. In your hosting control panel, increase the PHP memory limit to at least 256 MB (512 MB recommended for larger sites). 3. Enable a lightweight caching plugin such as WP Super Cache or W3 Total Cache if you are not already using one — but confirm it is compatible with OTTO by testing forms after activation. 4. If you use a security plugin with a web application firewall (WAF), temporarily disable the WAF and retest, as aggressive WAF rules can slow dynamic hook execution. 📋 Step 3: Troubleshoot the Form Redirect Issue If your forms only submit successfully when the action URL contains an OTTO redirect path, this typically means OTTO's URL rewriting or canonical redirect rules are intercepting the form's POST request. 1. Open the affected form's settings in your form plugin (e.g., Contact Form 7, Gravity Forms, WPForms). 2. Check the form action URL or confirmation redirect setting. If it points to an OTTO-generated URL rather than your original page URL, OTTO's redirect rules have overridden it. 3. In your WordPress admin, navigate to the OTTO settings or go to Left sidebar → OTTO SEO → SEO Automation in your Search Atlas dashboard at /seo-automation-v3. 4. Review any redirect rules or canonical URL settings OTTO has applied to the pages containing your forms. 5. Disable or edit redirect rules that apply to form-hosting pages, then retest form submission. 6. If your form plugin has a setting to force a specific action URL, set it explicitly to your page's canonical URL to prevent OTTO from overriding it. ✅ Step 4: Verify Everything Is Working After making changes, confirm the following before considering the issue resolved: - Page load time has returned to normal (test with at least two speed tools). - Forms submit successfully without relying on an OTTO redirect URL. - OTTO's SEO optimizations are still active and visible in the Search Atlas dashboard. - No new JavaScript console errors appear on pages with forms (check via browser DevTools → Console). 🚀 Preventive Best Practices - Always test forms and page speed immediately after updating the OTTO plugin to a new version. - Keep a staging environment where you can test OTTO configuration changes before applying them to your live site. - Review OTTO's redirect and canonical rules whenever you add new forms or landing pages to your site. - Ensure your hosting plan meets the minimum PHP memory requirements before activating OTTO on high-traffic or plugin-heavy sites. 💬 Still Need Help? If the steps above do not resolve your slowdown or form redirect issue, our team can review your specific OTTO configuration and hosting environment directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO's Disabled WordPress Plugin Error

🔍 What This Error Means When OTTO's diagnostics display a "WordPress plugin is currently disabled" warning, it does not always mean the plugin is actually deactivated inside WordPress. In most cases, the plugin is active — but a cached response is preventing OTTO from reading its current status correctly. This mismatch happens because WordPress and hosting providers aggressively cache API responses. OTTO checks a specific endpoint to confirm the plugin is running, and if that endpoint returns a stale or empty cached response, OTTO flags the plugin as disabled even though it is working fine. ⚙️ Step 1 — Confirm the Plugin Is Active in WordPress 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins → Installed Plugins. 3. Locate the Search Atlas plugin. 4. Confirm the plugin status shows Active. If it is deactivated, click Activate before continuing. 🗑️ Step 2 — Clear All Caches on Your Site This is the most important step. You need to clear every layer of caching that could be serving a stale response to OTTO. - WordPress caching plugin — If you use WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, or a similar plugin, open its settings and click Clear All Cache or Purge Everything. - Hosting-level cache — Log in to your hosting control panel (e.g., Kinsta, WP Engine, SiteGround, Cloudways) and purge the server cache from your hosting dashboard. - Cloudflare or CDN cache — If your site runs behind Cloudflare or another CDN, log in and click Purge Everything under the Caching settings. - Object cache — If your site uses Redis or Memcached, flush the object cache from your hosting dashboard or via your cache plugin's settings. 🔄 Step 3 — Re-run the OTTO Diagnostic Check 1. In Search Atlas, go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Open the OTTO panel for your site. 3. Locate the WordPress Plugin status card in the diagnostics section. 4. Click Refresh or re-run the site check to let OTTO re-read the plugin status. 5. The status should now show as Active or Connected. 💡 Why This Happens and How to Prevent It OTTO communicates with your WordPress site through a REST API endpoint that the Search Atlas plugin registers. If a caching layer returns an old response — or blocks the endpoint entirely — OTTO receives no valid signal and defaults to reporting the plugin as disabled. - Exclude the plugin's REST API endpoint from caching — In your caching plugin settings, add an exclusion rule for URLs containing /wp-json/search-atlas/. This prevents future caching conflicts. - Check for security plugins blocking REST API access — Plugins like Wordfence, iThemes Security, or All In One WP Security can restrict REST API access. Ensure the Search Atlas endpoint is whitelisted. - Avoid full page caching on admin-ajax requests — Confirm your caching rules are not caching authenticated or admin-level requests. 🚨 Still Showing as Disabled After Clearing Cache? If the diagnostic still shows the plugin as disabled after completing all the steps above, try the following: 1. Deactivate the Search Atlas plugin in WordPress, wait 30 seconds, then reactivate it. 2. Clear all caches again following Step 2. 3. Re-run the OTTO diagnostic check following Step 3. If the problem persists after these 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.

Fix the WordPress Plugin Wrong UUID Error

🧩 What Is the Wrong UUID Error? The Wrong UUID error appears when the Search Atlas OTTO SEO WordPress plugin cannot match the unique identifier (UUID) stored in your plugin settings with the one linked to your Search Atlas account. This mismatch prevents the plugin from communicating with the platform and must be corrected before OTTO SEO features will work. What to Do If You See This Error Because the exact steps to resolve a Wrong UUID error depend on your specific plugin version, account configuration, and WordPress environment, there is no single universal self-serve fix confirmed for all cases. If you encounter this error, the most reliable path is to contact our support team directly so an agent can look up the correct UUID associated with your account and guide you through re-entering it in the right location within your setup. Before reaching out, please have the following information ready so the agent can resolve your issue as quickly as possible: - Your Search Atlas account email address - The URL of the WordPress site where the plugin is installed - The version of the Search Atlas OTTO SEO plugin you have installed (visible in your WordPress Plugins list) - A screenshot or exact text of the error message you are seeing - Any recent changes you made to the plugin settings or your Search Atlas account before the error appeared Having these details ready will allow the support team to identify the correct UUID for your account and walk you through exactly where to enter it in your 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.

🔧 How to Fix WordPress and Rank Math Conflicts with OTTO SEO

Why WordPress and Rank Math Conflicts Happen When Search Atlas generates content and syncs it to your WordPress site, the Rank Math SEO plugin can sometimes interfere with how titles, meta descriptions, and other SEO data are displayed. This happens because Rank Math applies its own templates and rules that may override the SEO data Search Atlas sends to WordPress. Common symptoms include: - Titles or meta descriptions not matching what was generated in Search Atlas - Rank Math displaying warnings or errors about title length or duplicate meta tags - SEO data appearing differently on your live WordPress pages than expected General Troubleshooting Steps If you are experiencing conflicts between Search Atlas content and Rank Math, try these steps: - Check whether Rank Math has global title or meta templates enabled that may be overriding the SEO data synced from Search Atlas. - Review the SEO settings on individual WordPress posts or pages to see if Rank Math has modified what was published. - Verify that your WordPress connection in Search Atlas is active and syncing correctly by re-publishing or re-syncing the affected content. - If you recently installed or updated Rank Math, note whether the issue started after that change. - Clear your WordPress site cache after any changes to ensure updated SEO data is served correctly. Information to Have Ready When Contacting Support If the conflict persists, gathering the following details will help our team investigate and resolve the issue efficiently: - The name or URL of the affected WordPress site - The specific Search Atlas project or article experiencing the issue - Screenshots or a description of what Rank Math is displaying versus what Search Atlas generated - The version of Rank Math installed on your WordPress site - The approximate date and time when you first noticed the conflict If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Plugin 500 Error Blocking OTTO Sync

🔍 What This Article Covers If your OTTO (OTTO SEO) page is showing no titles, descriptions, or content, and your WordPress site is not syncing with Search Atlas, the root cause is likely a 500 Internal Server Error triggered during WordPress plugin authentication. This article walks you through the self-serve steps to attempt a fix before escalating to our team. ⚠️ Symptoms to Look For - OTTO page displays no titles, meta descriptions, or content suggestions. - WordPress site is not syncing with Search Atlas. - You are unable to publish blogs or generate content suggestions through the plugin. - A 500 Internal Server Error appears when the plugin tries to authenticate with Search Atlas. - Regenerating your API key does not resolve the authentication error. ⚙️ Step 1 — Deactivate and Reactivate the Plugin A known issue can occur when the Metasync WordPress plugin enters a broken state during activation or deactivation. Follow these steps in your WordPress admin panel: 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins in the WordPress sidebar. 3. Locate the Search Atlas / Metasync plugin. 4. Click Deactivate, wait a few seconds, then click Activate again. 5. Attempt to reauthenticate the plugin with your Search Atlas API key. Note: If you are using a page builder such as Elementor, be aware that the plugin has a known interaction with Elementor. If your Elementor editor hangs on a loading screen after reactivating the plugin, deactivate the Search Atlas plugin temporarily while you work in Elementor, then reactivate it when done. 🔑 Step 2 — Regenerate Your API Key If the 500 error persists after reactivating the plugin, try generating a fresh API key from within Search Atlas and re-entering it in the WordPress plugin settings. Even if you have tried this before, doing it immediately after a clean deactivation/reactivation cycle can resolve the issue in some cases. 1. Log in to your Search Atlas account. 2. Navigate to your account or API settings and generate a new API key. 3. Copy the new key. 4. Return to your WordPress admin panel and open the Search Atlas plugin settings. 5. Replace the existing API key with the newly generated one and save. 🔄 Step 3 — Trigger a Manual Site Scan in OTTO After successfully reauthenticating, trigger a fresh scan so OTTO can repopulate your page data: 1. In Search Atlas, go to Left sidebar → OTTO SEO → Overview. 2. Use the Scan action to trigger a new crawl of your site. 3. Wait for the scan to complete, then check whether titles, descriptions, and content suggestions have reappeared. 🌐 Hosting Environment Note This 500 error has been confirmed to occur on certain hosting environments, including SiteGround. If your site is hosted on SiteGround or a similarly configured environment and the steps above do not resolve the issue, this is likely a server-level conflict that requires engineering intervention. Please contact our support team as described below. 📋 Before You Contact Support To help our team resolve your issue as quickly as possible, please have the following ready: - A screen recording or screenshot of the 500 error as it appears during plugin authentication. - Your WordPress site URL. - The name of your hosting provider. - Confirmation of which steps above you have already tried. 💬 Still Need Help? If you have completed all the steps above and the 500 error or sync issue persists, our engineering team can investigate at the account level. If you need further assistance, open 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 OTTO Pixel WordPress Plugin Configuration

🔍 Overview The OTTO Pixel plugin connects your WordPress site to Search Atlas so OTTO can read your site's structure and deploy SEO optimizations automatically. If the integration is not working, the most common cause is one or more required checkboxes being disabled in the plugin's settings. This article walks you through the correct configuration. ✅ Before You Begin - Make sure you have the OTTO Pixel plugin installed and activated on your WordPress site. - Confirm you are logged in to Search Atlas with an account that has access to OTTO SEO (Left sidebar → OTTO SEO → SEO Automation). - Have your WordPress admin dashboard open in a separate tab so you can switch between both screens. ⚙️ Step 1 — Open the OTTO Pixel Plugin Settings 1. Log in to your WordPress admin dashboard. 2. In the left-hand menu, locate Search Atlas → Settings and click it to open the plugin settings page. 3. You will see a settings panel with several configuration checkboxes and your connection status. ☑️ Step 2 — Enable All Required Checkboxes Each checkbox controls a specific permission that OTTO needs to communicate with your site. Leaving any of these unchecked is the most frequent reason the integration fails. - Search Atlas API Key — Enter your API key here (or use One-Click Authentication to connect). - OTTO Pixel UUID — Enter your OTTO Pixel UUID so the plugin knows which OTTO project to connect to. - Disable OTTO for Logged in Users — Optional. Enable this to turn OTTO off while logged in so you can edit original content. Enable every checkbox that corresponds to the OTTO features you have activated inside Search Atlas. If you are unsure, enabling all checkboxes is safe and recommended for full functionality. 💾 Step 3 — Save Your Settings 1. After enabling all required checkboxes, scroll to the bottom of the plugin settings page. 2. Click Save Settings (or Update, depending on your plugin version). 3. Wait for the confirmation message confirming your settings have been saved. 🔄 Step 4 — Verify the Connection in Search Atlas 1. Return to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation. 2. Open your project and check the OTTO connection status indicator at the top of the page. 3. The status should now show as Connected or Active. 4. If OTTO was previously paused or showing an error, click Activate OTTO to restart the automation. 🛠️ Common Issues and Fixes - Plugin shows "Connected" but changes are not deploying: Double-check that the specific checkboxes for the features you are using (e.g., Schema, Meta Tags) are enabled, not just the master toggle. - Checkboxes revert after saving: A conflicting security plugin or caching plugin may be blocking the save. Temporarily disable caching, save the settings again, then re-enable your cache. - Connection status remains "Disconnected" after completing all steps: Clear your WordPress site cache and your browser cache, then reload both the plugin settings page and the Search Atlas OTTO SEO page. - OTTO Pixel plugin not visible in WordPress menu: The plugin may not be activated. Go to Plugins → Installed Plugins, find OTTO Pixel, and click Activate. 💡 Best Practices - After any WordPress core update or plugin update, revisit the OTTO Pixel settings to confirm all checkboxes are still enabled. - Keep the OTTO Pixel plugin updated to the latest version to ensure compatibility with new Search Atlas features. - If you manage multiple WordPress sites, repeat this configuration process for each site individually. 🙋 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.

🔌 Stop OTTO From Changing Canonical Tags in WordPress

🧭 Overview If OTTO has changed the canonical tag on one of your WordPress pages and you want to stop it, this article explains how canonical changes work in the Search Atlas WordPress plugin and the ways to stop them. Important: There is no "Dynamic SEO" toggle and no plugin setting that turns off OTTO's canonical changes for the whole site. Canonical changes are controlled per page, as described below. 🔍 How OTTO Changes Canonical Tags OTTO only changes a canonical tag when it has a canonical recommendation deployed for that page. When it does, OTTO updates the address in the page's existing canonical tag to the recommended one. Pages without a deployed canonical recommendation are not changed. 🛑 How to Stop OTTO Changing a Canonical Tag Use whichever option fits your situation: 1. Undeploy the canonical recommendation in Search Atlas. Open your OTTO project in Search Atlas, find the canonical recommendation for the affected page, and undeploy or remove it. This is the supported way to stop OTTO's canonical change for that page. 2. Set a manual canonical for the page. A valid canonical you set manually for a page takes priority over OTTO's recommendation, so OTTO will leave it unchanged. 3. Turn OTTO off for a single page. While logged in to WordPress, open the page on your live site and use the OTTO frontend toolbar to disable OTTO for that page. ✅ How to Confirm It Worked - In WordPress, go to Search Atlas → Settings and use Clear Page Cache (or Clear all cache). If you also use a caching plugin such as WP Rocket, clear its cache too. - Reload the page and view its source (Ctrl+U or Cmd+U). The canonical tag in the <head> should now show the address you expect. If you need further assistance, open 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 'No WP Website Found' Sync Error

What Is This Error? When you click Sync to CMS inside OTTO SEO Onpage Optimizations, you may see the message: "No WP website found for this project" — even though your WordPress site appears as connected inside the Search Atlas plugin. The steps below are general troubleshooting suggestions to help address this connection mismatch. Standard Troubleshooting Steps Work through these steps in order. In many cases they help resolve the error: 1. Verify your WordPress site is connected to the correct project. The WordPress site must be linked to the same project where your content item lives. Check Settings → CMS Connectors to confirm the connection is in place. 2. Disconnect and reconnect your WordPress site. Inside Settings → CMS Connectors, remove the WordPress connection and add it again from scratch. Confirm the plugin is active and the connection is re-established. 3. Retry the Sync to CMS action. After completing the steps above, navigate back to your content item in OTTO SEO Onpage Optimizations and attempt the sync again. If the Error Persists If the steps above do not resolve the "No WP website found for this project" error, follow these additional steps: 1. Clear your browser cache and reload the platform. 2. Disconnect your WordPress site from the project and reconnect it to refresh the integration. 3. Retry the Sync to CMS action on your content item. 4. If the error continues, contact our support team so they can investigate your specific project and connection configuration. Additional Tips - Make sure you are syncing from the correct project — the WordPress site must be connected to the same project where your content item lives. - If you manage multiple WordPress sites across different projects, double-check that each site is linked to its intended project before attempting a sync. If you are still experiencing this issue after trying the steps above, please reach out to our support team via the chat icon in your Search Atlas dashboard and we will be happy to help.

🛠️ WordPress Plugin Update Breaking Site CSS or Layout

🔍 Overview Following certain Search Atlas WordPress plugin updates, some users have reported visual rendering issues on client sites — including disappearing CSS backgrounds, squished column widths, and homepage content not displaying correctly. These issues have been linked to specific plugin versions and have been resolved by the Search Atlas WordPress team in previous cases. ⚠️ Known Affected Scenarios - CSS background images disappearing after a plugin update - Column widths becoming distorted or compressed - Homepage content failing to render while the plugin is active - Layout changes occurring specifically when the Search Atlas plugin is enabled These issues have been documented and resolved in multiple engineering cases across various plugin versions. 🚀 Immediate Steps to Try First 1. Clear your site cache. After any plugin update, caching layers can serve outdated CSS. Clear your WordPress cache plugin, server-level cache, and CDN cache (if applicable), then reload the affected page. 2. Check which plugin version is installed. In your WordPress admin dashboard, go to Plugins → Installed Plugins and confirm you are running the latest available version of the Search Atlas plugin. If a newer version is available, update it. 3. Deactivate and reactivate the plugin. Deactivating the Search Atlas plugin temporarily will confirm whether it is the direct cause of the layout issue. If the layout restores after deactivation, the plugin is the source of the conflict. 4. Test on a staging environment first. Before applying any future plugin updates to live client sites, test the update on a staging or development copy of the site to catch CSS conflicts before they affect production. 📋 If the Issue Persists After Clearing Cache If clearing your cache and updating to the latest plugin version does not resolve the layout issue, the problem likely requires backend investigation by the Search Atlas WordPress team. To get this resolved as quickly as possible, have the following ready before contacting support: - The URL of the affected site or sites - The Search Atlas plugin version currently installed - A brief description of the visual issue (e.g., background missing, columns squished) - WordPress admin credentials so the team can access and diagnose the site directly - The approximate date the issue first appeared In previous cases, support agents accessed affected sites directly, escalated to the WordPress engineering team, and applied fixes — after which cache clearing resolved the remaining visual artifacts. 💡 Prevention Tips - Always test plugin updates on staging before deploying to live client sites, especially immediately after a new plugin version is released.

WordPress Plugin Dashboard Shows Login Despite Sync

What Is This Issue? After successfully connecting your WordPress site to Search Atlas, the plugin dashboard may display a login screen or prompt you to select a free trial — even though your account is active and the sync appears complete. If you are experiencing this behaviour, try the troubleshooting steps below. If the issue persists after working through them, please contact our support team so we can investigate further. Step 1: Re-Authenticate the Plugin The first thing to try is disconnecting and reconnecting your Search Atlas account inside the plugin. This refreshes the authentication tokens between your WordPress site and the platform. 1. In your WordPress admin, navigate to the Search Atlas plugin settings. 2. Disconnect or log out of your Search Atlas account from within the plugin. 3. Log back in using your Search Atlas credentials and complete the connection flow again. 4. Once reconnected, reload the plugin dashboard and check whether the login screen still appears. Step 2: Deactivate and Reactivate the Plugin If re-authentication alone does not resolve the issue, deactivating and reactivating the plugin can reset its internal state. 1. Go to Plugins in your WordPress admin panel. 2. Find the Search Atlas plugin and click Deactivate. 3. Once deactivated, click Activate to turn it back on. 4. Return to the plugin dashboard and test again. Step 3: Clear All Caches Cached data — from your browser, WordPress caching plugins, or your hosting provider — can cause the plugin to display outdated authentication states. - Clear your browser cache and cookies, then reload the page. - If you use a WordPress caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), purge all cached files from within that plugin. - If your hosting provider offers server-level caching (for example, via a hosting dashboard), clear that cache as well. - After clearing all caches, navigate back to the Search Atlas plugin dashboard. Step 4: Uninstall and Reinstall the Plugin If the steps above have not worked, a clean reinstall removes any corrupted plugin files that could be causing the problem. 1. In your WordPress admin, go to Plugins and deactivate the Search Atlas plugin. 2. Click Delete to fully remove it. 3. Download the latest version of the Search Atlas plugin from the official source. 4. Install and activate it fresh, then reconnect your account. 5. Check the dashboard once more to see if the login prompt is gone. Step 5: Verify Your Plan Is Active In rare cases, a billing or subscription issue can cause the plugin to behave as if no plan is attached to your account. To rule this out, log in to your Search Atlas account directly in your browser and confirm that your plan is active and your site is listed as connected. If anything looks incorrect, contact our support team for assistance. Still Seeing the Issue? If none of the steps above resolve the problem, please reach out to our support team via the chat widget in your Search Atlas dashboard. Share a description of what you see in the plugin dashboard and any steps you have already tried, so we can investigate and resolve it for you as quickly as possible.

🛠️ Fix Search Atlas WordPress Plugin Visual Rendering Issues

🔍 Overview Some WordPress sites experienced visual rendering problems after activating the Search Atlas plugin. Symptoms included images appearing zoomed in, page layouts breaking, and visitors seeing 'page not found' errors across all browsers. These issues have been identified as a visual rendering crash tied to the Search Atlas WordPress plugin. Updating to the latest available version of the plugin is the recommended resolution. ⚠️ Symptoms to Look For - Images appear zoomed in or distorted after activating the Search Atlas plugin. - Homepage or other pages fail to display content correctly. - Visitors see 'page not found' errors site-wide while the plugin is active. - Layout breaks persist across multiple browsers, ruling out a browser-specific cause. ✅ Solution: Update the Search Atlas Plugin The visual rendering crash has been linked to the Search Atlas WordPress plugin. Updating to the latest available version is the confirmed fix for this issue. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins in the WordPress sidebar. 3. Locate the Search Atlas plugin in the list. 4. If an update is available, click Update Now. 5. Once the update completes, reload your website in a browser to verify images, layouts, and pages display correctly. 🔄 If the Problem Persists After Updating If updating the plugin does not immediately resolve the visual issues, try the following additional steps: - Clear your WordPress and page builder cache. If you use a caching plugin or a page builder such as Elementor, clear its cache after updating the Search Atlas plugin. Stale cached assets can continue to cause layout issues even after the underlying bug is fixed. - Clear your browser cache. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) to clear cached files, then reload your site. - Test in a private or incognito browser window. This rules out locally cached resources as the cause. - Deactivate and reactivate the plugin. In Plugins → Installed Plugins, deactivate the Search Atlas plugin, then reactivate it to ensure the updated version loads cleanly. 📋 Still Experiencing Issues? If your site continues to show rendering problems after updating the plugin and clearing caches, please reach out to the Search Atlas support team via the chat widget in your dashboard so we can investigate further.

Fix 404 Errors After SA Plugin Update

🔍 What Is Happening After activating or updating the Search Atlas WordPress plugin, some sites experience 404 errors on pages across the site. The rest of the site may appear to go offline even though no content has been deleted. This issue has been reported in connection with plugin updates, including v2.6.11. If you are seeing sitewide 404 errors following a Search Atlas plugin update, the steps below are the recommended starting points for resolving the problem. If self-service steps do not resolve the issue, please contact our support team for further investigation. ✅ Steps to Try The following steps address common causes of sitewide 404 errors in WordPress after a plugin update. Work through them in order. 1. Log in to your WordPress admin dashboard. 2. In the left-hand menu, go to Settings, then click Permalinks. 3. Without changing any settings, scroll to the bottom of the page and click Save Changes. 4. Reload any page on your site that was previously returning a 404 error to confirm it is now accessible. 5. If the issue persists, go to Plugins in your WordPress dashboard, deactivate the Search Atlas plugin, then reactivate it. Immediately re-save your permalink settings afterward (repeat steps 2–4). 6. If your site is on a managed WordPress host (such as WP Engine, Kinsta, or Flywheel), use your host's cache-clearing tool after saving permalink settings, as some hosts cache rewrite rules aggressively. 7. In your WordPress dashboard, go to Plugins and check the version number listed under the Search Atlas plugin. If an update is available, apply it and then re-save permalink settings. 🚫 What Not to Do - Do not delete and reinstall the plugin without first saving a note of your existing plugin settings, as reinstalling may reset your configuration. - Do not restore a full site backup unless all other steps have failed and support has advised it. 💬 Still Experiencing 404 Errors? If the steps above do not resolve the issue, please reach out to our support team with details about your hosting environment and the plugin version you are running. We're happy to investigate further.

⚠️ Content Assistant WordPress Plugin: Incorrect Version Detection on v1.10.x and Higher

The Search Atlas Content Assistant WordPress plugin incorrectly detects versions that contain double-digit segments — such as v1.10.x, v1.12.x, or v2.10.x — which can cause version-gated features to behave unexpectedly. Engineering has identified the root cause and a fix is in review for deployment; no action is needed on your end right now. 🔍 What's Happening with Content Assistant Version Detection The Content Assistant backend evaluates your installed plugin version to decide which features to enable. When a version contains a double-digit segment, the backend's version-parsing logic misreads the number and applies the wrong feature set to your account. You may be affected if you are running: - Content Assistant WordPress plugin v1.10.x or higher - Any plugin version with a double-digit segment (for example v1.12.x or v2.10.x) Common symptoms include: - Version-gated features failing to activate even though your plugin is up to date - An incorrect "update required" prompt appearing in the Content Assistant interface - Content Assistant functionality behaving unexpectedly or inconsistently If you are seeing one or more of these symptoms on a supported plugin version, you are likely impacted by this known issue. 🛠️ Workaround Steps for the Content Assistant Version Detection Issue There is currently no customer-side workaround available for this issue. The version comparison runs on the Search Atlas backend and can only be corrected by a server-side engineering deployment. Reinstalling, downgrading, or reconfiguring the Content Assistant WordPress plugin on your site will not resolve it. You do not need to take any action on your WordPress installation while the fix is being deployed. 📡 Engineering Status for the Content Assistant Fix Our team is aware of this issue and is actively working on a resolution. - Root cause: Identified — the backend version-parsing logic mishandles double-digit version segments. - Current status: A fix is in engineering review. - Next step: Deployment to production once the fix is approved. Once deployed, Content Assistant will detect your plugin version correctly and version-gated features will activate as expected — no further action required on your end. 📞 When to Contact Search Atlas Support Reach out to Search Atlas Support if any of the following apply: - You want your account flagged so the support team can notify you the moment the fix goes live - You are blocked on a specific Content Assistant workflow and need help confirming whether this issue is the cause - You continue to see version detection issues after the fix has been announced as deployed When you contact support, include your Content Assistant WordPress plugin version and a short description of the behavior you are seeing. This helps the team confirm the match to this known issue and monitor your account through resolution. 🌀 Our engineering team has identified the root cause and the fix is under review for deployment. Your support team is monitoring affected accounts and will follow up as soon as the fix is live — thank you for your patience.

🛠️ Fix Zoomed Images Caused by the Search Atlas Plugin

If images on your WordPress site appear zoomed or oversized after activating the Search Atlas (SA) plugin, clearing the Elementor cache resolves the issue. The fix takes less than a minute and requires no changes to the Search Atlas plugin itself. This article applies to WordPress sites that use Elementor as their page builder. If you use a different page builder, contact Search Atlas support. 🛠️ How to Clear the Elementor Cache in WordPress When the Search Atlas plugin is activated on a site running Elementor, the Elementor cache may need to be regenerated to render images at the correct size. Follow these steps in your WordPress admin panel (verified for Elementor 3.x): 1. Log in to your WordPress admin dashboard. 2. In the left sidebar, go to Elementor → Tools. 3. Click the General tab. 4. Click Regenerate Files & Data. 5. Wait for the on-screen confirmation that the process is complete. After regenerating, reload any affected page. Images return to their correct display size. If the issue reappears after a future Search Atlas plugin update or reactivation, repeat these steps to regenerate the cache. ✅ Confirm the Fix Worked Open an affected page and perform a hard refresh to bypass your browser's local cache: - Windows: Ctrl+Shift+R - Mac (Chrome/Firefox): Cmd+Shift+R - Safari on Mac: Cmd+Option+R, or go to Develop → Empty Caches then reload Images should now display at their correct size. Because the root cause is server-side, confirming the fix in one browser is sufficient — the resolution applies across all browsers automatically. 🌀 Clearing the Elementor cache after activating the Search Atlas plugin restores normal image rendering across your entire WordPress site. If images remain zoomed after completing these steps, contact Search Atlas support for a hands-on review of your configuration.

⚠️ Open Graph and Social Meta Checkboxes Not Saving in WordPress Plugin — Fixed

Open Graph and social meta toggle checkboxes in the Search Atlas WordPress plugin were reverting to enabled after every save. This bug has been fixed — updating to the latest plugin version resolves the issue immediately. 🔍 What's Happening The following nine checkboxes under the plugin's Open Graph and social settings could not be turned off: - Open Graph meta tags - Facebook meta tags - Twitter meta tags - OG image dimensions - Article timestamps - Article author - Article section - Article tags - Twitter image alt After unchecking any of these options and saving, the page reloaded with all checkboxes re-enabled. The settings were never stored, making it impossible to disable these features through the WordPress admin. 🛠️ How to Apply the Fix Update the Search Atlas WordPress plugin to the latest version. The fix ships in this release — no additional configuration is needed after updating. 1. Log in to your WordPress dashboard. 2. Go to Plugins → Installed Plugins or Dashboard → Updates. 3. Locate the Search Atlas plugin and click Update Now. 4. Once the update completes, navigate back to your OG and social settings. 5. Uncheck the desired options and click Save. The unchecked state will now persist correctly. 📡 Engineering Status The root cause of this bug has been identified and resolved. The fix is included in the latest release of the Search Atlas WordPress plugin and is available to all users now. No further action is required beyond updating the plugin. 📞 When to Contact Support If you update to the latest plugin version and checkboxes still revert after saving, contact our support team with the following details: - Your current WordPress version - The Search Atlas plugin version installed after updating - A brief description of the steps you followed Our team will follow up promptly to get your settings working correctly. 🌀 Updating the Search Atlas WordPress plugin resolves this issue completely — and if your Open Graph or social meta settings still aren't saving after the update, our support team is ready to help.

🛠️ Breadcrumbs "Enable" Toggle Reverts to ON After Saving in MetaSync

A bug in MetaSync causes the Enable Breadcrumbs toggle to revert to ON after saving, generating duplicate BreadcrumbList schema that conflicts with Yoast SEO. Update MetaSync to the latest version to permanently fix this. ⚠️ What Happens When you uncheck Enable Breadcrumbs in MetaSync settings and click Save Changes, the page reloads with the checkbox back to ON. The setting is not persisted. This causes MetaSync to keep injecting BreadcrumbList structured data alongside Yoast SEO's breadcrumb schema, which Google flags as a critical structured data conflict in Google Search Console. 🔍 Who Is Affected This issue affects you if all of the following apply: - MetaSync is installed on a WordPress site. - Yoast SEO is also active with its breadcrumbs enabled. - Google Search Console shows a critical error for duplicate BreadcrumbList structured data. ⚙️ How to Fix It This bug is resolved in the latest MetaSync release. Update the plugin to apply the fix. 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. Find MetaSync and click Update Now. If no update appears, deactivate then reactivate MetaSync to clear any cached plugin state. 3. Go to MetaSync → Settings → Breadcrumbs. 4. Uncheck Enable Breadcrumbs and click Save Changes. 5. Reload the settings page and confirm the checkbox stays unchecked. After saving, MetaSync stops injecting BreadcrumbList schema and the conflict with Yoast is resolved. ✅ How to Verify the Fix Worked Confirm the fix is working correctly: - Reload MetaSync → Settings → Breadcrumbs — the Enable Breadcrumbs checkbox should remain unchecked. - Run an affected page through Google's Rich Results Test — only one BreadcrumbList entry (from Yoast) should appear. - The critical error in Google Search Console will clear after Google re-crawls your affected pages, typically within 1–2 weeks. 💡 If the Toggle Still Reverts After Updating If the checkbox continues to revert even after updating MetaSync: - Clear your WordPress object cache using your caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, or similar). - Deactivate other SEO or schema plugins temporarily to rule out a secondary conflict. - Contact Search Atlas support with your MetaSync version number and a screenshot of the Breadcrumbs settings page immediately after saving. 🎯 Now that MetaSync is updated, the Enable Breadcrumbs toggle persists correctly and your site no longer outputs duplicate BreadcrumbList schema. If Search Console still shows errors after applying the fix, allow 1–2 weeks for Google to re-crawl and revalidate your affected pages.

🧱 How to Clear Cache in WordPress (Complete 2025 Guide)

When your WordPress site doesn’t show recent updates, caching is often the culprit. Cache helps speed up websites, but it can also store outdated versions of your pages. Here’s how to find and clear every layer of cache — from your hosting server to plugins and browsers — so your latest changes appear instantly. ⚙️ Step-by-Step Instructions 🏢 Step 1: Check for Server-Level Caching Most managed WordPress hosts automatically cache your website. Look for caching controls directly in your hosting dashboard. - WP Engine → Caching → Clear All Caches - SiteGround → Speed → Dynamic Cache → Flush Cache - Bluehost → Performance → Caching → Purge All If you don’t see these options, search your hosting help docs for “Flush Cache” or “Clear Cache.” 🌐 Step 2: Purge CDN Cache (Cloudflare or Similar) If you’re using Cloudflare, Akamai, or another CDN service: 1. Log in to your CDN account. 2. Go to the Caching tab. 3. Click Purge Everything. 4. Wait a few seconds, then reload your site to confirm. 👉 Resource: Cloudflare Docs – Purge Cache 💾 Step 3: Purge Object Cache (Redis / Memcached) Many hosting providers use Redis or Memcached to store database query results for faster performance. If you’re using one of these systems: 1. Go to WP Admin → Tools → Site Health → Info → Persistent Object Cache to confirm it’s active. 2. In your hosting control panel, look for Flush Object Cache or Clear Redis Cache. 3. On some platforms (like Kinsta, Cloudways, or RunCloud), this option appears directly on the site dashboard. 4. From the command line (WP-CLI), you can also run: 5. wp cache flush 👉 Resource: WordPress Developer Docs – Object Cache 🧭 Step 4: Clear Browser or Local Cache Sometimes, the “stuck” cache isn’t on your website — it’s in your browser. 1. Clear your browser cache and cookies. 2. Reload your site in Incognito/Private Mode to check the latest version. 3. Developers can use Chrome DevTools → Disable cache during testing. 👉 Resource: Google Chrome Help – Clear Cache & Cookies 🧰 Step 5: Manual Cache Purge (As a Last Resort) If your cache plugin or host-level purge doesn’t work, you can clear it manually: 1. Access your site via FTP or your hosting File Manager. 2. Navigate to: 3. /wp-content/cache/ 4. Delete all files and folders inside (but do not delete the main /cache/ folder itself). This forces WordPress to rebuild a fresh cache on the next page load. 👉 Resource: WordPress Advanced Admin – Cache 🔌 Step 6: Clear Cache Using Popular Plugins 🧩 WP Rocket - Go to Settings → WP Rocket → Dashboard. - Click Clear and Preload Cache. - Or, hover over the WP Rocket menu in your WordPress admin bar → choose Clear and Preload Cache. - Developers can purge cache programmatically with rocket_clean_domain() or rocket_clean_post(). 👉 Resource: WP Rocket Official Docs ⚡ W3 Total Cache (W3TC) 1. Navigate to Performance → Dashboard. 2. Click Empty All Caches. 3. Or use the admin bar → Performance → Purge All Caches. 4. Advanced users: run wp w3-total-cache flush all via WP-CLI. 👉 Resource: InMotion Hosting – W3 Total Cache Guide 🧹 WP Super Cache 1. Go to Settings → WP Super Cache. 2. Scroll to the Delete Cached Pages section. 3. Click Delete Cache to purge everything. 👉 Resource: Kinsta – WordPress Cache Guide 🪄 WP Fastest Cache 1. In your dashboard, open WP Fastest Cache → Delete Cache. 2. Click Delete Cache or Delete Cache + Minified CSS/JS if you changed styling or scripts. 👉 Resource: Hostinger Cache Tutorial 🔥 LiteSpeed Cache 1. Go to LiteSpeed Cache → Toolbox. 2. Click Purge Entire Cache. 3. You can also clear CSS/JS or Object Cache individually if needed. 👉 Resource: SupportHost – Clear Cache Guide 💡 FAQs ❓ Do I need to clear all caches every time I make a change? 💡 Not always. Most caching plugins and hosts auto-purge when you update a post, change your theme, or modify plugin settings. ❓ What’s the safest cache purge order? ⚙️ Always clear Hosting → CDN → Object Cache → Plugin Cache → Browser. ❓ My site still doesn’t update after clearing everything. What now? 🔍 Check your CDN cache headers or try forcing a hard refresh (Ctrl + Shift + R / Cmd + Shift + R). ✅ Closing Note Clearing cache regularly keeps your website updated and ensures visitors see the latest version of your content. If your site still doesn’t reflect recent changes, contact your hosting support — they may need to purge server-level caches manually. 🔗 Resources 👉 Resource: WordPress Developer Docs – Performance & Caching 👉 Resource: Cloudflare Docs – Purge Cache 👉 Resource: WP Rocket Official Documentation 👉 Resource: Kinsta WordPress Cache Guide 👉 Resource: Hostinger WordPress Cache Guide

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

🛠️ Fix MetaSync Canonical Tags on WordPress Archive Pages

🔍 What Is Happening If your WordPress site uses the Search Atlas MetaSync plugin, you may notice that archive pages, category pages, and search results pages are receiving canonical tags that point to an individual blog post — typically the first post in the page loop — rather than pointing to the archive URL itself. This incorrect canonical tag causes your site audit to flag these pages as having non-self-referential canonicals, which can confuse search engines about which URL to index. For example, your /blog/ archive page may carry a canonical tag pointing to /blog/my-first-post/ instead of /blog/. ⚙️ Root Cause This is a confirmed code defect in the MetaSync plugin. The canonical output function incorrectly applies post-level canonical logic to every page type — including archives, taxonomies, and search results — rather than restricting it to single post or page views. Engineering has identified and resolved this defect in a plugin update. ✅ Resolution: Update the MetaSync Plugin The fix is delivered as a plugin update. Follow these steps to apply it: 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins → Installed Plugins. 3. Locate the Search Atlas MetaSync plugin. 4. If an update is available, click Update Now. After updating, confirm that the plugin version shown is the latest release. 5. Once updated, load one of your affected archive or category pages in your browser and use your browser's View Page Source function to inspect the <link rel="canonical"> tag in the <head> section. 6. Verify that the canonical URL now matches the archive page's own URL rather than a blog post URL. 🔄 Short-Term Workaround (If You Cannot Update Immediately) If you are unable to update the plugin right away, you can prevent MetaSync from outputting incorrect canonical tags on non-singular pages by using a small code snippet added to your theme's functions.php file or via a code snippets plugin. The snippet should remove or override the MetaSync canonical output on archive, taxonomy, and search page types using WordPress conditional tags, and output a self-referential canonical for those page types instead. Important: Editing theme files or adding code snippets carries risk. Only proceed if you are comfortable with PHP and WordPress development, or work with a developer. If you need assistance, please reach out to our support team via the chat icon in your Search Atlas dashboard.

🛡️ Fix Cloudflare WAF Blocking WordPress Sync

🔍 What This Error Means When you try to publish or sync an article to your WordPress site, you may see a message such as "We're unable to sync with your WordPress site" or a status of cloudflare_blocked. This means your site is protected by Cloudflare, and its Web Application Firewall (WAF) is treating the request from Search Atlas as suspicious traffic. Cloudflare sits between your website and the internet. When our platform sends content to your WordPress REST API — specifically the Search Atlas SEO plugin's /wp-json/metasync/v1/ route — Cloudflare can mistakenly flag that automated request and stop it before it reaches your site. The result is a blocked sync, even though your login details and plugin are correct. A related symptom is an HTTP 525 ("SSL handshake failed") response from Cloudflare for this endpoint, which points to a Cloudflare-side connection problem rather than incorrect WordPress credentials. Note that cloudflare_blocked is distinct from a wp_client_error status, which indicates a different WordPress connection issue rather than a Cloudflare block. ⚙️ Why Cloudflare Blocks the Sync Cloudflare's firewall uses rules to filter out bots and automated tools. Publishing software like Search Atlas connects through the WordPress REST API, which can look like automated activity. Common reasons for a block include: - Managed WAF rules that flag requests to the /wp-json/ REST API endpoint. - Bot Fight Mode or Super Bot Fight Mode challenging non-browser traffic. - Rate limiting rules that block repeated requests in a short time. - Custom firewall rules created by your team or hosting provider. - Security plugins working alongside Cloudflare that add extra filtering. ✅ Before You Begin You will need access to your Cloudflare dashboard for the affected domain. If your site is managed by a hosting provider or developer, you may need to ask them to apply these changes. Always make one change at a time and re-test the sync so you know which fix worked. 🛠️ How to Allow the Sync in Cloudflare Follow these steps to let Search Atlas connect to your WordPress site: 1. Log in to your Cloudflare dashboard and select the domain you are trying to sync. 2. Go to Security, then WAF. 3. Open the Firewall rules or Custom rules tab. 4. Create a new rule that allows traffic to your REST API. Set the field to URI Path, the operator to contains, and the value to /wp-json/. The SearchAtlas plugin specifically uses the /wp-json/metasync/v1/ path, so you can target that route if you prefer a tighter, more specific rule. 5. Set the action for this rule to Skip or Allow, so these requests bypass the firewall. 6. Save and deploy the rule, then try the sync again from the Search Atlas platform. 🤖 Adjust Bot Protection Settings If the block continues, your bot protection may be the cause. In your Cloudflare dashboard: - Go to Security, then Bots. - Temporarily turn off Bot Fight Mode or Super Bot Fight Mode and test the sync. - If this resolves the issue, create an exception so legitimate requests to /wp-json/ are not challenged. You can also check Security, then Events, to see a log of blocked requests. This log helps you confirm which rule stopped the sync and lets you adjust the correct setting. 🌐 Allow Our Connection at the Server Level Some hosts apply security at the server level in addition to Cloudflare. If you still see a block after updating Cloudflare, ask your hosting provider to confirm that requests to the WordPress REST API are not being filtered, and that your SearchAtlas SEO plugin is active and up to date. 🔁 Re-Test the Sync After making your changes, return to the Search Atlas platform and try publishing again: 1. Open the article you want to publish. 2. Confirm your WordPress site is correctly connected in your integration settings. 3. Click Publish or Sync and wait for the confirmation message. If the sync succeeds, the block has been resolved. If it still fails, review your Cloudflare Events log again to identify any remaining rule that needs adjusting. 💡 Tips to Prevent Future Blocks - Keep your SearchAtlas SEO plugin updated to the latest version. Search Atlas sends sync requests using a WAF-aware user agent designed to reduce false blocks, so running the latest plugin version ensures you benefit from this behavior. - Avoid overly strict global firewall rules that apply to the entire site. - Document any custom rules you create so they are easy to review later. - Coordinate with your hosting provider before adding new security tools that may filter API traffic.

🛠️ How to Clear Cache in WordPress for the Search Atlas Plugin

If the OTTO Pixel isn't showing as detected after installing the Search Atlas plugin, caching is the most common cause. On most sites, clearing the WordPress cache is enough — but if you're on a CDN-backed host (such as Cloudflare or Pressable), you'll also need to purge your CDN cache to ensure OTTO detects the pixel correctly. ⚙️ Confirm Your Search Atlas Plugin Settings First Before clearing any cache, verify the plugin is configured correctly: 1. Go to the Search Atlas plugin settings in your WordPress dashboard. 2. Confirm your API keys and UUID are correctly filled in. 3. Click Save to apply the settings. Your configuration is saved and ready for the cache-clearing steps below. 🗑️ Clear Your WordPress Cache 1. Go to the frontend of your WordPress site. 2. In the top admin bar (top-right corner), click Clear Caches. 3. From the dropdown menu, select Clear All Caches. This clears outdated content from WordPress's caching layer and helps OTTO register the plugin correctly. ☁️ Clear Your CDN Cache (Non-WP-Rocket Sites) If your site runs on a CDN-backed host — such as Cloudflare, Pressable, or a similar edge-caching service — you also need to purge your CDN cache separately. Why this matters: A bug (WP-329) caused the OTTO plugin to send Cache-Control: public, max-age=3600 headers on non-WP-Rocket sites. This instructed CDNs and edge servers to aggressively cache pages, so a WordPress-level cache clear was immediately overridden — your CDN would re-serve stale content right away. Affected sites could also see broken forms and exposed nonces as side effects. This issue is fully resolved in the WP-329 plugin update. If you installed the Search Atlas plugin before this fix was released, perform a one-time CDN purge: - Cloudflare: In your Cloudflare dashboard, go to Caching → Configuration, then click Purge Everything. - Pressable: In your Pressable dashboard, go to Sites → [Your Site], then click Clear Cache. - Other CDN or host: Refer to your host's documentation for a full edge-cache purge. After purging, your CDN will serve fresh content and OTTO can detect the pixel on the next scan. 🔍 Verify OTTO Pixel Detection 1. Return to your OTTO dashboard. 2. Click Scan. OTTO should now detect the pixel and display a confirmation message. 🛠️ Troubleshoot If the OTTO Pixel Still Isn't Detected If OTTO still can't detect the pixel after completing all steps above, try the following: - Repeat both the WordPress cache clear and the CDN cache purge. - Confirm the Search Atlas plugin is updated to the latest version, which includes the WP-329 fix. - Check that no other plugin or server rule is overriding Cache-Control headers on your site. - Contact Search Atlas Support — we can verify your configuration and walk you through any remaining steps. 🎯 You now know how to clear both WordPress and CDN caches to get the OTTO Pixel detected correctly — including the extra CDN purge step needed on non-WP-Rocket hosts. If you're setting up the Search Atlas plugin for the first time, see our Search Atlas WordPress Plugin Installation Guide for full setup instructions.

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

⚠️ WordPress Plugin Header Incorrectly Shows "Not Connected" on Idle Pages

If your Search Atlas WordPress plugin header shows a red "Not Connected" badge after the page has been idle, refresh the page — your API key and connection remain intact. This is a known display glitch caused by temporary background-check failures during idle sessions. 🔴 What the "Not Connected" Status Badge Means The badge in the Search Atlas plugin header reflects the result of the most recent background check between your WordPress site and the Search Atlas API. A green dot means the last check succeeded; a red "Not Connected" dot means the most recent check failed. The badge updates automatically while any plugin page is open. After several minutes of inactivity, those background checks can fail for temporary reasons unrelated to your API key or account status. 💡 Why Idle Pages Trigger a False "Not Connected" Badge The plugin runs a background process that sends periodic requests to the Search Atlas API to sync your connection status. On idle pages, these requests can be blocked or dropped due to: - Temporary rate limiting on the server side — no action needed; the next check will succeed on its own - Transient network errors — a brief hiccup returns an empty or null API response - Request timeouts — the request times out before the Search Atlas API responds When any of these temporary failures occur, the badge flips to "Not Connected." This is a known display issue currently under engineering review. A permanent fix is targeted for an upcoming plugin release, and we will update this article once it is deployed. The badge does not accurately reflect your actual connection state when triggered by idle-session check failures. 🔍 How to Confirm the "Not Connected" Badge Is a False Alarm Before changing your API key or reinstalling the plugin, run these checks to confirm you are looking at a false alarm: 1. Refresh the page. If the badge returns to green immediately after a refresh, the disconnect was caused by an idle-session check failure — not a real connection problem. 2. Check how long the page was idle. If you stepped away for several minutes before noticing the red badge, idle-session failure is the most likely cause. 3. Navigate away and return. Go to a different Search Atlas plugin page and come back — a green badge on the fresh page load confirms your connection is intact. If the badge turns green after any of these steps, your connection is working correctly and no further action is needed. 🔄 How to Restore the Correct Connection Status After an Idle Session To clear the false "Not Connected" badge, follow these steps: 1. Press F5 (Windows / Linux) or Cmd + R (Mac) to refresh the current plugin page, or click your browser's Reload button. 2. Wait for the page to finish loading — the header badge updates within a few seconds. 3. Confirm the badge now shows a green dot and reads "Connected." All Search Atlas features — rank tracking, site audits, and keyword research — are fully accessible immediately after the refresh. No re-authentication or settings change is required. 🛠️ What to Do If the Badge Still Shows "Not Connected" After Refreshing If the badge remains red after a full page refresh, you may have a genuine connection problem. Work through these steps in order: 1. Verify your API key. Go to Search Atlas → Settings → API Key and confirm the key is entered correctly with no extra spaces or missing characters. 2. Check your account status. Log in at app.searchatlas.com and confirm your subscription is active. 3. Deactivate conflicting plugins. Security or caching plugins can block outgoing API requests. Temporarily deactivate them one at a time to isolate any conflict. 4. Check server firewall rules. Ask your hosting provider to confirm that outbound HTTPS requests to api.searchatlas.com are permitted. 5. Re-save your API key. In Search Atlas → Settings, clear the API key field, re-enter your key, and click Save Changes. If none of these steps resolve the issue, contact Search Atlas support and include your WordPress version, plugin version, and any error messages shown in your browser console (press F12 to open it). 🌀 A red "Not Connected" badge on an idle plugin page is almost always a temporary display glitch — a single page refresh is all it takes to recover. To review your full plugin setup, see Connecting the Search Atlas WordPress Plugin.

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

🔧 Fix WordPress Plugin Fatal Error and OTTO Pixel Alert

Overview Two separate issues can block a successful Search Atlas WordPress plugin installation: a fatal error that prevents activation entirely (commonly caused by PHP 7.4 incompatibility), and a site alert triggered after manually adding the OTTO pixel snippet to your theme header. This article walks you through resolving both issues in the correct order. Issue 1 — Fatal Error Blocks Plugin Activation (PHP 7.4) If you see "Plugin could not be activated because it triggered a fatal error" immediately after trying to activate the Search Atlas plugin, the most likely cause is that your server is running PHP 7.4, which is below the minimum required version. Why this matters: Standard troubleshooting steps — such as deactivating conflicting plugins or checking error logs inside WordPress — assume the plugin can at least partially load. When activation fails completely, those steps will not help until the PHP version is resolved first. 1. Confirm your current PHP version. Check your hosting control panel (cPanel, Plesk, or equivalent) — most hosts display the active PHP version under PHP settings or a similar section. You can also ask your host directly if you are unsure where to find this. 2. If your version is below PHP 8.0, upgrade to PHP 8.0 or higher. PHP 8.1 or 8.2 is recommended for best compatibility. Most managed hosts allow you to switch PHP versions from their control panel — consult your host's documentation if you are unsure how to do this. 3. After upgrading PHP, return to the Plugins section in your WordPress dashboard and activate the Search Atlas plugin again. 4. If the fatal error persists after upgrading PHP, check your server's PHP error log (available through your hosting control panel or via FTP) and note the exact error message before contacting support. Do not proceed to the OTTO pixel steps below until the plugin activates successfully. Adding the pixel snippet to a site where the plugin is not active will not establish a connection and may cause the alert described in Issue 2. Issue 2 — Site Alert After Adding the OTTO Pixel Snippet If you were advised to manually paste the OTTO pixel snippet into your theme's header and you then saw an alert or warning appear on your site, the snippet itself is the cause. This is a known side effect of adding the snippet to certain themes or page builders, and it must be removed before the alert will stop. How to remove the snippet and clear the alert: 1. Log in to your WordPress dashboard. 2. Navigate to your theme's header file. Depending on your setup, you can do this through your theme's editor in the Appearance section of your WordPress dashboard, or by using an FTP client or your host's File Manager to access the theme files directly. 3. Locate the OTTO pixel snippet and remove it completely, then save the file. 4. Confirm that the alert no longer appears on your site. If you continue to experience issues after following these steps, please reach out to our support team via the chat widget in your Search Atlas dashboard and we will be happy to help.