Troubleshooting: Deployment & Live Changes

📣 Generate PRs for Non-OTTO Sites With Frozen Accounts

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

🔧 How OTTO Deploys SEO Fixes to Your Site

🔧 Fix WordPress Plugin Disconnect and OTTO Deployment Failures

Overview If your OTTO SEO dashboard is showing a red connection status, or deployed fixes are not rendering on your live site, your WordPress plugin may have lost its connection to Search Atlas. This guide explains what may be happening and what to have ready when you contact our support team so we can resolve the issue as quickly as possible. Common Symptoms - Red indicator next to your WordPress site in OTTO SEO - Fixes marked as deployed but not visible on your live site - Deployment failures that revert to an undeployed state - Error messages related to API key issues - Unable to deploy specific fix types What May Be Causing This WordPress plugin disconnects and OTTO deployment failures can occur for several reasons, including an outdated plugin version, an expired or incorrectly entered API key, or a configuration issue between your WordPress installation and Search Atlas. Because the specific cause varies by account and site setup, our support team will need to investigate your connection directly. How to Escalate This Issue Since this is a bug-category issue that requires backend investigation, please do not attempt to delete and reinstall the plugin without guidance, as this may cause additional data loss. Instead, contact our support team and have the following information ready: - Your site URL — the exact domain connected to OTTO SEO - Your Search Atlas account email - A description of what you see — for example, the exact error message, the color of the status indicator, and which fix types are failing - When the issue started — approximate date and time, and whether anything changed around that time (e.g., a plugin update, WordPress update, or password change) - Your current plugin version — visible in your WordPress admin under Plugins Our team will review your connection status, verify your API key configuration, and push any necessary backend fixes to restore your deployment pipeline. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshoot Missing OTTO Deployments

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

🔧 Fix OTTO Meta Title Deployments

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

⚙️ OTTO Title Tag Deployment and Rollback

🔍 How OTTO title tags work OTTO can recommend and deploy optimized title tags for eligible pages. When deployment is enabled, OTTO adds the configured title to the page through its supported integration. The title shown to visitors and search engines may also be affected by your CMS, SEO plugin, caching, or other site code. 📊 Check the title on your site 1. Identify the affected page and compare its expected title with the title currently shown in the browser tab. 2. View the page source and check the element to see which title is present in the page HTML. 3. Repeat these checks for each affected page, since title behavior can differ between pages. ↩️ Understanding deployment and rollback The available information does not establish a particular control or procedure for disabling OTTO title deployment or rolling it back. Do not assume a specific setting will restore a previous title. The title rendered on a page can depend on the website’s CMS, SEO plugin, theme, custom code, or caching. Check these sources to understand which system is supplying the current title. 🛠️ Troubleshoot the displayed title 1. Check the browser tab title and the page source for the affected page. 2. Review the CMS title field, SEO plugin settings, theme templates, and custom code that may control the title. 3. Clear relevant website, CDN, and browser caches, then check the page again in a private browser window. ✅ Verify the final title Do not rely only on the browser tab. Check both the rendered page and the page source. If the title remains unexpected, review which site systems may be supplying or overriding it. Search engines can display a different title from the one in the page source, so allow time for them to recrawl the page. ⚠️ When the title still looks incorrect A title may remain unchanged temporarily because of browser, website, or CDN caching. Confirm the live HTML first, then allow time for search engines to recrawl the page. Some OTTO recommendations may match the title already on the page or may be treated as no-op recommendations. In that situation, there may be no visible change even though the recommendation is present. Manual title edits and other SEO plugin rules can also override the expected result. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛒 Troubleshooting Shopify SEO Title Deployment

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

🛠️ Fix OTTO Homepage Meta Description Deployment

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

🛠️ Clear a Stale MetaSync Deployment

🔍 When to clear a deployment Use this process when a URL still shows deleted OTTO or MetaSync content, such as an outdated keyword, after you removed the recommendation and cleared your site caches. MetaSync may retain a URL-specific deployment separately from your browser, CDN, or WordPress cache. Clearing those caches alone may not remove the stale deployment. ✅ Check the URL first 1. Open the affected URL in an incognito browser window. 2. Confirm that the response is fresh and not served from a CDN, page cache, or browser cache. 3. View the page source and check whether the outdated HTML is still present. 4. In Search Atlas, confirm that the related recommendation or optimization is deleted or un-deployed. 🧹 Request a targeted cleanup If the deleted content remains in a fresh, uncached response, the MetaSync deployment needs a targeted cleanup for that URL. Open the chat widget in the bottom-right corner of the platform and type human teammate. Share the complete URL and explain that you need the stale OTTO/MetaSync deployment cleared for that URL only. A targeted cleanup removes the stale MetaSync deployment without removing other deployed optimizations on your site. Include the deleted recommendation, the text that is still appearing, and the cache checks you completed. 🔄 Verify after cleanup 1. Wait for the team to confirm that the URL-specific deployment was cleared. 2. Request a new uncached response or use an incognito browser window. 3. Check the page source and rendered page for the deleted content. 4. Confirm that other OTTO or MetaSync optimizations remain active. ⚠️ Important considerations - Do not remove the MetaSync plugin or reset all deployments to resolve a single stale URL. - Purging WordPress, CDN, and browser caches does not necessarily clear MetaSync's own deployment. - If the URL was cloned, redirected, or recently changed, provide the original and current URLs so the deployment can be checked accurately. - For headless WordPress, WPGraphQL, or Next.js setups, mention the architecture when contacting the team because deployment behavior may differ. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Verify OTTO Deployments on WordPress

🔍 What deployment verification confirms Verifying an OTTO deployment helps confirm that changes made in Search Atlas have reached your WordPress website. Depending on your setup, changes may be applied through the OTTO WordPress plugin, a connected CMS sync, or a headless implementation. ⚙️ Check your OTTO installation 1. In Search Atlas, open OTTO SEO from the left sidebar. 2. Select Installation Guide. 3. Review the installation status and confirm that your WordPress site is connected to the correct project. 4. Confirm the OTTO WordPress plugin is installed and active in your WordPress admin area when your setup requires the plugin. Some headless WordPress setups may not show a visible plugin marker in the page source. In those cases, use the live page and deployment checks below instead of relying only on a page marker. 🚀 Confirm the change is published 1. Make or identify a small, specific change in OTTO SEO. 2. Save or publish the change according to the instructions shown in Search Atlas. 3. Wait several minutes, then open the affected page in a private browser window. 4. Compare the live page with the expected result. Check the page title, meta description, canonical URL, headings, or other element changed by OTTO. Use the exact published URL, including the correct protocol and subdomain. Testing a staging, redirected, or different version of the URL can make a successful deployment appear missing. 🛠️ Verify the live HTML To check whether an on-page change is live, open the affected page, view its page source, and search for the expected title, meta description, canonical URL, or other updated content. The browser inspector may show changes created after page load, while page source helps confirm what the server returned. For structured data or other code changes, use a suitable search engine testing tool or inspect the rendered page. Confirm that the result appears on the live URL, not only inside the Search Atlas preview. 🧹 Clear caching before retesting Caching is a common reason a deployment appears not to sync. After publishing, clear or bypass caches at each applicable level: - WordPress caching or optimization plugins - Hosting or server cache - Content delivery network cache - Browser cache Retest in a private browser window after caches are cleared. If the change appears in Search Atlas but not on the live page, compare the page again after cache expiration or request a cache purge from your hosting or CDN settings. 📊 If the change still is not visible 1. Confirm you edited the correct Search Atlas project and target URL. 2. Check that the URL is indexable and is not redirected to another page. 3. Verify that WordPress and the OTTO plugin are connected to the same site. 4. Check whether another plugin, theme, server rule, or CDN is replacing the title, canonical, or other element. 5. Review the page source and record what appears instead of the expected change. Do not repeatedly publish the same change before checking the live HTML and cache layers. These checks help identify whether the issue is installation, deployment, caching, or another WordPress setting. 💬 Get help with a deployment If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Meta Title Deployment

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

🛠️ Fix OTTO GBP Content Publishing Failed Errors

🔍 Overview If you are seeing Content Publishing Failed notifications for one or more of your OTTO-enabled Google Business Profiles (GBPs), you are not alone. This error typically means OTTO was unable to push content to your GBP on Google's side. This article explains the most common causes and walks you through the steps to fix them. ⚠️ Common Causes of Publishing Failures Before diving into fixes, it helps to understand what triggers this error. Publishing failures are almost always caused by one of the following: - Disconnected or expired Google account connection — The OAuth token linking your Google account to Search Atlas has expired or been revoked. - Insufficient Google account permissions — The connected Google account does not have Owner or Manager access to the GBP location. - GBP location suspended or unverified — Google has suspended or flagged the business listing, blocking third-party publishing. - Google API outage or rate limiting — Temporary issues on Google's end can cause batch publishing failures across multiple locations. - Duplicate or policy-violating content — Google rejects posts that contain content that violates its posting policies. 🛠️ Step-by-Step Troubleshooting 1. Check your Google account connection. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). Open OTTO settings and navigate to the connected accounts section. If your Google account shows a warning icon or a Reconnect prompt, click it and complete the OAuth flow to re-authorise the connection. 2. Verify account permissions on Google. Log in to business.google.com and confirm that the Google account connected to Search Atlas is listed as an Owner or Manager for every affected GBP location. Viewer-level access will cause publishing to fail silently. 3. Check the status of each GBP location. In your Google Business Profile dashboard, look for any locations marked as Suspended, Pending verification, or Disabled. OTTO cannot publish to listings that Google has restricted. Resolve any Google-side issues before retrying. 4. Retry the failed publications. After reconnecting your account or fixing permissions, return to Left sidebar → OTTO SEO → SEO Automation and locate the affected GBP tasks. Navigate to Content → Onpage Audit (Onpage Audit) and use the Retry option to trigger a fresh attempt for each failed item. 5. Review the content for policy violations. If only specific posts are failing while others succeed, open the flagged content and check for promotional language, URLs in disallowed fields, or restricted categories. Edit the content to align with Google's content policies and retry. 6. Wait and retry during a Google outage. If all GBPs failed at the same time and your connection looks healthy, the issue may be a temporary Google API disruption. Wait 30–60 minutes, then retry the publications. ✅ How to Confirm the Issue Is Resolved After completing the steps above, publishing is confirmed as working when: - The Content Publishing Failed notification no longer appears for the affected locations. - New OTTO-generated posts appear live on your GBP listings within the expected publishing window. - The OTTO task status in OTTO SEO shows Published or Completed rather than Failed. 🔄 Preventing Future Publishing Failures To minimise the chance of this error recurring, keep the following best practices in mind: - Re-authorise your Google account connection every time you change your Google password or revoke app permissions. - Ensure the connected Google account always retains Owner or Manager access to all GBP locations managed by OTTO. - Monitor your GBP listings in Google Business Profile regularly for verification or suspension notices. - Avoid bulk-scheduling large volumes of posts during known Google maintenance windows. 💬 Still Need Help? If you have followed all the steps above and are still seeing Content Publishing Failed errors, our team is ready to investigate further. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Image Validation Errors: Minimum size 400×300px, max 5MB, JPG/PNG only (no GIF/WebP/HEIC). Images must not contain watermarks or overlaid text covering >10% of image. Fix: open affected GBP content settings in Otto, remove/replace non-compliant image, re-trigger publishing.

🤖 OTTO Deployment, Lucky Button & Dynamic Indexing

🤖 What Is OTTO and How Does Deployment Work? OTTO is Search Atlas's AI-powered SEO automation engine. It audits your site, identifies technical SEO opportunities, and generates fixes — including meta descriptions, title tags, heading structures, schema markup, and more — directly from the platform. OTTO follows a review-then-deploy workflow by default. This means every suggested fix is presented to you for review before it goes live on your site. You stay in control at every step. ✅ How to Review and Deploy OTTO Recommendations 1. Go to OTTO SEO in the left sidebar, then open SEO Automation (or navigate to /seo-automation-v3). 2. Connect your site to OTTO if you haven't already, and complete the initial site audit. 3. Browse the generated recommendations grouped by category (e.g., Meta Tags, Headings, Schema). 4. Review each suggestion — you can edit the AI-generated content before deploying. 5. Select individual fixes or use bulk selection to deploy multiple items at once. 6. Navigate to Local → My Tasks (My Tasks) and click Deploy all changes to push approved changes live to your site. Changes are only applied to your site after you explicitly approve and deploy them. OTTO will never publish updates without your confirmation unless you use the I'm Feeling Lucky feature described below. 🍀 How Does the "I'm Feeling Lucky" Button Work? The I'm Feeling Lucky button is an optional one-click deployment shortcut designed for users who want to move fast and trust OTTO's recommendations without reviewing each item individually. Here is exactly what it does: - Skips the manual review step — OTTO automatically selects and deploys all high-confidence recommendations in a single action. - Applies changes immediately — fixes go live on your site as soon as you confirm the prompt. - Covers all eligible fix types — meta descriptions, title tags, heading tags, and other supported elements are all included in the batch deployment. Important: Before using I'm Feeling Lucky, we recommend completing at least one manual review cycle so you are familiar with the types of changes OTTO makes on your site. You can always roll back individual deployed items from the OTTO dashboard if needed. 📋 Can OTTO Generate Technical SEO Elements Automatically? Yes. OTTO can automatically generate a wide range of on-page and technical SEO elements, including: - Meta descriptions — unique, keyword-aligned descriptions for every page. - Title tags — optimised titles based on your target keywords and page content. - Heading structures (H1–H6) — logical heading hierarchies to improve readability and crawlability. - Schema markup — structured data to enhance search result appearance. - Canonical tags, alt text, and more — depending on your connected site and plan. All generated elements are AI-drafted and editable. You have full control to modify any suggestion before it is deployed, whether you deploy items one at a time or in bulk. 🔍 Where Is Dynamic Indexing and Can I See It? Dynamic Indexing is a feature within OTTO that helps search engines discover and index your pages faster by managing crawl signals and sitemap updates automatically. Currently, Dynamic Indexing status and activity are visible under Authority → Indexer (URL Indexer) in the left sidebar. From this view you can: - See which pages have been submitted for indexing and when. - Monitor indexing request status (submitted, indexed, pending). - Identify pages that may need attention due to crawl or indexing issues. Note: If the Dynamic Indexing tab is not visible in your dashboard, make sure your OTTO project is fully set up along with any connected indexing services. 💡 Quick Reference: OTTO Deployment Modes - Manual review mode (default): You review each recommendation and click Deploy when ready. Full control, no surprises. - I'm Feeling Lucky (bulk auto-deploy): OTTO deploys all high-confidence fixes in one action. Best for experienced users who trust the AI output. - Dynamic Indexing: Runs automatically in the background once enabled; status is visible in your OTTO dashboard. 🛠️ Troubleshooting Common Issues - Recommendations not appearing: Make sure your site audit has completed. Large sites can take a few minutes to fully process. - Deploy button greyed out: Check that OTTO is fully connected to your site and that your plan includes deployment for the selected fix type. - Dynamic Indexing tab not visible: Make sure your OTTO project is fully set up along with any connected indexing services. - Changes not reflecting on site: Allow a few minutes after deployment. Some changes depend on your CMS cache clearing — try purging your site cache. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes Generation vs. Deployment distinction: Generation analyzes pages and produces suggestions automatically once OTTO is connected — no live changes at this stage. Deployment is a separate step where you approve and push changes. Also explicitly lists: H1, H2/H3 headings, image alt text as generated elements.

