Troubleshooting: Titles, Meta & Headings

🔄 Refresh OTTO SEO Audit After Fixing H1 Errors

🛠️ Fix OTTO Pages With Missing Images and Formatting

🛠️ Delete OTTO Recommendations and Fix Article Titles

🗑️ How to Delete OTTO Recommendations If OTTO has generated title tag recommendations that are incorrect or that you do not want, you can remove them directly from the OTTO SEO dashboard. Deleted recommendations are removed from your task queue and will never be deployed to your site. 1. In the left sidebar, click OTTO SEO. 2. Scroll to the recommendations list and locate the title tag recommendation you want to remove. Use the filters to narrow the list by page URL or recommendation type. 3. Click the three-dot menu next to the recommendation. 4. Select Delete and confirm when prompted. To remove several recommendations at once, tick the checkbox beside each item, choose the bulk Delete action, and confirm. Deleting a recommendation never changes anything on your live site — it only clears the suggestion from OTTO. 💡 Why OTTO Suggests Title Changes You Already Made Sometimes OTTO recommends a new title tag even though you already updated the title yourself. These are called no-op recommendations — suggestions that would not actually change your page, because your current title already matches, or closely resembles, what OTTO is proposing. This typically happens when OTTO based its analysis on an earlier crawl of your site, before your manual edit went live. We are actively shipping an update so OTTO can tell the difference between a manual title edit and a genuine optimization opportunity. Until that update reaches your account, use this workaround: - Delete the no-op recommendation using the steps above. - Trigger a fresh crawl by going to OTTO SEO → Site Audit → Crawl Monitoring so OTTO picks up your current titles. - After the crawl completes, review any remaining recommendations and delete the ones that duplicate your manual edits. ✏️ Keeping Your Article Titles Exactly as You Set Them If you specified a title and Search Atlas appears to have invented a different one, the cause is almost always one of the following: - The SEO title field overrides the headline. The title tag used in search results comes from the SEO title field, not the article headline. If that field is left blank, the platform may auto-generate a title. - An OTTO title recommendation was deployed before your manual edit, overwriting your intended title. - The sync missed your latest save. See the next section for how to fix this. To lock in your preferred title: 1. In the left sidebar, click Content and open your article. 2. Open the article SEO settings and type your exact title into the SEO title field. Never leave this field blank. 3. Delete any pending OTTO title recommendation for that URL so it cannot overwrite your title when deployed. 4. Save the article, then re-sync it with your site. 🔄 Fixing Titles That Look Outdated After Syncing On WordPress sites, titles and meta descriptions are copied into Search Atlas by an asynchronous sync. Occasionally a sync misses a recent save, so the platform keeps displaying the old title even though the correct one is live on your site. 1. Open the article in Content, click Save again, and trigger a manual re-sync. 2. Run a fresh crawl under OTTO SEO → Site Audit → Crawl Monitoring. 3. Check the page in OTTO SEO → Site Audit → Page Explorer to confirm the fetched title now matches your live page. 4. If OTTO still shows the old version, delete the stale recommendation and reach out to support so we can force a refresh on our side. 🚫 Preventing Unwanted Title Recommendations - Always fill in the SEO title field for every article so OTTO has nothing to auto-generate. - Finish your title edits before running a crawl, so OTTO analyzes your final version. - Delete recommendations you disagree with — OTTO will not re-suggest a deleted recommendation for the same page unless the page changes significantly. - Re-crawl after bulk title updates so recommendation data stays current. 💬 Still Need Help? Our team can delete recommendation sets in bulk for you and investigate any title that refuses to sync. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛍️ Stop Shopify Product Title Overwrites

🔎 Identify the source of the overwrite If a Shopify product title changes after the page loads, the cause may be an active Atlas Brain deployment rather than a CMS Connector setting. Atlas Brain can apply changes to the live page after Shopify initially renders it. 1. Open the affected product in Shopify and note the original title. 2. Reload the product page and confirm whether the title changes after loading. 3. In Search Atlas, review the product’s Atlas Brain deployments or recommendations. 4. Check whether a deployment is active for the affected page, product, collection, or Shopify connection. 🛑 Undeploy Atlas Brain changes To stop the title overwrite, remove the active deployment that is applying the title change. 1. Open the Atlas Brain area in Search Atlas. 2. Locate the deployment affecting the Shopify product or connected site. 3. Open the deployment actions menu. 4. Select Undeploy, Remove deployment, or the equivalent rollback option shown in your account. 5. Confirm the action and wait for the deployment status to show that it is no longer active. Undeploying stops Atlas Brain from continuing to apply the deployed title change. It does not necessarily restore the previous Shopify title automatically. ✏️ Restore the correct Shopify title 1. In Shopify, open the affected product. 2. Enter the title you want customers to see. 3. Save the product. 4. Clear any applicable cache, then open the product page in a private browser window. 5. Reload the page and confirm the title remains unchanged after page load. 🔗 Check CMS Connector activity If the title still changes after Atlas Brain is undeployed, review recent CMS Connector activity for the product. Look for a sync or update that writes product titles to Shopify. Confirm that the connected Search Atlas content contains the intended title and that no active workflow is publishing the old value. Do not rely on unsupported settings such as “Sync Lock” or a CMS source-of-truth mode unless they are available and documented in your Search Atlas account. The first corrective action for this failure is to undeploy the active Atlas Brain deployment. ✅ Verify the fix - The affected Atlas Brain deployment is no longer active. - The Shopify product has the correct title. - The title remains correct after a full page reload. - No new CMS Connector activity is changing the title. If you need further assistance, open the 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 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 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.

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

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

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

🔍 Understanding OTTO Meta Description Flagging Discrepancies

🧭 Overview If you've noticed that OTTO flagged a different number of pages for missing meta descriptions compared to missing title tags — for example, 136 pages versus 220 — this is expected behaviour. It does not mean OTTO missed pages or that your audit is incomplete. This article explains why these numbers can differ. ⚙️ Why the Counts Differ OTTO audits title tags and meta descriptions as separate issues, and the number of pages flagged for each can vary. This is a known and expected behaviour within OTTO's audit logic. The two checks do not always evaluate the exact same set of pages, which is why you may see different flagged counts for each issue type. If you are seeing a discrepancy between the number of pages flagged for missing meta descriptions and the number flagged for missing title tags, this does not indicate a bug or an incomplete audit — it reflects how OTTO handles these as independent checks. ✅ What to Do If You're Concerned About Coverage If you believe pages with missing meta descriptions are not being surfaced correctly, here is what to do when contacting support: 1. Note the exact numbers you are seeing for each issue type (e.g. 136 flagged for meta descriptions, 220 for title tags). 2. Note the name of the project or domain where you are seeing the discrepancy. 3. Take a screenshot of the flagged pages list for each issue type if possible. 4. Have this information ready so a support teammate can investigate the specific audit scope applied to 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 Blocked Alt Text and Indexing Failures

