Troubleshooting: Pixel on WordPress

🛠️ Fix WordPress MetaSync Detection

🔍 Understand the connection status The WordPress MetaSync plugin may not be detected. When it is not detected, the OTTO script is an alternative installation method. 🔁 Check the WordPress plugin 1. Sign in to WordPress and open the MetaSync plugin settings. 2. Check whether the MetaSync plugin is detected in Search Atlas. 🚀 Install the OTTO script instead 1. If the MetaSync plugin is not detected, use the OTTO script installation method. 2. Copy the OTTO script provided for your site and add it to the required location on your WordPress site. 3. Save or publish the change so the script is active on the live site. ✅ Verify the installation - Return to Search Atlas and check whether the site is detected. - If it is still not detected, confirm that the OTTO script was saved and published on the live site. 💬 Get help with unresolved issues If the issue remains unresolved, confirm that the MetaSync plugin is not detected and that the OTTO script has been added and published. If you need further assistance, open 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 Pixel and Deployment Issues

🔍 Overview Two common issues affect WordPress sites connected to OTTO SEO: deployed changes (such as title tags) not appearing live on your site, and a "failed to fetch" error when attempting to install a pixel through the chatbot. This article explains why these happen and walks you through the steps to resolve them. ⚙️ Why Your Deployed Changes May Not Appear Live After deploying a change in OTTO SEO — for example, a page title or OG title update — you may notice the change still does not appear on your live WordPress site. This is usually caused by one of the following: - Caching: Your WordPress site, hosting provider, or a CDN (such as Cloudflare) is serving a cached version of the page that does not yet reflect the update. - Duplicate or conflicting plugin installs: If the OTTO SEO plugin and a Cloudflare Worker are both active on the same project, they can conflict and prevent changes from deploying correctly. - Plugin not fully synced: The OTTO SEO plugin on your WordPress site may not have received or applied the latest instructions from OTTO. ✅ Steps to Fix Deployed Changes Not Going Live 1. Clear all caches. Clear the cache in WordPress (using your caching plugin, such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), your hosting provider's cache, and any CDN cache (including Cloudflare). Then revisit the page in an incognito or private browser window. 2. Check for duplicate installations. Go to your WordPress dashboard and confirm that you only have one active method deploying OTTO SEO changes — either the OTTO SEO WordPress plugin or a Cloudflare Worker, not both. Having both active simultaneously causes a conflict that blocks deployments. Deactivate or remove the method you are not primarily using. 3. Verify the plugin is active and up to date. In your WordPress dashboard, navigate to Plugins and confirm the OTTO SEO plugin is installed, activated, and running the latest available version. Update it if a newer version is available. 4. Re-deploy the change in OTTO SEO. Return to the OTTO SEO platform, locate the change you deployed, and deploy it again. After deploying, wait two to three minutes, clear caches once more, and check your live site. 5. Check the deployment status in OTTO. OTTO verifies deployments by scanning your live page. If the status shows not live, this confirms the change has not yet been detected on the page. Follow the steps above and re-check after clearing caches. 📡 Why You Get a "Failed to Fetch" Error During Pixel Installation When using the OTTO chatbot to install a pixel on your WordPress site, a "failed to fetch" error typically means OTTO could not communicate with your WordPress site to complete the installation. Common causes include: - The OTTO SEO plugin is not installed or activated on your WordPress site. The pixel installation requires the plugin to be present and active so OTTO can interact with the necessary endpoints. - REST API access is blocked. Some security plugins, firewall rules, or hosting configurations block access to the WordPress REST API, which OTTO uses to install the pixel. - Incorrect site URL or connection settings in the OTTO SEO platform. ✅ Steps to Fix the "Failed to Fetch" Pixel Error 1. Install and activate the OTTO SEO plugin. In your WordPress dashboard, go to Plugins → Add New → Upload Plugin, upload the plugin .zip provided by Search Atlas, and install and activate it. If it is already installed, deactivate it and reactivate it to reset the connection. 2. Check that your REST API is accessible. Visit yoursite.com/wp-json/ in your browser. If you see a JSON response, the REST API is working. If you see an error or a blocked page, contact your hosting provider or check your security plugin settings to allow REST API access. 3. Confirm your site URL in OTTO. In the OTTO SEO platform, verify that the site URL connected to your project exactly matches your live WordPress site URL (including whether it uses www or not, and https). 4. Retry the pixel installation. Once the plugin is active and the REST API is accessible, return to the OTTO chatbot and attempt the pixel installation again. 🚀 Quick Checklist - OTTO SEO plugin installed, activated, and up to date - No duplicate install method active (plugin AND Cloudflare Worker simultaneously) - All caches cleared (WordPress, hosting, CDN) - WordPress REST API accessible (not blocked by security plugin or firewall) - Site URL in OTTO matches your live WordPress URL exactly - Re-deployed changes after clearing caches 💬 Still Need Help? If you have followed all the steps above and the issue persists, our 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.

🔧 OTTO Pixel Installation Troubleshooting for WordPress