🔧 OTTO Deployed Fixes Not Showing on Your Site

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

📋 Understanding OTTO Recommendation Persistence After Deployment

🔍 Overview When you manually implement an OTTO recommendation, you might expect it to disappear from your list automatically after the next analysis runs. However, OTTO is designed to keep recommendations visible indefinitely until you explicitly remove them. This article explains how recommendation persistence works and how to manage your list effectively. ⚙️ How OTTO Recommendation Persistence Works OTTO surfaces SEO recommendations based on analysis of your site. Once a recommendation appears in your list, it will remain there regardless of whether you have already deployed it. There are two important points to understand: - Deploying a recommendation does not remove it automatically. After you manually implement a fix, the recommendation stays in your list until you take action to dismiss it. - Running a new analysis does not clear deployed recommendations. Re-analysis updates the findings on your site but does not trigger automatic removal of existing recommendations from the list. This behavior is intentional. OTTO retains deployed recommendations so you always have a clear record of what changes were suggested and when you acted on them. 🗑️ How to Remove a Recommendation Manually Once you have implemented a recommendation, you can remove it from your list at any time. Follow these steps: 1. In the left sidebar, navigate to OTTO SEO and open SEO Automation (URL: /seo-automation-v3). 2. Locate the recommendation you have already deployed. 3. Select the recommendation to open its detail view. 4. Use the Dismiss or Mark as Done option to remove it from your active list. Removing a recommendation from the list does not undo any changes you have made to your site. It simply clears the item from your OTTO recommendation queue. 📌 Why Recommendations Persist by Design OTTO keeps suggestions visible after deployment for several practical reasons: - Audit trail. You can review everything OTTO suggested and confirm which items your team has addressed. - Avoiding duplicate work. If a recommendation is still visible, team members know it exists and can verify the implementation status before acting. - Manual control. You decide when a recommendation is truly resolved and ready to be cleared, rather than relying on automated removal that could dismiss items prematurely. ❓ Common Misconceptions Does crawl frequency affect when recommendations are removed? No. Crawl schedule and re-analysis do not control recommendation removal. New crawls update your site data and may surface new recommendations, but they will not remove existing ones from your list. Will a recommendation reappear if the issue returns after I dismiss it? No. Once a recommendation is dismissed or ignored, OTTO skips it in later crawls and does not suggest it again. ✅ Best Practices for Managing Your Recommendation List - After implementing a fix, immediately dismiss the corresponding recommendation to keep your list accurate and actionable. - Use the recommendation list as a running checklist — review it regularly with your team to track outstanding versus completed items. - Do not rely on re-analysis to clean up your list. Make manual dismissal part of your standard deployment workflow. 💬 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.

🔍 Recovering a Deep-Frozen Site in OTTO SEO

🧊 What Is a Deep Freeze in OTTO SEO? A deep freeze pauses all active SEO automations for a site and removes it from your active site list in OTTO SEO. Unlike a standard freeze, a deep freeze is designed for long-term suspension, which is why the site no longer appears in your normal view after it is applied. This is expected behaviour — the site has not been deleted, but it does require a specific recovery pathway to bring it back. ⚠️ Why You Can't See the Site Anymore When a site is manually deep frozen, OTTO SEO moves it out of the default site list to prevent accidental edits. If you are looking for the site in your main list and it is not there, this is the most likely reason. The site still exists in your account and can be recovered by our support team. 🔄 How to Recover a Deep-Frozen Site Because the recovery process requires backend access to restore deep-frozen sites, this action needs to be completed by our support team. You can find your deep-frozen sites under the Deep Frozen tab in OTTO SEO → All Sites. To get your site unfrozen as quickly as possible, please have the following details ready before reaching out: - The exact domain of the deep-frozen site (for example, bestfitdigital.co). - The approximate date the deep freeze was applied, if known. - The name of the Search Atlas account or workspace the site belongs to. Do not attempt to re-add the site manually — doing so may create a duplicate entry and could affect your historical data and automation history. ✅ After Unfreezing — What to Check - Confirm the site now appears in your OTTO SEO → All Sites (SEO Automation) list with an Active status. - Review your automation settings to make sure they are configured as expected. A deep freeze preserves your settings, but it is good practice to verify them after restoring. - Check that any scheduled tasks or pending optimisations are queued correctly and running. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Fix OTTO Script Deployment Not Appearing on Website

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

🚀 How OTTO Deploys SEO Changes to Your Site

🧠 Understanding How OTTO Deploys Changes OTTO does not modify your website's back-end code, database, or CMS files. Instead, it uses a front-end overlay method to inject SEO changes — including schema markup, meta titles, and meta descriptions — directly into your pages at the browser level. This means: - Your CMS (WordPress, Shopify, Webflow, etc.) will not show any changes in its editor or post settings. - The changes are not written into your HTML source files on the server. - Changes are applied in real time when a page is loaded in a browser, via the OTTO script installed on your site. This is expected behaviour, not a bug. The overlay approach allows OTTO to deploy and update SEO elements instantly, without requiring developer access or CMS edits. ✅ What You Need for Deployment to Work Before OTTO can deliver any changes to your site's visitors and to search engines, two conditions must be met: 1. The OTTO script must be installed on your website. Without this script, the overlay cannot load and no changes will appear. 2. OTTO must be activated for the relevant pages or site. Optimisations are only deployed to pages where OTTO has been switched on. To check or complete your script installation, navigate to the OTTO SEO section of the platform and follow the installation instructions provided for your platform. 🔍 How to Verify Your Changes Are Live Because OTTO's changes are not visible inside your CMS, you need to verify them directly in the browser. Use one of the following methods: Method 1: Browser Developer Tools (Recommended) 1. Open the published page on your website in a browser (Chrome or Firefox recommended). 2. Right-click anywhere on the page and select Inspect (or press F12). 3. Click the Elements tab. 4. Use Ctrl+F (or Cmd+F on Mac) to search for your meta title, meta description, or schema markup text. 5. If OTTO is active and the script is installed, your deployed values will appear inside the <head> section of the rendered page — even though they are absent from your CMS. Method 2: Google's Rich Results Test 1. Go to https://search.google.com/test/rich-results. 2. Enter the full URL of the page you want to check. 3. Run the test. Google's tool renders the page the same way a browser does and will detect OTTO-injected schema markup. Method 3: View Rendered Page Source 1. Open the page in Chrome. 2. In the address bar, type view-source: before the URL and press Enter. 3. Note: this shows the raw server HTML and will not include OTTO's overlay changes — use Method 1 or Method 2 to confirm live deployment instead. If your changes are not appearing after confirming the script is installed and OTTO is activated, please have the following ready when you reach out: your project name, the specific URLs affected, and a description of which elements (schema, meta title, meta description) are not showing as expected. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗑️ OTTO Site Removal vs Deep Freeze Billing

🔍 Overview When you stop using OTTO on a site, you have two options: Deep Freeze and Remove. These work very differently — one pauses OTTO activity while the recurring top-up charge continues, and the other permanently deletes the project. In both cases, the OTTO top-up (add-on) keeps billing on its normal cycle until you cancel it separately. Understanding the distinction helps you avoid unexpected charges and know exactly what happens to the fixes OTTO already deployed. ❄️ What Is Deep Freeze? Deep Freeze pauses all active OTTO automation on a site without permanently deleting it. Here is what happens when you Deep Freeze a site: - Automation is turned off and the project becomes read-only — no new scans run and no automation quota is used. - The project's OTTO site slot is released automatically after a 14-day hold period. - The recurring OTTO top-up (add-on) charge is NOT cancelled by freezing — it keeps billing on its normal cycle until cancelled separately. - Pixel-served changes stop showing while the site is frozen because the OTTO pixel no longer serves OTTO's changes; any changes written directly into your CMS remain in place. - You can reactivate the site within the 14-day window without losing your project data. Use Deep Freeze when you want a temporary pause and plan to return to active optimization soon. 🗑️ What Is Remove? Remove permanently deletes the OTTO project for that site. Here is what happens when you remove a site: - The project is deleted immediately and permanently — it cannot be recovered. - The OTTO slot is released and becomes available for a new site. - The recurring OTTO top-up (add-on) charge is not cancelled automatically by removing a site. To stop it, cancel the top-up in the dashboard at Profile avatar → Billing → Services → ⋮ menu on the top-up → Cancel, or ask support. - Any optimizations OTTO wrote directly into your CMS (for example through the WordPress plugin) remain on your site. Pixel-served changes, however, stop showing once the OTTO project is deleted or the pixel is removed. Use Remove when you no longer need OTTO on that site, then cancel the top-up separately to stop charges. 📊 Side-by-Side Comparison - Deep Freeze — Billing: The recurring top-up charge continues on its normal cycle until cancelled separately. - Deep Freeze — Project data: Preserved; site can be reactivated within the 14-day hold period. - Deep Freeze — Deployed fixes: Pixel-served changes stop showing while frozen; CMS-written changes remain in place. - Deep Freeze — OTTO activity: Automation off; project is read-only; no scans run and no automation quota is used. - Remove — Billing: The recurring top-up charge continues until cancelled separately in Billing → Services or via support. - Remove — Project data: Permanently deleted; cannot be restored. - Remove — Deployed fixes: CMS-written changes remain; pixel-served changes stop showing once the project is deleted. - Remove — OTTO activity: Ends permanently. ⚙️ What Happens to Deployed Optimizations After Removal? A common concern is whether removing a site will undo all the SEO work OTTO performed. It will not. OTTO applies most changes through the OTTO pixel script at page load. If the pixel is removed or the OTTO project is deleted, pixel-served changes stop showing on the site. Changes that were written directly into the site's CMS (for example through the WordPress plugin) can remain in place. If you want to reverse any specific CMS-written change, you would need to do so manually through your CMS or website editor. 🚀 How to Remove an OTTO Site 1. Open OTTO SEO → All Sites (SEO Automation) from the left sidebar. 2. Locate the site you want to remove. 3. Click the options menu next to the site name. 4. Select Remove and confirm the action when prompted. Removing the site does not cancel the recurring OTTO top-up charge — you must cancel the top-up separately at Profile avatar → Billing → Services → ⋮ menu on the top-up → Cancel, or by asking support. 💳 Cancelling the OTTO Top-Up After Removal Because removing (or freezing) a site does not automatically cancel the recurring OTTO top-up, you need to cancel it yourself: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing. 3. Open the Services tab, find the OTTO top-up, click the ⋮ menu, and choose Cancel. You can also ask support to cancel it for you. 💡 Which Option Should You Choose? - Choose Deep Freeze if you need a short break but want to keep your project data and return within the 14-day hold period. Remember to cancel the top-up separately if you also want billing to stop. - Choose Remove if you are done with OTTO on that site, and cancel the top-up separately to stop the recurring charge. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Title Tag Changes Not Showing on Google

🧭 Overview After deploying a title tag change, it is completely normal for the update to not appear immediately in Google's search results. This delay is caused by how Google crawls, processes, and caches web pages — not by a problem with your website or Search Atlas. This article explains why the delay happens and what steps you can take to encourage faster indexing. ⏱️ Why the Delay Happens When you update a title tag and deploy it to your live site, Google does not instantly detect the change. Here is what happens behind the scenes: - Crawl scheduling: Googlebot visits pages on its own schedule, which varies based on your site's crawl budget, authority, and how frequently it typically updates. - Processing and indexing: After Googlebot crawls the updated page, it must process the new content and update its index. This takes additional time. - Cache refresh: Even after the index is updated, Google's Search Engine Results Pages (SERPs) may still display a cached version of the old title for a short period. - Google's own rewriting: Google sometimes rewrites title tags to better match a user's search query. If you see a different title than what you set, Google may have overridden your tag — this is separate from indexing latency. In most cases, title tag updates are reflected in Google search results within a few days to a few weeks. For high-authority or frequently crawled sites, this can happen within 24–48 hours. For newer or lower-traffic sites, it may take longer. ✅ Steps to Encourage Faster Indexing While you cannot force Google to index your changes immediately, the following steps can help speed up the process: 1. Verify the change is live on your website. Before troubleshooting further, confirm that the updated title tag is actually present in your page's HTML. Right-click the page in your browser, select View Page Source, and search for the <title> tag. Make sure the new title appears there. 2. Submit the URL for indexing via Google Search Console. Open Google Search Console, paste your page URL into the top search bar, and click Request Indexing. This signals to Google that the page has been updated and should be recrawled. Note that this is a request, not a guarantee, and Google may take additional time to process it. 3. Check for crawl errors. In Google Search Console, review the Coverage or Pages report to ensure your page is not blocked by a noindex tag, robots.txt rule, or crawl error that would prevent Googlebot from seeing the update. 4. Ensure your sitemap is up to date. An updated XML sitemap helps Googlebot discover changed pages faster. Resubmit your sitemap in Google Search Console under Sitemaps if needed. 5. Build or refresh internal links to the page. Pages with more internal links tend to be crawled more frequently. Linking to the updated page from other active pages on your site can help Googlebot find it sooner. 📊 Monitoring Your Rankings in Search Atlas While waiting for Google to reflect your title tag change, you can monitor your page's ranking performance directly inside Search Atlas: - Go to Left sidebar → Keywords → Rank Tracker to track keyword positions for the page you updated. Rankings may shift as Google re-evaluates the page with the new title. - Use Left sidebar → Keywords → Keyword Magic to identify whether your new title tag is better aligned with the keywords your target audience is searching for. - Use Left sidebar → Keywords → Keyword Gap to compare your keyword coverage against competitors and validate that your title tag strategy supports your broader SEO goals. ⚠️ When to Be Concerned In most situations, waiting is the right approach. However, consider investigating further if: - More than 4 weeks have passed and the updated title still has not appeared in search results. - Google Search Console shows the page is not indexed or has a coverage error. - The title showing in the SERP is completely unrelated to either your old or new title tag — this may indicate a deeper on-page or structured data issue. 💡 Key Takeaways - Title tag changes are not reflected in Google search results instantly — this is normal and expected. - The typical timeframe is a few days to a few weeks depending on your site's crawl frequency. - Use Google Search Console's Request Indexing tool to signal your update to Google. - Search Atlas's Rank Tracker and Keyword tools can help you monitor ranking impact once the change is 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.

🛠️ Troubleshooting OTTO SEO Deployments Not Reflecting in Shopify

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

🔧 Fix OTTO Scan Pending Tasks and Deployment Failures

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

🔧 Fix OTTO Deployments Causing Wrong Link Redirects

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

🛍️ How to Confirm Deployed Changes Reach Shopify