Overview Two separate but often co-occurring issues can disrupt your on-page optimization workflow in Search Atlas: blocked image alt text recommendations that cannot be deployed, and Instant Indexing activation failures during service account provisioning. This article explains the root cause of each issue and what to do next. Why Are My Alt Text Recommendations Blocked? Search Atlas deploys alt text changes through an API override layer. When that deployment is blocked, it is typically because the API override process itself is encountering an error — not a browser or cache issue. Clearing your browser cache or cookies does not resolve this error. This is a server-side and API-level issue that requires escalation to the support team so they can investigate the specific block on your account. What to Have Ready When Escalating To help the support team resolve your blocked alt text deployment as quickly as possible, please have the following information ready before reaching out: - The name of the project or site where the alt text deployment is being blocked - The exact error message or status shown when the deployment fails - The timestamp (date and time) when you first noticed the block - Whether the issue affects a single recommendation or all queued recommendations Why Is Instant Indexing Failing During Setup? Instant Indexing activation failures during service account provisioning are related to a plan requirement. The Instant Indexing feature and the associated service account setup require a specific plan level in Search Atlas. If your current plan does not include this feature, provisioning will fail during the activation process. To resolve this, confirm that your Search Atlas subscription includes Instant Indexing access. If you are unsure which plan you are on or whether it includes this feature, the support team can verify your plan details and enable the correct access for your account. What to Have Ready When Escalating To help the support team resolve your Instant Indexing provisioning error quickly, please have the following ready: - Your Search Atlas account email address - The exact error message shown during service account provisioning - The timestamp when the provisioning failure 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 Meta Edits: View Source vs. Browser Inspect

Overview When OTTO applies meta title or meta description edits to your website, you may notice that the changes do not appear when you use your browser's View Page Source option. This is expected behaviour — not a bug. Understanding the difference between View Source and Browser Inspect will help you confirm your edits are live and visible to Google. How OTTO Delivers Meta Edits OTTO applies meta tag changes at the rendering stage, which means the edits may not be reflected in the raw static HTML returned by your server. There are two ways a browser can show you a page's code: - View Page Source: Displays the raw, static HTML that the server sends before rendering. OTTO's changes may not appear here. - Browser Inspect / DevTools: Displays the fully rendered version of the page after the browser has processed it. OTTO's meta edits will appear here. How to Verify Your OTTO Meta Edits Are Live To confirm your OTTO meta edits are rendering correctly, use your browser's Inspect or DevTools feature (typically accessed by right-clicking the page and selecting Inspect). In the Elements panel, search for the meta title or meta description tag and confirm it displays the updated text that OTTO generated. If the updated value appears there, your edit is rendering correctly in the browser. How Google Crawls OTTO-Generated Edits Google's crawler reads the rendered version of a page, similar to what you see in Browser Inspect rather than View Source. This means Google can index meta tags that are applied dynamically by OTTO. After OTTO applies edits, allow some time for Google to recrawl and re-render the page before expecting the changes to be reflected in search results. How to Confirm Google Has Indexed Your Updated Meta Title To check whether Google has picked up your updated meta title, open Google Search Console and use the URL Inspection tool for the page you edited. This will show you the version of the page Google last crawled and whether it reflects OTTO's changes. If it does not yet reflect the update, you can request a recrawl directly from that tool. If you need further assistance, open the 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.

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

🛠️ Understanding OTTO Title Tag Errors and AI Credits

What This Article Covers If you have noticed that the Title Tags section in OTTO shows flagged issues without a clear explanation of what is wrong, you are not alone. This article explains how OTTO surfaces title tag errors, when AI credits are used, and how you can make informed decisions before generating suggestions. How OTTO Flags Title Tag Issues OTTO automatically audits your pages and flags title tags that do not meet SEO best practices. A flag means OTTO has detected a potential problem with one or more title tag conditions, such as a missing, duplicate, or otherwise problematic title. The flag indicator will appear in the Title Tags section within OTTO. The flag may appear before the specific reason is fully visible. We understand this creates uncertainty about whether taking action is worth the cost of AI credits. When Are AI Credits Used? AI credits are consumed when you ask OTTO to generate a suggested title tag for a flagged page. Simply viewing the flagged list or reviewing a page does not spend credits. Credits are only deducted at the moment OTTO produces a new AI-written title suggestion for that URL. Here is a clear breakdown of what does and does not use credits: - Does NOT use credits: Viewing the list of flagged pages, seeing the flag indicator, reading the current title tag text - DOES use credits: Asking OTTO to generate an AI title suggestion for a specific page How to Evaluate a Flagged Title Before Using Credits Before asking OTTO to generate an AI suggestion, it is worth reviewing the existing title tag yourself to see if the issue is something you can address directly. Common title tag problems include a title that is blank, too short, too long, duplicated across multiple pages, or one that does not clearly describe the page content. If you can identify the problem yourself, you may be able to resolve it without consuming any AI credits. Only request an AI-generated suggestion when you want OTTO to produce an alternative title — that is the point at which credits are deducted. Taking a moment to assess the flagged title before requesting AI assistance helps you preserve credits for cases where you genuinely need them. If you need further assistance, open the 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 Meta Descriptions on Your Site

