Troubleshooting: Pixel Pending, UUID & Verification Errors

Fix OTTO Pixel Not Detected After Installation

🔧 Fix OTTO Pixel Verification on Lovable Sites

🛠️ Fix OTTO Crawl Failures and Pixel Detection Issues

🔍 Fixing Pixel Scan and Sitemap URL Issues

🔎 How the Deployment Scan Works When you activate OTTO, Search Atlas checks whether the OTTO pixel is installed on your site. The scan loads and renders your pages the same way a real browser does, then looks for the pixel in that rendered output. A deployment is marked as live only when the pixel is confirmed during the scan. Scans run in the background on a schedule, so a recently started scan may be queued, deferred, or still in progress before any verdict appears. 🤔 Why a Visible Pixel May Not Be Detected It is common for a developer to see the OTTO pixel in the live page source while the scan still shows no deployment. This does not always mean the pixel is missing. Common causes include: - The scan has not finished yet. Deployment scans are queued and can take time to complete. While a scan is pending or in progress, no deployment verdict appears, even if the pixel is already live on your site. - The pixel is deployed through Google Tag Manager (GTM) or another tag manager. Tag managers inject scripts after the initial page load. Because the scan evaluates the rendered page, a tag-manager deployment may not be recognized reliably. We recommend installing the OTTO pixel directly in the head section of your site instead. - Delayed script loading. If the pixel loads late in the page lifecycle, it may fall outside the scan window and go undetected. - Scan cooldowns. After a scan completes, there is a waiting period before a new scan can run, so recent changes to your site may not be reflected immediately. 🛠️ Steps to Resolve a Detection Issue 1. Confirm the OTTO pixel snippet is placed directly in the head section of your site, not only inside GTM or another tag manager. 2. Publish your changes and clear any server, plugin, or CDN caches so the scan sees the latest version of your pages. 3. Allow time for the next scheduled scan to run and complete. If a scan appears stuck in progress for more than 24 hours, contact us so we can investigate your project. 4. Check your URL scheme. Make sure your site, sitemap, and Search Atlas project all use the same protocol (https). A mismatch between http and https can produce false results in audit and sitemap checks. 🗺️ Where GSC Sitemap URLs Come From When you connect Google Search Console, Search Atlas imports the URLs listed in your sitemap. These URLs power site audit and sitemap coverage checks. Because they are synced from Google Search Console, they cannot be edited or deleted directly inside Search Atlas. They always reflect whatever your sitemap contains at the time of the sync. ✏️ How to Edit or Remove a Sitemap URL 1. Update the sitemap at the source, meaning in your CMS or wherever the sitemap file is generated, to add, change, or remove the URL slug. 2. If you changed a slug permanently, set up a redirect from the old URL to the new one so you do not lose traffic or backlinks. 3. Submit the updated sitemap in Google Search Console so Google registers the change. 4. Return to Search Atlas and re-sync your Google Search Console connection, or wait for the next automatic sync, so your URL list reflects the updated sitemap. After the sync completes, the outdated slug will stop appearing in your sitemap-based checks. If a page is still flagged as Not in XML Sitemap, verify that the sitemap entry and the live page use the exact same protocol and domain spelling, for example https with and without www are treated as different addresses. 💡 Tips to Avoid Future Discrepancies - Install the OTTO pixel directly in your site template rather than through a tag manager. - Keep your sitemap current whenever you publish, rename, or remove pages. - Use one consistent URL format (https, with or without www) across your site, sitemap, and Search Atlas project. - Allow one full scan cycle to pass before troubleshooting a fresh installation. 💬 Still Need Help? If the scan continues to report no deployment after you have confirmed direct pixel installation and a full scan cycle, or if a Google Search Console URL will not update after a re-sync, our team can look into your project 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 Missing Settings Menu and OTTO Pixel Install

🔍 Overview Some customers report that the Settings menu is missing from their sidebar, they cannot locate the OTTO Pixel code, or the MetaSync WordPress plugin is unavailable in the WordPress plugin repository. This article walks you through each issue and how to resolve it. ⚙️ Why the Settings Menu May Be Missing The Settings menu is not a standalone sidebar item. It is accessed through your account avatar in the top-right corner of the platform — not through the left sidebar. 1. Click your avatar or profile icon in the top-right corner of the platform. 2. Select Team Members from the dropdown to access account and workspace settings. If you do not see your avatar or the dropdown options, your user role may have restricted permissions. Contact your workspace administrator to confirm your access level. 📍 Where to Find the OTTO Pixel Code The OTTO Pixel installation code is located inside the OTTO SEO section, not in a general Settings menu. Follow these steps to find it: 1. In the left sidebar, click OTTO SEO. 2. Click Site Audit. 3. Click Installation Guide. The Installation Guide page contains your unique OTTO Pixel code snippet and step-by-step instructions for adding it to your website. Make sure you are copying the pixel code associated with the correct site if you manage multiple properties. ⚠️ Common OTTO Pixel Installation Issues Even after installing the pixel, OTTO may still report it as not installed. Below are the most common causes and fixes: - Wrong UUID in the pixel code: Each site has a unique pixel identifier. If you copied the code from another site or an older setup, the UUID may not match. Return to OTTO SEO → Site Audit → Installation Guide and copy a fresh code snippet for the correct site. - Duplicate pixel installed: Having the OTTO pixel installed more than once on the same page can cause detection errors. Check your theme files, tag manager, and any installed plugins to ensure only one instance exists. - Legacy SearchAtlas pixel still active: If you previously used the SearchAtlas pixel (especially under a white-label setup), the old pixel may conflict with the new OTTO pixel. Remove the legacy pixel before installing the current one. - Pixel installed in Website Studio but not on the live site: Changes made inside Website Studio must be published before they appear on your live site. After adding the pixel code in Website Studio, make sure you publish your site to push the update live. - Pixel not firing on all pages: The pixel should be placed in the <head> section of your site's global template so it loads on every page. If it is only added to one page, OTTO may not detect it reliably. 🔌 Installing the OTTO Pixel on WordPress The recommended method for WordPress sites is to use a plugin that lets you inject code into the <head> of your site. If the MetaSync plugin is not available in the WordPress plugin repository, use one of these widely available alternatives: - Insert Headers and Footers by WPCode — search for it directly in your WordPress dashboard under Plugins → Add New. - WPCode Lite — another reliable option for injecting scripts site-wide. Once the plugin is installed and activated, paste your OTTO Pixel code into the header section and save. The pixel should begin reporting within a few hours after your next site crawl. 🛒 Installing the OTTO Pixel on Shopify, GTM, and Other Platforms If your site runs on a platform other than WordPress, you can still install the OTTO Pixel manually: - Shopify: Go to Online Store → Themes → Edit Code and paste the pixel code inside the theme.liquid file, just before the closing </head> tag. - Google Tag Manager (GTM): Create a new Custom HTML tag, paste the pixel code, and set the trigger to All Pages. Publish your GTM container after saving. - Other platforms: Paste the pixel code into any global header template or theme file that loads on every page of your site. ✅ How to Verify the Pixel Is Detected After installation, return to OTTO SEO → Site Audit → Installation Guide in the platform. The page will indicate whether the pixel has been successfully detected on your site. Allow up to 24 hours for the status to update after a fresh install. If the status remains not installed after 24 hours, double-check that the pixel code is present in your live site's page source by right-clicking any page and selecting View Page Source, then searching for your pixel snippet. 💬 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 Wrong UUID on Website Studio

🧩 Why This Error Happens Each project you create in Website Studio generates its own unique OTTO pixel script. This script contains a UUID (Unique User Identifier) that is specific to that project alone. If you copy the pixel script from one Website Studio project and paste it into a different project, OTTO will detect a UUID mismatch and the scan will fail. This is the most common cause of the wrong UUID error: the pixel installed on your site belongs to a different Website Studio project, not the one you are currently trying to activate. ✅ How to Get the Correct Pixel Script Follow these steps carefully for each Website Studio project you want to connect to OTTO. 1. In the left sidebar, click OTTO SEO. 2. Click All Sites to see your list of sites. 3. Locate the site that corresponds to the Website Studio project you are working on and open it. 4. In the left sidebar under OTTO SEO, click Installation Guide. 5. Copy the pixel script shown on that page. This script contains the UUID that is uniquely tied to this specific project. 6. Go to your Website Studio project in the left sidebar under Website Studio and open the correct project. 7. Paste the pixel script into the header or footer code injection area of that project — do not use a script copied from any other project. 8. Save your changes and publish the site. 9. Return to OTTO SEO → Overview and click Scan to verify the pixel is detected correctly. ⚠️ Key Rules to Avoid UUID Errors - Never share pixel scripts between projects. Each Website Studio project must use only its own unique pixel script. - Always retrieve the script from the Installation Guide of the specific OTTO site that matches your Website Studio project. - If you have multiple Website Studio projects, repeat the steps above individually for each one — do not duplicate or reuse scripts. - After republishing a project, always run a fresh Scan from OTTO SEO → Overview to confirm the pixel is recognised. 🔍 How to Check Which UUID Is Currently Installed If you are unsure whether the correct script is installed, you can verify it quickly: 1. Open the live URL of your Website Studio project in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) to search for uuid. 4. Copy the UUID value you find and compare it to the UUID visible in OTTO SEO → Installation Guide for that project. 5. If the values do not match, remove the existing script and replace it with the correct one from the Installation Guide. 🗂️ Managing Multiple Website Studio Projects If you manage several Website Studio projects under the same account, use this checklist to stay organised: - Label each project clearly inside Website Studio so you can easily match it to the correct OTTO site. - Before installing any pixel, navigate to the OTTO site for that specific project and retrieve its Installation Guide script fresh — never copy from a previously saved file or another project. - After installing on each project, run a Scan individually per site to confirm successful detection before moving to the next. 💬 Still Seeing the Wrong UUID Error? If you have followed all the steps above and the wrong UUID error persists, it is possible the page cache is serving an older version of the site. Try clearing your Website Studio project's cache and republishing, then run the scan 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.

⚠️ OTTO Duplicate Installation Warning: Wrong Project UUID

The "Duplicate Installation Detected" warning in OTTO SEO means the same UUID tracking script is active on more than one website. This happens when the wrong site's OTTO script is pasted into another site's header — replacing it with the correct script clears the warning once the correct script is saved, published, and any site cache is cleared. It may take a few minutes for OTTO to re-scan the domain. ⚠️ What Causes the Duplicate Installation Detected Warning Every website you manage in OTTO SEO has a unique UUID (universally unique identifier) embedded in its tracking script. OTTO monitors which UUID reports from which domain. If Site A's script is installed on Site B, OTTO sees the same UUID coming from two different domains and triggers the duplicate warning. Common scenarios that cause this: - You manage multiple websites and accidentally copy the wrong site's script during setup. - A script from one OTTO project is pasted into the header of a different project's site. - You previously had an OTTO project for this domain, deleted or replaced it, and the old script with the previous UUID was never removed from the site. Check for and remove any legacy OTTO script tags before installing the new one. Note: In some cases, OTTO may incorrectly show as installed across multiple projects even when no UUID actually matches. If comparing UUIDs does not resolve the warning, contact Search Atlas support so an agent can verify the correct UUID for your account. Website Studio users: If your site is built with Search Atlas Website Studio, you may see a false duplicate warning due to a known platform issue, even if the pixel was only added once. Do not assume you pasted the wrong script — open a support ticket so the team can investigate. 🔍 How to Identify Which Site Has the Wrong UUID Compare the UUID embedded in each installed script against the UUID shown in your OTTO SEO dashboard for that domain. 1. In Search Atlas, go to OTTO SEO and open the project for each affected website. 2. Locate the UUID for each project — it appears in the installation script as either the HTML attribute data-uuid="your-uuid-here" on the script tag, or as the JavaScript property script.dataset.uuid = "your-uuid-here". Both forms reference the same value; which one you see depends on the installation method used. 3. In your website's CMS or theme editor, find the installed OTTO script inside the header (<head>) section. 4. Compare the UUID in the installed script to the UUID shown in your OTTO project for that domain. A mismatch confirms which site has the wrong script installed. 🛠️ How to Replace the OTTO Script with the Correct UUID Once you've identified the site with the wrong script, remove it and install the correct one for that domain. 1. In Search Atlas, go to OTTO SEO → your correct project → Installation and copy the correct UUID/script shown there. 2. In your website's CMS or theme editor, open the header section. 3. Find and delete the incorrectly installed OTTO script entirely. 4. Paste the correct script into the header of the matching website. 5. Save and publish your changes, and clear any site or CDN cache. 6. Return to the OTTO SEO dashboard and confirm the "Duplicate Installation Detected" warning has cleared. It may take a few minutes for OTTO to re-scan the domain. After saving, return to OTTO SEO. The "Duplicate Installation Detected" warning clears automatically once OTTO confirms the correct UUID is reporting from the correct domain. 🏗️ Website Studio Users: Known Limitation If your site is hosted on Search Atlas Website Studio, manually installing the OTTO pixel inside Website Studio may not result in a functional OTTO connection. OTTO deployments can fail because there is no CMS connector or Cloudflare Worker configured for Website Studio sites. If you are using Website Studio, open a support ticket referencing this known limitation rather than continuing to troubleshoot the script manually. 🔌 Alternative: Install OTTO via the Search Atlas WordPress Plugin If your site runs on WordPress, the Search Atlas WordPress Plugin installs the correct OTTO script automatically, eliminating the risk of copying the wrong UUID. 1. Install and activate the Search Atlas plugin by uploading the plugin .zip provided by Search Atlas in WordPress → Plugins → Add New → Upload Plugin. 2. Connect the plugin to your Search Atlas account. 3. Select the correct OTTO project for the site — the plugin manages the UUID and script automatically. This method is recommended for WordPress sites to prevent future UUID mismatches. UUID vs. API Key: When using the WordPress plugin, do not confuse the OTTO UUID (the data-uuid attribute in the installation script, tied to a specific OTTO project) with your Search Atlas API Key (found under Account Menu → Settings → API Keys, used to authenticate the plugin to your account). Entering one in place of the other will produce a connection failure that can look like a UUID mismatch. 🌐 Whitelabel Domain Note If your account has a whitelabel domain configured, OTTO scripts route through that domain. An unreachable whitelabel domain (for example, one not pointed to Search Atlas IPs) will cause OTTO connection failures that are unrelated to UUID mismatches but can appear alongside or be confused with duplicate/mismatch warnings. If you suspect this is the case, contact Search Atlas support. 🎯 You now know how to identify and fix the UUID mismatch that triggers OTTO's duplicate installation warning. For a visual walkthrough of the exact fix, watch the screen recording. If the warning persists after replacing the script, contact Search Atlas support so an agent can verify the correct UUID for your account.

🔍 OTTO Pixel Setup: Crawl Time and Error Messages

🧭 Overview When you first install the OTTO Pixel on your website, Search Atlas needs to crawl your site before it can fully verify the installation. During this crawl period, you may see a message saying the pixel is not installed correctly — even if your installation was done perfectly. This article explains what that message means, how long the crawl takes, and what to expect throughout the onboarding process. ⏱️ How Long Does the Initial Crawl Take? The initial site crawl can take up to 24 hours to complete. The exact duration depends on the size of your website, the number of pages, and current crawl queue volume. You do not need to keep the platform open while the crawl runs. Search Atlas processes the crawl in the background, and your status will update automatically once verification is complete. ⚠️ Why Does 'Not Installed Correctly' Appear? Seeing a not installed correctly message immediately after setup does not mean your installation failed. It means the crawl has not yet confirmed the pixel's presence across your site. Think of this message as a pending verification notice, not a failure alert. The system is gathering data and will update the status automatically once the pixel is confirmed — you do not need to reinstall or make any changes while the crawl is still in progress. ✅ What Does a Successful Installation Look Like? A successful OTTO Pixel installation has two phases: - In-progress state: The pixel code is on your site, the crawl is running, and the status may read not installed correctly. This is normal and expected. - Verified state: The crawl has confirmed the pixel across your site, and the status updates to show the pixel is Installed. You will also begin to see OTTO recommendations and automation activity populate in the dashboard. 🛠️ What Should You Do While You Wait? If you have just installed the OTTO Pixel, here is what to do: 1. Confirm the pixel code is present on your site (check your theme, tag manager, or CMS integration, whichever method you used to install it). 2. Wait up to 24 hours for the crawl to complete before assuming there is a problem. 3. Check back in your Search Atlas dashboard to see if the status has updated. 4. If the status still shows not installed correctly after 24 hours, contact support so the team can investigate the crawl 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.

🔍 OTTO Pixel NOT DETECTED Status Explained

🧭 Overview After installing the OTTO pixel on your website, the dashboard may display a NOT DETECTED status. In most cases, this is completely normal and does not mean your installation failed. This article explains why that status appears, how long to expect it, and what to check if the issue persists after the expected window. ✅ When NOT DETECTED Is Expected The NOT DETECTED status appears immediately after pixel installation because Search Atlas checks for the pixel on a schedule rather than instantly. For a brand-new project (under 2 hours old), automatic checks run every 15 minutes, so a correctly installed pixel is normally detected within about 15 minutes. From 2 to 24 hours old, checks run every hour; from 1 to 7 days old, every 6 hours; after 7 days the automatic checks stop. This is expected behaviour in the following situations: - You have just installed the pixel for the first time. - Your site audit has never completed a full crawl. - You recently re-installed or updated the pixel script. Do not re-install the pixel or make additional changes during this period, as doing so may reset the crawl process. ⏱️ First Crawl Timeline The initial site audit crawl can take some time to complete, depending on the size of your website and current system load. Larger sites with hundreds or thousands of pages will naturally take longer than smaller sites. During this window: - The NOT DETECTED status will remain visible on your dashboard. - No action is required on your part. Once the crawl completes, return to the pixel status area in the OTTO dashboard. The status should update from Not Installed to Installed automatically. If it does not update after the crawl has finished, proceed to the troubleshooting steps below. 📊 How to Monitor Progress in the Dashboard You can track your site audit crawl status directly inside the OTTO dashboard. Navigate to your connected website within the platform and open the OTTO dashboard, then look for the Site Audit section to check whether a crawl is in progress or has completed. If the crawl shows no progress after an extended period, proceed to the troubleshooting steps below. 🛠️ Troubleshooting a Genuinely Failed Installation If the crawl has completed and the status still shows NOT DETECTED, use the following checklist to identify the root cause: - Verify script placement: Confirm that the OTTO pixel script has been placed correctly in your website's page template so it loads on every page. In Shopify, this typically means adding the script inside the theme.liquid file. - Check for duplicate or conflicting scripts: Having multiple copies of the pixel script can cause detection failures. Review your theme files to ensure only one instance of the pixel script is present. - Confirm the script is published on your live si If you need further assistance, open 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 AI Visibility Projects and Install the OTTO Pixel

🧭 Overview If your AI Visibility projects have disappeared from your dashboard, or if you are unable to install the OTTO pixel through Cloudflare, this article explains what happened and walks you through your available options to get back on track. ❓ Why Are My AI Visibility Projects Missing? AI Visibility projects are tied to verified OTTO pixel connections. If the pixel on your site becomes unreachable or has not been confirmed as active recently, the platform may remove or deactivate associated projects to maintain data accuracy. Common reasons this happens include: - The OTTO pixel was removed from your website or became unreachable after a site update - A plugin conflict or caching layer is blocking the pixel from being detected - The pixel was never fully verified after the initial installation attempt - Your site's DNS or proxy settings changed, causing the pixel connection to drop Once your pixel is reinstalled and OTTO is detected again, the same project is reactivated automatically with its history preserved — a new project is not created. 🛠️ How to Reinstall the OTTO Pixel Without Cloudflare Cloudflare is one installation method, but it is not the only option. If you do not have Cloudflare access, use one of the alternatives below. ⚙️ Option 1 — Install via WordPress Plugin If your site runs on WordPress, this is the recommended alternative to Cloudflare. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3). 2. Open your OTTO project and locate the pixel installation section. 3. Select the WordPress Plugin installation method. 4. Install the Search Atlas (MetaSync) WordPress plugin on your site. 5. In WordPress, go to Search Atlas → Settings and paste your Search Atlas API key. 6. Paste your OTTO Pixel UUID and save. The plugin will handle the pixel installation. 7. Return to the platform to confirm the pixel status turns green. Note: If the plugin installation shows as partial or the pixel status does not update, the platform's diagnostic tool will surface the specific step that needs attention. Follow the on-screen guidance to resolve it. 💡 Option 2 — Install via AI-Assisted Prompt If you have access to an AI coding assistant or developer agent (such as ChatGPT, Cursor, or a similar tool), you can use the platform's built-in AI-assisted install path. 1. In your OTTO project's pixel installation section, click Copy AI Prompt or Open AI Agent. 2. Paste the copied prompt into your preferred AI coding tool. 3. Follow the instructions the AI provides to add the pixel to your site's code. 4. Return to the platform and check that your pixel status is verified. This method is ideal if you manage your site's code directly or work with a developer. 🖥️ Option 3 — Manual Code Installation You can add the OTTO pixel manually to your site's HTML if you have access to your theme files or a tag manager. 1. Copy your unique pixel snippet from the OTTO project settings. 2. Paste it into the section of every page on your site, or use Google Tag Manager to deploy it site-wide. 3. Publish the changes and allow a few minutes for the platform to detect the pixel. 4. Refresh your OTTO project page and confirm the connection status shows as verified. ✅ How to Check Your Pixel Status After any installation method, always confirm the pixel is active before rebuilding your AI Visibility projects. - Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. - Open your OTTO project and review the pixel status indicator. - A green verified status means the pixel is connected and active. - If the status is pending or shows an error, use the on-screen diagnostic guidance to identify what is blocking verification. 🚀 Reactivating Your AI Visibility Projects Once your pixel is verified and OTTO is detected again, your existing AI Visibility project is reactivated automatically with its history preserved. 1. Go to AI Visibility in the left sidebar (or navigate to /llm-visibility). 2. Confirm your project is active again and review its preserved history. 3. Make sure the domain matches the site where your pixel is installed. 4. Allow time for data to resume populating. Tip: AI Visibility relies on Site Explorer data for onboarding. If your domain has not been crawled yet, initial data may take some time to appear after your project is created. 💬 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 Logo Corruption After Search Atlas Pixel Install

About This Issue Some users have reported logo corruption or unexpected visual changes on their Shopify store after installing the Search Atlas tracking pixel. Our team is aware of this reported issue and is investigating the root cause. Because the exact cause can vary depending on your theme, pixel placement, and site configuration, our support team will need to review your specific setup directly in order to identify what is happening and guide you to the right fix. What to Have Ready Before Contacting Support To help our team investigate as quickly as possible, please gather the following before reaching out: - The name of your Shopify theme (e.g., Dawn, Debut, a custom theme) - The URL of the page where the logo corruption is visible - A screenshot or screen recording showing the visual issue - The date and time you first noticed the problem - Confirmation of where the pixel snippet is currently placed in your theme code (e.g., theme.liquid, a specific section file) - Any recent changes made to your theme around the time the issue started If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Not Detected Advanced Troubleshooting