This article explains exactly what happens when you click deploy in Search Atlas, and how to confirm that your changes have actually been written to your Shopify store — not just saved within the platform. If you have been unable to locate the integration settings or are unsure whether your updates went live, the steps below will help you verify both. 🔍 Common Causes of Confusion - 'Deployed' within Search Atlas vs. live on Shopify: In Search Atlas, a 'deployed' status means the platform has sent the changes to your connected Shopify store. It does not simply mean the changes were saved or staged inside Search Atlas. However, the update only appears live on Shopify if the integration is active and authenticated correctly at the time of deployment. - Broken or disconnected integration: If the Shopify connection was disconnected, re-authenticated, or the access token expired after you deployed, the changes may show as deployed in Search Atlas but never reached Shopify. - Propagation delay: Shopify may take some time to reflect metadata or content changes after a successful push. 🛠️ Step-by-Step 1. Open your project settings in Search Atlas and navigate to the integrations or connected apps section for your site. Locate your Shopify connection and confirm its status is active and authenticated — if it shows any error or requires re-authentication, that is likely why your changes did not reach Shopify. 2. If the connection requires re-authentication, reconnect your Shopify store by following the on-screen prompts before attempting to deploy again. 3. Once the integration is confirmed active, return to the page or content item you deployed and review its current deployment status inside Search Atlas to determine whether the push completed successfully or encountered an error. 4. If a previous deployment shows a failed or partial status, re-deploy the affected pages or content items while the Shopify integration is confirmed active. 5. After deploying, allow some time for Shopify to process the incoming changes before checking the result. ✅ How to Confirm It Worked - Check Shopify directly: Log in to your Shopify admin, navigate to the affected product, page, or blog post, and confirm the updated title, meta description, or content is visible there. This is the definitive confirmation that the change reached Shopify — not the status inside Search Atlas alone. - Check the deployment status inside Search Atlas: The item should display a status indicating the deployment completed. A status that appears stuck or shows an error indicates the push did not complete successfully. - Visit the live URL: Open the published Shopify URL in a browser and verify the updated content appears as expected on the live page. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

☁️ Fix Cloudflare Deployment Lag and Rank Tracker Setup

🔍 Overview When deploying OTTO SEO optimizations across multiple CDN and hosting providers, most providers go live within minutes. Cloudflare, however, can sometimes remain in an Awaiting status even after all other providers have successfully deployed. This article explains why this happens, what you can do about it, and how to continue tracking your keyword rankings in the meantime. ☁️ Why Cloudflare Shows 'Awaiting' Status Cloudflare operates its own global edge network with strict API rate limits and propagation rules. Unlike traditional hosting providers, Cloudflare requires an additional verification and token handshake before OTTO SEO can push changes through its API. The most common reasons for an Awaiting status are: - API token permissions: The Cloudflare API token connected to your Stack may be missing the required zone-level edit permissions. - Cache propagation delay: Cloudflare's edge nodes can take longer than standard hosts to register and confirm new deployments. - Zone ID mismatch: If the domain was recently migrated or re-added to Cloudflare, the Zone ID stored in your Stack may be outdated. - Rate limiting: High-volume domains with frequent deployments may temporarily hit Cloudflare's API rate limits, causing queued requests to stall. In the case of Stack ID 24055 for hugehealthfitness.com, the 13 other providers deploying successfully confirms the issue is isolated to the Cloudflare connection itself, not your overall Stack configuration. 🛠️ Steps to Resolve the Awaiting Status 1. Verify your Cloudflare API token. Log in to your Cloudflare dashboard, navigate to My Profile → API Tokens, and confirm the token assigned to your domain has Zone:DNS:Edit, Zone:Zone:Read, Workers Scripts:Edit, Workers Routes:Edit, and Workers KV Storage:Edit permissions enabled. 2. Confirm the correct Zone ID. In Cloudflare, go to your domain's Overview page and copy the Zone ID from the right-hand panel. Compare this to the Zone ID stored in your OTTO SEO Stack settings and update it if they differ. 3. Re-authenticate the Cloudflare connection. Inside the platform, navigate to your Stack settings, disconnect the Cloudflare integration, and reconnect it using your updated API token. This forces a fresh handshake. 4. Trigger a manual re-deploy. After reconnecting, select the affected Stack and click Re-deploy for the Cloudflare provider. Monitor the status over the next 5–15 minutes. 5. Wait for propagation if status remains. If the status updates to Processing after re-deploying, allow up to 30 minutes for Cloudflare's edge network to fully propagate the changes before checking again. 📊 Track Your Keyword Rankings While You Wait A Cloudflare deployment delay does not affect your ability to monitor keyword performance. You can set up or review your Rank Tracker at any time using the steps below. 1. In the left sidebar, click Keywords, then select Rank Tracker (Keyword Rank Tracker). 2. If you have not yet added keywords for your domain, click Start Tracking and enter the target terms you want to monitor for hugehealthfitness.com. 3. Select your target location, device type (desktop or mobile), and search engine, then click Save. 4. Rankings will begin populating within 24 hours. Return to Keywords → Rank Tracker at any time to view position history, changes, and trend data. To discover additional keyword opportunities while your Cloudflare deployment completes, go to Keywords → Keyword Gap to compare your domain against competitors, or use Keywords → Keyword Magic to expand your target keyword list. ✅ How to Confirm Cloudflare Is Successfully Deployed Once the issue is resolved, the Cloudflare provider card in your Stack will update from Awaiting to Live. You can verify this by opening your Stack in OTTO SEO and reviewing the provider status list. All providers, including Cloudflare, should display a green Live badge when deployment is complete. 💡 Tips to Prevent Future Delays - Use a dedicated Cloudflare API token for OTTO SEO rather than a global account token — this reduces the risk of permission conflicts. - Avoid making simultaneous bulk changes in both Cloudflare's dashboard and OTTO SEO, as competing API calls can cause queuing delays. - If your domain's nameservers or Cloudflare plan change, re-authenticate the integration in your Stack settings as soon as possible to keep the Zone ID current. 🙋 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 Deployment: Live Site vs. Builder Updates

Overview OTTO applies SEO changes—including heading optimizations, meta updates, and structured data—directly to your live website via script injection. This is intentional: it lets changes go live instantly without waiting for a full rebuild. However, because OTTO writes changes to the live DOM rather than editing your website builder's source files, your builder interface (e.g., WordPress block editor, Webflow, Wix) will not reflect those changes automatically. This article explains the full workflow, how to sync manually, and what to expect from GSC integration and automated keyword research within OTTO. How OTTO Deploys Changes to Your Live Site When you deploy an optimization through OTTO, the change is pushed through the Search Atlas script installed on your site. This script modifies your page's rendered HTML in real time. As a result: - Changes appear on your live site immediately after deployment. - Search engines crawl and index the updated content. - Your website builder's editor still shows the original, pre-OTTO content because the builder reads from its own source database, not the rendered live page. Think of it as a layer sitting on top of your builder. OTTO's layer is what visitors and search engines see; the builder layer is your internal editing environment. The two do not sync automatically. How to Manually Sync Builder Changes After OTTO Deployment To keep your builder consistent with what OTTO has deployed—especially if you plan to edit or rebuild pages later—follow these general steps: 1. In Search Atlas, navigate to the OTTO section and locate the relevant project and page. 2. Review the optimizations that OTTO has deployed for that page, including any heading, title, or content changes. 3. Open your website builder and navigate to the same page. 4. Manually replicate each change—update headings (H1, H2, H3), meta titles, and descriptions to match what OTTO deployed. 5. Save and publish the page in your builder. 6. If you want the builder to serve the content natively going forward, undeploy the corresponding OTTO change to avoid conflicts. Important: Do not edit the same element in your builder without first undeploying OTTO's version. Conflicting edits can cause the builder's republish to overwrite OTTO's live changes. Connecting Google Search Console for OTTO Integration OTTO works alongside your connected Google Search Console (GSC) property to inform its SEO suggestions. To ensure OTTO has the data it needs, you should verify your GSC property is properly connected to your Search Atlas project. Without a verified GSC connection, OTTO may not be able to pull site performance data or fully populate entity and topical information for your project. To connect GSC: 1. Go to your project settings in Sear If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Fix OTTO SEO Changes Not Showing on Google

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

🛠️ Troubleshooting Deployed Changes Not Reflecting in Shopify

This article explains the difference between a change being deployed within Search Atlas and that change being written to your live Shopify store — and walks you through what to check if your storefront has not updated after a deployment. 🔍 What Does 'Deployed' Actually Mean? In Search Atlas, deploying a change marks it as approved and ready to be pushed to your connected platform. However, deployment within Search Atlas does not always mean the change has been instantly written to Shopify. The two stages are distinct: - Deployed in Search Atlas: The change has been confirmed and queued on the Search Atlas side. - Written to Shopify: The change has been successfully transmitted to and accepted by your Shopify store via the integration. If your Shopify storefront does not reflect the change, it most likely means the write to Shopify is pending, failed silently, or the integration requires attention. 🛠️ Step-by-Step 1. Confirm the deployment status inside Search Atlas. Open the relevant project or optimization task and look for a status indicator next to the deployed item. A status such as "Deployed" or "Published" on the Search Atlas side confirms it was queued — but does not confirm Shopify received it. 2. Check whether your Shopify integration is active and authenticated. Open your project settings and navigate to the integrations or connected platforms area. Verify that your Shopify store is still connected, that the access token has not expired, and that no disconnection notice is shown. 3. Re-authorize the integration if needed. If the connection shows as expired or disconnected, follow the prompts to reconnect your Shopify store. After reconnecting, attempt to redeploy the change. 4. Redeploy the specific change. Once you have confirmed the integration is healthy, locate the item that was previously deployed and use the available option to push or redeploy it to Shopify. This forces a fresh write attempt. 5. Allow propagation time. After a successful write, Shopify may take a few minutes to reflect meta field updates, title or description changes, or other on-page edits depending on your store's cache and theme settings. Wait at least 5 minutes before concluding the change did not apply. ✅ How to Confirm It Worked To verify that your changes have been successfully written to Shopify — not just deployed in Search Atlas — check the following: - Visit the affected product, collection, or page directly in your Shopify admin and confirm the updated title, meta description, or content field matches what you deployed from Search Atlas. - Open the live URL of the affected page in a browser (use an incognito window to bypass cache) and inspect the page source or use a browser extension to confirm the updated meta tags are present in the HTML. - If Search Atlas shows a post-deployment status update (such as a confirmation timestamp or a "Synced" indicator), that is the most reliable signal that the write to Shopify completed successfully. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes When escalating to support, have ready: your project name, the specific URL(s) of affected Shopify pages/products/collections, the exact status shown in Search Atlas (e.g., Deployed, Pending), and any error messages received. Also: check the specific resource directly in Shopify admin to verify if SEO field values are present.

🛠️ Fix OTTO Duplicate Scripts and Intermittent Deployments

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

🛠️ Fix Knowledge Base Trust FAQ Deployment Errors

🔍 Overview When deploying your Knowledge Base Trust FAQ schema, you may encounter a deployment error that reads something like "questions should have answers" — even when all your visible Q&A pairs appear to be fully filled in. This article explains why this error occurs and how to resolve it quickly. ⚠️ Why This Error Happens The "questions should have answers" error is a schema validation failure. It does not mean that your completed Q&A entries are incorrect. It means that one or more empty Q&A slots exist in your deployment set alongside your filled entries. This is a common source of confusion: the platform may display 8 completed Q&A pairs, but if additional blank slots are present in the same deployment set — even if they appear empty or unused — the schema validator treats them as incomplete entries and blocks deployment. Common reasons empty slots appear: - Extra rows were added while building out Q&As and left blank. - A Q&A entry was partially started (e.g., a question was typed but no answer was saved) and then abandoned. - Slots were duplicated accidentally during editing. ✅ How to Fix the Error 1. Navigate to OTTO SEO → Knowledge Base in the left sidebar of your Search Atlas dashboard. 2. Open the FAQ deployment set that is producing the error. 3. Scroll through all Q&A slots — including those below your completed entries — and look for any rows where the question, the answer, or both fields are empty. 4. Select each empty slot and click Delete to remove it entirely. Do not leave any blank rows in the set. 5. Once all empty slots have been removed, save your changes. 6. Attempt deployment again. The schema validator should now pass without errors. 💡 Tips to Prevent This Error in Future - Only create a new Q&A slot when you are ready to fill it in completely. Avoid saving partial entries. - Before every deployment, do a quick scroll to confirm no empty rows exist below your last completed Q&A pair. - If you need a placeholder while drafting content, write a temporary answer so the slot is never truly empty. - After deleting a Q&A, check that the slot itself is also removed — not just cleared of its content. 🚫 What This Error Is Not It is important to note that this error is not related to Google Business Profile publishing. The Knowledge Base Trust FAQ schema is a separate feature and workflow. If you have seen guidance suggesting this error is connected to Google Business Profile, that information is incorrect. This error is caused exclusively by empty Q&A slots within the FAQ schema deployment set, and is resolved by deleting those slots as described above. 🙋 Still Seeing the Error? If you have deleted all empty slots and the error persists, it is possible a hidden or cached slot is still being detected by the validator. Try the following: - Refresh the page and reopen the FAQ deployment set before attempting deployment again. - Check whether any Q&A entry has a question filled in but is missing a saved answer (or vice versa) — both fields must be fully completed and saved. - If the error continues after these steps, our team can inspect the deployment set 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.

⚡ OTTO SEO Bulk Deployment for Large Page Counts

Overview When deploying OTTO SEO recommendations across a large site with many pages, the process may take longer than expected or appear to stall. This article explains what to keep in mind when running bulk deployments at scale and how to get the right support if you run into issues. What to Know About Large-Scale OTTO SEO Deployments Deploying OTTO SEO recommendations across a high page count (for example, 100 or more pages) can be resource-intensive. If your deployment appears slow, unresponsive, or incomplete, this is often related to the volume of pages being processed at once rather than an error in your setup. To reduce the risk of issues during large deployments, consider the following general guidance: - Deploy in smaller groups: Rather than attempting to deploy all pages at once, work through your pages in smaller groups to give the system time to process each set before moving on. - Allow time between deployments: Wait for one group to finish processing before starting the next. Triggering multiple large deployments simultaneously can cause delays or incomplete results. - Review results after each group: After each deployment group completes, check that the pages reflect the expected changes before continuing. When to Contact Support Because the optimal batch size, available deployment controls, and expected processing times depend on your specific site configuration and account setup, our support team can review your project directly and provide tailored guidance for your situation. When reaching out, please have the following ready to help us assist you faster: - Project or website name as it appears in your Search Atlas account - Total number of pages you are trying to deploy - Description of what you are seeing — for example, whether the deployment appears stuck, returns an error, or completes but shows unexpected results - Any error messages displayed on screen, including exact wording - Approximate time and date when the issue 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.

🛠️ How to Confirm OTTO SEO Changes Deploy to Shopify