🧭 Overview The OTTO pixel connects your WordPress website to OTTO SEO automation, allowing it to read and optimise your site. If the pixel fails to install or verify correctly, OTTO cannot activate. This article walks you through the most common WordPress pixel errors and how to resolve them step by step. ✅ Before You Begin Confirm the following before troubleshooting: - You are logged in to Search Atlas and have navigated to OTTO SEO via the left sidebar. - You have administrator access to your WordPress dashboard. - Your WordPress site is live and publicly accessible (not under a maintenance page or password protection). - You know which method you are using to install the pixel: plugin, manual code insertion, or a tag manager. ⚠️ Common Errors and What They Mean - "Pixel not detected" — Search Atlas cannot find the pixel code on your site. The code was not saved correctly or is being blocked. - "Verification failed" — The pixel was found but returned an unexpected response. This is often a caching or conflict issue. - "Connection timeout" — Your server did not respond in time. This may be a hosting or firewall restriction. - "Invalid site URL" — The URL entered in Search Atlas does not match the URL where the pixel is installed. Check for www vs. non-www or HTTP vs. HTTPS mismatches. 🔍 Step-by-Step Diagnostic Procedure 1. Check your pixel code is present. In your browser, open your WordPress homepage, right-click, and select View Page Source. Press Ctrl+F (or Cmd+F on Mac) and search for otto or the pixel script snippet. If it does not appear, the code has not been saved to your site. 2. Verify the URL in Search Atlas matches your live site. Go to OTTO SEO in the left sidebar and confirm the domain shown matches your WordPress site URL exactly, including the correct protocol (https://) and subdomain (www or non-www). 3. Clear all caches. Caching plugins (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) can serve old page versions that do not include the pixel. Clear your plugin cache, your hosting-level cache, and any CDN cache (such as Cloudflare). 4. Deactivate conflicting plugins temporarily. Security plugins (Wordfence, iThemes Security) and optimisation plugins (Autoptimize, WP Fastest Cache) can strip or defer scripts. Deactivate them one at a time and re-test pixel detection after each. 5. Check your theme's header file. If you installed the pixel manually, confirm the snippet is placed immediately before the closing tag in your theme's header.php file or via Appearance → Theme File Editor. Do not place it inside the body or footer. 6. Test with a plugin installation. If manual installation is failing, use the Search Atlas WordPress plugin instead. Install it from WordPress Dashboard → Plugins → Add New → Upload Plugin using the plugin .zip provided by Search Atlas, activate it, and enter your API key when prompted. The plugin handles pixel placement automatically. 7. Check for JavaScript errors. Open your browser's developer tools (F12), go to the Console tab, and reload your homepage. Look for any red errors that mention blocked scripts, CSP (Content Security Policy) violations, or failed network requests related to the pixel. 8. Review your Content Security Policy (CSP) headers. If your host or a security plugin enforces a strict CSP, it may block the pixel script from loading. Add the Search Atlas pixel domain to your CSP allowlist. Contact your hosting provider if you are unsure how to do this. 9. Re-trigger verification in Search Atlas. After making any changes, return to OTTO SEO in the left sidebar and click Verify Pixel or the equivalent re-check button to prompt a fresh detection attempt. 🔌 WordPress Plugin Settings Configuration If you are using the Search Atlas WordPress plugin, check these settings after activation: - API Key: Must match the key shown in your Search Atlas account settings. Copy and paste it directly to avoid typos. - Site URL: Confirm the URL auto-populated by the plugin matches your live domain exactly. - OTTO Pixel UUID: Ensure the correct UUID is entered in the OTTO Pixel UUID field under the Settings tab of the plugin, and that the Disable OTTO Frontend Toolbar toggle is configured as needed. - User Role Restrictions: Some plugin configurations exclude the pixel for logged-in administrators. Test pixel detection while logged out of WordPress or in an incognito browser window. 🌐 Hosting and Server Considerations - Maintenance mode: Plugins like SeedProd or Coming Soon Pro will block pixel detection. Disable maintenance mode before verifying. - Firewall rules: Managed WordPress hosts (WP Engine, Kinsta, Flywheel) have built-in firewalls that can block external script verification requests. Check your host's firewall logs or temporarily whitelist Search Atlas. - SSL/HTTPS issues: A mixed-content warning or an invalid SSL certificate can prevent the pixel from loading. Ensure your site has a valid SSL certificate and that all resources load over HTTPS. 💬 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 Errors on WordPress

🔍 Overview The OTTO pixel connects your website to Search Atlas so OTTO SEO can read your site's data and apply optimisations. On WordPress, the most common setup issues are an incorrectly entered UUID, a misconfigured plugin installation, or a white-label domain that interferes with pixel verification. This article walks you through the correct setup process and explains how to resolve each of these issues. ⚙️ Step 1 — Find Your OTTO Pixel UUID Before touching WordPress, make sure you have the correct UUID from Search Atlas. 1. Log in to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select the project you are connecting. 3. Open the OTTO Pixel or Connect Site section. 4. Copy the full UUID — it is a long alphanumeric string. Copy it directly from the platform to avoid typos. Important: The UUID is unique to each project. If you manage multiple sites, confirm you are copying the UUID that belongs to the exact domain you are configuring. 🔌 Step 2 — Install the Pixel Using the WordPress Plugin Search Atlas provides a dedicated WordPress plugin that inserts the OTTO pixel automatically when you enter your UUID. Follow these steps precisely. 1. In your WordPress admin dashboard, go to Plugins → Add New → Upload Plugin, upload the Search Atlas plugin .zip file provided by Search Atlas, then install and activate the plugin. 2. After activation, go to the Search Atlas top-level menu in the WordPress admin sidebar and open Settings. 3. Paste your UUID into the OTTO Pixel UUID field. Do not add extra spaces, quotation marks, or any other characters around it. 4. Save your settings. Once saved, the plugin automatically injects the pixel script into every page of your site. You do not need to manually copy or paste the full script code anywhere — the plugin handles this for you. If you have been manually inserting script code, remove those manual insertions to avoid duplication conflicts. ✅ Step 3 — Verify the Pixel Is Firing Correctly After saving, return to Search Atlas and use the pixel verification tool to confirm the connection. 1. Navigate back to OTTO SEO → SEO Automation → your project → OTTO Pixel section. 2. Click Verify Pixel or Check Connection. 3. If verification passes, your setup is complete. 4. If you still see a "UUID not correct" error, continue to the troubleshooting steps below. ⚠️ Troubleshooting: "UUID Not Correct" Error If the platform still reports that the UUID is not recognised after following the steps above, work through the following checks in order. - Re-copy the UUID: Select all text in the UUID field in Search Atlas, copy it fresh, clear the WordPress plugin field completely, and paste again. A single wrong character will cause verification to fail. - Check for caching: WordPress caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.) can serve a cached version of your pages that does not yet include the pixel. Clear all caches after saving the plugin settings, then re-run verification. - Check for conflicting scripts: If you previously inserted the OTTO script manually into your theme's functions.php, a header/footer plugin, or Google Tag Manager, remove those manual copies. Duplicate or malformed script instances will cause verification errors. - Confirm the plugin is active: Go to Plugins → Installed Plugins and confirm the Search Atlas plugin status shows Active. An inactive plugin will not inject any code. - Check your domain matches the project: In Search Atlas, confirm the domain listed under the project exactly matches the live URL of your WordPress site, including whether it uses www or not. 🌐 White-Label Domain Conflicts If your Search Atlas account is accessed through a white-label domain (for example, a custom URL like dashboard.youragency.com that points to the Search Atlas platform), this affects only the interface URL you use to log in — it does not affect how the OTTO pixel functions on your client's website. However, there are two scenarios where a white-label domain can indirectly cause issues. - Pixel script source URL: In some configurations, the pixel script may reference the Search Atlas origin domain. If your white-label setup involves custom DNS routing or SSL termination that blocks outbound requests, the pixel call may fail. Confirm with your hosting or DNS provider that your white-label domain correctly passes through all traffic to the Search Atlas platform without blocking script requests. - UUID copied from the wrong environment: If you have both a white-label dashboard and the main Search Atlas dashboard open, ensure you copy the UUID from the same environment where the project is registered. UUIDs are consistent across both interfaces, but double-checking removes any doubt. In most cases, a white-label domain configured correctly as a DNS CNAME or proxy to the Search Atlas platform will not interfere with pixel verification. If you have confirmed all the steps above and the error persists, the issue is most likely a caching layer or a duplicate script conflict rather than the white-label domain itself. 📋 Quick-Reference Checklist - UUID copied directly from OTTO SEO → SEO Automation → project → OTTO Pixel with no extra characters - Search Atlas WordPress plugin installed and Active - UUID pasted into the plugin settings and saved - No manual script copies in theme files, header/footer plugins, or Tag Manager - All WordPress caches cleared after saving - Project domain in Search Atlas matches the live site URL exactly - White-label domain DNS/proxy confirmed as passing through traffic correctly 💬 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 Pixel Installation Status Delays

🧩 What Is This Issue? After installing the Search Atlas tracking pixel on your WordPress site, the platform may continue to show the pixel as not detected or unverified even though you have already added it correctly. This delay is most commonly caused by an active site audit crawl running in the background, which temporarily prevents the system from confirming the pixel's presence. 🔎 Why Does This Happen? Search Atlas verifies your pixel by crawling your website. If a site audit crawl is already in progress when you install or check the pixel, the verification process queues behind it. Until the crawl completes, the pixel status will not update — even if the pixel is installed perfectly. This is expected platform behaviour and not a sign that your installation is broken. ✅ How to Confirm Your Pixel Is Installed Correctly Before waiting for the platform to update, manually verify the pixel is live on your site by following these steps: 1. Open your WordPress site in a browser (for example, mipcare.com). 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (Windows) or Cmd + F (Mac) to open the search bar. 4. Search for your Search Atlas pixel ID or the pixel script snippet. 5. If the snippet appears in the source code, your pixel is installed correctly and the platform will confirm this once the crawl finishes. If the snippet does not appear in the page source, the pixel may not have been saved properly. See the reinstallation steps below. ⏱️ How Long Should I Wait? In most cases, pixel status updates within a few hours after the site audit crawl completes. If more than 24 hours have passed and the status still shows as unverified, proceed to the troubleshooting steps below. 🛠️ Troubleshooting Steps 1. Check the pixel is saved in WordPress. Go to your WordPress dashboard, navigate to the plugin or theme section where you added the pixel snippet, and confirm the code is still present and saved. 2. Clear your WordPress cache. If you use a caching plugin such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, clear all cached files after installing the pixel. A cached version of your site may hide the pixel from the crawler. 3. Disable conflicting plugins temporarily. Security or performance plugins can sometimes block external crawlers. Temporarily disable them and re-trigger a pixel check. 4. Re-verify from the platform. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and locate your site's pixel settings. Use the Re-verify or Check Again option if available to trigger a fresh verification crawl. 5. Confirm no site audit is running. Go to Left sidebar → Site Metrics (Site Explorer) (URL: /site-explorer/list) and check whether a crawl is currently active for your domain. If one is running, wait for it to finish before re-checking pixel status. 💡 Tips to Avoid This Issue in Future - Install or update your pixel outside of scheduled crawl windows to get faster verification. - Always clear your site cache immediately after adding or updating the pixel snippet. - Use the page source method described above as a quick first check before contacting support. 🆘 Still Need Help? If you have followed all the steps above and the pixel status is still not updating after 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.

🔧 Fix OTTO Pixel Plugin WordPress Installation Errors

Overview If you keep seeing an OTTO Pixel Not Installed Correctly error after installing or reinstalling the plugin on WordPress, the problem is rarely the plugin itself. Two root causes account for almost every case: the Site Audit crawl has not completed, or a security or cache service is blocking the OTTO bot before it can verify the connection. Follow the steps below in order to resolve the error. Step 1: Confirm the OTTO Pixel Plugin Is Installed 1. Log in to your WordPress admin panel. 2. Go to Plugins → Installed Plugins and confirm the OTTO Pixel plugin is listed and active. 3. If it is deactivated, activate it and wait 30 seconds before proceeding. 4. Avoid reinstalling the plugin repeatedly — multiple reinstalls do not fix connection issues caused by crawl or bot-blocking problems. Step 2: Run and Complete a Site Audit Crawl OTTO cannot verify the pixel connection until a Site Audit crawl has finished successfully for the connected domain. This is the most common cause of the error and is often overlooked. 1. Log in to Search Atlas and navigate to OTTO SEO → Site Audit for your connected website. 2. Check the crawl status. If no crawl has run, or the last crawl did not complete, start a new crawl and wait for it to finish. Crawl time varies by site size — do not close the tab. 3. Once the crawl shows a completed status, return to the OTTO dashboard and check whether the pixel connection error has cleared. Important: A crawl that was interrupted or that returned errors may not satisfy the connection requirement. Confirm the crawl has fully completed before moving on. Step 3: Whitelist the OTTO Bot in Security and Cache Services Firewalls, CDNs, and caching plugins frequently block automated bots — including the OTTO crawler — which prevents OTTO from reaching your site to confirm pixel installation. You must whitelist the OTTO bot in every active security or cache layer. Cloudflare (most common) 1. Log in to your Cloudflare dashboard and select your domain. 2. Locate your firewall or WAF settings and add an allow rule for the OTTO bot. Contact our support team (see below) to obtain the exact IP range or user agent string to allowlist. 3. Alternatively, temporarily lower your security level, trigger a new Site Audit crawl to confirm the pixel connection clears, then restore your original security settings. 4. Once verified, add a permanent allow rule so the OTTO bot can reach your site going forward. Sucuri, Wordfence, or other security plugins 1. Open the settings for your active security plugin inside WordPress. 2. Find the IP allowlist or bot whitelist option and add the OTTO bot. Contact our support team (see below) to obtain the exact IP range or user agent string to allowlist. If you need further assistance, open 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 Authentication & Communication Errors

🧭 Overview If your OTTO pixel shows as Connected inside the WordPress plugin but the Search Atlas dashboard cannot communicate with it — and you see an Authentication credentials were not provided error — this is a known authentication sync failure between the OTTO WordPress plugin and Search Atlas. Cache clearing and reinstalling the plugin alone will not resolve this type of error. Because the exact steps to fix this depend on your specific account and site configuration, the most reliable path is to contact our support team directly so an agent can investigate and resolve it on your account. ⚠️ What This Error Typically Indicates - The API credentials stored in the plugin are missing, expired, or out of sync with Search Atlas. - The plugin installation itself is generally not the root cause. - A mismatch between the site URL registered in Search Atlas and the live WordPress site URL may contribute to the failure. - Security plugins, firewalls, or caching layers on the WordPress side can sometimes interfere with authentication requests. 📋 Before You Contact Support — What to Have Ready To help our team resolve this as quickly as possible, please have the following information available when you reach out: - The exact error message you are seeing (e.g., Authentication credentials were not provided). - The domain/URL of the affected WordPress site. - The name of the Search Atlas project or site the OTTO pixel is connected to. - The date and approximate time the error first appeared. - Whether any recent changes were made — such as regenerating an API key, switching from HTTP to HTTPS, installing a new security or caching plugin, or migrating the site. - Any other active WordPress plugins that handle security, firewalls, or HTTP authentication. 🛠️ While You Wait You can take the following general steps to rule out common environmental causes before an agent reviews your account: - Confirm that the site URL registered in Search Atlas exactly matches your live WordPress site URL — including the same protocol (https://) and the same trailing slash convention. - Temporarily deactivate any security or firewall plugins on your WordPress site to test whether they are stripping authentication headers from outgoing requests. - Clear any server-side or CDN cache layers so that requests are not being served stale or blocked responses. - Do not reinstall the plugin or regenerate your API key until an agent confirms this is the correct next step — doing so without guidance can complicate diagnosis. If you need further assistance, open 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 Installed Correctly' WordPress Plugin Error

🧩 Why This Error Appears Even When OTTO Receives Data If you see the message "Pixel is not installed correctly" inside Search Atlas but your data is still flowing into OTTO, you are not alone. This is a known discrepancy that commonly affects WordPress plugin installations. The error does not always mean your pixel is broken — it often means the platform's verification check cannot confirm the pixel's presence in the expected way, even though the pixel is firing successfully in the background. The two most frequent causes are: - A caching layer (plugin, server, or CDN) is preventing the verification script from reading the latest version of your page. - The pixel code is being injected by the Search Atlas WordPress plugin in a way that is valid for data collection but is not detected by the standard installation checker. 🔍 Step 1 — Confirm Your Pixel Is Actually Firing Before making any changes, verify that data collection is genuinely working: 1. Log in to Search Atlas and open OTTO. 2. Check the data dashboard for recent activity — page views, events, or session data recorded within the last 24 hours confirm the pixel is firing. 3. Open your WordPress site in a browser, right-click the page, and select View Page Source. 4. Use Ctrl + F (or Cmd + F on Mac) to search for your Search Atlas pixel ID or the pixel script snippet. 5. If the snippet appears in the source code, your pixel is installed. The error is a false positive caused by the verification mechanism, not a genuine installation failure. ⚡ Step 2 — Clear All Caching Layers Caching is the most common reason the pixel checker returns a false error. Complete all of the following steps in order: 1. Clear your WordPress caching plugin. Go to your WordPress admin panel, open your caching plugin (for example, WP Rocket, W3 Total Cache, or LiteSpeed Cache), and purge all cached files. 2. Clear your server-side cache. If your hosting provider offers server caching (such as Kinsta, WP Engine, or SiteGround), log in to your hosting dashboard and flush the server cache. 3. Clear your CDN cache. If you use Cloudflare or another CDN, log in and purge the cache for your entire domain. 4. Clear your browser cache. In your browser settings, clear cached images and files, then reload your site. 5. Return to Search Atlas and trigger the pixel verification check again. 🔌 Step 3 — Check the WordPress Plugin Settings Confirm the Search Atlas plugin is configured correctly inside WordPress: 1. In your WordPress admin panel, go to Plugins and confirm the Search Atlas plugin is active. 2. Open the plugin settings and verify your pixel ID matches the one displayed inside your Search Atlas account under the pixel configuration section. 3. Check that no other SEO or analytics plugin is conflicting with the pixel output. Plugins that modify the <head> section aggressively can occasionally strip or reorder scripts. 4. If you have a security plugin (such as Wordfence or iThemes Security), check whether script blocking or file change detection is enabled, as these can interfere with pixel injection. 🛠️ Step 4 — Manually Verify Pixel Placement If clearing caches does not resolve the error, manually confirm where the pixel is being output on your page: 1. Install the browser extension for your preferred web inspector or use Chrome DevTools (F12). 2. Open the Elements tab and expand the <head> section of your page. 3. Search for the Search Atlas pixel script. It should appear before the closing </head> tag. 4. If the script is present but placed inside a tag or wrapper that the verification check does not scan (for example, injected via a tag manager or deferred loading), this will cause a false-negative result from the checker even though the pixel fires correctly. 5. If you use Google Tag Manager to deploy the pixel rather than the WordPress plugin directly, note that GTM-based deployments can sometimes fail the built-in checker. Data will still flow to OTTO, but you may need to add the pixel snippet directly to the theme or plugin instead of through GTM. ✅ Step 5 — Re-run the Pixel Verification Check After completing the steps above, return to Search Atlas: 1. Navigate to the pixel or tracking settings section of your account. 2. Click Verify Installation or the equivalent re-check button. 3. Allow up to 5 minutes for the check to complete if your site is large or has a slow response time. 4. If the error clears and data continues flowing into OTTO, the issue is fully resolved. 5. If the error persists but data is still flowing into OTTO normally, your pixel is functional. You can continue using the platform without interruption while the discrepancy is investigated further. 📋 When to Escalate Contact support if any of the following apply: - Data has stopped flowing into OTTO and the pixel error is showing simultaneously. - You completed all steps above and the pixel snippet does not appear anywhere in your page source. - You recently updated the Search Atlas WordPress plugin or switched themes and the error appeared immediately after. If you need further assistance, open 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 Detection Errors on WordPress

🧩 Why These Errors Happen After installing the OTTO pixel on WordPress, you may see errors in your Search Atlas dashboard indicating that the pixel was not detected or that a duplicate installation was found. These issues typically occur because a caching layer is preserving an outdated snapshot of your page. The pixel exists in your live code, but the detection check is reading stale cached output instead. A common scenario for duplicate detection errors is switching from one installation method to another (for example, from a manual script to the OTTO WordPress plugin) without fully clearing the old cached version, so both appear active at the same time. In both cases the root cause is the same: a caching layer is preserving an outdated snapshot of your page. Simply disabling a caching plugin does not fix this — the cached files already saved to your server continue to be served until you actively purge them. ⚠️ Disabling vs. Purging: A Critical Difference Many customers turn off their caching plugin expecting the problem to clear automatically. This is the most common reason these errors persist. Understand the distinction: - Disabling a caching plugin stops new cache files from being created, but leaves all existing cached pages on your server untouched. Detection checks still read those old files. - Purging the cache deletes the stored snapshots immediately, forcing WordPress to rebuild each page from live code the next time it is requested. This is the step that allows the OTTO pixel detector to see your current installation. Always purge — do not just disable. 🛠️ Step 1: Purge Your WordPress Cache Follow the instructions for whichever caching solution your site uses. The exact menu location and button label will vary by plugin and version — consult your plugin's own documentation if you are unsure where to find the purge option. WordPress caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, and others) 1. Log in to your WordPress admin panel. 2. Locate your caching plugin in the admin sidebar or Settings menu. 3. Look for a Purge, Clear Cache, or equivalent option and run it. 4. Wait for confirmation that the cache has been cleared before proceeding. Hosting-level cache (SiteGround, Cloudways, Kinsta, and other managed hosts) Many managed hosts add a server-side caching layer that is separate from any plugin. Log in to your hosting control panel and look for a Purge Cache or Clear Cache option. 🔄 Step 2: Re-check Pixel Detection After purging all cache layers, return to the Home page and re-run the OTTO pixel detection check. In most cases the error will resolve once the cached pages have been replaced with the current live version of your site. If you have recently switched installation methods (for example, from a manual script to the OTTO WordPress plugin), verify that the old installation method has been fully removed before re-checking. Having two installation methods active simultaneously is the most common cause of duplicate detection errors. 📋 If the Error Persists If the pixel is still showing as not detected or duplicated after purging your cache, gather the following before reaching out for support: - Your WordPress site URL - The exact error message shown in your Search Atlas dashboard - Which caching plugin(s) or managed hosting provider you are using - Which OTTO pixel installation method you used (manual script, WordPress plugin, or other) If you need further assistance, open 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 Not Engaging on WordPress

🔍 Overview If the OTTO pixel shows as inactive or not engaging on your WordPress site, the issue is almost always related to how the pixel code is installed — or a mismatch between the site connected in Search Atlas and the URL where the pixel is deployed. This guide walks you through the correct installation steps and how to clean up duplicate sites in your account. ⚙️ How the OTTO Pixel Works The OTTO pixel is a small snippet of JavaScript that Search Atlas uses to verify ownership of your site and activate AI-powered SEO automation. For OTTO to engage, the pixel must be: - Installed on every page of your WordPress site (ideally in the <head> section) - Deployed on the exact URL that is connected inside Search Atlas - Publicly accessible — not blocked by a login wall, maintenance mode, or robots.txt 🚀 Install the OTTO Pixel on WordPress Follow these steps to install the OTTO pixel correctly on WordPress using the Search Atlas (MetaSync) plugin: 1. Install and activate the Search Atlas (MetaSync) plugin in your WordPress admin dashboard. 2. In WordPress, open Search Atlas → Settings. 3. Paste your Search Atlas API key into the designated field. 4. Paste your OTTO Pixel UUID into the designated field and save your changes. 5. Visit your live site to confirm the page loads correctly, then return to Search Atlas and click Verify Pixel. The status should update to Active within a few minutes. Note: The raw JavaScript pixel snippet is intended for non-WordPress platforms or alternative installs such as Google Tag Manager — on WordPress, the MetaSync plugin handles the pixel for you. 🔎 Common Reasons the Pixel Does Not Engage If verification still fails after installation, check the following: - Wrong URL connected: The site URL in Search Atlas must exactly match your live site URL — including or excluding www and https://. Even a small mismatch will prevent detection. - Caching plugin: If you use a caching plugin (e.g., WP Rocket, W3 Total Cache), purge the cache after installing the pixel so the new code is served to visitors. - Maintenance mode active: Plugins like SeedProd or Coming Soon Page will block Search Atlas from reading your site. Temporarily disable maintenance mode during verification. - Pixel placed in footer instead of header: Some themes and plugins delay footer scripts. Always place the pixel in the header section. - Security or firewall plugin blocking crawlers: Tools like Wordfence or Cloudflare may block external bots. Whitelist Search Atlas or temporarily pause the firewall during verification. - Pixel code was modified: Paste the code exactly as provided — do not edit or wrap it in additional tags. 🗂️ Fix Duplicate Sites in Your Account Duplicate sites typically appear when the same domain is added more than once — for example, once with www and once without, or once with http and once with https. To clean this up: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Review the list of connected sites and identify any duplicates. 3. Determine which version of the URL is your canonical (primary) site — this should match your WordPress Site Address found in Settings → General in WordPress. 4. Remove the duplicate entry by selecting it and choosing Delete Site or the equivalent remove option. 5. Ensure the pixel is only installed and verified on the correct, canonical URL going forward. Keeping duplicate sites active can split your OTTO activation data and prevent the pixel from engaging correctly, so it is important to remove them promptly. ✅ Verify Everything Is Working Once you have completed installation and removed duplicates, confirm the setup is correct: - Visit your live site and use your browser's View Page Source (right-click → View Page Source) to search for the OTTO pixel code. It should appear inside the section. - Return to Search Atlas (OTTO SEO → All Sites (SEO Automation) / /seo-automation-v3) and click Verify Pixel. - The OTTO status should change to Active or Engaging within a few minutes. 💬 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 Blocked by Security Plugins

🧭 Overview If your Search Atlas account is authenticated and synced successfully but the OTTO pixel still shows OTTO not found, a WordPress security plugin or Web Application Firewall (WAF) is most likely blocking the pixel script from loading or being written to your site. This is the most common root cause of this error and is not resolved by clearing your cache. This article walks you through identifying and resolving security plugin conflicts so OTTO can install and verify correctly. ⚠️ Why Security Plugins Block OTTO Security plugins like Wordfence, Sucuri, iThemes Security, and Cloudflare WAF are designed to block unfamiliar scripts and external code injections. Because the OTTO pixel is injected programmatically during installation, these tools can silently block or remove it before Search Atlas is able to verify its presence — even when your credentials and sync status appear healthy inside the platform. Common symptoms of this conflict include: - Account authentication shows as successful in Search Atlas - Site sync completes without errors - OTTO pixel status remains OTTO not found after multiple installation attempts - No visible error message in WordPress or your hosting dashboard 🔍 Step 1 — Identify Whether a Security Plugin Is the Cause 1. Log in to your WordPress admin panel. 2. Go to Plugins → Installed Plugins and check whether any of the following are active: Wordfence Security, Sucuri Security, iThemes Security (now Solid Security), All In One WP Security, Cloudflare (with WAF enabled), or any other firewall or malware-scanning plugin. 3. If one or more of these plugins are active, proceed to Step 2 for your specific plugin. If none are active, skip to Step 4. 🛡️ Step 2 — Whitelist OTTO in Your Security Plugin The confirmed root cause for this error is a security plugin — most commonly Wordfence — blocking the OTTO pixel script from being written to or loaded on your site. The general fix is to whitelist or allowlist the Search Atlas pixel script within your security plugin's settings so it is not blocked or removed. Because the exact menu labels and navigation paths vary by plugin and plugin version, consult your security plugin's own documentation for instructions on how to whitelist or allowlist an external script or URL. Apply this to each active security plugin on your site. When whitelisting, you will need to permit the Search Atlas pixel script domain and endpoint. If you are unsure of the exact URL or script path to whitelist, contact support using the instructions at the bottom of this article and a team member will provide it. General steps for any security plugin: 1. Log in to your WordPress admin panel. 2. Open the settings for your active security plugin. 3. Locate the firewall, script blocking, or allowlist/whitelist section within that plugin. 4. Add the Search Atlas pixel script URL or domain to the allowlist. 5. Save your changes and then retry the OTTO pixel installation from within Search Atlas. 🔄 Step 3 — Retry OTTO Installation 1. After updating your security plugin settings, return to your Search Atlas account. 2. Attempt to reinstall the OTTO pixel. 3. Wait a few minutes, then refresh the page to check whether the pixel status has updated from OTTO not found to a verified state. 🚨 Step 4 — If the Issue Persists If the OTTO pixel still shows as not found after whitelisting within your security plugin, there may be a second conflicting plugin, a hosting-level firewall, or another script-blocking rule in place. When escalating, please have the following ready: - Your site URL and the Search Atlas project name - The name and version of all active security or firewall plugins - Confirmation of what you have already whitelisted - Any error messages or logs from your security plugin If you need further assistance, open 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 Plugin Timeout and Throttling Errors

🧭 Overview When authenticating the OTTO pixel WordPress plugin, you may encounter two related issues: the authentication pop-up completes successfully but the connection times out before finishing, or repeated attempts trigger a Request Throttled error. These are distinct problems — this article explains what each error means and what to expect. ⚠️ Understanding the Two Errors Before troubleshooting, it helps to know what each error means: - Connection timeout during authentication: The plugin authenticated your credentials in the pop-up but the handshake between your WordPress site and Search Atlas did not complete in time. - Request Throttled error: After several failed or repeated authentication attempts in a short period, Search Atlas temporarily limits further requests from your site. This is not a permanent block. ⏳ Step 1 — Stop Retrying and Wait If you are currently seeing a Request Throttled error, stop attempting to reconnect immediately. Additional attempts may worsen the situation. 1. Close the OTTO pixel authentication pop-up in your WordPress dashboard. 2. Wait before attempting to reconnect. Because the exact duration and conditions depend on your account and situation, our support team can advise on next steps for your specific case. 3. Do not reload the authentication pop-up or navigate to the OTTO pixel settings while waiting. Once you have waited, you can attempt authentication again. If the issue persists, contact our support team for guidance tailored to your account. 🔧 Step 2 — Contact Support if the Issue Continues If you continue to see a connection timeout or a Request Throttled error after waiting, our team will need to investigate the specific conditions affecting your site and account. To help us assist you as quickly as possible, please have the following ready: - Your WordPress site URL - The exact error message you are seeing (a screenshot is helpful) - The approximate date and time the error first appeared - A note of how many authentication attempts you have made If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 OTTO Pixel WordPress Troubleshooting: Plugin Conflicts

🧭 Overview If the OTTO pixel is not connecting to your WordPress site after multiple attempts, the most common causes are plugin conflicts and cached code preventing the pixel from loading correctly. Follow the steps below in order to help resolve the issue. ⚠️ Known Conflicting Plugins The following types of plugins are known to interfere with OTTO pixel installation on WordPress: - SEO plugins — Can block or interfere with header scripts injected by OTTO. - Caching plugins — Serve stale page versions that do not include the OTTO pixel. - Security or firewall plugins — May block external script injection entirely. You do not need to permanently remove these plugins. In most cases, temporarily disabling them, re-attempting the pixel installation, and then re-enabling them resolves the conflict. 🛠️ Step-by-Step Fix 1. Access the OTTO section in Search Atlas. Navigate to the OTTO section for your website in Search Atlas. 2. Log in to your WordPress admin dashboard in a separate browser tab. 3. Deactivate conflicting plugins temporarily. Go to Plugins → Installed Plugins. Deactivate any active SEO plugin, caching plugin, and security/firewall plugin. Do not delete them — deactivating is enough. 4. Clear all WordPress cache layers. If your caching plugin has a settings page, open it and clear all cached files before deactivating. 5. Clear your browser cache. In your browser settings, select the option to clear cached images and files for all time. 6. Return to Search Atlas and retry the OTTO pixel installation. Follow the on-screen steps in the OTTO section to reconnect the pixel for your site. 7. Allow a few minutes before verifying. After completing the installation steps, allow a few minutes for the pixel signal to register. Then revisit your website in a new private/incognito window and confirm the pixel is active. 8. Re-enable your plugins one at a time. Reactivate each previously deactivated plugin individually and check the pixel status after each reactivation. If the pixel stops working after reactivating a specific plugin, that plugin is the source of the conflict. Leave it deactivated and contact support for guidance on a permanent fix. 📋 Before Escalating If the steps above do not resolve the issue, please have the following ready when you contact support: your WordPress site URL, the name of any plugin you identified as conflicting, and a description of where in the process the pixel connection fails. If you need further assistance, open 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 Pixel Installation Error Messages

🔍 Overview If you see a "Pixel is not installed correctly" warning inside Search Atlas or OTTO, but your pixel appears to be pulling data successfully, this is almost always a verification timing issue — not a real installation problem. This article explains why this happens and what steps to take. 💡 Why This Warning Appears The pixel verification system runs an automated check to confirm your tracking pixel is live and properly placed on your WordPress site. This check can occasionally return a false-negative error due to the following reasons: - Caching: Your WordPress site or a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) may be serving an older cached version of your page that does not yet include the pixel code. - Verification delay: After installing the pixel, the system may need a few minutes to re-check and confirm the installation. The error message can persist briefly even when the pixel is live. - Plugin conflicts: Another WordPress plugin may be stripping or blocking third-party scripts before they render in the page source. - Cookie consent tools: If you use a cookie consent or GDPR compliance plugin, it may be blocking the pixel from firing until a user accepts cookies — causing the automated check to miss it. ⚙️ How to Troubleshoot Step by Step 1. Confirm data is flowing: If OTTO is already receiving data from your site, your pixel is functionally installed. The warning is likely a stale verification status. 2. Clear your site cache: Log in to your WordPress dashboard, open your caching plugin, and purge all cached files. If your hosting provider offers server-level caching (e.g., Kinsta, WP Engine), clear that cache too. 3. Check the pixel in your page source: Visit your website, right-click the page, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for your pixel ID. If you can find it in the source code, the pixel is installed correctly. 4. Re-trigger the verification check: Inside Search Atlas, navigate to the pixel settings and click the option to re-verify or re-check your pixel installation. Allow 2–5 minutes for the system to complete the check. 5. Review cookie consent settings: If you use a GDPR or cookie consent plugin, make sure your pixel script is not categorised as a blocked or opt-in-only script. You may need to whitelist the Search Atlas pixel domain within your consent tool settings. 6. Deactivate plugins temporarily: To rule out a plugin conflict, temporarily deactivate other plugins one at a time (especially security or script-optimisation plugins) and re-check whether the pixel appears in your page source after each deactivation. 7. Check script placement: The Search Atlas WordPress plugin should automatically insert the pixel in the correct location. If you manually added the pixel code, verify it is placed inside the <head> section of your theme and not accidentally removed by a theme update. ✅ How to Confirm the Pixel Is Working Correctly Even while the error message is visible, you can confirm your pixel is operating normally by checking the following: - Data such as sessions, events, or conversion signals is actively appearing inside OTTO or your Search Atlas dashboard. - Your pixel ID is visible in the page source of your live website. - No JavaScript console errors related to the Search Atlas pixel appear when you open your browser's developer tools and visit your site. If all three conditions are true, your pixel is installed and working. The warning message will typically resolve itself once the automated verification re-runs successfully. 🚀 Prevent This Issue in the Future - Always clear your site cache immediately after installing or updating the Search Atlas WordPress plugin. - After any major WordPress update or theme change, re-verify your pixel inside Search Atlas to ensure nothing was disrupted. - Keep the Search Atlas WordPress plugin updated to the latest version to benefit from compatibility improvements. 🙋 Still Seeing the Error? If you have completed all the steps above and the "Pixel is not installed correctly" warning persists — especially if no data is flowing into OTTO — there may be a site-specific configuration issue 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 Pixel and Title Tag Deployment Issues

🔍 Overview Two of the most common WordPress-related issues in Search Atlas are: (1) a 'failed to fetch' error when installing the OTTO SEO pixel, and (2) deployed title tag changes that do not appear on your live site. Both problems usually share the same root cause — a conflict caused by having more than one active deployment method running at the same time. ⚠️ Why These Issues Happen Search Atlas can deploy changes to your WordPress site in two ways: - WordPress Plugin — the OTTO SEO plugin installed directly in your WordPress admin. - Cloudflare Worker — a script that intercepts and modifies pages at the network level. When both methods are active on the same project at the same time, they conflict with each other. This duplicate install state causes pixel fetch failures, prevents title tags from updating, and can even produce duplicate meta title tags on your homepage. You must use one method only. 🛠️ Step 1 — Check for a Duplicate Install 1. Log in to Search Atlas and open your project. 2. Navigate to Left sidebar → OTTO SEO → Installation Guide to view the Pixel Installation settings. 3. Check whether both the WordPress Plugin and a Cloudflare Worker are shown as active. 4. If both are enabled, this is the cause of your issues. Continue to Step 2. 🔧 Step 2 — Remove the Duplicate Deployment Method Decide which installation method you want to keep, then disable the other one completely. If you want to keep the WordPress Plugin: 1. Log in to your Cloudflare dashboard. 2. Go to Workers & Pages and locate the OTTO SEO worker assigned to your domain. 3. Disable or delete the worker. 4. Return to Search Atlas and confirm the pixel status shows only the plugin as active. If you want to keep the Cloudflare Worker: 1. Log in to your WordPress admin panel. 2. Go to Plugins and deactivate and delete the OTTO SEO plugin. 3. Return to Search Atlas and confirm the pixel status shows only the Cloudflare Worker as active. ✅ Step 3 — Reinstall the Pixel (If Needed) If you removed the plugin and are starting fresh with it, follow these steps to reinstall cleanly: 1. In Search Atlas, go to Left sidebar → OTTO SEO → Installation Guide and select WordPress Plugin. 2. Download the latest plugin file or copy your unique pixel snippet. 3. In your WordPress admin, go to Plugins > Add New > Upload Plugin and install the file. 4. Activate the plugin and return to Search Atlas to verify the pixel shows a connected status. Note: If you see a 'failed to fetch' error during installation, it almost always means an old Cloudflare Worker is still active. Confirm the worker has been fully removed before retrying. 📝 Step 4 — Fix Title Tags Not Updating Once only one deployment method is active and the pixel is confirmed connected, title tag changes should deploy correctly. If a previously deployed title tag is still not appearing live, follow these steps: 1. In Search Atlas, go to the page where the title tag change was deployed. 2. Check the deployment status — if it shows an error, redeploy the change. 3. Clear any caching on your WordPress site. Go to your caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) and purge all caches. 4. If you use Cloudflare, log in to your Cloudflare dashboard and go to Caching > Configuration > Purge Everything. 5. Visit your live page and perform a hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to bypass your browser cache. If the title tag is still showing the old value after completing these steps, check whether a theme or SEO plugin (such as Yoast SEO or Rank Math) is overriding the title tag. These plugins can conflict with Search Atlas deployments. 🔌 Resolving CSS or Plugin Conflicts In some cases, the OTTO SEO plugin may conflict with your WordPress theme or another active plugin, preventing changes from rendering correctly. To isolate the issue: - Temporarily switch to a default WordPress theme (such as Twenty Twenty-Four) and test whether the title tag appears correctly. - Deactivate other SEO plugins one at a time and check after each deactivation. - Re-enable plugins one by one to identify which one causes the conflict, then reach out for support. 💡 Quick Reference — Common Causes and Fixes - 'Failed to fetch' on pixel install — Remove the duplicate deployment method (plugin or Cloudflare Worker), then reinstall. - Title tag not updating — Confirm pixel is connected, redeploy the change, and purge all caches. - Duplicate meta title on homepage — A sign of a duplicate install state; remove one deployment method. - Changes deploy in Search Atlas but not visible on site — Check for caching layers and conflicting SEO plugins. 💬 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 UUID Errors and Plugin Connection