🧭 Overview After activating the OTTO WordPress plugin with your API key and UUID, Search Atlas Site Auditor must be able to crawl your site and confirm the pixel is present. If the auditor cannot reach your site — due to Cloudflare, a CDN, a firewall, or bot-blocking rules — it will report the pixel as undetected even when the plugin is installed and working correctly. Always check for server-side blocking first before revisiting plugin settings or caches. 🚧 Step 1 — Check for Cloudflare or CDN Bot Blocking This is the most common and most overlooked cause of pixel detection failures. Cloudflare and similar CDNs can silently block the Search Atlas crawler before it ever reads your page source. 1. Log in to your Cloudflare dashboard (or your CDN provider's dashboard). 2. Go to Security → Events and filter by the last 24 hours. Look for blocked or challenged requests from Search Atlas crawlers. 3. Go to Security → Bots and confirm that Bot Fight Mode or Super Bot Fight Mode is not set to block all automated traffic. 4. Go to Security → WAF → Firewall Rules and check whether any rule blocks unknown bots, specific user agents, or high-frequency crawlers. 5. If you find a blocking rule, create a WAF exception (allow rule) for the Search Atlas crawler, or temporarily set the security level to Essentially Off to test whether detection succeeds. 6. After making changes, return to the Search Atlas platform and re-run the Site Audit to trigger a fresh detection check. 🔥 Step 2 — Check Server-Level Firewalls and Security Plugins Even without Cloudflare, a server firewall or a WordPress security plugin can block the crawler at the hosting level. 1. If you use a security plugin such as Wordfence, Sucuri, iThemes Security, or All-In-One Security, open its settings and review the blocked IP log or lockout log. 2. Check whether your hosting provider's built-in firewall (common with WP Engine, Kinsta, SiteGround, and Cloudways) has flagged or rate-limited crawl traffic. 3. Temporarily whitelist the Search Atlas crawler user agent (SearchAtlasBot) or disable aggressive bot-blocking rules for testing, then re-trigger the Site Audit. 4. If your firewall requires specific IP ranges to be whitelisted, escalate to our support team with your site URL and firewall type so the current crawler IP list can be provided. 🤖 Step 3 — Verify robots.txt Is Not Blocking the Crawler A Disallow rule in your robots.txt file can prevent the Site Auditor from accessing the pages where the pixel should be detected. 1. Open a browser and navigate to https://yourdomain.com/robots.txt to view your current rules. 2. Check for any Disallow: / rules or rules targeting all user agents (User-agent: *) that would block automated crawlers from accessing your site. 3. If you find a blocking rule, either remove it or add a specific Allow entry for the Search Atlas crawler user agent (SearchAtlasBot). 4. Save your updated robots.txt, then return to the Search Atlas platform and re-run the Site Audit. 🗄️ Step 4 — Clear Site and CDN Cache After confirming no blocking rules are active, a stale cache may still serve an old version of your page that does not include the OTTO pixel script. 1. In your WordPress admin, navigate to your caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) and click Clear All Cache. 2. If you are using Cloudflare, log in to your dashboard, go to Caching → Configuration, and click Purge Everything. 3. Ask your hosting provider to flush any server-side object or page cache if the above steps do not resolve the issue. 4. Once all caches are cleared, re-run the Site Audit in Search Atlas to trigger a fresh crawl and detection check. 🔌 Step 5 — Confirm the OTTO Plugin Is Active and the Pixel Is Rendering If blocking and cache issues have been ruled out, verify the plugin itself is correctly outputting the pixel on your live pages. 1. Log in to your WordPress admin and go to Plugins → Installed Plugins. Confirm the Search Atlas plugin is Active (menu: Search Atlas → Settings). 2. In the OTTO plugin settings, confirm your API key and UUID are saved correctly and match what is shown in your Search Atlas account. 3. Open your homepage in a browser, right-click anywhere on the page, and select View Page Source. Search for otto or your UUID in the source code to confirm the pixel script is being output. 4. If the pixel script is not visible in the page source, deactivate and reactivate the OTTO plugin, then check the page source again. 5. After confirming the pixel is present in the source, return to Search Atlas and re-run the Site Audit. If you need further assistance, open 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 Mismatch After URL Change

Why This Happens When your website's URL changes — even a minor update such as switching from http to https, adding or removing www, or migrating to a new domain — your WordPress plugin may cache the old OTTO Pixel UUID against the previous URL. Search Atlas ties each UUID to a specific site URL for security and tracking accuracy. After a URL change, the cached UUID in the plugin may no longer match the active UUID in your Search Atlas project, even though the alphanumeric strings appear identical on screen. Until the plugin is re-synced, synchronization can silently fail. Signs You May Be Affected - The OTTO Pixel UUID displayed in your WordPress plugin looks the same as the one shown in Search Atlas, but the plugin reports a sync error or shows as disconnected. - OTTO SEO automation tasks are not executing on your site despite appearing active in the platform. - The plugin connection status shows a warning shortly after a domain migration, SSL change, or URL restructure. What to Have Ready Before Escalating Because the exact re-sync steps depend on your specific WordPress and hosting configuration, our support team will need to guide you through the process directly. To help us resolve this as quickly as possible, please have the following information ready when you contact us: - The project name in Search Atlas where OTTO is connected. - The old URL and the new URL of your website (e.g., http://example.com changed to https://www.example.com). - The type of URL change that occurred (HTTP to HTTPS, added/removed www, full domain migration, etc.). - The exact error message or status shown in your WordPress plugin settings. - The date or approximate timeframe when the URL change took place. - Whether you have already attempted to deactivate and reactivate the Search Atlas 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 Stuck in Pending Status

🧭 Overview When your OTTO Pixel shows a Pending status and the Search Atlas crawler reports the script as missing, the most common cause is mixing two different installation methods at the same time. You only need one installation method — using both simultaneously can cause verification conflicts that keep your pixel stuck in Pending. 📦 The Two Installation Methods Explained Search Atlas offers two ways to install the OTTO Pixel on your website. They are independent of each other, and you should choose only one based on your setup. - WordPress Plugin (Recommended for WordPress sites): Install the official Search Atlas WordPress plugin. Once activated and connected to your account, the plugin automatically embeds the OTTO Pixel script across your site. No manual code placement is required. - Custom Pixel (Manual script installation): Copy the OTTO Pixel script from your Search Atlas dashboard and paste it directly into your website's <head> section. This method works on any platform — WordPress, Shopify, custom HTML sites, or any CMS. Both methods place the same pixel script on your site. Installing both can create duplicate or conflicting signals that prevent the crawler from verifying the pixel correctly. ✅ How to Resolve Pending Status If your pixel is stuck in Pending, follow these steps to correct the conflict. 1. Identify which installation method you actually set up: - If you installed the Search Atlas WordPress plugin — that is your installation method. Check whether you also manually pasted a pixel script into your theme, header, or tag manager, and remove the duplicate. - If you are not using the WordPress plugin — make sure the pixel script is pasted correctly into the <head> section of your site and that only one copy of the script exists. 2. Ensure only one method is active at a time. Remove any redundant installation so a single, clean copy of the pixel script is present on your site. 3. Trigger a re-verification from your OTTO Pixel settings in the Search Atlas dashboard after removing the duplicate 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.

🔧 Fix OTTO Pixel UUID Mismatch on Lovable

🧭 Overview If you have followed the OTTO pixel installation guide, entered your UUID, and cleared your cache but the pixel still does not appear active, a duplicate or conflicting UUID in your Lovable project files may be the cause. This article explains what to check and what information to have ready if you need to escalate to our support team. 🔍 What Causes a UUID Mismatch? A UUID mismatch typically occurs when the OTTO pixel script has been inserted into your Lovable project more than once — for example, in multiple template or layout files — and the UUID values in those entries do not all match. Only one correctly formatted, consistent UUID should be present across all instances of the pixel script in your project. 🛠️ What You Can Try 1. Confirm the exact UUID you should be using by locating it in your OTTO setup within Search Atlas. Make sure you copy it precisely — UUIDs are case-sensitive and contain no spaces. 2. Review the files in your Lovable project where the OTTO pixel script has been inserted. Check that every instance of the script uses the same UUID and that the script does not appear more than once in the same file or across overlapping layout files. 3. Remove any duplicate or mismatched script entries so only one correct instance of the pixel script remains. 4. Save your changes and reload your site to allow the pixel to re-register. If after reviewing your project files you are unsure which entry is incorrect, or if the pixel still does not activate after removing duplicates, our support team can investigate the specific UUID and project configuration on your behalf. 📋 What to Have Ready When Escalating To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Your project name in Lovable and the URL of the affected site - The UUID you believe is correct, copied directly from your OTTO setup in Search Atlas - A brief description of where the pixel script was inserted in your project (e.g., which files or components) - Any error messages or symptoms you are seeing (e.g., pixel not detected, activation status unchanged) If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Pixel Installation, Duplicates, and Visibility Discrepancies

🧭 Overview If a client confirms their pixel is installed and firing correctly on their website but it still does not appear inside Search Atlas, you are not alone. This is one of the most common questions our support team receives. This article explains why that gap exists, what duplicate pixel installations mean for your data, and how to resolve both issues quickly. ❓ Why Doesn't My Pixel Appear in Search Atlas? Search Atlas detects pixels by scanning the pages it crawls. There are several reasons a confirmed, working pixel may still not show up inside the platform: - Crawl timing: Search Atlas crawls pages on a scheduled basis. If the pixel was installed recently, the platform may not have re-crawled the page yet. Allow up to 24–48 hours after installation before expecting the pixel to appear. - Tag Manager delay: Pixels deployed through Google Tag Manager or a similar container may load asynchronously or only under specific trigger conditions (e.g., after a button click or form submission). If the trigger has not fired during a crawl, Search Atlas will not detect the pixel. - Consent management platforms: If a cookie consent banner or CMP blocks the pixel from loading until a user accepts cookies, the Search Atlas crawler — which does not interact with consent banners — will never see the pixel fire. - SPA or JavaScript-rendered pages: On single-page applications, pixels may load only after client-side JavaScript executes. Depending on the crawl configuration, the pixel could be invisible to the scanner even when it works perfectly for real users. - Incorrect placement: The pixel code may be placed in a location the crawler does not reach, such as deep inside a shadow DOM element or inside an iframe. ⚠️ Is Having Duplicate Pixel Installations Harmful? Yes, duplicate pixels can cause real problems. Having the same pixel fire more than once per page visit leads to the following issues: - Inflated event data: Conversions, page views, and custom events are counted multiple times, making your analytics and ad platform reporting unreliable. - Wasted ad spend: Ad platforms such as Meta and Google use pixel data to optimise bidding. Duplicate signals skew the data they rely on, which can result in higher costs and lower campaign performance. - Audience pollution: Remarketing audiences built from pixel data become inaccurate when the same user is counted multiple times per session. - Slower page load: Every duplicate pixel fires additional network requests, which can marginally slow page performance. A single, correctly configured pixel per platform is always the recommended setup. 🛠️ How to Diagnose and Fix the Issue 1. Verify the pixel is live on the page: Use a browser extension such as Meta Pixel Helper, Google Tag Assistant, or a general tag debugger to confirm the pixel fires on the specific URL you are checking inside Search Atlas. 2. Check for consent or trigger conditions: If a CMP is active, temporarily bypass it in a private browser session to confirm the pixel loads without the consent wall. If the pixel only fires after consent, note that Search Atlas will not detect it through passive crawling alone. 3. Search for duplicates: In the same browser extension or in your browser's Network tab (filter by the pixel domain), look for the pixel request firing more than once per page load. If it fires twice, check both your direct HTML and your tag manager container for duplicate entries and remove one. 4. Trigger a re-crawl in Search Atlas: After confirming the pixel is live and non-duplicate, navigate to the relevant section of the platform and initiate a re-crawl or refresh of the page data so Search Atlas picks up the latest state. 5. Confirm the correct URL is being checked: Make sure the URL you are viewing inside Search Atlas exactly matches the URL where the pixel is installed, including any trailing slashes or protocol differences (http vs https). ✅ Quick Reference: Pixel Not Showing vs. Duplicate Pixel - Pixel confirmed working but not in Search Atlas → Wait for re-crawl, check consent settings, verify trigger conditions, and ensure the pixel fires on the exact crawled URL. - Pixel appearing multiple times per page → Audit your tag manager container and direct HTML for duplicate entries; keep only one instance active per platform. 💬 Still Need Help? If you have followed the steps above and the pixel still does not appear in Search Atlas, or if you are unsure whether your setup contains duplicates, If you need further assistance, open 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 Installed Correctly Error

🔍 Why You're Seeing This Error The "OTTO Pixel is not installed correctly" message appears when Search Atlas cannot detect your OTTO Pixel firing on your website. This can happen even if you have the WordPress plugin installed and your GTM container published. The most common causes are a conflict between two installation methods, an unpublished GTM tag, or a firing trigger that hasn't been configured correctly. ⚙️ How the OTTO Pixel Can Be Installed There are two supported ways to install the OTTO Pixel. You should use only one method — running both at the same time will cause conflicts and trigger the error. - Method 1 — WordPress Plugin: The OTTO Pixel snippet is injected directly into your site via the Search Atlas WordPress plugin. - Method 2 — Google Tag Manager (GTM): You add the OTTO Pixel as a custom HTML tag inside GTM and publish the container. If you installed the WordPress plugin and also added the pixel code inside GTM, disable one of them before proceeding. 🛠️ Step-by-Step: Verify Your GTM Installation If you are using GTM as your installation method, follow these steps carefully. 1. Confirm the WordPress plugin is not also injecting the pixel. In your WordPress dashboard, go to the Search Atlas plugin settings and check whether the pixel output is enabled. If it is, disable it so GTM is the only active method. 2. Check your GTM tag is set up correctly. Log in to your GTM account, open the correct container for your website, and locate the OTTO Pixel tag. Make sure the pixel code is pasted in full inside a Custom HTML tag — not a different tag type. 3. Verify the trigger fires on all pages. Open the tag in GTM and check the trigger assigned to it. It should be set to All Pages (Page View trigger). If no trigger is assigned, the tag will never fire. 4. Publish the GTM container. Click Submit in the top-right corner of GTM and then Publish to push the latest version live. Saving a tag without publishing means the change is not yet active on your site. 5. Use GTM Preview mode to confirm the tag fires. Click Preview in GTM, enter your website URL, and navigate to any page. In the Tag Assistant panel, confirm the OTTO Pixel tag shows a status of Fired. If it shows Not Fired or does not appear at all, revisit the trigger configuration in step 3. 🛠️ Step-by-Step: Verify Your WordPress Plugin Installation If you are using the WordPress plugin as your installation method (without GTM), follow these steps. 1. Confirm the plugin is active. In your WordPress dashboard, go to Plugins → Installed Plugins and verify that the Search Atlas plugin status shows Active. 2. Check the pixel is configured inside plugin settings. In WordPress, go to Search Atlas → Settings and confirm the OTTO Pixel UUID field is populated and saved. 3. Remove any duplicate pixel code from GTM. If the OTTO Pixel tag also exists inside a GTM container, remove or pause it and re-publish the container so it is no longer firing. 4. Clear your site cache. If you use a caching plugin such as WP Rocket, W3 Total Cache, or a CDN like Cloudflare, purge all caches so the latest version of your pages is served to visitors and to Search Atlas during verification. ✅ Re-Run the Pixel Verification in Search Atlas Once you have completed the steps above, return to Search Atlas and re-trigger the pixel check. 1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Locate your OTTO project and open its settings. 3. Find the Pixel Installation section and click Verify Installation or the equivalent re-check button. 4. Wait a few seconds for the check to complete. If the pixel is detected correctly, the error message will be replaced with a green confirmation status. 💡 Quick Troubleshooting Checklist - Only one installation method is active — plugin or GTM, not both. - GTM container has been published (not just saved). - GTM tag trigger is set to All Pages. - GTM Preview mode confirms the tag Fired. - WordPress plugin is Active and pixel output is enabled in settings. - Site cache and CDN cache have been purged. - No ad blocker or browser extension is interfering during your own verification test. 💬 Still Seeing the Error? If you have followed all the steps above and the pixel is still not verifying, there may be a theme conflict, a custom caching layer, or an advanced GTM configuration causing the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Pixel 'engage not found' JavaScript Error

🔍 What Is This Error? When you publish articles through OTTO and see an 'engage not found' error in your browser console or publishing workflow, it means OTTO Pixel is not receiving the signal it expects. This typically relates to how OTTO Pixel is configured on your site — specifically whether you are using the JavaScript snippet method, the WordPress plugin method, or a combination of both. This article explains what this error means and what to have ready when contacting our team for a fix. ⚠️ Root Cause: OTTO Pixel Plugin Configuration OTTO Pixel can be deployed in two ways: - JavaScript method: A code snippet added manually to your site's <head> or via a tag manager. - WordPress plugin method: The OTTO Pixel plugin installed directly in your WordPress dashboard. The 'engage not found' error is associated with OTTO Pixel plugin configuration and JavaScript integration issues. Running both methods simultaneously, or leaving a transition between them incomplete, can prevent the engage function from initialising correctly so that publishing actions fail to register. Because the exact resolution depends on your specific site setup and configuration, our support team will need to review your account directly to identify and fix the issue. ✅ How to Get This Resolved To help our team resolve this as quickly as possible, please have the following ready before reaching out: - Your site URL as connected in Search Atlas. - The exact error message you see (e.g., the full console output or any on-screen error text). - Which deployment method you are using — JavaScript snippet, WordPress plugin, or both. - A timestamp of when the error first appeared or when you last saw it. - Any recent changes you made to your site, theme, tag manager, or OTTO settings around the time the error started. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO SEO Pixel Not Detected After Install

Overview After installing the OTTO SEO WordPress plugin and entering your UUID, some users still see an error stating the pixel is not detected when running a dashboard scan. This happens because a successful pixel installation requires two credentials: your UUID and your Search Atlas API Key. Skipping the API Key is the most common reason the scan fails to recognise the plugin. Prerequisites - Your WordPress site with the OTTO SEO plugin installed and activated - Admin access to your Search Atlas account - Your OTTO UUID (found inside the OTTO dashboard) - Your Search Atlas API Key (see steps below if you do not have this yet) Step 1: Locate Your Search Atlas API Key 1. Log in to your Search Atlas account. 2. Open the Account Menu → Settings → API Keys. 3. Find the API Key section on this page. 4. Copy your API Key and keep it ready. Step 2: Navigate to OTTO SEO 1. From the Search Atlas platform, open OTTO SEO → All Sites (SEO Automation). 2. Open your OTTO project or create a new one for the target site. 3. Locate your UUID on the OTTO dashboard and copy it. Step 3: Configure the WordPress Plugin 1. In your WordPress admin panel, go to Plugins and confirm the OTTO SEO plugin is active. 2. Open the plugin's settings page. 3. Paste your UUID into the UUID field. 4. Paste your Search Atlas API Key into the API Key field. This step is required — without it, the pixel cannot authenticate and the scan will fail. 5. Save your settings to apply the changes. Step 4: Re-run the Dashboard Scan 1. Return to Search Atlas and open OTTO SEO → All Sites (SEO Automation). 2. On your OTTO dashboard, trigger a new scan to check the pixel status. 3. If both credentials were entered correctly, the pixel should now be recognised by the dashboard. Troubleshooting: Scan Still Failing? If the pixel is still not detected after completing all steps above, work through the following checks: - API Key copied incorrectly: Return to Account Menu → Settings → API Keys and re-copy the key, making sure there are no leading or trailing spaces when pasting. - UUID mismatch: Confirm the UUID in the plugin matches the UUID shown in the OTTO dashboard for this specific site. Each site has a unique UUID. - Plugin not saved: Revisit the plugin settings page and verify both fields are populated, then save again. - Caching conflict: If your site uses a caching plugin or CDN, clear all caches after saving the plugin settings, then re-run the scan. If you need further assistance, open 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 Connecting After Installation

🧭 Overview After installing the Otto Pixel on your website, Search Atlas needs to detect the pixel before it can activate SEO automation. If you see the message "Otto Pixel not found", the pixel may not be placed correctly, or the platform may need more time to verify the connection. This guide walks you through the most common causes and how to fix them. If the steps below do not resolve your issue, our support team can investigate directly — see the escalation note at the end of this article. ✅ Before You Start: Quick Checklist Run through these checks before diving into detailed troubleshooting: - The Otto Pixel code snippet has been added to every page of your website (or your site-wide header/footer template). - The snippet is placed inside the <head> tag of your HTML, not in the body or footer. - Your website is publicly accessible — not under construction, password-protected, or blocked by a firewall. - You have saved and published any changes made to your site after adding the pixel. - Sufficient time has passed since installation before checking connection status. 🛠️ Step-by-Step Troubleshooting 1. Confirm the pixel is installed site-wide. The pixel must appear on every page, not just the homepage. If you use a CMS like WordPress, add the snippet to your theme's global header template or use a plugin that injects scripts site-wide. 2. Check placement in the <head> tag. Open your page source (right-click → View Page Source in your browser) and search for your Otto Pixel snippet. It should appear between the opening <head> and closing </head> tags. If it appears elsewhere, move it to the correct location and republish. 3. Clear your site's cache. Caching plugins or hosting-level caches can serve outdated page versions without the new pixel code. Clear all caches — including server cache, CDN cache (e.g., Cloudflare), and any WordPress caching plugins — then verify the pixel appears in the page source again. 4. Disable conflicting plugins or scripts temporarily. Some security or performance plugins block third-party scripts. Temporarily disable them one at a time to identify if one is preventing the pixel from loading. 5. Check for JavaScript errors. Open your browser's developer console (F12 → Console tab) and reload your page. Look for any JavaScript errors that may be stopping scripts from running. Resolve any errors shown, then retry the connection. 6. Check your site's robots.txt and firewall settings. Make sure your robots.txt file and any firewall or security rules are not blocking Search Atlas from accessing your site or loading the pixel script. 🚨 If the Issue Persists: How to Escalate If you have worked through all the steps above and the Otto Pixel still shows as not connected, this issue will need to be investigated by our support team. To help us resolve it as quickly as possible, please have the following ready before reaching out: - The exact error message you are seeing in Search Atlas (e.g., "Otto Pixel not found"). - The URL of the website where the pixel was installed. - The name of your OTTO project in Search Atlas. - A screenshot or copy of your page source showing where the pixel snippet is (or is not) appearing. - The date and time of when you first attempted installation. - Details of any caching, security, or script-management plugins 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.

🛠️ OTTO Pixel Troubleshooting Guide

If OTTO shows "Not Installed," "Not Detected," or is not firing, this guide covers every known root cause and fix — from incomplete setup and crawler blocks to caching conflicts and script placement errors. ⚠️ Error States This Guide Resolves - "OTTO Not Installed" - "OTTO Not Detected" - "Missing crawl data" - Pixel not firing - No deployments verified 🔍 Root Causes Almost all OTTO detection failures trace back to one of these causes: - Incomplete project setup (installation wizard not completed) - Caching or minification interference - Incorrect script placement - Duplicate pixel installations - Blocked Search Atlas crawler - Site performance / slow server response time 🧭 Universal Troubleshooting Steps Work through Steps 1–6 in order. Most OTTO detection failures are resolved by Step 2 or earlier. ⏳ Step 0 — Give a Brand-New Install a Few Minutes First If you just finished installing the pixel and OTTO still shows "Not Installed" or "Not Detected," this is very often a short detection delay — caused by cache/CDN propagation or the page needing a moment before our scanner re-checks it — rather than a broken install. - Wait a few minutes after installing, clear your site's cache (and your browser cache), then re-run the diagnostic scan. - If the status still shows "Not Installed" after that, continue with Steps 1–6 below, which cover the confirmed root causes: incomplete setup, crawler blocking, caching, script placement, duplicate installs, and slow server response. Note: Pixel detection and your project's Site Audit crawl are separate systems. A Site Audit crawl still running in the background does not block or delay your OTTO pixel status. ✅ Step 1 — Check for Incomplete Project Setup If your site shows "Not Installed" despite the OTTO pixel visibly firing, the project was likely added to OTTO but the setup wizard was never completed. This most commonly surfaces on Duda-hosted sites but can occur on any platform. Regardless of your CMS, an incomplete wizard creates a false "Not Installed" status even when the pixel is live and firing correctly. 1. Go to OTTO and locate the affected project. 2. If a Continue Installation button appears, click it to finish the setup wizard. 3. Re-run the diagnostic scan once setup is complete. The pixel status changes from "Not Installed" to "Detected" as soon as the setup wizard finishes. Note: If you are using Classic View on the Search Atlas home page and cannot connect your website to an OTTO project (receiving an API 400 error), switch to the new default view and try again. This is a known interface-specific bug currently being resolved. If switching views does not help, contact support. 🛡️ Step 2 — Whitelist the Search Atlas Crawler If your CDN or firewall blocks the Search Atlas user agent, OTTO cannot detect your pixel — even when it is installed correctly. This is the most critical step if Step 1 did not resolve the issue. ☁️ Cloudflare Go to Cloudflare → Security → Bots and disable: - Bot Fight Mode - Super Bot Fight Mode ⚠️ Known Issue OTTO-1850 — OTTO Shows Inactive Despite a Validated Cloudflare API Token Even when the Cloudflare API token shows as Connected in OTTO settings, a known detection bug may still report OTTO as inactive. Disconnect and reconnect the Cloudflare integration, then re-run the diagnostic scan. ⚠️ Known Issue OTTO-1931 — Deployed Changes Appear Then Revert This is a known issue with the Cloudflare DNS integration. Reconnect the integration and re-deploy. If reverts continue, contact support and reference OTTO-1931. ⚠️ Known Issue OTTO-1943 — Updated H1 Visible in Google Search Console but AI Crawlers Still Show the Original This is an edge-level deployment issue where the H1 does not deploy for non-JS bots, even though Googlebot (which renders JS) sees the updated H1. Contact support and reference OTTO-1943 for the backend fix. ☁️ Cloudflare Worker — Special Character Corruption If characters like &amp; or ' appear on your pages after engaging OTTO via Cloudflare, this was caused by a known OTTO Cloudflare Worker script-injection bug (SPE-666) that affected headings with nested HTML elements. The bug is resolved and the updated Cloudflare Worker script is live. To apply the fix: 1. Disengage OTTO. 2. Go to Avatar → Settings → Integrations. 3. Disconnect and reconnect your Cloudflare integration. 4. Re-engage OTTO. If encoding issues persist after reconnecting, contact support. Webflow note: On Webflow sites, after disengaging OTTO to fix encoding corruption, the diagnostic tool may fail to re-detect the Cloudflare Worker installation. If this occurs, fully remove and re-add the Cloudflare integration from scratch rather than using the reconnect flow, then re-run the diagnostic scan. 🔒 WordFence Go to WP Admin → WordFence → Firewall → Firewall Options → Allowlisted IPs/User Agents and add: - Search Atlas Bot (https://www.searchatlas.com/) 🚫 Stop Bad Bots Plugin Go to WP Admin → Block Bad Bots → Settings → Settings tab and either disable Block All Bots, or add the allowed user agent: - Search Atlas Bot (https://www.searchatlas.com/) 🧹 Step 3 — Clear Cache and Disable Minification Caching layers and JavaScript minification can prevent the OTTO pixel from loading correctly, or cause a previously detected pixel to stop firing. 1. Clear your site's server-side cache (hosting control panel or caching plugin). 2. Clear any CDN cache (e.g., Cloudflare → Caching → Purge Everything). 3. If you use a WordPress caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), purge all cached files. 4. If JavaScript minification or concatenation is enabled, temporarily disable it and re-run the OTTO diagnostic scan to confirm whether minification is the cause. 5. Re-run the OTTO diagnostic scan after clearing all caches. 📌 Step 4 — Verify Script Placement The OTTO pixel must be placed in the correct location in your page's HTML. Incorrect placement can prevent detection even when the script is present. - Place the OTTO pixel script inside the <head> tag, as high as possible. - Confirm the script is not inside a conditional block, a footer widget, or a section that renders after the page body. - On WordPress, check that no plugin is deferring or async-loading the OTTO script in a way that delays its execution. - Use your browser's developer tools (View Source or Elements panel) to confirm the OTTO script tag is present and in the <head>. 🔁 Step 5 — Check for Duplicate Pixel Installations Multiple instances of the OTTO pixel on a single page can cause detection failures or conflicting signals. 1. Use your browser's developer tools (Network or Elements panel) to search for multiple instances of the OTTO pixel script. 2. If you find duplicates, remove all but one installation — typically keeping the one managed through OTTO's official integration or your CMS's <head> injection. 3. Re-run the OTTO diagnostic scan after removing duplicates. 🐢 Step 6 — Check Site Load Time If your server responds too slowly, the Search Atlas crawler may time out before completing its scan, causing OTTO optimizations to appear missing even when the pixel is installed correctly. 1. Test your site's load time using PageSpeed Insights or a similar performance testing tool. 2. If your server response time (TTFB) is consistently above 2–3 seconds, contact your hosting provider — a slow or timing-out server can prevent the crawler from completing a full scan. 3. Re-run the OTTO diagnostic scan after any hosting or performance improvements. 🛍️ Shopify — Correct OTTO Pixel Installation Manual OTTO pixel injection on Shopify can break themes and generate multiple errors if the script is pasted into the wrong location. Do not copy-paste the pixel script directly into Shopify's theme editor without following the correct steps. 1. In your Shopify admin, go to Online Store → Themes → Edit Code. 2. Open theme.liquid and locate the closing </head> tag. 3. Paste the OTTO pixel script immediately before </head>. 4. Save the file and verify the script appears in the page source before going live. Avoid injecting the script into snippets, sections, or asset files that Shopify's pipeline compiles or reorders — this can conflict with the asset pipeline and trigger theme errors. If your theme already has 9 or more errors after injection, contact Search Atlas support for agent-assisted theme remediation. 🤖 AI-Builder and React-Based Sites — Deployments Engaged but Not Visible On sites built with AI-powered or no-code builders (such as Lovable.ai) or custom React frameworks, OTTO deployments may appear as "Engaged" in the dashboard but never render on the live site. This occurs when the site's own client-side code — commonly a MutationObserver or hydration logic inside a component like Seo.tsx — intercepts and reverts OTTO's DOM changes after they are applied. 1. Confirm that OTTO shows deployments as "Engaged" but changes are invisible on the live page. 2. Ask your developer (or audit the framework source yourself) to search for MutationObserver, useEffect with DOM targeting, or hydration calls inside SEO-related components (e.g., Seo.tsx, Head.tsx). 3. Any component that overwrites <title>, <meta>, or heading elements after page load can revert OTTO's changes. Remove or adjust the conflicting logic so it does not override third-party DOM modifications. 4. Contact Search Atlas support if you need help identifying the conflicting component. ⚠️ Known Issue — Fatal Error on Divi / Elegant Themes WordPress Sites If your Divi or Elegant Themes WordPress site goes down or displays a fatal PHP error after OTTO pixel installation (Call to undefined function et_theme_builder_decorate_page_resource_slug()), this is a known active bug in Otto_pixel_class.php:626. Open a support ticket immediately and include the Sentry reference WORDPRESS-METASYNC-2XGY so the team can prioritize and expedite the fix for your account. 🎯 After completing these steps, your OTTO pixel should detect successfully and deployments should begin verifying. If you are still seeing errors, contact Search Atlas support with your site URL and the specific error message — and reference any known-issue code above if it applies to your 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.