When OTTO SEO marks a change as deployed, it means the change was pushed from Search Atlas toward your connected Shopify store — but the word alone does not confirm that Shopify accepted and saved the update. This article explains the distinction, walks you through verifying a successful write to Shopify, and tells you exactly what to check when a deployed change does not appear on your storefront. 🔍 What "Deployed" Actually Means Search Atlas uses deployed to indicate that the change has been sent through the integration. Whether that change is visible in Shopify depends on two additional conditions being true: the Shopify connection must be active and authenticated at the moment the change is pushed, and Shopify must have accepted the write without an API error. A status of deployed reflects the outbound action from Search Atlas — not a confirmed receipt from Shopify. 🛠️ Step-by-Step 1. Check your Shopify connection status. Open your project settings and look for the Shopify integration section. Confirm the store URL is correct, the access token has not expired, and the connection shows as active. A disconnected or re-authenticated store will silently drop pushes. 2. Re-verify the specific change in Shopify directly. Log in to your Shopify admin, navigate to the product, page, collection, or blog post that was updated, and inspect the field that OTTO SEO targeted (meta title, meta description, or on-page content). Compare what is in Shopify with what Search Atlas shows as the deployed value. 3. Check for Shopify theme or app conflicts. Some Shopify themes and third-party SEO apps override meta fields at render time. Even if Search Atlas successfully wrote the value, another app may be outputting its own value. Temporarily disable conflicting apps and preview the page source to confirm which value Shopify is serving. 4. Review the deployment log for errors. In your OTTO SEO project, open the activity or deployment history for the affected page. Look for any error flag, API timeout notice, or partial-success indicator next to the deployed item. If an error is logged, reconnect your Shopify integration and re-deploy the change. 5. Re-deploy the change manually if needed. If the value in Shopify does not match what Search Atlas deployed, use the re-deploy or re-publish action on the individual optimization to trigger a fresh write attempt after confirming the connection is healthy. ✅ How to Confirm It Worked A deployment is confirmed successful only when all three of the following are true: - Shopify admin matches: The field value in your Shopify admin (e.g., the SEO title or description on the product or page edit screen) exactly matches the value Search Atlas deployed. - Live page source matches: Right-click your Shopify storefront page, select View Page Source, and search for the <title> tag and og:description or meta name="description" meta tag. The rendered values should match what was deployed. - No override is active: No other Shopify app or theme snippet is replacing the value that Search Atlas wrote. If the Shopify admin shows the correct value but the live page does not, the issue is a theme or app override — not a failed deployment. If the Shopify admin still shows the old value, the write did not complete and the steps above should be repeated after reconnecting the integration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🖼️ OTTO Alt Text Deployment — Valid Integer Error Fix

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

🔧 Fix OTTO Title Changes Not Updating Live Site

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

🚀 Deploying More Than 100 OTTO Improvements at Once

Overview OTTO SEO allows you to deploy site improvements in bulk directly from the dashboard. This article explains what to expect when you have more than 100 improvements queued and how to work through large volumes efficiently. Deploying Large Batches of Improvements If you have more than 100 improvements ready to deploy in OTTO SEO, you may find that not all improvements are deployed in a single action. This is expected behaviour when working with large improvement queues. To work through a large queue of improvements: 1. Open OTTO SEO from your Search Atlas dashboard and navigate to the site you want to optimise. 2. Review your queued improvements and identify which items are ready to deploy. 3. Select and deploy your improvements. If you have more than 100 items, work through them in batches, allowing each deployment to complete before proceeding further. 4. Repeat the process for any remaining improvements until all fixes have been deployed. If OTTO reports fewer deployed fixes than the total the audit found, this is normal when dealing with high volumes — continue working through the queue in subsequent deployment actions until all improvements have been applied. Tips for Managing High-Volume Deployments - Check progress after each batch: After deploying, revisit the improvement list to confirm which items have been applied and how many remain. - Be patient with large queues: High volumes may require multiple deployment actions to fully complete. Avoid interrupting an in-progress deployment. When to Contact Support If improvements appear stuck, fail to deploy after repeated attempts, or the number of deployed fixes does not increase over time, our team can investigate further. Please have the following ready when you reach out: your site or project name, the issue types affected, and an approximate count of improvements remaining in the queue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ Troubleshooting Deployed SEO Changes Not Appearing in Shopify

This article explains what the Deployed status means in Search Atlas and why your SEO changes may not yet be visible inside Shopify. 🔍 What "Deployed" Actually Means In Search Atlas, Deployed means the changes have been approved and sent from Search Atlas to Shopify — but it does not automatically guarantee they are visible in your Shopify admin or live storefront. The change must also be accepted and rendered by Shopify, which depends on a successful connection between the two platforms. 🛠️ What to Do If Your Changes Are Not Appearing 1. Verify your Shopify integration is active. Confirm that your Shopify store is connected to Search Atlas. If the integration is disconnected, Search Atlas cannot write changes to Shopify even when the status shows Deployed. 2. Re-authenticate if needed. If the connection appears broken or was set up a long time ago, disconnect and reconnect your Shopify store, then re-deploy the changes. 3. Check the specific resource in Shopify. Log in to your Shopify admin and navigate directly to the page, product, or collection that was changed. Review the SEO fields to see whether the new values are present. 4. Re-deploy if values are still missing. If Shopify still shows the old values, return to Search Atlas, find the affected item, and trigger a new deployment. Monitor the status after saving to confirm it progresses to Deployed again. 5. Wait for propagation if the values are present. If the values are already updated in Shopify but are not yet showing in search results or on the live storefront, allow time for Shopify's theme to re-render and for search engines to re-crawl the page. 📋 When Escalating to Support If the steps above do not resolve the issue, please have the following ready when you contact us: - Your project name in Search Atlas - The specific URL(s) of the affected Shopify pages, products, or collections - The exact status shown in Search Atlas for the affected items (e.g., Deployed, Pending) - Any error messages you have seen, including the exact wording - The date and time when you last deployed the changes If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

📋 View and Track Deployed OTTO SEO Tasks

🔍 Overview After deploying OTTO SEO automation tasks, you may wonder where to find a record of what was deployed and how to confirm the changes are live. This article explains where to look for deployed tasks and what to expect regarding visibility on your website. 🗂️ Where Deployed Tasks Are Stored All deployed OTTO SEO tasks are tracked within your OTTO project in the Search Atlas platform. To locate your deployed tasks: 1. From the main left-hand navigation, go to OTTO SEO → All Sites (SEO Automation). 2. Select the specific OTTO project associated with the site where you deployed tasks. 3. Once inside the project, look for the area that lists your applied automation tasks. This is where completed deployments are recorded, showing what was deployed and when. 4. Review the listed tasks to confirm which changes have been applied to your site. If you cannot find a specific task, verify that you are inside the correct OTTO project. Also confirm that the deployment step was fully completed — tasks that were only saved or queued may not yet appear as deployed. 📋 What to Look for in Your Project Within your OTTO project, you will find a record of automation tasks that have been applied to your site. Use this to confirm what changes have been made and cross-reference with any site behavior you are monitoring. If you are still unable to locate a task, double-check that you completed the final deploy action (not just saved or staged the task), as only fully deployed tasks are recorded as deployed. ⏱️ When Will Changes Appear on Your Live Site? After a task is marked as deployed in the platform, it may take some time before the changes are visible on your live website. If changes do not appear immediately, allow some time to pass before checking again. 🙋 Still Can't Find Your Deployed Tasks? If you have checked your OTTO project and still cannot locate your deployed tasks, our team can help you identify where they are recorded. When reaching out, please have the following ready: your project name, the approximate date you deployed the tasks, and a description of the task type you are looking for. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 How to Pause OTTO, Review On-Page Changes, and Control What Gets Published

OTTO is built to automate on-page SEO improvements, but you always stay in control. If you want to review AI-generated changes before they are applied to your website, you can temporarily pause OTTO, inspect all recommendations, and selectively re-enable automation when you're ready. This guide explains exactly how to do that, step by step. ⏸️ When should you pause OTTO? Pausing (disengaging) OTTO is useful when: - 🧐 You want to review SEO changes before publishing - ✋ You need to approve or reject specific title, meta, or heading updates - 👥 You're validating changes with a client or internal team - ⚙️ You want to temporarily stop automation while making manual edits 💡 Note on terminology: Pausing OTTO is done by setting it to Disengaged — the terms Pause and Disengage mean the same thing throughout this guide and in the product. ⚠️ Important Disengaging OTTO does not revert, remove, or delete anything. It simply pauses automated publishing. If the OTTO status shows Engaged but no changes are being deployed after 10–15 minutes, or shows Disengaged but changes are still being pushed to your site, this indicates a stuck backend task on our side (the UI toggle changed state but the backend job did not complete). This is a known issue. Contact support and include the following so they can resolve it quickly: your project name, the domain, the toggle state shown in the UI, and the observed behavior (e.g., "toggle shows Engaged but no deployments after 20 minutes"). ⚠️ Website Studio compatibility: If your site is built with Search Atlas Website Studio, OTTO on-page changes (meta tags, title tags, etc.) will not deploy correctly through manual script installation. Adding the OTTO pixel script tag manually inside Website Studio is not sufficient — the platform requires either a CMS connector or a properly configured Cloudflare Worker for deployments to work. We strongly recommend contacting support before attempting any manual installation on a Website Studio site, so we can set up the correct deployment path for you. If changes appear deployed in OTTO but are not reflected on your live site, contact support. 🔄 Step 1: Disengage OTTO (Pause Automation) 1. Go to Left Sidebar → OTTO SEO → All Sites (SEO Automation) 2. Select the site you want to manage 3. At the top of the site overview, locate the OTTO Toggle 4. Toggle OTTO to Disengaged When OTTO is disengaged: - 🚫 No new on-page changes are published - 👀 All recommendations remain visible - ✍️ You can freely review and configure suggested updates This is a safe review state, not an error. 📍 Step 2: Navigate to On-Page Recommendations Continuing from Step 1 (you should already be on the site you selected under All Sites), follow this exact path within that site: 🧭 Path: OTTO SEO → All Sites (SEO Automation) → Select Your site → OTTO Grader (Onpage Optimizations) This section shows: - 📋 All detected on-page issues - 🤖 OTTO-recommended fixes - 🔍 Current live content vs suggested content - 🚦 Deployment status for each recommendation 🎛️ Step 3: Review and Control Individual Changes Inside Onpage Audit , you can approve or reject changes one-by-one — you do not have to re-engage OTTO wholesale. Use the per-item Enable/Disable controls described below to choose exactly which title, meta, or heading updates should be published when OTTO is re-engaged. 🔎 Filter by issue type (Title Tags, Meta Descriptions, Headings, etc.) 👁️ Compare Original content vs OTTO Suggested Fix ✅ Enable or ❌ disable recommendations at: Category level (for example, all Title Tag issues) Individual page level (such as your homepage) ℹ️ About supporting content suggestions: OTTO may suggest adding supporting content such as keyword lists or FAQ sections. This content is contextually relevant to the page, is visible to both users and search engines, and is designed to improve SEO without affecting the visual design of your page. It is not hidden using deceptive techniques (such as display:none keyword stuffing) and is not considered black-hat SEO, because it does not violate Google's guidelines on hidden text and links. If you prefer not to publish a specific supporting-content suggestion, simply disable it at the recommendation level before re-engaging OTTO. 🛠️ Tasks stuck in Pending: Some tasks may remain in Pending status when OTTO cannot generate a fix. The most common cause is image alt text recommendations where the image itself is missing from the site (not just missing alt text — the underlying image file cannot be found on the page). OTTO cannot generate alt text for an image that doesn't exist, so the task will stay in Pending. To resolve these, either add the missing image to the page and re-scan, or accept that those specific tasks will remain unresolvable until the image is present on the site. 🧠 What each state means: - Enabled → Will be applied when OTTO is active - Disabled → Will never be applied, even after re-engaging OTTO You can mix enabled and disabled items freely. Automation is granular, not all-or-nothing. ▶️ Step 4: Re-Engage OTTO When Ready After reviewing and configuring what should be published: 1. Return to the site overview 2. Toggle OTTO back to Engaged OTTO will now: - 🚀 Publish only the enabled recommendations - ⛔ Skip anything you disabled - 🔁 Respect your selections going forward You can disengage and re-engage OTTO as often as needed. 🧊 What happens if I leave OTTO disengaged? Nothing changes on your site. - ❌ No SEO updates are pushed - 🧾 No content is overwritten - 🗂️ All recommendations remain in a review state OTTO stays paused until you manually re-enable it. ❓ Common Questions Does disengaging OTTO delete recommendations? No. All recommendations remain available for review. Can I re-enable only some changes? Yes. You control recommendations at both category and page level. Will OTTO override my manual edits? No. Disabled recommendations are never applied. Is this reversible? Yes. OTTO can be paused or re-engaged at any time. OTTO is not a black box. You can: - ⏸️ Pause automation - 👀 Review every suggested change - 🎯 Decide exactly what gets published - ▶️ Re-engage only when you're confident This workflow is intentional and designed to give you editorial control with AI support, not forced automation.

Fix OTTO SEO Deploy All Button Disabled

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

Understanding OTTO Autopilot Bulk Deployment Limits

Overview When using OTTO SEO's Autopilot feature, deployments are processed in batches rather than all at once. If you have noticed that not all of your pending improvements were deployed in a single run, this is expected behaviour — Autopilot applies changes in grouped batches to protect site stability and allow incremental review. Why Batch Limits Exist The batch limit is designed with your site's health in mind. Deploying a very large number of changes simultaneously can: - Overwhelm your CMS or hosting environment with simultaneous write requests. - Make it harder to identify which specific change caused an issue if something goes wrong. - Slow down your site temporarily during the deployment window. By processing in batches, OTTO gives your server time to handle each group of changes and gives you a clear checkpoint to review results before continuing. What to Do If Not All Improvements Were Deployed If you find that some improvements were not deployed during a run, the specific batch size and exact triggers depend on your project configuration and are managed on the backend. Here is what you can do: 1. Navigate to OTTO SEO and open the relevant site project. 2. Check which improvements are still marked as pending after the most recent deployment run. 3. Note the exact number of improvements that were deployed versus the total number that were pending, so you have this information ready. 4. If improvements remain pending and are not being picked up in subsequent runs, contact our support team — provide your project name, the number of improvements pending, and the date and time of the last deployment run so our team can investigate your project's queue and batch configuration directly. Tips for Managing Large Deployments - Prioritise improvements by impact: Review your pending improvements and ensure your highest-priority items are approved and ready first. - Monitor each run: After each Autopilot run, revisit your project dashboard to confirm how many improvements were applied and how many remain. - Escalate stalled queues promptly: If your remaining improvements are not being processed across multiple runs, this may indicate a configuration issue that requires backend investigation — reach out with the details listed above so our team can resolve it 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.

🚀 Deploy All Button: Prerequisites and Correct Workflow