🧩 Why Duplicate Meta Descriptions Happen Duplicate meta descriptions occur when more than one tool or source writes a meta description to the same page at the same time. Search Atlas gives you several ways to set meta descriptions, and if more than one is active simultaneously, your site may display multiple conflicting tags. The three most common sources of conflict are: - OTTO SEO — Search Atlas's AI automation engine can deploy meta descriptions directly to your site. - Search Atlas sidebar (manual entry) — Meta descriptions entered manually through the on-page tools inside Search Atlas. - Third-party SEO plugins — Plugins installed on your site such as SmartCrawl, Yoast SEO, Rank Math, or All in One SEO may also be writing meta descriptions independently. When two or more of these sources are active for the same page, search engines and SEO audit tools will detect multiple meta description tags in the page's HTML — which is exactly what you are seeing. 🔍 How to Identify Which Sources Are Conflicting Before making any changes, confirm which tools are currently writing meta descriptions to the affected pages: 1. Open your browser and navigate to the affected page on your live site. 2. Right-click anywhere on the page and select View Page Source. 3. Press Ctrl + F (or Cmd + F on Mac) and search for meta name="description". 4. Count how many instances appear. If you see more than one, note the content of each tag so you can trace which tool produced it. 5. Log in to your WordPress dashboard (or your CMS) and check which SEO plugins are installed and active. 🛠️ How to Fix Duplicate Meta Descriptions The fix is straightforward: make sure only one source is responsible for writing meta descriptions. Follow the steps below based on your setup. ⚙️ Step 1 — Choose Your Preferred Meta Description Source Decide which single tool will manage your meta descriptions going forward. Search Atlas recommends using OTTO SEO for automated, AI-optimised descriptions, or entering them manually through Search Atlas if you prefer full manual control. Only one approach should be active at a time. 🤖 Step 2 — Check and Manage OTTO Deployments 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation). 2. Select the site that is showing duplicate meta descriptions. 3. Review the list of deployed actions and look for any meta description tasks that have been applied to the affected pages. 4. If you do not want OTTO to manage meta descriptions for specific pages, disable or roll back those individual deployments from within the OTTO task list. 5. If you do want OTTO to manage meta descriptions, leave these deployments active and proceed to disable all other sources in the steps below. ✏️ Step 3 — Remove Manual Entries in Search Atlas 1. In the left sidebar, go to Content, then select On-Page Audit. 2. Open the audit for the affected page. 3. Check whether a meta description has been entered manually in the sidebar panel. 4. If OTTO is handling meta descriptions for this page, clear the manual field so it is blank. This prevents Search Atlas from writing a second, separate tag. 🔌 Step 4 — Disable Meta Descriptions in Third-Party Plugins If you have a third-party SEO plugin installed (such as SmartCrawl, Yoast SEO, Rank Math, or All in One SEO), you must turn off its meta description output for the affected pages — or disable it site-wide if Search Atlas is your primary SEO tool. - SmartCrawl: Go to SmartCrawl → Sitemap & Meta in your WordPress dashboard, then navigate to the Meta Tags section and disable meta description output. - Yoast SEO: Open the page in the WordPress editor, scroll to the Yoast SEO meta box, and clear the meta description field. To disable it globally, go to Yoast SEO → Search Appearance and remove template tags from the meta description field. - Rank Math: Open the page editor, expand the Rank Math panel, and clear the meta description field. - All in One SEO: Open the page editor, scroll to the AIOSEO settings, and clear the meta description field. If you are unsure which plugin is generating the conflicting tag, deactivate plugins one at a time and check the page source after each deactivation until the duplicate disappears. ✅ Step 5 — Verify the Fix 1. After making your changes, revisit your live page and view the page source again. 2. Search for meta name="description" and confirm only one instance appears. 3. You can also use the Content → On-Page Audit tool in Search Atlas to re-scan the page and confirm the duplicate issue is resolved. 💡 Best Practices to Prevent Duplicates in Future - Use only one tool to manage meta descriptions across your site — either OTTO, the Search Atlas manual workflow, or a third-party plugin, never a combination. - When activating OTTO on a site that already has a third-party SEO plugin, always disable the plugin's meta description output first. - After any major plugin installation or update, re-audit your key pages to check for newly introduced duplicates. - Use the Content → Meta Generator tool in Search Atlas to create optimised meta descriptions, then deploy them through a single consistent channel. 💬 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 Alt-Text Suggestions for Missing Images Explained

🔍 Why OTTO Suggests Alt-Text for Images You Can't See If OTTO is recommending alt-text for an image that doesn't appear to be on your page, this may be caused by images that are present in the page's HTML source but are not visually prominent in the normal rendered view. This can include tracking pixels, placeholder assets, hidden section backgrounds, or template components injected by your CMS or funnel-builder platform. OTTO scans the raw HTML of your page, not the rendered visual layout. This means it detects every <img> tag in the source, including images that may not be immediately visible to you when browsing the page. This behaviour is intentional — OTTO flags all missing alt-text to ensure full accessibility and SEO compliance. ✅ How to Handle These Suggestions You have two straightforward options when OTTO surfaces an alt-text suggestion for an image you cannot locate visually: 1. Accept the suggestion. If the image exists in your source code, adding descriptive alt-text is still the correct SEO and accessibility practice. Review the suggested text and apply it if it is accurate. 2. Dismiss the suggestion. If you have confirmed the image is a tracking pixel, a decorative placeholder, or an artifact with no meaningful content, you can dismiss the task within OTTO. To inspect whether the image actually exists in your page source, right-click your page in a browser and select View Page Source, then search for the image file name or URL associated with the suggestion. This confirms the image is present even if invisible in the rendered view. 🗺️ Navigating to OTTO in the Platform OTTO is accessible within the Search Atlas platform. Once there, you can view all active OTTO tasks, including alt-text suggestions, grouped by site and category. If you manage multiple sites, navigate between your projects within the platform to view their respective task queues. 📋 Understanding OTTO Deployments When OTTO is deployed on a site, it audits the page source for accessibility and SEO issues — including missing alt-text on any image element it finds in the HTML. This includes images that may not be immediately visible in a standard browser view. If you need further assistance, open 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.

🔍 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 Search Atlas Meta Description Override Issues

🔍 Overview If Search Atlas is leaving your meta descriptions blank or injecting unexpected content — such as keywords or meta titles — into your pages, the most common cause is a crawler access restriction. When the Search Atlas crawler cannot reach your page, it cannot read or preserve your existing meta description, which causes it to fall back to a blank or auto-generated value. This article walks you through diagnosing the problem and whitelisting the Search Atlas crawler IPs so your meta descriptions are processed correctly. ⚠️ Symptoms of This Issue - Your meta description appears blank in search results or in the Search Atlas dashboard. - Search Atlas is injecting keywords or the meta title into the description field against your instructions. - The issue persists on specific pages even after you have manually set and saved a meta description. - The problem affects one or more URLs but not your entire site. 🧠 Why This Happens Search Atlas uses a crawler to read your pages and apply on-page optimisation settings, including meta descriptions. If your server, firewall, CDN, or security plugin blocks the crawler's IP addresses, the crawler cannot retrieve your existing meta description. As a result, Search Atlas either leaves the field blank or substitutes it with automatically generated content. This is not a bug in your settings. It is a connectivity issue between the Search Atlas crawler and your web server that must be resolved at the server or security layer. ✅ Step 1 — Confirm the Crawler Is Being Blocked Before whitelisting any IPs, confirm that a block is actually occurring: 1. Log in to your hosting control panel, firewall dashboard, or CDN provider (for example, Cloudflare, Sucuri, or Wordfence). 2. Navigate to the access logs or blocked requests section. 3. Search for any blocked requests originating from the Search Atlas crawler. 4. Note the timestamps and the specific URLs being blocked. If you see blocked requests in the logs, proceed to Step 2. If logs are unclear or inaccessible, proceed directly to the whitelist step — adding the IPs causes no harm and resolves the issue in the majority of cases. 🔧 Step 2 — Whitelist the Search Atlas Crawler IPs Add the Search Atlas crawler IP addresses to the allowlist in your firewall, CDN, security plugin, or hosting control panel. To obtain the exact list of current Search Atlas crawler IPs, please contact the support team using the instructions at the bottom of this article. The exact steps for adding IPs to your allowlist depend on your platform. In general: - Cloudflare: Locate the IP allowlist or firewall rules section in your Cloudflare dashboard and add each crawler IP as an allowed address. - Wordfence: In your WordPress admin panel, navigate to the Wordfence settings and add each IP to the whitelist under the firewall allowlist options. - Other firewalls or security plugins: Refer to your provider's documentation for adding IP addresses to an allowlist or trusted IPs list. ✅ Step 3 — Verify the Fix 1. After whitelisting the IPs, return to the affected page in your Search Atlas dashboard. 2. Trigger a re-crawl or wait for the next scheduled crawl cycle. 3. Confirm that your meta description is now being read and preserved correctly. If the meta description is still blank or incorrect after re-crawling, double-check that all crawler IPs were saved correctly in your firewall or security 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.

🗑️ Delete Non-Applicable Alt Text Issues in OTTO