🔧 Pixel Troubleshooting After CMS Migration

Overview Migrating your store to a new platform is one of the most common reasons the Otto site pixel stops firing. The migration process can change your site's structure and data layer in ways that silently break an otherwise correctly installed pixel. This article explains what to expect and how to get support if your pixel stops working after a CMS migration involving Google Tag Manager (GTM). Why Migration May Break Your Pixel When you migrate to a new platform, several types of changes can disrupt pixel tracking: - GTM container not republished: Your GTM container may still reference old trigger conditions that no longer apply on the new platform. - Data layer differences: Different platforms structure their data layers differently, so variables used by your pixel tags may no longer be available or may have different names. - GTM snippet missing from new theme: The new platform's theme may not include the GTM snippet, so no tags fire at all. - URL structure changes: Page-specific triggers may now point to different URL paths on the new platform. - Cookie and consent settings reset: A new domain or subdomain can affect previously stored consent, blocking the pixel from firing. What to Do If Your Pixel Stops Firing After Migration Because the specific steps to reconfigure your pixel depend on your platform and GTM setup, we recommend contacting our support team directly so they can review your container configuration and guide you through the correct fix for your setup. To help us resolve your issue as quickly as possible, please have the following ready when you reach out: - Your GTM container ID (formatted as GTM-XXXXXXX) - The platform you migrated from and the platform you migrated to - A description of what the pixel was tracking before the migration - Any error messages or unexpected behavior you have observed - The approximate date the migration took place If you need further assistance, open 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 Pixel 404 Errors on Noindex Pages

🔍 What Is Causing the 404 Errors? The OTTO pixel fires on every page where it is installed, including pages marked with a noindex directive. When OTTO attempts to track or process a noindex page, it may send a request that returns a 404 (Not Found) response. This happens because noindex pages are often intentionally excluded from public-facing content — they may lack canonical URLs, be behind access controls, or simply not resolve as expected by the pixel's endpoint. The result is harmless to your live site, but it creates noise in your error logs and can make genuine issues harder to spot. 📋 Common Noindex Pages That Trigger This Issue - Thank-you and confirmation pages - Search results pages (e.g., /?s=query) - Login, account, and checkout pages - Tag and author archive pages set to noindex - Staging or draft pages accidentally published - Paginated pages beyond page 1 (e.g., /blog/page/2/) ⚙️ How to Exclude Noindex Pages from the OTTO Pixel The recommended fix is to add a script exclusion rule so the OTTO pixel does not fire on noindex pages. The two approaches below cover the most common implementation methods. If you are unsure which method applies to your setup or cannot locate the relevant setting in Search Atlas, contact our support team for guided assistance. 🚀 Option 1 — Request a Script Exclusion via Search Atlas Support If your OTTO pixel is managed through Search Atlas, script exclusions for noindex pages can be configured at the account or session level. Because the exact location of exclusion settings may vary depending on your plan and OTTO version, the most reliable path is to contact the support team and request that noindex page patterns be added to your pixel's exclusion rules. When you reach out, have the following ready: - Your Search Atlas project name or domain - The specific URL patterns or page types generating 404 errors (e.g., /?s=*, /page/2/, thank-you pages) - A sample from your error logs showing the 404 responses 🛠️ Option 2 — Conditionally Load the Pixel in Your Theme or Tag Manager If you manage the pixel code directly, wrap it in a condition that checks for the noindex meta tag before firing. This approach works for WordPress themes, custom CMS setups, and Google Tag Manager. WordPress (functions.php or a custom plugin): - Use the wp_head hook and check is_singular() combined with your noindex logic before outputting the pixel script tag. - Exclude template types such as search pages (is_search()), 404 pages (is_404()), and any archive marked noindex. Google Tag Manager: - Create a new Trigger of type Page View. - Add a trigger condition: fire only when the robots meta tag variable does not contain****noindex. - Attach this trigger to the OTTO pixel tag so it fires only on indexable pages. ✅ How to Verify the Fix Is Working After applying either option, monitor your error logs over the next 24–48 hours. The 404 entries tied to noindex pages should stop appearing. You can also use your browser's developer tools (Network tab) to confirm the pixel does not fire on a known noindex page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Pixel Duplicate Installation Errors

🔍 Overview If OTTO Pixel reports a duplicate installation error but you can only find the script once on your site, the issue is almost always related to how or where the script was installed — not necessarily how many times you intentionally added it. This article walks you through the most common causes and how to resolve them. ⚠️ Why the Duplicate Error Appears OTTO Pixel scans the rendered version of your page rather than just your source code editor. A single script block can appear more than once in the rendered output for several reasons: - Theme or plugin conflicts: A WordPress theme, page builder, or plugin may cause any injected script to be output more than once. - Caching layers: Stale cached versions of your page can cause an outdated copy of the script to appear alongside the current one. - Custom code placement: If the snippet was added to both a global custom code field and a page-specific field, it may fire twice even though it looks like one entry. - Search term mismatch: Searching your source for the script string may return zero results if the installed version is minified or encoded differently. Always search for the full script string exactly as it appears in your installed code. 🔎 How to Check for True Duplicates 1. Review every location where the OTTO Pixel script could have been added — global header/footer fields, page-specific custom code fields, any header/footer plugins, and any tag manager configurations. 2. Look for the script string in each location individually. If it appears in more than one place, you have a true duplicate. 3. If you cannot find a duplicate in your editor but the error persists, check whether a caching plugin or CDN may be serving a stale version of the page that still contains an old copy of the script. 🧹 How to Resolve the Duplicate - Remove all existing instances of the OTTO Pixel script from your site, including custom code fields, header/footer plugins, and any tag manager tags. - Clear all caches — server cache, CDN cache, and browser cache — before re-checking. - Re-install the script in one location only. The recommended method is via your site's global custom code or header field. Do not add it through multiple channels simultaneously. - Verify the fix by returning to OTTO and re-running the pixel check to confirm the duplicate error is 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 OTTO Pixel Verification Failures: UUID Mismatch

🧩 Overview If your OTTO pixel appears to be correctly installed on your Website Studio site but verification keeps failing, the most common cause is a UUID mismatch. This means the pixel snippet installed on your site contains a different unique identifier than the one associated with your current Search Atlas project. Even a single character difference will cause verification to fail every time. This article explains how to identify whether a UUID mismatch is the cause, and how to fix it quickly. 🚨 Symptoms of a UUID Mismatch - Pixel verification fails repeatedly despite following all installation steps correctly. - The OTTO pixel script is visible in your site's code, but Search Atlas does not confirm a successful connection. - You may have previously connected a different project or reinstalled OTTO at some point. - Verification fails immediately after clicking the verify button, with no change in status. 🔎 What Is a UUID and Why Does It Matter? A UUID (Universally Unique Identifier) is a unique code embedded inside your OTTO pixel snippet. Search Atlas uses this code to match the installed pixel to your specific project. If the UUID in your installed snippet belongs to a different project — or an older version of the same project — Search Atlas cannot verify ownership, and the connection will fail. This mismatch commonly happens when a pixel snippet is copied from a previous project, reused across multiple sites, or pulled from a cached or outdated source. 🛠️ Step 1: Locate Your Correct UUID in Search Atlas 1. Log in to your Search Atlas account. 2. Open the specific project associated with your Website Studio site. 3. Find the OTTO pixel snippet provided for that project. 4. Copy the full pixel snippet — this contains your project's correct, current UUID. Important: Always copy the snippet directly from the project you are trying to connect. Do not reuse snippets from other projects or from previous installations. 🔍 Step 2: Check the UUID Currently Installed on Your Site 1. Access your website's code or the page where the OTTO pixel snippet is installed. 2. Find the currently installed OTTO pixel snippet. 3. Identify the UUID within the snippet — it is a long alphanumeric string, typically appearing as a parameter value (for example: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). 4. Compare this UUID character by character with the UUID in the snippet you copied from your Search Atlas project in Step 1. If the two UUIDs do not match exactly, you have identified the root cause of your verification failure. ✅ Step 3: Replace the Mismatched Snippet and Re-Verify 1. Remove the existing OTTO pixel snippet from your site. 2. Paste the correct snippet (copied in Step 1) in its place. 3. Save and publish your changes so the updated snippet is live on your site. 4. Return to your Search Atlas project and click the verify button to re-check the connection. 5. Confirmation should appear shortly if the UUIDs now match. If verification still fails after confirming the UUIDs match exactly, double-check that the updated snippet is fully published and live on your site, then wait a few minutes and try verifying 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 OTTO SEO Tag Detection and Invoice Emails

🧭 Overview This article covers two common questions in one place: why OTTO SEO may fail to detect its tag on your website, and how to configure automatic monthly invoice emails. Both are straightforward to resolve once you know where to look. 🏷️ Why OTTO SEO Is Not Detecting the Tag If OTTO SEO cannot verify its tag on your website, the most common cause is a Content Security Policy (CSP) blocking the tag from loading or being recognised. A CSP is a security header that controls which external scripts and resources a browser is allowed to execute on your site. To access OTTO SEO, go to the left sidebar and select OTTO SEO → SEO Automation (URL: /seo-automation-v3). From there you can view your tag status and troubleshoot detection issues. 🔍 How to Confirm a CSP Is the Problem 1. Open your website in Google Chrome. 2. Right-click anywhere on the page and select Inspect. 3. Click the Console tab. 4. Reload the page and look for error messages that include the words Content Security Policy or CSP. 5. If you see a CSP error referencing the Search Atlas or OTTO SEO script domain, your policy is blocking the tag. ✅ How to Fix the CSP Block You need to add the Search Atlas script domain to your site's CSP allowlist. The exact steps depend on how your CSP is set — it may be configured in your web server settings, a plugin, a CDN such as Cloudflare, or directly in your site's code. 1. Locate where your CSP header is defined (server config, .htaccess, CDN dashboard, or a security plugin). 2. Find the script-src directive in your policy. 3. Add the OTTO SEO script domain to that directive. If you are unsure of the exact domain to whitelist, open the chat widget in the bottom-right corner of the platform and type human teammate — our team will provide the correct domain for your account. 4. Save your changes and clear any server or CDN cache. 5. Return to OTTO SEO in Search Atlas and click Verify Tag to confirm detection is successful. If your site is managed by a developer or a hosting provider, share these instructions with them so they can update the CSP on your behalf. 📬 How to Set Up Automatic Monthly Invoice Emails Search Atlas can automatically send your invoices by email each billing cycle so you never have to download them manually. Follow the steps below to configure this. 1. Click your account avatar or initials in the top-right corner of the platform. 2. Select Billing or Billing & Subscription from the dropdown menu. 3. Navigate to Billing → Invoices (Invoices page). 4. Enter the email address (or addresses) where invoices should be delivered each month. 5. Toggle on Send invoice by email or Automatic invoice delivery if the option is present. 6. Click Save to confirm your settings. Once saved, a PDF invoice will be emailed to the specified address automatically after each successful monthly charge. You can add multiple email addresses — useful if your finance team needs a copy alongside your primary account owner. 💡 Tips for Managing Billing Emails - Use a shared inbox: Adding a finance or accounts-payable email address ensures invoices reach the right person even if team members change. - Check your spam folder: The first automated invoice email may be filtered. Mark it as safe to avoid future delivery issues. - Download past invoices: Historical invoices are always available in the Billing section of your account if you need to retrieve them manually. 🆘 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 Detection and Google Analytics Issues

🔍 Overview Two of the most common setup issues in Search Atlas involve the OTTO Pixel not being detected on your site and Google Analytics properties failing to appear or connect. This article walks you through the most likely causes and how to fix them. ⚙️ Why the OTTO Pixel May Not Be Detected The OTTO Pixel can fire correctly and even appear in your page source without being successfully detected by Search Atlas. This is usually caused by one of the following reasons: - Pixel placed inside an iFrame or shadow DOM: Search Atlas scans the top-level document. If your pixel is injected inside an iFrame or a shadow DOM component, the detection crawler cannot read it. - Pixel loading after a JavaScript delay: If the pixel fires only after a user interaction or a delayed script execution, the detection tool may scan the page before the pixel renders. - Cookie consent blocking the pixel: A cookie consent or consent management platform (CMP) may be preventing the pixel from loading for users who have not accepted tracking, including automated crawlers. - Caching layer serving a stale page: Your CDN or server cache may be serving an older version of the page that does not yet include the pixel code. - Incorrect placement in the HTML: The pixel must be placed inside the tag of every page you want tracked, not in the footer or conditionally loaded only on certain pages. ✅ How to Fix OTTO Pixel Detection 1. Open your site's source code and confirm the pixel snippet is placed inside the tag, directly in the HTML and not inside a script loader or tag manager container that delays execution. 2. If you are using a tag manager such as Google Tag Manager, make sure the trigger is set to All Pages and the firing priority is high enough to load before other scripts. 3. Check your cookie consent platform settings. Add the OTTO Pixel to the necessary or always active category so it loads without requiring user consent. 4. Purge your CDN and server cache after making any changes, then wait a few minutes before triggering a new detection scan. 5. In Search Atlas, go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and locate your site. Click Re-detect Pixel to run a fresh scan after you have made the corrections above. 📊 Why Google Analytics Properties Are Not Showing Up If your Google Analytics properties are missing from the Search Atlas connection screen or fail to load after authorisation, consider these common causes: - Wrong Google account connected: The Google account you authorised may not be the one that has access to the relevant GA4 or Universal Analytics property. - Insufficient permissions on the GA property: Your Google account needs at least Viewer level access to a property for it to appear in Search Atlas. Editor or Administrator access is required to write data. - GA4 property not yet published: A newly created GA4 property can take up to 24–48 hours to become visible through the Google API. Wait and try reconnecting later. - Token expired or revoked: If you recently changed your Google account password or revoked third-party app access, the existing token will be invalid and must be re-authorised. - Multiple Google accounts causing a conflict: Browser sessions with multiple Google accounts logged in simultaneously can cause the wrong account to be used during OAuth authorisation. ✅ How to Fix Google Analytics Connection Issues 1. Sign out of all Google accounts in your browser, then sign back in using only the account that owns or has access to the GA property you want to connect. 2. In Search Atlas, go to Left sidebar → OTTO SEO → All Sites (SEO Automation), open your site settings, and disconnect the existing Google Analytics integration. 3. Navigate to Site Metrics → Site Explorer (GSC Accounts page) and click Connect GA Account to complete the OAuth flow again, making sure you select the correct Google account and grant all requested permissions. 4. Once reconnected, confirm that the correct GA4 property appears in the dropdown. If it does not, verify that your Google account has at least Viewer access to that property inside Google Analytics under Admin → Property Access Management. 5. If the property was created recently, wait 24–48 hours and attempt the reconnection again. 💡 Quick Checklist Before Contacting Support - OTTO Pixel is in the tag on all target pages - No cookie consent or CMP is blocking the pixel from loading - CDN and server cache have been cleared after pixel changes - Re-detect Pixel scan has been run from Left sidebar → OTTO SEO → All Sites (SEO Automation) - Only one Google account is active in the browser during OAuth - The connected Google account has sufficient permissions on the GA property - Newly created GA4 properties have been given 24–48 hours to propagate 🆘 Still Need Help? If you have followed all of the steps above and are still experiencing issues, we are 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 OTTO Pixel and Google Ads Visibility Issues

Overview Two common setup questions in OTTO PPC relate to the OTTO pixel not connecting and existing Google Ads campaigns not appearing after linking your ad account. This article explains what to have ready when reaching out to our team for each issue. Part 1: OTTO Pixel Connection Issues If your pixel is not showing as connected in OTTO PPC, our support team will need the following information to investigate and resolve the issue on your behalf: - The website URL where the pixel is installed - The platform or CMS your site uses (e.g. WordPress, Shopify, custom build) - A description of what you currently see in OTTO PPC regarding the pixel status - Any error messages you have encountered Because pixel connection issues may require backend verification, please have these details ready before reaching out so our team can investigate as quickly as possible. Part 2: Existing Google Ads Campaigns Not Showing in OTTO PPC If you have connected your Google Ads account to OTTO PPC but cannot see campaigns you previously created, our team will need to look into the account sync on the backend. Please have the following ready when you contact support: - Your OTTO PPC project name - The Google Ads account ID you connected - The names or types of campaigns that are not appearing - Any error messages or status indicators you have seen in OTTO PPC Providing these details upfront will allow our team to identify and resolve the visibility issue without additional back-and-forth. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Shows 'not_installed' — Troubleshooting Guide

Why This Happens If your OTTO pixel appears correctly in your page source but the platform still shows a not_installed status, the pixel itself is not the problem. The issue is almost always a temporary delay between installation and detection. Several factors can cause this gap: - Browser or server-side caching — Your site may be serving a cached version of the page that does not yet reflect the updated code. - CDN or DNS propagation — If your site uses a content delivery network (CDN) or recently updated DNS records, changes can take time to reach all servers. - Detection service lag — The OTTO detection service runs periodic checks. A status update may not appear immediately after installation. - Tag manager delays — If you installed the pixel through Google Tag Manager or a similar tool, the container may not have published or fired correctly on all pages. Step-by-Step Troubleshooting 1. Confirm the pixel is in the page source. Open your website in a browser, right-click anywhere on the page, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) and search for your OTTO pixel script. If it appears here, the pixel is installed at the code level. 2. Check on a hard-refreshed, uncached page. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to force a full reload bypassing the browser cache. Then check the page source again to confirm the pixel is still present. 3. Purge your CDN or server cache. Log in to your hosting provider or CDN dashboard (for example, Cloudflare, Fastly, or WP Engine) and purge all cached files. This forces the detection service to scan your live, updated page rather than a cached copy. 4. Verify the pixel fires on the correct pages. OTTO detection checks specific URLs associated with your project. Make sure the pixel is present on the exact pages linked to your OTTO workspace — particularly your homepage or the URL you submitted during setup. 5. Check your tag manager container (if applicable). If you used Google Tag Manager, open your GTM workspace and confirm the tag is published (not just saved as a draft) and that the trigger is set to fire on All Pages or the relevant page URL. Preview the container using GTM's built-in preview mode to verify the tag fires correctly. 6. Wait and recheck. Detection service intervals mean that even a perfectly installed pixel may show not_installed for some time after installation. If all the steps above confirm correct installation, allow some time for the status to refresh automatically before contacting support. When to Contact Support If you have confirmed the pixel is present in your page source, your cache has been purged, and the status has not updated after a reasonable waiting period, our team can investigate the detection service 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.

🔧 OTTO Schema Deployment Not Detected by Validators

🔍 Understanding Schema Deployment Validation OTTO deploys schema markup directly to your live pages. However, external validators like validator.schema.org and Google Rich Results Test may not immediately detect the deployed schema. This can happen due to caching, crawling delays, or validator limitations with dynamically injected content. 📋 Common Reasons for Validation Failures - Caching layers — CDN or server caches may serve old page versions without the new schema. - Validator crawling delays — External tools do not crawl your site in real time; they rely on their own indexes. - JavaScript-rendered schema — Some validators cannot execute JavaScript, so schema injected via OTTO's client-side deployment may be invisible to them. - Page not yet crawled by Search Atlas — If the page hasn't been crawled in the platform, OTTO may not have deployed schema to it yet. 🛠️ Step-by-Step Troubleshooting 1. Open the live page in your browser and view the page source (Ctrl+U) to confirm the schema markup is present in the HTML. 2. Clear any CDN, server, or browser caches, then re-test the URL in the validator. 3. In Search Atlas, go to Left sidebar → OTTO SEO → Site Audit → Page Explorer and verify the target page shows as crawled and has a recent crawl date. 4. If the page is not crawled, trigger a new crawl from Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring. 5. Use the Google Rich Results Test with the "Live URL" option to fetch the current version of the page. 6. Check the Left sidebar → OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks panel for any schema deployment tasks that are pending, failed, or blocked by validation warnings. ⚠️ Known Platform Limitations Recent updates address cases where the internal validator incorrectly flagged valid schemas as invalid, blocking deployment. A fix has been released to prevent valid schemas from being blocked. An upcoming release will allow users to bypass validation warnings and deploy schema anyway, and will also prevent deployment on pages that have not yet been crawled. ✅ Best Practices - Always verify schema presence in the raw page source before relying on external validators. - Allow 24–48 hours for external validators to update after a successful deployment. - Monitor Crawl Monitoring to ensure target pages are regularly crawled. - If schema is deployed but not detected, wait for the next crawl cycle and re-test. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Paste the raw schema JSON into validator.schema.org and review field-level errors. Also check for 'Unrecognized or malformed fields' where OTTO-generated schema output may be present on the page but not parsed correctly by external validators — distinct from JS rendering or caching issues.

🔧 Fix OTTO Pixel Installation Detection Failures

🧩 Overview If your WordPress site displays the message OTTO Pixel is not installed correctly even after following the standard installation guide, a security plugin is often the hidden cause. This article walks you through the most common reason detection can fail and how to resolve it: security plugins blocking the pixel from loading or being detected correctly. 🛡️ Security Plugin Interference (Most Common Cause) Security plugins protect your site by restricting external scripts and HTTP requests. Unfortunately, this protection can also block the OTTO Pixel from loading or being detected correctly. Plugins that include features such as a firewall, script manager, content security policy (CSP) editor, or external request blocker are known categories of tools that can interfere with OTTO Pixel detection. Follow these steps to rule out or fix security plugin interference: 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins and identify any active security plugins. 3. Temporarily deactivate each security plugin one at a time. 4. After each deactivation, return to Search Atlas and trigger a fresh pixel detection check. 5. If detection succeeds after deactivating a specific plugin, that plugin is the cause. 6. Re-activate the plugin and configure it to allow the OTTO Pixel script — consult your security plugin's own documentation for instructions on whitelisting external scripts or domains. ⚙️ Whitelisting the OTTO Pixel in Your Security Plugin Once you have identified which security plugin is blocking detection, configure it to allow the OTTO Pixel rather than leaving it deactivated permanently. Most security plugins provide a way to whitelist specific scripts or external domains — refer to your plugin's official documentation or support resources for the exact steps, as menu locations and option names vary between plugins and versions. In general, look for settings related to any of the following within your security plugin: - Firewall whitelist or allowlist rules - Script or resource allowlist - Content Security Policy (CSP) exceptions - External HTTP request permissions Add the Search Atlas / OTTO Pixel script domain to the relevant allowlist, then re-run the pixel detection check in Search Atlas to confirm the issue is resolved. 📋 Before Contacting Support If you are unable to resolve the detection failure after working through the steps above, please have the following information ready when you reach out: - The name and version of the security plugin(s) active on your site - The exact error message shown in Search Atlas - Any blocked-request log entries from your security plugin, if available - A note of when the issue started and any recent changes made to your site or plugins If you need further assistance, open 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 Recognition and Integration Issues