Overview To use OTTO SEO on your website, two things must be in place: the Search Atlas plugin must be installed and connected to your Search Atlas account using a unique identifier called a UUID. If these steps are incomplete or misconfigured, you may see an error indicating that OTTO cannot fetch data from the API. This article walks you through the full setup and how to fix that error. What Is a UUID in Search Atlas? A UUID (Universally Unique Identifier) is a code that links your website's Search Atlas plugin directly to your OTTO SEO project inside the platform. Think of it as a secure handshake — the plugin uses this code to send and receive data from Search Atlas. If the UUID is missing, wrong, or not saved correctly in the plugin settings, the connection breaks and OTTO cannot fetch your site's data. Step 1: Install the Search Atlas Plugin on Your Website 1. Log in to your WordPress dashboard. 2. Locate the plugin installation area and search for Search Atlas. 3. Install and activate the plugin. 4. Once activated, the Search Atlas plugin will be available in your WordPress dashboard. Step 2: Connect the Plugin to Your Search Atlas Account Installing the plugin is not enough — you must connect it to your account using your UUID. Follow these steps carefully: 1. Log in to the Search Atlas platform and navigate to the OTTO SEO section. 2. Open or create your OTTO project and locate your OTTO UUID. This is a unique code tied to your specific OTTO project. 3. Copy the UUID exactly — do not add spaces or extra characters. 4. Go back to your WordPress dashboard and open the Search Atlas plugin settings. 5. Paste your UUID into the UUID field within the plugin settings and save your settings. Still Seeing the Error? If you have followed the steps above and still see an API error, please have the following information ready before reaching out: - Your OTTO project name - The exact error message you see (including any codes or details shown) - The timestamp when the error occurred - Confirmation of whether the UUID was saved in the plugin settings If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Script Not Recognized on WordPress