🔍 Overview When OTTO's On Page Optimizer scans your page for image alt text issues, it may flag items that are not applicable to your site — such as SVG files, icon fonts, or other unsupported image types that do not require alt text. These line items cannot be fixed automatically, but you can manually delete them so your audit reflects only actionable tasks. This article walks you through how to identify and remove those non-applicable alt text issues in the new OTTO format. 🤔 Why Are SVG and Unsupported Items Flagged? OTTO scans all image elements on a page and flags any that are missing alt text attributes. Some of these may include: - SVG files — inline or embedded SVGs that are decorative or icon-based - Icon fonts rendered as images — elements that visually appear as images but are not standard img tags - Unsupported image formats — file types that OTTO cannot automatically apply alt text to These items are flagged because the scanner detects a missing alt attribute, but in many cases no alt text is needed or the format is not supported for automated fixes. Deleting these line items tells OTTO they are not applicable to your workflow. 🧭 How to Navigate to the On Page Optimizer 1. Log in to your Search Atlas account. 2. In the left sidebar, go to OTTO SEO → All Sites (SEO Automation) and select your site. 3. Open OTTO Grader (the OTTO Grader is also accessible from OTTO SEO → Overview). 4. Scroll to the Image Alt Text task group to see all flagged alt text issues. 🗑️ How to Delete a Non-Applicable Alt Text Line Item 1. Locate the alt text issue you want to remove. Review the file name or image path to confirm it is an SVG, icon, or unsupported item that does not need alt text. 2. Find the delete option for that line item within the row. 3. Click the delete option to remove the line item from your On Page Optimizer task list. 4. Repeat these steps for any additional non-applicable items in the alt text group. Note: Deleting a line item does not make any changes to your live page. It only removes the task from OTTO's audit list, indicating that it is not applicable to your optimization workflow. ✅ Tips for Managing Alt Text Issues Efficiently - Review before deleting — Check each flagged item carefully. Some SVGs used as content images (such as infographics) may still benefit from a descriptive alt attribute. - Decorative images — Purely decorative images that add no informational value are safe candidates for removal from the audit list. - Keep a record — If you are managing multiple pages, note which item types you are removing so you can apply consistent decisions across 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 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 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 Meta Description Discrepancies Between Audit Tools

🧩 Why the Two Tools Can Show Different Results If Page Issues flags a page as missing a meta description but On-Page Audit shows one is present, this is almost always caused by an SEO plugin—such as Yoast SEO, Rank Math, or All in One SEO—injecting the meta description dynamically at render time rather than writing it directly into the page's static HTML. Here is what happens under the hood: - Page Issues crawls the raw HTML source of your page. If the meta description is added by a plugin after the page loads (via JavaScript or server-side logic tied to the plugin), the crawler may not detect it in the source. - On-Page Audit analyzes the rendered version of the page, which includes content added by plugins and scripts. This is why it correctly picks up the meta description. Neither tool is wrong—they are measuring different things. The discrepancy is a signal that your meta description delivery method may need attention. ⚠️ Common Plugins That Cause This Conflict The following plugins are known to inject meta descriptions in ways that can create detection gaps: - Yoast SEO — The most frequently reported cause. Yoast writes the meta description through its own output process, which can be missed by raw HTML crawlers depending on your server configuration and caching setup. - Rank Math — Similar behavior to Yoast; meta tags are managed through the plugin's rendering layer. - All in One SEO (AIOSEO) — Can produce the same discrepancy, particularly on pages using dynamic templates. - SEOPress — Occasionally causes conflicts on pages with heavy caching or CDN layers. 🛠️ How to Diagnose the Root Cause 1. Open the affected page URL in your browser. 2. Right-click anywhere on the page and select View Page Source (not Inspect Element). 3. Press Ctrl+F (or Cmd+F on Mac) and search for meta name="description". 4. If the tag is absent from the source but present in the Inspect Element panel, your plugin is injecting it dynamically. Continue to the resolution steps below. 5. If the tag appears in the source, the issue may be related to caching. Proceed to the cache-clearing step. ✅ Steps to Resolve the Discrepancy Step 1 — Check your plugin's output settings In your SEO plugin (Yoast, Rank Math, etc.), confirm that the meta description is actually saved for the affected page and that the plugin is set to output meta tags in the document <head>. Some plugins allow you to disable meta tag output globally or per post type. If you need further assistance, open the 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 from Pagination Canonicalization

🧩 Why Duplicate Paginated URLs Appear When Search Atlas crawls your site, it follows every discoverable URL — including paginated versions of your blog posts or archive pages. These are the numbered URLs that look like /blog/post-title/, /blog/post-title/2/, /blog/post-title/3/, and so on. If your paginated URLs are missing a canonical tag — or if each page points to itself rather than the root URL — Search Atlas flags them as duplicate content. This is accurate and expected behaviour: the tool is correctly identifying a canonicalization gap that could harm your search rankings. 📋 Understanding the Problem A paginated URL is only a duplicate risk when one or more of the following is true: - The paginated pages (?page=2, /2/, etc.) have no canonical tag at all. - Each paginated page self-canonicalises instead of pointing back to the root URL. - The root URL does not use a rel="canonical" tag pointing to itself. - Your CMS generates multiple URL formats for the same content (e.g. trailing slash vs. no trailing slash). All five (or more) numbered variants are then treated as separate pages with identical or near-identical content, which is exactly what Search Atlas reports. 🛠️ How to Fix Canonical Links Using OTTO OTTO SEO can apply canonical fixes directly to your site once it is activated and connected. Follow these steps: 1. In the left sidebar, click Site Metrics → Site Explorer to open the Site Explorer. 2. Select the property that contains the duplicate paginated URLs. 3. Review the list of flagged duplicate URLs. Confirm that the affected URLs share a common root path (e.g. the same blog post slug with numeric suffixes). 4. Open OTTO SEO from the left sidebar and ensure OTTO is activated for the correct site. 5. Navigate to OTTO SEO → Site Audit → Issues and look for the Duplicate Content or Canonical task group. 6. Select the flagged paginated URLs and apply the recommended canonical fix. OTTO will set the canonical tag on each paginated page to point to the root (page 1) URL. 7. Click Deploy to push the changes live. 8. Allow 24–48 hours for Search Atlas to re-crawl the pages and clear the duplicate flags. ✅ Best Practices for Pagination Canonicalization To prevent this issue from recurring, follow these canonicalization guidelines: - Root page self-canonicalises: The first page of any paginated series should include a canonical tag pointing to itself (e.g. <link rel="canonical" href="https://yourdomain.com/blog/post-title/" />). - Paginated pages point to root: Pages 2, 3, 4, and beyond should each carry a canonical tag pointing back to the root URL, not to themselves. - Use consistent URL formats: Decide on trailing slash or no trailing slash and apply it consistently across all paginated URLs. - Avoid indexing paginated pages: If paginated pages add no unique value, consider adding noindex alongside the canonical tag to reduce crawl waste. - Test after deployment: Use a browser extension or Google's URL Inspection Tool to confirm the canonical tag is rendering correctly in the HTML source. ❓ Still Seeing Duplicates After Fixing? If the duplicate flags persist after deploying canonical changes through OTTO, check the following: - The site re-crawl may not have completed yet — wait 48 hours and check again. - A caching plugin or CDN may be serving old page versions without the updated canonical tag. Purge your cache after deployment. - Your CMS theme or plugin may be overriding the canonical tags set by OTTO. Review any installed SEO plugins (e.g. Yoast, RankMath) for conflicting canonical settings. - Verify the canonical tag appears in the rendered HTML, not just the source — JavaScript-rendered pages can strip meta tags before they are indexed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔗 Fix Unwanted URL Parameters in Canonical Links