🔍 Overview If OTTO is not recognizing the pixel on your website — even though the code appears to be installed — there are several common causes. This guide walks you through the most effective troubleshooting steps to get your pixel detected and your site connected successfully. ⚙️ How OTTO Pixel Recognition Works OTTO scans your website to confirm the pixel is present and loading correctly. For recognition to succeed, the pixel script must be: - Placed in the correct location within your website's code - Loading without errors on the live, publicly accessible version of your site - Free from conflicts with caching, security plugins, or tag managers - Associated with the correct domain in your Search Atlas account If any of these conditions are not met, OTTO may fail to detect the pixel even when the code is visibly present in your HTML. 🛠️ Step-by-Step Troubleshooting 1. Verify pixel placement: The OTTO pixel script should be placed inside the <head> section of your website, ideally as close to the opening tag as possible. Placing it in the footer or inside a conditional block can prevent reliable detection. 2. Check the live site, not a staging environment: OTTO scans your publicly accessible URL. Make sure the pixel is deployed on the live version of your site, not a local or password-protected staging environment. 3. Confirm the correct domain is entered: In your Search Atlas account, verify that the domain associated with your OTTO project exactly matches the URL where the pixel is installed — including whether it uses www or non-www, and http or https. 4. Clear your site cache: Caching plugins and CDN services can serve an older version of your page that does not include the pixel. Clear all caches — server-side, plugin-level, and CDN — then trigger a fresh scan in OTTO. 5. Disable conflicting plugins temporarily: Security plugins, firewall tools, or JavaScript optimizers can block or defer the pixel script. Temporarily disable these one at a time and re-test recognition to identify the conflict. 6. Check for JavaScript errors: Open your browser's Developer Tools (F12), go to the Console tab, and reload your page. Look for any JavaScript errors that may be preventing the pixel from executing. 7. Inspect the rendered page source: Right-click your live website and select View Page Source. Search for the OTTO pixel snippet. If it does not appear, the script may be blocked before rendering. Also check the Elements panel in Developer Tools to see the fully rendered DOM. 8. Re-trigger the pixel scan: After making any changes, return to your OTTO project in Search Atlas and initiate a new scan to check whether the pixel is now detected. If you need further assistance, open 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 Installation Across CMS Platforms

🧭 Overview The OTTO Pixel connects your website to Search Atlas so OTTO can monitor and automate SEO tasks. If your pixel shows as Not Installed or Duplicate Detected, this guide walks you through platform-specific considerations, UUID validation, and a verification checklist for multi-account setups. 🔑 Step 1: Retrieve Your Account-Specific Pixel Code Each Search Atlas account has a unique pixel tied to its UUID. Using the wrong code—or reusing one across accounts—is the most common cause of detection errors. 1. Log in to Search Atlas and navigate to the OTTO or SEO automation section of the platform. 2. Select the specific account or project you are troubleshooting. 3. Locate the OTTO Pixel snippet for that account and copy it exactly as displayed. 4. Confirm the UUID string inside the snippet matches the account you are working on. The UUID is the alphanumeric identifier embedded in the pixel script URL. 5. If you manage multiple accounts, repeat this process for each one individually—never share a single pixel across different accounts. 📍 Step 2: Understand Header Placement Requirements The OTTO Pixel must be placed inside the <head> tag of every page, as high as possible before other scripts. Placement in the footer or body will cause unreliable detection and may trigger a Not Installed status even when the code is present. - The pixel should load on all pages, not just the homepage. - Avoid placing it inside conditional logic blocks that prevent it from firing on every page load. - If a tag manager (such as Google Tag Manager) is used, ensure the tag is set to fire on All Pages with no exceptions. 🏗️ Step 3: Platform-Specific Installation Guidance ⚡ GoHighLevel (GHL) GHL allows you to add custom scripts at the site or funnel level. Paste your OTTO Pixel snippet into your site's header script area so it fires on every page. Note that site-level scripts may not automatically apply to funnel pages—check each funnel's settings individually and add the pixel there as well if needed. Save and publish your changes, then allow some time before re-checking detection status in Search Atlas. 🔵 WordPress On WordPress, the pixel must be inserted into the <head> section of every page. You can do this by editing your theme's header template directly, or by using a plugin that allows you to inject scripts into the header site-wide. Using a plugin is generally recommended for stability, as direct theme edits may be lost if the theme is updated or changed. Whichever method you use, verify the pixel is loading on all pages—not just the homepage—after installation. 🌸 Orchid CMS Orchid CMS and similar platforms typically provide a global header code or custom script area in site settings. Paste your OTTO Pixel snippet into that header field so it applies across all pages. Consult your CMS documentation if you are unsure where the global header script area is located. ✅ Step 4: Verification Checklist - Confirm the UUID in your pixel snippet matches the correct Search Atlas account. - Verify the pixel is placed in the <head> section, not the footer or body. - Check that the pixel fires on all pages, not just the homepage. - For multi-account setups, ensure each site uses its own unique pixel—do not share snippets across accounts. - After making changes, wait a few minutes and then recheck pixel status in Search Atlas. - Use your browser's developer tools (View Source or Network tab) to confirm the pixel script is present in the page source. 🆘 Still Seeing Issues? If you have followed all of the steps above and your pixel status still shows as Not Installed or Duplicate Detected, a support agent can investigate further. When reaching out, please have the following ready: your Search Atlas project or account name, the URL of the affected site, the UUID from your pixel snippet, and a description of which CMS platform you are using. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Fix OTTO 'Not Engaged' Status After Pixel Installation

🔍 Overview If OTTO shows a Not Engaged status even though your pixel appears to be correctly installed, the issue may not be with the pixel code itself. Engagement activation depends on several additional conditions at the account, site, and settings level. This article outlines the known areas to investigate when OTTO remains in a Not Engaged state. 📋 Before You Begin Confirm the following before continuing. Each item should be true for engagement to activate: - The OTTO pixel is installed on every page of your website (typically via the <head> tag or a tag manager). - No duplicate pixel instances are present on your pages. - You are viewing the correct project in Search Atlas and confirm the domain shown matches your live site URL exactly, including any subdomain (e.g., www). - Sufficient time has passed since pixel installation, as engagement status may not update immediately. ⚠️ Areas to Investigate for Engagement Activation Failure When pixel installation appears correct, one of the following areas may be responsible for the Not Engaged status: - Domain mismatch: The domain registered in your Search Atlas project may not exactly match the domain where the pixel fires. Check for differences such as a missing or extra www, a trailing slash, or HTTP vs HTTPS. - Incomplete project setup: OTTO may require certain setup or onboarding steps to be completed before engagement can activate. Review your project configuration in Search Atlas to ensure all required steps have been completed. - Account subscription or seat limit: If your plan does not include OTTO or your OTTO seat allocation is exhausted, engagement will not activate regardless of pixel status. - Hosting environment restrictions: Some hosting environments may block the outbound signal from the OTTO pixel even when the pixel code is present on the page. - Pixel not firing site-wide: If the pixel is deployed through a tag manager, verify that it is configured to fire on all pages rather than only specific ones. - Cache serving a stale page version: A CDN or server-side cache may be serving a version of your pages that does not yet include the pixel code. Try clearing your cache and reconfirming pixel presence. 🛠️ Steps to Escalate Because confirming pixel signal delivery and account configuration requires backend access, the most effective path is to contact the support team directly. When you reach out, please have the following ready: - Your Search Atlas project name and the exact domain URL registered in that project - A description of how the pixel was installed (directly in code, via a tag manager, etc.) - Any error messages or status indicators you have observed in your Search Atlas account - The approximate date and time the pixel was installed or last updated If you need further assistance, open 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 Issues on Magento 2

🔍 Overview If OTTO is not detecting the pixel on your Magento 2 website — even after placing the code in your theme header — this guide walks you through the most common causes and how to fix them. Follow each step in order before moving to the next. ⚙️ How OTTO Pixel Installation Works OTTO requires a small JavaScript pixel to be present in the <head> section of every page on your website. Once detected, OTTO can activate automated on-page SEO improvements across your site. On Magento 2, several platform-specific factors can prevent the pixel from being recognised even when the code appears to be in place. ✅ Step-by-Step Troubleshooting 1. Confirm the correct pixel code is being used. Log in to Search Atlas and locate your OTTO pixel snippet. Do not reuse a snippet from a previous session — it may have changed. 2. Place the pixel in the correct Magento 2 location. The pixel code must be added to the <head> section of your Magento 2 theme so it loads on every page. Consult your developer or your theme documentation for the appropriate method to inject a script into the page head for your specific Magento 2 setup. After saving, flush your Magento cache to ensure the change takes effect. 3. Check that full-page cache is cleared. Magento 2 uses aggressive full-page caching. After saving your changes, ensure you clear all relevant caches — including any full-page cache and, if applicable, any reverse-proxy cache such as Varnish. 4. Verify the pixel renders in your page source. Open your website in a browser, right-click anywhere on the page, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for your OTTO pixel ID or the pixel script tag. If it is not present, the code was not saved correctly — repeat the previous step. 5. Check whether JavaScript bundling or minification is interfering. Magento 2's built-in JS bundling and minification can sometimes interfere with inline scripts. If you suspect this is the cause, consult your developer about temporarily disabling these optimisations to confirm whether they are blocking pixel detection. 6. Check for a Content Security Policy (CSP) blocking the pixel. Magento 2.4+ enforces strict Content Security Policies by default. If your browser console shows a CSP error related to the OTTO script, you will need to whitelist the OTTO domain in your store's CSP configuration. Consult your developer to add the required domain to your store's CSP allowlist. 📋 When to Escalate If you have worked through all of the steps above and OTTO still does not detect the pixel, please have the following ready before reaching out to support: - Your project or website name in Search Atlas - A description of where and how you added the pixel code - Confirmation of which caches have been cleared - Any error messages visible in your browser console (F12 → Console) If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix a Disconnected Pixel During Site Audit

🔎 What Is the Pixel Disconnection Issue? When Search Atlas runs a site audit crawl, the crawler systematically visits every page on your website. In some cases, this process can trigger a pixel disconnection — meaning the tracking pixel loses its active connection to the platform. This is a known behavior caused by the volume and speed of requests made during a crawl, which can temporarily interrupt the pixel's communication with Search Atlas servers. If you see a disconnected pixel status, do not worry. Your data is not lost, and the issue is straightforward to resolve. ⚠️ Why Does This Happen? There are a few common reasons why a pixel may disconnect during a site audit: - Crawler traffic volume: The site audit sends a high number of requests in a short period. Some hosting environments or security plugins may rate-limit or block this traffic, which can interrupt the pixel. - Caching plugins or CDN rules: Caching layers or content delivery networks may strip or block the pixel script from loading during the crawl. - JavaScript execution issues: The pixel relies on JavaScript to fire correctly. If your site's JS is partially blocked or deferred during crawling, the pixel may not load as expected. - Security or firewall settings: Firewalls, bot protection tools, or WAF (Web Application Firewall) rules may flag crawler requests and block associated scripts, including the pixel. 🛠️ How to Reconnect Your Pixel Follow these steps to restore your pixel connection after a site audit: 1. Navigate to OTTO SEO → SEO Automation using the left sidebar (URL: /seo-automation-v3). 2. Locate the project associated with your disconnected pixel. 3. Open the pixel settings for that project and copy the pixel code snippet. 4. Log in to your website's backend (WordPress, Shopify, or your CMS of choice) and confirm the pixel code is present in the <head> section of every page, or reinstall it if it was removed. 5. Return to Search Atlas and use the Verify Pixel option (if available) to confirm the connection has been re-established. 6. Once verified, re-run your site audit to confirm everything is working correctly. ✅ How to Prevent Future Disconnections Taking a few precautions before running a site audit can help keep your pixel connected throughout the crawl: - Whitelist the Search Atlas crawler IP ranges in your firewall or security plugin settings so crawl requests are not blocked. - Disable aggressive bot protection temporarily before starting a large crawl, then re-enable it once the audit is complete. - Check your CDN settings to ensure JavaScript files — especially third-party scripts like the Search Atlas pixel — are not being stripped or blocked. - Use a tag manager (such as Google Tag Manager) to load the pixel, which can improve reliability across different page states and crawl conditions. - Avoid running multiple large crawls simultaneously, as this can compound the load on your server and increase the chance of a disconnection. 📊 Checking Pixel Status in Site Explorer You can monitor your pixel status at any time by visiting Site Metrics → Site Explorer in the left sidebar (URL: /site-explorer/list). Your connected projects will display their current pixel health status here. If a project shows as disconnected, return to the steps in the section above to resolve it promptly and avoid gaps in your tracking data. 💬 Still Need Help? If you have followed the steps above and your pixel is still showing as disconnected, or if you are unsure which part of your setup is causing the issue, we are 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 Site Pixel Detection and Auditor Timeouts

🧭 Overview If Search Atlas is not detecting your site pixel — even though another tool confirms it is present in your page header — the issue is almost always related to how and when the pixel loads, or how the site auditor is able to access your site. This article walks you through the most common causes and how to fix them. 🔍 Why Your Pixel May Not Be Detected Search Atlas scans your page to verify the pixel during the site audit process. Several factors can prevent a successful detection even when the pixel is technically installed: - Pixel loads after the page renders (deferred or async loading): If your pixel fires via JavaScript after the initial page load, the auditor may finish scanning before the pixel becomes visible in the DOM. - Tag Manager delays: Pixels deployed through Google Tag Manager or similar tools may not fire during automated scans because trigger conditions (e.g., user interactions, consent acceptance) are not met. - Consent Management Platform (CMP) blocking: If your site uses a cookie consent banner, the pixel may be blocked until a user accepts cookies — something an automated scanner cannot do. - Caching layers serving a pixel-free version: CDN or server-side caching may serve a cached page that was rendered before the pixel was installed. - Geo-blocking or bot protection rules: Firewalls, Cloudflare bot-fight mode, or geo-restrictions may block the Search Atlas scanner before it can read your page content. - Pixel placed outside the <head> tag: The auditor specifically looks for the pixel in the page head. A pixel placed only in the body or footer may not be found. ⚙️ How to Resolve Pixel Detection Issues 1. Confirm placement in the <head> tag: Open your page source (right-click → View Page Source) and confirm the Search Atlas pixel snippet appears inside the <head> section, not just in the body. 2. Switch to direct (non-GTM) installation: Temporarily install the pixel directly in your site's theme or template header file, bypassing Tag Manager, to rule out trigger-condition issues. 3. Disable or configure your CMP for the pixel: Whitelist the Search Atlas pixel in your Consent Management Platform so it loads without requiring user consent, or set it to fire in the pre-consent category. 4. Purge your CDN and server cache: After installing or adjusting the pixel, clear all caching layers so the scanner receives a fresh version of your page. 5. Whitelist the Search Atlas crawler: In your firewall or bot-protection settings, allow automated scanners to access your site. If you use Cloudflare, temporarily disable Bot Fight Mode and retest. 6. Re-run the site audit: After making changes, navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and trigger a fresh audit to allow Search Atlas to re-scan your site. ⏱️ Resolving Site Auditor Timeout Errors A timeout occurs when the Search Atlas auditor cannot finish crawling your site within the allowed time window. This is separate from pixel detection but often happens alongside it. Common causes and fixes include: - Slow server response times: If your server takes more than a few seconds to respond, the auditor may time out. Use a performance tool such as Google PageSpeed Insights to check your Time to First Byte (TTFB) and address hosting or server issues. - Large or complex pages: Pages with excessive scripts, large images, or hundreds of DOM elements take longer to process. Optimise page performance to reduce load time. - Bot-blocking rules timing out the connection: Some security configurations do not outright block the crawler but cause it to hang until the connection drops. Review your firewall logs for dropped or stalled connections from scanning IP ranges. - Crawl budget exhaustion on very large sites: If your site has thousands of pages, the auditor may not complete within a single session. Contact support (see below) to discuss crawl configuration options. ✅ Quick Checklist Before Contacting Support - Pixel is confirmed in the <head> tag via View Page Source - Cache has been fully purged after pixel installation - Tag Manager triggers and CMP consent rules have been reviewed - Firewall and bot-protection settings allow automated scanners - A fresh audit has been re-run from Left sidebar → OTTO SEO → SEO Automation - Server response time is under 2 seconds 💬 Still Seeing the Issue? If you have worked through all the steps above and the pixel is still not being detected or the auditor continues to time out, 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.

🛠️ Fix OTTO UUID Mismatch on Your Homepage

🔍 What Is a UUID Mismatch? Every OTTO SEO installation uses a unique identifier called a UUID (Universally Unique Identifier). This UUID is embedded in the OTTO pixel installed on your website. A UUID mismatch occurs when the UUID detected on your homepage does not match the UUID associated with your Search Atlas project. When this happens, OTTO may appear as Installed in your dashboard even though it is not functioning correctly, or it may report an engaged wrong UUID — meaning it has picked up and activated a UUID that belongs to a different project or contains an invalid value. ⚠️ Common Causes of a UUID Mismatch - Invalid username stored as UUID: In some cases, a WordPress username or other non-UUID value was incorrectly saved as the OTTO pixel identifier during setup. - Non-canonical site ID used in the install tag: If your pixel was installed using a non-canonical version of your domain (for example, www vs. non-www), the UUID may not resolve correctly. - Incorrect www-prefixed canonical injected: OTTO may have injected a www-prefixed canonical tag on a site that does not use www, causing the pixel to reference the wrong domain identity. - Duplicate or conflicting pixel installations: Having multiple OTTO pixel snippets on the same page — each with different UUIDs — will cause OTTO to engage the wrong one. 🛠️ How to Troubleshoot and Fix the UUID Mismatch 1. Locate your correct UUID in Search Atlas. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). Open your project and find the OTTO pixel installation section. Copy the UUID displayed there — this is your authoritative UUID. 2. Check what UUID is live on your homepage. Open your homepage in a browser, right-click anywhere, and select View Page Source. Use Ctrl+F (or Cmd+F on Mac) to search for otto or uuid. Identify the UUID value currently embedded in the pixel snippet. 3. Compare the two UUIDs. If the UUID in your page source does not exactly match the UUID shown in your Search Atlas project, a mismatch is confirmed. 4. Remove any incorrect or duplicate pixel snippets. In your WordPress admin panel (or whichever CMS you use), locate where the OTTO pixel snippet is inserted — this is commonly in a header/footer plugin, your theme's functions.php, or a custom HTML block. Delete any snippet that contains the wrong UUID or any duplicate snippets. 5. Re-install the correct OTTO pixel. Copy the full pixel snippet from your Search Atlas OTTO SEO project page and paste it into the correct location on your site. Ensure the snippet is placed within the tag of every page, including the homepage. 6. Verify your canonical domain setting. Confirm whether your site uses www or non-www as its canonical domain. Make sure the pixel is installed under the matching version. If your site is non-www, do not install or reference the pixel using a www URL. 7. Clear your site cache. After updating the pixel, clear any caching plugin, server-side cache, or CDN cache so the new snippet is served immediately. 8. Re-check the page source. Reload your homepage, view the source again, and confirm the UUID now matches your Search Atlas project UUID exactly. 9. Reconnect OTTO in Search Atlas if needed. Return to Left sidebar → OTTO SEO → SEO Automation and check your project status. If OTTO still shows as uninstalled or mismatched after the steps above, use the reconnect or re-verify option within the platform to trigger a fresh detection. ✅ How to Confirm the Fix Was Successful After completing the steps above, your OTTO SEO project in Search Atlas should show a green Installed status with no UUID mismatch warning. The UUID visible in your homepage source code will match exactly what is displayed in your project settings. OTTO will then be able to crawl, optimise, and report on your site correctly. 💡 Tips to Prevent Future UUID Mismatches - Always copy the OTTO pixel snippet directly from your Search Atlas project page — never type or reconstruct it manually. - Use a single, consistent canonical domain (www or non-www) across your entire site and ensure your OTTO installation matches it. - If you migrate your site or change your domain structure, re-install the OTTO pixel from scratch using the updated snippet from Search Atlas. - Avoid installing third-party scripts or plugins that might overwrite or duplicate your OTTO pixel. 💬 Still Seeing a UUID Mismatch? If you have followed all the steps above and the mismatch 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.

🛡️ WAF Blocking Script Tags in OTTO Custom HTML

🔍 Overview When you paste code containing tags into the Custom HTML Content field inside OTTO SEO, the platform's Web Application Firewall (WAF) may strip or block that content before it is saved or deployed. This article explains why this happens, how to deliver JSON-LD structured data safely, and what to do if you need to inject other types of scripts. ⚙️ Why the WAF Blocks Script Tags Search Atlas runs a WAF in front of all user-submitted content fields to protect the platform and your site from cross-site scripting (XSS) and code-injection attacks. The WAF applies a blanket rule that flags any raw tag submitted through form inputs — including the Custom HTML Content field in OTTO SEO. This behavior is intentional and by design; it is not a bug specific to your account. The WAF rule affects: - Inline blocks (e.g. JSON-LD wrapped in ) - External script references (e.g. ) - Any HTML attribute that contains JavaScript event handlers ✅ Supported Way to Deliver JSON-LD Structured Data JSON-LD is the recommended format for structured data, and there is a dedicated, WAF-safe path to deploy it through OTTO SEO without using the Custom HTML Content field. 1. Open OTTO SEO → All Sites (SEO Automation) from the left sidebar (or navigate to /seo-automation-v3). 2. Select the page or template you want to add structured data to. 3. Look for the Schema / Structured Data section within the OTTO SEO page settings. 4. Enter your JSON-LD object directly into the structured data editor — without the wrapping tags. OTTO automatically wraps your payload in the correct tag and injects it into the page head at deploy time, bypassing the WAF rule entirely. 5. Save and deploy your changes as normal. This is the only fully supported method for delivering JSON-LD through OTTO SEO. It ensures your structured data passes WAF validation and is rendered correctly by search engine crawlers. 📋 What About Tracking Pixels and Other Scripts? Tracking pixels and third-party scripts (e.g. Google Tag Manager, Meta Pixel, TikTok Pixel) should not be added through the Custom HTML Content field. The recommended approach is: - Google Tag Manager (GTM): Install the GTM container snippet through your site's theme or CMS header/footer injection settings, then manage all pixels and scripts inside GTM. OTTO SEO can detect an existing GTM installation and will not duplicate it. - Native pixel fields: Some integrations within Search Atlas have dedicated pixel ID fields — use those instead of pasting raw script tags. - CMS-level injection: For scripts that must be on every page, add them at the theme or template level in your CMS (e.g. WordPress header.php, Shopify theme settings) rather than through OTTO's content fields. 🚫 What Is Not Supported - Raw tags pasted into the Custom HTML Content field — these will be blocked by the WAF and will not appear on your site. - Account-level WAF exceptions for individual customers — the WAF rules are platform-wide and cannot be disabled for specific accounts. - Encoding workarounds (e.g. Base64-encoded scripts or HTML entity encoding) — the WAF is designed to detect obfuscated script patterns and will still block them. 💡 Quick Troubleshooting Checklist - JSON-LD not appearing on your page? Confirm you are using the dedicated Schema / Structured Data section in OTTO SEO, not the Custom HTML Content field. - Structured data editor not visible? Make sure your OTTO SEO plan includes schema automation. Check your subscription or contact support. - Pixel not firing? Verify the pixel is installed at the CMS or GTM level, not through a Custom HTML field. - Custom HTML content disappearing after save? This is the WAF removing blocked tags. Remove any tags from your content before saving. 🆘 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 Website Studio SPA Navigation and Page Detection Issues

🔍 Overview Two known issues can affect your experience in Website Studio: the scroll position not resetting when navigating between pages in the preview, and a false duplicate-page error that incorrectly blocks you from creating pages with similar-but-distinct URL slugs. This article explains both issues, their causes, and what you can do right now. 📜 Issue 1: Scroll Position Does Not Reset on Page Navigation When navigating between pages in the Website Studio preview — for example, moving from the Home page to the Contact page — the preview window may not scroll back to the top of the new page. Instead, it retains the scroll position from the previous page, making it appear as though content is missing or the page did not load correctly. Why this happens: Website Studio uses a Single Page Application (SPA) router to handle navigation inside the preview. In certain cases, the router does not trigger a scroll-position reset when transitioning between pages, so the viewport stays wherever it was on the previous page. What you can do right now: - After navigating to a new page in the preview, manually scroll to the top of the preview window to verify the full page content is present. - Use the browser refresh button inside the preview frame to force a full reload of the newly selected page — this will always land you at the top. - If you are reviewing a specific section, use the Website Studio section panel to jump directly to that section rather than scrolling from the navigation. Status: This bug has been identified and a fix has been deployed. If you are still experiencing scroll issues after following the steps above, please contact our support team using the instructions at the bottom of this article. 🚫 Issue 2: Duplicate Page Detection Incorrectly Blocks New Pages When attempting to create a new page with a URL slug such as /education-acoustic-solutions/, Website Studio may display an error stating the page already exists — even though the only existing page is /acoustic-solutions/. These are two distinct pages, and the error should not appear. Why this happens: The duplicate-page detection logic performs a partial string match on existing URL slugs rather than an exact match. Because /acoustic-solutions/ is a substring of /education-acoustic-solutions/, the system incorrectly treats the new slug as a duplicate and blocks the creation. What you can do right now: 1. Confirm that the page you want to create does not already exist by checking your full page list in Website Studio under Pages. 2. If the slug you want is genuinely unique and the error still appears, try a temporary workaround: create the page with a slightly different slug (for example, /edu-acoustic-solutions/), publish it, then rename the slug to your intended URL in the page settings. 3. Alternatively, reach out to support (see below) and a teammate can create the page on your behalf while the fix is confirmed on your account. Status: This bug has been identified and resolved in the platform. If you encounter this error after the fix, the steps above will help you move forward without losing progress. ⚙️ Additional Context: SPA Detection on Single-Page HTML Uploads A related issue affected websites built from single-page HTML uploads. Website Studio was incorrectly identifying these uploads as SPA sites and applying SPA routing logic, which caused the system to delete all pages after the first. This has been fully resolved. If you uploaded a single-page HTML file and noticed pages disappearing, please re-upload your file and verify your page list is intact. ✅ Quick Checklist Before Contacting Support - Manually scroll to the top of the preview when switching pages to confirm content is loading correctly. - Check your full page list to confirm a slug truly does not exist before creating a new page. - Try the temporary slug workaround if the duplicate-page error persists. - Clear your browser cache and reload Website Studio if any visual issues remain after a fix has been noted as deployed. 💬 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 OTTO Pixel Detection Backend Mismatch