🔍 Overview The Deploy All button in Site Audit lets you publish AI-generated SEO suggestions across your entire site in one click. However, it only deploys suggestions that have already been generated by the AI. If you skip the generation step, Deploy All will only process the suggestions that exist at that moment — leaving the rest untouched. This article walks you through the correct end-to-end workflow so every suggestion is generated and deployed successfully. ⚠️ Why Only Some Suggestions Deployed If you added a new domain, clicked Deploy All, and only a fraction of your suggestions deployed (for example, 10 out of 55 title tags), this is almost always because the AI had only generated suggestions for a subset of your pages or categories at that point. Deploy All does not trigger AI generation — it deploys whatever suggestions already exist. You must complete the AI generation step first for every category you want to deploy. ✅ The Correct Workflow: Step by Step 1. Add your domain. In the left sidebar, go to OTTO SEO → SEO Automation (URL: /seo-automation-v3). Add your domain if you have not done so already and wait for the initial crawl to complete. 2. Open Site Audit. Once the crawl finishes, navigate to the Site Audit section for your domain. You will see suggestion categories such as Title Tags, Meta Descriptions, Headings, and others. 3. Generate AI suggestions for each category. This is the mandatory prerequisite step. For each category you want to deploy: - Open the category (for example, Title Tags). - Click the Generate or Generate AI Suggestions button for that category. - Wait for the AI to finish generating suggestions for all pages in that category. A progress indicator will confirm when generation is complete. - Repeat this process for every other category you want to include — Meta Descriptions, Headings, and so on. 4. Review generated suggestions (recommended). Before deploying, scan through the AI-generated suggestions to confirm they meet your expectations. You can edit any individual suggestion directly in the interface. 5. Click Deploy All. Once AI suggestions have been generated across all desired categories, click Deploy All. The button will now process and publish every available suggestion across your site. 💡 Key Things to Know - Deploy All only deploys what already exists. If a category has no generated suggestions, those pages are skipped entirely. - Generation takes time. For large sites with many pages, AI generation can take several minutes per category. Do not click Deploy All until all generation tasks show as complete. - You can deploy one category at a time. If you prefer more control, generate suggestions for a single category and use that category's individual deploy option before moving to the next. - Re-running generation is safe. If you added new pages or want fresh suggestions, you can re-generate a category at any time. Existing deployed suggestions will not be overwritten unless you deploy again after regenerating. - Newly added domains start with zero suggestions. Every time you connect a new domain, the AI has not yet run. You must manually trigger generation for each category before Deploy All will have anything to publish. 🗂️ Quick Reference: Generation Before Deployment - Step 1 — Crawl complete? Yes → proceed. No → wait for the crawl to finish. - Step 2 — AI suggestions generated for all categories? Yes → proceed. No → open each category and click Generate. - Step 3 — Ready to deploy? Click Deploy All to publish every generated suggestion at once. 🆘 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.

🚀 Deploy More Than 100 OTTO Improvements in Bulk

🔍 Overview When using OTTO SEO to deploy improvements across your site, you may notice that the platform applies a limit of 100 improvements per bulk deployment action. This is a deliberate safeguard designed to protect site stability, prevent server overload, and ensure each batch of changes is applied cleanly before the next set begins. This article explains why the limit exists, how to work within it effectively, and what to expect as the feature continues to evolve. ⚙️ Why the 100-Improvement Limit Exists Deploying large numbers of on-page changes simultaneously can put significant strain on both your website's server and Search Atlas's processing infrastructure. The 100-improvement cap helps to: - Prevent database and server overload — large uncapped batches can cause performance issues that affect your site and other users. - Ensure deployment accuracy — smaller batches allow the system to verify each change was applied correctly before continuing. - Maintain platform stability — our engineering team is actively working on scaling bulk operations safely (see the roadmap section below). 📋 How to Deploy More Than 100 Improvements Even with the current limit, you can still deploy hundreds or thousands of improvements — you just need to do it in sequential batches. Follow these steps: 1. Open OTTO SEO from your Search Atlas dashboard and navigate to the site you want to optimise. 2. Filter or sort your improvements by category, priority, or page to identify the first group you want to deploy. 3. Select up to 100 improvements from the list using the bulk-select checkboxes. 4. Click Deploy and wait for the confirmation that the batch has been successfully applied. 5. Repeat the process for the next group of improvements. There is no limit on how many batches you can run — only on the size of each individual batch. Tip: Start with your highest-priority improvements first — such as missing title tags, meta descriptions, or critical schema fixes — so your most impactful changes go live quickly while you work through the remaining batches. 💡 Best Practices for Large-Scale Deployments - Group improvements by type or page template — this makes it easier to review results and roll back a specific category if needed. - Allow time between batches — giving Search Atlas a few minutes to process and verify each batch before starting the next one helps ensure accuracy. - Monitor your site after each batch — check that pages are rendering correctly and that no unintended changes have occurred before continuing. - Use filters inside OTTO — filtering by improvement status (e.g. Suggested vs Deployed) helps you keep track of where you are across multiple sessions. 🛠️ What We're Building: Roadmap Update Our engineering team is actively working on improvements to bulk deployment capabilities. Planned work includes: - Expanded bulk deployment limits — we are developing the infrastructure to safely support larger batches without risking performance issues. - Bulk write-from-spreadsheet — an upcoming feature will allow you to upload improvements via spreadsheet with enforced validation, making large-scale deployments faster and more structured. - Enhanced OTTO Agent bulk actions — the OTTO Agent will gain the ability to suggest and deploy fixes in bulk with greater automation and control. These features are at various stages of development and will be announced in the platform when they become available. ❓ Frequently Asked Questions - Can I run multiple batches in the same session? Yes. You can deploy as many batches of up to 100 improvements as needed within a single session. There is no daily or session cap on the number of batches. - Will my progress be saved between sessions? Yes. Any improvements you have already deployed are marked as such in OTTO, so you can pick up where you left off in a future session. - Can I undo a batch after deploying it? OTTO SEO includes rollback functionality for deployed changes. Check the deployment history within your OTTO dashboard to revert specific batches if needed. - Is the 100-limit the same for all plan types? Currently, yes. As our bulk deployment infrastructure scales, higher limits may become available on certain plans. Watch for platform announcements. 💬 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 Anchor Text Duplication and Auto-Deployment

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

🛠️ Fix OTTO Deployed Content Not Appearing on Live Site

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

🛠️ Fix OTTO Heading Deployment JavaScript Errors

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

🛠️ OTTO SEO Deployments and Manual Backend Conflicts

🔍 Overview OTTO SEO automates on-page optimisations — including title tags, meta descriptions, and structured data — by deploying changes through a connected integration layer. If you are also making manual edits inside your Shopify (or other CMS) backend at the same time, those two sources can conflict, causing changes to appear missing, overwritten, or duplicated. This article explains how OTTO deployments work, what to expect after deploying, and the safest way to manage edits alongside OTTO. ⚙️ How OTTO SEO Deploys Changes When you approve and deploy a fix inside OTTO SEO, the platform pushes that change through its integration with your connected store or site. The deployment does not always edit your theme files or database records directly in the way a manual Shopify edit would. Instead, OTTO injects or overrides values through its connector layer. - Shopify connector: OTTO writes changes via the Shopify API. The update is visible in Search Atlas as "Deployed," but it may take a short crawl or cache-refresh cycle before it appears in your live storefront or in Google Search Console. - Cloudflare integration: For sites using Cloudflare, OTTO can serve optimised tags at the edge, meaning the change is live faster but may not be reflected inside your Shopify admin panel — this is expected behaviour. - Propagation delay: After deployment, allow up to 24–48 hours for search engines to recrawl and reflect the updated tags in search results. ⚠️ Why Title Tags Show as Deployed but Are Not Visible in Shopify This is the most common source of confusion. There are two typical causes: 1. OTTO uses API-level injection, not theme-file edits. When OTTO deploys a title tag via the Shopify API, it updates the SEO fields on the product, collection, or page object — not the Liquid template in your theme. Some Shopify themes prioritise the Liquid template value over the API value, which can make it appear as though nothing changed inside the Shopify editor even though the live HTML <title> tag is correct. 2. A conflicting manual edit was saved after deployment. If you (or a team member) manually edited the same title tag inside Shopify after OTTO deployed its version, your manual save will overwrite OTTO's value. OTTO will still show the status as "Deployed" because the deployment itself succeeded — it does not continuously monitor for subsequent manual changes. 🚫 Avoid Applying Both Manual Edits and OTTO Deployments to the Same Field Editing the same SEO field in both OTTO and your Shopify backend creates a conflict loop and can lead to: - Overwritten changes: whichever edit was saved last will win, and the other will be lost. - Apparent duplication: in rare cases, certain theme configurations can render both values, resulting in duplicate title tags or meta descriptions visible to crawlers. - Confusing status reporting: OTTO will continue to show "Deployed" even if a later manual save has overridden its output. The safest approach is to choose one source of truth for each SEO field and stick to it consistently. ✅ Recommended Workflow Follow these steps to keep OTTO deployments and your Shopify backend in sync: 1. Let OTTO own SEO fields. Once you connect OTTO SEO and begin deploying optimisations, stop editing title tags, meta descriptions, and other OTTO-managed fields directly inside Shopify. Manage all changes through OTTO SEO at Left sidebar → OTTO SEO. 2. Verify the live HTML, not the Shopify admin panel. After a deployment, right-click your live page in a browser and select View Page Source. Search for <title> to confirm the deployed value is present. The Shopify admin editor may not reflect API-level changes. 3. Clear your Shopify and browser cache. If the live source still shows an old value, clear your storefront cache (if applicable) and perform a hard refresh in your browser before assuming the deployment failed. 4. Check for theme overrides. Ask your developer to confirm that your Shopify theme's title tag in the Liquid template reads from the page_title variable rather than a hard-coded string. Hard-coded values will always override API updates. 5. Re-deploy if a manual edit overrode OTTO. If a team member saved a manual change that overwrote OTTO's deployment, simply return to OTTO SEO, find the affected page, and redeploy the fix. 📊 Checking Deployment Status in OTTO SEO To review what OTTO has deployed and its current status: 1. Go to Left sidebar → OTTO SEO (URL: /seo-automation-v3). 2. Find the site or project and open the relevant fix category (for example, Title Tags). 3. Review the status column. A Deployed status confirms the API call succeeded at the time of deployment — it does not guarantee the value has not been overridden since. 4. If you suspect a conflict, redeploy the fix and immediately verify the live page source before making any further manual edits. 💡 Key Takeaways - OTTO deploys SEO changes via API or edge injection — these may not appear inside the Shopify admin editor, which is expected. - "Deployed" in OTTO means the push succeeded, not that the value is immune to later manual overrides. - Editing the same field in both OTTO and Shopify causes conflicts, overwrites, and potential duplication. - Always verify changes by viewing the live page source, not the CMS editor panel. - Choose one system to own each SEO field and do not switch between them without a clear handoff. 🙋 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🧊 OTTO Site Slots and Deep Freeze Explained

🔍 What Is Deep Freeze in OTTO? When an OTTO-managed site is placed into Deep Freeze, it is paused and no longer actively managed by OTTO. However, a deep-frozen site continues to occupy one of your OTTO site slots until the freeze period has fully elapsed and the slot is released. 📊 Why Can't I Add a New Site After Freezing One? This is the most common source of confusion. Freezing a site does not immediately release its slot. A deep-frozen site must go through a release period before its slot becomes available again. Until that process completes, your slot count stays the same, and adding a new site may be blocked. Here is what happens step by step: 1. A site is placed into Deep Freeze. 2. The slot remains tied to the frozen site for the duration of the freeze period. 3. Once the freeze period ends, the slot is released and you can assign it to a new site. Until the freeze period ends, the slot remains locked — even if the site appears paused or frozen in the dashboard. ❄️ Does Freezing Multiple Sites Free More Slots? Not immediately. Each frozen site has its own release timeline. Freezing more than one site means multiple slots may eventually become available, but each slot only opens up when its individual freeze period has fully elapsed. Freezing more sites does not shorten the required period or bypass the limitation. 🗑️ Can I Remove a Frozen Site to Free the Slot? Because the exact options available depend on your account and plan, we recommend reaching out to our support team who can confirm the correct process for your specific setup and guide you through it safely. ⏱️ How Do I Check When a Slot Will Be Released? The OTTO SEO section of the platform displays information about your frozen sites and their current status. Check your OTTO dashboard for any available freeze or slot details. If you cannot locate the release information or the slot status is unclear, our support team can look this up for your account directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 Find and Track Your Deployed OTTO SEO Tasks

🧭 Overview After deploying OTTO SEO tasks, it can be unclear where to find them, which pages were affected, and why some changes do not appear on your live site right away. This article explains how to locate your deployed tasks, interpret their status, and what to do if changes are not yet visible. 📍 Where to Find Your Deployed OTTO Tasks All OTTO SEO activity is managed inside the OTTO SEO section of the platform. Follow these steps to locate your deployed tasks: 1. In the left sidebar, click OTTO SEO, then All Sites (SEO Automation). 2. Open your OTTO SEO project or select the relevant site. 3. Navigate to the Tasks or Deployed tab within the OTTO dashboard. Here you will see a list of every task that has been deployed, including the page it applies to, the task type, and its current status. 4. Use the filters at the top of the list to narrow results by status (for example, Deployed, Pending, or Failed) or by task category such as title tags, meta descriptions, or schema. Each row in the task list shows the target URL, the type of change made, the date it was deployed, and whether the deployment was successful. 📊 Understanding Task Status Labels OTTO uses several status labels to describe where a task is in the process: - Deployed: OTTO has successfully written the change to your site. The fix is live from Search Atlas's side. - Pending: The task has been queued but not yet applied. This can happen during high-volume deployments. - Failed: The change could not be applied. This is usually caused by a permissions issue, a plugin conflict, or a disconnected integration. - Crawled: A search engine bot has visited the page since the fix was deployed. This confirms the change is being discovered. ⏳ Why Changes May Not Appear on Your Site Yet A status of Deployed means Search Atlas has sent the change — but several factors can delay it from appearing on your live site or in search results: - Caching: Your website, hosting provider, or CDN may be serving a cached version of the page. Clear your site cache after a deployment to force the updated version to load. - Plugin or theme conflicts: Some WordPress plugins or themes override meta fields. If a deployed tag is not appearing, check whether another plugin is outputting the same field and taking priority. - Integration sync delay: If OTTO is connected via a plugin, confirm the plugin is active and that the connection status in the OTTO dashboard shows as Connected. - Search engine crawl delay: Even after your page is updated, Google and other search engines need to re-crawl and re-index the page before changes appear in search results. This can take anywhere from a few hours to several days depending on your site's crawl frequency. - Indexing not yet triggered: OTTO deploys the fix to your page, but requesting re-indexing from Google is a separate step. You can speed this up by submitting the updated URL manually through Google Search Console using the URL Inspection tool and clicking Request Indexing. 🛠️ Steps to Troubleshoot a Deployed Task Not Showing 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open your OTTO project. 2. Find the task in the deployed list and confirm its status is Deployed and not Failed. 3. Visit the affected page in your browser, open the page source (right-click → View Page Source), and search for the expected change — for example, the new title tag or meta description. 4. If the change is not in the page source, clear your site cache and reload. If it still does not appear, check your OTTO plugin connection status. 5. If the change is visible in the page source but not in search results, submit the URL for re-indexing via Google Search Console. 6. If the task shows a Failed status, review the error detail shown in the task row and check that OTTO has the necessary permissions to edit your site. 💡 Tips for Staying on Top of OTTO Deployments - Review the OTTO task list after every bulk deployment to confirm all tasks show a Deployed status before expecting changes on your site. - Clear your cache immediately after deploying a batch of tasks to avoid confusion caused by stale pages. - Use Google Search Console alongside OTTO to monitor crawl activity and confirm that search engines are picking up your updates. - Check back on deployed tasks after 48–72 hours — most changes will be crawled and reflected in search results within this window for regularly crawled sites. 💬 Still Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes If you cannot find a specific task, verify that you are inside the correct OTTO project. Also confirm that the deployment step was fully completed — tasks that were only saved or queued may not yet appear as deployed.