🔍 Overview If you have installed the OTTO script on your white-label WordPress site but the Site Auditor still shows "not installed" or returns an "incorrect domain" error, this guide walks you through the most common causes and how to fix them. ⚠️ Common Causes of This Error - The domain registered in Search Atlas does not exactly match the URL of your WordPress site. - A legacy Search Atlas pixel is installed instead of the current OTTO pixel. - The script was added to the wrong location in the WordPress theme or a caching plugin is serving an old version of the page. - A security tool (such as Avast or a firewall plugin) is blocking or stripping the OTTO script before it loads. - The site uses Google Tag Manager (GTM) and the tag is not firing correctly on all pages. ✅ Step 1 — Verify the Domain in Search Atlas 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Open your OTTO project and locate the domain listed at the top of the project settings. 3. Compare this domain exactly with the URL of your WordPress site — including whether it uses www or non-www, and http vs https. 4. If there is any mismatch, update the domain in the project settings to match your live site URL precisely. 🔄 Step 2 — Replace Any Legacy Script An older Search Atlas pixel will not be recognized by the current OTTO system. To get the correct, up-to-date script: 1. Inside your OTTO project, click Connect OTTO or Get Script to copy the current pixel code. 2. Log in to your WordPress admin dashboard. 3. Go to Appearance → Theme File Editor (or use a header/footer plugin such as Insert Headers and Footers). 4. Remove any existing Search Atlas or OTTO script that is already present. 5. Paste the new OTTO script inside the section of every page. 6. Save your changes. 🏷️ Step 3 — If You Are Using Google Tag Manager Deploying the OTTO pixel through GTM requires the tag to fire on all pages, not just the homepage. 1. In GTM, open the tag containing the OTTO script. 2. Confirm the trigger is set to All Pages. 3. Publish the GTM container to push the change live. 4. Use GTM Preview mode to confirm the tag fires on multiple pages of your site, including internal pages. 🛡️ Step 4 — Check for Security Plugin or Antivirus Interference Some security tools flag the OTTO pixel on white-label domains. To check whether this is happening: - Temporarily disable any WordPress security plugins (e.g., Wordfence, iThemes Security) and reload the page to see if the script is recognized. - If your visitors use Avast or similar antivirus software, the script may be blocked client-side — contact our team using the chat widget below for guidance on whitelisting the OTTO domain for your brand. - Re-enable your security plugins after testing. 🧹 Step 5 — Clear Caches and Re-verify 1. Clear your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache). 2. Clear any CDN cache (e.g., Cloudflare) by purging all files. 3. Open your site in a private or incognito browser window and view the page source (Ctrl + U on Windows, Cmd + U on Mac). 4. Search for the OTTO script in the source code to confirm it is present and unmodified. 5. Return to your OTTO project in Search Atlas and click Verify Installation to trigger a fresh check. 📊 Step 6 — Run a New Site Audit Once the script is confirmed in the page source, trigger a fresh audit to update the recognition status: 1. Go to OTTO SEO → Site Audit → Overview (Website Overview) in the left sidebar. 2. Open your project and click Recrawl Site. 3. Wait for the crawl to complete — this may take a few minutes depending on site size. 4. Check that the OTTO status now shows Active and that the domain error has cleared. 💡 Still Seeing the Error? If the domain error or "not installed" status persists after completing all steps above, there may be a configuration issue specific to your white-label setup 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 OTTO Pixel Blocked by Wordfence