🔍 Overview If your Search Atlas dashboard displays the OTTO pixel status as Not Installed but you can confirm the pixel code is present in your site's live HTML source, you are experiencing a backend detection mismatch. This issue is resolved by the Search Atlas support team on the backend — no self-serve fix is available. This article explains what to expect and how to prepare when reaching out for help. ⚙️ Why This Happens The OTTO pixel detection system checks for your pixel using backend logic. Sometimes a mismatch occurs between what the dashboard reports and what actually exists in your HTML. Because this is resolved at the backend level, the root cause will be investigated and corrected by the support team. 📋 What to Prepare Before Escalating To help the support team resolve your backend detection mismatch as quickly as possible, please have the following information ready when you open a support conversation: - Your project name in Search Atlas (the site or property affected). - The exact pixel status shown in your dashboard (e.g., "Not Installed"). - Confirmation that the pixel is present in your live site's HTML source — a screenshot or copy of the relevant HTML snippet is helpful. - The timestamp of when you first noticed the mismatch. - Any recent changes you made to the pixel installation (e.g., moved it to a tag manager, updated your theme, reinstalled the snippet). 💡 What Happens Next Once you contact the support team with the above details, they will investigate the detection mismatch on the backend and correct the pixel status. You do not need to reinstall or modify the pixel yourself while waiting for this fix. If you need further assistance, open 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 Installation and Custom CMS Setup

🔍 Overview Two common setup questions arise when connecting OTTO SEO to a site that uses a custom or unsupported CMS: why the integration dropdown shows limited options, and why OTTO displays Engaged but not Installed after the Pixel script has been added. This article explains both issues and walks you through the steps to resolve them. 🌐 Why Only Certain CMS Options Appear in the Integration Setup Search Atlas currently offers native one-click integrations for a curated list of supported platforms. If your site runs on a custom or proprietary CMS — for example, an in-house-built solution — it may not appear in the integration dropdown. This is expected behaviour and does not prevent OTTO from working on your site. For custom CMS platforms, you bypass the dropdown entirely and install the OTTO Pixel manually by adding the script directly to your site's code. Follow the steps in the section below to do this correctly. ⚙️ How to Manually Install the OTTO Pixel on a Custom CMS 1. In Search Atlas, navigate to the OTTO SEO section. 2. Open your OTTO project and go to the settings or setup area for your site. 3. Copy the OTTO Pixel script snippet provided in the dashboard. 4. Paste the snippet into your site's base HTML template so it loads on every page of your site. 5. Publish or deploy the change through your CMS or deployment pipeline. 6. Return to Search Atlas and allow a few minutes for OTTO to detect the Pixel. Important: The Pixel must load on all pages, not just the homepage. ❓ Why OTTO Shows "Engaged" but Not "Installed" These two statuses mean different things: - Engaged means OTTO has been activated for your project inside Search Atlas and is ready to work. - Installed means the OTTO Pixel script has been detected live on your website. If your status shows Engaged but not Installed, it means Search Atlas cannot yet detect the Pixel on your site. Common reasons include: - The script was added to only one page (e.g., the homepage) instead of the global template. - The deployment or publish step was not completed after adding the script. - A caching layer or CDN is serving an older version of the page without the script. - The script snippet was modified or truncated when pasting. ✅ How to Verify the Pixel Is Installed Correctly 1. Open any published page of your site in a browser. 2. View the page source and search for the OTTO Pixel script to confirm it is present. 3. Check that the script appears on multiple pages, not only the homepage. 4. If you recently deployed, clear your cache or wait for your CDN to propagate the update, then recheck the status in Search Atlas. If the status still does not update to Installed after confirming the above, please reach out to our support team with your project name and a description of your CMS setup so we 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. Additional Notes Verify the script is live: Open your website in a browser, right-click anywhere on the page, and select View Page Source. Search for your Pixel script tag to confirm it is present in the rendered HTML.

🔍 Fix OTTO Schema Not Detected on Homepage

🧭 Overview OTTO deploys and monitors schema markup across your connected site. In some cases, the homepage may appear to have no schema detected — even after a successful deployment. This article explains the most common reasons this happens and walks you through the steps to fix it. ⚠️ Why OTTO May Not Detect Schema on Your Homepage There are a few key reasons OTTO might not detect schema on your homepage: - The page has not been crawled yet. OTTO can only deploy and verify schema on pages that have been crawled and indexed within the platform. If your homepage has not been crawled, OTTO has no data to work with. - The page was not crawled before schema was deployed. Schema deployed to an uncrawled page may not be recognised or verified correctly, resulting in a null or empty detection state. - A crawl completed but schema validation has not refreshed. There can be a short delay between a crawl finishing and the schema detection status updating in the UI. - A conflicting schema source exists. If another plugin or tool (such as a WordPress SEO plugin) is also serving schema independently, it can interfere with what OTTO detects and reports. - The homepage URL format varies. A mismatch between how the homepage URL is stored (e.g. with or without a trailing slash, www vs. non-www) can cause OTTO to treat the crawled page and the deployed page as different URLs. 🛠️ How to Fix Schema Detection on Your Homepage 1. Confirm your site is connected to OTTO. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or navigate to /seo-automation-v3). Make sure your site is active and OTTO is enabled. 2. Check whether your homepage has been crawled. Inside OTTO, look for your homepage URL in the page list. If it is missing, trigger a new crawl for your site and wait for it to complete before deploying any schema. 3. Redeploy schema after the crawl completes. Once the homepage appears as a crawled page, navigate to the Schema section for that page and deploy the desired schema types. Do not deploy schema before the crawl has finished. 4. Refresh the detection status. After deploying, wait a few minutes and then reload the OTTO dashboard. The schema detection status should update to reflect the deployed markup. 5. Check for conflicting schema sources. If you are using WordPress, verify that other plugins are not independently outputting schema markup for the same page. Duplicate or conflicting schema can cause OTTO's detection to return incomplete results. Disable any overlapping schema output from third-party plugins. 6. Verify the homepage URL format. Confirm that the URL OTTO has crawled matches exactly how your homepage is accessed in a browser — including protocol (https://), subdomain, and trailing slash. ✅ How to Confirm Schema Is Working Once you have redeployed schema and the crawl has refreshed, you can confirm everything is working correctly: - Open the OTTO SEO → All Sites (SEO Automation) section and select your homepage from the page list. - Check that the schema types you deployed are shown as active and detected. - For additional validation, paste your homepage URL into Google's Rich Results Test to confirm the markup is visible to external tools as well. 💡 Best Practices to Prevent This Issue - Always allow a full site crawl to complete before deploying schema to any page. - Avoid using multiple tools to manage schema on the same pages. - Re-run a crawl periodically to keep page data current and ensure ongoing schema detection accuracy. 🙋 Still Need Help? If you have followed the steps above and schema is still not detected on your homepage, If you need further assistance, open 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 OTTO Wrong-Domain Pixel Error

🔍 What Is This Error? When you install the Search Atlas pixel instead of the white-label pixel, OTTO cannot verify your domain. This triggers a wrong-domain error that prevents Atlas Brain from deploying any SEO fixes to your site — including on platforms like GoHighLevel. The two pixels look similar during installation, but OTTO's domain-verification logic is strict: it only accepts the white-label pixel tied to your specific account. Using the default Search Atlas pixel causes a mismatch between the pixel's registered domain and the domain OTTO is trying to manage. ⚙️ Why This Happens - The Search Atlas pixel is a generic, platform-level pixel not linked to your white-label domain. - The white-label pixel is generated specifically for your account and contains a unique identifier that OTTO uses to confirm domain ownership. - Installing the wrong pixel means OTTO's verification check fails every time, regardless of where (GoHighLevel, WordPress, or any other CMS) the pixel is placed. 🚀 How to Fix It — Step by Step 1. Go to OTTO in the left sidebar by clicking OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select the website project that is showing the wrong-domain error. 3. Navigate to the Pixel / Tracking section within that project's settings. 4. Copy the white-label pixel snippet displayed there. This is the pixel unique to your account — do not use any snippet copied from general Search Atlas documentation or a different project. 5. Open your GoHighLevel account (or whichever platform hosts your site). 6. Locate the area where your current pixel is installed — typically in your site's header scripts or a dedicated tracking/scripts section. 7. Remove the existing Search Atlas pixel snippet in its entirety. 8. Paste the white-label pixel snippet you copied in step 4. 9. Save and publish the change so it goes live on your site. 10. Return to OTTO SEO in Search Atlas and trigger a re-verification for your domain. OTTO will re-scan for the pixel and, once it detects the correct white-label version, the wrong-domain error will clear automatically. ✅ How to Confirm the Fix Worked - The wrong-domain error banner disappears from your OTTO project dashboard. - The pixel status changes to Installed (green indicator). - Atlas Brain resumes queuing and deploying SEO optimisations to your site. If the status still shows Not Installed after following the steps above, double-check that no caching layer (CDN, platform cache, or browser cache) is serving the old page. Clear all caches and trigger verification again. 💡 Tips to Avoid This Issue in Future - Always retrieve your pixel snippet directly from the OTTO SEO section of your specific project — never from generic setup guides or email instructions that may reference the standard Search Atlas pixel. - If you manage multiple client sites, each project has its own unique white-label pixel. Do not reuse a pixel snippet across different domains. - After any site migration or platform change, re-verify the pixel inside OTTO to ensure the snippet transferred correctly. 🙋 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.

🔍 OTTO Pixel Installed But Not Detected

🔍 Why the Pixel Shows in Source but Fails the Scan When you add the OTTO pixel to your site and confirm it appears in the page source, your installation is technically correct. The Not Detected status is almost always caused by your site's bot-protection or firewall blocking the Search Atlas crawler before it can read your page HTML at all. Instead of seeing your pixel, the crawler receives an Access Denied, CAPTCHA, or JavaScript-challenge page and reports the pixel as missing. This is not a temporary caching issue and will not resolve on its own. It persists until the Search Atlas crawler IP addresses are explicitly allowed through your security layer. ​ 🚦 How to Confirm Bot-Protection Is the Cause Before changing any settings, check whether your site uses any of the following: Cloudflare (any plan, including free), Shopify's built-in bot protection, Boostmark, or any other web application firewall (WAF), CDN, or security plugin. If your site uses any of these, follow the fix for your platform below. If you are unsure, contact us via the chat widget and we can check our crawler logs for an Access Denied response from your domain. 🛒 Fix: Shopify Bot Protection 1. Log in to your Shopify Admin panel. 2. Go to Online Store → Preferences and confirm your store is not password-protected for external visitors. If your store is still in development mode with a storefront password enabled, the Search Atlas crawler cannot reach your pages at all — disable the password temporarily or add the crawler IPs to your password-page allowlist. 3. If you use a third-party Shopify anti-bot or fraud-protection app, open that app's settings and add the Search Atlas crawler IP addresses to its IP allowlist. The full crawler IP list is available inside Search Atlas at Left sidebar → OTTO SEO → Installation Guide, under the Crawler IP Whitelist section. 4. Save your changes and wait 10–15 minutes, then re-run the scan as described in the How to Re-Run the Scan section below. ☁️ Fix: Cloudflare Bot Protection Cloudflare is the most frequent cause of OTTO pixel detection failures. Even the free plan's Bot Fight Mode will silently block the Search Atlas crawler and serve it a JavaScript-challenge page instead of your actual HTML, making the pixel invisible to the scanner. 1. Log in to your Cloudflare dashboard and select the domain connected to your OTTO site. 2. Go to Security → Bots and note whether Bot Fight Mode or Super Bot Fight Mode is enabled. 3. Go to Security → WAF → Custom Rules and click Create rule. Configure it as follows: set Field to IP Source Address, set Operator to is in, then paste each Search Atlas crawler IP address as values — the complete list is available at Left sidebar → OTTO SEO → Installation Guide, under Crawler IP Whitelist. Set the Action to Skip → WAF managed rules, and if the option appears, also skip Bot Fight Mode for these IPs. 4. Save and deploy the rule. Cloudflare applies custom WAF rules within seconds. 5. Trigger a new pixel scan as described in the How to Re-Run the Scan section below. Important: Do not disable the Cloudflare proxy (orange cloud icon) for your domain — the custom WAF allowlist rule above is sufficient and keeps your site fully protected. 🔒 Fix: Boostmark and Other WAFs or CDNs If your site uses Boostmark or another WAF, security plugin, or CDN not listed above, the fix is the same: whitelist the Search Atlas crawler IP addresses in that platform's trusted-IP or allowlist section. 1. Log in to your WAF or security tool's admin dashboard. 2. Locate the IP allowlist section, commonly labelled Trusted IPs, IP Allowlist, or Whitelist Rules. 3. Add each IP address from the Search Atlas crawler list. The full list is available at Left sidebar → OTTO SEO → Installation Guide, under Crawler IP Whitelist. 4. Save your changes and wait 5–10 minutes before re-running the scan. ✅ How to Re-Run the OTTO Pixel Scan After whitelisting the crawler, trigger a fresh scan to confirm your pixel is now detected: 1. In Search Atlas, navigate to Left sidebar → OTTO SEO → All Sites. 2. Locate your site in the list and click into it to open the site dashboard. 3. Navigate to Left sidebar → OTTO SEO → Overview and find the pixel status indicator at the top of the page. 4. Click Re-scan or Verify Installation. The scan typically completes within a few minutes. 5. If the status changes to Detected, your site is fully connected and OTTO will begin automating SEO tasks on your next scheduled run. 💡 Other Causes to Rule Out If the pixel is still not detected after whitelisting the crawler IPs, confirm the following additional points: - Script placement in Shopify: The OTTO pixel must be placed inside the tag of your theme.liquid file, directly before the closing tag. Do not place it inside a conditional Liquid block or a deferred-load section, as the scanner may not execute those code paths. - Page cache not refreshed: If you use a caching plugin or Cloudflare's cache, purge the full-page cache after installing the pixel script so the scanner reads the updated live HTML rather than a cached version that predates your changes. - Content Security Policy (CSP) blocking: Some Shopify themes or third-party apps inject a CSP header that prevents external scripts from loading. Open your browser's developer console while loading your homepage and check for any CSP-related errors referencing the OTTO script domain. - Script only loads on some page types: Some themes conditionally inject scripts on certain templates. Confirm the pixel appears in the page source of your homepage, which is the page the scanner checks by default. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Verification Failures on Website Studio

🔍 Overview When you install the OTTO pixel on a Website Studio project, Search Atlas checks that the script is reachable and returns the expected response. If that check fails, OTTO cannot activate SEO automation for your site. This article explains the most common causes of verification failures and the general steps you can take — however, because the exact resolution depends on your specific setup, our support team may need to investigate further. ⚠️ Why Verification Fails Verification fails when Search Atlas cannot reach the OTTO script on your live site. The most frequent reasons are: - Script not saved or published: The pixel was added in the editor but the page was never published, so the script does not exist on the live URL. - Wrong placement: The script was placed in the body or a content block instead of the global section. - Caching: An old cached version of the page is served without the script. - Content Security Policy (CSP) or firewall rules: A CSP header or WAF rule is blocking external scripts from loading. - Incorrect script copied: The pixel code was modified or truncated during copy-paste. ✅ General Troubleshooting Steps 1. Retrieve your OTTO pixel code. Inside Search Atlas, navigate to the OTTO or OTTO SEO section and locate your Website Studio project. Find the option to view or copy your pixel installation script, and copy the full code without editing it. 2. Add the script to your site's global head section. In Website Studio, look for a global custom code or header code area — not an individual page setting. Paste the script so it loads in the on every page. 3. Save and publish your site. Apply your changes and publish so the live URL is updated. 4. Confirm the script is live. Open your site URL in a browser, right-click, choose View Page Source, and search (Ctrl+F or Cmd+F) for the OTTO script. If you see the full pixel code, the script is live. 5. Clear all caches. Clear any platform-level cache inside Website Studio, purge your CDN cache if you use one (Cloudflare, Fastly, etc.), and then hard-refresh your browser (Ctrl+Shift+R or Cmd+Shift+R). 6. Re-run verification. Return to the OTTO or OTTO SEO section in Search Atlas, locate your project, and trigger the verification check. Allow up to two minutes for the check to complete. 🔒 Fixing Blocked Scripts (CSP / Firewall) If the script appears in the page source but verification still fails, a security rule may be preventing it from executing or being reached by Search Atlas. Check your site's Content Security Policy headers and any Web Application Firewall rules to ensure external scripts are not blocked. If you need further assistance, open 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 Issues and Understand Billing Policies

🔍 Overview If OTTO is not detecting your pixel, you may feel stuck — and that frustration is completely understandable. This article walks you through the most common pixel detection fixes, explains how to get faster help, and clearly outlines our refund and cancellation policy so you know exactly where you stand. ⚙️ How to Access OTTO SEO To reach the OTTO SEO dashboard, go to the left sidebar and click OTTO SEO, then open SEO Automation inside it. The URL will end in /seo-automation-v3. From here you can view your OTTO activation status, connected domains, and pixel verification details. 🚀 Troubleshooting OTTO Pixel Not Detected The most common reason OTTO cannot detect your pixel is an installation or propagation issue. Work through the steps below in order before requesting escalation. 1. Confirm the pixel snippet is installed. The OTTO pixel must be placed in the section of every page on your website. If you use a CMS such as WordPress, use a header script plugin or your theme's header file to add the snippet globally. 2. Clear all caches. Purge your site cache, CDN cache (e.g., Cloudflare, Fastly), and any server-side caching layer. A cached version of your pages may serve old code that does not include the pixel. 3. Disable conflicting plugins or scripts. Security plugins, ad blockers loaded server-side, or tag management misconfigurations can strip third-party scripts. Temporarily disable them one by one to isolate the conflict. 4. Verify the snippet has not been modified. Copy the pixel code fresh from the OTTO dashboard and replace any existing snippet. Even a single changed character will cause detection to fail. 5. Allow up to 15 minutes after installation. After pasting the correct snippet and clearing caches, wait up to 15 minutes before clicking Verify Pixel in the OTTO dashboard. Detection is not instantaneous. 6. Test on a live URL. Pixel verification requires a publicly accessible URL. Pages behind a login, password protection, or a staging environment that blocks crawlers will not pass verification. 7. Check for Content Security Policy (CSP) headers. A strict CSP on your server can block the pixel from loading. Review your CSP rules and whitelist the OTTO script domain if necessary. If you have completed every step above and the pixel is still not detected, our support team can review your domain directly and identify the root cause. 💡 How to Get Faster Support We know slow support responses are frustrating, especially when an issue is blocking your workflow. The fastest way to reach a qualified team member is through the live chat widget inside the platform — response times there are significantly quicker than any other channel. To get the most helpful response as quickly as possible, include the following when you open a chat: - Your domain URL - A screenshot of the pixel snippet as it appears in your page source - The exact error message shown in the OTTO dashboard - A list of the troubleshooting 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. 📊 Refund and Cancellation Policy We want every customer to succeed with Search Atlas, and we stand behind our platform. Please read the following policy details carefully. - Refund window: Refund requests must be submitted within 72 hours of the original payment date. Requests made outside this window are outside our standard refund policy and cannot be processed as standard refunds. - Payments outside the 72-hour window: If your refund request falls outside the 72-hour period — including lump-sum or annual payments — we are unable to offer a cash refund under our standard terms. However, we encourage you to contact our team to discuss your situation. In some cases, account credit or an adjusted service arrangement may be available at our discretion. - Service cancellation: You may cancel your subscription at any time. To cancel, navigate to your account billing settings or contact support via the live chat widget. Cancellation stops future billing but does not automatically trigger a refund for prior payments. - Disputed charges: If you believe a charge was made in error, please contact our team through live chat before filing a dispute with your bank or payment provider. We can resolve most billing concerns quickly, and a chargeback may result in immediate account suspension. 🤝 Still Need Help? Our team genuinely wants to help you get OTTO working and make the most of your Search Atlas subscription. Whether your issue is technical or account-related, please reach out before making any final decisions — we may be able to resolve the problem faster than 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.

🔍 OTTO New Page Detection and Analysis Timing

🧭 Overview OTTO continuously monitors your website to identify optimization opportunities. However, new pages you add to your site are not detected instantly. Understanding how OTTO's detection cycle works will help you set the right expectations and avoid confusion when newly published pages don't appear right away. ⏱️ How Often Does OTTO Analyze Your Site? OTTO runs automated analysis cycles on a scheduled basis rather than in real time. This means: - New pages added to your website are picked up during the next scheduled crawl cycle, not immediately after publishing. - The detection window can vary depending on your site size, server response times, and current crawl queue priority. - It is normal for newly published pages to take some time before they appear inside OTTO's page list and receive optimization suggestions. This is expected behavior and does not indicate a problem with your account or website setup. 🚫 Why Manual Recrawl Is Not Available A common question from customers is why there is no button to trigger a manual recrawl after adding new pages. OTTO's crawl process is managed automatically by the platform to ensure consistent, system-wide performance for all users. Exposing a manual recrawl option could overload crawl queues and negatively impact analysis quality across the platform. As a result, manual recrawl is not a supported feature at this time. The best approach is to allow the scheduled cycle to complete. Once OTTO detects your new pages, they will be automatically queued for analysis and optimization suggestions. 📋 What to Do After Adding New Pages 1. Publish your new pages and ensure they are live and accessible (not password-protected or blocked by robots.txt). 2. Wait for the next OTTO crawl cycle to complete. New pages will appear in your OTTO dashboard once they have been detected and processed. 3. Check your OTTO SEO dashboard by navigating to Left sidebar → OTTO SEO → SEO Automation to see if the new pages have been picked up and whether OTTO has generated recommendations for them. 4. If your pages include new content clusters or topics, consider reviewing your Topical Maps (Left sidebar → Content → Topical Maps) to align your new pages with your broader content strategy. ✅ Tips to Help OTTO Detect New Pages Faster - Submit an updated sitemap to Google Search Console. While this does not directly trigger an OTTO crawl, a well-maintained sitemap helps ensure your pages are structured and discoverable. - Internal linking: Link to your new pages from existing, already-indexed pages on your site. This improves crawlability across all tools, including OTTO. - Avoid noindex or robots.txt blocks on pages you want OTTO to analyze. Blocked pages will be skipped during crawl cycles. - Keep page URLs clean and consistent with your existing site structure to prevent detection delays caused by redirect chains. 🔄 After OTTO Detects Your New Pages Once the crawl cycle is complete and your new pages are detected, OTTO will automatically: - Add them to your tracked page list inside the OTTO SEO dashboard. - Generate on-page optimization recommendations and apply eligible automations based on your active OTTO settings. - Flag any issues that may impact those pages' search performance. You do not need to take any manual action to trigger this — it happens automatically as part of OTTO's ongoing analysis. 💬 Still Need Help? If your new pages have not appeared in OTTO after a reasonable amount of time, or if you have added more than 15 pages and are concerned something may not be working as expected, 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.

🔍 Fix OTTO Pixel Installation Validation Delays

🧩 Why Validation Can Take Time After you add the OTTO pixel code to your website, Search Atlas needs to crawl your site before it can confirm the pixel is installed correctly. This crawl does not happen instantly — depending on your site's size and current crawl queue, validation can take anywhere from a few hours up to 48 hours. Seeing a "not installed correctly" status during this window does not necessarily mean something is wrong. 📋 Before You Wait: Confirm the Basics While the crawl completes, take a few minutes to double-check the following common installation mistakes that can cause a genuine validation failure: - Pixel placed in the correct location: The OTTO pixel snippet must be added inside the section of every page on your site, not in the body or footer. - API key is correct: Copy your API key directly from the Search Atlas platform to avoid any typos or extra spaces. - Snippet is complete: Make sure you copied the entire code block — even a missing character will cause validation to fail. - No caching layer blocking changes: If your site uses a caching plugin or a CDN (such as Cloudflare), clear your cache after adding the pixel so the new code is visible to crawlers. - Code not duplicated: Adding the snippet more than once on the same page can interfere with validation. Confirm it appears exactly once per page. ⏱️ What the Normal Timeline Looks Like 1. You add the pixel code to your site and save the changes. 2. Search Atlas queues a crawl of your domain — this typically begins within a few hours. 3. Once the crawl reaches your key pages, the platform validates the pixel presence. 4. Your OTTO dashboard updates to show a green confirmed status automatically — no manual action required. In most cases the status updates within 24 hours. If 48 hours have passed and the status is still showing as not installed, move on to the troubleshooting steps below. 🛠️ Troubleshooting After 48 Hours If more than 48 hours have passed and validation has not completed, work through these steps before contacting support: - Verify the pixel live on your site: Open your website in a browser, right-click the page, and select View Page Source. Search for your OTTO pixel snippet in the source code. If you cannot find it, the code was not saved correctly on your site. - Check for JavaScript errors: Open your browser's developer console (F12) and reload the page. Look for any JavaScript errors that might be preventing the pixel from firing. - Confirm the domain in Search Atlas matches your live URL: Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3) and verify the domain listed for your OTTO project exactly matches the URL where the pixel is installed, including whether it uses www or not. - Re-save or re-publish your site: Some CMS platforms (WordPress, Webflow, Wix, etc.) require you to republish pages after code changes. Confirm your changes are live. - Clear cache again: If you made any changes, clear your site cache and CDN cache one more time. ✅ How to Re-Trigger Validation After correcting any issues, you can prompt a fresh validation check from within the platform: 1. Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Open your OTTO project and locate the pixel installation section. 3. Select the option to re-check or re-validate the pixel. This queues a new crawl of your domain. 4. Allow up to 24 hours for the updated crawl to complete and reflect in your dashboard. 💡 Tips to Speed Up Future Validations - Install the pixel on your highest-traffic or most-linked pages first — crawlers tend to reach these pages sooner. - Submit an updated sitemap to Google Search Console after adding the pixel so crawlers index your changes faster. - Avoid making other structural changes to your site immediately after adding the pixel, as redirects or page moves can delay crawl completion. 🙋 Still Showing as Not Installed? If you have followed all the steps above and validation still fails after 48 hours, our team is ready to help 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 Duplication and Keyword Addition Issues