🔄 OTTO Deployment Changes Blocked by Cache Plugins

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

🔧 OTTO Heading Deployment Behavior on Wix Explained

🧭 Overview When OTTO deploys heading fixes on a Wix site, the changes may look like they have reverted or disappeared. This is expected behavior, not a bug. OTTO uses two distinct fix types for headings, and each one behaves differently depending on whether a heading is missing or simply too long. This article explains both fix types, how they appear on your site, and why your changes are working even when they seem invisible. 📋 The Two Types of Heading Fixes OTTO Deploys OTTO identifies heading issues in two categories, and each category is resolved in a different way. - Missing Heading Fix: When a required heading (for example, an H1) is completely absent from the page, OTTO injects the heading into the page with a display:none style. This means the heading exists in the page's HTML and is fully readable by search engine crawlers, but it is intentionally invisible to human visitors so it does not disrupt your Wix site's visual design. - Length Fix (Too Long or Too Short): When a heading already exists on the page but exceeds or falls below the recommended character length, OTTO replaces the heading text with an optimized version. This replacement is visually live — the updated heading text is visible to both visitors and search engines. 👁️ Why Missing Heading Fixes Look Like They Reverted After OTTO deploys a missing heading fix, you will not see any new text appear on your Wix page. Because the injected heading is set to display:none, it is hidden from view by design. This is the most common reason customers believe their changes have reverted — the fix was successfully deployed, but it is not meant to be seen. To confirm the fix is active, you can inspect the page source or use your browser's developer tools. The heading element will be present in the HTML with an inline display:none style. Search engines read this element and use it for indexing purposes, which is the intended outcome. 🔄 Why Length Fixes May Also Appear to Revert If a length fix appears to have reverted, the most likely explanation is one of the following: - Wix rendering delay: Wix sites can take a short time to reflect script-injected changes after a new page load. Try refreshing the page or clearing your browser cache and checking again. - OTTO re-evaluated the heading: If the heading was subsequently edited in your Wix editor and the text was changed again, OTTO may re-queue it for a new fix on the next optimization cycle. - Deployment is still in progress: Large batches of fixes may take several minutes to propagate. Wait a few minutes before concluding a fix has not applied. 🗂️ Summary of Expected Visibility by Fix Type - Missing heading injected by OTTO → Hidden on page (display:none), visible to search engines, invisible to visitors. This is correct and intentional. - Length-optimized heading replaced by OTTO → Visible on page, updated text shown to both visitors and search engines. 🚀 How to Check OTTO Heading Deployment Status 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Select your Wix site and open the OTTO dashboard. 3. Review the Headings section to see which fixes have been marked as deployed. 4. A fix marked as deployed is confirmed active regardless of whether it is visible on the page. 5. To verify a hidden heading in your browser, right-click the page and select View Page Source or open Inspect Element and search for your injected heading text. ⚠️ What Is Not Covered by This Behavior This article covers the standard behavior for Wix sites connected to OTTO. If you are seeing fixes marked as not deployed in the OTTO dashboard, or if a deployed fix disappears from the page source entirely after more than 24 hours, that may indicate a separate connectivity or script issue that requires investigation. 💬 Still Have Questions? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 Fix OTTO Deployments Turning On and Off

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

🔄 Rollback OTTO, Fix Duplicate Metadata & Local SEO

🧭 Overview This article covers three common questions from Search Atlas customers: how to roll back changes made by OTTO SEO, how to avoid duplicate metadata when using multiple SEO tools, and how to get the most value from Search Atlas as a local service business. Follow the guidance below to resolve each issue quickly. ↩️ How to Roll Back OTTO SEO Changes OTTO SEO applies on-page optimisations automatically, including meta titles, meta descriptions, keyword placements, and schema markup. If you want to undo these changes, follow the steps below. 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select the website or project where OTTO made changes. 3. Open the Deployed Fixes or Active Optimisations section. 4. Locate the specific fix or group of fixes you want to revert — you can filter by type, such as Meta Data, Keyword Optimisations, or Schema Markup. 5. Click Undeploy (or Roll Back) next to each fix to remove it from your site. 6. Confirm the action when prompted. OTTO will restore the original content that existed before the change was applied. Important notes about rolling back: - Rollback restores the previously saved version of that field. Make sure you verify the restored content looks correct in your CMS after undoing. - Schema markup fixes that were applied via bulk deployment may need to be individually undeployed if they are not visible in the standard deployment queue. If you cannot locate a specific schema fix after a bulk action, contact support using the instructions at the bottom of this article. - Meta description and keyword optimisation rollbacks take effect immediately once confirmed — no additional plugin update or cache clear is required on the Search Atlas side, though you may need to clear your site's own cache. 🚫 How to Avoid Duplicate Metadata When Using Multiple SEO Tools Duplicate meta descriptions, titles, or schema markup can occur when more than one SEO tool is writing to the same fields on your website. This is a common issue for customers who use Search Atlas alongside plugins like Yoast SEO, Rank Math, or All in One SEO. Follow these best practices to prevent conflicts: - Designate one tool as the source of truth. Decide whether Search Atlas OTTO or your WordPress SEO plugin will control meta fields and schema. Do not let both tools write to the same fields simultaneously. - Disable meta output in your WordPress plugin if you want OTTO to manage those fields. In most SEO plugins, you can disable meta title, meta description, and schema output per post type or site-wide in the plugin settings. - Disable OTTO's meta optimisations if you prefer to keep your existing plugin in control. In the OTTO SEO dashboard, you can selectively undeploy meta-related fixes while keeping other OTTO improvements (such as internal linking or heading structure) active. - Audit your schema markup regularly. Use a tool like Google's Rich Results Test to check that only one version of schema is being rendered per page. Duplicate schema can confuse search engines and may cause structured data errors in Google Search Console. - Check after every bulk deployment. Whenever OTTO runs a bulk update, spot-check a sample of pages to confirm no duplicate tags have been introduced. 📍 Getting Value from Search Atlas as a Local Service Business Search Atlas includes a dedicated Local suite built specifically for businesses that serve customers in a geographic area — such as contractors, medical practices, law firms, and home services. Key Local features and where to find them: - Left sidebar → Local → Overview — See a summary of your Google Business Profile (GBP) health, recent activity, and performance metrics in one place. - Left sidebar → Local → Posts — Publish and schedule GBP posts directly from Search Atlas to keep your profile active and engaging. - Left sidebar → Local → Reviews — Monitor and respond to customer reviews across your GBP listing without leaving the platform. - Left sidebar → Local → Local Citations — Build and manage consistent NAP (Name, Address, Phone) citations across directories to strengthen your local authority. - Left sidebar → Local → Media Library — Upload and manage photos and videos for your GBP profile to improve engagement and ranking signals. - Left sidebar → Local → My Tasks — Track outstanding local SEO tasks and recommendations assigned to your project. Maximising authority and internal linking for local businesses: - Use OTTO's internal linking suggestions (found in OTTO SEO → All Sites (SEO Automation)) to connect your service pages, location pages, and blog content. Strong internal linking helps search engines understand your site structure and distributes page authority effectively. - Build topical authority by creating content clusters around your core services and locations. OTTO can identify content gaps and suggest new pages to target local search queries. - Combine GBP optimisation with on-site SEO — consistent business information across your website and your GBP listing is a strong local ranking signal. ✅ Quick Reference Summary - Roll back OTTO changes: OTTO SEO → All Sites (SEO Automation) → Deployed Fixes → Undeploy individual fixes. - Prevent duplicate metadata: Use only one tool to write meta fields and schema per page. - Local SEO value: Use the Local suite (GBP posts, reviews, citations) alongside OTTO's on-site optimisations for the strongest results. If you need further assistance, open 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 an OTTO SEO Background Deploy Job

🔍 Overview When you run OTTO SEO on a project, it can queue background jobs that automatically deploy fixes or publish content to your site. If you notice that a pending job contains incorrect information — such as wrong city or state data pulled into a Content Genius article — it is important to act quickly before the job completes and the content goes live. This article explains how to locate an active OTTO SEO deployment, freeze it to stop further changes, and verify the job has been halted. ⚠️ When Should You Stop a Background Job? - OTTO is about to publish or deploy content with incorrect location data (e.g., wrong cities or states). - A Content Genius article was generated with settings that do not match your actual business location. - You want to review all pending fixes before they go live. - You are making changes to your site and do not want OTTO deploying at the same time. 🧭 How to Locate Your Active OTTO Deployment 1. Log in to Search Atlas and go to Left sidebar → OTTO SEO → All Sites (SEO Automation Projects). 2. On the All Sites page, find the project that has the active background job (for example, your sprinklelaundry.com project). 3. Check the project card for a status indicator showing a pending or in-progress deployment. ❄️ How to Freeze (Stop) the Deployment 1. From Left sidebar → OTTO SEO → All Sites (SEO Automation Projects), locate the project with the active job. 2. Select the checkbox next to the project to highlight it. 3. Click Freeze sites in the toolbar at the top of the page. This immediately pauses all pending OTTO deploy actions for that project. 4. Confirm the project status changes to frozen. No further fixes or content will be deployed while the site is frozen. Important: Freezing a site stops new deployments from going out but does not automatically roll back any changes that have already been applied. See the next section for guidance on reviewing what has already been deployed. 🔎 How to Review What Has Already Been Deployed 1. Go to Left sidebar → OTTO SEO → Site Audit → All Audits to see a full list of fixes OTTO has applied to your site. 2. Go to Left sidebar → OTTO SEO → Site Audit → Page Explorer to review individual pages and the changes made to them. 3. If content has already been published with incorrect location data, you will need to manually edit or delete that content from your CMS or WordPress dashboard. ✏️ Preventing Wrong Location Data in Future Jobs - Before generating a Content Genius article, confirm that your project is set to the correct business location (city and state). - Double-check OTTO's location settings in your project configuration before initiating a scan or deployment. - Use the Freeze sites option any time you want to review pending fixes before they go live. - After making corrections to your project settings, unfreeze the site and re-run the scan to generate a fresh, accurate set of recommendations. 💬 Need Immediate Help Stopping a Job? If you have an urgent deployment in progress that you cannot stop using the steps above, our team can intervene on your behalf. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. When you reach out, please share the project name, the domain, and a brief description of what the pending job is doing so our team can act as quickly as possible.

🔌 OTTO Deployed Fixes Not Appearing Live on WordPress

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

🔧 OTTO Fixes Deployed but Not Showing on Your WordPress Site

🔍 What's Happening If your OTTO fixes show as Deployed in the dashboard but are not visible in your page source or SEO extensions, the most common cause is that the OTTO WordPress plugin is deactivated on your site. OTTO uses a WordPress plugin to render its SEO optimizations as a real-time overlay. When the plugin is inactive, deployments are recorded in OTTO but nothing is applied to the live site. ✅ How to Fix It 1. Log in to your WordPress admin panel (typically at yourdomain.com/wp-admin). 2. Navigate to Plugins → Installed Plugins. 3. Locate the OTTO SEO plugin. 4. If it shows as Inactive, click Activate. 5. Reload your live site and confirm your deployed fixes now appear. ⚠️ Why Does This Happen? The OTTO plugin can be deactivated unintentionally during WordPress updates, theme changes, or routine maintenance. Periodically verify the plugin is active, especially after WordPress environment updates. 💬 Still need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🛠️ OTTO Heading Deployments on Wix Sites Explained

🔍 Overview When OTTO deploys heading optimizations to a Wix site, customers sometimes notice that the changes seem to disappear or revert immediately after deployment. This behavior is expected and is caused by how OTTO interacts with Wix's rendering environment. This article explains exactly what is happening and what you should expect to see. ⚙️ How OTTO Deploys Headings on Wix OTTO applies heading changes — such as rewriting H1, H2, or H3 tags for better SEO — by injecting optimized content through Wix's supported integration layer. Unlike platforms such as WordPress, Wix does not allow third-party tools to directly and permanently overwrite page content in the site editor. Instead, OTTO's changes are applied at the rendering level, meaning they are delivered to search engine crawlers and browsers when the page loads, rather than being stored visibly inside the Wix editor itself. 👁️ Are the Changes Visible in the Wix Editor? No — and this is the key point that causes confusion. When you open the Wix editor after OTTO has deployed heading changes, you will not see the updated headings reflected there. The Wix editor will continue to display your original content. This does not mean the deployment failed. The optimized headings are still being served correctly to visitors and search engine bots when the live page is rendered. ✅ How to Confirm the Changes Are Live To verify that OTTO's heading optimizations are active on your published Wix pages, use one of the following methods: 1. View the live page source: Open your published Wix page in a browser, right-click anywhere on the page, and select View Page Source. Search for your heading tags (H1, H2, etc.) and confirm the OTTO-optimized text is present in the source code. 2. Use a crawl tool: Run the URL through a site auditing tool such as Search Atlas's own Site Auditor to verify the headings being read by crawlers match your OTTO deployments. 3. Check OTTO deployment status: In the Search Atlas platform, navigate to OTTO SEO in the left sidebar and open All Sites (SEO Automation) inside it, then review the deployment log for your Wix site. A green status indicator confirms the changes were successfully pushed. 🔄 Why Do the Changes Look Like They Are Reverting? The appearance of reverting happens because: - Wix stores its own version of your page content independently of OTTO's injected optimizations. - When you view the Wix editor, you are seeing Wix's stored version — not the rendered, OTTO-optimized version that visitors and crawlers see. - If you manually edit and republish a page inside Wix after an OTTO deployment without re-deploying from OTTO, the Wix-stored content will take precedence and the OTTO heading changes will need to be redeployed. ⚠️ Important: Avoid Overwriting OTTO Changes To keep your OTTO heading optimizations intact on your Wix site, follow these best practices: - Do not manually edit headings in the Wix editor after OTTO has deployed changes to those same elements, unless you plan to redeploy from OTTO afterward. - Redeploy from OTTO any time you publish significant page updates in Wix. Navigate to OTTO SEO in the left sidebar and open All Sites (SEO Automation) inside it, then trigger a new deployment for the affected pages. - Use page source or a crawl tool — not the Wix editor — as your source of truth for what headings are actually live on your site. 💡 Summary OTTO heading changes on Wix are working as designed. The optimizations are applied at the rendering layer and are visible in the live page source and to search engine crawlers — but they will not appear inside the Wix editor. Changes may appear to revert if you edit and republish pages in Wix without redeploying from OTTO. Always check the live page source or OTTO's deployment log to confirm your changes are active. 🙋 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 FAQ Deployment Errors in OTTO

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

⏱️ OTTO Deployment Timing and UI Update Delays