🔍 What Is Happening? When Wordfence Security is active on your WordPress site, it can silently block the OTTO pixel script from loading — even if your Search Atlas account is authenticated and synced successfully. This causes the OTTO activation panel to display an "OTTO not found" error, because Wordfence intercepts the pixel request before it reaches your site. This is one of the most common reasons OTTO appears connected in Search Atlas but remains undetected on your website. ⚙️ Before You Begin Confirm the following before making any changes to Wordfence: - You are logged in to your WordPress admin dashboard with administrator access. - The Wordfence Security plugin is installed and active. - In Search Atlas, your site shows a successful account authentication and sync status under SEO Automation (Left sidebar → OTTO SEO → SEO Automation). - The OTTO status still reads "OTTO not found" despite the successful sync. 🛠️ How to Whitelist the OTTO Pixel in Wordfence Follow these steps to allow the OTTO pixel through Wordfence's firewall: 1. Log in to your WordPress Admin Dashboard. 2. In the left sidebar, click Wordfence, then select Firewall. 3. Click the Allowlisted URLs tab (sometimes labelled Whitelisted URLs depending on your Wordfence version). 4. Click Add URL to Allowlist. 5. In the URL field, enter the OTTO pixel endpoint. Use the exact URL provided in your Search Atlas OTTO installation instructions. It typically follows the pattern: yourdomain.com/?otto_pixel=1 — copy it directly from the Search Atlas platform to avoid typos. 6. Leave the Parameter fields blank unless Wordfence specifically prompts you to add one. 7. Click Save. After saving, Wordfence will stop blocking requests matching that URL pattern. ✅ Verify the Pixel Is Now Detected 1. Return to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation. 2. Locate your site and open the OTTO activation panel. 3. Click Re-check or Refresh Status to trigger a new pixel detection scan. 4. The status should update from "OTTO not found" to "OTTO Active" within a few seconds. If the status does not update immediately, wait two to three minutes and refresh the page. Detection can occasionally take a short time after the allowlist rule is saved. 💡 Additional Wordfence Settings to Check If whitelisting the URL alone does not resolve the issue, check these additional Wordfence settings: - Web Application Firewall (WAF) rules: Wordfence's WAF may have a rule blocking inline scripts. Under Wordfence → Firewall → All Firewall Options, temporarily set the WAF to Learning Mode, trigger the OTTO pixel, then review the blocked requests log to identify and allowlist the specific rule. - Brute Force Protection: If your site limits external requests aggressively, check Wordfence → Login Security and confirm that OTTO's server IP range is not blocked. Search Atlas uses fixed outbound IPs — contact support (see below) if you need the current IP list. - Live Traffic blocking: Go to Wordfence → Tools → Live Traffic and filter by Blocked to see if OTTO pixel requests appear. If they do, click the request and choose Allowlist this IP or Allowlist this URL. 🚫 Common Mistakes to Avoid - Do not deactivate Wordfence entirely as a test — this exposes your site to security risks and is unnecessary. - Do not confuse authentication errors with pixel errors. A successful sync in Search Atlas means your API credentials are correct, but it does not confirm the pixel script is loading on your front end. - Copy the pixel URL exactly from the Search Atlas platform. A single character difference will prevent the allowlist rule from matching. 💬 Still Seeing 'OTTO Not Found'? If you have followed all the steps above and the error persists, your hosting provider or a secondary security plugin (such as Sucuri, iThemes Security, or Cloudflare WAF) may also be blocking the pixel. If you need further assistance, open 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 Disengaging on WordPress