🔍 Overview Two separate issues can affect your OTTO setup and content optimization workflow: locked keyword fields in the Content Optimization section, and duplicate OTTO pixels on Wix CMS sites. This article explains what causes each issue and how to resolve them. 📊 Why Content Optimization Shows 'No Issues Found' But Won't Let You Add Keywords This is a known display behavior in OTTO's Content Optimization section. When the system reports no issues found for missing keywords, it means OTTO has already analyzed your page and determined that no keyword gaps currently require action based on its latest scan. In this state, the keyword and URL input fields become locked — this is intentional. OTTO disables manual additions when there is no active optimization task queued for that field. Here is what to check: - Page status: Confirm the page has been fully crawled and activated under OTTO. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and verify the page shows an active status. - Re-run an analysis: If you believe keywords are genuinely missing, trigger a fresh page analysis from the OTTO SEO dashboard. Once OTTO detects new gaps, the input fields will unlock automatically. - Target keyword assignment: Ensure the correct target keyword is assigned to the page. A mismatched or missing target keyword can cause OTTO to return a false clean result. - URL field requirements: The URL field only activates when OTTO has flagged a specific internal or external link opportunity. It cannot be edited independently outside of an active recommendation. If the fields remain locked after re-running the analysis and confirming your target keyword is correct, this may indicate a sync delay. Wait 10–15 minutes and refresh the page before attempting again. ⚙️ Understanding OTTO Pixel Duplication on Wix Pixel duplication — where the OTTO tracking pixel appears more than once on a page — is a Wix CMS issue, not a Search Atlas platform error. It occurs because of how Wix handles script injection across its site-wide and page-level settings. Common causes include: - The OTTO pixel was added manually to an individual page and also added through the Wix site-wide tracking or custom code section. - A Wix app or third-party integration has injected a duplicate script independently. - The pixel was embedded in both the Wix header code and a specific page's custom code block. 🚀 How to Remove Duplicate OTTO Pixels in Wix 1. Log in to your Wix account and open the site editor for the affected site. 2. Navigate to Settings → Custom Code (found under the Wix dashboard, not the editor). 3. Review all scripts listed under Head, Body Start, and Body End sections. 4. Identify any duplicate OTTO pixel entries — keep only one instance of the pixel, placed in the Head section with scope set to All Pages. 5. Delete all additional instances of the OTTO pixel code. 6. Save your changes and publish the site. 7. Return to Left sidebar → OTTO SEO → All Sites (SEO Automation) in Search Atlas and confirm the pixel status shows as connected without duplication warnings. Important: Do not add the OTTO pixel through both the Wix Custom Code panel and a page-level embed simultaneously. Choose one method — the site-wide Custom Code panel is recommended for full coverage. 💡 Quick Checklist Before Contacting Support - Target keyword is correctly assigned to the page in OTTO - Page analysis has been re-run within the last 15 minutes - Content Optimization fields are still locked after a fresh scan - Wix Custom Code panel has been checked for duplicate pixel entries - Site has been published in Wix after removing duplicate pixels - OTTO pixel status in Search Atlas shows as connected 🙋 Still Need Help? If you have completed all the steps above and are still experiencing locked fields or pixel duplication, If you need further assistance, open 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 Duplication Platform-Specific Troubleshooting Guide

🧭 Overview If your OTTO pixel appears to be duplicated on your site, the root cause is almost always one of two things: a configuration issue inside Search Atlas, or a conflict introduced by your CMS (such as Wix, WordPress, or a custom-built platform). These require different fixes, so identifying the source first will save you time. This article also covers a separate but related issue: seeing "no issues found" in the Content Optimization section while being unable to add keywords or URLs. Both topics are addressed below. 🔎 Step 1 — Detect Whether Duplication Is Platform-Side or Search Atlas-Side Before making any changes, confirm where the duplicate pixel is coming from. 1. Open your live website in a browser and right-click anywhere on the page, then select View Page Source. 2. Use Ctrl+F (or Cmd+F on Mac) to search for your OTTO pixel script ID or the keyword otto. 3. Count how many times the pixel snippet appears in the source code. 4. If the snippet appears once, duplication is not confirmed — revisit your Search Atlas dashboard settings. 5. If the snippet appears more than once, duplication is confirmed. Proceed to Step 2 to identify the source. Next, open OTTO SEO → SEO Automation (All Sites) in the left sidebar of Search Atlas. Locate your connected property and verify that the OTTO pixel is installed only once within the platform settings. If Search Atlas shows a single installation but your page source shows two or more instances, the duplication originates from your CMS — not from Search Atlas. 🌐 Step 2 — Wix CMS: Find and Remove a Duplicate Pixel Wix has two separate areas where tracking scripts can be added, which is the most common cause of pixel duplication on Wix sites. 1. Log in to your Wix dashboard and go to Settings → Custom Code (under the Advanced section). 2. Review all code snippets listed. Look for any snippet containing your OTTO pixel script. Note whether the same snippet appears more than once, or appears in both the Head and Body sections. 3. If you find a duplicate, click the three-dot menu next to the duplicate entry and select Delete. Keep only one instance, placed in the Head section, set to load on All Pages. 4. Additionally, check Settings → Tracking & Analytics. If the OTTO pixel was also added here separately, remove it from this location and keep only the Custom Code version. 5. Republish your Wix site and re-check your page source to confirm only one instance of the pixel remains. If you cannot locate a duplicate in either area but duplication is still confirmed in your page source, contact Wix Support directly — some Wix apps or third-party integrations can inject scripts independently. ⚙️ Step 3 — WordPress: Find and Remove a Duplicate Pixel 1. Log in to your WordPress admin panel and go to Appearance → Theme File Editor (or your child theme's header.php). 2. Search for the OTTO pixel snippet. If it exists here and in a plugin (such as Insert Headers and Footers or a tag manager), one copy must be removed. 3. Check all active plugins that manage header scripts. Disable or remove the OTTO snippet from any duplicate source, leaving only one active installation. 4. Clear your WordPress cache and any CDN cache, then recheck your page source. 🛠️ Step 4 — Custom CMS or Other Platforms If you are using a custom-built CMS, a headless setup, or any platform not listed above, check the following locations where your developers may have added the pixel script: - A global layout or base template file (often named layout.html, base.html, or _document.js) - A tag management system such as Google Tag Manager — check for duplicate tags firing the same pixel - A deployment pipeline or CI/CD script that injects scripts at build time If the duplication is inside a tag manager, open the tag manager account, search for OTTO-related tags, and ensure only one tag is configured and firing. Engage your development team or CMS vendor for build-level injection issues. 🗂️ Decision Tree — Search Atlas Support vs. CMS Provider Use the following criteria to decide who to contact: - Contact your CMS provider or developer if: the OTTO pixel appears more than once in your page source AND Search Atlas shows only a single pixel installation for your property. - Contact Search Atlas support if: the OTTO pixel appears more than once in your page source AND Search Atlas shows multiple pixel entries for the same property, OR if you cannot connect or verify your pixel from within the OTTO SEO dashboard. - Contact Search Atlas support if: the Content Optimization section shows "no issues found" but you are also unable to add keywords or target URLs — this indicates a platform-side data sync issue that our team needs to investigate. 📝 Content Optimization: "No Issues Found" and Cannot Add Keywords If your Content Optimization panel shows "no issues found" for missing keywords but the input fields for adding keywords or URLs are locked or unresponsive, this is not expected behavior. It is separate from the pixel duplication issue and is typically caused by a sync delay or a session-level data loading error. Try the following: 1. Hard-refresh the page using Ctrl+Shift+R (or Cmd+Shift+R on Mac) to clear any cached state. 2. Log out of Search Atlas, clear your browser cookies, and log back in. 3. Navigate back to OTTO SEO → SEO Automation (All Sites) in the left sidebar, reselect your target URL, and attempt to open Content Optimization again. 4. If the fields remain locked after these steps, the issue requires investigation by our support team. 💬 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 OTTO Pixel Check vs Scanner Mismatch

🧩 Why the Check and Scanner Can Disagree The installation check confirms that a pixel string exists somewhere on your page. The diagnostic scanner goes further — it verifies that the pixel is placed in the correct location and will fire reliably on every page load. When you use a custom CMS or GoHighLevel (GHL), certain platform-specific behaviours can satisfy the basic check while still failing the deeper scan. The three most common root causes are: - Wrong placement location: The pixel is added to the body or footer instead of the <head> section. - Widget or embed block used instead of raw code: Some CMS editors and GHL page builders wrap injected code inside a widget container, which delays or blocks the pixel from firing correctly. - GHL-specific head injection misconfiguration: GHL has a dedicated Head Tracking Code field in funnel and site settings. Pasting the pixel anywhere else — such as a custom HTML element on the canvas — causes the scanner to flag it as incorrectly installed. 🗺️ Where to Find Your OTTO Pixel Before troubleshooting, retrieve your unique pixel code from Search Atlas: 1. Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select the project you are working on. 3. Open the OTTO panel and navigate to Pixel Settings. 4. Copy the full pixel snippet shown there. Do not modify it. 🛠️ Step-by-Step Resolution — Custom CMS 1. Access your theme or template editor. Every custom CMS exposes a way to inject code into the global <head> tag — look for settings labelled Head Code, Custom Scripts, or Site Header. 2. Remove any existing OTTO pixel placements from page-level editors, footer sections, or widget blocks before proceeding. 3. Paste the pixel snippet directly into the global head injection field. It must sit as raw code — not inside a CMS text block, HTML widget, or shortcode wrapper. 4. Save and publish your changes so they go live across all pages. 5. Wait 2–3 minutes, then return to OTTO SEO V3 → OTTO → Pixel Settings and run the diagnostic scanner again. 🟡 Step-by-Step Resolution — GoHighLevel (GHL) 1. Open your GHL account and navigate to the site or funnel where OTTO should be active. 2. For a Funnel: go to the funnel, click Settings (top-right gear icon), and locate the Head Tracking Code field. 3. For a Website: go to Sites → Websites, open the site, click Settings, and find the Head Tracking Code field. 4. Delete any OTTO pixel code placed elsewhere — including custom HTML elements on the page canvas or footer sections. 5. Paste the full OTTO pixel snippet into the Head Tracking Code field only. This is the only GHL location the diagnostic scanner recognises as a valid installation. 6. Save the settings and re-publish or re-deploy the funnel or website. 7. Return to Search Atlas → OTTO SEO V3 → OTTO → Pixel Settings and run the diagnostic scanner to confirm the result is now passing. ✅ Quick Verification Checklist - Pixel is placed in the global head section, not page-level or footer. - No duplicate pixel instances exist across widgets, embeds, or canvas elements. - The pixel code was pasted as raw HTML — not wrapped in a CMS block or builder element. - For GHL: the pixel lives exclusively in the Head Tracking Code field in site or funnel settings. - Changes were saved and published before re-running the scanner. ⚠️ Common Mistakes to Avoid - Using a custom HTML element on the GHL canvas: This placement passes the basic check but always fails the diagnostic scanner. - Installing the pixel on a single page only: OTTO requires the pixel to be present site-wide. Always use global head injection. - Editing the pixel code: Any alteration to the snippet — even adding a space — can cause it to stop firing correctly. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO New Page Detection and Analysis Schedule

🧭 Overview If you have recently added new pages to your website and OTTO has not detected them yet, this is expected behaviour. OTTO operates on a fixed 7-day analysis cycle that runs independently of manual recrawls. Understanding the difference between a crawl and an OTTO analysis will help you set the right expectations and plan your SEO workflow accordingly. 🔍 The Difference Between Crawling and OTTO Analysis These are two separate processes, and it is important not to confuse them: - Crawling collects raw data from your website — page URLs, HTML content, metadata, and technical signals. A manual recrawl updates this dataset. - OTTO Analysis processes that crawl data to generate SEO recommendations, detect new pages, identify issues, and surface optimisation opportunities. This step runs on a scheduled cycle — not on demand. Running a manual recrawl refreshes the underlying data but does not trigger OTTO to re-analyse your site. OTTO will only process the latest crawl data when its next scheduled analysis runs. 📅 How the 7-Day OTTO Analysis Cycle Works OTTO analysis runs automatically on a 7-day schedule from the date your site was first connected. Here is what that means in practice: 1. Your site is connected to OTTO and an initial analysis runs. 2. OTTO sets a recurring 7-day cycle from that date. 3. Any new pages added to your site — regardless of when you added them or whether you ran a manual recrawl — will only be detected and analysed at the next scheduled cycle. 4. Once the cycle runs, new pages appear in OTTO and are eligible for recommendations and task generation. There is currently no way to force an immediate OTTO analysis outside of this schedule. This design ensures consistent, reliable processing across all connected sites. ⚙️ What Manual Recrawl Does and Does Not Do You can trigger a manual recrawl from the OTTO SEO section in the left sidebar, then open SEO Automation inside it. Here is a clear breakdown of its scope: - Does: Update the raw crawl data for your site with the latest page URLs, content, and technical signals. - Does: Ensure that when the next OTTO analysis cycle runs, it works from the most up-to-date crawl snapshot. - Does not: Trigger OTTO to immediately analyse new pages. - Does not: Accelerate or reset the 7-day analysis schedule. - Does not: Surface new pages in OTTO recommendations before the next cycle completes. Running a manual recrawl after adding new pages is still a good practice — it means the fresh pages are ready and waiting in the crawl data so OTTO can process them as soon as the next analysis cycle begins. ✅ Recommended Steps After Adding New Pages 1. Go to OTTO SEO in the left sidebar and open SEO Automation inside it (or navigate to /seo-automation-v3). 2. Trigger a manual recrawl to capture your new pages in the crawl dataset. 3. Note the date of your last OTTO analysis — this is shown in the OTTO dashboard. Your new pages will appear after the next 7-day cycle completes from that date. 4. Once the analysis cycle runs, return to the OTTO dashboard to review recommendations for your new pages. ⏱️ How Long Should I Expect to Wait? The maximum wait time is 7 days from your last OTTO analysis. If your last analysis ran 4 days ago, new pages should appear within the next 3 days. If you just had an analysis run today, you may wait a full 7 days before new pages are detected. You do not need to take any additional action during this window. OTTO will automatically pick up pages that are present in the crawl data when the cycle runs. ❓ Frequently Asked Questions - Can I request an immediate OTTO analysis? No — OTTO analysis runs on a fixed 7-day schedule and cannot be triggered manually or on demand at this time. - Will a manual recrawl hurt anything? No. Running a manual recrawl is safe and ensures your crawl data is current before the next analysis cycle. - What if my pages still do not appear after 7 days? First confirm the pages are publicly accessible and not blocked by your robots.txt file. Then run a manual recrawl and wait for the next cycle. If the issue persists, contact our support team using the chat widget. - Does this apply to all site changes, not just new pages? Yes. Any site change — updated content, removed pages, new metadata — is reflected in OTTO only after the next 7-day analysis cycle processes the updated crawl data. 💬 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 OTTO Pixel Not Installed After Previous Setup

🧩 Why This Happens The OTTO Pixel is a small tracking script that Search Atlas places on your website to enable SEO automation features. Once installed, the platform periodically checks that the script is still present and accessible on your site. If you recently made changes to your WordPress site — such as updating a plugin, switching themes, clearing caches, or migrating hosting — WordPress may have served a cached version of your pages that no longer includes the OTTO Pixel script. From Search Atlas's perspective, the pixel appears missing even though it was installed correctly before. The most common fix is a full WordPress cache purge, which forces your site to rebuild its pages and serve the latest version — including the OTTO Pixel code. ⚠️ Before You Start - Confirm the OTTO Pixel status in Search Atlas by going to OTTO SEO in the left sidebar, then opening SEO Automation (URL: /seo-automation-v3) and checking the pixel installation indicator. - Do not reinstall the pixel script manually before clearing the cache — this can create duplicate tags. - If you use a CDN (such as Cloudflare, BunnyCDN, or Amazon CloudFront), you will need to purge that cache separately after clearing WordPress. 🖥️ Option 1: Managed WordPress Hosting If your site is hosted on a managed WordPress platform such as WP Engine, Kinsta, Flywheel, or Pressable, follow these steps: 1. Log in to your hosting control panel or dashboard. 2. Locate the Cache or Performance section — the exact label varies by host. 3. Select Clear All Cache or Purge Cache for your site. 4. Wait 60–90 seconds for the purge to complete. 5. Return to Search Atlas, go to OTTO SEO in the left sidebar and open SEO Automation, and check whether the OTTO Pixel status has updated to installed. Most managed hosts also provide a cache-clearing button directly inside the WordPress admin toolbar at the top of the screen. Look for a label such as Clear Cache or your host's name next to a cache icon. 🔧 Option 2: Self-Hosted WordPress with a Cache Plugin If you manage your own WordPress hosting and use a caching plugin, the steps depend on which plugin you have installed. WP Super Cache 1. In your WordPress admin, go to Settings → WP Super Cache. 2. Click Delete Cache on the Easy tab. W3 Total Cache 1. In your WordPress admin, click Performance in the left menu. 2. Select Purge All Caches from the dropdown. LiteSpeed Cache 1. In your WordPress admin, click LiteSpeed Cache in the left menu. 2. Select Manage, then click Purge All. WP Rocket 1. In your WordPress admin toolbar, click WP Rocket. 2. Select Clear cache. After purging, wait 60–90 seconds, then return to Search Atlas, go to OTTO SEO in the left sidebar and open SEO Automation, to confirm the pixel status has updated. ☁️ Option 3: Purge Your CDN Cache If your site runs behind a CDN, cached copies of your pages at the CDN edge may still be served without the OTTO Pixel. Purge your CDN cache after clearing WordPress: - Cloudflare: Log in to the Cloudflare dashboard → select your domain → go to Caching → Configuration → click Purge Everything. - Other CDNs: Refer to your provider's documentation for a full cache purge or contact your CDN provider's support. Once the CDN purge is complete, check the OTTO Pixel status again in Search Atlas. ✅ Confirming the Fix 1. In Search Atlas, navigate to OTTO SEO in the left sidebar and open SEO Automation. 2. Review the OTTO Pixel installation status indicator. 3. If the status now shows as installed, no further action is needed. 4. If the status still shows as not installed after completing all cache purges, proceed to the next section. 👩‍💻 When to Involve a Developer You may need developer assistance if any of the following apply: - You cleared all caches and the pixel still shows as not installed after 5–10 minutes. - Your site uses a custom or headless WordPress setup where standard cache plugins do not apply. - Your hosting environment uses server-level caching (such as Nginx FastCGI cache or Varnish) that cannot be cleared through the WordPress admin. - You are unsure whether your site has a CDN or additional caching layers in place. In these cases, ask your developer to verify that the OTTO Pixel script tag is present in the rendered HTML source of your homepage and that no caching layer is stripping script tags from page output. 💬 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 OTTO Pixel Canonicalization Issues on Paginated Pages

🔍 What Is Happening? When OTTO SEO is active on your site, it uses a pixel installation method to detect and optimize your pages. During this process, OTTO appends a URL parameter — is_otto_page_fetch=1 — to page requests so it can identify which pages it is fetching for analysis. On paginated pages (for example, /blog/page/2/, /blog/page/3/), this parameter can be included in the URL that search engines see. Because canonical tags are sometimes generated dynamically based on the current URL, the parameter may cause the canonical tag to point to the parameterized URL instead of the clean, intended URL. This changes the canonicalization and can confuse search engines about which URL is the authoritative version of the page. ⚠️ Why This Is a Problem Canonical tags tell search engines which URL should be treated as the primary version of a page. If the canonical tag on /blog/page/2/ reads /blog/page/2/?is_otto_page_fetch=1 instead of the clean URL, it can lead to: - Incorrect pages being indexed or de-indexed - Duplicate content signals sent to search engines - Pagination sequences being misunderstood by crawlers - Loss of link equity across paginated content 🛠️ How to Fix the Issue Follow the steps below to prevent the is_otto_page_fetch=1 parameter from affecting your canonical tags. 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Locate your connected website and open the OTTO SEO settings for that property. 3. Check whether OTTO is set to use the pixel (JavaScript) installation method. This is the method most likely to append the fetch parameter to your URLs. 4. Switch to the WordPress plugin installation method if your site runs on WordPress. The plugin method does not rely on URL parameters to identify page fetches and is the recommended approach for avoiding this issue. 5. If you are not on WordPress or cannot switch methods, proceed to the steps below to exclude the parameter at the server or CMS level. ⚙️ Excluding the Parameter from Canonical URLs If switching installation methods is not possible, you can strip the parameter from canonical tag generation using one of the following approaches: - Yoast SEO / Rank Math / SEOPress: These plugins allow you to define URL parameters that should be ignored when generating canonical tags. Add is_otto_page_fetch to the list of ignored parameters in your SEO plugin settings. - Google Search Console parameter handling: In Google Search Console, navigate to Legacy Tools → URL Parameters and configure is_otto_page_fetch as a parameter that does not change page content. This tells Googlebot to ignore the parameter during crawling. - Server-level rewrite rules: If you have access to your .htaccess file or Nginx configuration, you can add a redirect rule that strips the is_otto_page_fetch parameter from incoming requests before the page is rendered, ensuring the canonical tag is always generated from the clean URL. ✅ How to Verify the Fix After applying your chosen fix, confirm it is working correctly before moving on: 1. Visit one of your paginated blog pages directly in a browser and append ?is_otto_page_fetch=1 to the URL manually (for example, /blog/page/2/?is_otto_page_fetch=1). 2. View the page source and search for the canonical tag (use Ctrl+F or Cmd+F and search for rel="canonical"). 3. Confirm the canonical tag points to the clean URL — /blog/page/2/ — without the parameter appended. 4. Repeat this check across several paginated pages to ensure consistency. 5. Use the URL Inspection tool in Google Search Console to re-fetch a paginated page and confirm the rendered canonical is correct. 💡 Best Practices Going Forward - Prefer the WordPress plugin method for OTTO installation whenever possible — it is more reliable and avoids URL parameter side effects. - Regularly audit your canonical tags on paginated pages using a crawler such as Search Atlas's own Site Auditor to catch canonicalization drift early. - Keep your SEO plugin and OTTO pixel updated to benefit from the latest fixes and improvements. 🙋 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 OTTO Pixel Installation and Engagement Issues

🔍 Overview OTTO is Search Atlas's AI-powered SEO automation assistant. Before OTTO can begin optimizing your site, it must be both installed (pixel detected) and engaged (actively authorized to make changes). These are two separate states — a correctly installed pixel does not automatically mean OTTO is engaged. This article walks you through the most common reasons OTTO shows as not engaged and how to resolve them. ⚙️ Understanding the Two OTTO States It is important to distinguish between these two statuses: - Pixel Installed: Search Atlas has detected the OTTO tracking pixel on your website. This confirms the code is present and firing correctly. - Engaged: OTTO has been granted permission to actively apply SEO optimizations to your site. This step must be completed separately after installation. A site can show a successfully installed pixel while still displaying not engaged if the engagement step was never completed or was interrupted. 🚀 How to Engage OTTO Follow these steps to activate OTTO engagement on your site: 1. In the left sidebar, navigate to OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 2. Select the website you want to engage OTTO on. 3. Locate the OTTO Engagement section on the dashboard. 4. Click the Engage OTTO button. If the button is greyed out or unavailable, proceed to the troubleshooting steps below. 5. Wait up to 60 seconds for the status to update. Refresh the page if the status does not change automatically. 🛠️ Troubleshooting: OTTO Still Shows as Not Engaged If the pixel is confirmed as installed but OTTO still shows not engaged, work through the following checks: - Check your website connection: Confirm the website is correctly connected to your Search Atlas account. Go to OTTO SEO → SEO Automation and verify the domain is listed and verified. - Confirm pixel placement: The OTTO pixel must be placed in the section of every page on your site, not just the homepage. If you are using a tag manager, ensure the tag is firing on all pages and is not blocked by consent settings. - Look for caching issues: If your site uses a caching plugin or CDN (such as Cloudflare, WP Rocket, or Varnish), clear all caches after installing the pixel. Cached pages may serve an outdated version of your site without the pixel. - Disable conflicting plugins temporarily: Security plugins, firewall plugins, or ad blockers on your browser can sometimes interfere with pixel verification. Try verifying in a different browser or incognito window with extensions disabled. - Check for JavaScript errors: Open your browser's developer tools (F12), go to the Console tab, and reload your site. Look for any JavaScript errors that might prevent the pixel from executing correctly. - Wait for propagation: After making changes, allow up to 5 minutes before retrying engagement. Pixel verification is not always instantaneous. - Re-attempt engagement: Return to OTTO SEO → SEO Automation, select your site, and click Engage OTTO again after completing the checks above. 💡 Common Scenarios and Quick Fixes - Pixel installed via Google Tag Manager: Make sure the GTM container is published after adding the OTTO tag. An unpublished container will not fire the pixel on your live site. - WordPress sites: If you installed the pixel using a header plugin (e.g., Insert Headers and Footers), confirm the plugin is active and the code was saved correctly. Deactivating the plugin will remove the pixel. - Shopify or other hosted platforms: Ensure the pixel code was added to the correct theme file and that the theme is currently active. Switching themes will remove customizations. - Engagement button not clickable: This may indicate a permission issue. Confirm you are logged in as an account owner or have admin-level permissions for the workspace. ✅ Confirming Successful Engagement Once OTTO is successfully engaged, the status indicator in OTTO SEO → SEO Automation will update to show Engaged. You will also see OTTO's recommendations and automation options become available for your site. If the status remains not engaged after completing all steps above, further investigation by the support team will be needed. 💬 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 Installation Errors and Duplicates

🧭 Overview When installing OTTO on your website, you may encounter two common errors: OTTO pixel not detected or a warning about multiple/duplicate installations. These errors prevent OTTO from activating SEO automation on your site. This guide walks you through diagnosing the root cause and resolving both issues step by step. 🔍 Understanding the Two Error Types Before troubleshooting, identify which error you are seeing: - OTTO pixel not detected: The Search Atlas scanner cannot find the OTTO JavaScript snippet on your website. This usually means the snippet was not saved correctly, is blocked, or was placed in a location that does not load on every page. - Multiple installations / duplicate deployment detected: The scanner found more than one instance of the OTTO pixel on the same page. This can happen when the snippet is added via two different methods simultaneously — for example, manually in a theme header AND through a plugin or tag manager at the same time. 🛠️ Step 1 — Retrieve Your Unique OTTO Pixel Snippet 1. Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select your website property (e.g., brandalltarps.com). 3. Click Connect OTTO or open your OTTO settings and locate the Install Pixel section. 4. Copy your unique pixel snippet exactly as shown. Do not modify any characters. Your snippet is unique to your account and domain. Using a snippet from a different property will cause a detection failure. 🚫 Step 2 — Remove All Existing OTTO Installations Before re-installing, you must remove every existing instance of the pixel to eliminate duplicates. Check each of the following locations: - Theme header/footer files: In your CMS (WordPress, Shopify, etc.), open your theme editor and search for any code containing otto or your Search Atlas pixel ID. Delete it. - Header/footer plugins: If you used a plugin such as Insert Headers and Footers, WPCode, or a similar tool, open that plugin and delete the OTTO snippet from every field. - Google Tag Manager: Log in to GTM, open your container, and check all tags for any OTTO or Search Atlas pixel tag. Pause or delete any you find, then publish the container to apply the change. - Other tag managers or site scripts: Check Cloudflare Workers, Segment, or any custom scripts in your hosting control panel. After removing all instances, clear your website cache entirely (hosting cache, CDN cache, and any caching plugins) before proceeding. ✅ Step 3 — Reinstall the OTTO Pixel Correctly Choose one installation method only and do not repeat the snippet in a second location. - Recommended — WordPress plugin or CMS integration: Use the Search Atlas OTTO plugin or the built-in integration if your CMS supports it. This is the most reliable method and avoids manual code errors. - Manual theme installation: Paste the snippet once inside the <head> tag of your theme's global header file (header.php in WordPress). Confirm it appears on every page by checking your homepage, a blog post, and a product or category page. - Google Tag Manager: Create a new Custom HTML tag, paste the snippet, set the trigger to All Pages, and publish the container. Do not also add the snippet to your theme — use GTM exclusively. 🔎 Step 4 — Trigger and Interpret the Scanner Validation 1. Return to OTTO SEO in the left sidebar, open SEO Automation in Search Atlas, and open your OTTO settings. 2. Click Verify Installation or Re-scan to trigger a fresh pixel check. 3. Wait up to 2–3 minutes for the scanner to complete. Interpret the scanner result as follows: - Pixel detected — Active: Installation is successful. OTTO will begin processing your site. - Pixel not detected: The snippet is missing or blocked. Re-check Step 2 and Step 3, confirm your cache is cleared, and verify the snippet is in the <head> section (not the footer only). - Multiple instances detected: More than one copy of the snippet is loading. Repeat Step 2 to find and remove the extra instance, clear cache, then re-scan. ⚠️ Common Causes of Pixel Detection Failure - Caching: A cached version of your site may serve old code. Always purge all caches after any change. - Conditional loading: Some themes or plugins load header scripts only on certain page types. Confirm the snippet fires on all page types. - Security or firewall plugins: Tools like Wordfence or Sucuri may block external scripts. Add the OTTO script domain to your allowlist. - Script deferral: Avoid wrapping the OTTO snippet in defer or async attributes that may prevent proper detection by the scanner. - Subdomain vs. root domain mismatch: Ensure the domain in your OTTO settings exactly matches the domain where the pixel is installed, including or excluding www. 💬 Still Seeing an Error? If you have followed every step and the error persists, if you need further assistance, open 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 Installation and Landing Page Publishing

🔍 Overview If your OTTO pixel isn't tracking correctly, your permalink structure is causing errors, or your landing pages aren't publishing as expected, this guide walks you through the most common causes and fixes. Follow each section in order to resolve the issue quickly. ⚙️ Step 1 – Verify Your OTTO Pixel Installation The OTTO pixel must be placed correctly on your website for OTTO SEO to track and apply optimizations. An incorrect installation is the most common reason the pixel appears inactive. 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Locate your connected website and open the OTTO Settings panel. 3. Copy the pixel code snippet provided. Make sure you copy the complete snippet — partial copies are a frequent source of errors. 4. Paste the snippet into the section of every page on your website. If you use a tag manager (such as Google Tag Manager), add it as a new Custom HTML tag set to fire on All Pages. 5. Save your changes and allow up to 15 minutes for the pixel to register as active in Search Atlas. Tip: Use a browser extension such as Tag Assistant or PixelMe to confirm the pixel fires on page load before returning to Search Atlas to verify the status. 🔗 Step 2 – Resolve Permalink Issues Permalink mismatches can prevent OTTO from correctly mapping optimizations to the right pages. This typically happens after a site migration, a WordPress permalink settings change, or a URL restructure. 1. Confirm that the URL structure in Search Atlas matches the live URL structure on your website exactly — including trailing slashes, www vs. non-www, and http vs. https. 2. If you use WordPress, go to Settings → Permalinks in your WordPress dashboard and click Save Changes without making any edits. This flushes the rewrite rules and often resolves broken permalink mapping. 3. Return to OTTO SEO V3 in Search Atlas and trigger a Re-crawl or Resync of your site so OTTO picks up the updated URL structure. 4. Check that no redirect chains exist on the affected URLs. A page that redirects (301 or 302) to another URL will break the direct OTTO–page association. Important: If you recently changed your domain or moved to HTTPS, update your site URL inside Search Atlas settings before re-syncing. 🚀 Step 3 – Troubleshoot Landing Page Publishing Failures If a landing page you configured through OTTO did not publish, one of the following issues is usually responsible. - Pixel not active: OTTO cannot publish pages to a site where the pixel is unverified. Complete Steps 1 and 2 above first. - Insufficient site permissions: The integration connecting Search Atlas to your CMS must have editor or administrator level permissions. Check your CMS user roles and update if needed. - Conflicting plugins or firewall rules: Security plugins (e.g., Wordfence) and WAFs can block external publishing requests. Temporarily disable them to test, then whitelist Search Atlas IP ranges if publishing succeeds. - Permalink conflict on the target slug: If a page or post already exists at the target URL slug, the new landing page may fail silently. Choose a unique slug or delete the conflicting page first. - Unsaved page configuration: Ensure you clicked Publish (not just Save Draft) inside the OTTO landing page builder before expecting the page to go live. ✅ Step 4 – Confirm Everything Is Working 1. Open your website in an incognito browser window and navigate to the published landing page URL. 2. Verify the page loads correctly and displays the content you configured. 3. Return to OTTO SEO V3 in Search Atlas and confirm the landing page status shows as Published and the pixel status shows as Active. 4. If OTTO optimizations were pending, check that they now show a Deployed status rather than Pending or Failed. 💡 Common Mistakes to Avoid - Installing the pixel inside the tag instead of the tag. - Only adding the pixel to the homepage instead of all pages site-wide. - Forgetting to re-save WordPress permalink settings after a URL structure change. - Using a CMS integration account with read-only permissions. 🆘 Still Need Help? If you have followed all the steps above and the pixel, permalink, or publishing issue persists, our team can investigate 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.

🔌 Fix OTTO Pixel Intermittent Disconnection Issues

🔍 Understanding the Problem If your sites appear disconnected in OTTO SEO every time you log in — even though the OTTO Pixel is already installed — you are not alone. This is a known issue that usually stems from a small number of common causes: the pixel code being partially removed by a plugin or theme update, caching layers serving stale page versions without the pixel, or the pixel being placed in a location that causes it to load inconsistently. Working through the steps below will identify and fix the root cause so you do not need to reconnect your sites repeatedly. ✅ Step 1 — Verify the Pixel Is Still Present on Your Site Plugin updates, theme changes, and site migrations can silently remove the OTTO Pixel code. Before anything else, confirm the pixel is still live on your website. 1. Open your website in a browser and press Ctrl + U (Windows) or Cmd + Option + U (Mac) to view the page source. 2. Press Ctrl + F (or Cmd + F) and search for ottoseo or the pixel script snippet you originally installed. 3. If the code is missing, navigate to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3), open the affected site, and reinstall the pixel following the on-screen instructions. 4. Repeat this check for every site showing as disconnected. 🗂️ Step 2 — Clear All Caching Layers Caching plugins, server-side caches, and CDN caches can serve an older version of your page that does not include the pixel, causing OTTO SEO to register the site as disconnected. Clear every cache layer in the following order: 1. WordPress caching plugin — Go to your cache plugin dashboard (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache) and click Clear All Cache. 2. Hosting server cache — Log in to your hosting control panel and flush the server-side or object cache if available. 3. CDN cache — If you use Cloudflare, BunnyCDN, or a similar service, log in and purge the cache for the affected domain. 4. After clearing all caches, reload your website and re-verify the pixel is present using the source-view method in Step 1. 📍 Step 3 — Check Pixel Placement The OTTO Pixel must load on every page, consistently. Placement in the wrong location can cause intermittent detection failures. - The pixel should be placed inside the section of your site's HTML, before the closing tag. - If you are using a tag manager such as Google Tag Manager, ensure the tag is set to fire on All Pages and is not blocked by any exception rules. - Avoid placing the pixel inside page builders, widgets, or footer areas that only render on certain templates — these locations cause inconsistent loading. - If your theme or plugin provides a dedicated Header Scripts field, use that field to paste the pixel code directly. 🔄 Step 4 — Reconnect and Monitor Your Sites Once you have confirmed the pixel is present, caches are cleared, and placement is correct, reconnect your sites in OTTO SEO and monitor them over the next 24–48 hours. 1. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Select the disconnected site and follow the prompts to reconnect it. 3. Log out of Search Atlas and log back in after a few hours to confirm the connection status remains active. 4. If a site disconnects again after this process, note the exact time and any changes made to the site (updates, new plugins, cache activity) — this information will help our support team diagnose the issue faster. 🛡️ Step 5 — Prevent Future Disconnections Taking a few preventative measures will significantly reduce the chance of this happening again. - Test after every site update: Any time you update your theme, plugins, or CMS, re-verify the pixel is still in place using the source-view check. - Exclude the pixel script from minification: Some optimisation plugins minify or combine scripts in ways that break the pixel. Add the pixel script URL to your plugin's exclusion list. - Disable aggressive script blocking: Security plugins with JavaScript blocking features can interfere with the pixel. Whitelist the OTTO Pixel script domain in your security plugin settings. - Use a child theme: If your pixel is added directly to a parent theme's header file, a theme update will overwrite it. Always add custom code through a child theme or a dedicated header scripts plugin. 💬 Still Experiencing Disconnections? If you have completed all of the steps above and your sites continue to disconnect intermittently, our team can investigate 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.