🔍 Overview When you deploy optimizations through OTTO SEO, changes are processed in stages — from Search Atlas sending instructions to your site, through to your CMS applying them and the OTTO UI reflecting the results. Understanding this pipeline helps set the right expectations and avoid unnecessary concern when updates don't appear instantly. ⏳ How Long Do Deployments Take? Deployment times vary depending on several factors, but here are the general benchmarks to keep in mind: - Initial deployment trigger: OTTO sends instructions to your site within seconds of you clicking Deploy. - CMS processing time: Your CMS (e.g. WordPress) typically applies changes within 1 to 5 minutes, depending on server speed, plugin load, and site size. - OTTO UI refresh: After your site processes the changes, the OTTO dashboard may take an additional 5 to 15 minutes to reflect the updated deployment status. - Full propagation: In some cases — particularly for larger sites or sites with caching layers — the complete cycle can take up to 30 minutes. If it has been fewer than 30 minutes since you deployed, the process may still be running normally in the background. 🔄 Why Hasn't My Deployment Updated After 10 Minutes? Seeing no change after 10 minutes is common and usually not a sign that something has gone wrong. Here are the most frequent reasons for a delay at this stage: - Caching plugins: Tools like WP Rocket, W3 Total Cache, or server-level caches can prevent freshly deployed changes from appearing immediately. OTTO may have applied the update, but the cached version of your page is still being served. - CDN propagation: If your site uses a CDN such as Cloudflare, updated content may take extra time to propagate across all edge nodes. - Server response delays: Slow or overloaded hosting environments can stall the handshake between Search Atlas and your CMS. - UI polling interval: The OTTO dashboard does not update in real time. It checks for status changes on a scheduled interval, so there is always a short lag between when your site updates and when OTTO reflects it. ✅ What to Check Before Escalating Before reaching out to support, run through these quick checks: 1. Wait the full 30 minutes from the time you clicked Deploy. 2. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3) and hard-refresh the page (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to force the UI to reload the latest status. 3. If you use a caching plugin, purge your site cache and check whether the deployed changes now appear on the live page. 4. If your site uses Cloudflare or another CDN, purge the CDN cache for the affected URLs. 5. Check that your OTTO connection is still active by reviewing the site settings in the OTTO SEO section. A disconnected site will not receive deployments. ⚠️ When Something May Actually Be Wrong If more than 30 minutes have passed and none of the checks above resolved the issue, there may be a genuine problem worth investigating. Signs that a deployment has failed include: - The deployment status shows a persistent error or failed badge in the OTTO UI. - Changes are not visible on the live page even after clearing all caches. - The OTTO connection status shows as disconnected or inactive. In these cases, document the affected URL(s) and the approximate time you triggered the deployment before contacting support — this will help the team investigate faster. 💬 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.

📤 Export Deployed Page Title Changes from OTTO

🗺️ Overview When OTTO deploys page title changes, you can track progress and export a record of completed deployments from the Deployment Summary section. The exact steps differ depending on whether you are using OTTO v2 or OTTO v3. Use the sections below to find the right instructions for your version. 🔍 How to Check Which OTTO Version You Are Using To confirm your version, go to the left sidebar and select OTTO SEO, then open SEO Automation. The URL will update to /seo-automation-v3 if you are on OTTO v3. If you land on an older interface without that URL segment, you are on OTTO v2. 📋 OTTO v2 — Find and Export the Deployment Summary Follow these steps if you are on OTTO v2: 1. In the left sidebar, select OTTO SEO, then open SEO Automation to open your OTTO dashboard. 2. Locate the Deployment Summary panel. In v2, this section is visible directly on the main dashboard page without any additional clicks — scroll down if you do not see it immediately. 3. The panel displays a progress indicator, such as 71/133, showing how many page title changes have been deployed versus the total queued. 4. To export the completed changes, click the Export button displayed in the top-right corner of the Deployment Summary panel. The file downloads as a CSV containing all deployed page titles, their URLs, and deployment timestamps. 📋 OTTO v3 — Find and Export the Deployment Summary OTTO v3 uses a redesigned interface. The Deployment Summary and its export option are not visible by default on the main dashboard — they are located inside the Domain Report tab and require a hover interaction to reveal the export control. Follow these steps carefully: 1. In the left sidebar, select OTTO SEO, then open SEO Automation. Confirm you are on OTTO v3 by checking that the URL contains /seo-automation-v3. 2. At the top of the OTTO dashboard, locate the tab row and click the Domain Report tab. 3. Once inside the Domain Report tab, scroll to the Deployment Summary section. You will see a progress counter showing deployed versus total changes, for example 71 of 133 page titles deployed. 4. The export button in v3 is hidden until you interact with the row. Hover your cursor over the Deployment Summary section header. An Export icon will appear on the right side of the header bar. 5. Click the Export icon to download a CSV file. The file includes each deployed page title, its target URL, the original title, and the date it was deployed. Important: If you do not hover over the section header, the export icon will not be visible. This is expected behaviour in OTTO v3 and is not a bug. 📊 Understanding the Deployment Progress Counter The counter you see — for example, 71/133 — means: - 71 — page title changes that have been successfully deployed to your site. - 133 — the total number of page title changes OTTO has queued or approved for deployment. Only deployed changes (the first number) are included in the exported CSV. Changes that are still pending or awaiting approval are not included until they are deployed. ⚠️ Common Issues and Quick Fixes - I cannot see the Domain Report tab in v3. Make sure you have at least one domain connected to OTTO. If no domain is active, the tab may be hidden. Go to your OTTO settings and confirm your domain is connected and verified. - The export icon does not appear when I hover. Try refreshing the page and hovering again. If the icon still does not appear, clear your browser cache or try a different browser. If the problem persists, contact support using the method below. - My exported CSV is empty. The CSV only includes changes with a Deployed status. If all your changes are still pending, the file will have no data rows. Wait for deployment to complete or check your deployment queue for errors. - I see a Deployment Summary in v3 but the counter shows 0/133. This may mean OTTO has queued changes but deployment has not yet started. Confirm that auto-deployment is enabled or manually trigger deployment from the Domain Report tab. 💬 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 Rollback Not Reflecting on Live Site

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

🤖 Fix OTTO SEO Showing Zero Deploys

🔍 Why OTTO SEO Shows 0 Deploys OTTO SEO uses a two-step workflow: first you generate suggestions, then you deploy them. If you see 0 deploys, it almost always means suggestions have not yet been generated, or they are waiting to be reviewed and deployed. Engaging OTTO SEO does not automatically push changes to your site — you need to complete both steps manually. 🗺️ Step 1 — Open OTTO SEO 1. Log in to Search Atlas. 2. In the left sidebar, click OTTO SEO, then open SEO Automation. The URL will change to /seo-automation-v3. 3. Select the website you want to work on from the property selector at the top of the page. 4. Confirm that OTTO SEO is shown as Engaged for that property. ✨ Step 2 — Generate Suggestions 1. Inside the OTTO SEO dashboard, locate the Generate Suggestions button or the relevant task category (for example, Title Tags, Meta Descriptions, or Schema). 2. Click Generate for each category you want OTTO to analyse. OTTO will crawl your pages and produce a list of recommended changes. 3. Wait for generation to complete — a progress indicator will show when OTTO is working. This can take a few minutes depending on the size of your site. 4. Once complete, the suggestions panel will populate with individual recommendations for each page. Important: OTTO SEO must finish generating suggestions before the Deploy option becomes available. If you skip this step, the deploy counter will remain at 0. 🚀 Step 3 — Deploy Generated Suggestions 1. Review the suggestions listed in the OTTO SEO dashboard. You can approve all suggestions at once or select specific ones to deploy. 2. Click Deploy next to individual suggestions, or use the Deploy All option to push all approved recommendations live. 3. OTTO SEO will apply the changes directly to your connected site. The deploy counter will increment for each successful change. 4. Refresh the dashboard after a moment to confirm the updated deploy count. ⚠️ Common Reasons for 0 Deploys - Suggestions not yet generated: You engaged OTTO but never clicked Generate. Return to the dashboard and run generation for each task category. - Suggestions pending review: Suggestions were generated but not yet deployed. Open each category, review the recommendations, and click Deploy. - No pages crawled: OTTO could not access your site. Check that your website URL is correct and that OTTO has been granted the necessary site access or plugin permissions. - Website not connected: If the site integration (WordPress plugin or DNS verification) is incomplete, OTTO can generate suggestions but cannot deploy them. Verify your site connection in the account settings. - Suggestions filtered out: Active filters on the dashboard may be hiding suggestions. Clear any status or page filters to see all available items. ✅ Troubleshooting Checklist - OTTO SEO status shows Engaged for the correct property. - You have clicked Generate inside at least one task category. - Generation has fully completed — no spinner or progress bar is visible. - You have clicked Deploy on one or more suggestions. - Your site connection (plugin or DNS) is active and verified. - No dashboard filters are hiding pending suggestions. - You have refreshed the page after deploying to see the updated counter. 💬 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 Script Deployment Across Multiple Pages

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

🤖 OTTO Meta Changes Not Deploying After Plugin Deactivation

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

↩️ How to Roll Back All OTTO Changes

🔍 Overview If you need to undo every change OTTO has deployed to your site, the Roll Back All button lets you reverse all optimisations in a single action. Before you can access this button, you must first select your site inside Content Genius. Skipping this step is the most common reason customers cannot find the option. 🖥️ Step 1 — Open Content Genius In the left sidebar, click Content (Content Genius). This opens the Content Genius dashboard where all your OTTO-managed sites are listed. 🌐 Step 2 — Select Your Site This step is required. The Roll Back All button will not appear until a site is actively selected. 1. On the Content Genius dashboard, locate the site you want to roll back. 2. Click the site name or its corresponding Manage button to open the site view. 3. Confirm the site name is displayed at the top of the page before continuing. ↩️ Step 3 — Roll Back All Deployed Changes 1. With your site selected, look for the Roll Back All button. It is located in the upper area of the site management view, near the deployment controls. 2. Click Roll Back All. 3. A confirmation prompt will appear asking you to verify the action. Read the message carefully, as this will undo all OTTO-deployed changes for the selected site. 4. Click Confirm to proceed. OTTO will begin reverting all deployed optimisations. Depending on the number of changes, this may take a few moments to complete. ⚠️ What to Expect After Rolling Back - All changes previously deployed by OTTO will be removed from your site. - Your site will return to the state it was in before OTTO applied those optimisations. - The changes will still be visible inside Content Genius as undeployed suggestions, so you can review and selectively redeploy individual items if needed. - Rolling back all changes does not delete your OTTO configuration or disconnect your site. 💡 Rolling Back Individual Changes Instead If you only want to undo specific optimisations rather than everything at once, you can roll back changes one at a time. Inside the site view, locate the deployed change you want to reverse and click the individual Roll Back option next to that item. This gives you more granular control without affecting the rest of your deployed changes. ❓ Frequently Asked Questions Why can't I see the Roll Back All button? The most common cause is that no site has been selected. Return to the Content Genius dashboard, click into your site, and the button will become visible. Can I redo the changes after rolling back? Yes. The suggestions remain in Content Genius after a rollback. You can review them and choose to redeploy any or all of them at any time. Will rolling back affect my live site immediately? Yes. The rollback is applied to your live site. If OTTO had made on-page changes, those will be removed once the process completes. 🆘 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.

🛒 Deploying OTTO Meta Descriptions to WooCommerce Pages

🔍 Why Meta Tags May Be Missing on Product Pages OTTO deploys meta titles and descriptions on a per-URL basis, not globally across your entire site. This means that even if your homepage and blog posts are already optimised, each WooCommerce product page must be individually selected and deployed to receive its meta tags. If meta descriptions appear on your homepage but not on product pages, the most likely cause is that those product URLs have not yet been targeted for deployment. 📋 Before You Begin - Make sure OTTO is activated for your connected domain. - Confirm your WooCommerce product pages have been crawled and are visible in your URL list inside OTTO SEO V3. - Check that you have not excluded product page URL patterns (such as /product/) from OTTO's scope. 🚀 How to Deploy Meta Tags to a WooCommerce Product Page 1. In the left sidebar, click OTTO SEO and then open SEO Automation to access the OTTO dashboard at /seo-automation-v3. 2. Locate the Meta Tags section within the OTTO task list. 3. Use the URL search or filter to find the specific product page URL you want to optimise — for example, yoursite.com/product/blue-widget. 4. Click the product URL to open its meta tag settings. 5. Review the AI-generated meta title and description. Edit either field if needed to better match your product's target keywords and value proposition. 6. Toggle the deployment switch to On to push the meta tags live to that page. 7. Repeat this process for each additional product page. ⚡ Deploying Meta Tags Across Multiple Product Pages If you have a large WooCommerce catalog, deploying pages one by one can be time-consuming. Use the following approach to work through your product catalog efficiently. - Filter by URL pattern: In the OTTO SEO V3 dashboard, filter or search for /product/ to surface all product page URLs at once. - Bulk selection: Use the bulk-select checkbox to highlight multiple product URLs simultaneously. - Bulk deploy: With multiple URLs selected, apply the deployment action to push meta tags to all selected pages in one step. - Prioritise top products first: Start with your highest-traffic or highest-converting product pages to capture SEO value quickly while you work through the rest of the catalog. ✅ Verifying Deployment Was Successful After deploying, confirm the meta tags are live on each product page. 1. Open the product page URL in your browser. 2. Right-click anywhere on the page and select View Page Source. 3. Use Ctrl + F (or Cmd + F on Mac) to search for meta name="description". 4. Confirm that the deployed description appears in the source code. You can also use a browser extension such as a meta tag inspector to quickly check the active title and description without viewing raw source code. ⚠️ Common Issues and Fixes - Product pages not appearing in the URL list: Run a fresh crawl of your site from the OTTO SEO V3 dashboard to ensure all product URLs are indexed by OTTO. - Meta tags deployed but not showing in source: Clear your site cache and any server-side caching plugin (such as WP Rocket or W3 Total Cache) after deployment. - Another SEO plugin is overriding OTTO: If you have Yoast SEO, Rank Math, or All in One SEO active on your WooCommerce product pages, their meta output may take precedence. Disable meta tag output in those plugins for product pages, or deactivate them entirely if OTTO is your primary SEO tool. - Deployment toggle is greyed out: Verify that OTTO is fully activated for your domain and that your current plan includes meta tag deployment for the number of URLs you are targeting. 💬 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 Deployment vs. Google Indexing Timeline

🔍 What This Article Covers When you deploy meta title and description changes through OTTO in Search Atlas, two separate events happen at different times. This article explains both stages so you know exactly what to expect and how to speed up the process. ⚡ Stage 1: Instant Deployment to Your Live Website As soon as you deploy a meta title or meta description update in OTTO, the change is applied to your live website immediately via JavaScript. This means: - The updated tag is active on the page right away. - Any visitor who loads the page will see the new meta data in the page source. - No manual code changes or developer involvement is required. Deployment itself is not the delay — the wait comes in the next stage. 🕐 Stage 2: Google Must Re-Crawl and Re-Index Your Page Even though your changes are live on the website instantly, Google does not know about them yet. Google maintains its own schedule for crawling and re-indexing pages. Until Google revisits your page, the old meta title and description will continue to appear in search results and in the Page Explorer inside Search Atlas. Here is what the typical timeline looks like: - Minimum: 2–3 days for frequently crawled, high-authority pages. - Typical: 5–10 days for most pages. - Maximum: Up to 14 days or longer for low-traffic or rarely crawled pages. This delay is controlled entirely by Google and is not something Search Atlas can override. It applies to all websites, regardless of the tool used to deploy changes. 📊 Why Page Explorer May Still Show the Old Values The Page Explorer in Search Atlas reflects the meta data that Google has most recently indexed for your page. If Google has not yet re-crawled the page since your OTTO deployment, Page Explorer will still display the previous title and description. Once Google indexes the updated page, Page Explorer will automatically reflect the new values on its next data refresh. 🚀 How to Speed Up Google Re-Indexing You cannot force Google to crawl your page immediately, but you can submit a re-indexing request to move the page higher in Google's crawl queue. Follow these steps: 1. Go to Google Search Console (search.google.com/search-console) and sign in with the account linked to your website. 2. Paste the exact URL of the updated page into the search bar at the top. 3. Click Request Indexing. 4. Google will typically process high-priority pages within 1–3 days after a manual request. This is the fastest available method and is strongly recommended after any significant meta data deployment. 🔗 Using the Search Atlas Index Integration Search Atlas also offers a native Index integration that can help streamline the indexing process for your pages. To access it: - Navigate to OTTO SEO in the left sidebar, then open SEO Automation (or go to /seo-automation-v3). - Look for the Index integration options within the OTTO dashboard. This integration works alongside Google Search Console to help signal updated pages for re-crawling and can reduce the time between deployment and Google reflecting your changes. 📋 Quick Reference Summary - OTTO deployment: Instant — changes are live on your website immediately via JavaScript. - Google search results: 2–14 days — Google must re-crawl the page on its own schedule. - Page Explorer update: Reflects Google's most recent indexed data — updates after Google re-indexes the page. - To speed things up: Submit a re-indexing request in Google Search Console or use the Search Atlas Index integration. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔍 OTTO Deployment: H1/H2 Tag Changes Affecting Page Titles

🔍 What Happens to Page Titles After OTTO Deployment? After deploying OTTO on a Shopify site, you may notice that some page titles have changed unexpectedly. This is a known behavior caused by how OTTO applies on-page optimizations. OTTO can modify H1 and H2 tags as part of its on-page SEO optimizations. Depending on how your Shopify theme is structured, changes to these heading tags may affect the visible page title displayed on your storefront. This can be surprising if you were not expecting visual changes to your storefront content. If the new titles do not match your brand or content preferences, you can reverse them by undeploying the relevant OTTO optimizations from within the OTTO dashboard. 📋 Before You Begin - Make a note of the affected pages and their original titles before making any changes. - Ensure you have access to your Search Atlas account with OTTO configured for your Shopify site. - Navigate to the OTTO SEO section in your Search Atlas account to access the OTTO dashboard. 🔄 How to Undeploy H1/H2 Tag Changes in OTTO 1. Open the OTTO dashboard from the OTTO SEO section of your Search Atlas account. 2. Select the website profile that was affected by the unexpected title changes. 3. Locate the area of the dashboard where your deployed optimizations are listed. 4. Identify the H1 or H2 tag optimizations applied to the pages whose titles were affected. 5. For each affected page, use the available option to undeploy or reverse the H1/H2 tag optimization. 6. Repeat for all pages where the title was changed unexpectedly. If you are unsure which specific optimizations to undeploy, or if you cannot locate the relevant controls in your dashboard, please reach out to our support team for guidance — have your website profile name and a list of the affected page URLs ready so the team can assist you efficiently. ⏱️ How Long Does It Take for Changes to Sync? After undeploying an optimization, the reversal may not appear instantly on your Shopify storefront. Allow some time for the change to propagate before checking whether your original titles have been restored. Avoid re-deploying any H1/H2 optimizations on the same pages until you have confirmed the original titles have been restored. ✅ How to Verify the Titles Have Been Restored After allowing sufficient time for the changes to propagate, visit the affected pages on your Shopify storefront and confirm that the original page titles are displaying correctly. If the titles have not reverted as expected, contact our support team with the affected page URLs, your website profile name, and a description of the issue. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🚀 Understanding OTTO Deploy All Batch Deployment

🔍 Overview The Deploy All button in OTTO SEO is designed to apply multiple SEO optimizations across your site in a single action. However, customers sometimes expect it to resolve every detected issue in one click. This article explains how batch deployment works and why certain issues may remain after running it. ⚙️ How Deploy All Works When you click Deploy All, OTTO groups eligible optimizations and applies them to your site automatically. Not every detected issue will be resolved by a single Deploy All action — some issues are intentionally held back and require individual attention before they can be deployed. You can access OTTO by navigating to OTTO SEO → All Sites (SEO Automation) in the left sidebar of the platform. ⚠️ Why Some Issues Are Not Fixed by Deploy All Certain SEO issues cannot be batch-deployed and will remain in your issue list after running Deploy All. This is expected behavior. Those issues need to be reviewed and actioned individually within the OTTO dashboard before they can be applied to your site. 📋 What to Do When Issues Remain After Deploy All 1. After running Deploy All, check the OTTO dashboard for any issues that were not automatically deployed. 2. Review each remaining issue individually and follow the on-screen prompts to complete or approve the recommended fix. 3. Deploy each confirmed fix once you have reviewed it. 💡 Tips - Run Deploy All first to handle eligible optimizations in bulk, then focus on the smaller set of issues that require individual review. - If you are unsure why a specific issue was not deployed by Deploy All, our support team can review your account and clarify the behavior for that issue 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.

↩️ Rollback OTTO SEO Deployments to Stop Header Changes

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

🛠️ Fix Meta Tag Deployment Persistence

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

⚙️ OTTO Deployment, Lucky Button, and Dynamic Indexing Explained

🔍 Overview OTTO is Search Atlas's OTTO SEO automation engine. It can generate technical SEO elements such as meta descriptions and headings, and it can deploy them to your site — but generation and deployment are two separate steps. This article explains the full workflow, the I'm feeling lucky button, credit costs, and how Dynamic Indexing appears to your users. 🛠️ How OTTO Generates SEO Elements OTTO can automatically generate the following on-page SEO elements for your site pages: - Meta titles - Meta descriptions - H1 headings - H2 and H3 subheadings - Image alt text - Schema markup suggestions To access OTTO, go to OTTO SEO → SEO Automation in the left sidebar (URL: /seo-automation-v3). From there, select your connected site and navigate to the relevant task category to view generated recommendations. OTTO generates suggestions based on your existing page content, target keywords, and SEO best practices. Each suggestion is queued for your review before anything is applied to your live site. ✅ Generation vs. Deployment: What Is the Difference? These are two distinct steps and it is important to understand both: 1. Generation: OTTO analyzes your pages and produces SEO element suggestions. This happens automatically once OTTO is connected and activated for your site. No changes are made to your live site at this stage. 2. Deployment: You review the generated suggestions and choose to approve and deploy them. Deployment pushes the changes to your site. By default, OTTO does not deploy changes without your approval. This two-step process ensures you maintain full control over what goes live. OTTO is designed to assist your workflow, not replace your editorial judgment. 🍀 How the 'I'm Feeling Lucky' Button Works The I'm feeling lucky button is a bulk-action shortcut available inside the OTTO dashboard. Here is exactly what it does: - It automatically approves and queues all currently generated suggestions across the selected task category for deployment in one click. - It does not skip the deployment mechanism — it simply removes the need to approve each suggestion individually. - It applies only to suggestions that have already been generated and are waiting in your review queue. It does not trigger new generation. Important limitations to know before using this button: - Once you click I'm feeling lucky, the batch approval cannot be undone in bulk. You would need to revert individual changes manually. - It is best suited for sites where you have already reviewed a sample of OTTO's output quality and are confident in its recommendations. - This button does not bypass credit consumption. Credits are still used per deployment action. 💳 Credit Costs for OTTO Actions OTTO actions consume credits from your Search Atlas plan. Here is how credits apply: - Generation: Generating suggestions consumes credits based on the number of pages analyzed and elements produced. - Deployment: Deploying approved suggestions also consumes credits. Using I'm feeling lucky to deploy in bulk will consume credits proportional to the number of changes deployed. - You can monitor your remaining credits inside your account settings at any time. If you are concerned about credit consumption before using bulk deployment, review a sample of OTTO's suggestions first and use selective approval for your most important pages. 🚫 Can OTTO Deploy Changes Without Manual Verification? Currently, OTTO does not fully auto-deploy without any human interaction. The workflow always produces a review queue that requires at least one explicit action from you — either approving suggestions individually or using the I'm feeling lucky button to approve all at once. There is no setting at this time that causes OTTO to detect, generate, and deploy SEO elements to your live site in a fully automated loop without any user input. This is an intentional safeguard to protect site quality and give you editorial control. 📡 Dynamic Indexing: What It Is and Who Can See It Dynamic Indexing is a Search Atlas feature that helps accelerate the discovery and indexing of your site's pages by search engines. It works by intelligently signaling updated and new content so that crawlers prioritize those pages. Is Dynamic Indexing visible to your end users (site visitors)? No. Dynamic Indexing operates entirely at the technical infrastructure level. It involves interactions between Search Atlas, your site's sitemap or API endpoints, and search engine crawlers. Your site visitors do not see any interface, badge, or indicator related to Dynamic Indexing. What you can see as a Search Atlas user: - Indexing status reports inside the OTTO dashboard showing which pages have been submitted and their crawl status. - Logs of indexing requests sent on your behalf. - Page-level visibility into which URLs are pending, indexed, or flagged for re-indexing. To review Dynamic Indexing activity, go to OTTO SEO → SEO Automation in the left sidebar and select your site, then navigate to the Indexing section within OTTO's task panel. 📋 Quick Reference Summary - OTTO generation: Automatic, produces a review queue, no live changes yet. - OTTO deployment: Requires your approval — individual or via I'm feeling lucky. - I'm feeling lucky: Bulk-approves all queued suggestions for deployment in one click; cannot be bulk-undone. - Auto-deploy without verification: Not currently available. - Credits: Consumed at both generation and deployment stages. - Dynamic Indexing: Invisible to site visitors; fully technical and backend-facing. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🔧 OTTO Deployments Not Rendering on React SPA Sites

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

🚀 Deploy All Site Audit Suggestions Correctly

🔍 Overview The Deploy All button in the OTTO SEO V3 tool lets you apply AI-generated SEO suggestions — such as title tags, meta descriptions, and other on-page fixes — to your site in bulk. However, there is an important workflow step that must be completed first: AI suggestions must finish generating before Deploy All will apply them all. If you click Deploy All too early, only the suggestions that have already been generated at that moment will be deployed. This is the most common reason customers see partial deployments, such as 10 out of 55 title tags being applied. ⚙️ How the Deploy All Workflow Works 1. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). 2. Add your domain and complete the initial site setup if you have not already done so. 3. Once the site is connected, OTTO SEO V3 will begin crawling your site and generating suggestions for each page. This process runs in the background and can take several minutes depending on the size of your site. 4. Wait for suggestion generation to complete. You will see a progress indicator showing how many suggestions have been created. Do not click Deploy All until this process is finished. 5. When all suggestions are ready, click Deploy All to apply every generated suggestion to your site at once. ⚠️ Why Only Some Suggestions Deployed If you clicked Deploy All before suggestion generation was complete, the system deployed only the suggestions that existed at that moment. The remaining suggestions were still being generated in the background and were not yet available to deploy. This is the most common cause of partial deployments. It is not a bug — it is a timing issue in the workflow. 🛠️ How to Fix a Partial Deployment If you have already deployed a partial set of suggestions, follow these steps to deploy the rest: 1. Go to Left sidebar → OTTO SEO → SEO Automation. 2. Select your domain from the dashboard. 3. Wait until the suggestion generation progress indicator shows that all suggestions are complete. 4. Review the remaining undeployed suggestions to confirm they look correct. 5. Click Deploy All again — this will apply only the suggestions that have not yet been deployed, so previously deployed items will not be duplicated or overwritten. 💡 Best Practices for Deploying Suggestions - Always wait for full generation before deploying. Check that the progress indicator shows 100% or a completed status before clicking Deploy All. - Review suggestions before deploying. You can browse individual suggestions by page or by suggestion type — such as title tags or meta descriptions — to confirm the AI recommendations meet your expectations. - Deploy in stages if preferred. Instead of using Deploy All, you can select specific suggestion categories or individual pages and deploy them separately for greater control. - Check your deployment log. After deploying, review the log inside OTTO SEO V3 to confirm how many suggestions were successfully applied and identify any that may need manual attention. ❓ Frequently Asked Questions How long does suggestion generation take? Generation time depends on the number of pages on your site. Small sites may complete in a few minutes; larger sites can take longer. You will see a live progress indicator inside the OTTO SEO V3 dashboard. Will clicking Deploy All a second time overwrite what was already deployed? No. Deploy All only applies suggestions that have not yet been deployed. Already-deployed suggestions are not affected. Can I deploy suggestions for just one type, like title tags only? Yes. Inside OTTO SEO V3, you can filter suggestions by type and deploy a specific category rather than all suggestions at once. 🆘 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 Agent Slow to Deploy H1 Tags

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