🔍 Overview The OTTO Pixel is a small tracking script that connects your WordPress site to Search Atlas, enabling OTTO SEO to read your site's data and apply optimisations. If the Pixel keeps showing as Disabled in Search Atlas — even after you've re-engaged it — a conflict or configuration issue on your WordPress site is likely breaking the connection. This article walks you through the most common causes and how to fix them. ⚙️ How to Check the Pixel Status 1. In Search Atlas, click OTTO SEO in the left sidebar, then open SEO Automation (or go to /seo-automation-v3). 2. Locate your connected site and check the OTTO Pixel status indicator. 3. If it shows Disabled or Disengaged, continue with the steps below before re-engaging. ⚠️ Common Causes of Pixel Disengagement - Caching plugins overwriting the page — Plugins such as WP Rocket, W3 Total Cache, or LiteSpeed Cache can serve a cached version of your pages that does not include the Pixel script, causing Search Atlas to lose the connection. - Minification or script optimisation — JavaScript minification or deferred script loading can corrupt or delay the Pixel, preventing it from firing correctly. - Security or firewall plugins blocking the script — Plugins like Wordfence or iThemes Security may flag the Pixel as an unknown external script and block it. - CDN stripping scripts — A CDN such as Cloudflare may strip or defer third-party scripts, including the OTTO Pixel. - Theme or plugin conflicts — A recently updated theme or plugin may be interfering with script injection. - Multiple WordPress installs or staging environments — If the same Pixel ID is used across a live site and a staging site, the connection can become unstable. 🛠️ Step-by-Step Fixes 1. Clear all caches. Go to your caching plugin's settings and purge the entire site cache. If you use a CDN, purge the CDN cache as well. Then re-check the Pixel status in Search Atlas. 2. Exclude the OTTO Pixel script from minification and deferral. In your caching or performance plugin, find the JavaScript optimisation settings and add the OTTO Pixel script URL or handle to the exclusion list. Save and clear the cache again. 3. Whitelist the Pixel in your security plugin. Check Wordfence, iThemes Security, or any equivalent plugin for blocked scripts. Add the OTTO Pixel domain to the allowlist and ensure it is not being flagged as malicious. 4. Disable Rocket Loader in Cloudflare (if applicable). Log in to Cloudflare, go to Speed → Optimization, and turn off Rocket Loader. This prevents Cloudflare from deferring the Pixel script. You can also use a Page Rule to disable performance features for your site's key pages. 5. Test with plugins deactivated. Temporarily deactivate all plugins except the Search Atlas WordPress plugin, then re-engage the Pixel in Search Atlas. If it stays connected, reactivate plugins one by one to identify the conflicting plugin. 6. Verify the plugin is installed correctly. In your WordPress dashboard, go to Plugins → Installed Plugins and confirm the Search Atlas plugin is active and up to date. Deactivate it, then reactivate it, and re-engage the Pixel in Search Atlas. 7. Check for duplicate Pixel IDs. If you have a staging site, make sure it is using a separate connection or that the Pixel is disabled on staging. Two environments sharing the same Pixel ID can cause repeated disengagement. ✅ How to Re-Engage the Pixel After Fixing the Issue 1. In Search Atlas, click OTTO SEO in the left sidebar, then open SEO Automation. 2. Select your site and click the option to re-engage or enable the OTTO Pixel. 3. Reload your WordPress site's homepage in a new browser tab (not from cache) to trigger the Pixel. 4. Return to Search Atlas and refresh the page to confirm the Pixel status shows as Active. 💡 Tips to Keep the Pixel Stable - After any WordPress update, plugin update, or cache configuration change, verify the Pixel status in Search Atlas. - Set your caching plugin to exclude the OTTO Pixel script permanently from optimisation rules. - Avoid using the same Pixel ID on both your live site and any staging or development environment. 🆘 Still Disengaging After All Steps? If you have followed every step above and the OTTO Pixel continues to disengage, our support team can investigate further. If you need further assistance, open 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 Plugin WordPress Checkout Conflicts