🧭 Overview When you run a Screaming Frog crawl on a site managed with Search Atlas, you may notice canonical links containing an extra URL parameter: is_otto_page_fetch=1. This parameter is appended by Otto, the Search Atlas automation engine, during page fetches for analysis. It is an internal crawl signal and should never appear in your canonical tags on the live site. If it does, search engines may index the wrong canonical URL, which can negatively affect your SEO. This article explains why this happens, how to verify the issue, and the exact steps to resolve it inside Search Atlas and Screaming Frog. 🔍 Why This Parameter Appears Otto adds is_otto_page_fetch=1 to page requests so it can identify its own crawl traffic internally. Under normal circumstances this parameter exists only in the HTTP request and is never written to the page's HTML. However, if your site or CMS dynamically generates canonical tags based on the current request URL, the parameter can be captured and rendered inside the <link rel="canonical"> tag. This is a site-side configuration issue that Search Atlas tooling can help you detect and fix. ✅ Step 1 — Confirm the Issue in Screaming Frog 1. Open Screaming Frog and crawl your site. 2. Click the Canonicals tab in the lower panel. 3. In the filter dropdown, select Contains a Canonical URL. 4. Export the list and search for any canonical value containing is_otto_page_fetch=1. 5. Note the affected URLs. If only a handful appear, the issue is likely isolated to pages with dynamic canonical logic. If the parameter is widespread, your CMS is globally reflecting request parameters into canonical tags. ⚙️ Step 2 — Configure Parameter Filtering in Search Atlas Search Atlas lets you define URL parameters that should be stripped before canonical evaluation. Follow these steps: 1. Log in to Search Atlas and navigate to your project. 2. Open Settings and select Crawl Configuration. 3. Scroll to the URL Parameter Exclusions section. 4. Click Add Parameter and enter is_otto_page_fetch (without the value). 5. Save your settings. Otto will now strip this parameter from all URLs before they are evaluated, reported, or compared against canonical values. After saving, re-run your site audit from within Search Atlas. The parameter should no longer appear in canonical link reports generated by the platform. 🛠️ Step 3 — Fix the Canonical Tag on Your Site Even after adjusting Search Atlas settings, you must prevent your site from writing the parameter into the canonical tag in the first place. The correct fix depends on your CMS or framework: - WordPress (Yoast / Rank Math / All in One SEO): These plugins build canonical URLs from get_permalink() rather than the raw request URL, so they are usually not affected. If you are using a custom canonical filter or a theme function that reads $_SERVER['REQUEST_URI'], update it to use get_permalink() or home_url(add_query_arg(array(), false)) with query args explicitly stripped. - Custom CMS / server-side rendering: Locate where the canonical meta tag is built and ensure the URL is constructed from the canonical page path, not the live request URL. Strip all query parameters before inserting the value into the tag, or maintain an explicit allowlist of parameters that are permitted in canonicals. - Cloudflare / CDN or edge workers: If a worker or transform rule is injecting or reflecting parameters, add a rule to strip is_otto_page_fetch before the canonical tag is generated or cached. 📋 Step 4 — Re-Crawl and Verify in Screaming Frog 1. After updating your site, clear any full-page cache (WordPress cache plugins, Varnish, Cloudflare cache, etc.). 2. Return to Screaming Frog and run a fresh crawl. 3. Go back to the Canonicals tab and re-export the list. 4. Confirm that no canonical URLs contain is_otto_page_fetch=1. 5. If affected pages had previously been indexed with the incorrect canonical, submit them via Google Search Console under URL Inspection > Request Indexing to prompt Google to re-evaluate the correct canonical. 🚫 Common Mistakes to Avoid - Only fixing it in Screaming Frog settings: Configuring Screaming Frog to ignore the parameter hides it from reports but does not fix it on your live pages. Always fix the source. - Caching old pages: If your CDN or server cache is serving stale HTML, the bad canonical will persist even after a code fix. Always purge caches after making changes. - Blocking Otto entirely: Blocking the Otto crawler user agent in robots.txt will prevent Search Atlas from auditing your site. Instead, use the parameter exclusion settings described in Step 2. 💬 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 Non-Indexable Pages Caused by Canonical Mismatches

🧭 Overview If your homepage or any other page shows as non-indexable in Site Audit despite having no noindex tag, being listed in your XML sitemap, and appearing unblocked in your robots.txt file, the root cause is often a canonical URL mismatch. This is one of the most frequently missed causes of false non-indexable flags, and it can be resolved quickly once identified. 🤔 What Is a Canonical URL Mismatch? A canonical tag tells search engines which version of a URL is the authoritative, preferred version of a page. When the canonical URL declared on a page does not exactly match the URL that Site Audit is crawling, the tool correctly flags the crawled version as non-indexable — because it is effectively deferring indexing authority to a different URL. Common mismatches include: - Trailing slash differences: The page is crawled as example.com/ but the canonical tag points to example.com (or vice versa). - HTTP vs. HTTPS: The canonical specifies http:// while the live page serves over https://. - WWW vs. non-WWW: The canonical uses www.example.com but the crawled URL is example.com. - URL parameter inconsistencies: The canonical omits or includes query parameters that appear in the crawled URL. - Uppercase vs. lowercase characters: A mismatch in letter casing between the canonical and the crawled URL. Even a single character difference between the crawled URL and the declared canonical is enough to trigger a non-indexable flag in Site Audit. 🔎 How to Identify a Canonical Mismatch in Site Audit 1. Go to OTTO SEO → Site Audit in the left sidebar of your Search Atlas dashboard. 2. Open your most recent crawl report and navigate to the Indexability section. 3. Click on the affected page (for example, your homepage) to open its detail panel. 4. Look for the Canonical URL field in the page details. Compare the value shown there against the exact URL that was crawled (displayed at the top of the detail panel). 5. Check whether the two URLs are identical, character for character, including protocol, subdomain, trailing slash, and casing. If the canonical URL and the crawled URL do not match exactly, you have found your issue. 🛠️ How to Fix a Canonical URL Mismatch Once you have identified the mismatch, choose the fix that applies to your situation: - Trailing slash: Decide on one consistent format (with or without trailing slash) and update either your canonical tag or your server redirect so both URLs resolve to and declare the same preferred version. - HTTP vs. HTTPS: Update your canonical tags to use https:// on all pages and ensure your server redirects all HTTP traffic to HTTPS. - WWW vs. non-WWW: Pick one version as your canonical domain, set up a 301 redirect from the other, and make sure all canonical tags reflect your chosen version. - URL parameters: If parameters are irrelevant to page content, strip them from your canonical tags or configure parameter handling in Google Search Console. - Casing issues: Update your canonical tags or configure server-level redirects so all URLs are consistently lowercase. After making changes, re-crawl your site in Site Audit to confirm the mismatch has been resolved and the page is now flagged as indexable. ✅ How to Re-Crawl and Verify the Fix 1. In the left sidebar, select OTTO SEO → Site Audit. 2. Open your project and click Re-crawl or Start New Crawl. 3. Once the crawl completes, return to the Indexability section. 4. Confirm the previously flagged page no longer appears in the non-indexable list. 5. In the page detail panel, verify the Canonical URL field now matches the crawled URL exactly. ⚠️ Other Common Causes of Non-Indexable Flags If fixing your canonical tag does not resolve the issue, also check for these additional causes: - A noindex directive in the page's <meta robots> tag or HTTP response header. - The page being blocked in your robots.txt file. - JavaScript-rendered content that prevents the crawler from reading the page's canonical tag correctly. - The page returning a non-200 HTTP status code such as a redirect chain or server error. 💬 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.