🛠️ Fix OTTO Pixel Invalid HTML Header Injection

🔍 What Is the OTTO Pixel? The OTTO Pixel is a small tracking script that Search Atlas can inject into your website's section. It helps OTTO monitor on-page changes and publishing activity in real time. However, some website configurations — particularly certain WordPress themes, page builders, or security plugins — may flag this injected script as invalid HTML, causing warnings in tools like Google Search Console, W3C Validator, or your hosting environment. The good news: disabling the OTTO Pixel does not remove your ability to publish optimizations, deploy schema markup, or use any other OTTO automation feature. Publishing functionality remains fully intact. ⚙️ Two Ways to Install the OTTO Pixel There are two methods for adding the OTTO Pixel to your site. If you are experiencing invalid HTML warnings, switching from the plugin method to the manual script method — or disabling it entirely — is the recommended fix. - Plugin Installation: OTTO installs a WordPress plugin that automatically injects the pixel script into your site's header. This is the default method and the most common source of invalid HTML conflicts. - Manual Script Installation: You copy the pixel script and paste it directly into your theme's header template or a dedicated header script manager. This gives you full control over placement and formatting, reducing the risk of HTML conflicts. 🚀 How to Disable the OTTO Pixel Follow these steps to turn off the OTTO Pixel injection and stop the invalid HTML from appearing in your headers: 1. Log in to your Search Atlas account and navigate to OTTO SEO in the left sidebar, then open All Sites (SEO Automation) (or go to /seo-automation-v3). 2. Select the website project that is experiencing the invalid HTML issue. 3. Open the OTTO Settings for that project. 4. Locate the OTTO Pixel toggle or installation section. 5. Switch the toggle to Off or select Disable Pixel to stop the script from being injected into your site's header. 6. Save your settings. Once disabled, revisit your site and re-run your HTML validation tool to confirm the invalid markup warning has been resolved. Your OTTO publishing features — including content deployment, schema, and on-page optimizations — will continue to work normally. 💡 When to Use Manual Script Installation Instead If you want to keep pixel tracking active but avoid plugin-related HTML conflicts, the manual script method is the better choice. Use this approach when: - Your security plugin or firewall is blocking the auto-injected script. - Your theme or page builder is restructuring the header and breaking the plugin's output. - You need precise control over where the script appears in the tag. To switch to manual installation, navigate back to the OTTO Pixel settings section, select Manual Installation, and copy the provided script snippet. Paste it into your theme's header.php file just before the closing tag, or use a trusted header script manager plugin. ✅ What Stays Active After Disabling the Pixel Disabling the OTTO Pixel only removes the tracking script from your header. The following features remain fully operational: - OTTO content publishing and on-page optimization deployments - Schema markup generation and injection - Internal linking automation - Meta title and description updates - All reporting and analytics inside Search Atlas 🆘 Still Seeing Invalid HTML? If you have disabled the pixel and are still experiencing invalid HTML warnings, the issue may be caused by another plugin, theme component, or a cached version of your page. Try clearing your site cache and any CDN cache layers after making the change, then re-validate. If you need further assistance, open 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 Disabled After Otto SEO Install

🧩 Understanding the Issue After installing the Otto SEO plugin on your WordPress site, you may notice that Otto Pixel appears as disabled in your Search Atlas dashboard — even though the Otto SEO plugin shows as Engaged. These are two separate components that serve different purposes, and each must be activated independently. Otto SEO handles on-page optimizations, schema, and content automation. Otto Pixel is a lightweight tracking script that collects performance and behavioral data from your site. Installing Otto SEO does not automatically activate Otto Pixel — you must enable it separately. 🔍 Why This Happens - Otto SEO and Otto Pixel are distinct features with independent activation states. - Installing or connecting the Otto SEO plugin does not trigger Otto Pixel deployment. - Otto Pixel requires explicit activation from within the Search Atlas platform before it fires on your site. - A previously disabled Otto Pixel will remain disabled after a new plugin installation unless you manually turn it on. ✅ How to Enable Otto Pixel on Your WordPress Site 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO (URL: /seo-automation-v3). 3. Select the project connected to your WordPress site. 4. Locate the Otto Pixel section on the project dashboard. 5. Click the toggle or Enable button next to Otto Pixel to activate it. 6. Once enabled, Search Atlas will generate your unique Otto Pixel script. 7. Confirm the status changes from Disabled to Active or Engaged. 🛠️ Verifying Otto Pixel Is Firing on Your Site After enabling Otto Pixel in Search Atlas, confirm it is correctly installed and running on your WordPress site: 1. Visit your WordPress site in a browser. 2. Right-click anywhere on the page and select Inspect (or press F12). 3. Go to the Network tab and reload the page. 4. In the filter bar, type otto to search for the pixel request. 5. If you see a successful request (status 200), Otto Pixel is firing correctly. 6. Alternatively, use the Sources or Elements tab to search the page source for the Otto Pixel script tag. If you do not see the pixel firing after following the steps above, proceed to the troubleshooting section below. ⚠️ Troubleshooting Otto Pixel Not Appearing If Otto Pixel is enabled in Search Atlas but still does not appear to fire on your WordPress site, work through the following checks: - Plugin version: Make sure your Otto SEO plugin is updated to the latest version. Outdated versions may not support Otto Pixel deployment. In WordPress, go to Plugins → Installed Plugins and check for available updates. - Plugin connectivity: Confirm the Otto SEO plugin is properly connected to your Search Atlas account. In WordPress, navigate to the Otto SEO plugin settings and verify your API key or account connection is valid. - Caching conflict: Clear your WordPress site cache and any CDN cache (such as Cloudflare). Cached pages may serve an older version of your site without the Otto Pixel script. - Script blocking: Check whether a security plugin (such as Wordfence or iThemes Security) or a Content Security Policy (CSP) is blocking third-party scripts. Whitelist the Otto Pixel domain if necessary. - Theme or page builder conflict: Some WordPress themes and page builders strip scripts added via plugins. Test by temporarily switching to a default WordPress theme (such as Twenty Twenty-Four) and checking whether the pixel fires. - Multiple Otto SEO plugin instances: Ensure only one instance of the Otto SEO plugin is active. Duplicate or conflicting plugin files can prevent the pixel from loading. 🔄 Re-Syncing Your WordPress Connection If Otto Pixel remains disabled after completing all steps above, try re-syncing the connection between Search Atlas and your WordPress site: 1. In Search Atlas, click OTTO SEO in the left sidebar (URL: /seo-automation-v3). 2. Open your project settings and locate the WordPress site connection. 3. Disconnect and then reconnect your WordPress site using your API credentials. 4. Return to the Otto Pixel section and re-enable it. 5. Return to your WordPress site, clear all caches, and verify the pixel is firing using the browser inspection method described above. 📋 Quick Reference Checklist - Otto Pixel toggled to Active in Search Atlas OTTO SEO dashboard - Otto SEO plugin updated to the latest version in WordPress - API key or account connection verified in the Otto SEO plugin settings - Site cache and CDN cache cleared - No security plugins or CSP rules blocking the pixel script - No theme or page builder conflicts preventing script injection - WordPress connection re-synced in Search Atlas if needed - Otto Pixel request confirmed as status 200 in browser DevTools If you need further assistance, open 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 Installation on BOKUN CMS

🔍 Overview If your OTTO pixel was previously connected to your BOKUN website but stopped working — or you have added the tracking code to your header and it still shows as inactive — this guide walks you through the correct reinstallation process. BOKUN has specific requirements for custom script injection that can cause the standard copy-paste approach to fail silently. ⚙️ Before You Begin Confirm the following before attempting a reinstall: - You have admin access to your BOKUN account. - You know which BOKUN website (if you manage more than one) needs the pixel. - Your Search Atlas account is active and you can reach the OTTO dashboard. - You have already removed or deactivated any previous version of the OTTO pixel code from BOKUN to avoid conflicts. 📋 Step 1 — Copy Your OTTO Pixel Code 1. Log in to Search Atlas. 2. In the left sidebar, navigate to OTTO SEO, then open SEO Automation inside it (URL: /seo-automation-v3). 3. Select the website associated with your BOKUN property. 4. Click Activate OTTO or open the OTTO settings for that site. 5. Locate the Pixel / Tracking Code section and click Copy Code. Keep this tab open — you will need it again in Step 3. 🖥️ Step 2 — Clear the Old Code from BOKUN 1. Log in to your BOKUN account and go to Website Builder. 2. Select your website, then open Settings (or Advanced Settings depending on your BOKUN plan). 3. Navigate to the Custom Code or Header Scripts section. 4. Delete all existing OTTO pixel snippets completely. Partial or duplicate code is a common reason the pixel never activates. 5. Save the changes before proceeding. 📥 Step 3 — Reinstall the OTTO Pixel Code in BOKUN 1. Still inside BOKUN's Custom Code / Header Scripts section, paste the fresh pixel code you copied in Step 1. 2. Make sure the code is placed inside the tag area, not the body or footer — BOKUN sometimes labels this section differently depending on your theme. Look for labels such as Head HTML, Custom Head Code, or Tracking Scripts. 3. Save and publish your website. In BOKUN, changes to custom code do not take effect until the site is explicitly published. ✅ Step 4 — Verify Activation in Search Atlas 1. Return to Search Atlas, go to OTTO SEO in the left sidebar, and open SEO Automation inside it. 2. Open the OTTO settings for your website. 3. Wait up to 10 minutes, then refresh the page to check the pixel status. 4. The status indicator should change from Inactive to Active. If it does not, proceed to the troubleshooting section below. 🔧 Common Issues and Fixes - Pixel still shows Inactive after 10 minutes: Confirm the BOKUN site was fully published after you saved the code — draft mode will not fire the pixel. - Code added to the wrong section: BOKUN's website builder has separate code fields for individual pages and for the global site header. Make sure you used the global / site-wide header field, not a page-level field. - Caching delay: BOKUN may serve cached versions of your pages. Try opening your live website in an incognito browser window to bypass the cache, then recheck the status in Search Atlas. - Multiple BOKUN websites: If you manage more than one BOKUN site, verify you pasted the code into the correct website. Each BOKUN website must have its own unique OTTO pixel code. - Script blocked by a third-party app: Some BOKUN marketplace integrations or cookie-consent tools block custom scripts. Temporarily disable third-party scripts and test activation again. 💡 Tips to Prevent Future Disconnections - After major BOKUN theme updates, always verify that custom code sections were not reset to default. - Keep a backup copy of your OTTO pixel code saved in a secure document so you can quickly reinstall without revisiting Search Atlas. - Check OTTO pixel status periodically from the OTTO SEO V3 dashboard to catch any unexpected disconnections early. 🙋 Need More Help? If you have followed every step above and the pixel still will not activate, If you need further assistance, open 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 Errors After Whitelabel Setup