🔍 Overview When you activate the Search Atlas Otto pixel plugin on your WordPress site, you may notice that your checkout page or other page elements stop displaying correctly. This is a known compatibility issue caused by a conflict between the Otto pixel script and your WordPress theme or checkout plugin. This article explains why this happens and walks you through the steps to resolve it. ⚙️ Why This Happens The Otto pixel plugin injects a tracking script into your WordPress site to enable OTTO SEO automation and data collection. In some cases, this script can conflict with: - WooCommerce or other checkout plugins that load their own scripts on the checkout page - Page builder themes (such as Divi, Elementor, or Avada) that manage script loading in a custom way - Caching or performance plugins (such as WP Rocket or W3 Total Cache) that minify or defer JavaScript in a way that interferes with the pixel script - Security plugins that block or modify third-party scripts The result is often broken page layouts, missing checkout fields, or JavaScript errors that prevent customers from completing a purchase. 🛠️ How to Resolve the Conflict Follow these steps in order to identify and fix the issue: 1. Deactivate caching and minification temporarily. Go to your caching plugin settings and disable JavaScript minification and deferral. Then reload your checkout page to see if the issue is resolved. If it is, re-enable caching options one at a time to find the specific setting causing the conflict. 2. Exclude the Otto pixel script from optimisation. In your caching or performance plugin, add the Otto pixel script URL to the exclusion list so it is never minified, combined, or deferred. 3. Check your security plugin settings. If you use a security plugin such as Wordfence or iThemes Security, ensure it is not blocking external scripts. Add the Otto pixel domain to any allowlist or whitelist. 4. Test for theme conflicts. Temporarily switch to a default WordPress theme (such as Twenty Twenty-Four) and reload the checkout page. If the page displays correctly, the conflict is with your active theme. Contact your theme developer for guidance on loading third-party scripts safely. 5. Check for JavaScript errors. Open your browser's developer tools (press F12), go to the Console tab, and reload the checkout page. Note any error messages. These can help pinpoint which script or plugin is causing the conflict. 6. Update all plugins and your theme. Outdated plugins are a common cause of script conflicts. Ensure the Otto pixel plugin, your checkout plugin, and your theme are all running their latest versions. ✅ Verifying the Fix After completing the steps above, confirm everything is working correctly: - Visit your checkout page in a private or incognito browser window to bypass any cached version - Complete a test transaction from start to finish to confirm the checkout flow is fully functional - Check that your OTTO SEO data is still being recorded by navigating to Left sidebar → OTTO SEO → SEO Automation inside Search Atlas 🚀 Preventing Future Conflicts To avoid similar issues in the future, keep these best practices in mind: - Always test plugin activations on a staging site before deploying to production - Keep a record of any script exclusions you have added to your caching or security plugins - After updating any plugin — including the Otto pixel plugin — re-test your checkout page to confirm it remains functional 💬 Still Need Help? If you have followed all the steps above and your checkout page is still not working correctly, 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 OTTO Pixel Not Detected on WordPress