🔍 Understanding OTTO Title Tag Issues and Suggestions

🧭 Overview When OTTO detects a Title Tag issue on your site, it flags the page and displays the current title value. You may notice that OTTO does not immediately explain why the title needs updating, and that generating a suggested replacement requires AI credits. This article explains how the Title Tag issue type works, what triggers a flag, and how to get actionable suggestions. ⚠️ Why OTTO Flags a Title Tag OTTO evaluates every page title against a set of on-page SEO best practices. A title is flagged when one or more of the following conditions are detected: - Too short or too long: Titles should fall within the recommended range of 30–100 characters. Titles outside this range may be truncated or under-descriptive in search results. - Missing target keyword: The primary keyword for the page is absent from the title, reducing its relevance signal to search engines. - Duplicate title: The same title appears on multiple pages, which can cause indexing confusion and keyword cannibalisation. - Generic or non-descriptive text: Titles such as "Home" or "Page 1" provide no meaningful context to users or crawlers. Currently, OTTO displays the flagged title value so you can review it directly, but a detailed written explanation of the specific rule that triggered the flag is not yet shown inline. This diagnostic improvement is on our product roadmap and is actively being developed. 💡 Why AI Credits Are Required for Suggestions Generating a replacement title is not a simple rule lookup — OTTO uses AI to analyse your page content, target keyword, and character constraints before producing a contextually relevant suggestion. This generation process consumes AI credits because it calls a large language model to craft a title that is both SEO-optimised and aligned with your content. Think of the AI credit as the cost of having a specialist writer review your page and propose an improved title, rather than applying a generic template. 🛠️ How to Review and Fix Title Tag Issues in OTTO 1. Open OTTO from your Search Atlas dashboard and navigate to the Title Tags issue category. 2. Review the current title shown for each flagged page. Cross-reference the common flag reasons listed above to identify the likely problem (e.g., check character count, look for your target keyword). 3. When you are ready to generate a suggestion, click the Generate button next to the flagged title. OTTO will use AI credits to produce an optimised replacement. 4. Review the suggested title. If it meets your needs, apply it directly. If you prefer to write your own fix, you can manually edit the title field without spending any credits. 5. Once a title is updated, mark the issue as resolved so OTTO tracks your progress accurately. 📊 Managing Your AI Credits To avoid running out of credits unexpectedly, consider these tips: - Prioritise generating suggestions for pages with the highest traffic or strategic importance first. - For straightforward fixes — such as a title that is simply too long — edit the title manually to save credits for more complex cases. - You can check your remaining AI credit balance in your account settings at any time. 🚧 Known Issues and Upcoming Improvements Our engineering team is actively working on several improvements related to Title Tag diagnostics: - A "How it works" tooltip update is in development that will clarify the 30–100 character range guideline directly within the OTTO interface, so the flagging criteria are immediately visible without leaving the page. - Work is ongoing to ensure title tag suggestions are consistently unique and meaningfully differentiated from the original title. - A bug affecting title tag display on page load is also being resolved to improve the stability of the OTTO interface. These updates will roll out progressively. No action is required on your end — improvements will appear automatically once deployed. ❓ Frequently Asked Questions - Can I fix a title tag without using AI credits? Yes. You can type your own replacement title directly into the editable field. AI credits are only consumed when you click Generate to request an AI-written suggestion. - Why does the suggestion look very similar to my original title? In some cases, the original title may already be close to optimal, and the AI makes minor refinements. If you receive a suggestion that feels too similar, try editing the title manually for a more distinct result. Our team has also addressed cases of near-identical suggestions in a recent update. - Will OTTO explain the reason for each flag in the future? Yes. Inline diagnostic explanations are planned as part of ongoing OTTO improvements. The tooltip update currently in development is a first step toward this goal. 💬 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 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 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 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 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 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 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.

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

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

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

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

🔍 Why OTTO Detects H2 Headings From Wrong Sections

🧭 Overview OTTO analyzes your page's HTML structure to identify headings and generate SEO suggestions. Occasionally, customers notice that OTTO is pulling H2 headings from sections like FAQs, sidebars, or footers rather than the main content area. This article explains why that happens and what you can do about it. 🤔 Why Does This Happen? OTTO crawls the raw HTML of your page exactly as a search engine would. It reads all H2 tags present in the page's source code, regardless of where they visually appear on the page. This means if your FAQ section, sidebar, or any other page component uses H2 tags, OTTO will include them in its analysis. Common reasons OTTO picks up H2 headings from unexpected locations include: - FAQ sections using H2 tags: Many FAQ plugins and themes mark each question with an H2 tag, which places them at the same heading level as your main content headings. - Widgets and sidebars: Some themes apply H2 tags to widget titles or sidebar section headers. - Page builders: Drag-and-drop builders sometimes assign H2 tags to decorative or secondary elements by default. - Third-party embeds: Scripts or embedded components can inject their own heading tags into your page HTML. ⚙️ Is This an OTTO Issue or a Website Code Issue? In most cases, this is a website code or theme structure issue, not a bug in OTTO. OTTO is correctly reading the heading hierarchy that exists in your HTML. When non-primary content like FAQs uses H2 tags, it signals to both OTTO and search engines that those elements share equal importance with your core content headings — which may not reflect your intent. That said, OTTO uses the heading data it finds to generate crawl suggestions. If the heading structure it reads is inconsistent with your page's actual content hierarchy, the suggestions it produces may feel off-target. 🛠️ How to Fix Heading Structure on Your Page To help OTTO — and search engines — correctly interpret your page structure, review and update your HTML heading tags as follows: 1. Audit your page HTML: Right-click your page in a browser and select View Page Source or use browser developer tools to search for all H2 tags. Note which sections they belong to. 2. Reclassify FAQ and secondary headings: Change FAQ question headings, sidebar titles, and widget headers from H2 to H3 or H4 tags. Reserve H2 tags for your primary content sections only. 3. Check your theme or page builder settings: Many themes and builders let you change the heading level for specific components without editing code directly. Look for a "Heading Tag" or "HTML Tag" dropdown in your FAQ plugin or widget settings. 4. Re-run OTTO after making changes: Once you have updated your heading structure, navigate to OTTO SEO in the left sidebar, open SEO Automation, and allow OTTO to re-crawl the page. OTTO will then reflect the corrected heading hierarchy in its suggestions. ✅ Best Practices for Heading Structure Maintaining a clean heading hierarchy benefits both OTTO's analysis and your overall SEO performance. Follow these guidelines: - Use one H1 tag per page for the primary page title. - Use H2 tags only for main content sections that directly support the page's primary topic. - Use H3 and H4 tags for subsections, FAQs, sidebars, and supporting content. - Avoid skipping heading levels (e.g., jumping from H1 to H4), as this can confuse crawlers. - Treat your heading structure as an outline — it should reflect the logical flow and priority of your content. 💬 Still Seeing Unexpected Heading Suggestions? If you have corrected your heading structure and OTTO is still pulling headings from the wrong locations, or if you are unsure how to update your site's HTML, 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 Inconsistent OTTO Alt Text Suggestions

