🛠️ Troubleshooting

🛠️ Troubleshooting AI Credits Used With No Results

This article addresses a known issue where an AI generation task — such as page-level schema creation in the OTTO SEO tab — reports as completed and deducts credits, but the generated output does not appear in your project. This can happen when results are delayed after a generation job finishes. Follow the steps below to recover your results or escalate for a credit review. 🛠️ Step-by-Step 1. Wait and hard-refresh before assuming failure. After a generation completes, allow some time for results to appear. Then press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh, bypassing any cached page state. 2. Re-open the specific site and navigate back to the OTTO SEO tab. Close the current tab or project view entirely, return to your project list, and reopen the affected site. Navigate back to the OTTO SEO section and check whether the schema entries now appear. 3. Check for any status indicators in the OTTO SEO tab. Look at the OTTO SEO tab to see whether the generation is shown as completed or still pending. If the job shows as completed but no output is visible, this confirms a result delivery issue. 4. Do not re-run the generation immediately. Triggering the same generation a second time before the first result is confirmed will consume additional credits. Wait for a support confirmation (see below) before retrying. 5. Document your evidence before reaching out. Take a screenshot of: (a) the OTTO SEO tab showing no output, and (b) your credit balance or usage log showing credits were deducted. This allows the support team to verify the issue and process a credit adjustment if warranted. ✅ How to Confirm It Worked The issue is resolved when all of the following are true: the page-level schemas you generated are visible and listed inside the OTTO SEO tab for the affected site; the correct number of schemas matches the pages you submitted for generation; and no duplicate or empty entries appear in the list. If you re-ran the generation after following the steps above, verify that only one set of results exists to avoid duplication. If credits were consumed but results never appeared, a support agent can confirm the generation outcome on the backend and issue a credit adjustment where applicable. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Script Verification and Manage Your Account

🔍 Overview If OTTO is not verifying your installed script, it can be frustrating — especially if you are considering cancelling your membership as a result. This article walks you through the most common reasons script verification fails, how to fix them, and what to do if you still want to cancel your account. ⚙️ How OTTO Script Verification Works When you activate OTTO SEO on a website, Search Atlas deploys a small script to your site. OTTO's AI then checks for that script to confirm the connection is live. If the script cannot be detected, OTTO will show a verification error and automation will not run. Verification can fail for several common reasons: - The script was not saved or published correctly on your website - A caching plugin or CDN is serving an older version of your page - A security plugin or firewall is blocking external script detection - The script was placed in the wrong location in your site's HTML - Your website requires HTTPS but the script was added to an HTTP page 🛠️ Steps to Fix the Verification Issue 1. Locate your OTTO script: Go to the left sidebar and select OTTO SEO, then open All Sites (SEO Automation) (URL: /seo-automation-v3). Find your website and open its OTTO settings to copy the script snippet. 2. Confirm the script is published: Log in to your website's CMS or code editor and verify the script appears in the <head> section of every page. Make sure the changes are saved and published — not just saved as a draft. 3. Clear your cache: If you use a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), purge all cached files. Also clear any CDN cache (such as Cloudflare) if applicable. 4. Check for script blockers: Temporarily disable security or firewall plugins and re-run the verification. If it passes, whitelist the Search Atlas script domain in your security settings before re-enabling the plugin. 5. Re-run verification: Return to OTTO SEO → All Sites (SEO Automation) (/seo-automation-v3), select your site, and click Verify Script again. Allow up to two minutes for the check to complete. 6. Test with a fresh browser tab: Open your website in a private or incognito window to confirm the script appears on the live page, then retry verification. 💡 Still Not Verifying? Before You Cancel Script issues are almost always resolvable with the right configuration. Our support team can remotely review your script placement and verification logs, saving you the trouble of cancelling and potentially losing your SEO progress. We strongly recommend reaching out before taking any cancellation steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. 🚪 How to Cancel Your Membership If you have decided to proceed with cancellation, please be aware of the following before you act: - Cancelling your account will immediately deactivate OTTO on all connected websites - Your SEO automation history and configurations will no longer be accessible - Subscription fees are non-refundable once a billing cycle has started (refer to your plan's terms) To request a cancellation, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. A team member will process your request and confirm the cancellation in writing. ❓ Frequently Asked Questions - Can I cancel immediately mid-billing cycle? Yes, but access continues until the end of your current billing period. Our team will confirm the exact end date when you submit your request. - Will cancelling delete my data? Your account data and projects stay on your account after cancellation and are available again if you resubscribe. Deleting your account is a separate, permanent action. - Can I reactivate after cancelling? Yes, you can resubscribe at any time, though your previous OTTO configurations may need to be reconfigured.

🛠️ Fix OTTO Issues Before Cancelling Your Account

🔍 Overview If you're experiencing issues with OTTO SEO and considering cancelling your account, please read this article first. Many OTTO installation problems have quick fixes, and our team can resolve most issues within minutes. This guide walks you through common troubleshooting steps and explains your options so you can make an informed decision. ⚙️ Common OTTO Installation Issues and Fixes Before cancelling, try the following steps to resolve the most frequently reported OTTO installation problems: 1. Verify your website is connected: Go to the left sidebar and select OTTO SEO, then open SEO Automation (or navigate to /seo-automation-v3). Confirm your site appears in the project list and shows an active connection status. 2. Re-activate OTTO: On the OTTO SEO V3 dashboard, locate your site and click the OTTO toggle. If OTTO shows as inactive or errored, toggle it off, wait 10 seconds, then toggle it back on. 3. Check your website platform: OTTO works via a script or plugin installed on your website. Confirm the Search Atlas script or plugin is correctly installed and not blocked by a caching plugin, firewall, or CDN setting. 4. Clear your site cache: After installing or re-installing OTTO, clear your website and CDN cache to ensure the latest script loads correctly. 5. Refresh the OTTO SEO V3 dashboard: Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and check whether OTTO's status has updated. 🚀 How to Access the OTTO SEO V3 Dashboard To check OTTO's installation status and manage your settings: - Click OTTO SEO in the left sidebar of the Search Atlas platform, then open SEO Automation. - You can also navigate directly to /seo-automation-v3. - Select the relevant site project to view OTTO's current activation status and any error messages. 💡 Before You Decide to Cancel We understand that a technical issue can be frustrating, especially when it blocks you from getting results. Here's what we recommend before cancelling your account: - Contact support first: Our team can diagnose and fix most OTTO installation issues in real time. Many problems are caused by simple configuration conflicts that take only a few minutes to resolve. - Request a guided walkthrough: If you're unsure whether OTTO was set up correctly, a support teammate can share their screen and walk you through the process step by step. - Ask about a pause option: If you need time to sort out technical issues without losing your data or settings, ask our team whether a temporary pause is available for your plan. 🗂️ How to Cancel Your Account (If You Still Wish to Proceed) If you have already tried the troubleshooting steps above and still wish to cancel, please follow the steps below: 1. Click your avatar in the top-right corner of the platform to open the Avatar Menu (👤). 2. Navigate to Settings (/settings) and open the Team Members tab to access your account settings; billing is separate at Billing (/billing). 3. Look for the subscription or billing section to manage or cancel your plan. 4. If you cannot locate the cancellation option or need assistance, contact our support team via the chat widget — see the section below. Important: Cancelling your account will remove access to all your projects, reports, and OTTO configurations. This action cannot be undone, so please ensure you have exported any data you need before proceeding. 📞 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 Topical Map Generation and Metadata Issues

🛠️ Fix OTTO SEO Schema Update Errors

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

🛠️ OTTO Pixel Troubleshooting Guide

🛠️ Troubleshoot Missing, Pending, or Suggested Schema Markup in OTTO

🛠️ 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 Bulk Schema Deployment and OG Descriptions in OTTO SEO

Overview Two common questions from OTTO SEO users involve bulk schema deployment and the OG description field. This article explains what each one means and what to do if you are experiencing issues with either. What Is OG Description? OG description stands for Open Graph description. It is a short text snippet that controls how your page appears when shared on social media platforms such as Facebook and LinkedIn. It is part of your page's on-page metadata and is separate from your standard meta description, though both describe your page content. If you are unsure how OG description applies to your specific setup in OTTO SEO, or if the field is behaving unexpectedly, our support team can review your account and clarify how it is being used. Bulk Schema Deployment in OTTO SEO OTTO SEO allows you to generate schema markup for multiple pages at once. If you are experiencing issues with bulk-generated schemas — such as schemas that appear to disappear or do not behave as expected — this is something our support team can investigate directly on your account. Because the specifics of bulk schema behavior can vary depending on your site configuration and account state, there is no single universal self-serve fix. The most reliable next step is to contact our team so they can review what happened and guide you through completing your deployment correctly. When reaching out, please have the following ready: - The name of the project or domain where you are working - A description of what you attempted (e.g., generating schemas for multiple pages at once) - What you observed — for example, schemas that were generated but later could not be found - Any error messages or unusual behavior you noticed, with approximate timestamps if possible If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Domain Processing Failures Caused by Browser Cache

🔍 Overview If your website domain is failing to process inside Search Atlas, the issue may not be with the platform itself — it can often be traced back to stale or corrupted data stored in your browser's cache. This article walks you through how to identify and fix the problem quickly. ⚠️ Symptoms of This Issue - Your domain appears stuck on "processing" and never completes. - You see an error message when adding or verifying a domain in Search Atlas. - The same domain processes successfully in a different browser or device. - Reloading the page does not resolve the problem. 💡 Why This Happens Your browser stores temporary files, cookies, and cached data to help pages load faster. Over time, this stored data can become outdated or corrupted. When Search Atlas tries to process a domain, your browser may serve old, conflicting data instead of sending a fresh request to our servers — causing the processing step to fail or stall. 🛠️ How to Fix It Follow these steps to clear your browser cache and retry the domain processing: 1. Open your browser settings. In most browsers, you can do this by pressing Ctrl + Shift + Delete on Windows or Cmd + Shift + Delete on Mac. 2. Select the correct time range. Choose All time to make sure all relevant cached data is removed. 3. Check the right boxes. Make sure at minimum the following are selected: Cached images and files, Cookies and other site data. 4. Clear the data. Click the confirm or clear button to complete the process. 5. Close and reopen your browser. Fully quit the browser — do not just close the tab — then reopen it. 6. Log back in to Search Atlas. Go to app.searchatlas.com, sign in with your credentials, and navigate back to your domain settings. 7. Retry the domain processing. Attempt to add or process your domain again. ✅ Additional Troubleshooting Steps If clearing your cache does not resolve the issue, try the following: - Use a different browser. Test the domain processing in an alternative browser such as Chrome, Firefox, Edge, or Safari to determine if the problem is browser-specific. - Disable browser extensions. Ad blockers, privacy tools, or VPN extensions can sometimes interfere with platform requests. Try disabling them temporarily and retry. - Use an incognito or private window. This loads the platform without any cached data or active extensions, which helps isolate the cause. - Check your internet connection. An unstable connection can interrupt the processing request. Switch networks if possible and try again. 🙋 Still Having Trouble? If you have followed all of the steps above and domain processing is still failing, our support team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix Otto Duplicate Installation and Plugin Conflicts

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

🛠️ Fix Schema Markup Errors in Brand Vault

🔍 Overview The Schema Creator (More Features → Schema Creator) allows you to define and manage schema markup for your key service pages using JSON-LD. If you are seeing an error when entering schema or the markup is not appearing in your page source, this guide outlines what to have ready and how to get the issue resolved quickly. ⚠️ Common Reasons Schema Markup May Fail - Invalid JSON syntax: A missing bracket, comma, or quotation mark can cause the schema to be rejected or silently dropped. - Incorrect schema type: Using a schema type that does not match the page content can trigger validation errors. - Conflicting existing schema: If your page already contains schema markup added via your CMS or theme, a duplicate or conflicting block may prevent the new markup from rendering. - Page not re-crawled yet: After saving, it can take time for changes to be reflected in the live page source if a cache layer or CDN is involved. 🛠️ What to Do Before Escalating 1. Note the exact error message. Copy or screenshot any error text you see when working with schema in More Features → Schema Creator. 2. Identify the affected project and page. Have the project name and the URL of the page showing the schema issue ready. 3. Validate your JSON-LD independently. Paste your schema into Google's Rich Results Test (search.google.com/test/rich-results) or Schema Markup Validator (validator.schema.org) to check for syntax or structural errors. Note any issues flagged. 4. Check your live page source. Open the live page in your browser, right-click, and select View Page Source. Use Ctrl+F to search for your schema type (for example, LocalBusiness or Service) and note whether the markup is present or absent. 5. Record when the issue started. Note the approximate date and time you first noticed the schema error or missing markup. 📋 When to Contact Support If you are experiencing a schema markup error in More Features → Schema Creator and cannot resolve it using the steps above, please reach out to our team with the following information ready: your project name, the affected page URL, the exact error message you are seeing, and the results of your JSON-LD validation. This will allow our team to investigate and resolve the issue as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix 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 Headings & HTML Entities Cloudflare Worker Fix

🔍 Overview If your site uses OTTO SEO with a Cloudflare Worker to inject optimizations, you may have noticed that heading changes (H1, H2, etc.) appear correctly in your browser but are not visible in Google Search Console's (GSC) Live Test or are inconsistent in View Page Source. This issue specifically affects headings that contain HTML entities — for example, an ampersand rendered as &, a registered trademark symbol (®), or similar encoded characters. ⚙️ What Causes This Issue OTTO delivers heading optimizations by injecting a script via Cloudflare Worker that matches existing heading text on the page and replaces it with the optimized version. When a heading contains an HTML entity (such as & stored as & in the page source), the Worker script encounters a mismatch: - The page source contains the encoded version of the character (e.g., &). - The OTTO script tries to match the decoded or differently encoded version. - Because the text does not match exactly, the Worker skips the heading replacement entirely. - In some cases, the script re-encodes the entity a second time, causing double-encoding (e.g., &amp;), which can break heading styling and display incorrect text. Your browser is forgiving — it decodes and renders HTML entities automatically, so the heading looks correct to a human visitor. However, Google's crawlers and the GSC Live Test read the raw page source, where the mismatch or double-encoded entity is visible, meaning Googlebot may not see your optimized heading at all. ✅ What Has Been Fixed Our engineering team has identified and resolved this bug. The fix ensures that: - The Cloudflare Worker script correctly normalises HTML entities before attempting to match heading text, so encoded characters no longer cause a mismatch. - Double-encoding is prevented — entities are decoded once, matched accurately, and re-encoded correctly in the final output. - Heading optimizations are now applied consistently in both the browser and the raw page source, making them visible to Google's crawlers and the GSC Live Test. This fix is being rolled out as part of an active release. If your site was affected, the corrected behavior will apply automatically once the update reaches your site's Worker configuration — no action is required on your part. 📊 How to Confirm Optimizations Are Working After the fix has been applied to your site, follow these steps to verify that OTTO heading optimizations are now visible in both the browser and GSC: 1. Go to Google Search Console and open the URL Inspection tool. 2. Enter the URL of a page where OTTO has applied a heading optimization. 3. Click Test Live URL and wait for the crawl to complete. 4. Open the HTML tab within the live test results and search for your optimized heading text. 5. Confirm the heading appears with the correct, optimized content and no double-encoded characters. You can also use your browser's View Page Source (right-click → View Page Source, not Inspect Element) to check the raw HTML. The optimized heading should be visible in the source with correctly encoded entities. 💡 Additional Checks in OTTO SEO To review the heading optimizations OTTO has deployed on your site: 1. In Search Atlas, click OTTO SEO in the left sidebar. 2. Select your connected site and open the deployed optimizations view. 3. Filter by Headings to see which H1 and H2 optimizations are active. 4. Cross-reference these with the GSC Live Test results to confirm successful deployment. If you see a heading optimization listed as deployed in OTTO but it is still not appearing correctly in GSC after the fix rollout, note the specific URL and heading text (including any special characters) for our support team. 🚀 Preventing Future Issues While this bug has been fixed, keep the following best practices in mind when working with OTTO heading optimizations on pages that use special characters: - After OTTO deploys a heading change, always verify using View Page Source rather than browser Inspect Element — the inspector renders entities automatically and can mask encoding problems. - Use GSC URL Inspection → Test Live URL as your definitive check for what Googlebot sees. - If your site uses a page builder such as Elementor, be aware that some builders manage heading output differently; confirm optimizations render correctly in both the builder preview and the live source. 🆘 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix OTTO Heading Optimization LiteSpeed Rendering Error

Overview When OTTO deploys a heading optimization on sites running LiteSpeed Cache, a conflict can occur between OTTO's dynamic optimization script and LiteSpeed's caching behavior. This may cause visible rendering errors on your site, such as raw JavaScript appearing as text or SEO metadata becoming missing or malformed. This is a known compatibility issue between OTTO's heading optimization and LiteSpeed. Because the root cause is a bug, the steps below describe how to report it effectively so our team can investigate and resolve it for your site. What to Expect This issue requires investigation by our technical team. There is no guaranteed self-serve fix, because the conflict depends on your specific LiteSpeed configuration and how OTTO's optimization was applied. Our team will need to review your site's setup to identify the correct resolution. How to Escalate This Issue To help our team investigate as quickly as possible, please have the following information ready before reaching out: - The URL of the affected page where the rendering error is visible - The name of the OTTO heading optimization that was deployed (if known) - A description of the symptoms you are seeing — for example, JavaScript text appearing on the page or missing SEO metadata - Screenshots or a screen recording of the error as it appears on your site - The approximate date and time when the issue first appeared If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 OTTO Deployment Changes Blocked by Cache Plugins

🧩 Why Your OTTO Changes May Not Be Showing After deploying changes through OTTO (found in the left sidebar under OTTO SEO → All Sites (SEO Automation)), you may notice that updates do not appear on your live website — even after waiting 24–48 hours. In most cases, the culprit is not OTTO itself but a cache plugin installed on your WordPress site. Cache plugins store a static snapshot of your pages to speed up load times. When OTTO pushes changes to your site, the cache plugin can serve the old cached version to visitors instead of the updated content. This issue has been confirmed with Airlift and can also occur with other popular cache plugins, including WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and Cloudflare's caching layer. 🔍 How to Confirm Cache Is the Problem Before clearing your cache, verify that cache interference is the actual cause: 1. Open your website in a private or incognito browser window. 2. Check whether the OTTO-deployed changes (meta titles, descriptions, schema, headings, or other on-page updates) are visible. 3. If the changes still do not appear, log in to your WordPress admin dashboard and check whether a cache plugin is active under Plugins → Installed Plugins. 4. If a cache plugin is listed and active, proceed with the steps below to clear it. 🛠️ How to Fix It — Airlift Cache If you are using the Airlift plugin, follow these steps: 1. Log in to your WordPress admin dashboard. 2. In the left sidebar, click Airlift. 3. Navigate to the Cache tab or section. 4. Click Purge All Cache (the exact button label may vary slightly by version). 5. Wait 1–2 minutes, then reload your website in a private browser window to confirm the OTTO changes are now visible. 🛠️ How to Fix It — Other Common Cache Plugins The process is similar for other cache plugins. Use the guide below for your specific plugin: - WP Rocket: Go to Settings → WP Rocket and click Clear Cache in the dashboard panel. - W3 Total Cache: Click Performance in the WordPress sidebar, then select Purge All Caches. - WP Super Cache: Go to Settings → WP Super Cache and click Delete Cache. - LiteSpeed Cache: Click the LiteSpeed Cache icon in the WordPress admin toolbar and select Purge All. - Cloudflare: Log in to your Cloudflare dashboard, go to Caching → Configuration, and click Purge Everything. Note that this clears the CDN cache, not the WordPress cache — you may need to do both. ✅ After Clearing the Cache Once you have purged your cache, take these steps to confirm everything is working correctly: 1. Open your website in a private or incognito browser window (this prevents your own browser cache from interfering). 2. Navigate to the specific pages where OTTO deployed changes. 3. Verify that the updates — such as revised meta titles, descriptions, or structured data — are now reflected on the live page. 4. If you use a CDN (such as Cloudflare, BunnyCDN, or KeyCDN), purge the CDN cache as well, since CDN-level caching can cause the same issue independently of your WordPress cache plugin. 🚫 How to Prevent This in the Future To avoid deployment visibility delays after future OTTO sessions, consider building cache purging into your standard workflow: - Purge your cache immediately after every OTTO deployment before checking whether changes appear on the live site. - If your cache plugin supports it, configure automatic cache expiration so cached pages refresh after a set interval (for example, every 12–24 hours). - Some cache plugins offer selective purging — you can purge only the URLs that OTTO modified rather than clearing your entire cache, which reduces the performance impact. - If you use Cloudflare with the Automatic Platform Optimization (APO) feature enabled, remember that APO caches pages aggressively and must be purged separately after any on-page changes. 💬 Still Not Seeing Your Changes? If you have cleared both your WordPress cache and your CDN cache and the OTTO-deployed changes are still not visible after 30 minutes, there may be a secondary issue such as a server-level cache, a reverse proxy, or a conflict with another 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.

↩️ Rollback OTTO SEO Deployments to Stop Header Changes

🔍 Overview OTTO SEO (also referred to as OTTO SEO) can automatically deploy optimizations to your website, including changes to page headers such as H1s, H2s, and title tags. If these modifications are not what you intended, you can roll back the deployment at any time. This article explains what to expect during the rollback process and how to verify the fix has been applied across your entire website. 🎥 Video Walkthrough For a visual demonstration of the rollback process, watch this short screen recording before following the steps below: https://jam.dev/c/04026dad-be0a-498c-aa7a-15726e7d42a1 🛑 Why OTTO SEO May Be Changing Your Headers When OTTO SEO is connected to your website and a deployment is activated, it applies a set of approved or auto-generated optimizations — including header tag modifications — directly to your site's front-end. This is expected behavior when a deployment is live. Rolling back the deployment removes those changes and restores your original content. 🔄 How to Roll Back an OTTO SEO Deployment 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) from the left-hand menu. 2. Select the website project where the header changes are occurring. 3. Locate the section that lists your active deployments for that project. 4. Find the deployment that is currently live and responsible for the header modifications. 5. Use the rollback option available for that deployment to reverse the changes. You may be asked to confirm the action before it proceeds. 6. Once confirmed, OTTO SEO will begin reversing the applied changes on your website. ✅ How to Confirm the Rollback Worked After completing the rollback, take the following steps to verify that the header changes have been removed across your entire website: - Hard-refresh your browser on the affected pages (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to clear any cached content. - Check multiple page types — including your homepage, category pages, and blog posts — to confirm headers have returned to their original state. - If your site uses a caching plugin or CDN (such as Cloudflare, WP Rocket, or similar), clear your cache at the server or CDN level. OTTO SEO changes may still appear on cached pages until the cache is purged. - Return to the deployments area in OTTO SEO and confirm the deployment is no longer active. - Use a tool such as Google Search Console's URL Inspection tool to fetch and render specific pages if you want to confirm how Google sees your headers after the rollback. ⚠️ Important Considerations Before Rolling Back - Rolling back a deployment will remove all optimizations applied by that deployment, not just the header changes. Review what other changes were included before proceeding. If you need further assistance, open 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 Playbook 403 Errors and OTTO Deployment Issues

🔍 Overview Two related issues can interrupt your SEO automation workflow: a 403 permission error when launching a playbook (such as Create Press Release), and OTTO deployment changes not rendering on your WordPress site after the playbook runs. This article explains what these issues look like and what information to have ready so our team can resolve them for you quickly. ⚠️ Understanding the 403 Permission Error A 403 error means the system has blocked an action because it does not recognise you as having the required permission. This error can appear when attempting to run a playbook and will prevent the playbook from starting. Because this is a backend issue, our support team will need to investigate your specific account configuration to identify the cause and apply a fix. When contacting support, please have the following ready: - The exact name of the playbook you were trying to run (e.g. Create Press Release). - The exact error message you received, including any error code shown on screen. - The date and time the error occurred. - Whether this playbook was created by you or shared from another account. 🚀 Why OTTO Changes Are Not Showing on Your WordPress Site After OTTO deploys changes, you may find that those changes do not appear on your live WordPress site. Symptoms can include changes appearing to apply inside Search Atlas but not rendering on the live site, or being prompted repeatedly to approve the same deployment action. Because this is a backend issue, our team will need to review your account and site configuration directly. When contacting support, please have the following ready: - Your project or site name as it appears in Search Atlas. - A description of the specific changes OTTO was deploying (e.g. page type, content type). - The date and time you first noticed the issue. - Any error messages or status indicators shown in the platform. - Confirmation of which WordPress site is affected (URL). ✅ In the Meantime While awaiting a fix, you can take the following steps: - Clear your browser cache and any caching plugin active on your WordPress site, then check your live pages again to rule out a display cache issue. - Verify that the OTTO plugin is active and up to date in your WordPress dashboard under Plugins. - Check that your WordPress connection to Search Atlas has not been interrupted by reviewing your connected sites settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix the D15 Validation Check Infinite Loop

🔍 What Is the D15 Validation Check? The D15 validation check is an on-page audit rule inside OTTO SEO. When working correctly, it flags any issues it detects, you address them, and the recommendation is marked as resolved. However, some customers experience a bug where the D15 check continues to flag the same items as incomplete — even after confirming they have been addressed. This is a known issue currently being investigated by the Search Atlas engineering team. ⚠️ Why This Happens The root cause is a loop in the OTTO recommendation engine. Under certain conditions, the agent re-evaluates the same checks in a cycle without registering that the previous recommendation was completed. This can result in: - The D15 recommendation reappearing immediately after being resolved - The audit appearing stuck or resetting to a previous state - No visible feedback to confirm whether your changes were registered This behaviour is not caused by anything you have done incorrectly. The loop is a platform-side issue with how recommendations are processed and dismissed. ✅ Steps to Take Right Now 1. Confirm your changes are saved correctly. Revisit the relevant page or settings and verify that any fields flagged by the D15 check are properly filled in and saved. Take a screenshot for your records. 2. Refresh the OTTO dashboard. Close the tab, clear your browser cache, and reopen the platform. In some cases a fresh session allows the recommendation engine to re-evaluate your page cleanly. 3. Check for duplicate recommendations. Scroll through your full recommendation list to see if the D15 item appears more than once. If it does, this confirms the looping behaviour and is useful information to share with our team. 4. Do not repeatedly re-enter the same information. Making repeated edits in an attempt to resolve the flag will not fix the underlying loop and may cause additional confusion in the audit log. 📋 What to Have Ready When You Escalate Because this is a platform-side bug, our team will need to investigate on the backend. To help us resolve it as quickly as possible, please have the following ready before reaching out: - The exact name of the project or page affected - A screenshot showing the D15 recommendation appearing after you have already addressed it - Any timestamps or details about when the looping behaviour first started - Whether the recommendation appears more than once in your list If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Search Atlas & Rank Math Meta Tag Conflicts

🔍 What Is Happening? When Search Atlas and Rank Math SEO Pro are both active on your WordPress site, they can interfere with each other's meta tag output. Customers typically see one or more of the following symptoms: - Meta descriptions are dropped entirely from the page source. - Robots meta tags appear malformed (for example, conflicting directives present at the same time). - The live page still renders Rank Math's original meta values even after updating settings in Search Atlas. These issues are caused by both plugins writing to the same WordPress hooks simultaneously. Search Atlas cannot fully override Rank Math's output, and Rank Math silently wins the conflict, even when its settings appear to be inactive. ⚙️ Step 1 — Choose One Plugin to Control Meta Output Running two SEO plugins at the same time is the root cause of every conflict described above. You must designate one plugin as the single source of truth for all meta tags on your site. Option A — Use Search Atlas as your primary SEO plugin (recommended): 1. In your WordPress admin, go to Plugins → Installed Plugins. 2. Find Rank Math SEO Pro and click Deactivate. 3. Confirm that Rank Math is fully deactivated before continuing. Option B — Keep Rank Math and disable conflicting Search Atlas meta features: 1. In your WordPress admin, open the Search Atlas plugin settings. 2. Disable any meta output options (such as title, description, robots, or Open Graph settings) so Search Atlas no longer writes to those hooks. 3. Manage all meta values exclusively inside Rank Math. 🛠️ Step 2 — Clear Cached and Conflicting Meta Values After deactivating or adjusting plugin settings, stale values stored in post meta can still cause incorrect output. Follow these steps to clear them: 1. Open any affected post or page in the WordPress editor. 2. Manually re-enter your desired meta title and meta description in whichever plugin you have chosen as your single source of truth. 3. Click Save or Update. 4. Reload the page in your browser using a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). 5. Right-click the page and choose View Page Source to confirm that only one set of meta tags is present. If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.), purge its cache after completing the steps above so the corrected meta tags are served to visitors and search engines. If you need further assistance, open 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 Crawler Failures Caused by Homepage Redirects

🧭 Overview OTTO relies on a pixel installed in your website's source code to verify installation and begin crawling your site. However, certain homepage redirect configurations can prevent OTTO from detecting that pixel — even when it is genuinely present. This article explains why this happens and walks you through the steps to resolve it. ⚠️ Common Symptoms - The OTTO pixel appears in your website's HTML source code, but the installation check reports it as not detected. - Your site scan returns an error indicating the homepage could not be reached — even though your site is live and accessible. - Project creation remains in an incomplete or pending state for more than 24 hours. - OTTO may switch the project domain to a different variation than the one you originally entered (for example, from a root domain to a subdomain). 🔎 Why This Happens When OTTO attempts to verify your pixel or scan your homepage, it sends an internal request to your URL. If your server is configured to redirect that URL — for example, from http:// to https://, from non-www to www, or from your root domain to a subdomain — OTTO's crawler follows the redirect chain. During this process, one or more of the following issues can occur: - Query strings that OTTO appends to identify its own requests may get stripped by the redirect, causing the crawler to lose track of the request. - OTTO lands on a different page or subdomain than the one where the pixel is installed, so detection fails. - In some WordPress environments, redirect rules can interfere with OTTO's crawl requests in ways that place additional load on the server. These issues are rooted in how your server or WordPress configuration handles redirect rules, not in the pixel installation itself. 🛠️ How to Fix It Follow the steps below to identify and correct the redirect configuration that is blocking OTTO. 1. Confirm your canonical domain. Decide on the single domain format OTTO should use — for example, https://www.yourdomain.com. This must exactly match the domain entered in your OTTO project settings. Open your OTTO project and verify that the domain shown matches your intended canonical domain precisely. 2. Check your redirect rules. In your hosting control panel, .htaccess file, or Nginx configuration, review any redirect rules applied to the homepage. Ensure that redirects preserve the full URL including any query strings. If you use a WordPress plugin (such as Redirection or Rank Math), check whether query string stripping is enabled and disable it. 3. Preserve query strings in redirects. Update your redirect rules so that query parameters are passed through. In Apache .htaccess, use a RewriteRule that appends %{QUERY_STRING} to the destination. In Nginx, ensure your return or rewrite directives include $is_args$args in the target URL. 4. Update the domain in your OTTO project if needed. If OTTO is scanning a different domain variation than the one your pixel is installed on, update the project to use the exact domain where the pixel lives. This ensures OTTO's verification request goes to the correct destination. 5. Re-run the installation check. After adjusting your redirect configuration, return to your OTTO project and trigger a new installation check or site scan to confirm the pixel is now detected successfully. 📋 Before Escalating If you have followed the steps above and OTTO still cannot detect your pixel or complete a scan, please have the following information ready when you contact support: - Your project's domain URL as entered in OTTO. - The exact redirect rules currently applied to your homepage (for example, a copy of your .htaccess file or Nginx config block). - A description of any error messages displayed in your OTTO project. - Whether your site runs on WordPress, and if so, which redirect-related plugins are active. If you need further assistance, open 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 Schema Deploy All Button Issues

🔍 Overview The Deploy All button in OTTO SEO is designed to deploy schema and other recommended tasks across all eligible pages in a single action. However, there are known cases where it may deploy fewer tasks than expected, appear to succeed without making changes, or get stuck in a loading state. ⚠️ What to Do If Deploy All Is Not Working Because this is a known bug, the specific cause affecting your project needs to be investigated by our support team. To help us resolve this as quickly as possible, please have the following information ready before reaching out: - The name of the affected OTTO project - The URL(s) of pages where schema was not deployed - A description of the behavior you observed (for example: button shows success but nothing deployed, button stays in a loading state, or only some tasks were deployed) - The approximate date and time when you attempted the deployment - Any error messages displayed during or after the deployment attempt If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Troubleshoot OTTO SEO Pixel Not Connecting in GHL

🧭 Overview After installing the OTTO SEO Pixel in GoHighLevel (GHL), your dashboard should show the pixel as Connected within about 15 minutes on a new project. If it has been longer than that and the status still shows as unconnected, this guide will walk you through the most common causes and how to fix them. ⚡ Key Things to Know Before You Start - The OTTO SEO Pixel only needs to be installed on one page of your GHL site — it does not need to be added to every page. - Connection confirmation typically happens within about 15 minutes after a correct installation on a new project, since Search Atlas automatically checks new projects every 15 minutes. - If you prefer a visual walkthrough, a Loom video guide is available — see the section below. 🔍 Step 1 — Verify the Pixel Code Is Correctly Placed 1. In GHL, open the page where you added the pixel code. 2. Go to the page's Settings and locate the Header Tracking Code or Custom Code field. 3. Confirm the full OTTO SEO Pixel snippet is pasted there — it must be complete, with no characters missing or added. 4. Make sure the code is placed inside the <head> section, not the body or footer. 🌐 Step 2 — Confirm the Page Is Published and Live 1. Check that the page where you added the pixel is published, not saved as a draft. 2. Open the live URL of that page in your browser. 3. Right-click the page and select View Page Source. 4. Use Ctrl + F (or Cmd + F on Mac) to search for otto or your pixel ID — it should appear in the source code. 5. If you do not see it, the page may not have saved correctly. Re-paste the code, save, and republish. 🔄 Step 3 — Refresh the OTTO SEO Dashboard 1. In Search Atlas, navigate to OTTO SEO using the left sidebar. 2. Open your OTTO SEO project and go to the pixel connection section. 3. Click Check Connection or refresh the page to prompt a new verification check. 4. Wait a few minutes after refreshing before checking the status again. Note that automatic checks run every 15 minutes for projects under 2 hours old, every hour from 2–24 hours old, every 6 hours from 1–7 days old, and stop after 7 days. 🛠️ Step 4 — Use the Alternative Installation Method If the standard installation is not working, try the alternative method shown in the Loom video guide: 1. In your OTTO SEO pixel setup screen, look for the link labeled Watch Loom Video or Video Walkthrough. 2. Follow the video steps exactly — the video demonstrates an alternative way to embed the pixel in GHL that avoids common copy-paste errors. 3. After completing the steps in the video, republish the page and return to your dashboard to recheck the connection status. 🚫 Common Mistakes to Avoid - Adding the pixel to multiple pages: You only need it on one page. Adding it to many pages will not speed up detection and may cause conflicts. - Placing the code in the wrong field: In GHL, use the Header Tracking Code field specifically — avoid the body or footer code fields. - Checking too soon: Allow at least 15 minutes after a fresh installation before declaring it failed, since that's how often new projects are automatically checked. - Browser caching: If you are testing the live page, use an incognito window or clear your cache to ensure you are seeing the latest published version. ✅ How to Confirm the Pixel Is Working - The status in your OTTO SEO dashboard changes from Not Connected to Connected. - You can see the pixel ID in the page's HTML source code when you view the published page. - OTTO SEO begins populating data for that website within your project. 💬 Still Need Help? If you have followed all steps above and the pixel is still not showing as connected, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Site Creation Quota Errors

🔍 Overview When creating a new OTTO site, some customers encounter a 'quota exhausted' error even though their account appears to show available OTTO site slots. This article explains why this happens and walks you through the steps to resolve it. ⚙️ Why This Error Occurs In many cases, this error is related to your Site Audit quota rather than just your OTTO site slots. OTTO relies on Site Audit to crawl and analyse your website, so an OTTO site generally needs an available Site Audit project as well. The 'quota exhausted' error typically appears when one of the following is true: - Your Site Audit project limit has been fully used by existing projects, leaving no room for a new OTTO site to create one automatically. - Deleted or inactive OTTO sites have left behind orphaned Site Audit projects that are still counting toward your quota. - Your account was recently upgraded but the Site Audit quota has not yet synced with your new plan limits. 🚀 How to Fix the Error 1. Check your Site Audit usage. Review how many Site Audit projects are currently active across all sites in your account. 2. Remove unused Site Audit projects. If you have Site Audit projects tied to old, deleted, or unused domains, remove them to free up quota. Locate the relevant site and delete its associated Site Audit project. 3. Retry site creation. Once quota has been freed, attempt to add your new OTTO site again. 4. Verify your plan limits. If you recently upgraded your plan and the error persists, your quota may need a moment to refresh. Log out and log back in, then retry. 💡 Tips to Avoid This Error in the Future - Before adding a new OTTO site, always confirm that your Site Audit project count is below your plan's limit. - When you remove an OTTO site you no longer need, also delete its associated Site Audit project to keep your quota clean. - If you manage multiple websites, consider auditing your active Site Audit projects regularly to remove any that are outdated or no longer relevant. 📊 Understanding Your Quota Your plan defines two related limits: OTTO site slots (the number of sites you can activate OTTO on) and Site Audit project slots (the number of crawl projects allowed). If you still see a quota error after confirming free OTTO slots, check your Site Audit project count as well -- our support team can confirm exactly how the two interact on your account. 🆘 Still Seeing the Error? If you have freed up Site Audit projects and the error continues, our support team can review your account's quota state directly and resolve it on your behalf. Please have your project name and the exact error message ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 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 Incorrect Google Maps URL in OTTO Schema

🔍 Overview If your OTTO project contains a sameAs schema array with a Google Maps URL pointing to the wrong business location, this guide explains why it happens and what steps to take to get it corrected. Because the field is read-only inside the platform, resolving this issue requires action from the Search Atlas support team. ⚠️ What This Issue Looks Like You may notice this problem when reviewing your structured data or schema output for a site managed in OTTO. Common signs include: - The sameAs field in your Local Business schema contains a Google Maps URL referencing an incorrect city or region. - The Google Maps link points to a completely different location than your business address. - The field is locked, preventing you from editing it directly inside the OTTO project. 💡 Why This Happens OTTO builds and caches schema data automatically based on the business information available at the time the project is created or last synced. In some cases, an incorrect Google Maps URL can become hardcoded in the schema cache if: - The source business data contained an error at the time of the initial schema build. - A previous Google My Business listing or map entry was linked to the wrong location. - The schema cache was not refreshed after a business address or Maps URL was updated. Because schema fields in OTTO are validated and locked to protect structured data integrity, these values cannot be edited directly by users once they are set. 🛠️ How to Resolve the Issue Follow these steps to report and fix a locked incorrect Google Maps URL in your OTTO schema: 1. Confirm the correct Google Maps URL. Open Google Maps, search for your business by name and address, and copy the full, accurate URL from the browser address bar. Make sure it resolves to the correct physical location. 2. Locate your OTTO project. Find the affected site in your OTTO project list. 3. Note the domain and incorrect URL. Record the exact domain name of the affected site and the incorrect Google Maps URL currently shown in the sameAs schema field. 4. Contact support via the chat widget. Share the domain name, the incorrect URL, and the correct replacement URL with the support team. The support team will manually update the database record and rebuild the schema cache for that project. 📋 Information to Have Ready To help the support team resolve your request as quickly as possible, prepare the following before opening the chat: - The full domain name of the affected OTTO project. - The incorrect Google Maps URL currently appearing in the sameAs schema field. - The correct Google Maps URL you want to replace it with. - Any relevant context about when the mismatch was first noticed or what may have caused it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Find and Deploy Your OTTO Grader Undeployed Fixes

🤔 Why Does This Happen? You may notice a mismatch in your OTTO Grader dashboard: the summary shows a number of undeployed fixes, but when you look at each category individually, every category displays zero remaining fixes. This is a known display behaviour, not a data error. 🔎 Steps to Locate and Deploy Your Pending Fixes Follow these steps to find and act on your undeployed fixes in the Grader dashboard: 1. Open your OTTO Grader dashboard and note the total undeployed fix count shown in the summary section. 2. Check all available category sections — review every category listed in your dashboard rather than relying only on the default view, as fixes may not appear prominently in the initial summary. 3. Try a full page refresh — occasionally the summary count and category counts fall out of sync due to a display lag. Refreshing the page can resync the totals. 4. If fixes become visible, select and deploy them from within the relevant category. 📋 What to Have Ready If You Need to Escalate If the steps above do not surface the missing fixes, our support team can investigate the discrepancy at the account level. Before reaching out, please have the following ready: - Your project name — the specific project where the mismatch is appearing. - The undeployed fix count shown in your summary. - A screenshot or description of what your Grader dashboard currently displays, including which categories show zero. - Any actions you have already taken — for example, if you recently deployed a batch of fixes or made changes to your OTTO settings. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Clear Your Cache to Fix Technical Issues

🤔 Why Clearing Your Cache Helps Your browser stores copies of websites — images, scripts, and page data — in a temporary storage area called a cache. This speeds up loading times, but it can also cause problems. If your cached data is outdated or corrupted, you may experience issues such as: - Pages not loading correctly or appearing broken - Features not responding or behaving unexpectedly - Changes you made not showing up on screen - Buttons, menus, or dashboards appearing blank or misaligned - Login or session errors Clearing your cache forces the browser to download a fresh version of the page, which resolves most of these issues quickly. 🕐 When to Clear Your Cache First Before reporting a bug or contacting support, always try clearing your cache if you notice: - A feature that was working has suddenly stopped - The platform looks different from what is described in the documentation - You recently updated your account settings but the old data is still showing - You are seeing an error message after a platform update Cache clearing takes less than a minute and resolves the majority of technical issues without any further steps needed. 🌐 How to Clear Cache in Google Chrome 1. Open Chrome and click the three-dot menu in the top-right corner. 2. Select Settings. 3. Click Privacy and security in the left sidebar. 4. Select Clear browsing data. 5. Set the time range to All time. 6. Check Cached images and files. You may also check Cookies and other site data if the issue persists. 7. Click Clear data. 8. Reload the Search Atlas platform and log back in if prompted. 🦊 How to Clear Cache in Mozilla Firefox 1. Open Firefox and click the three-line menu in the top-right corner. 2. Select Settings. 3. Click Privacy & Security in the left panel. 4. Scroll to the Cookies and Site Data section and click Clear Data. 5. Check Cached Web Content and click Clear. 6. Reload the Search Atlas platform. 🧭 How to Clear Cache in Safari (Mac) 1. Open Safari and click Safari in the top menu bar. 2. Select Settings (or Preferences on older versions). 3. Click the Advanced tab. 4. Check Show Develop menu in menu bar. 5. Click Develop in the top menu bar. 6. Select Empty Caches. 7. Reload the Search Atlas platform. 🌊 How to Clear Cache in Microsoft Edge 1. Open Edge and click the three-dot menu in the top-right corner. 2. Select Settings. 3. Click Privacy, search, and services. 4. Under Clear browsing data, click Choose what to clear. 5. Set the time range to All time. 6. Check Cached images and files and click Clear now. 7. Reload the Search Atlas platform. ⚡ Quick Fix: Hard Refresh If you do not want to clear your full cache, a hard refresh bypasses the cache for a single page load. This is the fastest first step to try: - Windows / Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R A hard refresh reloads the current page while ignoring any stored cache, without affecting your other browsing data. ✅ After Clearing Your Cache Once you have cleared your cache, follow these steps to confirm the issue is resolved: 1. Close and reopen your browser. 2. Navigate back to Search Atlas and log in. 3. Return to the page or feature that was causing the issue. 4. Test the feature again to confirm it is working correctly. If the problem continues after clearing your cache and performing a hard refresh, the issue may be related to your account, a platform configuration, or a temporary service disruption. 💬 Still Experiencing Issues? If clearing your cache did not resolve the problem, our team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Troubleshooting a Disabled Continue Button

This article helps you resolve situations where the Continue button is greyed out, unclickable, or a provided link does not let you move forward. There are several common reasons this happens, and the steps below will help you pinpoint and fix the exact cause. 🔍 Common Causes - A required field on the current page is empty or contains invalid input. - The link you received has expired or was already used. - Your account does not yet meet a prerequisite (such as completing an earlier step or verifying your email). - A browser extension or cached session is interfering with the page. 🛠️ Step-by-Step 1. Check for unfilled or invalid fields. Scroll through the entire page and look for any fields highlighted in red, marked with an error message, or left blank. Fill in or correct each one before trying again. 2. Verify the link is still valid. Links sent by email or shared for onboarding steps often expire after a set period. If you received the link more than 24–48 hours ago, request a new one through the platform or contact support using the chat widget. 3. Confirm any prerequisite steps are complete. Some steps unlock only after an earlier action is finished — for example, confirming your email address or completing an onboarding stage. Return to the beginning of the flow and check that all prior steps show a completed status. 4. Clear your browser cache and cookies. In your browser settings, clear cached data and cookies, then reload the page and try the link again. Alternatively, try opening the link in a private or incognito window. 5. Disable browser extensions. Ad blockers, script blockers, and other extensions can prevent buttons from activating. Temporarily disable them and reload the page. 6. Try a different browser. If the issue persists, open the link in a different supported browser (such as Chrome or Firefox) to rule out a browser-specific problem. ✅ How to Confirm It Worked You will know the issue is resolved when the Continue button becomes fully clickable (no longer greyed out) and pressing it advances you to the next step or page without an error. If the button was part of an emailed link, successful resolution means the destination page loads completely and you can interact with its content. If you are still on the same page after clicking, scroll up to check for any new error messages that appeared after your attempt. If you need further assistance, open 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 Perform a hard refresh (Ctrl+Shift+R on Windows / Cmd+Shift+R on Mac) to clear cached state, then revisit the page from the start of the flow. Also: if you arrived via a shared/direct link, navigate to that section through the main menu instead, as skipping earlier steps can leave required state unfulfilled.

🖼️ OTTO SEO: Disable Image Schema and Remove Conflicting JavaScript

🔍 Overview OTTO SEO can automatically inject ImageObject schema markup into your WordPress pages. If OTTO generates schema using inline data:image/svg+xml URLs, Google Search Console (GSC) will flag these as Invalid Image Metadata errors because Google cannot crawl or index base64-encoded inline images. This article explains what causes this issue and how to get it resolved. ⚠️ Before You Begin - You need Administrator access to your WordPress dashboard. - You need access to your Search Atlas account with OTTO SEO activated for your domain. - GSC errors may take 24–72 hours to clear after schema is removed. This is normal. 🛠️ What This Issue Involves The root cause is OTTO SEO injecting ImageObject schema that references inline base64-encoded SVG images, which Google cannot validate. The fix requires disabling OTTO's image schema output for your domain so that these invalid entries are no longer generated. Because the exact location of image schema controls within OTTO SEO settings may vary depending on your account configuration, the specific toggle or setting name is best confirmed with the Search Atlas support team, who can guide you to the correct control for your setup and disable it on your behalf if needed. 📋 Steps to Request Resolution 1. Log in to your Search Atlas account and navigate to the OTTO SEO section. 2. Review your current OTTO settings to see if there is any schema-related configuration visible for your domain. 3. If you cannot locate an image schema setting, or if the Invalid Image Metadata errors persist after any changes you attempt, contact the Search Atlas support team directly. 4. When reaching out, have the following ready: - Your domain name (e.g., the site where OTTO SEO is activated) - A screenshot or list of the specific GSC errors you are seeing - The date the errors first appeared in Google Search Console - Confirmation of whether you have already made any changes to OTTO settings A support teammate can identify the correct schema setting for your account, disable image schema output, and confirm whether any JavaScript tag adjustments are needed on the WordPress side. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ Core Web Vitals Not Updating in OTTO Dashboard

🔍 Overview Some customers have noticed that Core Web Vitals scores in the OTTO dashboard have not refreshed, even after rescanning their site or making performance improvements. This article explains why this happens and what you can do in the meantime. ⚠️ What Is Happening Core Web Vitals data inside the OTTO dashboard is sourced from the Chrome User Experience Report (CrUX), which is Google's real-user field data collected over a 28-day rolling window. Our engineering team has identified a bug where this CrUX data is not refreshing as expected, even when a new Site Audit crawl is triggered. As a result, the scores displayed in your OTTO dashboard may appear frozen or out of date. Our team is actively working on a fix, and a resolution is being prioritised. 📊 Why Rescanning Does Not Force a Refresh It is important to understand that triggering a new Site Audit crawl does not automatically pull fresh CrUX field data from Google. The two processes are separate: - Site Audit crawl — checks your site's technical structure, links, and on-page elements. - Core Web Vitals (CrUX field data) — pulls real-user experience data that Google aggregates over a rolling 28-day period. This data updates on Google's own schedule and is fetched separately by our platform. Because of the current bug, our platform is not successfully retrieving the latest CrUX dataset even when a refresh is attempted, so the dashboard continues to show older scores. 🛠️ What to Do Right Now While the fix is being deployed, you can still monitor your Core Web Vitals performance using the following alternatives: 1. Google PageSpeed Insights — Visit pagespeed.web.dev and enter your URL to get both lab data and field data directly from Google. This gives you the most up-to-date CrUX scores available. 2. Google Search Console — Check the Core Web Vitals report in your Search Console account. This report reflects real-user field data for your entire site. 3. Chrome DevTools or Lighthouse — Run a local Lighthouse audit for lab-based performance metrics that reflect your current site state regardless of CrUX availability. 💡 What to Expect After the Fix Once the engineering fix is fully deployed, the OTTO dashboard will resume pulling fresh CrUX field data on its normal schedule. At that point, Core Web Vitals scores will update to reflect the most recent 28-day rolling window of real-user data, and any improvements you have made will be reflected in the refreshed scores once enough real-user traffic has been recorded by Google. If you need further assistance, open 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 Meta Changes Not Deploying After Plugin Deactivation

🔍 Overview If OTTO shows as connected but your meta changes are not appearing on your site after disabling a conflicting plugin such as Rank Math, the issue is almost always related to a required re-read cycle — not a connection failure. This article explains the timing requirements and the correct steps to get your meta changes deployed successfully. ⚠️ Why This Happens OTTO writes meta data directly to your site. When a third-party SEO plugin like Rank Math is active, it can override or block OTTO's meta output, causing changes to appear stuck or undeployed. Simply disabling the conflicting plugin does not immediately allow OTTO to re-apply the affected changes. After plugin deactivation, OTTO needs some time — it is not instant — to re-read your site and redeploy the queued meta changes. This re-read cycle is automatic and necessary for OTTO to detect the cleared conflict and push the correct meta data. Clearing your site cache alone will not trigger this process or speed it up. ✅ Step-by-Step Resolution 1. Disable the conflicting plugin. In your WordPress dashboard, go to Plugins, locate Rank Math (or any other active SEO plugin), and deactivate it. Only one SEO plugin should manage meta data at a time. OTTO cannot deploy its changes while another plugin holds control of the same meta fields. 2. Confirm OTTO is connected. In Search Atlas, navigate to the left sidebar and select OTTO SEO, then open SEO Automation. Verify that your site shows a connected status on the OTTO dashboard. If the status shows disconnected, reconnect before proceeding. 3. Do not retrigger or reapply changes manually yet. After deactivating the plugin, allow OTTO's automatic re-read cycle to complete. Wait some time before checking whether the meta changes have deployed — this can range from under an hour to several hours. Triggering additional changes during this window may extend the process. 4. Check your site after the waiting period. Once the re-read cycle has had time to complete, visit the affected pages and inspect the meta title and description using your browser's page source or an SEO browser extension. The changes applied by OTTO should now be visible. 5. Clear your site cache after confirming deployment. Only after you have confirmed that OTTO has successfully written the meta changes should you clear your WordPress cache, CDN cache, or any caching plugin. Clearing cache before deployment is confirmed does not help and can make it harder to verify whether OTTO's changes have taken effect. 🔌 Plugin Conflict Guidelines To prevent this issue from recurring, follow these best practices when using OTTO for meta management: - Use only one SEO plugin at a time. Rank Math, Yoast SEO, All in One SEO, and similar plugins all write to the same meta fields as OTTO. Having more than one active will cause conflicts. - Disable meta output from other plugins if you choose to keep them active. Some plugins allow you to turn off their meta title and description output without fully deactivating the plugin. If you use Rank Math for other features such as schema markup, disable only its meta and title settings rather than the whole plugin. - Do not reactivate the conflicting plugin without re-checking OTTO's deployment status. Reactivating a conflicting plugin will override OTTO's meta output again and restart the conflict cycle. 🕐 Timing Reference Use the table below as a quick reference for the OTTO re-read cycle after plugin deactivation: - Wait time: Not instant — allow OTTO some time to re-crawl before checking again - When to clear cache: After confirming meta changes are deployed, not before - When to contact support: If changes still have not appeared after a reasonable wait and your site remains connected 💬 Still Need Help? If your meta changes have not deployed after waiting the full 6 hours and your site shows as connected in OTTO, there may be a deeper configuration issue that requires manual review. If you need further assistance, open 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 Extended Crawl Times — Diagnosis and Communication

🔍 What Is a Normal OTTO Crawl Time? Most OTTO crawls complete within 15–45 minutes depending on site size and server response speed. Crawls on larger sites (5,000+ pages) or sites with slow hosting may take up to 60–75 minutes. A crawl running beyond 90 minutes is considered extended and requires escalation. ⚠️ User-Actionable Causes vs. Backend System Status Before escalating, it helps to understand whether the delay is something you can influence or whether it requires backend investigation. User-actionable causes (you can address these now): - The site has a very large number of pages — OTTO crawls every accessible URL, so sites with 10,000+ pages naturally take longer. - Slow server response times on your website — if your hosting is under load, OTTO receives pages more slowly. - A previous crawl cycle was incomplete — starting a new crawl before the last one finishes can queue delays. - Robots.txt or crawl-rate directives are throttling OTTO — check that your site does not restrict crawl frequency. Backend system causes (require Support investigation): - The crawl job is stuck in a processing queue behind other jobs. - A backend worker has stalled mid-crawl. - A system-side timeout has not yet triggered a retry. - OTTO shows an active crawl status but no new pages are being processed. Only a Support teammate with backend access can distinguish between these two categories with certainty. 🗺️ How to Check Your Current Crawl Status in the Platform 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Open the OTTO dashboard for the relevant website. 3. Look at the crawl progress indicator at the top of the page — it displays pages crawled, pages remaining, and an estimated completion time when available. 4. If the progress bar has not moved for more than 20 consecutive minutes, the crawl may be stalled rather than simply slow. 5. Note the exact time the crawl started (visible in the crawl history log below the progress bar) so you can report the duration accurately if you need to escalate. Important: The platform progress indicator reflects the last-synced status. It may lag a few minutes behind actual backend processing. A crawl that appears frozen for under 20 minutes is likely still running normally. 📋 When to Provide a Time Estimate vs. Generic Guidance Use the table below to decide the right response at each stage. - Crawl running 0–60 minutes: No action needed. Share the normal range (15–45 min for small sites, up to 75 min for large sites) and advise the customer to wait. - Crawl running 60–90 minutes with visible progress: Reassure the customer that large or complex sites can take this long. Confirm progress is still moving and give a rough estimate based on pages remaining. - Crawl running 60–90 minutes with no visible progress for 20+ min: Escalate immediately — do not offer further generic troubleshooting. - Crawl running 90+ minutes regardless of progress: Escalate immediately so a teammate can check backend queue position and provide an accurate time estimate or restart the job. Only a Support teammate with backend access can provide a specific remaining-time estimate (for example, "35 minutes remaining"). If you cannot see this in the platform UI, do not guess — escalate instead. 🚨 Escalation Criteria and Steps Escalate to the Support team when any one of the following is true: - The crawl has been running for 90 minutes or longer. - The progress bar has shown no movement for 20 or more consecutive minutes at any point during the crawl. - The crawl status shows active but the pages-crawled counter has not increased in over 15 minutes. - OTTO displays an error message or a spinning loader with no status text. When you escalate, share the following information to speed up the investigation: 1. The domain being crawled. 2. The exact time the crawl started. 3. The current pages-crawled count and total pages shown in the UI. 4. Whether the progress bar has been moving recently or appears frozen. 5. Any error messages visible on the OTTO dashboard. 💡 Tips to Prevent Extended Crawl Times - Avoid starting a new crawl while a previous one is still active — wait for full completion before re-triggering. - Ensure your website's server is not under heavy load when running an OTTO crawl (avoid scheduling during peak traffic hours). - Check that your robots.txt does not include a low Crawl-delay value that forces OTTO to slow down. - For very large sites, expect the first crawl to take the longest — subsequent crawls are typically faster because OTTO only re-processes changed pages. 🙋 Need Help Right Now? If your crawl has been running for 90+ minutes or appears stalled and you need an accurate status check or time estimate, please escalate directly to the team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix MetaSync Canonical Tags on WordPress Archive Pages

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

🗺️ Fix Google Maps Embeds in Otto Site Setup

🔍 Overview When setting up a new Otto site with a Google Business Profile (GBP) link, you may encounter a Google Embedded Map error. This happens because Otto requires a specific iframe embed code — not a standard Google Maps URL. This article walks you through generating the correct embed code and configuring it properly in your Otto site setup. ⚠️ Why the Error Occurs Otto's site builder expects a Google Maps iframe embed code to display your location map. Common causes of the error include: - Pasting a regular Google Maps URL (e.g., https://maps.google.com/...) instead of an iframe code - Using a Google Business Profile link directly - Copying a shortened or redirect URL from the browser address bar None of the above formats are compatible with the embedded map field. You must use the iframe code generated directly from Google Maps. 🛠️ How to Get Your Google Maps Iframe Embed Code 1. Go to Google Maps at maps.google.com in your browser. 2. Search for your business name or address until your location pin appears. 3. Click on your business listing to open the location panel on the left side of the screen. 4. Click the Share button (the icon with an arrow pointing outward) in the location panel. 5. In the Share dialog, select the Embed a map tab. 6. Choose your preferred map size from the dropdown menu (Medium is recommended for most Otto layouts). 7. Click Copy HTML to copy the full iframe code to your clipboard. The copied code will look similar to this: <iframe src="https://www.google.com/maps/embed?pb=..." width="600" height="450" style="border:0;" allowfullscreen="" loading="lazy"></iframe> This is the correct format Otto expects. ⚙️ How to Add the Embed Code in Otto Site Setup 1. Navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar, or go directly to /seo-automation-v3. 2. Open your Otto site setup and locate the Google Embedded Map field. 3. Paste the full iframe code you copied from Google Maps into this field. 4. Do not modify or shorten the code — paste it exactly as copied. 5. Save your changes and preview your site to confirm the map loads correctly. ✅ Quick Checklist Before You Save - The code starts with <iframe and ends with </iframe> - The URL inside the src attribute contains maps/embed — not a redirect or short link - You have not manually edited any part of the code - You are not pasting a GBP profile URL or a browser address bar URL 💡 Tips and Common Mistakes - GBP links are not embed codes. Your Google Business Profile URL is separate from the embeddable map iframe. Always generate the embed code directly from Google Maps using the steps above. - Avoid browser URL copying. The URL in your browser's address bar when viewing a location on Google Maps is not compatible with the embed field. - Check for extra spaces. Occasionally, copying from certain browsers may add a leading space before the iframe tag. Remove any whitespace before the opening < character. - Map not showing after save? Clear your browser cache and reload the site preview. Embedded maps can sometimes take a moment to render on first load. 🆘 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 a Crawler That Misses Pages Beyond the Homepage

🔍 Overview When the Search Atlas crawler only picks up your homepage and ignores the rest of your site, several different root causes could be responsible. This guide walks you through every common reason — in order of likelihood — so you can isolate and fix the problem quickly without guesswork. ⚙️ Step 1: Check Your Crawl Settings Start inside the platform before looking anywhere else. 1. Open Website Studio from the left sidebar (URL: /website-studio). 2. Select the project you want to audit. 3. Go to Crawl Settings and confirm the starting URL is set to your root domain (e.g., https://example.com), not a single page. 4. Make sure Follow Internal Links is enabled. If this toggle is off, the crawler will never leave the starting URL. 5. Save any changes and re-run the crawl. 📏 Step 2: Increase the Crawl Depth Limit Crawl depth controls how many links away from the homepage the crawler is allowed to travel. A depth of 1 means only the homepage; a depth of 2 means the homepage plus pages directly linked from it, and so on. 1. In Crawl Settings, locate the Crawl Depth field. 2. If it is set to 1, raise it to at least 3 for small sites or 5–10 for larger sites. 3. Save and re-run the crawl. If your important pages are buried several clicks from the homepage, a low depth limit is the most common reason they are missed. 🚫 Step 3: Review URL Exclusion Patterns Exclusion rules (sometimes called URL filters or blocklists) tell the crawler to skip certain paths. A pattern that is too broad can accidentally block large sections of your site. 1. In Crawl Settings, open the Excluded URLs or URL Patterns section. 2. Look for wildcard rules such as /blog/*, /products/*, or /*?* that could be sweeping up pages you actually want crawled. 3. Remove or narrow any rule that unintentionally targets your missing pages. 4. Save and re-run the crawl. ✅ Step 4: Confirm Your Domain Is Whitelisted The crawler only follows links that belong to the whitelisted domain. If your site uses subdomains (e.g., shop.example.com) or a www vs. non-www variation, those must be explicitly allowed. 1. In Crawl Settings, find the Allowed Domains or Whitelist field. 2. Add every variation of your domain that hosts content — including subdomains, www, and non-www versions. 3. Save and re-run the crawl. 🤖 Step 5: Audit Your robots.txt File A misconfigured robots.txt file on your server can instruct crawlers to skip entire sections of your site. This is a server-side issue, so you will need to check it outside the platform. 1. Visit https://yourdomain.com/robots.txt in your browser. 2. Look for Disallow rules that cover the paths where your missing pages live (e.g., Disallow: /category/). 3. If the Search Atlas crawler is listed under a specific User-agent with restrictive rules, those rules apply to it. 4. Update your robots.txt to allow the paths you want crawled, then re-run. 🗺️ Step 6: Check Your XML Sitemap The crawler uses your sitemap as a discovery aid. If pages are missing from it, they may never be found — especially if internal linking is sparse. 1. Visit https://yourdomain.com/sitemap.xml to confirm it exists and loads correctly. 2. Verify that the pages you expect to be crawled are listed. 3. If your sitemap is empty, outdated, or missing, regenerate it through your CMS or SEO plugin. 4. In Crawl Settings, enter your sitemap URL under Sitemap so the crawler can reference it directly. 🔗 Step 7: Inspect Internal Linking on the Homepage If the crawler finds links correctly but your internal pages are still missing, the homepage itself may not be linking to them — or those links may not be crawlable. - Links inside JavaScript-rendered menus or single-page application (SPA) frameworks may not be visible to the crawler. - Links using onclick events instead of standard <a href> tags are typically not followed. - Ensure key pages are reachable through standard HTML anchor links from at least one crawlable page. 🌐 Step 8: Rule Out Server-Side Blocking Some hosting environments or security plugins (e.g., Cloudflare firewall rules, rate limiters, or bot-protection services) can block crawlers by IP or User-agent before they even reach your pages. - Check your hosting control panel or CDN dashboard for any rules that might block automated traffic. - Temporarily whitelist the Search Atlas crawler User-agent if your host allows it. - If you see 403 Forbidden or 429 Too Many Requests errors in the crawl report, server-side blocking is likely the cause. 🔁 Quick Troubleshooting Checklist - Follow Internal Links toggle is on - Crawl depth is set to 3 or higher - No overly broad URL exclusion patterns - All domain variants are whitelisted - robots.txt does not block the target paths - XML sitemap is valid and entered in crawl settings - Key pages are linked via standard HTML anchors - Server or CDN is not blocking crawler traffic If you need further assistance, open 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 H1 Rendering Lag & Cache Issues

What Is This Issue? After OTTO applies an H1 optimization to your page, you may notice a brief visual glitch where the original H1 appears for a split second before switching to the optimized version. This is called a Flash of Original Content (FOOC) and is a rendering or cache issue — not a sign that OTTO's optimization has failed. Common symptoms include: - The H1 visibly changes text a moment after the page finishes loading - The H1 shown in your browser differs from what appears in the page source - The issue appears intermittently, often after a recent OTTO update - Visitors or site audits see two different H1 values depending on timing This behavior is almost always caused by a stale cache — either in Webflow, your browser, or a CDN layer — serving the old H1 while OTTO's JavaScript update is still executing on top of it. Why This Happens OTTO injects optimizations at runtime using a JavaScript snippet embedded on your site. When a visitor loads your page, the browser first renders the cached HTML (which may contain the old H1), and then OTTO's script executes and replaces the H1 with the optimized version. If the cache is stale, the gap between the initial render and the script execution becomes visible. The most common sources of a stale cache are: - Webflow's internal cache — Webflow caches published pages. If you have not republished your site since OTTO's last update, the old page HTML may still be served. - Browser cache — Your browser stores a local copy of the page. Returning visitors are especially likely to see the old version. - CDN or proxy cache — If your site sits behind a CDN or reverse proxy, those edge nodes may be serving a cached version that predates OTTO's changes. Step-by-Step Fix Work through the steps below in order. Most customers resolve the issue at Step 1 or Step 2. 1. Verify OTTO's H1 optimization is active. Log in to your Search Atlas account and confirm that OTTO is deployed on the affected site and that H1 optimization has been applied. If it has not been deployed, deploy OTTO and allow a few minutes for changes to propagate before testing. 2. Republish your Webflow site. Republish your site to your live domain. This forces Webflow to regenerate the cached page HTML with the latest content. After publishing, wait 2–3 minutes before testing. 3. Clear your browser cache. Use your browser's settings to clear cached images and files, then do a hard reload of the page to confirm the updated H1 is displayed correctly. 4. Purge any CDN or proxy cache. If your site is served through a CDN or reverse proxy, purge the cache for the affected pages through that service's dashboard so the updated HTML is fetched from origin. If you have completed all steps above and the FOOC persists, the issue may require a review of how OTTO's script is loading relative to your page's render pipeline. Please have the affected page URL and a description of the behavior ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Automatic SEO Updates Not Running

🧭 Overview If OTTO's automatic SEO updates are not running on your WordPress site, the issue is usually caused by one of four root causes: a broken plugin connection, a conflicting cache or security plugin, a misconfigured OTTO activation, or a WordPress cron failure. This article walks you through each diagnostic layer so you can pinpoint and fix the problem without needing to escalate. ✅ Before You Begin: Confirm Your Setup Baseline Answer the following questions before proceeding. Your answers will point you to the correct section below. - Is the Search Atlas plugin installed, activated, and showing a Connected status in WordPress → Search Atlas? - Does the OTTO dashboard in Search Atlas (left sidebar → OTTO SEO → SEO Automation) show any recent activity or a last-run timestamp? - Are there any error messages visible in WordPress → Search Atlas or in your browser console? - Which cache plugin are you using (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache, none)? - Do you have a security or firewall plugin active (e.g., Wordfence, Cloudflare, Sucuri)? Keep your answers handy as you work through the steps below. 🔌 Step 1: Verify the Plugin Connection to Search Atlas 1. In your WordPress admin panel, go to Plugins → Installed Plugins and confirm Search Atlas SEO is active. 2. Go to WordPress admin → Search Atlas → Settings and check that your API key is entered and the status reads Connected. 3. If the status shows Disconnected or blank, copy your API key from Search Atlas (left sidebar → OTTO SEO → SEO Automation, then navigate to your account settings) and re-paste it into the plugin settings field. 4. Click Save Changes, then refresh the page to confirm the connection status updates to Connected. 5. If the connection still fails after re-entering the key, deactivate the plugin, delete it, reinstall it fresh from the WordPress plugin directory or your Search Atlas dashboard download link, and re-enter the API key. 🤖 Step 2: Check OTTO Activation and Dashboard Activity 1. Log in to Search Atlas and navigate to left sidebar → OTTO SEO → SEO Automation. 2. Confirm that OTTO is toggled on for your target site. A grey or paused indicator means OTTO is not actively processing updates. 3. Review the activity log or last-run timestamp. If OTTO shows no activity in the past 24 hours despite being enabled, the issue is likely a delivery problem between Search Atlas and your WordPress site — not an OTTO configuration issue. 4. Check whether specific update categories (meta tags, schema, internal links) are individually enabled. Each category can be toggled independently; confirm all desired categories are active. 5. If OTTO was recently activated, allow up to 30 minutes for the first batch of updates to be pushed to the plugin. 🚫 Step 3: Identify and Resolve Cache or Security Plugin Conflicts Cache and security plugins are the most common cause of OTTO updates being blocked or silently discarded after delivery. 1. Disable your cache plugin entirely (not just clear the cache) and then trigger a manual OTTO update from the Search Atlas dashboard. Check whether the update appears on your site. 2. If the update goes through with the cache plugin disabled, the cache plugin is intercepting requests. Configure it to exclude the Search Atlas plugin endpoint from caching rules. Refer to your cache plugin's documentation for REST API exclusion settings. 3. If you use WP Rocket, go to WP Rocket → Advanced Rules and add /wp-json/search-atlas/ to the Never Cache URL(s) field. 4. If you use LiteSpeed Cache, go to LiteSpeed Cache → Excludes and add the Search Atlas REST route to the exclusion list. 5. For Wordfence or Cloudflare, check the firewall activity log for any blocked requests originating from Search Atlas IP ranges. Whitelist those IPs or create a firewall rule to allow the REST API calls through. ⏱️ Step 4: Diagnose WordPress Cron Failures OTTO relies on WordPress cron (WP-Cron) to schedule and execute updates on your server. If WP-Cron is broken or disabled, updates will queue but never run. 1. Install and activate the free WP Crontrol plugin from the WordPress plugin directory. 2. Go to Tools → Cron Events and look for any Search Atlas or OTTO-related cron events. Confirm they are scheduled and not overdue by hours or days. 3. If no Search Atlas cron events appear, deactivate and reactivate the Search Atlas plugin to re-register the scheduled events. 4. Check whether DISABLE_WP_CRON is set to true in your wp-config.php file. If it is, your host requires a real server cron job. Contact your hosting provider to set up a server-level cron that calls wp-cron.php every 5 minutes. 5. On high-traffic or managed WordPress hosts (e.g., WP Engine, Kinsta), WP-Cron is often replaced by a system cron automatically. Confirm with your host that scheduled tasks are running correctly. 🔍 Step 5: Collect Error Details for Faster Resolution If the steps above do not resolve the issue, gather the following information before contacting support. This prevents unnecessary back-and-forth and gets you to a resolution faster. - Screenshot of the OTTO dashboard in Search Atlas (left sidebar → OTTO SEO → SEO Automation) showing current status and last activity. - Any error messages from WordPress admin → Search Atlas or your browser's developer console (press F12 → Console tab). - Name and version of your cache plugin and any active security plugins. - Your WordPress version and PHP version (found in WordPress admin → Tools → Site Health → Info). - Whether DISABLE_WP_CRON is present in your wp-config.php. - A list of troubleshooting steps you have already attempted. 💬 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 Only Crawling One Page After Installation

🔍 Overview After installing OTTO on your website, the crawler should systematically visit and index all pages within your connected domain. If OTTO reports only 1 page crawled after installation, your server or security layer is almost certainly blocking the Search Atlas crawler before it can follow internal links. This article walks you through diagnosing the block and whitelisting the crawler on the most common platforms. ⚠️ Symptoms That Confirm Crawler Blocking - OTTO shows 1 page crawled and the count does not increase over time. - The crawl appears to complete unusually fast (within seconds). - Internal links on your site are not discovered or are shown as uncrawled. - Your server logs show repeated 403, 429, or 503 responses from the Search Atlas crawler user-agent or IP range. - You have recently added or updated a firewall, WAF, CDN, or bot-protection rule. If you see one or more of these signs, proceed to the diagnosis steps below. 🛠️ Step 1 — Identify What Is Blocking the Crawler Work through this quick diagnosis tree to pinpoint the source of the block before attempting a fix. 1. Check your robots.txt file. Visit yourdomain.com/robots.txt and look for any Disallow rules that could apply to all bots or to the Search Atlas user-agent specifically. If a broad Disallow: / rule exists, the crawler cannot access any page beyond the entry point. 2. Check for a WAF or bot-protection service. If your site uses Cloudflare, Sucuri, Wordfence, AWS WAF, Imperva, or a similar tool, its bot-blocking rules may be treating the Search Atlas crawler as a threat and returning a block page after the first request. 3. Check your hosting control panel. Some managed hosts (WP Engine, Kinsta, SiteGround, etc.) include built-in bot filtering that can block crawlers not on their approved list. 4. Check for rate-limiting rules. A rate limiter may allow the first request (the home page) and then drop all subsequent requests from the same IP, causing OTTO to stall at exactly 1 page. ✅ Step 2 — Whitelist the Search Atlas Crawler Once you know where the block is coming from, use the relevant instructions below to allow the crawler through. Search Atlas Crawler IP Addresses Add the following IP addresses to your allowlist in whichever platform is blocking the crawler. Always refer to your OTTO dashboard or contact our team for the most current IP list, as addresses may be updated periodically. - Navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). - Open your connected website and select OTTO Settings. - Scroll to the Crawler IP Addresses section to copy the current IP list directly from the platform. Cloudflare 1. Log in to your Cloudflare dashboard and select the affected domain. 2. Go to Security → WAF → Tools. 3. Under IP Access Rules, enter each Search Atlas IP address and set the action to Allow. 4. Optionally, create a WAF Custom Rule that matches the Search Atlas user-agent string and sets the action to Skip all security rules. Wordfence (WordPress) 1. In your WordPress admin, go to Wordfence → Firewall → Blocking. 2. Select Whitelist IPs that bypass all rules. 3. Add each Search Atlas crawler IP address and save. Generic WAF or Hosting Firewall 1. Locate the IP allowlist or whitelist section in your WAF or hosting control panel. 2. Add each Search Atlas crawler IP as a trusted source. 3. If your platform supports user-agent rules, also add the Search Atlas crawler user-agent string available in your OTTO Settings panel. robots.txt 1. Open your robots.txt file for editing. 2. Add a block explicitly allowing the Search Atlas crawler, using the exact user-agent string shown in your OTTO Settings panel, followed by Allow: /. 3. Make sure no subsequent Disallow rule overrides this permission. 4. Save and re-publish the file, then allow up to 15 minutes for the change to propagate. 🔄 Step 3 — Restart the OTTO Crawl 1. Go to OTTO SEO in the left sidebar, then open Site Audit → Overview (Website Overview). 2. Select your website to view the Website Overview page. 3. Click Recrawl Site to trigger a fresh crawl now that the IP addresses are whitelisted. ⏱️ Expected Crawl Completion Timelines Crawl completion time varies with site size and how quickly the whitelisting change propagates — smaller sites generally complete faster than very large sites, and OTTO may continue processing large sites in the background after the initial pass. If a crawl seems to be taking unusually long relative to your site's size, contact support so we can check on its progress. You can monitor real-time crawl progress from the OTTO SEO V3 dashboard. The page count will increment visibly once the block is resolved. 🚫 Common Mistakes to Avoid - Whitelisting the IP in only one layer when multiple security tools are active — check every layer (CDN, WAF, host firewall, plugin). - Forgetting to save or publish the whitelist changes before restarting the crawl. - Confusing the Search Atlas crawler with Google bot and applying rules to the wrong user-agent. - Not restarting the crawl after whitelisting — OTTO will not automatically retry until a new crawl is initiated. 💬 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 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 Troubleshooting for GoHighLevel Websites

🧭 Overview If you are using a GoHighLevel (GHL) website and OTTO is showing a "pixel not installed correctly" warning, you are not alone. This error is a known platform-specific display issue. The standard WordPress or Shopify troubleshooting steps do not apply here. This article walks you through the GHL-specific workaround that resolves the error and lets you deploy OTTO fixes without interruption. ⚠️ Why This Happens on GHL GoHighLevel manages scripts and tracking pixels differently from other website platforms. Even when the OTTO pixel is correctly placed in your GHL site settings, the Search Atlas system may still flag it as undetected due to the way GHL renders and caches custom scripts. This is a verification display issue — not a problem with your pixel code itself. ✅ Before You Begin Confirm the following before applying the workaround: - You have access to your GHL site's Settings and the Header Tracking Code field. - You have already copied your unique OTTO pixel snippet from Search Atlas. - You are logged in to Search Atlas and have navigated to OTTO SEO in the left sidebar, then opened SEO Automation inside it (URL: /seo-automation-v3) to access your OTTO dashboard. 🛠️ GHL-Specific Workaround (Step-by-Step) 1. Copy your OTTO pixel snippet. In Search Atlas, go to OTTO SEO in the left sidebar, then open SEO Automation inside it. Locate your OTTO pixel code and copy the full snippet to your clipboard. 2. Open your GoHighLevel account. Navigate to the website or funnel where OTTO is being deployed. 3. Access site tracking settings. In GHL, go to Sites → Your Website → Settings → Tracking Code (or Header Tracking Code, depending on your GHL version). 4. Paste the OTTO pixel snippet. Paste the full pixel code into the header tracking field. Make sure no extra characters or line breaks are added before or after the snippet. 5. Save and publish the changes. Click Save, then republish your GHL site so the script is pushed live to all pages. 6. Return to Search Atlas and trigger a manual recheck. In your OTTO dashboard (go to OTTO SEO in the left sidebar, then open SEO Automation inside it), locate the pixel verification section and click Recheck or Verify Pixel. Allow up to about 15 minutes for the system to detect the pixel across your GHL domain, since automatic checks run every 15 minutes for new projects. 7. Proceed with deploying OTTO fixes. Once the pixel status updates to confirmed, all OTTO fix deployment options will become available. If the status display still shows a warning but your pixel is live, you can proceed — the underlying detection is functional. 🔁 One-Time Application — Important Note This workaround only needs to be completed once per GHL website. After the pixel is correctly placed in the GHL tracking code field and verified, you will not need to repeat these steps unless you create a new site, switch domains, or reset your GHL site settings. Do not reinstall or duplicate the pixel snippet, as multiple instances of the same pixel code can cause tracking conflicts. ❓ Frequently Asked Questions - The pixel status still shows an error after following these steps. What should I do? Wait about 15 minutes and trigger the recheck again. GHL sites can have a short cache delay before newly added scripts are detectable. If the issue persists after two rechecks, contact support using the chat widget below. - Can I use the WordPress or Shopify pixel instructions instead? No. Those instructions reference plugin-based or theme-based installation methods that do not exist in GHL. Always use the steps in this article for GoHighLevel websites. - Will this affect my other GHL tracking scripts? No. Adding the OTTO pixel to the header tracking field in GHL does not interfere with Google Analytics, Facebook Pixel, or other scripts already installed there. - My GHL site uses funnels, not a standard website. Does this still apply? Yes. For GHL funnels, navigate to the individual funnel settings and add the pixel to the Funnel Settings → Tracking Code field using the same steps above. 💬 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 Stuck on 301-Redirect Domains

🔍 Overview When your domain uses a 301 redirect (for example, redirecting http:// to https://, or non-www to www, or a trailing-slash variant), OTTO's homepage discovery process can fail silently. The result is a project that stays stuck in Processing for 72 hours or longer, and a dashboard message reading OTTO not found — even though the OTTO script is correctly installed and visible in your rendered DOM. This article explains why this happens, how to confirm it is the cause, and the steps you can take right now to get OTTO running. ⚙️ Why This Happens OTTO's homepage discovery engine sends an initial request to the URL you registered during project setup. If that URL returns a 301 redirect, the crawler follows the redirect chain to reach the final destination page. Under certain server and CMS configurations — particularly WordPress sites — the redirect strips the query string that OTTO appends to its internal fetch request. This causes the crawler to land on an unexpected page, crawl 0 pages, and throw a PageImportException error internally. Because no pages are successfully crawled, OTTO cannot confirm the script installation and marks the project as unresolvable. Common redirect scenarios that trigger this issue include: - http → https redirects where the server drops query parameters - non-www → www (or www → non-www) redirects - Trailing-slash redirects (e.g., example.com/page → example.com/page/) - WordPress permalink redirects that lose incoming query strings mid-chain ✅ How to Confirm This Is Your Issue 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate your project and check its status. If it shows Processing and has been in that state for more than a few hours, or shows OTTO not found, this redirect issue is a likely cause. 3. In a browser, paste your registered domain URL into the address bar and press Enter. Watch the address bar — if the URL changes at all (protocol, subdomain, or trailing slash), a 301 redirect is active on your homepage. 4. Confirm your OTTO script is present by right-clicking your homepage, selecting Inspect, and searching the DOM for the OTTO script tag. If it appears, the script is installed correctly and the problem is the redirect, not the installation. 🛠️ Steps to Resolve the Issue 1. Identify the final, canonical URL of your homepage. This is the URL your browser settles on after all redirects complete (check the address bar). For example, if you entered http://example.com and landed on https://www.example.com/, the canonical URL is https://www.example.com/. 2. Update your OTTO project to use the canonical URL. Navigate to OTTO SEO → All Sites (SEO Automation), select your project, and open project settings, and ensure the domain registered matches the final destination URL exactly — including the correct protocol (https), subdomain (www or non-www), and trailing slash if applicable. 3. Verify your server preserves query strings through redirects. If you manage your own server or WordPress installation, check that your redirect rules (in .htaccess, Nginx config, or a redirect plugin) pass query parameters to the destination URL. A correct Apache rule looks like: RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L,QSA] — note the QSA flag (Query String Append). 4. Re-trigger homepage discovery. After correcting the registered URL or the redirect configuration, go to Left sidebar → OTTO SEO → All Sites (SEO Automation), select your project, and use the Refresh data action to restart the discovery process. 5. Wait up to 30 minutes for the new crawl to complete. If the project moves from Processing to an active state and the OTTO dashboard populates data, the issue is resolved. 🚫 What Not to Do - Do not register a URL that still redirects. OTTO must be pointed at the final destination URL, not an intermediate one. - Do not reinstall the OTTO script if it is already present in the rendered DOM — reinstalling will not fix a redirect-related discovery failure. - Do not wait longer than 24 hours after making changes without re-triggering the crawl manually. The system will not automatically retry indefinitely. 📊 Known Limitations and Fixes in Progress Our engineering team has identified and addressed several related issues: - A fix for the core PageImportException / 0 pages crawled error on reachable sites is currently in release. - A fix for WordPress redirect configurations that drop OTTO's query string is awaiting release. - Improvements to homepage detection speed (splitting JavaScript rendering from discovery) and canonical URL resolution (www vs non-www) have already been deployed. Once the remaining fixes are fully released, many of these scenarios will be handled automatically. Until then, following the manual steps above will unblock your project. 💬 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 Recognizing Deleted Articles

🔍 Why Does This Happen? When you delete an article from your website, OTTO does not automatically know the page is gone. OTTO builds its understanding of your site based on a crawl snapshot taken at a specific point in time. If that snapshot was captured before you deleted the article, OTTO will continue to reference the old URL until the site is re-crawled and the data is refreshed. This is a common occurrence after bulk content clean-ups, CMS migrations, or when pruning thin or outdated pages from your site. 🚀 How to Fix It Follow these steps to clear the stale article data and bring OTTO up to date with your current site structure. 1. Navigate to SEO Automation. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. The URL will end in /seo-automation-v3. 2. Locate the OTTO session for your site. Find the domain that is showing the deleted articles and open its OTTO session. 3. Re-crawl your site. Look for the Re-Crawl or Refresh Site Data option within the session settings. Triggering a fresh crawl tells OTTO to re-index your live pages and discard any URLs that no longer return a valid response. 4. Wait for the crawl to complete. Crawl time varies depending on the size of your site. Once finished, OTTO will update its page list automatically. 5. Review the updated page list. After the crawl completes, return to the OTTO session and confirm the deleted articles no longer appear. Any URL that returns a 404 Not Found or a redirect will be removed from OTTO's active recommendations. 6. Dismiss or ignore residual suggestions (if needed). If any stale suggestions remain after the re-crawl, use the Dismiss option next to the affected recommendation to manually remove it from your queue. 💡 Tips to Prevent This in the Future - Re-crawl after major content changes. Whenever you delete, redirect, or restructure a significant number of pages, trigger a fresh crawl in OTTO right away to keep its data accurate. - Set up proper 301 redirects. When deleting articles, redirect the old URLs to relevant live pages. This is good SEO practice and also helps OTTO correctly map your site's current structure. - Audit your content before activating OTTO. Running a crawl before you start a new OTTO session ensures recommendations are based on your most current content inventory. ⚙️ What OTTO Does With Deleted URLs Once a re-crawl is complete, OTTO automatically filters out any URL that is no longer live. Specifically: - Pages returning a 404 error are removed from the active page list. - Pages returning a 301 or 302 redirect are updated to reflect the destination URL. - Pages that have been noindexed after deletion may still appear but will be flagged accordingly. OTTO will not generate new SEO recommendations for URLs that are confirmed as non-existent after the crawl. 🆘 Still Seeing Deleted Articles? If deleted articles continue to appear even after a successful re-crawl, there may be an underlying issue with how your CMS is serving those URLs or a cached version that is still returning a 200 status code. Check your CMS and hosting cache settings to confirm the pages are fully removed at the server level. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Title Tags and OTTO Connection Status

🔍 Overview If your Search Atlas title tags have stopped appearing on your site, or your dashboard is showing a conflicting or unclear OTTO connection status, this guide will walk you through the most common causes and how to resolve them quickly. ⚙️ How OTTO Controls Title Tags OTTO is the Search Atlas AI automation engine that deploys on-page SEO changes — including title tags — directly to your website. When OTTO is fully connected and active, any title tag optimisations it generates are pushed live automatically. If the connection is interrupted or the status appears inconsistent in your dashboard, those changes may stop deploying or may be overridden by your CMS or another plugin. 📊 Check Your OTTO Connection Status 1. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 2. Locate the OTTO status indicator at the top of the page. It should display as Connected with a green indicator. 3. If the status shows Disconnected, Pending, or is missing entirely, proceed to the steps below. 🚀 Resolve a Disconnected or Unclear OTTO Status 1. Refresh the connection: On the OTTO SEO V3 page, find the OTTO connection panel and click Reconnect or Re-authorise if the option is available. 2. Verify your site is added correctly: Go to Site Explorer in the left sidebar and confirm your domain appears in the site list. If it is missing, re-add it and then return to OTTO SEO V3 to reconnect OTTO. 3. Check for a conflicting SEO plugin: Another SEO plugin on your site (such as Yoast, Rank Math, or All in One SEO) may be overriding the title tags OTTO is deploying. Disable title tag output in those plugins, or remove duplicate title tag fields to let OTTO take control. 4. Clear your site and browser cache: After reconnecting, clear your website cache (via your hosting panel or caching plugin) and your browser cache, then reload the page to confirm the title tags are now displaying correctly. 5. Confirm OTTO is active on the correct pages: Inside the OTTO SEO V3 dashboard, review which pages OTTO is enabled for. Title tags will only deploy on pages where OTTO automation is switched on. 💡 Why the Dashboard May Show Conflicting Status A conflicting status — for example, the dashboard showing Connected while title tags are not appearing — is usually caused by one of the following: - A recently changed WordPress password or API key that broke the authentication between Search Atlas and your site. - A site migration or domain change that was not reflected in your Search Atlas account settings. - A caching layer serving an older version of your page before OTTO's changes are visible. - A conflicting plugin that outputs its own title tags after OTTO writes its version, effectively overriding it. ✅ Confirm Title Tags Are Displaying Correctly 1. After completing the steps above, visit one of the affected pages in a private or incognito browser window. 2. Right-click the page and select View Page Source. 3. Search for the <title> tag and confirm it matches the optimised version OTTO generated in your OTTO SEO V3 dashboard. 4. If the title still does not match, repeat the cache-clearing step and check for conflicting plugins again. 🆘 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 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 <head> section of your site's HTML, before the closing </head> 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 Meta Tags Blocked by SSR Libraries

🧩 Overview When you deploy meta titles and descriptions through OTTO (found in the left sidebar under OTTO SEO, then SEO Automation), they are written directly into your site's HTML. However, if your site uses a server-side rendering (SSR) framework or a head-management library such as Unhead.js, Nuxt, Next.js, or Vue Meta, those libraries often re-render or overwrite the <head> section after OTTO's changes are applied. The result is that your meta tags appear correct inside Search Atlas but never show up in Google SERPs or browser tabs. ⚠️ Symptoms - Meta titles and descriptions are marked as deployed in OTTO but do not appear in live Google search results. - The browser tab still displays the old title or a generic site name. - Inspecting the page source (Ctrl + U) shows the correct meta tags, but the rendered DOM (F12 → Elements) shows different or missing values. - The issue affects multiple pages simultaneously after a framework upgrade or plugin update. - Re-deploying through OTTO does not resolve the problem. 🔍 Why This Happens SSR libraries manage the <head> element as part of their own rendering lifecycle. When your page loads, the library rebuilds the head section using its own configuration, which overwrites anything injected externally — including OTTO's meta tags. Common conflict sources include: - Unhead.js — used by Nuxt 3 and other Vue-based frameworks to manage reactive head data. - Nuxt useSeoMeta / useHead composables — define meta tags at the component level and take priority at runtime. - Next.js <Head> component or Metadata API — controls head output during server and client rendering passes. - Vue Meta — an older Vue plugin that merges and overrides head tags reactively. - React Helmet / React Helmet Async — manages document head in React SPAs and SSR apps. In every case, the root cause is the same: the SSR library has its own meta tag definition that loads after — or instead of — OTTO's injected values, causing the OTTO values to be discarded. ✅ How to Resolve the Conflict Choose the approach that matches how your site is built. If you are not sure which library your site uses, ask your developer to check the project's package.json file. 1. Remove or clear the conflicting meta definition inside the SSR library. Find every place in your codebase where the page's title or description is set — for example, inside useHead(), useSeoMeta(), <Head> components, or metaInfo objects — and delete or blank out those values. This allows OTTO's deployed values to persist without being overwritten. 2. Pass OTTO's values into the SSR library instead of bypassing it. If removing the definitions is not practical, retrieve the meta values from your CMS or a data layer populated by OTTO and feed them into your SSR library's head configuration. This keeps the library in control of rendering while using OTTO's content as the source of truth. 3. Disable or exclude OTTO injection for pages managed by the SSR library. Inside Search Atlas, navigate to OTTO SEO in the left sidebar, open All Sites (SEO Automation), then open the relevant OTTO project. Locate the pages where the conflict occurs and pause or skip meta tag deployment for those URLs. Manage their meta tags entirely through the SSR library using OTTO's recommended values as a reference. 4. Check plugin execution order if using a CMS plugin (e.g., WordPress with a Nuxt front end). Ensure the OTTO integration script or plugin loads after the SSR framework has finished its initial head render, or use a server-side hook to inject OTTO's values before the framework's first render pass. Your developer can verify this in the framework's lifecycle documentation. 🔎 How to Confirm the Fix Worked 1. Open the affected page in your browser and press F12 to open Developer Tools. 2. Go to the Elements tab and expand the <head> section. 3. Confirm that the <title> tag and the <meta name="description"> tag show the values you set in OTTO. 4. Use Google Search Console → URL Inspection to fetch a live version of the page and verify that Google reads the correct meta tags. 5. Allow 24–72 hours for the updated meta tags to appear in Google SERPs after confirmation. 🛡️ How to Prevent This in Future - Before deploying meta tags through OTTO on an SSR site, audit your codebase for any existing head-management library and document which pages it controls. - Establish a single source of truth for meta tags — either OTTO or the SSR library — and ensure your team does not mix both approaches on the same pages. - After any framework upgrade (e.g., moving from Nuxt 2 to Nuxt 3), re-test OTTO meta tag deployment on a staging environment before pushing to production, as upgrades often change how head libraries behave. - Use the Content → On-Page Audit tool (left sidebar → Content → On-Page Audit) to regularly scan live pages and verify that deployed meta tags are present in the rendered 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.

🖼️ Otto Audit AI Alt Text Not Populating Fix

🔍 Overview Otto Audit AI can generate alt text suggestions for images found during a site audit. If the suggestions fail to populate, one of several root causes may be responsible. This article covers common things to check and how to escalate effectively if the issue persists. ⚠️ Common Things to Check - Image accessibility: Otto fetches images directly from their URLs. If an image is behind authentication, on a password-protected or staging environment, or blocked by robots.txt, Otto may not be able to read it. - Broken image URLs: If an image link returns an error or does not load at all, Otto has nothing to analyse. - Audit crawl timing: Alt text suggestions are tied to the most recent crawl. If images were added to the site after the last crawl completed, they will not appear in the audit results until a new crawl is run. - Temporary processing delay: Occasionally there may be a short delay before suggestions appear after an audit completes. 🛠️ Step-by-Step Troubleshooting 1. Verify the image is publicly accessible. Open the exact image URL in an incognito or private browser window while logged out of your site. If the image does not load, check whether an authentication barrier or crawler restriction is preventing access, then re-run the audit after resolving it. 2. Confirm the image URL is valid. Paste the image URL into a browser and confirm the image loads without errors. If it does not, fix the broken link on your site and re-run the audit. 3. Re-run the Otto Audit. Navigate to OTTO SEO → Site Audit → Overview (Website Overview), locate your project, and click the Recrawl Site button. Once the crawl finishes, return to the Images section and check whether alt text suggestions have populated. 4. Wait briefly and refresh. If the audit has just completed, wait a few minutes and then refresh the page to allow processing to finish. 5. Escalate if the issue persists. If alt text suggestions still do not appear after completing the steps above, gather the following before contacting support: your project name, the specific image URLs affected, the date and time you ran the audit, and any error messages displayed in the platform. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

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

🔄 Troubleshooting OTTO SEO Schema Generation Delays

This article addresses a known display issue where page-level schema generation in the OTTO SEO tab reports as successful, but the generated schemas do not appear immediately. This is typically a delay between the backend completing the generation and the UI reflecting the result — not a failed generation. 🔍 What Is Happening When schema generation appears to complete but no output is visible in the OTTO SEO tab, there may be a delay in the UI displaying the results. The generation may have completed successfully on the backend even though nothing is shown on your screen yet. 🛠️ What to Do 1. Do not re-run the generation immediately, as the schema may already exist on the backend. 2. Wait a moment, then refresh the page and navigate back to the OTTO SEO tab for the affected domain. 3. Check whether the schema output is now visible in the OTTO SEO tab for the page(s) you targeted. 4. If the schema is still not visible after refreshing, contact our support team before retrying the generation — a member of our team can verify whether the output was saved on the backend. ✅ How to Confirm It Worked - The schema output is visible in the OTTO SEO tab for the specific page(s) you targeted. - The schema content is populated and not blank or in a loading state. - You are able to copy, edit, or implement the schema without triggering a new generation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Meta Keywords Not Saving in OTTO SEO Automation

🔍 Overview Some users in SEO Automation v3 reported that edits made to meta keywords — including manually adjusted OTTO suggested fixes — would not save. The changes appeared to apply on screen but were not retained after refreshing or navigating away. This was a confirmed platform bug, not a user error or account configuration issue. The engineering team identified and resolved it. This article explains what happened and what to do if you are still experiencing the issue. ⚙️ What Caused This Issue Our support team replicated the problem and escalated it to engineering. The confirmed issue was that manually edited OTTO suggested fixes were not saving — even though the interface appeared to accept the edits, they were never stored successfully. A related issue affecting meta keyword rendering and persistence was also identified and resolved as part of the same round of fixes. ✅ Current Status: Fix Is Live The fix for this bug has been reviewed, released, and confirmed live in production. You should now be able to edit and save meta keywords and other OTTO suggested fixes without any issues. 📋 Steps to Verify the Fix Is Working for You 1. Log in to your Search Atlas account and navigate to the OTTO section of your workspace. 2. Open the site or page where you previously experienced the issue. 3. Locate the meta keyword or OTTO suggested fix you want to edit and make your change. 4. Save the edit and then refresh the page or navigate away and return. 5. Confirm that your edit has been retained correctly. If your edits are now saving as expected, no further action is needed. 🚨 If You Are Still Experiencing the Problem If edits are still not saving after following the steps above, it is possible your browser or session is serving a cached version of the platform. Try the following before reaching out to support: - Hard refresh your browser by pressing Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. - Clear your browser cache and cookies, then log back in to Search Atlas. - Try a different browser or open the platform in a private or incognito window to rule out a browser-specific issue. - Check that you are working in SEO Automation v3 — ensure you have not inadvertently switched to a different version of the tool. After trying the above, attempt to save your meta keyword edit again and verify whether it persists after a page refresh. If the problem continues after completing all steps above, please contact our support team so we can investigate your account directly.

OTTO Agent Slow to Deploy H1 Tags

Overview Some users have reported that when asking the OTTO AI Agent to check, generate, and deploy H1 tags on specific pages, the process runs much longer than expected — sometimes appearing to stall or loop indefinitely. This article explains what steps you can take when this happens. Why This Happens Slow or stalled H1 tag deployments via the OTTO AI Agent can occur for a variety of reasons depending on your site configuration, page count, or platform conditions at the time of the request. The steps below walk you through the most common self-serve fixes before escalating to our support team. Steps to Resolve 1. Wait a few minutes before taking any action. If the OTTO Agent appears stuck, allow some time to pass — the process may still be running in the background and may complete on its own. 2. Start a new OTTO chat session. Close your current OTTO Agent chat and open a fresh session. Re-submit your H1 tag request in the new session, as the previous session may have encountered a timeout or loop that a new session will not inherit. 3. Check your site connection status. Navigate to OTTO SEO → All Sites (SEO Automation) in Search Atlas and confirm that your site is still properly connected. If the connection shows as disconnected or errored, disconnect and reconnect your site, then retry the H1 deployment request. 4. Reduce the scope of your request. Instead of asking OTTO to deploy H1 tags across all pages at once, break the request into smaller batches — for example, ask it to process 10–20 pages at a time. This reduces processing load and makes it easier to identify which pages may be causing the slowdown. 5. Re-trigger the deployment. After starting a new session and confirming your site connection, explicitly ask OTTO to re-check and re-deploy H1 tags on the specific pages that did not complete. Providing the exact page URLs in your request can help OTTO target only the affected pages. 6. Verify deployment status after each attempt. Once OTTO confirms the task is complete, navigate to the affected pages in your Search Atlas dashboard to confirm the H1 tags are showing as deployed. If a page still shows no H1 or a pending status, include that specific URL in a follow-up request to OTTO. Tips to Avoid This Issue - Keep your H1 deployment requests focused on a manageable number of pages per session to reduce processing time. - If you notice the agent is taking longer than usual, check whether there are any platform status updates or announcements that may indicate a known service disruption. Still Experiencing Slowness? If you have tried all the steps above and the OTTO Agent is still slow or failing to deploy H1 tags, please reach out to our support team via the chat icon in your Search Atlas dashboard so we can investigate the underlying cause specific to your account and configuration.

Fix Image Alt Text Generation Errors in OTTO

Overview Some users encounter a persistent error when attempting to generate image alt text suggestions in OTTO. This error can appear even after clearing your cache, using incognito mode, or switching browsers and devices — which rules out a local issue on your end. If you are experiencing this error, the steps below can help you resolve it. Because this type of issue may require investigation on the backend, contacting the support team is often the most direct path to a resolution. What You Should Try First 1. Hard refresh the page by pressing Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to ensure you are loading the latest version of the platform. 2. Try incognito or private browsing mode to rule out browser extensions or cached data causing interference. 3. Switch to a different browser (e.g., Chrome, Firefox, Edge) to confirm the error is not browser-specific. 4. Wait a short time and try again. If a recent update was deployed, a brief delay before retrying can allow changes to propagate fully to your account. 5. Attempt generation on fewer images at a time to help isolate whether the issue is specific to certain images or URLs. If only certain images fail, note which ones — this information will be important when escalating to the support team. When the Error Persists If you have completed all the steps above and the error continues, the issue requires investigation by the support team, who can review the affected OTTO project on the backend and escalate if needed. Before reaching out, note down the following: - The name of the affected OTTO project. - An example of one of the image URLs that fails to generate (copy it from your browser if possible). - Whether the error appears on all images or only specific ones. - The browser and device you are using. Providing these details upfront will help the team reproduce and investigate the issue as quickly as possible. To get help, please contact the Search Atlas support team.

🔄 Fix OTTO SEO Analysis Stale Scheduled Dates

🧭 Overview If OTTO SEO shows a next analysis date that has already passed — for example, displaying Aug 27 when today is Aug 30 — this may indicate that the scheduled analysis task did not run as expected. This article explains what information to gather and how to get support to resolve it. 🔍 What This Issue Looks Like You may be experiencing an analysis scheduling delay if: - The next scheduled analysis date shown in your OTTO SEO dashboard is in the past and has not updated. - No new analysis results have appeared despite the scheduled date having passed. - The analysis does not appear to be running or queued. This is distinct from a normal scheduling cycle where the next analysis date is today or in the future and OTTO is simply waiting for its next run. 🚨 What To Do Because OTTO SEO analysis scheduling is managed at the backend level, resolving a stale or missed scheduled date requires investigation by the support team. There is no self-serve button or setting within the platform that is confirmed to reset the scheduler. To help the support team resolve this as quickly as possible, please have the following ready before reaching out: - Your project or site name as it appears in the OTTO SEO dashboard. - The stale next analysis date currently displayed (e.g., "Aug 27"). - Today's date and how many days the date has been in the past. - Any error messages or warning banners visible on your OTTO dashboard — copy the exact wording if possible. - The last date a successful analysis did complete, if visible in your dashboard. 📋 What to Expect Once the support team investigates, they will be able to identify whether the scheduled task failed to trigger and take the necessary backend action to reset it. You do not need to attempt workarounds in the meantime, as doing so may not address the underlying scheduling 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 and Rank Math Meta Conflicts

🔍 Overview When the OTTO WordPress plugin and Rank Math SEO are both active on the same site, two known conflicts can occur: robots meta tags render in a malformed format, and meta descriptions disappear entirely from the page source. This article explains why these issues happen and what you can do right now to restore correct meta output. ⚙️ Why This Happens A confirmed conflict exists between the OTTO WordPress plugin and Rank Math SEO when both are active simultaneously. This conflict produces two problems: - Malformed robots tags: The two plugins interfere with each other's robots meta tag output, which can corrupt the combined output. - Missing meta descriptions: A conflict between the two plugins can result in the meta description tag being absent from the rendered HTML. These issues affect sites where both plugins are active at the same time. ✅ Recommended Workaround Follow the steps below to stop the conflict and restore correct meta output on your site. 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the OTTO SEO plugin and click Deactivate. 4. Open a new browser tab and visit your site. Use View Page Source (right-click → View Page Source) to confirm that: - The robots meta tag is well-formed and includes all expected directives. - The meta description tag is present and contains the correct text set in Rank Math. If deactivating the OTTO plugin alone does not restore the meta description, review your Rank Math meta description settings to ensure a value is set for the affected post type. 📋 How to Verify the Fix Is Working After applying the workaround, perform a quick sanity check on at least three representative pages (homepage, a blog post, and a category page): - Right-click the page and choose View Page Source. - Search for robots — you should see a single, well-formed robots meta tag containing all expected directives. - Search for description — you should see one meta description tag with the correct content. If either tag is still missing or malformed after deactivating OTTO, please escalate by providing your site URL, the exact malformed output from View Page Source, and the versions of both the OTTO plugin and Rank Math you have installed. If you need further assistance, open 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 Title Changes Not Updating on WordPress

🗂️ Overview When you deploy a title change through OTTO SEO, you may notice the updated title does not immediately appear on your WordPress site. This is not a bug — several common factors can delay or block the change from showing. This article explains why this happens and walks you through the steps to resolve it. ⚙️ How OTTO Applies Title Changes OTTO SEO communicates with your WordPress site through the Search Atlas plugin. When you deploy a title change, OTTO sends the update directly to your site via this connection. The change should appear promptly, but a few conditions must be met for the update to go through successfully. ⚠️ Common Reasons Title Changes Are Not Reflecting - Caching is serving an older version of the page. WordPress caching plugins (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) store a static snapshot of your page. Until the cache is cleared, visitors — and even you — will see the old title. - A conflicting SEO plugin is overriding the title. If another SEO plugin (such as Yoast SEO or Rank Math) is active and managing titles, its settings may take priority over the changes OTTO applies. - The Search Atlas WordPress plugin is outdated or disconnected. An outdated plugin version or a broken site connection can prevent OTTO from pushing changes successfully. - The deployment did not complete. If you navigated away during deployment or encountered an error, the change may not have been fully applied. 🛠️ How to Fix the Issue 1. Clear your WordPress cache. Log in to your WordPress dashboard, open your caching plugin, and purge or clear all cached files. After clearing, reload the page and check whether the updated title now appears. 2. Check for conflicting SEO plugins. If another SEO plugin is active, either deactivate it or ensure it is not set to manage title tags for the affected pages. Only one plugin should control title output at a time. 3. Update the Search Atlas WordPress plugin. In your WordPress dashboard, go to Plugins → Installed Plugins, locate the Search Atlas plugin, and install any available updates. Outdated versions may not communicate reliably with OTTO. 4. Verify the site connection in Search Atlas. In the platform, navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. Confirm that your site is connected and that OTTO is active for the correct domain. 5. Redeploy the title change. If the steps above do not resolve the issue, try redeploying the title change from the OTTO SEO V3 section. This will resend the update to your WordPress site. 6. Check the change on a different browser or device. Your local browser may be caching the old page title. Open an incognito window or a different browser to verify whether the new title is live. ✅ How to Confirm the Title Has Updated After following the steps above, use one of these methods to confirm the title change is live: - Open the page in an incognito or private browsing window and check the browser tab for the updated title. - Right-click the page and select View Page Source. Search for the <title> tag to see the exact title currently served by WordPress. - Use a third-party tool such as Google's URL Inspection tool in Google Search Console to fetch the live page and verify the title shown to search engines. 💡 Pro Tips to Prevent This Issue - After any OTTO deployment, make clearing your WordPress cache part of your standard workflow to ensure updates go live immediately. - Avoid running multiple SEO plugins simultaneously. Designate Search Atlas as the sole plugin managing on-page SEO fields to prevent conflicts. - Keep the Search Atlas plugin updated to benefit from the latest compatibility improvements and bug fixes. 🙋 Still Need Help? If you have followed all the steps above and the title change is still not appearing on your WordPress site, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚙️ Fix OTTO GSC Instant Indexing

🔍 What the error means The Plan insufficient message means your current Search Atlas subscription does not include OTTO GSC Instant Indexing. The feature cannot be enabled until your account has an eligible plan or add-on. ✅ Check your plan 1. Open the Avatar Menu (👤) from your avatar in the top-right corner. 2. Select Billing, then open the Plans & Top-ups tab. 3. Review your current subscription and available plans or top-ups. 4. Upgrade or add the required service if GSC Instant Indexing is not included. 🔗 Connect Google Search Console After confirming that your plan supports the feature, make sure the correct Google Search Console property is connected to the project. OTTO cannot activate GSC Instant Indexing without an active GSC connection and the required permissions. 1. Go to Site Metrics → Site Explorer (Manage Sites → Connect GSC Account). 2. Reconnect GSC if it is disconnected, then select the correct property. 3. Return to OTTO and enable GSC Instant Indexing again. 🔄 If the error continues Refresh the page after reconnecting GSC and try again. If the feature still shows Plan insufficient after your plan has been updated, sign out and back in to refresh account access and billing status. If you need further assistance, open 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 Scan Pending Tasks and Deployment Failures

Overview After running an OTTO scan, some tasks may remain in a Pending status even after attempting manual deployment. This article explains the most common reasons this happens and the concrete steps you can take to resolve it on your own. Why Tasks Stay Pending After an OTTO Scan Pending tasks after a scan are typically caused by one of the following: - WordPress connection issues: OTTO deploys changes directly to your site via a plugin connection. If the plugin is disconnected, outdated, or the site credentials have changed, deployment may fail and tasks will remain pending. - Insufficient permissions: The connected WordPress user account may not have the required admin-level permissions to write changes to the site. - Conflicting plugins or themes: Security plugins, caching layers, or page-builder themes can block OTTO's write requests, causing tasks to stall. - Site downtime or server errors: If your site is temporarily unavailable at the time of deployment, OTTO cannot push changes and the task stays queued. - Task dependencies: Some tasks require a parent task to be completed first. If a prerequisite task has failed, dependent tasks will remain pending until the blocker is resolved. How to Fix Pending Tasks and Manual Deployment Failures Work through the steps below in order. Most pending-task issues can be resolved without contacting support. 1. Reconnect the Search Atlas plugin to your WordPress site. In Search Atlas, go to your OTTO project and open the site connection settings. Disconnect and then reconnect your WordPress site. This refreshes the plugin token and clears stale credential errors. After reconnecting, return to the OTTO task list and retry the pending tasks by clicking the deploy/retry option next to each task. 2. Verify the connected WordPress user has Administrator privileges. Log in to your WordPress dashboard and go to Users. Confirm that the account connected to Search Atlas has the Administrator role. If it does not, update the role and then retry deployment from OTTO. 3. Temporarily disable conflicting plugins. In your WordPress dashboard, go to Plugins and deactivate security plugins (e.g., Wordfence, iThemes Security), caching plugins (e.g., WP Super Cache, W3 Total Cache), or firewall tools one at a time. After each deactivation, return to OTTO and retry the pending tasks to identify which plugin is blocking deployment. Re-enable any plugin that does not affect OTTO's ability to deploy. 4. Confirm your site is online and reachable. Visit your site in a browser and verify it loads without errors. If your host is experiencing downtime or your site returns a 500/503 error, wait for it to recover and then retry deployment in OTTO. 5. Resolve any failed parent tasks first. In the OTTO task list, look for tasks marked as Failed or Error. Pending tasks that depend on a failed parent will not deploy until the parent is fixed. Address the failed task first, then retry the dependent pending tasks. 6. Manually retry deployment. Once the steps above are complete, select the pending tasks in OTTO and use the manual deploy option to push them again. Check the task status after a few minutes to confirm they have moved out of Pending. If the Issue Persists If tasks remain pending after completing all steps above, please have the following ready when you contact support: - The name of the project or site where the pending tasks appear - The specific task names or task types that are stuck in Pending status - Any error messages you see when attempting manual deployment - Whether you have recently changed your WordPress credentials, updated the Search Atlas plugin, or made changes to your hosting environment - The approximate date and time when the issue began If you need further assistance, open 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 Shopify Pixel Duplicate Text from H1 Logo

What Is Causing the Duplicate Text? Some Shopify store owners report seeing duplicate text on their storefront after installing a tracking pixel that appears related to the H1 logo tag in their theme. This is a known issue pattern involving Shopify pixel placement and H1 logo tag conflicts. Because the specific cause and fix can vary depending on your Shopify theme and how your pixel was installed, this issue requires investigation by our support team to identify the correct resolution for your store. What to Have Ready Before Contacting Support To help our team resolve this as quickly as possible, please gather the following information before reaching out: - Your Shopify store URL and the name of the active theme you are using. - A screenshot or screen recording showing the duplicate text as it appears on your storefront, including which page it appears on (homepage, collection page, product page, etc.). - Confirmation of when the duplicate text first appeared — for example, immediately after pixel installation or after a theme update. - The exact location in your theme where you placed the Search Atlas tracking pixel, if you added it manually. - Any error messages you see in your browser console (you can open this with F12 in most browsers). Having this information ready will allow our team to identify the conflict and provide you with a verified fix specific to your setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔒 Fix OTTO Pixel Blocked by Security Plugins

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

🖼️ OTTO Alt Text Deployment — Valid Integer Error Fix

🔍 What Is This Error? When deploying alt text through OTTO, you may see an error message containing the phrase "valid integer" or similar wording about an invalid or unexpected value. This error is related to the OTTO alt text deployment process and may also coincide with issues around project dashboard visibility. This error requires engineering review and cannot be resolved by refreshing the page, clearing your browser cache, or retrying the deployment. ⚠️ How to Recognise This Specific Error You are likely experiencing this issue if all of the following are true: - You are attempting to deploy alt text for one or more images inside OTTO. - The error message includes the words "valid integer". - The error appears consistently on the same image or set of images — it does not resolve after retrying. - Other alt text deployments on different pages or images complete successfully. If the error is random, affects all images equally, or disappears on retry, see the general OTTO deployment troubleshooting article instead. 🏠 My New Project Is Also Missing From the Dashboard If you created a new project and it is not appearing on your home dashboard, this may be a related issue that also requires investigation by our team. Confirm that you are logged in to the correct workspace before escalating, then include this detail when you contact support — it helps the team investigate both issues together. 🚫 Steps That Will NOT Fix the Valid Integer Error The following actions are commonly suggested for general deployment errors but will not resolve this type of error: - Clearing browser cache or cookies - Switching browsers or devices - Logging out and back in - Retrying the deployment multiple times - Removing and re-adding the affected images manually 📋 What to Prepare Before Escalating Because this error requires engineering review, please have the following information ready when you contact support: - The exact error message text — copy and paste the full message as it appears on screen - Your project name as it appears in the platform - Whether your project dashboard is also affected (project not appearing as expected) If you need further assistance, open 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 Slots Stuck Due to Frozen Sites

What Is This Issue? Some users find that their OTTO slots show as fully used even though no active projects are visible. Deleted or deep-frozen sites may reappear in the OTTO section, and any attempt to create a new project or unfreeze an existing one results in a quota error. This is a known bug currently being resolved by the engineering team. Why This Happens When a site enters a deep freeze state, it continues to hold an OTTO slot for a set period — typically 14 days from the freeze date — before that slot is automatically released. If a site appears deleted but is still in a deep freeze cycle, it can silently occupy your quota, making it impossible to use your slots normally. A fix to allow deleting deep-frozen projects to immediately free a slot has already been completed by engineering, and additional improvements to show a clear countdown for when frozen slots will be released are currently in development. What You Should Do First 1. Open OTTO SEO → All Sites (SEO Automation) in your account and review all projects listed, including any that appear frozen or inactive. 2. Check whether any frozen sites are still occupying your slots. Even if you previously deleted a site, it may still be holding a slot during the deep freeze period. 3. If you can unfreeze a project, do so and then delete it to free that slot manually. 4. If the unfreeze or delete actions are blocked by a quota error, proceed to the steps below — our support team can add a temporary slot so you can complete the action yourself. The Workaround (Applied by Support) In confirmed cases of this bug, the support team applies a temporary workaround: one extra OTTO site slot is added to your account. This gives you the headroom needed to either unfreeze and delete a stuck project, or create a new OTTO project right away. The temporary slot is removed, and your original quota is restored, once the deep freeze period ends and the frozen slots are automatically released — typically 14 days after the last deep freeze event. Because this workaround requires a manual adjustment to your account, it cannot be completed as a self-serve step. To get unblocked as quickly as possible, contact our support team using the chat option inside Search Atlas — an agent can apply the slot addition in the same session. How to Request the Fix 1. Before reaching out, note the following so the agent can act quickly: the number of slots shown as used, the names or URLs of any frozen or reappearing sites, and the approximate date those sites were frozen or deleted. 2. Open the in-platform chat inside Search Atlas by clicking the chat widget in the bottom-right corner and typing human teammate to be connected with a member of our team. 3. Share the details above and request a temporary slot addition to unblock your OTTO quota. Agents can apply this adjustment in the same session, so have your site details ready to speed up the process. 4. Once the slot is added, return to your OTTO projects, unfreeze and delete the stuck site, or create your new project. Your quota will return to normal automatically after the deep freeze period ends — no further action is needed on your end. What Happens Next After the support agent adds the temporary slot, you will have immediate access to complete the action that was previously blocked. The frozen site will continue its deep freeze cycle and the slot it holds will be released automatically at the end of that period. You do not need to follow up with support once you have completed your unfreeze or project creation — the quota correction happens automatically. If you are still seeing quota errors after the temporary slot has been added, reply in the same chat thread and the agent will investigate further.

Brand Vault Missing After OTTO Project Deletion

🔍 What Is This Issue? If you delete an OTTO Project, your Brand Vault may stop appearing in the platform — even though it still exists. You may see an error such as 'No Brand Vault found for hostname', or find that creating a new Brand Vault for the same domain fails. This happens because the Brand Vault was linked to the deleted OTTO Project and was not automatically released when that project was removed. ⚙️ Why This Happens Brand Vaults are associated with OTTO Projects. When an OTTO Project is deleted, the Brand Vault previously linked to it can become inaccessible — it is not deleted itself, but it is no longer visible or usable through the platform UI. This was a known platform behaviour addressed in engineering fix CG-1901, which ensures that Brand Vaults are delinked from soft-deleted OTTO Projects rather than hidden alongside them. Existing affected vaults required a manual backend correction to restore access. ✅ How to Confirm You Are Affected - You deleted an OTTO Project for a domain, and afterwards the Brand Vault for that domain no longer appears. - The platform shows 'No Brand Vault found for hostname' when you try to access Brand Vault features for that domain. - Attempting to create a new Brand Vault for the same domain does not succeed or produces an unexpected result. 🚀 Steps to Resolve This 1. Confirm the affected domain name (hostname) — this is the domain for which the OTTO Project was deleted and the Brand Vault is now missing. 2. Check whether your account was created or last affected before the CG-1901 fix was deployed. If the Brand Vault is still missing today, your vault needs a one-time manual backend delink to restore visibility. 3. Before contacting support, gather the following so your ticket can be actioned immediately: your account email address, the exact hostname or domain name affected, and a note confirming that the OTTO Project for that domain was deleted prior to the Brand Vault going missing. 4. Open the live chat widget and contact our support team. Provide the hostname, your account email, and let the agent know your Brand Vault is missing after an OTTO Project was deleted. The agent will locate your account record and perform a manual backend delink of the Brand Vault from the deleted OTTO Project. 5. The support team will manually delink the Brand Vault from the deleted OTTO Project on the backend. This restores full access to your existing Brand Vault — no data is lost and you do not need to recreate anything. The team can action this quickly once the domain is confirmed. 6. After the fix is applied, return to the platform and navigate to the Brand Vault section for that domain. Verify that the vault is visible and that Brand Vault operations (such as editing or applying vault settings) complete without error. If any operations still fail, reply in the same chat thread so the team can confirm the backend change completed successfully. 💡 What Happens After the Fix Is Applied Once the Brand Vault is delinked from the deleted OTTO Project on the backend, it will reappear in the platform and all Brand Vault operations will resume normally. No data is lost during this process. If you need further help, open the live 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 Heading Optimization Failures in Elementor & Gutenberg

🔍 Overview When OTTO deploys heading optimizations (H1, H2, etc.) on WordPress sites built with Elementor or Gutenberg, you may encounter frontend rendering errors, blank sections, or deployments that appear successful but make no visible changes. This article explains the known conflict between OTTO and these page builders, and sets out what to have ready when you contact our team for assistance. ⚠️ Why This Happens OTTO heading optimization deployments can conflict with page builders like Elementor and Gutenberg. Because these builders store and render page content differently from standard WordPress post content, OTTO's heading changes may not apply correctly, may produce rendering errors, or may appear to succeed without any visible change on the live page. The exact mechanism of the conflict depends on how your specific site and page builder version are configured. ✅ How to Recognize the Issue - A heading optimization deployment reports as successful, but the updated heading text is not visible on the live page. - The page displays a rendering error, broken layout, or blank section near a heading element after a deployment. - No error message is shown in the platform, making the failure difficult to detect. 🛠️ What to Do Because this is a known compatibility issue between OTTO and certain page builder configurations, the resolution requires investigation by our support team. This is not something you can fully self-serve at this time. Before reaching out, please collect the following information so our team can investigate quickly: - Project or site name as it appears in your Search Atlas account. - Page builder in use — confirm whether the affected page was built with Elementor, Gutenberg, or another editor. - Which heading(s) failed — note the heading level (H1, H2, etc.) and the page URL where the failure occurred. - What you observed — for example: rendering error on the frontend, no visible change after deployment, or a blank section near a heading. - Timestamp of the deployment attempt (date and approximate time, including your timezone). - Any cache-clearing steps already taken — note whether you cleared your site cache (via caching plugin, hosting panel, or CDN) after the deployment. Avoid re-deploying or making additional heading changes on the affected page until our team has reviewed the issue, as further deployments may make the conflict harder to diagnose. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO AI Suggestions Quota Showing Zero Fix

What This Issue Looks Like In some cases, your OTTO AI Suggestions quota may display as 0 — even when your plan includes a higher allowance or you have been granted additional limits. When this happens, OTTO is unable to generate recommendations, effectively blocking your workflow until the quota is corrected. This is a known platform issue that has been resolved at the engineering level. However, if your account is still affected, the fix must be applied manually by our team on the backend. Why This Happens This quota display error can occur due to how AI suggestion limits are tracked and enforced at the account level. In confirmed cases, the quota counter became out of sync with the actual allowance tied to the account — showing 0 even when usage was low or limits had been increased. Engineering has addressed the underlying causes, but individual accounts may still need a backend correction applied. Steps to Take Right Now 1. Verify your quota is genuinely stuck at 0. Navigate to the OTTO section of your platform and check your current OTTO AI Suggestions usage. If the quota reads 0 and you believe your plan or granted limits should allow more, the account is likely affected by this issue. 2. Confirm your plan or limit grant is active. If you were given a temporary limit increase (for example, as part of a Summit promotion or a manual entitlement), make note of the dates and the expected allowance. This information will help our team resolve the issue faster. 3. Try a hard refresh or log out and back in. Before contacting support, clear your browser cache, perform a hard refresh (Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac), or log out of Search Atlas and log back in. In some cases this causes the quota display to re-sync. If your quota still shows 0 after logging back in, proceed to the next step. 4. Check if your OTTO AI Suggestions usage was recently reset or if a new billing cycle has started. Sometimes quotas re-sync automatically at the start of a new billing period. Log out and back into your account after your billing cycle resets to confirm whether the quota has updated. If it remains at 0 after a new cycle begins, this confirms a backend correction is needed. 5. Request a manual quota reset directly in chat — our team can apply the backend fix right away. Because the fix requires a backend adjustment, there is no further self-serve action inside the platform that will correct this. However, our support team can apply the quota reset for you quickly: open the chat in the bottom-right corner of Search Atlas, type a message such as "My OTTO AI Suggestions quota is stuck at 0 — can you reset it?", and an agent will locate your account and push the correction on the backend. When you reach out, share the following details so our team can escalate and resolve your case as quickly as possible: - Your account email or workspace name - The quota value currently displayed (0) - The allowance you expect based on your plan or grant (for example, the number of AI Suggestions included or promised) - The approximate date the quota stopped working or first appeared as 0 - Any relevant promotion, grant, or billing event you believe is connected (for example, a Summit promo code or a recent plan upgrade) What Happens After You Contact Us Once our team receives your message, they will verify your account entitlements and apply a backend quota reset. In confirmed cases, this fix is applied the same day and your OTTO AI Suggestions quota is immediately updated to reflect your correct allowance — no further action is needed on your end. After the reset you can return to OTTO and begin generating recommendations right away. If you have not heard back within one business day or your quota is still showing 0 after the reset was confirmed, reply to the same chat thread and reference your original conversation so the team can re-escalate. You can reach us anytime via the chat icon in the bottom-right corner of Search Atlas.

OTTO VisIQ Suggested Fixes Not Saving or Deploying

🔍 Overview Some users have encountered issues when working with OTTO's VisIQ Suggested fixes where edits or suggestions are not saving or deploying correctly. This issue has been investigated and resolved by our engineering team. This article explains what to do if you are still experiencing problems. ⚠️ Understanding the Issue VisIQ Suggested fix save/deploy failure: In some cases, OTTO VisIQ suggested fixes were not saving or deploying as expected. This was a confirmed bug that caused edits to fail silently on deploy. A fix has since been deployed by engineering. ✅ Step 1 — Clear Your Browser Cache and Try in Incognito If you are still seeing a save or deploy error, the first step is to rule out a browser caching issue: 1. Clear your browser's cookies and cache completely. 2. Open a new incognito or private browsing window. 3. Log back in to Search Atlas and navigate to your OTTO-enabled site's VisIQ section. 4. Attempt to save or deploy the suggested fix again. In many cases, this resolves the error immediately. If the problem persists after completing these steps, continue to Step 2. 🔄 Step 2 — Retry Saving Your VisIQ Edits The underlying bug that prevented suggested fixes from saving and deploying in VisIQ has been fixed. To confirm everything is working correctly for your site: 1. Navigate to your OTTO-enabled site and open the VisIQ section. 2. Locate the VisIQ Suggested fix you previously attempted to save or deploy. 3. Re-enter or re-apply your edit if it was not retained from before the fix. 4. Save and deploy the suggestion as normal. Your edits should now save and deploy correctly. 💡 What Was Fixed Our engineering team resolved an issue where OTTO VisIQ suggested fixes were not saving on deploy. If you attempted to save or deploy a suggested fix before this resolution was in place, you may need to re-enter and re-deploy your changes. 📬 Still Having Trouble? If you have followed the steps above and are still experiencing issues saving or deploying VisIQ suggested fixes, please reach out to our support team so we can investigate further. You can contact us directly from your Search Atlas account.

🛠️ Fix OTTO SEO Analysis Scheduling Delays

🔍 Overview If OTTO SEO Automation shows a next analysis date that has already passed — for example, the scheduled date reads Aug 27 but today is Aug 30 — and no new analysis has run, this article explains why it happens and what steps to take to resolve it. ⚙️ Why Scheduling Delays Happen OTTO SEO Automation schedules analyses based on a queue that processes sites in order. Delays can occur for several reasons: - High queue volume: During peak usage periods, the analysis queue may back up, pushing scheduled runs past their original date. - Site processing time: Larger websites with many pages take longer to crawl and analyse, which can cause the next scheduled run to slip. - Temporary system lag: Occasionally, a background sync issue can cause the displayed next analysis date to fall out of step with the actual queue position. - Account or project configuration changes: Recent changes to your project settings, domain, or connected site can pause or reset the analysis schedule. ✅ How to Check the Current Status 1. In the left sidebar, click OTTO SEO, then open SEO Automation to open the OTTO SEO Automation dashboard (URL: /seo-automation-v3). 2. Locate the affected project and review the Next Analysis date displayed on the project card. 3. Compare that date with today's date to confirm the delay is real and not a display refresh issue. 4. Try a hard browser refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to rule out a cached date being shown. 🚀 Steps to Resolve the Delay 1. Refresh the page after a few minutes. Queue processing is automatic, and the analysis may complete shortly after you notice the delay. 2. Manually trigger a new analysis if the option is available on your plan. Open the project inside OTTO SEO → All Sites (SEO Automation) and look for a Scan or Run diagnostics button to force the process to start immediately. 3. Verify your project is active. Confirm the project status shows as active and is not paused. A paused project will not run scheduled analyses. 4. Check for recent changes. If you recently updated the target URL, changed the domain, or modified project settings, the schedule may have reset. Review your project configuration and confirm all required fields are saved correctly. 5. Wait up to 24 hours. In cases of high queue volume, analyses that are a few days overdue will typically complete within 24 hours as the queue clears. 💡 Tips to Prevent Future Delays - Avoid making frequent changes to project settings, as each change can interrupt or reset the analysis queue for that project. - Monitor your scheduled analysis dates regularly inside the OTTO SEO V3 dashboard so you can spot and address delays early. - If you manage multiple projects, note that all projects share the same processing queue — large or complex sites may occasionally push smaller ones back. 🆘 Still Seeing a Delay? If you have followed the steps above and the analysis still has not run after 24 hours, our team can investigate the queue status for your specific project. If you need further assistance, open 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 Atlas Brain 400 Errors With OTTO SEO

🧠 What Is This Error? When you send a custom prompt to Atlas Brain and receive a persistent 400 error, this is almost always caused by a missing OTTO SEO project for your domain. Atlas Brain requires an active OTTO SEO project to process tool calls and generate responses. Without one, every request fails at the API level before Atlas Brain can do any work. This is not a system-wide outage. It affects only domains that have not yet been connected to an OTTO SEO project. ⚠️ Why Does This Happen? Atlas Brain uses your OTTO SEO project as its source of context — it pulls your domain data, crawl results, and SEO settings to power its responses. If no active project exists for the domain you are working with, Atlas Brain has no context to reference and returns a 400 Bad Request error instead of a response. Common situations where this occurs include: - You are using Atlas Brain for the first time on a domain that has never had an OTTO SEO project created. - A previous OTTO SEO project was deleted or disconnected from the domain. - You are testing Atlas Brain on a new domain you recently added to your account. ✅ How to Fix It: Create an OTTO SEO Project The resolution confirmed by our support team is to create an OTTO SEO project for your domain. To do this, navigate to the OTTO SEO section of the platform and create a new project for the domain you are working with. Once the project has been created and is set up for your domain, return to Atlas Brain and re-send your custom prompt. The 400 error should no longer occur. 🔍 How to Confirm the Error Is Resolved After creating the OTTO SEO project, return to Atlas Brain, select the same domain, and send a prompt. If Atlas Brain returns a response instead of a 400 error, the issue is resolved. If you still see a 400 error, confirm that the OTTO SEO project has been created for the correct domain. If you need further assistance, open 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 Page Load Failures Blocking Internal Links

🔍 Overview If a page refuses to load inside Search Atlas — even after clearing your cache — you may find yourself locked out of the Internal Links update feature. This guide walks you through the most effective fixes, step by step, so you can get back to optimizing your site without delay. ⚠️ Common Causes of Page Load Failures Before jumping into fixes, it helps to understand what typically triggers this issue: - Browser cache or cookies serving a stale or corrupted session - Browser extensions (ad blockers, privacy tools) interfering with platform scripts - Unstable internet connection causing incomplete page loads - Outdated browser version lacking support for platform features - Temporary platform hiccup affecting a specific page or session 🧹 Step 1: Clear Cache and Cookies Properly A basic cache clear sometimes misses cookies that store broken session data. Follow these steps for a thorough reset: 1. Open your browser settings and navigate to Privacy & Security (or equivalent). 2. Select Clear browsing data. 3. Choose All time as the time range. 4. Check both Cached images and files and Cookies and other site data. 5. Click Clear data, then close and reopen your browser. 6. Log back into Search Atlas and attempt to load the page again. 🌐 Step 2: Try a Different Browser or Incognito Mode If clearing the cache does not resolve the issue, test in a clean environment: - Open an Incognito or Private window in your current browser and log in to Search Atlas. - If that does not work, try a different browser entirely (e.g., switch from Chrome to Firefox or Edge). - If the page loads successfully in a different browser, the problem is tied to your original browser's settings or extensions. 🔌 Step 3: Disable Browser Extensions Ad blockers, VPNs, and privacy extensions frequently block scripts that Search Atlas needs to render pages correctly. 1. Open your browser's extension or add-on manager. 2. Temporarily disable all extensions. 3. Reload the Search Atlas page. 4. If the page now loads, re-enable extensions one at a time to identify the culprit, then keep it disabled while using Search Atlas or add the platform to its allowlist. 🔄 Step 4: Force a Full Page Refresh A hard refresh bypasses locally cached files without requiring you to clear your entire cache: - Windows/Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R Attempt this two or three times. If the page loads on any attempt, you can proceed to update your internal links normally. 🌍 Step 5: Check Your Internet Connection An unstable connection can cause partial page loads that appear as failures. Try the following: - Run a quick speed test to confirm your connection is stable. - If you are on Wi-Fi, move closer to your router or switch to a wired connection. - Restart your router if speeds are significantly lower than expected. - Once your connection is stable, reload the page in Search Atlas. 📊 Step 6: Accessing Internal Links After the Page Loads Once the page loads successfully, you can update your internal links through the On-Page Audit feature: 1. In the left sidebar, click Content. 2. Select On-Page Audit. 3. Choose the page you want to work on. 4. Navigate to the Internal Links section within the audit results. 5. Apply your updates and save your changes. 💡 Tips to Prevent This Issue in the Future - Keep your browser updated to the latest version for the best compatibility with Search Atlas. - Periodically clear your cookies and cache — once a week is a good habit. - Add Search Atlas to your ad blocker's allowlist so extensions never interfere again. - If you are working in a team, ensure all users are accessing the platform on a supported, up-to-date browser. 🆘 Still Experiencing the Issue? If you have worked through all the steps above and the page still will not load, our support team is ready to 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 Common Website Studio Issues and Credits

🔍 Overview Website Studio is a powerful AI-powered page builder inside Search Atlas. Like any actively developed tool, it has experienced some known issues that may affect your workflow — including unexpected menu changes, revert functionality that removes content, incorrect credit displays, and blog preview images not loading. This article explains each issue and what to do if you are still affected. ⚠️ Known Issues and Current Status The following types of issues have been reported by customers and investigated by our engineering team. If you are experiencing any of the following, please escalate so our team can investigate and restore credits or fix the issue for your account: - Deployment errors or pages failing to generate: Some users have encountered errors that prevent pages from deploying or generating correctly, even when their account appears to have sufficient credits. - Credits being consumed unexpectedly: Some users have reported credits being deducted for actions that should not consume credits, or credit balances appearing incorrect in the interface. - Revert functionality removing content unintentionally: The revert feature restores a previous version of your page and will remove any content added after that point. Use it only when you intentionally want to roll back to a prior state. - Blog preview images not loading: Some users have reported that blog preview images do not display correctly within Website Studio. 🔄 What to Do If You Experience These Issues If you encounter any of the issues listed above or notice unexpected behaviour in Website Studio, follow these steps: 1. Refresh the platform. Many display-related issues, such as incorrect credit balances, are resolved with a hard refresh of your browser. 2. Check your credit balance. Review your credit balance within the platform to confirm whether credits have been deducted unexpectedly. 3. Avoid using the Revert function unless necessary. The revert feature restores a previous version of your page and will remove any content added after that point. Only use it when you intentionally want to roll back to a prior state. 4. Re-attempt page generation with a refined prompt. If a generation error appears, try simplifying or rephrasing your prompt and generate again. 5. Escalate to our support team. If the issue persists, contact our team with your project name, a description of the issue, the exact error message (if any), and the approximate timestamp when the problem occurred. Our team can investigate your account and restore credits where applicable. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🛠️ Fix OTTO Loading Errors and Audit Delays

🔍 Understanding the Issue If OTTO fails to load or your site audit appears stuck, you are not alone. These issues are usually caused by one of a few common factors: an incomplete site audit, browser-related conflicts, or a temporary sync issue within the platform. This article walks you through the most effective fixes so you can get OTTO running as quickly as possible. ⚙️ Step 1 — Check Your Site Audit Status OTTO requires a completed site audit before it can fully load and activate. If your audit is still in progress or has not been triggered, OTTO will not initialise correctly. 1. In the left sidebar, click OTTO SEO, then open Site Audit and select All Audits. 2. Check whether a site audit is shown as In Progress or Pending. 3. If no audit has been run yet, click Run Site Audit and wait for it to complete fully before attempting to load OTTO again. 4. If an audit is already in progress, allow it to finish — audit times vary depending on site size, but most complete within 5 to 30 minutes. Important: Do not refresh the page repeatedly while an audit is running. Excessive refreshing can interrupt the process and cause further delays. 🌐 Step 2 — Clear Your Browser Cache and Cookies Cached data and outdated cookies are a frequent cause of loading errors inside Search Atlas. Clearing them takes less than two minutes and resolves the majority of OTTO loading issues. 1. Open your browser settings (usually accessible via the menu in the top-right corner). 2. Navigate to Privacy and Security or Clear Browsing Data. 3. Select Cached images and files and Cookies and other site data. 4. Set the time range to All time and confirm the deletion. 5. Close and reopen your browser, then log back into Search Atlas. 6. Return to OTTO SEO in the left sidebar, open Site Audit, and select All Audits to attempt to load OTTO again. 💡 Step 3 — Try a Different Browser or Incognito Mode Browser extensions such as ad blockers, VPNs, or script managers can interfere with how OTTO loads. Testing in a clean environment helps identify whether the issue is browser-specific. - Open a new Incognito or Private window in your current browser and log in to Search Atlas. - Alternatively, try a completely different browser (for example, switch from Chrome to Firefox or Edge). - Navigate to OTTO SEO in the left sidebar, open Site Audit, and select All Audits to check whether OTTO loads correctly. If OTTO loads successfully in incognito mode or a different browser, the issue is likely caused by an extension or a corrupted browser profile. Disable your extensions one by one to identify the culprit. 🔄 Step 4 — Refresh Your OTTO Connection Sometimes a simple session reset is all that is needed to restore the connection between OTTO and your site data. 1. Log out of Search Atlas completely using the Avatar Menu (👤). 2. Wait 30 seconds, then log back in. 3. Go to OTTO SEO in the left sidebar, open Site Audit, and select All Audits. 4. If prompted to reconnect or reactivate OTTO, follow the on-screen instructions to complete the setup. 📊 Step 5 — Verify Your Site Is Properly Connected OTTO can only function correctly when your site is connected and verified within the platform. A missing or broken site connection will prevent OTTO from loading. 1. In the left sidebar, click Site Metrics (Site Explorer) to go to /site-explorer/list. 2. Confirm that your website appears in the list and shows an Active status. 3. If your site is missing or shows an error, re-add it by clicking Add New Site and completing the verification steps. 4. Once the site is confirmed as active, return to OTTO SEO in the left sidebar, open Site Audit, select All Audits, and try loading OTTO again. ✅ Quick-Reference Checklist - Site audit is fully completed — not in progress or pending. - Browser cache and cookies have been cleared. - OTTO loads correctly in incognito mode or a different browser. - You have logged out and back in to refresh your session. - Your site is active and verified under Site Metrics (Site Explorer). 🆘 Still Experiencing the Error? If you have worked through all of the steps above and OTTO is still not loading, our team is ready to 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. When you reach out, please have the following information ready to help us resolve your issue faster: your website URL, the browser and version you are using, the exact error message displayed (a screenshot is helpful), and the current status of your site audit. Additional Notes Navigate directly to https://dashboard.searchatlas.com/site-audit/list to check audit status. Audit runs automatically when you connect a project to OTTO; no action required while it runs. Large sites can take the full 24 hours.

Fix Missing Pages in OTTO SEO On-Page Optimization

🧭 Overview After re-crawling your site, you may notice that certain pages — especially important money pages — do not appear in the OTTO Grader (Onpage Optimizations) section of OTTO SEO. This is often caused by those pages being orphaned (no internal links pointing to them) and also missing from your sitemap. Since OTTO SEO discovers pages by following internal links during a crawl and by reading sitemap files, pages that are neither linked nor included in a sitemap are invisible to the crawler by default. This article explains why this happens and walks you through the steps to get those pages indexed and optimized inside OTTO SEO. ❓ Why Orphaned Pages Are Not Detected OTTO SEO crawls your site the same way search engines do — by starting from your homepage, following internal links from page to page, and discovering URLs listed in your sitemap files. If a page has no internal links pointing to it and is not included in a sitemap, the crawler has no path to reach it, so it never appears in your OTTO Grader (Onpage Optimizations) queue, regardless of how many times you re-crawl. Common reasons a page becomes orphaned include: - The page was created but never added to a menu, category, or internal linking structure. - Internal links to the page were removed during a site redesign or content update. - The page was recently published but has not yet been linked from any other page on the site. ⚙️ How to Fix Orphaned Pages There are two approaches: fix the underlying orphan issue so OTTO SEO can discover the page naturally, or escalate to the support team for a backend review of your crawl settings. 1. Add internal links to the orphaned page, or include it in your sitemap. Link to the page from at least one other crawlable page on your site — such as your homepage, a relevant blog post, a category page, or your site navigation — or add the URL to your sitemap. Once an internal link exists or the page appears in the sitemap, the next crawl will discover and include the page. 2. Re-crawl your site after adding internal links or updating your sitemap. Trigger a new crawl of your OTTO SEO project and allow it to complete fully before checking OTTO Grader (Onpage Optimizations) under OTTO SEO → Overview (or OTTO SEO → All Sites → select a site → OTTO Grader) for the updated page list. 3. Verify the page is not blocked. Confirm the orphaned page is not excluded by your robots.txt file or a noindex tag, as either of these can prevent OTTO SEO from processing the page even when it is linked. 4. Escalate if pages are still missing. If the page remains absent after adding internal links or sitemap entries and re-crawling, contact the support team. When you reach out, have your project name, the exact URLs of the missing pages, and the date of your most recent crawl ready so the team can investigate your crawl settings on the backend. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Pages Flipping Between Indexable and Not-Indexable

🧭 What This Article Covers If you notice a page alternating between Indexable and Not-Indexable status in Search Atlas, this guide walks you through the most common causes and the steps to resolve them permanently. ⚠️ Why Indexability Status Keeps Changing Indexability flipping is almost always caused by one or more conflicting signals on the page or server. Google re-crawls pages on its own schedule, and each crawl can return a different result if the underlying signals are inconsistent. Common root causes include: - Conflicting noindex directives — a noindex meta tag exists in some page states (e.g. logged-in vs. logged-out, A/B test variant, or CMS draft mode) but not others. - Inconsistent canonical tags — the canonical URL changes between crawls, making Google treat the page as alternately authoritative or duplicate. - robots.txt blocking and unblocking — deployment pipelines or CDN rules that toggle robots.txt entries across environments (staging vs. production). - Conditional server responses — the server returns a 200 for some user agents and a 403/404/503 for Googlebot, depending on caching or bot-detection rules. - JavaScript rendering delays — a client-side script injects a noindex tag after the initial HTML loads, so the directive appears only when JS renders fully. - CMS workflow settings — publishing, scheduling, or preview modes that temporarily alter meta robots values. 🛠️ Step-by-Step Troubleshooting 1. Audit the page in Search Atlas On-Page Audit. Navigate to Left sidebar → Content → On-Page Audit, enter the affected URL, and check the Indexability section. Note every flag raised — pay particular attention to meta robots, canonical, and HTTP status warnings. 2. Inspect the live page source. Open the URL in a browser, right-click, and select View Page Source. Search for noindex, nofollow, and canonical. Then repeat the check using a tool that renders JavaScript (such as Google Search Console's URL Inspection → Test Live URL) to see the rendered DOM. Compare both versions. 3. Check your robots.txt. Visit yourdomain.com/robots.txt and confirm the affected URL or its directory is not disallowed. If you use separate staging and production environments, verify the correct robots.txt is being served in production. 4. Review server response codes. Use Google Search Console's URL Inspection tool to see the HTTP response Googlebot receives. If it differs from what a browser sees, investigate your CDN, WAF, or bot-detection configuration. 5. Check for A/B testing or personalisation scripts. If you run split tests or personalised content, ensure the control variant — and every variant — does not conditionally inject a noindex tag. Use the Fetch as Google option in URL Inspection to confirm what Google actually sees. 6. Audit your CMS publishing workflow. In WordPress, Shopify, or similar platforms, check that draft, scheduled, or preview states cannot be accessed by Googlebot. Restrict preview URLs with a password or IP allowlist rather than a noindex tag on the live URL. 7. Stabilise the canonical tag. Ensure the canonical tag on the page always points to the same, final URL — including consistent use of www vs. non-www, HTTP vs. HTTPS, and trailing slashes. 8. Re-run On-Page Audit after each fix. Return to Left sidebar → Content → On-Page Audit and re-audit the URL to confirm all indexability flags are resolved before requesting re-indexing. ✅ Confirming the Fix Once you have resolved the conflicting signals, take these final steps to accelerate stabilisation: - Submit the URL for re-indexing via Google Search Console → URL Inspection → Request Indexing. - Monitor the page's indexability status in Search Atlas over the following 7–14 days to confirm it stays consistently Indexable. - If you made changes to robots.txt, re-submit your sitemap in Google Search Console so Googlebot picks up the updated rules promptly. 💡 Prevention Tips - Use a staging subdomain with HTTP authentication rather than a noindex tag to protect pre-production pages. - Add indexability checks to your pre-deployment QA checklist so meta robots and canonical tags are verified before every release. - Schedule regular On-Page Audits in Search Atlas to catch any regressions early. 🙋 Still Need Help? If you have followed all the steps above and the page indexability is still flipping, our team is ready to investigate with you. If you need further assistance, open 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 Project Errors After WordPress Migration

🔍 Overview When you migrate a website from WordPress to Website Studio, your existing OTTO SEO project may stop working correctly. This mismatch can cause broken tracking, errors, and project failures. Because resolving this requires backend intervention, this article explains what is happening and what to have ready when you contact our team. ⚠️ Why This Happens OTTO SEO projects are tied to a specific site configuration at the time they are created. When you migrate from WordPress to Website Studio, the underlying site structure and tracking endpoints change. The old OTTO project does not automatically update to reflect the new setup, which can lead to: - Errors when OTTO tries to communicate with the old WordPress installation - Broken internal links and tracking scripts that reference the old site - Project failures if the old and new configurations come into conflict 🚫 What Not to Do Before contacting support, avoid these common mistakes that can make the problem worse: - Do not delete the old OTTO project immediately — deleting it without proper backend cleanup can cause conflicts and corrupt site-level data - Do not create a new OTTO project before the existing issue is resolved — running two projects against the same domain can multiply errors - Do not attempt to reconnect the OTTO widget on the WordPress side — your site has moved to Website Studio and the WordPress connection is no longer valid 📋 What to Have Ready Before Escalating Because this issue requires backend action by our team, please gather the following information before reaching out so we can resolve it as quickly as possible: - The name of the affected OTTO project - The domain that was migrated (both the old WordPress domain and the new Website Studio domain, if different) - The exact error message or error code you are seeing - The date and approximate time the migration took place - Any steps you have already attempted If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix OTTO Pixel Logo and Text Glitches on Wix

🔍 What Is Happening? If your Wix site is showing unexpected changes to your logo, headings, or other text elements after installing the OTTO Pixel, this is a known issue that requires investigation by the Search Atlas support team. Because the root cause can vary by site configuration, there is no single self-serve fix available at this time. ⚠️ Do Not Remove the OTTO Pixel Do not remove the OTTO Pixel from your Wix site in an attempt to fix this issue. Removing the Pixel will disconnect OTTO from your site, and pixel-served changes will stop showing (changes written directly into the site's CMS can remain). 🛠️ What to Prepare Before Contacting Support To help the support team investigate and resolve your issue as quickly as possible, please have the following ready when you reach out: - The exact URL of the Wix page or pages where the logo or text changes are occurring. - Screenshots or screen recordings that clearly show the unexpected changes. - The date and approximate time when you first noticed the issue. - Confirmation of whether the OTTO Pixel is currently installed and active on your site. - Any recent changes you made to your Wix site or OTTO settings before the issue began. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Duplicate URLs in OTTO After Slug Changes

🧭 Overview When you change a page's URL slug, both the old and new versions can sometimes appear in Google search results — even after setting up a redirect and clearing your cache. This happens because search engines may still hold a cached reference to the old URL. This article explains what typically causes duplicate URL issues after a slug change, and what information to have ready when contacting our support team for account-specific guidance. ⚠️ Why This Happens A duplicate URL issue after a slug change is typically caused by one or more of the following: - Google's crawl delay: Search engines can take days or weeks to fully deindex the old URL, even after a redirect is in place. - Redirect not registered: If the old slug still exists in your site's records, it may conflict with the new one. - Missing or incorrect canonical tag: If the canonical tag on your new page still references the old URL, Google will treat both as valid versions. - Sitemap not updated: An outdated sitemap can keep the old URL active in the index. 📋 What to Have Ready Before Contacting Support Because duplicate URL issues after slug changes can involve account-specific OTTO configurations, our support team will need the following details to investigate and resolve your situation: - Your project name in OTTO where the slug change was made. - The old URL (before the slug change) and the new URL (after the slug change) — exact full URLs, not just the slug segment. - When the slug change was made — the approximate date and time. - A description of what you are currently seeing — for example, both URLs appearing in search results, or the old URL still being indexed. - Any steps you have already taken — such as clearing your cache or updating your sitemap — and what the outcome was. Having these details ready will allow our team to review your specific OTTO configuration and provide targeted guidance as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO Pixel, Subdomains, AI Quota & Alt Tags

🧭 Overview This article covers four interconnected OTTO issues that are often reported together. Work through each section that applies to your situation. 📡 OTTO Pixel Detection: Why Your Pixel May Show as Not Installed Even if your OTTO pixel is firing correctly in Google Tag Manager (GTM), the Search Atlas platform may still display a Not Installed status. This is expected behaviour and does not mean your pixel is broken. Why this happens: OTTO verifies pixel installation by cross-referencing data collected during a completed site audit. The pixel status will not update to Installed until a full site audit cycle has finished processing. What to do: 1. Confirm the pixel tag is published and firing in GTM using GTM Preview mode or a browser tag inspector. 2. Navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3) and open your OTTO project. 3. Check whether a site audit is currently running or queued. If a previous audit has not completed, the pixel status will remain pending. 4. Trigger a new site audit if none is in progress. Audit completion typically takes 2–24 hours depending on site size. 5. Once the audit completes, return to the OTTO dashboard. The pixel status should update automatically within 1 hour of audit completion. Important: Do not remove and reinstall the pixel tag if GTM is already firing it correctly. Re-installation is unnecessary and will not speed up detection. 🌐 Setting Up OTTO Projects for Subdomains OTTO treats each subdomain as a separate project. A pixel installed on www.example.com will not be detected for a project configured against blog.example.com, even if both are on the same root domain. Architecture requirements: - Create a dedicated OTTO project for each subdomain you want to optimise. - Each project requires its own pixel installed on the corresponding subdomain. - Site audits run independently per project, so subdomain audits do not share credit or progress with the root domain project. Steps to set up a subdomain project: 1. Go to OTTO SEO in the left sidebar and open SEO Automation. 2. Click Add New Project and enter the full subdomain URL (e.g., https://blog.example.com). 3. Copy the pixel code generated for this new project and install it exclusively on the subdomain — do not reuse the pixel from your root domain project. 4. Publish the tag in GTM (or add it directly to your subdomain's <head>), then run a fresh site audit for the subdomain project. If you manage multiple subdomains, repeat this process for each one. ⚡ AI Generation Quota: Limits, Top-Ups & Upgrade Paths OTTO's AI content and automation features draw from a shared AI generation quota tied to your Search Atlas subscription plan. When quota is exhausted, AI-powered actions (such as generating meta descriptions, titles, or content suggestions) will pause until quota is restored. How quota works: - Quota resets automatically on your monthly billing date. - Quota is consumed across all OTTO SEO V3 features, including OTTO suggestions, bulk AI writing, and automated fixes. - You can monitor your remaining quota from Avatar → Billing → Plans & Top-ups (Billing) under the Total Quota list. Quota limits by plan tier: - Starter: 25,000 AI words per month - Growth: 100,000 AI words per month - Pro: 300,000 AI words per month Topping up mid-cycle: If you exhaust your quota before your billing date, you have two options: 1. Purchase a quota top-up add-on — available in blocks directly from your billing settings. Top-up blocks are added instantly and do not affect your renewal date. 2. Upgrade your plan — if you regularly exhaust quota, upgrading to the next tier is more cost-effective than recurring top-ups. To purchase a top-up or upgrade, navigate to the top-right corner (avatar) → Billing (Plans & Top-ups tab) and select the relevant option. Changes take effect immediately. 🖼️ Alt Tag Detection Failures: Why OTTO Flags Already-Fixed Images If OTTO is reporting missing alt tags on images where you have already added alt text, the issue is almost always a recrawl timing delay, not a detection error. Why OTTO still shows the flag: OTTO's alt tag checks are based on the most recent completed site audit. If you added alt text after the last audit ran, OTTO has not yet seen the updated markup and will continue displaying the old finding until the page is recrawled. CMS-specific considerations: - WordPress, Webflow, and similar CMS platforms sometimes cache rendered HTML. Even after you save alt text in the CMS, the live page may serve cached content without the alt attribute for several hours. - For JavaScript-rendered images, alt attributes added via JS may not be read by the crawler. Ensure alt text is present in the static HTML or the server-side rendered output, not injected client-side after page load. Steps to verify and resolve: 1. Open the affected page URL directly in a browser and use View Page Source (not browser DevTools) to confirm the alt attribute is present in the raw HTML. 2. If the alt text is visible in the source, the fix is confirmed on your end. You now need to trigger a recrawl. 3. Go to OTTO SEO in the left sidebar, open SEO Automation, then navigate to your OTTO project and initiate a new site audit. 4. Allow up to 7 days for a full recrawl cycle to complete across large sites. Most standard sites recrawl within 24–72 hours. 5. Once the audit completes, return to the OTTO issues list. The alt tag flag should be cleared automatically. If the flag persists after recrawl: Re-check the raw HTML source to confirm the alt attribute is genuinely present and not empty (alt="" is treated as decorative and will still trigger a flag if OTTO expects descriptive alt text). Make sure alt text is descriptive and contains at least a few meaningful words. 💬 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 AI Malformed Headings With Quotation Marks

🔍 What Is This Issue? Some customers notice that OTTO AI generates page headings that include quotation marks or placeholder text such as "Optimized H2 Heading" instead of clean, publish-ready copy. These malformed headings are not intentional and should not appear in your final content. This article explains why this happens and what you can do to resolve it. 💡 Why Does This Happen? Malformed headings with quotation marks or placeholder text typically occur for one of the following reasons: - Incomplete AI generation: OTTO's content generation was interrupted mid-process — for example, by a slow network connection, a browser timeout, or navigating away from the page before generation finished. - Ambiguous or missing page context: If the target page lacks a clear title, meta description, or focus keyword, OTTO may fall back to generic placeholder structures while it waits for more context to generate accurate headings. - Cached draft content: A previous incomplete generation run may have saved a partial draft. When OTTO resumes, it can sometimes surface that cached output instead of starting fresh. - Template token bleed: In rare cases, an internal prompt template token is exposed in the output instead of being replaced with real content. This is a known edge case that our engineering team actively monitors. ⚙️ How to Fix Malformed Headings 1. Navigate to OTTO AI. In the left sidebar, click OTTO SEO, then open Site Audit, and select Page Explorer. 2. Locate the affected page. Find the page that contains the malformed headings in the Page Explorer list. 3. Clear and regenerate. Open the page's heading suggestions, delete any heading that contains quotation marks or placeholder text, and click Regenerate to prompt OTTO to produce a fresh version. 4. Verify your focus keyword is set. Before regenerating, confirm that the page has a focus keyword assigned. OTTO relies on this to produce contextually accurate headings. If it is missing, add it and then regenerate. 5. Check your page title and meta description. Ensure both fields are filled in. Sparse page context is a common trigger for placeholder output. 6. Accept or edit the new suggestion. Review the regenerated heading. If it looks correct, accept it. If you prefer custom wording, click the edit icon to adjust the text before applying it to the page. 🚫 How to Prevent This in the Future - Always set a focus keyword before running OTTO on a page. This gives the AI the context it needs to generate specific, accurate headings. - Stay on the page until the generation progress indicator completes. Navigating away early can interrupt the process and leave partial output. - Use a stable internet connection when running bulk OTTO optimizations. Timeouts during large batches are a common cause of incomplete generation. - Review suggestions before applying. OTTO shows a preview of every heading before you publish. Make it a habit to scan for any text that looks generic or includes punctuation marks where there should be none. - Refresh and retry if generation stalls. If the progress indicator freezes for more than 30 seconds, refresh the page and rerun the generation for that specific page rather than the entire batch. 📊 When to Escalate If you regenerate a heading multiple times and it continues to include quotation marks or placeholder text, this may indicate a deeper configuration issue with that specific page or a temporary platform-side anomaly. In that case, make a note of the affected page URL and the exact heading text that was generated — this information will help our team investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Deployed Content Not Appearing on Live Site

🔍 Overview After approving and deploying OTTO recommendations, the Search Atlas dashboard may show a Deployed status while the changes are not yet visible on your live website. Installation Diagnostics may also flag unverified deployment errors. This article explains why this happens and walks you through the steps to resolve it. ⚠️ Why This Happens The Deployed status in the OTTO dashboard reflects that Search Atlas has sent the approved changes — it does not always confirm that your live site has received and applied them. Several factors can break the sync between the dashboard and your website: - WordPress plugin disconnection: The Search Atlas or OTTO WordPress plugin may have lost its authenticated connection to the platform. - Plugin version mismatch: An outdated plugin version may not be able to process the incoming deployment correctly. - Caching layers: Server-side, plugin-based, or CDN caches can serve old versions of your pages even after changes have been applied to the database. - Hosting or firewall restrictions: Some hosting environments block outbound or inbound API calls, preventing OTTO from writing changes to your site. - Theme or plugin conflicts: A third-party plugin or active theme may be overriding the changes OTTO is attempting to apply. ✅ Step-by-Step Troubleshooting 1. Verify the WordPress plugin is active and connected. Log in to your WordPress admin panel, go to Plugins → Installed Plugins, and confirm the Search Atlas plugin is active. Then return to your OTTO dashboard and check that the site connection shows a green Connected status. 2. Update the Search Atlas WordPress plugin. In your WordPress admin panel, go to Plugins → Installed Plugins and check for any available updates to the Search Atlas plugin. Install the latest version and then re-run the OTTO deployment. 3. Re-authenticate the site connection. Inside the OTTO dashboard, locate your connected property, disconnect it, and reconnect it using a fresh API key or reconnection flow. This resolves token expiry issues that can silently block deployments. 4. Clear all caching layers. Clear the cache in your WordPress caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), your hosting control panel, and your CDN (such as Cloudflare). After clearing, revisit your live site to check whether the changes now appear. 5. Run Installation Diagnostics. Inside the OTTO dashboard, open Installation Diagnostics and review each line item. Resolve any items flagged as Unverified or Error before attempting to redeploy. 6. Temporarily disable conflicting plugins. Deactivate other SEO or optimisation plugins one at a time to identify any plugin that may be overriding OTTO's changes. Recheck the live site after each deactivation. 7. Redeploy the affected items. Once the connection is confirmed and caches are cleared, return to the OTTO dashboard, select the affected recommendations, and redeploy them. Confirm the changes are now visible on the live site. 💡 Prevention Tips - Keep the Search Atlas WordPress plugin updated whenever a new version is released. - Clear your site cache immediately after every OTTO deployment to avoid stale page delivery. - Check Installation Diagnostics after each major deployment batch to catch errors early. - Avoid running multiple SEO plugins simultaneously, as conflicting meta or schema output can cause unexpected behaviour. 🆘 Still Need Help? If you have followed all the steps above and your OTTO deployments are still not reflecting on the live site, our team can investigate the connection logs and deployment records for your specific property. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Audit AI Alt Text Not Populating

🔍 Overview When using OTTO Audit AI to generate alt text suggestions for images, some customers find that the AI suggestions fail to appear or the field remains empty. This guide walks you through the most common causes and how to resolve them quickly. ✅ Before You Begin: Quick Checklist Before troubleshooting, confirm the following: - You are navigating via Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). - Your OTTO session is active and fully loaded — look for the green status indicator next to your site. - The images you are targeting are indexed within OTTO's audit scope (i.e., they were detected during the most recent site audit). - Your browser is up to date and you are not using a browser extension that may block scripts (such as an ad blocker). 🚧 Common Causes and Fixes Work through each of the following scenarios in order. Most customers resolve the issue within the first two steps. 1. Audit has not completed or is still processing. OTTO must finish a full site audit before alt text opportunities are surfaced. Navigate to OTTO SEO → SEO Automation and check the audit status at the top of the dashboard. If the audit shows In Progress, wait for it to complete, then refresh the page and try again. 2. No images with missing alt text were detected. If all images on the audited pages already have alt text, OTTO will have no items to populate suggestions for. Scroll through the audit results under the Image Optimization section to confirm whether any alt text tasks are listed. If none appear, your images may already be optimised. 3. The AI suggestion button is not being triggered correctly. Click directly on the individual image task row to expand it, then look for the Generate with AI button within the expanded view. Clicking the button at the top-level list view without expanding the row first can cause the suggestion to appear to fail. 4. Session timeout or authentication issue. Log out of Search Atlas completely, clear your browser cache, log back in, and navigate back to OTTO SEO → SEO Automation. Re-open the audit and attempt to generate alt text again. 5. Browser or network interference. Try generating alt text suggestions in an incognito or private browser window. Disable any browser extensions temporarily. If the suggestions populate in incognito mode, a browser extension is likely the cause. 6. Audit data is stale. If the audit was run more than a few days ago, the data may no longer reflect the current state of your site. Re-run the audit by selecting Recrawl Site within OTTO SEO → Site Audit → Overview (Website Overview), wait for it to complete, and then attempt to generate alt text suggestions again. ⚙️ How to Re-Run an Audit 1. Navigate to Left sidebar → OTTO SEO → Site Audit → Overview (Website Overview). 2. Select the site you are working on from the site selector at the top of the page. 3. Locate the Recrawl Site button and confirm the action. 4. Wait for the audit to reach 100% complete — this may take a few minutes depending on site size. 5. Once complete, open the Image Optimization section and click on an image task row to expand it. 6. Click Generate with AI to trigger the alt text suggestion. 💡 Tips for Best Results - Ensure images are hosted on your domain or a CDN that OTTO can access. Images blocked by robots.txt or requiring authentication cannot be processed. - AI-generated alt text works best when your page content is rich — OTTO uses surrounding page context to create relevant suggestions. - After accepting a suggestion, deploy changes via the OTTO one-click deploy feature to push alt text updates live without touching your code. 🆘 Still Not Working? If you have followed all the steps above and alt text suggestions are still not populating, 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.

OTTO Schemas Stuck in Review — Fix Deployment Issues

🔍 What Is This Issue? Some users find that schemas generated by OTTO become stuck in a Review status and cannot be deployed. When you attempt to deploy them, the process runs indefinitely and fails — sometimes causing you to lose credits by regenerating the same schemas repeatedly. This issue has been investigated and fixed by the Search Atlas engineering team. Multiple underlying causes were identified, including a validation error that incorrectly blocked valid schemas from deploying, and a pipeline bug affecting schemas on pages that had no review or rating data. Both have been resolved in platform updates. ⚙️ Why This Happens - A schema validation bug was incorrectly flagging valid schemas and preventing deployment. - Product pages with no review or rating data caused certain schema types to get stuck in Review with no fields to correct. - A broader schema pipeline issue affected AI generation, schema importing, validation, and deployment across multiple domains. All of these issues have been patched. If you are still experiencing stuck schemas, the steps below will help you resolve them. 🚀 How to Resolve Stuck Schemas 1. Refresh the page and check schema status. After the recent platform fixes, some schemas that were previously stuck may now show as deployable. Reload your OTTO session and review the current status of your schemas before taking further action. 2. Attempt deployment again. Try deploying the schemas that were previously stuck. In many cases, the engineering fixes applied to the platform will allow previously stuck schemas to deploy successfully without any additional steps on your end. 3. Avoid repeated regeneration. If schemas are still showing as stuck, do not keep regenerating them. Each regeneration consumes credits and will not resolve an underlying platform-side issue. Contact support instead so the team can manually deploy the pending schemas and escalate any credit loss on your behalf. 💡 Tips to Avoid Wasting Credits - Do not regenerate schemas that are stuck — regeneration should be a last resort only after confirming the platform-side issue is resolved. - If a schema is stuck with no fields to correct and no clear error message, this is a platform-side issue and regenerating will not fix it. Reach out to support instead. - Keep an eye on your schema quota after any deployment attempts that failed, and report unexplained credit loss to the support team so it can be reviewed and escalated. 📬 Still Experiencing This Issue? If your schemas remain stuck after following the steps above, please contact the Search Atlas support team via the chat widget in your dashboard. The team can manually deploy pending schemas and investigate any credit loss caused by the issue.

🔍 Fix OTTO SEO Analysis Stuck in Progress

🧭 Overview If your OTTO SEO analysis appears frozen on Analysis in progress or your Google Search Console (GSC) data appears disconnected inside Recommendations, this is a known bug that requires investigation by our technical team. The issue may relate to a processing delay or a GSC integration sync failure on the backend. This article explains what to expect and how to escalate effectively. ⚠️ Common Symptoms - The OTTO SEO analysis remains stuck on Analysis in progress for an extended period without completing. - Google Search Console shows as connected in your account settings but appears disconnected or missing inside the Recommendations section. - GSC-related data does not appear or refresh as expected within OTTO SEO. 🛠️ What Is Happening This is a backend bug. The analysis stall and GSC disconnection within Recommendations are not caused by anything you have done incorrectly. They occur due to an internal processing or integration failure that cannot be resolved through self-serve steps alone. Our team needs to investigate the issue on your specific project. 📋 How to Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact name of the project or site where the analysis is stuck. - The approximate time the analysis started and when it appeared to stall. - Whether Google Search Console is shown as connected in your account settings. - Any error messages or status indicators you can see on screen (screenshots are helpful). If you need further assistance, open 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 Meta Descriptions on WooCommerce Pages

🔍 Overview If OTTO is successfully deploying meta titles and descriptions on your homepage and blog posts but not on WooCommerce product pages, you are not alone. WooCommerce product pages use a custom post type that requires a specific configuration inside OTTO before deployments take effect. This article walks you through the most common causes and the steps to resolve them. ⚙️ Why This Happens WooCommerce product pages are registered as a custom post type (product) rather than standard WordPress pages or posts. OTTO's deployment settings are scoped by post type, so if the product post type is not explicitly enabled, OTTO will skip those pages during deployment — even when everything else appears to be working correctly. Additional reasons meta data may not appear on WooCommerce product pages include: - A conflicting SEO plugin (such as Yoast SEO or Rank Math) is overriding OTTO's output for the product post type. - The WooCommerce product pages were not included in the initial OTTO site crawl. - OTTO deployment has not been re-run after the product post type was enabled. - A caching plugin or server-level cache is serving a stale version of the page. ✅ Step-by-Step Fix 1. Open OTTO SEO. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. This opens the OTTO SEO dashboard at /seo-automation-v3. 2. Check post type settings. Inside OTTO, locate the deployment or site settings panel and confirm that the product post type is toggled on. If it is disabled, enable it and save your changes. 3. Verify there are no plugin conflicts. If another SEO plugin is active on your WordPress site, make sure it is not set to manage meta data for WooCommerce products. Only one plugin should control meta output per post type. Disable meta management for the product post type in the conflicting plugin, or deactivate the plugin entirely if OTTO is your primary SEO tool. 4. Re-crawl your WooCommerce product pages. Return to the OTTO SEO dashboard and trigger a new crawl so that product pages are discovered and indexed within OTTO. 5. Re-deploy meta data. After the crawl completes, run a new OTTO deployment targeting your product pages. OTTO will now write the meta titles and descriptions to the correct post type. 6. Clear your cache. In your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache) or your hosting control panel, purge the full-site cache. Then reload a product page and use your browser's View Page Source option to confirm the meta tags appear inside the <head> section. 🔎 How to Confirm the Fix Worked After completing the steps above, verify that the deployment was successful: - Open any WooCommerce product page in your browser. - Right-click anywhere on the page and select View Page Source. - Use Ctrl + F (or Cmd + F on Mac) and search for meta name="description". - Confirm that the correct description written by OTTO is present in the source code. If the meta title and description now appear in the page source, the fix was successful. Changes may take 24–72 hours to be reflected in Google Search results. 💡 Pro Tips - Whenever you add a new custom post type to your WordPress site, revisit OTTO's post type settings to make sure it is included in future deployments. - Use the Meta Generator tool (left sidebar → Content → Meta Generator) to bulk-create optimised meta titles and descriptions for all your WooCommerce products before deploying with OTTO. - After any major WooCommerce update, re-run an OTTO crawl to catch any post type or URL structure changes. 🆘 Still Need Help? If you have followed all the steps above and OTTO meta descriptions are still not appearing on your WooCommerce product pages, If you need further assistance, open 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 <head> 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 <head> 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 </head> 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.

🔍 OTTO Scan Pending Tasks Troubleshooting Guide

🧭 Overview After running an OTTO scan, some tasks may remain in a Pending status instead of completing automatically. This can happen for a variety of reasons related to your site setup, content, or permissions. This guide explains what to do if tasks stay pending and what to prepare when escalating to our support team. ❓ Why Do Tasks Stay Pending After an OTTO Scan? OTTO automates SEO fixes across your site, but certain conditions can prevent tasks from moving out of a pending state. Possible reasons include: - Missing images or missing alt text: OTTO may flag images that lack alt text, but completing these fixes may require manual input in your CMS before the task can be resolved. - CMS permission restrictions: OTTO may not have sufficient access rights to write changes directly to your content management system, which can block automatic deployment. - Unsupported page types: Certain page templates, dynamically generated pages, or password-protected content may not be compatible with OTTO's automated deployment. 🖼️ Resolving Pending Tasks for Missing Images and Alt Text If OTTO has flagged image or alt text tasks as pending, these typically require manual action in your CMS. General steps to resolve them include: 1. Review your OTTO task list to identify which tasks are in a pending state and note the affected URLs. 2. Go to the affected page in your CMS and locate the image flagged by OTTO. 3. Add a descriptive, keyword-relevant alt text value to the image. 4. Save and publish the change in your CMS. 5. Return to OTTO and re-run the scan for that URL to check whether the fix has been detected. Repeat this process for each pending image or alt text task. If tasks remain pending after completing these steps, escalate to our support team as described below. 🚫 Manual Deployment Failures: What to Prepare for Support If tasks continue to fail or return to a pending status after your attempts to resolve them, our support team will need to investigate on the backend. To help us assist you as quickly as possible, please have the following ready before reaching out: - Your project name and the domain associated with the OTTO scan. - The specific task names or URLs that remain in a pending or failed state. - Any exact error messages displayed when you attempt manual deployment. - The date and approximate time the scan was run or the failure occurred. - Details about your CMS, any active SEO plugins, or third-party tools that may interact with OTTO. If you need further assistance, open 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 Duplicate Scripts and Intermittent Deployments

🔍 What Is Happening? If your OTTO deployments appear to switch on and off without any action on your part, or if optimizations seem to apply inconsistently across your site, the most common cause is duplicate OTTO scripts installed in your Cloudflare Worker. When two copies of the script run simultaneously, they can conflict with each other, producing unpredictable behavior and intermittent functionality. ⚠️ Why Duplicate Scripts Occur Duplicate scripts typically appear in Cloudflare Workers for one of the following reasons: - OTTO was connected to Cloudflare more than once — for example, after a reconnection attempt while the original integration was still active. - A manual script was added to Cloudflare at the same time as an automatic OTTO deployment. - A previous OTTO configuration was not fully removed before a new deployment was initiated. - Multiple team members independently set up the Cloudflare integration without coordinating. 🛠️ What to Do If You Suspect Duplicate Scripts Because duplicate OTTO scripts in Cloudflare Workers require careful identification and removal to avoid breaking your site, this issue needs to be reviewed by our support team. To help us resolve it as quickly as possible, please have the following ready before reaching out: - The name of the affected OTTO project or website - A description of the intermittent behavior you are seeing (e.g., deployments switching on and off, optimizations not applying consistently) - The approximate date and time when the issue started - Any error messages you have encountered - Whether multiple Cloudflare connections or manual script additions were made to this project 🔄 How to Prevent This in the Future Follow these best practices to avoid duplicate scripts recurring: - Never reconnect Cloudflare while an active OTTO integration already exists. Always fully remove the existing integration before setting up a new one. - Coordinate with your team so that only one person manages the Cloudflare integration for a given OTTO project at a time. - Avoid manually adding scripts to your Cloudflare Worker if OTTO is handling deployments automatically. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 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 CSP Blocking Your OTTO Pixel and GTM

🧩 What Is This Issue? Your OTTO pixel may show as Engaged in the Search Atlas dashboard, yet changes still fail to push to your site. A common cause is a Content Security Policy (CSP) — a browser-level security header — that blocks external scripts, network requests, or tracking pixels from loading on your pages. This is a client-side browser issue, not a server-side crawler or bot-blocking problem. Whitelisting IPs or adjusting bot-protection rules will not resolve it. You need to update your CSP headers to explicitly allow Search Atlas domains. 🔍 CSP vs. Crawler IP Blocking — Know the Difference These are two separate systems and require different fixes: - Crawler IP blocking (403 errors): Your server refuses requests from Search Atlas crawlers. Fix by whitelisting Search Atlas IP ranges in your firewall or WAF settings. - Content Security Policy (CSP) blocking: Your browser refuses to load or communicate with external scripts and endpoints. Fix by adding Search Atlas domains to your CSP header directives. This is the issue described in this article. 🌐 Which Domains Do You Need to Whitelist? The wildcard *.searchatlas.com covers all current and future Search Atlas subdomains, including dashboard.searchatlas.com and bots.searchatlas.com. Using the wildcard is the recommended approach so you do not need to update your CSP each time a new subdomain is introduced. Add the following entries to your CSP header: - script-src: Allows Search Atlas GTM and pixel scripts to execute in the browser. Add *.searchatlas.com. - connect-src: Allows the pixel to send data back to Search Atlas endpoints via XHR or Fetch requests. Add *.searchatlas.com. - img-src: Allows tracking pixels loaded as 1×1 image beacons. Add *.searchatlas.com. If your CSP is managed via an HTTP response header, your updated directives should look similar to this example: script-src 'self' *.searchatlas.com; connect-src 'self' *.searchatlas.com; img-src 'self' *.searchatlas.com; If you also use a meta http-equiv CSP tag in your HTML, apply the same domain additions there. Note that connect-src and some directives are not supported in meta tags — use HTTP headers for full coverage. ✅ Step-by-Step: Applying the CSP Fix 1. Open your server, CDN, or hosting control panel where HTTP response headers are managed (for example, Cloudflare, Nginx, Apache, or your CMS security plugin). 2. Locate your existing Content-Security-Policy header. 3. Add *.searchatlas.com to the script-src, connect-src, and img-src directives. Do not remove any existing trusted domains. 4. Save and deploy the updated header configuration. 5. Open your browser's developer tools (F12), navigate to the Console tab, and reload your page. Confirm there are no remaining CSP violation errors referencing searchatlas.com. 6. Check the Network tab to verify that GTM and pixel requests to searchatlas.com domains return a 200 status rather than being blocked. 📋 Verify GTM Script Placement A correct CSP alone is not enough if your GTM snippet is not placed properly on the page. Confirm the following: - The GTM script tag is placed immediately after the opening <head> tag on every page. - The GTM noscript iframe is placed immediately after the opening <body> tag. - No other script or plugin is stripping or deferring the GTM tags before the CSP evaluation occurs. If you manage your site through a CMS such as WordPress, use an official GTM integration plugin to ensure correct placement and avoid tag removal during theme updates. 🗺️ Reprocess Your Sitemap After CSP Updates Once your CSP is updated and the pixel is confirmed loading correctly in the browser, trigger a sitemap reprocess inside Search Atlas so OTTO can re-evaluate your pages with the pixel now active: 1. In the left sidebar, go to Site Metrics (Site Explorer). 2. Locate your project and open its settings. 3. Resubmit or reprocess your sitemap to prompt a fresh crawl and allow OTTO to detect the correctly firing pixel across all indexed URLs. Changes pushed by OTTO will only apply to pages that are successfully crawled after the pixel is verified as active. 🛠️ Quick Troubleshooting Checklist - Pixel shows Engaged but changes not applying: CSP is the most likely cause — follow the steps above. - CSP updated but errors persist: Check for a separate Content-Security-Policy-Report-Only header that may indicate additional blocked resources. - Changes applied but not visible on site: Clear your CDN or server-side cache after OTTO pushes updates. - Wildcard not supported by your setup: Add dashboard.searchatlas.com and bots.searchatlas.com as explicit entries to each directive. 💬 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 Engaged on GoDaddy

🧭 Overview If you have installed the OTTO pixel on a GoDaddy website builder template and the platform still shows the pixel as not engaged, standard WordPress troubleshooting steps will not apply to your setup. GoDaddy's website builder is a standalone drag-and-drop platform — it does not use plugins, theme files, or a WordPress dashboard. This article walks you through the correct fix for GoDaddy-hosted sites. ⚠️ Before You Begin Confirm the following before proceeding: - You are using GoDaddy Website Builder (also called GoDaddy Websites + Marketing), not a WordPress site hosted on GoDaddy. - You have already installed the OTTO pixel code in your GoDaddy site's header or footer settings. - The OTTO dashboard at OTTO SEO → All Sites (SEO Automation) (left sidebar → OTTO SEO → All Sites (SEO Automation)) still shows the pixel status as Not Engaged after several minutes. If you are using WordPress — even if it is hosted on GoDaddy — please refer to the standard OTTO pixel troubleshooting article instead. 🔍 Why This Happens on GoDaddy Templates GoDaddy's website builder handles custom code snippets differently from WordPress. When pixel code is pasted into the header or footer section, the builder can occasionally save a malformed or incomplete version of the script. This means the pixel fires incorrectly or not at all, even though it appears to be installed. The most reliable fix is to fully remove the existing pixel code and re-add it as a clean paste. 🛠️ Step-by-Step Fix: Delete and Re-Add the Pixel 1. Copy your OTTO pixel code. In Search Atlas, navigate to the left sidebar and select OTTO SEO → All Sites (SEO Automation). Locate your OTTO pixel code and copy the full script to your clipboard. Do not modify it. 2. Log in to GoDaddy. Go to godaddy.com, sign in, and open your Website Builder editor for the relevant site. 3. Open Website Settings. In the GoDaddy editor, click Settings (usually found in the left panel or top navigation), then select Website or SEO / Tracking depending on your GoDaddy plan version. 4. Find the existing pixel code. Look for a Header Code, Footer Code, or Custom Code field. You should see the OTTO pixel script already pasted there. 5. Delete the existing pixel code entirely. Select all text in the code field and delete it. Make sure the field is completely empty — do not leave any partial script tags or whitespace. 6. Save the empty field. Click Save or Apply to confirm the removal. This step is important; skipping it can cause the old code to persist. 7. Paste the pixel code fresh. Click back into the same code field and paste your OTTO pixel code directly from your clipboard. Do not retype it manually. 8. Save again. Click Save or Apply to store the new code. 9. Publish your site. In the GoDaddy editor, click Publish to push the changes live. The pixel will not be detectable until the site is published. 10. Verify in Search Atlas. Return to OTTO SEO → All Sites (SEO Automation) in Search Atlas and wait up to 5 minutes for the pixel status to refresh. It should now display as Engaged. ✅ Confirming the Pixel Is Active Once the steps above are complete, you can do a quick browser check to confirm the pixel is firing: - Visit your published GoDaddy site in a browser. - Right-click the page and select View Page Source. - Use Ctrl+F (or Cmd+F on Mac) to search for otto or the beginning of your pixel script. - If the script appears in the source, the pixel is correctly embedded and should register as engaged in Search Atlas within a few minutes. 🚫 Common Mistakes to Avoid - Not publishing after saving. GoDaddy saves changes to a draft state. The pixel is only live — and detectable — after you click Publish. - Pasting into the wrong field. Some GoDaddy plans show multiple code fields. Always paste into the global header or footer field, not a field tied to a single page, unless OTTO specifically requires per-page placement. - Editing rather than replacing. Modifying the existing code instead of deleting and re-pasting it can preserve hidden formatting errors. Always start with a clean, empty field. - Using WordPress troubleshooting steps. Plugin-based fixes, functions.php edits, and theme file changes do not apply to GoDaddy Website Builder and will not resolve this issue. 💬 Still Not Engaged After These Steps? If the pixel still shows as not engaged after completing all steps above, there may be a caching or account-level issue that requires a closer look. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Fix FAQ Deployment Errors in OTTO

🔍 What This Error Means When you click Deploy on your FAQ items and see the message "empty fields cannot be deployed," it means one or more of your FAQ items are missing a generated answer. OTTO requires every FAQ item to have a complete answer before it can be deployed to your site. The error is not related to your site connection or deployment settings — it is caused by unanswered questions in your FAQ list. ⚠️ Why This Happens FAQ items can exist in your OTTO dashboard without answers in several situations: - You imported or added questions manually without generating answers yet. - Answer generation was interrupted or failed silently for some items. - You selected all items in bulk and attempted to deploy before reviewing each one. - Some items were added through a crawl or suggestion tool and were never processed. With a large batch like 308 items, it is common for a portion of them to have blank answer fields that are easy to miss before deploying. ✅ How to Find and Fix Empty FAQ Answers 1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Open your OTTO workspace and go to the FAQ section. 3. Look for a filter or status indicator that lets you sort or view items by answer status. Filter for items marked as empty, unanswered, or missing content. 4. Select all unanswered FAQ items. 5. Click Generate Answers (or the equivalent bulk action button) to trigger AI answer generation for all selected items. 6. Wait for the generation process to complete. Depending on the number of items, this may take a few minutes. 7. Once all items show a populated answer, return to the FAQ list, select all 308 items, and click Deploy. 💡 Tips for Large FAQ Batches - Generate before you deploy: Always run answer generation across the full batch first, then do a final review before deploying. - Use bulk selection carefully: Selecting all and deploying immediately skips the validation step — filter for empty items first. - Check generation status: After bulk generating, re-apply the empty filter to confirm zero items remain unanswered before you attempt deployment again. - Deploy in segments: If you are managing a very large FAQ set, consider deploying in smaller confirmed batches to make troubleshooting easier if an error appears. 🔄 What to Do If Answers Still Will Not Generate If you select unanswered items, trigger generation, and the answer fields remain blank after the process completes, try the following: - Refresh the page and check whether the answers populated correctly. - Check that the FAQ questions themselves are not blank — an empty question field will prevent answer generation. - Remove and re-add any FAQ items that appear stuck, then trigger generation again. - Make sure your OTTO workspace is connected to the correct target website. If the problem persists after these steps, if you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix OTTO Rollback Not Reflecting on Live Site

🔍 Why Your Rollback Isn't Showing Yet When you reverse an OTTO SEO suggestion, Search Atlas applies the change immediately at the platform level. However, your live site may continue displaying the old content for several hours because of cached versions stored at one or more layers between Search Atlas and your visitors. This is expected behaviour and does not mean the rollback failed. Caching can exist at multiple levels, including your hosting server, your content delivery network (CDN), your WordPress or CMS page cache plugin, and even your browser. All of these layers must serve the updated version before the rollback becomes visible. ✅ Confirm the Rollback Was Applied in Search Atlas 1. In the left sidebar, click OTTO SEO, then open SEO Automation inside it (URL: /seo-automation-v3). 2. Locate the page or element you rolled back. 3. Check the status indicator — it should show the suggestion as inactive or not deployed. 4. If the status still shows as active or deployed, the rollback may not have saved correctly. Try rolling back again and wait for the confirmation message before leaving the page. Once you have confirmed the rollback is recorded in Search Atlas, the remaining steps focus on clearing caches so your live site catches up. 🛠️ Step 1 — Clear Your Hosting or Server Cache Log in to your hosting control panel or server management tool and locate the cache-clearing option. Common locations include: - cPanel / Plesk: Look for a "Cache Manager" or "Varnish Cache" section and click Flush Cache. - WP Engine / Kinsta / Cloudways: Each managed host has a one-click Clear Cache button in its dashboard. - Apache / Nginx VPS: Restart the web server or use your cache module's flush command. After clearing the server cache, wait two to three minutes before testing your live URL. 🌐 Step 2 — Purge Your CDN Cache If your site uses a CDN such as Cloudflare, Fastly, or AWS CloudFront, you must also purge the cached files there. - Cloudflare: Go to your Cloudflare dashboard → select your domain → Caching → Configuration → click Purge Everything or enter the specific URL to purge. - Fastly / CloudFront: Use the Invalidate or Purge option in your CDN's cache settings, targeting the affected page URL. CDN propagation can take up to 30 minutes globally, but most visitors will see the updated version within a few minutes of purging. 🔌 Step 3 — Clear Your CMS or Plugin Cache If your site runs on WordPress or a similar CMS, a caching plugin is likely storing a static version of each page. Clear it using one of the following methods: - WP Super Cache / W3 Total Cache: In your WordPress admin, go to the plugin settings and click Delete Cache or Empty All Caches. - WP Rocket: Click the WP Rocket icon in the admin bar and select Clear Cache. - LiteSpeed Cache: In the WordPress admin bar, hover over LiteSpeed Cache and click Purge All. - Other CMSs (Shopify, Wix, etc.): Most hosted platforms clear cache automatically within minutes; no manual action is usually needed. 🖥️ Step 4 — Clear Your Browser Cache Even after server and CDN caches are cleared, your own browser may still show the old version from its local cache. To force a fresh load: - Windows: Press Ctrl + Shift + Delete, select Cached images and files, and click Clear data. - Mac: Press Cmd + Shift + Delete and follow the same steps. - Quick test without clearing: Open the page in a private or incognito window — this always fetches a fresh copy from the server. ⏱️ How Long Should I Wait After Clearing Caches? In most cases the updated content appears within five to fifteen minutes after clearing all cache layers. CDN propagation worldwide can occasionally take up to 30 minutes. If the rollback is still not visible after 30 minutes and you have completed every step above, it is worth double-checking that the rollback status in Search Atlas shows as inactive before escalating. 💡 Tips to Avoid This Issue in the Future - Before deploying or rolling back OTTO suggestions on high-traffic pages, schedule changes during low-traffic periods so you can verify them quickly. - Consider temporarily setting shorter cache TTLs (time-to-live) on your CDN for pages where you are actively running OTTO experiments. - Use an incognito window or a tool like Google Cache or GTmetrix to verify what live visitors actually see after any change. 🆘 Still Need Help? If you have completed all the steps above and the rollback is still not reflecting on your live site, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO H1 Rendering and Webflow Cache

🔍 What Is Happening and Why When OTTO SEO optimizes your H1 tag, it injects the updated heading through a script that runs after your page has loaded. This means there is a brief moment where the browser first displays your original H1, and then OTTO's optimized version replaces it. This is called a flash of original content, and it is a known behavior caused by the order in which your browser loads page elements versus OTTO's optimization script. In most cases, this visual flicker is temporary and does not affect how search engines read your final, rendered H1. However, if the issue persists or causes a noticeable delay, clearing your Webflow cache is the most effective fix. ⚙️ How OTTO Applies H1 Optimizations OTTO SEO applies on-page changes — including H1 tags — by injecting optimizations at the rendered layer of your site. This approach allows OTTO to make improvements without requiring direct edits to your source code or CMS templates. The process works as follows: 1. Your browser requests the page and loads the original HTML, including the pre-existing H1 tag. 2. OTTO's script executes and replaces the H1 with the optimized version. 3. The final rendered page displays the OTTO-optimized H1. This sequence is intentional and is how OTTO delivers changes across a wide variety of CMS platforms, including Webflow. 🌐 Why Webflow Cache Makes This Worse Webflow serves your site through a content delivery network (CDN) and caches pages aggressively to improve load speed. If your Webflow cache is storing an older version of your page, it may conflict with OTTO's real-time script injection, causing the H1 flicker to appear more pronounced or to persist longer than expected. Clearing the Webflow cache forces the CDN to serve a fresh version of your page, which allows OTTO's H1 optimization to render more cleanly and with less delay. ✅ How to Clear Your Webflow Cache Follow these steps to clear your Webflow site cache and resolve the H1 rendering issue: 1. Log in to your Webflow Designer or Webflow Dashboard. 2. Open the project for the site where the H1 issue is occurring. 3. Click the Publish button in the top-right corner of the Designer, or navigate to Project Settings. 4. Select Publish to your domains. Even if you have not made changes, republishing forces Webflow to purge the cached version of your pages. 5. Wait for the publish process to complete, then revisit the affected page in a new browser tab. If you are using a custom domain with an additional CDN layer (such as Cloudflare), you may also need to purge the cache at that level. Log in to your CDN provider's dashboard and look for a Purge Cache or Clear Cache option. 🔎 How to Confirm the Fix Worked After clearing your cache, verify that the H1 is rendering correctly by following these steps: - Open the affected page in a new incognito or private browser window to avoid loading any locally cached version. - Watch the page as it loads and check whether the H1 flicker has stopped or significantly reduced. - Right-click the page and select Inspect, then look at the final rendered H1 in the Elements panel to confirm it matches OTTO's optimized version. - You can also use the OTTO SEO dashboard under SEO Automation (left sidebar → OTTO SEO → SEO Automation) to review which H1 optimizations are active on your page. 💡 Additional Tips to Minimize H1 Flicker - Republish regularly: After OTTO applies new optimizations, republish your Webflow site to keep the cached version in sync. - Avoid duplicate H1 tags: Make sure your Webflow template only has one H1 per page. Multiple H1 elements can cause unexpected behavior when OTTO targets the tag for replacement. - Check script load order: If you have added custom scripts to your Webflow project, ensure they are not delaying OTTO's optimization script from running. In Webflow, scripts placed in the Footer Code section of Project Settings typically load after page content, which is the recommended placement. 🆘 Still Seeing the Issue? If you have cleared your Webflow cache and the H1 is still flickering or not updating correctly, there may be a conflict with a custom script, a third-party plugin, or a Webflow-specific configuration 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.

🔍 Fix OTTO Page Count Discrepancies in Issues

🧭 Overview When you open OTTO, you may notice that the total page count at the top looks correct — for example, 16 pages detected — but individual issue sections like Title Tags or Meta Descriptions show only a small subset, such as 3 pages. This discrepancy is a known issue that the support team can investigate and resolve on a per-account basis. ⚙️ Why This Happens OTTO pulls its page-level data directly from your Site Audit crawl. In some cases, OTTO may detect the total number of pages on your site but not yet reflect the full page count across individual issue sections. This can result in a temporary gap between the overall page count and what appears in specific issue areas. ✅ What To Do If you are seeing fewer pages in OTTO's issue sections than your total detected page count, here is what you can do: - Note your project name and the specific issue sections where pages appear to be missing. - Note the total page count displayed versus the number shown in the affected sections. - Check whether your Site Audit has fully completed before escalating — if a crawl is still in progress, allow it to finish and then check the issue sections again. - If the numbers still do not match after the audit has completed, contact the support team with the details above so they can investigate your account 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 v3 Company Location Reverting to Default

🔍 Why Does This Happen? OTTO v3 uses a Domain Knowledge Network (DKN) to personalise AI-generated SEO content for your business. If your company location settings appear to revert to UK defaults, it usually means the DKN company details were never fully saved, were saved under the wrong domain, or were cleared during a domain reset. Every time OTTO generates content, it pulls from these stored details — so an incomplete or missing profile will cause it to fall back on default values. 📍 Where to Find Company Location Settings Follow these steps to locate and update your company details inside OTTO v3: 1. In the left sidebar, click OTTO SEO, then open SEO Automation (URL: /seo-automation-v3). 2. Select the correct domain from the domain switcher at the top of the page. Make sure you are editing the intended domain before making any changes. 3. Navigate to the Domain Knowledge Network section within the OTTO v3 dashboard. 4. Open the Company Details or Business Information panel. 5. Locate the Location fields, including country, region, city, and address. 6. Update all fields to reflect your correct business location. 7. Click Save to confirm your changes before leaving the page. ✅ How to Confirm Your Settings Are Saved After saving, take these steps to verify that your location details are persisting correctly: - Refresh the page and reopen the Domain Knowledge Network panel to confirm the new values are displayed. - Check that the correct domain is selected in the domain switcher — settings are stored per domain, so switching domains will show different profiles. - Run a short OTTO content generation task and review the output to confirm it reflects your correct location, not UK defaults. ⚠️ Common Reasons Settings Keep Reverting If your location continues to reset after saving, check for these common causes: - Wrong domain selected: OTTO v3 stores DKN profiles per domain. If you have multiple domains, ensure you are editing and saving under the correct one. - Incomplete save: Navigating away before clicking Save will discard your changes. Always confirm the save action before leaving the panel. - Domain reset or reconnection: Reconnecting or resetting a domain can clear previously saved DKN data. After any domain reset, re-enter your company details. - Multiple users overwriting settings: If your account has multiple users, another team member may be resetting the profile. Coordinate with your team to avoid conflicting edits. 💡 Best Practices to Prevent This Issue - Complete all Company Details fields in the DKN as soon as you connect a new domain — do not leave any fields blank. - After any domain-level change (reset, reconnect, or plan change), immediately revisit the DKN and re-confirm your company location. - Designate one team member as responsible for maintaining DKN settings to avoid accidental overwrites. - Periodically spot-check your DKN profile, especially if you notice OTTO-generated content referencing unexpected locations or generic business descriptions. 🆘 Still Need Help? If you have followed all the steps above and your location settings continue to revert, or if you cannot locate the DKN company details panel, our team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why OTTO Isn't Showing Your On-Page Fixes

🧭 Overview After deploying on-page fixes through OTTO, you may notice that the changes don't appear immediately inside the platform — or that OTTO still shows outdated content such as old meta descriptions, blog posts, or a previous site icon. This is almost always caused by a crawl delay, not a deployment failure. This article explains why this happens and what you can do to speed up the process. ⚙️ Why Does This Happen? OTTO relies on its site crawler to read your live website and update the data it displays inside the platform. When you deploy a fix, the change goes live on your site right away — but OTTO's display won't update until the crawler revisits your pages and pulls in the new data. Several factors can slow this down: - Large websites: Sites with many pages take longer to fully re-crawl. - Crawl queue: During high-demand periods, your site may be queued behind other crawl requests. - Server response time: If your hosting server responds slowly, the crawler takes longer to process each page. - Caching layers: CDN or server-side caches may serve the old version of your page to the crawler even after you've updated your site. This is a known platform behaviour. Your fixes are live on your website — OTTO's dashboard simply needs time to catch up and reflect them. ✅ How to Confirm Your Fixes Are Already Live Before taking any action inside OTTO, verify that your changes are actually live on the front end: 1. Open your browser and navigate to the affected page. 2. Right-click the page and select View Page Source. 3. Search for the specific element you changed (e.g., meta title, meta description, alt tag, or H1). 4. If your updated content appears in the source code, the fix is live — OTTO just hasn't re-crawled it yet. You can also open the page in a private/incognito window to bypass your local browser cache and confirm the live version. 🛠️ Steps to Refresh OTTO's Data Follow these steps to prompt OTTO to re-crawl your site and update its displayed data: 1. In the left sidebar, click OTTO SEO → All Sites (SEO Automation) to open the OTTO dashboard. 2. Locate your connected website and open its OTTO session. 3. Look for the Re-crawl or Refresh Site option within the session controls and click it. 4. Allow the crawl to complete — this can take anywhere from a few minutes to several hours depending on your site size. 5. Once the crawl finishes, return to the OTTO dashboard and check whether your fixes are now reflected. If you have a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) or a CDN (such as Cloudflare), clear your cache before triggering the re-crawl. This ensures the crawler sees the most up-to-date version of your pages. ⏱️ How Long Should I Wait? Crawl times vary based on site size and server performance. As a general guide: - Small sites (under 50 pages): Typically update within 15–60 minutes. - Medium sites (50–500 pages): May take 1–4 hours. - Large sites (500+ pages): Can take several hours or longer. If more than 24 hours have passed since you triggered a re-crawl and your fixes still aren't showing inside OTTO, proceed to the next section. 🚩 When to Contact Support Reach out to our team if any of the following apply: - Your fixes are confirmed live in your page source but OTTO hasn't updated after 24+ hours. - The re-crawl appears to be stuck or never completes. - Specific elements such as your site icon, blog posts, or structured data are consistently not being picked up despite multiple re-crawl attempts. - Your OTTO session shows fixes as Deployed but the frontend of your site does not reflect them at all. If you need further assistance, open 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 Test page speed via Google PageSpeed Insights: score below 50 or TTFB above 600ms indicates crawl impact. Check server response with GTmetrix/Pingdom — above 1–2 seconds can cause crawler timeouts on content-heavy pages.

🛠️ Fix OTTO Script Unexpected Text on Shopify

**🔍 What Is Happening?** When the OTTO script is active on a Shopify store, some themes display unexpected or duplicate text on the homepage — often near the logo or top of the page. This happens because OTTO reads and interacts with the semantic HTML structure of your theme, and certain header layouts can cause it to surface hidden or unintended text content. This is **not** caused by where the OTTO script is placed in your theme.liquid file. The root cause is almost always how your logo or site title is wrapped inside **header.liquid**. **🧩 Why header.liquid Is the Cause** Many Shopify themes wrap the store logo inside an ** ** tag on the homepage for SEO purposes. This is a common and valid pattern. However, some themes include visible text inside thattag alongside the logo image — such as the store name as a text fallback. When OTTO scans the page for heading structure, it reads that text as meaningful on-page content and may surface or interact with it in unexpected ways, causing it to appear visually on the page. Common scenarios that trigger this issue: - The logo is wrapped in anthat also contains plain text (e.g., the store name as a fallback). - The text inside theis hidden with CSS but not removed from the DOM, making it invisible to visitors but readable by scripts. - A wrapping the logo contains text nodes that OTTO interprets as heading content. # **📋 How to Diagnose the Problem** Before editing any files, confirm the issue is coming from the header area: 1. Look at your Shopify homepage with the OTTO script active. Note **exactly where** the extra text appears — is it near the logo, top navigation, or banner area? 2. Right-click the unexpected text in your browser and select **Inspect** to open browser developer tools. 3. Check whether the text is inside an **** tag or a wrapper element directly surrounding your logo. 4. In your Shopify admin, go to **Online Store → Themes → Edit Code** and open the **header.liquid** file (or **sections/header.liquid** depending on your theme). 5. Search for **logo wrapper** 1. In your header.liquid file, locate thetag wrapping your logo. 2. If there is plain text (such as your store name) sitting alongside the logo image tag, remove the text node or replace it with an empty string. 3. Save the file and reload your homepage to confirm the extra text is gone. **Option 2 — Use an aria-label instead of visible text** 1. If the text inside theis serving an accessibility purpose (screen reader label), replace it with an **aria-label** attribute on theor the anchor tag inside it. 2. For example: **** with only the image tag inside — no visible text. 3. This keeps your store accessible without exposing text that OTTO can surface. **Option 3 — Visually hide the text correctly** 1. If a previous developer hid the text using **display: none** or **visibility: hidden**, OTTO may still read it. Use a proper visually-hidden CSS class instead (sometimes called **sr-only**). 2. A visually-hidden element uses **position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0,0,0,0);** — this keeps it available to screen readers but out of the normal document flow that OTTO processes. # **⚙️ Verify OTTO Is Still Working After the Fix** 1. In the Search Atlas platform, go to **OTTO SEO** using the left sidebar. 2. Open your connected Shopify site and run an OTTO scan to confirm all optimisations are still being applied correctly. 3. Check your homepage in the browser with the OTTO script active to confirm no unexpected text remains. 4. Review your H1 tag in OTTO's on-page recommendations to ensure the homepage heading structure is being read as intended. # **🚫 What Not to Do** - **Do not move the OTTO script** from its current position in theme.liquid — script placement is not the cause of this issue and relocating it will not fix it. - **Do not delete thetag** around your logo — this tag carries SEO value on the homepage and should be preserved. - **Do not hide text with display: none alone** — some scripts, including OTTO, can still access and process text hidden this way. # **💬 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 Site Audit Bug Fixes July 2026

Two bug fixes have been shipped for OTTO and Site Audit, addressing issues with the Raw JSON Schema editor and a concurrent loader race condition in the OTTO v3 Issues Table. ✨ What's New This release resolves two bugs that could disrupt your experience when working with schema markup in OTTO: - JSON Schema editor node highlighting: The Raw JSON Schema editor was incorrectly highlighting the wrong node when removing {} or [] brackets. This has been corrected so the editor now accurately highlights the affected node during edits. - Concurrent schema generation loader race: A race condition in the OTTO v3 Issues Table caused inconsistent loader behavior when multiple schema generation requests were triggered simultaneously. This has been fixed to ensure the loader state is handled reliably under concurrent operations. 🛠️ How to Use It 1. Navigate to OTTO SEO from your Search Atlas dashboard. 2. Open the Issues Table to review any schema-related tasks. 3. Use the Raw JSON Schema editor to make edits — node highlighting will now reflect the correct element when adding or removing brackets. 4. Trigger schema generation as needed, knowing that concurrent requests will no longer cause loader inconsistencies. 🔍 Recognizing These Issues If you have experienced either of the following symptoms, they are caused by the bugs described above and are now resolved — no action is required on your part: - Wrong node highlighted in the JSON Schema editor: While editing schema markup in the Raw JSON Schema editor, you may have noticed that deleting a {} or [] bracket caused a different, unrelated node to become highlighted instead of the one you were editing. This was a display bug and did not alter your schema data, but it made it difficult to track which element was being modified. - Loader spinning inconsistently or getting stuck: If you triggered schema generation for multiple pages or issues at the same time in the OTTO v3 Issues Table, you may have seen the loading indicator behave erratically — for example, continuing to spin after generation completed, or stopping prematurely. This was caused by a race condition when concurrent requests were processed simultaneously. 📋 What to Expect These are targeted bug fixes with no changes to existing workflows or feature functionality. The JSON Schema editor and OTTO v3 Issues Table should now behave consistently and accurately. No action is required on your end — the fixes are applied automatically. If you are still seeing incorrect node highlighting or loader inconsistencies after reading this, please hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to ensure you are running the latest version of the platform. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO SEO UUID Mismatch with Cloudflare

🔍 What Is a UUID Mismatch? When you activate OTTO SEO on your website, Search Atlas generates a UUID (Universally Unique Identifier) — a unique code that links your site to your OTTO SEO workspace. A UUID mismatch occurs when the UUID that OTTO detects on your site does not match the one stored in your Search Atlas account. This issue most commonly appears when your site is proxied through Cloudflare DNS. Cloudflare's caching and proxy settings can interfere with how the UUID is served and verified, causing OTTO SEO to fail validation even if you followed every setup step correctly. ⚙️ Why Cloudflare Can Cause This Problem Cloudflare sits between your visitors (and Search Atlas) and your origin server. When OTTO SEO attempts to verify your UUID, it sends a request to your domain. If Cloudflare is caching an old version of the page or blocking certain requests, the UUID it returns may be outdated, missing, or from a different deployment entirely. Common contributing factors include: - Aggressive page caching — Cloudflare serves a cached page that does not contain the latest UUID snippet. - Performance features that modify JavaScript — Certain Cloudflare optimizations can defer or alter scripts, which may prevent the UUID from loading correctly at verification time. - Security or bot-filtering rules — Firewall or bot-protection settings may block the Search Atlas verification crawler before it can read the UUID. - Proxied DNS records — Proxy mode routes traffic through Cloudflare, which can alter the response seen by the OTTO verifier. 🚀 What to Do When You Experience a UUID Mismatch Because the exact configuration that causes a UUID mismatch can vary depending on your Cloudflare setup, the most reliable path to resolution is to contact our support team directly. When you reach out, please have the following ready so our team can investigate efficiently: - Your Search Atlas project/site name and the domain experiencing the mismatch - A description of your Cloudflare DNS configuration (e.g., whether the DNS record is proxied or DNS-only) - Any Cloudflare features you have enabled that affect JavaScript delivery, caching, or security/bot filtering - The exact error message or status shown in your Search Atlas account when validation fails - A timestamp of when the issue first occurred or was last observed Having this information ready will allow our team to identify the specific Cloudflare setting interfering with UUID validation and guide you through the correct fix for your 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.

🏷️ H1 Tags Not Updating After CMS Fixes

🔍 Overview When OTTO detects and pushes H1 tag fixes through your CMS, you may notice that the updated values do not appear in your Search Atlas project even after deployment. This is a known discrepancy between what OTTO detects during a crawl and what is ultimately reflected at the project level. This article walks you through the most common causes and the exact steps to resolve them. ⚠️ Understanding the Crawl Detection vs. Project Reflection Gap OTTO scans your pages during a crawl and identifies the correct H1 values. However, the project view may still show outdated H1 tags for several reasons: - The WordPress plugin has not been updated to the latest version required to write H1 changes correctly. - Server-side or browser cache is serving old page content, preventing the new H1 from being read. - A theme-level H1 override is replacing the page-level value after OTTO applies the fix. - The project has not been reprocessed since the fix was deployed, so the crawl data is stale. Each of these causes requires a different resolution step. Work through them in the order listed below. 🔌 Step 1 — Update the Search Atlas WordPress Plugin An outdated plugin version is the most common reason H1 fixes deploy to the CMS but do not render correctly on the live page. 1. Log in to your WordPress admin dashboard. 2. Navigate to the Plugins section of your dashboard. 3. Locate the Search Atlas plugin in the list. 4. If an update is available, apply the update and wait for it to complete. 5. Once updated, visit one of the affected product pages in your browser and check the page source to confirm the H1 tag now contains the correct value in the raw HTML. If the plugin is already on the latest version, proceed to Step 2. 🗑️ Step 2 — Clear All Caches Even after a successful plugin update, caching layers can serve stale HTML that still contains the old H1 value. Clear every cache layer in this order: 1. WordPress caching plugin: Open your caching plugin (for example, WP Rocket, W3 Total Cache, or LiteSpeed Cache) and use its option to purge or clear all cached files. 2. Hosting-level cache: Log in to your hosting control panel and flush any server-side page or object cache. Contact your host if you are unsure how to do this. 3. CDN cache: If your site uses a CDN such as Cloudflare, log in and purge the cache for the affected URLs according to your CDN provider's instructions. 4. Browser cache: Open the affected page in an incognito or private browser window to rule out locally cached content. After clearing all caches, reload the affected product page and check the H1 tag in the page source again before moving to the next step. 🔄 Step 3 — Reprocess Your Project If the H1 values are now correct on the live page but still appear outdated inside Search Atlas, the project needs to be reprocessed so the platform picks up the latest crawl data. 1. Open your Search Atlas project. 2. Trigger a new crawl or reprocessing run so the platform re-reads your updated pages. 3. Once the reprocessing is complete, return to the affected pages in your project and verify the H1 tags now reflect the correct values. 🎨 Step 4 — Check for Theme-Level H1 Overrides If H1 tags are still incorrect after completing the steps above, a theme-level override may be replacing the values OTTO writes. Check your active theme's template files and any page builder settings to ensure no hardcoded or dynamically generated H1 is overwriting the page-level value set by OTTO. If you are unsure how to identify theme overrides, consult your theme or page builder documentation. If you need further assistance, open 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 Deployments Causing Wrong Link Redirects

Overview When OTTO deploys an SEO automation, it can sometimes modify links on your site in ways you did not intend — for example, redirecting a CTA button to the wrong page. If you are experiencing unexpected link redirects that appear to be caused by an OTTO deployment, this article explains how to approach the issue and what information to have ready. What Is Happening OTTO automates a range of on-site SEO changes, and some of those changes can affect how links behave. If a CTA button or internal link started redirecting to an unintended destination after OTTO was activated or after a new deployment was applied, it is likely that a specific OTTO deployment is responsible for the change. What You Should Do 1. Log in to Search Atlas and open the OTTO dashboard from the left sidebar. 2. Review your active OTTO deployments to identify which one may be affecting the link in question. Look for any deployments related to link modifications or redirects on the affected page. 3. If you are able to identify the specific deployment causing the issue, disable it from within the OTTO dashboard to stop the change from being applied going forward. 4. If you are unsure which deployment is responsible, or if disabling a deployment does not resolve the redirect, escalate to the support team for backend investigation. What to Have Ready When Contacting Support Because identifying and disabling the correct OTTO deployment may require backend access, our support team may need to assist you directly. To speed up the process, please have the following ready before reaching out: - The project name or site URL where the wrong redirect is occurring - The specific page URL that contains the affected link or CTA button - The expected destination the link should point to, and the actual destination it is currently redirecting to - The approximate date and time the issue started, if known - Any OTTO deployment names or IDs you have already identified as potentially related If you need further assistance, open 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 FAQ Schema Deployment Errors in OTTO

🔍 Overview When deploying a Knowledge Based Trust (KBT) FAQ schema through OTTO SEO, you may encounter a deployment error that reads something like "questions should have answers" — even when every Q&A pair appears to have an answer filled in. This article explains why this happens and how to resolve it. ⚠️ Why This Error Occurs This error is most commonly caused by one of the following issues, even when the FAQ fields look complete on screen: - Hidden empty entries: A blank Q&A row exists in your list that is not immediately visible. OTTO validates every row, including ones you may have accidentally added and left empty. - Whitespace-only answers: An answer field contains only spaces or line breaks, which OTTO does not count as valid content. - Unsaved edits: Changes made to an answer were not saved before deployment was triggered, leaving the stored value empty. - Special characters in answers: Certain characters (such as unmatched quotation marks or HTML tags) can cause a field to be rejected during schema validation. - Answer field character limit: Answers that exceed the allowed character limit may be silently truncated or rejected, resulting in an effectively empty value at the schema level. 🛠️ How to Resolve the Error 1. Open your FAQ schema in OTTO SEO and navigate to the Q&A section for the affected page. 2. Scroll through every Q&A entry — including any rows below the fold. Look for any row where the answer field is blank, contains only spaces, or shows placeholder text. 3. Delete any empty or incomplete rows by clicking the remove/delete icon next to that entry. You do not need a minimum of 8 Q&As remove any that are not fully complete. 4. Check each remaining answer to confirm it contains real, readable text with no leading or trailing whitespace. 5. Re-save each Q&A entry individually by clicking the save or confirm button on that row before proceeding. 6. Attempt deployment again once all entries are confirmed complete and saved. 💡 Tips to Prevent This Error - Always save each Q&A row immediately after entering the answer — do not rely on a single bulk save before deployment. - Avoid copying and pasting text from Word or Google Docs without first pasting it into a plain-text editor to strip hidden formatting characters. - Keep answers between 50 and 300 characters as a safe range to stay within schema validation limits. - Review your FAQ list one final time before clicking Deploy to catch any overlooked empty rows. ❓ Frequently Asked Questions I can see answers in all 8 rows — why is OTTO still rejecting the deployment? Scroll down to check whether a 9th or later row exists below the visible area. Even a single empty row will trigger the validation error for the entire schema block. Delete any incomplete rows and redeploy. Will deleting empty rows affect my live FAQ schema? No. Removing an empty row that was never successfully deployed will not affect any content currently live on your website. Only fully deployed Q&As are written to your schema. Does the order of Q&A pairs matter for deployment? The order does not affect whether deployment succeeds, but it does control the sequence in which questions appear in your FAQ schema markup. Reorder entries as needed before deploying. 📞 Still Need Help? If you have followed all the steps above and the deployment error persists, our team is ready to 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.

🔌 OTTO Pixel WordPress Troubleshooting: Plugin Conflicts

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

🔍 OTTO SEO: Homepage Title Tag Suggestions Missing

⚠️ Why This Happens There are two main reasons OTTO may skip a homepage title tag suggestion: - Homepage not recognised as a page: OTTO uses specific signals to identify the homepage. If the root URL (e.g., https://yourdomain.com/) is redirected, returns an unexpected status code, or is listed in the sitemap with a trailing slash inconsistency, OTTO may not flag it for analysis. - Automated posting quota reached: OTTO enforces a platform-wide automated posting quota. Reaching this quota can pause suggestion generation for one or more projects, including the homepage. 🛠️ What You Can Do 1. Check your homepage URL for redirect or format issues. In a browser, visit both https://yourdomain.com and https://yourdomain.com/ and confirm both resolve to the same page with a 200 OK status (you can use a free HTTP status checker tool). If the homepage redirects to a subdirectory or www variant, OTTO may be attributing the page to a different URL. Ensure the URL in your sitemap exactly matches the canonical homepage URL you expect OTTO to analyse. 2. Confirm your automated posting quota has not been reached. If your plan's automated posting limit has been reached, suggestion generation may be paused across your projects. Contact our support team to confirm your current quota status and to request a manual review of the affected homepage. 3. Contact support with the following details ready: your project name, the exact homepage URL, any redirect behaviour you observed, and whether the issue affects multiple pages or only the homepage. This allows our team to investigate the detection or quota issue directly on your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ Fix og:image Not Rendering on OTTO Pages

🔍 Overview If you have configured an og:image meta tag through the Search Atlas WordPress plugin but it is not appearing in your page source — while other Open Graph tags like og:title, og:description, and og:url display correctly — you are experiencing a known conflict between OTTO-managed pages and the plugin's Open Graph meta box. This article explains why this happens and walks you through the steps to resolve it. ⚙️ Why This Happens When OTTO is active on a page, it takes control of on-page optimisations, including meta tag output. In some cases, OTTO's output overrides values set manually in the Search Atlas plugin's OG/social meta box, causing your custom og:image value to be silently ignored in the rendered HTML. This is a known issue currently under active review by the Search Atlas engineering team. The fix — which ensures customer-set OG and social tags always take priority over OTTO's suggestions — is in the review stage and will be released in an upcoming update. 🛠️ How to Resolve It Now While the permanent fix is being released, use the following workaround to ensure your og:image tag renders correctly. 1. Check your OTTO activation status. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. Locate the page in question and confirm whether OTTO is active on it. 2. Review OTTO's og:image suggestion. Inside OTTO for that page, check if OTTO has generated its own og:image value. If it has, this value is currently taking precedence over your plugin setting. 3. Set the og:image directly inside OTTO. Instead of relying on the Search Atlas plugin's meta box for that field, enter your desired image URL into OTTO's Open Graph image field. This ensures the value is output by the same system controlling the page and will render correctly in the page source. 4. Verify the tag in your page source. After saving, open your page in a browser, right-click, and select View Page Source. Search for og:image to confirm the tag is now present with the correct image URL. 5. Test your social sharing preview. Use a tool such as the Facebook Sharing Debugger or LinkedIn Post Inspector to confirm the image appears correctly when your URL is shared on social platforms. 📋 Additional Checks If the og:image tag is still missing after following the steps above, review the following: - Plugin conflicts: Ensure no other SEO or Open Graph plugin (such as Yoast SEO, Rank Math, or All in One SEO) is installed and active. Multiple plugins outputting Open Graph tags can cause conflicts where tags are duplicated or suppressed. - Image URL format: Confirm the image URL is absolute (e.g., https://yourdomain.com/image.jpg) and not relative. Social crawlers require a full URL to fetch the image. - Image accessibility: Make sure the image is publicly accessible and not blocked by a login wall, password protection, or robots.txt rules. - Caching: Clear your site cache, CDN cache, and any server-side cache after making changes. Cached HTML can serve an older version of the page source that does not include your updated tags. 🚀 What to Expect After the Fix Once the engineering update is released, customer-configured OG and social meta tag values set in the Search Atlas WordPress plugin will always take priority over OTTO's automatically generated suggestions. You will no longer need to enter the og:image value inside OTTO separately — the value from the plugin's meta box will render correctly on all OTTO-managed pages without any additional steps. 💡 Best Practice Recommendation Until the update is live, we recommend managing all Open Graph values — including og:image, og:title, and og:description — directly within OTTO for any page where OTTO is active. This keeps all meta tag output under a single system and prevents conflicts from occurring. 🙋 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.

🔄 Unlimited OTTO Quota Not Applied After Promotion

🔍 What Is This Issue? Some customers on the Platinum Summit plan with an active unlimited OTTO promotion find that the platform still enforces a hard project cap — preventing new OTTO projects from being created. This happens because of a sync issue between the billing system and the project creation gate. Your quota is correctly recorded in billing, but it has not been applied to the part of the system that controls project limits. ⚠️ How to Recognise This Problem - Your billing page shows an active unlimited OTTO promotion. - You receive an error such as "out of quota" when trying to create a new OTTO project. - You are blocked at a hard project cap (for example, 3 projects) even though your plan should allow more. - The OTTO SEO section of the platform reflects a limit rather than an unlimited quota. 🛠️ What You Should Do Because this issue is caused by a backend sync problem, there are no settings you can change yourself to fix it. You will need our team to trigger a manual quota refresh on your account. Follow the steps below to get this resolved as quickly as possible. 1. Confirm your promotion is active. Before contacting support, check that your unlimited OTTO promotion is shown as active in your billing details. This helps our team verify your entitlement immediately. 2. Note the exact error. If you see an on-screen error message when trying to create a new OTTO project in Left sidebar → OTTO SEO → All Sites (SEO Automation), make a note of it or take a screenshot. This speeds up diagnosis. 3. Contact our team via live chat. Open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Share your account details and let them know you are seeing a quota cap despite having an active unlimited promotion. 4. Request a backend quota refresh. Ask the agent to escalate a quota refresh for your account. Our specialized team can push a backend update that syncs your billing entitlement with the project creation gate. 5. Confirm the fix. Once the refresh is applied, return to Left sidebar → OTTO SEO → All Sites (SEO Automation) and attempt to create a new OTTO project. The block should be removed and your unlimited quota reflected correctly. 📋 What to Expect - The quota refresh is performed by a specialized backend team and typically resolves the issue in a short turnaround after escalation. - You do not need to make any changes to your plan or repurchase your promotion. - Once resolved, your unlimited OTTO project creation should work immediately without any further action on your part. 💡 Why Does This Happen? Promotional quota upgrades — such as the unlimited OTTO entitlement on Platinum Summit plans — are applied at the billing level. In some cases, a sync delay means the project creation system does not receive the updated limit from billing. This is a known platform issue that our engineering team continues to address. It does not affect your billing status or the validity of your promotion. 🆘 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 Schemas Stuck in Not Deployed

🔍 What This Article Covers If your OTTO schemas show SYNC_COMPLETE but remain stuck in a Not Deployed status, this article explains why that happens and what you need to do to get them deployed successfully. ⚙️ Why Schemas Get Stuck in Not Deployed A SYNC_COMPLETE status means OTTO has successfully synced your schema data from your site. However, syncing is only the first step. Before OTTO can deploy a schema to your pages, it validates that all required fields for that schema type are populated with real data. For Product schemas, the most common reason deployment stalls is that one or more of these required fields are empty or incomplete: - review — at least one customer review must be present - aggregateRating — a valid aggregate rating value (e.g., 4.5 out of 5 based on 30 reviews) must exist - name — the product name must be populated - offers — pricing and availability details must be present If any required field is missing, OTTO cannot produce a valid schema that meets Google's structured data guidelines, so it holds the schema in Not Deployed rather than pushing broken markup to your site. 🛠️ How to Fix Schemas Stuck in Not Deployed 1. Go to the left sidebar and select OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Locate the schemas listed as Not Deployed and click into each one to open the schema detail view. 3. Review the field checklist. Any field flagged as missing or invalid will be highlighted. 4. Return to the corresponding page or product on your site and add the missing data — for example, enable customer reviews, add an aggregate rating, or complete pricing information. 5. Once the required fields are populated on your site, trigger a fresh sync by clicking Sync within the OTTO schema panel. 6. After SYNC_COMPLETE runs again with the updated data, OTTO will re-validate the schema. If all required fields now pass, the status will move to Deployed automatically. 📋 Common Required Fields by Schema Type - Product — name, offers, review, aggregateRating - Article — headline, author, datePublished - LocalBusiness — name, address, telephone - FAQ — at least one Question and acceptedAnswer pair If OTTO detects that a required field cannot be sourced from your page at all, it will leave the schema in Not Deployed to protect your site from invalid structured data that could trigger Google Search Console errors. ✅ How to Confirm Deployment Succeeded After syncing with the corrected data, the schema card status will update to Deployed within a few minutes. You can also use Google's Rich Results Test tool to confirm the structured data is live and valid on your page. 💬 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's Disabled WordPress Plugin Error

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

🛠️ OTTO Dynamic SEO Injecting Wrong Schema Types

🔍 What Is Happening OTTO's Dynamic SEO feature uses AI to detect and inject structured data (schema markup) onto your pages via the data-otto-pixel='dynamic-seo' attribute. In some cases, the AI may generate and approve schema types that do not match your page's content — for example, injecting VacationRental, Course, SoftwareApplication, WebApplication, or MobileApplication schema onto a page about an unrelated topic such as basement waterproofing. This issue is caused by the Dynamic SEO AI misclassifying page content during schema generation. The incorrect schemas are then approved and deployed automatically. Your sitewide schema and other Search Atlas components are not affected — only the schemas generated and injected by the Dynamic SEO feature. ⚙️ How to Confirm the Issue 1. Open your browser's developer tools on the affected page (right-click the page and select Inspect, then go to the Elements tab). 2. Search for data-otto-pixel='dynamic-seo' in the page source. If this attribute is present alongside incorrect schema types, OTTO's Dynamic SEO feature is the source. 3. Note which schema types are listed. If they do not match your page's actual topic or business type, you are experiencing this issue. 4. Optionally, confirm your sitewide schema is unaffected by reviewing your schema settings in the Search Atlas dashboard — sitewide schema is managed separately from Dynamic SEO-injected schema. 🚀 Steps to Resolve Because removing specific incorrect schemas requires a backend correction to mark them as deleted and sweep the affected project, this issue cannot be fully resolved through the platform UI alone. To get it fixed as quickly as possible, complete the diagnostic steps below and then contact support — providing the details up front will allow engineering to act immediately without back-and-forth. 1. Identify all pages on your site where incorrect schema types are being injected by OTTO's Dynamic SEO feature, using the inspection method described above. 2. Note the exact incorrect schema types appearing on each affected page (for example: VacationRental, Course, SoftwareApplication). 3. Open the live chat widget (bottom-right of any Search Atlas page) and submit a message that includes: - The URL(s) of the affected page(s) - The incorrect schema type(s) appearing on each page - Confirmation that data-otto-pixel='dynamic-seo' is present in the page source 4. The support team will escalate to engineering, who will remove the incorrect schemas at the database level and run a project sweep to ensure they are fully undeployed from your live site. 5. Once engineering confirms the fix, re-inspect the affected pages using the steps above to verify that the incorrect schema types no longer appear in the page source. If any incorrect types remain, reply to your open support conversation with the remaining schema details so engineering can re-sweep. 💡 Why This Cannot Always Be Self-Resolved Incorrect schemas injected by Dynamic SEO are stored and tracked at the database level with unique IDs. Fully removing them requires an engineering action to mark those records as deleted and confirm the deployment is cleared from your live site. Simply disabling a se

🔧 Fix OTTO v3 Location Settings Reverting to Default

What's Happening Some users have reported that their OTTO v3 company location settings revert to a default value — often a UK location — after they have previously configured them. This can cause content generated by OTTO v3 to reflect the wrong country or region. How to Fix It Follow these steps to manually correct and re-save your OTTO v3 location settings: 1. Open your OTTO v3 project. From your Search Atlas dashboard, navigate to the project where the location is reverting. 2. Go to OTTO v3 Settings. Inside the project, locate the OTTO v3 configuration or settings section. 3. Find the Company Location or Business Location field. Look for the field that controls your company's country or region. This is the field that may be reverting to an incorrect default (e.g. a UK location). 4. Set the correct location. Select or type the correct country and/or region for your business. 5. Save your changes explicitly. Make sure to click the Save (or equivalent confirmation) button after updating the field. Do not navigate away before saving. 6. Re-activate OTTO v3 if prompted. In some cases, re-deploying or re-activating OTTO v3 on the project after saving ensures the updated location is applied to future content generation. 7. Verify the change persisted. Leave the settings page, then return to it and confirm the correct location is still displayed. If the Issue Persists If your location settings continue to revert after following the steps above, the root cause may be specific to your account or project configuration. Please have the following information ready when you contact support: - The name of the project or workspace where the location settings are reverting. - The location value that keeps appearing (e.g. the incorrect default country or region). - The correct location you need the settings to reflect. - Any steps you have already taken to try to fix the issue (e.g. re-saving settings). - Approximate date and time when you first noticed the reversion. If you need further assistance, open 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 OTTO Project Missing from Atlas Brain

🔍 Overview If your OTTO project is active but does not appear in Atlas Brain or the playbook, you will not be able to add it or run on-page SEO fixes through Atlas Brain. This is a known sync issue that requires a manual resync from the Search Atlas team. The steps below will help you confirm the issue, attempt a self-service refresh, and gather everything needed so support can resolve it as quickly as possible. ⚠️ What Causes This Issue This problem occurs when an OTTO project exists in the OTTO projects list but fails to sync into Atlas Brain automatically. As a result, the project is missing from Atlas Brain, and you cannot run playbook fixes or on-page SEO tasks for that domain. This is a platform-level sync issue and is not caused by anything you have done incorrectly. ✅ How to Confirm You Are Affected - Your website domain is listed as an active project in OTTO. - The same project does not appear when you open Atlas Brain. - You cannot run playbook fixes or on-page SEO tasks for that domain through Atlas Brain. 🛠️ Steps to Take 1. Verify the project is active in OTTO. Check that your domain is listed and active in your OTTO projects. If it is not active, activate it before proceeding. 2. Check Atlas Brain for the project. Open Atlas Brain and look for your domain. Confirm it is genuinely missing and not simply hidden by a search term or filter. 3. Do not attempt to re-add the project. Trying to add the same project again will return a Request failed: 400 error because the backend already has a record of it. Additional re-add attempts will not resolve the issue and may complicate the fix. 4. Perform a hard browser refresh. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full reload of the page. Then recheck Atlas Brain to see whether the project now appears. 5. Clear your browser cache and log out, then log back in. Clear your browser cache, log out of Search Atlas, log back in, and navigate to Atlas Brain again. This ensures you are not viewing a stale cached version of the project list. 6. Try a different browser or incognito window. Open Search Atlas in a different browser or in a private/incognito window and check Atlas Brain. If the project appears there, the issue is isolated to your browser environment. If it is still missing, the problem is a backend sync issue. 7. Contact support for a manual resync. If the project remains missing after completing the steps above, the fix requires a backend resync that only the Search Atlas team can trigger. Reach out to our support team and share your domain URL along with confirmation that the project is active in OTTO but missing from Atlas Brain. The support team will escalate to a specialist who can perform the resync. To reach us, open the chat widget in the bottom-right corner of the platform and type human teammate. 📋 What Happens After You Contact Support Once you report the missing project, the support team will escalate the issue to a specialist who can trigger a manual resync. In the confirmed case, the resync was completed quickly and the customer confirmed the project appeared in Atlas Brain immediately afterward. You do not need to recreate the project or make any changes to your OTTO setup. 📝 Information to Have Ready - Your domain URL as it appears in OTTO. - Confirmation that the project is active in OTTO but not visible in Atlas Brain. - Which browsers or devices you already tried, and whether the project appeared in any of them. If you need further help, open the chat widget in the bottom-right corner of the platform and type human teammate. Additional Notes Gather before contacting support: the exact domain/project name, a screenshot or description of the 400 error received when attempting to re-add, and your account email or workspace identifier.

🔧 Fix Webflow OTTO Connection Conflicts on Your Site

🧭 Overview Connecting OTTO SEO to a Webflow site requires a specific installation method. Because Webflow restricts how custom code is injected, using the wrong method — or mixing two methods — creates a conflict that blocks both OTTO activation and Google Search Console (GSC) verification. This article explains why this happens and how to fix it. ⚠️ Why the Conflict Happens OTTO can be connected to your site in two ways: - Google Tag Manager (GTM) — the pixel fires through an existing GTM container. - JavaScript Pixel — the pixel is pasted directly into your site's <head> code. Webflow sites frequently have both GTM and a custom code section active at the same time. If the OTTO pixel is present in both locations, the duplicate tags conflict with each other. This causes OTTO to fail its site verification check and prevents GSC from confirming site ownership, even if you have followed the setup video exactly. 🔍 How to Diagnose the Conflict 1. In your browser, open your Webflow site and press Ctrl + U (or Cmd + U on Mac) to view the page source. 2. Press Ctrl + F and search for your OTTO pixel ID or the Search Atlas script tag. 3. If the pixel appears more than once in the source, you have a duplicate conflict. 4. Also check whether a GTM container script (GTM-XXXXXXX) is present — this confirms GTM is active on the page. 🛠️ How to Fix the Conflict You must choose one installation method and remove the other completely. We recommend the method that matches how your site is already set up. Option A — Use GTM only (recommended if GTM is already on your site): 1. Log in to your Google Tag Manager account. 2. Open the container for your Webflow site. 3. Create a new Custom HTML tag and paste the OTTO JavaScript pixel inside it. 4. Set the trigger to All Pages and publish the container. 5. Go to your Webflow Designer, open Site Settings → Custom Code. 6. Delete any Search Atlas or OTTO script tags from the Head Code and Footer Code fields. 7. Save and publish your Webflow site. Option B — Use the JavaScript Pixel only (recommended if you do not use GTM): 1. Go to your Webflow Designer, open Site Settings → Custom Code. 2. Paste the OTTO JavaScript pixel into the Head Code field. 3. Make sure the same pixel is not also firing through GTM. Open GTM and delete or pause any existing OTTO/Search Atlas tags. 4. Save and publish your Webflow site. 📊 Reconnect OTTO and Verify GSC After cleaning up the duplicate, complete the reconnection in Search Atlas: 1. In the left sidebar, go to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Select your project and open the OTTO SEO settings. 3. Click Verify Site. OTTO will re-check for the pixel on your live Webflow URL. 4. Once OTTO verification passes, return to Google Search Console and run the ownership verification again. GSC reads the same pixel tag, so it should now confirm successfully. Important: Always click Publish in Webflow after making any custom code changes. Webflow does not push code changes to your live site until you publish — this is the most common reason verification appears to fail even after following the steps above. ✅ Quick Checklist Before You Verify - The OTTO pixel appears exactly once in your live page source. - You are using only one installation method (GTM or JavaScript, not both). - Your Webflow site has been published after the code change. - You are verifying the exact URL added to your Search Atlas project (www vs. non-www matters). - Your GTM container is published, not just saved, if you are using the GTM method. 💬 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 Plugin Errors and Missing Projects

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

🔢 OTTO Quota Errors: Website Slots vs. Site Audit

🧭 Overview When you see a quota exhausted error while adding a website to SearchAtlas OTTO, it does not mean you have reached your plan's website limit. These are two separate limits, and confusing them is the most common reason this error causes unexpected frustration. This article explains the difference and walks you through how to resolve it. ⚖️ Two Separate Limits Explained Your SearchAtlas plan manages two independent quotas that both relate to websites but work in completely different ways: - Website plan slots: The total number of websites you can add and manage inside SearchAtlas across all features. If your plan supports up to 5 websites, this is the number you can register in the platform. - Site Audit quota: A separate limit on how many websites can have an active Site Audit crawl enabled at the same time. This quota is governed by your subscription tier and is independent of how many websites your plan allows you to add. The quota exhausted error is triggered by the OTTO quota, not your website plan slots. You may still have available website slots on your plan and still encounter this error if all your OTTO slots are in use. 🔍 Why This Error Appears in OTTO When you connect a new website to OTTO, the platform consumes an OTTO project slot for that site. If all your OTTO slots are already occupied by other websites, the system cannot add a new project and returns the quota exhausted error. ✅ How to Resolve the Error To free up an OTTO slot and successfully add your new website to OTTO, follow these steps: 1. Navigate to the OTTO section of the platform. 2. Review the list of websites currently connected to OTTO. 3. Identify any website that no longer needs to be managed in OTTO — for example, a site you are no longer actively optimising. 4. Disconnect or remove that website from OTTO to release its slot. 5. Return to the website you were trying to add and complete the OTTO setup again. Once a slot is freed, the quota exhausted error will no longer appear for the new website. 📊 How to Check Your Current OTTO Usage You can review which websites are currently consuming OTTO slots directly inside the platform: - Navigate to the OTTO section of the platform. - Each website listed with an active OTTO connection is using one OTTO slot. - Count the active connections and compare them against the OTTO limit included in your plan. If you are unsure what your OTTO limit is or need help identifying which websites to disconnect, please reach out to our support team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🛠️ Topical Terms Not Autopopulating in OTTO Content Assistant V2

🔍 Overview Some users have reported that topical terms do not autopopulate in the OTTO Content Assistant V2 sidebar, and are also unable to manually add or change keywords. This was a confirmed platform-level bug that has since been investigated, fixed, and deployed to production. ⚙️ What Was Happening The issue affected the Content Assistant V2 sidebar, where topical terms are expected to populate automatically to guide AI content generation. Affected users experienced one or more of the following: - Topical terms not appearing in the Content Assistant V2 sidebar - Inability to manually add new keywords - Inability to edit or update existing terms This was not a configuration error on the user's side. The root cause was a platform bug related to how topical terms were being populated and filtered during AI generation in Content Assistant V2. ✅ Current Status This bug has been fully resolved. The engineering team completed an investigation, scoping, development, code review, and QA process before deploying the fix to production. The issue is now marked as done and the fix is live for all users. 🚀 What You Should Do Now If you were previously affected by this issue, follow these steps to confirm everything is working correctly: 1. Open the Content Assistant V2 sidebar for the relevant page or project. 2. Check whether topical terms are now autopopulating as expected. 3. If needed, attempt to manually add or edit a keyword to confirm full functionality is restored. 🛠️ If the Problem Persists The fix has been deployed to production, so most users should no longer experience this issue. However, if topical terms are still not appearing or you are still unable to edit keywords, consider the following before contacting support: - Hard refresh your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to clear any cached version of the page. - Try a different browser or incognito window to rule out browser-specific issues. - Check that you are using Content Assistant V2 and not an older version of the content workflow. If the issue remains after trying the steps above, it is important to document what you are seeing. A screen recording or screenshots showing the missing topical terms will help the support team investigate quickly. 💬 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 On-Page Audit Content Section Not Updating

🧭 What This Article Covers Some customers notice that the Content section inside the Site Audit's On-Page Audit does not update or reflect recent changes to their pages. This article explains the most common causes and the steps you can take to get the audit refreshing correctly again. 📍 How to Navigate to On-Page Audit 1. Log in to your Search Atlas account. 2. In the left sidebar, click Content. 3. From the expanded menu, select On-Page Audit. This opens the On-Page Audit tool where you can review content-level recommendations for any page you have analysed. ⚠️ Why the Content Section May Not Update There are several reasons the content section inside the On-Page Audit may appear stale or unresponsive: - The audit has not been re-run. Content scores and recommendations do not update automatically after you make changes to a page. You must manually trigger a new audit run. - The page URL has not been re-submitted. If you updated the page but did not re-enter or refresh the URL inside the tool, the tool continues to display the previous results. - Browser cache is serving an old version. A cached version of the platform page can make results appear frozen even when a new audit has completed. - The audit is still processing. Large or complex pages can take several minutes to complete. The content section populates last, after technical and metadata checks finish. - A temporary platform issue. Occasional system delays can prevent results from rendering. These are usually resolved within a short time. 🛠️ Steps to Fix the Issue 1. Re-run the audit. Inside the On-Page Audit tool, locate your target URL and click the option to run or refresh the audit. Wait for all sections, including the content section, to finish loading before reviewing results. 2. Clear your browser cache. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh. Alternatively, clear your browser's cached files from your browser settings and reload the platform. 3. Try a different browser or incognito window. Open Search Atlas in a private or incognito window to rule out local caching or extension conflicts. 4. Wait a few minutes and reload. If the audit was recently triggered, give the tool up to five minutes to complete processing, then reload the On-Page Audit page. 5. Check your internet connection. An unstable connection can interrupt data loading. Confirm you have a stable connection and try again. 6. Log out and log back in. Sign out of Search Atlas, clear your session, and sign back in before re-running the audit. ✅ Confirming the Content Section Is Working Once the issue is resolved, the content section of the On-Page Audit will display: - A content score based on how well the page matches top-ranking competitors. - Term and phrase recommendations showing which keywords to add, increase, or reduce. - Word count guidance relative to the top-ranking pages for your target keyword. If the section still appears blank or shows outdated data after following all steps above, the issue may require investigation by our team. 💬 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 'Not Installed' Detection on Shopify

🧭 Overview If Search Atlas reports the OTTO pixel as not installed but you can see the script in your Shopify theme.liquid source code, there may be an issue with how or where the pixel script was added to your theme. Our support team can verify the installation and help identify the cause. 🔍 What to Check First Before reaching out, review the following in your Shopify Admin: - Confirm the OTTO pixel script is present in your theme.liquid file by opening Online Store → Themes → Edit Code and locating the file in the Layout folder. - Note the exact location of the script within the file (e.g., where it appears relative to other tags). - Check whether the pixel status in Search Atlas has updated since the script was added — it may take a short time to reflect changes. 🛠️ How to Escalate for Further Help If the pixel still shows as not installed after confirming the script is in your theme.liquid, contact our support team. To help us investigate as quickly as possible, please have the following ready: - Your Search Atlas project name or domain - A screenshot or copy of where the OTTO pixel script currently appears in your theme.liquid file - The exact status message shown in Search Atlas (e.g., "Not Installed," "Pending," or any error text) - Approximately when the script was added to your theme If you need further assistance, open 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 Script & Empty Dashboard Reports

🧭 Overview If your Otto script is not firing correctly or your OTTO dashboard reports are showing empty data, two separate but related issues may be at play: a broken script connection and incomplete report setup. This article walks you through both fixes in the correct order. ⚠️ Before You Begin Confirm the following before troubleshooting: - You have access to your website's backend or CMS to manage scripts. - Your site uses HTTPS (not HTTP). Otto scripts will not execute on insecure connections. - You are logged into Search Atlas and can navigate to SEO Automation inside OTTO SEO in the left sidebar (/seo-automation-v3). 🔁 Step 1 — Clear Cache and Reinstall the Otto Script A corrupted or outdated script installation is the most common cause of Otto not firing. Follow this sequence exactly: 1. Go to OTTO SEO in the left sidebar of Search Atlas, then open SEO Automation. 2. Select your project and open the Otto Setup section. 3. Copy the latest version of your Otto script snippet. 4. Log in to your website's CMS or hosting backend. 5. Remove the existing Otto script completely — do not leave any old version in place. 6. Clear your website's server-side cache and any CDN cache (e.g., Cloudflare, WP Rocket, W3 Total Cache). 7. Paste the newly copied Otto script into the correct location — typically inside the <head> tag of your site's global template. 8. Save and publish the changes. 9. Clear your browser cache, then reload your website to verify the script is present in the page source. To verify the script is live, right-click your webpage, select View Page Source, and search for otto or your unique script ID. If it does not appear, repeat the installation step. 🔒 Step 2 — Validate Your HTTPS Connection Otto scripts are blocked on non-secure connections. Confirm your site is fully secured: - Your site URL must begin with https:// — not http://. - There should be no mixed-content warnings in your browser's console (press F12 → Console tab and look for security errors). - Your SSL certificate must be valid and not expired. You can check this by clicking the padlock icon in your browser's address bar. If your site is running on HTTP or has SSL errors, resolve the certificate issue with your hosting provider before reinstalling the Otto script. 📊 Step 3 — Set Up Your OTTO Dashboard Reports Correctly Empty reports in the OTTO dashboard are almost always caused by missing data connections rather than a script problem. Each report type requires specific data sources to be active. Navigate to Reports in the left sidebar (/report-builder/projects-list) and check the following for your project: - Data Entry: Confirm that your project has at least one active data entry connected. Without this, report widgets will display empty. - Keyword Rank Tracker (KRT): Your keyword tracking campaign must be active and have completed at least one crawl cycle. Go to OTTO SEO in the left sidebar → All Sites (SEO Automation) → your project → KRT and verify keywords are being tracked. - Site Explorer: A Site Explorer analysis must have been run for your domain. If it has never been run, report sections that pull backlink or organic data will appear blank. - Google Business Profile (GPB) Integration: If your report includes local SEO or GBP widgets, your Google Business Profile must be connected under your project settings. Disconnected or unverified profiles will result in empty GBP report sections. After confirming all data sources are active, return to your report (Executive Summary) and click Refresh Summary, and allow up to 24 hours for fresh data to populate. 🎥 Step 4 — How to Submit a Video for Faster Diagnosis If you have recorded a screen video (for example, via Loom) showing the issue, our support team can review it directly. To get the fastest resolution: 1. Ensure your video clearly shows: the Otto script section in Search Atlas, the page source of your website (confirming whether the script is present or absent), and the empty report view in the OTTO dashboard. 2. Note the exact URL of the affected website and the name of the project in Search Atlas. 3. Open the chat widget in the bottom-right corner of the platform. 4. Type human teammate to connect with a support agent. 5. Share your video link along with the project name, website URL, and a brief description of what you see in each part of the video. Providing all four pieces of information (video, URL, project name, description) allows our team to diagnose the issue without needing to ask follow-up questions, which significantly speeds up resolution. ✅ Quick Checklist - Old script removed and new script reinstalled inside <head> - Server cache, CDN cache, and browser cache cleared - Site confirmed on HTTPS with a valid SSL certificate - KRT campaign active with at least one completed crawl - Site Explorer analysis run for the domain - GBP connected if local SEO report widgets are in use - Report refreshed and given up to 24 hours to populate If you need further assistance, open 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 Otto Title Tags Blocked by SEO Plugins

🔍 What Is Happening and Why When Otto applies a title tag suggestion to your pages, it writes those changes through Search Atlas's automation layer. However, if another WordPress SEO plugin — such as Yoast SEO, Rank Math, All in One SEO, or SEOPress — is active on your site, that plugin may override Otto's title output at the page-rendering level. The result: Otto marks the suggestion as applied, your daily crawl re-reads the live page, and the crawl reports the title as unchanged because the competing plugin's value is still being served to search engines. This is a plugin priority conflict, not a bug in Otto. Both tools are writing title data, but only one value is rendered in the HTML <title> tag — and most SEO plugins win that race by default. ⚠️ How to Confirm You Have This Conflict 1. Navigate to the Otto or SEO automation section of Search Atlas and open the page where the title suggestion was applied. 2. Check the suggestion status — if it shows as applied or published but your live page still displays the old title, a conflict is likely. 3. Right-click your live page in a browser, select View Page Source, and search for the <title> tag. If you see your old title or the competing plugin's value instead of Otto's suggestion, the conflict is confirmed. 4. In your WordPress dashboard, navigate to the SEO plugin that is active and check whether a custom title is stored for that specific page. A saved value there will always override Otto. 🛠️ Fix Option 1 — Clear the Title Inside Your SEO Plugin (Recommended) You do not need to deactivate your SEO plugin. Instead, remove the custom title value stored inside that plugin for the affected page, leaving the field blank. Otto's value will then render without conflict. 1. Open the page or post editor in WordPress. 2. Scroll to the SEO plugin's meta box (usually below the content editor). 3. Locate the SEO Title or Title Tag field for that specific page. 4. Delete any text in that field so it is completely empty, then save or update the page. 5. Return to the Otto or SEO automation section in Search Atlas and trigger a manual re-crawl of the page, or wait for the next daily crawl to confirm the Otto title is now rendering correctly. Repeat this for each page where Otto suggestions are not appearing. If you have many affected pages, most SEO plugins support bulk-editing or CSV export/import of meta fields, which lets you clear titles at scale without opening each post individually. 🛠️ Fix Option 2 — Set Your SEO Plugin to Use the Default (CMS) Title Format Some SEO plugins allow you to choose the title source at a global or post-type level. Setting the title format to inherit from the CMS or leaving the global title template blank can prevent the plugin from overriding page-level values. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Project Activation and Schema Deployment Errors

Overview If your OTTO project fails to activate or you receive an error when trying to deploy schemas, this article explains what to do next. Because the specific causes of OTTO activation and schema deployment errors can vary and require investigation on the backend, the steps below are designed to help you gather the right information before reaching out to our support team. What to Check Before Contacting Support Before escalating, run through the following to help our team investigate faster: - Note the exact error message you are seeing (for example, 'unable to process request' or any other specific wording). - Identify which OTTO project is affected — have the project name and the associated website URL ready. - Note the approximate date and time when the error first occurred. - Try refreshing your browser and attempting the action again. If the error persists after a refresh, it is unlikely to resolve on its own. - Check whether the issue affects one specific project or all projects in your account, and note that detail when you reach out. What to Have Ready When You Escalate Our support team will need the following details to investigate your OTTO activation or schema deployment error: - Your account email address and the name of the affected workspace. - The exact error message displayed when the failure occurs. - The name of the affected OTTO project and the website it is connected to. - A screenshot or screen recording of the error if possible. - The timestamp of when the error occurred. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🔧 Fix Title Tags and OTTO Connection Issues

🧭 Overview If your title tags have stopped displaying on your site, or your Search Atlas dashboard shows an unclear or conflicting OTTO connection status, this guide walks you through the root causes and the correct fixes — step by step. Generic cache-clearing rarely solves these issues on its own. This article helps you identify whether the problem stems from a plugin update, an OTTO sync failure, or a dashboard state mismatch. 🔍 Step 1: Identify the Root Cause Before taking any action, determine which of the following scenarios applies to your situation: - Title tags stopped displaying recently: A plugin update — either to the Search Atlas plugin or a conflicting SEO plugin — is the most common cause. - OTTO connection shows as connected and disconnected simultaneously: This is a dashboard state mismatch, not a true connection failure. - Title tags were never applied despite OTTO being enabled: OTTO may not have completed its sync after the initial connection. - Title tags disappeared after clearing your site cache: The cache clear may have exposed an underlying sync issue that was previously masked. 🔌 Step 2: Check Your OTTO Connection Status A conflicting status display (for example, showing both active and inactive at the same time) usually means the dashboard state has not refreshed after a recent change. Follow these steps to verify your true connection status: 1. Navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Locate your connected site and check the OTTO status indicator. 3. Hard-refresh the page using Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force the dashboard to reload its current state. 4. If the status remains conflicting after the refresh, disconnect OTTO and reconnect it: click the site settings icon, select Disconnect OTTO, wait 30 seconds, then reconnect. 5. After reconnecting, confirm the status shows a single, clear Connected state before proceeding. 🔄 Step 3: Validate Plugin Sync After a Plugin Update Plugin updates — to Search Atlas or any other SEO plugin on your WordPress site — can interrupt the sync between OTTO and your live site. If a title tag was applied by OTTO before the update, the update may have overwritten or deactivated it. 1. Log in to your WordPress admin panel. 2. Go to Plugins → Installed Plugins and check the version of the Search Atlas plugin currently installed. 3. If the update was recent and coincides with when title tags stopped displaying, roll back to the previous stable version using a plugin such as WP Rollback, then test whether title tags reappear. 4. Check that no other active SEO plugins (such as Yoast SEO or Rank Math) are also writing title tags to the same pages. Conflicting plugins will override OTTO's output. 5. Deactivate any conflicting SEO plugins, then return to Search Atlas and re-apply the affected title tags through OTTO. 🗄️ Step 4: Re-sync OTTO After Resolving Plugin Conflicts Once you have confirmed a clean plugin environment, force OTTO to re-sync so that your title tag changes are pushed live correctly. 1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Open the OTTO dashboard for your affected site. 3. Locate the title tag optimizations that failed to display and re-deploy them by selecting the relevant recommendations and clicking Apply. 4. Visit the affected pages on your live site and inspect the page source (right-click → View Page Source) to confirm the correct title tag appears inside the <title> tag in the <head> section. 🗑️ Step 5: Know When Cache Clearing Actually Helps Cache clearing is only effective in a specific scenario: when OTTO has already successfully synced and applied the correct title tags, but your browser or server cache is serving an older cached version of the page. It does not fix broken plugin sync, OTTO connection failures, or conflicting plugin overwrites. - Clear your cache when: OTTO shows the title tag as applied, the page source confirms the correct tag, but the tag is not visible in browser previews or social share tools. - Do not rely on cache clearing when: The page source itself shows the wrong or missing title tag — this confirms the issue is at the sync or plugin level, not the cache layer. - To clear your WordPress cache, use your active caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) and purge all cached files. Then re-check the page source. ✅ Quick Diagnostic Checklist - OTTO connection status shows a single clear Connected state after a hard refresh - No conflicting SEO plugins are active on your WordPress site - The Search Atlas plugin is on a stable, tested version - Title tags are confirmed as applied inside OTTO's dashboard - Page source shows the correct <title> tag in the <head> - Cache was cleared only after confirming the correct tag is in the page source 💬 Still Seeing Issues? If you have completed all the steps above and title tags are still not displaying, or OTTO's connection status continues to show a conflict, our team can investigate the sync logs directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Metadata Fields Not Saving Fixes

🔍 Overview Some users found that manually edited metadata fields in OTTO — including meta titles, meta descriptions, meta keywords, and Twitter site fields — appeared to accept new values but did not save or deploy them. The platform would show the edited text without actually applying the changes. This was caused by a confirmed bug where the platform stored the text but silently failed to complete the save and deployment process. This bug has been fixed and the resolution is now live. ✅ What Was Happening To be specific, the issue affected the following fields when edited manually inside OTTO: - Meta title (title tags) - Meta description - Meta keywords - Twitter site fields When a user typed new values into these fields, the save action would appear to accept the input but failed to complete the approval and deployment step. As a result, the changes never took effect on the site, even though they appeared to be accepted in the interface. 🚀 Current Status: Bug Is Fixed The engineering team identified and resolved this issue. The fix was deployed and is now live. You should be able to manually edit and save metadata fields in OTTO without any problems. If you were affected by this bug before the fix, your previously entered values may not have been deployed. You will need to re-enter and save those fields to ensure the changes are applied correctly. 📋 Steps to Re-Enter and Save Your Metadata 1. Open the OTTO session for the affected site. 2. Navigate to the on-page metadata section where the affected fields are displayed. 3. Manually re-enter the values for any fields that did not save previously, such as meta title, meta description, meta keywords, or Twitter site fields. 4. Save the changes. The approval and deployment steps should now complete successfully. 5. Verify that the saved values are reflected as approved and that the changes have been deployed to your site. 🆘 Still Experiencing Issues? If you re-enter your metadata values and they still do not save or deploy correctly after the fix, please let us know by reaching out to our support team so we can investigate further.

Fix OTTO Schema Deployment Errors and Failures

Overview When OTTO generates schemas automatically, the AI can occasionally produce invalid data — such as numeric fields stored as text, corrupted characters (like malformed ampersands), or null-valued fields. These errors cause schemas to fail validation and become stuck in an undeployed state, and you may see a message like No deployable recommendation found. This article explains the known issue and provides concrete steps you can take to resolve it. In cases where the malformed data cannot be corrected through the steps below, the Search Atlas support team can investigate and resolve the affected recommendations directly. Common Symptoms - Attempting to deploy a schema has no effect. - A message appears saying No deployable recommendation found. - Schemas remain stuck in an undeployed state even after repeated attempts. - Schemas were generated for product pages that have no review or rating data, resulting in empty or invalid fields. What To Do 1. Identify the affected schemas. Navigate to the OTTO section of the platform and locate the schemas that are failing to deploy. Note which recommendations are sitting in an undeployed or pending state. 2. Check for obvious data issues. Look at the field values in the affected schema recommendations. Common problems include: numeric fields (such as width, height, price, or rating values) appearing as text strings rather than numbers; special characters that look corrupted or broken (such as malformed ampersands in titles or descriptions); and fields that are empty or contain null values where real content is expected. 3. Edit the affected schema fields manually. If you can identify the malformed field, edit it directly within the schema recommendation to correct the value — for example, change a text-formatted number to a proper numeric value, remove corrupted characters, or delete empty fields that are causing validation failures. Save the changes and attempt to deploy the schema again. 4. Remove invalid review or rating fields for pages with no review data. If a schema was generated for a page that has no reviews or ratings, open the schema recommendation and remove the review and rating fields entirely. Schemas without those fields can deploy successfully when the source page does not contain that data. Save and attempt deployment again. 5. Attempt deployment after corrections. After editing the affected fields, try deploying the schema again. In most cases, correcting the malformed or empty fields resolves the validation error and allows the schema to deploy successfully. 6. Contact Search Atlas support if schemas remain stuck. If you have corrected the visible field issues and the schema still cannot be deployed, reach out to the support team with the details of the affected schemas and account. The team can investigate the underlying data at the account level and resolve any remaining malformed recommendations directly. Why This Happens The OTTO AI schema generator can produce field values in the wrong format or leave required fields empty when source page data is missing or ambiguous. This results in schemas that fail internal validation and cannot be deployed until the underlying data problems are corrected. If you need further assistance, please contact the Search Atlas support team through the chat widget or your account's support channel and we'll be happy to help.

🛠️ Fix OTTO Installation, Redirects, and Blank Recommendations

🔍 Overview This article covers three connected issues that can occur during or after an OTTO site installation: the installation staying stuck in a Processing state, the OTTO script appearing as Not Found despite correct placement, and OTTO recommendations showing Length: 0 across crawled pages even after a fix is deployed. These issues are often caused by 301 redirect conflicts that interfere with OTTO's internal page-fetching process. ⚙️ Why This Happens OTTO verifies its installation by fetching your pages internally. When a 301 redirect is present — for example, between a www and non-www version of your site, or between trailing-slash and non-trailing-slash URLs — that redirect can interfere with OTTO's ability to confirm the script is installed, and the installation loop continues indefinitely. This same redirect behaviour also prevents OTTO from reading page content, which causes recommendations to remain blank after deployment. Additionally, OTTO may list both the 301 and 200 versions of a redirected URL in its crawl data, leading to duplicate entries and data gaps that further block recommendation generation. ✅ Step 1 — Confirm Your Script Is Installed Correctly 1. Open your OTTO SEO dashboard and navigate to your connected site. 2. Locate the script snippet provided for your site. 3. Verify the snippet is placed inside the <head> tag on every page of your site, including your homepage. 4. If you are using a WordPress plugin, confirm the plugin is active and has not been deactivated by a recent update. 🔄 Step 2 — Identify and Resolve 301 Redirect Conflicts A 301 redirect between your site's www and non-www versions, or between trailing-slash and non-trailing-slash URLs, is the most common cause of a stuck installation. Follow these steps: 1. Determine the canonical version of your domain — for example, https://example.com (non-www) versus https://www.example.com (www). 2. In your OTTO SEO dashboard, confirm that the domain entered during setup exactly matches your canonical version, including the correct www or non-www prefix. 3. Check your server or WordPress settings (.htaccess, Nginx config, or redirect plugin) and ensure all traffic resolves to a single canonical URL without chained or conflicting redirects. 4. If you use a caching plugin or CDN, purge all caches after making redirect changes. 🔁 Step 3 — Trigger a Reprocess After resolving redirect conflicts and confirming your script is correctly installed, trigger a reprocess of your site within the OTTO SEO dashboard. This allows OTTO to re-crawl your pages and generate recommendations based on accurate page content. 🛠️ When to Escalate If you have completed the steps above and OTTO remains stuck in Processing, the script still shows as Not Found, or recommendations continue to show Length: 0, the issue may require a backend investigation. When contacting support, please have the following ready: your site's domain name, the exact error or status shown in your dashboard, and the approximate date and time you first noticed the problem. If you need further assistance, open 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 Schema Sync, FAQ Indexing & Timezone Metadata

🔍 Overview OTTO's schema deployment engine occasionally encounters three related issues that can surface together: FAQ schema generated for content that isn't visibly rendered on the page, a mismatched deployment inventory where the dashboard count doesn't reflect what's actually live, and malformed ImageObject or timezone metadata that conflicts with your Google Business Profile (GBP) listings. This article explains why these issues occur and what to expect while our team works to resolve them. ⚠️ Why Hidden FAQ Content Gets Indexed OTTO generates FAQ schema based on structured content signals it detects on your page. In some cases, FAQ blocks exist in the page's underlying HTML — added by a plugin, theme, or CMS template — but are hidden from visitors using CSS or JavaScript. Search engines can still crawl and index this hidden structured data, which may cause a mismatch between what users see and what appears in search results. This issue is tracked and being actively resolved in our development pipeline. 📊 Understanding the Deployment Inventory Mismatch If the number of active schema items shown in your OTTO dashboard does not match what you expect to be live, this is a known sync issue our engineering team is investigating. The discrepancy may appear across schema types including FAQ, ImageObject, and LocalBusiness entries. Because this is a backend synchronization issue, resolution requires action from our support team. To help us investigate and correct the mismatch as quickly as possible, please have the following ready when you reach out: - The name of the affected OTTO project - The specific URLs where the schema discrepancy appears - The schema types involved (e.g. FAQ, ImageObject, LocalBusiness) - Screenshots of the inventory count you are seeing versus what you expect - Any error messages shown in your OTTO dashboard or Google Search Console 🕐 Timezone Metadata and GBP Conflicts Timezone metadata errors can cause your opening hours or other time-sensitive structured data to conflict with your live Google Business Profile listings. This type of error is corrected on the backend and cannot be resolved through dashboard settings alone. When contacting support about a timezone metadata issue, please have ready: - Your OTTO project name - The affected GBP listing name and location - The incorrect timezone or hours currently showing - The correct timezone or hours that should be reflected If you need further assistance, open 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 Atlas Brain 'Unable to Process Request' Error

Understanding the Error If Atlas Brain is not processing requests or your schema deployments are failing, the most common cause is that your OTTO project has not been activated. Atlas Brain relies on an active OTTO project to process requests and deploy schemas to your website. Without activation, Atlas Brain cannot complete tasks for that project. Step 1 — Confirm Your OTTO Project Status Before troubleshooting anything else, verify whether your OTTO project is active: 1. Open your OTTO project for the website you are trying to work with. 2. Check whether the project is active or inactive. If it is not yet active, proceed to Step 2. 3. If the project is already active, skip to Step 3 to verify your connection settings. Step 2 — Activate Your OTTO Project If your OTTO project is not yet activated, follow these steps to activate it: 1. Open your OTTO project for the website you want to work with. 2. Locate the activation option associated with the project and enable it. 3. Wait for the activation process to complete. Once the project shows as active, return to Atlas Brain and attempt your request again. Step 3 — Deploy Your Schema After Activation With your OTTO project active, you can now deploy schemas successfully. Follow this workflow: 1. Open your activated OTTO project for the website. 2. Locate the schema-related options within the project. 3. Review the schema recommendations generated by Atlas Brain for your site. 4. Select the schemas you want to deploy and initiate the deployment. 5. Atlas Brain will push the selected schemas to your website once deployment is confirmed. If Atlas Brain still returns an error after activation, check that your website is correctly connected to OTTO and that your site credentials or integration settings are up to date. If the issue persists, please have your project name, the exact error message, and the time the error occurred ready before reaching out so our team can investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO Pixel Installation Troubleshooting for WordPress

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

🛠️ Fix OTTO Title Tags Overridden by WordPress SEO Plugins

🔍 Why This Happens OTTO SEO writes optimized title tags directly to your pages during its daily crawl cycle. However, if another WordPress SEO plugin — such as Yoast SEO, Rank Math, All in One SEO, or The SEO Framework — is active on your site, it will typically take priority over any externally applied title tag changes. This conflict prevents OTTO's suggestions from rendering as the live title on your website, even after a successful crawl. In short: two plugins are competing to control the same HTML element, and WordPress defaults to the one installed locally on your server. ⚙️ How to Confirm the Conflict 1. Open your browser and navigate to any page where OTTO applied a title tag suggestion. 2. Right-click the page and select View Page Source. 3. Press Ctrl+F (or Cmd+F on Mac) and search for <title>. 4. Compare the live title in the source code against the title OTTO suggested inside the platform. 5. If they differ, a conflicting plugin is almost certainly overriding OTTO's output. 🛠️ How to Fix the Conflict Choose the resolution method that best fits your workflow: - Option 1 — Disable title tag control in your SEO plugin (Recommended): Most SEO plugins let you turn off their title tag management without fully deactivating the plugin. For example, in Yoast SEO go to SEO → Search Appearance and ensure you are not overriding individual post/page titles. In Rank Math, navigate to Rank Math → Titles & Meta and clear any hardcoded title templates. Consult your specific plugin's documentation for the exact setting. - Option 2 — Remove the conflicting SEO plugin entirely: If you are using another SEO plugin solely for title and meta tag management, and OTTO is now handling that function, you can deactivate and delete the conflicting plugin from your WordPress dashboard under Plugins → Installed Plugins. - Option 3 — Manually enter OTTO's titles inside your SEO plugin: If you need to keep your existing SEO plugin active for other features, copy each title suggestion from OTTO and paste it manually into that plugin's title field for each page. This ensures both tools are aligned on the same value. 🔄 Re-Running the OTTO Crawl After Fixing 1. Log in to Search Atlas and go to OTTO SEO in the left sidebar, then open All Sites (SEO Automation) inside it (or navigate to /seo-automation-v3). 2. Select the project where the title tag issue occurred. 3. Locate the affected pages in the OTTO task list and confirm the title tag suggestions are still marked as applied. 4. Trigger a new crawl or wait for the next scheduled daily crawl to run. 5. After the crawl completes, repeat the View Page Source check described above to verify the correct title is now live. ✅ Best Practices to Prevent Future Conflicts - Run only one tool responsible for title and meta tag management at a time — either OTTO or your WordPress SEO plugin, not both. - After onboarding OTTO to a site, audit your installed plugins and disable any overlapping SEO features. - Document which plugin manages which SEO element so your team avoids re-enabling conflicting settings during future site updates. - After any WordPress plugin update, re-check a sample of your OTTO-managed title tags to ensure nothing was reset by the update. 💬 Still Need Help? If you have followed all the steps above and OTTO title tags are still not appearing correctly 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 WordPress Status Verification and Sync Times

🧩 Overview After installing the Otto pixel UUID code on a WordPress site, the project dashboard may continue to show a Not Installed status for a short period. This is expected behavior. Search Atlas needs time to detect and verify the pixel on your site before the status updates. This article explains the sync timeline, what causes delays, and the steps to take if the status does not update. ⏱️ Expected Sync Timeline Once the Otto pixel UUID code has been correctly added to your WordPress site, the status in Search Atlas should update automatically. Here is what to expect: - Typical sync time: 5–15 minutes after installation. - Maximum wait time: Up to 60 minutes in some cases, depending on server response times and caching configurations. - Status location: Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3), then open your project to view the current pixel status. If the status updates to Installed within this window, no further action is needed. If the status still shows Not Installed after 60 minutes, proceed to the troubleshooting steps below. 📋 How to Verify Your Otto Pixel Installation Before waiting for the status to sync, confirm that the pixel was added correctly by following these steps: 1. Log in to your WordPress admin dashboard. 2. Navigate to the theme or plugin where you placed the Otto pixel UUID code. Common locations include your theme's header.php file, a header script plugin, or a tag manager integration. 3. Confirm the full UUID code is present and has not been altered, truncated, or wrapped in extra characters. 4. Ensure the code is placed inside the <head> section of every page, not just the homepage. 5. Save your changes and clear any caching plugins or server-side cache (see the caching section below). 6. Visit your live website and use your browser's View Page Source function (right-click → View Page Source) to search for your UUID. If it appears in the source code, the pixel is present on the page. ⚠️ Common Reasons the Status Stays 'Not Installed' Several factors can prevent the status from updating even when the pixel code appears to be in place: - Caching plugins: WordPress caching plugins such as WP Rocket, W3 Total Cache, or LiteSpeed Cache can serve old versions of your pages that do not yet include the pixel. Clear all caches immediately after installation. - Server-level caching: Hosting providers may cache pages at the server level. Contact your host or flush the server cache from your hosting control panel. - CDN caching: If your site uses a CDN such as Cloudflare, cached edge copies of your pages may not reflect the new code. Purge the CDN cache after installation. - Incorrect code placement: The UUID must be in the <head> section. Placing it in the footer or body can cause detection failures. - Code modified or incomplete: Copy the UUID code directly from Search Atlas without reformatting. Extra spaces, missing characters, or HTML encoding errors will break detection. - New project delay: Newly created projects may take slightly longer for the first status check to complete. Allow up to 60 minutes before escalating. 🔄 Steps to Take If Status Does Not Update After 60 Minutes 1. Confirm the pixel is visible in your page source as described above. 2. Clear all caches — WordPress plugins, server cache, and CDN — then wait an additional 10 minutes. 3. Return to OTTO SEO → All Sites (SEO Automation) in the left sidebar and refresh your project page to trigger a new status check. 4. Double-check that the UUID code in WordPress exactly matches the code shown in Search Atlas. Do not retype it manually; copy and paste directly from the platform. 5. If your site uses a security plugin such as Wordfence or iThemes Security, verify that outbound requests from Search Atlas are not being blocked. 6. Temporarily disable caching and security plugins, visit your site, then recheck the status in Search Atlas. ✅ Confirming a Successful Installation The project status will change from Not Installed to Installed once Search Atlas successfully detects the pixel. You do not need to take any manual action to trigger this — the platform checks automatically. Once installed, Otto can begin crawling and optimizing your site. Keep caching plugins configured to exclude or delay caching on newly updated pages to avoid similar delays in the future. 💬 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 Bulk AI Image Alt Text Generation Error

🔍 Overview Some users encountered an error message — 'A valid integer is required' — when selecting all images and attempting to run bulk AI alt text generation in OTTO. This prevented alt text from being generated for any images in the selection. This issue was confirmed as a bug and has since been fully resolved by our engineering team. No workaround is needed — the fix is live in production. ⚙️ What Caused the Issue The error was caused by a bug in the bulk image alt text generation process inside OTTO. When a user selected all images and triggered bulk generation, the system passed an invalid value that caused the process to fail immediately with the 'A valid integer is required' message. The issue was tracked and resolved under an internal engineering fix for bulk alt text generation. ✅ What You Should Do Now 1. Navigate to the OTTO image alt text section in your Search Atlas platform. 2. Access the area where you previously experienced the error. 3. Select your images and run the bulk AI alt text generation again. 4. The process should now complete successfully without displaying any error message. If the generation completes but changes do not appear deployed, allow a few moments and refresh the page, as bulk operations on large image sets may take additional time to fully apply. 📊 Additional Notes on Large Image Sets If you are working with a very large image inventory, be aware that bulk alt text generation may take longer to complete. For especially large sets, the process may time out or report completion before all changes are fully applied. If you notice this behaviour, try processing images in smaller batches to ensure reliable results. 💡 Still Seeing the Error? If you have refreshed the page and are still experiencing the 'A valid integer is required' error after the fix has been deployed, it is possible your browser is serving a cached version of the platform. Try the following steps: - Clear your browser cache and cookies, then reload the platform. - Try using a different browser or an incognito/private window. - Ensure you are logged in to the correct Search Atlas account and workspace. If the issue persists after these steps, if you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Duplicate OTTO JavaScript and GSC Instant Indexing

Overview Two issues can appear together on WordPress sites using OTTO SEO: a duplicate JavaScript warning caused by multiple OTTO pixel installations, and a Google Search Console (GSC) instant indexing connection failure. This guide walks you through the general approach to resolving both — removing the duplicate first, then reconfiguring the Search Atlas plugin with your UUID. Step 1: Identify All OTTO JavaScript Installations The duplicate warning appears when the OTTO pixel is loaded more than once on the same page. Before making any changes, check every location where the script could be installed: - Theme files: In your WordPress admin, look inside your theme's header and footer files for any snippet containing otto or your OTTO UUID string. - Code Snippets or similar plugins: Check any active snippet that references OTTO or inserts a tracking script. - Other plugins: Check any header/footer injection plugins for OTTO script fragments. Make a note of every location where the script appears before you remove anything. Step 2: Remove All Duplicate OTTO Scripts Remove the OTTO script from every location you found except the official Search Atlas WordPress plugin — that will be your single, authoritative source after reconfiguration. 1. Delete or disable the OTTO snippet in any code snippets plugin you are using. 2. Remove any OTTO script lines from your theme's header and footer files, then save each file. 3. Disable any other header/footer injection plugins that were loading the script. Step 3: Reconfigure the Search Atlas WordPress Plugin with Your UUID Once duplicate scripts have been removed, reconfigure the Search Atlas WordPress plugin using your OTTO UUID. Your UUID is available within your Search Atlas account. Enter it into the Search Atlas plugin on your WordPress site to reconnect the plugin as the single authoritative source of the OTTO pixel on your site. If you are unsure where to locate your UUID or which field to use in the plugin, contact our support team for guided assistance — they can walk you through the exact steps for your account. Step 4: Reconnect Google Search Console Instant Indexing After the plugin is properly configured with your UUID, reconnect your GSC instant indexing integration through the Search Atlas platform. If you encounter any difficulty completing this step, our support team can assist you 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 Shopify Pixel Duplicate Text & H1 Issues

🔍 What Is Causing the Duplicate Text? When a tracking pixel is placed incorrectly inside your Shopify theme, it can interfere with how your page renders. The most common result is duplicate text appearing on your storefront, especially near your H1 heading or logo. This usually happens because the pixel snippet is injected inside a Liquid block that outputs visible HTML content, rather than staying within a safe, non-rendering section of the <head>. The three most frequent causes are: - The pixel code is placed inside a Liquid section or block that also renders visible page elements. - The snippet is added after the closing </title> tag but before critical theme elements, disrupting the render order. - The pixel is embedded inside the header section file (e.g., header.liquid) rather than in the global theme.liquid file. ⚙️ Where to Correctly Place Your Pixel in Shopify The safest and recommended location for any tracking pixel in Shopify is inside the global theme.liquid file, placed immediately before the closing </head> tag. This keeps the script in the document head without touching any rendered content on the page. 1. Log in to your Shopify Admin and go to Online Store > Themes. 2. Click Actions > Edit Code on your active theme. 3. In the left-hand file tree, open Layout > theme.liquid. 4. Use Ctrl+F (or Cmd+F on Mac) to search for </head>. 5. Place your full pixel snippet directly above the closing </head> tag — not inside any Liquid {% section %} or {% block %} tags. 6. Click Save and reload your storefront to confirm the duplicate text is gone. 🚫 Common Mistakes to Avoid - Do not paste the pixel inside header.liquid, logo.liquid, or any section file — these files render visible HTML and will cause content duplication. - Do not wrap the pixel in any Liquid output tags such as #{{ }} or {% %}. Pure JavaScript or <script> tags only. - Do not add the pixel through a Shopify Custom HTML block in the theme editor — these blocks render inside the page body and can conflict with heading tags. - Avoid placing the pixel inside the <body> tag area unless the pixel provider explicitly requires a <noscript> body fallback, which should go immediately after the opening <body> tag. ✅ How to Verify the Fix Worked After saving your changes, follow these steps to confirm the issue is resolved: 1. Open your Shopify storefront in a new incognito or private browser window to bypass any cached version. 2. Visually inspect your homepage, product pages, and collection pages for any repeated text near the logo or H1 heading. 3. Right-click the page and select View Page Source. Search for your pixel code and confirm it appears only once, inside the <head> section. 4. Use a free tool like Google's Rich Results Test or browser DevTools (F12 > Elements tab) to check that only one <h1> tag exists per page. 💡 Using Google Tag Manager Instead If you manage multiple pixels or frequently update tracking scripts, consider deploying your pixel through Google Tag Manager (GTM). GTM gives you a single, safe container tag inside theme.liquid and lets you add or update pixels without editing theme code again. This significantly reduces the risk of accidental duplication or theme conflicts. To use GTM with Shopify, place the GTM <script> snippet before </head> and the <noscript> snippet immediately after the opening <body> tag — both in theme.liquid. 🆘 Still Seeing Duplicate Text? If you have followed all the steps above and the issue persists, the duplication may be caused by a conflicting app or a second pixel instance added through a Shopify app embed. Check Online Store > Themes > Customize > App Embeds and disable any embed that may be injecting additional scripts into your header or logo area. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO SEO Title Tag Edits Not Saving

🔍 Overview Some users found that after manually editing a title tag in the OTTO on-page optimization section and clicking save, the change would not stick — the system reverted the field back to the previous value. This was a confirmed platform issue that has since been resolved. ⚙️ What Was Happening When a user attempted to overwrite an OTTO-suggested title tag with their own version, the manual input was not being retained. The field would appear to accept the change, but after saving, the original value would be restored. This affected manual edits to title tags within the on-page optimization workflow. ✅ Current Status — Issue Resolved This issue was escalated to our engineering team and the fix has been deployed to production. Manual title tag edits in the on-page optimization section should now save correctly. 🚀 What You Should Do Now 1. Open OTTO SEO and navigate to the on-page optimization section for the site where you experienced the issue. 2. Locate the title tag field you previously tried to edit. 3. Enter your desired title tag and save the change. 4. Perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to confirm the value has been retained. If the value reverts, try saving once more. If you see an error message on screen when saving, note the exact wording before reaching out to support. If the edit saves and persists after a hard refresh, the fix is working correctly for your account. 🆘 Still Experiencing the Issue? If your title tag edits are still reverting after the fix, work through the following steps before escalating: 1. Clear your browser's cookies and cache completely, then open a new incognito or private browsing window and log back in to attempt the save again. This resolves the problem in many cases and rules out a browser caching issue. 2. If the issue persists in one browser but not another, a local browser extension or setting may be interfering — try a different browser to confirm. 3. If edits are still not saving after clearing cache and switching browsers, disconnect and reconnect OTTO for the affected site: go to OTTO settings, disconnect OTTO from the site, wait a few seconds, then reconnect it. After reconnecting, re-enter your manual edits, click Save, and perform a hard refresh to confirm the changes persist. If none of the above steps resolve the issue, please report it immediately so our team can investigate your specific setup. Open 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 A platform-side error was occurring silently in the background whenever a manually edited OTTO suggested fix was submitted. This meant the save action appeared to complete on screen but the data was never written.

🔧 Fix Duplicate Heatmap Entries and OTTO Pixel Scripts

What Causes These Duplicates? Two separate but related issues can occur when setting up Local SEO Heatmaps and the OTTO pixel on a WordPress site: - Duplicate business entries in Local SEO Heatmaps — This happens when the same Google Business Profile (GBP) location is connected or imported more than once. Common triggers include re-connecting a GBP account after a sync error, importing locations multiple times, or creating a new project for a business that already has an active one. - Duplicate OTTO pixel scripts on WordPress — This occurs when the OTTO pixel snippet is added manually (via a theme, plugin, or header editor) while the Search Atlas WordPress plugin is also active and injecting the same script automatically. Both methods running simultaneously result in the pixel firing twice per page load. Understanding the root cause lets you fix the issue correctly and prevent it from recurring. How to Remove Duplicate Business Entries in Local SEO Heatmaps 1. In the left sidebar, go to Local → Local SEO Heatmaps. 2. Review your list of GBP projects. Look for any business name that appears more than once with the same address or location details. 3. Click into each duplicate entry and compare the creation date, heatmap data, and connected GBP account to identify which entry is the original and which is the duplicate. 4. Select the duplicate entry you want to remove and use the available project settings or delete option to permanently remove it. 5. Repeat for any additional duplicates until only one entry per business location remains. Important: Before deleting any entry, confirm it does not contain unique heatmap scan data you want to keep. If both entries hold valuable data, export or note the results before removing the duplicate. How to Remove Duplicate OTTO Pixel Scripts on WordPress The OTTO pixel should only be injected once per page. Follow these steps to identify which method is causing the duplication and remove the extra instance. 1. Log in to your WordPress admin dashboard. 2. Check whether the Search Atlas WordPress plugin is installed and active by going to Plugins → Installed Plugins. If it is active, the plugin handles pixel injection automatically — you do not need to add the script manually anywhere else. 3. If you also added the pixel script manually, locate and remove it. Common places where manual scripts are added include: - Your theme's header or footer template files - SEO or header management plugins that allow custom code injection - Any other plugin or tool configured to insert scripts site-wide 4. After removing the manual instance, save your changes and clear any site or server cache. 5. Reload a page on your site and verify that the OTTO pixel script appears only once in the page source. If you need further assistance, open 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 GSC Connection Slot Limit Errors

🧩 What Is This Error? When you try to connect Google Search Console (GSC) to a project inside OTTO SEO, you may see an error message indicating that OTTO could not create a new service connection for your project. The most common cause is that your current Search Atlas plan has reached its maximum number of OTTO plan slots, so no additional projects can be activated. 📊 Understanding OTTO Plan Slots Every Search Atlas subscription includes a set number of OTTO plan slots. Each slot represents one active project that OTTO SEO can manage and connect to GSC. Once all slots are occupied, OTTO cannot activate new projects until a slot is freed up or your plan is upgraded. - Plan slot: One slot = one active OTTO-managed project with GSC connected. - Slot limit reached: No new GSC connections can be established until a slot becomes available. - Inactive projects still count: Projects that are set up but not actively used may still hold a slot. 🛠️ How to Fix the Error Follow these steps to resolve the slot limit issue and successfully connect GSC to your project. 1. Check your current slot usage. Review how many projects currently have OTTO activated and GSC connected by navigating to the OTTO SEO section of your account. 2. Identify projects you no longer need. Look for projects that are inactive, paused, or no longer relevant to your SEO work. 3. Deactivate OTTO on unused projects. Open the project you want to free up and deactivate OTTO SEO for that project. This releases the slot back to your plan allowance. 4. Retry the GSC connection. Return to the project where you received the error. Attempt to connect GSC again — with a free slot now available, the connection should complete successfully. 5. Verify the connection. Confirm that GSC data is now flowing into your project inside the OTTO SEO dashboard. 🚀 Upgrade Your Plan for More Slots If you need OTTO SEO active across more projects simultaneously, upgrading your Search Atlas plan is the best long-term solution. A higher-tier plan provides additional OTTO slots so you can manage a larger portfolio of sites without hitting connection limits. - Review your current plan and available upgrade options via the top-right avatar → Billing (Plans & Top-ups). - Upgrading instantly increases your slot allowance — no need to deactivate existing projects. 💡 Tips to Avoid This Error in the Future - Regularly audit your active OTTO projects and deactivate any that are no longer in use. - Before adding a new site to OTTO, confirm you have at least one free slot available. - Align your Search Atlas plan tier with the number of sites you actively manage through OTTO SEO. If you need further assistance, open 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 Logo Error in Creative Assets

🔍 What Is This Issue? When trying to publish a campaign, you may encounter a persistent error that prevents the campaign from going live. In many cases, this error is triggered because the logo file is not present in your Creative Assets — even if the logo already exists in your Brand Vault. This mismatch causes the publish action to fail. 📋 Why Does This Happen? Your Brand Vault and your Creative Assets are two separate areas of the platform. A file saved in your Brand Vault does not automatically appear in Creative Assets. If a logo was added to Brand Vault but was never explicitly added to Creative Assets, the campaign will not be able to reference it, resulting in a publish error. This is a known sync limitation that has been investigated and improved, but re-adding the file manually is the reliable fix if you encounter this issue. ✅ How to Fix It 1. Identify the error: If your campaign fails to publish and you see a persistent error message, suspect a missing asset in Creative Assets — particularly your logo file. 2. Check your Creative Assets: Navigate to the Creative Assets section of your campaign. Review whether your logo file is listed there. 3. Check your Brand Vault: Confirm that the logo file exists in your Brand Vault. If it is there but not in Creative Assets, this confirms the issue. 4. Re-add the logo to Creative Assets: Manually add the logo file directly to Creative Assets. You can typically do this by uploading the file again or selecting it through the available asset options within the Creative Assets section of your campaign. 5. Attempt to publish again: Once the logo is present in Creative Assets, retry publishing your campaign. The error should be resolved. 💡 Tips to Avoid This Issue - Whenever you set up a new campaign, verify that all required brand assets — especially your logo — are present in Creative Assets, not just in your Brand Vault. - If you see a vague publish error, always check whether any required files are missing from Creative Assets before investigating other causes. - After adding new assets to your Brand Vault, manually add them to Creative Assets for any campaigns where they are needed. 🚀 Still Seeing the Error? If re-adding the logo to Creative Assets does not resolve the publish error, or if the logo file does not appear as an option when you try to add it, there may be a deeper sync issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Product Schemas Stuck in Suggested Status

🔍 Overview When OTTO SEO generates Product schemas, they may sometimes remain in Suggested status and cannot be deployed. This can happen due to validation issues, missing content, or a stale schema state that prevents OTTO from marking the schema as ready. This article explains the most common causes and walks you through the steps to resolve them. ⚙️ Why Product Schemas Get Stuck in Suggested There are several reasons a Product schema may not advance past Suggested status: - Validation failure (is_valid = False): OTTO runs an internal validation check before allowing deployment. If the schema fails validation — even silently — it is blocked from moving forward. - Missing or empty schema content: In some cases, OTTO generates a schema entry but the underlying markup content is empty or unavailable. The schema appears in the list but has nothing to deploy. - Stale schema state: After regeneration, a schema can get stuck in a review or suggested state with no visible fields to correct, leaving no clear path to deployment. - Irrelevant schema suggestion: OTTO may occasionally suggest a schema type that does not match the page content, which can cause the suggestion to stall without clear next steps. 🚀 How to Resolve Stuck Product Schemas 1. Navigate to OTTO SEO. In the left sidebar, click OTTO SEO → SEO Automation (All Sites) or go directly to /seo-automation-v3. 2. Locate the affected URLs. Find the specific pages where Product schemas are showing as Suggested. You can use the schema filter or search by URL to narrow down the list. 3. Review the schema details. Click on the schema to open its details panel. Check whether the schema has populated content and review any fields flagged for correction. 4. Edit and complete any required fields. If fields are visible and incomplete, fill them in with accurate product information (name, price, availability, description, etc.) and save your changes. 5. Regenerate the schema if content is missing. If the schema panel appears empty or shows no editable fields, use the regenerate option to trigger a fresh schema generation for that URL. Wait for OTTO to complete the process before attempting deployment again. 6. Attempt deployment. Once the schema shows valid content and passes the internal check, the Deploy button should become active. Click it to push the schema live. 7. Verify deployment status. After deploying, confirm the schema status has changed from Suggested to Deployed in the schema list for those URLs. 💡 Tips to Prevent Schemas Getting Stuck - Ensure the target page has sufficient product-related content before OTTO generates a schema — sparse pages are more likely to produce incomplete suggestions. - After regenerating a schema, allow a few minutes for OTTO to fully process before reviewing or deploying. - If a schema type suggested by OTTO does not match the page (for example, an Article schema on a product page), dismiss it and manually select Product as the schema type before regenerating. - Regularly review your schema list for any items sitting in Suggested status for more than 24 hours, as these may require manual intervention. 🆘 When to Contact Support If you have followed all the steps above and your Product schemas are still stuck in Suggested status — especially if the Deploy button remains inactive or the schema content appears empty after regeneration — our team can trigger a manual deployment on your behalf. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please have the following ready to speed up the resolution: - The full URLs of the affected pages - The domain or project name in OTTO SEO - A screenshot of the schema status panel for each affected URL - Any error messages or empty field warnings you have observed

🛠️ Fix ImageObject Schema Errors and Manage OTTO Schema Settings

🔍 Overview After connecting your WordPress site to OTTO, you may notice ImageObject metadata validation errors appearing in Google Search Console (GSC). These errors are typically caused by conflicting schema output — OTTO generates its own structured data, and if a separate schema plugin is also active on your site, both sources attempt to output schema markup at the same time. The result is duplicate or malformed structured data that GSC flags as invalid. The good news: OTTO has a built-in schema management feature inside your project settings. You do not need a third-party plugin to manage schema, and you do not need to leave OTTO to fix this. This article walks you through exactly how to resolve the issue. ⚙️ How OTTO Handles Schema OTTO can generate and inject structured data (schema markup) for your connected site on a per-page basis after you approve or publish the recommendation (unless OTTO auto-deploy is enabled). This includes common schema types such as Article, BreadcrumbList, WebPage, and ImageObject. Because OTTO manages schema natively, running an additional WordPress schema plugin alongside it will almost always produce conflicts. Common symptoms of a schema conflict include: - ImageObject validation errors in GSC under Enhancements or Rich Results - Duplicate structured data warnings in third-party schema testing tools - Unexpected schema types appearing that you did not configure 🗂️ Step 1 — Deactivate Your WordPress Schema Plugin Before adjusting anything in OTTO, remove the source of conflict by deactivating any schema or structured data plugin currently active on your WordPress site. Common plugins that conflict with OTTO include Rank Math, Yoast SEO (when schema output is enabled), Schema Pro, and WP Schema. 1. Log in to your WordPress Admin Dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the schema or SEO plugin generating structured data. 4. Click Deactivate. Do not delete it yet — confirm the errors clear first. If you rely on that plugin for other features (such as redirects or sitemaps), check whether those features can be handled by OTTO or a separate dedicated plugin before fully removing it. 🔧 Step 2 — Access OTTO Schema Settings in Project Settings OTTO gives you direct control over whether it outputs schema markup for your site. To access these controls: 1. Log in to your Search Atlas account. 2. From the left navigation, open OTTO SEO → All Sites (SEO Automation). 3. Select the project connected to the affected site. 4. Click the Settings icon or navigate to the Project Settings tab for that project. 5. Scroll to the Schema section. 6. Here you will see a toggle or option to enable or disable OTTO's schema output for the site. If you want OTTO to handle all schema going forward (the recommended approach), ensure the Schema option is enabled in OTTO and the WordPress plugin is deactivated. If for any reason you prefer to manage schema entirely through a plugin, you can deactivate schema in OTTO's settings so only one source outputs structured data. ✅ Step 3 — Validate the Fix in Google Search Console After resolving the conflict, confirm the errors are clearing in GSC: 1. Open Google Search Console for your property. 2. Go to Enhancements or Rich Results in the left sidebar. 3. Locate the ImageObject report showing errors. 4. Click into the report and select Validate Fix. 5. Google will re-crawl the affected URLs. Full validation can take several days depending on crawl frequency. You can also use Google's Rich Results Test tool to spot-check individual URLs immediately after making your changes, before GSC re-crawls. ❓ Frequently Asked Questions Will deactivating my schema plugin break my site's SEO? No. As long as OTTO's schema output is enabled for your project, OTTO will continue generating structured data for your site. You are switching the source, not removing schema entirely. Can I customize the schema OTTO outputs? OTTO manages schema output automatically based on your content. For specific customizations beyond the built-in controls, consult the OTTO project settings or reach out via the chat widget below. The errors are still showing after I made these changes — why? GSC does not update instantly. After clicking Validate Fix, allow 3–7 days for Google to re-crawl your pages. If errors persist after that window, there may be another plugin or theme function injecting schema. Use the Rich Results Test to inspect a live URL and check the page source for duplicate application/ld+json script blocks. Do I need to repeat these steps for multiple sites? Yes. Schema settings are configured per project in OTTO. If you manage multiple connected sites, check each project's settings individually. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot OTTO SEO Pixel on GHL

🔍 Overview After installing the OTTO SEO Pixel on a GoHighLevel (GHL) site, the Search Atlas dashboard should confirm the connection within about 15 minutes. If your dashboard still shows the Pixel as disconnected after 20 or more minutes, one of the common issues below is usually the cause. Work through each section in order until the Pixel shows as Connected. ✅ Before You Begin Confirm you have the following ready before troubleshooting: - Access to the GoHighLevel site builder for the website you are connecting. - Your OTTO SEO Pixel snippet — found in Search Atlas by navigating to OTTO SEO in the left sidebar, then opening SEO Automation inside it (URL: /seo-automation-v3), then selecting your project and opening the Pixel setup step. - A way to clear your browser cache and cookies. 🧩 Step 1 — Verify the Pixel Snippet Is Copied Correctly An incomplete or altered snippet is the most common reason the Pixel does not connect. 1. Go to OTTO SEO in the left sidebar of Search Atlas, then open SEO Automation inside it. 2. Open your project and locate the Pixel snippet in the setup panel. 3. Click Copy directly from the panel — do not retype or manually select the code, as this can introduce hidden characters. 4. Paste the snippet into a plain-text editor (such as Notepad or TextEdit) and confirm it starts with <script> and ends with </script> with no extra characters before or after. 📋 Step 2 — Confirm Placement in GHL The Pixel must be placed in a location that loads on every page of your site. In GoHighLevel, the correct location is the site-wide Header Tracking Code field. 1. Log in to GoHighLevel and open the Sites section. 2. Select the website you are connecting to OTTO SEO. 3. Click Settings (the gear icon) for that site. 4. Scroll to the Header Tracking Code field. 5. Paste the OTTO SEO Pixel snippet here. If other scripts are already present, paste the OTTO snippet on a new line after them — do not replace existing code. 6. Click Save and then Publish the site to push the change live. Important: Adding the snippet only to an individual page footer or a single funnel step will not satisfy the Pixel check. It must be in the site-wide header settings. 🌐 Step 3 — Confirm the Site Is Published and Publicly Accessible The Search Atlas system verifies the Pixel by scanning your live site URL. If the site is in draft mode or password-protected, the scan will fail. - Open your site's public URL in a private or incognito browser window to confirm it loads without a login prompt or "coming soon" page. - In GoHighLevel, ensure the site status is set to Published, not Draft. - If you use a custom domain, confirm DNS has fully propagated and the domain resolves correctly. 🔎 Step 4 — Manually Verify the Pixel Is Firing You can confirm the snippet is live on your site before waiting for the dashboard to update. 1. Open your site's public URL 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 ottoseo or the unique ID from your Pixel snippet. 4. If the snippet does not appear in the source, return to Step 2 and re-check your GHL settings. 5. If the snippet does appear, proceed to Step 5. ⏱️ Step 5 — Trigger a Manual Recheck in Search Atlas Once the snippet is confirmed live, prompt Search Atlas to re-scan your site. 1. Navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (URL: /seo-automation-v3). 2. Open your project and go to the Pixel setup step. 3. Click the Verify / Recheck button if available, or save your project settings to trigger a fresh scan. 4. Wait up to 15 minutes and refresh the page. The status should update to Connected. ⚠️ Common Mistakes to Avoid - Adding the snippet to only one page: The Pixel must load site-wide. Use the Header Tracking Code field in GHL site settings, not a single page. - Not publishing after saving: In GHL, saving alone does not push changes live. Always click Publish. - Using the wrong project's Pixel: Each OTTO SEO project generates a unique snippet. Make sure the snippet matches the project you are trying to connect. - Browser cache showing old source: If you recently added the snippet and the page source still looks old, hard-refresh with Ctrl + Shift + R (or Cmd + Shift + R on Mac) or use incognito mode. 💬 Still Not Connected? If you have followed all the steps above and the Pixel still shows as disconnected, our support team can review your specific setup 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.

Brand Vault Not Syncing Fresh OTTO Crawl Data

Overview Brand Vault pulls crawl data from OTTO to keep your brand's SEO context accurate and up to date. In some cases, Brand Vault may continue displaying older crawl data even after OTTO has completed a new site crawl — for example, after a site relaunch or a manual rescan. This article explains why this happens, what you should do, and what to expect. What Causes This Issue This problem is related to Brand Vault not syncing fresh data after a new OTTO site crawl completes. As a result, Brand Vault may continue showing previous crawl results rather than the latest data. What To Do If Brand Vault Shows Stale Data If you have completed a new OTTO crawl but Brand Vault is still displaying outdated information, we recommend contacting our support team so they can investigate and apply the appropriate fix for your account. To reach us, use the Get in touch button below, or message us directly through the chat — we will look into the sync issue for your account. Tips to Keep Brand Vault Data Accurate - Always run an OTTO scan after significant site changes, such as a relaunch, domain migration, or large content update. - Give the crawl time to fully complete before checking Brand Vault for updated data. - If you update brand information directly in Brand Vault, confirm that the changes are saved before relying on them for AI-assisted tasks. Need Further Help? If Brand Vault is still not reflecting your latest OTTO crawl data, our team is ready to investigate. Please reach out to our support team using the Get in touch button below and we will look into the issue for your account.

🔄 Fix Header Changes Not Appearing After Deletion

🧩 Why This Happens When you delete a header optimization in Search Atlas — such as an OTTO-managed header tag — the change is saved on the platform side. However, your website or browser may still be serving a cached version of the page, which means the old header value continues to appear on the frontend even though it has been removed from your settings. This is a standard caching behavior and is not a bug in Search Atlas. Clearing the relevant caches will resolve the issue in most cases. 🗺️ Where to Find Header Optimizations Header optimizations managed by OTTO or applied manually can be found within Search Atlas. Before clearing any cache, confirm the deletion was saved successfully by revisiting the relevant section of the platform and verifying the header optimization no longer appears in your settings. ✅ Step 1 — Confirm the Deletion in Search Atlas 1. Navigate to the section of Search Atlas where you made the change. 2. Locate the page or section where the header optimization was applied. 3. Confirm the OTTO tag or custom header value is no longer listed. 4. If the optimization is still present, delete it again and save your changes before proceeding. 🌐 Step 2 — Clear Your Browser Cache Your browser stores copies of web pages to load them faster. This cached version may still display the old header value after deletion. 1. Open your browser settings (usually accessible via the menu in the top-right corner). 2. Navigate to Privacy and Security or Clear Browsing Data. 3. Select Cached images and files (and optionally cookies if the issue persists). 4. Set the time range to All time to ensure no old data remains. 5. Click Clear data and then reload your website in a new tab. Quick shortcut: On most browsers, pressing Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) opens the clear cache dialog directly. 🖥️ Step 3 — Clear Your Website Server Cache If clearing the browser cache does not resolve the issue, your web server or hosting provider may be caching the page at the server level. The steps for this vary depending on your setup: - WordPress with a caching plugin (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache): Log in to your WordPress dashboard, go to the plugin settings, and select Clear All Cache or Purge Cache. - Cloudflare or other CDN: Log in to your Cloudflare dashboard, navigate to the Caching section, and select Purge Everything or purge the specific URL where the header change was made. - Other hosting providers: Refer to your hosting provider's documentation for instructions on purging or clearing the server-side page cache. 🔁 Step 4 — Verify the Fix 1. After clearing all relevant caches, open your website in a new browser tab or an incognito/private window. 2. Inspect the page header using your browser's developer tools (right-click → Inspect → Elements) to confirm the old header value is no longer present. 3. If the old header value still appears, repeat the cache-clearing steps for any additional caching layers (e.g., a secondary CDN or server-side object cache). If you need further assistance, open 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 Found' on Redirect Sites

🔍 Overview If your OTTO site scan shows "OTTO not found" even though the OTTO pixel script is present in your website's source code, the most common cause is a homepage redirect. When OTTO's crawler follows a redirect from your root domain to a different URL (such as a subdomain, a subfolder, or a campaign page), it may land on a page where the pixel is not installed — causing the scan to fail. This article explains why this happens, how to confirm it is the cause, and what steps you can take to get your site scanning successfully. ⚙️ Why This Happens When OTTO scans your site, it starts by fetching your homepage. If your homepage redirects to another URL, OTTO follows that redirect and checks the final destination page for its pixel. Common redirect scenarios that trigger this issue include: - Your root domain (e.g., example.com) redirects to a subdomain (e.g., www.example.com or services.example.com) - Your homepage redirects to a country or language subfolder (e.g., example.com/en/) - A WordPress or server configuration causes OTTO's fetch to land on an unexpected page - The pixel is installed only on the root domain page, not on the redirect destination In these cases, OTTO may report it cannot reach the homepage or detect the pixel, even though a standard browser visit works fine. ✅ How to Confirm a Redirect Is the Cause 1. Open a browser and navigate to the domain you registered in OTTO. 2. Note the URL shown in your browser's address bar after the page fully loads. If it differs from the domain you entered in OTTO, a redirect is occurring. 3. Right-click the final page and select View Page Source. Search for the OTTO pixel script. If the pixel is absent on the redirect destination, that confirms the problem. 🛠️ Steps to Fix the Issue 1. Install the OTTO pixel on the redirect destination. Identify the final URL your homepage redirects to and ensure the OTTO pixel script is present in the <head> section of that page. This is the most reliable fix in most cases. 2. Verify the pixel on all key pages. If your site uses multiple redirects or regional subfolders, confirm the pixel is present across all pages you want OTTO to manage. 3. Check your redirect settings. If your site runs on WordPress or another CMS, review any redirect plugins or server configuration settings that may be causing unexpected redirect behavior. 4. Re-run the OTTO scan. After installing or confirming the pixel on the redirect destination, trigger a new scan in OTTO to verify the pixel is now detected successfully. 📋 When to Escalate If you have confirmed the pixel is present on the redirect destination but OTTO still reports it as not found, please contact support. When reaching out, have the following ready: - The exact domain you registered in OTTO - The final URL your homepage redirects to - Confirmation of where the pixel is installed (e.g., a link to the page source) - Any error messages or scan results shown in OTTO If you need further assistance, open 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 UUID Mismatch with Cloudflare DNS

🧭 Overview If you set up OTTO SEO using Cloudflare DNS and are seeing a UUID mismatch error, the root cause is almost always the same: Cloudflare DNS integration does not automatically inject the correct OTTO UUID into your site's code. Generic troubleshooting steps like clearing cache or re-checking your page source will not resolve this. The fix requires you to disconnect Cloudflare from the OTTO setup and manually paste the correct script directly into your site's HTML. ⚠️ Why This Happens OTTO SEO works by injecting a unique tracking script — identified by a UUID — into your website's code. This UUID links your site to your OTTO workspace in Search Atlas. When customers choose the Cloudflare DNS setup path, they expect Cloudflare to handle the script delivery automatically. However, Cloudflare DNS only manages your domain's DNS records. It does not write, inject, or update the OTTO script in your site's source code. As a result: - Your site may appear connected in Cloudflare but the UUID in your page source is missing, outdated, or belongs to a different site. - OTTO cannot verify your site because the UUID it expects does not match what it finds — or finds nothing at all. - Cache-clearing, script re-validation, and re-checking the Installation Guide will not help because the script was never correctly placed in your code to begin with. ✅ How to Fix It: Manual Script Installation Follow these steps carefully to resolve the UUID mismatch. 1. Navigate to SEO Automation. In the left sidebar, click OTTO SEO, then open SEO Automation inside it. Your URL should show /seo-automation-v3. 2. Open your site's OTTO settings. Select the website that is showing the UUID mismatch error. 3. Copy the correct OTTO script. Locate the installation script in the OTTO setup panel. This script contains your site's unique UUID. Copy the entire script exactly as shown — do not modify any part of it. 4. Do not use the Cloudflare DNS installation method for this step. Close or ignore any Cloudflare-specific instructions. You will install the script directly into your site's code instead. 5. Paste the script into your site's HTML. Open your website's code editor, CMS theme editor, or tag manager. Paste the OTTO script inside the <head> tag on every page where OTTO should be active. If you are using WordPress, paste it via your theme's header file or a header script plugin. 6. Remove any old or duplicate OTTO scripts. Search your site's source for any previously installed OTTO scripts and delete them. Having multiple scripts with different UUIDs will cause continued conflicts. 7. Save and publish your changes. 8. Return to OTTO SEO in Search Atlas and run verification. OTTO will scan your page source for the correct UUID. If the script was pasted correctly, the mismatch error will clear. 🌐 If You Still Want to Use Cloudflare You can continue using Cloudflare for DNS management, CDN, and security — those features are unaffected. The key point is that the OTTO script must live in your actual site code, not be delegated to Cloudflare for injection. Once the script is manually installed in your HTML, Cloudflare will serve it normally as part of your pages without any conflict. 🔍 How to Confirm the Script Is Installed Correctly - Open your website in a browser and right-click anywhere on the page, then select View Page Source. - Use Ctrl+F (or Cmd+F on Mac) to search for otto or your UUID string. - You should see exactly one instance of the OTTO script containing your correct UUID inside the <head> section. - If you see zero results, the script was not saved correctly — repeat step 5 above. - If you see more than one result, remove the duplicates and keep only the current, correct script. 💬 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 Logo Glitch on Wix

🔍 What Is This Issue? Some customers using OTTO SEO on Wix-powered websites notice that their site logo or text elements appear to change randomly after OTTO's pixel script is active. This is a known compatibility behaviour between the OTTO pixel and Wix's own rendering engine — it does not delete your SEO optimizations, but it can affect your site's visual appearance if not handled correctly. ⚙️ Why Does This Happen? OTTO uses a lightweight pixel script to apply on-page SEO changes in real time. Wix manages its own DOM (the code structure of your page) independently, which can occasionally cause conflicts when both systems try to update page elements — such as your logo image or heading text — at the same time. The result is an intermittent visual glitch rather than a permanent change to your content. ✅ How to Fix the Glitch Follow these steps in order to resolve the conflict without losing any OTTO optimizations: 1. Do not deactivate OTTO. Disengaging OTTO keeps your project's settings, recommendations and history for later reactivation, but the OTTO pixel will stop serving OTTO's changes while the project is disengaged. Work through the steps below instead. 2. Clear your Wix site cache. In your Wix dashboard, go to Settings → Advanced → Clear Cache, then publish your site again. Many visual glitches resolve after a fresh cache clear. 3. Check for duplicate pixel installations. Log in to Search Atlas, go to OTTO SEO in the left sidebar and open SEO Automation, and open your connected site. Confirm that only one OTTO pixel snippet is installed in your Wix site's custom code section. Duplicate snippets are the most common cause of element conflicts. 4. Verify pixel placement in Wix. In your Wix dashboard, navigate to Settings → Custom Code. Ensure the OTTO pixel is placed in the <head> section and set to load on All Pages. If it appears more than once, remove the duplicate and republish. 5. Re-publish your Wix site. After confirming a single, correctly placed pixel, click Publish in the Wix editor to push a clean version of your site live. 6. Test across browsers and devices. Open your site in an incognito window and on a mobile device to confirm the logo and text are now stable. 📊 Confirm Your OTTO Optimizations Are Intact After applying the fix, verify that your SEO work has not been affected: - Go to OTTO SEO in the left sidebar and open SEO Automation, then open your site dashboard. - Check that your previously approved optimizations still show a status of Active. - Use Keywords → Rank Tracker (left sidebar → Keywords → Rank Tracker) to confirm your tracked keywords are still being monitored without interruption. 🚀 Prevent the Glitch From Returning To reduce the chance of this issue recurring, keep the following best practices in mind: - Only ever install the OTTO pixel once per site. If you reinstall or reconnect your site in Search Atlas, remove the old pixel code from Wix first. - After any major Wix theme update or template change, clear your site cache and confirm the pixel is still in the correct position. - Avoid using third-party Wix apps that inject code into the <head> section alongside OTTO, as overlapping scripts can trigger similar conflicts. 💡 Still Seeing the Glitch? If you have followed all the steps above and the logo or text changes are still occurring, it is likely a site-specific conflict that our team can investigate 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 SEO Bug Fixes and Improvements

This release resolves several visual and data issues in OTTO SEO and Audit. The fixes listed below are applied automatically — no action is required on your end unless noted. What's New The following bug fixes and improvements are now live in the platform: - Diagnostic scan modal spacing fixed: A layout spacing issue on the All Sites Page diagnostic scan modal has been corrected for a cleaner, more consistent appearance. What to Expect - The diagnostic scan modal spacing fix is a visual correction and does not affect underlying data or functionality. If you have questions about any of these changes or notice unexpected behavior after the update, please reach out to our support team for assistance.

🔍 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 Plugin UUID Configuration Errors in WordPress

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

🔧 Fix Flagged Links and Missing Citations Safely

Overview This article covers three common issues customers encounter after running a site audit or setting up local citations: how to act on flagged links without losing valuable backlinks, why image alt text may not appear as expected in audit results, and why citations may be missing from your dashboard. Understanding Flagged Links in Your Audit When your site audit flags links, it does not automatically mean those links should be deleted. Review each flagged link individually before taking action. Consider whether the referring domain is relevant and authoritative, and whether removing or disavowing the link could harm your backlink profile. A cautious, link-by-link approach is recommended. For broken outbound links, update the link in your content to point to a live, relevant page. For broken inbound links pointing to deleted pages on your site, you can work to preserve link value by ensuring the destination page exists and is accessible. Image Alt Text in Audit Results If your audit has flagged images with missing alt text, here are steps you can take to address them: - Open the Site Audit section from the left sidebar → OTTO SEO → Site Audit and locate the audit report for the relevant project. - Look for image-related or on-page SEO flags within the report, which identify images that are missing alt text. - For each flagged image, go to the page in your CMS or site editor and add descriptive alt text that accurately reflects the image content. - Re-run the audit after making your changes to confirm the flags have been cleared. If the audit report is not showing image-related issues at all despite expecting them, verify that your audit was configured to include on-page checks, and try running a new audit to get a fresh scan. Citations Not Appearing in Your Dashboard If citations you have submitted or claimed are not showing in your dashboard, work through the following steps: - Confirm that your business name, address, and phone number (NAP) are entered consistently across all listings, as inconsistencies can prevent citations from syncing correctly. - Check whether the citation submission was completed fully — incomplete submissions may not be processed. - Review each citation source in your dashboard to see whether its status is shown as pending, claimed, or requiring verification. - If a citation requires verification (such as a postcard or phone verification from the directory), complete that verification step before expecting it to appear as active. - If a citation appears stuck or shows an error status, note the specific citation source name, the status displayed, and the project it belongs to — this information will help the support team investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Pixel Not Engaging on GoDaddy

🔍 Overview If you have installed the OTTO pixel on a GoDaddy website builder site but the dashboard still shows the pixel as not engaged, you are not alone. GoDaddy's template-based website builder applies extra layers of code management that can block or delay pixel activation. This article walks you through the most effective fixes so OTTO can start optimizing your site. ⚙️ Why This Happens on GoDaddy Templates GoDaddy's proprietary website builder (distinct from WordPress on GoDaddy hosting) restricts how custom scripts are loaded. Common reasons the OTTO pixel fails to engage include: - Script placement limitations: GoDaddy templates do not always support placing scripts in the <head> tag directly, causing the pixel to fire too late or not at all. - Caching layers: GoDaddy applies aggressive server-side and CDN caching that can serve stale pages without the pixel present. - Content Security Policy (CSP) restrictions: Some GoDaddy templates block third-party scripts by default. - Single-page template rendering: Certain GoDaddy themes render content dynamically, which prevents standard pixel triggers from firing correctly. ✅ Step-by-Step Troubleshooting 1. Verify the pixel code is copied correctly. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3), open your OTTO project, and copy the full pixel snippet. Paste it into a plain-text editor and confirm there are no truncated characters or extra spaces. 2. Place the pixel in the correct location in GoDaddy. Log in to your GoDaddy account, open your website editor, navigate to Settings → Website Settings → Header Code (or equivalent in your template), and paste the full OTTO pixel snippet there. Avoid placing it only in the body or footer section. 3. Clear all GoDaddy caches. In your GoDaddy dashboard, locate the Cache or Performance settings and purge the cache entirely. Wait 5–10 minutes before rechecking pixel status in Search Atlas. 4. Disable any active CDN temporarily. If you have Cloudflare or GoDaddy's built-in CDN enabled, temporarily pause it to test whether the pixel engages. This helps identify whether caching is the root cause. 5. Check for Content Security Policy blocks. Using your browser's developer tools (press F12), open the Console tab and reload your website. Look for any errors mentioning refused to load script or Content Security Policy. If present, you will need to whitelist the OTTO script domain inside GoDaddy's CSP settings or contact GoDaddy support to adjust the policy. 6. Test in an incognito window. Open your website in a private/incognito browser tab to bypass local browser cache and confirm the pixel script is present in the page source (right-click → View Page Source and search for the OTTO pixel code). 7. Re-check pixel status in Search Atlas. Return to Left sidebar → OTTO SEO → SEO Automation (/seo-automation-v3), reload your OTTO project dashboard, and check whether the pixel status has updated to Engaged. Pixel status can take up to 15 minutes to refresh after a successful detection. 💡 Alternative: Use Google Tag Manager on GoDaddy If direct pixel installation continues to fail, deploying OTTO through Google Tag Manager (GTM) is a reliable workaround for GoDaddy template limitations: - Install the GTM container snippet into GoDaddy's Header Code section. - Inside GTM, create a new Custom HTML tag and paste the full OTTO pixel snippet. - Set the trigger to All Pages and publish the GTM container. - Return to Search Atlas and verify pixel engagement status after 10–15 minutes. GTM bypasses many of the script restrictions imposed by GoDaddy templates and is the recommended method for complex template environments. 🚫 Common Mistakes to Avoid - Do not paste the pixel snippet multiple times — duplicate instances can cause conflicts and prevent engagement. - Do not use GoDaddy's drag-and-drop HTML block widget as your only installation method, as these blocks are often excluded from the rendered <head> section. - Do not check pixel status immediately after installation — always allow at least 10–15 minutes and clear cache first. 🆘 Still Not Resolved? If you have completed all the steps above and the OTTO pixel still shows as not engaged, our team can investigate your specific GoDaddy template 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 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.

🛠️ Fix GSC Schema Errors from OTTO Deployments

🔍 What Is This Issue? After OTTO deploys schemas to your site, Google Search Console (GSC) may flag schema errors or warnings on certain pages — including your homepage. This can happen when OTTO deploys structured data to a page that has not yet been crawled, or when a schema type (such as Article schema) is removed and the change is not yet reflected in Google's index. This article walks you through the steps that our support team has confirmed resolve this issue. ⚙️ Step 1: Review and Roll Back Problem Schemas in OTTO The first step is to identify which schemas are causing the GSC errors and temporarily remove them so your site is in a clean state before reindexing. 1. Go to your Search Atlas dashboard and navigate to OTTO. 2. Locate the site experiencing GSC errors and open its OTTO settings. 3. Review the schemas currently deployed on the affected page (for example, your homepage). 4. Temporarily roll back or undeploy the schemas that GSC is flagging as errors. If you are unsure which schemas to remove, start with any recently changed or newly added schema types on that page. 5. Save your changes inside OTTO. 🌐 Step 2: Republish Your Site After rolling back the schemas in OTTO, you need to push those changes live on your website. - Wix users: Log in to your Wix dashboard and republish your site so the updated (schema-free) version is publicly accessible. - Other platforms: Clear any caching layers and ensure the live version of your page no longer contains the flagged schema markup. You can verify this by viewing the page source or using Google's Rich Results Test tool. 📊 Step 3: Request Reindexing in Google Search Console Once your site is republished without the problematic schemas, ask Google to recrawl and reindex the affected page. 1. Open Google Search Console and select your property. 2. Paste the URL of the affected page (e.g., your homepage) into the URL Inspection tool at the top of the screen. 3. Click Request Indexing. Google will queue the page for recrawling, which typically takes a few hours to a few days. 4. Once Google has recrawled the page, the schema errors should no longer appear in the Enhancements or Rich Results reports in GSC. 🚀 Step 4: Redeploy Schemas After Errors Clear After Google has confirmed the errors are resolved (or after the flagged errors disappear from GSC reports), you can safely redeploy your schemas through OTTO. 1. Return to OTTO in your Search Atlas dashboard and open it for your site. 2. Redeploy the schemas you rolled back in Step 1, making sure the affected pages have been fully crawled by OTTO before deploying structured data to them. 3. Repub

Fix OTTO Script Detection on White-Label WordPress

🧩 Why This Happens When the OTTO script is installed on a white-label WordPress site, the script may register against the wrong domain. As a result, the Site Auditor cannot verify ownership and throws an incorrect domain error — even if the snippet appears to be in the right place in your page source. This is a known conflict specific to white-label WordPress sites. If you are experiencing this error, contact our support team so they can investigate the domain mapping and guide you to the correct setup method for your specific configuration. ✅ General Troubleshooting Steps While support reviews your case, you can try the following steps to rule out common causes. 1. Log in to your Search Atlas account and navigate to your OTTO setup for the affected site. 2. Confirm that the OTTO script or plugin installed on your WordPress site corresponds to the correct site in your Search Atlas account. Mismatches between sites are a common cause of domain errors on white-label setups. 3. Log in to your WordPress admin dashboard (e.g., yoursite.com/wp-admin) and check whether OTTO is connected via a plugin or a manually placed script snippet. Note which method is in use — your support agent will need this information. 4. If your site uses caching plugins (e.g., WP Rocket, W3 Total Cache, LiteSpeed Cache), clear all caches and purge your CDN cache if applicable, then check whether the error persists. 5. If your site uses a page builder (such as Elementor or Divi) that injects custom scripts, verify that only one instance of the OTTO script is present on the site. Duplicate or conflicting script instances can interfere with detection. 6. After making any changes, return to your Search Atlas account and trigger a fresh check for your site, then allow a few minutes for the connection status to refresh. ⚠️ Important Notes for White-Label Sites - If you manage multiple white-label client sites, confirm that each site is connected to its own corresponding site entry in Search Atlas. Do not share credentials or tokens across different domains. - If the error persists after the steps above, contact Search Atlas support with details about your white-label configuration so the team can identify the correct resolution for your setup.

🔍 Fix OTTO SEO Score Showing Zero

🤔 Why Is My OTTO SEO Score Showing Zero? If your OTTO SEO score is showing 0 across one or more projects, it almost always means that no SEO fixes have been deployed yet. OTTO calculates your score based on the fixes it has successfully applied to your site — so until at least one fix is deployed, the score will remain at zero. This is expected behaviour for new OTTO activations or projects where fixes are still pending review. It does not mean something is broken. ✅ How OTTO Calculates Your SEO Score Your OTTO SEO score reflects the state of fixes that have been successfully deployed to your website. Here is how the scoring works: - 0 fixes deployed → Score displays as 0 - Some fixes deployed → Score reflects the proportion of completed fixes - All fixes deployed → Score reaches its maximum value for that project OTTO will never show a non-zero score until at least one fix has been actively deployed — this ensures the score is always an accurate reflection of real on-site changes. 🛠️ Steps to Deploy Your OTTO Fixes Follow these steps to deploy fixes and start seeing your score update: 1. Navigate to the OTTO SEO section of the platform and open the project that is showing a score of 0. 2. Check that OTTO has been activated for this project. If you see an activation prompt, complete that step first. 3. Review the list of recommended fixes OTTO has generated for your project. 4. Deploy the available fixes for your project. Your SEO score will update once fixes are confirmed as live. ⚠️ Common Reasons Fixes May Not Be Deploying If you have attempted to deploy fixes but your score is still showing 0, check the following: - OTTO is not activated: OTTO must be fully activated and connected to your site before it can deploy changes. Look for a setup or activation prompt on the project page. - Site connection issue: If OTTO cannot communicate with your website, deployments may fail. Verify that your site integration (WordPress plugin or DNS connection) is active and up to date. - Fixes are pending, not deployed: Reviewing or approving a fix is not the same as deploying it. Make sure you have completed the deployment action — not just selected the fix. - Recently activated project: OTTO may still be crawling and generating recommendations. Allow a few minutes after activation before expecting fixes to appear. 🔄 What to Do After Deploying Fixes After deploying fixes, allow a few minutes for the platform to process the changes and update your score. If your score remains at 0 after deploying fixes, note your project name, any error messages shown, and the approximate time you attempted the deployment before reaching out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🏷️ OTTO Page-Level Schema Bulk Deployment via GTM

Overview Some users encounter issues when deploying page-level schemas through OTTO using Google Tag Manager (GTM). Because the specific resolution for this issue requires investigation of your account and GTM configuration, the Search Atlas support team will need to assist you directly. Common Symptoms - Only a fraction of your selected schemas (for example, 5 out of 800 pages) show as deployed after a bulk deploy action. - Checkboxes for individual schema selection or bulk-deploy options are not visible on the page. - The main-entity fields display as blank or show a null value and you are unsure what to enter. What to Have Ready Before Contacting Support To help the support team investigate and resolve your issue as quickly as possible, please gather the following information before reaching out: - Your project name in Search Atlas. - The exact number of pages you attempted to deploy schemas to and how many actually show as deployed. - A description of the symptom you are experiencing (for example, missing checkboxes, blank main-entity fields, or incomplete bulk deployment). - Your GTM container ID and whether your GTM container has been published after OTTO pushed the schema tags. - Screenshots or screen recordings showing the issue, including any error messages displayed in the UI. - The timestamp of when you attempted the bulk deploy action. - The browser and browser version you are using. Next Steps If you are experiencing issues with OTTO page-level schema bulk deployment via GTM, please contact us via the chat icon in the bottom-right corner of Search Atlas and we will be happy to investigate and resolve the issue on your behalf.

🔍 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 <head> 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 Pagination Canonicalization With Installation Methods

🧭 Overview When OTTO is installed using the WordPress plugin method, it can append an is_otto_page_fetch=1 query parameter to paginated blog URLs (for example, /blog/page/2/?is_otto_page_fetch=1). This changes the perceived canonical URL of those pages, which can create duplicate content signals and confuse search engine crawlers. Switching to the custom script installation method removes this parameter entirely and restores correct canonicalization. ⚙️ Understanding the Two OTTO Installation Methods OTTO can be installed on your site in two ways. Each method works differently and has different implications for how OTTO fetches and processes your pages. - Plugin method: A WordPress plugin is installed directly on your site. OTTO uses internal WordPress hooks to fetch page content, and this process appends the is_otto_page_fetch=1 parameter to URLs during pagination crawls. This parameter can be picked up by your CMS or SEO plugin and treated as a unique URL, altering the canonical tag. - Custom script method: A lightweight JavaScript snippet is added to your site's <head> section manually or via a tag manager. This method does not interact with WordPress URL routing, so it never appends the is_otto_page_fetch=1 parameter. Canonicalization remains unaffected. 🔍 How to Confirm You Have the Canonicalization Issue 1. Navigate to any paginated page on your blog (for example, yoursite.com/blog/page/2/). 2. Open your browser's developer tools, go to the Network tab, and reload the page. 3. Check whether the request URL or the canonical tag in the page <head> includes is_otto_page_fetch=1. 4. Alternatively, crawl your site with a tool like the Search Atlas Site Auditor and filter for URLs containing is_otto_page_fetch. If that parameter appears in your canonical tags or is being indexed, you are affected and should migrate to the custom script method. 🔄 How to Migrate From the Plugin to the Custom Script Follow these steps in order. The process takes fewer than ten minutes and does not require downtime. 1. Retrieve your OTTO custom script. Log in to Search Atlas, go to OTTO SEO in the left sidebar, and open All Sites (SEO Automation). Locate the Installation or Connect Site section and copy the custom JavaScript snippet provided for your website. 2. Add the script to your site's <head>. Paste the snippet into your site's <head> section. You can do this by editing your theme's header.php file directly, using a plugin such as Insert Headers and Footers, or publishing it through Google Tag Manager. 3. Verify the script is firing correctly. Open your site in a browser, view the page source, and confirm the OTTO script appears inside the <head> tag. Then return to the OTTO dashboard in Search Atlas and confirm the site shows a connected status. 4. Deactivate and delete the OTTO WordPress plugin. In your WordPress admin panel, go to Plugins, locate the OTTO plugin, click Deactivate, and then click Delete. Removing the plugin stops it from appending the is_otto_page_fetch=1 parameter immediately. 5. Check your paginated URLs again. Visit your paginated blog pages and confirm the parameter no longer appears in the URL or the canonical tag. 🛡️ When to Use Each Installation Method - Use the custom script method for all WordPress sites, especially those with blogs, archives, or any paginated content. This is the recommended default for most users. - Use the plugin method only if your hosting environment restricts access to the <head> section and you have no tag manager available. Be aware of the pagination canonicalization limitation and monitor your site for the issue described in this article. ❓ Frequently Asked Questions Will migrating to the custom script break any existing OTTO automations? No. Your OTTO settings, optimizations, and connected data remain intact. Only the method by which the pixel fires on your site changes. Do I need to re-authorize or reconnect my site after migrating? Not usually. As long as the custom script includes the correct site token and your site shows as connected in the OTTO dashboard, no re-authorization is needed. The parameter still appears after I deleted the plugin. What should I do? Clear your site's server-side cache, CDN cache, and any WordPress caching plugin cache. If the parameter persists after a full cache purge, contact support using the instructions below. Will search engines un-index the incorrect canonical URLs automatically? Once the parameter is gone from your canonical tags, search engines will gradually recrawl and correct the indexed versions. You can speed this up by submitting your sitemap in Google Search Console. 💬 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 Cloudflare OTTO Worker Installation: DNS Redirect and Header Issues

Understanding the www Redirect Problem When your Cloudflare diagnostic fails and reports a missing OTTO Worker header, it is often because your domain configuration redirects www traffic to non-www (or vice versa). This redirect can bypass the Cloudflare Worker on one domain variant, causing the diagnostic check to fail and preventing OTTO from functioning properly on that version of your site. For example: if visitors access www.yourdomain.com but are redirected to yourdomain.com, the Worker installed on the www variant may never execute, so the diagnostic check finds no OTTO header on that version. Step 1: Identify Which Domain Variant Is Failing 1. Log into your Search Atlas account and navigate to your OTTO installation area. 2. Trigger a diagnostic check for your domain. 3. Review the diagnostic results and note which domain variant shows the missing header error (www or non-www). 4. Take note of the exact error message — it will indicate the domain variant that failed the check. Step 2: Check Your Cloudflare DNS and Redirect Rules You need to verify your Cloudflare configuration to understand how traffic is being routed between www and non-www variants. 1. Log into your Cloudflare account and select your domain. 2. Review your DNS records for both www and non-www variants to confirm they are correctly configured. 3. Check your Cloudflare redirect or rewrite rules to identify any rules that forward www traffic to non-www (or vice versa). 4. Determine whether any redirect rules may be executing before the OTTO Worker has a chance to run, which would prevent the Worker from injecting its required header. Step 3: Ensure the OTTO Worker Covers the Correct Domain Variant A common cause of this issue is that the OTTO Worker is only installed or routed for one domain variant. You need to confirm the Worker is configured to handle traffic on the domain variant your visitors actually land on after any redirects. 1. In your Cloudflare account, review the routes or triggers associated with your OTTO Worker. 2. Confirm the Worker is active for the domain variant that is failing the diagnostic (the one visitors are redirected to). 3. If the Worker is only covering one variant, update your Cloudflare Worker routing settings to extend coverage to the other variant as needed. 4. If you are unsure how to adjust your Cloudflare Worker routing, contact the Search Atlas support team for guided assistance specific to your account configuration. Step 4: Re-run the Diagnostic After Making Changes 1. After updating your Cloudflare configuration, return to your OTTO installation in Search Atlas. 2. Trigger the diagnostic check again to confirm the OTTO Worker header is now detected on the previously failing domain variant. 3. If the diagnostic still fails after making adjustments, reach out to the Search Atlas support team via the chat icon in your dashboard so an agent can review your specific Cloudflare and OTTO configuration directly.

🛠️ Fix the 'Select Approved Site' Error in Publication Media

🔍 What Is This Error? When creating a Publication Media account in Search Atlas, you may see the following message: "Select at least one approved site to continue." This error means that no approved sites are currently linked to your Publication Media account, so the system cannot proceed with the creation step. 💡 Why Does This Happen? This error occurs for one or more of the following reasons: - You have not yet added any sites to your Publication Media account. - The sites you added are still pending review and have not been approved yet. - A previously submitted site was rejected, leaving no approved sites available to select. - Your account is new and the approval process has not been completed. 🚀 How to Resolve the Error 1. Check your site approval status. Navigate to your Publication Media dashboard and review the status of any sites you have submitted. Sites must show a status of Approved before they can be selected during account creation. 2. Add a site if none exist. If you have not submitted any sites yet, use the Add Site option within the Publication Media section to submit your first domain for review. 3. Wait for approval. After submitting a site, the review process may take some time. You cannot proceed with account creation until at least one site is approved. Check back after receiving a confirmation notification. 4. Resubmit a rejected site. If your site was rejected, review any feedback provided, make the necessary changes, and resubmit the site for approval. 5. Refresh and retry. Once at least one site shows an Approved status, return to the account creation flow, select the approved site, and continue. ⚙️ Tips to Avoid This Error - Always confirm that a site's status is Approved before starting the Publication Media account creation process. - Submit your sites for review well in advance of when you plan to create your account, to allow time for the approval workflow to complete. - If you manage multiple domains, ensure at least one is approved and active before proceeding. 📊 Still Seeing the Error? If you have one or more approved sites but the error still appears, try the following: - Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached data. - Log out of Search Atlas, log back in, and attempt the account creation again. - Try using a different supported browser such as Google Chrome or Microsoft Edge. If the problem persists after following these steps, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix 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 Avatar 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 Avatar 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 Outdated Image Metadata and Cache

🔍 What Is This Issue? OTTO may continue injecting ImageObject structured data for images that have been removed from your website — for example, images like Group_20.png — because the deployed fix still contains references to those old files. This causes warnings in schema validation tools such as Google's Rich Results Test or Schema Markup Validator. To stop OTTO from injecting outdated image metadata, roll back (undeploy) the affected fix in OTTO, or edit the fix in OTTO to reference the correct image. This article explains why it happens and how to resolve it. ⚙️ Why Does This Happen? OTTO scans your site and stores a snapshot of page content, including images, to build and inject structured data efficiently. If an image is removed from your site after OTTO has already cached it, the old metadata can persist until the cache is refreshed. OTTO does not automatically detect mid-cycle image removals in real time, so a manual cache purge is required to bring the injected schema back in sync with your current content. 🛠️ How to Refresh OTTO Metadata 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to OTTO SEO → SEO Automation (URL: /seo-automation-v3). 3. Select the project or website affected by the outdated image metadata. 4. Locate the deployed fix that references the outdated image and either roll back (undeploy) the fix, or edit the fix in OTTO to point to a current image. OTTO will stop injecting the outdated ImageObject once the fix is rolled back or updated. 5. If your site uses its own caching (server, CDN, or a WordPress caching plugin), clear that cache as well so the updated metadata is served to visitors. 6. Re-validate your schema using a tool such as Google's Rich Results Test to confirm the outdated ImageObject entries are no longer present. ✅ How to Confirm the Fix Worked - Open Google's Rich Results Test or the Schema Markup Validator and enter the affected page URL. - Check that no ImageObject entries reference old or missing image files (e.g., filenames that no longer exist in your media library). - If your site uses a CDN, allow up to 24 hours for edge caches to propagate the updated metadata globally. You will need to clear your own CDN or caching-plugin cache separately. 💡 Tips to Prevent This Issue - Re-scan after major content changes. Whenever you remove, replace, or significantly update images on your site, trigger a manual re-scan in OTTO to keep structured data in sync. - Remove unused images from your CMS media library. Deleting old image files from your media library (not just from pages) reduces the chance of stale references being picked up in future scans. - Check schema after redesigns or migrations. Site redesigns frequently swap out image assets. Always validate your schema immediately after a redesign or platform migration. 🆘 Still Seeing Outdated Metadata? If you have rolled back or edited the affected fix in OTTO but the outdated ImageObject schema warnings persist, there may be a deeper sync issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Why OTTO Can't Add New Sites Explained

🧩 Understanding the Connection Between OTTO and Site Audit OTTO projects and Site Audit are closely linked inside Search Atlas. Every time you create an OTTO project for a website, the platform automatically creates a corresponding Site Audit project for that same domain. This means that to add OTTO to a brand-new domain, you need both a free Site Audit project slot (for that domain's Site Audit) and a free OTTO site slot — If no Site Audit project exists for the domain, OTTO automatically creates one first, then creates the OTTO project. Because of this relationship, you may find yourself unable to add a new site to OTTO for a brand-new domain even when it appears you have available OTTO slots remaining. The real bottleneck can be your Site Audit limit when no Site Audit project yet exists for that domain. ⚠️ Why This Happens: Quota Logic Explained Here is how the quota system works step by step: 1. Your subscription plan includes separate quotas for Site Audit projects and OTTO sites, each with its own limit. 2. Adding OTTO to a site requires a Site Audit project for that domain; if one does not already exist, OTTO automatically creates it first, then creates the OTTO project. 3. For a brand-new domain, you need both a free Site Audit project slot (for the domain's Site Audit) and a free OTTO site slot. If the domain already has a Site Audit project, only an OTTO site slot is used. 4. Purchasing additional OTTO slots adds OTTO site slots only — it will not increase your Site Audit project quota. 🔎 How to Check Your Current Usage Before troubleshooting, review your current project usage across both tools: - Navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3) to see all active OTTO projects and your OTTO slot usage. - Check your Site Audit section to count how many audit projects are currently active, including any that may have been created independently of OTTO. Look for Site Audit projects that are no longer in active use. These are common culprits for unexpectedly hitting the quota ceiling. 🛠️ How to Free Up Slots and Add Your New Site Follow these steps to resolve the issue: 1. Audit your existing Site Audit projects. Identify any projects for old, inactive, or test domains that you no longer need. 2. Delete unused Site Audit projects. Removing even one unused audit project will free up a slot and allow you to proceed. 3. Return to OTTO SEO (Left sidebar → OTTO SEO → All Sites (SEO Automation)) and attempt to add your new site to OTTO again. 4. If you need more simultaneous projects without removing existing ones, upgrade your plan to increase your Site Audit limit and/or your OTTO site limit, since these are separate quotas. 💡 Best Practices to Avoid Hitting Quota Limits - Regularly review and clean up Site Audit projects for domains you are no longer actively optimising. - When purchasing additional slots, confirm whether your plan upgrade increases Site Audit limits, OTTO site limits, or both — OTTO top-ups add OTTO site slots only. - Remember that Site Audit and OTTO have separate quotas, so both must have room when onboarding a brand-new domain. - Before onboarding a new client domain into OTTO, check that you have both a free Site Audit slot and a free OTTO site slot available. ❓ Still Unable to Add a New Site? If you have freed up Site Audit slots and your quota appears to have room but you are still blocked from adding a new OTTO project, there may be a sync issue between your plan entitlements and your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Site Setup and GSC Authentication Errors

🗺️ Overview When adding a new OTTO site or connecting a Google Search Console (GSC) property, you may encounter two separate errors that appear around the same time: - Address Country field error — a character limit or formatting validation issue during site setup - GBP token expiration error — a Google Business Profile authentication failure that blocks GSC property connection These are two distinct problems with different causes and fixes. This article walks you through resolving both. 🏳️ Fix 1: Address Country Field Validation Error The Address Country field has a strict character limit and formatting requirement. If the field is not highlighted automatically, the error is still present and will block you from saving. 1. During OTTO site setup, scroll to the Address Country field. 2. Check that the value entered is a valid two-letter ISO country code (for example, US, GB, AU). Do not enter the full country name. 3. Delete any extra spaces or special characters from the field. 4. If the field appears empty or unchanged, click into it, clear the content completely, and re-enter the correct two-letter code. 5. Save the form again. The validation error should no longer appear. If the error persists after correcting the country code, try refreshing the page and re-entering your site details from the beginning before saving. 🔑 Fix 2: GBP Token Expiration Error When Adding a GSC Property A GBP token expiration error means the OAuth connection between Search Atlas and your Google account has expired or been revoked. This prevents Search Atlas from verifying your ownership of Google Search Console properties. Follow these steps to re-authenticate and restore the connection: 1. In the left sidebar, click Local → GBP Projects to go to your GBP projects (/gbp-galactic/gbp-projects). 2. Locate the Google Business Profile project associated with the GSC property you are trying to add. 3. Look for a Reconnect or Re-authenticate button next to the project. Click it. 4. A Google sign-in window will open. Sign in with the Google account that owns or has access to the GSC property. Make sure you select the correct account if you manage multiple Google accounts. 5. Grant all requested permissions when prompted. Skipping any permission will cause the token to fail again. 6. Once authentication is complete, return to your OTTO site setup and attempt to add the GSC property again. If you do not see a Reconnect option, disconnect the GBP project entirely and reconnect it from scratch using the same Google account. ⚠️ Common Reasons the Token Expires - You changed your Google account password after the initial connection was made. - You revoked Search Atlas access in your Google account's security settings. - The OAuth token exceeded Google's inactivity expiration period (typically six months without use). - You connected using a different Google account than the one that owns the GSC property. ✅ Confirm the GSC Property Is Added Successfully 1. After re-authenticating, navigate back to your OTTO site setup. 2. Select the GSC property from the dropdown list. If it now appears, the token issue is resolved. 3. Save the site. Verify that the property is linked by checking for GSC data populating in your site dashboard within 24 hours. If the GSC property does not appear in the dropdown even after re-authenticating, confirm that the Google account you used has Owner or Full User permissions on that property inside Google Search Console directly. Restricted User access is not sufficient for connection. 🔄 If Both Errors Appear at the Same Time Resolve the Address Country field error first, then tackle the GBP token expiration. Attempting to connect a GSC property while the site form still has validation errors can cause both processes to fail in a way that makes it difficult to tell which error is blocking you. Fix them in sequence for the clearest outcome. 💬 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 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 Title Changes Not Updating Live Site

Overview When you deploy a title change through OTTO, the update is written to your site via the Search Atlas WordPress plugin — not through the WordPress admin backend. This means the change should appear on your live site without you needing to do anything inside WordPress directly. If your updated title is not showing on the live site, something in the deployment pipeline needs attention. How OTTO Title Deployment Works OTTO pushes title changes directly to your live WordPress site through the Search Atlas plugin. The process is automatic once you approve and deploy a recommendation. There is no intentional buffer time — changes are designed to reflect on the live site within a few minutes of deployment. - OTTO does not modify WordPress backend settings such as SEO plugin configurations, theme settings, or custom fields. - OTTO writes directly to your live page metadata through the plugin connection. - If the title change shows as deployed inside OTTO but is not visible on the live site, the issue is with the connection or plugin status — not a delay. Step-by-Step Troubleshooting 1. Confirm the deployment was approved. Inside OTTO, locate the title recommendation and verify that it has been approved and deployed. If it still shows as pending or unapproved, complete the deployment action before proceeding. 2. Check the Search Atlas WordPress plugin is active. Log in to your WordPress admin dashboard and go to Plugins. Confirm the Search Atlas plugin is installed, activated, and shows no error notices. 3. Verify the plugin is connected to the correct site. Inside Search Atlas, confirm that the WordPress site URL associated with your OTTO connection matches your live domain exactly, including whether it uses www or not. 4. Clear your site cache. If you use a caching plugin such as WP Rocket, W3 Total Cache, or a hosting-level cache, clear it after deployment. Cached pages will continue showing the old title until the cache is refreshed. 5. Clear your browser cache. Open the page in a private or incognito browser window to rule out a locally cached version. 6. Check for a conflicting SEO plugin. If you have Yoast SEO, Rank Math, or another SEO plugin active, it may be overriding the title set by OTTO. Verify that no manual title has been entered in those plugins for the affected page. 7. Re-deploy the change. If all of the above look correct and the title is still not updating, locate the deployed recommendation inside OTTO and use the option to re-deploy. This sends the change through the pipeline again and can resolve one-off sync failures. If the Issue Persists If you have worked through all the steps above and the title is still not updating on your live site, please reach out to our support team for further assistance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix IndexNow Key Not Found Error in WordPress

🔍 Overview When activating Bing IndexNow through OTTO on a WordPress site, some customers encounter an "Index Now key not found" error (HTTP 400). This happens even when the Search Atlas WordPress plugin is correctly installed and a CMS Connector connection is active. This article explains why the error occurs and how to resolve it. ⚠️ Why This Error Happens Bing's IndexNow verification process requires your site to serve a plain-text key file at a specific URL. The error is triggered when Bing cannot access that file. Common causes include: - Your server uses nginx and returns a 403 Forbidden response for .txt files in the site root. - A server-level rule blocks direct access to root-level text files. - A caching layer or CDN intercepts the request before the key file can be served. - The key file was not yet written to disk at the moment Bing attempted verification. - A previous plugin version did not include the virtual serving or keyLocation fallback logic now required for certain hosting environments. ✅ Step-by-Step Fix 1. Update the Search Atlas WordPress plugin. Go to your WordPress dashboard, navigate to Plugins → Installed Plugins, and check for an available update to the Search Atlas plugin. Install the latest version — it includes a fix that serves the IndexNow key file virtually and adds a keyLocation fallback for nginx hosts that previously returned 403 errors. 2. Verify the key file is accessible. After updating, open a browser and go to https://yourdomain.com/<your-indexnow-key>.txt. Replace <your-indexnow-key> with the actual key shown in OTTO. The page should return a plain-text response containing only the key string. If you see a 403 or 404, proceed to the next steps. 3. Check nginx or .htaccess rules. If your host uses nginx, ask your hosting provider to confirm that .txt files in the web root are not blocked. If your host uses Apache, open your .htaccess file and look for any Deny or FilesMatch rules that may block .txt access. 4. Purge your cache. If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.) or a CDN (Cloudflare, etc.), purge all cached files. Cached 404 or 403 responses can prevent Bing from seeing the key file even after the plugin is updated. 5. Retry activation in OTTO. In the Search Atlas platform, go to OTTO SEO (left sidebar) and open your site's OTTO dashboard. Navigate to Indexing → Bing IndexNow and click Activate (or Retry) to trigger a fresh key verification. 🔎 Confirm the Fix Worked After retrying activation, OTTO will show a green active status next to Bing IndexNow when verification succeeds. If the status remains red or the error persists, use the troubleshooting checklist below before contacting support. 📋 Troubleshooting Checklist - Plugin is updated to the latest Search Atlas version. - Key file URL returns HTTP 200 with plain-text key content in a browser. - No nginx location block or .htaccess rule blocks root .txt files. - Site cache and CDN cache have been fully purged. - WordPress site is publicly accessible (not behind basic auth or maintenance mode). - OTTO activation was retried after completing all steps above. 💬 Still Seeing the Error? If you have completed every step above and the "Index Now key not found" error still appears, our team can investigate your specific server 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 GSC Integration and Address Fields in OTTO

🗺️ Overview When setting up a WordPress OTTO site, you may run into two common configuration issues: your Google Search Console (GSC) property not appearing in the site dropdown, and no visible field to enter a business address. Neither issue is related to billing or quota limits — both have straightforward fixes explained below. 🔍 Issue 1: GSC Site Not Showing in the Dropdown When you create or configure a WordPress OTTO site, you are prompted to select a GSC property from a dropdown. If your site is missing from that list, it is almost always caused by one of the following reasons. ⚠️ Common Reasons Your GSC Site Is Missing - GSC account not connected: Your Google Search Console account has not been linked to Search Atlas. The dropdown only shows properties from a connected GSC account. - Wrong Google account connected: The GSC property you need belongs to a different Google account than the one currently authorised in Search Atlas. - Property not verified in GSC: The site exists in GSC but ownership has not been verified. Unverified properties do not appear in the dropdown. - Property type mismatch: Domain properties and URL-prefix properties are both supported, but the property must be active and returning data in GSC before it appears here. ✅ Steps to Fix a Missing GSC Site 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Open your OTTO site settings or begin creating a new WordPress OTTO site. 3. Before selecting a GSC property, confirm your Google account is connected. Look for a Connect Google Search Console option and verify the correct Google account is authorised. 4. If you are signed in with the wrong Google account, disconnect the current account and reconnect using the Google account that owns the GSC property you need. 5. Once the correct account is connected, return to the GSC dropdown — your property should now appear. 6. If the property is still missing, log in to Google Search Console directly at search.google.com/search-console and confirm the site is verified and actively owned under that Google account. 7. After verifying ownership in GSC, return to Search Atlas and refresh the dropdown. Allow up to a few minutes for the connection to sync. 📍 Issue 2: No Field to Add a Business Address On the OTTO site configuration screen, the Single Address tab shows limited fields and may not display a dedicated input for a full business address. This is by design — the Single Address tab is intended for basic location data only. To enter a complete business address, you need to use the Multiple Address tab instead. ✅ Steps to Add a Business Address 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Open your WordPress OTTO site settings. 3. Navigate to the address or location configuration section. 4. Click the Multiple Address tab — this tab contains the full address form including street address, city, state, postcode, and country fields. 5. Enter your business address details in the available fields. 6. Save your changes before exiting the configuration screen. Note: If you only need to associate a single location with your site, you can still use the Multiple Address tab — simply add one address entry. This tab gives you complete address fields that the Single Address tab does not provide. 💡 Quick Reference Summary - GSC site missing from dropdown → Check that the correct Google account is connected and the property is verified in GSC. - No address field visible → Switch from the Single Address tab to the Multiple Address tab to access the full address input form. - These issues are not billing or quota related — no plan changes are needed to resolve either problem. 💬 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 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 GSC Properties Missing From Report Builder

Overview If your Google Search Console (GSC) property appears correctly in your OTTO SEO audits but is missing from the GSC selection list inside Report Builder, this article explains what may be happening and what steps you can take to resolve it. Why This Happens Search Atlas surfaces GSC data differently depending on where you are in the platform. A property can be connected and visible in your OTTO SEO audits while still not appearing in Report Builder — typically because the property has not been enabled for reporting in Manage Sites. How to Resolve This Issue To make a GSC property available in Report Builder, go to Manage Sites and locate the site associated with your GSC property. Check whether the GSC property is enabled for that site within Manage Sites. Enabling it there should make the property appear in the Report Builder selection list. If you do not see an option to enable the GSC property in Manage Sites, or if the property still does not appear in Report Builder after checking there, please have the following ready before contacting support: - The exact GSC property URL that is missing from Report Builder (for example, the domain or URL prefix you see in Google Search Console). - Confirmation that the property does appear in your OTTO SEO audit within Search Atlas. - Your Search Atlas account email or workspace name. - Any screenshots showing the property present in your audit but absent from the Report Builder selection list. Quick Reference If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix WordPress Plugin 500 Error Blocking OTTO Sync

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

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

OTTO Suggested Fix Edits Not Saving

🔍 What This Article Covers Some users found that when they manually edited an OTTO suggested fix — for example, changing an auto-generated title to their preferred wording — the change would not persist after attempting to save it. The field reverted to the original OTTO suggestion every time. This article explains what caused the issue and what to do if you experience it. ⚙️ What Was Causing the Problem This was a confirmed platform bug. When a user manually edited an OTTO suggested fix and attempted to save it, the save did not persist and the field reverted to the original suggestion. This issue affected manual edits to OTTO on-page suggestions such as titles and meta descriptions. ✅ Steps to Try If You Experience This Issue If you are seeing edits fail to save, work through the following steps in order: 1. Refresh the page and try again. Close the current tab, navigate back to the OTTO suggestions area, and attempt the edit again. 2. Clear your browser cache or try an incognito/private window. Cached data can sometimes cause the interface to behave unexpectedly. Test in a private browsing session to rule this out. 3. Try a different browser. If the issue appears in one browser but not another, a local browser extension or setting may be interfering. 💡 Still Seeing the Problem? If you have followed all the steps above and your manually edited OTTO suggestions are still not saving, this may indicate a separate or environment-specific issue that needs investigation. Please reach out to our support team and we will investigate further. Open 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 Tool Failed Message Troubleshooting Guide

🤔 What Does the 'Failed' Message Mean? When Otto — Search Atlas's OTTO SEO automation tool — displays a Failed status next to your connected site, it means Otto encountered an interruption while crawling or processing your site's data. This does not mean your site has been disconnected or that any previously applied optimizations have been lost. In most cases, this is a known display glitch triggered by a temporary timeout or a brief server-side interruption during the crawl process. Your site connection remains intact, and the issue is fully recoverable by initiating a fresh recrawl. ⚠️ Why Does This Happen? The Failed status can appear for several common reasons: - A temporary timeout occurred while Otto was crawling your site. - A brief server interruption affected the data processing pipeline. - Your site returned an unexpected response during the crawl (for example, a momentary slowdown or blocked request). - The crawl session was interrupted before it could complete successfully. None of these causes indicate a problem with your site's SEO health or your Search Atlas account. A recrawl resolves the issue in the vast majority of cases. 🛠️ How to Fix It: Step-by-Step Recrawl Instructions Follow these steps to clear the Failed status and restart the Otto crawl for your site: 1. Log in to your Search Atlas account and navigate to OTTO SEO → Site Audit → Overview (Website Overview) using the left sidebar. 2. Locate the site showing the Failed status in your Otto dashboard. 3. Click on the site to open its Otto settings and overview panel. 4. Look for the Recrawl Site button on the Overview (Website Overview) page and click it. 5. Confirm the action if prompted. Otto will immediately queue a fresh crawl for your site. 6. Wait for the crawl to complete. The status will update automatically once Otto finishes processing. You do not need to disconnect or reconnect your site. Initiating the recrawl is all that is required. ⏱️ How Long Will the Recrawl Take? Recrawl times vary depending on the size of your site and current system load. As a general guide: - Small sites (under 100 pages): typically 5–15 minutes. - Medium sites (100–1,000 pages): typically 15–45 minutes. - Large sites (1,000+ pages): may take up to a few hours. Once the recrawl is complete, the Failed status will be replaced with an active status and your Otto data will be refreshed. You do not need to stay on the page while the crawl runs — you can navigate away and return later to check the updated status. ✅ After the Recrawl Completes When the recrawl finishes successfully, you should see: - The site status updated from Failed to an active crawl status. - Refreshed site data, including updated page counts and SEO opportunity summaries. - All previously deployed Otto optimizations still in place — a recrawl does not remove or reset any changes Otto has already applied to your site. If the Failed status reappears after the recrawl completes, try running a second recrawl. Persistent failures after two attempts may indicate a site accessibility issue that requires further investigation. 🆘 Still Seeing the Failed Status? If the Failed message persists after one or two recrawl attempts, it may point to a deeper connectivity issue between Otto and your site — for example, your site blocking the Otto crawler or an authentication problem. In this situation, our team can investigate 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.

🛠️ Troubleshoot Common OTTO Configuration Issues

🔍 Overview This article covers common OTTO configuration issues reported by Search Atlas users across five integration and feature areas: autopilot settings, product page indexing, Google Search Console connection, link deployment, and PPC keyword sync. Because the exact steps to resolve each issue depend on your specific project setup, the guidance below describes what to check and what information to have ready so our team can assist you as quickly as possible. ⚙️ Autopilot Setting Not Saving If OTTO's autopilot toggle keeps reverting or does not save, try the following general checks: - Confirm the change was saved: Some settings require an explicit save action after toggling. Make sure you complete any confirmation step on the page before navigating away. - Check for conflicting task-level settings: Individual task settings within your OTTO project may conflict with the global autopilot setting. Review your project's task-level configurations and clear any overrides before re-enabling autopilot. - Rule out a browser or session issue: Clear your browser cache, log out, log back in, and retry the toggle. If the issue persists after these checks, note the project name and a description of the behaviour you are seeing before reaching out to support. 📄 Product Pages Not Being Indexed If product pages are not getting indexed after OTTO deploys optimisations, consider the following: - Check page accessibility: Confirm the pages are publicly accessible and not blocked from being crawled or indexed, as OTTO cannot request indexing for pages that search engines cannot reach. - Confirm your GSC connection is active: Indexing requests depend on a working Google Search Console connection. See the section below if your GSC connection has an issue. - Allow time for processing: Indexing requests submitted through GSC are not instant. Check your OTTO project for the current submission state of the affected pages. If pages remain unindexed and you have ruled out the above, contact support with your project name and the specific URLs affected. 🔗 Google Search Console Not Connected A broken or missing GSC connection will prevent OTTO from pulling performance data and submitting indexing requests. General steps to investigate: - Open your OTTO project and check the connection status for your Google Search Console integration. - If the connection shows as disconnected or expired, initiate the reconnection flow using the Google account that has the appropriate access to the GSC property. - Make sure you select the correct GSC property that matches your site after reconnecting. If you are unable to reconnect GSC on your own, contact support with your project name and the Google account you are using for the integration. 🔗 Link Deployment Issues If links deployed by OTTO are not appearing on your site as expected, check the following: - Verify deployment status: Review your OTTO project to confirm whether the link tasks show a completed or pending status. Tasks that remain in a pending state have not yet been applied to your site. - Check site permissions: OTTO requires the necessary access to your site to deploy changes. Confirm that the integration connecting OTTO to your site is active and has not expired. - Review the target pages: Make sure the pages where links are being deployed are published and accessible. If links are still not deploying correctly after checking the above, contact support with your project name, the specific tasks affected, and a description of what you are seeing. 💰 PPC Keyword Sync Issues If PPC keywords are not syncing into OTTO as expected, check the following: - Confirm your PPC integration is connected: The keyword sync depends on an active connection between OTTO and your PPC account. Verify the integration is active in your project settings. - Allow time for syncing: After connecting or reconnecting a PPC account, keyword data may take some time to populate. Wait a short period and then refresh your project. - Check the correct account is linked: Make sure the PPC account connected to OTTO is the one that contains the keywords you expect to see. If keywords are still not syncing after these checks, contact support with your project name, the PPC account in question, and a description of the keywords or campaigns affected. If you need further assistance, open 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 Autopilot settings are tied to active project state; changes made while paused won't commit. Check project status badge (must show Active). Also: URL Exclusion Patterns, Crawl Depth limit, and E-commerce Crawl Mode toggle for Shopify product page indexing.

🛠️ Fix OTTO Script Not Recognized on WordPress

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

🔍 Fix OTTO 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 OTTO Site Quota After Deleting a Project

🔍 Overview When you delete an OTTO project and its pixel, you might expect your site quota to return to zero immediately. However, the platform can sometimes still show 1 OTTO site in use, preventing you from installing the pixel on a new URL. This article explains why this happens and how to resolve it. ⚙️ Why Does This Happen? Deleting an OTTO project does not always instantly release the associated site slot from your quota. There are a few common reasons this occurs: - Cache delay: The quota counter can take a short time to refresh after a project is deleted. - Pixel still linked: If the pixel was removed from your website but the project was not fully deactivated inside Search Atlas, the slot may remain occupied. - Domain still registered: The original domain may still be registered against your account even after project deletion, holding the quota open. 🛠️ How to Free Your OTTO Site Quota Follow these steps carefully to release the occupied slot and install your pixel on a new URL. 1. Go to OTTO SEO → All Sites (SEO Automation): In the left sidebar, click OTTO SEO, then All Sites (SEO Automation). This opens the OTTO dashboard at /seo-automation-v3. 2. Check for remaining projects: Review the project list for any entries tied to your old URL — including projects with a disconnected or inactive status. These can still hold a quota slot. 3. Fully deactivate the project: Open the old project, then look for a Deactivate or Disconnect Site option. Complete this step before deleting — skipping deactivation is the most common reason the slot is not released. 4. Delete the project: Once deactivated, delete the project using the project settings or the trash icon. 5. Refresh your quota: Return to the main OTTO SEO dashboard and wait up to 2 minutes, then refresh the page. Your site count should now show 0. 6. Install on your new URL: Create a new OTTO project for your new URL and follow the standard pixel installation steps. ✅ Confirm Your Quota Has Been Released After completing the steps above, verify the following before setting up your new project: - The OTTO SEO dashboard shows 0 of your allotted sites in use. - No old projects appear in the project list, even with inactive or disconnected labels. - The option to add a new site is no longer greyed out or blocked. 💡 Tips to Avoid This Issue in the Future - Always deactivate a project first before deleting it — this ensures the site slot is properly released. - Remove the OTTO pixel from your website after deactivating the project in Search Atlas, not before. - If you plan to move to a new domain, deactivate and delete the old project before creating the new one to avoid hitting your quota limit. 🆘 Still Seeing 1 Site in Use? If you have followed all the steps above and your quota still shows 1 site in use, a manual reset may be needed on the account level. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Null Field Errors in OTTO Schema Markup

🔍 What Does the 'offers': null Error Mean? When OTTO generates schema markup for your pages, it pulls structured data from the content it finds on that page. If OTTO detects a Product Schema on your page but cannot find pricing, availability, or offer-related content, it inserts 'offers': null as a placeholder in the generated schema. This is not a system crash or a bug — it means OTTO found a schema type that typically includes an Offers field, but the corresponding data was either absent from the page or not yet provided. Search engines like Google may flag a null Offers field as incomplete structured data, which is why it surfaces as an error in your schema report. 📋 Understanding OTTO Schema States: 'Review' vs. 'FOUND' OTTO assigns each schema one of two states to help you manage your markup: - Review — OTTO has drafted a schema based on page content, but it requires your approval before being applied. Fields may be incomplete. - FOUND — OTTO has detected an existing schema already present on the page (e.g., hardcoded in your theme or CMS). OTTO surfaces it so you can see and manage it, but it originates from your site's existing code. A common point of confusion: customers are sometimes told that FOUND schemas cannot be edited or removed. This is incorrect. Both Review and FOUND schemas can be managed within OTTO — you can edit individual fields, leave non-applicable fields empty where acceptable, or work with your developer to remove hardcoded schemas from the source if needed. ⚙️ How OTTO Auto-Populates the Offers Field When you click Regenerate on a schema, OTTO re-scans the page and attempts to pull fresh data. Here is what happens depending on your page content: - If pricing or offer data exists on the page — OTTO will auto-populate the Offers field with values it finds (price, currency, availability, etc.). - If no offer data exists on the page — OTTO will again return 'offers': null. Regenerating alone will not fix this if the underlying page content does not include offer information. Regeneration is a useful first step, but it is not a guaranteed fix. If your page genuinely does not contain product pricing or availability, you have additional options outlined below. ✅ When Is an Empty or Null Offers Field Acceptable? Not every business sells products or services with listed prices. If the Offers field does not apply to your page or business model, leaving it null or omitting it entirely is often acceptable. Consider the following: - Google's structured data guidelines do not require an Offers field for all Product schemas, but they do recommend it for better eligibility in rich results like price snippets. - A null Offers field will typically generate a warning rather than a critical error in Google Search Console, meaning your schema is still valid — just not fully enhanced. - If the Offers field genuinely does not apply to your business (e.g., you list products but handle pricing offline or via inquiry), it is safe to remove or omit this field. 🛠️ How to Resolve the 'offers': null Error in OTTO Follow the steps below based on your situation: 1. Go to the left sidebar and select OTTO SEO, then navigate to your schema markup section within OTTO. 2. Locate the schema showing the 'offers': null error and open it for editing. 3. Option A — Your page has pricing data: Click Regenerate to prompt OTTO to re-scan the page. If pricing, availability, or offer details are present in your page content, OTTO will auto-populate the Offers field. Review the result and approve the schema. 4. Option B — You want to add offers manually: Instead of regenerating, click into the schema editor and manually enter the Offers details — including price, price currency, and availability. This is the most reliable method when your page content is minimal or structured in a way OTTO cannot easily parse. 5. Option C — Offers do not apply to your business: In the schema editor, you can clear the Offers field entirely or remove that property from the schema. An empty or omitted Offers field will not break your schema — it will simply not qualify for offer-related rich result features. Save and approve the updated schema. 🔗 Note: Relative vs. Absolute URLs in Schema Some customers experiencing schema errors alongside the null Offers issue have also encountered a separate problem: OTTO or an existing schema may be generating relative URLs (e.g., /products/item) instead of absolute URLs (e.g., https://www.yoursite.com/products/item) in fields like url or image. Search engines require absolute URLs in structured data. If you notice URL-related warnings in Google Search Console alongside your schema errors, check that all URL fields in your schema use the full absolute format including the protocol and domain. 💡 Quick Reference: Which Option Should I Use? - Page has pricing content but offers show null → Regenerate the schema, then review and approve. - Page content is sparse or OTTO cannot detect pricing → Manually enter Offers details in the schema editor. - Offers do not apply to your business or page → Clear or omit the Offers field; this is safe and will not invalidate your schema. - Schema is marked FOUND and appears hardcoded → Edit the field in OTTO, or work with your developer to update the source code 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 Recurring Schema Deletion Bug in OTTO

🔍 Problem Overview Some customers experience a bug where a deleted VacationRental schema keeps reappearing on their pages after removal. This causes SEO optimizations to disappear overnight and prevents proper site indexing. The issue stems from a database inconsistency where schema rows marked for deletion are not properly flagged as deleted in the system. 🛠️ Root Cause Engineering identified that schema records with a deleted_at timestamp but was_deleted = False were not being fully processed. This caused the system to treat them as active, leading to automatic re-deployment of the schema during nightly reprocessing cycles. ✅ Permanent Fix Applied Engineering executed a one-time database correction: Set was_deleted = True on all schema rows where deleted_at IS NOT NULL AND was_deleted = False. They also fixed the underlying deletion code path to ensure future deletions are properly recorded and respected. 🧪 Verification Steps 1. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer. 2. Locate a page where the VacationRental schema previously reappeared (e.g. taking-flight-with-disc.html). 3. Confirm the schema no longer appears on the page. 4. Wait 24 hours and recheck the page to ensure the schema does not return. 5. Verify SEO optimizations remain intact and indexing resumes normally. 🛡️ Prevention The deletion logic has been corrected so that any schema marked for deletion is immediately and permanently flagged with was_deleted = True. Related fixes in the OTTO pipeline now prevent silent re-deployment of stale schemas and ensure audit trails are maintained. 📌 Related Fixes (Completed) - OTTO: Domain Level Schema Retains Old Location After Removal From Brand Vault - OTTO & Audit: Manual reprocessing is un-deploying the schema - fix(otto): clean stale FOUND schemas for pages with no HTML schema data If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Diagnose OTTO Plugin Slowdown and Form Redirect Issues

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

🔧 Fix OTTO Installation Detection Issues with Cloudflare Proxy

Overview If OTTO cannot detect your Search Atlas plugin installation and your domain uses Cloudflare, the issue may be related to your Cloudflare DNS proxy configuration. Specifically, when your domain's DNS record is set to DNS only (grey cloud) instead of Proxied (orange cloud), OTTO may fail to detect the installation correctly. This article explains why this happens and walks you through the fix. Why This Happens OTTO's installation detection relies on traffic being routed through Cloudflare's proxy. When a DNS record is set to DNS only (grey cloud), traffic bypasses Cloudflare entirely. As a result: - OTTO's installation detection cannot complete successfully. - Search Atlas may not recognize your site as properly installed. This can affect your apex domain (e.g., yourdomain.com), your www subdomain, or both — even if you have completed the installation steps correctly inside Search Atlas. How to Fix It You will need to log in to your Cloudflare account and update the proxy status for the affected DNS record(s). Follow these steps: 1. Log in to your Cloudflare dashboard at dash.cloudflare.com. 2. Select the account and domain that you are connecting to OTTO. 3. Click DNS in the left-hand navigation to open your DNS records. 4. Locate the A record or CNAME record for your apex domain (e.g., yourdomain.com) and your www subdomain if applicable. 5. Check the Proxy status column for each record. If it shows a grey cloud and the label DNS only, the proxy is disabled. 6. Click the grey cloud icon to toggle it to an orange cloud (Proxied) and confirm the change when prompted. 7. Save your changes and allow a few minutes for the update to take effect. Verify the Fix in Search Atlas Once you have enabled the Cloudflare proxy for the affected records, return to Search Atlas and check whether OTTO now detects your installation successfully. If the installation is detected, the issue should be resolved and OTTO will be active on your site. Important Considerations - Check both your apex domain and www subdomain — both records may need to be set to Proxied. - If you are unsure which records to update, review all DNS entries associated with the domain you connected to OTTO. - If you have made the change and OTTO still cannot detect your installation, please reach out to our support team and we can investigate further.

🔌 Fix OTTO Pixel Not Detected on WordPress

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

⚙️ OTTO and Site Audit Bug Fixes

A set of targeted stability improvements has been shipped for OTTO and Site Audit, resolving visual inconsistencies, a persistent modal issue, and table rendering regressions that were impacting the audit workflow. 🐛 What's Fixed - White-label messaging consistency: Pixel and state messaging was displaying inconsistently across different surfaces in white-label environments. Labels and status indicators now appear uniformly wherever white-label is applied. - GSC connection modal auto-dismiss: The Google Search Console connection modal in OTTO Audit was remaining open after a successful connection. It now closes automatically once the connection is confirmed. - shadCN component rendering: Several interface components built with the shadCN library were rendering incorrectly throughout OTTO. Underlying component issues have been resolved to restore consistent styling across the platform. - Page-title table responsiveness: The page-title table had incorrect responsive scroll thresholds and cell-wrapping behaviour, causing layout issues on smaller screens. Both have been corrected. - Site Audit DataTable visual regressions: A recent DataTable migration introduced visual regressions in Site Audit. All affected display issues have been fully resolved. 📋 What to Expect - White-label pixel and state messaging will now appear consistently across all surfaces. - The GSC connection modal in OTTO Audit will dismiss automatically after a successful connection, eliminating the need to manually close it. - OTTO interface components will render without visual glitches or styling inconsistencies. - The page-title table will scroll and wrap cells correctly across all screen sizes. - Site Audit's DataTable will display accurately with no visual regressions from the recent migration. If you need further assistance, open 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.

🛠️ Fix the Site Explorer Backlinks Export Error

🔍 What Is This Error? When attempting to export backlinks from the Site Explorer backlinks page, some users encountered the following message: "Export unavailable — This page belongs to a different domain." This error prevented the export from completing, even when the backlinks data was clearly visible on screen. The data itself was not missing — the issue was caused by a mismatch in the internal site identifier used by the export feature, which caused it to incorrectly treat the page as belonging to a different domain. ✅ Current Status: Resolved This issue has been fully investigated and fixed by the Search Atlas engineering team. The underlying cause — a mismatched site identifier that blocked the export — has been corrected, and the fix is now live for all users. If you encountered this error in the past, you should now be able to export your backlinks without seeing this message. 🚀 How to Export Your Backlinks Now 1. Navigate to Site Explorer and open your project. 2. Go to the backlinks section of your project within Site Explorer. 3. Verify that your backlinks data is displayed as expected. 4. Use the export option to download your backlinks. The export should now complete successfully. ⚙️ What to Do If the Error Still Appears In the rare case that you still see the "Export unavailable — This page belongs to a different domain" message after the fix, try the following steps before contacting support: - Refresh the page and attempt the export again. A stale session can sometimes carry over a previous error state. - Clear your browser cache and reload the platform to ensure you are running the latest version. - Try a different browser to rule out a local browser issue. - Confirm you are viewing the correct project. Navigate to Site Explorer, select your intended project, and then attempt the export from within that project's backlinks view. If the error persists after trying all of the above, contact support and include the following details to help us investigate quickly: the exact URL or domain you entered in Site Explorer, a screenshot of the error message if possible, and the date and time you encountered the error. 💡 Additional Notes The engineering team also resolved related export issues in Site Explorer during the same period, including CSV exports returning empty files for keywords, competition, and backlinks data. If you experienced any of those problems, they have been addressed as well and exports should now work correctly across all data types. 🙋 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 CMS Image Alt Text Sync Errors

🔍 Overview If you see a "Something went wrong. Please try again" error when trying to sync image alt text optimizations to your CMS through OTTO, this article explains what causes it, what you can try yourself, and how to get it escalated quickly if the error persists. ⚠️ What Causes This Error This error is a known bug that prevented OTTO from successfully syncing image alt text optimization tasks to a connected CMS. Engineering ticket SPE-1137 was raised and a fix has been deployed to production. Most users are no longer affected. However, if you are still experiencing this error, the steps below will help you resolve it or get the right team involved fast. Important: OTTO's Sync to CMS feature currently works exclusively with the WordPress plugin. If your site runs on a different CMS platform (such as Drupal), sync is not yet supported for image alt texts. ✅ Steps to Try First 1. Confirm your WordPress plugin is installed and connected. The Sync to CMS feature requires the Search Atlas WordPress plugin to be active and properly connected to your site. If the plugin is outdated or disconnected, syncing will fail. 2. Retry the sync. Go to OTTO in the platform and attempt to sync the image alt text task again. Temporary network or session issues can sometimes cause a one-off error. 3. Refresh your session. Log out of the platform, clear your browser cache, log back in, and try the sync again. 4. Try a different browser. If the error continues, attempt the sync in an alternative browser to rule out a local browser issue. 5. Check your site's theme. If your WordPress site uses the Oxygen theme, image alt text syncing has been identified as unreliable due to how that theme renders pages over HTTP. This is a known limitation — contact support (see below) so our team can advise on the best path forward for your setup. 📋 If the Error Persists If you have followed the steps above and the error still appears, our support and engineering teams will need to investigate further. To help us resolve your issue as quickly as possible, please have the following ready before reaching out: - A screen recording or screenshots clearly showing the error occurring during the sync attempt - The URL of the page or post you are trying to sync alt texts to - The name of your WordPress theme - Confirmation of whether your Search Atlas WordPress plugin is installed and which version you are running Having this information prepared allows our team to escalate your case with full context and minimise back-and-forth. 💡 Known Limitations to Be Aware Of - WordPress only: Sync to CMS for image alt texts is supported exclusively via the Search Atlas WordPress plugin. Other CMS platforms are not currently supported for this feature. - Oxygen theme: Image alt text syncing has been reported as unreliable on sites using the Oxygen theme due to its HTTP render path. Our team is aware of this behaviour. 🤝 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 Cloud Stack Build Server Error 500

🔍 What This Article Covers Some customers have experienced Cloud Stack builds that fail with a Server Error 500 and remain stuck on the message 'Waiting for content generation to complete...'. This issue was caused by a platform-level bug that has since been resolved by our engineering team. This article explains what happened and what steps to take so your build completes successfully. ⚙️ What Caused the Error This error was traced to an internal platform issue affecting the Cloud Stack build process. The engineering team identified and resolved the bug, and the fix has been deployed across the platform. ✅ Steps to Resolve Because the underlying bug has been fixed, you do not need to change your build settings or recreate your project. Follow the steps below to successfully complete your Cloud Stack build: 1. Retry the build. Attempt to run the Cloud Stack build again. The error should no longer occur now that the platform fix is in place. 💡 Tips If the Build Still Fails - Make sure you are using the latest version of your browser and that no browser extensions are interfering with the platform. - Try a different browser entirely if the issue persists. - Wait a few minutes and attempt the build again, as occasional transient network issues can cause temporary failures. 🆘 Still Need Help? If your Cloud Stack build continues to fail after following the steps above, please gather the following details before reaching out so our team can investigate quickly: - Your domain or target keyword for the build - A screenshot or screen recording of the error If you need further assistance, please contact our support team so we can investigate further.

OTTO Manual Edits Not Saving in OTTO SEO

🔍 Overview Some users have experienced an issue where manually editing OTTO suggested fixes in the OTTO SEO task appears to work — the edit fields open, changes can be typed in — but clicking Save does not retain those changes. Following the steps below has resolved this issue for affected accounts. ✅ What You Should Do If your manual edits to OTTO suggested fixes are not saving, work through these steps in order: 1. Navigate to the OTTO SEO task section in the platform. 2. Locate the OTTO suggested fix you want to edit and open the edit fields. 3. Make your changes and click Save. 4. Refresh the page and reopen the same item to check whether your edits have been retained. 5. If the edits are still not saving after a refresh, disconnect and reconnect OTTO for the affected site: go to your OTTO settings, disconnect OTTO from the site, wait a few seconds, then reconnect it. This re-establishes the sync between OTTO and the site and has resolved the save issue for affected users. 6. After reconnecting, return to the OTTO SEO task, re-enter your manual edits, click Save, and refresh the page to confirm the changes are now persisting. If your changes are persisting after saving and refreshing, the issue has resolved itself for your account. ⚠️ If You Are Still Experiencing This Issue If disconnecting and reconnecting OTTO does not resolve the problem, gather the following details before reaching out so the investigation can begin quickly: - The specific field or suggested fix you are trying to edit. - Whether any error message appears after clicking Save, or if the page simply reverts your changes silently. - The affected site URL and the OTTO task type. If you need further assistance, please reach out to our support team via the chat icon in the bottom-right corner of the platform, and a member of our team will be happy to help. 📋 Summary Manually edited OTTO suggested fixes in the OTTO SEO task may fail to save for some users. Disconnecting and reconnecting OTTO for the affected site has resolved this issue for affected accounts. If the problem persists after reconnecting, contact our support team with the details listed above so the issue can be investigated promptly.

🛠️ Fix OTTO Script Installation and Logo H1 Issues

**🔍 Overview** Two of the most common OTTO setup issues are **not being able to locate the installation script** and a **logo being detected as an H1 heading** on your site. Both problems can prevent OTTO from running diagnostics correctly and deploying optimisations. This guide walks you through resolving each one. **⚙️ Step 1 — Find and Install the OTTO Script** The OTTO script is the foundation of all automation. Without it installed on your site, diagnostics cannot run and no changes can be deployed. 1. Log in to Search Atlas and navigate to **OTTO SEO** in the left sidebar, then open **SEO Automation**. 2. Select the website project you want to work with. 3. Look for the **OTTO Setup** or **Connect Site** prompt. If OTTO is not yet activated, you will see a button to begin setup — click it. 4. On the setup screen, locate the **OTTO script snippet**. It is a short JavaScript tag that looks similar to: **** 5. Copy the full script snippet. 6. Paste the snippet into the **** section of every page on your website. If you use a CMS such as WordPress, you can add it via your theme's header file or a header/footer plugin. 7. Save your changes and reload your website. **Tip:** If you manage multiple sites, each site has its own unique script. Make sure you copy the script for the correct project. **✅ Step 2 — Verify the Script Is Detected** After installation, confirm that Search Atlas can detect the script before attempting to run diagnostics. 1. Return to **OTTO SEO** in the left sidebar and open **SEO Automation**. 2. Open your website project and look for a **script status indicator** or **connection status** badge near the top of the page. 3. If the status shows **Connected** or **Active**, the script is installed correctly and diagnostics can proceed. 4. If the status shows **Not Detected**, double-check that the script was pasted inside the **** tag and that there are no caching layers serving an older version of your page. Clear your site cache and try the verification again. **Common reason diagnostics fail:** A caching plugin or CDN (such as Cloudflare) serving a cached page without the new script. Always purge your cache after installation. **🖼️ Step 3 — Resolve the Logo Detected as H1** OTTO flags a logo as an H1 when your site's HTML wraps the header logo image inside an ** ** tag. This is a structural SEO issue because every page should have exactly one H1 that describes the page content — not the site logo. To fix this issue, you need to change the HTML tag wrapping your logo from **** to a non-heading element such as a ** ** or ** **, or simply remove the heading tag entirely and keep the anchor link and image only. 1. Open your website's theme or template editor and locate the header file (commonly **header.php** in WordPress themes, or the equivalent in your CMS). 2. Find the code block that outputs the logo. It will look similar to: **Site Name** 3. Replace the outer **** and **** tags with a neutral element. For example: ** Site Name ** 4. Save the file and clear your site cache. 5. Return to OTTO and re-run diagnostics to confirm the H1 issue is resolved. **Important:** If your theme does not give you direct access to the header HTML, check your theme's **Customizer** or **Logo settings** — some page builders and themes have a toggle to control whether the logo is wrapped in a heading tag. Page builders such as Elementor, Divi, and Beaver Builder expose this as a simple dropdown option in the header widget settings. # **🚀 Step 4 — Re-run OTTO Diagnostics** Once the script is verified and the logo H1 issue is corrected, run a fresh diagnostic scan to confirm everything is in order. 1. Go to **OTTO SEO** in the left sidebar and open **SEO Automation**. 2. Open your website project and click **Run Diagnostics** (or the equivalent scan button in the OTTO panel). 3. Wait for the scan to complete. This typically takes a few minutes depending on the size of your site. 4. Review the results. The logo H1 flag and any script-related warnings should no longer appear. # **💡 Quick Troubleshooting Checklist** - **Script not detected?** Confirm it is in the ****, not the footer, and that your cache has been cleared. - **Logo H1 persists after editing?** A caching layer may still be serving the old HTML — purge all caches including your CDN. - **Using a page builder?** Check the header widget or section settings for a heading-level option and set it to none or paragraph. - **Changes not saving?** Ensure you have the correct file permissions and that you are editing the active theme, not a parent theme that gets overridden. # **💬 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 Trailing Slash Duplicate URL Fix

Overview A confirmed bug caused OTTO's Brand Vault (formerly Knowledge Graph) to automatically append a trailing slash to homepage URLs inside the Top Pages section. This prevented customers from removing the slash or adding the correct URL format, and caused OTTO to create and auto-optimize duplicate versions of the same page. This issue has been resolved by the Search Atlas engineering team. If you are still experiencing duplicate homepage URL entries or related optimization issues in your OTTO session, please reach out to our support team so they can review and correct your account directly. What the Bug Did - Added a trailing slash to homepage URLs automatically (e.g., example.com/ instead of example.com). - Prevented manual deletion or correction of the affected URL inside Brand Vault. - Caused OTTO to treat the two URL variants as separate pages and apply optimizations to both, creating duplicates. Current Status This bug has been fully resolved in the Search Atlas platform. The fix addresses trailing slashes being incorrectly stripped or appended on homepage URLs in the Top Pages section of Brand Vault, and prevents duplicate URL optimization from occurring going forward. Still Seeing Duplicate URLs? Because this was an engineering-level fix, there is no self-service action required on your end. If you are still seeing duplicate homepage URL entries or residual duplicate optimizations in your Brand Vault after the fix has been applied, please contact our support team via the chat widget so an agent can review your specific OTTO session and clear any remaining duplicate data from your account. If you need further assistance, don't hesitate to reach out to us via the live chat widget in the bottom-right corner of the platform (type human teammate to be connected with a member of our team).

🔍 OTTO Not Detecting Your Website in GA4

🧭 Understanding the Problem There are two separate connections that must be in place for OTTO to detect your website through GA4: - GA4 connected to Search Atlas — your Google Analytics 4 account is authorized inside the platform. - OTTO receiving data from GA4 — OTTO specifically recognizes and maps your website property within that connected GA4 account. Having GSC connected successfully does not guarantee OTTO will detect your site in GA4. These are independent integrations. This article walks you through resolving the GA4 detection failure specifically for OTTO. ✅ Before You Begin Confirm the following before troubleshooting: - Your GA4 account is connected inside Search Atlas (not just GSC). - The website you want OTTO to detect — for example, www.axsysdental.com — exists as a property inside that GA4 account. - You have at least Viewer permissions on the GA4 property. 🔗 Step 1 — Verify GA4 Is Connected to Search Atlas 1. In the left sidebar, click OTTO SEO to open the OTTO dashboard at /seo-automation-v3. 2. Locate your website project and open its settings. 3. Check whether GA4 appears as a connected data source alongside GSC. If GA4 is not listed, you must connect it before OTTO can detect any GA4 property. 4. If GA4 is not connected, navigate to Site Metrics → Site Explorer (GSC Accounts page) and click Connect GA Account, complete the Google authorization flow, and grant access to the correct Google account that owns your GA4 property. 🏠 Step 2 — Confirm the Correct GA4 Property Is Selected Even when GA4 is authorized, OTTO may be pointed at the wrong account or property. This is the most common reason a website is not detected. 1. Inside the OTTO dashboard, open the GA4 connection settings for your project. 2. Check which GA4 Account is selected. If you manage multiple Google accounts, make sure the account shown is the one that contains your website property. 3. Under the selected account, verify the correct GA4 Property is chosen — for example, the property associated with www.axsysdental.com. 4. If the property is missing from the dropdown, it means the authorized Google account does not have access to that property. In this case, disconnect GA4 and reconnect using the correct Google account. 🔄 Step 3 — Disconnect and Reconnect GA4 If the correct property is selected but OTTO still does not detect the website, a fresh authorization often resolves the issue. 1. In the OTTO dashboard at /seo-automation-v3, open the data source settings for your project. 2. Disconnect the existing GA4 connection. 3. Re-authorize GA4 using the Google account that owns the target property. 4. When prompted to select a property, choose the exact property that matches your website URL. 5. Save the connection and wait up to 5 minutes for OTTO to sync and detect the website. 📊 Step 4 — Check Site Metrics for Data Flow After reconnecting, verify that data is flowing correctly by checking Site Metrics. 1. In the left sidebar, click Site Metrics to open the explorer at /site-explorer/list. 2. Search for your website — for example, www.axsysdental.com. 3. If organic and traffic data is populating, the GA4 connection is active and OTTO should now detect the site. 4. If data is missing here as well, this confirms a broader data sync issue that requires backend review by our team. ⚠️ Common Reasons OTTO Cannot Detect Your Website - Wrong Google account authorized — the authorized account does not own or have access to the GA4 property. - Multiple GA4 accounts — the website property exists in a different GA4 account than the one connected. - GA4 property is new — properties created within the last 24–48 hours may not yet be available for OTTO to detect. - Insufficient permissions — the Google account used during authorization has less than Viewer access on the GA4 property. - Website URL mismatch — the URL in your OTTO project does not exactly match the URL registered in the GA4 property (for example, with or without www). 💬 Still Not Detected After Troubleshooting? If OTTO still does not detect your website after completing all steps above, our team can perform a backend verification to confirm the GA4 property mapping and data flow for your specific 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 Fixes Deployed but Not Showing on Your WordPress Site

🔍 What's Happening If your OTTO fixes show as Deployed in the dashboard but are not visible in your page source or SEO extensions, the most common cause is that the OTTO WordPress plugin is deactivated on your site. OTTO uses a WordPress plugin to render its SEO optimizations as a real-time overlay. When the plugin is inactive, deployments are recorded in OTTO but nothing is applied to the live site. ✅ How to Fix It 1. Log in to your WordPress admin panel (typically at yourdomain.com/wp-admin). 2. Navigate to Plugins → Installed Plugins. 3. Locate the OTTO SEO plugin. 4. If it shows as Inactive, click Activate. 5. Reload your live site and confirm your deployed fixes now appear. ⚠️ Why Does This Happen? The OTTO plugin can be deactivated unintentionally during WordPress updates, theme changes, or routine maintenance. Periodically verify the plugin is active, especially after WordPress environment updates. 💬 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 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 Script Deployment Across Multiple Pages

🧭 Overview When title tags, meta descriptions, and headings are marked as deployed in the Search Atlas dashboard but are not showing up on your live website, the most common cause is an incomplete OTTO script or UUID installation. This means the script is either missing from certain pages, installed incorrectly, or not firing properly on your platform. This article walks you through diagnosing and fixing the issue across WordPress, Shopify, Webflow, and custom-built websites. 🔍 Step 1 — Confirm the Issue Is Script-Related Before diving into platform-specific steps, verify that the OTTO script is the root cause: 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Open the OTTO project for your website and check which pages show deployed changes. 3. Visit one of those pages in your browser, right-click the page, and select View Page Source. 4. Use Ctrl+F (or Cmd+F on Mac) to search for otto or your unique UUID string. 5. If the script is not found in the page source, the script is missing from that page. 6. Repeat this check on two or three additional pages to determine whether the problem is isolated to specific pages or affects your entire site. Important: A partial installation — where the script exists on some pages but not others — is the most frequent reason deployed changes appear only on part of your website. 🟦 WordPress If your site is built on WordPress, the OTTO script should be loaded globally via a plugin or your theme. A partial installation usually means the script was added to only one template or page. 1. Log in to your WordPress admin dashboard. 2. Navigate to Appearance → Theme File Editor or open your active theme's header.php file. 3. Confirm the OTTO script tag with your UUID appears inside the <head> section. 4. If you used a plugin such as Insert Headers and Footers or WPCode, open that plugin and verify the script is set to load on All Pages, not just the front page or specific post types. 5. Clear any caching plugins (e.g., WP Rocket, W3 Total Cache) and visit your site again to recheck the page source. 🟩 Shopify On Shopify, the OTTO script must be placed in the theme layout file so it loads across every page of your store. 1. In your Shopify admin, go to Online Store → Themes → Edit Code. 2. Open the theme.liquid file (or your active layout file). 3. Confirm the OTTO script tag with your UUID is placed inside the <head> tags, not inside a section or block file. 4. If the script is in a section file, it will only load on pages that include that section — move it to theme.liquid. 5. Save the file, then use Shopify's Preview mode to check the page source on your homepage, a product page, and a collection page. 🟪 Webflow In Webflow, scripts added at the page level only affect individual pages. The OTTO script must be added at the site level to deploy across all pages. 1. Open your project in the Webflow Designer. 2. Go to Project Settings → Custom Code. 3. Paste the OTTO script tag with your UUID into the Head Code field under the Site-wide section — not under any individual page settings. 4. Click Save Changes and publish your site. 5. If you previously added the script under a specific page's custom code, remove it from there to avoid duplicate or conflicting instances. ⚙️ Custom or Other Platforms For websites built on custom frameworks, static site generators, or other CMS platforms, the goal is the same: ensure the OTTO script loads in the <head> of every page. 1. Locate the global layout or master template file for your platform — this is typically named layout.html, base.html, _layout.liquid, or similar. 2. Paste the full OTTO script tag with your UUID inside the <head> element of that file. 3. If your platform uses a build process (e.g., Next.js, Gatsby, Hugo), redeploy or rebuild the site after adding the script. 4. For static HTML sites, you must add the script to the <head> of every individual HTML file, or consolidate pages into a shared template. 5. After updating, verify the script appears in the source of at least three different page types on your live site. ✅ Step 2 — Re-Verify in Search Atlas After Fixing 1. Once the script is confirmed present across your pages, return to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Open your OTTO project and trigger a re-scan or refresh the deployment status for the affected pages. 3. Allow up to 15 minutes for changes to propagate, then revisit your live pages and check the title tags, meta descriptions, and headings directly in the page source. 4. You can also use the Website Studio (Left sidebar → Website Studio, URL: /website-studio) to review on-page SEO element status after redeployment. ⚠️ Common Mistakes to Avoid - Adding the script at page level instead of site level — always use a global template or layout file. - Incorrect UUID — copy the UUID exactly from your OTTO project settings; extra spaces or characters will break the connection. - Caching — cached versions of pages may hide a freshly added script; always clear your cache before re-testing. - Multiple script instances — having the script in both a global template and individual pages can cause conflicts; keep only one instance. 💬 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 Noindex on WordPress Blog Page

🔍 Overview If your WordPress /blog/ (or Posts page) is showing a noindex, nofollow robots meta tag even though your per-page settings and Yoast SEO are set to index, OTTO may be deploying a conflicting robots directive. This article explains why this happens and walks you through the steps to fix it. ⚙️ Why This Happens WordPress has a special page type called the Posts page (also known as the blog index). This is the page you assign under Settings → Reading → Your homepage displays → A static page → Posts page. It behaves differently from a standard post or page — it has no editable content in the WordPress editor, and some SEO plugins treat it as a virtual or system page. OTTO can sometimes apply a noindex, nofollow robots meta tag to this page type due to one or more of the following reasons: - OTTO detects the Posts page as a non-canonical archive or paginated index and applies conservative indexing rules automatically. - A previously deployed OTTO configuration included a noindex directive that is now persisted, even if you have since updated your settings. - A conflict exists between OTTO's deployment layer and another active SEO plugin (such as Yoast SEO), where OTTO's output takes precedence at the rendering layer despite the plugin showing the correct settings. 🔎 How to Confirm the Issue 1. Visit your /blog/ URL in a browser and open View Source (Ctrl+U or Cmd+U). 2. Search for robots in the source code. 3. Check whether the rendered meta tag reads noindex, nofollow — if it does, and your Yoast or plugin settings say otherwise, OTTO is likely overriding them. 4. Also check the page in Google Search Console under URL Inspection to confirm what Googlebot sees. 🛠️ Steps to Fix the Issue 1. Log in to your Search Atlas account and navigate to Left sidebar → OTTO SEO. 2. Locate the OTTO project connected to your WordPress site and open it. 3. Find the deployment settings for your Posts page / blog index URL (typically /blog/ or whichever URL is set as your Posts page). 4. Check whether a robots meta deployment is active for that URL. If a noindex directive has been deployed, update it to index, follow and redeploy. 5. If no explicit robots setting is configured inside OTTO but the noindex is still appearing, this indicates a persisted deployment from a previous OTTO configuration. In this case, use the Disable OTTO toggle for that specific page to suppress OTTO's output, then re-enable it after clearing the cached deployment. 6. After making changes, purge your WordPress cache (via your caching plugin or hosting provider) and wait a few minutes before re-checking the rendered source. 7. Re-run the URL Inspection in Google Search Console and request re-indexing once the correct index, follow tag is confirmed in the source. 💡 Important Notes - The Posts page is not editable in the WordPress block editor. This means per-page Yoast settings may not apply in the same way as regular pages. Always verify the rendered output in View Source rather than relying solely on plugin UI settings. - If you are running Yoast SEO, Rank Math, or another SEO plugin alongside OTTO, there may be a conflict where OTTO's deployment layer outputs its own robots tag independently of the plugin. OTTO's tag will typically appear separately in the <head> and may take precedence with crawlers even if the plugin tag looks correct. - Disabling OTTO on a per-page basis while a bug fix is in progress is a safe interim step — your Yoast or Rank Math settings will then control the robots meta for that URL. 🚀 Prevention Tips - After any new OTTO deployment, spot-check critical pages — especially your homepage, blog index, and key category pages — by viewing the rendered source directly. - Use Google Search Console's URL Inspection tool regularly to confirm what Googlebot sees, not just what your plugin settings display. - When assigning a Posts page in WordPress Settings → Reading, note that URL in your OTTO configuration and verify its robots settings are explicitly set to index, follow. 💬 Still Seeing the Issue? If you have followed all the steps above and the noindex tag is still appearing on your WordPress Posts page, 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.

🔧 OTTO UI Bug Fixes and Dropdown Improvements

A targeted bug fix update improves the reliability and visual accuracy of key OTTO interface elements, ensuring smoother interactions across deploy actions, Brand Vault dropdowns, and pagination controls. ✨ What's New This release addresses three UI issues that were affecting the OTTO experience: - Deploy/Undeploy Spinner: The loading spinner that appears when deploying or undeploying OTTO actions was not displaying or behaving correctly. This has been resolved so the spinner accurately reflects the operation in progress. - Brand Vault Dropdown Clipping: The Brand Vault dropdown was being visually clipped, cutting off options and making selection difficult. It now renders fully and correctly within the interface. - Pagination Dropdown Width: The pagination dropdown was rendering at an incorrect width, causing layout inconsistencies. It now displays at the proper size for a cleaner, more consistent look. 🛠️ How to Use It 1. Navigate to OTTO SEO in your Search Atlas dashboard. 2. Attempt a deploy or undeploy action and confirm the spinner appears and completes as expected. 3. Open the Brand Vault dropdown and verify all options are fully visible without clipping. 4. Use the pagination controls and confirm the dropdown renders at the correct width. 📋 What to Expect These are visual and interaction bug fixes with no changes to underlying functionality. No configuration or workflow changes are required on your end. All improvements take effect automatically upon your next session. If you need further assistance, open 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 Deployed Fixes Not Showing on Your Site

🔍 Why OTTO Fixes Appear Deployed but Aren't Visible When OTTO marks an SEO fix as Deployed, it means you have approved/deployed the fix in OTTO. The status does not wait for a check that the live site shows the change — caching can delay what visitors see. However, several layers between the plugin and the browser can prevent those changes from appearing immediately in the live page source or in Chrome SEO extensions. The most common culprits are caching, conflicting SEO plugins, and an outdated or inactive OTTO plugin. ✅ Step 1: Confirm the Fix Is Truly Deployed Before troubleshooting, verify the deployment status inside Search Atlas. 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and open your project card. 2. Navigate to OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks and locate the relevant task. 3. Confirm the status shows Deployed. If it still shows Pending or In Progress, wait a few minutes and refresh the page. 🗑️ Step 2: Clear Your WordPress Cache Caching plugins serve stored copies of your pages. Until the cache is cleared, visitors — and tools like Chrome SEO extensions — will see the old version. Clear the cache in whichever plugin you use: - WP Rocket — WordPress Dashboard → WP Rocket → Clear Cache - W3 Total Cache — WordPress Dashboard → Performance → Purge All Caches - WP Super Cache — WordPress Dashboard → Settings → WP Super Cache → Delete Cache - LiteSpeed Cache — WordPress Dashboard → LiteSpeed Cache → Purge All If you are unsure which caching plugin is active, check with your developer or hosting provider. ☁️ Step 3: Purge Your CDN Cache If your site uses a CDN such as Cloudflare, the CDN may still be serving a cached version of the page. Log in to your CDN provider's dashboard and purge the cache for the affected URLs — or purge everything if you are unsure which URLs are affected. 🌐 Step 4: Test in a Private Browser Window Your browser may be displaying a locally cached page. Open an incognito or private browsing window, navigate to the affected URL, and right-click → View Page Source to inspect the meta tags directly. This bypasses browser and extension caches and gives you the true live output. ⚡ Step 5: Check for Conflicting SEO Plugins If another SEO plugin — such as Yoast SEO, Rank Math, or All in One SEO — is active on your WordPress site at the same time as the Search Atlas plugin, it may override OTTO's meta descriptions and title tags. To resolve this: 1. In your WordPress dashboard, go to Plugins → Installed Plugins. 2. Identify any other active SEO plugins. 3. Disable them or configure them to stop outputting competing meta tags on pages that OTTO manages. 🔌 Step 6: Verify the OTTO Plugin Is Active and Up to Date The Search Atlas OTTO plugin must be installed, activated, and on the latest version. To check: 1. In your WordPress dashboard, go to Plugins → Installed Plugins and confirm the Search Atlas plugin shows as Active. 2. If an update is available, click Update Now. 3. To reinstall or download the latest plugin file, go to Left sidebar → OTTO SEO → Installation Guide inside Search Atlas. 🔄 Step 7: Re-deploy the Fix If all the steps above are complete and the changes still do not appear, try re-deploying the fix: 1. Go to OTTO SEO → All Sites (SEO Automation) → Select your project → Tasks. 2. Find the relevant task, click Undeploy, then click Deploy again. 3. Clear your WordPress and CDN caches once more, then recheck the page source in a private browser window. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Script Unreachable Error on Your Wix SEO Dashboard

Is This the Right Article for You? If your OTTO scripts are showing unreachable on one or more Wix client sites, this article will help you get the right support to resolve it. Why OTTO Scripts Show as Unreachable on Wix An OTTO script can report unreachable on a Wix site for several reasons, including a connectivity issue on the Search Atlas side or a configuration problem with how the site is connected to OTTO. Because Wix has platform-specific limitations, these issues typically require investigation by the Search Atlas support team to resolve. What to Do Because the root cause of an OTTO script unreachable error on a Wix site often requires backend investigation, the recommended step is to contact the Search Atlas support team directly. When you reach out, please provide: - Your Search Atlas account email - The name and URL of the affected Wix site - A description of the issue, including when you first noticed the unreachable status The support team will investigate your account and site configuration and work with you to restore the OTTO connection for your Wix site. Still Need Help? If you are still experiencing this issue, please use the chat widget on this page to contact the Search Atlas support team and mention this article. We're here to help investigate your specific account and site configuration.

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

🔌 Fix Multiple Websites Disconnected from OTTO SEO

🔍 Overview If multiple websites have suddenly disconnected or disengaged from OTTO SEO, you are not alone. This can happen for several reasons, including authentication changes, subscription limits, or platform sync issues. This article explains the most common causes and walks you through how to reconnect your sites. ⚠️ Common Reasons for Mass Disconnection - Subscription or plan change: If your plan was downgraded, renewed, or modified, the number of OTTO-activated sites allowed may have changed, causing some sites to disengage automatically. - Google Search Console re-authentication: OTTO SEO relies on a live connection to Google Search Console. If your Google account credentials expired or permissions were revoked, all connected sites under that account may disconnect at once. - Workspace ownership or user changes: Removing or changing the account owner, or revoking a team member's access, can break the link between OTTO and the sites they originally connected. - Platform sync timeout: Occasional platform-side sync issues can temporarily disengage sites. This is rare but can affect multiple properties at the same time. 🛠️ How to Reconnect Your Websites to OTTO SEO 1. Navigate to OTTO SEO V3: In the left sidebar, click OTTO SEO, then open SEO Automation to access the OTTO SEO dashboard at /seo-automation-v3. 2. Review your site list: You will see all sites associated with your workspace. Sites that are disconnected will show a disengaged or inactive status indicator next to their name. 3. Check your Google Search Console connection: At the top of the OTTO dashboard, verify that your Google Search Console account is still authenticated. If you see a prompt to reconnect, click it and follow the on-screen steps to re-authorize access. This single action can restore the connection for all sites linked under that Google account. 4. Re-activate each affected site: For sites that remain disengaged after re-authenticating, click the site name to open its OTTO profile, then click Activate OTTO to re-enable automation. 5. Verify site metrics are loading: After reconnecting, go to Left sidebar → Site Metrics (Site Explorer) to confirm that data is flowing correctly for each reconnected domain. 📊 How to Confirm All Sites Are Active Once you have completed the reconnection steps, return to the OTTO SEO V3 dashboard and confirm that each of your websites shows an active OTTO status. You can also check individual domain performance by navigating to Left sidebar → Keywords → Rank Tracker to verify that rankings and data are being tracked as expected. 💡 How to Prevent Future Disconnections - Keep Google Search Console permissions up to date: Ensure the Google account connected to Search Atlas retains owner-level access to all your Search Console properties. - Review your plan limits regularly: Check how many OTTO activations your current plan allows and ensure your active site count stays within that limit. - Avoid removing the primary workspace owner: If you need to change team roles, add the new owner before removing the existing one to maintain uninterrupted connections. - Monitor site status after any account change: Any time you update billing, team members, or Google permissions, log into the OTTO SEO V3 dashboard to confirm all sites remain active. 🆘 Still Seeing Disconnected Sites? If you have followed all the steps above and one or more sites are still showing as disengaged, or if a large number of sites disconnected simultaneously without an obvious cause, our team can investigate the issue 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 Unexpected Text on Shopify Homepage from OTTO

🔍 What Is Happening? When the OTTO SEO script is active on your Shopify store, you may notice unexpected or unfamiliar text appearing on your homepage. This is typically caused by OTTO injecting SEO content — such as meta descriptions, structured data labels, or optimised copy — directly into your page in a way that becomes visible to visitors rather than staying hidden in the page source. This is a known compatibility issue between the OTTO script and certain Shopify themes, and it can be resolved by following the steps below. ⚙️ Why This Happens OTTO automates on-page SEO by deploying a JavaScript snippet to your site. In most cases this works seamlessly, but some Shopify themes render JavaScript output in unexpected locations. When that happens: - SEO-optimised text meant for search engines appears as visible copy on the page. - Structured data or hidden schema markup gets displayed in plain text. - Injected content lands outside its intended HTML container. The root cause is usually a theme conflict rather than a fault with OTTO itself, but the fix is straightforward. 🚀 How to Fix It: Step-by-Step 1. Pause OTTO for the affected page. Log in to Search Atlas, navigate to OTTO SEO in the left sidebar and open SEO Automation (or go to /seo-automation-v3), find the affected URL, and temporarily disable OTTO automation for that page to stop new content from being injected while you troubleshoot. 2. Check your Shopify theme for stray text. In your Shopify admin, go to Online Store → Themes → Edit Code. Open your homepage template (usually index.liquid or sections/main-index.liquid) and look for any plain text that does not belong — this may be content OTTO injected that the theme rendered visibly. 3. Remove any stray injected content. If you find unexpected text in the theme files that was added by OTTO, carefully delete only that text. Do not remove any theme code. Save the file and preview your homepage to confirm the text is gone. 4. Clear your Shopify cache. In some cases, the old content may still appear due to caching. Use a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) or clear your browser cache, then reload the page. 5. Re-enable OTTO with script placement review. Before turning OTTO back on for this page, return to OTTO SEO in the left sidebar of Search Atlas and open SEO Automation to review the script placement settings for your Shopify integration. Ensure the script is set to inject into the <head> section only, not the body or a theme section block. 6. Test on a duplicate theme first. If you are unsure about any changes, duplicate your Shopify theme before making edits. This gives you a safe fallback if something goes wrong. ✅ How to Confirm the Issue Is Resolved After completing the steps above, verify the fix by doing the following: - Visit your Shopify homepage in an incognito or private browser window to see it without cached data. - Confirm no unexpected text is visible anywhere on the page. - Use a tool such as Google's Rich Results Test or View Page Source to confirm that OTTO's SEO content is present in the source code but not rendered visibly. - Re-enable OTTO automation for the page and monitor for 24 hours to ensure the issue does not return. 🛡️ How to Prevent This in the Future - Always test OTTO on a staging or duplicate theme before applying changes to your live Shopify store. - Review theme update notes — Shopify theme updates can change how JavaScript is rendered and may reintroduce this conflict. - Check OTTO deployment settings in Search Atlas after any major Shopify theme change to ensure script placement is still correct. 💬 Still Seeing the Issue? If the unexpected text persists after following these steps, or if you are not comfortable editing theme files, do not make further changes on your own. If you need further assistance, open 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.

🔧 Why OTTO Suggested Fixes Appear Blank

🧭 Overview When OTTO surfaces issues under Onpage Optimizations, it is showing you a list of identified problems on your site — not a list of ready-made fixes. Suggested fixes are a separate step that must be triggered deliberately. Recrawling your site will not populate blank suggested fixes, and there is no automatic background process that generates them after a crawl completes. If you see hundreds of blank fix entries alongside only a handful of populated ones (for example, 4–6 populated out of hundreds), this means fixes have not yet been generated for those items — not that something went wrong with the crawl. 🗺️ How the Two-Step Model Works Understanding the distinction between these two steps is the key to resolving blank suggested fixes: 1. Step 1 — Issue Discovery (Site Audit / Onpage Optimizations): When OTTO crawls your site, it identifies SEO issues and opportunities — missing meta descriptions, thin content, broken links, and so on. This step populates the issue list under Left sidebar → OTTO SEO → Overview and related views. It does not generate the actual fix content. 2. Step 2 — Fix Generation (Manual or Atlas Agent): Suggested fixes must be explicitly created. You choose how: write them yourself, or use Atlas Agent to generate them automatically at scale. Until this step is completed for a given issue, its suggested fix field remains blank. ✅ How to Populate Blank Suggested Fixes Choose the method that best fits your workflow: - Manually write a fix: Navigate to Left sidebar → OTTO SEO → Overview, open an issue with a blank fix, and enter your fix content directly in the suggested fix field. - Use Atlas Agent for bulk generation: Atlas Agent can generate suggested fixes across multiple issues automatically. Navigate to Left sidebar → OTTO SEO → Tasks and use Atlas Agent to trigger fix generation for the issues you want to address. This is the recommended approach when you have a large number of blank fixes. - Work through Page Explorer: Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer to review issues on a page-by-page basis and generate or enter fixes for each page individually. 🔄 What Recrawling Actually Does Recrawling your site from Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring refreshes the issue discovery layer only. It updates which problems exist on your site based on its current state. It does not: - Auto-generate suggested fix content for new or existing issues - Restore or recover previously blank fix entries - Trigger any background reprocessing of fix data After a recrawl, you may see updated issue counts or new issues appear — but any fix entries that were blank before will remain blank until you generate them using the steps above. ​ 💡 Tips for Large Sites - If you have hundreds of blank fixes (as is common after an initial audit of a large site like a roofing company with many service pages), use Atlas Agent in bulk rather than filling fixes one by one. - Prioritise high-impact issue types first — for example, missing title tags or meta descriptions — before moving to lower-priority items. - Check Left sidebar → OTTO SEO → Tasks to monitor the status of any Atlas Agent fix-generation jobs you have submitted. 🚫 A Note on Support Guidance There is no feature called a manual project reprocess in the platform, and no internal team action that can bulk-generate suggested fixes on your behalf. If you have been advised to wait for a reprocess, please disregard that guidance and follow the steps in this article instead to generate your fixes directly. ​ 💬 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 SEO Deploy All Button Disabled

🔍 Overview The Deploy All button in OTTO SEO will remain disabled — greyed out and unclickable — when there are no approved suggestions ready to deploy. This is the most common reason customers see the button inactive. This article explains the underlying cause and the steps to resolve it. ⚠️ Why Deploy All Stays Disabled Deploy All depends entirely on approved suggestions existing in your OTTO SEO session. If suggestions have not been generated and approved yet, the button will always be disabled regardless of your plan, pixel status, or quota. The most common causes are: - No suggestions have been generated yet — OTTO SEO has not processed your connected pages. - Suggestions exist but none are approved — Suggestions were generated, but you have not reviewed and approved them. - A reprocess was triggered but is still in progress — Generation can take a few minutes; the button will remain inactive until it completes. - The reprocess completed but returned zero suggestions — This can happen if the connected pages have no optimisation opportunities detected. ✅ Step-by-Step: How to Enable Deploy All 1. Open your OTTO SEO project from the Search Atlas dashboard. 2. Select the website or project you are working on. 3. Check whether suggestions are already listed under any of the OTTO SEO task categories. 4. If no suggestions are visible, trigger a fresh content generation and wait for the process to complete before proceeding. 5. Once generation finishes, review the suggestions that appear. 6. Approve the suggestions you want to deploy. 7. After at least one suggestion is approved, the Deploy All button will become active. Click it to push all approved suggestions to your site. 🔄 What to Do If Reprocess Returns No Suggestions If you triggered a manual reprocess and it completed but still shows no suggestions, try the following: - Confirm your pages are connected — OTTO SEO can only generate suggestions for pages that have been added to your project. Verify that your target URLs appear in the connected pages list. - Check that your project setup is complete — Some suggestion types require additional tracking or configuration to be active on your site. Confirm your project settings are fully configured. - Review your plan limits — Your current plan may affect the number or types of suggestions available. Check your account settings to confirm you have available capacity. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Why OTTO Shows Fewer Pages Than Expected

🔍 Overview When OTTO scans your website, it detects the total number of pages on your site. However, the number of pages shown inside specific issue sections — such as Title Tags, Meta Descriptions, or Heading Tags — may be lower than the total page count. This is expected behaviour, not a bug. For example, OTTO might detect 16 total pages on your site but only display 3 pages in the Title Tags section. This article explains why this happens and what you can do about it. 💡 Why the Page Counts Differ OTTO's total page count reflects every URL it discovered during the site crawl. Issue sections, however, only list pages that have a specific problem detected. Pages that already meet best-practice standards for a given element are not included in that section because they require no action. - Total pages detected: All URLs found during the crawl, regardless of their SEO health. - Pages in an issue section: Only the URLs where OTTO identified a problem with that specific element (e.g., a missing, duplicate, or too-long title tag). If 13 out of 16 pages have well-optimised title tags, only the remaining 3 pages — those with a title tag issue — will appear in the Title Tags section. This focused view is intentional so you can act on problems without sifting through pages that are already optimised. ⚙️ Common Reasons a Page May Not Appear in an Issue Section - The page already has a compliant title tag, meta description, or heading structure. - The page was excluded from a specific check because it is a tag page, archive page, or other non-primary URL type. - The page was crawled but OTTO determined it does not require optimisation for that particular element. - The crawl is still in progress and not all pages have been fully analysed yet. ✅ How to Verify Your Site Is Fully Scanned 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Open your OTTO session for the relevant website. 3. Check the total pages detected figure shown in the OTTO dashboard header. 4. Confirm the crawl status shows Complete. If a crawl is still running, wait for it to finish before reviewing issue sections. 5. Once the crawl is complete, review each issue section individually. The pages listed in each section are exclusively those needing attention for that specific issue. 🛠️ What to Do If Pages Seem to Be Missing If you believe a page should appear in an issue section but does not, follow these steps: 1. Re-crawl your site. In your OTTO session, trigger a fresh crawl to ensure the latest version of each page is analysed. New or recently updated pages may not have been included in the previous crawl. 2. Check for excluded URLs. Review whether the missing page's URL pattern has been excluded from scanning in your OTTO settings. 3. Inspect the page directly. Manually verify whether the page truly has the issue you expect. If the element is already optimised, OTTO will correctly omit it from that section. 4. Review filters. Make sure no active filters inside the issue section are hiding certain pages from view. 📊 Understanding Your True SEO Coverage To get a complete picture of all pages and their individual SEO statuses, use the Site Metrics (Site Explorer) section in the left sidebar. This area gives you broader visibility into your site's overall performance and can help you cross-reference which URLs have been crawled and how they are performing across different metrics. Remember: a lower page count in an issue section is a positive signal — it means fewer pages need fixing. Focus your effort on the pages that are listed, resolve each issue, and re-run the crawl to confirm the fixes are reflected. 💬 Still Need Help? If you have reviewed your crawl results and still believe pages are incorrectly missing from an issue section, If you need further assistance, open 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 Deployed but Changes Not Showing Live

🧭 Overview OTTO SEO marks a deployment as successful once it writes metadata changes to your project. However, if your site is built on a JavaScript framework such as React, Next.js, TanStack Router, or Lovable, the live page may still display old title tags and meta descriptions — even after clearing your browser cache and confirming there are no IP or DNS issues. This is a framework-level rendering conflict, not a crawl-blocking issue and not a problem with OTTO itself. This article explains why it happens and how to resolve it. ⚠️ Why This Happens Traditional websites serve HTML directly from the server, so OTTO's metadata changes appear immediately in the page source. Single-Page Applications (SPAs) work differently: - The browser downloads a JavaScript bundle and builds the page client-side. - Many SPA frameworks include their own metadata management libraries (for example, React Helmet, Next.js Head, TanStack Router loaders, or Lovable's built-in meta handling). - These libraries write their own title tags and meta descriptions after the page loads, which overwrites the values OTTO already deployed. - Because OTTO's changes exist in your project files but are overridden at runtime, the Search Atlas dashboard may correctly show the deployment as successful while visitors and search engines see the old metadata. Clearing your cache does not resolve this because the conflict happens in the framework's runtime logic, not in cached files. ✅ How to Confirm This Is Your Issue 1. In Search Atlas, confirm that OTTO shows the affected pages as successfully deployed. 2. Open the live page in your browser and press Ctrl+U (or Cmd+Option+U on Mac) to view the raw page source. 3. Search the source for your expected title tag or meta description text. 4. If the source shows OTTO's updated values but the rendered page (viewed normally) shows old values, your framework's metadata manager is overriding OTTO at runtime. 5. If the source itself still shows old values, OTTO's deployment may not have completed — contact support using the instructions at the bottom of this article. 🛠️ How to Fix the Conflict The resolution requires telling your SPA framework to defer to OTTO's metadata rather than managing it independently. Follow the steps below based on your stack. ⚛️ React (Create React App or custom React) 1. Locate any usage of React Helmet or React Helmet Async in your codebase. 2. Remove or comment out the <Helmet> blocks that set title and meta description on

🛠️ Fix OTTO Script Deployment Not Appearing on Website

🔍 Overview After deploying title tags, meta descriptions, and headings through OTTO SEO, you may notice the changes are confirmed in the Search Atlas dashboard but are not visible on your live website. This is almost always caused by one of a few common issues: the OTTO script is missing or incorrectly placed on your site, a caching layer is serving an older version of your pages, or the deployment has not yet fully propagated. This article walks you through each fix step by step. ⚙️ Step 1: Verify the OTTO Script Is Installed OTTO SEO relies on a JavaScript snippet added to your website to apply deployed changes. If this script is missing or placed incorrectly, no changes will appear on your live site regardless of what is deployed in the dashboard. 1. In Search Atlas, go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Locate your connected website and open its OTTO settings. 3. Copy the OTTO script snippet provided on that page. 4. On your website, open your theme or template editor and navigate to the section where you can edit the <head> tag. 5. Paste the OTTO script inside the <head> tag — either directly after <head> or just before </head>. Do not place it in the footer or body. 6. Save and publish your changes. Important: The script must be present on every page where you want OTTO deployments to take effect. If you are using a page builder or a custom theme, confirm the script is loading site-wide and not just on a single template. ✅ Step 2: Confirm the Script Is Firing Correctly After installing the script, verify it is actually loading on your live site before troubleshooting further. 1. Open your live website in a browser. 2. Right-click anywhere on the page and select Inspect (or press F12). 3. Go to the Console tab and look for any JavaScript errors related to the OTTO script. 4. Go to the Sources or Network tab and search for the OTTO script URL to confirm it is loading with a 200 status. 5. If you see errors or the script is not listed, re-check the installation in Step 1. 🗂️ Step 3: Clear All Caching Layers Even with the script correctly installed, a caching plugin, CDN, or server-side cache can serve visitors a stored version of your page that does not include the latest OTTO changes. Clear caches in this order: - WordPress / CMS cache: If you use a caching plugin such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, clear all cached files from within that plugin's settings. - CDN cache: If your site uses Cloudflare, Fastly, or another CDN, purge the cache from your CDN dashboard. - Server cache: Contact your hosting provider or clear the server-level cache from your hosting control panel if applicable. - Browser cache: In your browser, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh, bypassing the local browser cache. After clearing all caches, revisit the affected pages to check whether the deployed changes are now visible. 🔄 Step 4: Re-Deploy from the OTTO Dashboard If the script is installed correctly and caches have been cleared but changes are still not appearing, try re-triggering the deployment from Search Atlas. 1. Go to OTTO SEO in the left sidebar, then open SEO Automation. 2. Open the relevant project and navigate to the page or pages where changes are not showing. 3. Review the deployment status for each element — title tags, meta descriptions, and headings should show as Deployed. 4. If any items show a pending or failed status, select them and re-deploy. 5. Wait up to 5 minutes after re-deploying, then hard-refresh your live page to check again. ⚠️ Common Reasons Deployments Fail - Script placed in the wrong location: The OTTO script must be in the <head> tag, not the footer. - Script only on one page template: Ensure the snippet is added globally so it loads on all pages. - Conflicting scripts or plugins: Another SEO plugin (e.g., Yoast, RankMath) may be overwriting title tags and meta descriptions. Disable duplicate SEO plugins or configure them to defer to OTTO. - CSP or firewall blocking the script: A Content Security Policy header or WAF rule may be preventing the OTTO script from loading. Check your server or CDN security settings. - Page not connected to OTTO: Confirm the specific URL is listed and active inside your OTTO project. 💡 Still Not Working? If you have completed all the steps above and OTTO deployments are still not appearing on your live website, our team can review your script installation and deployment logs directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Diagnose and Fix Technical Account Issues

🔍 Overview Experiencing a technical issue in Search Atlas can be frustrating, especially when it's not clear what's causing it. This article walks you through a structured diagnostic process so you can pinpoint the problem quickly and either resolve it yourself or get targeted help from our team. ⚙️ Step 1: Identify the Exact Symptom Before troubleshooting, clearly define what is not working. Ask yourself: - What feature or page is affected? (e.g., a specific report, account settings, or a tool you rely on) - What did you expect to happen? - What actually happened? (error message, blank screen, incorrect data, slow loading) - When did it start? (after a specific action, after a certain date) Having clear answers to these questions will dramatically speed up diagnosis — both for your own troubleshooting and if you need to contact support. 🌐 Step 2: Run Basic Browser Checks Many technical issues are caused by the browser environment rather than the platform itself. Work through these checks first: 1. Hard refresh the page — Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the cached version of the page. 2. Clear your browser cache and cookies — Stale cache data is one of the most common causes of display and loading issues. 3. Disable browser extensions — Ad blockers, VPNs, and script blockers can interfere with platform functionality. Test in a clean browser session. 4. Try a different browser — Open Search Atlas in an alternative browser (Chrome, Firefox, Edge, Safari) to rule out browser-specific conflicts. 5. Try an incognito or private window — This bypasses most extensions and cached data in one step. 👤 Step 3: Check Your Account and Permissions Some issues are tied to account-level settings rather than the platform itself. - Verify your role and permissions — Check your account settings to confirm your role has access to the feature you're trying to use. - Check your subscription plan — Certain features are only available on specific plans. Review your current plan details under the top-right avatar → Billing (Plans & Top-ups tab) to ensure the feature is included. - Confirm you're in the correct workspace — If your account has multiple workspaces, make sure you're working inside the right one. 🚀 Step 4: Test the Specific Feature If the issue is with a specific tool, isolate it by navigating directly to that feature from the main menu and testing it in isolation. Note whether the problem occurs consistently or only under certain conditions (e.g., with a specific project, a particular data set, or after a certain action). 📋 Step 5: Gather Information Before Escalating If the steps above do not resolve your issue, collect the following details before reaching out to support — this will help our team investigate quickly: - Your account or workspace name - The exact feature or page affected - The exact error message, if one appears (a screenshot is ideal) - The date and time the issue first occurred - The browser and operating system you are using - Whether the issue occurs in other browsers or incognito mode If you need further assistance, open 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 Meta Descriptions and Meta Ad Studio Access

Overview This article covers two common questions in one place: why meta descriptions may not appear for an account in OTTO SEO Tasks, and how Meta Ad Studio access works — including eligibility requirements and how to check or request access. Why Meta Descriptions Are Missing in OTTO SEO Tasks If meta descriptions are not showing for an account in OTTO SEO Tasks, work through the following checks in order: 1. Confirm a task has been generated. Meta descriptions only appear after a generation run has been triggered and completed. Navigate to OTTO SEO Tasks, select the relevant project, and verify that a completed task exists before reviewing results. 2. Check that the correct project and domain are selected. Make sure the active project and domain match the account you are troubleshooting. 3. Verify meta descriptions were enabled as an output type. If meta descriptions were not selected during task setup, re-run the task and enable that output type before generating again. 4. Wait for processing to finish. Large sites may take several minutes to complete. Refresh the page and check the task status before drawing conclusions. If meta descriptions are still missing after working through all steps above, gather the following before escalating: your project name or domain, the exact task name or ID, and a screenshot showing the missing output. What Is Meta Ad Studio? Meta Ad Studio is a Search Atlas feature for creating and managing Meta advertising campaigns from within the platform. It is not available to all accounts by default — access depends on your current subscription plan and account configuration. How to Check and Enable Meta Ad Studio Access Follow these steps to determine whether Meta Ad Studio is available on your account and to request access if needed: 1. Check your current plan. Log in to Search Atlas and review which features are included on your subscription. Meta Ad Studio is a plan-dependent feature, so confirm whether it appears in your feature list. 2. Look for Meta Ads in the platform navigation. If your plan includes it, navigate to the left sidebar → Ads → Meta Ads (Which ad platform do you want to see first?). If you do not see it, your account may not yet be enabled. 3. Check any required account connections. If the feature is visible but not functioning, verify that any required external accounts are properly linked within the platform. 4. Request access if needed. If Meta Ad Studio does not appear and you believe your plan should include it, contact the support team with your account name, current plan, and a description of what you are trying to accomplish. If you need further assistance, open 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 Schema Stuck & Focus Terms Quota

🔍 Overview Two common issues can appear together in OTTO: schemas that remain in a Not Deployed state even after a successful sync, and a Focus Terms quota that appears maxed out even when you have far fewer active articles than your plan limit. This article explains why both happen and what you can do right now. ⚙️ Why Schemas Get Stuck in "Not Deployed" After OTTO completes a sync (SYNC_COMPLETE), you may still see a number of schemas listed as Not Deployed. This is caused by one of the following: - Stale validation flag: Internally, a schema record can carry an is_valid = false flag from a previous failed generation attempt. Even though the sync finished, OTTO will not push a schema to your site while that flag is present. - Silent generation failure: In some cases, schema generation fails without surfacing an error message, leaving the record in a broken state. The Not Deployed count in the dashboard may also not match the number of records actually listed — this is a known display inconsistency that has been resolved in a recent update. - Schema needs review: Some schemas are flagged as Needs Review before deployment. These must be reviewed or approved before OTTO will deploy them. 🚀 How to Resolve Stuck Schemas 1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3) and open the Schema section for the affected site. 2. Filter the schema list by Not Deployed to isolate the stuck records. 3. Check whether any schemas are also flagged as Needs Review. Open each one and approve or make the requested edits, then save. 4. Once schemas are in a valid state, trigger a new Sync using the Sync button in the OTTO dashboard. This clears stale validation flags and re-attempts deployment. 5. After the sync completes, refresh the page and confirm the Not Deployed count has decreased. If schemas remain stuck after a fresh sync, it is likely the underlying record still carries a stale flag that requires a backend fix. Please contact support using the instructions at the bottom of this article. 📊 Why Your Focus Terms Quota Shows 120/120 The Focus Terms quota counts all articles that have ever been assigned a Focus Term inside OTTO — not just articles that are currently published or active. This means: - Articles that have been moved to Trash inside Search Atlas still hold their Focus Term slot. Trashing an article does not automatically release the quota. - If you have a large number of trashed articles (for example, 231 trashed articles), those records continue to consume quota until they are permanently deleted. - This is why you may see a quota of 120/120 while only ~38 articles appear active in your workspace. 💡 How to Free Up Focus Terms Quota 1. Go to Content → Content Genius (What are we writing today?) and use Restore article to view your Deleted articles. 2. Review the deleted articles and confirm you no longer need them. 3. Permanently delete the deleted articles you want to remove. A permanent delete — not just a move to Trash — is required to release the quota. 4. Once the permanent deletion is processed, your Focus Terms quota will update to reflect the freed slots. Important: Permanently deleted articles cannot be recovered. Make sure you have exported or saved any content you may need before deleting. 🛠️ Quick Reference: Common Questions - Will a new Sync automatically fix all stuck schemas? In most cases, yes. A fresh sync clears stale flags and retriggers deployment. If schemas remain stuck, a backend correction may be needed. - Does deleting trashed articles affect my live site? No. Articles already in Trash are not published. Permanently deleting them only removes them from Search Atlas. - Can I edit schema raw JSON directly? Full raw-JSON editing (including adding and deleting schema blocks) is currently in development and will be available in a future release. - Why does the Not Deployed count not match my list? This was a known display bug. It has been resolved in a recent platform update. If you still see a mismatch, refresh the page or trigger a new sync. 💬 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 Blocked by Cloudflare

🔍 Why the OTTO Pixel Goes Missing If the OTTO pixel script is not appearing in your WordPress site's page source — even though the Search Atlas plugin is active, your API key is synced, and server-side rendering is enabled — Cloudflare's bot protection is almost certainly the cause. Cloudflare can intercept and strip scripts it identifies as bot-like activity before they ever reach your browser, making it appear as though the pixel was never injected. This is one of the most common reasons for OTTO pixel detection failures and is straightforward to resolve by adjusting your Cloudflare settings. ⚙️ How Cloudflare Blocks the OTTO Pixel Cloudflare sits between your server and your visitors. When its security rules are set too aggressively, they can: - Block or silently remove script tags injected by WordPress plugins - Challenge requests that the OTTO pixel makes during page rendering - Strip scripts flagged as potential bot traffic before the HTML reaches the browser Because the block happens at the CDN layer, the Search Atlas plugin has no way to override it — the fix must be applied inside your Cloudflare dashboard. ✅ Step-by-Step Fix: Whitelist the OTTO Pixel in Cloudflare 1. Log in to your Cloudflare dashboard at cloudflare.com and select the domain where OTTO is installed. 2. Go to Security → WAF (Web Application Firewall) in the left sidebar. 3. Check your Firewall Rules and Managed Rules for any rules that block or challenge JavaScript injection or third-party scripts. Disable or adjust rules that may target plugin-generated scripts. 4. Navigate to Security → Bots and review your Bot Fight Mode setting. If Super Bot Fight Mode or Bot Fight Mode is enabled, it may be challenging the OTTO script. Consider switching to Allow for verified bots, or create an exception. 5. Create a WAF Exception (Skip Rule) to whitelist the OTTO pixel endpoint: - Go to Security → WAF → Custom Rules and click Create rule. - Set the rule to match requests where the URI path contains the OTTO script path or originates from the Search Atlas domain. - Set the action to Skip → All remaining custom rules. - Save and deploy the rule. 6. Disable Rocket Loader for your site temporarily (under Speed → Optimization → Rocket Loader). Rocket Loader rewrites how JavaScript loads and can prevent plugin scripts from injecting correctly. Test whether the pixel appears after disabling it. 7. Clear your Cloudflare cache by going to Caching → Configuration → Purge Everything after making any changes. 🧪 How to Verify the Pixel Is Now Detected 1. Open your WordPress site in a browser and navigate to any page where OTTO is active. 2. Right-click the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) and search for otto or your Search Atlas script snippet. 4. If the script appears in the source, the pixel is now being injected successfully. 5. Return to Search Atlas by navigating to OTTO SEO → All Sites (SEO Automation) in the left sidebar (or go to /seo-automation-v3), and confirm that OTTO shows the pixel as detected. 💡 Additional Things to Check - Other security plugins: Plugins like Wordfence, Sucuri, or iThemes Security can also block script injection independently of Cloudflare. Check their settings if the issue persists after the Cloudflare fix. - Caching plugins: WP Rocket, W3 Total Cache, or LiteSpeed Cache may serve a cached version of the page that pre-dates the OTTO pixel. Purge all caches after any configuration change. - Server-side rendering confirmation: Double-check that server-side rendering is toggled on inside the Search Atlas plugin settings on your WordPress site, not just within the Search Atlas platform. - API key sync: Re-save your API key inside the plugin settings to force a fresh connection, then check the page source again. 💬 Still Seeing the Issue? If you have followed all the steps above and the OTTO pixel is still not appearing in your page source, If you need further assistance, open 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 After Crawl

🤔 Why These Two Statuses Are Independent When you check your dashboard and see that your site crawl has not run in several days and OTTO shows as not installed, it is easy to assume these are the same problem. They are not. The site crawl and the OTTO pixel installation are two completely separate systems with different triggers, verification methods, and root causes when something goes wrong. - Site crawl — Search Atlas crawls your website to collect technical SEO data such as broken links, missing meta tags, and page speed signals. Crawl status is managed inside OTTO SEO → Site Audit (Crawl Monitoring) and runs on a scheduled or manually triggered basis. - OTTO pixel — OTTO is the OTTO SEO automation layer. For OTTO to apply and monitor SEO changes on your site, a lightweight pixel (code snippet) must be installed on your website. OTTO checks independently whether that pixel is present and firing correctly. A completed crawl does not confirm that the OTTO pixel is installed. Likewise, a missing or delayed crawl does not mean OTTO is broken. You need to troubleshoot each issue separately. 📋 Step 1 — Check Your Site Crawl Status If your site has not been crawled in four or more days, follow these steps to investigate. 1. Open Search Atlas and navigate to your project's crawl or site audit area. 2. Look for the last crawl date displayed on the project overview. If the crawl is overdue, use the option available on screen to trigger a fresh crawl manually. 3. Crawls on large sites can take anywhere from a few minutes to several hours depending on the number of pages. Wait for the crawl to reach 100% before reviewing results. 4. If the crawl fails to start or gets stuck, check that your website is publicly accessible and that no firewall or bot-protection rule is blocking the Search Atlas crawler. Common reasons a crawl may be delayed or missing include a temporarily inaccessible site, a paused project, or a recently changed domain or subdomain setting inside the project configuration. ⚙️ Step 2 — Verify OTTO Pixel Installation Independently Even if your crawl completes successfully, OTTO will still show as Not Installed if the pixel has not been placed on your site or is not firing correctly. Follow these steps to verify the pixel separately. 1. Open your project inside Search Atlas and locate the OTTO setup or installation area. 2. Find and copy the OTTO pixel code snippet displayed for your project. 3. Paste the snippet into the <head> section of every page on your website. You can do this through your CMS theme files, a tag manager such as Google Tag Manager, or by asking your developer to add it directly to your site template. 4. Once the snippet is in place, return to Search Atlas and use the pix If you need further assistance, open 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 <head> 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 'offers': Null Error in OTTO Product Schema

When OTTO auto-generates a Product schema and cannot extract pricing or availability data from your page, it may leave the offers field empty or null. This causes the schema to be flagged as invalid and prevents your page from qualifying for Google Product rich results. This article explains why it happens and how to fix it manually. 📋 Why This Happens OTTO builds Product schema by crawling your page at the time of generation. If your product page does not display price and availability in a format OTTO can read during that crawl, the offers property is left null and the schema fails validation. Regenerating the schema without first updating your page content will reproduce the same null result — it is not a bug that resolves itself on retry. Important: Google requires the offers property for Product pages to qualify for rich results in search. A Product schema without valid offers data will not unlock enhanced listings, even if the rest of the schema is correct. 🔧 How to Fix It 1. In your Search Atlas dashboard, go to Left sidebar → OTTO SEO → All Sites → [your project] → Overview → Onpage Optimizations (OTTO Grader) and navigate to Schema Markup. 2. Find the page showing an invalid schema status. It will be marked with a red or error indicator. 3. Open the schema to enter the editor. 4. Choose the fix that matches your page: - Page has no pricing data: Remove the offers property from the schema entirely. This clears the validation error. Note that the page will not qualify for Product rich results without it. - Page does have pricing data: Populate the offers field manually. At minimum, include price, priceCurrency, and availability — the three properties required by schema.org for a valid Offer. 5. Save your changes and deploy the schema. ⚠️ Known Limitations - OTTO cannot auto-populate offers if pricing data is not visible and machine-readable on the live crawled page. Manual entry is the only resolution in that case. - If price or availability changes on your page after the schema is deployed, you will need to update the schema manually to keep it accurate. 💬 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.

🔍 Why OTTO Schema Isn't Showing in External Validators

🎯 Overview A common question we hear is: my OTTO plugin shows as connected and the schema shows as deployed, so why isn't it appearing in Google Rich Results Test, schema validators, or search results? This article walks through the most frequent causes and how to resolve them so your structured data is served and recognized correctly. ⏱️ Give It Time to Crawl and Cache OTTO deploying schema is not the same as Google indexing it. Even when a validator can read the markup instantly, search results and rich results require Google to re-crawl the page. Keep these timelines in mind: - Validators (Rich Results Test, Schema.org validator): Should reflect changes within minutes to a few hours after deployment. - Google Search rich results: Can take days to weeks after Google re-crawls the page. - CDN or caching plugins: May serve a cached version of the page without the injected schema until the cache clears. If a validator does not show your schema after a few hours, continue with the checks below. ✅ Confirm the Page Is Crawlable OTTO schema will not be recognized if the target URL cannot be crawled by search engines. We previously fixed an issue where schema was being deployed on pages that were not crawled. Verify the following for the exact URL you are testing: - The page returns a 200 status (not a redirect, 404, or 500). - The URL is not blocked in robots.txt. - The page does not carry a noindex meta tag or header. - You are validating the exact same URL that OTTO deployed to — including trailing slashes, http vs https, and www vs non-www variations. 🔗 Test the Correct URL Variation Schema is deployed on a specific URL. If your site redirects between www and non-www, or between http and https, validators may test a version of the page that OTTO did not inject into. Always run the validator against the canonical, final URL that resolves in your browser after any redirects. ⚠️ Check for Validation Errors and Warnings OTTO validates schema before deployment. In some cases schema may deploy with warnings, and certain errors can prevent Google from recognizing it as valid structured data. Watch for these known issues: - @context must use HTTPS: If the schema context reads http:// instead of https://, validators may reject it. Ensure your context is set to the secure schema.org URL. Note that this error can also appear in nested schema properties and may not always be caught before deployment — if validators flag an @context HTTPS error even after re-deploying, inspect all nested schema objects for http:// references. - Bypassed validation warnings: OTTO allows you to bypass validation and deploy anyway with a warning. If you used this option, the deployed schema may contain errors that external validators flag. If you bypassed a validation warning during deployment, re-review the schema and correct the underlying issue before re-deploying. 🧹 Rule Out Duplicate or Stale Schema If schema continues to appear even after you remove an OTTO deployment — or the wrong schema shows up — another source may be serving structured data on the same page. Common sources include: - A separate SEO or schema plugin injecting its own markup. - Your WordPress theme adding built-in schema. - A previously cached version of the page still being served. Conflicting or duplicate schema can cause validators to display unexpected results. Disable other schema sources temporarily to isolate what OTTO is serving. Note for WordPress users: A known issue exists where schemas continue to be served on a page even after the OTTO schema deployment has been removed. If you are seeing schema in validators that you have already deleted in OTTO, check whether another plugin or theme is the source, and also clear all caches before concluding OTTO is still injecting it. This issue has been addressed in a recent release (WP-541). 🔄 Re-Deploy and Clear Caches Once you have confirmed the page is crawlable and free of validation errors, refresh your deployment: 1. Confirm the OTTO plugin still shows as connected. 2. Re-deploy the schema to the target URL. 3. Clear your WordPress cache and any CDN cache. 4. Load the live page and view the source to confirm the JSON-LD markup is present. 5. Run the URL through the Rich Results Test and a schema validator again. If the markup is present in the page source but a validator still does not detect it, the issue is almost always a caching layer or a URL mismatch — recheck those first. 💬 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 Suggested Fixes Blank After Audit

🧐 Why Suggested Fixes Appear Blank After a recrawl, OTTO does not populate all suggested fixes at once — it analyses pages progressively as the crawl processes your site. If you open the audit results while the crawl is still running, or immediately after it finishes, you will typically see a small number of populated fixes alongside a large number of blank rows. This is expected behaviour, not a bug. Additional causes for blank suggested fixes include: - Crawl still in progress: Fixes are generated as each page is processed. Blank rows simply mean those pages have not been analysed yet. - Crawl interrupted or incomplete: A timeout, crawl-credit limit, or connectivity issue can stop the crawl early, leaving unvisited pages without recommendations. - Pages excluded from the crawl: Pages that are noindexed, blocked by robots.txt, or manually excluded will not receive suggested fixes. - Stale audit view: The results panel sometimes does not refresh automatically after a crawl completes, causing the display to appear out of sync. 🛠️ Step-by-Step: Get Your Fixes to Populate 1. Verify the crawl has fully completed. Go to Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring. A spinning indicator or a Crawling status means analysis is still running — wait until the status changes to Completed before reviewing results. 2. Refresh the overview page. Once the crawl shows Completed, navigate to Left sidebar → OTTO SEO → All Sites, open your project card, then go to Left sidebar → OTTO SEO → Overview. Press Ctrl + R (Windows) or Cmd + R (Mac) to force the latest fix data to load. 3. Review pending tasks. Visit Left sidebar → OTTO SEO → All Sites (SEO Automation) → select your site → Overview (OTTO Grader) and check the Pending Optimizations section for any queued or stuck OTTO action items. Resolving or dismissing stale tasks can unblock the fix generation process. 4. Inspect individual pages. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer and click a page that shows a blank fix. If the page status reads Not Crawled or Excluded, that page was skipped during the audit and will not receive suggestions until it is included in a future crawl. Check your crawl settings to ensure the page is not inadvertently excluded. 5. Trigger a fresh recrawl. If fixes remain blank after completing the steps above, start a new crawl from Left sidebar → OTTO SEO → All Sites by opening your project card and selecting the recrawl option. Allow the crawl to finish completely before reviewing suggested fixes. ⏳ How Long Should You Wait? OTTO populates fixes progressively throughout the crawl. For small sites (under 100 pages), recommendations typically appear within a few minutes of the crawl completing. Larger sites with hundreds or thousands of pages may take noticeably longer. Always confirm the Completed status in Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring before concluding that fixes are missing. Important: Avoid launching a second recrawl while one is already in progress. Overlapping crawls can produce incomplete or inconsistent fix data. ✅ Quick Checklist Before Contacting Support - Crawl status shows Completed in Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring - Browser has been refreshed after the crawl finished - No pending or stuck tasks in the Pending Optimizations section under Left sidebar → OTTO SEO → All Sites (SEO Automation) → select your site → Overview (OTTO Grader) - Affected pages are not marked Excluded or Not Crawled in Left sidebar → OTTO SEO → Site Audit → Page Explorer - Sufficient time has passed for OTTO to process all crawled pages If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚠️ Fixing the "Quota Exhausted" Error When Adding OTTO Sites

📋 Overview Some users see a "quota exhausted" error when trying to add a new OTTO SEO site, even though they believe they still have available site slots. In most cases, this happens because adding OTTO to a brand-new domain requires both a free OTTO site slot and a free Site Auditor project slot for that domain, since OTTO requires a Site Audit project for the same domain, and if one does not already exist, it is created automatically before the OTTO project. OTTO site slots and Site Auditor project slots are two separate quotas, each with its own limit. This article explains why this occurs and walks you through resolving it. 🔍 Why This Happens Your subscription includes a defined number of OTTO site slots and a separate number of Site Auditor project slots. These are tracked independently, but OTTO requires a Site Audit project for the same domain (one is created automatically first if it does not already exist), which means: - Each OTTO SEO site you add consumes one OTTO site slot. - Adding OTTO to a brand-new domain also creates a Site Auditor project for that domain automatically first, which uses one Site Auditor project slot. - If the domain already has a Site Auditor project, only an OTTO site slot is used (OTTO does not create a second Site Auditor project). - Sites created during trials, testing, or by other team members still count toward your totals. As a result, you may have hit either your OTTO site limit or your Site Auditor project limit for the domain you are trying to add. OTTO top-ups add OTTO site slots only. ✅ How to Check Your Current Usage Before adding a new site, confirm how your existing slots are being used: 1. Log in to your Search Atlas account. 2. Open OTTO SEO → All Sites (SEO Automation) and review the list of active sites. 3. Navigate to OTTO SEO → Site Audit → All Audits and review the list of existing projects. 4. Compare your OTTO site usage against your OTTO site limit, and your Site Auditor project usage against your Site Auditor project limit. 5. Check your subscription details to confirm both allowances. If either quota has reached its limit for what you are trying to add, that is the cause of the quota exhausted error. 🐞 Still Seeing the Error When Slots Appear Available? In some cases the error appears even though your dashboard or billing shows an open slot. This usually points to a quota count that is temporarily out of sync rather than a genuinely full account: - Quota count not fully loaded: On the first load of an account, the Site Audit quota can briefly display as 0/N before your real usage populates. This is a known display issue that has been addressed: refresh the page so the accurate count loads before you try to add a site. The displayed total typically corrects itself after a reload, and it has also been observed to update once you complete an add or delete action. - Enforcement vs. billing mismatch: There was a known issue where quota enforcement blocked adding a new site even though billing showed an available slot (for example, blocking an additional site while one slot still appeared free). This has been resolved, but if you still encounter it, reload the page and retry adding the site. If both your OTTO site usage and your Site Auditor project usage are clearly below their respective limits and the error persists after refreshing, reach out to support so the team can verify your account's quota. 🧹 How to Free Up Quota To make room for a new OTTO site, you can remove sites or projects you no longer need: - Remove unused Site Auditor projects: Open the Site Auditor, identify projects that are no longer active, and delete them to release their slots. - Remove inactive OTTO sites: In the OTTO SEO section, delete any sites you are no longer managing. - Audit duplicate entries: Look for duplicate or test sites that may have been added during setup and remove them. After removing the unneeded sites or projects, return to OTTO and try adding your new site again. The slot should now be available. ⬆️ When to Upgrade Your Plan If all of your current OTTO sites and Site Auditor projects are active and necessary, you have simply reached the limit of your plan. In that case, the best option is to upgrade to a plan with a higher site allowance. To do this: 1. Go to your subscription or billing settings. 2. Review the available plans and their site limits. 3. Select a plan that provides enough OTTO site slots and Site Auditor project slots for your needs. 4. Confirm the upgrade and return to OTTO to add your new site. 💡 Tips to Avoid This in the Future - Periodically review both your OTTO sites and Site Auditor projects to keep usage clean. - Remove test or trial sites as soon as they are no longer needed. - Coordinate with your team so multiple members do not unknowingly consume shared slots. - Plan your site allowance with both tools in mind when choosing a subscription. 💬 Need More Help? If you need further assistance, click the chat icon in the bottom-right corner of the platform to start a live chat with a member of our team.

🛠️ Revert Not Updating in Real Time for ZIP and HTML Projects in Website Studio

If you click Revert on a ZIP- or HTML-imported Website Studio project and the preview still shows your AI changes, the revert did work — refresh your browser or switch pages to see the original version. A fix is rolling out now. 🔍 What's Happening in Website Studio After you apply AI modifications to a Website Studio project that was imported through ZIP upload or HTML upload, clicking Revert does not refresh the editor preview in real time. The page looks unchanged, so it can appear the revert failed. The revert actually succeeds on the backend. The original page state is restored — only the live preview display lags behind. Who is affected - Customers using Website Studio projects created via ZIP upload or HTML upload. - Anyone clicking Revert after applying AI modifications to those projects. Projects created through other import methods are not impacted by this display issue. 🛠️ Workaround to See the Reverted Page Use these steps to display the restored original version right away: 1. Click Revert on your ZIP- or HTML-imported project as usual. 2. Refresh your browser, or navigate to another page in the editor and then back to this one. 3. View the page — the reverted (original) state now displays correctly. You'll see your page restored to its original version, confirming the revert applied successfully. 📡 Engineering Status for This Issue Our team is aware of this display behavior and has addressed it. The fix is currently rolling out, after which the editor preview will update in real time when you click Revert. No action is needed on your part to receive the fix. 📞 When to Contact Support The revert is applied on the backend even when the preview looks unchanged, so the refresh workaround resolves the display in nearly all cases. Contact Search Atlas Support if: - You refresh the browser or switch pages and the original version still does not appear. - Your reverted content shows incorrect or missing elements after refreshing. Share your project name and import method (ZIP or HTML) so the team can review your case quickly. 🎯 Your revert is safe — the team has the fix in motion, and a quick refresh shows your original page restored in the meantime.

🛠️ Fix OTTO Stale Organization JSON-LD on Pages

🔍 Overview In some cases, OTTO may inject an Organization JSON-LD schema node containing outdated information — such as an old phone number or a previous business name — into your homepage or other pages. This can be confusing because the outdated schema does not appear in Domain-Level Schema or Page-Level Schemas inside the Search Atlas dashboard, making it difficult to locate and remove. This article explains why this happens and walks you through how to resolve it. ⚙️ Why This Happens When OTTO first analyzes your site, it may detect an existing Organization schema and store certain display fields internally. Under specific conditions, OTTO can re-inject this cached schema data into your page's Custom HTML (also referred to as header_html_insertion) even after the original schema has been updated or removed elsewhere. Because the stored data bypasses the standard Domain-Level and Page-Level Schema panels, it remains invisible in the dashboard — making it appear as though OTTO is injecting schema from nowhere. A platform-level fix has been deployed that strips the outdated cached fields to stop this from happening going forward. However, if your site was affected before the fix, you may still need to manually clear the stale schema using the steps below. 🚀 How to Remove the Stale Organization Schema 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select your website and open the OTTO dashboard for the affected domain. 3. Go to the Active tab within OTTO SEO → All Sites (SEO Automation) and review any active schema deployments listed there. 4. Look for any Organization schema entries that are active. If you find one containing outdated details, click it to open the editor and either update the information or deactivate/remove the deployment. 5. Next, check the Custom HTML or header injection settings. If your platform exposes an area for custom header code, search for any <script type="application/ld+json"> blocks containing Organization data and delete them. 6. If you manage a WordPress site, log in to your WordPress admin panel and navigate to Plugins. Confirm the Search Atlas / OTTO plugin is up to date, as older plugin versions may continue serving cached schema even after dashboard changes. 7. After making changes, use a tool such as Google's Rich Results Test or Schema Markup Validator to verify the outdated Organization JSON-LD no longer appears on your page. ✅ How to Verify the Fix - Paste your homepage URL into Google's Rich Results Test (search.google.com/test/rich-results) and confirm the Organization schema now shows the correct business name, phone number, and other details. - Use your browser's View Page Source feature and search for application/ld+json to check that no outdated Organization block remains in the raw HTML. - If the stale schema still appears after following all steps, the data may be cached at the server or CDN level — try clearing your site cache and re-testing. 🛡️ How to Prevent This in the Future - Keep business information current in OTTO. Update your Organization details in the OTTO dashboard whenever your phone number, business name, or address changes. - Avoid adding Organization JSON-LD in multiple places. Do not add Organization schema both through OTTO and through a separate plugin or theme option, as duplicate entries can cause conflicts. - Keep the Search Atlas plugin updated. Platform fixes — including the schema caching fix — are delivered through plugin and dashboard updates. - Review Domain-Level Schema after major site changes. Any time you rebrand or update contact information, audit your active schema deployments in OTTO to ensure everything is current. 💬 Need More Help? If you have followed the steps above and the stale Organization JSON-LD is still appearing on your site, our team can investigate 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 billing_not_active Error in Image Alt Text

🔍 What Is This Error? When you try to generate image alt texts using AI — either in bulk or one at a time through OTTO or the Site Audit — you may see a billing_not_active error. This can happen even if your subscription is active and you have remaining AI quota. The error is caused by a billing date sync issue on the platform side, not by anything you have done wrong. ⚙️ How to Fix It 1. Refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh and clear any cached session data. 2. Sign out and sign back in. Log out of Search Atlas completely, then log back in. This forces the platform to re-verify your billing status and often resolves the error immediately. 3. Retry the alt text generation. Navigate back to the image alt text feature — either through OTTO or the Site Audit — and try generating alt texts again. 4. Wait a few minutes if the error persists. In some cases, the billing sync takes a short time to update. Wait 3–5 minutes, then try again. 📍 Where to Find Image Alt Text Generation You can access AI image alt text generation in two places inside Search Atlas: - OTTO: Open your OTTO dashboard, go to the Image Optimization section, and use the bulk or individual alt text generation option. - Site Audit: Navigate to your site audit report, find the Image issues section, and trigger alt text generation from there. 🚫 Known Causes to Rule Out Before contacting support, confirm the following are not contributing to the issue: - Billing date mismatch: If your billing renewal date recently passed, there may be a brief window where the system incorrectly flags your account. Signing out and back in usually resolves this. - Image blocked by CDN: Some images hosted behind a content delivery network (CDN) cannot be accessed by Search Atlas for alt text generation. If a specific image consistently fails, its CDN settings may be blocking the request. This is separate from the billing error. - Unexpected errors on individual images: If only one or two images fail while others succeed, the issue is likely with those specific images rather than your billing status. ✅ After the Fix Once you have signed back in and the billing status is correctly recognised, your AI image alt text generation should work normally. Your existing AI quota is not affected by this error — any failed generation attempts do not consume your credits. 💬 Still Seeing the Error? If the steps above do not resolve the issue, our team can investigate your account billing status 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 Sync to CMS Not Updating Your CMS

🔍 Overview Some users have reported that the Sync to CMS toggle returns a Something went wrong error, and OTTO SEO optimizations — such as alt text changes or meta title updates — do not appear on their WordPress site even after reinstalling the plugin or re-authenticating their connection. This article explains the known cause, what you can check on your end, and how to get this resolved quickly if the issue persists. ⚙️ What Causes This Issue This behaviour has been traced to a software bug on the Search Atlas side that can prevent the Sync to CMS feature from pushing OTTO optimizations to WordPress correctly. The bug affects the sync process itself — not your WordPress plugin installation or authentication credentials. In confirmed cases, the engineering team identified and deployed a fix that fully resolved the problem. Because this is a platform-side issue, there are no local troubleshooting steps that will repair it on their own. However, there are a few things worth verifying before escalating, to rule out common configuration gaps. ✅ What to Check First Before contacting support, run through the following checks to confirm your setup is correct: 1. SearchAtlas WordPress plugin (MetaSync) is installed and active: Sync to CMS is available exclusively for websites connected through the SearchAtlas WordPress plugin (MetaSync). If your site uses the Cloudflare or Pixel installation method, the Sync to CMS option will not appear in your project. Confirm the plugin is installed and active on your site. 2. Your project is connected via the WordPress plugin: Sync to CMS only applies to WordPress plugin projects. If your project is not connected through the SearchAtlas WordPress plugin, the sync cannot proceed. 3. Re-authenticate if prompted: If your WordPress connection was recently changed or expired, re-authenticate the connection from within your project settings. A successful re-authentication should be confirmed before testing the sync again. 4. Test the sync again after re-authentication: After confirming the above, attempt to use the Sync to CMS toggle again. If the error persists, the issue is likely on the platform side. ⚠️ Important Limitations to Know The Sync to CMS feature has several built-in limitations that are worth keeping in mind: - WordPress plugin projects only: Sync to CMS is available only for websites connected through the SearchAtlas WordPress plugin (MetaSync). Sites using the Cloudflare or Pixel installation method do not have access to this feature. - Heading changes and Link corrections do not sync: Heading changes and Link corrections (Issues with Links) are not synced. These optimizations modify the page body content, which SEO plugins such as Yoast SEO, Rank Math, and AIOSEO do not provide equivalent fields for — so there is nothing to synchronize. - Heading and Link changes are editor-dependent: These content changes are supported only on posts and pages using the Gutenberg or Classic Editor. They are intentionally skipped on page builders such as Elementor, Divi, WPBakery, Beaver Builder, Oxygen, and Brizy, because those builders store content outside the standard WordPress post body. - All other optimization types sync regardless of editor: Meta title, meta description, focus keyword/keyphrase, Open Graph title and description, Twitter title and description, schema/structured data, canonical URL, and image alt text all sync regardless of which editor or page builder is used. Image alt text updates are written to the WordPress Media Library. 🛠️ If the Error Persists If you have confirmed your SearchAtlas WordPress plugin is active, your project is properly connected via the WordPress plugin, and the Something went wrong error still appears after attempting to sync, this indicates a platform-side issue that requires the engineering team to investigate. This type of issue cannot be resolved through self-service steps alone. In confirmed cases, our team has been able to identify the root cause, deploy a targeted fix, and fully restore sync functionality for the affected project. To get this escalated quickly, contact our support team directly so they can log the issue and engage the relevant engineers on your behalf. 💬 Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When reaching out, it helps to include the following details to speed up the investigation: - The domain or project name affected - The exact error message you are seeing - Whether re-authentication was attempted and whether it completed successfully - Which specific OTTO optimizations are not syncing (e.g. alt text, meta descriptions)

⚠️ "Add a page" Modal Not Translating on Filter by URL Page

We're aware that the 'Add a page' modal in Semantic Analysis and KBT (Knowledge Base Tool) tabs displays in English rather than your selected language (French and Spanish) on the Filter by URL page. As a temporary workaround, you can switch your project language to English to complete this task. We're working to resolve this localization issue. 📍 What's Happening When you open the 'Add a page' modal in the Semantic Analysis or KBT tabs on the Filter by URL page, the modal text appears in English regardless of your project language setting. This affects users working in French and Spanish. The rest of the Search Atlas interface displays correctly in your selected language—only this specific modal is unaffected. 🛠️ Workaround Steps Follow these steps to use the 'Add a page' modal while we fix the localization: 1. Go to your project settings. (Project settings are accessible regardless of your selected interface language.) 2. Change your project language to English. 3. Navigate back to the Filter by URL page. 4. Open the Semantic Analysis or KBT tab. 5. Click 'Add a page' and complete your task. 6. Return to project settings and switch your language back to your preferred language (French or Spanish). Your project data and settings remain unchanged during this process. ⏳ Engineering Status Our team is aware of this translation issue and investigating a permanent fix. We're prioritizing this localization problem to ensure the modal displays correctly in all supported languages. 🆘 When to Contact Support If the workaround doesn't resolve your issue, or if you encounter English text in other areas of Search Atlas, please contact support. We're here to help—we're committed to fixing this localization issue quickly. 🎯 You now understand the scope of this translation issue and can use the workaround to complete your task. For additional help or if you encounter related localization problems, reach out to our support team.

Fix OTTO Overriding WordPress Blog noindex

🔍 What Is Happening? If your WordPress Posts page (commonly /blog/) is showing a noindex, nofollow robots meta tag in the browser source even though every Yoast SEO setting and per-page setting is explicitly set to index, the cause is almost always OTTO's deployed robots meta tag. OTTO can inject its own robots meta tag directly onto your pages as part of a deployment. This tag is written at the platform level and takes precedence over WordPress and Yoast settings. No amount of adjusting Yoast or your theme will remove it — the override must be resolved inside Search Atlas. ⚠️ Why This Happens When you run an OTTO deployment that includes a robots meta directive, OTTO pushes that instruction to your connected WordPress site. This is intentional behaviour — it allows OTTO to manage crawlability at scale. However, it can create a conflict if: - An earlier OTTO deployment set the Posts page to noindex, nofollow and the setting was never reversed. - A bulk robots meta deployment targeted archive or listing pages and included your Posts page unintentionally. - You updated Yoast after the OTTO deployment, so Yoast now says index but OTTO's previously deployed tag still takes precedence on the live page. In all these cases, your page will remain noindex until you explicitly update or remove the OTTO-deployed tag. 🛠️ How to Check the OTTO-Deployed Robots Tag 1. Log in to Search Atlas and open the relevant project. 2. Navigate to OTTO SEO → All Sites (SEO Automation) for that project. 3. Review any deployed actions related to robots meta, noindex, or crawlability settings. 4. Identify whether a noindex, nofollow directive was deployed to your Posts page URL (e.g. /blog/). ✅ How to Fix the Conflict 1. Inside Search Atlas, locate the OTTO-deployed robots meta action affecting your Posts page. 2. Update the robots directive for that page to index, follow, or remove the deployed tag entirely if you prefer Yoast to manage it going forward. 3. Re-deploy the updated action so OTTO pushes the corrected tag to your WordPress site. 4. Once deployed, view the page source in your browser (Ctrl + U or Cmd + U) and confirm the robots meta tag now reads index, follow. 5. Clear any WordPress, server-side, or CDN cache so search engines receive the updated tag immediately. After these steps, Yoast and OTTO will be in agreement and your Posts page will be crawlable and indexable again. 🔎 How to Verify the Fix Is Live - Browser source check: Search the page source for robots and confirm the meta tag reads index, follow. - Cache cleared: Ensure all caching layers have been purged so the updated tag is served to crawlers. If you have reviewed OTTO's deployed actions and cannot identify the source of the noindex tag, or if the tag persists after re-deploying, please reach out to our support team via the chat icon in Search Atlas so we can investigate further.

🛠️ Brand Vault Stuck in "Analyzing" State: Causes, Troubleshooting, and Resolution

If Brand Vault has been stuck in the "Analyzing" state for more than 2 hours, a background process has stalled. Follow the steps below to identify the cause, clear the issue yourself, or escalate to support with the right details ready. ⚠️ Normal vs. Stuck: When to Take Action A brief "Analyzing" status — typically under 30 minutes — is expected when Brand Vault first processes your brand data. Take action if any of the following apply: - The status has not changed after 2 or more hours - Brand Vault has shown "Analyzing" for multiple days - The status persists after closing and reopening your browser 🔍 Common Causes of a Frozen Brand Vault Analysis Several conditions can cause Brand Vault to stall in the "Analyzing" state: - Large or complex brand dataset: Accounts with a high volume of brand assets or tracked domains can exceed normal processing time. - Silent backend failure: A server-side task may have failed without resetting the status display, leaving it permanently stuck. - Interrupted connection during setup: A network disruption during the initial analysis can leave the process in a partial state. - Browser session conflict: Having Search Atlas open in multiple tabs or browsers can interfere with real-time status updates. 🛠️ How to Troubleshoot Brand Vault Stuck in Analyzing Work through these steps in order. Stop as soon as the "Analyzing" status clears and Brand Vault loads correctly. 1. Wait at least 2 hours if you recently initiated the analysis. Processing time scales with your brand's data volume — large accounts take longer. 2. Hard-refresh the page. Press Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac) to force the browser to reload the latest status directly from the server. 3. Close all other Search Atlas tabs. Reduce your session to a single tab, then navigate back to Brand Vault. 4. Clear your browser cache and reload the page. A stale cache can display an outdated "Analyzing" label even after processing has finished. 5. Log out and log back in. Go to your Avatar Menu (👤), select Log Out, sign back in, then navigate to Brand Vault. 6. Open Brand Vault in a different browser or an incognito window to rule out a browser-specific issue. If Brand Vault loads correctly after any of these steps, your analysis has completed successfully. 📞 When and How to Contact Search Atlas Support If Brand Vault is still stuck after completing all troubleshooting steps — especially if it has been in the "Analyzing" state for more than 5 hours or across multiple days — contact the Search Atlas support team. Include the following details to speed up resolution: - Your account email address and workspace name - The date and approximate time the analysis started - A screenshot showing the "Analyzing" status - The browser and operating system you are using - Whether the issue appears in multiple browsers or on different devices The support team can inspect the backend processing task, reset the analysis pipeline, and confirm when Brand Vault is fully operational for your account. 🎯 You now know the most likely causes of a frozen Brand Vault analysis and the exact steps to clear it. If troubleshooting does not resolve the status, contact Search Atlas support with the details above so the team can reset the analysis process directly on the backend.

🔍 Site Explorer Showing No Data for Your Site

🧭 Overview If you open Site Explorer and see zeros, blank charts, or missing keyword and traffic data for your domain, you are not alone. This is a known behaviour that most commonly affects low-traffic, newer, or niche domains. This article explains why it happens and walks you through the steps to get your data populating correctly. ❓ Why Does This Happen? Site Explorer pulls data from Search Atlas's proprietary index. For a domain to display populated metrics, that domain must have enough crawl history and search visibility for our systems to have indexed it. The most common reasons data appears empty include: - Low organic traffic: Sites with very few monthly visitors may fall below the threshold required for our index to surface detailed keyword and traffic data. - New or recently launched domains: Domains that are new to the web or recently rebranded may not yet have sufficient crawl data available. - Regional or niche domains: Sites that target a narrow geographic market or highly specific niche may have limited data in our global index. - Data processing delay: New domain lookups can take two or more minutes to load as our system fetches and processes data in real time. - Cache or sync lag: Occasionally, a domain's overview panel may display zeros while the Keywords tab already shows data. This is a display sync issue that resolves automatically. 🛠️ Steps to Troubleshoot 1. Wait and refresh: If you just entered a domain for the first time, wait at least two to three minutes, then refresh the page. Real-time lookups for obscure or low-traffic domains take longer to process. 2. Check the Keywords tab directly: Navigate to Left sidebar → Site Metrics and open your domain's report. Click the Keywords tab. If keywords appear there but the Overview shows zeros, this is a known display sync issue and the data will reconcile shortly. 3. Verify the domain format: Make sure you have entered the domain without a trailing slash and in the correct format (for example, shop.valvolineglobal.com rather than https://shop.valvolineglobal.com/). Subdomain and root domain results are indexed separately. 4. Try the root domain: If you searched a subdomain and see no data, try searching the root domain (for example, valvolineglobal.com) to see if data is available at that level instead. 5. Check back after 24–48 hours: For genuinely low-traffic or new sites, our index refreshes periodically. Data that is not available today may appear after the next crawl cycle. 📊 What to Expect for Low-Traffic Sites Search Atlas Site Explorer is powered by a large-scale organic search index. Sites that receive fewer than a few hundred monthly organic visits may show limited or no keyword data. This does not mean the tool is broken — it reflects what is available in our index for that domain at that time. As the site grows its organic presence, more data will become available automatically. The metrics most likely to appear first for smaller sites are backlinks and referring domains, since those are indexed differently from keyword and traffic data. If you need backlink data specifically, check More Features → Backlinks → Backlink Research. ⚠️ Known Display Issues Our engineering team has identified and resolved several related display bugs, including: - Overview showing 0 organic keywords while the Keywords tab shows thousands of results. - Project cards showing zero backlinks even when backlink data exists inside the report. - Historical data appearing to stop at a specific date due to a domain history sync delay. - Shareable links not displaying metrics for certain domains. If you experience any of these symptoms, a page refresh or waiting a short period usually resolves the display. Underlying data is not lost. 💬 Still Seeing No Data? If you have followed all the steps above and your domain still shows no data after 48 hours, our support team can investigate whether a manual data refresh or cache clear is needed for your specific domain. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Pixel Not Detected on Shopify

🔍 Understanding the Problem You have added the OTTO pixel script to your Shopify store, and when you inspect the page the code is clearly there. Yet the OTTO scan still reports that the pixel is not detected. This is one of the most common Shopify installation issues, and in almost every case the pixel itself is fine. The real cause is usually bot-blocking. Shopify and many security or firewall services automatically block traffic that looks automated. Because the OTTO detection scan uses an automated crawler to visit your site, that crawler can be blocked before it ever reaches your page. When the crawler is blocked, it cannot see the pixel, so the scan reports it as missing even though the code is installed correctly. ✅ Confirm the Pixel Is Installed Correctly Before changing any settings, quickly confirm the installation is valid: 1. Open your live Shopify store in a browser. 2. Right-click the page and choose View Page Source. 3. Use your browser's find function (Ctrl+F or Cmd+F) to search for your OTTO pixel or the OTTO script identifier. 4. Confirm the script appears in the source of your published theme, not just the theme editor preview. If the script appears in the live page source, your installation is correct and the detection issue is almost certainly caused by bot-blocking. 🚫 Why Bot-Blocking Causes False Results Automated protection can come from several places on a Shopify store: - Shopify's built-in bot protection, which filters suspicious or automated visits. - Third-party firewalls or security apps installed from the Shopify App Store. - Content delivery or proxy services such as Cloudflare and other CDNs, or bot-management and DDoS-protection tools. Cloudflare in particular can serve a challenge or error page to our crawler even when your pixel or UUID was deployed successfully, so the scan never sees the installed code. - Password-protected or unpublished stores that block all outside visitors, including crawlers. Any of these can return an error page or an empty response to our crawler instead of your real page. The scan then sees no pixel and marks it as not detected. 🔧 How to Resolve It Work through these steps to allow the OTTO crawler to reach your site: 1. Remove the store password. In Shopify, go to Online Store, then Preferences, and make sure the password page is disabled so the store is publicly accessible. 2. Review security and firewall apps. Temporarily disable or adjust any bot-protection, firewall, or rate-limiting apps and then run the scan again. 3. Whitelist the OTTO crawler. If your security tool supports allow-lists, add an exception so automated requests from our crawler are not blocked. If you use Cloudflare, make sure the crawler is not caught by a firewall rule or bot-fight challenge. Our team can provide the crawler details you need through live chat. 4. Check for aggressive rate limiting. Some tools block repeated visits from the same source. Loosen these limits so the scan can complete. 5. Re-run the OTTO scan. After making changes, trigger a fresh scan rather than waiting for the next automatic check. ⏱️ What to Expect After Making Changes Detection is not always instant. Once bot-blocking is removed and a new scan runs successfully, allow some time for the results to update. If the pixel is now reachable, the status will change to detected on the next completed crawl. If you installed the pixel through Google Tag Manager, detection can take roughly 10–15 minutes to register after a successful scan. Keep in mind that detection can only succeed if the crawler can load your published page exactly as a normal visitor would. If the page still returns a security challenge, error page, or password prompt, the scan will continue to report the pixel as missing. 💡 Quick Checklist - The pixel appears in the live page source. - The store is published and not password-protected. - No firewall, bot-protection, or security app (including Cloudflare) is blocking automated visits. - Rate limits are not blocking repeated crawler requests. - A fresh scan has been run after making changes. Additional Notes our engineering team is actively improving pixel-detection reliability across Shopify and other CMS platforms

🔧 Troubleshooting OTTO Schema Update Errors

📋 Overview When updating a schema for a page in OTTO SEO automation, you may encounter errors that prevent you from saving or modifying your schema configuration. This article helps you identify whether you have an update error (during creation or modification) or a deployment error (during publishing), so you can troubleshoot the right issue. 🎯 What is a Schema Update Error? A schema update error occurs before you publish. It prevents you from saving changes to your schema configuration. Common causes include invalid field values, missing required fields, permission restrictions, or API rejections during modification. The schema is stuck in draft or editing mode and cannot be saved. 🎯 What is a Schema Deployment Error? A schema deployment error occurs during or after publishing. Your schema saves correctly, but fails to go live on your page. Common causes include a disconnected OTTO pixel, network timeouts, or pending approval states. If your schema saves but won't publish, that is a deployment issue, not an update issue. 🔍 Identify Your Error Type Ask yourself: Can I save my schema changes to the draft? If no, follow the Update Error steps below. If yes but your schema won't publish, see our Schema Deployment Errors article instead. ✅ Fix Schema Update Errors 📌 Step 1: Check Required Fields - Open the schema editor for your page in OTTO SEO automation. - Look for fields marked with a red asterisk (*) or red outline. - Fill in all required fields with valid data. - Attempt to save again. 📌 Step 2: Validate Field Formats Ensure all fields match their expected format: - URLs: must start with http:// or https:// - Numbers: no letters or special characters unless specified - Dates: must follow YYYY-MM-DD format - Email: must contain @ and a valid domain - Phone: must follow your region's standard format Correct any mismatched values and save. 📌 Step 3: Check Your User Permissions If the error mentions "permission denied" or "unauthorized," your account may lack schema editing rights. Contact your workspace admin to confirm you have editor or admin access to this page's schema. 📌 Step 4: Clear Your Browser Cache Stale cache can cause validation errors. Clear your browser cache and cookies, then refresh the page. Log back in and try updating the schema again. 📌 Step 5: Try a Simpler Change Make a small, obvious change to one field (such as adding a single character to a text field), then save. This helps isolate whether the error is field-specific or system-wide. If the simple change saves, the issue is with your original data. 📌 Step 6: Export and Reimport If the schema remains stuck: 1. Export your current schema configuration (if your platform provides this option). 2. Create a new schema from scratch for the same page. 3. Manually re-enter your data using the exported values as reference. 4. Save and test. ❌ Schema Update vs. Deployment: Quick Reference Update Error: Error appears when you try to save or modify the schema. Schema is in draft or editing mode. You cannot proceed to publish. Deployment Error: Schema saves correctly. Error appears when you publish or during publishing. Schema is pending or failed to go live on the page. If you can save your schema but it will not publish, do not follow the steps above. Instead, consult our Schema Deployment Errors article or contact support. 🚀 Next Steps Once your schema saves successfully, you can publish it to your page. If publishing fails, visit our deployment troubleshooting guide. If you need further assistance, open 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 Deployments Turning On and Off

🧭 Overview If your OTTO deployments are switching on and off on their own, getting stuck, or failing to stay active, this article walks you through the four most common root causes and how to fix each one. Follow the diagnostic steps below in order to identify your specific issue quickly. 🔍 Step 1 — Confirm the Symptom Before troubleshooting, identify exactly what you are seeing. This helps pinpoint the right fix. - Deployments toggle off shortly after turning on — likely a script reinitialization loop or Cloudflare conflict. - Deployments appear active but changes are not applied — likely a task queue delay. - Deployments turn on but revert after a few minutes — likely a permission or CMS sync failure. - Deployments stay stuck in a loading or processing state — likely a task queue backlog. ⏱️ Cause 1 — Task Queue Processing Delays OTTO processes deployments through a background task queue. During high-traffic periods or after bulk changes, tasks can back up and cause deployments to appear inactive or to cycle on and off as tasks retry. How to resolve: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Open the affected site and check the deployment status indicator. If it shows a spinning or pending state, the queue is still processing. 3. Wait 5–10 minutes and refresh the page. Do not toggle the deployment off and on again during this time, as repeated toggling adds more tasks to the queue and worsens the delay. 4. If the stuck state persists beyond 15 minutes, disable the deployment once, wait 2 minutes, then re-enable it to force a fresh task entry. ☁️ Cause 2 — Cloudflare Integration Configuration Issues If your site uses Cloudflare, certain settings can conflict with OTTO's script delivery and cause deployments to deactivate intermittently. The most common culprits are aggressive caching rules, Rocket Loader, and Bot Fight Mode. How to resolve: 1. Log in to your Cloudflare dashboard and navigate to the Speed section for your domain. 2. Disable Rocket Loader. This feature asynchronously loads JavaScript and can prevent OTTO's deployment script from initializing correctly. 3. Go to Security → Bots and temporarily disable Bot Fight Mode. OTTO's script requests can be misidentified as bot traffic, causing the connection to drop. 4. In Caching → Configuration, set the caching level to Standard and ensure that the page rule or cache rule covering your site does not cache HTML responses aggressively. 5. If you use Cloudflare Workers or Page Rules that rewrite or redirect URLs, verify they do not intercept the OTTO script endpoint (/_otto/ paths). 6. After making changes, purge your Cloudflare cache and re-enable the OTTO deployment in Search Atlas. 🔁 Cause 3 — Script Installation or Reinitialization Loops A reinitialization loop occurs when the OTTO script is installed, then detected as conflicting with another script or plugin, removed automatically, and then reinstalled — causing a visible on/off cycle. This is most common on WordPress sites with security or performance plugins. How to resolve: 1. In your WordPress admin panel, check for plugins that manage or block external scripts, such as security hardening plugins, script managers, or cookie consent tools. 2. Temporarily deactivate these plugins one at a time, re-enable the OTTO deployment after each deactivation, and observe whether the toggling stops. This isolates the conflicting plugin. 3. Once identified, whitelist the OTTO script domain (cdn.searchatlas.com) in that plugin's settings instead of keeping it deactivated. 4. Verify the script is only installed once. Go to OTTO SEO → All Sites (SEO Automation) → your site → Deployment Settings and confirm there is no duplicate script entry. If you previously installed the OTTO snippet manually in your theme files, remove it to avoid a double-installation conflict. 🔐 Cause 4 — Permission or CMS Sync Failures OTTO requires continuous write access to your CMS to apply and maintain changes. If the connected account's permissions are revoked, expire, or fall out of sync, deployments will revert or toggle off automatically. How to resolve: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open the affected site. 2. Navigate to Avatar (top-right) → Settings → CMS Connectors and review the connected CMS credentials. 3. If you see a warning icon or a Reconnect prompt, click it and re-authenticate with your CMS account. Use an account that has Administrator-level permissions. 4. If no warning is shown but the issue persists, disconnect the CMS integration, save, then reconnect and re-authenticate from scratch to force a full credential refresh. 5. After reconnecting, re-enable the deployment and monitor it for 10 minutes to confirm it holds its active state. ✅ Quick Diagnostic Summary - Spinning/stuck state for under 15 min → Wait for queue to clear. - Toggles off immediately after enabling → Check Cloudflare Rocket Loader and Bot Fight Mode. - Cycles on and off repeatedly every few minutes → Check for conflicting plugins causing a script loop. - Reverts to off after 5–10 minutes → Reconnect CMS credentials with Administrator access. 💬 Still Need Help? If you have worked through all four causes and the intermittent toggling continues, gather the following details before reaching out: your site URL, the approximate time the toggling started, and any recent changes made to your CMS, Cloudflare settings, 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.

Remove OTTO NLP Keyword Modules From Your Homepage

OTTO deploys NLP keyword optimizations through its own integration layer — not your CMS. This means they can appear active on your homepage even when your page editor shows no changes. Use the steps below to remove them entirely from within Search Atlas. 📋 What You Need to Know First NLP keyword modules are injected by OTTO's deployment layer (typically a Cloudflare Worker or direct site integration). Because they live outside your CMS, you cannot remove them by editing your theme, templates, or page content. Undeploying a fix removes the live injection but keeps the recommendation saved in OTTO — you can re-apply it at any time without starting over. These modules are injected as hidden structured data (JSON-LD) or hidden HTML elements in your page source, which is why they do not appear in your page editor but are still present in your page's markup. ⚙️ How to Remove NLP Keywords from Your Homepage 1. Open your Search Atlas dashboard and navigate to OTTO via Left sidebar → OTTO SEO → All Sites → [your project card]. 2. Select your project. 3. Go to SEO Fixes or Deployments. 4. Use the page URL filter to locate your homepage — typically / or your root domain URL. 5. Find the fix type labeled NLP Keywords or NLP Terms. In the dashboard these may also appear as nlp_terms (Semantic Analysis / Knowledge Graph) or nlp_faq (Knowledge-Based Trust / Factual Enhancement). 6. Select the fix and click Undeploy, or toggle it off. 7. Confirm the action when prompted. ⏱ What Happens After You Undeploy - The NLP keyword injection is removed from your homepage's live output. - If OTTO is connected via a Cloudflare Worker, allow a few minutes for the Worker to re-sync before the change is visible. - The NLP suggestions remain saved in OTTO and can be redeployed whenever needed. - Known issue: A confirmed platform bug (currently queued for a fix) can cause NLP and FAQ modules to remain on the page after undeployment — a stale injection. If the content is still present after a few minutes and a hard refresh, contact support via the chat widget below. ⚠️ Common Mistakes to Avoid - Do not edit your website files or CMS to remove these modules — changes there will not affect OTTO's deployment layer. - Use Undeploy if you want to pause the fix. Only use Delete if you want to permanently remove the recommendation from your project. - Undeploying NLP terms on your homepage does not affect NLP fixes deployed to other pages in your project. - If the NLP module is injecting irrelevant keyword clusters (content unrelated to your site's topic), undeploy the homepage NLP fix and then redeploy it to regenerate only that page's output. This will not affect NLP fixes on other pages. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Site Lens: Orphan Pages Count Text Visibility (Resolved)

🔍 What Was Happening In the Site Lens view inside Site Audit, the orphan pages count label rendered in a color that blended into the dark background of the Settings panel. The label was present in the interface but effectively unreadable, making it impossible to see how many orphan pages had been detected for your site. This affected any user who opened the Site Lens Settings panel when orphan pages were present in their audit results. 🛠️ How to Load the Fix The fix is live in production. If the orphan pages count text still appears hard to read, your browser may be serving a cached version of the app. Perform a hard refresh to force the latest version to load: - Windows or Linux: Press Ctrl + Shift + R - Mac: Press Cmd + Shift + R After the hard refresh, the orphan pages count text displays correctly in the Site Lens Settings panel. 📡 Engineering Status Our team identified the root cause and deployed a fix to production. The resolution has been verified and no changes to your account or project settings are required. A hard refresh is the only step needed if you are still experiencing the problem. 📞 When to Contact Support If the orphan pages count text remains unreadable after performing a hard refresh, reach out to our support team. To help us investigate quickly, include: - Your browser name and version - A screenshot showing the affected text in the Site Lens Settings panel - The domain or OTTO project name where you are seeing the issue 🎯 The orphan pages count label now displays correctly in Site Lens. If a hard refresh does not resolve the issue for you, our support team is ready to help you get unblocked.

🔌 OTTO Pixel Installation via GTM on Proprietary CMS

🧭 Overview When you install the OTTO pixel through Google Tag Manager (GTM) on a proprietary or custom CMS, the Search Atlas dashboard may still show a Not Installed status even after the tag is correctly configured. This is almost always caused by aggressive server-side or CDN caching on your CMS — not a problem with GTM or the OTTO pixel code itself. This article walks you through the correct troubleshooting path and helps you decide when to stop OTTO diagnostics and escalate to your hosting or CMS provider instead. 📌 What Is Duct Tape SEO and Why Does It Matter Here? Duct Tape SEO is the Search Atlas onboarding and activation framework that connects your website to OTTO, our OTTO SEO automation engine. It is the layer responsible for verifying that the OTTO pixel is detected on your site before any automated SEO actions can begin. During pixel verification, Duct Tape SEO sends detection requests to your website URL. If your CMS caches pages at the server level, those cached responses may not include the GTM container script — which means the OTTO pixel never loads in the response that Duct Tape SEO inspects, even though GTM is correctly set up on the live site. This is why the dashboard shows Not Installed: Duct Tape SEO is reading a stale cached page, not the live rendered version of your site. ✅ Step 1: Confirm Your GTM Setup Is Correct Before assuming a cache issue, verify that GTM itself is configured properly: 1. Log in to your GTM account and open the container linked to your site. 2. Confirm the OTTO pixel tag exists, is set to fire on All Pages, and is not paused. 3. Click Preview in GTM and enter your website URL. The GTM debug panel should show the OTTO pixel tag firing on page load. 4. Publish the container if you have made any recent changes. Unpublished changes are not live. 5. Return to Search Atlas, navigate to OTTO SEO in the left sidebar, and trigger a pixel re-check. If the GTM preview confirms the tag is firing but the dashboard still shows Not Installed, proceed to Step 2. 🗄️ Step 2: Clear Your CMS and Server Cache This is the most common root cause on proprietary CMS platforms. Cache must be cleared at every layer — plugin, server, and CDN — before Search Atlas can detect the pixel correctly. Common cache locations to clear: - CMS built-in cache: Look for a Cache, Performance, or Optimization section inside your CMS admin panel and purge all cached pages. - Caching plugins: If you use a plugin such as WP Rocket, W3 Total Cache, LiteSpeed Cache, or a proprietary equivalent, clear all caches from within the plugin settings. - Server-side cache: Contact your hosting provider or system administrator and ask them to purge the full page cache at the server level (Nginx, Apache, Varnish, or equivalent). - CDN cache: If your site sits behind a CDN such as Cloudflare, Fastly, or a proprietary CDN, purge the entire cache or at minimum purge the cache for your homepage and key landing pages. After clearing all cache layers, wait two to three minutes, then return to OTTO SEO in the left sidebar and trigger another pixel re-check. 🔍 Step 3: Verify the Pixel Is Live in a Browser After clearing cache, manually confirm the pixel is rendering on your live site: 1. Open your website in a browser using a private or incognito window (this bypasses browser cache). 2. Open the browser developer tools (F12) and go to the Network tab. 3. Reload the page and filter requests by searching for otto or your GTM container ID (format: GTM-XXXXXX). 4. Confirm that both the GTM container script and the OTTO pixel request appear in the network log. If you can see both requests in the browser but the Search Atlas dashboard still shows Not Installed, this confirms the cached page Duct Tape SEO is inspecting has not yet been refreshed. Repeat Step 2 and ask your hosting provider to confirm the purge was applied globally, including to any edge nodes. 🚦 When to Stop OTTO Diagnostics and Escalate Stop running OTTO troubleshooting steps and escalate to your hosting or CMS provider when all three of the following are true: - The GTM preview panel confirms the OTTO pixel tag is firing correctly. - A private browser session shows the pixel loading in the network tab on your live site. - The Search Atlas dashboard still shows Not Installed after multiple pixel re-checks. At this point, the issue is not with OTTO or GTM. Your hosting or CMS provider needs to confirm that server-side caching, edge caching, or a reverse proxy is not serving stale responses to external crawlers and verification tools. Ask them specifically: "Can external requests from third-party tools receive a fully rendered, non-cached version of my pages?" ⚠️ Important Notes for Proprietary CMS Platforms - Some proprietary CMS platforms cache pages separately for logged-in users versus public visitors. Ensure cache is cleared for the public, unauthenticated view of your pages. - If your CMS uses server-side rendering (SSR) or static site generation (SSG), the GTM script must be included in the rendered HTML output — not injected only on the client side after the initial response is served. - Some enterprise CMS platforms require a deployment or publish action to push cache changes to production. Confirm with your CMS administrator whether this step is required. 💬 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.

🔄 Why OTTO Schema Doesn't Appear in Your WordPress Plugin

📐 Two Separate Systems When you deploy schema through OTTO SEO (Left sidebar → OTTO SEO → All Sites → [your project card]), the changes are delivered via a JavaScript overlay — a script that injects schema markup directly onto your live page at render time. This allows changes to go live immediately without touching your WordPress database or plugin settings. Because of this architecture, your WordPress plugin fields will never reflect changes made through OTTO. The two systems operate independently and do not communicate with each other. ⚠️ Why the Plugin Fields Look Empty - OTTO overlay: Schema is injected via JavaScript when your page loads. It is live and visible to search engine crawlers. - WordPress plugin: Stores schema in your WordPress database. It has no visibility into what OTTO's overlay is serving. ✅ How to Confirm Your Schema Is Live 1. Run your page through Google's Rich Results Test — OTTO-injected schema will appear there. 2. Use View Page Source on the live page to see the schema rendered by the overlay. 3. Check Left sidebar → OTTO SEO → All Sites → [your project card] — a green "Deployed" badge confirms the overlay is active. 📌 Avoid Schema Conflicts If your WordPress plugin is also configured to output schema for the same page types, you may end up with duplicate or conflicting markup. Disable schema output in your WordPress plugin for any page type OTTO is already managing. 💬 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 Canonical Tags on Paginated Archive Pages

🧭 Overview When OTTO deploys canonical tag optimizations, it works reliably on most page types. However, paginated archive pages — such as /blog/2/, /blog/3/, and beyond — can sometimes display incorrect or missing canonical tags after deployment. This article explains why this happens and what you can do about it. ​ 🔎 What Is the Issue? After OTTO deploys a canonical optimization, you may notice that paginated versions of your archive or blog index pages do not reflect the correct canonical URL. For example: - The canonical on /blog/2/ points to the first post in the loop instead of the paginated archive page itself. - The og:url tag also inherits the wrong URL from the first post in the loop. - The canonical appears correct on page 1 (/blog/) but breaks on subsequent pages. This is a known limitation related to how WordPress outputs canonical and Open Graph tags on archive, category, and search result pages. In some environments, the existing theme or plugin emits a canonical pointing to the first post in the loop rather than the archive URL — and OTTO's deployment cannot always override this in a persistent way. ​ ⚙️ Why Does This Happen? OTTO applies canonical changes by modifying the page's DOM at deployment time. On most pages, this works as expected. On paginated archive pages, two compounding factors can interfere: - WordPress loop behavior: Certain WordPress themes and SEO plugins emit the canonical tag using the first post returned in the query loop, which means archive pages receive the wrong canonical by default before OTTO can intervene. The Search Atlas WordPress plugin previously had this same behavior on archive, category, and search pages — this has been resolved (WP-418). - DOM-only replacement limitation: In some configurations, OTTO's canonical update is applied only at the DOM level and does not fall back to a string-level replacement. If the page regenerates or the canonical is written late in the render cycle, the OTTO update may not persist across all paginated URLs (WP-536). - Canonical metabox write-only issue: An additional edge case exists where a canonical value saved via the canonical metabox is stored correctly but never emitted as the actual canonical URL on the front end. This issue (WP-544) is currently in release and affects environments where metabox-level canonical overrides are expected to take effect. This is not a configuration error on your end — it is a technical constraint that the Search Atlas engineering team has identified and is actively working to resolve. ​ ✅ What You Can Do Right Now While the platform-level fix is being finalized, the following steps can help reduce or eliminate incorrect canonicals on your paginated archive pages: 1. Check your WordPress SEO plugin settings. If you are using a plugin such as Yoast SEO, Rank Math, or All in One SEO, navigate to its settings and confirm that canonicals for archive and category pages are set to the archive URL — not inherited from the first post. Disable any option that auto-generates canonical tags based on loop content. 2. Re-deploy the canonical optimization via OTTO. In the Search Atlas platform, go to Left sidebar → OTTO SEO → All Sites (SEO Automation). Locate the affected project, open the canonical issue type, and re-deploy. You can now use the Deploy All by Issue Type feature to deploy across all paginated URLs at once without pagination restrictions. In some environments, a second deployment resolves the persistence issue. 3. Verify with a live crawl after deployment. After redeploying, use Left sidebar → Site Metrics → Pages to inspect the affected paginated URLs and confirm the canonical tag is now correct. 4. Avoid conflicting canonical sources. If your theme outputs its own canonical tag independently of your SEO plugin, the conflicting sources can override OTTO's changes. Remove or disable any hardcoded canonical output in your theme's header.php or equivalent template file. 📋 How to Confirm the Canonical Is Correct To verify whether the canonical tag is rendering correctly on a paginated archive page, follow these steps: 1. Open the paginated URL in your browser (for example, https://yourdomain.com/blog/2/). 2. Right-click the page and select View Page Source. 3. Search for canonical using Ctrl+F or Cmd+F. 4. Confirm the href value matches the paginated URL exactly — for example, https://yourdomain.com/blog/2/ — and not the URL of any individual post. If the canonical still points to a post URL after following the steps above, the issue may require a deeper configuration review. ​ 🛠️ Engineering Status The Search Atlas engineering team has already shipped fixes for the most common variants of this issue, including: - Correcting the canonical and og:url tags emitted by the Search Atlas plugin on archive, category, and search pages (WP-418 — Done). - Ensuring OTTO canonical deployment applies consistently across all paginated URLs without restriction, including a UI update supporting mass deployment by issue type (OTTO-996, OTTO-997 — Done). Two remaining fixes are currently in progress: - String-level fallback for DOM-only replacement failures (WP-536) — currently in release. This update will improve reliability for environments where the canonical is written late in the render cycle and the DOM-level update does not persist. - Canonical metabox emission fix (WP-544) — also currently in release. This resolves cases where a canonical value is saved via the metabox but never output as the canonical URL on the front end. 💬 Still Seeing the Problem? If you have followed the steps above and the canonical tag is still incorrect on your paginated archive pages, our team can review your specific site configuration and deployment logs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Restore Lost OTTO SEO Content Generation Quota

🔍 Overview In some cases, content generated inside OTTO SEO may unexpectedly show a fail status — even if you had already edited and prepared it for publishing. When this happens, you may need to regenerate the content, which consumes additional quota that should not have been used. Our support team can investigate these cases and restore the quota spent on failed generations. ⚠️ What Causes This Issue Content generated in OTTO SEO can occasionally fail to save or sync correctly due to a platform-side error. This is a known issue that our engineering team is actively working to resolve. The result is that content you already edited and prepared disappears and is marked as failed, forcing you to regenerate it and use extra tokens in the process. ✅ What You Should Do 1. Confirm the failure. Go to Left sidebar → OTTO SEO and review your generated content. Note which articles or items are showing a fail status that you had previously edited or completed. 2. Record the quota used. Before contacting support, note how many tokens or quota credits were consumed on the failed generations. This information speeds up the restore process significantly. 3. Do not regenerate immediately if possible. If you have already regenerated the content, note both the original and the additional quota used so support can restore the full amount. 4. Contact our support team. Our team has been granted permission to restore quota in verified cases of content failure. This cannot be done automatically — a support agent must review and approve the restore on a case-by-case basis. 📋 Information to Have Ready To help our support team process your quota restore as quickly as possible, gather the following before reaching out: - The number of quota credits or tokens consumed on failed generations - The approximate date and time the failure occurred - A brief description of what happened — for example, that content was edited and ready to publish before it disappeared - Any screenshots or screen recordings showing the fail status, if available 🛠️ What Happens After You Contact Support A support agent will review your case and, if the failure is confirmed, escalate it internally to obtain permission for a quota restore. Once approved, the agent will reset the quota credits that were lost. You will receive confirmation once the restore has been completed. Note that any underlying sync or publishing discrepancy may be separately escalated to the engineering team for further investigation. 💡 Tips to Avoid Losing Work - If content is marked as fail shortly after generation, wait a few minutes and refresh the page before assuming the content is lost — quota display and content sync can sometimes lag behind. - Copy or save any edited content to a separate document before publishing, so you have a backup if a sync issue occurs. - Check back on your quota after bulk generation tasks, as there have been known instances where quota panels do not refresh immediately after articles are created. 💬 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 Not Rendering on React or Lovable SPA Sites

🔍 Why OTTO Changes Don't Appear on Your Live Site OTTO deploys SEO changes by injecting updated meta tags via a script in your site's <head>. On traditional HTML sites this works without issue. On React, Lovable, and other single-page application (SPA) frameworks, these frameworks manage their own metadata through JavaScript libraries (e.g. react-helmet) that run on every page render and overwrite OTTO's injected values. OTTO automatically detects SPA frameworks and uses JavaScript rendering for re-crawls, but this client-side overwrite is a code-level conflict that still requires one of the fixes below. This is why OTTO correctly reports the deployment as Engaged — the deployment is working. The conflict happens after the page loads, when the framework replaces OTTO's tags with its own values. ✅ How to Confirm This Is Your Issue - In Left sidebar → OTTO SEO → All Sites, OTTO shows the deployment as Engaged or Deployed - Clearing cache still shows old title/meta description - Your site was built with React, Next.js, Vite, or generated by Lovable - Lovable sites only — Cloudflare Worker installation: there is a known issue where the Cloudflare Worker install method silently proxies apex and www DNS records, which can break sites hosted on Lovable. If your Lovable-hosted site stopped loading correctly after OTTO installation, switch to the standard script tag installation method while this is being resolved. 🛠️ Two Ways to Fix It 1. Adjust script load order — Modify your app's entry point so the Search Atlas script loads before React's metadata manager initializes. 2. Use the OTTO API integration — Write SEO values directly into your codebase via API. This is the recommended approach for React and Lovable sites. Contact support to request setup credentials and the guide. 💬 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. Additional Notes For Lovable sites, the OTTO script must be added to the index.html file inside the head tag — not inside any React component. Place the script as early as possible in the head section, before any other JavaScript files. Also: check View Page Source vs DevTools Elements tab to distinguish raw HTML vs rendered DOM conflicts.

⚠️ OTTO Corrupts Inline JavaScript — Slider Revolution and Modern JS Syntax

OTTO can inadvertently corrupt inline JavaScript that uses modern operators — specifically ?? (nullish coalescing) and ??= (nullish assignment) — causing plugins like Slider Revolution to fail silently. Disabling OTTO and clearing your site cache immediately restores affected elements while the engineering fix is deployed. 🔍 What Is Happening OTTO's page-optimization feature processes inline script blocks on your site. In some cases, it collapses the ?? and ??= operators — valid modern JavaScript syntax — down to a single ?, producing a JavaScript SyntaxError. Because browsers suppress SyntaxErrors in inline scripts silently, the affected script stops executing entirely, which causes: - Plugin sliders (e.g., Slider Revolution) to appear blank or disappear entirely - Any plugin or widget sharing the same inline script block to stop working - No visible error message on the front end of your site Who is affected: Sites running OTTO alongside Slider Revolution, or any theme or plugin that uses ?? or ??= operators in inline JavaScript. 🛠️ Workaround Steps Follow these steps to restore your slider and other affected JavaScript elements immediately. 1. Log in to your WordPress admin dashboard. 2. Go to Search Atlas → Settings in the left-hand navigation menu. 3. Disable OTTO for your site, or toggle off the page-optimization feature. 4. Clear any server-side or CDN cache for your site. 5. Reload your homepage — Slider Revolution and all affected JavaScript elements should now render correctly. Note: OTTO's SEO-assistance features are paused while it is disabled. You can re-enable OTTO safely once the fix is released. 📡 Engineering Status Our engineering team has identified and resolved the root cause of this issue. The fix is complete and is awaiting release. No action beyond the workaround above is required — once the update is deployed to your site, you can re-enable OTTO without any risk to your inline JavaScript. 📞 When to Contact Support Reach out to the Search Atlas support team if: - The workaround steps above do not restore your slider or affected elements - You cannot access the OTTO settings panel in your WordPress dashboard - You notice additional JavaScript failures after disabling OTTO When you contact us, include your site URL and a brief description of which elements are still affected after following the workaround. 🌀 Our engineering team has already resolved the root cause and the fix is on its way — once deployed, re-enabling OTTO will restore full optimization with no impact on your JavaScript. If your slider is still missing after following the steps above, contact our support team for direct assistance.

🔧 OTTO Activity Tab Errors and Schema Rollback

🗺️ What This Article Covers This article explains two issues you may encounter in OTTO (OTTO SEO): an error on the Activity or Work Summary tab that asks you to contact support, and how to roll back AI-generated JSON-LD schema changes and export a change log for your project. Both issues are common and usually self-resolvable in a few steps. ​ ⚠️ Why the OTTO Activity Tab Shows a "Contact Support" Error The most common cause of the OTTO Activity tab or Work Summary export throwing a "Something went wrong. Please contact support" error — or loading indefinitely — is a missing or disconnected Google Search Console (GSC) connection on your project. OTTO relies on live GSC data to populate the Activity tab and generate the Work Summary export. If GSC is not linked, or the OAuth token has silently expired, OTTO cannot retrieve the data it needs and will display this error. Other causes include a briefly expired GSC OAuth token (where the connection appears active but has lost authorisation in the background) or a short-lived platform sync delay. Always check your GSC connection status before contacting support — it resolves the error in the vast majority of cases. ​ 🔌 Step 1 — Check and Reconnect Your GSC Integration 1. Navigate to Left sidebar → OTTO SEO → Installation Guide. 2. Select your project from the project selector at the top of the page. 3. Scroll to the Google Search Console section and confirm whether your GSC property shows a green Connected status. 4. If the status is Not Connected, Disconnected, or missing entirely, go to Site Metrics → (GSC page) and click Connect GSC Account to complete the OAuth authorisation prompts to re-link the property. 5. Once reconnected, allow 2–5 minutes for OTTO to sync your GSC data, then return to the Activity tab and refresh the page. ✅ Step 2 — Confirm the Activity Tab Now Loads After reconnecting GSC, navigate to Left sidebar → OTTO SEO → Overview and select your project from the project selector. Click the Activity (also labelled Work Summary) tab. The tab should now display your full OTTO task history without any error. If the error persists after reconnecting GSC and waiting 5 minutes, try clearing your browser cache or switching to a different browser before contacting support. ​ ↩️ Step 3 — Roll Back AI-Generated JSON-LD Schema Changes If OTTO has deployed JSON-LD structured data markup to your project and you need to revert those changes, follow these steps: 1. Navigate to Left sidebar → OTTO SEO → All Sites → Select your project → Tasks. 2. Select your project from the project selector at the top of the page. 3. In the task list, filter or search for tasks of type Schema or JSON-LD to locate the recently deployed changes. 4. Click the specific task you want to revert to open its detail panel. 5. Select the Rollback or Undo option within the task detail panel and confirm the action when prompted. 6. Repeat for each schema task you need to revert. Important: Rolling back a task removes the AI-deployed schema markup from the affected pages. This action is not automatically reversible — confirm you want to revert before proceeding. If you need to re-deploy the same schema later, you can do so again from Left sidebar → OTTO SEO → All Sites → Select your project → Tasks. ​ 📤 Step 4 — Export the Work Summary (Change Log) To download a full timestamped log of all OTTO activity — including schema deployments, rollbacks, and other AI-driven changes — for your project: 1. Navigate to Left sidebar → OTTO SEO → Overview and select your project from the project selector. 2. Click the Activity (or Work Summary) tab. 3. Click the Export Work Summary button in the top-right area of the tab. 4. The downloaded file will contain a complete timestamped log of every task OTTO has applied to your project, which you can use as a change log for review or handoff. Note: If the Export Work Summary button returns a "Something went wrong" error, this is almost always caused by the missing GSC connection described in Step 1. Reconnect GSC first, then retry the export. ​ 🔍 Quick Troubleshooting Checklist - Activity tab loading indefinitely or throwing an error? Check your GSC connection at Left sidebar → OTTO SEO → Installation Guide. - "Something went wrong. Please contact support" on the Work Summary export? Reconnect GSC at Left sidebar → OTTO SEO → Installation Guide, wait 2–5 minutes, and retry. - Need to see a complete log of every change OTTO made? Go to Left sidebar → OTTO SEO → Overview → Activity tab and click Export Work Summary. - Need to roll back specific JSON-LD schema changes? Go to Left sidebar → OTTO SEO → Tasks, filter by Schema type, and use the Rollback option on each relevant task. - Export still failing after reconnecting GSC? Clear your browser cache or switch browsers, then retry before contacting support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 OTTO Deployed Fixes Not Appearing Live on WordPress

🧭 Overview When OTTO marks a fix as deployed — such as a meta description update, title tag change, or schema addition — it means the instruction has been sent successfully from Search Atlas. However, for those changes to appear live on your WordPress site, the OTTO WordPress plugin must be installed and active. If the plugin is deactivated or missing, OTTO has no way to write changes to your site, and the fixes will never appear in the page source or any Chrome SEO extension. ​ 🔍 Most Common Cause: OTTO Plugin Deactivated The number one reason deployed OTTO fixes do not appear live is that the OTTO plugin has been deactivated on your WordPress site. This can happen after a WordPress update, a hosting migration, a security scan that disables unfamiliar plugins, or a manual change by another team member. To check and fix this: 1. Log in to your WordPress admin dashboard. 2. Go to Plugins → Installed Plugins. 3. Locate the OTTO by Search Atlas plugin in the list. 4. If the plugin shows as Inactive, click Activate. 5. Return to Search Atlas, navigate to Left sidebar → OTTO SEO → Overview, and confirm your site is connected. 6. Check the page source or your Chrome extension to verify the deployed fixes are now live. ⚙️ How OTTO Deployment Works Understanding the deployment flow helps you pinpoint issues quickly: - OTTO generates SEO recommendations and lets you approve and deploy them directly from Search Atlas. - Once deployed, Search Atlas sends the approved changes to your WordPress site via the OTTO plugin. - The plugin receives those instructions and applies them to the relevant pages on your live site. - If the plugin is inactive or disconnected, the changes queue on the Search Atlas side but never reach your site. ✅ Full Pre-Check List Before Troubleshooting Further Before trying advanced steps, confirm all of the following: - OTTO plugin is installed and active in WordPress → Plugins → Installed Plugins. - Plugin version is up to date. An outdated plugin may fail to apply certain fix types. Update it from the WordPress plugin screen if a newer version is available. - Site is connected in Search Atlas. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and confirm your domain shows a green connected status. - The correct site is selected. If you manage multiple sites, make sure you are viewing the right one under Left sidebar → OTTO SEO → Overview. - Fixes are marked as Deployed, not just Approved. Under Left sidebar → OTTO SEO → Tasks, confirm the status column shows Deployed for the fixes in question. 🔄 Additional Troubleshooting Steps If the plugin is active and the site is connected but fixes are still not appearing live, try the following in order: 1. Clear your WordPress cache. If you use a caching plugin such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, purge all cached pages after deploying fixes. Cached pages serve an older version of your HTML and will not reflect new changes until the cache is cleared. 2. Clear your CDN cache. If your site uses Cloudflare or another CDN, purge the cache from your CDN dashboard as well. 3. Reconnect the CMS connector. In Search Atlas, go to Left sidebar → OTTO SEO → Installation Guide, find your site, and follow the steps to reconnect. This refreshes the authentication token between Search Atlas and your WordPress plugin. 4. Redeploy the affected fixes. Under Left sidebar → OTTO SEO → Tasks, locate the fixes that are not appearing, and use the redeploy option to push them again after confirming the plugin is active. 5. Check for plugin conflicts. Temporarily deactivate other SEO plugins (such as Yoast SEO or Rank Math) to confirm they are not overriding the meta tags OTTO is writing. Only one SEO plugin should control meta output at a time. 🛠️ Reinstalling the OTTO Plugin If the plugin was deleted rather than just deactivated, you will need to reinstall it: 1. In Search Atlas, go to Left sidebar → OTTO SEO → Installation Guide. 2. Select your site and follow the on-screen instructions to download the latest version of the OTTO plugin. 3. In your WordPress admin, go to Plugins → Add New → Upload Plugin and upload the plugin file. 4. Click Activate once the installation is complete. 5. Return to Search Atlas to verify the connection is restored under Left sidebar → OTTO SEO → All Sites (SEO Automation). 💬 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.

🛠️ Resolving Page-Level Schema Null Value Warnings and Internal Link Redirect Issues in OTTO

This article explains why OTTO flags null values in your Page-Level Schema Markup, why fixing Review and Aggregate Rating warnings can feel like a loop, and how to clear internal link warnings tied to redirected URLs. ⚠️ Why OTTO Flags Null Review and Aggregate Rating Schema Fields OTTO scans each page for content patterns that match known schema types. When it detects a star-rating element on the page, it interprets that element as review-related content and suggests Review and Aggregate Rating schema properties. The warning appears when OTTO has no underlying data to populate those properties. If the page has no actual product reviews, rating values, or review counts, OTTO cannot fill the Review and Aggregate Rating fields, so they remain null and trigger the schema warning. Why the fix loops and how to break it The fix appears to loop because the warning is not caused by a broken setting you can toggle off. OTTO keeps detecting the star-rating element and keeps suggesting the same Review and Aggregate Rating properties, but there is no review data on the page to satisfy them. Re-running the fix re-detects the same element and re-creates the same null fields. Here's what to do: instead of re-running the fix, choose the path below that matches your page. How to resolve the null schema warnings Choose the option that matches your page: - If the page has no reviews: the null Review and Aggregate Rating values are expected. You can safely dismiss this warning or manually populate the Review and Aggregate Rating fields. The star-rating element triggers the suggestion, but with no review data available, these fields cannot be populated automatically. - If the page should display reviews: add genuine review content to the page, such as customer reviews, a numeric rating value, and a review count. Make sure that review data is visible on the page so OTTO can detect it. Once that data exists on the page, OTTO can populate the Review and Aggregate Rating fields instead of leaving them null. After you confirm which case applies and update the page accordingly, OTTO can resolve the Review and Aggregate Rating fields on the next crawl rather than re-flagging empty values. Note: Other schema fields can trigger a similar Review Required state. For example, numeric fields such as an ImageObject's width and height that are flagged as strings can keep a page stuck in Review. This is a known issue tracked separately (OTTO-2193); if you encounter it, reach out to support so it can be confirmed against that fix. 🔗 Why OTTO Warns About Internal Links Pointing to Redirected URLs OTTO flags internal links when they point to a URL that redirects to another URL. In this case, internal links still point to /collections/halloween-collection, which redirects to /collections/halloween. Relying on that redirect is what triggers the internal link warning. How to fix the redirected internal link warnings 1. Find every internal link that points to the redirecting URL, /collections/halloween-collection. 2. Update each of those links to point directly to the final destination, /collections/halloween, so they no longer rely on the redirect. 3. Save your changes and allow OTTO to recrawl the site. Once the internal links point directly to /collections/halloween and OTTO recrawls the site, these internal link warnings should clear. 🎯 You now know that null Review and Aggregate Rating warnings come from a star-rating element with no review data behind it, and that internal link warnings clear once you point links directly to the final URL instead of a redirect. Update the relevant pages and links, then let OTTO recrawl to confirm the issues resolve.

🛠️ Fixing the "Field 'url' Contains a Relative URL" Schema Validation Error in OTTO

When OTTO flags the warning "Field 'url' contains a relative URL — absolute URLs are required", a URL field in your schema holds a path instead of a full web address. Find the field, prepend your site's protocol and domain, and the warning clears immediately. ⚠️ What This Error Means Schema markup standards require every URL value to be absolute — it must include the protocol and domain so search engines can resolve it unambiguously. A relative URL is missing that prefix. - Relative URL (invalid): /blog/my-article - Absolute URL (required): https://www.example.com/blog/my-article Any value that begins with / or ../ is relative and will trigger this warning. 🔍 How to Find the Affected Field OTTO does not currently highlight the specific field causing the error, so you need to locate it manually inside the schema editor. 1. Open OTTO and navigate to the schema that shows the warning. 2. Click Review Schema to open the schema editor. 3. Scan every field whose key is url, image, sameAs, contentUrl, or any other key that holds a URL value. 4. Identify any value that starts with / or ../ — these are the relative URLs you need to fix. This issue appears most often in Article, Product, BreadcrumbList, ImageObject, and Organization schema types, but can occur in any schema that references a URL. ✏️ How to Convert a Relative URL to an Absolute URL Once you find a field with a relative value, update it by prepending your site's full protocol and domain. 1. Note your site's root domain — for example, https://www.example.com. 2. Click the affected field in the schema editor to edit its value. 3. Replace the relative path with the complete absolute URL. 4. Click Save to apply the change. Example: - Before: /products/blue-widget - After: https://www.example.com/products/blue-widget Repeat for every field in the schema that still contains a relative path. A single schema can have multiple url fields — each one must be absolute. ✅ How to Confirm the Fix Is Complete 1. After saving, click Review Schema again. 2. Check the validation results for the "Field 'url' contains a relative URL" warning. 3. If the warning is gone, your schema is valid and ready to deploy through OTTO. If the warning persists, at least one more field still holds a relative URL. Return to the schema editor, locate the remaining instance, and apply the same fix. 🎯 You can now identify any relative URL field inside an OTTO schema and convert it to an absolute URL to pass validation. For a full overview of how OTTO validates and deploys schema markup across your site, see the OTTO Schema Management guide.

🛠️ OTTO Work Summary Export Error: 'Something Went Wrong'

When you try to export Work Summary results from an OTTO SEO project, a generic 'Something went wrong' error can prevent the export from completing. Work through the steps below to clear the error and download your data. 🔍 What Causes the Work Summary Export Error The error appears when the OTTO Work Summary export request cannot be processed. Common triggers include: - A temporary server-side issue during the export request - A backend processing or validation error on the server - A browser session that has timed out or lost its authentication token - A browser cache conflict interfering with the export action - Work Summary data still loading in the background when the export is triggered 🛠️ How to Fix the OTTO Work Summary Export Error Work through the steps below in order. Most users resolve the error at step 1 or 2. 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac), then wait for the Work Summary to fully load before clicking Export again. 2. Log out and log back in. Open your Avatar Menu (👤), select Log Out, sign back in, and navigate back to the OTTO project's Work Summary section. A fresh session resolves most authentication-related export failures. 3. Clear your browser cache. In your browser settings, clear cached files and cookies for searchatlas.com, reload the Work Summary page, and retry the export. In Chrome, go to Settings → Privacy and security → Delete browsing data, select Cached images and files and Cookies, filter by searchatlas.com under Advanced, and click Delete data. 4. Switch to a different browser. Open the OTTO project in Chrome or Edge (recommended browsers) and attempt the export again. Firefox and Safari may apply stricter cookie policies that interfere with authenticated export requests. 5. Wait a few minutes and retry. If the platform is under elevated load, waiting 3–5 minutes before retrying is often enough for the request to succeed. 6. Contact support if the error persists. If none of the above steps work, contact Search Atlas support and include your project URL, browser name and version, OS, and a screenshot or screen recording of the error. This lets the support team escalate to engineering if needed. A successful export downloads a file directly to your browser's default downloads folder. If no file appears and no error shows, check your browser's download manager. ⚠️ If the Work Summary Export Error Persists If the error continues after completing all steps above, contact Search Atlas support with the following details so the team can investigate promptly: - The name or domain of the affected OTTO project - The date and approximate time the error occurred - Your browser name and version - A screenshot or screen recording of the error message If the error persists across multiple browsers, devices, and sessions, it may indicate a temporary platform-side issue. Check the Search Atlas status page or contact support to confirm whether a known issue is affecting exports. In some cases, account quota limits can interfere with data exports or project actions. If you see a quota-related message alongside the export error, contact support to review your account quota. Open a support ticket directly from More Features (apps-grid icon) → Help → Report a Bug inside Search Atlas. 🎯 You now know how to diagnose and resolve the 'Something went wrong' error in the OTTO Work Summary export. If none of the steps above clear the error, contact Search Atlas support with the details listed above for a fast investigation.

🛠️ Fix OTTO Injecting Custom HTML Below the Footer

If OTTO is placing SEO enhancements below your footer and breaking the layout on every page, you can fix it by removing the injected custom HTML. The recommended path is to delete the deployment from the Custom HTML Content module in the OTTO dashboard; you can also remove it from your WordPress editor. Either way, finish by clearing your WP cache. This article shows you where that HTML lives, how to spot it, and how to remove it safely. 🔍 Why OTTO Adds Custom HTML Below the Footer OTTO applies SEO improvements through on-page fixes. Some of these fixes inject custom HTML directly into your pages through the Custom HTML Content module. That injected content is tagged with a data-otto-pixel attribute so you can identify it. The content appears below the footer when OTTO cannot anchor the injected block to its intended position in the page template. This typically happens when a theme or template structure doesn't expose the expected insertion point, so the Custom HTML Content module falls back to rendering the block at the end of the page — below the footer on every page. This Custom HTML Content module behavior is tracked under OTTO-2305. Removing the specific injected deployment restores the original layout. 🧭 How to Identify the OTTO Custom HTML The injected content carries a data-otto-pixel attribute. This attribute is your marker for finding exactly which HTML block OTTO added, so you can delete that block without touching the rest of your page. What to Look For - An HTML block or element containing the data-otto-pixel attribute. - Content that appears below the footer on all pages rather than in a single intended location. 👀 How to View Deployed Custom HTML in the OTTO Dashboard Before removing anything, confirm what OTTO has deployed so you delete the correct block. 1. Open the OTTO dashboard for the affected site. 2. Go to the Custom HTML Content module. 3. Open the Deployed tab to see every custom HTML block OTTO has injected. 4. Review the deployments to identify the one carrying the data-otto-pixel attribute that is rendering below your footer. 🗑️ How to Remove the OTTO Custom HTML (Recommended) The primary, customer-confirmed way to remove the injected content is through the Custom HTML Content module in the OTTO dashboard. 1. In the OTTO dashboard, open the Custom HTML Content module menu. 2. On the Deployed tab, click each deployment to open it. 3. Delete the text (the injected custom HTML) inside the deployment. 4. Press Edit & Deploy to apply the change. 5. Clear your WordPress cache (see the cache section below) and reload an affected page to confirm the layout is restored. 🔧 Alternative: How to Delete the OTTO Custom HTML in WordPress If you prefer to remove the block directly in WordPress, delete the injected HTML from the editor, then clear your cache to reveal the corrected layout. 1. Open the WordPress editor for the affected page or template. 2. Locate the custom HTML block marked with the data-otto-pixel attribute. 3. Delete that custom HTML block. 4. Save your changes in WordPress. Watch the Video Walkthrough Your Search Atlas support contact can share a short video tutorial that demonstrates exactly how to find and delete the data-otto-pixel HTML inside the WordPress editor. If you don't have it yet, reach out to support to request the walkthrough. 🧹 How to Clear Your WP Cache After Deleting the HTML After you delete the custom HTML — whether from the Custom HTML Content module or the WordPress editor — your site may still show the old layout until the cache refreshes. Clearing the cache is an essential final step. 1. Open your WordPress caching plugin or hosting cache settings. 2. Clear or purge the WP cache. 3. Reload an affected page. Once the cache clears, you'll see the corrected page layout with the unwanted content below the footer removed. 🎯 You've now located the data-otto-pixel HTML, removed it from the Custom HTML Content module (or the WordPress editor), and cleared your cache to restore your layout. If the issue returns or you spot another injected block, contact Search Atlas support for the video walkthrough or further help with OTTO on-page fixes.

🛠️ Whitespace Gaps Between Content Blocks After OTTO/UCMS Sync

Extra <br> tags injected during an OTTO or UCMS content sync cause large blank spaces between Gutenberg blocks. The platform fix is already deployed — use the steps below to manually clean up any posts synced before the fix rolled out. ⚠️ What Causes the Whitespace Gaps During an OTTO or UCMS content sync, extra <br> (line-break) tags are inserted between Gutenberg block elements — for example, between a heading block and a paragraph block. WordPress renders each injected <br> as a full line of vertical space, producing the large visible gaps you see in both the Block Editor and the published frontend. This bug has been fixed in the recent platform update. Posts synced before the fix was deployed may still contain injected <br> tags and need the manual cleanup steps below. 📌 Which Posts Are Affected Any post synced via OTTO or UCMS before the recent platform fix was deployed may contain injected <br> tags and require manual cleanup. Posts synced after the fix do not need cleanup. If you are unsure which posts were synced before the fix, contact Search Atlas support for confirmation. 🔍 How to Confirm Extra <br> Tags Are Present Switch to the WordPress Code Editor to inspect the raw block markup: 1. Open the affected post in the WordPress Block Editor (Gutenberg). 2. Click the Options menu (⋮) in the top-right corner of the editor toolbar. 3. Select Code editor to view the raw HTML markup. 4. Scroll through the markup and look for standalone <br /> or <br> tags that appear between block comment delimiters — lines beginning with <!-- /wp:... or <!-- wp:.... If you see <br> tags between block boundaries rather than inside a block's own content, the OTTO/UCMS sync injection is confirmed as the source of the whitespace gaps. 🛠️ How to Remove the Extra <br> Tags Manually While in Code editor view (see the confirmation steps above), remove the injected tags: 1. Use your browser's find function (Ctrl+F on Windows / Cmd+F on Mac) inside the Code editor to locate each instance of <br. 2. Delete every <br /> or <br> that appears between two block comment delimiters. Leave any <br> tags that sit inside a block's own content — those are intentional line breaks. 3. Click Exit code editor to return to the visual Block Editor and verify the gaps are no longer visible. 4. Click Update (or Save draft) to save the cleaned post. 5. Reload the live frontend page to confirm the extra vertical spacing is gone. Your page now displays with normal spacing between all content blocks. 🚀 Permanent Fix Status The platform-level fix has already been deployed. OTTO and UCMS syncs will no longer inject extra <br> tags between Gutenberg blocks — no manual cleanup is required for future syncs. Posts synced before the fix are not retroactively corrected; use the manual removal steps above to clean up any existing affected posts. 🎯 You now know why OTTO/UCMS syncs produce whitespace gaps in the Gutenberg Block Editor and how to manually remove the injected <br> tags from affected posts. If gaps persist after the fix has rolled out to your account, contact Search Atlas support so the team can investigate further.

⚠️ OTTO Cache Serving Blank Pages on WordPress (0-Byte Response)

If your WordPress front-end shows blank pages while /wp-admin and /wp-login.php still load normally, the OTTO full-page cache has likely stored an empty (0-byte) response. This article shows you how to confirm the cause using response headers and restore your site immediately. ⚠️ What a 0-Byte OTTO Cache Response Looks Like A 0-byte cached response produces a specific symptom pattern you can distinguish from a PHP crash or a hosting outage: - Every front-end URL — homepage, posts, and category pages — returns HTTP 200 with a completely blank body - The browser shows a white or empty page with no error message and no partial content - The WordPress admin (/wp-admin), login page (/wp-login.php), and REST API endpoints continue to load normally - All visitors see blank pages — the issue is not limited to one browser or account PHP errors and theme crashes typically break the admin dashboard too, or display a visible error message. A hosting outage returns a 5xx status code rather than HTTP 200. When you see HTTP 200 + blank body + working admin, check the OTTO cache first. 🔍 How to Confirm OTTO Cache Is Serving the Empty Response The x-metasync-otto-cache response header tells you whether OTTO served a page from its cache. A value of HIT combined with a blank page body confirms a 0-byte cache event. Check response headers in browser DevTools 1. Open your browser and press F12 to open DevTools, then select the Network tab. 2. Load your homepage or any blank front-end URL. 3. Click the first document request in the list and open the Headers panel. 4. Under Response Headers, locate the x-metasync-otto-cache header. If the value is HIT and the page is blank, OTTO is serving the stored 0-byte response. If the value is MISS or the header is absent, OTTO is not the cause — check your active theme and plugins instead. Check response headers with curl Run the following command, replacing the URL with your site address: curl -sI https://yoursite.com Look for x-metasync-otto-cache: HIT and content-length: 0 in the output. Both values together confirm the diagnosis. 🛠️ How to Clear the OTTO Cache and Restore Your Site Purging the OTTO full-page cache deletes the 0-byte entry and forces OTTO to re-cache a valid response on the next page visit. Your front-end returns to normal immediately after the purge. Clear the cache from the WordPress admin 1. Log in to /wp-admin — this continues to work even when the front-end is blank. 2. In the left sidebar, go to Search Atlas → Settings (OTTO cache: Clear Page Cache / Clear Post Cache / Clear all cache). 3. Click Clear All Cache and confirm when prompted. 4. Reload your front-end homepage to verify pages are rendering correctly. Clear the cache from the Search Atlas dashboard 1. Log in to app.searchatlas.com and open your site's OTTO workspace. 2. Go to Settings → Full-Page Cache. 3. Click Purge Cache and confirm. You'll see a green confirmation message when the purge completes. After purging, OTTO re-caches a fresh response the next time each page is visited. Reload a front-end URL to confirm the blank pages are resolved. 💡 Why a 0-Byte Response Gets Cached OTTO stores the HTTP response it receives the first time it crawls a page. If that initial response is empty — due to a conflict at that exact moment — the empty response is stored and served to every subsequent visitor until the cache is cleared. Common triggers include: - Page builder initialization failure: Plugins like Elementor Pro can output a blank body if a license check or asset load fails at the moment OTTO first crawls the page. - Theme activation during cache warm-up: Activating or switching a theme (such as Hello Elementor) while OTTO is building its cache can cause an empty response to be stored. - Managed hosting server rules: Hosts like WP Engine apply server-level request filtering that can interfere with OTTO's cache-crawl requests and produce a 0-byte response. - Plugin deactivation while cache is live: Deactivating a plugin that a cached page depends on causes the page to render blank, which OTTO then re-caches as valid content. ⚙️ How to Prevent Future 0-Byte Cache Events Follow these practices to reduce the risk of OTTO caching an empty response: - Clear the OTTO cache before and after any theme change, major plugin update, or hosting migration. - After any maintenance window, reload a front-end page and confirm that x-metasync-otto-cache shows HIT with visible content — not a blank page. - Exclude pages that rely on external license checks or volatile dynamic content (steps below). Exclude specific pages from the OTTO full-page cache If a specific page repeatedly triggers empty-cache events, exclude it so OTTO always serves it dynamically: 1. In /wp-admin, open the Search Atlas plugin and go to the Compatibility page, then scroll to the OTTO Excluded URLs section. 2. Enter the page URL (e.g., https://example.com/my-account) in URL Pattern, choose a Match Type (Exact Match or Contains), and click Add Excluded URL. 3. OTTO will not run on those URLs and its cache is cleared for them, so they are served fresh on every request. Note: cart and checkout pages are skipped by the plugin automatically — you do not need to exclude them. Excluded pages are always served dynamically and are not affected by future 0-byte cache events. 🎯 You can now confirm a 0-byte OTTO cache event using the x-metasync-otto-cache: HIT header, restore your site by purging the cache from /wp-admin or the Search Atlas dashboard, and reduce recurrence by clearing the cache around theme and plugin changes. For more on configuring OTTO's caching rules, see the OTTO Full-Page Cache Settings article.

🛠️ Errors by Service & How to Fix Them

When a Search Atlas feature stops working, shows missing or delayed data, or appears stuck, the cause almost always traces to one specific service layer. Find your symptom below — each entry states the cause and the fastest path to resolution. 🔧 Linkgraph (Core API) 🔴 OTTO Metrics Not Updating Cause: Missing or broken background task (Celery — Search Atlas's asynchronous task processor). 1. Re-run the scan: in OTTO SEO → All Sites (SEO Automation), find the site's row and click Scan. 2. Trigger a manual recalculation: click Recalculate in the OTTO Overview panel, or go to OTTO → Settings → Recalculate Metrics. 3. If the issue persists after clicking Recalculate, wait 15–30 minutes for background tasks to complete, then refresh the page. 🔴 OTTO — AI Content Generation Stuck (Permanent Spinner) Cause: Celery worker crash left the generation flag uncleared (OTTO-1496, now resolved). The ai_gen_in_progress flag previously stayed set after a mid-generation crash, blocking new generations. Because the fix adds an automatic TTL and cleanup task, most users will never see this spinner again. If you encounter a stuck spinner on an older generation job, use the navigate-away step below as a one-time reset while the cleanup task catches up. - Navigate away from the OTTO content generation page (for example, go to the OTTO Overview tab), then return to the content generation view. This forces the UI to re-evaluate the generation status flag. - Re-trigger AI content generation. - If the spinner remains after navigating back, wait 15–30 minutes for the TTL-based cleanup task to clear the flag automatically, then refresh the page before re-triggering generation. - If the spinner recurs after navigating away and re-triggering, contact support. The underlying bug (stuck ai_gen_in_progress flag) was resolved in OTTO-1496; a recurrence may indicate a new instance of the same pattern. Reference OTTO-1496 so the support agent has context. 🔴 OTTO PPC — Ad Strength Data Stale or Missing Cause: gRPC sync failures in sync_ad_strength_for_account (PPC-1813, now resolved). Ad strength and ad quality scores in OTTO PPC stopped updating for affected accounts starting March 2026. - The backend fix has been deployed — ad strength data should now sync correctly. - Allow up to 24 hours for scores to fully re-populate after the fix. - If ad strength data is still stale or missing after 24 hours, contact support and reference PPC-1813. 🔴 OTTO PPC — Missing Weekly Campaign Performance Data Cause: Boundary condition in the weekly sync task caused campaigns to be skipped (PPC-1781, now resolved). An exact 7-day boundary in the weekly campaign performance sync silently skipped campaigns from the previous run. - New weekly syncs now capture all campaigns correctly. - If you notice gaps in weekly data prior to the fix date, contact support and reference PPC-1781 to request a backfill. 🔴 OTTO via Cloudflare — Special Character Encoding Corruption Cause: Cloudflare script encoding bug that corrupted special characters on customer sites (SPE-666, now resolved). 1. Disengage OTTO on the affected site. 2. Confirm with Search Atlas support that the updated Cloudflare script has been deployed on the Search Atlas side. 3. Reconnect the Cloudflare integration to re-engage OTTO. 🔴 OTTO — Schema Markup Generation or Deploy Failure Cause: The schema markup generator did not run, or browser-cached state is preventing deployment. 1. In the OTTO optimization dashboard, click the purple Generate button before attempting to deploy any suggested schema markup. 2. Clear your browser cache and retry the deploy. 3. If the error persists after these steps, this indicates a system-level generator failure. Open a support ticket with high priority and include the site URL and the schema type you were trying to deploy. 🔴 OTTO — Unwanted Text or Content Appearing on Site After OTTO Engagement Cause: An active deployed OTTO fix (for example, a Heading Length fix) is inserting content into the front-end of the site. 1. Go to OTTO → Deployments. 2. Identify the deployed fix responsible for the unwanted text (such as a Heading Length fix matching the affected element). 3. Undeploy that specific fix to remove the injected content from the site. 🔴 OTTO WordPress Plugin — API Key Could Not Be Verified Cause: The OTTO WordPress plugin requires two separate credentials. This error usually means only one was provided, or the values were entered in the wrong fields. 1. In Search Atlas, go to Settings → API Keys and copy your 32-character SearchAtlas API Key. Paste it into the Search Atlas API Key field in the WordPress plugin (WordPress plugin → Search Atlas → Settings). 2. Provide the second required credential — the OTTO project / site UUID — in its dedicated field in the plugin settings. Refer to the OTTO WordPress plugin setup documentation for the exact field name and where to copy the value from in Search Atlas. 3. Save the plugin settings. If the error persists, contact support with a screenshot of the plugin configuration screen. 🔴 503 / Dashboard Not Loading Cause: General gateway error at the dashboard level (upstream service unavailable or temporary network issue). 1. Refresh after 30–60 seconds. 2. Retry the action. 3. If the error persists beyond 2–3 minutes, check the Search Atlas status page or contact support with a screenshot of the error. 🔴 Tasks Stuck / Never Complete Cause: Queue mismatch or task failure. The stuck-site retry cap was increased in G3.9 — the system now makes more automatic attempts before declaring a final failure, so a task that previously appeared stuck may now self-resolve. 1. Do not re-trigger immediately. Wait at least 10–15 minutes without any manual intervention. 2. Avoid duplicate triggers while retries are in flight. 3. Re-trigger the action only after the task status changes to a final error state. 🔴 Crawl Stuck "In Progress" Cause: Timeout on a large site. 1. Reset the crawl. 2. Re-run the crawl. 3. Reduce crawl scope if the site is large. 🔴 Jobs Stop Mid-Process Cause: Memory limit exceeded (OOM — out of memory). - Retry with a smaller operation. - Avoid running multiple bulk-heavy actions simultaneously. 🔭 Site Explorer 🔴 Site Explorer Data Missing or Delayed (holistic_pillars Tasks) Cause: Database connection exhaustion affecting Site Explorer's holistic_pillars Celery tasks (SE-605, observed during the May 4 spike). Connection pool saturation caused holistic pillars tasks to fail or stall, leading to missing or delayed Site Explorer data. 1. Wait 10–15 minutes for the connection pool to recover and for queued holistic_pillars tasks to retry automatically. 2. Refresh the Site Explorer view to confirm whether the missing data has populated. 3. If data is still missing or delayed after 30 minutes, contact support and reference SE-605 so the team can confirm the task state for your project. 🎯 You now know the cause and fastest fix for the most common Search Atlas service errors. If your issue isn't listed here or persists after following these steps, contact Search Atlas support with your error details and any relevant ticket references from this guide.

⚠️ OTTO Un-Deploy Wipes SEO Plugin Meta Fields (Known Issue)

When you un-deploy an OTTO recommendation, a known bug can blank your SEO plugin's meta title and description fields. A simple three-step workaround fully protects your data until the fix is released. 🔍 What's Happening When you un-deploy an OTTO recommendation on a WordPress site, OTTO should clear only its own internal fields and leave your SEO plugin values untouched. Due to this bug, it instead overwrites those fields with an empty string — leaving your pages with blank meta tags. Blank meta tags harm SEO more than stale or default values. Any meta title or description you manually entered in your SEO plugin before the OTTO deployment is permanently lost by the un-deploy. Who is affected: WordPress sites using OTTO with RankMath, Yoast SEO, or AIOSEO where at least one OTTO recommendation has been un-deployed. Scope: This issue only affects un-deploy. If meta fields blank during deploy, contact support — that is a separate issue. 🛠️ Temporary Workaround (until WP-373 ships) Follow these steps each time you un-deploy an OTTO recommendation to protect your SEO data: 1. Record your current values. Before un-deploying, open your SEO plugin (RankMath, Yoast, or AIOSEO) and copy or screenshot the meta title and meta description for every affected page. 2. Un-deploy in OTTO. Proceed with the un-deploy as normal inside Search Atlas. 3. Re-enter your values immediately. Return to your SEO plugin and paste the title and description you recorded in step 1. Your fields are now fully restored. Already un-deployed and lost your values? You will need to manually rewrite the meta title and description for each affected page in your SEO plugin. Use cached versions of your pages, previous ranking data, or your brand guidelines to reconstruct them. Re-deploying the same recommendation: The workaround protects your SEO plugin values from being blanked on un-deploy. If you re-deploy the same recommendation afterward, your manually re-entered values will be preserved (or overwritten based on the recommendation content) — test on one page first. 📡 Engineering Status Our engineering team has identified and resolved this bug. The fix is complete and awaits release (WP-373). Check your dashboard for updates. We will update this article as soon as the update is live. You do not need to submit a bug report — the issue is confirmed and the fix is queued for deployment. 🐛 Related Known Issues This is one of three persistence layer bugs being fixed together. If your SEO plugin fields aren't saving correctly during deployment, that is WP-372 or WP-410. These issues are being addressed as part of the same fix (WP-373) and will be resolved when that update ships. 📞 When to Contact Support Reach out to the Search Atlas support team if any of the following apply: - The workaround does not restore your SEO fields as expected after re-entering your values. - You are seeing blank meta tags on pages where you did not un-deploy an OTTO recommendation. - You need assistance reconstructing lost meta titles or descriptions across a large number of pages. 🎯 The fix for this issue is already built and queued for release — follow the workaround above to keep your SEO data intact, and normal behavior will be restored automatically once the update ships.

⚠️ 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 Avatar 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.

🖥️ Search Atlas — Dashboard & Navigation Issues

Use this guide to diagnose and fix login failures, blank pages, unexpected logouts, locked features, and UI display problems in the Search Atlas dashboard. 🔐 Error 1: Login form doesn't respond when I click Sign In What's happening: A browser extension or cache issue is blocking the login process. Steps to try: - Hard-refresh the page. - Disable browser extensions (ad blockers, privacy tools, password managers) and try again. - Try an incognito window. - Clear cookies and cache for dashboard.searchatlas.com. - Use the Forgot Password link to reset credentials if the form consistently won't submit. 🔄 Error 2: Logged out unexpectedly in the middle of working What's happening: Your session expired or was reset due to a network interruption. Steps to try: - Log back in — your saved work is not lost. - Check that your browser doesn't clear cookies when it closes. - Ensure your browser allows cookies from searchatlas.com. - If this happens frequently, contact support — it may indicate a session configuration issue. 🔒 Error 3: A feature I expect is locked or shows an upgrade prompt What's happening: Either the feature isn't included in your plan or your account needs a session refresh after a recent upgrade. Steps to try: - Log out and log back in — plan changes require a fresh session. - Check your plan features: Click your avatar (top-right corner) → Billing (Plans & Top-ups). - Wait 10 minutes after upgrading — activation has a short delay. - If your plan shows the feature but it's still locked, contact support with a screenshot. ⚪ Error 4: Page loads blank — only white space visible What's happening: A JavaScript bundle failed to load, often triggered by a browser extension or stale cache. Steps to try: - Hard-refresh: Ctrl + Shift + R / Cmd + Shift + R. - Open in incognito mode. - Clear browser cache and reload. - Try Chrome — it's the most compatible browser for the platform. - Contact support if blank pages occur consistently across browsers. Note: If the blank screen appears specifically inside Website Builder and is accompanied by a persistent "making changes" spinner, this may indicate a platform-level issue rather than a browser-side problem. Contact support immediately with your project URL so the team can investigate server-side — support has a dedicated escalation path for Website Builder-specific blank-page incidents. ⚠️ Error 5: After a recent browser update, parts of the UI are broken What's happening: Browser updates occasionally break JavaScript rendering for complex web apps. Steps to try: - Hard-refresh to reload all JavaScript assets. - Clear full browser cache (not just cookies). - Disable recently updated extensions. - Try in a different browser to confirm it's browser-specific. - Check if the issue resolves itself after 24 hours — our team deploys compatibility fixes quickly. 🔔 Error 6: Notification or alert banners won't dismiss What's happening: The dismiss button's click handler failed, usually due to a JavaScript error. Steps to try: - Hard-refresh the page — the banner usually won't reappear. - If the banner is blocking important UI, use browser zoom-out (Ctrl + -) to see around it temporarily. - Log out and back in. - Report it to support with a screenshot — include the banner text so we can identify the source. 🔀 Error 7: Data from one project appearing in another project's view What's happening: A rare caching issue is mixing project data. Affects dashboard widgets and reports. Steps to try: - Hard-refresh the page immediately. - Log out and log back in to clear any cross-project session data. - Navigate directly to the correct project via Left Sidebar → OTTO SEO → All Sites → [Your Project Name]. - Contact support immediately — this is a data isolation issue we prioritize. 👥 Error 8: Team member can't access the account after being invited What's happening: The invite may have expired, gone to spam, or the seat limit was reached. Steps to try: - Go to Top-right Corner Avatar → Settings → Team Members (Pending Invites) and resend the invite. - Have the teammate check their spam folder. - Confirm your plan allows the number of seats you're trying to fill: Click your avatar (top-right corner) → Billing (Plans & Top-ups). - After the teammate accepts the invite, have them log out and back in to refresh permissions. - Contact support if the accepted invite shows no access — include the teammate's email address. 🌀 Most dashboard and navigation issues trace back to browser cache, extensions, session timeouts, or permission mismatches — not system failures. Work through the steps for your specific error above, and contact support if the problem persists.

🗺️ Search Atlas — Topical Maps & Content Planning Issues

This article covers Topical Maps, content planning, competitor gap analysis, topic clusters, content briefs, custom topics, saved maps, and Content Velocity reporting inside Search Atlas. ⚠️ Error 1: Topical Map is stuck on "Generating" for more than 30 minutes What's happening Competitor analysis and keyword gap analysis (DKN) run as asynchronous background jobs. Network interruptions, provider delays, or queue congestion can cause the generation task to stall. This is more common when: - analyzing very large domains - using broad seed topics - or generating multiple maps simultaneously. Steps to try 1. Go to: Left Sidebar → Local → Local SEO Tools →Topical Maps 2. Locate the generation job stuck in: "Generating"/"Fetching data" 3. Click Delete/Cancel on the stuck task 4. Start a new generation: - this will NOT delete existing maps - only the failed job is replaced 5. Reduce the scope temporarily: - use fewer competitors - or a narrower seed topic 6. Avoid running multiple Topical Maps simultaneously for the same domain 7. Wait 2 hours if the task remains frozen: - stalled jobs automatically time out and retry 8. Hard-refresh the dashboard after retrying: - Ctrl + Shift + R - Cmd + Shift + R 9. Check: Left Sidebar → Content → Topical Maps for duplicate stuck processes 10. Contact support if: - every generation attempt stalls repeatedly - or generation never completes after multiple retries Important Notes - DKN jobs are resource-intensive - large topical maps may legitimately require extended processing time - canceling a stuck job does not delete completed maps ⚠️ Error 2: Topical Map generated but clusters are missing or empty What's happening The AI cluster generation engine occasionally returns malformed or incomplete cluster data that cannot be parsed correctly. This can cause: - empty topic groups - blank keyword clusters - or partially generated maps. Steps to try 1. Open the affected Topical Map 2. Identify: - empty clusters - incomplete topic groups - or blank sections 3. Click Regenerate Clusters on the affected section 4. Wait several minutes for the cluster rebuild to complete 5. Refresh the map after regeneration 6. If multiple clusters are empty: - delete the map - regenerate from scratch 7. Narrow the seed keyword: - overly broad topics increase malformed cluster probability 8. Avoid running simultaneous cluster regenerations 9. Test with a smaller competitor set temporarily 10. Contact support if: - regenerated clusters continue returning empty - or the same map repeatedly fails parsing Important Notes - cluster generation depends on AI parsing pipelines - broad generic keywords produce lower-quality cluster separation ⚠️ Error 3: Competitor domains not showing up in the gap analysis What's happening Competitor intelligence data is pulled from external SEO research providers. Very small, new, or low-authority domains: - may not exist in the provider database yet - or may have insufficient crawl coverage. Steps to try 1. Verify the competitor domain is publicly accessible 2. Confirm the domain: - ranks in Google - has indexed pages - and has backlink activity 3. Try larger competitors in your niche first 4. Use competitor domains with: - 500+ referring domains - or established organic visibility 5. Avoid testing with: - new domains - staging sites - or low-traffic microsites 6. Run: Left Sidebar → Site Metrics → Competitors separately to confirm the competitor has provider coverage 7. Refresh the gap analysis after changing competitors 8. Reduce the number of competitors in the request 9. Retry during off-peak hours 10. Contact support if: - major well-known competitors never appear - or all competitor analysis remains blank Important Notes - competitor visibility depends on external provider coverage - provider databases refresh independently from Search Atlas ⚠️ Error 4: "Cannot create analysis" error when starting a new Topical Map What's happening A duplicate or active DKN generation task already exists for the same domain. The system blocks overlapping analysis jobs to: - prevent queue conflicts - avoid duplicate processing - and reduce malformed outputs. Steps to try 1. Go to: Left Sidebar → Content→ Topical Maps → Check Active Jobs 2. Look for: - pending jobs - stuck jobs - or active generations 3. Wait for active jobs to complete 4. Cancel frozen or duplicate jobs 5. Refresh the page after cancellation 6. Retry generation after several minutes 7. Avoid opening multiple generation tabs simultaneously 8. Confirm another team member is not already running the same analysis 9. Reduce the scope of the request temporarily 10. Contact support if: - no active jobs exist - but generation still fails immediately Important Notes - duplicate protection is intentional system behavior - background jobs may require several minutes to clear after cancellation ⚠️ Error 5: Content brief generated from a topical cluster is off-topic What's happening The content brief inherits context from the cluster seed keyword. If the seed keyword is: - too broad - ambiguous - or low-intent …the generated brief may become generic or partially irrelevant. Steps to try 1. Edit the cluster's primary keyword 2. Make the keyword: - more specific - more localized - or more intent-driven 3. Add: - target audience - industry - or content angle 4. Use: Refine Brief before regenerating 5. Avoid generic seed terms like: - "marketing" - "SEO" - "software" 6. Use long-tail intent-focused keywords instead 7. Regenerate the brief after refining 8. Compare competitor examples manually 9. Add custom subtopics if important context is missing 10. Contact support if: - all briefs consistently generate irrelevant outputs Important Notes - brief quality depends heavily on keyword specificity - AI-generated briefs should be treated as strategic first drafts ⚠️ Error 6: Topical Map not including keywords I know are important What's happening Automated keyword discovery prioritizes: - provider data - competitor overlap - and detected search demand. Very niche or long-tail keywords may not be discovered automatically. Steps to try 1. Use: Add Custom Topic inside the map 2. Manually create missing keyword clusters 3. Run: Left Sidebar → Keyword → Keywords Research separately for the missing terms 4. Import discovered keywords into the map manually 5. Expand competitor selection 6. Add more seed keywords before regeneration 7. Use localized variations of important terms 8. Include question-based queries and FAQs 9. Regenerate cluster relationships after additions 10. Contact support if: - large obvious keywords never appear in discovery Important Notes - no automated keyword discovery system captures 100% of long-tail search behavior - manual augmentation is expected for advanced SEO workflows ⚠️ Error 7: Saved Topical Map is no longer visible in the list What's happening Topical Maps are attached to the project where they were created. If the project: - was archived - deleted - disconnected - or moved …the associated map may disappear from the visible list. Steps to try 1. Check whether the project was deleted accidentally 2. Restore the archived project if possible 3. Refresh the Topical Maps dashboard 4. Confirm you are inside the correct workspace 5. Verify another team member did not rename or move the project 6. Check filters inside the Topical Maps list 7. Log out and back in to refresh permissions 8. Search for the map by project/domain name 9. Contact support if: - the project exists - but maps remain permanently missing Important Notes - restoring a project restores associated Topical Maps - workspace permissions affect map visibility ⚠️ Error 8: Content Velocity chart shows no data What's happening Content Velocity is a Beta reporting feature that requires enough publishing history before meaningful trends can be generated. Steps to try 1. Confirm your account has at least 30 days of publication history 2. Verify content was published through: - OTTO - Website Studio - or tracked publishing systems 3. Refresh the reporting dashboard 4. Expand the date range 5. Confirm the correct project is selected 6. Verify content tracking is enabled for the project 7. Wait for the next reporting cycle 8. Continue publishing content consistently 9. Avoid expecting meaningful trends from very small datasets 10. Contact support if: - the chart remains empty after 45+ days - or previously visible data disappears unexpectedly Important Notes - Content Velocity is still evolving as a Beta feature - trend analysis improves with larger publishing history datasets Most Topical Maps & Content Planning issues are not caused by broken Search Atlas functionality. They are usually related to: - asynchronous DKN processing - AI clustering behavior - competitor data limitations - broad seed topics - duplicate background jobs - or insufficient content history. Because Topical Maps combine AI generation, SEO intelligence, and semantic clustering systems, some delays or incomplete outputs are expected during large-scale analysis operations. 👉 The best Topical Maps results come from: - highly specific seed topics - strong competitor selection - narrow semantic intent - clean project organization - and allowing background analysis jobs enough time to complete

🛠️ OTTO SEO Injecting Unexpected Text into Your Page Headings

When OTTO SEO deploys a Heading Length fix, it pushes changes to your page's HTML heading tags (H1–H6) — not your site's navigation header or banner area. Undeploying a fix removes the injected text for sites with a working CMS connector or Cloudflare Worker. For Website Studio sites using only the pixel script, undeployment will not work — see the compatibility note below. What the change looks like: For example, if your original H1 was "Shoes" and OTTO's Heading Length fix determined it was too short, it may have rewritten it to "Buy Affordable Running Shoes Online" — replacing or expanding the original text within the heading tag. Before you begin: The undeploy workflow requires a properly configured OTTO installation (CMS connector or Cloudflare Worker). Website Studio sites using only the manually installed pixel script cannot deploy or undeploy fixes at all — OTTO's deployment pipeline is non-functional (is_deploy_functional = False) without a CMS connector or Cloudflare Worker. Approved fixes are saved in the database but are never pushed to your live site. If you are in this configuration, connect a supported integration before attempting any deploy or undeploy actions — see the compatibility note further down. Two separate actions — don't confuse them: (1) Undeploying a fix via the OTTO dashboard, which explicitly reverses that optimization and removes the injected text from your live site; and (2) Removing the OTTO pixel or script from your site, which only stops future changes and does NOT roll back already-deployed fixes. To remove injected heading text, you must use action (1). 🔍 Why OTTO SEO Is Modifying Your Heading Tags OTTO SEO's Heading Length fix rewrites HTML heading tags (H1–H6) to meet on-page SEO length recommendations. When deployed, the fix applies those changes live to your website's front end. This affects on-page heading elements only, not your site's top navigation or banner area. Disengaging OTTO from your site (for example, removing the pixel/script or disconnecting the CMS connector) stops new changes from being applied, but it does not roll back fixes that were already deployed. Those deployed fixes stay active on your live site until you explicitly undeploy each one. This is expected behavior, not a bug. Important: Removing the OTTO pixel or script from your site does NOT undeploy fixes. Previously deployed heading changes will remain on your live site until each fix is individually undeployed from within the OTTO SEO dashboard. Disengaging OTTO and undeploying a fix are two separate actions with different outcomes. 🛡️ Is OTTO's Heading Injection Safe? (Google Compliance) OTTO's Heading Length fix only modifies the visible text inside your page's H1–H6 tags. It does not use hidden content (such as display:none styling), keyword stuffing, or cloaking — the rewritten heading is the same for users and for search engine crawlers, and is contextually relevant to the page's topic. This is consistent with Google's Search Essentials (formerly Webmaster Guidelines), which define deceptive practices as showing different content to users than to crawlers or stuffing unrelated keywords to manipulate rankings — neither of which apply to OTTO's heading rewrites. This safety guidance applies specifically to the Heading Length fix covered in this article and is distinct from other OTTO fix types (for example, injected FAQ sections or keyword lists), which are addressed in their own documentation. 🛠️ How to Undeploy the Heading Length Fix To remove the injected heading text, locate and undeploy the Heading Length fix inside OTTO SEO: 1. Log in to Search Atlas and open OTTO SEO for your site. 2. Locate your list of deployed fixes. 3. Find the fix labelled Heading Length. 4. Click Undeploy next to the Heading Length fix. 5. Confirm the action in the dialog that appears. 6. Wait for the status to update to Undeployed. 7. Verify on your live site that the heading text has returned to its original state. Once undeployed, OTTO SEO removes the heading text change from your live site. For most CMS connector and Cloudflare Worker installations, this happens immediately. For pixel or manual script installations, visible changes on the live site and reflected audit state may lag or behave inconsistently — hard-refresh your browser and re-crawl your Site Audit if the change does not appear promptly. Compatibility note: Use this checklist to identify your installation type and the level of undeploy support available: - WordPress CMS Connector — fully supported for deploy and undeploy. If you are using the WordPress plugin for OTTO, do not also add WordPress as a separate CMS connector integration — having both active simultaneously can cause deployment conflicts. The WordPress plugin alone is sufficient. - Cloudflare Worker — fully supported for deploy and undeploy. If your Cloudflare Worker shows as connected but OTTO's connection scanner cannot detect the pixel/UUID on your live site, undeploy actions may not execute correctly. In this case, contact support to verify Worker status before relying on the undeploy workflow. - Website Studio pixel-only — NOT supported for deploy or undeploy. OTTO projects in this state will show is_deploy_functional = False and is_active = False; both flags must be resolved by connecting a supported integration. Approved fixes are saved in the database but never pushed to your live site until you add a supported connector. - Pixel or manual script on a third-party CMS — limited support; the Site Audit dashboard may not accurately reflect the live state. Important: If your project uses the manually installed pixel script, the Site Audit dashboard may display the original (pre-OTTO) heading text even when your live site is correctly showing the deployed version. This is a known reporting discrepancy — do not use the Site Audit view as the sole confirmation that a fix has or has not been deployed. ⚠️ Known issue — Website Studio pixel-only setups: This is a confirmed product issue. OTTO projects on Website Studio with only the manually installed pixel are flagged as is_deploy_functional = False and is_active = False on the backend, meaning no fix will ever reach your live site regardless of the dashboard status shown. The supported resolution is to connect a CMS connector or deploy a Cloudflare Worker. If you cannot do either, contact Search Atlas support for guidance. ⚠️ Known issue — Cloudflare Worker not detected: If you have connected a Cloudflare Worker but OTTO's connection scan still shows the pixel as undetected, this is a known issue. The Worker deployment may be functional even if the scan reports otherwise — contact support to verify backend status before troubleshooting further. If you are unsure which category you fall into, go to OTTO SEO > Installation Guide and confirm that a CMS connector or Cloudflare Worker is shown as connected. If neither is connected, contact Search Atlas support to verify your OTTO installation configuration before attempting any deploy or undeploy actions. ✅ Confirming the Heading Text Is Removed After undeploying, reload your website and check the affected heading. The OTTO-injected text should no longer appear on the live page. Note: The Site Audit dashboard may continue to display the previous heading text after undeploying due to a known reporting delay. For pixel-based installations, the Site Audit crawler may not accurately reflect the live deployment state even when JS rendering is active. Verify changes directly in your browser (or via browser dev tools by inspecting the heading element on the live page) rather than relying solely on the Search Atlas dashboard. Known reporting discrepancy — manual pixel (manual_script) installs: If you are using the manual pixel (manual_script) installation, be aware that the Site Audit dashboard may not accurately reflect currently deployed heading changes — it may display original source titles instead of OTTO-deployed ones, even with JS rendering enabled. This is a known reporting discrepancy; the live site state (verified in your browser) is the authoritative source. ⏱️ If the Heading Text Persists After Undeploying For most installations, undeployed changes propagate to the live site within a few minutes. If the original heading text does not return: - Hard-refresh your browser (Ctrl+F5 or Cmd+Shift+R) to bypass local browser cache. - Clear any CDN or page cache (for example, Cloudflare, WP Rocket, or your hosting provider's cache layer). - Re-crawl your Site Audit so the dashboard reflects the current live state. - If the injected text still persists after 24 hours, contact Search Atlas support with your OTTO project UUID so the team can investigate. Troubleshooting note for pixel script installs: If you use the pixel script and the Site Audit report still shows the original heading text after deploying a fix, this may be a known dashboard display issue — not a failed deployment. Verify the live page directly in your browser or use a third-party HTML inspection tool to confirm the actual deployed state before re-attempting deploy or undeploy. 🧩 About Other Content OTTO May Inject OTTO may also inject supporting SEO content beyond heading changes — such as keyword lists or FAQ sections — that may not be prominently visible in your site's main design. This content is contextually relevant, legitimate SEO content placed to support the page's topic, and is distinct from the Heading Length fix covered in this article. Is this black-hat SEO? No. Google's Webmaster Guidelines define hidden content as deceptive when it shows different content to users than to search engines, or when it stuffs unrelated keywords solely to manipulate rankings. The supporting content OTTO injects is topically relevant to the page, identical for users and crawlers, and intended to improve the page's semantic completeness — not to deceive. If you have concerns about specific content types being injected on your site, or want a particular injection removed, contact Search Atlas support. 🎯 Once you undeploy the Heading Length fix, your original heading text is restored to the live site (subject to your installation type). If unexpected text persists after undeploying, contact Search Atlas support for further assistance.

🤖 Search Atlas — OTTO SEO Automation Issues

🗂️ Troubleshooting Quick Reference — All Products

📌 Overview This index lists every product-specific troubleshooting section in the Search Atlas Help Center. Use it when you need to find the right troubleshooting category quickly without browsing the full menu. ⚙️ OTTO SEO - Troubleshooting: Audits, Crawl & Indexing - Troubleshooting: Deployment & Live Changes - Troubleshooting: Pixel Pending, UUID & Verification Errors - Troubleshooting: Pixel on GoHighLevel & Other Builders - Troubleshooting: Pixel on Shopify, Wix & Squarespace - Troubleshooting: Pixel on WordPress - Troubleshooting: Pixel, Cloudflare, GTM & Caching - Troubleshooting: Platform Conflicts & Caching - Troubleshooting: Scanning, Reprocessing & Knowledge Graph - Troubleshooting: Schema Errors - Troubleshooting: Titles, Meta & Headings - Troubleshooting: Wrong or Duplicate Content - Troubleshooting: Billing, Sites & Top-Ups (OTTO-specific billing) 🔍 Site Audit & Technical SEO - Troubleshooting: Audit Errors (General) - Troubleshooting: Audit Stuck, Empty or Zero Results - Troubleshooting: Crawl Failures & Blocked Crawlers - Troubleshooting: Instant Indexing Issues - Troubleshooting: Quota & Credits Errors - Troubleshooting: Scores, Reports & Exports ✍️ Content - Troubleshooting: Brand Vault Issues - Troubleshooting: Content Generation Errors - Troubleshooting: Press Release Issues (Content section) - Troubleshooting: Publishing & CMS Sync 📢 Ads (OTTO PPC) - Troubleshooting: Billing & Charges (Ads-specific) - Troubleshooting: Campaign Launch & Sync - Troubleshooting: Conversion Tracking & Retargeting - Troubleshooting: Data, Reports & Audits (Ads-specific) - Troubleshooting: Google Ads Connection & Accounts 🔗 Authority Building - Troubleshooting: Backlink Data & Reports - Troubleshooting: Cloud Stacks Issues - Troubleshooting: Credits & Refunds (Authority-specific) - Troubleshooting: Link Lab & Publisher Orders - Troubleshooting: Press Release Issues (Authority section) - Troubleshooting: Other Issues 📍 Local SEO & GBP - Troubleshooting: Citation & Listing Issues - Troubleshooting: GBP Audit & Reports - Troubleshooting: GBP Connection & Verification - Troubleshooting: GBP Data Mismatch & Sync - Troubleshooting: GBP Posts & Social Media Issues - Troubleshooting: Heatmap Issues 🔑 Keywords & Site Explorer - Troubleshooting: Keyword Data Missing or Zero - Troubleshooting: Keyword Tool Errors & Quota - Troubleshooting: Rank Tracker Issues - Troubleshooting: Site Explorer Issues 📊 Site Metrics (GSC & GA4) - Troubleshooting: GSC & GA4 Connection - Troubleshooting: GSC & GA4 Performance Data 📈 Reports & Report Builder - Troubleshooting: Data Missing or Mismatched - Troubleshooting: GA4 & Analytics Connection - Troubleshooting: Report Builder: PDF, Layout & Export - Troubleshooting: Scheduled & Email Delivery 🌐 Website Studio - Troubleshooting: Forms, Popups & Embeds - Troubleshooting: Images, Fonts & Styling - Troubleshooting: Navigation, Menus & Headers - Troubleshooting: Page Editing & Templates - Troubleshooting: Publishing, Domains & SSL 🔌 Integrations, API & MCP - Troubleshooting: Authentication & Connection - Troubleshooting: MCP & API Access - Troubleshooting: Shopify, Wix & Webflow Connectors - Troubleshooting: Sync & Publishing Failures - Troubleshooting: WordPress Plugin Issues 🤖 AI Products - Troubleshooting: AI Agent Behavior (AI Agent) - Troubleshooting (Coworker / AI Co-Worker) - Troubleshooting (AI Visibility) 📱 Social Hub - Troubleshooting: Social 💡 Tips for Finding the Right Article 1. Know the product first. Each section above maps directly to a product area. Identify which tool the customer is using before searching. 2. Use the category, not just search. Search returns results across all sections. Navigating to the specific product's troubleshooting category surfaces only the relevant articles. 3. Check the OTTO SEO section for pixel and deployment issues. These are the most frequent troubleshooting topics and have the most articles. 4. For billing questions, use the Account, Billing & Agency section instead of the product-specific troubleshooting categories.

📄 Fixing Google Doc Export Errors in Content Editor

📌 Overview If you click the Google Doc export option in the content editor and it fails, stalls, or shows an error, you are not alone. In most cases the cause is something on the browser or Google account side, and you can fix it in a few minutes. This article explains the most common causes and walks you through the fixes. 🔎 Common Causes Exports to Google Docs usually fail for one of these reasons: - Google account permissions: Search Atlas has not been given permission to create files in your Google Drive, or the permission has expired. - Wrong Google account: You are signed in to several Google accounts, and the export is trying to use a different one than you expect. - Blocked pop-ups: Your browser blocks the Google sign-in or permission window, so the export never completes. - Full Google Drive: Your Drive has no storage space left for a new document. - Browser issues: Old cached data, cookies, or extensions such as ad blockers and privacy tools interfere with the export. - Very large content: A long article with many images or tables takes longer to export and may time out. ✅ Quick Fixes to Try First Start with these simple steps. They solve most export problems. 1. Wait about 30 seconds after clicking export, then check your Google Drive. Sometimes the document is created even though the editor still shows a loading state. 2. Refresh the content editor page and try the export again. 3. Make sure your content is saved before exporting. 4. Check that you are signed in to the correct Google account in the same browser. 🔐 Reconnect Your Google Account If the export keeps failing, the permission between Search Atlas and Google may need to be refreshed. 1. Open your Google Account settings and go to the section for third-party apps and access. 2. Find Search Atlas in the list and remove its access. 3. Return to the content editor and start the export again. 4. When Google asks for permission, choose the correct account and approve all requested access. Be sure to accept every permission box. If you leave one unchecked, the export may fail because the app cannot create the document. 🪟 Allow Pop-Ups and Check Your Browser The Google permission window opens in a pop-up. If your browser blocks it, the export cannot finish. - Allow pop-ups for the Search Atlas site in your browser settings. - Temporarily turn off ad blockers or privacy extensions and try again. - Try an incognito or private window, which disables most extensions. - Clear your browser cache and cookies, then sign in again. - Use an up-to-date version of Google Chrome, which usually works best with Google services. 💾 Check Your Google Drive Storage If your Google Drive is full, Google cannot create the new document. Open Google Drive and check your storage at the bottom of the left menu. If you are near or over your limit, delete files you no longer need, empty the trash, or free up space, then try the export again. 📏 Exporting Large Articles Long articles with many images, tables, or embedded elements can take longer to export. If a large export fails: - Wait a little longer before trying again, and check Google Drive for the document. - Split the content into smaller sections and export them one at a time. - Compress or reduce the number of large images in the article. 📝 Workaround: Copy and Paste If you need your content right away, you can move it manually. Select all of the text in the content editor, copy it, and paste it into a new Google Doc. Formatting such as headings and lists usually carries over, though you may want to double-check images and tables. 🛠️ Information to Gather Before Contacting Support If none of the steps above work, a few details will help our team resolve the issue faster: - The name of the article or project you are exporting - The exact error message, or a screenshot if there is one - The browser and version you are using - Whether you tried an incognito window and reconnecting your Google account - Approximately how long the article is and whether it contains many images 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔄 New Pages Missing in OTTO After Recrawl

🔍 What You May Be Seeing You ran a recrawl on your site and the new pages now appear in Page Explorer. However, when you open OTTO Automation, those same pages are not listed. This is a common question, and it does not mean the crawl failed. 🧠 Why This Happens Crawling and OTTO processing are two separate steps: - Crawling discovers the pages on your site and adds them to Page Explorer. - OTTO processing analyzes those pages so OTTO can generate and manage optimizations for them in Automation. A recrawl updates your page list, but OTTO may not automatically pick up the new pages. In that case, the project needs to be reprocessed so OTTO can include them. ✅ Quick Checks Before Requesting a Reprocess Run through these checks first. They resolve many cases on their own. 1. Confirm the crawl finished. Make sure the recrawl shows as complete and is not still running. 2. Verify the pages in Page Explorer. Search for the exact page URLs to confirm they were captured. 3. Check the correct site. If you manage several sites, confirm you are viewing the same project in both Page Explorer and OTTO Automation. 4. Clear filters. Remove any active filters or search terms in OTTO Automation that could hide the new pages. 5. Refresh the page. Reload your browser or log out and back in to make sure you are seeing the latest data. 6. Allow some time. After a crawl, processing can take a while on larger sites. Check again later before taking further action. 🔁 How to Get the New Pages Into OTTO If the pages are in Page Explorer but still missing from OTTO Automation after the checks above, the site most likely needs to be reprocessed. 1. Open the project for the affected site. 2. Go to OTTO and check whether a reprocess or refresh option is available for the site. 3. If it is available, start it and allow time for processing to complete. 4. Return to OTTO Automation and check that the new pages are listed. If you do not see a reprocess option, our team can trigger it for you. Share the site name and a few example page URLs so we can check them quickly. 💡 Tips to Avoid This in the Future - After every recrawl, confirm new pages appear in both Page Explorer and OTTO Automation before making further changes. - When you add many pages at once, such as a new section or product category, expect that a reprocess may be needed. - Keep a list of newly published URLs so you can verify them easily. - Make sure new pages are accessible to crawlers and not blocked by settings such as noindex tags or robots rules. 🛠️ Still Not Showing? If the pages are still missing after a reprocess, include the following details when you contact us: - The site or project name - Two or three example URLs that are missing from OTTO Automation - The approximate date and time of your last recrawl - Whether the pages appear in Page Explorer 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fixing Rolled-Back OTTO Changes Still Showing

🔍 Overview You rolled back one or more OTTO optimizations, such as Missing Keywords, NLP Terms, Heading Optimizations or Dynamic Indexing, but your live WordPress site still shows them. This is a known situation, and it usually means an older copy of the OTTO data is still being served. This article explains why it happens, what you can check yourself, and how to get it fully cleared. 🧩 Why Rolled-Back Changes Can Still Appear When OTTO is connected through the WordPress plugin, the plugin keeps a stored copy of the optimizations so your pages load quickly. After a rollback, your site can keep showing the old changes for a few reasons: - Stored plugin data: The plugin may still hold the previous OTTO data for the site and has not refreshed it yet. - Page caching: A WordPress caching plugin or your host may be serving a saved copy of the page from before the rollback. - CDN caching: A service such as Cloudflare may be delivering an older version from its servers. - Browser caching: Your own browser may be showing a saved version of the page. - Outdated plugin version: An older plugin version may not pick up rollbacks as reliably. ✅ Step 1: Confirm the Rollback in OTTO First, make sure the rollback was saved on the OTTO side. 1. Open your project in Search Atlas and go to OTTO SEO. 2. Open each optimization type you rolled back (for example Missing Keywords, NLP Terms, Heading Optimizations, Dynamic Indexing). 3. Check that the affected pages show the change as rolled back or not deployed. 4. If any items still show as active, roll them back again and wait a few minutes. 🧹 Step 2: Clear Your Caches Work from the closest layer to your visitors back toward your site. 1. Browser: Do a hard refresh, or open the page in a private or incognito window to rule out browser caching. 2. WordPress caching plugin: Clear all caches in your caching plugin (for example WP Rocket, LiteSpeed Cache, W3 Total Cache or similar). 3. Host-level cache: If your host provides its own cache, clear it from your hosting dashboard. 4. CDN: Purge the cache in your CDN, either everything or just the affected URLs. After each step, reload the page and check whether the old changes are still there. 🔄 Step 3: Refresh the OTTO Plugin Connection 1. Log in to your WordPress dashboard and open the Search Atlas plugin settings. 2. Check that the plugin is connected to the correct project and that the connection shows as active. 3. Update the plugin to the latest version if an update is available. 4. Look for any option to sync, refresh or clear OTTO data in the plugin settings and run it if you see one. 5. Clear your site caches again, then re-test the page. 🔎 Step 4: Verify What Your Site Is Serving To check whether the old changes are really still live, look at the page itself rather than relying on what you remember. - Open the page in a private window. - View the page source and check the title, meta description, headings and body text for the OTTO changes you rolled back. - Compare against the original content in your WordPress editor. If the page source still shows rolled-back content after all caches are cleared, the plugin is most likely still holding stored OTTO data for the site. 💬 When You Need Our Team to Clear Stored Plugin Data If the rollback is confirmed in OTTO and the caches are cleared, but the changes still render, the stored OTTO data for your site in the plugin needs to be cleared on our side. You cannot always do this yourself from the dashboard, so our team will handle it for you. To speed things up, include this information when you reach out: - Your website domain - Which optimization types you rolled back (for example Missing Keywords, NLP Terms, Heading Optimizations, Dynamic Indexing) - Two or three example page URLs that still show the old changes - The caching plugin or CDN you use, if any - Your current Search Atlas plugin version If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 🛡️ Tips to Avoid This in the Future - After any rollback, clear your site cache and CDN cache right away. - Keep the Search Atlas plugin updated to the latest version. - Roll back in small batches and check a sample page before rolling back everything. - Use a private browser window when checking your results so you see what visitors see. - If you use aggressive page caching, set it to refresh automatically when content changes. ❓ Quick FAQ - How long should I wait after a rollback? Allow a few minutes for the change to process, then clear your caches. If nothing changes after that, follow the steps above. - Will clearing the plugin data delete my WordPress content? No. It only removes the stored OTTO optimization data. Your original pages and posts stay as they are. - Can I re-apply OTTO changes later? Yes. You can deploy optimizations again at any time from OTTO.

🛠️ Fix Publication Media Noindex and Missing Anchor Errors

🔍 What This Error Means When you submit a published article to Publication Media, our system visits the live page and checks that it meets two requirements. If either check fails, the submission is rejected, even if the article looks fine in your browser. A rejection message may look like this: The page the article has been published on has a meta robots tag instructing search engines not to index the page and Missing Target anchor text followed by your keyword and target landing page. This message reports two separate problems: - Noindex problem: the page tells search engines not to index it. A page that cannot be indexed will not deliver SEO value, so it cannot be accepted. - Missing anchor problem: the page does not contain a link that uses the exact target anchor text and points to the exact target landing page. Both checks must pass before the article is accepted. 🚫 Why the Noindex Check Fails A noindex instruction is usually a hidden setting, so the page can look perfectly normal to a visitor. Common causes include: - The site's global setting to discourage search engines from indexing is turned on (common on new or staging sites). - The individual post or page has a noindex option enabled in an SEO plugin or in the page settings. - The article is saved as a draft, private, or password-protected page. - The page category, tag, or template is set to noindex. - The server sends a noindex instruction in the page headers, which you cannot see on the page itself. ✅ How to Check and Remove the Noindex Tag 1. Open the published article in your browser. 2. Right-click the page and choose View Page Source. 3. Press Ctrl+F (Cmd+F on Mac) and search for noindex. 4. If you find a line like meta name="robots" content="noindex", the page is blocked from indexing. 5. Go to your site's admin area and open the article's settings. 6. Find the search engine visibility or indexing option in your SEO plugin or page settings and set it to index (allow search engines to show this page). 7. Check the site-wide setting too. Make sure search engine visibility is not set to discourage indexing. 8. Save or update the page and make sure its status is Published. If you cannot find a noindex tag in the page source, it may be coming from the server headers or a security or caching tool. Ask whoever manages your hosting to check for an X-Robots-Tag header. 🔗 Why the Anchor Text Check Fails The system looks for a clickable link on the page that meets both conditions: - The visible link text matches the target anchor text exactly (for example, do deer eat moonflowers). - The link points to the exact target landing page shown in the error message. Typical reasons it is not detected: - The keyword appears in the article as plain text but is not hyperlinked. - The anchor text was reworded, shortened, or changed in capitalization or spelling. - The link goes to a different page, or to a slightly different version of the URL (for example, http instead of https, a missing or extra trailing slash, or added tracking parameters). - The link was removed when the article was edited or reformatted in your editor. - The link is added by a script after the page loads, so it is not in the page source. - An old cached version of the page is being shown without the link. 🧭 How to Fix the Missing Anchor 1. Open the error message and copy the exact target anchor text and target landing page URL. 2. Edit the published article and find the sentence that contains the keyword. 3. Make sure the keyword is typed exactly as shown, with no extra words inside the link. 4. Select that text and add a link. Paste the target landing page URL exactly as shown. 5. Update the page, then open it in a private browser window and click the link to confirm it goes to the right page. 6. Open View Page Source and search for the anchor text to confirm the link appears in the page code. ♻️ Clear Your Cache Before Resubmitting After you fix either problem, the live page may still show the old version to our system. This is a common reason an article is rejected again even though it was corrected. - Clear the cache in your website's caching plugin, if you use one. - Clear any CDN or hosting cache. - Wait a few minutes, then reload the page in a private browser window to confirm your changes are live. 🚀 Resubmit Your Article 1. Confirm the page is published and publicly accessible without a login. 2. Confirm there is no noindex tag in the page source. 3. Confirm the exact anchor text links to the exact target landing page. 4. Return to Publication Media and submit the article URL again. 💡 Quick Checklist - The page status is Published, not draft or private. - Search engine visibility is allowed for the site and for this page. - No noindex appears in the page source. - The anchor text matches the target exactly. - The link goes to the exact target landing page URL. - The cache has been cleared. 💬 Still Seeing the Error? If the article still gets rejected after you have worked through the steps above, we are happy to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Please include the article URL and the full error message so we can look into it faster.

🔍 Fixing Site Audit History and OTTO Metadata Issues

📌 Overview This article covers four issues customers often report together: two Site Audit exports that show different numbers for the same date, OTTO changing H2 headings in the wrong place on Elementor pages, meta description tags that do not appear, and the Twitter Description edit (pencil) icon not responding. For each one, you will find likely causes, checks you can run yourself, and what to send our team if you still need help. 📊 Why Two Site Audit Exports Can Show Different Numbers for the Same Date If two exports for the same day (for example, October 9) show different values such as 494 and 720, the exports are usually not measuring the same thing. These are the most common reasons: - More than one crawl on the same day. A scheduled crawl and a manual re-crawl can both be dated October 9. Each crawl has its own results, so the numbers can differ. - Different crawl scope. If the page limit, crawl settings, or the pages found changed between crawls, the totals change too. - Different metrics. A health score is normally shown on a 0 to 100 scale. A value like 494 or 720 is more likely a count, such as the number of issues or pages. Check the column header in each export. - Site changes between crawls. Fixes, new pages, redirects, or server errors during a crawl can all change the results. - Export timing. Exports made at different times may pull from different crawls that share the same date label. 🧾 How to Compare Your Two Exports 1. Open both files and note the exact column names that hold the 494 and 720 values. 2. Check whether each export lists a crawl date and time, not just a date. 3. Compare the total number of pages crawled in each export. 4. Compare the issue counts by category (errors, warnings, notices). 5. In Site Audit, open the audit history and check whether more than one crawl exists for that date. If the page totals differ, the crawls most likely had different scope. If the page totals match but the issue counts differ, the site or the crawl settings probably changed between runs. 🔎 Crawl IDs and Affected URL Lists Crawl IDs and full lists of affected URLs for a specific crawl are not always visible in the exported file. Our team can look up the crawls behind each export and tell you which one each number came from. To speed this up, have the following ready: - Your domain and project name - Both export files, or screenshots showing the two values - The date and approximate time you ran each export - Which score or count you are comparing 🧩 OTTO Changing H2 Headings in the Wrong Elementor Widgets OTTO finds headings on the page and applies suggested H2 changes. Elementor pages can make this harder to predict. A heading with the same text can appear in several places, such as a reusable template, a header or footer, a popup, or a duplicated section. If OTTO matches the wrong one, the change appears in the wrong widget. To investigate, try these steps: 1. Open the affected page in your browser and view the page source. Search for the heading text to see how many times it appears. 2. In Elementor, check whether the heading is part of a global widget, a saved template, or a theme-builder section. 3. Note which widget changed and which one OTTO should have changed. 4. Pause or undo the OTTO change for that page while you investigate. 5. Clear your site cache and any caching plugin, then reload the page to confirm what is really live. To help us fix the targeting, send us the page URL, the original heading text, the heading OTTO should have changed, and a screenshot of the widget that was changed by mistake. 🏷️ Missing Meta Description Tags If OTTO shows a meta description but you cannot find it on your live page, check the following: - Confirm in the page source. Open the live page, view the source, and search for the word description inside the head section. - Clear caches. Caching plugins, your host, or a CDN can keep serving an older version of the page. - Check for SEO plugin conflicts. If another SEO plugin also writes meta tags, one may override or remove the other. - Check the page type. Some templates, archives, or custom page types handle meta output differently from standard pages. - Confirm the change is published. Make sure the change is deployed and not still pending. If the tag is still missing after these checks, send us a list of the affected URLs and tell us which SEO plugin and caching tools your site uses. ✏️ Twitter Description Pencil Not Responding If the pencil icon next to the Twitter Description does not open an edit field, try these steps first: 1. Refresh the page and try again. 2. Clear your browser cache, or open the platform in a private window. 3. Turn off browser extensions, especially ad blockers, and try again. 4. Try a different browser. If it still does not respond, send us the browser name and version, the page URL you were editing, and a screenshot or short screen recording. This helps us reproduce the problem quickly. 📨 What to Include When You Contact Us - Your domain and project name - Both Site Audit exports, with the dates and times they were run - Affected page URLs for the H2, meta description, or Twitter Description issues - Screenshots showing what you expected and what you saw - Your browser and any SEO or caching plugins in use 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔧 Fix Five Common OTTO Configuration Issues

🧭 Overview This article covers five common OTTO configuration issues you may encounter inside Search Atlas. Follow the relevant section below to resolve each problem quickly. ⚙️ 1. OTTO Autopilot Settings Not Saving If your autopilot settings reset after you save them, the most common cause is that the OTTO project is not fully activated. 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3). 2. Open your OTTO project and check the project status badge at the top of the screen. It must show Active before any settings are persisted. 3. If the project is in Draft or Paused status, click Activate Project and wait for the confirmation banner. 4. Re-enter your autopilot preferences — toggle frequency, task types, and priority rules — then click Update Settings. 5. Refresh the page and confirm the settings are retained. If they reset again, deactivate the project, wait 30 seconds, reactivate it, and repeat the save. Important: Autopilot settings are tied to the active project state. Changes made while a project is paused will not be committed to the system. 🕷️ 2. Product Pages Not Being Indexed by OTTO Crawler OTTO may skip product pages due to crawl speed limits, URL exclusion conditions, or the Pages to Crawl cap. 1. Navigate to OTTO SEO → All Sites (SEO Automation) and open the relevant OTTO project. 2. Click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal, and review the URL Exclusion conditions list. Remove any condition that unintentionally matches your product page URL structure (for example, a Contains condition matching /products/ or ?variant=). 3. Check Pages to Crawl and raise the limit if your catalogue is large, so the crawl is not cut short. 4. Under Crawl Speed (pages per second), use a lower speed if your store runs on Shopify or a similar platform. This reduces request frequency to avoid server-side blocking while ensuring full product catalogue coverage. 5. Click Update Settings, then trigger a recrawl using the Recrawl Site button in OTTO SEO → Site Audit → Overview (Website Overview). 6. Allow up to 24 hours for large catalogues. Monitor progress in the Crawl Log panel. Tip: If products are behind a login or age gate, OTTO cannot crawl them. Ensure the URLs you want indexed are publicly accessible. 🔗 3. GSC Account Not Connecting in OTTO Settings A mismatch between the Google account used for GSC and the account linked to your Search Atlas workspace is the most frequent cause of connection failures. 1. Go to Settings → Integrations in the left sidebar. 2. Under Google Search Console, check which Google account is currently authorised. The email shown must exactly match the Google account that owns or has full access to your GSC property. 3. If the accounts do not match, click Disconnect, then Connect GSC and sign in with the correct Google account. 4. After authorising, use the Property dropdown to select the exact GSC property that corresponds to your website. Note that https://www.example.com and https://example.com are treated as separate properties in GSC — select the one that has verified data. 5. Click Confirm Connection. A green status indicator confirms the link is active. Note: If you manage multiple sites, repeat this process inside each OTTO project individually. GSC connections are not shared across projects. 🔥 4. Wildfire Community Backlinks Being Auto-Deployed Without Approval By default, Wildfire can be set to auto-deploy approved link opportunities. If links are going live without your explicit review, the auto-deployment control needs to be adjusted. 1. Navigate to OTTO SEO → All Sites (SEO Automation) and open your OTTO project. 2. Select the Wildfire tab, then open Deployment Settings. 3. Locate the Auto-Deploy Mode toggle. If it is set to On, all opportunities that meet your minimum score threshold will deploy automatically. 4. Switch Auto-Deploy Mode to Off to require manual approval for every link before it goes live. 5. Alternatively, keep auto-deploy enabled but raise the Minimum Quality Score threshold to a higher value (for example, 70 or above) so only high-confidence opportunities are deployed without review. 6. To review links already deployed without approval, go to the Deployed Links log and use the Retract option next to any link you want removed. 7. Click Save Deployment Settings to apply your changes. Best practice: Set auto-deploy to Off when you first set up Wildfire and only enable it after you have reviewed several batches and are confident in the quality scoring for your niche. 📊 5. PPC Keyword Operations Stuck in Pending Status PPC keyword tasks remain in pending status when the Google Ads account is not properly connected or when the account permissions are insufficient. 1. Go to Settings → Integrations in the left sidebar. 2. Under Google Ads, check the connection status. If it shows Not Connected or Expired, click Connect Google Ads and complete the OAuth flow using the Google account that has Standard or Admin access to your Ads account. 3. After connecting, select the correct Ads Account ID from the dropdown. If you manage multiple accounts, ensure you select the account that contains the campaigns you want OTTO to optimise. 4. Return to the PPC Keywords panel and check whether any pending operations now show a Processing or Completed status. Allow up to 10 minutes for the queue to clear after reconnecting. 5. If operations remain stuck after reconnecting, click the three-dot menu next to a pending task and select Retry. If the retry fails with an error code, note the code and contact support. Note: Read-only Google Ads access will cause all write operations — such as adding keywords or adjusting bids — to fail. The connected account must have Standard access or higher. 💬 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 SEO Health Score Volatility and Exclude Pages from OTTO Crawls

🔍 Why Your SEO Health Score Changes After Fixing Issues Your SEO Health Score is calculated by a continuous audit, not a one-time snapshot. Every time OTTO crawls your site, it re-evaluates all pages against the latest SEO rules. This means the score can shift up or down even after you have fixed issues — and that is expected behavior, not a bug. Common reasons your score may show more issues after a fix: - New pages were added — freshly published or indexed pages are crawled and audited automatically. - Template-driven issues surfaced — if your site uses templates (e.g., WooCommerce product pages, archive pages), a single template problem can multiply across hundreds of URLs in one crawl cycle. - Rule updates — Search Atlas periodically refines its SEO audit rules, which can surface issues that were previously uncategorized. - Previously skipped URLs — OTTO discovers new URLs over time as your sitemap or internal links grow. The score reflects the real-time health of everything OTTO can see. If the number of detected issues rises, focus on which issue types are flagged rather than reacting to the score alone. Fixing one high-impact template issue can resolve hundreds of individual instances at once. 🚫 How to Exclude Pages from OTTO Crawls Excluding low-value or template pages from OTTO crawls prevents unnecessary credit consumption and keeps your audit results focused on pages that matter. The supported method is OTTO's URL Exclusion conditions, configured in your project's OTTO SEO Settings. ⚙️ Exclude Pages with URL Exclusion Conditions This is the fastest method and does not require any changes to your website. 1. In the left sidebar, click OTTO SEO → SEO Automation (All Sites) (URL: /seo-automation-v3). 2. Select your project (e.g., designoneprinting.com) from the project list. 3. At the top of the project overview, click the Autopilot / Smart Crawl card to open the OTTO SEO Settings modal. You can also reach it from the All Sites table by clicking the Smart Crawl status text on your site's card. 4. Scroll to URL Exclusion conditions and click + Add condition. 5. Set the condition to Exclude all URLs that Contains or Start With the text you want to skip — for example, Contains /shop/page/ excludes all paginated shop pages. 6. Click Update Settings. Exclusions take effect on the next crawl cycle. Best for: Quickly excluding specific URL patterns without touching your website files. ⚠️ What Does NOT Exclude Pages from OTTO Two approaches are often recommended in general SEO guides, but neither one excludes pages from OTTO: - Robots meta tags (noindex) — OTTO's crawler does not treat a noindex tag as an exclusion. A page carrying noindex is still crawled and can still receive OTTO optimizations. Use URL Exclusion conditions instead. - robots.txt — OTTO ignores robots.txt unless Crawl Criteria is set to Respect robots.txt in the OTTO SEO Settings modal. Even when it is enabled, robots.txt affects every crawler that respects the file — Google included — not just OTTO. For OTTO-specific control, use URL Exclusion conditions. Tip for designoneprinting.com users: If your print-preview or product-configurator pages are generating repeated audit issues, add URL Exclusion conditions for those paths (for example Contains /print/ or your configurator path), then re-run the audit and confirm the tracked page count drops. 💳 Understanding OTTO Credit Usage OTTO credit consumption follows a pattern that surprises some users: the first crawl of a project is the heaviest. Here is why and what to expect: - Initial crawl: OTTO discovers and audits every accessible URL on your site. If your site has 500 pages, all 500 are crawled and credits are consumed upfront. - Subsequent crawls: OTTO uses incremental crawling where possible, prioritizing changed or newly discovered pages. Credit usage typically drops after the first cycle. - Template pages multiply costs: A site with 10 product templates but 300 product pages will crawl all 300 URLs. Excluding template-driven pages before the first crawl saves the most credits. - Crawl frequency: More frequent crawl schedules consume more credits. If credit usage is a concern, reduce crawl frequency in your project settings until exclusions are configured. To maximize credit efficiency, set up your URL exclusions before triggering a manual crawl or enabling an automatic crawl schedule on a new project. ✅ Quick Reference — Which Method Should I Use? - Excluding pages from OTTO: URL Exclusion conditions in OTTO SEO Settings (the method above). - noindex tags: never exclude a page from OTTO. - robots.txt: ignored by OTTO unless Crawl Criteria is set to Respect robots.txt — and then it affects all respectful crawlers, not just OTTO. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Background Repolling Fixed After Navigation

A background repolling issue that persisted after customer frontend navigation has been fixed as of the 2026-07-21 platform release (CB-1191). The platform no longer performs unnecessary background data requests after you move between pages. ✨ What's New Previously, background repolling processes continued running even after navigating away from the originating page in the platform. This caused unnecessary network activity and could result in degraded performance — such as slower page loads or data appearing to refresh unexpectedly — while you were using a completely different section of the platform. The fix, shipped as part of the Core / Churn Buster release on 2026-07-21, ensures that background repolling stops as expected the moment you navigate to a new section of the platform. 🛠️ How to Use It No action is required on your end. This fix has been applied automatically to the platform. Simply continue navigating the platform as normal — background processes will now correctly stop when you move between pages. 📋 What to Expect Background repolling will no longer persist after navigating away from a page. There are no changes to the visible interface or your existing workflows. If you previously noticed slower performance or unexpected activity while switching between platform sections, this fix addresses that root cause. 🔍 Troubleshooting Related Issues If you believe you are still experiencing unexpected background activity or performance issues related to page navigation after 2026-07-21, here are steps to help identify and report the problem: 1. Note the specific page or section where you observed the issue (e.g., which part of the platform you navigated away from and which page you navigated to). 2. Record the exact behavior you noticed — for example, slower performance, unexpected network activity, or data appearing to refresh after navigation. 3. Note the timestamp when the issue occurred so our team can cross-reference platform logs against the CB-1191 deployment. 4. Check if the behavior is reproducible — navigate away from the same page again and observe whether the issue repeats. Having this information ready — particularly the affected page, a description of the behavior, and the timestamp — will allow our team to investigate quickly if escalation is needed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Platform Fixes and Improvements

We've resolved an issue and made an improvement to give you a smoother, more reliable experience. Here's what changed and what it means for you. ✨ What's New OTTO SEO - Background data polling no longer continues after you navigate away from OTTO, preventing unnecessary network activity when you're working elsewhere in the platform. 📋 What to Expect - All of these changes are already live — no action is needed on your end. - If you previously encountered any of the behaviors described above, they should now be 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.

🔧 OTTO SEO & Crawl Monitoring Bug Fixes

The 2026-08-26 release resolves six usability and display issues across OTTO SEO and Crawl Monitoring. All fixes are live and apply automatically — no action is needed on your end. 🕷️ Crawl Monitoring Fixes - Tab switching now works correctly: The Average Response Time and Total Download Size tabs in Crawl Monitoring previously appeared clickable but did not switch the displayed data. Both tabs now respond correctly and load their respective content. - Clearer empty state when Crawl Monitoring is not installed: The previous experience showed a dismissible pop-up and empty data boxes when Crawl Monitoring had not yet been set up. This has been replaced with a persistent not-installed banner that makes the setup status immediately obvious and stays visible until installation is complete. - Installation Guide subtitle corrected: The subtitle shown in the Crawl Monitoring Installation Guide was incorrectly describing a different feature. It now accurately reflects Crawl Monitoring. 📡 Live Monitoring Fix - Alert count wording corrected: The alert count in Live Monitoring now uses correct singular and plural grammar — for example, 1 Alert Detected instead of 1 Alerts Detected. ⚙️ OTTO SEO & Audit Fixes - XML Sitemaps modal search results no longer persist: When closing and reopening the XML Sitemaps modal inside OTTO SEO and Audit, previous search results were incorrectly carried over. The modal now resets cleanly each time it is opened. - Quota top-up modal wording corrected: The OTTO quota top-up modal displayed per sites, which was grammatically incorrect. This has been updated to read per site. ℹ️ What You Need to Do No action is required. All fixes from this release are applied automatically across your account. If you were affected by any of the issues described above, they should now be resolved. If a problem persists, please let us know. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🐛 Search Atlas Homepage Error Now Fixed

We resolved an issue where the Search Atlas homepage was displaying an unexpected error, preventing users from accessing the platform normally. The homepage now loads as expected. 🛠️ What Was Fixed Some users encountered an unexpected error when visiting the Search Atlas homepage, which blocked access to the platform. This issue has been resolved and the homepage now works correctly for all users. 📋 What to Expect The Search Atlas homepage should load without any errors. If you previously bookmarked a specific page or were redirected due to the error, simply navigate back to the homepage and it will load as normal. No changes to your account or settings were made as a result of 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 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 Avatar Menu (👤) 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.

🔍 OTTO Searched URL Field Blank

🔎 What the field does In OTTO SEO, the Searched URL field accepts a page or image URL and looks for matching Image Alt Text issues. 🧭 Where to find it Open OTTO SEO from the left sidebar, then locate the URL search field. ✍️ How to search a URL 1. Enter the complete URL, including https:// or http://. 2. Confirm the URL points to a page or image that OTTO can access. 3. Submit the search and allow a few moments for results to load. For example: https://example.com/page or https://example.com/image.jpg. ⚠️ Why the field may stay blank A known OTTO issue can cause the field or results to remain blank or continue loading, even when a full URL is entered. This may happen because the search request is not processed correctly by the page. 🛠️ What to try - Check that the URL is complete and contains no extra spaces. - Try a different page or image URL. - Refresh the OTTO SEO page and search again. - Use the latest version of your browser. If the field remains blank or spins indefinitely after these steps, the issue may require a product fix rather than a change to your URL. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Troubleshoot OTTO Edits Not Live

🔍 Confirm the change was deployed Open OTTO SEO from the left sidebar, then review the affected project, page, and recommendation. Confirm the edit shows as deployed, not drafted, pending, or awaiting approval. If you changed schema or another item after the original deployment, deploy the updated change again. Editing a previously deployed item does not always publish the new version automatically. 🔗 Check the connected delivery method OTTO delivers changes through the connection configured for your project, such as the OTTO WordPress plugin. Confirm the connection is active and installed on the same website and environment as the affected page. For a Go High Level website, verify that the connected delivery setup is attached to the correct domain and that the page is published in Go High Level. Also confirm the page was not replaced, duplicated, or moved to another funnel or subdomain after the OTTO edit was deployed. ⚙️ Verify project engagement Make sure the project is engaged and that OTTO is enabled for the affected site. If the project or delivery connection was recently paused, reconnected, or changed, deploy the edit again after confirming the current configuration. 🧹 Clear caching and conflicting changes Caching can make an older version of a page appear live. Clear or bypass caches in Go High Level, your CDN, hosting layer, browser, and any SEO or optimization tools. Then open the page in a private browser window. Check for other tools or custom code that may overwrite title tags, meta descriptions, schema, or page content after OTTO applies its changes. Temporarily disable conflicting automation only if it is safe for your site, then test the page again. 🧪 Verify the live page directly Do not rely only on the status shown in the OTTO dashboard. Open the affected URL on the public site and inspect its live HTML source. Search for the expected title, meta description, schema, or other deployed content. Compare the live HTML with the intended OTTO edit. If the expected code is present but the dashboard reports that it is not live, the status may be inaccurate. If it is absent, continue checking the delivery connection, page URL, and caching layers. 📄 Check the exact URL and page version - Confirm the deployed URL matches the live canonical URL, including protocol, subdomain, path, and trailing slash. - Make sure redirects are not sending visitors to a different page. - Check that the page is published and accessible without a login or preview link. - Confirm the live page is not using a different template or location than the page selected in OTTO. ✅ When to contact support Capture the affected URL, the OTTO edit, deployment time, delivery method, and a copy of the live HTML showing the missing change. This information helps the team determine whether the issue is caused by delivery, caching, a conflicting tool, or an incorrect live-status report. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Brand Vault Update Issues

🔍 What is happening? Brand Vault updates are processed through the Search Atlas dashboard or API. After you submit an update, the system may take time to ingest and index the information. During this process, the displayed status may be delayed or may not accurately reflect the latest progress. If the update has been pending for several days, it may be an indexing-status issue rather than a failed update. ✅ Check the update status 1. Open the Brand Vault area in the Search Atlas platform. 2. Review the latest update message and timestamp. 3. Refresh the page and confirm whether the new information appears. 4. Allow additional processing time if ingestion is still in progress. ⚠️ About “Please try again in a few minutes” A recurring Brand Vault update failure showing “Please try again in a few minutes” was tracked as CG-1339. That issue is marked Done. If you still see this message, refresh the platform and try the update again once. Avoid repeatedly submitting the same update while processing is underway. 📊 Why the status may look incorrect A separate improvement to make Brand Vault indexing status clearer and non-blocking is currently In Development under issue CG-3900. Until this improvement is released, the status shown in the platform may not update immediately even when ingestion is continuing. 🧾 Check your case status For an update tied to your specific account or case, include the approximate submission date, the message displayed, and whether the new Brand Vault information appears anywhere in the platform. The current status of your individual case is the best source for confirming whether additional action is needed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Resolve OTTO SEO WordPress Detection

🔍 What the detection error means OTTO SEO should recognize an active, connected WordPress plugin so it can sync approved SEO changes, such as title tags, to your website. A message such as “OTTO not found” or “No WordPress site detected” can appear even when WordPress is connected correctly. The error does not necessarily mean your connection is missing. It may indicate that OTTO SEO has not yet confirmed the plugin, the connection needs to be refreshed, or your site is running a cached version of the plugin connection. ✅ Confirm the correct OTTO setup 1. In Search Atlas, open AI SEO → OTTO SEO from the left sidebar. 2. Confirm that the correct project and domain are selected. 3. Check that the WordPress plugin is installed and active on the matching website. 4. Make sure you are checking the same domain in WordPress and Search Atlas, including the correct HTTPS version and any www or non-www variation. You do not need to look for an option named OTTO pixel on the OTTO SEO page. WordPress detection is based on the connected OTTO WordPress plugin, not a separate pixel setting. 🔄 Refresh the WordPress connection 1. Log in to the WordPress website with administrator permissions. 2. Open the installed OTTO SEO plugin and confirm it is active. 3. If an update is available, update the plugin and save its settings. 4. In Search Atlas, return to AI SEO → OTTO SEO and allow the project to reload. 5. Run the available scan or refresh action, then check whether the detection message has cleared. If the plugin was recently installed, activated, updated, or reconnected, wait a few minutes before scanning again. This gives the platform time to verify the connection. 🧹 Check common WordPress blockers - Temporarily clear the WordPress, server, CDN, and security-plugin caches. - Confirm that a firewall or security plugin is not blocking requests from Search Atlas. - Check that WordPress REST API access is available. Security settings that disable or restrict REST API requests can prevent detection. - Verify that the site is publicly reachable and does not require a maintenance-mode login. - Make sure only one intended OTTO SEO plugin connection is active for the domain. 📊 Verify that syncing works After the site is detected, select an available OTTO SEO fix, such as a title tag recommendation, and use the sync or apply action. Then confirm the change in WordPress. If detection succeeds but syncing still fails, refresh the connection and repeat the test with one fix before applying additional changes. 🚨 When to request help If the error continues after these checks, note the project name, domain, WordPress version, plugin status, and the time of your latest connection attempt. Also include a screenshot of the error and whether the site uses a CDN, firewall, or caching plugin. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix Lead Capture Widget Testing Errors

🔍 What the error means When testing the Site Analysis lead capture widget, guests may see an error such as “Logo Invitation Required — Registration on this domain is by invitation only.” This means the widget is currently restricting unauthenticated visitors from submitting a lead. ⚙️ Why this happens The widget currently works for authenticated visitors, but guest submissions can fail because of a known product issue tracked as WL-476. The issue is in development. ✅ How to test the widget 1. Sign in to Search Atlas. 2. Open the page containing your Site Analysis lead capture widget. 3. Test the widget while authenticated. 4. Submit the form and confirm that the lead is recorded as expected. 🚫 What you cannot change There is currently no documented customer-side setting that removes the invitation-only restriction for guest visitors. Changing the widget configuration or domain settings will not resolve this known issue. 📌 Recommended next steps - Use an authenticated Search Atlas session when testing the widget. - Do not treat the invitation error as a problem with your form data or domain setup. - Retest guest submissions after the issue is resolved. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Troubleshooting Blog Image Validation

This error means the platform could not retrieve or read the image file during validation. Replacing the file with a clean, locally saved copy usually resolves the issue. 🛠️ Step-by-Step 1. Save the image to your device and open it to confirm that it loads correctly. 2. Create a fresh copy in a standard image format such as JPG or PNG. Follow any format or size limits shown by the upload control. 3. Rename the copy using simple letters and numbers, then upload that new file instead of the original. 4. Wait for the upload to finish completely before continuing or saving the blog. 5. If the error returns, try a smaller version of the image or upload a different known-good image to determine whether the issue is limited to the original file. ✅ How to Confirm It Worked The image should display a preview or thumbnail after uploading, and the validation message should disappear. Confirm that the image remains visible in the blog draft after saving or reopening it. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Publication Queue Removal Bug Explained

🔍 What Is This Issue? A system bug caused some posts to be removed from the publication queue even after they had been successfully published on time. This affected customers who completed their posts within the required window but were incorrectly flagged, triggering an automated removal from the queue. If this happened to you, your post was published — the removal was a system error, not a reflection of your performance or eligibility for payment. ⚙️ Why Did This Happen? Our publication queue system uses an automated pipeline to track post status and timing. A bug in this pipeline caused the system to incorrectly remove some posts from the queue even though they had been successfully published on time. Our engineering team identified the issue and worked to resolve it. ✅ What Has Been Fixed? Our team has investigated and resolved the underlying system bug responsible for the incorrect queue removals. Affected posts were reviewed and corrected on the backend. 📋 What Should You Do If This Affected You? If your post was published on time but was removed from the queue, follow these steps: 1. Confirm your post is live by visiting the published URL or checking your connected platform (e.g., Google Business Profile). 2. Take a screenshot or note the published date and time as evidence. 3. Have your project name, the affected post details, and any relevant timestamps ready when you reach out so our team can review and correct your queue status promptly. If you need further assistance, open 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 Schema Deployment Failures and AI Suggestion Deletions

🔍 Overview Some customers have reported that schemas approved inside OTTO fail to go live, projects cannot be activated, and AI-generated schema suggestions are automatically deleted shortly after being created. These issues were caused by bugs in the OTTO schema pipeline — both have now been fully resolved through a platform update. This article explains what caused the problems, confirms the current status, and walks you through steps to verify your projects are working correctly. ⚠️ What Was Causing These Issues Two separate but connected bugs affected the OTTO schema pipeline: - AI Schema Generator producing invalid schema suggestions: A bug in the AI schema generation pipeline caused schema suggestions to be automatically deleted shortly after being created, resulting in AI suggestions disappearing without explanation. - Schema deployment failures and project activation blocks: A separate bug prevented approved schemas from going live. In some cases, this also blocked entire projects from activating within OTTO. ✅ Current Status — Issues Resolved Both issues have been fixed at the platform level. The following changes were deployed: - The AI Schema Generator bug that caused suggestions to be automatically deleted has been resolved. New suggestions will no longer be removed unexpectedly. - The bug that prevented approved schemas from going live and blocked project activation has been resolved. No action is required on your end to receive these fixes — they have been applied automatically across all affected accounts. 🔄 Steps to Verify Your Projects Are Working If your projects were affected, follow these steps to confirm everything is functioning correctly: 1. Open OTTO and navigate to the project that was experiencing issues. 2. Check the project activation status. The project should now show as active. If it is still showing as blocked, try deactivating and reactivating OTTO for that project. 3. Navigate to the Schema section within your OTTO project. 4. Review your AI-generated schema suggestions. New suggestions generated after the fix will no longer be auto-deleted. 5. Approve any schemas you wish to deploy and confirm they move to an approved or deployed status within a few minutes. 6. If you had schemas that were deleted during the affected period, you can regenerate them by using the schema generation option within your OTTO project. If you need further assistance, open 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 Content Persisting After Removal

🔍 Overview When OTTO SEO deploys optimizations to your website — such as adding text like "24/7" to a page — it writes those changes through a synchronization layer that operates independently of the page editor. This means that simply editing or deleting the text in your page builder, or even deactivating the Search Atlas plugin, may not be enough to remove the deployed content from your site's frontend. This article explains why this happens and walks you through the correct steps to fully remove OTTO-deployed content. ⚙️ Why Does This Happen? OTTO deploys optimizations by pushing content through a metadata sync process, separate from what you see in your page builder (such as Elementor, Gutenberg, or another editor). Because of this architecture: - Deleting text directly in your page editor may not remove the value OTTO has stored in the background metadata fields. - Deactivating the Search Atlas plugin stops new deployments but does not automatically roll back content that has already been written to your site. - Cached versions of your pages may continue to serve the old content even after changes are made. ✅ How to Fully Remove OTTO-Deployed Content Follow these steps in order to ensure OTTO-deployed content is completely cleared from your site. 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Locate the deployed optimization you want to remove. Find the specific page and the optimization item (for example, the text element containing "24/7"). 3. Un-deploy the optimization by toggling it off or selecting the option to revert/remove the deployment. This is the critical step — it instructs OTTO to clear the metadata fields it originally wrote, rather than leaving them in place. 4. Confirm the change is reflected on your site by visiting the page on the frontend. Allow a few minutes for the update to propagate. 5. Clear your site's cache. If you use a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) or a CDN (such as Cloudflare), purge the cache for the affected page or your entire site to ensure visitors see the updated version. 6. Check your page builder. After un-deploying through OTTO, open the page in your editor and confirm the content no longer appears. If it remains, manually delete it as a final clean-up step. ⚠️ Important Notes - Deactivating the plugin is not the same as un-deploying. Always use the un-deploy action inside OTTO SEO → All Sites (SEO Automation) before deactivating or uninstalling the Search Atlas plugin. - Cloudflare and CDN users: Deployments passing through Cloudflare DNS may take slightly longer to clear. After un-deploying, wait a few minutes and purge your CDN cache before checking the frontend. - Elementor users: In some cases, OTTO's H1 or content optimizations may interact with Elementor's rendering. If you notice display issues after un-deploying, re-save the affected page in Elementor to refresh its output. - Staging or subdomain environments: If you are working on a staging or subdomain setup, note that OTTO deployment behavior on these environments may differ. Contact support if you encounter unexpected persistence on a staging site. 🔄 Step-by-Step Summary 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Find the optimization on the affected page. 3. Un-deploy the optimization through the OTTO interface. 4. Clear your site cache and CDN cache. 5. Verify the content is gone on the frontend. 6. Manually remove any remaining content in your page editor if needed. 💬 Still Seeing the Content? If you have followed all the steps above and the content is still appearing on your site's frontend, there may be a deeper caching or synchronization issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🛠️ Fix OTTO Deployment Count and Freezing Issues

🔍 Overview Some customers experience OTTO deployment count issues or a frozen, unresponsive interface. These symptoms may affect deployment status visibility and prevent normal interaction with OTTO. ⚠️ Common Symptoms - OTTO deployment counts appear incorrect. - The OTTO interface freezes or becomes unresponsive. - Clicks or other interactions stop working. 🛠️ What to Do Because these symptoms can indicate an OTTO platform issue, there is no confirmed self-serve resolution documented for this problem. Avoid repeatedly retrying deployments if the interface is frozen. When escalating the issue, have the affected client or project name, the deployment count shown, the approximate date and time of the issue, a description of what happened before the interface froze, and any screenshots or exact error messages available. Note whether the issue affects one client or multiple clients. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix OTTO Title Tag Deployment Status Not Updating

🔍 Overview Some customers notice that OTTO title tag deployments continue to show as not deployed. This article explains what information to collect when the deployment status does not update so the issue can be investigated accurately. ⚙️ What to Check Confirm which title tag recommendation or URL is affected and note whether the deployment action completed successfully. The available information does not confirm a specific cause or self-serve fix for this status issue. 🚀 When to Contact Support If the status remains unchanged, contact support with the project or site name, the affected URL or URLs, the exact title tag recommendation, the time and date of the deployment attempt, and any error message or confirmation shown. Include a screenshot if available and note whether the issue affects one page or multiple pages. ✅ What Happens Next Support can use these details to investigate whether the deployment was processed and why the displayed status has not updated. Avoid repeating the deployment until the original attempt has been reviewed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Fix OTTO Instant Indexing Silently Disabling

🧭 Overview OTTO's instant indexing may stop dispatching across multiple projects without a visible error. This article explains what to collect when the issue occurs and how to escalate it for investigation. 🔎 Confirm the Issue Check the affected projects and identify whether instant indexing has stopped dispatching across more than one project. Record the project names, the affected URLs, when dispatching stopped, and any error message or status shown in the platform. 📋 Escalation Information This issue requires investigation when instant indexing is silently disabled across projects. Include the affected project names, example URLs, the approximate time the issue began, and screenshots or copied error details if available. Support can use this information to investigate the indexing connection and determine the appropriate restoration steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔍 Fix Duplicate FAQ Sections

🧭 What content1Summary and content8Summary mean These labels identify content summary fields used during article generation. They are not intended to create two separate FAQ sections on the same page. If both fields contain similar questions and answers, the generated article may display duplicate or misplaced FAQ content. This can happen when source instructions, templates, or generated content include overlapping FAQ material. 🔎 How to identify the issue 1. Open Content from the left sidebar. 2. Select Content Genius. 3. Open the relevant generated article or project. 4. Review the article outline and search for repeated FAQ headings, questions, or answers. 5. Compare the content associated with content1Summary and content8Summary. Duplicate content may appear as two FAQ headings, repeated accordion items, or the same questions placed in the middle of the article and again at the end. 🛠️ How to fix duplicate FAQs 1. Keep only one FAQ section in the article. 2. Remove repeated questions and answers from the summary or generation instructions. 3. Make sure each FAQ question is unique and directly related to the article topic. 4. Regenerate the article or edit it manually after removing the duplicate content. 5. Preview the final article and confirm that each question appears only once and that answers display as normal text. ✍️ Prevent the issue in new articles - Use one clearly defined FAQ section in your content brief. - Avoid copying the same FAQ list into multiple summary fields. - Review generated content before publishing, especially after bulk generation. - Check that FAQ formatting uses the available FAQ controls rather than pasted markup or unsupported HTML. - When reworking an existing article, confirm that the original FAQ section is not being retained alongside a newly generated one. ✅ Final publishing checklist - There is only one FAQ heading unless multiple sections are intentionally required. - No question or answer is repeated. - FAQ items appear in the intended location. - Accordion controls, if used, have one arrow per item and readable text. - No raw tags such as <answer> appear in the published content. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛒 Troubleshooting Shopify SEO Title Deployment

This article helps you resolve a common point of confusion: a title tag change shows as "deployed" inside the platform, but you're not sure whether that change actually reached your live Shopify store, or only updated inside your Search Atlas account. 🛠️ Step-by-Step 1. Locate the specific page or product whose title tag you edited and note the exact new title text you expect to see. 2. Check the deployment status for that page inside the platform. A status of "deployed" means the system sent the update to Shopify, not that Shopify has necessarily saved and rendered it yet — treat this as a signal to verify, not final proof. 3. Confirm your Shopify integration is properly connected by checking your integration or connection settings within the platform. If the connection shows as disconnected, expired, or requires re-authentication, changes will show as deployed on the Search Atlas side but will never reach Shopify. 4. If the connection looks healthy but the title still hasn't updated, try re-deploying that single title tag change rather than waiting, since some changes can silently fail without an error being surfaced. 5. If the title still does not update after a re-deploy, check whether the page in question is cached by Shopify's theme or a CDN/caching app, since cached pages can display an old title even after the underlying data has changed. ✅ How to Confirm It Worked 1. Open the live page directly on your Shopify storefront (not inside Search Atlas) in a new private/incognito browser window to avoid cached results. 2. View the page source (right-click and select "View Page Source" or use your browser's developer tools) and search for the <title> tag to see the exact text Shopify is currently serving. 3. Compare this exact text to what you set inside the platform. If they match, the change has been successfully written to Shopify and deployment is confirmed. 4. If the live title still doesn't match after confirming the integration connection and re-deploying, this points to a caching or theme-level issue on the Shopify side rather than a deployment failure. If you need further assistance, open 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 Meta Title Deployment

🔍 Why your meta title may not change When OTTO cannot reach your website, it cannot deploy the updated meta title. The title may also remain unchanged if the fix has not been deployed, the page is cached, or another system is overriding the title. 🌐 Check whether the domain is reachable 1. Open OTTO SEO from the left sidebar. 2. Go to OTTO SEO → Site Audit and review the site or domain status. 3. Confirm that the affected URL loads normally in a private browser window and does not redirect to a login page, maintenance page, or error page. Also check that DNS, SSL, firewall, and security settings are not blocking Search Atlas or OTTO requests. Cloudflare or another security service may require an allowlist rule for the OTTO installation. ⚙️ Confirm the OTTO installation 1. Open OTTO SEO → Site Audit → Installation Guide. 2. Confirm that the installation method shown for your site is complete and active. 3. Use the available installation check to verify that OTTO is detected on the live site. 4. If the installation is not detected, review the instructions and publish the required code or connection again. If your site uses React, another JavaScript framework, or aggressive Cloudflare rules, the installation may need an alternative method. Verify the title in the page source or server-rendered HTML when possible, not only in the browser inspector. 🚀 Deploy the meta title again 1. Open OTTO SEO from the left sidebar. 2. Open the page containing the meta title recommendation. 3. Confirm that the proposed title is correct and save the change. 4. Choose the deployment option and wait for the deployment status to complete. 5. Refresh the page and confirm that the fix shows as deployed or live. If OTTO reports that the title is already optimal, the existing title may match the generated recommendation. In that case, no visible change is expected. ✅ Verify the live title 1. Open the published URL in a private browser window. 2. View the page source and find the <title> element. 3. Compare the live title with the title configured in OTTO. 4. Check the URL in Google Search Console or another search result only after the live page is correct, because search engines may show a cached or rewritten title. 🧹 Clear caching and conflicting settings Clear your CDN, Cloudflare, hosting, and website cache after deployment. If the title still does not match, check SEO plugins, themes, templates, and custom code that may replace the title after OTTO applies its change. Make sure only one system controls the page title. 💬 Get help with an unreachable domain If you need further assistance, open 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 Bulk Schema Deployment Issues

🔍 Understanding the Issue OTTO bulk deployment may not apply all schema suggestions, even when the deployment appears to complete. This can leave some suggestions showing as undeployed. ✅ What to Do 1. Note the number of schema suggestions that remain undeployed. 2. Record the affected website and, if available, the specific pages or schema suggestions that were not deployed. 3. Note when the bulk deployment was attempted and any error or confirmation message that appeared. 4. Contact support with the website name, remaining undeployed count, affected URLs, deployment timestamp, and exact message shown. Support can investigate the deployment status and determine why the suggestions were not applied. ⚙️ What to Expect This issue may require investigation of the deployment process. Providing the affected website, exact URLs, remaining count, timestamp, and any displayed error helps the team review the failed or incomplete deployment. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🔧 Fix OTTO Pixel Not Recognized on Drupal

🧭 Overview After installing the OTTO pixel on a Drupal site, Search Atlas may still show the code as unrecognized. Standard cache clearing alone is often not enough — Drupal requires a full cache flush to propagate header changes. This article walks you through every troubleshooting step to get your OTTO pixel recognized quickly. ✅ Before You Begin Confirm the following before troubleshooting: - You have admin access to your Drupal site and the Search Atlas platform. - Your OTTO pixel code has been copied exactly from Search Atlas — no extra spaces or characters. - You are editing the correct site in Search Atlas: navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3) and confirm the domain shown matches your Drupal site. 📋 Step 1: Verify the Pixel Is in the Correct Location The OTTO pixel must be placed inside the <head> tag of every page on your site, not in the body or footer. In Drupal, the recommended way to do this is through your active theme's html.html.twig file or a dedicated header block, depending on your theme setup. - Open your Drupal admin panel and go to Appearance → your active theme → Edit. - Locate the html.html.twig template (or equivalent header template). - Confirm the OTTO pixel code snippet appears immediately after the opening <head> tag. - Save your changes. If you are using a module such as Head JS, Google Tag Manager, or a custom block to inject header scripts, ensure the OTTO pixel is placed directly in the template file, not inside GTM or any asynchronous script loader, as these can delay or block pixel recognition. 🚫 Step 2: Remove Any Conflicting GTM or Script Loader Code Google Tag Manager and similar tools load scripts asynchronously after the page has already started rendering. This can prevent Search Atlas from detecting the OTTO pixel reliably. - If you previously inserted the OTTO pixel inside a GTM container, remove it from GTM entirely. - Add the pixel code directly to your theme template as described in Step 1. - Double-check that no other plugin or module is moving or deferring scripts in the <head> tag. 🗑️ Step 3: Flush All Drupal Caches (Critical Step) This is the most common reason the OTTO pixel remains unrecognized after installation. Drupal caches rendered HTML, Twig templates, and asset aggregations aggressively. A standard cache clear may not rebuild all layers. You must perform a full cache flush. Method A — Drupal Admin UI (Recommended): 1. Log in to your Drupal admin panel. 2. Go to Configuration → Development → Performance. 3. Click Clear all caches. 4. Wait for the confirmation message before proceeding. Method B — Drush Command Line (More Thorough): 1. Connect to your server via SSH. 2. Navigate to your Drupal root directory. 3. Run the command: drush cr (cache rebuild). This rebuilds all Drupal caches, including Twig compiled templates. 4. If you use a CDN or reverse proxy (such as Cloudflare, Varnish, or Nginx caching), purge the cache at that layer as well. Method C — Hosting-Level Cache: - If your hosting provider (e.g., Pantheon, Acquia, WP Engine for Drupal) has its own caching layer, log in to your hosting dashboard and purge or flush the site cache separately. This step is required even after running Drush. 🔍 Step 4: Verify the Pixel Is Live on Your Site After flushing all caches, confirm the pixel is visible in your page source before asking Search Atlas to re-verify: 1. Open your website 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 otto or the beginning of your pixel code snippet. 4. Confirm the code appears inside the <head> section of the source. If the code does not appear in the page source, the template change was not saved correctly or a caching layer is still serving an old version of the page. Repeat Steps 1 and 3. 🔄 Step 5: Re-Verify in Search Atlas 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Locate your connected site and open its OTTO settings. 3. Click the Verify or Check Pixel button to trigger a fresh detection scan. 4. Allow up to two minutes for the verification to complete. If verification still fails after completing all steps above, your site may have a Content Security Policy (CSP) header blocking external scripts, or a module may be stripping unrecognized code from the <head> tag. Check your Drupal security modules (such as Security Kit) for script restrictions. ⚠️ Common Mistakes to Avoid - Clearing cache without flushing: Drupal's "Clear cache" button does not always rebuild Twig templates. Always use Drush cr or the Performance page flush for header changes. - Inserting the pixel via GTM: GTM-loaded scripts are not reliably detected. Place the pixel directly in your theme template. - Forgetting CDN or proxy cache: Changes to your HTML will not be visible until the CDN cache is also purged. - Editing the wrong theme: Drupal may have a base theme and a sub-theme. Confirm you are editing the active sub-theme template. 💬 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 Heading Deployment JavaScript Errors

🔍 What Is Happening? After OTTO deploys a heading optimization on your site, you may notice one or more of the following symptoms on your homepage or other pages: - JavaScript errors appearing at the top of the page - Broken page layout or malformed HTML structure - Heading text displaying HTML entities (e.g., & instead of &) - Elementor or other page builders rendering incorrectly These issues are caused by a conflict between the OTTO deployment and how your site processes heading tags. The deployment can inject code into the <head> tag in a way that breaks the expected HTML structure, leading to rendering errors on the frontend. ⚠️ What to Expect This is a known bug tied to how OTTO heading optimizations are injected into certain site configurations. Because the root cause requires investigation on the backend, there is no guaranteed self-serve workaround. Attempting to manually undo or reconfigure OTTO settings without guidance may not fully resolve the issue and could introduce additional conflicts. Our support team will need to investigate your specific site setup to identify what is causing the malformed injection and determine the correct fix. 📋 What to Have Ready When You Contact Support To help us resolve this as quickly as possible, please gather the following before reaching out: - Project name in Search Atlas where the OTTO heading deployment was made - URL(s) of the affected page(s) showing the JavaScript errors or broken layout - Exact error message(s) from the browser console (open with F12 → Console tab) - Timestamp of when the heading optimization was deployed or when you first noticed the issue - Page builder or theme in use (e.g., Elementor, Divi, block editor) - OTTO installation method currently active on your site (if known) If you need further assistance, open 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 Slowdown on Duda Sites

🔍 Overview When you install the OTTO SEO tracking pixel on a Duda website, you may notice the site loads significantly slower or returns errors shortly after the script is added. This article explains what is known about this issue and how to get it resolved. ⚠️ Why This Happens Slowdowns after adding the OTTO pixel to a Duda site have been reported by customers, including those using white-label domains. The exact cause can vary by account and site configuration. Because this is a confirmed bug category, the underlying issue typically requires investigation by our support team rather than a self-serve fix. Common symptoms include: - Dramatically increased page load times after adding the pixel - Browser console errors or network request failures - The site appearing to hang or time out before rendering 🛠️ What to Do Next Since this is a bug that requires backend investigation, please do not attempt to re-add or rearrange the pixel script in the meantime, as this may complicate troubleshooting. Instead, gather the following information before contacting support so our team can investigate quickly: - Your site URL — the full Duda site domain where the slowdown occurs - Your Search Atlas account email or workspace name - Whether you are using a white-label domain — yes or no, and the white-label domain if applicable - The exact symptoms you are seeing — for example, load time increase, specific error messages, or timeout behaviour - When the slowdown started — approximate date and time, and whether it began immediately after installing the pixel - Any browser console error messages — copy the exact text if possible Having these details ready will allow our team to identify the root cause and apply the appropriate fix on the backend without unnecessary back-and-forth. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Duplicate Anchors, Auto-Deploy & Exclusion Bugs

🔍 Overview Some customers have encountered three related issues with OTTO SEO: hundreds or thousands of identical anchor text instances being generated across a site, changes being auto-deployed without approval, and URL exclusion rules not filtering the correct pages. This article explains what is happening with each issue and what information to have ready when contacting support. ⚠️ Issue 1 — Duplicate Anchor Text Some sites have experienced OTTO generating a very large number of identical anchor text suggestions across multiple pages. This is a known bug. It is not something you can resolve by changing settings on your end. What to have ready when escalating: - The name of the affected project or site. - A rough count or screenshot showing the duplicated anchor text suggestions. - The specific anchor phrase(s) that are being repeated. - The timestamp or date when you first noticed the issue. ⚠️ Issue 2 — Unwanted Auto-Deployments Some customers have reported that OTTO changes appear to have been deployed without a deliberate deploy action, or conversely that the dashboard shows a deployed status but the changes are not present on the live site. This is a known platform bug and cannot be self-resolved through the interface. What to have ready when escalating: - The name of the affected project or site. - A description of what you expected to happen versus what actually occurred (e.g., changes deployed without approval, or status shows deployed but pages are unchanged). - The URLs of specific pages affected. - Any timestamps or date ranges when the unexpected behavior was observed. ⚠️ Issue 3 — URL Exclusion Filter Not Working Correctly Some customers have found that URL exclusion rules are matching pages that were not intended to be excluded. This appears to be related to how the exclusion logic matches URLs and is a known bug. It cannot be fully corrected by adjusting your exclusion rules alone. What to have ready when escalating: - The name of the affected project or site. - The exact exclusion rule(s) you entered. - The URLs that were incorrectly excluded or incorrectly included as a result. - Screenshots of your current exclusion settings if possible. 📌 Next Steps All three of these are known bugs currently being investigated by the engineering team. Please do not attempt workarounds that involve approving or deploying large numbers of suggestions manually, as this may make it harder to diagnose the underlying issue. Gather the information listed above for whichever issue applies to you before reaching out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Empty OTTO AI Recommendations After Crawl

🔍 Overview After a successful site crawl, OTTO should automatically generate AI-powered SEO recommendations for Page Titles, Meta Descriptions, and Image Alt Text. In some cases, these fields remain blank even though the crawl appears to have completed without errors. This happens when the recommendation-generation pipeline fails silently after the crawl finishes — the crawl itself succeeds, but the downstream process that feeds page data to the AI does not complete as expected. This article explains what may be happening and what to have ready when you contact our team for assistance. ⚠️ Why This Happens Empty AI recommendations after a completed crawl typically indicate a failure in the pipeline that runs after the crawl finishes. The crawl itself may report as successful, but the stage responsible for generating recommendations may not trigger or complete correctly. This is a backend issue that requires investigation by our support team. ✅ How to Confirm the Issue Before reaching out, verify the following so you can provide accurate details to our team: 1. Open your OTTO project and confirm that the crawl status shows as completed. 2. Navigate to any page-level issue category — such as Page Titles, Meta Descriptions, or Image Alt Text. 3. Check whether AI-generated suggestions are missing across all pages or only on specific pages. 4. Note approximately when the crawl was completed and whether this is the first time this has occurred for this project. 🔄 What to Have Ready When You Escalate Because this issue involves a backend pipeline failure, our team will need to investigate on your behalf. To help us resolve it as quickly as possible, please have the following information ready: - Project name — the exact name of the OTTO project affected. - Crawl completion timestamp — the date and time the crawl finished. - Scope of the issue — whether all pages are missing recommendations or only a subset. - Any error messages — copy the exact text of any error or warning displayed in the interface. - Whether this has happened before — note if previous crawls on this project generated recommendations successfully. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Schema Not Showing in Rich Results Test

🧩 Overview When OTTO deploys schema markup to your site, it should be visible in Google's Rich Results Test tool within a short time. If your schema is marked as published in the OTTO dashboard and the OTTO Pixel is confirmed active, but the schema still does not appear in the Rich Results Test, this may indicate a service-level deployment problem that requires engineering review. This article explains what to check first, how to identify a backend issue, and exactly when to escalate to our team. ✅ Step 1 — Confirm OTTO Is Active and Schema Is Published 1. Log in to your Search Atlas account and open your OTTO dashboard for the site in question. 2. Confirm that the OTTO Pixel is active for the site. 3. Verify that the relevant schema type is in a published state — not pending or draft. 4. Note the approximate date and time the schema was published so you can reference it during escalation. 🌐 Step 2 — Check the Live Page Source The Rich Results Test tool reads the page as Google sees it. Before assuming a rendering issue, verify that the schema is actually present in your page's HTML source: 1. Open the target URL in a browser. 2. View the page's HTML source (the method varies by browser, but most browsers allow this from the browser menu or a keyboard shortcut). 3. Search the source for application/ld+json. 4. If no schema block appears, the markup is not reaching the page — this confirms a deployment-level failure, not a Google indexing delay. Important: If the schema is absent from the page source even though OTTO shows it as published, do not continue with further client-side troubleshooting. Proceed directly to the escalation step below. 🔎 Step 3 — Run the Rich Results Test If the schema block is present in the page source, run a live test to check how Google interprets it: 1. Go to Google Rich Results Test. 2. Enter the full URL of the page and run the test. 3. Review the results for detected schema types and any reported errors or warnings. If Google detects the schema here but it still does not appear in search results, this is a normal indexing delay and may take several days. No action is needed beyond monitoring. ⚠️ Escalation Criteria — When to Contact Our Team Stop troubleshooting and escalate right away if any of the following conditions are true: - The schema is marked as published in OTTO but is completely absent from the live page source. - The OTTO Pixel is active and schema is published, yet the schema does not appear after an extended period. - You are seeing inconsistent behavior across pages or schema types that you cannot explain through indexing delays alone. 📋 What to Have Ready When You Escalate To help our team investigate as quickly as possible, please have the following information ready: - The name of the project or site affected. - The specific URL(s) where schema is not appearing. - The schema type(s) that should be deployed (e.g., Article, FAQ, Product). - The date and time the schema was marked as published in OTTO. - Confirmation of whether the schema block is present or absent in the live page source. - Any error messages or unexpected results from the Rich Results Test. If you need further assistance, open 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 Pages With Missing Images and Formatting

🔍 Overview When OTTO SEO deploys changes to your website, most pages update correctly. However, in some cases you may notice that certain pages appear incomplete — with missing images, stripped formatting, or content that looks different from what you see in your CMS. This article explains why this happens and what to have ready when escalating to our support team. ⚙️ Why Pages May Appear Incomplete There are a few known reasons why OTTO-generated pages can show missing images or broken formatting: - Theme or page builder compatibility: Some page builder themes can conflict with OTTO deployments, causing body content — including images and graphics — to be stripped from affected pages. If this has occurred, the pages may remain incomplete until the deployment is corrected by our team. - Pages visible in OTTO but missing from your CMS: OTTO discovers pages by crawling your live website. If a page exists on your site but was not created through your CMS (for example, pages generated by a plugin, third-party tool, or a previous platform migration), OTTO will detect and display it — but your CMS will have no record of it. This means you cannot edit those pages directly inside your CMS. - Cached or incognito discrepancies: In some cases, OTTO audits may flag issues such as missing alt tags or non-optimised images that do not actually exist on the live page. This is often a caching issue. Viewing the page in an incognito or private browser window typically shows the correct, up-to-date state. 🚀 Steps to Take Before Escalating 1. Check your site in incognito mode: Open your browser in a private or incognito window and visit the affected pages. If the images and formatting appear correctly there, the issue is likely a local browser cache. Clear your browser cache and reload the page. 2. Identify pages missing from your CMS: If OTTO shows a page that you cannot find or edit in your CMS, the page exists on your live site but was not created through the CMS. Locate the source of that page — such as a plugin, redirect rule, or external tool — and manage it there. 3. Note the exact pages affected: Make a list of the specific URLs or page names where images or formatting are missing. This will help our team investigate quickly. 📋 What to Have Ready When Contacting Support Because missing images and formatting issues on OTTO-generated pages often require backend investigation, please have the following information ready before reaching out: - The project name and the domain affected - A list of specific URLs where content appears incomplete or images are missing - The page builder or CMS theme your site uses (for example, whether you are using a third-party page builder) - Whether the issue appears in an incognito browser window as well as your normal browser - Any recent changes made to the site around the time the issue began If you need further assistance, open 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 Campaign Creation Success Message Bug

Overview A known backend issue can cause OTTO to display a success message after you attempt to create a PPC campaign, even though the campaign was not actually created. The confirmation message appears as expected, but when you navigate to your dashboard, the campaign is missing. This is a backend bug involving a false campaign creation success message. Because the issue originates in the backend, it cannot be resolved through self-serve steps alone — you will need to contact our support team to have the campaign created correctly. How to Recognise This Issue - OTTO displays a success message or similar confirmation after you attempt to create a campaign. - The campaign does not appear in your OTTO dashboard after the success message. - Refreshing the page does not make the campaign appear. What to Do Because this is a backend bug, our team will need to investigate and resolve it on your behalf. To help us do this as quickly as possible, please have the following information ready before reaching out: - The name of your OTTO project where you attempted to create the campaign. - The approximate date and time of the failed campaign creation attempt. - Any error messages you saw during or after the creation attempt. - Confirmation of whether your Google Ads or PPC account is connected to the project. What Not to Do - Do not attempt to create the same campaign multiple times before speaking with support, as repeated attempts may complicate the investigation. - Do not assume the campaign is live based on the success message alone. Always verify the campaign appears in your dashboard before treating it as active. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress OTTO Installation and Authentication Issues

🔍 Overview Connecting WordPress to OTTO SEO requires two things: the Search Atlas WordPress plugin installed on your site, and a valid Search Atlas account linked during setup. If your site is not connecting or authentication keeps failing, this guide walks you through every step to fix it. ✅ Before You Begin Make sure the following are in place before attempting to connect: - You have admin access to your WordPress site. - You have an active Search Atlas account. - Your WordPress site is live and publicly accessible (not in maintenance mode or behind a login wall). - Your server allows outbound HTTP requests (some managed hosts block these by default). 🛠️ Step 1: Install the Search Atlas WordPress Plugin 1. Log in to your WordPress dashboard. 2. Go to Plugins → Add New. 3. Search for Search Atlas. 4. Click Install Now, then Activate. Important: The plugin does nothing on its own. It must be connected to your Search Atlas account to function. Do not skip Step 2. 🔗 Step 2: Connect WordPress via the OTTO Installation Guide 1. In Search Atlas, go to Left sidebar → OTTO SEO → Installation Guide. 2. Select WordPress as your platform. 3. Follow the on-screen instructions to generate your connection credentials. 4. Copy the credentials provided and paste them into the Search Atlas plugin settings inside your WordPress dashboard. 5. Save your settings and wait for the connection status to update. You can also add or manage connected sites by going to Left sidebar → OTTO SEO → All Sites. ⚠️ Common Reasons Authentication Fails If your site still shows as not connected or authentication is not completing, check each of the following: - Wrong credentials entered: The plugin requires the exact credentials generated in the Search Atlas Installation Guide. Do not use your Search Atlas login username or password here. - Credentials entered in the wrong field: Make sure you are pasting each value into the correct field inside the plugin settings. - Plugin not activated: Verify the plugin is active under Plugins → Installed Plugins in WordPress. - Caching conflict: If your site uses a caching plugin (e.g., WP Rocket, W3 Total Cache), clear the cache after saving the plugin settings. - Firewall or security plugin blocking the connection: Security plugins like Wordfence can block outbound requests. Temporarily disable them to test the connection, then whitelist Search Atlas if needed. - Maintenance mode enabled: Disable any maintenance mode plugin before attempting to connect. - Server-level restrictions: Some hosting providers block external API calls. Contact your host to confirm outbound requests are allowed. - Server limits causing 500 errors: If connecting the plugin fails with a 500 error, your hosting plan may not have enough PHP resources. Ask your hosting provider to raise the PHP memory limit to at least 256MB and the maximum execution time to 300 seconds, then try connecting again. 🔄 Step 3: Re-authenticate If the Connection Breaks 1. Go to Left sidebar → OTTO SEO → All Sites. 2. Find the affected site and check its connection status. 3. If the status shows an error, remove the site and re-add it using the steps in the Installation Guide. 4. Generate fresh credentials and re-enter them in your WordPress plugin settings. 📊 Step 4: Verify the Connection Is Working Once credentials are saved, return to Left sidebar → OTTO SEO → Overview. Your WordPress site should appear as connected. You can then run a scan by going to Left sidebar → OTTO SEO → All Sites and clicking Scan. 💡 Tips to Avoid Connection Issues - Always generate fresh credentials from the Installation Guide — do not reuse old ones. - Check that your WordPress version and PHP version meet the minimum requirements listed in the plugin description. - If you manage multiple sites, connect each one individually through OTTO SEO → All Sites. 🆘 Still Not Connecting? If you have followed all the steps above and your WordPress site is still not authenticating, our team can investigate your specific setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

OTTO Installation Troubleshooting and Site Optimization Guide

Overview OTTO is Search Atlas's SEO automation tool. When installed correctly, OTTO assists with site optimization without disrupting your site's functionality. However, if you notice 404 errors or network issues after installation, this guide will help you identify whether OTTO is a contributing factor and how to resolve it safely. Does the OTTO Script Cause 404 or Network Errors? In most cases, the OTTO script does not directly cause 404 errors or network failures. These errors are typically related to one of the following pre-existing or unrelated issues: - Missing or broken page URLs on your website - Hosting configuration issues - Plugin or theme conflicts triggered independently of OTTO - DNS propagation delays after recent changes That said, it is worth ruling out OTTO as a contributing factor before taking more drastic steps like restoring your site to a prior version. How to Check If OTTO Is the Cause 1. Temporarily pause OTTO: Log in to Search Atlas and navigate to the OTTO section of the platform. Follow the available options to pause or disable OTTO for your connected site. 2. Clear your browser cache and any caching plugins on your website. 3. Test your site by visiting the affected pages. Check whether the 404 errors or network errors persist. 4. If the errors disappear after pausing OTTO, re-enable it and contact support for further investigation. If the errors remain, OTTO is not the cause and you should investigate your hosting environment. Troubleshooting 404 Errors on Your Site Hosting environments can sometimes produce 404 errors due to configuration issues that are unrelated to third-party scripts. Before restoring your site to a prior version, consider the following general approaches: - Check your site's URL and routing configuration to ensure pages and links are set up correctly. - Review recently installed or updated plugins or extensions that may conflict with your site routing. - Check your hosting provider's server status to confirm there are no active outages affecting your hosting plan. - Consult your hosting provider's support documentation for platform-specific troubleshooting steps relevant to your setup. Should You Restore Your Site to a Prior Version? Restoring your site to a prior version is a last resort and should only be done if all other troubleshooting steps have been exhausted and you have confirmed that OTTO is not the source of the issue. Always create a backup before attempting a restore. Need Help? If you are unsure whether OTTO is contributing to your site issues, or if you have completed the steps above and still cannot resolve the problem, please reach out so our team can investigate further. When escalating, have the following ready: your site URL, the exact error message you are seeing, and the approximate time the issue began. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting Common OTTO SEO Issues

🔍 Overview OTTO SEO automates on-page optimizations across your website. While OTTO is designed to work seamlessly in the background, you may occasionally encounter issues such as schema validation errors, rolled-back changes, or unexpected behavior with generated content. This article walks you through the most common problems and how to resolve them. 🗺️ How to Access OTTO SEO To open OTTO SEO, navigate to the Left Sidebar → OTTO SEO → SEO Automation or go directly to /seo-automation-v3 in your platform URL. From this dashboard, you can review active optimizations, check deployment status, and manage OTTO settings for your project. ⚠️ Schema Validation Error: @context Must Use HTTPS One known issue involves a schema validation error where the @context property is set to http://schema.org/ instead of the required https://schema.org/. This can cause your structured data to fail validation in tools like Google's Rich Results Test. To check for this issue: 1. Go to Left Sidebar → OTTO SEO → SEO Automation. 2. Review the schema recommendations or deployed schema blocks for your pages. 3. Look for any @context values that begin with http:// rather than https://. If you spot this error, note the affected pages and contact support using the live chat widget. Our team is actively working on a fix to ensure all generated schema uses HTTPS by default. ↩️ OTTO Rolled Back Meta Data or Keyword Optimizations In some cases, OTTO may roll back previously deployed meta data or keyword optimizations. This can happen when a new project sync, audit refresh, or conflicting rule is triggered. If you notice that optimizations have been undone: 1. Open OTTO SEO → SEO Automation from the left sidebar. 2. Review the deployment history or activity log for the affected pages. 3. Check whether a rollback event is recorded and what triggered it. 4. Re-deploy the affected optimizations manually if needed. If the rollback continues to occur or you cannot identify the cause, reach out via the chat widget for escalation. 🖼️ Image Alt Text: Per-Image Updates An OTTO alt-text fix belongs to one specific image, and deploying it updates only that image — not the whole page or project. Keep this in mind when reviewing alt-text suggestions, as each deployment is scoped to the individual image it was generated for. To deploy an alt-text fix: 1. Navigate to Left Sidebar → OTTO SEO → SEO Automation. 2. Locate the alt-text suggestion for the specific image you want to update. 3. Deploy the fix and allow OTTO to apply the change to that image. ✍️ Generated Content Issues: Headings, Titles, and Meta Descriptions OTTO's content generation should produce headings, titles, and meta descriptions that match your target language and stay within recommended character limits. Known issues that have been resolved include: - Headings or titles being cut off mid-word. - Open Graph (og:) and Twitter meta tags generating under the recommended length. - Generated content appearing in the wrong language. If you are still experiencing any of these problems, verify that your Brand Vault settings and language preferences are correctly configured. You can access Brand Vault from the OTTO SEO page or On-Page Strategy section. If the modal does not open as expected, try refreshing the page or clearing your browser cache before trying again. ✅ General Troubleshooting Steps Before contacting support, try these steps to resolve most OTTO SEO issues: - Refresh the page — Some display issues resolve on reload. - Clear your browser cache — Cached data can cause outdated information to appear. - Check your project's audit status — An incomplete audit can affect OTTO recommendations. - Review your Brand Vault settings — Incorrect brand or language settings can affect generated content quality. - Re-deploy affected optimizations — If changes were rolled back, manually re-deploying may resolve the issue. 💬 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 SEO Disengaged Mode: Fix Unresponsive Interface

What Is OTTO SEO Disengaged Mode? Search Atlas includes an OTTO SEO feature that assists with on-page optimisations in the content editor. When OTTO SEO is disengaged, some users have reported that parts of the interface become unresponsive — buttons appear visible but cannot be clicked, and actions do not register. Common Symptoms - Clicking buttons in the editor produces no response after disengaging OTTO SEO. - Suggested changes are visible but cannot be accepted or dismissed. - The editor area appears interactive but does not respond to input. Steps to Try Before Contacting Support If your interface becomes unresponsive after disengaging OTTO SEO, work through the following steps in order: 1. Hard refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force a full reload, bypassing any cached page state. 2. Clear your browser cache and cookies for the Search Atlas domain, then reload the editor. 3. Re-engage OTTO SEO, then disengage it again. Toggling the OTTO SEO setting off and back on (then off again) can reset the interface state and restore click responsiveness. 4. Try a different browser or an incognito/private window. This rules out browser extensions or local cache as the cause. 5. Reopen the project. Close the current editor tab, navigate back to your project list, and reopen the affected content item from scratch. If none of the above steps restore responsiveness, escalate to our support team. When you reach out, please have the following ready so our team can investigate efficiently: - The name of the project or content item where the issue occurred. - Whether OTTO SEO was manually disengaged or changed state automatically. - The browser and operating system you are using. - A description of exactly which part of the interface stopped responding. - Any steps you already tried (e.g. refreshing, reopening the editor). If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot OTTO SEO Setup and Errors

🔍 Overview OTTO is Search Atlas's AI-powered SEO automation tool. When customers first activate OTTO or deploy its recommendations, they sometimes notice unexpected website behavior — such as broken pages, slower load times, or network-related errors. This article helps you understand what to do if something goes wrong during or after OTTO setup, and how to get help if issues persist. ⚙️ What OTTO Does to Your Site OTTO applies on-page and technical SEO optimizations automatically. If you notice unexpected website behavior after activating or deploying OTTO recommendations, it is worth checking whether the timing of the issue coincides with recent OTTO activity before assuming another cause. If you are experiencing network-level errors (such as 502 or 504 gateway timeouts, SSL failures, or DNS resolution issues), these are likely unrelated to OTTO and should be investigated with your hosting provider. 🚨 Is OTTO Causing My Website Errors? Before assuming OTTO is responsible for an issue, work through this quick checklist: 1. Check the timing. Did the errors begin within minutes of deploying OTTO recommendations? If the issue started hours or days later, OTTO is unlikely to be the cause. 2. Identify the error type. Page-level issues (broken layouts, missing content, redirects) could be related to OTTO changes. Server or network errors (5xx status codes, SSL warnings, DNS failures) are outside OTTO's scope. 3. Test a specific page. If only certain pages are affected, check whether OTTO made changes to those pages specifically. ↩️ Should I Restore My Site or Remove OTTO? In most cases, a full site restore is not necessary. Try these targeted steps first: - Review OTTO activity. Check your OTTO setup within Search Atlas to identify which recommendations were recently deployed and compare the deployment timing with when your errors first appeared. - Revert recent changes if possible. Depending on your setup, you may be able to undo recent OTTO-applied changes through your CMS or site backup before considering a full restore. - Use your CMS backup tools. If something looks wrong with your content, check your CMS revision history before performing a full site restore. - Perform a full restore only as a last resort. A full restore removes all OTTO progress and should only be considered if targeted reversions do not resolve the issue. 📋 What to Have Ready When Escalating If you are unable to resolve the issue on your own, please have the following information ready before reaching out to our team: - Your project or website name in Search Atlas - The exact error message or description of the unexpected behavior - The approximate date and time the issue first appeared - Any steps you have already taken to investigate or resolve 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 Delayed OTTO Recommendations

🔍 What delayed generation means OTTO creates recommendations after a site crawl discovers pages and identifies opportunities. A delay means the recommendation job has not completed yet; it does not necessarily indicate that OTTO is broken. The exact issue is usually one of these: - Waiting for crawl discovery: OTTO has not yet found new or changed pages. - Processing delay: The recommendation job is still generating results, especially for bulk requests. - No actionable change: The page is already optimal, so OTTO may have no recommendation to display. - Autopilot timing: Older workflows could wait for the next weekly autopilot cycle instead of generating recommendations after discovery. 📊 Check the recommendation status 1. Open OTTO SEO from the left sidebar. 2. Select All Sites and open the affected site. 3. Review the latest crawl and recommendation activity. 4. Open Crawl Monitoring to confirm whether the crawl completed and whether new pages or changes were discovered. 5. Check the recommendation list for a completed result, a pending job, or an indication that the page is already optimal. 🔄 Refresh the site data If the crawl has completed but recommendations are not visible, go to Home and select Refresh data. Return to OTTO SEO → All Sites and review the site again. Do not repeatedly submit the same request while a job is pending. Duplicate requests can increase processing time and make the status harder to interpret. ⚙️ Request a new generation 1. Confirm that the site is installed and connected under OTTO SEO → Installation Guide. 2. Run a scan from OTTO SEO → All Sites. 3. Wait for the scan to finish and confirm that the target page was discovered. 4. Review the generated recommendations. If the page is already optimized, no change may be suggested. ✅ When no recommendation is an expected result OTTO may identify a page as already optimal. In that case, a recommendation is not missing—the system found no meaningful improvement to make. Minor wording changes are not generated when they are unlikely to improve the page. 🧭 If the issue still appears unresolved Record the site, page URL, scan time, and the status shown in OTTO. Also note whether the crawl completed, whether the page was discovered, and whether the result says it is already optimal. This information helps distinguish a pending job from a completed no-op result or a platform 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.

🔧 OTTO SEO Common Issues & Troubleshooting Guide

What Is OTTO SEO? OTTO SEO is Search Atlas's on-site optimization tool. It audits your website, generates SEO recommendations, and helps you deploy fixes to improve your site's performance. Where to Find Your Domain Key Number (DKN) Your Domain Key Number (DKN) is a unique identifier that links your website to your OTTO SEO workspace. To locate your DKN: 1. Log in to your Search Atlas account. 2. Navigate to the OTTO SEO section from the main dashboard. 3. Select the project or domain you want to work with. 4. Look for your Domain Key Number (DKN) within that project's area. 5. Copy the DKN and keep it handy — you will need it when installing the OTTO SEO plugin on your website. If you cannot locate your DKN after following the steps above, note your project/domain name and contact support for help pinpointing the exact location in your account. Common OTTO SEO Issues & Self-Serve Troubleshooting Before reaching out to support, try the following steps for the most common OTTO SEO problems: - OTTO not connecting: Confirm you have entered the correct DKN in the plugin settings on your website. Double-check for extra spaces or typos when copying the DKN. - No recommendations appearing: Ensure the site audit has fully completed — this can take several minutes after connection. Refresh the OTTO SEO dashboard and check again once the audit status shows as complete. - Changes not deploying: Verify that the OTTO SEO plugin is active and up to date on your website. Deactivating and reactivating the plugin can resolve connection issues that prevent deployment. - Plugin installation issues: Confirm your site meets the plugin requirements and that no conflicting plugins are interfering. Check your WordPress (or relevant CMS) plugin list for conflicts. When to Contact Support If the self-serve steps above do not resolve your issue, please have the following ready when you reach out: - The domain name or project name you are working with - Your Domain Key Number (DKN), if you have been able to locate it - A description of the exact issue you are experiencing (e.g., OTTO not connecting, no recommendations appearing, changes not deploying) - Any error messages you have seen, including the exact wording - The date and time when the issue first occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix an Article Stuck on Final Completion Step

Overview If your article reaches the final step of the completion workflow but never finishes, this guide explains what to do. Because the specific cause in your case may vary, the steps below cover the most common general actions you can take on your end. If none of them resolve the issue, our support team can investigate the root cause directly. What You Can Try 1. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to reload the page and clear any cached state. Then attempt to complete the article again. 2. Clear your browser cache and cookies. Go to your browser settings and clear cached images, files, and cookies for the Search Atlas domain. Close and reopen the browser, log back in, and retry the completion step. 3. Try a different browser or incognito window. Open an incognito or private window (or switch to a different supported browser such as Chrome or Firefox) and repeat the workflow. This rules out browser extensions or persistent session data as the cause. 4. Wait a few minutes and retry. A brief service interruption may have caused the request to time out. Waiting a short time and trying again can resolve a temporary platform or network error. When to Escalate If the steps above do not resolve the issue, please contact our support team. To help us investigate as quickly as possible, have the following ready: - The exact name of the article that is stuck - The workspace or project it belongs to - A description of what happens at the final step (e.g. spinner that never stops, error message text, page that goes blank) - The browser and operating system you are using - Approximate time and date when the issue first occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Fix Empty Video and News Sitemaps in Search Atlas

🔍 Overview If your video-sitemap.xml or news-sitemap.xml returns an empty URL set — even when you have published video pages or recent news content — this article explains the most common causes and what information to have ready when escalating to support. ⚙️ Why This Happens Empty video or news sitemaps are almost always caused by one or more of the following: - Missing structured data: Search Atlas generates video sitemaps by reading VideoObject schema markup on your pages. If no valid schema is detected, no URLs may be included. - Missing news metadata: News sitemaps require a publication name and date in a supported news schema or meta tag format. Pages without this data may be excluded. - Pages not yet crawled: Newly published pages may not have been picked up by the latest crawl cycle, so the sitemap builder may have no data to include. - Sitemap count mismatch: The OTTO dashboard count and the live sitemap file may temporarily appear out of sync while a crawl or regeneration is still in progress. 🛠️ How to Diagnose the Issue 1. Open your browser and navigate directly to yoursite.com/video-sitemap.xml and yoursite.com/news-sitemap.xml. 2. Check whether the files load at all. A completely blank response or a server error (such as a 403 or 404) is different from an empty <urlset> — note which you see. 3. Visit one of your published video or news pages and use a schema validation tool (such as Google's Rich Results Test) to confirm that valid VideoObject or NewsArticle structured data is present. 4. Check the publication date on your news pages. Dates must be within the window accepted by Google News (typically the last two days for new submissions). ✅ What to Have Ready When You Contact Support Because resolving empty video or news sitemaps requires a backend investigation, please gather the following before reaching out so our team can act quickly: - Your project name or domain as it appears in Search Atlas. - The exact sitemap URLs returning empty results (e.g., yoursite.com/video-sitemap.xml). - The URLs of specific video or news pages you expect to appear in the sitemap. - Any error messages or status codes you see when accessing the sitemap files directly. - The date and time you first noticed the issue. - A note on whether structured data is present on the affected pages (you can verify this with Google's Rich Results Test). If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Recovering Blog Articles Deleted After Image Fix

🔍 What Happened A recent update to Website Studio resolved an issue where blog post image previews were not rendering correctly. In some cases, this fix unintentionally removed published blog articles from customers' blog pages. If you noticed that one or more blog posts disappeared after this update, you are not alone — this was a known platform-side issue that has since been resolved. 📋 What You Should Do First Before contacting support, take a few minutes to gather the following information. This will help our team restore your articles as quickly as possible: - The titles or URLs of the blog articles that went missing - The approximate date when you last saw the articles published on your blog page - Your Website Studio domain or project name so our team can locate your workspace - Any screenshots of the missing articles if you have them (for example, from a previous browser session or a cached version) ⚠️ Why This Happened The root cause was a bug in Website Studio where certain publishing actions — including image preview rendering fixes — could overwrite or remove previously published blog posts. Specifically, the platform was not always preserving all existing blog entries when changes were applied to the site. This has been patched, and new publishing actions should no longer affect previously published content. ✅ Steps to Check Before Escalating 1. Log in to Website Studio and navigate to your blog page to confirm which articles are missing. 2. Check Content Genius — if the articles were originally drafted there, the content may still exist as saved drafts even if they are no longer visible on your live blog page. 3. Review your published content list inside Website Studio to see if the articles appear as unpublished rather than deleted. 4. Try re-publishing any drafts that still exist in Content Genius directly to Website Studio to see if they restore correctly. 💬 How to Get Your Articles Restored If your articles are not recoverable through the steps above, our team can investigate and restore your content on the back end. To get help fast, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Please share the article titles, your project name, and any other details you gathered in the checklist above so we can resolve this as efficiently as possible. 🚀 What We Have Fixed Our engineering team has resolved several related blog stability issues in Website Studio, including: - Blog pages that were only keeping one article visible at a time after publishing from Content Genius - Published blog posts rendering as raw XML instead of styled web pages - Blog posts becoming unclickable or disappearing when unrelated site changes were saved - Published blog posts vanishing after a new prompt was submitted in the Content Genius chat These fixes are now live in production. If you experience any of these issues going forward, please report them immediately through the chat widget so our team can investigate. 🛡️ How to Protect Your Blog Content Going Forward - Keep drafts saved in Content Genius so you always have a recoverable copy of your blog content. - Take note of your published article URLs after publishing so you can quickly identify if anything goes missing. - Avoid making multiple simultaneous publishing changes until you confirm each one has saved correctly. - Check your live blog page after any major update or site change to confirm all articles are still visible. If you need further assistance, open 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 Zero OTTO Score and Enable Automations

🧭 Overview If your OTTO Score shows 0 and no fixes are being applied — even though the OTTO pixel appears installed — there are a few common causes related to automation settings and pixel placement. This guide explains what to check so you can get OTTO actively optimising your site. 🔗 Step 1: Enable Internal Linking and Alt Text Automations Internal linking and alt text automations are not enabled by default. You must turn them on manually inside your OTTO project settings. Once enabled, OTTO will begin generating internal link suggestions and writing alt text for images on your connected site. Allow a few minutes for the first pass to complete. ✅ Step 2: Verify the OTTO Pixel Is Placed Correctly The dashboard may show the pixel as installed even if it is placed in the wrong location. An incorrectly placed pixel prevents OTTO from reading your site and deploying fixes. If you are unsure whether your pixel is placed correctly, check your site's page source or plugin configuration and confirm the OTTO snippet is present and active on your live pages. 🔌 Step 3: Confirm Your Project Is Connected A disconnected project will show the pixel as installed but will not process any fixes or update your OTTO Score. Inside your project settings, verify that the site URL and connection status are correct. If the project appears disconnected, reinstall the pixel snippet on your site and re-verify the connection from within your project settings. 📋 When to Contact Support If you have completed the steps above and your OTTO Score remains at 0, a member of our team can investigate further on the backend. Please have the following ready when you reach out: - Your project name and the domain URL as entered in your project settings - The current connection status shown in your project settings - A description of which automations you have attempted to enable - Any error messages you have seen If you need further assistance, open 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 Tool: Fix Deleted Articles Still Appearing

Why Does OTTO Still Recognize Deleted Articles? If you have deleted an article and OTTO continues to reference or recognize it, this is a known issue that our team can investigate and resolve on your behalf. Because the exact behavior depends on how your site's content is indexed within OTTO, the resolution requires a support agent to review your specific workspace. What to Prepare Before Contacting Support To help our team resolve this as quickly as possible, please have the following ready when you reach out: - Your project or workspace name in Search Atlas where the issue is occurring. - The URL or title of the deleted article that OTTO is still referencing. - Confirmation that the article has been fully removed from your live website (e.g., the URL now returns a 404 error or redirect) and from your CMS (not saved as a draft or in the trash). - A description of where OTTO is still showing the deleted article — for example, in suggestions, content recommendations, or another specific area of the platform. - The approximate date and time when you first noticed the issue. Having this information ready will allow our support team to investigate your content index and take the appropriate action to clear the outdated reference from your workspace. What Happens Next Once you contact support, a team member will review your OTTO workspace and work to remove the deleted article from your content index. You do not need to take any additional steps in the platform before speaking with our team. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖥️ Fix HTTP 413 Errors in OTTO SEO Previews

🔍 What Is the HTTP 413 Error in OTTO SEO? When you use OTTO SEO to preview changes on a large WordPress page, you may see an HTTP 413 (Content Too Large) error inside the preview window. This error can look alarming, but it does not mean your page is broken or that OTTO has failed to process your changes. The 413 error in this context means one thing: the page you are trying to preview is too large for OTTO's built-in preview window to load. It is a preview limitation only and has no effect on your live site or on OTTO's ability to deploy your SEO changes. ⚠️ Why This Happens OTTO SEO's preview window is a lightweight rendering environment designed to give you a quick visual check of your changes. It has a size limit on the content it can load at one time. Very large WordPress pages — for example, pages with heavyweight page builders, many embedded blocks, large images, or complex layouts — can exceed this limit and trigger the 413 error. This is not caused by: - Your server's PHP memory limit or upload settings - A security plugin blocking the request - A Web Application Firewall (WAF) rejecting traffic - Any misconfiguration on your WordPress site You do not need to change any server-side settings to resolve this issue. ✅ How Your Changes Are Still Applied Even when the preview fails with a 413 error, OTTO SEO continues to work normally in the background. When you deploy changes through OTTO, they are written directly to your WordPress site — the preview window is a separate step and does not control deployment. In short: a failed preview does not mean a failed deployment. Your SEO changes are still live on your site. 🛠️ What To Do Instead of Using the Preview If you see a 413 error in the OTTO preview, follow these steps to verify your changes were applied correctly: 1. Go to Left sidebar → OTTO SEO → SEO Automation (or navigate to /seo-automation-v3). 2. Confirm that the changes you intended to make are shown as deployed or active in the OTTO SEO dashboard. 3. Open your WordPress page directly in a new browser tab using your site's live URL. 4. Use your browser's built-in developer tools (right-click → Inspect → Elements or View Page Source) to confirm the SEO changes — such as updated meta titles, descriptions, or structured data — are present in the page code. 5. Optionally, use a third-party tool such as Google's Rich Results Test or a meta tag checker to verify the changes are visible externally. 📋 Quick Reference: Preview Error vs. Live Site - 413 error in preview window: The page is too large for the preview to render. This is expected for large or complex pages. - Live site deployment: Unaffected by the preview error. OTTO applies changes directly to your site regardless of preview status. - Server-side changes needed: None. Do not adjust PHP settings, disable security plugins, or modify WAF rules to fix this error. 🔄 When To Contact Support You should reach out to our team if: - Your OTTO dashboard shows the changes as not deployed or shows an error other than 413 in the preview. - You have confirmed the changes are deployed in OTTO but they do not appear on your live site after a reasonable time. - You are seeing the 413 error on pages that are not unusually large or complex. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix OTTO Script Slowdown on Duda Sites

🔍 Why This Happens If your Duda site feels sluggish after installing the OTTO SEO script, the most common cause is an inactive Agency Whitelabel. When whitelabel setup is skipped or left incomplete, the OTTO script makes extra background requests that can significantly delay page rendering — even after you clear your site cache. This issue has been reported on Duda sites in particular, but the underlying fix applies regardless of your CMS. ⚙️ Check Your Whitelabel Status Before making changes, confirm whether your Agency Whitelabel is active. 1. Log in to your Search Atlas account. 2. Navigate to More Features → Agency Hub (Set up your Agency's White Label). 3. Review your whitelabel configuration to see if it has been completed. If fields such as your brand name, logo, or custom domain are blank or marked as inactive, your whitelabel is not fully configured — and this is likely causing the performance drag. 🚀 Activate Your Whitelabel Settings Completing your whitelabel setup allows the OTTO script to load efficiently without unnecessary background calls. 1. Go to More Features → Agency Hub (Set up your Agency's White Label). 2. Enter your brand name and upload your logo. 3. Review the remaining whitelabel configuration options. 4. Activate whitelabel if it is not already enabled. 5. Save your changes. Once whitelabel is active, the OTTO script stops making the redundant requests that slow down your pages. 🧹 Clear Your Duda Site Cache After activating whitelabel, clear all caching layers so visitors receive the optimized version of your site. 1. Log in to your Duda dashboard. 2. Open the affected site. 3. Navigate to Settings → Site Optimization → Clear Cache. 4. Publish your site to push the updated version live. If you use a CDN or external caching service, purge those caches as well. 📊 Verify the Improvement Once you have completed the steps above, confirm that your load times have improved. - Open your live site in an incognito or private browser window. - Test multiple pages, including the homepage and any pages where OTTO is deployed. - Use a speed testing tool such as Google PageSpeed Insights or GTmetrix. In most cases, page load times return to normal immediately after whitelabel activation and a full cache clear. 💡 Additional Tips If slowdowns persist after completing whitelabel setup, consider these additional steps: - Confirm you are using the latest version of the OTTO installation script. - Check that no other third-party scripts are conflicting with OTTO. - Review your OTTO SEO dashboard to ensure everything is configured correctly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Troubleshooting OTTO Connection Failures and Service ID Errors

Overview When OTTO fails to connect to a project, you may see a missing or blank service ID, OTTO Score errors across all sites, and OTTO SEO Strategy features that are unavailable. These symptoms commonly trace back to a pixel installation problem, a script conflict, or a caching issue. Follow the steps below in order to diagnose and resolve the connection failure. Step 1: Confirm Your Service ID Exists A service ID is generated when OTTO is successfully linked to a project. If no service ID appears, the connection did not complete. 1. Navigate to the OTTO SEO section of the platform and select the affected project. 2. Look for your service ID in your OTTO or OTTO SEO settings area. If the field is blank or shows an error, do not proceed with pixel installation until the connection has been refreshed. 3. Try disconnecting and reconnecting OTTO to the project, then check whether a service ID is generated. 4. Copy the service ID once it appears and keep it ready for the steps below. Step 2: Verify Pixel Installation on Your Site The OTTO pixel must be present on every page of your site for the service ID to register correctly. Choose the installation method that matches your setup. WordPress Plugin Method 1. Log in to your WordPress admin dashboard. 2. Install and activate the OTTO pixel plugin associated with your Search Atlas account. 3. Open the plugin settings and paste your service ID into the designated field. 4. Save changes and confirm the pixel snippet appears in your site's <head> section by viewing the page source and searching for your service ID. Manual Script / Custom Code Method 1. From your OTTO settings, copy the full pixel script snippet. 2. Paste the snippet inside the <head> tag of your site's HTML template or theme header file so it loads on every page. 3. If you use a page builder, place the script in the builder's global custom code or header scripts section rather than on individual pages. 4. Save and publish your changes, then verify the snippet is present in the page source. Google Tag Manager Method 1. Open your GTM container and create a new custom HTML tag. 2. Paste the OTTO pixel script into the tag body. 3. Set the trigger to fire on all pages. 4. Submit and publish the container version. 5. Use GTM's preview/debug mode to confirm the tag fires on page load before moving to the next step. Step 3: Clear Cache and Test Caching can prevent an updated pixel from being detected. After installing or updating the pixel: 1. Clear your site's server-side cache, any caching plugin cache (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache), and your CDN cache if applicable. 2. Open your site in a private/incognito browser window to avoid brow If you need further assistance, open 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 Explorer and OTTO Data Not Updating

🔍 Overview In some cases, triggering a Site Explorer refresh or running a Scan and Recalculate in OTTO may appear to complete — the screen briefly responds — but your data remains unchanged or missing. This article explains why this happens and what steps to take to get your data refreshed. ⚙️ Why This Happens A refresh request is processed in the background by our internal systems. Occasionally, there can be a delay between when you trigger the refresh and when the updated data becomes visible on screen. The action may have been successfully queued even if the interface did not clearly confirm it. Additionally, our team is actively working to improve how domain metrics are retrieved for OTTO, which may affect refresh behaviour in some situations. 🛠️ What to Try First 1. Wait and reload: After triggering a refresh, wait a few minutes and then fully reload the page in your browser. Background jobs can take time to complete, and a stale browser cache may prevent updated data from appearing. 2. Check OTTO again after the crawl finishes: Navigate to your OTTO dashboard and confirm that the Scan has fully completed before checking your metrics. Results will not update until the scan reaches 100%. 3. Clear your browser cache: If the page still shows old data after reloading, clear your browser cache and cookies, then revisit the page. This rules out a local display issue. 4. Try a different browser or incognito window: If clearing cache does not help, open the platform in a private/incognito window or a different browser to confirm the issue is not browser-specific. 5. Re-trigger the refresh if needed: If data is still missing after following the steps above, navigate to your OTTO dashboard and initiate another Scan. Monitor the page over the next few hours to see if metrics update. 📊 When the Issue Requires Our Team If you have followed all the steps above and your Site Explorer or OTTO data still has not updated after several hours, the refresh may need to be manually applied by our internal team — as was the case in situations like this previously. This is not something you can force from the platform interface alone. In this scenario, contacting support promptly gives our team the best chance of resolving it the same day. 💡 Tips to Avoid This Issue - Allow sufficient time after a Scan before checking OTTO metrics — large sites can take longer to process. - Avoid triggering multiple consecutive refreshes in quick succession, as this can cause queuing delays. - If you need data refreshed by a specific date, contact support in advance so our team can prioritise your request. 🙋 Still Need Help? If your data is still not updating after following the steps above, our team can es

🌐 Fix OTTO Suggestions in Wrong Language

🔍 What Is Happening and Why OTTO determines the language of each page by reading the HTML lang attribute at crawl time. If your Spanish pages have <html lang="en"> in their markup, OTTO interprets them as English pages and generates suggestions in English — regardless of the actual content on the page or any settings in Brand Vault. This is the most common reason bilingual or multilingual sites receive suggestions in the wrong language. It can also cause your OTTO score to appear stuck or metrics to stop updating, because suggestions generated in the wrong language may not apply correctly to the page. ✅ How to Fix It 1. Identify the affected pages. Check the source code of your Spanish pages and look for the opening <html> tag. If it reads <html lang="en">, that is the root cause. 2. Update the lang attribute. Ask your developer to change the lang attribute on all Spanish pages to <html lang="es">. For regional variants, use the appropriate BCP 47 tag (for example, lang="es-MX" for Mexican Spanish or lang="es-ES" for Spanish from Spain). 3. Re-crawl your site in OTTO. After the code change is deployed, trigger a new scan in OTTO so it picks up the corrected language signal and regenerates suggestions in Spanish. 4. Verify the new suggestions. Once the crawl completes, review the updated suggestions for your Spanish pages to confirm they are now generated in Spanish. ⚠️ Why Brand Vault Settings Do Not Override This Brand Vault stores information about your brand, tone, and preferences, but it does not override the page-level language signal. OTTO relies on the lang attribute in the HTML of each individual page to determine which language to use for suggestions. The fix must be applied at the HTML level by your developer. 🏗️ Long-Term Recommendation for Bilingual or Multilingual Sites If you manage a bilingual or multilingual site, the most reliable architecture is to host each language version on a separate subdomain or as a separate project in OTTO. For example: - English site:www.example.com → one OTTO project with lang="en" pages - Spanish site:es.example.com → a separate OTTO project with lang="es" pages This approach ensures OTTO can accurately detect the language for every page in each project and generate targeted, language-correct suggestions without any cross-language interference. 📊 What to Do If Suggestions Are Still Wrong After Re-Crawling If you have corrected the lang attribute, re-crawled, and OTTO is sti

🛠️ OTTO Meta Title Edits Not Saving Fix

🔍 What Is This Issue? When you open an OTTO suggested fix for a meta title and manually edit the text, clicking save appears to do nothing. The change does not persist, even after a hard refresh. This is a known platform bug that has been reported and resolved by the Search Atlas team. ✅ Current Status: Fixed This issue has been confirmed as fixed. You no longer need to work around it. If you experienced this problem in the past, your edits were not being saved due to a platform-side error — not because of anything you did wrong. 🚀 What You Should Do Now 1. Navigate to the OTTO section of Search Atlas. 2. Open the suggested fix for the meta title you want to edit. 3. Make your manual edit to the meta title as usual. 4. Save the change. The edit should now save correctly and persist after a page refresh. If you previously attempted an edit that did not save, revisit that page and re-apply your change. It should now save without any issues. ⚙️ Why Did This Happen? A platform-side error was occurring silently in the background whenever a manually edited OTTO suggested fix was submitted. This meant the save action appeared to complete on screen but the data was never written. The engineering team identified and resolved the root cause. 💡 Tips to Confirm Your Edit Saved - After saving, perform a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) and check that your edited meta title is still displayed. - If the value reverts to the original OTTO suggestion, try saving once more — the fix is live and the issue should not recur. - If you see an error message on screen when saving, note the exact wording before reaching out to support. 🆘 Still Having Trouble? If your meta title edits are still not saving after the fix, it is possible you are encountering a separate, unrelated issue. Please reach out to our support team for further assistance.

OTTO Showing Stale Data After On-Page Fixes

🧭 Overview After deploying on-page fixes through OTTO, you may notice that the platform still shows old data — outdated meta tags, missing blog posts, an incorrect site icon, or SEO scores that haven't improved. This is almost always caused by a slow-loading website preventing Search Atlas's crawler from fully scanning your pages, not a sync issue with your CMS or content tool. This article explains what causes stale OTTO data, how to confirm it is a crawl speed problem, and the steps to resolve it. ⚠️ Why This Happens Search Atlas crawls your website to read live on-page data and verify that deployed fixes are in place. If your site loads slowly, the crawler may time out before it can retrieve a page's content. When this happens: - OTTO continues to display the last successfully crawled version of your data. - Fixes you have deployed appear undetected, even though they are live on your site. - Elements like blog posts, site icons, and meta descriptions may not match what a visitor sees in a browser. This symptom is commonly mistaken for a CMS sync gap or a content ingestion error, but the root cause is page performance, not a platform configuration problem. 🔍 How to Confirm a Crawl Speed Issue Before troubleshooting, confirm that slow site performance is the likely cause by checking the following: 1. Test your page speed. Open Google PageSpeed Insights (pagespeed.web.dev) and enter your domain. A score below 50 on mobile or desktop, or a Time to First Byte (TTFB) above 600 ms, indicates your site is slow enough to affect crawlers. 2. Check your hosting server response. Use a tool such as GTmetrix or Pingdom to measure server response time. Anything above 1–2 seconds can cause crawler timeouts on content-heavy pages. 3. Confirm fixes are live in a browser. Visit the affected pages directly in an incognito browser window and verify your deployed changes are visible. If they appear correctly in a browser but not in OTTO, the issue is crawl-side, not deployment-side. 🛠️ Steps to Resolve the Issue 1. Improve your site's load time. Work with your developer or hosting provider to reduce page load time. Common fixes include enabling caching, compressing images, using a CDN, and minimising render-blocking scripts. The goal is a TTFB under 400 ms and a full page load under 3 seconds. 2. Allow time for re-crawling. Once performance improvements are in place, Search Atlas will re-crawl your site on its next scheduled cycle. After the crawl completes, OTTO should reflect your deployed fixes accurately. 3. Contact support if data remains stale. If your site speed has improved and OTTO still shows outdated data after a reasonable period, reach out to the Search Atlas support team so they can investigate the crawl status for your domain directly. If you need further assistance, please contact our support team via the chat widget in your Search Atlas dashboard.

🖼️ Fix Image Padding Issues in Cloud Stacks

🔍 Overview Some customers noticed that padding around article images disappeared in their Cloud Stack projects, affecting the professional appearance of published content. This was caused by a CSS rendering defect in Cloud Stack templates — specifically in the Standard Authority and Agency templates — where image padding, alignment, and button display were not rendering correctly across different screen sizes. Search Atlas engineers have since resolved the underlying CSS issues through several targeted fixes, including corrections to image padding, content alignment, responsive layout behaviour across breakpoints, and the display of inline elements such as the Read more button. ✅ What Was Fixed - Missing or collapsed padding around images in Cloud Stack article templates - Broken image dimensions and missing padding in Agency template previews - Alignment issues with authority copy and local business layouts on smaller screens - Responsive layout defects affecting Cloud Stack base templates across different breakpoints - Excessive page scrolling caused by the Images section layout These fixes were deployed by the engineering team and apply automatically to your Cloud Stack projects — no manual action is required on your end to receive the updates. 🛠️ What To Do If You Still See Layout Issues If you are still experiencing image padding or layout problems in your Cloud Stack projects after the fixes were deployed, follow these steps: 1. Open your Cloud Stack projects in Search Atlas and navigate to the affected project. 2. Review how images and content are rendering in the current preview. 3. If the layout still appears broken — for example, images have no padding, content is misaligned, or the Read more button is missing — try refreshing the page and reviewing the template again, as cached versions of the page can sometimes display outdated rendering. 4. If the issue persists after refreshing, check whether the problem appears only in the preview or also in the published output, and note which template type you are using (for example, Standard Authority or Agency). 5. Gather a screenshot or brief description of what is broken, including the template name and the URL of the affected Cloud Stack, before contacting support. 💡 Tips for Maintaining a Professional Layout - Use the built-in template options available within Cloud Stacks rather than heavily customised templates, as standard templates receive ongoing compatibility updates. - After publishing or updating a Cloud Stack, check the live output on multiple screen sizes to confirm images and text are displaying correctly. - If you use a custom template, be aware that custom CSS may conflict with platform-level updates — review your cust

🧹 Clear Your Browser Cache to Fix Search Atlas Display Issues

If Search Atlas is behaving unexpectedly — such as pages not loading correctly, outdated content appearing, or features not responding — clearing your browser cache is a quick and effective first troubleshooting step. Cached files can sometimes become outdated or corrupted, causing display and performance issues. Follow these steps to clear your browser cache: - Open your browser settings. This is usually accessible via the menu icon (three dots or lines) in the top-right corner of your browser window. - Navigate to the Clear Browsing Data option. In most browsers, you can also reach this directly by pressing Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac). - Make sure Cached images and files is selected. You may uncheck other options if you prefer to keep your browsing history and cookies intact. - Click Clear Data to remove the cached files. - Once the cache has been cleared, open a private or incognito window and navigate to Search Atlas to confirm whether the issue has been resolved. A private window ensures no old cached data is being used. If clearing the cache does not resolve your issue, try repeating the test in a different browser to rule out a browser-specific problem. If the issue persists across browsers or private windows, please reach out to us by using the live chat widget in the app to chat with a human teammate — we are happy to help investigate further.

⚡ OTTO Not Regenerating Title Tags or Meta Descriptions

Overview Some users have reported that OTTO appears to process regeneration requests for title tags and meta descriptions but the content does not actually update. This can affect a single site or multiple subaccounts at the same time. If you are experiencing this issue, contact our support team so they can investigate your account directly and apply a fix on the platform side. What Causes This Issue The root cause can vary by account. In documented cases, the issue was resolved by the support team investigating the account and addressing a platform-side problem. Because the underlying cause may differ between accounts, our team will need to review your specific setup to determine the correct resolution. Steps to Take 1. Confirm the issue is not isolated to one page. Attempt to trigger regeneration on at least two or three different pages or sites. Note whether any of them update successfully. If at least one page updates, the issue may be page-specific rather than account-wide. 2. Check whether multiple subaccounts are affected. If you manage subaccounts, check whether the issue is present on all of them or only a subset. Isolating which sites are affected helps narrow down whether this is an account-level or site-level problem. 3. Try manually re-triggering generation for a single page. Navigate to the affected page in OTTO, deselect and reselect the title tag or meta description task, and attempt to regenerate it individually rather than in bulk. In some cases this can prompt the platform to process the update correctly. 4. Check your OTTO credit balance. If your account has run out of generation credits, regeneration requests may appear to process but will not produce updated content. Verify your credit balance under Avatar (top-right) → Billing → Plans & Top-ups and top up if needed, then retry regeneration. 5. Disconnect and reconnect OTTO for the affected site. If the issue persists on a specific site, try deactivating OTTO for that site and reactivating it. This can clear a stuck state without requiring you to fully delete and recreate your setup. 6. Contact support with your findings. If none of the above steps resolve the issue, share which sites or subaccounts are affected, when the issue started, what you have already observed, and whether any titles or meta descriptions updated at all. This information will help the team investigate and apply a platform-side fix quickly. What Happens After You Report It Once you contact support, the team will investigate your account and determine whether a fix needs to be applied on the platform side. You do not need to delete and recreate your OTTO setup or reconfigure your sites while waiting for a resolution. If you need further assistance, please reach out to our support team and we will be happy to help.

🔍 Fix OTTO Pixel 'Not Found' Status on Squarespace

🧭 Overview After installing the OTTO pixel on your Squarespace site, you may notice a Not Found status in Search Atlas. In most cases, this is completely normal during the initial setup phase. This article explains why it happens and walks you through what to do — and when to take action. ⏳ Why 'Not Found' Is Expected After Installation When you first install the OTTO pixel, Search Atlas automatically checks for it 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 no automatic checks after 7 days. A correctly installed pixel on a new project is normally detected within about 15 minutes. Until the check runs, the pixel status may display as Not Found — even if the pixel was installed correctly. This is expected behavior and does not mean your installation failed. No action is needed during this window. 📋 How to Install the OTTO Pixel on Squarespace If you have not yet installed the pixel, follow these steps to add it to your Squarespace site: 1. In Search Atlas, go to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Select your project and open the OTTO dashboard. 3. Copy the OTTO pixel code snippet provided on the setup screen. 4. Log in to your Squarespace account and go to Settings. 5. Navigate to Advanced, then select Code Injection. 6. Paste the pixel code into the Header field. 7. Click Save and publish your site. Once saved, return to Search Atlas. On a new project, the automatic check typically detects your pixel within about 15 minutes. ✅ How to Confirm Your Pixel Is Installed Correctly Before waiting for the audit to finish, you can do a quick manual check to make sure the pixel code was added properly: - Open your Squarespace site 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 pixel ID or the OTTO script tag. - If the code appears in the page source, the pixel is installed correctly. - If it does not appear, revisit the Code Injection settings in Squarespace and re-paste the pixel code. 🔄 What to Do If It's Still Not Detected If the Not Found status persists well beyond the expected check interval for your project's age, work through the following checks: - Confirm the pixel is in the Header field: Squarespace's Code Injection has separate fields for Header and Footer. The OTTO pixel must be placed in the Header field only. - Check that your site is published: Squarespace sites in trial or password-protected mode may block external scripts from loading. Make sure your site is publicly accessible. - Avoid page-level overrides: Some Squarespace templates allow per-page code injection that can override global header code. Ensure no page-level settings are removing the script. - Clear your browser cache and recheck page source: A cached version of your page may not reflect recent changes. Open the site in an incognito window to verify the pixel loads. - Re-save the Code Injection settings: Occasionally Squarespace does not apply changes until you save and republish. Open the Code Injection field, confirm the code is present, and save again. 🔁 Manually Trigger a Recheck After confirming the pixel is present in your page source, you can prompt Search Atlas to re-scan your site sooner: 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Open your project's OTTO dashboard. 3. Locate the pixel status section and click Recheck or Re-run Audit if that option is available. If the option is not visible, Search Atlas will automatically re-check your pixel on its regular schedule based on your project's age. ⚠️ Common Mistakes to Avoid - Placing the pixel in the Footer field instead of the Header. - Adding the pixel to only one page instead of the global Code Injection settings. - Installing the pixel while the site is password-protected or in trial mode. - Checking the status immediately after installation before the next automatic check has run (typically within about 15 minutes on a new project). 💬 Still Seeing 'Not Found'? If you have followed all the steps above and your pixel still shows Not Found after the expected check interval, our team is ready to help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🍞 Fix OTTO Pixel Detection Issues on Toast Websites

🔍 Why This Happens on Toast Websites Toast is a closed restaurant-focused website platform with its own internal caching layer and strict script-loading rules. Standard troubleshooting steps — such as clearing your browser cache or repositioning a script tag — do not apply here. When OTTO Pixel stops being detected on a Toast website, the root cause is almost always one of the following: - Residual OTTO Pixel code left over from a previous install - Toast's internal cache serving an outdated version of your site - A Google Tag Manager (GTM) container conflicting with the direct pixel install Follow the steps below in order. Skipping steps or repeating the install without completing the full removal process is the most common reason reinstallation fails. 🗑️ Step 1 — Completely Remove Existing OTTO Pixel Code from Toast Before adding any new code, you must ensure no previous version of the OTTO Pixel remains on your Toast site. 1. Log in to your Toast account and navigate to your website settings. 2. Open the section where custom scripts or tracking codes are managed (sometimes labeled Header Scripts, Custom Code, or Advanced Settings). 3. Locate every instance of OTTO Pixel code. This includes any snippet containing your OTTO tracking ID or references to the OTTO script URL. 4. Delete all instances completely. Do not leave any partial snippets behind. 5. Save your changes. Important: If you installed OTTO Pixel more than once during previous troubleshooting attempts, there may be duplicate entries. Check the custom code area thoroughly before proceeding. 🏷️ Step 2 — Remove Google Tag Manager if Present If you previously installed OTTO Pixel through a Google Tag Manager (GTM) container, or if GTM is active on your Toast site alongside a direct OTTO Pixel install, this conflict will prevent detection. 1. Check your Toast custom code area for any GTM snippet (it will reference googletagmanager.com). 2. If GTM is present and was used to fire the OTTO Pixel, remove the GTM container snippet from Toast entirely, or pause the OTTO Pixel tag inside GTM so it is not firing. 3. Choose one installation method only: either a direct OTTO Pixel snippet in Toast, or via GTM — never both at the same time. 4. Save all changes. If you intend to use GTM as your installation method, ensure the GTM container is published with the OTTO Pixel tag active before moving to the cache-clearing step. 🧹 Step 3 — Clear Toast's Internal Cache Toast caches your website at the platform level. Clearing your browser cache alone will not update what Toast serves to visitors or to OTTO's detection system. 1. Inside your Toast dashboard, locate the Publish or Save & Publish option for your website. 2. Trigger a full republish of your site. On some Toast plans this is labeled Force Refresh or Clear Cache. 3. If you do not see a dedicated cache-clearing option, saving any minor change to your site (such as editing a word in a paragraph, then reverting it) and republishing will force Toast to regenerate your pages. 4. Confirm the publish completed successfully before continuing. ➕ Step 4 — Reinstall the OTTO Pixel 1. In Search Atlas, go to OTTO SEO in the left sidebar (URL: /seo-automation-v3). 2. Locate your OTTO Pixel snippet for the relevant project. 3. Copy the snippet in full. 4. Return to your Toast custom code area and paste the snippet once into the correct field (typically the Header section). 5. Save and republish your Toast site. ⏳ Step 5 — Wait 20+ Minutes Before Testing Detection After republishing, Toast requires time to propagate changes across its network. Attempting to verify OTTO Pixel detection immediately after reinstallation is one of the most common sources of confusion — the pixel will appear undetected even when the install is correct. - Wait a minimum of 20 minutes after your final publish before running a detection check. - When you are ready to test, open your live Toast website URL in a private or incognito browser window to avoid cached responses from your own browser. - Return to Search Atlas and trigger the OTTO Pixel verification check from the OTTO SEO section. ✅ Quick Checklist Before Contacting Support - All previous OTTO Pixel code removed from Toast custom code fields - GTM conflict resolved — one installation method only - Toast internal cache cleared via a full republish - Fresh OTTO Pixel snippet pasted once into the Header section - Site republished and at least 20 minutes have passed - Detection tested from a private browser window on the live site URL 💬 Still Not Detected? If you have completed every step above and OTTO Pixel is still not being detected, there may be a Toast account-level restriction or a platform update affecting script loading. If you need further assistance, open 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 Deployments Not Rendering on React SPA Sites

🧩 Why This Happens on React and Lovable Sites OTTO deploys your SEO changes by injecting a script into your site's head section. On traditional websites, those changes appear immediately. However, React-based sites — including those built with Lovable — use client-side rendering (CSR), meaning JavaScript controls what the browser displays after the initial page load. When React, or a library such as React Helmet, manages the head element, it can overwrite OTTO's injected meta tags and title tags after the page hydrates. This is why OTTO's dashboard shows the deployment as Engaged while your live site still displays old tags — OTTO deployed successfully, but your framework's render cycle replaced the changes. 🔍 Step 1: Verify OTTO Is Installed Correctly Before troubleshooting rendering, confirm that OTTO's script is placed in the correct location on your site. 1. Go to Left sidebar → OTTO SEO → Installation Guide and follow the platform-specific instructions for your site type. 2. For Lovable sites, the OTTO script must be added to the index.html file inside the head tag — not inside any React component. 3. Place the script as early as possible in the head section, before any other JavaScript files, so it executes before React hydrates the page. 4. After confirming placement, go to Left sidebar → OTTO SEO → All Sites, open your project card, and verify the site status shows as Active. 🛠️ Step 2: Inspect the Live Page Source vs. Rendered DOM There are two versions of your page's HTML: the raw source (what the server sends) and the rendered DOM (what JavaScript builds in the browser). Understanding the difference between them helps pinpoint exactly where the conflict occurs. 1. In your browser, right-click the live page and select View Page Source. Check whether OTTO's meta tags and title appear in the raw HTML. If they are missing here, the script may not be executing at load time. 2. Open DevTools → Elements tab and inspect the live head section. If OTTO's tags are present in the DOM but absent from View Page Source, your framework is injecting them client-side only — which many search engine crawlers may not process, causing the tags not to rank or update. 3. If OTTO's tags are absent from both views, the script is not executing at all. Return to Step 1 and re-check your installation. ⚙️ Step 3: Resolve Head Management Library Conflicts React apps frequently use head management libraries — such as React Helmet or react-helmet-async — that set meta tags from within the component tree. These libraries run after the page loads and will overwrite tags that OTTO injected earlier. - Search your Lovable project for any components that set the page title, meta description, or Open Graph values. These are commonly found in layout components, router configuration files, or dedicated SEO components. - For pages managed by OTTO, remove or disable the conflicting meta tag declarations inside your React components so OTTO becomes the single source of truth for SEO metadata on those pages. - If removing the library is not an option, ensure the values it sets exactly match what OTTO is deploying to eliminate any visible discrepancy. 📋 Step 4: Confirm the Redeployment in OTTO After resolving any script placement or library conflicts, re-verify the deployment is active and free of errors. 1. Go to Left sidebar → OTTO SEO → All Sites and open your project card. 2. Navigate to OTTO SEO → All Sites (SEO Automation) → your project → Deployment History and review recent deployment tasks for any warnings or errors associated with the affected pages. 3. If needed, trigger a fresh redeployment from your project card and allow a few minutes for the changes to propagate. 4. Repeat the browser inspection from Step 2 to confirm OTTO's tags are now rendering correctly in the live DOM. ✅ Quick Checklist Before Contacting Support - OTTO script is placed inside index.html in the head section — not inside a React component. - Script loads before all other JavaScript files on the page. - No React Helmet or similar library is overwriting OTTO's tags on the same pages. - Site status is Active in Left sidebar → OTTO SEO → All Sites. - No errors or warnings are visible in OTTO SEO → All Sites (SEO Automation) → your project → Deployment History. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting AI Schema Generation Not Displaying

This article addresses a specific issue where page-level schemas appear to generate successfully — credits are deducted and a confirmation message is shown — but no schema output is visible in the OTTO SEO tab afterwards. This is typically caused by a display delay or a rendering hiccup following processing, and does not always mean the generation failed. 🔍 Common Causes - Display lag after processing: The AI engine finishes generating the schema, but the UI does not automatically refresh to show the result. - Browser or session cache: A stale cached state can prevent newly generated content from rendering correctly. - Partial processing interruption: A brief network or server interruption during generation can cause output to be stored but not surfaced in the UI. 🛠️ Step-by-Step 1. After seeing the generation confirmation, perform a hard refresh of the page (Ctrl + Shift + R on Windows/Linux, or Cmd + Shift + R on Mac) to clear any cached state and force the UI to reload the latest data. 2. If the schema still does not appear, navigate away from the OTTO SEO tab to another section of the platform, then return to the OTTO SEO tab. This triggers a fresh data fetch from the server. 3. If you are still not seeing output, log out of your account and log back in, then return to the project and check the OTTO SEO tab again. 4. If the schema remains absent after completing the steps above, do not re-run the generation immediately — note the domain (e.g., shepcorestore.com), the approximate time of generation, and the number of credits deducted, and contact support so the team can investigate without you losing additional credits. ✅ How to Confirm It Worked After refreshing or re-navigating, you should see the generated schema code populated in the OTTO SEO tab for the relevant pages. Each page that was processed will display its schema markup in the corresponding field. If schemas are present and credits were deducted, the generation completed successfully. If the fields remain empty but credits were still used, this confirms a display or delivery issue that requires support review — your generation data is likely stored on the backend and can be recovered without re-running and spending additional credits. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicated Lists in Blog Content

🔍 Why duplicated lists appear When a numbered or bulleted list appears first as a formatted list and again as regular paragraphs, the content may contain two versions of the same text. This can happen when list formatting is converted during publishing, when a page is resynced, or when the website editor keeps an earlier copy alongside the updated content. The issue may be visible in the published page even when the article looks correct in Search Atlas. This is usually a publishing or website-editor issue rather than intentional content generation. ✅ Check the article in Search Atlas 1. Open Content in the left sidebar. 2. Select Content Genius. 3. Open the affected article using the relevant writing action, such as Write an article or Rework existing article. 4. Search for the duplicated list text and confirm whether it appears once or twice in the article editor. If the content appears twice in Search Atlas, remove the repeated paragraphs or list before publishing. Keep only one version of each numbered or bulleted section. 🧹 Fix the live blog page 1. Open the affected page in your website or CMS editor. 2. Switch to the HTML, code, or source view if available. 3. Find the repeated list content. One copy may use a list element, while the other may use separate paragraph elements. 4. Delete the extra copy and preserve the correctly formatted numbered or bulleted list. 5. Save or update the page, then check the published URL in a private browser window. Do not simply hide the duplicate with styling. Removing the extra content from the page source prevents visitors and search engines from receiving repeated text. 🔄 If the duplicate returns after syncing If the list reappears after a resync or update, first remove the duplicate from the website editor and save the page again. Then compare the article in Search Atlas with the live page. Avoid repeatedly resyncing the article until the duplicate source has been identified, as this can restore the unwanted copy. Also check whether a page template, reusable content block, import tool, or publishing integration is inserting the list a second time. Test one affected page after making the correction before updating multiple managed blog pages. 🛡️ Prevent future duplicates - Review list sections in the article preview before publishing. - Use one list format consistently instead of combining a formatted list with manually repeated paragraphs. - After publishing, verify the live URL and inspect the source when the visible content looks duplicated. - When updating an existing article, edit the current page instead of creating a second copy. - Keep a record of corrected URLs so the same pages can be checked after future syncs. 💬 Get help with a recurring issue When contacting support, include the affected URL, the article name, whether the duplicate appears in Search Atlas or only on the live page, and whether it returns after resyncing. If you need further assistance, open 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 Meta Tag Deployment Persistence

🔍 What this issue means A meta title or meta description may show Not Deployed, fail to save, or return to an earlier value after deployment. In some cases, Search Atlas reports a successful deployment, but the change does not appear on the live page. Previously deployed assets may also become undeployed. This is usually caused by a CMS or SEO plugin overriding the deployment, an empty field that cannot be saved correctly, or a synchronization issue between Search Atlas and your website. ✅ Check the deployment status 1. Open the affected project in Search Atlas. 2. Review the page's meta title and meta description fields. 3. Save the changes, then deploy them again. 4. Refresh the page and confirm the status remains Deployed. 5. Open the live page in a private browser window and view its source to confirm the intended tags are present. 🔌 Check CMS and plugin conflicts On WordPress, SEO plugins such as Rank Math can override values deployed by Search Atlas. The Search Atlas status may show Deployed while the original plugin value still renders on the page. - Check whether the affected page has a title or description configured in an SEO plugin. - Compare the plugin value with the value in Search Atlas. - Remove or update conflicting values where appropriate. - Deploy the Search Atlas value again and verify the live page source. Do not disable an SEO plugin without confirming how your website uses it. If both systems must remain active, ensure only one system controls each meta field. ✍️ Check empty fields Edits may fail when the page's title or description field starts empty. Enter a complete value instead of saving a blank field, then deploy again. 1. Enter the full meta title or description manually. 2. Save the change. 3. Wait for the save confirmation. 4. Deploy the asset again. 5. Refresh Search Atlas and confirm the value persists. 🔄 Re-deploy and verify persistence Use this sequence when a deployment succeeds but later becomes undeployed: 1. Record the intended title and description. 2. Save the values in Search Atlas. 3. Deploy the page. 4. Wait for the deployment to finish before leaving the page. 5. Refresh Search Atlas and check the status. 6. Check the live page source and confirm the rendered values. 7. Return later and verify that the status and live values have not changed. If you undeploy a page, values managed by the SEO plugin may remain in place. Undeploying should not necessarily blank those plugin-controlled values. 📄 When several pages are affected If many pages, such as 24 meta title tags, show Not Deployed, avoid editing every page repeatedly. First test one affected page using the steps above. If the test page persists correctly, deploy the remaining pages in smaller groups and verify each group. If the test page fails, investigate the CMS connection and plugin configuration before making more bulk changes. 🧾 Information to collect before contacting support - Project and affected page URLs. - The exact meta title or description values you attempted to deploy. - Whether the field was previously empty. - The deployment status before and after refreshing. - The CMS and SEO plugins active on the site. - Whether the live page source shows the Search Atlas value or another value. - Screenshots of the status and any error messages. If you need further assistance, open 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 Suggested Fixes Blank After Site Audit

🗺️ Understanding the Two-Step Model OTTO's workflow is divided into two distinct stages that must each be completed separately. Step 1 — Issue Discovery: When you run a Site Audit or recrawl your domain, OTTO scans your site and surfaces SEO issues and opportunities in the Onpage Optimizations section. This step identifies what needs to be fixed. It does not automatically create suggested fixes. Step 2 — Fix Generation: Suggested fixes must be actively generated for each issue after discovery. They will never populate on their own as a result of crawling or recrawling. This is the step most customers miss. ❓ Why Are My Suggested Fixes Blank? Seeing hundreds of blank suggested fixes after a site audit or recrawl is expected behaviour — it is not a bug or a processing delay. A blank fix field simply means no fix has been generated for that issue yet. Common reasons this happens: - You recrawled the site but did not trigger fix generation afterwards. - Only a small initial batch of fixes were generated in a previous session (for example, 4–6 out of hundreds of issues), leaving the rest blank. - Fix generation requires a deliberate action — either manual or via Atlas Agent — and does not run in the background. Important: There is no automatic background process that will populate blank fixes after a recrawl. Waiting will not cause fixes to appear. ✅ How to Generate Suggested Fixes You have two options to generate suggested fixes for your open OTTO issues. Option 1 — Generate Fixes Manually 1. Go to Left sidebar → OTTO SEO → Overview. 2. Select your site from the site list. 3. Open the Onpage Optimizations section. 4. Click into an issue category that shows blank fixes. 5. For each issue row, click the Generate Fix action button to create the suggested fix for that specific issue. Option 2 — Use Atlas Agent (Recommended for Large Sites) 1. Go to Left sidebar → OTTO SEO → Overview. 2. Select your site. 3. In the Onpage Optimizations section, activate Atlas Agent to batch-generate fixes across all open issues. 4. Atlas Agent works through the full issue list and populates suggested fixes at scale, saving you from processing hundreds of rows individually. ⚠️ What Recrawling Actually Does Recrawling refreshes the issue discovery layer only. It will: - Detect new SEO issues introduced since the last crawl. - Mark previously resolved issues as fixed. - Update issue counts and page-level data. Recrawling will not: - Generate or populate suggested fixes for any issues. - Trigger any background reprocessing of fix content. - Replace the manual or Atlas Agent fix-generation step. 🚀 Step-by-Step: Fix Blank Suggestions Now If you are seeing hundreds of blank suggested fixes, follow these steps to resolve it: 1. Confirm your recrawl has completed by checking Left sidebar → OTTO SEO → Crawl Monitoring. 2. Navigate to Left sidebar → OTTO SEO → Overview and open Onpage Optimizations for your site. 3. Use Atlas Agent to batch-generate fixes across all open issues, or generate fixes individually for your highest-priority pages first. 4. Refresh the page after generation completes to see all suggested fixes populated. If you need further assistance, open 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 OTTO Data After Platform Migration

🔍 Overview After Search Atlas migrated projects to the V3 dashboard, some customers noticed that OTTO data — including Content, Authority Technicals, and UX Signals — appeared blank or incomplete on certain projects. This article explains why this happens and walks you through the steps to resolve it. ⚙️ Why This Happens When projects are migrated from the legacy platform to the V3 dashboard, OTTO's data sync does not always transfer automatically. The V3 environment treats migrated projects as new instances, which means OTTO needs to be reactivated and re-synced to begin collecting and displaying data again. This affects all OTTO categories: Content, Authority Technicals, and UX Signals. This is a known post-migration behaviour and is not a sign that your data has been lost. It simply means OTTO needs to re-establish its connection to each affected project. ✅ How to Restore Missing OTTO Data 1. Navigate to SEO Automation: From the left sidebar, click OTTO SEO, then open SEO Automation inside it, or go directly to /seo-automation-v3. 2. Select the affected project: Use the project switcher at the top of the page to open the project that is missing data (for example, seangarner.co or halfmoonplumbing.com). 3. Check OTTO activation status: On the OTTO dashboard, confirm whether OTTO is shown as Active. If OTTO is inactive or shows a setup prompt, proceed to the next step. 4. Reactivate OTTO: Click the Activate OTTO button and follow the on-screen prompts to reconnect OTTO to the project. This re-establishes the data sync for Content, Authority Technicals, and UX Signals. 5. Trigger a data refresh: Once OTTO is active, click Refresh Data or wait for the automatic sync cycle to complete. Initial data population can take up to 24 hours depending on site size. 6. Repeat for each affected project: If you have multiple projects with missing data, repeat steps 2–5 for each one individually. 📊 What Data Will Be Restored Once OTTO is reactivated and synced, the following sections will repopulate in the V3 dashboard: - Content: On-page content recommendations and optimisation opportunities. - Authority Technicals: Backlink health, domain authority signals, and technical SEO flags. - UX Signals: User experience metrics and page-level performance indicators. If any category still appears empty after 24 hours, it may indicate that OTTO has not yet crawled enough data for that specific section. Allow an additional crawl cycle before raising a support request. 💡 Tips to Prevent This in Future - After any platform update or migration notice from Search Atlas, log in and verify OTTO is still showing as Active on all your projects. - Check the V3 dashboard at /seo-automation-v3 regularly to catch any sync gaps early. - If you manage a large number of projects, prioritise checking your highest-traffic sites first. 🆘 Still Need Help? If you have reactivated OTTO and your data is still not appearing after 24 hours, or if you are unable to complete the reactivation steps, 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.

🛠️ Shopify Installation Status and OTTO Indexing Delays

🔍 Overview After connecting a new Shopify store to Search Atlas, it is common to see a status message that reads not installed correctly on the dashboard. In most cases, this is not an error. It simply means the platform has not yet finished verifying your installation. The status is temporary and resolves automatically once OTTO finishes indexing your website. This article explains what to expect and how to confirm everything is working properly. ⏳ Why the Status Shows 'Not Installed Correctly' When you add a Shopify site, Search Atlas needs time to crawl your store, verify the connection, and begin pulling data into OTTO. During this window, the dashboard may display a status that looks like a failure even when the installation was completed successfully. Think of it as a loading screen. The installation itself is complete; OTTO simply needs time to verify and catalog your site's data before the status updates. - Verification typically completes within 24 to 48 hours after installation. - OTTO indexing — where your site's pages are fully processed and SEO recommendations are generated — can take up to 72 hours for larger stores. - Indexing time varies depending on the size of your Shopify store. Smaller stores will typically complete indexing faster, while larger stores with more pages may take longer. - The status message updates automatically once verification is confirmed. No manual refresh or reinstallation is needed. ✅ How to Confirm Your Shopify Site Is Connected Correctly While you wait for the status to update, you can take a few steps to confirm the installation was completed on your end. 1. Log in to your Shopify Admin panel and navigate to Apps. 2. Confirm that the Search Atlas app appears in your installed apps list. 3. Return to Search Atlas and go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). 4. Check whether your Shopify domain appears in the site list. If it does, the connection was registered successfully. 5. Go to Left sidebar → Site Metrics (Site Explorer) (URL: /site-explorer/list) and select your Shopify domain. If site data is beginning to populate, the installation is working correctly. 🚀 What Happens After OTTO Finishes Indexing Once OTTO completes the indexing process, you will see the following changes in your dashboard: - The installation status updates to installed correctly. - OTTO begins generating SEO automation recommendations for your Shopify pages, including titles, meta descriptions, and schema. - Site data — such as keyword rankings and traffic metrics — starts appearing under Site Explorer. You do not need to take any action to trigger this. The process runs automatically in the background. ⚠️ When You Should Be Concerned In most cases, waiting 48–72 hours resolves the status message. However, reach out for support if any of the following apply: - More than 72 hours have passed and the status still shows not installed correctly. - Your Shopify domain does not appear in the OTTO SEO V3 or Site Explorer sections after 48 hours. - You receive an explicit installation error message (distinct from the pending status). - You accidentally uninstalled and reinstalled the app and are unsure whether the reconnection was successful. - OTTO is not generating any data after a reasonable indexing window has passed. If any of these situations occur, contact our support team with your Shopify site name, the approximate time of installation, and a description of what you are seeing so we can investigate further. 💡 Tips to Avoid Installation Issues - Make sure you complete the full connection flow in Search Atlas without closing the browser tab mid-process. - Do not uninstall and reinstall the app within the first 24 hours — this resets the verification timer. - Ensure your Shopify store is publicly accessible (not password-protected) so Search Atlas can crawl it successfully. 🙋 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 Disappearing Keywords, OTTO Quota & Billing Issues

🔍 Overview This article covers three related issues that some Search Atlas customers have experienced: keywords disappearing shortly after being added by city, the OTTO site quota displaying an incorrect count even after purchasing top-ups, and an unexpected charge appearing on your account instead of the plan amount you intended. Follow the steps below to understand what causes each issue and how to resolve it quickly. 📍 Keywords Disappearing After City Targeting If you add keywords filtered by city and they vanish approximately one hour later, this is most commonly caused by one of the following: - Session sync delay: The platform may not have saved the city-level targeting before your session refreshed. Always confirm changes are saved before navigating away. - Filter state reset: Active city filters can reset if the browser tab is idle for an extended period. Re-applying the filter after a refresh may not re-save the underlying keyword set. - Quota limit reached: If your keyword tracking quota is full, newly added keywords may appear temporarily and then be dropped automatically. To check and resolve this issue: 1. Go to the left sidebar and select Keywords (URL: /research/keyword-researcher). 2. Confirm your current tracked keyword count against your plan's limit. If you are at or near the limit, remove unused keywords before adding new city-targeted ones. 3. Re-add your city-targeted keywords, then refresh the page after 60 seconds to confirm they have been saved correctly. 4. If keywords continue to disappear after confirming you have available quota, escalate via the chat widget (see the support section below). ⚙️ OTTO Site Quota Displaying Incorrectly After purchasing an OTTO site quota top-up, the platform may still display the previous (lower) quota count. This is a known display sync issue and does not necessarily mean your top-up was not applied. To verify and fix your OTTO quota display: 1. Go to the left sidebar and select OTTO SEO, then open SEO Automation inside it (URL: /seo-automation-v3). 2. Hard-refresh your browser (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to force the platform to reload your current entitlements. 3. Check the site quota counter again. In most cases, a hard refresh will sync the correct number. 4. If the count is still wrong after refreshing, log out of Search Atlas completely, wait 2–3 minutes, then log back in and recheck. 5. If the quota remains incorrect after these steps, contact support so a teammate can manually verify the top-up was applied to your account and correct the displayed value. Important: Do not purchase a second top-up before confirming with support. Purchasing a duplicate top-up to work around a display bug may result in an additional charge without adding extra quota beyond what you already paid for. 💳 Unexpected or Incorrect Billing Charge If you were charged an amount you did not expect — for example, a charge of $513 when you intended to purchase a $99 plan — this can happen in the following scenarios: - Add-on or top-up selected unintentionally: During checkout, additional add-ons (such as OTTO site top-ups, keyword tracking expansions, or content credits) may have been included alongside the base plan. - Annual plan selected instead of monthly: Selecting an annual billing cycle at checkout will charge the full annual amount immediately rather than a monthly instalment. - Multiple charges triggered: Rapidly clicking the checkout or upgrade button more than once can occasionally trigger duplicate transactions. Steps to take immediately if you see an unexpected charge: 1. Do not attempt to cancel or downgrade your plan yourself, as this may forfeit refund eligibility or affect your active campaign data. 2. Take a screenshot of the charge as it appears on your bank or card statement, including the date, amount, and merchant name. 3. Contact Search Atlas support immediately via the chat widget (details below) and provide the charge amount, the date it appeared, and the plan you intended to purchase. 4. A teammate will review your billing history, confirm what was charged, and process a refund for any amount that was not authorised or intended. Refund processing time: Once a refund is approved by the Search Atlas billing team, it typically appears on your statement within 5–10 business days, depending on your card issuer. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Fix OTTO Scan Pending Tasks Redirect Loop

🔍 What Is This Issue? Some customers find themselves stuck in a loop where OTTO SEO repeatedly redirects them to a pending tasks page. No matter which section of the platform they try to access, they are sent back to the same pending tasks screen and cannot navigate away. This article explains what to do right now and when to escalate. ⚠️ Why This Happens This appears to be an internal issue within the OTTO scan process where pending tasks become unresolved and the platform continues routing you back to the pending tasks screen. The exact root cause requires investigation by our technical team on the backend. 🛠️ Steps to Try First 1. Hard-refresh the platform. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to clear the cached state and reload the page. 2. Wait 20–30 minutes and try again. Some scan tasks are processed asynchronously. Giving the process time to complete may allow the loop to resolve on its own. 3. Clear browser cookies and cache for the platform domain. A stale session can sometimes persist the redirect state. Clear your browser data, log back in, and return to OTTO SEO. 📋 When to Escalate If the steps above do not resolve the issue, this will require backend investigation by our support team. Please have the following information ready before reaching out: - The name of the project or site affected - A description of the pending tasks shown (e.g. the number and type of tasks listed) - The approximate time the loop started - Any actions you took in OTTO SEO immediately before the issue began If you need further assistance, open 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 Open Graph Image & Meta Output Issues

🔍 Overview Open Graph (OG) output issues have been reported in the Search Atlas WordPress plugin. This article covers common symptoms users have encountered, and walks you through steps to confirm whether the issue is resolved on your site after updating. ⚠️ Known Issue Users have reported problems with Open Graph image output in the Search Atlas WordPress plugin. Symptoms may include incorrect or missing OG tags, unexpected page layout changes, or featured images not appearing as expected when content is shared. If you are experiencing any of these symptoms, follow the troubleshooting steps below. ✅ Steps to Troubleshoot 1. Update the Search Atlas WordPress plugin to the latest available version. Go to your WordPress dashboard, navigate to Plugins > Installed Plugins, and check for updates next to the Search Atlas plugin. 2. Clear all caches after updating — this includes your WordPress cache plugin, server-side cache, CDN cache, and any Elementor CSS cache. 3. Inspect your Open Graph tags using a tool such as the Facebook Sharing Debugger or the OpenGraph.xyz preview tool. Paste in the URL of a post, an archive page, and your homepage separately. 4. Check archive pages specifically. Visit your blog archive (e.g. /blog/) and confirm that the og:url and canonical tag point to the archive URL — not the URL of an individual post. 5. Verify OG image output. In your page source or a meta tag inspector, confirm that your Open Graph image tag is present and populated correctly. 6. Check your page layout. If you use a page builder such as Elementor, review affected pages to confirm that images and layout elements are rendering at the expected dimensions. 📋 When Escalating If you are still experiencing issues after following the steps above, please have the following ready when you contact support: - The URL(s) of the affected page(s) - A description of the specific symptom (e.g. missing OG image, broken layout, incorrect canonical URL) - Any third-party plugins that may interact with OG output (e.g. page builders, media storage plugins) - Your current Search Atlas plugin version - Any error messages or screenshots you can share If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO UUID Errors and Plugin Connection

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

🛠️ Fix OTTO Home Page Warnings and Google Ads Sync Issues

🔍 Overview Two common issues can cause confusion in OTTO: (1) the home page showing warnings or alerts even after you have already deployed fixes, and (2) discrepancies between campaigns created by OTTO in Google Ads and what appears inside the OTTO campaign hub. This article explains what you should have ready when contacting support so these issues can be resolved as quickly as possible. ⚠️ Home Page Warnings After Deployment After deploying OTTO recommendations, you may still see warnings or alerts on your home page. This does not always mean your fixes failed — it may reflect a known display or data-refresh issue on the backend. Because the root cause requires investigation on our end, please gather the following before escalating: - The name of the project or site affected. - A description of what the home page is currently showing. - Confirmation of which recommendations you have already deployed and approximately when you deployed them. - A screenshot of the home page warning, if possible. 📊 Google Ads Campaign Sync Discrepancies When OTTO creates or manages campaigns in Google Ads, you may notice that what appears in your Google Ads account does not match what is shown in the OTTO campaign hub. Because discrepancies of this kind require backend investigation, please have the following ready before escalating: - The exact campaign name(s) affected. - A description of the specific fields or details that do not match. - The approximate date and time you first noticed the discrepancy. - Screenshots from both the OTTO campaign hub and your Google Ads account showing the mismatch, if available. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

🔍 Why OTTO Meta Tags Aren't Showing in Google

🧭 Overview You've deployed updated meta tags through OTTO SEO, confirmed the changes are live on the page, and Google has even re-crawled the page — but the new meta tags still aren't showing in actual search results. This is a common and frustrating experience. The good news is that it's almost always a timing or caching issue, not a problem with your deployment. ⚙️ How Google Updates Search Snippets There is an important distinction between crawling and indexing. When Google crawls your page, it reads and stores the raw content. When it indexes your page, it processes that content and decides what to display in search results. These are two separate steps and can happen hours or even days apart. - Crawl confirmed: Google visited and read your page. - Index updated: Google has processed the crawl data and refreshed what appears in search results. - SERP snippet refreshed: The visible title and description in search results have been updated — this step can lag behind the others. A confirmed crawl does not guarantee that the search snippet will update immediately. Google's systems prioritise and schedule index updates independently of crawl events. ⏱️ Expected Timelines Meta tag changes typically take between a few days and several weeks to fully reflect in search results, depending on your site's crawl frequency, domain authority, and how competitive the keyword landscape is. Even after a successful re-crawl, snippets can take additional time to refresh in the search engine results pages (SERPs). - High-authority, frequently crawled sites: may see updates sooner - Newer or lower-traffic sites: may wait longer for changes to appear - Highly competitive queries: Google may override your meta description with its own generated snippet regardless of your tags ✅ How to Verify Your Deployment Is Working Correctly Before assuming something is broken, confirm that the meta tag changes are correctly live on the page: 1. View the source of your page in a browser and search for the meta title and description tags to confirm the updated values are present in the HTML. 2. Run the page through Google Search Console's URL Inspection tool and use the live URL test. If the meta tags appear correctly there, the deployment is working — Google simply hasn't refreshed the SERP snippet yet. 3. Optionally verify with a browser extension such as SEOquake or a meta tag checker tool to confirm the tags are live in the page's HTML. If all of the above confirm the correct tags are present, the deployment is successful. The delay is entirely on Google's side. 🛠️ Steps to Speed Up Google's Snippet Refresh While you cannot force Google to update its snippets on demand, the following steps may help prompt a faster refresh: - Use Google Search Console's URL Inspection tool to request indexing for the affected page. - Ensure your sitemap is up to date and submitted in Google Search Console. - Build or refresh internal links pointing to the updated page to signal its importance. - Monitor Google Search Console over the following days and weeks for index status changes. If your meta tags are confirmed live in the page HTML but the SERP snippet has not updated after several weeks, this is worth escalating so our team can review the deployment on your project. When reaching out, please have the following ready: the affected page URL, a screenshot or copy of the current HTML meta tags, and the date OTTO deployed the changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 Chrome User Experience Report Not Updating After Recrawl

🧭 Overview The Chrome User Experience (CrUX) report inside the Search Atlas Site Audit displays real-world performance data collected by Google from actual Chrome users visiting your site. Because this data originates from an external Google dataset rather than the crawl engine itself, it follows a different refresh cycle than other audit metrics. Understanding that distinction is the key to resolving most data-freshness issues. 🔍 Why the CrUX Report Does Not Update Immediately After a Recrawl Running a new site audit recrawl refreshes data that Search Atlas collects directly — such as broken links, indexability signals, and on-page elements. The Chrome User Experience report is different: - External data source: CrUX data is sourced from Google's public CrUX dataset, which Google updates on a rolling 28-day window, published once per month (typically in the first week of each month). Search Atlas cannot force Google to release new data ahead of that schedule. - Recrawl scope: A site audit recrawl instructs the Search Atlas crawler to re-examine your site's pages. It does not trigger a new pull from the Google CrUX dataset unless the dataset itself has been refreshed since your last audit. - Cached dataset: If the Google CrUX dataset has not been updated since your previous audit, the report will display the same figures regardless of how many recrawls you run. - Insufficient real-world traffic: Google only includes URLs in the CrUX dataset that receive a minimum threshold of Chrome user visits. Pages with low traffic may show no CrUX data at all, or data may appear intermittently. ⚠️ Common Scenarios and What They Mean - Recrawl completed but CrUX scores are identical: The Google dataset has not released a new monthly update yet. Wait until the dataset refreshes and then run a new audit. - Some pages show CrUX data and others do not: Pages without data likely fall below Google's minimum traffic threshold. This is a Google-side limitation and cannot be changed from within Search Atlas. - Scores changed in Google Search Console but not in Search Atlas: Google Search Console can display more granular or provisional data. The CrUX dataset used by Search Atlas reflects the full monthly aggregation, which may lag by a few days after Google publishes it. - CrUX data shows for the domain but not individual URLs: Google aggregates CrUX at both the origin (domain) level and the URL level. If a specific URL lacks sufficient traffic data, only origin-level data will appear. ✅ Step-by-Step Troubleshooting 1. Confirm the Google CrUX dataset has been updated. Check the Google CrUX release schedule — updates are typically published in the first week of each calendar month. If you ran your recrawl before the latest release, no new CrUX data will be available yet. 2. Run a fresh recrawl after the dataset releases. Navigate to Left sidebar → OTTO SEO → Site Audit → All Audits, open your project audit, and trigger a new recrawl. The report will then pull the most recently available CrUX data. 3. Check the audit timestamp. Inside your audit, confirm the date the CrUX data was last fetched. If it predates the most recent Google CrUX release, a new recrawl will resolve the discrepancy. 4. Verify your site has sufficient Chrome traffic. If pages consistently show no CrUX data, cross-reference your Google Search Console → Core Web Vitals report. If data is absent there too, the pages likely do not meet Google's minimum traffic threshold. 5. Review the Page Explorer for individual URL data. Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer to inspect CrUX availability at the individual page level. This helps identify which URLs are included in the dataset and which are not. 6. Check Crawl Monitoring for any crawl errors. Navigate to Left sidebar → OTTO SEO → Crawl Monitoring to confirm the recrawl completed without errors. An interrupted crawl may result in incomplete data across all report sections, including CrUX. 📋 What to Expect Going Forward - CrUX data inside Search Atlas refreshes once per month, aligned with Google's public dataset release cycle. - After Google releases a new dataset, run a fresh recrawl to pull the updated figures into your audit report. - Improvements you make to Core Web Vitals will take at least one full 28-day collection window before they appear in CrUX scores. - Origin-level CrUX data is available for most sites with any meaningful traffic, but URL-level data requires higher individual page traffic volumes. 💬 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 SEO Tag Not Detected via Google Tag Manager

🧭 Overview When OTTO SEO is deployed through Google Tag Manager (GTM), the platform must detect the tag on your website before activation can proceed. If the tag check fails, your OTTO SEO project will remain inactive even though GTM shows the tag as published. This article covers what to check on your end and how to escalate if the issue persists. ⚙️ How OTTO SEO Tag Detection Works After you connect your domain to an OTTO SEO project, the platform checks whether the OTTO SEO script is present and loading correctly on your site. When the tag is deployed via GTM rather than hardcoded into your HTML, GTM-specific configuration issues can prevent the script from being detected. 🔎 Common Causes of Tag Detection Failure via GTM - GTM container not published: The tag exists in GTM as a draft but has never been submitted and published to the live container. - Incorrect trigger configuration: The tag is set to fire on a specific page or event rather than on all pages, so the detection check may land on a page where the tag never fires. - Content Security Policy (CSP) blocking: Your site's CSP headers restrict third-party scripts, preventing the OTTO SEO script from executing. - Tag firing order or sequencing: Another tag or GTM rule is pausing or blocking the OTTO SEO tag from firing during the initial page load. - Consent Mode / cookie banner interaction: If GTM is configured with Consent Mode, the OTTO SEO tag may be held back until user consent is granted, which can interfere with detection. - Cached page being served: A CDN or server-side cache layer may serve a stale page that pre-dates the GTM container publish, so the tag is absent from the response. ✅ Steps to Try Before Escalating 1. Confirm the GTM container is published. In your GTM workspace, verify that the container version containing the OTTO SEO tag has been submitted and is live. A draft tag will not fire on the live site. 2. Check the trigger scope. Open the OTTO SEO tag in GTM and confirm the trigger is set to fire on all pages. If it is scoped to a specific URL or event only, update it to fire on all pages and republish the container. 3. Use GTM's Preview mode. Load your homepage while GTM Preview is active and confirm the OTTO SEO tag is firing on the initial page view. If it is not firing, review your trigger settings and any tag blocking or sequencing rules. 4. Check your Content Security Policy. Review your site's CSP headers to confirm that third-party scripts required by OTTO SEO are not being blocked. If they are, add the necessary domain to your allowlist. 5. Clear your CDN or server cache. If your site uses a CDN or caching layer, purge the cache after publishing your GTM container so detection checks see the latest version of your pages. 6. Disable Consent Mode temporarily for testing. If your GTM setup uses Consent Mode, check whether the OTTO SEO tag is configured to require consent before firing, and adjust accordingly. 📋 How to Escalate If you have worked through all the steps above and the OTTO SEO tag is still not being detected, please reach out to our support team. To help us investigate as quickly as possible, have the following ready: - Your OTTO SEO project name and the domain in question - Your GTM container ID - A description of which steps you have already tried - Any error messages or console output you have observed - Approximate date and time when 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 SEO Missing Edit Icon and Manual Suggestions

🔍 Overview Some customers have noticed that the edit icon is no longer visible on certain rows in the OTTO SEO suggested fixes section, and that the option to write suggestions manually is no longer available. This article explains what is known about this behaviour and how to get help if you are affected. ⚙️ What Is Happening Some users have reported that the edit icon on OTTO SEO suggestion rows is not visible, and that the ability to manually write or enter suggestions in the suggested fix section is unavailable. The exact conditions that cause these features to be hidden have not been fully confirmed, and this behaviour is currently under investigation as a potential bug. If you are experiencing this, you are not alone — it has been reported by multiple customers and is a known issue being looked into by the Search Atlas team. 📋 How to Escalate This Issue Because the root cause of this behaviour has not yet been confirmed, the best course of action is to contact the support team directly. To help the team investigate as quickly as possible, please have the following ready before reaching out: - The project name or domain where OTTO SEO is set up - The specific page or URL where the edit icon or manual suggestion option is missing - A screenshot showing the affected row or section, if possible - The approximate date and time you first noticed 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.

⚡ How to Fix a WordPress Cache Error on Your Blog Post

This article covers a cache-related display error that can appear after publishing a blog post in WordPress. Because the original support ticket for this issue contained only a topic label — with no documented agent resolution or confirmed root cause — we are not able to provide verified self-serve steps for this specific error at this time. What We Know The reported symptom is: a blog post displaying a WordPress cache error after publishing. The underlying cause and the exact fix applied by our support team have not been documented, so any specific troubleshooting steps would be speculative and could lead you in the wrong direction. What to Do Next To get accurate help with this issue, please contact our support team directly. When you reach out, having the following information ready will help us resolve your issue as quickly as possible: - Your project or site name as it appears in Search Atlas - The exact error message you are seeing (a screenshot is ideal) - The URL of the affected blog post - The date and time the error first appeared - Any recent changes you made to the post or your WordPress setup before the error occurred If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicate H1 Tags Blocking OTTO Optimization

🔍 Overview If OTTO SEO is unable to complete its optimization on your site, a duplicate H1 tag in your Website Studio pages may be the cause. This issue occurs when the page builder adds a second H1 tag alongside the one OTTO manages, creating a conflict that blocks optimization and may affect your SEO deliverables. This article explains why this happens, how to confirm it, and the steps you can take to resolve it. ⚠️ Why Duplicate H1 Tags Cause Problems Every page should have exactly one H1 tag — it signals to search engines what the page is primarily about. When Website Studio publishes a page, it can sometimes inject an additional H1 element into the HTML, resulting in two H1 tags on the same page. This creates two specific problems: - OTTO conflict: OTTO detects the extra H1 as an SEO error it cannot safely overwrite without risking layout or content issues, so it pauses the optimization task. - Audit failures: Your site will fail Search Atlas SEO audits flagging multiple H1 tags, which may impact your overall SEO score and project deliverables. ✅ How to Confirm the Issue Before making any changes, verify that a duplicate H1 exists on the affected page: 1. Open your published website in a browser. 2. Right-click anywhere on the page and select View Page Source (or press Ctrl+U / Cmd+U). 3. Use Ctrl+F / Cmd+F to search for <h1. 4. If two or more results appear, the duplicate H1 issue is confirmed. 🛠️ How to Fix the Duplicate H1 in Website Studio Follow these steps to remove the extra H1 tag directly inside Website Studio: 1. Log in to your Search Atlas account and navigate to Website Studio from the left sidebar. 2. Open the page editor for the affected page. 3. Click on each heading element visible on the page and check its tag type in the formatting panel. Look for any element set to H1 that is not your primary page title. 4. Select the duplicate H1 element — typically a section title, hero subtitle, or a block that was inadvertently styled as H1. 5. Change its tag to an appropriate level such as H2 or H3, or remove the element entirely if it is not needed. 6. Save your changes and republish the page. 7. Re-check the published page source using the steps above to confirm only one <h1 tag remains. 🚀 Re-running OTTO After the Fix Once the duplicate H1 is removed and the page is republished, OTTO should be able to resume optimization automatically. To manually trigger a refresh: 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate the affected site in your OTTO dashboard. 3. If the site shows a paused or incomplete status, select it and allow OTTO to re-scan and apply pending optimizations. 4. Confirm the H1 optimization task is now marked as complete in the task list. 💡 How to Prevent This in the Future To avoid duplicate H1 tags appearing after future edits or republishing: - Always assign your primary page title as the sole H1 element. Every other heading on the page should start at H2. - After making structural changes in Website Studio, re-check the page source before republishing to confirm there is only one H1. - If you are using pre-built templates or section blocks, review the default heading levels — templates sometimes set decorative titles to H1 by default. - Run a Search Atlas SEO Audit on your domain after publishing updates to catch any heading hierarchy issues early. 📞 Need Further Help? If you have checked the page source, made the corrections in Website Studio, and OTTO is still blocked — or if you cannot locate the duplicate H1 element in the editor — our team can investigate the underlying HTML 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 JobPosting Schema Errors on Non-Job Pages

🔍 Overview If Google Search Console is flagging JobPosting schema errors on pages that are not job listings — such as city-level service pages or location landing pages — this is a known schema deployment issue. Incorrect schema associations can confuse Google's crawlers, suppress rich result eligibility, and contribute to traffic drops across multiple pages. This article explains why this happens and how to fix it using OTTO SEO. ⚠️ Why This Happens There are several reasons why JobPosting schema may appear incorrectly on non-job pages: - Stale schema type display: After pasting a new schema JSON and deploying, the schema list may still show the old schema type (for example, "Organization" or "JobPosting") instead of the updated one. The label is outdated even though a different schema was deployed. - Schema shown as deployed without generation: In some cases, OTTO may display a schema as deployed at the page level even if no schema was intentionally generated or pushed to that page. - Validation suppression conflicts: When deploying with validation suppressed, the system may return an is_approved: false status for schemas that were found on the page, causing confusion about what is actually live. Any of these conditions can result in the wrong schema type being associated with pages across your site — including high-volume city-level pages — which Google may then flag as errors. 🔎 How to Identify Affected Pages 1. Go to the left sidebar and select OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Open the site that contains the affected pages. 3. Navigate to the Schema section within OTTO. 4. Review the schema type listed for each page. If city pages or non-job pages show JobPosting as their schema type, they are incorrectly flagged. 5. Cross-reference with Google Search Console under Enhancements → Job Postings to confirm which URLs are being flagged. 🛠️ How to Fix Incorrect JobPosting Schema Follow these steps to remove or correct the schema on affected pages: 1. In OTTO SEO, locate the affected page in the schema list. 2. Check the schema JSON that is currently associated with the page. If it contains @type: JobPosting and this page is not a job listing, the schema needs to be replaced or removed. 3. Paste the correct schema JSON for that page type (for example, LocalBusiness or Service schema for city-level pages). 4. Before deploying, confirm the schema type label in the list has updated to reflect the new JSON. If it still shows the old type, refresh the page and check again. 5. Use the per-row validation bypass option if the schema fails validation but you are confident the JSON is correct. A warning will appear — review it before proceeding. 6. Deploy the corrected schema to the page. Important: After deploying, wait 24–48 hours and then re-check Google Search Console to confirm the JobPosting errors have cleared for those URLs. 🚫 How to Remove Schema Entirely from a Page If a city-level page should not have any structured data deployed through OTTO, you can remove the schema row entirely: 1. In the OTTO SEO schema list, find the affected page row. 2. Select the row and choose the option to delete or unassign the schema. 3. Confirm the removal and redeploy so the page is no longer associated with any schema through OTTO. This ensures Google will no longer detect a JobPosting signal on that page, which should resolve the Search Console error over time. 📊 Monitoring Recovery Across City Pages Once corrections are deployed, monitor progress using these steps: - In Google Search Console, use the URL Inspection Tool to request re-indexing for your most important city pages. - Check the Enhancements report weekly to track the decline in JobPosting errors. - Within Search Atlas, use Left sidebar → AI Visibility → Visibility to monitor any traffic recovery trends at the domain or page level. ✅ Best Practices to Prevent This Issue - Always verify the schema type label in the OTTO schema list matches the JSON you intend to deploy before clicking deploy. - Only apply JobPosting schema to pages that genuinely list job openings with required fields (title, hiringOrganization, jobLocation, datePosted). - For location or city pages, use LocalBusiness, Service, or WebPage schema types instead. - After any bulk schema deployment, spot-check a sample of URLs in Google Search Console to catch mislabeled schema early. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Duplicate H1 Tags Blocking OTTO SEO

🔍 Overview Some customers have noticed that their published Website Studio site contains a duplicate H1 tag inside the index.html file. This duplicate H1 is not visible or editable through the Website Studio interface, but it can trigger an SEO audit failure and prevent OTTO SEO from fully optimizing the page. This article explains what causes the issue, how to confirm it, and what steps to take. ⚙️ What Causes the Duplicate H1? A known bug in Website Studio can cause certain published sites to generate a duplicate H1 tag inside the compiled index.html file. This happens at the code-generation level, meaning the duplicate does not appear in the visual editor and cannot be deleted manually by the customer. 📊 How This Affects OTTO SEO OTTO SEO scans your live page and flags any page that contains more than one H1 tag as an error. When a duplicate H1 exists in the compiled HTML, OTTO cannot clear this audit item automatically because the second H1 is not part of your editable content. As a result: - Your Search Atlas SEO audit will show a duplicate H1 warning on the affected page. - OTTO SEO may be unable to complete its full optimization pass for that URL. - The issue persists even after editing or saving changes in Website Studio. ✅ How to Confirm the Issue 1. Open your live site URL in a browser, right-click the page, and select View Page Source. 2. Use Ctrl+F (or Cmd+F on Mac) and search for <h1. If two or more results appear in the source code, the duplicate is confirmed. 3. You can also check your OTTO SEO audit results for your Website Studio domain and look for any H1-related error on the homepage or any published page. 🚀 Next Steps Because the duplicate H1 lives inside the compiled index.html file and not in the visual editor, the fix must be applied at the backend level. This is a known bug that requires intervention from our support team. When reaching out, please have the following ready: - Your Website Studio domain or project name - The specific page URL where the duplicate H1 appears - Confirmation that you have verified the duplicate in the page source (the number of <h1 results found) If you need further assistance, open 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 Unclickable Loop Results in Site Explorer

🧭 Overview When running a playbook in Site Explorer — particularly the SEO Research Organic loop — you may find that the results appear in the output panel but cannot be clicked or opened. This article explains why this happens and walks you through the steps to resolve it. ⚠️ Why Loop Results Are Not Clickable This issue is typically caused by one or more of the following: - The domain search is still loading. Site Explorer sections can briefly show an empty or broken state while data is being fetched for a newly searched domain. Clickable links are not activated until the section fully loads. - A known display bug. A resolved platform issue previously caused certain loop output rows to appear interactive before they were ready. If your account has not yet received the latest update, you may still encounter this. - Sub-navigation items are disabled. Some sections within Site Explorer are temporarily disabled depending on the data available for the domain. Disabled items look clickable but do not respond — hover tooltips now indicate when an item is unavailable. - You navigated directly to the Site Explorer base URL. Typing the base web address of Site Explorer into your browser without a domain query leads to a dead-end page. Always launch Site Explorer from within the platform to ensure the tool loads correctly. 🛠️ How to Fix Unclickable Loop Results 1. Wait for the page to fully load. After entering a domain, give Site Explorer a few seconds to complete the data fetch. A loading skeleton will appear while sections are populating — wait until all sections show live data before interacting with loop results. 2. Refresh the page. If results remain unresponsive after loading is complete, perform a hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any stale display state. 3. Re-run the playbook loop. Navigate back to your playbook, open the SEO Research Organic loop, and re-run it. Once the output regenerates, the result links should be fully active. 4. Launch Site Explorer from the platform menu. Do not type the Site Explorer URL directly into your browser. Instead, access it through the left-hand navigation menu inside Search Atlas to ensure the tool initialises with the correct session context. 5. Check for disabled sub-nav sections. Hover over any section tabs or sub-navigation items that appear greyed out. A tooltip will now display explaining why the item is currently unavailable for the domain you searched. 6. Try a different browser or clear your cache. Cached assets can occasionally interfere with interactive elements. Clear your browser cache or switch to a different browser to rule out a local issue. ✅ Confirming the Issue Is Resolved Once the fix is applied, you should be able to: - Click on any row within the SEO Research Organic loop output and open the corresponding result. - See a loading skeleton — rather than a blank or broken state — while new domain data is being fetched. - View informative hover tooltips on any sub-navigation items that are temporarily disabled. 💡 Tips to Avoid This Issue in the Future - Always access Site Explorer through the platform's navigation menu, not by typing the URL directly. - Allow the domain data to fully load before interacting with playbook loop outputs. - If you notice a section stuck in a blank state for more than 30 seconds, refresh the page and re-search the domain. 🆘 Still Need Help? If you have followed all the steps above and loop results are still not clickable, If you need further assistance, open 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 Item URL in Breadcrumb Schema

🔍 What Is This Issue? When MetaSync generates a BreadcrumbList schema on custom taxonomy archive pages (such as category, tag, or custom taxonomy archives), it may omit the item URL property from one or more breadcrumb list elements. Google Search Console flags this as a "Missing field item" error in the Rich Results report, which can prevent your breadcrumbs from appearing in search results. This typically affects pages like /blog/category/news/ or any archive URL tied to a custom taxonomy, where the taxonomy label is included in the breadcrumb trail but its corresponding URL is not passed through to the schema markup. ⚠️ Why Does This Happen? The BreadcrumbList schema requires every ListItem to include three properties: - @type — set to ListItem - position — the numeric order of the item in the trail - item — an object containing the @id (URL) and name of that breadcrumb step On taxonomy archive pages, MetaSync may resolve the taxonomy label correctly but fail to attach the corresponding archive URL to the item property. The result is a ListItem entry with a name but no URL, which Google treats as invalid markup. 🛠️ How to Fix the Missing Item URL Follow the steps below to manually correct the breadcrumb schema for your taxonomy archive pages using the Search Atlas Schema module. 1. Log in to Search Atlas and navigate to the Schema Creator by clicking the apps-grid icon in the header, then selecting More Features → Schema Creator. 2. Search for the taxonomy archive page that is generating the error (for example, a category or custom taxonomy archive URL). 3. Open the existing BreadcrumbList schema for that page. If no schema exists, create a new one by selecting BreadcrumbList from the schema type menu. 4. Locate the ListItem entry that corresponds to the taxonomy label (this is the step missing its URL). 5. In the item field for that ListItem, enter the full absolute URL of the taxonomy archive page — for example, https://yourdomain.com/blog/category/news/. 6. Confirm that every ListItem in the breadcrumb trail has a valid name, position, and item URL populated. 7. Save the schema and use the Google Rich Results Test (search.google.com/test/rich-results) to validate the updated markup before resubmitting in Search Console. ✅ How to Verify the Fix in Google Search Console 1. Go to Google Search Console and open the Enhancements section in the left menu. 2. Select Breadcrumbs to view the current error report. 3. Click on the "Missing field item" error to see affected URLs. 4. After applying the fix in Search Atlas, click Validate Fix next to the affected URLs. 5. Google typically re-crawls and updates the status within a few days to two weeks. 🧩 Additional Notes - If you are using Rank Math or another SEO plugin alongside MetaSync, check that both tools are not outputting competing BreadcrumbList schemas on the same page. Duplicate or conflicting schema blocks can cause further validation issues. Disable breadcrumb schema output from the third-party plugin if MetaSync is your primary schema tool. - Custom taxonomy archives sometimes require the breadcrumb trail to be configured manually, as MetaSync cannot always resolve dynamic archive URLs automatically. - If your breadcrumb schema was previously generating valid markup and stopped after a recent update, check the Schema module for any unsaved changes or reset configurations. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix Search Atlas Buffering and Loading Issues

🔍 Overview If Search Atlas is buffering, stuck on a loading screen, or displaying unexpected errors, several common factors could be responsible — from browser settings to temporary platform issues. This guide walks you through the most effective fixes to get you back up and running quickly. ⚠️ Common Symptoms - The platform loads indefinitely without displaying content - Pages or projects are stuck in a loading state - An unexpected error screen appears on the homepage - The UI flickers or shakes while navigating - Tools such as Site Explorer return an Error 500 or fail to load results - Restricted browser pages show an infinite loader instead of a clear error message 🛠️ Step-by-Step Troubleshooting 1. Refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to perform a hard refresh. This forces the browser to reload all assets instead of using a cached version. 2. Clear your browser cache and cookies. Outdated cached data is one of the most common causes of loading problems. In Chrome, go to Settings → Privacy and Security → Clear Browsing Data, select Cached images and files and Cookies, then click Clear data. 3. Disable browser extensions. Extensions — especially ad blockers, VPNs, or script blockers — can interfere with platform requests. Open an Incognito / Private window (which disables most extensions by default) and try loading Search Atlas again. 4. Check your internet connection. Run a speed test at a site such as fast.com. A slow or unstable connection can cause requests to time out, resulting in buffering or error 524 messages. 5. Try a different browser or device. If Search Atlas loads correctly in another browser (e.g., Firefox or Edge) or on a different device, the issue is isolated to your original browser environment. 6. Check for platform-wide issues. Intermittent errors (such as ERR_FAILED 524 or Error 500) are sometimes caused by temporary server-side conditions. If multiple tools or projects are affected at the same time, the issue may resolve on its own within a few minutes. Wait a short while and try again. 7. Avoid restricted browser pages. Certain Chrome pages (such as chrome:// URLs or browser extension pages) block external scripts and can trigger an infinite loader. Always access Search Atlas through a standard browser tab using a regular https:// URL. ✅ Best Practices to Prevent Loading Issues - Keep your browser updated to the latest stable version. - Use Google Chrome or Mozilla Firefox for the best compatibility with Search Atlas. - Avoid running Search Atlas alongside resource-heavy applications that may limit available memory or bandwidth. - If you use a VPN or proxy, try disabling it temporarily — these tools can reroute traffic in ways that cause timeout errors. 📋 Information to Have Ready Before Contacting Support If the steps above do not resolve your issue, gathering the following details in advance will help our team diagnose the problem faster: - The browser name and version you are using - The specific tool or page where the loading issue occurs (e.g., Site Explorer, Homepage) - A screenshot or screen recording of the error or buffering state - Approximately when the issue started - Whether the issue happens consistently or only intermittently 💬 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 Anchor Text Duplication and Auto-Deployment

🔍 Understanding the Problem Some customers have noticed that OTTO generates a large number of identical anchor texts across their site. Others have found that OTTO applies changes automatically, including keyword assignments they did not approve. This article explains what is known and what to expect when you reach out for help. ⚙️ What Is Known These issues — repeated anchor text patterns and unexpected automatic deployments — have been reported by customers using OTTO. The specific cause may vary depending on your individual site configuration and settings, and our support team is equipped to investigate your particular setup. 🛠️ What to Do Because these issues involve OTTO's backend behaviour tied to your specific site setup, resolving them requires assistance from our support team. To help us investigate and act as quickly as possible, please have the following information ready before you reach out: - Your project or site name as it appears in Search Atlas. - Examples of the duplicated anchor texts you are seeing (a few specific phrases and the pages they appear on). - A description of the auto-deployment behaviour you did not expect — including approximately when it occurred, if known. - Any recent changes you made to keyword assignments or OTTO settings before the issue appeared. Our team will review your site's OTTO configuration and work with you directly to correct the duplication and adjust deployment controls to match your preferences. If you need further assistance, open 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 Audit and OTTO Tasks Stuck at Approval

🔍 Overview Some customers notice that Site Audit and OTTO tasks appear to start normally but never complete — they consistently stop at the approval step, even after waiting several days or retrying multiple times. This is a known issue that our team investigates on a case-by-case basis. ⚙️ What Is the Approval Step? The approval step is a required checkpoint where OTTO waits for you to review and confirm recommended changes before applying them to your site. Tasks will remain paused at this step until action is taken. If your tasks are stuck here and you are unable to move them forward, this may indicate an underlying issue that requires backend investigation. 📋 What to Have Ready When Escalating Because this issue requires investigation by our support team, please have the following information ready before reaching out: - Project name — the exact name of the Search Atlas project where the tasks are stuck. - Affected site URL — the domain associated with the stuck tasks. - Task type — which specific Site Audit or OTTO task types are affected (e.g. meta titles, schema, internal links). - How long the tasks have been stuck — approximate date and time when you first noticed the issue. - Any error messages — copy the exact text of any error or status message displayed on the affected tasks. - Steps already attempted — note anything you have already tried, such as navigating away and back, or waiting for a data refresh. Having this information ready will allow our team to investigate and resolve the issue as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📊 Why Your OTTO Healthy Page Count Dropped

🔍 Overview After OTTO completes a new site crawl, you may notice your healthy page count drops. You may also find that changes you previously approved and implemented now require re-approval. This article explains what is happening and what steps to take. ⚠️ Known Issue: Healthy Page Count Drops After a Re-Crawl Our team is aware of an issue where OTTO's healthy page count can drop unexpectedly after a re-crawl runs, and previously approved changes may revert to requiring re-approval. This is a known bug — our engineering team is actively investigating the root cause. We do not yet have a confirmed cause or estimated fix date, and we appreciate your patience while we work on a resolution. 🛠️ What to Do When Your Count Drops Since this is a known bug under active investigation, there are no guaranteed self-serve steps to restore the count at this time. However, the following information will help our engineering team diagnose and address your specific case. Please have these details ready when you reach out: - Project name and URL of the affected site - Approximate date and time when you first noticed the healthy page count drop - Whether a re-crawl ran around the time the count changed - Details of any fixes that reverted to requiring re-approval (page URLs and the specific fixes involved) - Screenshots showing the healthy page count before and after the drop, if available If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO URL Validation Errors in Website Studio

Overview When adding a website to OTTO inside Website Studio, the platform runs a URL validation check before allowing you to proceed. If your site shows as Invalid or Not Found, this article explains what to check and how to get help from our team. What to Check First Before reaching out to support, please confirm the following: - Your URL is entered in the correct format, including the protocol (for example, https://www.yourdomain.com). - Your site loads correctly in a browser with no error pages or maintenance screens active. - Your SSL certificate is active and not expired. - Your DNS records have fully propagated. If you have confirmed all of the above and the validation error still appears, the issue will need to be investigated by our support team. How to Escalate When contacting support, please have the following ready so our team can investigate as quickly as possible: - The exact URL you are trying to validate. - A screenshot or description of the exact error message you see. - The date and time (with timezone) when the error first occurred. - Your project or account name in Search Atlas. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Conversion Tracking Launch Failures

🔍 Overview When OTTO attempts to launch conversion tracking, it may flag items that require attention before it can proceed. This article explains what to do if OTTO is unable to launch conversion tracking on your site, and how to get the right support to resolve it. ⚙️ What Happens During a Conversion Tracking Launch Failure If OTTO cannot launch conversion tracking, resolving the issue typically requires a backend action from our team — it may not be something you can fully resolve on your own through the platform interface. 🚀 What to Do If OTTO Flags a Launch Failure Because resolving this issue requires a backend action from our support team, please gather the following information before reaching out: 1. Note the exact error message or flag that OTTO is displaying when the launch failure occurs. 2. Record your project name and the domain associated with the site where conversion tracking is failing. 3. Note the timestamp of when the failure occurred or was first noticed. If you need further assistance, open 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 on Drupal

Overview If OTTO is not recognizing your pixel after installing it on a Drupal site, you are not alone. Drupal's caching layers, module conflicts, and theme structure can all interfere with pixel detection. This guide walks you through the most common areas to check when troubleshooting a pixel that is not being recognized. Before You Begin Make sure you have the following ready before troubleshooting: - Admin access to your Drupal site - Your OTTO pixel code, available inside your Search Atlas account - Access to your Drupal theme files or a module capable of injecting code into the page head Step 1 — Confirm Your Pixel Code Is Correct Start by verifying you are using the right pixel code for your site. 1. Log in to Search Atlas and locate your OTTO pixel snippet. It should be the complete script tag assigned to your specific site. 2. Copy the code fresh — do not rely on a previously saved copy that may be outdated. Step 2 — Place the Pixel Directly in the HTML Head A reliable method on Drupal is injecting the pixel code directly into the <head> section of your base theme, bypassing any third-party tag manager. 1. In your Drupal admin panel, navigate to your active theme's template files. 2. Open the base HTML template file for your theme. 3. Paste your OTTO pixel code immediately after the opening <head> tag. 4. Save the file. Important: If you previously installed the pixel through Google Tag Manager (GTM), consider removing it from GTM and placing it directly in the template instead. GTM loads asynchronously and may be affected by certain Drupal performance modules, which can cause detection failures. Step 3 — Clear All Drupal Caches Drupal aggressively caches page output, so changes to templates may not appear until caches are fully cleared. 1. Navigate to your Drupal admin panel and clear all site caches using the available cache-clearing option in your configuration settings. 2. If your hosting environment supports command-line tools, a full cache rebuild from the command line can ensure all layers are cleared. 3. If your site uses a CDN, purge the CDN cache as well to ensure visitors receive the updated page. Step 4 — Verify the Pixel Is Live on the Page After clearing caches, confirm the pixel is actually rendering in the browser. 1. Open your website in a browser and navigate to any page. 2. Right-click and select View Page Source. 3. Use Ctrl+F (or Cmd+F on Mac) to search for a unique string from your pixel code. 4. If the code appears in the source, the pixel is present on the page and OTTO should be able to detect it. If it does not appear, revisit Steps 1–3 above. If you need further assistance, open 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 'not_installed' Status on WordPress

🧭 Overview If your OTTO pixel appears in your page source and your holistic scores are updating, but the OTTO dashboard still shows a not_installed status, you may be experiencing a conflict between a manually inserted script and the Search Atlas WordPress plugin. This article explains what is known about this issue and what to have ready if you need to escalate. 🔍 Why This Happens OTTO uses more than one method to verify a successful pixel installation. A pixel that is manually pasted into your theme or a custom code field may fire correctly for some purposes, but it can still result in a not_installed status if the Search Atlas WordPress plugin cannot recognise the installation as valid. This type of conflict — where the pixel is technically present on the page but the status does not update — is a known issue for WordPress users who have mixed manual and plugin-based installation methods. ✅ What to Do The confirmed resolution for this issue involves removing any manually inserted OTTO pixel script and allowing the Search Atlas WordPress plugin to manage pixel installation exclusively. Having both a manual script and the plugin active at the same time is the primary cause of the not_installed conflict. To get this resolved, please have the following ready when you contact our team: - Your site URL - Confirmation of whether you have a manually inserted OTTO pixel script (e.g. pasted into your theme header or a custom HTML field) - Confirmation of whether the Search Atlas WordPress plugin is currently installed and active on your site - A screenshot of the not_installed status in your OTTO dashboard - Any error messages or unusual behaviour you have observed A support teammate will review your specific setup and guide you through the correct steps to resolve the conflict. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏳ Fix OTTO Loading Errors During Site Audit

🔍 Overview If OTTO fails to load after you have completed the setup steps, the most common cause is not a technical error with the installation itself. OTTO requires a completed site audit before it can activate and display your SEO recommendations. This audit can take up to 24 hours to finish, and OTTO will remain in a loading or pending state until it does. This article explains the site audit prerequisite, how to check its progress, and what to do if the process takes longer than expected. 📋 Why the Site Audit Is Required Before OTTO can analyse your website and generate optimisation tasks, it needs a full picture of your site's current SEO health. The site audit crawls your pages, collects technical data, and builds the foundation OTTO uses to prioritise recommendations. Without a completed audit, OTTO has no data to work from and cannot load your dashboard correctly. - The site audit runs automatically when you connect a project to OTTO. - Audit duration depends on the size of your website. Most audits complete within a few hours, but large sites can take the full 24 hours. - No action is required from you while the audit runs. ✅ How to Check Your Site Audit Progress You can monitor the status of your site audit at any time by following these steps: 1. Open the Search Atlas platform and sign in to your account. 2. Navigate to OTTO SEO → Site Audit (All Audits) at /site-audit in the left sidebar. 3. Locate the project connected to OTTO and review the audit status column. 4. If the status shows In Progress or a percentage complete, the audit is still running. This is expected behaviour. 5. If the status shows Completed, return to OTTO SEO → All Sites (SEO Automation) in the left sidebar and reload OTTO. Refreshing the OTTO page before the audit is marked as completed will not speed up the process and may display a loading error. Allow the audit to finish fully before expecting OTTO to activate. 🔄 What Happens When the Audit Completes Once the site audit reaches 100% completion, OTTO updates its status automatically. You do not need to restart the audit or re-connect your project. The expected sequence is: - Site audit status changes to Completed in the audit list. - OTTO activates and loads your personalised SEO task list. - Your dashboard populates with recommendations, fixes, and priority scores based on the audit data. If you are logged in when the audit finishes, simply refresh the OTTO SEO page to see OTTO fully loaded. If you return later, OTTO will load automatically on your next visit. ⚠️ When to Escalate the Issue In most cases, waiting for the site audit to complete resolves the OTTO loading error without any further action. However, you should escalate if any of the following situations apply: - The site audit status has shown In Progress for more than 24 hours without advancing. - The audit status is shown as Completed but OTTO still fails to load after refreshing. - The audit list page shows an error or your project does not appear in the list at all. - You connected your project more than 24 hours ago and have not received any audit progress update. If any of these conditions apply, our team can investigate the audit job directly and resolve any processing delays on the backend. 🛠️ Quick Troubleshooting Summary 1. Check the audit status at OTTO SEO → Site Audit (All Audits) (/site-audit) before assuming an installation problem. 2. Wait up to 24 hours if the audit is still in progress. This is normal and expected. 3. Refresh OTTO via OTTO SEO → All Sites (SEO Automation) only after the audit status shows Completed. 4. Escalate to the team if the audit stalls beyond 24 hours or if OTTO does not load after a completed 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 and Squarespace Builder Sync Conflicts

Why the Sync Gap Happens OTTO deploys SEO fixes to your website outside of Squarespace's visual editor. Because Squarespace's builder manages its own content separately, it may not reflect changes that OTTO has applied. This creates a sync gap: your live site may be correct, but the Squarespace editor appears unchanged. This is expected behavior and does not mean the changes failed. To confirm what is actually live on your site, always verify by viewing the published page directly in your browser rather than relying on the Squarespace editor view. Common Conflict Scenarios Understanding when conflicts occur helps you choose the right approach before making changes. - Meta descriptions: OTTO applies an optimized meta description to your page. If you later edit the meta description inside Squarespace's editor settings and save, Squarespace may overwrite OTTO's value. - Image alt text: OTTO writes alt text to your images. If you replace or re-upload the same image inside Squarespace, OTTO's alt text may be lost. - Page titles: Squarespace controls title tags through its CMS fields. OTTO can override these, but a Squarespace save event on the same page may restore the original title tag. - Schema markup: OTTO-injected structured data lives outside Squarespace's awareness. However, duplicate schema can occur if structured data is also added manually inside Squarespace. Important: The specific conflict scenarios listed above are general patterns based on how Squarespace and OTTO interact. Your exact situation may differ. If you are unsure which scenario applies to you, please reach out to our support team so an agent can review your account directly. Best Practices: Choosing Your Deployment Method Use the following guidance as a starting point when deciding whether to let OTTO manage a fix or handle it natively inside Squarespace. Because this topic requires hands-on review of your specific site and OTTO configuration, our support team can confirm the right approach for your setup. - Let OTTO manage: Schema markup, canonical tags, robots directives, bulk alt text across many images, and technical meta tags where Squarespace provides no native control. - Use Squarespace natively: Page titles and meta descriptions on pages you actively edit and republish often. Entering these directly in Squarespace's editor fields prevents Squarespace from overwriting OTTO's values after every save. - Coordinate both: If OTTO has already deployed a meta description or title and you want to keep it, copy OTTO's exact value into the corresponding Squarespace editor field. This aligns both systems and removes the conflict. - Avoid duplication: Do not add the same structured data or meta tags manually inside Squarespace if OTTO is already managing them, as this can result in duplicate tags on your live page. Verifying Your Live Site To confirm which values are actually live on your published site, use the following methods: 1. Open the published page in an incognito or private browser window to bypass any cached versions. 2. Right-click the page and select View Page Source to inspect the raw HTML and confirm the meta tags, alt attributes, and structured data that are actually being served. If the live page source does not reflect what OTTO deployed, or if you are unsure how to interpret the results, please escalate to our support team. To help us investigate quickly, have the following ready: your project name, the specific page URL where the conflict is occurring, the exact field or tag that appears incorrect, and a screenshot or copy of what you see in both the Squarespace editor and the live page source. If you need further assistance, open 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 Errors on Shopify

🧭 Overview After installing the OTTO SEO pixel on your Shopify store, you may see error indicators in the platform suggesting the pixel is not detected. In many cases, these errors are temporary and appear while the platform is still processing your store's data after installation. This article explains general steps you can take if you encounter pixel errors, and how to get help if the issue persists. ⚠️ Why Errors May Appear After Installation When you first connect OTTO SEO to your Shopify store, the platform begins verifying the pixel signal. During this initial processing period, the pixel status display may show error or pending indicators. These can be temporary states that resolve on their own once processing is complete. You may want to wait a short while after installation before concluding there is a real problem. ✅ General Troubleshooting Steps If you are seeing a pixel error after installing OTTO SEO on Shopify, try the following: 1. Confirm that you completed all installation steps as described in the OTTO SEO setup guide provided during onboarding. 2. Verify that the pixel code snippet was added to your Shopify store's theme as instructed. 3. Wait for the platform to finish its initial processing of your store before re-evaluating the pixel status. 4. Refresh the relevant page in Search Atlas after some time has passed to see if the status has updated. 5. If the error persists after waiting, double-check that your Shopify theme is active and that no recent theme changes removed the pixel snippet. If you have followed these steps and the pixel error is still showing, the issue may require a closer look from our support team. 📋 What to Have Ready When Escalating If the problem cannot be resolved through the steps above, please have the following information ready when you contact support: - Your Search Atlas project name and the Shopify store URL. - The exact error message or status label you are seeing in the platform. - The date and time you completed the pixel installation. - Any recent changes made to your Shopify theme around the time the error appeared. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix False-Positive Audit Flags in OTTO

🧐 Why Am I Seeing These Flags? When OTTO's Site Audit reports Multiple Meta Descriptions or Too Many External Links on a page you know is clean, you are seeing a false positive. These flags are not generated in real time. They reflect the data captured during the last completed analysis crawl. If your page had a temporary issue at the time of that crawl — such as a caching layer serving a duplicate meta description, a plugin injecting extra links, or a deployment that has since been rolled back — the flag will remain visible until the next crawl refreshes the data. In short: OTTO reports what it found during its last crawl, not the current live state of your page. 📋 Common Reasons for Each Flag - Multiple Meta Descriptions: A caching plugin or CDN served a cached page with a duplicate meta tag at crawl time. A theme or SEO plugin was briefly outputting two meta description tags. A staging-to-live deployment temporarily introduced conflicting tags. - Too Many External Links: A widget, footer script, or ad network was active at crawl time and injected additional outbound links. A temporary plugin or A/B test added links that have since been removed. A page template included partner links that were later cleaned up. Because OTTO evaluates the HTML it receives during the crawl, any transient condition present at that moment will be recorded and flagged — even if you fix the issue immediately afterward. ⏱️ When Will the Flags Clear? Flags clear automatically on the next scheduled weekly analysis. OTTO runs a full site analysis on a weekly cycle. Once that analysis completes and no longer detects the issue on your page, the flag will be removed from your audit results. Important: Triggering a manual recrawl or reprocessing a page inside the platform does not refresh Site Audit flags. A manual recrawl updates other data points but does not re-run the full audit analysis that controls these issue flags. Only the weekly analysis cycle does that. ✅ What You Should Do Right Now 1. Open your page in a browser and use View Page Source (right-click → View Page Source) to confirm only one meta description tag is present in the raw HTML. 2. Check your page in an incognito window and via a tool such as Google's Rich Results Test to rule out caching serving a different version to crawlers. 3. Review any active plugins, widgets, or scripts that could inject external links — disable them temporarily if needed and verify the source again. 4. If the page source is clean, no further action is required. The flag will clear automatically after the next weekly analysis runs. 5. Make a note of the date so you can confirm the flag is gone after the next weekly cycle completes. 🔄 How to Check Your Audit Results You can review current Site Audit flags by navigating to Left sidebar → OTTO SEO → Site Audit and opening your OTTO dashboard. Flags are listed under the relevant issue categories. The date of the last completed analysis is displayed at the top of the audit results so you can confirm how recent the data is. ❓ What If the Flag Persists After the Next Weekly Analysis? If the flag is still present after a full weekly analysis has run and your page source is confirmed clean, the issue may be genuine and related to how a crawler or bot sees your page differently from a standard browser. In that case: - Test your URL using a crawler-emulation tool to see what a bot receives. - Check whether your server or CDN is serving different HTML to user agents identified as crawlers. - Review any server-side rendering or JavaScript frameworks that may inject tags or links after the initial HTML is delivered. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Site Audit XML Sitemap Detection Discrepancy Fix

🔍 Why Does This Discrepancy Happen? The Site Audit tool crawls your XML sitemap at a specific point in time. If your sitemap was updated after the last crawl — or if a caching, formatting, or submission issue exists — the tool may show a page as missing even though it appears in your live sitemap. This is a common and fully resolvable issue. Work through the steps below in order. Most customers resolve this in under five minutes. ✅ Step 1: Force a Re-Crawl of Your Site Audit The most common cause is simply a stale crawl. The tool captures a snapshot of your sitemap; any pages added after that snapshot will not appear until you re-crawl. 1. Navigate to OTTO SEO → Site Audit from the left sidebar. 2. Select the project that contains the affected site. 3. Click the Re-Crawl or Recrawl Site button, usually located in the top-right area of the audit dashboard. 4. Wait for the crawl to complete — crawl time varies depending on site size. 5. Once finished, return to the sitemap report and check whether the page now appears. If the page is still missing after a fresh crawl, continue to the next step. 🧹 Step 2: Clear Your Browser Cache and Reload A cached version of the Site Audit dashboard can display outdated results even after a new crawl has completed. 1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac) to open your browser's cache-clearing settings. 2. Select Cached images and files and Cookies and site data. 3. Set the time range to All time and confirm. 4. Close and reopen your browser, then log back into Search Atlas. 5. Navigate back to the Site Audit sitemap report and verify the result. 🔗 Step 3: Validate the URL Format in Your Sitemap The Site Audit tool performs exact URL matching. A mismatch in URL format between what the tool expects and what is declared in your sitemap will cause a page to be flagged as missing even if the content is live. Check for these common formatting issues in your XML sitemap file: - HTTP vs. HTTPS: Ensure all URLs use https://. Mixed protocols cause missed matches. - Trailing slash inconsistency:https://example.com/page/ and https://example.com/page are treated as different URLs. Pick one format and apply it consistently. - www vs. non-www: Confirm your sitemap uses the same domain variant (with or without www) as your canonical URLs. - URL encoding: Special characters in URLs must be properly encoded. Spaces, ampersands, or accented characters that are not encoded will cause detection failures. - Sitemap URL accessibility: Open the sitemap URL directly in your browser (e.g., https://yourdomain.com/sitemap.xml) and confirm the page in question is listed exactly as expected. Correct any formatting issues in your sitemap file, save the changes, and then force a re-crawl following Step 1 again. 📡 Step 4: Verify Your Sitemap Is Submitted in Google Search Console If your sitemap is not submitted to Google Search Console (GSC), or if a recently updated sitemap has not been re-submitted, the Site Audit tool may reference an outdated or incomplete version. 1. Log in to Google Search Console at search.google.com/search-console. 2. Select the correct property for your site. 3. In the left menu, go to Indexing → Sitemaps. 4. Confirm your sitemap URL is listed and shows a Success status. 5. If the sitemap is not listed, click Add a new sitemap, enter your sitemap URL, and submit. 6. If the sitemap is listed but shows errors or a stale last-read date, remove it and resubmit to prompt Google to re-fetch it. After verifying or resubmitting in GSC, return to Search Atlas and run a fresh Site Audit re-crawl (Step 1). ⚙️ Step 5: Check for Multiple or Nested Sitemaps Some sites use a sitemap index file that references multiple child sitemaps. If the page in question lives in a child sitemap that is not linked from the index, the Site Audit tool may not crawl it. - Open your sitemap index file (commonly at /sitemap_index.xml or /sitemap.xml) and confirm it includes a reference to the child sitemap containing the missing page. - If the child sitemap is missing from the index, add the reference and re-submit the sitemap index to GSC. - Then trigger a re-crawl in Site Audit. 📋 Quick Diagnostic Checklist - Re-crawl completed after the page was added to the sitemap - Browser cache cleared before checking results - URL uses HTTPS, consistent trailing slash, and correct www/non-www format - URL is properly encoded with no special character issues - Sitemap is submitted and shows Success status in Google Search Console - Page appears in the correct child sitemap if a sitemap index is in use Working through this checklist resolves the vast majority of sitemap detection discrepancies in Site Audit. If you complete all steps and the page is still showing as missing, the issue may require a deeper technical review. 💬 Still Seeing the Discrepancy? If you need further assistance, open 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 Squarespace /home Path Duplication with OTTO

What Is the Squarespace /home Duplication Issue? Squarespace automatically assigns the path /home to your website's homepage. This means your homepage is accessible at both yourdomain.com and yourdomain.com/home, creating two separate URLs that point to identical content. For OTTO and Search Atlas tracking, this causes a duplication problem: analytics, indexing signals, and SEO data are split across both URLs instead of being consolidated under one canonical address. As a result, your Search Atlas dashboard may show inflated page counts, inconsistent crawl data, or reduced accuracy in performance metrics for your homepage. Why Squarespace Forces This Structure This behaviour is built into Squarespace's platform architecture. Squarespace treats /home as the default internal slug for your homepage and does not allow you to remove it natively. Even if your domain resolves correctly to the root URL for visitors, the /home path remains active and indexable, which means search engines and tracking tools can detect both versions. This is not an OTTO configuration error. It is a platform-level constraint unique to Squarespace that requires a specific workaround to resolve. Recommended Fix: URL Mappings Redirect The confirmed resolution for this issue is to use Squarespace's built-in URL Mappings feature to create a server-side redirect. This permanently redirects /home to your root domain, consolidating all signals to one URL. 1. Log in to your Squarespace account and open your site settings. 2. Navigate to Settings → Advanced → URL Mappings. 3. Add the following mapping on a new line: /home → / 301 4. Save your changes. 5. Return to Search Atlas and allow OTTO to recrawl your site so the updated URL structure is reflected in your dashboard. The 301 redirect tells search engines and OTTO that /home has permanently moved to the root domain. Once the crawl completes, duplication should no longer appear in your dashboard. If you are unsure how to apply this fix or if the duplication persists after completing these steps, please reach out for assistance so our team can review your specific setup. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO Pixel UUID Duplication After Platform Upgrades

What Is Happening and Why After a Search Atlas platform upgrade, your OTTO Pixel may display a duplicated or incorrect UUID in the dashboard. This is a known issue that can occur when a platform upgrade affects the existing pixel configuration. Because this issue involves the relationship between your Search Atlas account and your Google Tag Manager (GTM) setup, the exact steps to resolve it depend on your specific account state and configuration. Generic steps like clearing your cache will not resolve this issue. The root cause is a mismatch between the UUID in your GTM container and the UUID currently active in your Search Atlas account. Resolving it requires locating your current active OTTO Pixel UUID in Search Atlas and ensuring your GTM tag reflects that same UUID. How to Identify This Issue You are likely experiencing this problem if you notice any of the following after a platform upgrade: - Two different UUIDs appear under your OTTO Pixel settings in Search Atlas. - The OTTO Pixel status shows as disconnected or unverified despite the script being present on your site. - GTM is still firing a UUID that no longer matches what appears in your Search Atlas dashboard. - OTTO automations are not triggering or tracking correctly. What to Prepare Before Contacting Support Because the specific resolution for UUID duplication depends on your account configuration and cannot be completed without account-level access, our support team will need to assist you directly. To help us resolve this as quickly as possible, please have the following ready when you reach out: - The name of the affected OTTO project. - The UUID or UUIDs currently showing in your OTTO Pixel settings (screenshot helpful). - The UUID currently in your GTM tag for the OTTO Pixel (screenshot helpful). - The date or approximate time the duplication was first noticed, especially if it followed a platform upgrade. - Whether OTTO automations have stopped triggering or tracking since the issue appeared. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

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

OTTO Schema Not Appearing in Google Rich Results

🔍 Overview When OTTO deploys schema markup, it should appear on your live site and pass Google's Rich Results Test. If you're seeing the wrong schema type or if the schema isn't showing up at all, this is a known issue that requires investigation by our support team. ⚙️ What May Be Happening OTTO schema deployment not appearing in Google Rich Results is a bug-category issue. The root cause can vary depending on your site configuration, and our team will need to investigate your specific setup to identify what is preventing the schema from appearing or validating correctly. 📋 What to Have Ready When You Escalate To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact URL of the page where schema is not appearing. - The schema type you expected OTTO to deploy (e.g., Product, Article, FAQ). - The schema type that is actually appearing, if any (e.g., WebPage, or nothing at all). - A screenshot or copy of the result from Google's Rich Results Test for that URL. - The name of your OTTO project and the date/time you first noticed the issue. - Any recent changes made to the page or site (content updates, plugin changes, theme changes) that may be relevant. If you need further assistance, open 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 Topical Map Generation and Edit Issues

🔍 Overview Two known issues can affect Topical Maps in Search Atlas: articles failing to start generating, and content layout appearing broken after editing headings or meta tags. Both are bugs that our team is actively investigating. This guide explains what to expect and how to escalate effectively if you encounter either issue. ⚠️ Issue 1: Article Generation Fails to Start Some customers find that after clicking to generate articles from a Topical Map, nothing happens — no progress indicator, no status update, and no content is produced. This is a known issue. The root cause has not yet been confirmed, and there is no guaranteed self-serve workaround at this time. 📋 How to Escalate a Generation Failure To help our team investigate as quickly as possible, please have the following ready before reaching out: - Your project or Topical Map name — the exact name as it appears in your account. - The exact time you attempted generation — including your timezone. - The number of articles you selected — how many topics or subtopics you attempted to generate at once. - A description of what you saw — for example, whether any button state changed, whether any error message appeared, or whether the page was completely unresponsive. - Your browser and operating system — for example, Chrome on Windows 11. ⚠️ Issue 2: Layout Corruption After Editing Headings or Meta Tags Some customers report that after editing article headings or meta tags inside Topical Maps, the layout of their content appears broken. This is a known issue currently under investigation. The confirmed root cause has not been identified, and no self-serve fix has been documented. 📋 How to Escalate a Layout Corruption Issue Please gather the following details before contacting support so our team can investigate efficiently: - Your project or Topical Map name — the exact name as it appears in your account. - Which fields you edited — for example, which heading level or which meta tag was changed. - When the issue first appeared — the date, time, and your timezone. - What the broken layout looks like — a screenshot or screen recording showing the problem is extremely helpful. - Where the corruption appears — for example, inside the Search Atlas editor, in an exported file, or on a published 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 MetaSync Rate Limiting and Performance Issues

What Is OTTO MetaSync? OTTO MetaSync is a feature that synchronises meta titles and descriptions deployed by OTTO SEO directly to compatible SEO plugins installed on your WordPress site, including All in One SEO (AIOSEO). When active, MetaSync runs checks on each page load to verify that deployed meta values are still in place. While this keeps your meta data consistent, it can introduce rate-limiting errors and page load performance degradation on high-traffic or resource-constrained WordPress sites. This article explains what is known about this behaviour and how to get support if you are experiencing it. How Meta Titles and Descriptions Are Deployed When OTTO SEO deploys a meta title or description alongside AIOSEO, the interaction between OTTO and the plugin can affect how and whether values are stored persistently in AIOSEO's database. In some configurations, deployed values may not appear inside the AIOSEO editor interface, which can indicate that they are being applied dynamically rather than written directly to AIOSEO's saved fields. If you are seeing any of the following, your site may be affected by MetaSync-related behaviour: - Meta titles or descriptions disappear or do not appear inside the AIOSEO interface after deployment. - You are seeing rate-limiting errors on your WordPress site after enabling OTTO SEO. - You are experiencing increased page load times or higher Time to First Byte (TTFB) after OTTO deployment. What to Do If You Are Affected Because the specific steps to adjust MetaSync settings depend on your site configuration and the version of OTTO SEO you are using, we recommend contacting our support team directly. When you reach out, please have the following ready so we can resolve your issue as quickly as possible: - Your project name and the WordPress site URL affected. - The exact error messages you are seeing (screenshots are helpful). - A description of the performance symptoms — for example, when they started and whether they correlate with a specific OTTO deployment. - The version of the AIOSEO plugin installed on your site. - Any recent changes made to your OTTO SEO settings or deployments. Our team will review your configuration and guide you through the correct steps to resolve rate-limiting errors and restore normal page load performance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting an Unclickable CMS Publish Button

This article addresses a specific issue where the Publish button for a blog post appears visible but cannot be clicked. The steps below walk through common root causes and self-serve checks you can perform before escalating to support. 🔍 Common Causes of an Unclickable Publish Button - Required fields are incomplete: The CMS may block publishing if mandatory fields (such as title, meta description, featured image, or slug) are empty or contain invalid characters. - Content is still processing: If content is still being generated or saved, the publish button may remain locked until that process completes. - Unsaved changes: Edits that have not been saved can cause the publish action to be disabled. - Insufficient role permissions: Your account role may only allow drafting, not publishing. An Admin may need to update your permissions. - Stale browser session: An expired session or cached state can freeze interactive elements including the publish button. 🛠️ Steps to Try 1. Check for validation errors. Scroll through the entire blog post editor and look for any fields highlighted in red or marked with a warning. Fill in all required fields — commonly title, URL slug, and meta description — before attempting to publish again. 2. Wait for any active processing to finish. If content is still being generated or saved, wait until all activity has fully completed before clicking Publish. 3. Save the draft before publishing. Use the save option available in the editor before clicking Publish. This can clear any unsaved-state lock. 4. Check your account permissions. Confirm with your workspace Admin that your account role includes publishing rights. If your role is restricted to drafting only, ask an Admin to update your permissions. 5. Refresh your session. Log out of the platform, clear your browser cache and cookies for the site, then log back in and reopen the post. 6. Try a different browser or an incognito window. Open the same post in a second browser or an incognito tab and attempt to publish. This isolates whether the issue is browser-specific. 7. If the button remains unclickable after all of the above steps, escalate to support. When contacting the team, please have the following ready: the name of the project or blog post affected, the exact URL of the editor page, a description of any error messages or visual indicators you see, and the approximate time the issue began. This information will help the team investigate quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix OTTO Pixel Detection Errors on WordPress

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

🔍 Fix OTTO SEO Changes Not Showing on Google

🧭 Overview After OTTO applies SEO changes to your site, those updates must be crawled and indexed by Google before they appear in search results. If you are not seeing your changes reflected on Google, there are several root causes to rule out — from publication status inside OTTO to sitemap configuration and content quality. Work through the checklist below in order to identify and fix the issue quickly. ✅ Step 1: Confirm Your OTTO Project Is Published OTTO changes only go live on your site when the project is in an active published state. An unpublished or paused project means no changes have actually been pushed to your pages. 1. In the left sidebar, click OTTO SEO, then open All Sites (SEO Automation). 2. Locate the project you are working with and check its status tab (Active or Deep Frozen). 3. If the status shows Deep Frozen, click into the project and reactivate it. 4. Once published, verify the on-page changes appear correctly by visiting the affected URLs directly in your browser. 🗺️ Step 2: Check Your Sitemap Submission in Google Search Console Google needs to discover your updated pages. A missing or outdated sitemap slows down this process significantly. 1. Log in to Google Search Console and select your property. 2. Navigate to Sitemaps and confirm your sitemap URL is submitted and shows a Success status. 3. If no sitemap is submitted, add your sitemap URL (typically yourdomain.com/sitemap.xml) and click Submit. 4. If the sitemap was already submitted but shows errors, regenerate it from your CMS or SEO plugin and resubmit. 🤖 Step 3: Review Your robots.txt File A misconfigured robots.txt can block Google from crawling the pages OTTO has optimised, preventing any changes from being indexed. 1. Open a browser and go to yourdomain.com/robots.txt. 2. Check that Googlebot is not disallowed for the pages or directories you have optimised. 3. Look for lines such as Disallow: / or Disallow: /blog/ that may be blocking key sections of your site. 4. If you find incorrect disallow rules, update the robots.txt file and then request a recrawl in Google Search Console using the URL Inspection tool. 🔎 Step 4: Request Indexing via Google Search Console For high-priority pages, you can ask Google to crawl and index them immediately rather than waiting for the next automatic crawl. 1. In Google Search Console, open the URL Inspection tool. 2. Enter the exact URL of a page where OTTO changes are not showing. 3. If the report shows the page is not indexed or the last crawl date is before your OTTO changes were published, click Request Indexing. 4. Repeat this for up to 10–15 priority URLs. For larger batches, rely on your updated sitemap. 📊 Step 5: Monitor Ranking Changes in Rank Tracker Use Search Atlas to track whether your target keywords begin moving after indexing occurs. This confirms that OTTO's changes are having the intended effect. 1. In the left sidebar, click Keywords, then select Rank Tracker (Keyword Rank Tracker). 2. Filter by the domain associated with your OTTO project. 3. Review ranking positions for the keywords tied to the pages you optimised. 4. Allow 3–14 days after indexing before drawing conclusions, as Google re-evaluates rankings after re-crawling. 📝 Step 6: Audit Content Quality on Affected Pages Even when pages are correctly indexed, Google may not rank them higher if the content does not meet quality thresholds. OTTO optimisations work best when the underlying content is substantive and relevant. - Thin content: Pages with fewer than 300–500 words of meaningful body text are often ranked poorly. Expand the content where needed. - Duplicate content: Ensure the page is not substantially duplicating another page on your site or an external source. - Crawl budget issues: Large sites with many low-value pages may have key pages crawled infrequently. Use the URL Inspection tool to check crawl frequency. - Core Web Vitals: Poor page experience signals can suppress rankings. Review the Core Web Vitals report inside Google Search Console. ⏱️ Step 7: Understand Normal Indexing Timelines If all the above steps check out, the most likely explanation is that Google simply has not crawled the updated pages yet. Typical timelines are: - High-authority domains: 24–72 hours after sitemap submission or indexing request. - New or low-authority domains: 1–4 weeks or longer for organic crawling. - Competitive SERPs: Ranking changes may take 2–6 weeks to stabilise even after indexing. Continue monitoring your Rank Tracker weekly and use the Keyword Gap tool (left sidebar → Site Explorer → Keyword Gap) to identify additional optimisation opportunities while you wait. 💬 Need More Help? If you have completed all the steps above and your OTTO changes are still not appearing in Google after two weeks, there may be a site-specific technical issue that requires deeper investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Understanding OTTO Grader Undeployed Fixes Count

🔍 Overview You may notice that your OTTO Grader displays a total count of undeployed fixes — for example, 344 fixes not deployed — while every individual category shows 0 issues remaining. This can be confusing, but it is a known display behaviour that has a straightforward explanation. 💡 Why This Happens The total undeployed fix count shown on the OTTO Grader summary reflects a cumulative historical snapshot of all fixes that were identified across your site at the time OTTO last ran a full audit. This number does not always update in real time when you resolve issues category by category. There are two common reasons for the mismatch: - Fixes were resolved outside OTTO: Some issues may have been corrected manually in your CMS or by another tool. OTTO tracks that a fix was recommended but cannot automatically confirm it was applied externally, so the count persists until a new full scan is completed. - Pending scan refresh: OTTO updates category-level counts more frequently than the top-level summary. If you recently deployed fixes, the summary total may lag behind the individual category totals until the next full grader sync. 📊 How to View the 344 Undeployed Fixes To investigate which specific fixes make up the undeployed count, follow these steps: 1. In the left sidebar, click OTTO SEO, then open SEO Automation to go to the OTTO dashboard (/seo-automation-v3). 2. Open the OTTO Grader for the relevant site. 3. Review each fix category listed in the grader. Even if a category shows 0 deployable fixes, expand it to check for items marked as Ignored, Skipped, or Not Applicable — these still count toward the undeployed total. 4. Look for a Filters or Status dropdown within each category and set it to show All statuses, not just active ones. This reveals fixes that were dismissed or excluded rather than deployed. 5. Check the Ignored Fixes section if available. Any fix you or a team member previously ignored is excluded from the deployable queue but still included in the undeployed summary count. ⚙️ How to Reconcile the Count Once you have identified where the undeployed fixes are sitting, you have two options to bring the summary count to zero: - Deploy the fixes: If any ignored or skipped fixes are still valid improvements, update their status to active and deploy them through OTTO. - Mark fixes as Ignored or Not Applicable: If certain fixes do not apply to your site (for example, recommendations for page types you do not use), explicitly mark them so OTTO can exclude them cleanly from the count. After taking either action, trigger a manual rescan by navigating to OTTO SEO → Overview (OTTO Grader) to recalculate the summary total against the current state of all categories. 🚀 Best Practices to Keep Your Count Accurate - Run a full OTTO Grader rescan after making bulk changes to your site, whether through OTTO or manually in your CMS. - Regularly review the Ignored fixes list to ensure nothing important has been accidentally dismissed. - Address fixes category by category and rescan between sessions so the summary total stays in sync. - Avoid making large structural site changes (URL changes, template updates) without triggering a rescan immediately after, as stale fix recommendations can inflate the undeployed count. 🙋 Still Need Help? If you have followed the steps above and your undeployed fix count still does not reflect the correct number, or you cannot locate where the 344 fixes are categorised, our team is happy to 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.

🔁 Resolving a Persistent OTTO Pixel Duplicate Badge

🧭 Overview The Duplicate Installation badge appears on your project when Search Atlas detects more than one instance of the OTTO pixel firing on your site. Removing the extra snippet from your page source is often not enough — if the original injection method is still active in your CMS, plugin, or tag manager, the pixel continues to load twice and the badge persists even after a recrawl. 🔍 Step 1 — Verify the Frontend HTML First Before changing anything in your CMS, confirm exactly how many pixel instances are present on your live site. 1. Open any page on your website in a browser. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (or Cmd + F on Mac) and search for your OTTO pixel ID or the script tag otto-pixel. 4. Count every match. If you see more than one result, note the surrounding code for each — this tells you which injection methods are active. 5. Repeat this check on at least two other page types (homepage, a blog post, a product page) because some injection methods are template-specific. 🗂️ Step 2 — Remove the Pixel by Injection Method Match your setup to the correct removal procedure below. Deleting code from one location while another method is still enabled will reproduce the duplicate on every page load. - WordPress plugin (e.g., Insert Headers and Footers, WPCode): Go to the plugin's settings page in your WordPress dashboard, locate the OTTO pixel snippet, and delete the entry entirely. Disabling the snippet toggle is not sufficient — remove the entry so it cannot re-enable on a plugin update. - Theme template files (functions.php, header.php, or equivalent): Access your theme's file editor or connect via FTP/SFTP, find the pixel code in your theme files, delete it, and save. If a child theme is active, check both the child and parent theme files. - Google Tag Manager: Log in to your GTM workspace, find the OTTO pixel tag, and disable or remove it before publishing a new container version. Verify the tag is no longer firing before publishing; delete the tag permanently once confirmed. - Other tag managers (Segment, Tealium, Adobe Launch): Follow the same logic — locate the tag or rule that injects the pixel script, disable or delete it, then publish the updated container. - Shopify (theme template or app embed): In your Shopify admin, access your theme's code editor and search your main layout file (e.g., theme.liquid) for the pixel snippet and remove it. Also review any installed apps that inject header scripts, and check any store preferences or script fields where pixel code may have been added. - Hard-coded HTML (static sites or custom CMS): Remove the script block directly from your base template file, then redeploy or republish your site so the change takes effect on all pages. 🔄 Step 3 — Clear Caches and Trigger a Recrawl After removing all extra instances, caches at the server, CDN, or plugin level may continue serving the old page source. Clear every cache layer you have access to before requesting a new crawl in Search Atlas. 1. Clear your hosting or server-side cache. 2. Purge any CDN cache (Cloudflare, Fastly, etc.). 3. If you use a WordPress caching plugin, purge it from the plugin's dashboard. 4. Return to Search Atlas, open the affected project, and trigger a recrawl so the platform can re-evaluate the pixel installation count. ⚠️ What to Do If the Badge Persists If the Duplicate Installation badge remains after completing all steps above, the pixel may still be loading from an injection point you haven't yet identified. Before reaching out for help, have the following ready: - Your project name in Search Atlas. - The URL of a page that still shows two pixel instances in View Page Source. - A description of every injection method you've already removed (plugin name, file name, tag manager tag name, etc.). - Screenshots or a copy of the relevant source code showing the duplicate. If you need further assistance, open 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 'Not Found' After Cloudflare Setup

Overview If you are seeing a 'not found' status after connecting your Cloudflare API token to OTTO, this may be related to how OTTO's pixel installation interacts with your custom site configuration. Because the details of this issue can vary depending on your specific site setup, our support team will need to review your case directly to identify the correct resolution. What to Have Ready Before Contacting Support To help our team resolve your issue as quickly as possible, please have the following information available when you reach out: - Your site URL where OTTO is being installed. - The exact 'not found' error message or status text shown in the platform. - A description of how you completed the Cloudflare API token connection and any steps you have already tried. - Any screenshots of the error or relevant settings pages. If you need further assistance, open 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 Empty On-Page Audit Results After Plugin Install

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

📱 Fix Approval Button Hidden on iPhone

🔍 Overview Some iPhone users find that the approval button inside the Search Atlas platform appears below the visible screen area, making it difficult or impossible to tap. This is a known display issue on iOS mobile browsers. The steps below offer general workarounds you can try to access the approval button on your iPhone. 📋 Affected Area - Feature: Tool approval workflow - Affected devices: iPhone (iOS Safari and other mobile browsers) 🛠️ Workarounds to Access the Approval Button Try the following options in order. Most users are able to resolve the issue with one of these approaches. 1. Scroll down on the approval screen. After the approval prompt loads, place your finger on the screen and scroll downward. The button may simply be off-screen and reachable by scrolling. 2. Rotate your iPhone to landscape mode. Turn your device sideways to switch to landscape orientation. The wider view often brings hidden UI elements into the visible area. 3. Zoom out in your browser. Reduce the zoom level in your browser settings and reload the page, then try tapping the approval button again. 4. Request the desktop site. Most iOS browsers offer an option to load the full desktop version of a website. Enabling this forces the full desktop layout, which may position the button correctly. 5. Use a different browser. If your current browser is not working, try an alternative iOS browser. Navigate to app.searchatlas.com, log in, and retry the approval step. 6. Switch to a desktop or laptop. If none of the above options work, completing the approval action from a desktop browser is the most reliable alternative. ⚙️ Current Status This is a known usability issue on iPhone devices. No action is needed on your end beyond the workarounds above. If you need further assistance, open 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 Cache Conflicts With Hosting Providers

🔍 Overview Search Atlas OTTO applies on-page optimizations — including caching directives — to help improve your site's SEO performance. However, if your hosting provider also runs its own caching layer, these two systems can conflict. The result is often slower page load times, stale content being served, or unexpected behavior after OTTO makes changes. This article explains why the conflict happens and what to do if you experience it. ⚠️ Why This Conflict Happens Many managed hosting providers and CDN services cache your site's pages at the server or edge level. When OTTO also applies cache-related optimizations, both systems may attempt to control what gets cached and for how long. Common symptoms include: - Pages loading more slowly than before OTTO was activated - OTTO changes not appearing on the live site immediately - Mixed or inconsistent page versions being served to visitors - Core Web Vitals scores declining after OTTO deployment 🧩 How To Identify the Conflict 1. Run a speed test on a key page (e.g. using Google PageSpeed Insights or GTmetrix) before and after OTTO activation to confirm the degradation is linked to OTTO. 2. Check your hosting control panel to see whether server-level caching is active. 3. Temporarily purge all caches from your hosting dashboard and retest your page speed. If performance improves, a cache conflict is likely the cause. 🛠️ What To Do Next Because this issue involves an interaction between OTTO's optimization layer and your hosting provider's caching system, resolving it may require investigation by our engineering team. This is a known area where backend configuration changes can be needed. When contacting support, please have the following ready: - The name of the project or site affected in Search Atlas - Your hosting provider's name - A description of the symptoms you are seeing (e.g., slower load times, stale pages) - Approximate date and time when the issue started - Any speed test results or screenshots you have collected Having this information ready will help our team investigate and resolve the conflict as quickly as possible. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix OTTO WordPress Plugin 'Not Detected' Error

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

🛠️ Fix OTTO Plugin Error 403 and Performance Issues

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

🛠️ Fix Display Issues in Your Projects Section

🔍 Overview Some customers notice unexpected content, overlapping elements, or unusual behaviour when clicking on the Projects section of their account. This article walks you through the most common causes and the steps you can take to resolve them quickly. ⚙️ Common Causes of Projects Display Issues UI display problems in the Projects section are usually caused by one of the following: - Cached browser data — outdated files stored in your browser can cause the interface to render incorrectly. - Browser extensions — ad blockers, script blockers, or other extensions may interfere with how the platform loads. - Unsupported or outdated browser — the platform works best on the latest versions of Chrome, Firefox, Edge, or Safari. - Temporary session error — a interrupted login session can occasionally cause elements to display out of place. - Account or project configuration — in some cases, a specific project setting or permission level may trigger unexpected display behaviour. 🚀 Step-by-Step Troubleshooting Follow these steps in order. Most display issues are resolved within the first few steps. 1. Hard refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force the browser to reload the page without using cached files. 2. Clear your browser cache and cookies. Go to your browser settings, clear all cached images, files, and cookies, then reload the platform. 3. Disable browser extensions. Temporarily turn off any extensions — especially ad blockers or script managers — and check if the issue persists. 4. Try a different browser or an incognito/private window. This rules out browser-specific conflicts. If the Projects section displays correctly in a private window, a browser extension or cached data is likely the cause. 5. Log out and log back in. Sign out of your Search Atlas account, close the tab, reopen the platform, and sign in again to start a fresh session. 6. Check on a different device. If possible, access your account from another computer or device to determine whether the issue is device-specific. 📊 Checking Your Project Settings If the display issue is limited to a specific project, it may be related to how that project is configured. To review your project settings: 1. Navigate to the Projects section from your main dashboard. 2. Click on the affected project to open it. 3. Review the project details, including any assigned team members or connected domains, for anything that looks incomplete or misconfigured. 4. If a project appears duplicated, blank, or showing data from a different project, note the project name and the exact behaviour you are seeing before reaching out for support. 👥 Reviewing Team Member Access Display discrepancies can sometimes occur when account permissions are inconsistent across team members. To check your team settings, click your avatar in the top-right corner of the platform and select Team Members, or navigate directly to /settings. Confirm that roles and project access are configured as intended for each user. 💡 When to Contact Support If you have completed all the steps above and the issue is still present, our support team can investigate your specific account and project 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. To help us resolve your issue as quickly as possible, please have the following ready before reaching out: - The name of the affected project - A description of what you see when clicking on Projects (e.g. blank screen, duplicate entries, wrong data) - The browser and device you are using - A screenshot or screen recording of the issue, if possible

🔧 Fix Stagnant Content Scores and Remove Injected Keywords

Overview This article covers two common issues in the SEO Content Assistant: removing keywords that have been injected into your page by the tool, and troubleshooting a content score that isn't moving despite significant content work. Both issues have distinct causes and fixes — work through each section that applies to you. How to Remove Injected Keywords The SEO Content Assistant may inject suggested keywords into your content as part of its optimization recommendations. These can be removed manually from the editor at any time. 1. Open the SEO Content Assistant and locate the page you are working on. 2. Open the editor for that page. 3. Identify the injected keyword text you want to remove within the editor canvas. 4. Click on the relevant text to select it, then delete it using your keyboard. 5. Save your changes once you have finished editing. If the keyword reappears after saving, your page content may not have synced correctly. Try closing and reopening the editor, then repeat the steps above. Why Your Content Score Isn't Moving A stagnant content score is one of the most common — and most frustrating — issues in content optimization. If you have made significant edits and the score has not changed, work through the checks below in order. Check 1 — Trigger a Fresh Analysis The content score does not update automatically every time you make edits. After completing your changes, look for an option within the SEO Content Assistant to re-analyze or refresh the score for your page. The exact label may vary, but this action tells the tool to re-evaluate your content based on your latest edits. 1. Open your page in the SEO Content Assistant. 2. After completing your edits, locate and click the button or option that triggers a new content analysis. 3. Wait for the analysis to fully complete before reading the updated score. If you do not trigger a fresh analysis, the score displayed may still reflect your content from a previous session. Check 2 — Close and Reopen the Editor The editor can sometimes display a version of your page that does not reflect your most recent saves. If your score still appears frozen after triggering a fresh analysis, try the following: 1. Save your current work. 2. Close the page editor completely. 3. Hard-refresh your browser: press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. 4. Reopen the page in the SEO Content Assistant and trigger a new analysis. Check 3 — Verify Your Content Has Saved Correctly If you are still not seeing score movement after the steps above, it is worth confirming that your edits were actually saved before the analysis ran. Open the editor again, review the content on screen, and confirm it reflects all the changes you intended to make. If you need further assistance, open 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.

🛠️ Troubleshooting OTTO SEO Deployments Not Reflecting in Shopify

This article explains what the Deployed status means in OTTO SEO, why changes sometimes appear deployed inside Search Atlas but have not yet updated your Shopify store, and how to verify that your changes are truly live. 🔍 What "Deployed" Actually Means When OTTO SEO shows a change as Deployed, it means the change has been approved and pushed from Search Atlas toward your connected Shopify store. However, deployment is a two-step process: Search Atlas sends the update, and Shopify must successfully receive and apply it. A Deployed status confirms the first step — it does not always guarantee Shopify has finished writing the change to your storefront. 🔎 Common Reasons Changes May Not Appear in Shopify - Shopify sync delay: Shopify can take several minutes to propagate metadata and content changes across its CDN. Wait at least 5–10 minutes before concluding a change is missing. - Disconnected or re-authenticated integration: If the Search Atlas–Shopify connection was interrupted (for example, after a password reset or app permission change), deployments may not reach Shopify even though they show as Deployed inside Search Atlas. 🛠️ Steps to Take 1. Wait at least 5–10 minutes after a deployment before checking whether the change has appeared in your Shopify store, as sync delays are common. 2. Check your Shopify integration status inside Search Atlas to confirm the connection between Search Atlas and your Shopify store is still active. If you suspect the connection was interrupted, reconnect by going through the integration setup flow and re-authorizing the Search Atlas app inside your Shopify admin. 3. In your Shopify admin, navigate to the affected page, product, or post and inspect the relevant field (such as meta title or meta description) directly in the Shopify editor to see what value Shopify is currently storing. 4. If the value in Shopify does not match what was deployed from Search Atlas, contact the support team with your project name, the specific URL or resource affected, the exact field that was changed, and the approximate time of deployment so the team can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Schema Deployment Stuck in Manual Review

🔍 Overview Some OTTO users have encountered a situation where schema deployments appear to succeed — the API returns a 'Success' response — but no schemas actually deploy. Affected schemas remain frozen in manual review status and cannot be deployed or modified. This article explains what caused this issue, what was fixed, and what to do if you are still affected. ⚙️ What Caused the Issue Engineering identified two root causes that prevented schemas from moving out of manual review: - Invalid data types for image dimensions: ImageObject schemas had width and height values stored as strings instead of the required numeric format. This caused schema validation to incorrectly block deployment of otherwise valid schemas. - Missing review or rating data: Certain schemas were flagged for manual review when the pages they were associated with lacked review or rating data. Once in review, the schemas could not be deployed or corrected — even after regeneration, no fields were presented to fix. These issues were confirmed by engineering and tracked internally. The underlying bugs have been fixed and the fix is live in production. ✅ What Was Fixed Engineering resolved the schema validation logic that was incorrectly blocking valid schemas from deploying. Specifically: - The validation error caused by string-formatted width/height values in ImageObject schemas has been corrected. - Schemas stuck in review due to absent review or rating data can now progress through the deployment pipeline without being blocked. Following the fix, affected schemas were manually reprocessed by the engineering team to regenerate and redeploy the pending queue. 🚀 What You Should Do Now If you experienced this issue, follow these steps to confirm your schemas are now deploying correctly: 1. Log in to your Search Atlas account and navigate to the OTTO section of your dashboard. 2. Check the status of your pending schemas. Schemas that were previously frozen in manual review should now show an updated status. 3. If schemas were recently reprocessed, allow a short period for the deployment queue to clear and for statuses to refresh. 4. Attempt to deploy any remaining schemas that are still in a pending or review state. If the option is now available, proceed with deployment as normal. 5. Verify that your deployed schemas are returning correctly by checking the relevant pages or using a schema validation tool of your choice. ⚠️ If Schemas Are Still Stuck The fix is live, but if your schemas are still showing as frozen in manual review or still not deploying after following the steps above, your account may need a manual reprocess triggered by our team. This is not something you can initiate yourself — our support team handles it 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. 💡 Tips to Avoid Schema Issues - Ensure that pages associated with schemas have sufficient structured data, including review and rating information where applicable, before initiating deployment. - If a schema enters manual review and presents no fields to correct after regeneration, do not attempt repeated deployments — contact support so the issue can be escalated to engineering promptly. - Monitor your schema statuses after bulk deployments to catch any that stall early.

🛠️ Fix Incorrect OTTO Title Tag Recommendations

🔍 Overview OTTO SEO analyses your site's title tags and suggests improvements when it detects issues. Occasionally, OTTO may flag title tags that are already well-optimised, generating recommendations that do not reflect real errors. This article explains why this happens and what you can do about it. ⚙️ Why OTTO Flags Correct Title Tags In some cases, OTTO compares a generated title tag suggestion against your existing title tag and does not recognise that they are identical or equivalent. Instead of marking the recommendation as unnecessary, OTTO surfaces it as an actionable change. This is a known issue that our engineering team is actively working to resolve. Specifically: - OTTO may generate a title tag that matches your current title exactly but still presents it as a recommended change. - Recommendations may persist through deployment cycles even after the underlying issue has been addressed. - Affected sites may see a non-zero title tag error count despite having fully optimised titles. 📊 How to Review Your Title Tag Recommendations 1. Open OTTO SEO and navigate to your site's title tag recommendations. 2. Review each flagged recommendation and compare the suggested title against your current live title tag. 3. If the suggested title is identical or equivalent to your existing tag, the recommendation does not reflect a genuine error and can be safely dismissed. 4. For recommendations where a real difference exists, evaluate whether the suggested change represents a genuine improvement before applying it. 🚀 What to Do If Incorrect Recommendations Persist If OTTO continues to show title tag errors for pages you know are correctly optimised, follow these steps: 1. Confirm the existing title tag on the affected page is live and correctly set in your CMS or site code. 2. Trigger a fresh crawl from within OTTO SEO so the tool analyses the most current version of your pages. 3. After the crawl completes, return to the title tag recommendations and check whether the error count has updated. 4. If incorrect recommendations remain after a fresh crawl, note the affected page URLs so you can share them with our support team for manual review and removal. 💡 Best Practices for Title Tags - Keep title tags concise to avoid truncation in search results. - Include your primary keyword naturally near the beginning of the title. - Ensure each page on your site has a unique title tag that accurately describes the page content. - Avoid duplicating title tags across multiple pages. If you need further assistance, open 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 Competitor Page Display Issues

🔍 What this article covers Search Atlas comparison pages, including Search Atlas vs Ahrefs, Semrush, Surfer SEO, and all SEO tools, are public webpages. If a page appears to have broken CSS, missing styling, or an unusual layout, the issue is usually related to cached files, browser extensions, or a temporary website asset problem. 🧹 Try these quick fixes 1. Refresh the page using a hard refresh: Ctrl + Shift + R on Windows or Command + Shift + R on macOS. 2. Open the page in a private or incognito window. 3. Try a different browser or device. 4. Disable ad blockers, privacy tools, translation tools, and other browser extensions temporarily. 5. Clear cached images and files for searchatlas.com, then reload the page. 6. Check whether the issue affects one comparison page or several. 📄 Comparison pages to check - Search Atlas vs Ahrefs - Search Atlas vs Semrush - Search Atlas vs Surfer SEO - Search Atlas vs All SEO Tools Use the page address shown in your browser when reporting a problem. This helps the team identify the affected template or page asset. 📝 What to include in a report If the issue continues after the steps above, collect the following details: - The full page URL - A screenshot or short screen recording - Your browser and operating system - Whether the issue occurs in a private window or another browser - The approximate date and time you noticed the issue - Any visible error message or missing page element ⚙️ Using Search Atlas while the page is unavailable A display issue on a public comparison page does not necessarily affect the Search Atlas platform. You can continue using the platform through the left sidebar, including Site Metrics for Site Explorer, Keyword Magic, Rank Tracker, and Keyword Gap, or Local for local SEO projects and related tools. 💬 Get help from our team If the layout remains broken after troubleshooting, share the details through the platform so the issue can be reviewed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot Non-Clickable Loop Artifacts

🔍 What this issue means Some loop runs produce output artifacts that appear in Search Atlas but cannot be opened or clicked. This usually means the output is still loading, was not saved as an interactive artifact, or the page displayed an outdated session state. ✅ Check the loop output 1. Open the loop and wait for the run to finish completely. 2. Check whether the output is labeled as an artifact, result, or plain text. Only interactive artifacts include an openable destination. 3. Refresh the page once the run is complete. A refresh can restore the artifact when the first page load shows incomplete output data. 4. Open the loop again and check whether the artifact is now clickable. 🧭 Understand expected behavior Not every loop output is designed to open as a separate artifact. Text, status messages, evaluation results, and other informational output may be displayed without a link. Interactive outputs should provide a clickable target when the artifact has been successfully created and saved. ⚙️ If the artifact remains unavailable - Confirm that the loop run completed without an error. - Try refreshing the page and reopening the relevant workspace or issue. - Check whether the output appears consistently across repeated runs. - Record the loop name, run time, output type, and the URL of the affected page. - Take a screenshot showing the non-clickable output, if possible. Do not repeatedly regenerate the loop if the output is missing. Re-running may create a different result and make the original issue harder to investigate. 💬 Contact support If the output should be interactive but remains non-clickable after these steps, share the recorded details with our team so we can investigate the specific run. If you need further assistance, open 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 Brand Vault Image 404 Errors in Website Studio

🔍 Overview When you add images from the Brand Vault to a landing page in Website Studio, you may encounter a 404 error — meaning the image fails to load and displays a broken link instead. In some cases, an error pop-up also appears during page preview and cannot be dismissed. This article explains what causes this issue and walks you through the steps to resolve it. ⚠️ What Causes This Error This issue is triggered by a known bug where Brand Vault filters carry over incorrectly into the image path, causing the image URL to break. Specifically: - The image URL generated by the Brand Vault includes an invalid filter segment (e.g., /images/ is appended incorrectly), making the path unresolvable. - This can affect images added to landing pages, clone mode pages, and PPC sites built inside Website Studio. - The bug has also been known to prevent images from being added to a page even after a successful Brand Vault upload. The underlying engineering fixes for this bug have been deployed. If you are still experiencing the issue, follow the steps below to resolve it on your end. 🛠️ How to Fix Brand Vault Image 404 Errors 1. Navigate to Website Studio. In the left sidebar, click Website Studio (URL: /website-studio). 2. Open your affected landing page and locate the section where the broken image appears. 3. Remove the broken image. Click on the image element and delete it from the page. 4. Re-open the Brand Vault image picker. Click the image placeholder or the insert image option within the page editor. 5. Re-select your image from Brand Vault. Browse to the correct image and insert it fresh. Do not use a previously copied image URL — always select directly from the Brand Vault picker to ensure a clean URL is generated. 6. Preview the page again. Click the preview option to confirm the image now loads correctly and the error pop-up no longer appears. 7. Save and publish your page once the image displays as expected. 💡 Tips to Prevent This Issue - Always upload images to the Brand Vault before building or editing your landing page, so the assets are fully processed and available. - Avoid duplicating or copy-pasting image URLs from previous pages — always re-select images through the Brand Vault picker. - If you are working with clone mode pages, re-link any Brand Vault images after cloning, as image references may not carry over correctly. - After uploading a new image to the Brand Vault, wait a few seconds before inserting it into a page to allow the asset to finish processing. ✅ Confirming the Fix Once you have re-inserted the image directly from the Brand Vault picker, preview your page to verify: - The image displays correctly without a broken icon or placeholder. - No 404 error pop-up appears during preview. - The published version of the page renders the image as expected for visitors. If the image still fails to load after following these steps, the asset itself may not have uploaded successfully. Try deleting and re-uploading the image to the Brand Vault, then insert it into the page again. 🙋 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.

🛠️ Troubleshooting Page Schema Generation

This article explains what to do when page-level schema credits are used but no generated schemas appear in Search Atlas. Follow the self-serve steps below to resolve the issue on your own before reaching out to our team. 🔍 Step 1 — Verify Your Schema Output Location Generated schemas may not appear where you expect them. Check the following: - Navigate to the affected page inside your Search Atlas project and look for a Schema or Structured Data section within the page editor or page details panel. - Confirm you are viewing the correct project — schemas are stored per-project, so switching projects will show different results. - If you ran generation in bulk, allow a few minutes for all pages to finish processing before concluding that output is missing. 🔄 Step 2 — Check Page Classification Schema generation results depend on the page type classification assigned to each URL. An incorrect classification can cause the generator to produce no usable output or consume credits without visible results. - Open the affected page in your project and review the Page Type or classification setting (e.g., Article, Product, Local Business). - If the classification looks incorrect, update it to match the actual content of the page. - Save the updated classification before retrying generation. 🔁 Step 3 — Retry Schema Generation for One Page Before retrying your entire batch, test with a single page to confirm the fix works and to avoid consuming additional credits unnecessarily. - Select one of the affected URLs in your project. - Trigger schema generation for that page only. - Wait for the process to complete, then check whether the schema output now appears correctly. - If the single-page retry succeeds, you can proceed to re-run generation for the remaining affected pages. 📊 Step 4 — Review Credit Usage To confirm how many credits were consumed versus how many schemas were successfully produced: - Navigate to your account's Credits or Usage section in Search Atlas. - Compare the number of credits deducted against the number of schemas that appear in your project. - Note any discrepancy (e.g., 10 credits used, 0 schemas visible) so you have this information ready if you need to escalate. ✅ If the Issue Persists — How to Escalate Effectively If the steps above do not resolve the problem, our team can investigate at the backend level. Please have the following ready when you reach out: - The affected project name - The specific URLs that failed - The schema type selected for each affected page - The number of credits used without a result - Any error messages or unexpected behavior you observed - The approximate date and time the generation was run If you need further assistance, open 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 Crash, Lost Pages & ROI Discrepancy Explained

🔍 Overview Some customers have noticed a sharp drop in Flawless Pages, unexpected changes in OTTO ROI figures, or both — often following a period of site instability. This article explains the most common causes, what happened behind the scenes, and the steps you can take to stabilise and restore your results. ⚠️ Why Did My Flawless Page Count Drop So Dramatically? A sudden drop in Flawless Pages (for example, from 600+ down to 96) is almost always caused by one or more of the following technical events: - OTTO recrawl crash: A known bug caused OTTO's recrawl process to crash when it encountered pages with a NULL status code. This halted suggestion generation and left affected URLs in an unresolved state. - Meta data rollback: In some cases OTTO rolled back previously applied meta data and keyword optimisations, causing pages that were previously counted as Flawless to lose their optimised status. - 500 errors introduced by OTTO Gateway: A Metasync/OTTO Gateway issue rewrote valid 200 responses as 500 (API_ERROR) on certain URLs. Google Search Console began de-indexing those pages, removing them from the Flawless count. - Lost canonical tags: A rendering issue caused OTTO to drop canonical URLs on specific render paths, which can cause Google to treat pages as duplicate or unverified, reducing the Flawless count. - Site stuck in manual reprocess state: If OTTO got stuck reprocessing your site, new optimisations could not be applied and previously counted pages reverted to an unoptimised state. Credits spent on pages that were later affected by these bugs are a legitimate concern. Please escalate through the chat widget (instructions at the bottom of this article) so our team can review your account and arrange any appropriate credit adjustment. 📊 Why Are My OTTO ROI Figures Changing (e.g. $165K → $105K)? OTTO ROI is a dynamic, recalculated estimate — it is not locked in at the moment optimisations are applied. The figure changes whenever: - The underlying page count changes (e.g. pages drop from Flawless back to Needs Work after a rollback or error). - Keyword ranking data refreshes from Google Search Console or our crawler, updating traffic and value assumptions. - Pages are de-indexed by Google following server errors (500s), reducing the estimated organic value OTTO can claim. - OTTO re-scans your site and discovers pages that were previously miscounted or skipped due to the NULL status-code crash. This means a drop from $165K to $105K does not necessarily mean $60K of real revenue was lost — it reflects a corrected calculation after page or ranking data changed. Once underlying issues are resolved and pages return to Flawless status, the ROI figure will recover accordingly. 🚀 Steps to Stabilise OTTO and Recover Your Pages 1. Run a fresh scan: Go to Left sidebar → OTTO SEO → All Sites and click Scan next to your site. This forces OTTO to recrawl with the latest fixes applied and clears stale NULL status-code entries. 2. Check for stuck reprocessing: In Left sidebar → OTTO SEO → Overview, confirm your site does not show a Processing or Pending status badge. If it does, contact support immediately via the chat widget. 3. Review the All Audits log: Navigate to Left sidebar → OTTO SEO → All Audits to see a history of changes OTTO applied or rolled back. This helps you identify which pages lost their optimisations and when. 4. Check Crawl Monitoring for 500 errors: Go to Left sidebar → OTTO SEO → Crawl Monitoring and filter by 5xx status codes. Any URLs showing 500 errors should be flagged to support so the Gateway rewrite issue can be investigated for your domain. 5. Re-apply optimisations to reverted pages: Once the scan completes and no errors remain, OTTO will automatically re-suggest optimisations for pages that were rolled back. Apply them to restore your Flawless count. 6. Monitor GSC re-indexing: After 500 errors are resolved, Google typically re-crawls and re-indexes affected pages within 1–4 weeks. Your ROI figure will rise again as those pages return to the index. 💡 How to Prevent This From Happening Again - Keep a staging environment key active if your site uses custom render paths — this prevents OTTO from bailing out and dropping canonicals mid-render. - Do not freeze and unfreeze OTTO rapidly during active reprocessing, as this can trigger the stuck-state bug. - Check Crawl Monitoring weekly for any spike in 4xx or 5xx errors so you can catch gateway issues before Google de-indexes pages. - Review the All Audits log after every OTTO scan to confirm optimisations were applied and not rolled back. 🙋 Still Seeing Discrepancies? If your page count or ROI figures continue to fluctuate after following the steps above, or if you believe credits were unfairly consumed during a crash event, our support team can manually audit your account history and arrange corrections. If you need further assistance, open 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 Crashes, Lost Pages, and ROI Discrepancies Explained

🔍 Overview Some customers have noticed a significant drop in Flawless Pages, unexpected changes in OTTO ROI figures, and lost keyword or meta optimizations after experiencing an OTTO crash or site error. This article explains why these issues occur, what triggers them, and the steps you can take to recover and prevent further data loss. ⚠️ Why OTTO Crashes Can Cause Page and ROI Drops OTTO continuously crawls and applies optimizations to your site. When a critical error occurs during a crawl cycle — such as a failed URL status check, a gateway rewrite error, or a site getting stuck in a reprocess state — OTTO may do one or more of the following: - Roll back previously applied meta data and keyword optimizations to a safe state, causing Flawless Page counts to drop. - Fail to generate new suggestions because URLs could not be connected or crawled successfully. - Convert successful page responses (200) to errors (500) if the OTTO gateway encounters an API fault, which can trigger de-indexing in Google Search Console. - Lose canonical URL settings on render paths where OTTO exited unexpectedly. These behaviors are built-in safety mechanisms, but they can have a visible and frustrating impact on your reported metrics. 📊 Why Page Counts and ROI Figures Fluctuate OTTO ROI and Flawless Page counts are calculated dynamically each time OTTO scans your site. If your site experienced a crash and then a partial recovery, you may see figures jump between values (for example, 382 pages one day and 275 the next, or ROI shifting from $165K to $105K) for the following reasons: - Recrawls re-evaluate every page from scratch. Pages that were previously counted as Flawless may no longer meet all criteria if optimizations were rolled back. - Credits spent during the crash period may not be reflected in recovered data. If OTTO applied fixes that were later rolled back due to an error, those pages lose their Flawless status even though credits were consumed. - ROI is tied directly to Flawless Page count. As the number of optimized pages changes, the estimated ROI recalculates automatically. There is no manual override — the figure always reflects the current state of your site. - Indexing delays from Google can cause further discrepancies between what OTTO reports and what is visible in Google Search Console. 🚀 How to Check Your Current OTTO Status 1. Go to Left sidebar → OTTO SEO → Overview to see your current Flawless Pages count and OTTO ROI figure. 2. Navigate to Left sidebar → OTTO SEO → All Audits to review any recent audit findings and identify pages that lost their Flawless status. 3. Check Left sidebar → OTTO SEO → Crawl Monitoring to see if any crawl errors or stuck states are currently active on your site. 4. If your site shows a status that appears frozen or unresponsive, go to Left sidebar → OTTO SEO → All Sites and use the Scan action to trigger a fresh crawl. 🛠️ Steps to Recover Lost Optimizations 1. Trigger a new scan. Go to Left sidebar → OTTO SEO → All Sites and select Scan next to your affected site. This forces OTTO to re-evaluate all pages and re-apply eligible optimizations. 2. Review rolled-back pages. In Left sidebar → OTTO SEO → All Audits, filter for pages that previously had optimizations and now show issues. Re-apply fixes manually where needed. 3. Check canonical URLs. If OTTO exited unexpectedly on certain render paths, canonical tags may be missing. Confirm canonical settings are correctly applied on affected pages after the next crawl completes. 4. Monitor Google Search Console. If any URLs returned 500 errors during the crash window, check GSC to confirm those URLs are being re-indexed. It may take several days for Google to re-crawl and restore rankings. 5. Avoid re-processing during active errors. If OTTO is still showing crawl failures, wait for the current scan to complete or contact support before running additional scans, as overlapping processes can compound data loss. 💡 How to Prevent This in the Future - Use the Freeze feature cautiously. You can freeze sites in Left sidebar → OTTO SEO → All Sites using Freeze sites to pause automated changes if you suspect instability. - Monitor Crawl Monitoring regularly. Checking Left sidebar → OTTO SEO → Crawl Monitoring after major site changes helps you catch stuck crawl states before they escalate. - Document your baseline. Take note of your Flawless Pages count and ROI figure after each successful scan so you have a reference point if figures shift unexpectedly. 💬 Still Seeing Discrepancies? If your page counts or ROI figures continue to fluctuate after completing a fresh scan, or if you believe credits were consumed for optimizations that were subsequently rolled back without resolution, our team can investigate your specific site history. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting Playbook Page Errors

This article helps you resolve a “page not found” error when opening a playbook in Atlas Agent. 📍 Where to Find It Open Home from the left sidebar, then select Browse all playbooks. 🛠️ Step-by-Step 1. Open Home from the left sidebar. 2. Select Browse all playbooks. 3. Find the affected playbook in the list and open it from there instead of using an older bookmark or direct link. 4. Because switching browsers has already been tried, clear the platform’s saved site data in your current browser. In your browser settings, find the site’s cookies and cached files, remove them, then close and reopen the browser. 5. Sign in again and repeat the verified path: Home → Browse all playbooks → the affected playbook. 6. If only one playbook still fails, copy its current URL and note whether other playbooks open successfully. ✅ How to Confirm It Worked The fix worked when the playbook opens from Browse all playbooks, its page content loads normally, and refreshing the page does not return the “page not found” error. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Homepage Meta Description Deployment

🔎 What this issue means If OTTO shows a homepage meta description as approved but it is missing from the live page, the deployment may have failed or another system may be replacing it. This guide covers the most common checks before requesting help. ✅ Check the OTTO recommendation 1. Open OTTO SEO from the left sidebar. 2. Select All Sites and open the affected site. 3. Confirm the homepage meta description is approved and the site is not frozen. 4. If the recommendation is still pending, approve it before checking the live page. 🚀 Confirm the deployment 1. Open OTTO SEO → Overview and review the deployment status. 2. Open OTTO SEO → All Audits and run a scan for the homepage. 3. Use the page source or a browser SEO extension to check whether the live HTML contains one meta description tag. 4. Refresh the page in a private browser window to avoid viewing cached content. ⚙️ Check common causes - Site is frozen: In OTTO SEO → All Sites, confirm the site is not frozen. Unfreeze it if appropriate, then redeploy. - CMS or SEO plugin override: WordPress, Yoast, or another SEO tool may replace OTTO’s value. Check the homepage SEO settings and prevent conflicting tools from overriding the description. - Unsupported punctuation: Curly quotes, unusual dashes, or other special characters can prevent some WordPress deployments from saving. Replace them with standard quotes or hyphens and redeploy. - Duplicate tags: If the live HTML contains more than one meta description, remove the conflicting CMS or plugin value and run another scan. - Cache: Clear the website, hosting, CDN, and browser caches, then verify the live HTML again. 📚 Review installation and site data Open OTTO SEO → Installation Guide to confirm OTTO is installed correctly and active on the site. You can also review OTTO SEO → Crawl Monitoring to confirm that the homepage is being crawled and that the latest page data is available. 🧪 When to request help If the description is approved, the site is active, the homepage is crawled, and the live HTML still does not contain the expected value, collect the site URL, homepage URL, approval time, deployment status, and a screenshot of the scan result. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Troubleshoot Missing Yoast Author Schema

🧭 Overview Yoast author schema can intermittently appear to be missing when MetaSync OTTO or another external sync updates the page’s JSON-LD. In affected cases, the Yoast graph may be replaced with "@graph": false, or imported schema blocks may be dropped. This can prevent the expected Person entity for the author from appearing. ⚠️ Known causes - Yoast conflict handling: A known MetaSync conflict could produce invalid JSON-LD with "@graph": false on OTTO-covered pages. - External schema imports: Schema blocks that were not eligible for import could be silently skipped. - Sync timing: A page may briefly show older or incomplete markup while an external sync is processing. - Caching: WordPress, plugin, CDN, or browser caches can continue serving an earlier version after the schema is corrected. - Author data: Missing or incomplete author details in WordPress can prevent Yoast from creating a Person node. ✅ What Search Atlas has addressed Search Atlas has completed fixes for the MetaSync Yoast conflict handler and OTTO persistence across Yoast, Rank Math, and AIOSEO. These changes address invalid graph output and improve schema synchronization. Schema import eligibility and result reporting are also being improved, so unsupported or skipped blocks can be identified more accurately. 🔎 How to verify the issue 1. Open the affected page in an incognito browser window. 2. View the page source and search for application/ld+json, "@graph", and "@type":"Person". 3. Check whether the page contains "@graph": false, an empty graph, or a Person node without the expected author information. 4. Compare the page source with the rendered DOM. If they differ, a plugin, theme, or client-side script may be changing the markup. 5. Clear WordPress, SEO plugin, server, CDN, and browser caches, then check the page again. 🛠️ Recommended checks - Confirm the author has a valid WordPress user profile and display name. - Check that Yoast is enabled for the post type and that the page is not excluded from search or schema output. - Review whether OTTO or MetaSync is covering the page and whether an external schema sync recently ran. - Do not add a second manual Person graph until the existing Yoast and OTTO output has been reviewed. Duplicate entities can create new validation issues. - After changes, allow the sync to finish and purge all relevant caches before testing again. 📊 Expected result The page source should contain valid JSON-LD with an @graph array. That graph should include the article or webpage entities and, where author data is available, a linked Person entity. A temporary absence immediately after a sync can be cache-related, but repeated output of "@graph": false indicates a conflict or failed schema update. 💬 Get help When contacting the team, include the affected URL, WordPress and SEO plugin versions, whether OTTO or MetaSync covers the page, the time of the latest sync, and a page-source excerpt showing the JSON-LD. If you need further assistance, open 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 Homepage Meta Description

🔍 What this issue means OTTO may show an approved homepage meta description while the live page still displays the old description, no description, or a different value. This can happen when the deployment payload is incomplete, the CMS rejects the content, another SEO plugin overrides OTTO, or cached HTML is being served. ✅ Confirm the recommendation is approved 1. Open OTTO SEO from the left sidebar. 2. Go to All Sites and select the affected site. 3. Open the relevant recommendation or audit result. 4. Confirm the homepage meta description is approved and ready to deploy. If it is not approved, approve it first and allow OTTO time to process the deployment. ⚙️ Check OTTO installation 1. Go to OTTO SEO → Installation Guide. 2. Confirm OTTO is installed on the correct site and CMS environment. 3. Check that the installation is active on the homepage, not only on internal pages. 4. If the site was recently migrated, verify that the current domain and production environment are connected. 🔄 Refresh and scan the site 1. Open OTTO SEO → Overview and select Scan. 2. After the scan finishes, open All Audits and review the homepage result. 3. Use Refresh data from the Home page if the platform still shows old information. 4. Check the live homepage source for one meta description tag and confirm its content matches the approved value. 🧩 Check CMS and SEO plugin conflicts On WordPress sites, Yoast or another SEO plugin may overwrite OTTO’s homepage description. Temporarily review the homepage SEO settings and confirm that another plugin is not generating a second meta description or replacing OTTO’s value. Also check whether the homepage is built from a theme or page-builder template that controls the description. ✍️ Use compatible description text Re-save the description using standard punctuation and plain text. Curly quotation marks, unusual dashes, copied formatting, or invalid characters can cause some WordPress deployments to fail silently. Avoid duplicate meta description tags and remove hidden formatting before approving the recommendation again. 🧹 Clear caching layers Clear the WordPress cache, caching plugin, CDN cache, and server cache if applicable. Then open the homepage in a private browser window and view its source. Browser refreshes alone may not show newly deployed HTML. 📊 Review deployment diagnostics 1. Open OTTO SEO → Crawl Monitoring and review the latest crawl. 2. Check OTTO SEO → Knowledge Base for site-specific implementation details. 3. Look for deployment errors, missing payload values, duplicate tags, or an override from another plugin. 4. Record the site URL, homepage URL, approval time, scan time, and the exact live meta description before requesting help. 💬 Contact support If the homepage still does not show the approved description after these checks, do not repeatedly approve the same recommendation. If you need further assistance, open 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 Stuck Page Explorer Data

🔍 Understanding outdated Page Explorer data Page Explorer data can occasionally remain unchanged while Search Atlas processes a crawl or updates site metrics. This may affect all pages or only specific segments, statuses, and filters. A recent crawl may also show different page totals across screens while processing is still completing. ✅ Check the latest available data 1. Open Site Metrics from the left sidebar. 2. Review the Page Explorer results and note the latest crawl or update date shown. 3. Clear active filters, segments, or status selections to confirm whether the issue affects all pages. 4. Check additional pages using pagination. If a filter was recently applied, return to page 1 before reviewing the results. 🔄 Refresh the Page Explorer view 1. Refresh the browser page. 2. Reopen Site Metrics from the left sidebar. 3. Remove and reapply any filters or segments. 4. Compare the results with the previous update date rather than relying only on the visible page count. 🧭 Check whether processing is still running Data may not update immediately after a crawl, analysis, or profile refresh. Allow the process time to finish, then check Page Explorer again. If other Site Metrics modules, such as backlinks, competitors, topical data, or position changes, are also showing old information, the delay may affect the broader site profile rather than Page Explorer alone. 🛠️ When to request help Contact the team if the data remains unchanged after refreshing and checking again later, especially when: - All pages have been stuck since a previous date. - The update date does not change after a completed analysis. - Filters show inconsistent results or page totals. - You see an error such as “Failed to Fetch Updated Profile.” - Different screens show conflicting crawl or page counts after processing has finished. Before contacting us, record the site, the date the data became outdated, the filters used, and any visible error message. A screenshot can also help us investigate faster. If you need further assistance, open 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 Incorrect Breadcrumb Schema

🔎 Understand the schema error Incorrect schema can cause Google Search Console errors when a page contains invalid, incomplete, or mismatched structured data. For example, a subscription or event page may publish a BreadcrumbList that does not match the page hierarchy, URL, or visible navigation. Search Atlas may label this markup as MetaSync Breadcrumbs Schema. The error can affect a specific URL, such as https://experienceepic.com/theeventreport/, without affecting the rest of the site. 🛠️ Check the affected page 1. Open the affected URL in a browser and confirm that the page loads correctly. 2. Review the page's visible breadcrumb navigation, if available. The breadcrumb names and links should match the structured data. 3. Check whether the page is a subscription, product, event, or other page type. Breadcrumb schema should describe the page path, not the subscription details. 4. Run the URL through Google's Rich Results Test or Search Console's URL inspection tools to confirm the exact error and affected schema item. ⚙️ Correct the breadcrumb schema Use the system that currently adds schema to the page. If the markup is generated by your website, CMS, theme, or another SEO plugin, update or remove the conflicting BreadcrumbList there first. A page should not publish multiple conflicting breadcrumb definitions. If you manage the markup in Search Atlas, open More Features → Schema Creator → Breadcrumb. Review the breadcrumb entries and confirm that: - The schema uses the correct page URL. - Each breadcrumb has the correct name and position. - URLs use HTTPS and point to valid, canonical pages. - The final breadcrumb represents the current page. - There are no duplicate or empty entries. Save the corrected schema and publish or deploy it to the affected page. If the page should not have breadcrumb markup, clear the entries or remove the generated BreadcrumbList from that page. ✅ Validate and request reprocessing 1. Clear your website or CDN cache, if applicable. 2. View the page source and confirm that the old schema is no longer present. 3. Run the URL through the Rich Results Test again. 4. In Google Search Console, open URL inspection, enter the affected URL, and select Request indexing after the correction is live. 5. Allow Google time to recrawl the page. Search Console errors may remain visible until Google processes the updated markup. 🚫 Avoid common schema problems - Do not add breadcrumb schema solely to resolve a Search Console warning if the page has no corresponding navigation. - Do not use HTTP URLs when the site uses HTTPS. - Do not include subscription plans, prices, or payment details in BreadcrumbList markup. - Do not publish several schema versions for the same page from different tools. - Do not assume a successful test immediately removes an existing Search Console report. 💬 Get help with a persistent error If the incorrect schema continues after you update the page, provide the affected URL, the Search Console error text, and a copy of the current page source. If you need further assistance, open 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 and Yoast Schema Conflicts

🔍 What is happening OTTO and Yoast can both attempt to generate structured data on the same WordPress pages. When OTTO takes over schema output, Yoast may return an empty @graph:[] instead of its normal BlogPosting and author entities. This can affect many posts at once, including sites with 700 or more articles. The issue is usually a schema-output conflict, not missing author data in WordPress or Yoast. ✅ Confirm the conflict 1. Open an affected blog post in an incognito browser window. 2. View the page source and search for application/ld+json. 3. Check whether Yoast outputs an empty @graph while OTTO-related schema markup is present or controls the page output. 4. Test several posts, including posts with different authors and publication dates, to confirm the issue is site-wide. 5. Use Google’s Rich Results Test or Schema Markup Validator to compare an affected page with a page from before OTTO was enabled. 🛠️ Restore Yoast schema output 1. In WordPress, open the OTTO plugin settings or installation configuration. 2. Find the setting that enables OTTO schema, structured data, schema takeover, or replacement of existing schema. 3. Disable OTTO’s schema output or configure OTTO to preserve the existing Yoast schema. Do not disable OTTO’s other SEO changes unless required. 4. Save the configuration and clear WordPress, hosting, CDN, and browser caches. 5. Regenerate or recrawl the affected URLs if your setup provides a schema refresh or site scan option. Setting names can differ by OTTO plugin version and WordPress configuration. If no schema control is visible, temporarily deactivate the OTTO plugin on a staging site and retest. If Yoast schema returns, the conflict is confirmed. 👤 Verify BlogPosting and author data 1. Open a recently updated post and inspect its JSON-LD. 2. Confirm the @graph contains a BlogPosting entity. 3. Confirm BlogPosting includes an author property that references or contains a Person entity. 4. Check that the Person entity includes a valid name and, where applicable, a profile URL. 5. Test posts by multiple authors to ensure the fix applies across the site. Do not manually add duplicate BlogPosting or Person schema to every post. Duplicate entities can create new validation issues and may conflict with Yoast after future updates. 🧪 Validate at scale For a site with 700 or more posts, first validate a representative sample: old and new posts, posts by different authors, and posts using different templates. Then crawl the full blog section to identify pages that still return an empty graph or lack BlogPosting and author data. Search engines may need time to recrawl the corrected pages. A valid test result confirms the markup is present, but it does not guarantee immediate changes in search results. 🚨 If the issue continues Check for additional schema plugins, theme-generated JSON-LD, caching layers, and custom code that filters Yoast schema. Re-enable only one schema provider at a time on staging to identify competing output. When requesting help, include an affected URL, a page-source excerpt showing the empty graph, the OTTO plugin version, the Yoast version, and the result after disabling OTTO schema output. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting Delayed Page Schema

This article explains why credits may be deducted even when page-level schema does not appear, and how to resolve and verify the issue. 🛠️ Step-by-Step 1. Open the page-level schema generation area for the affected page and review the generation result or status. 2. Check whether the page contains clear, complete content that matches a supported schema type. AI may consistently misclassify ambiguous or thin pages. 3. Improve the page content and make its primary purpose clear before trying again. Recrawling the same unchanged page may produce the same classification. 4. Run schema generation again after the page changes are saved or published. Avoid repeated retries on an unchanged page. 5. Review the generated output and apply or save it if the product presents that option. ✅ How to Confirm It Worked Confirm that a schema result is visible for the affected page and that it matches the page's actual content type. A credit deduction confirms processing started, not that schema was successfully generated. If no schema appears after correcting the page and retrying once, contact support instead of repeatedly recrawling. If you need further assistance, open 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 Incorrect Vehicle Text After OTTO Heading Optimization

🔍 Overview If vehicle names on your inventory pages are displaying incorrectly after page load — for example, a Jeep Wrangler listing showing as Jeep Compass — this is most likely caused by OTTO's heading optimization script overwriting text that is dynamically injected by your website's JavaScript, such as a Google Tag Manager (GTM) container or a third-party inventory feed script. This article explains why this happens, how to identify the conflict, and what steps to take to resolve it. ⚙️ Why This Happens OTTO's heading optimization works by rewriting H1 and H2 tag content based on the SEO recommendations it generates at the time of optimization. However, some automotive dealership websites use dynamic scripts — often loaded through GTM or a vehicle inventory platform — to populate page headings with the correct vehicle name after the initial HTML has loaded. When both systems try to control the same heading element, a conflict occurs: - OTTO writes the optimized heading text during or after page render. - The dynamic inventory script also runs post-render and attempts to inject the correct vehicle name. - Depending on execution order, one script overwrites the other — resulting in the wrong vehicle name being displayed. This issue has been observed with GTM containers that trigger vehicle-data scripts on DOM-ready or window-load events, and is not limited to any single inventory platform. 🔎 How to Identify the Conflict Before making any changes, confirm that OTTO's script is the source of the overwrite by following these steps: 1. Open the affected inventory page in your browser (for example, your /new-jeep page). 2. Right-click the incorrectly displayed vehicle name heading and select Inspect to open browser developer tools. 3. In the Elements panel, check whether the displayed text matches what OTTO has written or what your inventory script expects. 4. Switch to the Network or Console tab and look for requests or script executions related to your GTM container ID (for example, GTM-TCCS243) and any inventory or vehicle-data scripts it fires. 5. Use the Event Listener Breakpoints in the Sources panel to watch for DOM mutations on the heading element — this will show you which script modifies the text last. ✅ How to Resolve the Issue Once you have confirmed the conflict, use one or more of the following approaches to fix it: - Exclude the affected URL pattern from OTTO heading optimization. In Search Atlas, navigate to OTTO SEO using the left sidebar. Review the heading optimization settings for the affected page and disable or exclude heading rewrites for dynamic inventory pages where vehicle text is controlled by a third-party script. - Check for a heading length suffix issue. A known issue caused OTTO to append text such as "Length n(number)" to heading suggestions. If you see this pattern in the deployed heading, the optimization may need to be re-applied after this fix was resolved on the platform side. - Coordinate script execution order in GTM. If your development team manages the GTM container, ask them to ensure the inventory vehicle-data script fires after OTTO's dynamic_optimization.js has completed. This can be done by adjusting tag firing priority or using a custom trigger that waits for OTTO's script to finish. - Re-deploy the OTTO optimization after resolving the conflict. Once the script conflict has been addressed, return to OTTO SEO in the left sidebar and re-apply the heading optimization for the affected pages so that the correct, intended text is written cleanly without interference. - Verify the fix after deployment. Reload the affected inventory page in an incognito window and confirm the correct vehicle name appears in the heading immediately after page load and after any dynamic scripts have run. 🚗 Special Considerations for Automotive Inventory Pages Automotive dealership websites frequently use dynamic vehicle data because inventory changes daily. Keep these best practices in mind to prevent future conflicts: - Avoid applying OTTO heading optimizations to URL patterns that are fully controlled by your inventory management system (IMS) or dealer platform. - Focus OTTO heading optimization on static or semi-static pages such as brand landing pages, service pages, and location pages. - If your inventory platform injects H1 text dynamically, treat those headings as outside OTTO's scope unless your development team can guarantee a stable execution order. - After any GTM container update, re-test affected inventory pages to ensure no new script conflicts have been introduced. 💬 Still Seeing Incorrect Vehicle Text? If you have followed the steps above and the incorrect vehicle text is still appearing, our team can investigate your specific GTM container configuration and OTTO deployment in more detail. If you need further assistance, open 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 Template Picker Hidden Behind Popup

🔍 Overview Some customers encounter an issue where the template picker is hidden behind a popup, making it unavailable or unclickable. ⚠️ What You Might Experience - The template picker is hidden behind a popup. - You cannot view or select a template. - Clicks on the picker do not respond as expected. 🛠️ What to Do This is a bug involving the template picker and a popup overlay. If you experience this issue, contact support for assistance. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Meta Title Deployments

🔍 Why the meta title did not change OTTO cannot deploy a meta title when the project domain is unreachable. Make sure the domain loads successfully before trying the deployment again. 🌐 Check whether your domain is reachable 1. Open the project domain in a browser. 2. Confirm that the website loads successfully instead of showing a DNS error, timeout, or other connection error. 3. If the domain is unreachable, resolve the domain or hosting issue so the website can be accessed publicly. 4. After the domain becomes reachable, try the meta title deployment again. ⚠️ If the domain remains unreachable OTTO cannot complete the deployment while the project domain cannot be reached. Restore access to the domain first, then retry the deployment. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Brand Vault Contact Number Auto-Reverting Bug

🔍 Overview Some customers have reported that a contact number in Brand Vault automatically reverts after being updated. This article explains what to do if the issue occurs. ⚙️ What to Do If your Brand Vault contact number reverts after you update it, report the issue to the support team for investigation. 📋 Contact Support When reporting the issue, explain that the Brand Vault contact number automatically reverted after being updated. The team can investigate the reported bug and advise on next steps. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot Missing OTTO Deployments

🔍 Why OTTO changes may not appear OTTO updates may not appear immediately in the WordPress editor or on the live page. OTTO can apply changes through the WordPress integration, Google Tag Manager, or site code, so some updates are rendered dynamically rather than saved as visible WordPress fields. For example, schema markup, meta titles, and meta descriptions may be active on the live page without appearing in the standard WordPress post editor. Conversely, a deployment can show as successful while caching, integration settings, or theme behavior prevents the change from rendering. ✅ Confirm the deployment status 1. In Search Atlas, open OTTO SEO from the left sidebar. 2. Open the relevant project or site audit area and locate the affected URL. 3. Check whether the recommendation or fix is marked Deployed, Fixed, or still pending. 4. Confirm that the URL is canonical, publicly accessible, and included in the latest crawl. 🔄 Run a fresh sync and recrawl If the deployment is complete but the page is unchanged, refresh the connection between Search Atlas and WordPress. 1. Open OTTO SEO → Site Audit → Installation Guide and confirm the WordPress integration is installed and active. 2. Verify that the connected WordPress site is the same site and environment as the affected URL. 3. Use the available CMS sync or redeploy action for the affected page. 4. Start a new crawl from OTTO SEO → Site Audit after the sync finishes. 🌐 Check the live page Do not rely only on the WordPress backend. Open the published URL in a private browser window and inspect the page source or rendered HTML. - For meta titles and descriptions, check the page source for the title element and meta description. - For schema, use a structured-data testing tool or inspect the JSON-LD in the rendered page source. - For headings and image alt text, view the live page and confirm the rendered content. If the change appears on the live page but not in WordPress, this is expected for dynamically applied OTTO updates. WordPress fields may remain unchanged even though search engines can read the deployed output. 🧹 Clear caching and integration conflicts Cached pages, CDN layers, optimization plugins, and duplicate SEO tools can display older content or overwrite OTTO changes. - Clear the WordPress cache, CDN cache, and any server-side cache. - Temporarily check whether an optimization or SEO plugin is generating competing titles, descriptions, schema, headings, or alt text. - If using Google Tag Manager, confirm the container is published and loading on the affected page. - Check that consent settings or security tools are not blocking the OTTO script. - Test the page without a browser cache by using a private window or a hard refresh. 📋 When to review deployment details Review the deployment details when several pages are affected, changes repeatedly revert, or the live page differs from the deployment preview. Record the affected URL, deployment status, integration type, and the exact change that is missing. This information helps identify whether the issue is related to WordPress, GTM, caching, or the page template. 💬 Get help from our team If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix Missing Target Article Validation

🔍 What the error means The “Missing Target Anchor Text” error means Search Atlas could not confirm the required anchor text and destination link on the published target article during validation. The link may appear correct in your editor or browser while the automated check receives different content, an older page version, or a modified HTML structure. ✅ Check the live article 1. Open the target URL in a private or incognito browser window. 2. Confirm that the page loads successfully without requiring a login, special access, or a temporary preview link. 3. Search the rendered page for the exact required anchor text, including spelling, spacing, punctuation, and capitalization. 4. Confirm that the anchor text is linked directly to the required target URL. 5. Check that the link is a normal DoFollow link and does not include a nofollow, sponsored, or ugc attribute. 6. Verify that the link is in the article content, not only in navigation, a footer, a sidebar, a related-content block, or a hidden element. 🛠️ Check the link destination Compare the destination URL exactly with the required URL. Differences such as http versus https, www versus non-www, trailing slashes, URL parameters, fragments, redirects, or a canonical destination can prevent validation. If the required URL redirects, update the article so the link points directly to the final destination whenever possible. 🔄 Republish and validate again Validation can use the publicly available version of a page rather than an unsaved editor version. After making changes, publish the article and wait for the updated page to load consistently. Then return to the relevant article in Content and run the validation again. If your site uses caching, a content delivery network, or a publishing workflow, clear or complete those processes first. 🧩 Check for content and keyword mismatches Some article-generation or editing workflows may create content without the expected target keyword or may associate a keyword with the wrong article. Confirm that the article is assigned to the intended target URL and keyword, and that the required anchor text was not changed during editing. If the article was generated from a planner or AI workflow, compare its assigned target details with the current validation requirements. 📄 Check the page source when needed If the link is visible but the error remains, inspect the page source or browser developer tools and confirm that the anchor exists in the HTML delivered to visitors. JavaScript-rendered links, links inside blocked content, duplicate anchor text, or a page that serves different content to automated requests may not be detected reliably. 🚨 When to request an investigation Request a review if all of the following are true: - The live URL is publicly accessible. - The exact anchor text appears in the published article. - The link points directly to the required destination. - The link is DoFollow and appears in the main article content. - You republished the page and ran validation again. When contacting the team, include the article URL, target URL, exact anchor text, a screenshot of the live link, and the approximate time of your latest validation attempt. This helps the team compare the live page with the validation result and identify caching, rendering, assignment, or dashboard issues. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ Fix Page Explorer Stuck in Processing Status

Overview The Page Explorer tool inside OTTO SEO's Site Audit occasionally shows a "Page is being processed" banner for an extended period, and the Recrawl Page button becomes disabled. This article explains what to do if you encounter this stuck state. Why Does This Happen? When a recrawl is triggered, Page Explorer runs background processing tasks for the page. In some cases, a known issue can cause the processing banner to persist even after the core work is complete, leaving the page flagged as still processing in the UI. What You Should Try First 1. Wait a little while. Short processing delays are normal. Give the system some time to finish background tasks before taking further action. 2. Hard-refresh your browser. Force a full page reload to clear any stale UI state that may be displaying an outdated processing status. 3. Check if your data is already updated. Scroll through the Page Explorer report for the affected URL. If metrics, issues, and recommendations are visible and up to date, the crawl likely completed successfully and only the UI state is stuck. 4. Navigate away and return. Go to a different section of the platform and then navigate back to Page Explorer. This can sometimes clear a stale processing state displayed in the UI. If the Banner Remains Stuck If the processing banner has been showing for an extended period and the Recrawl Page button remains disabled after trying the steps above, the processing job likely needs to be manually cleared on the backend. To escalate, please have the following ready: - The exact URL of the page showing the stuck processing status - Approximately how long the processing status has been stuck - The name of the OTTO SEO project or site affected If you need further assistance, open 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 Choose-Plan Page Stuck Loading

🔍 Overview Some customers encounter a spinning loader, blank plan cards, or errors such as 'Failed to get updated profile data' or 'Network error' when reaching the choose-plan page after registration. This can happen across different browsers and devices. This article explains why this occurs and walks you through every step to resolve it. ⚠️ Common Symptoms - The choose-plan page displays an infinite spinning wheel with no plan options loading. - Error messages appear: 'Failed to get updated profile data' or 'Network error'. - The Start Free Trial button stays on 'Processing…' for 20–40 seconds before anything happens — or nothing happens at all. - The issue persists across multiple browsers, incognito/private mode, and mobile devices. 🛠️ Step-by-Step Troubleshooting 1. Wait briefly and refresh. If you just registered, the system may still be provisioning your account. Wait 60 seconds, then press F5 (or pull-to-refresh on mobile) to reload the page. 2. Clear your browser cache and cookies. Cached data from a previous session can interfere with profile loading. Clear your cache, close all tabs, and reopen the choose-plan page. 3. Try a different browser. Open the page in a different browser (for example, Chrome, Firefox, or Edge) to rule out a browser-specific conflict. 4. Disable browser extensions. Ad blockers, VPNs, and privacy extensions can block API calls that load plan data. Disable all extensions, then reload the page. 5. Check your internet connection. A weak or intermittent connection can trigger network errors. Switch networks (for example, from Wi-Fi to mobile data) and try again. 6. Use a direct login link. Navigate directly to app.searchatlas.com, log in with your registered credentials, and allow the platform to redirect you to the choose-plan page automatically. 7. Try again after 10–15 minutes. Temporary backend delays can cause profile data to be unavailable. If none of the above steps work immediately, wait a short time and try again. 💡 About the 'Processing…' Delay on Start Free Trial When you click Start Free Trial, the button may show 'Processing…' for up to 40 seconds before the checkout window opens. This is a known delay that occurs while the system prepares your trial session. Do not click the button multiple times — doing so can cause duplicate requests. Wait for the checkout to open on its own. 📋 What Our Team Can Do for You If the choose-plan page still does not load after completing all the steps above, a member of our team can manually activate your free trial so you can access the platform right away. No further action is required on your end — simply reach out and we will handle it. 🆘 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 Press Release Validation Error in OTTO

What Is This Error? When ordering a press release inside an OTTO project, you may encounter a validation error related to the press release content type. This is a known issue that our team will need to investigate directly on your account. What to Have Ready Before Contacting Support - The name of the affected OTTO project - The exact validation error message you are seeing - The timestamp or date and time when the error occurred - Any screenshots of the error, if available What to Expect Because this error occurs at the account and project level, our support team will need to look into your specific OTTO project configuration to identify the cause and apply a fix. There are no self-serve steps available to resolve this error on your own at this time. If you need further assistance, open 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 SSL Errors and Subdomain Traffic Serving Issues

Overview OTTO relies on a correctly installed pixel to serve optimizations across your connected domains. SSL certificate errors can prevent the pixel from loading securely, which blocks OTTO from serving traffic on affected domains. This article walks you through diagnosing and resolving SSL-related pixel issues on your site. Why This Happens SSL errors occur when the OTTO pixel script is blocked by your server or CDN because it cannot establish a trusted secure connection. Common causes include: - The pixel script src uses http:// instead of https://, causing a mixed-content error on HTTPS sites - An expired or missing SSL certificate on the domain or subdomain where OTTO is deployed - CDN or firewall rules that strip, rewrite, or block third-party scripts - A Content Security Policy (CSP) header that does not allow the OTTO pixel domain Steps to Diagnose and Fix the Issue 1. Check the pixel URL protocol: Confirm that the OTTO pixel snippet's src attribute begins with https://. An http:// reference on an HTTPS page will trigger a mixed-content error and silently prevent the pixel from loading. 2. Confirm your SSL certificate is valid: Use a tool such as SSL Labs or your browser's padlock icon to verify your domain's certificate is active, not expired, and covers all subdomains where OTTO should serve. A wildcard certificate (*.yourdomain.com) is recommended when OTTO is deployed across multiple subdomains. 3. Review subdomain DNS and CDN settings: Each subdomain must resolve correctly. Check for CDN rules or firewall policies that may strip or rewrite the OTTO pixel script. Common culprits include Cloudflare Rocket Loader, HTML minification rules that break inline scripts, and WAF rules blocking third-party script tags. 4. Update your Content Security Policy (CSP): If your site uses a CSP header, ensure the OTTO pixel domain is included in your script-src and connect-src directives. If you are unsure which domain to whitelist, contact our support team using the instructions at the bottom of this article. 5. Confirm the pixel is present on all affected pages: Verify the OTTO pixel snippet is included in the <head> section of every page you want OTTO to serve, including pages on subdomains. 6. Test after each change: After making any of the changes above, load the affected page in your browser and open the developer console (F12) to confirm no SSL or mixed-content errors are reported for the OTTO pixel script. What to Have Ready When Contacting Support If you have worked through the steps above and the pixel is still not loading, our team can investigate further. Please have the following ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Deployment and Playbook Errors on WordPress

🔍 Overview If your OTTO SEO suggestions are not deploying to your WordPress site, or if the Atlas playbook returns a 403 or 400 error during preview, this article explains what may be happening and what to have ready when you contact our team for assistance. ⚙️ What May Be Causing This OTTO deployment and playbook preview errors on WordPress trial sites can stem from a number of underlying causes, including plugin connectivity issues, caching conflicts, or an incomplete site authorisation. Because these errors often require backend investigation to diagnose correctly, our support team will need to look into the specifics of your setup directly. 📋 What to Have Ready When You Escalate To help our team resolve your issue as quickly as possible, please gather the following before reaching out: - The exact error message you are seeing (e.g., 403 Forbidden, 400 Bad Request, or any other on-screen text). - The name of your WordPress project or trial site as it appears in Search Atlas. - The timestamp of when the error first occurred or the most recent occurrence. - A brief description of the action you were taking when the error appeared (e.g., running a playbook preview, deploying suggestions, scanning the site). - Any caching or third-party plugins you have active on the WordPress site (e.g., WP Rocket, Google Tag Manager). - Screenshots of the error if available. Having this information ready will allow our team to investigate your specific configuration without delays. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Pixel Verification on Lovable Sites

Overview If you have added the OTTO pixel code to your Lovable site and Search Atlas still shows the pixel as unverified, this article explains what is known about this issue and how to get it resolved. This topic also covers related OTTO SEO questions about title generation and content grading on Lovable sites. What Is Known About This Issue OTTO pixel verification failures on Lovable CMS, as well as questions about title generation and content grading in this context, require investigation by our support team. Because Lovable handles script rendering differently from traditional HTML sites, verification issues on this platform may need a backend review to identify the root cause specific to your project. Our team has handled cases involving this combination of issues — pixel verification, title generation, and content grading questions — on Lovable sites. The exact cause can vary per project, and a support agent will need to review your specific setup to confirm what is happening and take any necessary action. What to Have Ready When You Escalate To help our team resolve your issue as quickly as possible, please have the following information ready before reaching out: - Your Search Atlas project name connected to the Lovable site. - Your OTTO pixel ID as shown in your Search Atlas account. - The live URL of your Lovable site where the pixel should be active. - A description of the specific issue — for example, whether it is pixel verification, title generation, content grading, or a combination. - Any error messages or status indicators you see in Search Atlas related to OTTO SEO on this project. - Screenshots of the relevant sections in Search Atlas and in your Lovable project settings, if available. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Pixel Not Engaging on WordPress

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

🔍 Fix OTTO Pixel Detection Failures via Cloudflare

Overview When your site runs behind Cloudflare, certain security settings or configurations can block or delay Search Atlas from verifying your OTTO pixel installation. This guide covers general troubleshooting steps for Cloudflare-proxied sites and explains what information to have ready if you need to escalate to our support team. Step 1: Confirm Your Pixel Installation Method Before changing any Cloudflare settings, confirm that the OTTO pixel snippet has been correctly installed on your site using the method recommended for Cloudflare-proxied domains. If you are unsure which installation path applies to your setup, or if you followed a generic installation guide rather than one specific to Cloudflare, reinstalling the pixel using the appropriate method for your site configuration is a good first step. Step 2: Review Cloudflare Security and Bot Protection Settings Cloudflare's security features — including bot protection settings such as Bot Fight Mode and Super Bot Fight Mode — can sometimes treat automated verification requests as bot traffic and block them. If you have aggressive bot protection or Web Application Firewall (WAF) rules enabled, review those settings in your Cloudflare dashboard and consider whether any rules might be preventing Search Atlas's verification crawler from accessing your site. Step 3: Account for DNS and Cache Propagation If you recently added or changed the pixel snippet, allow some time for DNS and cache changes to propagate before re-triggering pixel verification in Search Atlas. You should also purge your Cloudflare cache after making changes to ensure the updated page response is being served correctly. Step 4: Check for Cloudflare Worker Conflicts Cloudflare Workers that modify HTML responses — such as workers that inject scripts, rewrite headers, or alter <head> content — can interfere with pixel delivery. Review any active Workers on your domain and consider whether any might be stripping or modifying the OTTO pixel before it is served. When to Escalate If you have worked through the general checks above and pixel detection is still failing, our support team can investigate further. Please have the following information ready before reaching out: - Your site's domain name and the OTTO project name in Search Atlas - The installation method you used for the OTTO pixel - Which Cloudflare features are currently active on your domain (e.g., Bot Fight Mode, Workers, WAF rules) - Any error messages or status indicators shown in your OTTO settings - The approximate time and date you last attempted pixel verification If you need further assistance, open 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 GHL

🔍 Overview If you have installed the OTTO pixel on your GoHighLevel (GHL) website but the Search Atlas dashboard still shows it as not installed correctly, you are not alone. This is a known detection issue specific to how GHL renders pages, and it does not necessarily mean your pixel is missing. This article walks you through the steps to confirm your installation and resolve the detection flag so OTTO can deploy fixes on your site. ⚙️ Why This Happens on GHL GoHighLevel uses a custom page-rendering engine that can delay or alter how external scripts are loaded. OTTO's pixel verification system scans the page for the script at a specific moment during load. On GHL sites, the pixel may load slightly out of sync with that scan window, causing a false not installed status even when the code is present and firing correctly. ✅ Step 1 — Confirm the Pixel Is Present on Your Site 1. Open your GHL website in a browser and navigate to any published page. 2. Right-click anywhere on the page and select Inspect (or press F12) to open Developer Tools. 3. Go to the Elements tab and use Ctrl+F (Windows) or Cmd+F (Mac) to search for ottoseo or your unique pixel ID. 4. If the script tag appears in the HTML, your pixel is installed. Proceed to Step 2. 5. If the script tag does not appear, re-install the pixel by following the instructions in the OTTO onboarding flow under Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 🔧 Step 2 — Re-Install the Pixel in GHL Correctly To ensure the pixel loads as early as possible and is not blocked by GHL's rendering engine, follow these placement guidelines: - In your GHL account, go to Sites → Your Website → Settings → Header Tracking Code. - Paste the OTTO pixel script inside the <head> section, not the footer. Head placement gives the script the best chance of firing before OTTO's verification scan runs. - Make sure the script is not wrapped in any conditional logic or tag manager delay rules that could postpone its execution. - Save your changes and publish the site. 🔄 Step 3 — Re-Trigger Pixel Verification in Search Atlas 1. Log in to Search Atlas and navigate to Left sidebar → OTTO SEO → All Sites (SEO Automation). 2. Locate your connected GHL website in the OTTO dashboard. 3. Click Verify Pixel or the re-check option next to the installation status indicator. 4. Wait up to 60 seconds for the scan to complete. 5. If the status updates to Installed, you are ready to deploy OTTO fixes. 💡 Step 4 — If the Status Still Shows Not Installed Some GHL configurations cache pages aggressively. Try the following before escalating: - Clear the GHL page cache from your site settings and republish all pages. - Test on a page that has been freshly published within the last 10 minutes to rule out stale cache. - Temporarily disable any third-party scripts or apps in GHL that might be blocking external JavaScript from loading. - Try verifying from a different browser or in an incognito window to rule out local caching on your end. 🚫 Common Mistakes to Avoid - Placing the pixel in the footer: Footer scripts load last and are most likely to be missed by the verification scan. - Using a tag manager with delays: Tag managers that fire scripts after a timer or scroll event will cause verification failures. - Installing the pixel on only one page: The OTTO pixel should be installed globally across all pages of your GHL site, not on a single landing page. - Duplicate pixel snippets: More than one instance of the pixel on the same page can cause conflicts. Ensure it appears only once in your header code. 📊 Confirming OTTO Is Active After Verification Once the pixel is verified, return to Left sidebar → OTTO SEO → All Sites (SEO Automation) and check that your site's OTTO status shows as Active. You should now be able to review and deploy recommended SEO fixes without any blocking warnings. If fixes still appear locked, try refreshing the page or logging out and back in to force the dashboard to update your site's verification state. 🆘 Still Need Help? If you have followed every step above and the pixel still shows as not installed, our team can review your specific GHL 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.

⚡ OTTO Plugin Installation – Projects Not Showing in Dashboard

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

🛠️ Fix 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 'No Service ID Returned' Connection Error

🔍 What Is This Error? When you add a global project in OTTO SEO and attempt to connect it to a website, you may see the error: "No service ID was returned." This means OTTO was unable to complete the connection because a required service identifier was not generated during the setup process. This is typically a configuration or timing issue — not a problem with your website. ⚙️ Common Causes - The project was created before the domain was fully verified or indexed in Search Atlas. - A required integration step was skipped during the global project setup. - The project was added too quickly after domain entry, before the system finished registering the service. - A temporary platform sync issue interrupted the service ID generation. 🚀 Step-by-Step Resolution 1. Navigate to SEO Automation. In the left sidebar, click OTTO SEO, then open SEO Automation. The URL will be /seo-automation-v3. 2. Locate your project. Find the global project you added for the affected site (for example, your Select Insurance project) in the OTTO project list. 3. Disconnect the project. Click the options menu next to the project and select Disconnect or Remove Connection. Confirm when prompted. 4. Delete the project entirely. If the disconnect option alone does not resolve the issue, delete the project from your OTTO workspace so you can start fresh. 5. Wait 2–3 minutes. Allow the platform time to clear the previous session data and service registration before recreating the project. 6. Re-add the global project. Click Create Project (on the Home page), enter your domain details carefully, and complete every field before submitting. Do not navigate away during this step. 7. Attempt the connection again. Once the project appears in your list, click Connect to OTTO and wait for the confirmation message. The service ID should now be returned successfully. 💡 Tips to Prevent This Error - Always verify that your domain is active and accessible before adding it as a global project. - Complete all setup fields in a single session — do not leave the form partially filled and return later. - If you manage multiple projects, add them one at a time and confirm each connection before moving to the next. - Refresh the OTTO dashboard before starting a new project connection to ensure you are working with the latest session data. 📊 Still Seeing the Error After Reconnecting? In rare cases, the service ID generation may fail due to a backend sync issue that requires manual intervention. If you have followed all the steps above and the error persists, it is best to reach out so a teammate can investigate your specific project configuration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix Search Atlas Script Not Working on GoHighLevel

🔍 Overview If you have added the Search Atlas script to your GoHighLevel (GHL) website but OTTO is not detecting it, the most common cause is a Cloudflare security rule that blocks the Search Atlas crawler before it can verify the script. This article walks you through diagnosing and fixing the issue so OTTO can successfully connect to your site. ⚠️ Common Symptoms - You added the Search Atlas script to your GHL site but OTTO still shows the site as undetected or not connected. - The Installation Guide shows the script as missing even though you can see it in your GHL settings. - You notice two script tags on your site — this is normal GHL behavior and is not a duplicate error. 🧩 Why This Happens Cloudflare's bot protection can treat the Search Atlas crawler as an unwanted bot and block its requests. When the crawler is blocked, it cannot reach your page to confirm the script is present, so OTTO never registers a successful connection. The fix is to whitelist the Search Atlas crawler in your Cloudflare settings so it can access your site freely. ✅ How to Fix It 1. Log in to your Cloudflare dashboard for the domain connected to your GoHighLevel site. 2. Navigate to your security or bot management settings. The exact location depends on your Cloudflare plan, but look for sections related to bot protection, firewall rules, or IP access rules. 3. Add a whitelist rule that allows the Search Atlas crawler. Create an allow rule for the Search Atlas crawler user agent or IP range. If you are unsure of the exact crawler details, contact our support team using the instructions at the bottom of this article and a teammate will provide them. 4. Save your changes and allow a few minutes for the rule to propagate. 5. Trigger a new scan in Search Atlas. Return to your Search Atlas account and run a fresh scan on your site so OTTO can attempt to detect the script again. 6. Check the installation status. Confirm in your Search Atlas account whether the script is now detected and the site shows as connected. 📋 Additional Notes - Two script tags on your GHL site is expected. GoHighLevel sometimes renders the script tag more than once. This is standard GHL platform behavior and does not indicate a problem with your installation. - CMS detection may show as "Custom CMS" instead of "GoHighLevel." Our engineering team is actively working on improving GoHighLevel fingerprinting so the CMS is recognised correctly. This does not affect OTTO's ability to optimise your site once the script is connected. - If your site uses a third-party proxy or additional anti-bot service beyond Cloudflare, the same principle applies — the Search Atlas crawler must be permitted through any layer that sits in f

🔧 Fix 'No WP Website Found' Sync Error

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

🔌 Otto SEO Plugin Impersonation Warning Explained

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

🛠️ Fix Deleted Projects and GSC Connection Issues

Overview This article covers two separate issues you may encounter in Search Atlas: a deleted project that continues to appear in the Active Projects list, and Google Search Console (GSC) sites that do not appear in the connection list despite verified ownership. If you are experiencing either of these problems, our support team can investigate and resolve them on your behalf. Issue 1: Deleted Project Still Appears in Active Projects If you have deleted a project but it continues to show in your Active Projects list, this is a known issue that our support team can look into directly. Before reaching out, try the following basic steps: 1. Perform a hard refresh of the page or sign out and back in to rule out a temporary display issue. 2. Check whether the project can be opened. If it loads normally, try deleting it again and wait for any on-screen confirmation before navigating away. 3. If the project still appears after signing back in, contact support and provide the project name so our team can investigate. Issue 2: GSC Sites Not Appearing in the Connection List If your Google Search Console properties do not appear when you try to connect GSC to Search Atlas, this may be related to your GSC integration setup. Before contacting support, please check the following: 1. Confirm you are signing in with the same Google account that has access to the GSC properties you expect to see. 2. Verify that your GSC properties are active and accessible when you log in directly to Google Search Console. 3. If properties are confirmed active but still do not appear in Search Atlas, contact support and provide the affected GSC property URLs and the Google account email used during connection. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix 'Pixel Not Installed Correctly' WordPress Plugin Error

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

🛠️ OTTO Pixel Not Detected on Dealer.com Sites

🔍 Overview If your site runs on the Dealer.com CMS and the OTTO Pixel shows as not installed inside Search Atlas, this is a known platform-specific detection issue. It does not necessarily mean the pixel is missing from your site — it means Search Atlas cannot verify it through its standard detection method due to how Dealer.com renders and serves its pages. ⚙️ Why This Happens Dealer.com is an automotive-focused CMS that uses a heavily managed hosting and rendering environment. This setup can prevent external tools from reading page source code in the standard way. As a result, even when the OTTO Pixel script is correctly placed on your site, Search Atlas may still report its status as not detected. Common reasons the pixel goes undetected on Dealer.com sites include: - Deferred or async script loading: Dealer.com often loads third-party scripts after the initial page render, which can cause detection checks to miss the pixel entirely. - Restricted page source access: Dealer.com's infrastructure may block or limit external crawlers from reading the full HTML output of a page. - Tag Manager conflicts: If the pixel is deployed via a Tag Manager container rather than hardcoded into the page template, it may not appear during a standard source scan. - CDN or proxy caching: Dealer.com uses content delivery networks that may serve cached versions of pages without the pixel present in every response. ✅ How to Confirm the Pixel Is Actually Installed Before escalating, verify the pixel is live on your site using these steps: 1. Open your site in a browser (e.g., www.polestarfortlauderdale.com). 2. Right-click anywhere on the page and select Inspect (or press F12) to open browser DevTools. 3. Go to the Sources or Network tab and search for otto or your unique pixel ID. 4. Alternatively, use the Elements tab and press Ctrl+F (or Cmd+F on Mac) to search for the pixel script tag. 5. If the script appears, the pixel is installed correctly — the issue is limited to how Search Atlas detects it remotely. 🚀 Steps to Request Manual Pixel Verification Because automated detection may not work reliably on Dealer.com sites, Search Atlas supports a manual verification process. Follow these steps: 1. Log in to Search Atlas and navigate to OTTO SEO in the left sidebar, then open SEO Automation inside it (or go to /seo-automation-v3). 2. Locate the OTTO Pixel status for your site and take a screenshot showing the not detected status alongside your domain name. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate. 4. Share your domain, the screenshot, and confirmation that your site uses Dealer.com as the CMS. 5. Our team will manually confirm pixel activity on the backend and update your account status accordingly. 💡 Best Practices for Dealer.com Pixel Installation To give the OTTO Pixel the best chance of being detected automatically in future scans, work with your Dealer.com account representative to ensure: - The pixel script is placed in the <head> section of every page template, not just the homepage. - The script loads synchronously where possible, rather than being deferred or set to async-only. - If using Google Tag Manager, confirm the GTM container itself fires on all pages and that the OTTO Pixel tag has no restrictive trigger conditions. - Any cookie consent or privacy tools are configured to allow the pixel to load for users who accept analytics cookies. 🙋 Still Seeing Issues? If you have confirmed the pixel is on the page but Search Atlas still reports it as undetected after following the steps above, our support team can investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes The only confirmed fix is to delete the existing pixel and reinstall it from scratch. Delete the existing OTTO Pixel entry (do not re-save/update it), generate a new pixel, remove the old script from Dealer.com, paste the new script, and allow about 15 minutes for status to update on a new project (automatic checks run every 15 minutes for projects under 2 hours old).

🔌 Fix WordPress Plugin Authentication and Sync Errors

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

🛠️ Fix a Stuck Payment Screen and Platform Confusion

Overview If you're seeing a "Please wait" screen that never moves, or if the platform feels unfamiliar after signing up, you're not alone. These two issues often happen together — a payment page stalls during initial setup, leaving you unsure where to go next. This article walks you through what to do if you get stuck at the payment screen and how to reach support if it doesn't resolve. What to Do If the Payment Screen Is Stuck Before taking any action, wait at least 60 seconds — the screen sometimes takes a moment to finish processing. Do not refresh the page immediately, as this can interrupt the checkout flow. 1. Check your email. If you received a confirmation or welcome email from Search Atlas, your payment went through successfully and your account is ready. Go to searchatlas.com and log in directly rather than waiting on the stuck screen. 2. Hard-refresh the page. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to reload without using cached data. 3. Try a private or incognito window. This bypasses stored cache and many browser extensions in a single step. 4. Switch browsers. If the issue persists, try accessing the platform in a different browser such as Google Chrome or Mozilla Firefox. If you complete these steps and still cannot access your account, do not attempt to re-enter your payment details. Contact support first to confirm whether a charge was applied before trying again. Getting Oriented Once You're Inside If the platform feels unfamiliar after signing up, our support team can walk you through where to find the tools you need and how to set up your first project. Don't hesitate to reach out — getting started guidance is something we're happy to provide 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 Stuck OTTO Trial Activation

🔍 What causes this issue? Your OTTO trial activation can get stuck while it is setting up your OTTO project. Until that activation finishes, the OTTO connection in WordPress cannot be completed, so the plugin connection will keep failing even if you retry it. The blocker is the incomplete activation, not your WordPress setup itself. ✅ What to do first 1. Allow the OTTO trial activation for your website to finish in Search Atlas before attempting the WordPress connection. 2. Do not start multiple trial activations or projects for the same website while one is still in progress, as this can make it harder to identify the correct project later. 3. Once the trial activation has fully completed, return to the OTTO plugin in WordPress and retry the connection. ⚠️ If the activation stays stuck A trial activation that remains stuck typically needs to be investigated and completed by our team rather than resolved entirely from your side. Continuing to retry the WordPress plugin connection while the activation is incomplete will not fix it — the plugin needs a fully activated OTTO project before it can connect successfully. 💬 Information to have ready when you contact us To help us resolve a stuck activation as quickly as possible, please gather the following details before reaching out: - Your website URL and the domain used for the OTTO trial. - The exact message or behavior you see during activation, such as whether it never completes. - The date and time (including your timezone) when you started the trial activation. - Any steps you have already tried, such as retrying the WordPress connection. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

VIP Hub Subscription Cancelled Message Display Bug

What Is This Issue? Some customers accessing the VIP Hub are seeing a message that states their subscription has been cancelled, even though their account may be fully active. This is a known display error within the VIP Hub interface — your subscription may not have actually been cancelled. This article explains what is known about this issue and how to get it resolved quickly. What We Know Our team has identified a subscription cancellation display error occurring within the VIP Hub. The error causes a cancellation message to appear incorrectly for some users. Because this is a display-level issue, the message you see in the VIP Hub may not reflect the true status of your account. Steps to Resolve the Display Error Because this is a display-level bug, the recommended step is to reach out to our support team so they can verify your actual account status and confirm whether your subscription is still active. Do not take any account actions (such as re-subscribing or making payments) based solely on this message before speaking with support. What to Have Ready When You Contact Support To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - Your account email address or username. - The exact wording of the cancellation message you are seeing. - Confirmation of which hub you were accessing (e.g. VIP Hub). - The date and approximate time you first noticed the message. - Any recent account activity you are aware of, such as a plan change, renewal, or payment. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Resolve OTTO Quota Blocked by Payment Issues

🔍 Understanding the OTTO Quota Block When your OTTO quota becomes blocked due to an unpaid or failed invoice, you'll see an error like Quota Exhausted – 0 OTTO AI Suggestions even though you have available AI Generation Points. This happens because your account's quota access is frozen until your payment issue is resolved. The quota block is a safety measure—it prevents further usage while your billing is incomplete. ⚠️ Why Your Payment May Be Failing Payment failures typically occur for these reasons: - Expired or outdated card information – Your payment method's expiration date has passed or details are no longer valid. - Insufficient funds – Your bank account or card doesn't have enough balance to cover the charge. - Bank or card restrictions – Your financial institution has blocked the transaction for security reasons or declined it outright. - Billing address mismatch – The address on file doesn't match your card issuer's records. - International payment blocks – Some payment processors flag cross-border transactions as suspicious. ✅ Steps to Unblock Your OTTO Quota Step 1: Update Your Payment Method 1. Log into your Search Atlas account and click your Avatar (top-right). 2. Select Billing, then go to Plans & Top-ups. 3. Click Add Payment Method. 4. Enter your current card details or add a different payment method (debit card, credit card, or other accepted option). 5. Ensure the billing address matches your card issuer's records exactly. Step 2: Retry Your Payment 1. After updating your payment method, locate your outstanding invoice in the Billing section. 2. Click Pay Now or Retry Payment. 3. Complete the payment process. A confirmation email will arrive once the transaction succeeds. Step 3: Verify Quota Has Been Restored 1. Navigate to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Look for your OTTO quota display under the OTTO SEO section in Avatar → Billing → Plans & Top-ups (typically shown as remaining OTTO AI Suggestions). 3. If your quota now shows available points, your block has been lifted and you can resume using OTTO features. 🛠️ Troubleshooting Payment Failures If payment still fails: - Contact your bank – Call your card issuer's fraud department to confirm the transaction is allowed. - Use a different payment method – Try a different card or alternative payment option if available. - Verify billing address – Confirm your address matches exactly what your bank has on file (including capitalization, abbreviations, and spacing). - Check for temporary holds – Some banks place temporary holds on payments; wait 24 hours and retry. 💡 Preventing Future Quota Blocks Enable Auto-Renewal – If your plan supports it, enable automatic payment renewal so invoices are paid before they become overdue. Keep Payment Methods Current – Update your card details before expiration dates to avoid payment failures. Monitor Your Billing – Check your billing section regularly for any payment notices or upcoming due dates. Purchase Top-Ups in Advance – If you use OTTO frequently, consider purchasing quota top-ups when your points are still available rather than waiting until exhausted. ❓ Still Seeing the Error? If you've completed all steps above and your OTTO quota remains blocked, there may be a backend issue preventing the quota from refreshing. If you need further assistance, open 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 Login Loop After Paying

🔍 What Is Happening? After completing a purchase, some customers find that logging in sends them back to the registration page or prompts them to enter card details again — as if their subscription was never activated. In most cases, this happens because the email address used to log in does not match the email address on the account where the payment was processed. 💡 Why Does This Happen? It is common to have more than one email address and to accidentally type a variation when signing up or logging in. For example, a payment might be tied to yourname@gmail.com while you are trying to log in with yourname.work@gmail.com. Even a small difference — a missing word, an extra letter, or a different domain — will cause the platform to treat you as a new, unregistered user. 🛠️ How to Resolve It 1. Check all email addresses you own. Think about every email address you may have used when you first signed up or completed checkout — personal, work, or alternative accounts. 2. Check your payment confirmation email. Look in your inbox (and spam or junk folders) for a receipt or confirmation sent around the time of purchase. The email address that received this message is very likely the one registered to your account. 3. Try logging in with each email address. Go to the Search Atlas login page and attempt to sign in using the email addresses you identified in the steps above. 4. Use the Forgot Password option if needed. If you are unsure of the password for a particular email address, use the password reset option on the login page. Enter the email, check that inbox for a reset link, and follow the instructions to set a new password. 5. Confirm access. Once you log in successfully, you should land on your dashboard with your subscription active and all features accessible. ⚠️ Important Things to Check - Double-check for common typos such as missing words, swapped letters, or different domains (for example, .com vs .net). - If you use Google or another single sign-on method, make sure you are selecting the correct Google account — your browser may default to an account that is different from the one used at signup. - Check spam and promotions folders for the original signup or purchase confirmation, as these can help you identify the correct email. 🆘 Still Stuck? If you have tried all the email addresses you can think of and still cannot access your account, our team can look up the correct email on your behalf using your payment details. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💳 Fix OTTO SEO Billing Errors Fast

🔍 Overview Billing errors related to OTTO SEO V3 and OTTO SEO can occur for a variety of reasons, including payment processing issues, plan mismatches, or usage overages. This article walks you through the most common billing errors, how to resolve them yourself, and when to escalate to our support team. ⚠️ Common OTTO SEO Billing Errors Before reaching out for help, check whether your issue matches one of these common scenarios: - Duplicate charges: Your payment method was charged more than once for the same billing period. - Incorrect plan amount: The amount charged does not match your selected OTTO SEO V3 or OTTO SEO plan. - Failed payment not reflected: A payment failed but your account still shows a balance due or was unexpectedly downgraded. - Missing credits or usage limits: OTTO SEO credits were deducted incorrectly or your usage limit appears lower than your plan allows. - Upgrade or downgrade not applied: A recent plan change was not reflected in your invoice or available features. 🛠️ Step-by-Step Troubleshooting 1. Check your billing history. Navigate to the top-right avatar → Billing inside the Search Atlas platform. Review your invoices to confirm the charge amounts and dates. 2. Verify your current plan. Go to top-right avatar → Billing → Plans & Top-ups (Billing) and confirm that the plan listed matches what you signed up for. If you recently upgraded or downgraded, allow up to 24 hours for changes to fully process. 3. Review your OTTO SEO credit usage. Open the top-right avatar → Billing → Plans & Top-ups and check your credit balance and usage log. Confirm whether credits were consumed by scheduled tasks, automations, or manual actions. 4. Check your payment method. Under the top-right avatar → Billing (Plans & Top-ups tab), use the Add Payment Method button to make sure your card or payment details are current and valid. An expired card can trigger failed payments that result in account restrictions. 5. Clear your browser cache and reload. Sometimes display errors cause billing figures to appear incorrectly. A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) can resolve visual discrepancies. 📋 Information to Have Ready Before Contacting Support If you cannot resolve the billing error on your own, gathering the following details in advance will help our team resolve your issue faster: - The invoice number or transaction ID from your billing history - The date and amount of the incorrect charge - A brief description of what you expected to be charged versus what was actually charged - Your current plan name (e.g., Starter, Pro, Agency) and any recent plan changes - Screenshots of the billing error or incorrect charge, if available 🔄 How Billing Disputes Are Handled Once our support team receives your billing dispute, here is what to expect: - Acknowledgement: A team member will review your account and billing records, typically within one business day. - Investigation: Our billing team will cross-reference your plan, usage data, and payment processor records to identify the root cause. - Resolution: Depending on the error type, we may issue a credit to your account, process a refund, or correct your subscription details. You will be informed of the outcome directly through the chat. Please note that refund eligibility is subject to our billing policy. Our team will advise you on the available options based on your specific situation. 💡 Tips to Prevent Future Billing Errors - Keep your payment method up to date, especially before your renewal date. - Review your OTTO SEO credit usage regularly to avoid unexpected overages. - When changing plans, confirm the change is reflected under top-right avatar → Billing → Plans & Top-ups (Billing) before assuming it has taken effect. - Enable billing notifications in your account settings so you receive alerts for upcoming renewals and payment failures. 🙋 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.

🛠️ Paid OTTO Seats Not Appearing in Your Account

🔍 Overview After purchasing additional OTTO seats, most accounts are provisioned automatically. However, in some cases a known billing sync issue can prevent your new seats from appearing — even after a successful payment and receipt. This article explains how to confirm the problem and resolve it. ⚙️ What Causes This Issue A quota provisioning gap can occur between our billing system and the product, meaning your account is charged correctly but the seats are not reflected in the platform. This is a known issue our engineering team is actively working to resolve. ✅ Step 1: Confirm the Charge Went Through Before taking further action, verify that your payment was processed successfully: 1. Log in to your Search Atlas account and navigate to your Billing section. 2. Check that an invoice or receipt exists for the OTTO seat purchase. 3. Look for a recent charge or transaction entry related to your OTTO seat add-on to confirm the payment completed. If you can see a charge or invoice but your OTTO seats are still not available in the platform, proceed to the next step. 📊 Step 2: Check Your Current OTTO Quota Navigate to your Avatar (top-right) → Billing → Plans & Top-ups (Team Members quota) and review your current seat quota. Compare the number of available OTTO sites against the number of seats you purchased. If the available seats do not match your purchase, your account has not been provisioned correctly and you will need to contact support for a manual fix. ⏱️ Step 3: Wait and Refresh (24-Hour Window) In many cases, the provisioning delay resolves automatically within 24 hours of purchase. After confirming your charge and reviewing your quota: 1. Wait up to 24 hours from the time of purchase. 2. Log out of your Search Atlas account completely. 3. Close your browser or clear your browser cache. 4. Log back in and navigate to the OTTO section again. 5. Check if your OTTO seat quota has updated. If your seats appear after refreshing, the issue is resolved and you can begin connecting new OTTO sites immediately. 💬 Step 4: Contact Support for a Manual Fix If your OTTO seats still do not appear after 24 hours and a full refresh, this issue requires a billing team member to manually update your quota on the back end. To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The number of OTTO seats you purchased - The date of purchase - Your invoice number or confirmation email - A screenshot of your current OTTO quota showing the mismatch Once you contact support and share the above details, our billing team can apply the fix immediately on their end — you do not need to take any additional action inside the platform. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. 🚀 What Happens Next Once your request is received, our billing team will update your OTTO seat quota manually on the back end. After the fix is applied, you will receive a follow-up confirmation. We recommend refreshing the platform and checking your OTTO quota again to confirm the seats are now showing correctly. 💡 Tips to Avoid Confusion - Always check your Billing section first to confirm a successful charge before assuming seats are missing. - If you recently changed your subscription plan, be aware that plan changes can sometimes affect add-on quotas — mention this to the support agent when you reach out. - Most provisioning issues resolve within 24 hours; a full browser refresh often helps the updated quota appear correctly.

🔧 Fix GSC Site Limit After Plan Upgrade

Overview After upgrading your Search Atlas plan, you may notice that the number of active Google Search Console (GSC) sites available does not immediately reflect your new plan's limit. In most cases, resolving this requires our support team to manually verify and sync your updated plan entitlements on the backend. The preliminary steps below are worth trying first, but please be prepared to escalate quickly if they do not resolve the issue. Why This Happens Your GSC site limit is tied directly to your active subscription tier. When you upgrade, the system needs to verify and apply your new plan entitlements. In some cases, the update may not reflect instantly due to reasons such as cached browser data or account entitlements not yet syncing across all platform modules. A backend sync by our support team is often required to fully apply the new limit. Preliminary Checks 1. Confirm your upgrade was successful. Navigate to the top-right avatar → Billing (Plans & Top-ups) and verify that your current plan reflects the upgraded tier. Check that the billing charge has been processed. 2. Hard-refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear the cached page and reload the latest platform data. 3. Log out and log back in. Sign out of your Search Atlas account completely, then sign back in. This forces the platform to reload your updated account permissions and plan entitlements. 4. Check your active site slots. After logging back in, navigate to the GSC site management area of the platform and review how many active sites are currently listed. The count should reflect your new plan's limit. 5. Check workspace settings. If you manage multiple workspaces, ensure you are operating within the workspace that holds the upgraded subscription. Limits are applied at the workspace level, not the individual user level. Backend Resolution — What to Expect If your GSC site limit still does not reflect your upgraded plan after completing the steps above, the most likely resolution is a manual backend entitlement sync performed by our support team. This is not something you can trigger yourself from the platform. When reaching out, please have the following ready so our team can act quickly: - Your account email and workspace name - The date and time of your plan upgrade - The number of active GSC site slots currently shown in your account - A screenshot of your current billing or subscription page confirming the upgraded plan If you need further assistance, open 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 URL Indexer Quota After Hyperdrive Top-Up

🧭 Overview Some customers notice that their URL Indexer quota still displays as exhausted immediately after completing a Hyperdrive Credit (HDC) top-up. This can be alarming — especially if you have a large batch of URLs, such as newly purchased backlinks, waiting to be indexed. This article explains why this happens, what has been fixed, and what steps to take if you are still affected. ⚠️ What Caused This Issue A resolved platform bug affected how Hyperdrive Credits were converted into URL Indexer quota. Specifically: - In some cases, a top-up deducted Hyperdrive Credits from your balance but did not correctly award the corresponding URL Indexer quota. - In other cases, the quota display did not refresh after a successful top-up, making it appear as though no quota had been added even when it had. - A separate related issue caused top-ups to over-award quota or bypass credit consumption entirely, which triggered a correction that may have affected some accounts during the fix window. All of these issues have been marked as resolved by the Search Atlas engineering team. If you topped up recently and still see an exhausted quota, the steps below will help you confirm your current balance and get indexed quickly. 🛠️ Steps to Resolve a Quota Sync Issue 1. Navigate to the URL Indexer. Go to Left sidebar → Authority → Indexer (URL Indexer). 2. Check your displayed quota. Look at the quota counter at the top of the page. If it still reads zero or exhausted, proceed to the next step. 3. Hard-refresh the page. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force a full reload. This clears any cached quota display and pulls the latest data from the server. 4. Verify your Hyperdrive Credit balance. Check your account billing or credits section to confirm the top-up transaction completed and that credits were deducted. If credits were deducted but quota is still zero after a refresh, this is a billing discrepancy that requires manual review. 5. Wait up to 5 minutes. In rare cases, quota sync can take a few minutes to propagate. Refresh again after waiting briefly. 6. Retry submitting your URLs. Once quota appears correctly, submit your backlink URLs for indexing as normal through the URL Indexer interface. 💡 Tips for Indexing Large Batches of Backlinks - Submit in batches. If you have hundreds or thousands of URLs, break them into smaller batches of 100–500 URLs. This makes it easier to track progress and identify any URLs that fail validation. - Use valid URL formats. The URL Indexer validates each URL before processing. Ensure all submitted URLs include the full protocol (e.g., https://) and have no spaces or special characters. - Monitor quota consumption. After each batch submission, check the quota counter to confirm URLs were accepted and quota was deducted as expected. - Top up proactively. If you regularly purchase backlinks in large volumes, consider topping up your URL Indexer quota before you need it to avoid delays. ❓ Frequently Asked Questions Will I be charged twice if there was a sync error? The engineering fixes ensure that Hyperdrive Credits are only deducted once per valid top-up and that the correct quota is awarded. If you believe you were charged without receiving quota, contact support via the chat widget so the team can audit your transaction history and issue any necessary correction. Can I use Hyperdrive Credits for anything other than URL Indexer top-ups? Hyperdrive Credits are used for specific Authority-building features. They are not applicable to AI generation quota or other unrelated platform features. If you received guidance stating otherwise, please disregard it — it was inaccurate. What if my quota shows correctly but URLs are not being indexed? Confirm that your URLs pass validation (correct format, publicly accessible). If valid URLs are submitted but not processed within a reasonable timeframe, reach out via the chat widget for investigation. 🆘 Still Need Help? If you have confirmed that Hyperdrive Credits were deducted but your URL Indexer quota was not updated after following the steps above, our team can manually audit your account and restore any missing quota. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💸 Understand Billing, Indexing, and Plan Limits

🧾 Why Am I Being Charged Beyond My Base Plan? The Starter plan includes a set number of indexing credits each billing cycle. If you submit more URLs than your plan allowance covers, Search Atlas may apply top-up credits to keep your requests running. These additional charges will appear as a separate line item on your invoice. To understand your charges, review the billing section of your Search Atlas dashboard, where you can see a breakdown of your base plan credits and any additional top-up charges applied during the billing period. - Base plan credits: Included in your monthly fee and reset each billing cycle. - Top-up credits: Applied when base credits are exhausted, billed at the applicable top-up rate. - Unexpected charges: If you see charges you don't recognize, please reach out to our support team with your account details and the invoice date so we can review the billing activity with you. 🔍 How Does Indexing Work on the Starter Plan? The Starter plan uses two indexing methods to request that search engines crawl and index your pages: 1. Google Search Console (GSC) Integration: Search Atlas connects to your verified GSC property and submits URLs through the Google Indexing API. This method is subject to Google's daily quota limits, which are set by Google and cannot be changed by Search Atlas. 2. Bing IndexNow: Search Atlas simultaneously pings Bing via the IndexNow protocol, which typically processes submissions faster than GSC. For both methods to work, you must complete the integration setup within your Search Atlas account. If either connection is missing or broken, submissions may fail or remain pending without being sent. Important: Submitting a URL does not guarantee indexing. Search engines make the final decision on whether and when to index a page. Indexing requests are a signal, not a command. ⚙️ What to Do If Indexing Is Not Working If pages are not being indexed or submissions appear to be failing, the most reliable first step is to contact our support team directly. Because indexing issues can stem from GSC quota limits, integration configuration, or plan-tier restrictions — factors that vary per account — our team can review your specific setup and identify the root cause. When you reach out, please have the following ready to help us resolve your issue as quickly as possible: - Your Search Atlas account email or workspace name - The URLs you submitted that are not being indexed - The approximate date and time you submitted them - Any error messages or status labels you have seen in your dashboard - Whether your GSC property is verified directly in Google Search Console at search.google.com/search-console Unverified GSC properties cannot receive API submissions. If you need further assistance, open 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 GSC Quota Errors and Understand Plan Limits

🔍 What Does the 'Quota Exceeded' Error Mean? When you try to connect a Google Search Console (GSC) site and see a Quota Exceeded error, it means you have reached the maximum number of GSC sites allowed on your current plan across your workspace. This is not a Google-side error. The limit is enforced by Search Atlas based on the plan your workspace is subscribed to. 📋 GSC Site Limits by Plan Each Search Atlas plan includes a set number of GSC site connections. If your workspace has reached the maximum for your current plan, you must either remove an existing GSC site or upgrade to a higher plan before adding a new one. If your workspace has not yet reached the maximum for your plan, re-check whether the site you are adding is a duplicate, improperly formatted, or already connected under a different property type (domain vs. URL prefix). 🛠️ How to Fix a Quota Exceeded Error 1. Navigate to your GSC integrations area within the Search Atlas dashboard. 2. Review your connected sites and identify any that are no longer needed. 3. Disconnect any site you no longer require to free up a slot. 4. Try adding your new GSC site again. If you need all existing sites and still require more connections, upgrading your plan is the recommended solution. You can find plan and billing options by clicking your avatar in the top-right and selecting Billing. ⬆️ How to Upgrade Your Plan 1. Open Billing from the top-right Avatar Menu (👤) in the Search Atlas dashboard. 2. Review the available plans and identify one that meets your GSC site connection needs. 3. Follow the on-screen steps to upgrade. 🎁 GSC Connections During a Free Trial The number of GSC site connections available to you depends on the plan tier selected when you started your free trial. To confirm exactly which features and limits apply to your current trial, check your account's plan details page or contact our team for clarification. If you need further assistance, open 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 Blocked Website Connection in OTTO SEO

🔍 Why Is My Website Connection Blocked? If you see a prompt asking for a credit card when trying to connect your website to OTTO SEO Automation — even though you have already made a purchase — it almost always means one of two things: - Your subscription is inactive — the plan that includes OTTO SEO has expired or was cancelled. - A payment has failed — a recent charge was declined, which automatically paused access to connected features. Search Atlas requires an active, paid subscription to establish and maintain website connections inside OTTO SEO. When a payment issue is detected, the platform suspends the connection to protect your account and prompts you to update your billing details. ⚙️ How to Diagnose the Issue 1. Log in to your Search Atlas account. 2. Click your avatar in the top-right corner and go to Billing → Plans & Top-ups. 3. Check the PRO Plan Subscription status text. It should read Active. If it shows Cancelled, Past Due, or Inactive, that is the root cause. 4. Scroll to the Payment Method section and confirm your card details are current and have not expired. 5. Review the Recent Invoices list for any invoice marked Failed or Unpaid. 💳 How to Resolve a Failed Payment 1. Click your avatar in the top-right corner, go to Billing → Plans & Top-ups, and click Add Payment Method. 2. Enter your new or corrected card details and click Save. 3. Once saved, click Retry Payment next to the failed invoice (if that option is shown), or wait up to a few minutes for the system to attempt the charge automatically. 4. When the invoice status changes to Paid and your subscription shows Active, your website connection will be restored. 🔄 How to Reactivate a Cancelled Subscription 1. Go to Billing → Plans & Top-ups and click Reactivate Plan or Choose a Plan. 2. Select the plan that includes OTTO SEO Automation and complete the checkout process. 3. After payment is confirmed and your subscription is active, navigate to OTTO SEO in the left sidebar, open SEO Automation, and reconnect your website. 🌐 How to Reconnect Your Website After Resolving the Issue 1. In the left sidebar, go to Website Studio (URL: /website-studio). 2. Select the website you want to connect, or add a new one. 3. Follow the on-screen prompts to complete the connection — you should no longer be asked to enter a credit card if your subscription is active. 💡 Tips to Prevent This in the Future - Keep your payment method up to date. Update your card before it expires to avoid automatic suspension. - Enable billing notifications. Search Atlas sends email alerts when a payment fails — make sure your account email is monitored. - Check your subscription status periodically, especially if you recently switched plans or used a promotional period. 🛠️ Still Need Help? If you have updated your billing details and your website connection is still blocked, or if you are unsure which plan includes OTTO SEO, our team can review your account 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.

URL Indexer Quota Not Resetting After Renewal

Understanding the Issue After your billing cycle renews, you may notice your URL Indexer quota still appears fully used and is preventing you from submitting new URLs. This can happen because the URL Indexer includes two distinct types of quota that behave differently at renewal. Recurring vs. Non-Recurring Quota Explained Your URL Indexer quota is made up of two separate allocations: - Recurring quota: A set number of URL indexing credits included in your plan that automatically renew each billing cycle. - Non-recurring quota: Additional credits purchased separately as a one-time top-up. These do not reset or replenish at renewal — once used, they are gone. If your counter does not reset as expected after renewal, it is likely because the bulk of your available quota came from a one-time purchase that has already been fully consumed. The smaller recurring portion from your plan will still be added on your renewal date, but this may not be enough to visibly change a near-full counter. What Happens at Billing Renewal On your renewal date, Search Atlas automatically adds your plan's recurring URL Indexer credits to your account. This happens in the background — you do not need to take any action to trigger it. However, if your counter still appears maxed out after renewal, it is most likely because: - Your non-recurring (purchased) credits were already fully used before renewal. - The recurring credits added at renewal are a small number relative to your total limit, so the counter may still appear nearly full. How to Check Your URL Indexer Usage 1. Navigate to the URL Indexer section of your Search Atlas account. 2. Review your current quota usage to confirm how many credits remain. 3. Check whether your billing renewal date has passed — if it has and your quota still appears blocked, your recurring credits may not have been applied yet, or you may need additional credits. How to Get More URL Indexer Credits If your recurring plan credits are not sufficient for your needs, you have two options: - Upgrade your plan: A higher-tier plan may include a larger recurring URL Indexer quota each month. - Purchase a top-up: You can buy additional non-recurring credits. Keep in mind that these are a one-time addition and will not renew automatically. To explore upgrade or top-up options, please contact our support team who can assist you with the available choices for your account. Still Need Help? If your quota does not appear to have updated after your renewal date, or you are unsure which type of credits were consumed, reach out to our support team via the chat icon in your account and we will investigate your quota status directly.

🛠️ Fix OTTO Site Count and Billing Discrepancy

🔍 Overview Some customers have noticed a mismatch between the number of OTTO sites they are being billed for and the number of sites that actually appear in their account. For example, you may be billed for 12 sites but only see 11 in the platform, or find that adding a previously removed site prompts an unexpected charge. This is a known backend issue that requires our team to correct manually. ⚙️ What Causes This? This discrepancy is caused by a backend quota or billing sync issue. Known related problems include: - OTTO site quotas showing a higher or lower number than what was originally purchased. - Re-adding a site triggering a new charge even when a billing slot already exists for it. These issues cannot be self-resolved from within the platform because they require a backend correction by a specialized team. 📊 How to Check Your OTTO Site Count Before reaching out, confirm the discrepancy on your end: 1. Navigate to OTTO SEO → All Sites (OTTO SEO Projects) to view all sites currently connected to OTTO. 2. Count the number of active sites listed there. 3. Compare that number to the quantity of OTTO sites shown on your billing dashboard. 4. If the billed quantity is higher than your active site count, or if adding a site you previously had prompts an unexpected charge, you have a discrepancy that needs to be corrected. 🚀 How to Get This Fixed Because this issue requires a backend correction, our specialized team can resolve it once they are made aware of it. Follow these steps to get your discrepancy corrected as fast as possible: 1. Gather the following details before reaching out — having these ready will allow the team to escalate your case immediately: - The number of OTTO sites you are currently being billed for. - The number of active OTTO sites you can see in your account. - The domain(s) that are missing or causing an unexpected charge. - A brief description of what action triggered the discrepancy (for example, re-adding a removed site). 2. Open the chat widget inside the Search Atlas platform and send a message to our support team. Include all the details listed above in your first message so no back-and-forth is needed. 3. If you prefer, you can also email us at support@searchatlas.com with the same details. 4. Our support team will confirm receipt and escalate your case to the specialized internal team who performs the backend correction. You do not need to take any further action after submitting your report. 5. You will be notified once the correction has been applied and your site count and billing are back in alignment — no additional charge is applied for the correction. 💡 What to Expect Once our team receives your report, the discrepancy is escalated to a specialized internal team who performs a backend correction. The fix brings your site count and billing back into alignment. To help our team resolve this as quickly as possible, make sure to include all the details listed above — specifically the billed site count, the active site count you see in the platform, and the affected domain(s) — when you first reach out. If you are unsure whether you have a discrepancy, follow the steps in the How to Check Your OTTO Site Count section above before contacting support. If you need further assistance, our team is happy to help — reach out via the in-platform chat at any time.

💳 Billing, Indexing Plans, and Fixing Index Failures

📋 How Search Atlas Billing Works Your base subscription covers a fixed monthly allowance of indexing credits based on your plan tier. If you submit more URLs than your plan includes, Search Atlas may apply additional charges on top of your base plan fee to fulfil those requests. This means your monthly invoice may be higher than your base plan cost if you have submitted URLs beyond your included allowance. You can review all charges, credit usage, and top-up history at any time by clicking your Avatar (top-right) → Billing (Activity Log / Invoices tabs). - Base plan fee: charged on your renewal date regardless of usage. - Additional charges: may apply when your submitted URLs exceed your plan's monthly credit limit. - Credit rollover: check your plan details in your account settings to confirm whether unused credits carry over to the next billing cycle. 🔍 How Indexing Works in Search Atlas Search Atlas uses two indexing channels to submit your URLs to search engines: 1. Google Search Console (GSC) API — Search Atlas connects to your verified GSC property and submits URLs through Google's official indexing pipeline. 2. Bing IndexNow — URLs are simultaneously pinged to Bing and other IndexNow-compatible engines for faster discovery. Both channels must be correctly configured for indexing to work. If either connection is missing or broken, submissions may fail or return errors. ⚙️ Setting Up GSC and Bing IndexNow Google Search Console setup: 1. Navigate to the Integrations section inside your Search Atlas account settings and locate the Google Search Console option. 2. Initiate the connection and sign in with the Google account that owns your GSC property. 3. Select the correct property, making sure it matches the exact URL prefix or domain of your site. 4. Save the connection and confirm that the integration shows an active status before submitting URLs. Bing IndexNow setup: 1. Navigate to the Integrations section inside your Search Atlas account settings and locate the Bing IndexNow option. 2. Search Atlas generates a unique API key for your site — copy it as directed on screen. 3. Upload the key file to the root of your website as instructed (e.g., yoursite.com/your-key.txt). 4. Complete the verification step on screen. Once the integration shows an active status, Bing IndexNow is ready to use. If either integration shows a warning or disconnected status, re-authenticate or re-upload the key file before submitting URLs. 🚨 Why Your Pages May Not Be Indexing After Several Days Submitting URLs in Search Atlas does not guarantee immediate or complete indexing — search engines make the final decision. However, if a significant number of your submitted URLs remain unindexed after several days, work through the following checks: - Verify both integrations are active: Return to the Integrations section and confirm that both GSC and Bing IndexNow show an active (not disconnected or warning) status. A broken connection means submissions are not reaching search engines. - Check that the correct GSC property is selected: If the property in Search Atlas does not exactly match your site's URL (including http vs https and www vs non-www), submissions will fail silently. - Confirm the Bing IndexNow key file is accessible: Open a browser and visit yoursite.com/your-key.txt — if the file returns a 404 or is blocked, re-upload it to the root of your site. - Review your credit balance: If your plan's monthly indexing credit limit has been reached and no top-up has been applied, new URL submissions will not be processed. Check your credit usage under your Avatar (top-right) → Billing (Activity Log / Invoices tabs). - Check for crawlability issues: Search Atlas can submit URLs, but if those pages are blocked by robots.txt, require login, or have a noindex tag, Google and Bing will not index them regardless of submission. Review your pages directly to rule this out. - Allow additional time for lower-authority sites: New or low-authority domains may take longer for search engines to crawl and index even after a valid submission. This is normal search engine behavior and not a Search Atlas error. If you have confirmed all integrations are active, credits are available, and pages are crawlable, but indexing is still not occurring, escalate by opening the chat widget and providing your project name, the specific URLs affected, any error messages shown in the platform, and the date you first submitted those URLs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ GSC & Bing Indexing, AI Premium Credits, and Domain Knowledge Network Guide

Fix GSC Instant Indexing and Bing Indexing issues, recover missing AI Premium credits, and build a cluster-driven content strategy with the Domain Knowledge Network (DKN). ⚠️ Content AI Processing Errors in the Article Editor If you see an error when editing the About The Author section or other AI-assisted fields in the article editor, this is a known intermittent issue with the Search Atlas content AI processing pipeline. - Check status.searchatlas.com for the latest incident updates before contacting Support. - No action is needed on your end — the Search Atlas team is actively mitigating the issue. - Wait a few minutes, then try editing again. Once the incident resolves, all AI-assisted article fields will function as expected. 🔍 GSC Instant Indexing Troubleshooting Search Atlas GSC Instant Indexing submits your URLs directly to Google Search Console for faster crawling and indexing. If submissions are not going through, follow these steps: 1. Go to Settings → Integrations and confirm your Google Search Console account is connected. 2. Verify the correct GSC property — either a domain property or a URL-prefix property — is selected. 3. Re-submit the affected URL from the Instant Indexing tool. If your connection is confirmed active and submissions still fail, contact Search Atlas Support with the affected URLs so the team can investigate further. 🔗 Bing Indexing Troubleshooting Search Atlas Bing Indexing uses the Bing URL Submission API, which requires root access — admin-level control over your domain's DNS or server — to verify ownership with Bing Webmaster Tools. - If your hosting provider controls DNS on your behalf, Bing Indexing cannot be configured until you obtain root access to add TXT verification records. - Confirm root-level DNS or server access before connecting Bing Indexing in Search Atlas. - If access is confirmed but the integration is still failing, contact Search Atlas Support to escalate the issue. Once domain ownership is verified and the integration is active, Search Atlas will submit your URLs to Bing automatically. 💳 Missing AI Premium Credits — Recurring vs. Non-Recurring Search Atlas AI Premium credits come in two types with different restoration rules. Understanding the difference helps set the right expectations when you contact Support. - Recurring credits refill monthly as part of your plan. If they appear missing or depleted in error, Search Atlas Support can restore them directly. After restoration, reload your browser tab to see the updated balance. - Non-recurring credits are one-time top-up credits. Once consumed, they cannot be restored by Support. When contacting Support about missing credits, specify whether the shortfall is in your recurring or non-recurring balance so the correct action can be taken right away. 🗺️ How to Use the Domain Knowledge Network (DKN) Strategically The Domain Knowledge Network (DKN) maps your domain's topical coverage — showing which subject clusters you own, which are partially covered, and where gaps exist. Use that gap data to drive your content calendar instead of planning topics at random. 📌 Find Your Next Articles in the Gap Map Open the Topical Maps and look for cluster gaps — topic areas where your domain has little or no coverage. Each gap signals a missing article. Treat the full gap list as your prioritized content backlog. 🎯 Fill Partial Clusters Before Opening New Topics 1. Identify clusters where you already have some content but coverage is incomplete. 2. Prioritize filling those clusters first — completing a partial cluster builds topical authority faster than starting a brand-new topic area from scratch. 3. Follow the cluster structure, not individual keyword impulses. 📈 Rank Your Gaps by Authority Potential Within your gap list, move to the top any clusters where your existing domain equity gives you a competitive advantage — topics where you are closest to establishing clear authority. 🔗 Combine the DKN with the Search Atlas Content Planner Use the DKN alongside the Search Atlas Content Planner to convert cluster gaps into scheduled, briefed articles with target keywords, structure recommendations, and word-count guidance. This keeps your strategy cluster-driven from planning through publication. For step-by-step walkthroughs, visit the Search Atlas documentation and sign up for a live DKN training session. 🌀 You now know how to troubleshoot GSC and Bing Indexing failures, recover recurring AI Premium credits, and apply a gap-first, cluster-driven approach with the Domain Knowledge Network — check status.searchatlas.com any time to monitor for active incidents affecting Search Atlas tools.

🔍 Duplicate Geogrid Scans and Credits

🔍 Why duplicate scans can happen Geogrid scans run asynchronously, which means processing may continue after a scan is submitted. In some cases, a recovery process can incorrectly treat an active scan as stuck in PENDING status and start it again. This can create duplicate provider work and duplicate geogrid pin records. This issue is related to scan recovery handling, not the monthly automation schedule. Automated scans are still intended to run only once during their scheduled interval. 💳 Are duplicate scans charged twice? Not necessarily. In the reported incident, the duplicate scan activity did not result in a second geogrid credit charge. Duplicate processing and duplicate credit usage are separate issues, so your credit balance must be checked before restoration is considered. 🛠️ What happens to affected credits? Credit restoration is reviewed case by case. The current fix is designed to prevent recovery sweepers from restarting scans that still have asynchronous processing or an active batch job. Credit restoration is not automatically included in that fix. If your balance appears lower than expected, keep the affected project, scan dates, and geogrid details available for review. The team can verify whether credits were actually deducted and determine the appropriate next step. ✅ How to report a duplicate scan 1. Open the affected project and identify the duplicate geogrid scans. 2. Record the scan dates, approximate times, location settings, and affected keywords. 3. Compare your geogrid credit balance before and after the scans, if that information is available. 4. Open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. 🚀 How Search Atlas is preventing repeats The prevention work updates recovery checks so they skip geogrids with asynchronous processing still pending or with a live batch job. This helps prevent an in-flight scan from being mistaken for a stuck scan and dispatched again. Until the prevention update is fully available, a duplicate-looking result does not always mean that two credits were charged. Verification of the account activity is required.

🛠️ Fix SAB Dummy Address Citations and Get Credits Back

🏠 Understanding the SAB Citation Problem If you manage a Service Area Business (SAB) — a business that serves customers at their location rather than a physical storefront — your Google Business Profile (GBP) is set to hide your address from the public. However, some third-party citation directories and data aggregators do not support address suppression. When a citation is submitted to one of these incompatible directories, your internal dummy address (the placeholder address used for NAP consistency) can be published publicly instead of being hidden. This creates two problems: your private address is exposed, and the credits spent submitting to those incompatible aggregators may not have delivered value. This article explains how to identify affected citations, request corrections, and ask for credit reimbursement. 🔍 Step 1 — Identify Which Citations Were Affected Before contacting support, gather the details of each affected citation so your request can be processed quickly. 1. Review your citation results within the platform and note every directory where your dummy address appears publicly instead of being suppressed. 2. For each affected listing, record: the directory name, the URL of the live listing, and the date the citation was submitted. Having this information ready will significantly speed up the correction and reimbursement process. ⚙️ Step 2 — Understand Which Aggregators Are Incompatible Not all citation networks support SAB address suppression. Directories that are incompatible will always display a physical address field and have no mechanism to leave it blank or hidden. Common signs of an incompatible aggregator include: - The listing shows a full street address even though your GBP has the address hidden. - The directory does not offer a Service Area Business or no storefront option during listing creation. - The published address matches your internal dummy address exactly. Credits spent on these incompatible aggregators are eligible for reimbursement because the submission could not be completed in a way that meets SAB privacy requirements. 📋 Step 3 — Request Address Correction and Credit Reimbursement Search Atlas handles SAB citation corrections and credit reimbursements through the support team. To submit your request, please have the following ready: - The list of affected citations compiled in Step 1, including directory names, live listing URLs, and submission dates. - A clear statement that you are requesting both address correction and credit reimbursement for incompatible aggregators. - Your project name or any other identifying information that will help our team locate the relevant citations quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⏳ Paid OTTO Account Not Showing After Purchase

🔍 Overview After purchasing an additional OTTO SEO account, most customers see it provisioned within a few minutes. In some cases, however, a known billing issue can prevent the new account from appearing — even though your payment was successfully processed. This article explains what is happening and what to do next. ⚙️ What Causes This Issue? When you complete a purchase, Search Atlas triggers an automatic provisioning step that activates your new OTTO account. In certain billing configurations, this step can fail silently after payment. The result is: - Your payment is taken successfully. - Your new OTTO account is not added to your dashboard. - The issue requires a manual fix by our finance team. This is a known issue that our engineering team has resolved at the system level. However, accounts already affected still need to be individually corrected by our team. ✅ How to Check If Your Account Is Affected 1. Go to Left sidebar → OTTO SEO (URL: /seo-automation-v3). 2. Check whether your newly purchased OTTO account appears in the list. 3. If it is missing and some time has passed since your payment, your account is likely affected by this issue. 🛠️ What To Do Next Our team can resolve this quickly by either provisioning your account manually or issuing a refund, depending on your preference. To get this sorted as fast as possible: 1. Open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a support agent. 2. Share the following details so the team can act immediately: - The email address on your Search Atlas account. - The approximate time and date of your payment. - The name of the client site you need to activate OTTO for. Our team will escalate to finance, confirm the payment, and provision your account or arrange a refund without delay. 💡 Tips While You Wait - Do not attempt to repurchase the OTTO account — you may be charged twice. - Keep an eye on your email for a payment confirmation from Stripe as proof of purchase — this may be helpful when speaking with the team. 💬 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 instantly connected with a member of our team.

🛠️ SAB Dummy Address Suppression and Credit Reimbursement

🔍 Understanding the Issue If you run a Service-Area Business (SAB), your Google Business Profile intentionally hides your physical address from the public. When Search Atlas builds citations on your behalf, a dummy address is sometimes required as a placeholder to complete directory submissions. Most directories suppress this address automatically — but some third-party aggregators publish it publicly instead. If you have found that one or more of your SAB citations show a dummy address visible to the public, this article explains how to identify affected listings, request corrections, and recover any credits spent on incompatible aggregators. ⚠️ Why This Happens Citation networks and data aggregators vary in how they handle SAB privacy settings. Directories that are fully SAB-compatible will either hide the address field or display a service-area description in its place. However, some aggregators do not support address suppression and will publish whatever address is submitted. Search Atlas flags known incompatible aggregators before submission where possible, but edge cases can occur. 📋 Step 1 — Identify Affected Citations 1. Confirm that your GBP profile is set to hide your physical address (as expected for a service-area business). 2. Review each submitted citation and check whether the directory is displaying your dummy address publicly. You can do this by visiting the live directory URL included in your citation report. 3. Make a list of every directory where the dummy address is visible. ✏️ Step 2 — Request Address Suppression or Removal Once you have identified the affected citations, take the following steps for each one: - Directories with a self-service portal: Log in to the directory account created during citation building and update the address field to remove or hide the address. Save your changes and allow time for the update to propagate. - Directories without self-service access: Contact the directory directly using their listed support channel and request that the address be suppressed or the listing be removed. Reference your business name and the dummy address so their team can locate the record quickly. - Aggregator-distributed citations: If the dummy address was pushed through a data aggregator, suppression may need to happen at the aggregator level first before downstream directories update. Note which aggregator is involved so our team can assist. 💳 Step 3 — Request Credit Reimbursement If credits were spent on citation submissions to directories that are incompatible with SAB address suppression, you may be eligible for a reimbursement. To escalate this request, please have the following ready for our support team: - Your project name or the affected SAB business name - The specific directories or aggregators where the dummy address is publicly visible - Any citation report URLs or screenshots showing the publicly displayed address Our team will review the affected submissions and determine whether a credit reimbursement applies to your account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix Your Account Plan Display Discrepancy

Why Does My Plan Look Wrong? If you are on a paid plan but notice a different plan name displayed somewhere in the platform, your account and billing may still be unaffected. A display discrepancy between what you expect to see and what is shown can occasionally occur. Because the specific cause of a plan display discrepancy can vary by account, our support team will need to investigate your account directly to identify what is happening and confirm your correct plan status. What to Have Ready When You Contact Support To help our team resolve this as quickly as possible, please have the following information ready before reaching out: - The exact plan name you believe your account should be on - A screenshot showing the incorrect plan display - The email address associated with your Search Atlas account - The approximate date when you first noticed the discrepancy If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔄 URL Indexer Quota Not Resetting After Billing

How URL Indexer Quota Resets Work Most Search Atlas quotas reset automatically on your monthly billing date. However, there is a known issue where URL Indexer credits may fail to refresh on the expected billing date, causing them to appear stale or fully consumed even when you have not submitted URLs recently. Why Your Credits May Show as Fully Consumed If your URL Indexer quota has not reset as expected after your billing date, this is likely related to a platform-level issue affecting credit refresh for the URL Indexer tool. This is a bug that requires investigation by our team on the backend — there are no self-serve steps that will resolve it directly. What to Have Ready When Escalating To help our team investigate and resolve your quota reset issue as quickly as possible, please have the following information ready before reaching out: - Your account email address associated with your Search Atlas subscription. - Your billing date — the date on which your monthly cycle was expected to reset. - The credit amounts displayed — specifically, how many URL Indexer credits are shown as available versus consumed. - Your current plan name, so our team can verify your expected quota allocation. - Any relevant screenshots of the quota display showing the unexpected state. Our team will review your account on the backend and manually trigger or correct the quota reset where needed. If you need further assistance, open 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 Hyperdrive Credit Balance and VIP Access Issues

What This Article Covers This article explains two common account questions: how to access your VIP video sessions, and why your Hyperdrive credit balance on the dashboard may not match the number of credits you expect. Accessing Your VIP Video Sessions VIP video sessions are linked to your account. If you are having trouble locating or accessing them, follow these steps: 1. Check the inbox of the email address associated with your Search Atlas account for any message containing your video access details or a redemption link. This email is typically sent at the time of purchase or plan activation. 2. If you cannot find the email, check your spam or promotions folder. 3. If you find a redemption link or access URL in your email, click it directly to activate or join your VIP session. Do not share this link, as it is tied to your account. 4. If your VIP sessions do not appear and you have a confirmation of purchase, your sessions may not yet be applied to your account. Have your order confirmation or receipt ready, then contact support so a teammate can apply your access manually. Understanding Hyperdrive Credit Balance Discrepancies If the Hyperdrive credit count shown on your dashboard does not match what you expect, this may be related to a recent purchase, plan change, or promo code redemption that has not yet fully reflected on your account. To troubleshoot on your own, try the following steps: 1. Refresh your dashboard or log out and log back in to ensure you are seeing the most up-to-date credit balance. 2. Confirm that your most recent purchase, plan change, or promo code redemption is shown as active on your account. 3. If your credit balance still does not look correct after refreshing, note the exact credit amount displayed and when you made your purchase or redeemed your code, so a support teammate can investigate efficiently. If the discrepancy remains after these steps, a support teammate can review your account history and credit records. When reaching out, please have the following ready: your account email, the exact credit amount shown, the expected credit amount, and any order confirmation or promo code details related to the transaction. If you need further assistance, open 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 Metrics and Understand Credit Refresh

Overview Site Metrics gives you access to keyword research, rank tracking, and competitive analysis tools. If your metrics stop loading — or your credits did not change after upgrading — this guide explains what to check and how to get help resolving credit or access issues. Why Site Metrics May Not Be Working There are a few common reasons Site Metrics may appear broken or fail to return data: - Credit limit reached: Each plan includes a monthly credit allowance for Site Metrics lookups. Once you exhaust your credits, queries may stop returning results until your credits refresh. - Browser or cache issue: A stale browser session can prevent the tool from loading correctly. Clear your browser cache or try a different browser. - Account sync delay: After a plan change, it can take a few minutes for your account to reflect the update. Refresh the page or log out and back in. - Incorrect navigation: Make sure you are accessing the correct section of the platform for the tool you want to use. Credits After Upgrading If your credit count did not change after upgrading your plan, our support team can investigate and resolve this for you. Credit behavior after an upgrade — including how trial credits and paid plan credits interact — depends on your specific account configuration and billing cycle details that only our team can verify. Before reaching out, please have the following ready to help us resolve your issue as quickly as possible: - Your account email address - The date you upgraded your plan - The credit balance shown in your account before and after the upgrade (if available) - Any error messages or unexpected behavior you observed Quick Troubleshooting Checklist - Clear your browser cache or switch to a different browser - Log out and log back in to force an account sync - Check your account or billing settings to view your current credit balance and refresh date - If credits still appear incorrect after a few minutes, contact support with your account details ready If you need further assistance, open 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 Hyperdrive Credit Balance Discrepancies

🔍 Overview If Atlas Brain is displaying an "Insufficient Hyperdrive Credits" error even though you believe your account has enough credits, you are not alone. This issue typically occurs when a recent top-up has not yet reflected in your available balance, or when there is a temporary sync delay between your credit account and the Atlas Brain engine. This article explains why this happens and walks you through the steps to resolve it. ⚡ What Are Hyperdrive Credits? Hyperdrive Credits (HDC) are the currency used to power Atlas Brain actions within Search Atlas. Each task or AI-driven operation consumes a set number of credits. When your balance drops too low, Atlas Brain will pause and display an insufficient credits error to prevent incomplete or failed operations. 🛠️ Common Causes of the Discrepancy - Top-up processing delay: After purchasing or adding Hyperdrive Credits, there can be a short processing window before the new balance is reflected in Atlas Brain. - Cache sync lag: Your account dashboard and Atlas Brain may briefly show different balances while the system syncs. - Pending transactions: A credit purchase that is still being verified by the payment processor will not appear as available until the transaction is confirmed. - Session-level caching: If you were already logged in when a top-up was processed, your active session may still be reading the old balance. ✅ Step-by-Step: How to Resolve the Error 1. Check your current HDC balance. Navigate to Avatar → Billing → Plans & Top-ups (Billing) to view your Hyperdrive Credits quota. Note the exact number displayed — for example, 75 HDC. 2. Confirm your top-up was completed. Go to your billing or payment history and verify that the top-up transaction shows a status of Completed or Confirmed. If it shows Pending, wait up to 15 minutes for the payment processor to finalize it. 3. Refresh your session. Log out of Search Atlas completely, then log back in. This forces your session to pull the latest credit balance from the server rather than a cached value. 4. Hard-refresh the page. After logging back in, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear any locally cached page data. 5. Re-check your HDC balance. Return to Avatar → Billing → Plans & Top-ups (Billing) and confirm whether the updated balance is now showing. If a top-up was completed, it should now be reflected. 6. Retry the Atlas Brain action. Once your balance is confirmed and correct, return to the task that triggered the error and try running it again. ⏱️ How Long Does a Top-Up Take to Reflect? In most cases, Hyperdrive Credits are added to your account within a few minutes of a successful payment. However, in some situations — particularly during high-traffic periods or when using certain payment methods — the update may take up to 15–30 minutes. If your balance has not updated after 30 minutes and your payment history confirms the transaction is complete, this may indicate an account-level sync issue that requires manual investigation. 💡 Tips to Prevent This Issue - Top up your Hyperdrive Credits before your balance reaches zero to avoid interruptions to Atlas Brain workflows. - Always wait for a payment confirmation email before assuming credits have been added. - Avoid running large Atlas Brain tasks immediately after a top-up — give the system 2–3 minutes to sync the new balance. - Regularly monitor your HDC balance via Avatar → Billing → Plans & Top-ups (Billing), especially before scheduling bulk operations. 🆘 Still Seeing the Error? If you have followed all the steps above and Atlas Brain is still reporting insufficient Hyperdrive Credits despite a confirmed top-up, there may be an account-level issue that our team needs to investigate. If you need further assistance, open 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 Billing and Slider Issues

💡 Overview OTTO billing and slot displays can occasionally show outdated information after reducing your OTTO allocation. For example, your account may have been reduced by two slots, but the billing page may still display the previous charge of $630 instead of the amount for nine slots. 🔍 Why the amount may look incorrect Billing and quota updates may not appear everywhere at the same time. A temporary display issue can cause the following: - The previous slot count remains visible after a reduction. - The billing amount does not immediately reflect the updated number of slots. - A top-up window shows an incorrect price or does not clearly show the amount already owned. These are display or synchronization issues and do not necessarily mean your account was charged incorrectly. ✅ Check your current OTTO allocation 1. Open OTTO SEO from the left sidebar. 2. Select All Sites to review the sites assigned to OTTO. 3. Check the active site count and confirm that the reduced slots are no longer assigned. 4. Open Overview and use Scan if the page appears out of date. 5. Refresh the page, then review the billing or top-up information again. 💰 Understanding a charge after reducing slots Your expected charge should be based on the active OTTO slots after the reduction is fully applied. If you should have nine slots but still see a charge based on eleven, allow time for the billing display and account quota to synchronize. Do not purchase additional slots while the displayed amount is being corrected. First confirm the active slot count and check whether the amount updates after refreshing. 🛠️ Fix the slider display issue If the OTTO slider, slot selector, or related controls appear stuck or display unexpected values: 1. Refresh the page. 2. Return to OTTO SEO → All Sites, then reopen the relevant OTTO settings. 3. Confirm the active and frozen site counts before changing the slider. 4. Make one change at a time and wait for the update to finish. 5. Check the displayed slot count and billing amount again. If a slider or other page control behaves incorrectly across multiple refreshes, avoid repeated changes. The issue may be limited to the interface display rather than your actual allocation. 📋 What to include when reporting a mismatch If the charge and active slot count still disagree, record the following before contacting support: - The number of slots you expect to have. - The number of active slots shown in OTTO SEO → All Sites. - The amount displayed on the billing or top-up screen. - When the slot reduction was completed. - A screenshot showing the mismatch, if available. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Refunds for Failed Project Crawls

🔍 Why project crawls get stuck A project crawl can remain loading when Search Atlas cannot access or complete a scan of the website. Common causes include robots.txt rules, firewall or security settings, server timeouts, DNS issues, or a site that is temporarily unavailable. A crawl that has not finished after several hours may need attention, especially if the same project has failed more than once. 🔄 What happens after a crawl fails Search Atlas uses retry attempts to recover from temporary crawl problems. The system can make up to three attempts. If all attempts fail, the crawl should be treated as unsuccessful rather than left loading indefinitely. When an eligible crawl fails after the available retries, the related quota or credits may be returned automatically. Refresh the project and review its crawl status before starting another attempt. ✅ Check your website before retrying 1. Confirm the website loads normally in a browser. 2. Check that the site is not blocking Search Atlas or automated crawlers. 3. Review robots.txt and firewall settings for restrictions. 4. Confirm that DNS and hosting services are working. 5. Make sure the project uses the correct website URL and access details. Fixing the underlying access issue before retrying can help prevent another failed crawl and additional processing time. 💳 When to request a refund Request a refund review when a project remains stuck, repeated attempts fail, or the expected quota or credit return does not appear. Include the project name, website URL, approximate start time, number of attempts, and screenshots of the loading or error message. Do not repeatedly start new attempts while the original crawl is still processing. Multiple attempts can make the project status harder to review. 💬 Contact support about a refund If the crawl has been stuck for an extended period or you need a refund review, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Our team can review the crawl history, confirm whether a retry or refund was processed, and investigate cases where a failed crawl did not receive the expected quota or credit return.

🛠️ Resolving Missing Alt Text and Refund Delays

🔍 Overview Some customers have reported that a missing image alt text bug was marked as resolved in a previous support conversation, yet the issue persists in their account. In some cases, a prorated refund was also promised as part of the resolution but has not been processed. This article explains what to expect, how to confirm the fix is applied, and how to follow up on a pending refund. 🖼️ Understanding the Missing Image Alt Text Bug The missing image alt text bug affects pages where alt attributes should be automatically detected or populated by Search Atlas tools but appear blank or absent in reports. This can cause: - Inaccurate on-page SEO audit scores - Alt text recommendations not reflecting actual page content - Persistent audit warnings even after manual fixes are applied If a previous support conversation confirmed this bug was resolved but you are still seeing the same problem, the fix may not have been fully deployed to your account, or a secondary instance of the issue may have been introduced. ✅ How to Verify Whether the Fix Has Been Applied 1. Clear your browser cache and reload the Search Atlas platform to rule out a display issue. 2. Navigate to the affected page audit and trigger a manual re-crawl by clicking the refresh or re-analyse option within the tool. 3. Check the Images section of your on-page audit report and confirm whether alt text values are now being detected correctly. 4. If the problem persists across multiple pages or projects, the bug is likely still active on your account. Document the pages affected by saving screenshots or noting the URLs. This information will help the support team investigate and escalate the issue more quickly. 💳 Understanding Prorated Refunds When a confirmed platform bug impacts your ability to use a feature you pay for, our support team may approve a prorated refund to credit you for the affected period. Here is what you should know: - Refunds are processed manually by our billing team after a support agent confirms approval. - Processing time varies by case — our billing team can give you an estimated timeline once a refund is approved. - The refund amount is calculated based on the duration of the disruption and your current subscription plan. - Refunds are returned to the original payment method on file. If a refund was promised in a prior conversation — for example, by a support teammate on August 11 — and you have not seen it reflected in your account or bank statement after a reasonable amount of time, this may indicate a processing delay or an administrative oversight that needs to be reviewed. 📋 What Information to Have Ready Before contacting support, gather the following so the team can locate your case and act quickly: - The date of your original support conversation (e.g., August 11) and the name of the agent who approved the refund - The specific pages or projects where the alt text issue is still occurring - Your account email address and current subscription plan - Any screenshots or notes from previous conversations confirming the promised resolution and refund 🚀 Next Steps If your alt text issue remains unresolved after following the verification steps above, or if your promised refund has not arrived within the timeframe you were given, please reach out to us directly so we can investigate and prioritise your case. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you connect, mention that you have an unresolved bug escalation and a pending prorated refund so the agent can immediately pull up the relevant case history and escalate to billing if needed.

🛠️ Fix Schema Failures, Billing & Refund Issues

Overview This article covers three common issues that sometimes occur together: schema markup failing to deploy, charges appearing after a subscription cancellation, and how to request a refund for disputed invoices. Read through the relevant section below to understand your situation and take the right next step. Schema Deployment Failures Schema deployment can fail for several reasons. Common causes include: - OTTO SEO not activated on the site: Schema deployment requires OTTO SEO to be active on the target domain. Verify that OTTO SEO is enabled for your site before attempting to deploy schema. - Google Search Console not connected: OTTO SEO requires a verified Google Search Console connection. Check that your GSC account is properly linked and shows no errors. - Conflicting schema on the page: If duplicate schema already exists in your site theme or another plugin, OTTO may detect a conflict and pause deployment. Remove or disable the conflicting schema source and retry. - Inactive or paused subscription: Schema deployment is a paid feature. If your subscription has lapsed, deployments may not publish until your plan is reactivated. - Unsupported schema type for the page: Certain schema types require specific page attributes. Make sure the page content matches the schema type you have selected. After addressing the relevant cause above, retry the schema deployment from within the OTTO SEO tool. If the issue persists, please reach out to our support team with your site URL, the schema type you are trying to deploy, and a description of the error you are seeing. Charged After Canceling Your Subscription If you see a charge after canceling, consider the following: - Cancellation timing: Search Atlas bills at the start of each billing cycle. If you canceled after your renewal date, the charge for that cycle may have already processed. Cancellation stops future renewals — it does not automatically reverse a charge that has already been made. - Cancellation may not have completed: A cancellation is only confirmed when you receive a confirmation email from Search Atlas. If you did not receive one, your subscription may still be active. Log in to your account and check your subscription status. - Multiple workspaces or add-ons: If your account includes additional workspaces or add-ons, these may generate separate charges. Review your invoices in your account billing section to identify which item generated the charge. If you believe you were charged in error, gather the relevant invoice details (invoice number, charge date, and amount) and contact our support team to open a refund dispute. Requesting a Refund for a Disputed Invoice If you would like to dispute a charge or request a refund, gather your invoice number, charge date, and the amount in question before reaching out. Our support team will review the details and advise on next steps in line with our refund policy. If you need further assistance, open 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 Issues Before Cancelling Your Subscription

🔍 Understanding the Problem If you believe Search Atlas is causing issues on your website — such as broken layouts, slow load times, or script conflicts — there are several quick steps you can take to identify and fix the problem before cancelling your subscription. In most cases, technical conflicts can be resolved without losing access to your SEO tools and data. ⚙️ Step 1: Isolate the Issue Before assuming Search Atlas is the root cause, rule out other variables: - Check recent changes: Did the issue start after installing a plugin, updating a theme, or making code changes on your site? - Test in a different browser: Open your site in an incognito window or a different browser to rule out cache or extension conflicts. - Disable other plugins temporarily: If you run WordPress or a similar CMS, deactivate other plugins one at a time to identify any conflict. - Clear your site cache: A stale cache can cause display issues unrelated to Search Atlas. 🤖 Step 2: Review Your OTTO SEO Settings If you are using the OTTO SEO automation feature, some on-page optimisations or injected code may interact with your site's existing structure. To review or pause OTTO's activity: 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 OTTO SEO panel and toggle off any active automations you want to pause. 4. Reload your website and check whether the issue persists. Pausing OTTO SEO automations does not cancel your subscription — it simply stops automated changes from being applied to your site while you investigate. 🔗 Step 3: Check Tracking Scripts and Integrations Search Atlas may use lightweight tracking scripts to gather analytics. If these conflict with another tool on your site: - Check your website's header and footer for duplicate or conflicting scripts from other SEO or analytics tools. - If you added a Search Atlas tracking pixel or code snippet manually, verify it was placed correctly and is not duplicated. - Use a tool like Google PageSpeed Insights or your browser's developer console to identify specific script errors. 💾 Step 4: Back Up Your Data Before Any Action If you are considering cancellation, keep in mind that cancelling your subscription will remove access to your projects, keyword data, reports, and SEO history. Before taking any action: - Export any reports or keyword lists you want to keep. - Take screenshots or download CSVs of important campaign data. - Note any OTTO SEO changes applied to your site so you can review or revert them manually if needed. 🚀 Step 5: Get Help from the Support Team Our support team can investigate technical conflicts with you directly and help find a solution — often much faster than starting over with a new tool. Many site-breaking issues reported by customers have been resolved without any subscription changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please share: - A description of the issue and when it started. - Your website URL and CMS platform (e.g. WordPress, Shopify). - Any error messages or console errors you have seen. - A list of other plugins or tools currently active on your site. ❌ If You Still Need to Cancel If you have followed the steps above and still wish to cancel, you can manage your subscription from your account settings. Go to your account profile in the top-right corner, select Billing, and follow the cancellation steps. Please note that cancellations take effect at the end of your current billing period and data cannot be recovered afterwards.

🛠️ Cancel OTTO Site Top-Ups After Plan Upgrade

🔍 Overview After upgrading your Search Atlas plan, you may find that you are unable to cancel an existing OTTO site top-up. The platform may display your services incorrectly, show the top-up as still active, or return an error when you attempt to remove it. This article explains why this happens and the steps you should take to resolve it. ⚙️ Why This Happens OTTO site top-ups are billing add-ons tied to your subscription in our payment system. When you upgrade your plan, your underlying subscription record changes. In some cases, this causes a mismatch between what the platform displays and what exists in the billing system. Common symptoms include: - The cancel button for a top-up is missing or unresponsive. - A top-up still appears as active even after you attempted to remove it. - You continue to be charged for a top-up that should have been cancelled. - The platform does not reflect your current services accurately after the upgrade. 🚀 What to Try First 1. Refresh your browser and navigate back to OTTO SEO → All Sites (SEO Automation) via the left sidebar (or go to /seo-automation-v3). Sometimes a stale session causes display issues. 2. Log out and log back in to force your account data to reload with your updated plan details. 3. Revisit your billing or add-ons section and attempt the cancellation again. After a plan upgrade, it can take a few moments for the system to sync correctly. ⚠️ When Self-Service Cancellation Is Not Available If the steps above do not resolve the issue, the top-up cancellation likely requires a manual fix on the billing side. This is a known limitation that occurs when: - The top-up's internal billing reference was not carried over correctly during the plan upgrade. - The top-up is linked to a previous subscription record that no longer exists in the payment system. - A cancellation flag was set but the charge was not stopped on the payment processor's side. In these situations, you cannot complete the cancellation yourself and you will not be charged incorrectly — our team will correct the billing record and ensure no further charges are applied for the cancelled top-up. 💡 How to Get This Fixed Our support team can manually remove the top-up from your billing subscription and confirm that no further charges will be made. To get help quickly, please have the following information ready before contacting us: - The date you upgraded your plan. - The number of OTTO site top-ups you expected to cancel. - Any error message you saw when attempting to cancel. - A screenshot of your current OTTO SEO page if the services are displaying incorrectly. If you need further assistance, open 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 Cache Issues Refund Process

🔧 Understanding OTTO Cache Problems OTTO SEO automation can sometimes serve stale cached SEO data due to Cache-Control header issues. This has been documented in engineering tickets where Cache-Control: private headers prevented host/CDN caching, causing CPU spikes and 30-second first-load times. Subsequent fixes addressed Cache-Control: public headers breaking forms and leaking nonces on non-WP-Rocket sites. These cache issues can lead to significant traffic and crawl distribution drops. 📋 Refund Eligibility and Process Refund requests for OTTO cache-related issues are evaluated case by case. While the Terms of Service mention a 72-hour window, exceptions have been granted for documented technical issues caused by platform bugs. The human support team has successfully processed refunds for customers experiencing verified OTTO cache problems that resulted in traffic loss. If you believe you qualify for a refund due to OTTO stale cache issues: 1. Document the timeline of traffic drops and correlation with OTTO activation 2. Gather evidence from Google Search Console or analytics showing crawl distribution decline 3. Note any engineering ticket references related to OTTO cache fixes 4. Contact support through the platform chat widget 💰 Refund Details from Recent Case In a recent resolved case, a customer received a refund of $341.58 to their original payment method. The refund typically reflects within 5–10 business days. This refund was granted after escalation despite initial denial based on the 72-hour ToS window. 🛑 How to Cancel Your Subscription To cancel your subscription and stop future billing: 1. Navigate to Left sidebar → OTTO SEO → All Sites 2. Click on the affected site 3. Go to billing/account settings within the site configuration 4. Follow the cancellation prompts Alternatively, you can manage billing directly through your account settings in the platform. 🔧 OTTO Cache Fixes and Prevention Engineering has deployed several fixes for OTTO cache issues: - Configurable OTTO cache TTL setting under Advanced Settings → Cache Management - OTTO SEO Cache Self-Verification Probe for connectivity resilience - Cache Health Visibility improvements - Fixes for WordPress plugin causing site outages across multiple client websites To access cache management settings: 1. Go to Left sidebar → OTTO SEO → Installation Guide 2. Check Advanced Settings for Cache Management options 3. Adjust OTTO cache TTL as needed for your hosting environment 📞 Getting Further Help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

💸 Refund Requests for OTTO PPC Add-On Errors

📋 Overview We understand how frustrating it can be when an add-on doesn't perform as expected. This article explains Search Atlas's refund policy for the OTTO PPC / Google Ads Add-on, what qualifies for a billing review, and the steps to take if you believe you were charged in error. 🗓️ Understanding the Refund Policy Window Refund requests for add-on charges, including the OTTO PPC / Google Ads Add-on, follow a short standard policy window. This means: - Refund requests must be submitted within 48 hours of the original charge date (72 hours for annual-plan charges). - Requests submitted after this window are considered outside policy and are not automatically eligible for a refund. - Charges from previous billing cycles — for example, a charge from May reviewed in July — fall outside the standard policy window. We set this window to ensure billing disputes are handled promptly and accurately, while keeping our records and reconciliation process manageable for all customers. ⚠️ What Counts as an OTTO PPC Error? Not every unexpected result from the OTTO PPC Add-on qualifies as a billing error. A qualifying error typically involves one or more of the following: - The add-on was charged but never activated or applied to your account. - A verified platform bug caused the add-on to malfunction during the billing period in question. - Duplicate charges occurred for the same billing cycle. The following situations are generally not considered billing errors: - Campaign performance that did not meet your expectations. - Google Ads spend that exceeded your anticipated budget (this is controlled within Google Ads, not Search Atlas). - Misconfigurations set by the user rather than a platform fault. 🔍 How to Check Your OTTO PPC Activity Before submitting a refund request, review your OTTO PPC usage to gather supporting details. Follow these steps: 1. Log in to your Search Atlas account. 2. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 3. Locate the OTTO PPC section and review the activity log for the billing period in question. 4. Take note of any specific errors, actions taken, or anomalies you observed during that time. Having this information ready will help our team assess your case more quickly. 📝 How to Submit a Refund Review Request Even if your request falls outside the standard 48-hour window, you can still ask our team to review your case. We evaluate out-of-policy requests on a case-by-case basis, particularly when there is clear evidence of a platform error. 1. Gather your billing details: the charge date, invoice number, and a description of the errors you experienced. 2. Include any screenshots or evidence of the OTTO PPC errors from the relevant billing period. 3. Open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. 4. Share your case details clearly, specifying the charge date and what went wrong. Our team will review the information provided and respond with a decision. Please note that out-of-policy refunds are not guaranteed and are approved at the discretion of our billing team based on the evidence presented. 💡 Tips to Avoid Future Billing Issues - Review add-on charges promptly — check your invoices each month so any discrepancies are caught within the 30-day window. - Monitor OTTO PPC activity regularly — log in to OTTO SEO V3 to confirm the add-on is functioning as expected after each billing cycle. - Report issues immediately — if you notice an error, contact support right away rather than waiting until the next billing period. 🙋 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix 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 <head> 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 48 hours of the original payment for monthly and quarterly plans, or within 72 hours for annual plans. Requests made outside this window are outside our standard refund policy and cannot be processed as standard refunds. - Payments outside the refund window: If your refund request falls outside the window for your plan — 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.

💵 Understanding Partial Refunds for Failed Press Releases

If you paid for a Swedish press release distribution and received only a partial refund after the publication failed, the refund requires review to confirm what happened and whether the amount is correct. 💡 Why You May Have Received a Partial Refund A failed Swedish press release may result in a partial refund rather than a full refund. The available information does not confirm the exact calculation or which parts of the distribution were affected, so support must review the specific release and order. 🔍 What to Prepare for a Refund Review To help the team investigate your partial refund, have the following information ready: - The press release title - Your order ID, if available - The date the release was submitted - The partial refund amount you received - Any error message or failure details shown when the release failed Include these details when requesting a review so the team can check the failed Swedish press release and confirm the refund. 💳 Refund Review The exact refund amount and any available next steps depend on the details of your order. Support can review whether the partial refund was applied correctly and explain the outcome for the failed release. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Cancel OTTO Sites Add-On and Fix Billing Sync

🔍 Overview If you have purchased additional OTTO site slots (also called OTTO Sites add-ons) and want to stop them from renewing, you can request a cancellation through the platform. Some customers experience an error or see no change after attempting to cancel — this article explains why that happens and what to do next. 📋 Before You Begin - OTTO Sites add-ons are billed as separate child subscriptions under your main Search Atlas plan. - Cancellation stops the add-on from renewing at the next billing date. Your existing OTTO site activations remain available until the end of the current paid period. - Cancelling the add-on does not automatically deactivate any sites already using those slots — you must freeze or deactivate those sites separately if needed. ⚙️ How to Cancel Your OTTO Sites Add-On 1. Log in to Search Atlas and navigate to your Billing settings, accessible from your Avatar Menu (👤). 2. Locate the OTTO Sites add-on under your active subscriptions or add-ons section. 3. Use the cancellation option available for the OTTO Sites line item to initiate the cancellation. 4. After submitting your cancellation request, refresh the page to verify the add-on status has updated. If it still shows as active after refreshing, see the troubleshooting section below. 🚨 Common Issue: Cancellation Appears Successful but Doesn't Take Effect Some customers complete the cancellation steps but after refreshing the page the add-on still shows as active. This is a known Stripe billing sync issue where the cancellation signal between Search Atlas and Stripe does not complete correctly. What causes this? Your OTTO Sites add-on is managed as a child subscription in Stripe. In some cases, a temporary sync delay or a billing event can prevent the cancellation from being fully registered, causing the billing interface to appear unresponsive or to revert the cancellation. 🔧 What to Do If Cancellation Does Not Take Effect Because this issue involves a Stripe billing sync problem at the backend level, it cannot be fully resolved through self-serve steps alone. If your OTTO Sites add-on continues to show as active after you have submitted your cancellation request, you will need to contact our support team to have the cancellation and sync corrected manually. To help our team resolve this as quickly as possible, please have the following ready when you reach out: - Your Search Atlas account email address - The name of the OTTO Sites add-on or subscription you are trying to cancel - The approximate date and time you attempted the cancellation - A description of what you see in your billing settings (e.g., whether the add-on still shows as active or renewing) If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ What to Do When Cancel Option Is Missing

🔍 Overview If you want to cancel your Search Atlas subscription but cannot find a cancel link or button, you are not alone. In most cases the option is hidden for a simple reason, such as your user role or how the subscription was purchased. This article explains the common causes and what to do next. ❓ Why the Cancel Option May Be Missing - You are not the account owner or admin. Billing controls are usually available only to the person who owns the account or has admin permissions. - You are logged in to a different account. If you have more than one email address or workspace, you may be viewing an account that is not the one being billed. - The subscription is already cancelled or set to end. If a cancellation is already scheduled, the cancel option may no longer be shown. - The plan was set up outside the standard checkout. Custom, agency, or specially arranged plans may be managed differently from standard subscriptions. - You are on a free trial or a plan with no active payment. There may be nothing to cancel if no paid subscription is active. - A temporary display issue. A cached page or browser extension can sometimes hide buttons. ✅ Quick Checks to Try First 1. Log out, then log back in using the email address that was used to sign up and pay for the plan. 2. Open your account settings and look for the billing or subscription section. 3. Check whether your role is Owner or Admin. If you are a team member, ask the account owner to review the billing section. 4. Look for a notice showing that your plan is already set to cancel or end on a certain date. 5. Refresh the page, or try a different browser or an incognito window. Disable ad blockers or extensions that may hide page elements. 6. Check your inbox for past receipts or confirmation emails to confirm which account and email address are linked to the subscription. 🧾 Information to Have Ready If the cancel option is still missing, having the details below ready helps our team resolve your request faster: - The email address on the account you want to cancel - The name of your plan, if you know it - The approximate date of your last payment - A short description or screenshot of what you see on the billing page 💬 Getting Help From Our Team If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Please state clearly in your message that you want to cancel your subscription. This lets the team start on the right request straight away. 💡 Helpful Tips - Request cancellation before your next renewal date to help avoid another billing cycle. Your renewal date is usually shown on the billing page or in your receipts. - Keep any confirmation message you receive after cancelling so you have a record. - If you only want to pause or change your plan, mention that in the chat. There may be a better option than cancelling. - If you manage several accounts, confirm which one you want to cancel so the correct one is updated. 📌 Summary A missing cancel option is most often caused by account permissions, being logged in to the wrong account, or a subscription that is already ending. Run through the quick checks above, and if the option still does not appear, our team can help you directly through the chat widget.

⚙️ Fix Stuck Plan Changes and Cancellations

🔍 What this article covers Use these steps if a plan change remains stuck or if you need to cancel your Search Atlas subscription. 💳 Change your plan Open your Search Atlas subscription or billing settings and follow the available instructions to select a different plan. If the plan change remains stuck or the page keeps spinning, do not repeatedly submit the request. 🚫 Cancel your subscription Open your Search Atlas subscription or billing settings and follow the available cancellation instructions. Review any confirmation or billing status shown after completing the cancellation. If confirmation is missing, do not assume the cancellation was completed. 📋 Before contacting support Have the following details ready: the account email or workspace name, the action you attempted, the approximate time it happened, your browser, and a screenshot of the spinning page if available. Do not share payment details or passwords. 💬 Get help from our team If the page still spins, your plan does not change, or cancellation confirmation is missing. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🎓 How to Locate and Access Search Atlas Academy Training Content

Search Atlas Academy is your built-in training hub, offering courses, certifications, and walkthroughs to help you get the most out of the platform. If you are struggling to find the Academy or clicking a training link that does not load correctly, this guide will walk you through the correct navigation path and common fixes. 📍 Where to Find the Academy The Academy is accessible directly from your Search Atlas dashboard. To locate it: - Log in to your Search Atlas account. - From the left sidebar, click Home to land on your main dashboard at /home. - Click the More Features apps-grid icon in the header (not on the Home screen) to open it. - Within More Features, you will find the link to Search Atlas Academy, along with certification tracks and course modules. If you do not see the More Features icon, try refreshing your browser or clearing your cache, as dashboard layouts are updated periodically and a stale cache can hide newer navigation elements. 🔗 Why Provided Links or Instructions May Not Work Several factors can cause Academy links to fail or redirect incorrectly: - White-labeled environments: If you access Search Atlas through a reseller platform (such as a white-label plugin, GoHighLevel, or Vendasta), some Academy or help links may point to pages still showing Search Atlas branding instead of your agency's branding, or may not resolve at all. This is a known issue our team actively monitors and resolves as it is reported. - Outdated bookmarks: Direct links shared in older emails, PDFs, or third-party guides may no longer match the current URL structure after platform updates. - Browser session issues: Being logged out, using incognito mode, or having conflicting extensions can prevent Academy pages from loading properly, especially for embedded or white-labeled app users. - Plugin version conflicts: If you access Search Atlas through a WordPress white label plugin, an outdated plugin version can block access to certain settings and linked resources, including training content. 🛠️ Troubleshooting Steps 1. Always navigate to the Academy through the More Features apps-grid icon in the header rather than relying on external or bookmarked links. 2. Clear your browser cache and cookies, then log in again using a standard (non-incognito) browser window. 3. If you access Search Atlas through a white-label plugin, confirm you are running the latest plugin version, as older versions may restrict access to settings and linked content. 4. If you are a reseller or agency customer accessing Search Atlas through a third-party platform (Vendasta, GoHighLevel, etc.), try logging in directly through the native Search Atlas dashboard to confirm whether the issue is specific to the embedded environment. 5. Disable browser extensions temporarily, as ad blockers or privacy tools can sometimes interfere with embedded training content. 📚 Certification and Course Access If you are working toward a Search Atlas certification, all modules and progress tracking are managed within the Academy itself, accessed via the More Features apps-grid icon in the header. If your certification progress does not appear to save or your completed modules are not reflecting correctly, this may be part of an ongoing audit and improvement process our team is actively working through. 💬 Need More Help? If you have followed these steps and still cannot locate or access Search Atlas Academy content, our team can investigate your specific account and environment. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 How to Handle Broken Training Course Links

🔍 What This Article Covers If you or your clients have clicked a link to a Search Atlas Academy course post — such as a lesson inside the AI SEO Client Acquisition System — and received an error or blank page, this article explains why that can happen and what steps to take. ⚠️ Why a Course Link May Appear Broken - The lesson is temporarily unavailable while content is being updated or republished. - The URL has changed because the course structure was reorganised. - Access permissions have not yet been granted for your account or your client's account. - A cached or old link was shared before a course was restructured. ✅ Steps to Take When a Link Is Broken 1. Refresh the page and try the link again — temporary loading issues often resolve on their own. 2. Log out and log back in to your Search Atlas account, then retry the link. 3. Navigate directly to the Academy by visiting discover.searchatlas.com and browsing to the relevant course category manually. 4. Check that your account has access to the specific course or programme. Some content is tied to specific plan tiers or purchases. 5. Try a different browser or device to rule out a local caching or browser extension issue. 📋 If You Are Sharing Links with Clients When sending Academy course links to clients, keep the following in mind: - Always confirm the link works from your own account before sharing it with a client. - Encourage clients to access content by logging into their own account at discover.searchatlas.com and navigating to the course directly, rather than relying solely on a direct URL. - If a specific lesson has moved or been updated, direct your client to the course homepage and guide them to the correct module from there. 🛠️ Reporting a Broken Link to the Search Atlas Team If you have followed the steps above and the link is still not working, it is important to report it so the team can investigate and fix the issue promptly. When you reach out, please include: - The full URL of the broken link. - The name of the course or lesson you are trying to access. - A brief description of what you see when you open the link (error message, blank page, redirect, etc.). - Whether the issue affects one user or multiple users. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

🛠️ Fix OTTO SEO Pixel Installation on Shopify

🔍 Overview The OTTO SEO Pixel must be active on your Shopify store before the Site Auditor can verify your connection and begin automating SEO improvements. If the auditor still shows the pixel as not installed after you have followed the standard steps, this guide will help you identify and fix the most common causes. ⚙️ How the OTTO SEO Pixel Works on Shopify The pixel is a small JavaScript snippet that Search Atlas injects into your storefront. It allows OTTO SEO to read page data, confirm site ownership, and apply on-page optimizations. Shopify has specific theme and permission requirements that can prevent the snippet from loading correctly if any step is missed. ✅ Pre-Installation Checklist Before reinstalling, confirm the following: - Active theme: You are editing the theme that is currently live and published — not a duplicate or unpublished theme. - Staff permissions: Your Shopify account has Themes edit permissions. Ask the store owner to verify if you are unsure. - Script access: Your Shopify plan supports custom script injection. The Starter plan does not support code edits to theme files on all storefronts — confirm your plan level. - No duplicate snippet: The pixel code has not already been pasted more than once into your theme, which can cause a conflict. 🚀 Step-by-Step Pixel Installation 1. In Search Atlas, navigate to OTTO SEO in the left sidebar, then open SEO Automation (URL: /seo-automation-v3). 2. Select your Shopify project and open the OTTO SEO panel. 3. Click Get Pixel Code and copy the full snippet to your clipboard. 4. Log in to your Shopify admin and go to Online Store → Themes. 5. Next to your live theme, click Actions → Edit code. 6. In the file tree on the left, open Layout → theme.liquid. 7. Paste the pixel snippet immediately before the closing </head> tag. 8. Click Save in the top-right corner of the code editor. 9. Return to Search Atlas and click Verify Installation in the OTTO SEO panel. 🔎 Troubleshooting: Pixel Still Not Detected If the Site Auditor still shows the pixel as uninstalled after completing the steps above, work through the following checks: - Wrong theme file edited: Shopify stores sometimes have multiple themes. Confirm you edited theme.liquid inside the currently published theme, not a backup or development theme. - Snippet placed in wrong location: The code must appear inside the <head> section, just before </head>. Placing it after </body> or at the very bottom of the file will cause detection to fail. - Save not applied: Shopify occasionally logs you out mid-session. Re-open theme.liquid and check that the snippet is still present — if it is missing, paste it again and save. - Content Security Policy (CSP) blocking the script: Some third-party security or performance apps add strict CSP headers. Temporarily disable any such apps and click Verify Installation again to test. - Caching layer active: If you use a CDN (such as Cloudflare) in front of your Shopify store, purge the cache after installation so the updated theme.liquid is served to the verification crawler. - Headless or custom Shopify setup: If your storefront uses a headless framework (Hydrogen, Next.js, etc.), the standard theme.liquid method does not apply. The pixel must be added to the root HTML template of your frontend application instead. 💡 After a Successful Installation Once Search Atlas confirms the pixel is active, the Site Auditor status will update to Connected. OTTO SEO can then crawl your pages and begin applying automated optimizations. Allow up to 15 minutes for the status to refresh after a successful verification. 🆘 Still Need Help? If you have followed every step above and the pixel is still not being detected, our team can review your specific Shopify 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.

⚡ OTTO WordPress Installation and 'Not Found' Fix

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

🔍 Otto Pixel: Understanding 'Not Installed' During Audit

🧩 Overview After installing the Otto pixel plugin on your WordPress site, you may notice that Otto still displays a "Pixel Not Installed" message. This is expected behavior and does not mean something went wrong. This article explains why this message appears and what happens next. ⚙️ Why Otto Shows 'Pixel Not Installed' When you first connect your site to Otto, the platform automatically checks whether the pixel is installed on a schedule based on the 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, after which automatic checks stop. A correctly installed pixel on a new project is normally detected within about 15 minutes. Until the next scheduled check runs, Otto may still display "Pixel Not Installed" as a temporary placeholder status. This is a normal part of the setup workflow, not an error. ✅ What You Should Do Right Now 1. Confirm the plugin is installed and active. In your WordPress dashboard, go to Plugins → Installed Plugins and verify the Otto pixel plugin is listed and has the status Active. 2. Confirm the plugin is connected to the correct site. Make sure the API key or site URL inside the plugin settings matches the property you added in Search Atlas. 3. Do nothing further — wait for the next automatic check. On a new project this is typically within about 15 minutes. Otto will automatically update the pixel status. No manual refresh or reinstallation is needed. 🔎 How to Check Your Pixel Status 1. In the left sidebar, click OTTO SEO, then open SEO Automation to access the Otto dashboard. 2. Locate your connected site and review the pixel status indicator. 3. If the automatic check has run and the pixel was detected successfully, the status will update to Pixel Installed. 4. If the status still shows "Pixel Not Installed" well beyond the expected check interval, proceed to the troubleshooting steps below. 🛠️ Troubleshooting: Still Not Installed If the pixel has not been detected after the expected automatic check, check the following common causes: - Plugin deactivated or deleted: Return to Plugins → Installed Plugins in WordPress and confirm the Otto plugin is still active. - Caching plugin interference: A caching plugin may be serving old page versions that do not include the pixel code. Clear your site cache and any CDN cache, then allow a few hours for Otto to re-crawl. - Theme or page builder conflicts: Some themes or page builders prevent scripts from loading in the expected location. Try deactivating other plugins temporarily to identify a conflict. - Incorrect API key: Open the Otto plugin settings in WordPress and verify the API key matches the one shown in your Search Atlas account. - Site not publicly accessible: Otto's crawler cannot scan password-protected, maintenance-mode, or staging sites. Ensure your site is publicly reachable. 📋 Quick-Reference Summary - The "Pixel Not Installed" message right after setup is normal and temporary. - Automatic pixel checks run every 15 minutes for projects under 2 hours old, every hour from 2 to 24 hours, every 6 hours from 1 to 7 days, and stop after 7 days. - A correctly installed pixel on a new project is normally detected within about 15 minutes. - Use the troubleshooting checklist above if the status has not updated as expected. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔌 Fix WordPress OTTO Connection and Authentication Issues

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

🔧 Fix Missing Domains in Your Golden Loops Workbook

Overview If one or more domains are missing from your Golden Loops workbook — for example, they do not appear in your domain list or you cannot run reports for them — this is typically a backend configuration issue that requires our team to investigate and resolve on your behalf. What This Means Missing domains in a Golden Loops workbook are not always something you can fix through the platform interface alone. In many cases, the root cause involves how domains are configured or associated with your workbook on the backend. Our support team will need to look into your specific account setup to identify and correct the problem. What to Expect Once you reach out, a member of our team will review your account, identify why the domains are not appearing in your workbook, and make the necessary backend adjustments. You do not need to attempt to reconfigure your workbook manually before contacting us. What to Have Ready When You Escalate To help our team resolve this as quickly as possible — especially if you are working against a deadline — please have the following information ready when you contact us: - Your account email address — the email associated with your Search Atlas account. - The exact domain URLs that are missing — for example, seoraleigh.net. List every domain that should appear but does not. - The name of the specific workbook where the domains are missing. - Any deadline or urgency context — let us know if you have a time-sensitive client deliverable so we can prioritize accordingly. - Any error messages or unexpected behavior — describe exactly what you see (or do not see) when you access the workbook. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

⚡ OTTO Pixel Setup via Google Tag Manager Troubleshooting

Overview Setting up the OTTO Pixel through Google Tag Manager (GTM) is a common workflow for connecting your site to OTTO in Search Atlas. If you are experiencing issues with the pixel not being detected or seeing an OTTO not found status, this article explains what to prepare and how to escalate so our team can help you resolve it quickly. What Is the OTTO Pixel and Why Use GTM? The OTTO Pixel allows Search Atlas to verify that OTTO is active on your website. Google Tag Manager is a supported installation method that lets you deploy the pixel without editing your site's code directly. Each Search Atlas project generates its own unique pixel code, so the correct code must be installed for the correct project. Common Causes of OTTO Pixel Connection Issues - GTM container not published: Adding a tag in GTM and saving it is not enough — the container must be submitted and published before any tags will fire on your live site. - Wrong project code installed: Each project has a unique pixel code. Using a code from a different project will prevent OTTO from detecting the connection. - Duplicate or conflicting pixel installations: If the OTTO Pixel was previously added manually to your site's theme or a plugin, this can conflict with the GTM-based installation. Only one installation method should be active at a time. - Tag not triggering correctly: The GTM tag must be configured with an appropriate trigger (such as All Pages) to fire on your website. Use GTM's Preview mode to verify the tag is firing as expected. - GSC integration not connected: If you are also experiencing issues with Google Search Console integration alongside the pixel, both may need to be verified or reconnected from within your project settings. What to Have Ready When Contacting Support Because OTTO Pixel issues often require our team to inspect your project configuration directly, please have the following information ready before reaching out: - Your Search Atlas project name and the domain it is associated with - The specific error message or status you are seeing (e.g., OTTO not found) - Whether you are using GTM or another installation method - Whether the GTM container has been published after adding the OTTO tag - Any screenshots of your GTM tag configuration or the OTTO Pixel section in your project - Whether a previous manual pixel installation may still be present on the 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.

Install and Troubleshoot the OTTO Pixel on Wix

Overview The OTTO pixel allows Search Atlas to track your site's performance and power AI-driven SEO automation. Installing it on Wix requires a different process than WordPress or other CMS platforms. This article outlines the general approach for getting the pixel installed on a Wix site so you can get it firing correctly. Before You Begin - You must have Editor or Owner access to your Wix site. - You need your OTTO pixel code snippet, which you can copy from within your Search Atlas account under the OTTO or OTTO SEO section. - Make sure your Wix site is published after installation — unpublished changes will not fire the pixel on the live site. How to Install the OTTO Pixel on Wix 1. Log in to your Wix account and open your site dashboard. 2. Locate the section of your Wix dashboard that allows you to add custom or third-party code to your site. The exact location and label of this section may vary depending on your Wix plan and version — consult the Wix Help Center if you are unsure where to find it. 3. Create a new custom code entry. 4. Paste your OTTO pixel code snippet into the code field. 5. Give the entry a recognisable name, such as OTTO Pixel - Search Atlas. 6. Configure the code to load on all pages and to be placed in the head section of the page, if your Wix plan supports these options. 7. Save your changes. 8. Publish your site to push the changes to your live URL. How to Verify the Pixel Is Firing After publishing, confirm the pixel is active by visiting your live site URL in a browser (not an editor preview mode) and checking that the pixel code is present in the page source. The pixel will not fire in editor preview modes — always verify on your published, live site URL. Common Issues - Pixel not detected after saving: Confirm you have published the site after saving the custom code. Changes are not live until the site is republished. - Code added but not appearing in the page source: Check that the code was saved correctly and configured to apply to all pages. Re-open the custom code entry to verify the snippet is still present and was not lost during saving. - Wix plan limitations: Some Wix plans restrict the ability to add custom code. If you do not see an option to add custom code, you may need to upgrade your Wix plan. Check the Wix Help Center for details on which plans support custom code injection. Need Help? If you are unable to locate the correct section in your Wix dashboard, or if the pixel is still not firing after following the steps above, our support team can assist you. When reaching out, please have the following ready: your Search Atlas project name, your live site URL, a description of where in Wix you attempted to add the code, and any error messages or unexpected behaviour you observed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.