🧭 Overview After installing the OTTO pixel on a WordPress site via the Search Atlas (MetaSync) WordPress plugin, the Search Atlas dashboard may still show the pixel status as Not Installed. Generic HTML debugging steps rarely solve this. The most common cause on WordPress is a missed plugin setting — specifically the Enable meta description toggle — which must be active for the pixel to be detected correctly. Follow the checklist below in order before contacting support. ✅ Step 1: Confirm the Search Atlas (MetaSync) Plugin Is Configured 1. In WordPress, install and activate the Search Atlas (MetaSync) plugin. 2. In the WordPress admin, go to Search Atlas → Settings. 3. Paste your Search Atlas API Key (or connect with One-Click Authentication) and paste your OTTO Pixel UUID. The plugin then handles the pixel automatically — you do not need to paste the JavaScript snippet on WordPress. (The code snippet is intended for non-WordPress platforms or alternative installs such as Google Tag Manager.) 4. To confirm the pixel is loading, open any page on your site, right-click, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for otto or the first few characters of your pixel ID. If you cannot find it, revisit the plugin settings before continuing. ⚙️ Step 2: Enable the 'Enable Meta Description' Setting (Most Common Fix) This is the single most frequently missed step on WordPress and the primary reason the OTTO pixel fails to register even when the code appears to be present. 1. In your WordPress admin panel, navigate to Settings and open the configuration page for your active SEO plugin (for example, Rank Math, Yoast SEO, All in One SEO, or The SEO Framework). 2. Locate the setting labelled Enable meta description (exact wording may vary slightly by plugin) and make sure it is turned on. 3. Save your changes. 4. Return to the Search Atlas dashboard under OTTO SEO and click Recheck Pixel Status or reload the page after one to two minutes. Why this matters: The OTTO pixel relies on meta description output to confirm correct page-level integration. If your SEO plugin suppresses meta descriptions globally, the pixel verification check cannot complete, and the dashboard will continue to report the pixel as not installed — regardless of whether the snippet code is physically present in the page source. 🔍 Step 3: Check for Plugin or Theme Conflicts 1. Temporarily switch to a default WordPress theme (such as Twenty Twenty-Four) and recheck pixel status in Search Atlas. 2. If that resolves the issue, re-activate your original theme and identify which theme feature or child-theme customisation is stripping the <head> output. 3. If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), purge all caches after any configuration change, then recheck. 4. If you use a CDN or a proxy service such as Cloudflare, ensure that HTML minification or script optimisation is not removing or deferring the pixel snippet. 🛡️ Step 4: Verify No Security Plugin Is Blocking Output - Security plugins such as Wordfence or iThemes Security can block or modify <head> content. Temporarily disable them one at a time and recheck pixel status after each. - If your site uses a Content Security Policy (CSP), confirm that the OTTO pixel domain is included in your allowlist. 🔄 Step 5: Force a Fresh Pixel Status Check 1. After completing any configuration change, clear your browser cache and open your website in a private or incognito window to ensure you are viewing the live, uncached version. 2. In Search Atlas, navigate to OTTO SEO and trigger a pixel recheck. Allow up to about 15 minutes for the status to update, since automatic pixel checks run every 15 minutes for projects under 2 hours old. 3. If status remains Not Installed after confirming every step above, proceed to the quick reference checklist below before contacting support. 📋 WordPress Pixel Installation Checklist - Search Atlas (MetaSync) plugin installed and configured with API Key and OTTO Pixel UUID at Search Atlas → Settings - Enable meta description toggled ON in your active SEO plugin — this is the most common blocker - All caches purged after every configuration change - CDN or Cloudflare HTML optimisation not stripping the snippet - Security plugins not blocking output - No Content Security Policy preventing the pixel domain - Pixel status rechecked in Search Atlas after each fix attempt 💬 Still Showing as Not Installed? If you have worked through every step above and the pixel status still shows Not Installed, our team can review your specific site 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.