Overview When you upgrade your Search Atlas plan or configure a whitelabel subdomain, your Otto pixel becomes tied to a new URL environment. Any previously installed pixels are no longer valid for that domain, which causes "Otto not deployed" and "Access forbidden" errors across your projects. The fix requires you to regenerate your Otto pixel inside the platform and redeploy it to each site under your new whitelabel subdomain. When Pixel Regeneration Is Required You must regenerate and redeploy your Otto pixel any time one of the following changes occurs: - You upgrade to a new Search Atlas plan - You set up or change a whitelabel subdomain - You transfer projects to a different whitelabel environment - Your current pixel was generated before your whitelabel subdomain was fully activated In all of these cases, the old pixel references the previous domain and will not authenticate correctly against the new whitelabel URL, triggering the errors you are seeing. Step 1 — Confirm Your Whitelabel Subdomain Is Active Before regenerating your pixel, make sure your subdomain is fully propagated and reachable. 1. Open a browser and navigate to your whitelabel subdomain. 2. Confirm the Search Atlas login screen loads without errors. If it does not load, your DNS records may still be propagating — allow sufficient time after initial setup for propagation to complete. 3. Log in through your whitelabel subdomain URL, not through the default Search Atlas domain. All steps below must be completed while logged in via your whitelabel URL to ensure the pixel is generated for the correct environment. Step 2 — Regenerate Your Otto Pixel 1. Log in to the platform via your whitelabel subdomain URL. 2. Navigate to OTTO SEO → All Sites (SEO Automation). 3. Select the project that is showing "Otto not deployed." 4. Locate the pixel or deployment option within the project and use the available control to generate a new pixel script. The platform will produce a fresh pixel tied to your active whitelabel subdomain. 5. Copy the full pixel code snippet that appears. Do not close this screen until you have successfully installed the code in the next step. Step 3 — Redeploy the Pixel to Your Site 1. Log in to the WordPress admin panel (or your site's CMS) for the project you are working on. 2. Navigate to the location where your previous Otto pixel was installed. This is typically inside a header script field, a dedicated Otto plugin settings page, or a custom code snippet area. 3. Replace the old pixel code with the new pixel code you copied in Step 2. 4. Save your changes and clear any site or server caches. 5. Return to the platform and verify that the project now shows Otto as deployed. If it still shows an error, wait a few minutes and refresh the page before troubleshooting 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 Scan Failures in HubSpot

🧭 Overview After pasting the OTTO Pixel into HubSpot, some users see a scan failure even though the code appears to be installed correctly. In most cases, the root cause is not the installation itself — it is a security layer on the hosting environment that blocks the Search Atlas crawler before it can verify the Pixel. This article walks you through a correct HubSpot installation and, critically, how to whitelist the Search Atlas crawler on servers and security tools that are not Cloudflare. 📋 Step 1: Install the OTTO Pixel in HubSpot 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) using the left sidebar (URL: /seo-automation-v3). 2. Open your OTTO project and copy the full Pixel script snippet. 3. Log in to your HubSpot account and navigate to the Settings area, then look for the section where you can add custom tracking or header code to your site pages (the exact menu label may vary by HubSpot plan and version — consult HubSpot's current documentation if needed). 4. Paste the OTTO Pixel snippet into the header code field for your site, then save your changes. 5. Return to Search Atlas and trigger a new scan to confirm detection. If the scan still fails after completing these steps, proceed to the crawler whitelisting section below. 🛡️ Step 2: Whitelist Search Atlas Crawlers (Non-Cloudflare Environments) If your client's site does not use Cloudflare, the crawler may be blocked by one of the following: a Web Application Firewall (WAF), a WordPress security plugin, a server-level firewall rule, or a CDN provider. Use the relevant section below to allow the Search Atlas crawler through. 🔎 Identify the Search Atlas Crawler Details Before whitelisting, you need the crawler's identifiers. Allow access for the following: - User-Agent string:SearchAtlasBot - IP ranges: To obtain the current crawler IP list, open the chat widget in the bottom-right corner of the platform and type human teammate — a member of our team will provide the up-to-date IP ranges, as they may be updated periodically. ⚙️ Whitelisting by Environment Type WordPress Security Plugins (e.g., Wordfence, Sucuri, or similar WAF/security plugins) 1. Open the plugin's settings dashboard in WordPress. 2. Locate the Whitelisting, Allowlist, or Trusted Bots section (the exact label varies by plugin). 3. Add SearchAtlasBot as a trusted User-Agent. 4. If the plugin allows IP-based rules, also add the Search Atlas crawler IPs obtained from the support team. 5. Save settings and re-run the OTTO scan. Server-Level Firewalls (Nginx, Apache, or similar) 1. Access your server and open the relevant configuration file for your web server or firewall tool. 2. Add a rule to allow requests from the SearchAtlasBot User-Agent and from the Search Atlas crawler IP ranges. 3. Reload or restart the web server to apply the changes. 4. Re-run the OTTO scan in Search Atlas to confirm the crawler can now access the site. If you are unsure which security layer is blocking the crawler, check your server or WAF access logs for blocked requests matching the SearchAtlasBot User-Agent — this will identify which tool needs to be configured. If you need further assistance, open 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 in Dashboard

🧩 Understanding the Four Stages of OTTO Pixel Detection Seeing the OTTO Pixel snippet in your page source is only the first step. The Search Atlas dashboard confirms detection only after completing four distinct stages. Each stage can fail independently, which is why confirming one stage does not guarantee the next will succeed. 1. Installation — The pixel code is present in your website HTML. 2. Firing — The code executes when a browser loads the page. 3. Data Transmission — The fired pixel sends a request to Search Atlas servers. 4. Dashboard Detection — The Search Atlas UI reflects the received data and marks the pixel as active. IP whitelisting and code visibility in page source only address Stage 1. If your dashboard still shows the pixel as undetected after more than 30 minutes, the issue almost certainly lies in Stage 2, 3, or 4. ⏱️ Expected Detection Timeline Once the pixel fires and data reaches Search Atlas servers, the dashboard should update within 5 to 30 minutes. If more than 30 minutes have passed since a real browser visited your page with the snippet present, use the verification steps below to diagnose where the process is stalling. 🔎 How to Verify Each Stage ✅ Stage 1 — Confirm Installation Open your browser, navigate to your website, right-click anywhere on the page, and select View Page Source. Search for OTTO or the snippet ID provided in your Search Atlas account. If the code appears, Stage 1 is complete. ⚡ Stage 2 — Confirm the Pixel Is Firing A pixel present in HTML does not automatically mean it executes. Rendering issues, JavaScript errors, or tag manager conflicts can block execution. To verify firing: 1. Open your website in a browser. 2. Press F12 (or right-click and select Inspect) to open DevTools. 3. Click the Console tab and look for any JavaScript errors. Errors appearing before the pixel code loads may prevent execution. 4. Reload the page while DevTools is open to capture all activity from the start. If you see JavaScript errors unrelated to OTTO, resolve those first, as they can interrupt all scripts that load after them. 📡 Stage 3 — Confirm Data Transmission to Search Atlas This is the most common hidden failure point. Even if the pixel fires, a browser extension, firewall, Content Security Policy (CSP) header, or ad blocker can silently block the outbound request before it reaches Search Atlas servers. 1. Open your website in a browser with no extensions enabled (use an Incognito window and disable all extensions, or use a fresh browser profile). 2. Open DevTools and click the Network tab. 3. In the filter bar, type searchatlas to filter relevant requests. 4. Reload the page. 5. Look for an outbound request to a Search Atlas endpoint (the URL will contain searchatlas.com). A status code of 200 confirms the request succeeded. If no request appears, the pixel is either not firing (return to Stage 2) or an external factor is blocking the outbound call. Common blockers include: - Ad blockers or privacy extensions — test in a clean browser profile. - Content Security Policy (CSP) headers — ask your developer to check whether your site's CSP restricts outbound requests to external domains. - Firewall or proxy rules — ensure your hosting environment permits outbound requests to Search Atlas servers. - Caching plugins or CDN rules — some configurations serve cached HTML without executing scripts. Purge your cache and retest. If a request appears but returns a 4xx or 5xx status code, note the exact code and contact support using the instructions at the bottom of this article. 📊 Stage 4 — Confirm Dashboard Detection Once Stage 3 is verified, allow up to 30 minutes for the Search Atlas dashboard to update. To check detection status: 1. Log in to Search Atlas and go to OTTO SEO → All Sites (SEO Automation) from the left sidebar (URL: /seo-automation-v3). 2. Locate your OTTO project and open its settings. 3. Review the pixel status indicator. If Stage 3 confirmed a successful request but the dashboard still shows undetected after 30 minutes, proceed to the next section. 🛠️ Additional Checks if All Stages Appear Correct - Correct snippet placed on the correct domain — verify the snippet in your Search Atlas account matches the domain you are testing. Snippets are domain-specific. - Pixel placed inside the correct HTML tag — the OTTO Pixel snippet should be placed inside the tag of your page, not inside a conditional comment or a template section that only loads for logged-in users. - Testing with a real browser visit — search engine crawlers and synthetic monitoring tools do not trigger pixel firing. Use an actual browser session. - Cookie consent or consent management platform (CMP) — if your site uses a cookie consent banner, the pixel may be configured to fire only after a user accepts tracking. Test by accepting all cookies and reloading. 📋 Quick Checklist Before Contacting Support - Pixel code is visible in page source on the correct domain. - No JavaScript errors appear in the DevTools Console on page load. - A Network request to a searchatlas.com endpoint returns a 200 status code in a clean browser profile with no extensions. - Cache has been purged and the page retested. - More than 30 minutes have passed since confirming a successful Network request. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix OTTO Head Tag Detection After Re-adding Site

🧭 Overview If you have added the OTTO head tag to your site but OTTO still shows it as undetected, the most effective fix is to remove the site from OTTO and re-add it after verifying the tag is installed correctly. This article walks you through the process. ⚠️ Before You Begin Confirm the following before removing your site: - You have access to your site's CMS or code editor. - You know where your site's section is managed (theme file, custom code block, or plugin). - You are using the latest OTTO script tag provided inside the platform — do not reuse a tag copied from a previous session. 🗑️ Step 1: Remove Your Site from OTTO Navigate to OTTO SEO → All Sites (SEO Automation) and locate your site. Use the available option to remove the site from OTTO and confirm the action when prompted. Your site will be disconnected from OTTO. No SEO automations or previously applied changes will be affected on your live site at this stage. 📋 Step 2: Re-add Your Site and Copy the Correct Script Tag Once the site has been removed, use the option to add your site again and enter your domain. When the platform provides a script tag for verification, copy it exactly as shown — do not modify it before pasting it into your site. 🏗️ Step 3: Add the Tag to Your Site's Head Section Paste the copied script tag into the section of your site. Where you do this depends on your CMS or website platform — refer to your platform's documentation for instructions on adding custom code to the head section. After saving, if your site uses any caching or performance plugins or services, clear all caches so the updated tag is served to visitors and to OTTO's verification check. 🟡 Lovable CMS If your site is built with Lovable, take care to add the OTTO script tag in the location that persists across publishes. Refer to Lovable's official documentation for guidance on adding persistent custom head code, then paste the OTTO script tag there before publishing. ✅ Step 4: Verify Detection in OTTO Return to OTTO SEO → All Sites (SEO Automation) and check whether your site now shows the head tag as detected. If detection is still not confirmed after completing the steps above, reach out to the support team with your site URL, the CMS you are using, and a description of where you placed the script tag. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Site Pixel Not Detected in Search Atlas

🧭 Overview After installing the Search Atlas pixel on your website, you may notice that the platform has not yet detected it — even if a third-party tool confirms the pixel is present in your page header. This is expected behavior. Detection depends on the site auditor completing a full crawl of your site, which can take up to 24 hours. This article explains why the delay occurs, what to expect during that window, and how to confirm your pixel is correctly installed in the meantime. ⏱️ Why the Pixel Is Not Detected Immediately Search Atlas detects your site pixel by crawling your website during the site auditor process — it does not perform a real-time check at the moment of installation. Because of this, there is a natural delay between when you install the pixel and when the platform confirms detection. This delay is normal and does not mean your pixel is broken or missing. - The site auditor runs a full crawl of your domain to collect data, including pixel presence, page health, and technical SEO signals. - Crawl queue and site size affect how long the process takes. Larger sites or high-demand periods may push completion toward the full 24-hour window. - Your pixel can be correctly installed and fully functional even while the platform still shows it as undetected. 📋 What to Expect After Installing Your Pixel After installing your pixel, allow up to 24 hours for the site auditor to complete its crawl and update the detection status in the platform. You do not need to reinstall the pixel or take any action during this window. Allow the full 24-hour period to pass before treating the delay as an issue. If the pixel is still not detected after 24 hours, proceed to the verification steps below. 🤖 OTTO Status Update Expectations If you are using OTTO, Search Atlas's OTTO SEO automation, its status reflects data from the most recently completed site audit. This means: - OTTO will not show your pixel as active until the site auditor has finished processing and confirmed detection. - Any OTTO recommendations or automations that depend on pixel data will update automatically once the audit completes — you do not need to re-trigger anything manually. ✅ How to Verify Your Pixel Is Correctly Installed While Waiting While the site auditor processes your site, use the following steps to confirm your pixel is in place so you can be confident the detection update will succeed once the crawl finishes: 1. Open your website in a browser and view the page source (right-click → View Page Source). 2. Search for your Search Atlas pixel code in the <head> section of the page. 3. If the pixel code is present in the header, your installation is correct. No further action is needed — wait for the site auditor to complete its crawl. If you need further assistance, open 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 False Duplicate OTTO Pixel Warnings

🧭 Overview If your Search Atlas account displays a warning about duplicate OTTO Pixel installations, it does not always mean two copies of the pixel code are actively running on your site. This article explains what triggers that alert, how to verify whether a true duplicate exists, and how to resolve lingering OTTO SEO status messages after you have already removed scripts. ⚠️ What the Duplicate Warning Actually Means The duplicate OTTO Pixel alert is triggered by signals detected within Search Atlas related to your account's pixel configuration state. This distinction is important: the warning can appear even if you inspect your page source, CMS dashboard (such as DealerOn), and Google Tag Manager and find only one instance of the pixel code — or none at all. The alert reflects the account's internal configuration state, not a real-time audit of your live site. 🔎 How to Check for a True Duplicate Before contacting support, run through the following verification steps to gather accurate information about your pixel status. 1. Check your live page source. Open your website in a browser, right-click the page, and select View Page Source. Use Ctrl+F (Windows) or Cmd+F (Mac) to search for otto or your pixel ID. Note how many times it appears. 2. Audit Google Tag Manager. Log in to your GTM workspace and review all tags. Search for any tag containing your OTTO Pixel ID. Confirm whether it is set to fire on all pages or on specific triggers. Check both Published and Workspace versions. 3. Check your CMS backend. In DealerOn or your equivalent CMS, locate the section where third-party scripts or tracking codes are added. Confirm whether the pixel snippet appears there, and note the exact placement (header, footer, or body). Document what you find in each location. This information is essential for the support team to diagnose your account configuration accurately. 🤖 What the OTTO SEO Status Actually Reflects The OTTO SEO status shown inside Search Atlas may continue to show as active even after you have removed the pixel code from your CMS or tag manager. Resolving this typically requires a configuration adjustment on the account side. When escalating to support, please have ready: your domain name, a description of where the pixel was previously installed (GTM, CMS, or both), and a note of what you observed when checking your page source and CMS backend. 📋 Next Steps If you have completed the verification steps above and the duplicate warning or OTTO SEO status is still not resolved, please reach out to our support team with the details you gathered. If you need further assistance, open 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 Not Showing Connected After Install

🔍 Overview After adding the OTTO script to your website, you may notice the dashboard still shows the pixel as not connected. In most cases, this is completely normal. Search Atlas checks for the pixel on a schedule based on your project's age: every 15 minutes for projects under 2 hours old, every hour from 2 to 24 hours old, every 6 hours from 1 to 7 days old, and automatic checks stop after 7 days. A correctly installed pixel on a new project is normally detected within about 15 minutes. No reinstallation is needed — you simply need to wait for the next check and for the initial audit to finish. 📋 Understanding Connection Statuses Once the OTTO script is installed, your dashboard will display one of two statuses: - Audit in Progress — The OTTO pixel has been detected and the initial site audit is actively running. Search Atlas is crawling your site and collecting data. This is the expected status immediately after installation. - Connected — The initial site audit has completed successfully. OTTO is fully active and ready to manage SEO automation on your site. The transition from Audit in Progress to Connected happens automatically once the audit finishes. You do not need to take any action during this time. ⏱️ Why Does the Audit Take Time to Complete? When the OTTO script is first installed, Search Atlas performs a comprehensive crawl of your entire website. This initial audit scans your pages, content, metadata, and technical SEO signals so OTTO can build an accurate baseline before making any recommendations or changes. The time required depends on the size of your site — larger sites with many pages naturally take longer to crawl. 📊 How to Monitor Your Audit Progress You can track the status of your site audit at any time from inside the platform by navigating to the OTTO dashboard and locating your connected site. If the status shows Audit in Progress, the crawl is still running — check back periodically. Once the status updates to Connected, your OTTO setup is complete and fully active. ✅ How to Confirm Your Script Was Installed Correctly While waiting for the audit to complete, you can verify that your script is installed properly so you can rule out any installation issues by checking that the OTTO script tag is present in your site's code and loading without errors. If the script is present and loading correctly, the Audit in Progress status simply means the crawl is still running — no further action is needed on your end. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Pixel Not Detected During Site Audit

🧭 Overview If you have installed the OTTO Pixel on your WordPress site and the status still shows Not Detected, do not worry. In most cases, this is completely expected behavior — not a sign that something went wrong with your installation. This article explains why the Not Detected status can appear while a site audit is active and what you should do while you wait. ⚙️ Why This Happens When you connect your site to OTTO, the OTTO Pixel verification check runs automatically on a schedule based on how old the project is: every 15 minutes for projects under 2 hours old, every hour from 2 to 24 hours old, every 6 hours from 1 to 7 days old, and no automatic checks after 7 days. This means: - The Not Detected status may simply mean the next scheduled check has not yet run. - It does not necessarily mean the Pixel is missing, broken, or installed incorrectly. - A correctly installed Pixel on a new project is normally detected within about 15 minutes. Attempting to reinstall or troubleshoot the Pixel before the next scheduled check is unlikely to speed up detection. ✅ What to Do While You Wait 1. Go to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Locate your connected site and open its OTTO dashboard. 3. Wait for the next scheduled Pixel check to run — for a brand-new project this is normally within about 15 minutes. 4. Refresh the page and check the OTTO Pixel status again. 🔧 If the Status Still Shows Not Detected After the Next Check If the next scheduled check has run and the OTTO Pixel status still shows Not Detected, it is worth verifying your installation. Check that the Pixel code or plugin is active on your site and that nothing is preventing it from loading correctly (for example, a caching layer serving pages without the Pixel code). If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix an Unengaged OTTO Pixel

🔍 What Does "Not Engaged" Mean? The OTTO pixel is a small piece of code installed on your website that allows OTTO SEO to read your site, deploy optimizations, and track changes. When the pixel status shows Not Engaged, it means Search Atlas can no longer detect the pixel on your site. This usually happens after a theme update, plugin conflict, website migration, or a manual code change that removed or overwritten the pixel. Until the pixel is re-engaged, OTTO cannot push or maintain any on-page SEO changes. ⚙️ Step 1 — Check Your Current Pixel Status 1. Log in to Search Atlas and navigate to your OTTO SEO project. 2. Check the pixel status shown for your project. If it shows as Not Engaged, continue to the steps below. 🧩 Step 2 — Locate Your OTTO Pixel Code 1. Within your OTTO SEO project settings, locate the pixel code provided for your site. 2. Copy the full pixel code snippet shown. Make sure you copy the entire snippet without missing any characters. 🌐 Step 3 — Reinstall the Pixel on Your Website There are two common installation methods. Use the one that matches how your site is built. The pixel code snippet is intended for non-WordPress platforms or alternative installs such as Google Tag Manager; on WordPress, use the MetaSync plugin instead. WordPress sites: 1. Install and activate the Search Atlas (MetaSync) WordPress plugin. 2. In WordPress, open Search Atlas → Settings. 3. Paste your Search Atlas API key. 4. Paste your OTTO Pixel UUID. 5. Save your changes — the plugin will handle the pixel for you. Non-WordPress or custom sites: 1. Open your site's main HTML template or layout file. 2. Paste the OTTO pixel code immediately before the closing </head> tag on every page, or in the shared header partial if your framework supports one. 3. Deploy and publish the changes. ✅ Step 4 — Verify the Pixel Is Detected 1. Return to Search Atlas and open your OTTO SEO project. 2. Allow some time for Search Atlas to crawl your site and confirm detection. 3. The pixel status should update once the pixel is successfully found on your site. ⚠️ Common Reasons the Pixel Stops Working - Theme or plugin update: Some updates overwrite header templates or reset custom code injections. Always re-check your pixel after major updates. - Caching plugins: Aggressive caching can serve old page versions that no longer include the pixel. Clear your site cache after reinstalling. - Website migration: Moving your site to a new domain or host can cause the pixel code to be lost. Always reinstall the pixel after a migration. - Manual code edits: Editing theme files directly can accidentally remove the pixel snippet. If you need further assistance, open 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 Installation Issues Fast

🔍 Overview The OTTO pixel is a small tracking script that connects your website to OTTO SEO, allowing Search Atlas to monitor your site and apply automated SEO improvements. If the dashboard shows your pixel as not installed, this guide will help you locate your pixel script and troubleshoot the most common causes. 📋 Step 1: Retrieve Your OTTO Pixel Script You can find your unique pixel script directly inside the Search Atlas platform. Follow these steps: 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Locate the website you want to configure and open its OTTO SEO settings. 4. Navigate to the Pixel or Install section within that site's OTTO dashboard. 5. Copy the full pixel script shown on screen — make sure you copy the entire code block without missing any characters. Keep this script handy before moving on to the installation steps below. ⚙️ Step 2: Install the Pixel on Your Website The method you use depends on your website platform. Follow the instructions for your setup: - WordPress: Install the Search Atlas (MetaSync) WordPress plugin. Once activated, go to Search Atlas → Settings in your WordPress admin, paste your Search Atlas API Key (or use One-Click Authentication), and paste your OTTO Pixel UUID. The plugin will then handle the pixel automatically. If the plugin is only partially installed, make sure all plugin files were uploaded successfully and that the plugin is fully activated — not just installed. - Shopify: Go to your Shopify admin, navigate to Online Store → Themes → Edit Code, and paste the pixel script just before the closing </head> tag in your theme.liquid file. Save your changes. - GoHighLevel (GHL): In your GHL account, go to Sites → Funnels or Websites → Settings → Tracking Code and paste the pixel script into the header tracking field. - Other platforms: Paste the pixel script into the <head> section of your site's HTML, or use your platform's built-in tag/script manager to deploy it site-wide. 🚨 Common Reasons the Pixel Shows as Not Installed After installing the script, the OTTO dashboard may still report the pixel as not detected. Here are the most frequent causes and how to fix them: - Script not on all pages: The pixel must load on every page of your site, not just the homepage. Confirm your script is placed in a global template or header file. - Caching delay: Server-side or CDN caching can delay detection. Clear your site cache and wait up to 15 minutes before checking again. - Cloudflare blocking the script: If your site uses Cloudflare, certain security rules or Workers can block the pixel from firing. Check your Cloudflare dashboard for any Authorization errors (error code cf_10000), and ensure the OTTO pixel domain is not blocked by a Firewall rule or Worker route. - Script placed incorrectly: The pixel must appear inside the <head> tag, not in the footer or body. Double-check the placement in your theme or template editor. - Partial WordPress plugin install: If you used the WordPress plugin, navigate to Plugins → Installed Plugins in your WordPress admin and confirm the plugin status shows Active. A partially uploaded plugin file will prevent the pixel from loading correctly. - JavaScript errors on the page: A separate JavaScript error on your site can prevent the pixel from executing. Open your browser's developer console (F12) and look for any errors on the page. ✅ Step 3: Verify the Pixel Is Detected Once you have installed or corrected your pixel script, follow these steps to confirm it is working: 1. Clear your browser cache and your website's server cache. 2. Visit your website in a browser to trigger a page load. 3. Return to OTTO SEO → All Sites (SEO Automation) in your Search Atlas dashboard and open the OTTO settings for your site. 4. Check the pixel status — it should now show as Installed or Active. 5. If the diagnostic tool shows a partial or failed status, review the specific reason code displayed and match it to the troubleshooting items listed above. 💡 Tips to Avoid Future Issues - Always copy your pixel script fresh from the Search Atlas dashboard — do not reuse a script copied from another site. - After any theme update or platform migration, verify the pixel is still present and loading correctly. - If you use a tag manager such as Google Tag Manager, test the tag is firing on all pages using the preview mode before going live. 🙋 Still Need Help? If you have followed all the steps above and the pixel still shows as not installed, or if you are seeing a specific error not covered here, 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.

🚫 Duplicate OTTO Pixel: How to Find, Fix, and Prevent Multiple Installations

Installing the OTTO Pixel is the first step to unlocking AI-powered SEO automation — but when it's installed more than once, OTTO may: - Show "Duplicate Installation Detected" in Diagnostics - Fail to fully enable - Misread page state or slow down verification The tricky part: you might not realize it's installed twice (the plugin, GTM, theme code, etc.). This guide explains exactly how to confirm, fix, and prevent duplicates across WordPress, Shopify, Wix, GTM, GoHighLevel, Webflow, Squarespace, custom sites, and more. 🔎 TL;DR — What "duplicate pixel" really means OTTO has detected multiple instances of the OTTO Pixel loading on your site. In some cases, incomplete setup or missing site metadata on certain platforms can trigger false duplicate-detection warnings. Typically, actual duplicates occur when: - WordPress plugin + GTM + manual <script> - Script injected on multiple templates or pages - Apps, CDNs, or minifiers re-injecting the same script Before diagnosing a duplicate, always verify that all installation steps are complete and basic site information (like business address on certain platforms) is filled in. OTTO needs one clean installation path and one UUID per project. 🧭 Quick path: How to confirm you have a duplicate 1. Use both of these methods: 1) Check the live HTML manually 1. Open your homepage in a browser (the same domain you configured in Search Atlas). 2. Right-click → View Page Source. 3. Press Ctrl+F (Windows) / Cmd+F (Mac) and search for: sa-dynamic-optimization searchatlas data-uuid 4. Count how many times the OTTO script appears: - If you see two or more script blocks with the OTTO src/UUID →, you definitely have duplicates. - If you only see one, it may still be duplicated via GTM or apps → continue with method 2. 2) Confirm via OTTO Diagnostic (recommended) 1. Go to Search Atlas → OTTO SEO → All Sites. 2. Click on your site to open the OTTO SEO Automation dashboard. 3. Click Scan → Run Diagnostics. OTTO will begin scanning your site for the installed Pixel. During this stage, you'll see the message: "Running Diagnostics… We're checking the selected page for any OTTO implementation issues. This might take a few seconds — hang tight! A detailed report will be ready shortly." Wait for the diagnostic to complete, then scroll through the results. If OTTO sees multiple instances, you'll see a message like: - "Duplicate Installation Detected" If you see that status, you can be sure OTTO is detecting more than one Pixel, and you should go ahead with the platform-specific fix. 🧰 Universal Fix Checklist (do this before you dive into platform specifics) Goal: keep one install method, remove everything else. 1. Choose ONE source of truth - WordPress plugin or - GTM or - Manual <head> script or - CMS global "Custom Code / Code Injection" or - GHL Global Section Never mix methods (e.g., plugin + GTM + manual script). 2. Remove all other copies of the OTTO script - Delete extra <script> tags from theme files, page builders, embeds, or extra sections. - Remove GTM tags that inject OTTO if the plugin is your source. - Remove plugin / app embeds if GTM or manual script is the source. 3. Clear caches everywhere - Browser: hard reload (Ctrl+Shift+R / Cmd+Shift+R) or open in Incognito. - WordPress cache (via Search Atlas plugin): - WordPress → Search Atlas → Settings → Settings dropdown → Advanced → Error Logs → Clear All Cache Plugins. - Cache plugins / host: click "Purge / Clear All Cache" in WP Rocket, LiteSpeed, W3TC, host panel, etc. - CDN / WAF: e.g. Cloudflare → Caching → Purge Everything. - CMS publish: Shopify/Wix/Webflow/Squarespace → Save + Publish / Publish to domains. 4. Force OTTO to re-check - Search Atlas → OTTO SEO → All Sites → Select your site → Scan → Run Diagnostics. - Wait 3–5 minutes and refresh. If the duplicate is fully resolved, the diagnostic will stop showing the "Duplicate Installation Detected" message. 🖥️ Platform-by-Platform Fix Playbooks 🟩 WordPress (Plugin vs GTM vs manual script) Most common root causes - OTTO installed via the Search Atlas plugin and via GTM or theme/header code. - Script added in header.php or functions.php plus plugin injection. - Staging → production migration that left old code and the plugin active. - Cache/minification plugins cloning or delaying the script. How to fix (plugin as source of truth — recommended) 1. Keep the Search Atlas WordPress plugin as the only OTTO source. 2. Remove any OTTO scripts from: - GTM tags - header.php, functions.php, or other theme files 3. In WordPress → Search Atlas → Settings: - Ensure Authentication Successful. - API Key, Plugin Auth Token, and OTTO Pixel UUID are populated. 4. Clear cache via: Search Atlas → Settings → Settings dropdown → Advanced → Error Logs → Clear All Cache Plugins. If GTM is your source of truth instead 1. In WordPress, disable OTTO features in the plugin or disconnect Pixel injection. 2. Remove any manual OTTO scripts from theme files. 3. In GTM: - Use one Custom HTML tag with the OTTO script. - Trigger: All Pages or Initialization – All Pages. - Advanced Settings: fire Once per page. 4. Publish the container. 5. Re-run OTTO Diagnostics. 🟨 Google Tag Manager (GTM) Common root causes - Two GTM containers installed simultaneously. ❓ Troubleshooting: When It's Not Actually Duplicates Some platforms show duplicate-detection symptoms that aren't actually caused by multiple pixel installations. Here's how to rule these out: - Duda sites: If OTTO shows "Not Installed" or similar despite seeing the pixel live on your site, ensure you've completed the "Continue Installation" step in your Duda site settings. Incomplete setup can trigger false detection errors. - Lovable-built sites: OTTO requires basic site metadata to detect your pixel properly. Verify that your business address field is filled in and complete, then run a manual recrawl to allow OTTO to refresh its detection. - Lovable AI builder: If you're using the Lovable AI site builder, check your site code for MutationObserver conflicts that may prevent OTTO deployment. These conflicts can block the pixel from initializing correctly. - Shopify: Manual code injection (adding scripts directly to theme files) can cause theme errors and prevent proper OTTO detection. If you've manually injected the OTTO pixel, we recommend reaching out to support for assistance with proper integration.