🔍 Why Alt Text Quality Can Vary OTTO generates alt text by analysing the image file itself alongside the surrounding page context — including the page title, headings, and body copy. When any of these inputs are incomplete or ambiguous, the quality of the suggestion can drop. Understanding the root causes helps you get consistently strong results. Common reasons for inconsistent alt text include: - Generic or unclear image file names — files named IMG_4892.jpg or photo1.png give OTTO very little to work with. - Low page context — pages with thin content, missing headings, or no clear topic make it harder for OTTO to infer what an image represents. - Mixed image types on one page — decorative images, product shots, and infographics all require different alt text approaches, and a mixed batch can produce uneven outputs. - Images with embedded text — screenshots, banners, or graphics containing text are harder for OTTO to interpret accurately without additional context. - Very small or low-resolution images — OTTO has less visual data to analyse, which can lead to vague suggestions. 🛠️ How to Improve Alt Text Consistency Follow these steps to give OTTO the best possible inputs before generating or regenerating alt text. 1. Rename image files descriptively before uploading. Use short, keyword-relevant names such as red-running-shoes-side-view.jpg instead of generic strings. This single change has the biggest impact on output quality. 2. Ensure the page has sufficient content. Navigate to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3) and check that the target page has a clear H1, at least one H2, and a descriptive body paragraph before running OTTO. 3. Separate image batches by type. If a page contains both decorative and informational images, process them in separate OTTO sessions. This helps the model apply the correct descriptive style to each group. 4. Add a manual hint in the image title or caption field. Where your CMS allows it, fill in the image title or caption before triggering OTTO. These fields are read as additional context. 5. Regenerate suggestions individually for outliers. After a bulk run, review each suggestion. For any that look off, select that image individually and regenerate. A single-image pass gives OTTO a more focused context window. ✅ How to Review and Edit Alt Text in OTTO Once OTTO has generated suggestions, you can review and refine them directly inside the platform. 1. Go to OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select the relevant site and open the page you want to review. 3. Locate the Images section within the OTTO recommendations panel. 4. Click on any alt text suggestion to open the inline editor. 5. Make your edits and click Save to apply the change before deploying. Always aim for alt text that is descriptive, under 125 characters, and relevant to both the image and the page topic. Avoid keyword stuffing — natural, readable descriptions perform better for both accessibility and SEO. 💡 Best Practices for Long-Term Consistency - Establish an image naming convention across your team before assets are uploaded to your CMS. - Run OTTO on pages that are content-complete — avoid generating alt text on draft or placeholder pages. - Review OTTO suggestions before deploying rather than auto-applying in bulk, especially for e-commerce product images where accuracy is critical. - Re-run OTTO after major page content updates — if the page topic changes, existing alt text may no longer be contextually accurate. 🆘 Still Seeing Inconsistent Results? If you have followed the steps above and OTTO is still producing low-quality alt text for specific images, it may indicate an issue with how those images are indexed or served 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 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 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 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 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 Footer 404 External Links Fast

🔍 What Are OTTO Footer Backlinks? When OTTO is activated on your site, it may inject a small otto-community-backlink div in your site's footer. This div contains external links that are part of the OTTO community backlink network. Over time, some of these external URLs can return a 404 (Not Found) status, meaning the destination page no longer exists. OTTO automatically monitors these footer links for you, but it is important to understand where to find them, how to identify broken ones, and what steps to take when a 404 is detected. 📍 Where to Find OTTO Footer Link Monitoring 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 or domain you want to review. 4. Navigate to the OTTO Dashboard for that project. 5. Look for the External Links or Backlink Health section within the OTTO interface — this is where footer link statuses are reported. OTTO continuously checks the status of every external link it has placed in your site's footer. Any link returning a 404 error will be flagged automatically in this section for your review. ⚠️ Why 404 Footer Links Are a Problem Broken outbound links in your footer can negatively affect your site in several ways: - User experience: Visitors who click a broken link encounter an error page, reducing trust in your site. - Crawl budget: Search engine bots waste crawl budget following dead-end links. - SEO signals: Too many broken outbound links can weaken your site's perceived quality in search engine assessments. Resolving these 404 links promptly keeps your site healthy and your OTTO network participation in good standing. 🛠️ How to Fix OTTO Footer 404 Links Once you have identified broken footer links inside the OTTO Dashboard, follow these steps to resolve them: 1. Review the flagged links: In the External Links or Backlink Health section, you will see a list of footer URLs with their current HTTP status. Focus on any link marked 404. 2. Let OTTO auto-replace the link: In most cases, OTTO will automatically queue a replacement URL from the community network to swap out the broken link. Check whether an auto-replacement is already pending for the flagged link — if it is, no manual action is needed. 3. Manually remove or deactivate the link: If auto-replacement is not available or you prefer manual control, use the toggle or remove option next to the broken link inside the OTTO Dashboard to deactivate it. This removes the broken URL from your footer's otto-community-backlink div immediately. 4. Re-run an OTTO scan: After making changes, trigger a fresh scan from the OTTO Dashboard to confirm the 404 link no longer appears in your footer and that all remaining footer links return healthy status codes. 5. Verify on your live site: Inspect your site's footer directly — either via your browser's developer tools or a source-code view — to confirm the otto-community-backlink div no longer contains the broken URL. 🔄 How OTTO's Automatic Monitoring Works OTTO runs scheduled health checks on every external link it manages in your footer. Here is what happens automatically: - Continuous scanning: OTTO periodically sends requests to each footer link URL to verify it returns a valid 200 status code. - 404 flagging: Any URL that returns a 404 response is immediately flagged in your OTTO Dashboard with the affected link and its status. - Auto-replacement queue: When a replacement URL is available in the community network, OTTO queues it to replace the broken link without requiring manual intervention. - Dashboard alerts: You will see a notification or count update in your OTTO SEO V3 dashboard whenever new broken footer links are detected, so you are never left unaware. Because monitoring is automatic, you do not need to manually check your footer's HTML on a recurring basis — OTTO surfaces the issues for you inside the platform. 💡 Best Practices for Healthy Footer Links - Check your OTTO Dashboard at least once a week for any newly flagged 404 links. - Do not manually edit or delete the otto-community-backlink div from your site's theme or template — always manage these links through the OTTO Dashboard to avoid sync issues. - If you notice a spike in 404 detections, trigger a manual re-scan to ensure OTTO's data is up to date. - Keep OTTO activated and your project connected so monitoring remains active at all times. 🆘 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.

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

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