OTTO VisIQ Suggested Fixes Not Saving or Deploying

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

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

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

⚠️ Atlas AI Agent: NLP Terms Not Fully Deploying

The Atlas AI Agent may stop after the first batch of NLP terms — or report "no deployable fixes" — before finishing the full deployment. Re-prompting the agent with your original request will complete the process. 🔍 What's Happening The Atlas AI Agent processes NLP terms in batches. It may stop before completing all batches in a single session. Symptoms you may notice: - The agent reports "no deployable fixes" even when NLP terms are clearly pending. - The agent deploys only the first batch of NLP terms, then stops. - You need to re-prompt the agent multiple times before all NLP terms are deployed. This affects you if you're using the Atlas AI Agent to deploy NLP terms in bulk or in batches. 🛠️ Workaround Steps Follow these steps in the Atlas AI Agent chat to complete the full NLP terms deployment: 1. Open the Atlas AI Agent chat and send your original NLP terms deployment request. 2. Wait for the first batch to finish deploying. 3. Re-send the same deployment request after each batch completes. 4. If the agent replies with "no deployable fixes," dismiss the message and prompt it again with the same original request. 5. Repeat steps 3 and 4 until the agent confirms that all NLP terms have been deployed. You'll know the deployment is complete when the Atlas AI Agent confirms there are no remaining NLP terms to deploy. 📡 Engineering Status Our team is aware of this issue and is actively investigating a permanent fix so the Atlas AI Agent can complete NLP terms deployments in a single session without requiring re-prompts. Until the fix ships, the workaround above will get your full NLP terms list deployed successfully. We apologize for the inconvenience. 📞 When to Contact Support Reach out to Search Atlas support if: - You've repeated the workaround multiple times and NLP terms are still not deploying. - The Atlas AI Agent stops responding or shows an error other than "no deployable fixes." - You're unsure whether your NLP terms deployed successfully. Send a message through the in-app chat and include a brief description of what you've tried so the support team can assist you faster. 🌀 The re-prompt workaround will get your full NLP terms list deployed while our engineering team works on a permanent fix — if you continue to hit issues, contact Support through the in-app chat.

OTTO Deployed but Changes Not Showing Live

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