🛠️ 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: 3. Replace the outer and tags with a neutral element. For example: 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.

🔧 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 . 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 Duplicate OTTO Anchor Texts at Scale

🧭 Overview OTTO's Internal Linking Opportunities feature can, in some cases, apply the same anchor text across a large number of pages, creating widespread duplication. There is currently no bulk regeneration option within the platform. This article explains what to expect and how to get help resolving the issue as efficiently as possible. ⚠️ Understanding the Limitation When OTTO generates anchor text suggestions for Internal Linking Opportunities, it may produce identical anchor text across many URLs — for example, when a batch of pages shares a dominant keyword theme. Once those suggestions are accepted and deployed, the platform does not provide a one-click option to regenerate or replace them in bulk. This is a known product limitation. 🔍 Step 1: Identify the Full Scope of Duplication 1. Navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Open the Internal Linking Opportunities section. 3. Review your deployed suggestions and note which anchor texts appear to be repeated and across how many URLs. 4. Determine whether the duplicates are concentrated on a single target page or spread across multiple targets — this affects which remediation path is most practical. 🚨 Step 2: Escalate to Our Team for Assisted Remediation Because bulk regeneration is not currently available in the platform, and because per-suggestion editing of already-deployed anchor texts is not a confirmed self-serve option at this time, the recommended path for any volume of duplicate anchor text is to contact our team directly. Our team can assess options for assisted remediation based on your specific situation. When you reach out, please have the following information ready to help us assist you faster: - Your project name and the affected domain - The specific anchor text or texts that are duplicated - An estimate of how many URLs or pages are affected - Whether the duplicate suggestions have already been deployed or are still pending - Any relevant timestamps or recent 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.

Fix Duplicate Meta Descriptions in OTTO SEO

When OTTO SEO and another SEO plugin are both configured to write meta descriptions on your WordPress site, your pages may render two tags simultaneously. Search engines like Google read only the first tag they encounter, making your intended description unpredictable in search results. 📋 Why This Happens OTTO SEO deploys meta descriptions through its JavaScript pixel (injected into your site's ) or the Search Atlas WordPress plugin. If a plugin such as Yoast SEO, Rank Math, or All in One SEO is also set to output a meta description, both tags appear in the rendered HTML. Because OTTO's pixel writes to the DOM after page load, the other plugin's server-rendered tag is already present in the raw HTML source — creating a true duplicate every time. 🔧 How to Fix It Choose which tool should own your meta descriptions, then follow the matching steps below. Option A: Let OTTO control meta descriptions 1. Open OTTO SEO and navigate to your project. 2. Go to On-Page fixes and confirm the meta description fix is deployed. 3. In your conflicting plugin, disable meta description output: - Yoast SEO: Go to SEO > Search Appearance and turn off meta descriptions. - Rank Math: Go to General Settings and disable the meta description field. - All in One SEO: Locate the meta description setting under General Settings and disable it. Option B: Let your existing SEO plugin control meta descriptions 1. Open OTTO SEO and navigate to your project. 2. Go to On-Page fixes and locate the meta description fix. 3. Toggle off or undeploy that specific fix so OTTO no longer writes the tag. ⚠️ Important Notes - OTTO does not automatically detect or suppress output from conflicting plugins — the duplicate must be resolved manually. - There is no built-in conflict resolution toggle inside OTTO; the fix requires disabling the duplicate source in one tool or the other. - Rank Math silent override: A known issue exists where Rank Math can silently override OTTO's meta description deployment. If the OTTO dashboard shows a status of Deployed but the wrong description still appears in your page source, Rank Math may be actively overriding OTTO's output despite the deployment indicator. In this case, you must disable the meta description field in Rank Math's General Settings (Option A, step 3) to resolve the conflict. - After making changes, use View Page Source in your browser (not the DevTools inspector) to confirm only one tag appears in the raw HTML. 💬 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 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.

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

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

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

🖼️ Fixing OTTO vs Press Release Image Count

📌 What This Article Covers When you launch a traditional press release, OTTO validates your Knowledge Graph (which OTTO may refer to as your Brand Vault) before the campaign can go live. Sometimes OTTO reports more images than you can see in your Knowledge Graph editor. For example, you may see 3 images on screen while OTTO flags 5. This article explains why that happens and how to reconcile the count so your campaign can launch. 🤔 Why the Image Counts Differ Your Knowledge Graph stores images from several places, and not all of them appear in the main visible gallery. OTTO counts every image record attached to the Knowledge Graph, while the editor usually shows only the primary, visible images. Common reasons for a higher OTTO count include: - Logo and profile images that are stored separately from the main gallery. Logos are also validated for their dimensions when loaded from the Knowledge Graph, so they count as image records even though they sit outside the gallery. - Images pulled from connected sources such as a linked website, social profile, or business listing. - Previously uploaded images that were replaced but not fully removed. - Duplicate entries created when the same image was added more than once. Because these images still exist in the record, OTTO includes them in its total even when they are not shown in the visible gallery. Keep in mind that the press release tool enforces a maximum number of images. If the Knowledge Graph holds more image records than the press release allows, validation will treat it as a blocker and stop the campaign from launching until the extra images are removed. 🔍 How to Review Every Stored Image Follow these steps to see the full list of images OTTO is counting: 1. Open the Knowledge Graph for your project. 2. Enter edit mode so all fields are visible. 3. Scroll through each section, including logo, profile image, and any gallery or media sections. 4. Check any fields linked to connected sources, as these can add images automatically. 5. Compare the total number of stored images against the count OTTO reported. This helps you find the images that are counted but not shown in the main view. 🛠️ How to Align the Image Count Once you have located all stored images, adjust them to match what the press release requires: 1. Remove duplicates: delete any repeated images so each appears only once. 2. Delete outdated images: remove replaced or unused images that are still attached. 3. Stay within the image limit: if OTTO's count is higher than the press release allows, remove the extra records so the total no longer exceeds the maximum. 4. Add missing images: if the press release needs more images, upload high-quality files that represent your brand. 5. Save your changes so the Knowledge Graph updates. After saving, return to OTTO and refresh the validation. The image count should now reflect your updates. 🚀 Relaunching Your Press Release With the counts aligned, you can activate your campaign: 1. Reopen the press release setup. 2. Confirm the image validation now passes. 3. Complete any remaining required fields. 4. Click activate to launch the campaign. If OTTO still reports a mismatch after saving, refresh the page and allow a short time for the Knowledge Graph to sync before trying again. 💡 Tips to Prevent Future Mismatches - Keep only the images you actively use in your Knowledge Graph. - Remove old images instead of leaving them attached when replacing them. - Review connected sources, as they can add images automatically. - Check the full image list before launching any campaign, and confirm it stays within the press release's image limit. 💬 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.

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

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.