OTTO SEO
By Camilo Aponte
By Camilo Aponte
OTTO pixel installation, deployments, schema and on-page optimization.
Onboarding
Content Injection & Cleanup
Deployment & Rendering
Features & How-To
Pixel Installation: General Setup & Verification
Pixel Installation: Google Tag Manager & Cloudflare
Pixel Installation: Shopify
Pixel Installation: Webflow, GoDaddy & Other Builders
Pixel Installation: Wix & Squarespace
Schema & Structured Data
WordPress
Troubleshooting: Audits, Crawl & Indexing
Troubleshooting: Billing, Sites & Top-Ups
Troubleshooting: Deployment & Live Changes
Troubleshooting: Pixel Pending, UUID & Verification Errors
Troubleshooting: Pixel on GoHighLevel & Other Builders
Troubleshooting: Pixel on Shopify, Wix & Squarespace
Troubleshooting: Pixel on WordPress
Troubleshooting: Pixel, Cloudflare, GTM & Caching
Troubleshooting: Platform Conflicts & Caching
Troubleshooting: Scanning, Reprocessing & Knowledge Graph
Troubleshooting: Schema Errors
Troubleshooting: Titles, Meta & Headings
Troubleshooting: Wrong or Duplicate Content
🛠️ Fix OTTO Title Tag Deployment Status Not Updating
🔍 Overview Some customers notice that OTTO title tag deployments continue to show as not deployed. This article explains what information to collect when the deployment status does not update so the issue can be investigated accurately. ⚙️ What to Check Confirm which title tag recommendation or URL is affected and note whether the deployment action completed successfully. The available information does not confirm a specific cause or self-serve fix for this status issue. 🚀 When to Contact Support If the status remains unchanged, contact support with the project or site name, the affected URL or URLs, the exact title tag recommendation, the time and date of the deployment attempt, and any error message or confirmation shown. Include a screenshot if available and note whether the issue affects one page or multiple pages. ✅ What Happens Next Support can use these details to investigate whether the deployment was processed and why the displayed status has not updated. Avoid repeating the deployment until the original attempt has been reviewed. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🛠️ Fix OTTO Deployment Count and Freezing Issues
🔍 Overview Some customers experience OTTO deployment count issues or a frozen, unresponsive interface. These symptoms may affect deployment status visibility and prevent normal interaction with OTTO. ⚠️ Common Symptoms - OTTO deployment counts appear incorrect. - The OTTO interface freezes or becomes unresponsive. - Clicks or other interactions stop working. 🛠️ What to Do Because these symptoms can indicate an OTTO platform issue, there is no confirmed self-serve resolution documented for this problem. Avoid repeatedly retrying deployments if the interface is frozen. When escalating the issue, have the affected client or project name, the deployment count shown, the approximate date and time of the issue, a description of what happened before the interface froze, and any screenshots or exact error messages available. Note whether the issue affects one client or multiple clients. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🛡️ Allowlist OTTO SEO in Cloudflare WAF and CSP
🔍 Overview OTTO SEO needs to crawl your site and load its scripts without being blocked by your server's firewall or Content Security Policy (CSP). This article explains the areas to review when troubleshooting access problems in Cloudflare or another security layer. ⚠️ Review Your WAF Configuration Check your Cloudflare WAF and any other firewall, security plugin, or server-level protection that could block OTTO SEO's crawler. Review the security events and blocked requests associated with your site, then create an exception for the crawler according to the identifier and guidance provided for your account. If you use a third-party WAF or firewall plugin, review its allowlisting documentation and apply the equivalent exception there as well. 🌐 Review Your Content Security Policy If your site sends a Content-Security-Policy HTTP header, review the directives that control scripts, connections, and other resources required by OTTO SEO. Confirm that your policy permits the Search Atlas resources used by your site, based on the domains shown in your account or provided by Search Atlas support. - script-src — review whether required OTTO SEO scripts are permitted. - connect-src — review whether required connections are permitted. - img-src — review whether required image resources are permitted. ✅ Test After Updating Your Rules After updating your WAF or CSP, retry the affected OTTO SEO action and check your browser console, server logs, and security events for blocked requests. If requests are still blocked, record the exact error, affected domain, and timestamp before escalating 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 instantly connected with a member of our team.
⚙️ Update OTTO Schema and Descriptions
🔍 Overview OTTO can update your website’s cloud schema and meta descriptions. After changes are created or published, the live site may continue showing older data temporarily because deployment, page caching, or content delivery networks can delay the update. 🚀 Start an OTTO update 1. Open OTTO SEO from the left sidebar. 2. Select the relevant project and review its current status. 3. Use Create to generate or update recommendations for schema and meta descriptions. 4. Use Scan when you need OTTO to recheck the current site content before making changes. 5. Review the proposed updates and follow the available publishing or deployment prompts. 📊 Check deployment status After publishing, allow the deployment to finish before checking the live site. A completed action in OTTO does not always mean that every cached version of the page has refreshed. - Confirm that the correct project and domain are selected. - Check whether the update is still processing, queued, or complete. - Verify that the intended URL is included in the project and is accessible to search engines. - Wait for deployment and caching to complete before comparing the page again. 🧪 Verify schema and meta descriptions 1. Open the affected live URL in a private browser window. 2. View the page source or inspect the rendered HTML. 3. Search for the updated meta description and relevant JSON-LD properties, such as Product or hasProduct. 4. Compare the live output with the latest version shown in OTTO. Search results may not update immediately after the page source changes. Search engines can retain previously crawled descriptions until they recrawl the page. 🛠️ Troubleshoot stale live data - Deployment is incomplete: Wait until the update finishes, then verify the URL again. - Page or CDN cache is stale: Purge the relevant cache if your hosting or caching setup provides that option. - Multiple schema sources exist: Check whether your CMS, theme, plugins, or another SEO tool is adding older Product or hasProduct JSON-LD. - The wrong page was checked: Confirm the URL, canonical address, language version, and project domain. - Source and rendered HTML differ: Check the page after JavaScript loads, since some sites add metadata dynamically. - Search results still show old text: This can be normal until the page is crawled again; it does not necessarily mean the deployment failed. ✅ Best practices - Change one set of metadata at a time and record the affected URLs. - Keep only one trusted source for each schema property where possible. - Recheck both the page source and the rendered page after deployment. - Do not repeatedly republish while an earlier deployment is still processing. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🛠️ Reset Playbook Cooldown After Errors
🚦 What causes the Playbook cooldown? OTTO may place a temporary cooldown on a Playbook after repeated redirect errors or unsuccessful actions. This protects your site from additional changes while the issue is reviewed. 🔍 Check the OTTO error first 1. Open AI SEO → OTTO SEO from the left sidebar. 2. Review the affected Playbook and its error details. 3. Confirm that the target URLs, redirect destinations, and site access are correct. 4. Fix any redirect loops, invalid destinations, missing pages, or conflicting rules on your site. 🔄 Request a cooldown reset Customers cannot manually override a Playbook restriction from the interface. After correcting the underlying redirect issue, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team. Include the project, affected Playbook, approximate failure time, and the error message. Our team can review the failure and determine whether the cooldown can be reset safely. 📊 Review possible crawl charges If repeated failures may have triggered multiple crawls, include the approximate dates and times in your message. Our team can review the related activity and explain any applicable usage or billing impact. Do not repeatedly retry the Playbook while the issue is being investigated. ✅ Prevent repeat failures - Test redirect destinations in a browser before retrying. - Check that URLs use the correct protocol, domain, and path. - Remove redirect loops and chains where possible. - Wait for the cooldown review before starting another Playbook run. - Keep the error details available so the issue can be diagnosed quickly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🛠️ Fix OTTO Content Persisting After Removal
🔍 Overview When OTTO SEO deploys optimizations to your website — such as adding text like "24/7" to a page — it writes those changes through a synchronization layer that operates independently of the page editor. This means that simply editing or deleting the text in your page builder, or even deactivating the Search Atlas plugin, may not be enough to remove the deployed content from your site's frontend. This article explains why this happens and walks you through the correct steps to fully remove OTTO-deployed content. ⚙️ Why Does This Happen? OTTO deploys optimizations by pushing content through a metadata sync process, separate from what you see in your page builder (such as Elementor, Gutenberg, or another editor). Because of this architecture: - Deleting text directly in your page editor may not remove the value OTTO has stored in the background metadata fields. - Deactivating the Search Atlas plugin stops new deployments but does not automatically roll back content that has already been written to your site. - Cached versions of your pages may continue to serve the old content even after changes are made. ✅ How to Fully Remove OTTO-Deployed Content Follow these steps in order to ensure OTTO-deployed content is completely cleared from your site. 1. Log in to Search Atlas and navigate to OTTO SEO → All Sites (SEO Automation) using the left sidebar. 2. Locate the deployed optimization you want to remove. Find the specific page and the optimization item (for example, the text element containing "24/7"). 3. Un-deploy the optimization by toggling it off or selecting the option to revert/remove the deployment. This is the critical step — it instructs OTTO to clear the metadata fields it originally wrote, rather than leaving them in place. 4. Confirm the change is reflected on your site by visiting the page on the frontend. Allow a few minutes for the update to propagate. 5. Clear your site's cache. If you use a caching plugin (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache) or a CDN (such as Cloudflare), purge the cache for the affected page or your entire site to ensure visitors see the updated version. 6. Check your page builder. After un-deploying through OTTO, open the page in your editor and confirm the content no longer appears. If it remains, manually delete it as a final clean-up step. ⚠️ Important Notes - Deactivating the plugin is not the same as un-deploying. Always use the un-deploy action inside OTTO SEO → All Sites (SEO Automation) before deactivating or uninstalling the Search Atlas plugin. - Cloudflare and CDN users: Deployments passing through Cloudflare DNS may take slightly longer to clear. After un-deploying, wait a few minutes and purge your CDN cache before checking the frontend. - Elementor users: In some cases, OTTO's H1 or content optimizations may interact with Elementor's rendering. If you notice display issues after un-deploying, re-save the affected page in Elementor to refresh its output. - Staging or subdomain environments: If you are working on a staging or subdomain setup, note that OTTO deployment behavior on these environments may differ. Contact support if you encounter unexpected persistence on a staging site. 🔄 Step-by-Step Summary 1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar. 2. Find the optimization on the affected page. 3. Un-deploy the optimization through the OTTO interface. 4. Clear your site cache and CDN cache. 5. Verify the content is gone on the frontend. 6. Manually remove any remaining content in your page editor if needed. 💬 Still Seeing the Content? If you have followed all the steps above and the content is still appearing on your site's frontend, there may be a deeper caching or synchronization issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
🔍 Find SEO Issues and Affected Pages in OTTO
🗺️ Overview OTTO SEO includes a built-in Site Audit tool that scans your website and surfaces SEO issues grouped by type. This article walks you through how to navigate to the audit, locate affected pages, and understand the information available so you can start fixing issues quickly. 🚀 Step 1: Open OTTO SEO 1. Log in to your Search Atlas account. 2. In the left sidebar, click OTTO SEO, then SEO Automation. This takes you to the main OTTO SEO dashboard (All Sites) at /seo-automation-v3. 3. You will see a list of your connected sites under the All Sites view. Active and Deep Frozen sites are shown here. 🌐 Step 2: Select Your Website 1. From the All Sites list, click the website you want to audit. 2. This opens the Overview page for that site, where you can see a high-level summary of your site's SEO health. 3. If you have not yet run a scan, click the Scan button at the top of the Overview page to trigger a fresh crawl of your site. 📋 Step 3: Navigate to All Audits 1. In the left sidebar, click OTTO SEO, then Site Audit, then select All Audits. 2. This page lists every audit that has been run for your connected sites, along with the scan date and a summary of issues found. 3. Click on a specific audit to open the full audit report for that scan. 🔎 Step 4: Browse Issues and Find Affected Pages Inside the audit report, issues are organised by category — for example, missing meta titles, broken links, slow page speed, and more. Here is how to drill down to the affected pages: 1. Scroll through the Issues section to see all detected SEO problems, each showing a count of how many pages are affected. 2. Click on any issue to expand it and reveal the list of specific pages that have that problem. 3. Use the View Pages option within an issue to see the full list of affected URLs, along with relevant details such as the current value and the recommended fix. 4. You can sort or filter the list to prioritise the pages that will have the greatest impact on your SEO performance. 📊 Step 5: Use Crawl Monitoring for Ongoing Tracking In addition to on-demand audits, OTTO SEO includes Crawl Monitoring for continuous tracking of your site's health. - Go to Left sidebar → OTTO SEO → Site Audit → Crawl Monitoring to view live crawl data and track newly discovered issues over time. - This is especially useful for large sites where new pages are published frequently or where issues may appear after a site update. 💡 Tips for Getting the Most from Site Audit - Run a fresh scan after making changes to your site so the audit reflects your latest content. - Start with high-impact issues — issues affecting the most pages or flagged as critical will typically deliver the biggest SEO gains when fixed. - Check the Knowledge Base inside OTTO SEO (Left sidebar → OTTO SEO → Knowledge Base) for guidance on how to resolve specific issue types. - Use the Overview page as your starting point each session — it gives a quick summary of your site's overall health score and highlights areas needing attention. 🛠️ Troubleshooting - Audit not loading or showing an error: Refresh the page and try again. If the issue persists, run a new scan from the Overview page. - Page count looks incorrect: This can happen immediately after a new scan finishes. Wait a moment and refresh the audit report to see updated counts. - No issues showing: Confirm that OTTO SEO is properly installed on your site by visiting Left sidebar → OTTO SEO → Installation Guide. 💬 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.
⚡ Set Up OTTO IndexNow
⚡ What IndexNow does IndexNow notifies search engines, including Bing, when your pages are added, updated, or removed. This can help them discover changes faster, but it does not guarantee indexing or ranking. 🔗 Connect Bing to Search Atlas 1. Open your project in Search Atlas and go to the OTTO SEO settings. 2. Open the IndexNow or instant indexing setup area. 3. Choose Bing and follow the connection instructions shown in the platform. 4. If prompted, sign in to Bing Webmaster Tools and select the website that matches your Search Atlas project. 5. Complete any ownership verification requested by Bing. The verified website and project URL must use the same domain and protocol where applicable. If Bing asks you to verify ownership, use one of its available verification methods, such as an HTML file, meta tag, or DNS record. Complete verification in Bing Webmaster Tools before returning to the Search Atlas setup. 🔑 Create the IndexNow key file 1. Copy the IndexNow API key provided during the OTTO setup. 2. Create a plain-text file using that exact key as the file name, followed by .txt. For example, if the key is abc123, the file name is abc123.txt. 3. Save the file as UTF-8 text. Do not add formatting, quotation marks, spaces, or extra text. The file should contain the key itself. 4. Upload the file to the root directory of your website. 📁 Where to upload the file The root directory is the top-level public folder that serves your domain. The file must be reachable at a URL like https://www.example.com/abc123.txt or https://example.com/abc123.txt, depending on the version of your domain used in Search Atlas. Do not place the file inside /wp-content/, /uploads/, a theme folder, or another subfolder. The file must be alongside files such as index.html or the main public website files. 🛠️ Upload options by website type - WordPress: Use your hosting control panel, hosting file manager, SFTP, or a file-management plugin approved by your site administrator. Upload the file to the WordPress installation's public root, usually the folder containing wp-admin and wp-content. - Other hosted platforms: Use the platform's file manager or custom-code/file-upload area. Look for an option that publishes a static file at the domain root, not a page editor or media library. - Git-based or developer-managed sites: Add the file to the repository's public root and deploy the change. - Sites without file access: Ask your hosting provider, developer, or website administrator to upload the UTF-8 file to the public root and confirm its live URL. ✅ Verify the setup 1. Open the key file URL in a browser, such as https://example.com/abc123.txt. 2. Confirm the page displays only the exact key. 3. Check that the URL does not redirect to a login page, 404 page, homepage, or file-download error. 4. Return to the OTTO IndexNow setup and use the verification or test option. 5. Save the configuration and allow time for the first notification to process. 🔍 Common setup problems - The file name does not match the API key exactly. - The key was saved with a hidden extension such as .txt.txt. - The file includes a blank line, spaces, quotation marks, or rich-text formatting. - The file was uploaded to a subfolder instead of the domain root. - The file is available on www, but the project uses the non-www version, or the reverse. - The website blocks crawlers, requires authentication, or redirects the key URL. - Bing ownership verification is incomplete or was completed for a different domain variation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🔑 OTTO DNS Cloudflare API Token Setup Guide
🔍 Overview When installing OTTO via Cloudflare, it is essential to use an account-level API token — not a personal API token. Using a personal token may show a "Connected" status in Search Atlas, but OTTO will not complete installation on your site. This article walks you through creating the correct token so your OTTO installation works immediately. ⚠️ Why Personal API Tokens Do Not Work Cloudflare offers two types of API tokens: - Personal API tokens — scoped to individual user profiles and found at dash.cloudflare.com/profile/api-tokens. These do not grant the account-level permissions required for OTTO to deploy its worker scripts. - Account-level API tokens — created from within your Cloudflare account dashboard. These provide the necessary permissions for worker creation and script deployment, which OTTO requires to install correctly. Even though Search Atlas may display "Connected" with a personal token, the underlying worker deployment will silently fail. Always use an account-level token to ensure full functionality. 🛠️ How to Create a Cloudflare Account-Level API Token 1. Log in to your Cloudflare account at dash.cloudflare.com. 2. From the top navigation, select the account you want to connect to OTTO (not your user profile). 3. In the left sidebar, click Manage Account, then select API Tokens. 4. Click Create Token. 5. Choose Create Custom Token to configure the required permissions manually. 6. Under Permissions, add the following: - Account — Workers Scripts — Edit - Account — Workers Routes — Edit - Zone — Zone — Read - Zone — DNS — Edit 7. Under Account Resources, set the token to apply to your specific account. 8. Under Zone Resources, select All zones or the specific zone (domain) where OTTO will be installed. 9. Click Continue to Summary, review your settings, then click Create Token. 10. Copy the generated token immediately — Cloudflare will only display it once. 🚀 How to Connect the Token in Search Atlas 1. In Search Atlas, navigate to Left sidebar → OTTO SEO. 2. Open or create the OTTO project for your domain. 3. When prompted for your Cloudflare credentials, paste the account-level API token you just created. 4. Complete the connection flow. Search Atlas should display "Connected" and OTTO should begin installing on your site immediately. ✅ How to Confirm OTTO Installed Successfully After connecting with the correct token, verify the installation was successful by checking the following: - The OTTO status in your project shows as Active (visible under Left sidebar → OTTO SEO). - The Cloudflare Workers section of your account shows a new worker script deployed by OTTO. - Your website loads correctly with no disruption to DNS or page performance. 💡 Common Mistakes to Avoid - Using a personal API token — always create the token from the account dashboard, not your user profile page. - Missing permissions — ensure all four permission sets (Workers Scripts, Workers Routes, Zone Read, DNS Edit) are included. Missing any one of them can prevent deployment. - Wrong zone scope — if the token is scoped to the wrong zone, OTTO cannot access your domain. Double-check the zone resources during token creation. - Token copied incorrectly — the token is shown only once. If you missed copying it, delete it and generate a new one. 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
⚙️ OTTO SEO and Webflow: Current Limitations Explained
🔍 Overview OTTO SEO connects to your website through a JavaScript pixel that is installed on your pages. On some platforms, OTTO can write changes directly to your page content at the source level — meaning edits land inside the actual CMS and persist as real content updates. On Webflow, this deeper integration is not yet available. This article explains what that means for your site, why the limitation exists, and what the current situation looks like. ⚙️ How the OTTO Pixel Works on Webflow When you install OTTO on a Webflow site, the pixel is injected as a client-side JavaScript snippet. This means OTTO can: - Read and analyse your page content - Surface SEO recommendations and audit findings - Apply certain on-page changes via the browser at render time However, because the pixel operates client-side, it cannot write changes back into Webflow's CMS or Designer. Any modifications OTTO applies are rendered in the browser layer — they are not stored as permanent edits inside your Webflow project. 🚧 Why a Source-Level Fix Is Not Yet Available Webflow uses a closed Designer environment and a separate CMS API that requires a different integration approach — one that goes beyond what a client-side pixel can do on its own. Bridging OTTO's automation engine with Webflow's CMS API at a source level is a significant technical undertaking, and this capability is not currently available. 📊 What This Means for Your Webflow Site Right Now If you are running OTTO on a Webflow site, here is what you can expect: - SEO audits and recommendations work fully — OTTO will scan your site and surface issues through the standard audit workflow. - Client-side optimisations applied by the pixel are active while the pixel is loaded, but are not written into Webflow's source content. - Manual implementation is currently required — to make OTTO's recommendations permanent, you or your team will need to apply the suggested changes directly inside the Webflow Designer or CMS editor. 🛠️ Interim Workaround: Applying OTTO Recommendations Manually in Webflow While native CMS-write is unavailable, you can still action every OTTO recommendation by following these steps: 1. Run an OTTO audit on your Webflow site. Navigate to OTTO SEO → Site Audit in the left sidebar, select your project, and open the Audit or Recommendations panel to see a prioritised list of issues. 2. Export or note the specific recommendations — for example, missing meta titles, meta descriptions, heading structure issues, or alt-text gaps. OTTO surfaces the exact field and suggested value for each finding. 3. Log in to your Webflow project and open the page or CMS Collection that contains the flagged content. 4. For static pages: Open the page in the Webflow Designer, click the relevant element or use the SEO settings panel (Page Settings → SEO tab) to update meta title, meta description, Open Graph fields, or on-page content as recommended by OTTO. 5. For CMS Collection items: Go to your Webflow CMS editor, open the relevant Collection, and edit the individual item fields (e.g., SEO Title, Meta Description, or custom fields) to match OTTO's suggested values. 6. Publish your Webflow site after making changes so that updates go live and are reflected when OTTO re-scans the page. 7. Re-run the OTTO audit to confirm the issues are resolved and track your progress over time. Repeating this workflow for each audit cycle allows you to systematically implement OTTO's recommendations even without automated CMS-write support. 🗺️ Roadmap Status A native, source-level Webflow integration — one that writes changes directly into your Webflow CMS — is not available at this time. There is no confirmed delivery date for this capability. If you need further assistance, open 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 <title> 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.
⚙️ Install and Update OTTO
🛠️ Why the OTTO script may cause slowdowns OTTO can affect site performance when an older installation script is still active or when the script points to a white-label domain that is no longer configured correctly. This can happen even when the script was originally copied from the installation instructions. Use the latest installation code shown in your Search Atlas account. Do not manually edit the script or reuse code from another project. 📋 Get the current OTTO installation script 1. Sign in to Search Atlas. 2. Open AI SEO → OTTO SEO from the left sidebar. 3. Open the relevant project. 4. Find the OTTO installation or connection instructions. 5. Copy the complete, current script provided for that project. 🔄 Replace the script on your website 1. Remove the previous OTTO script from your website, tag manager, theme, or plugin. 2. Paste the newly copied script in the same location recommended by the instructions. 3. Make sure the script is added only once. Duplicate installations can create extra requests and slow down page loading. 4. Publish the website or tag manager changes. If your site uses a content management system, caching plugin, CDN, or tag manager, publish and clear the relevant cache after replacing the script. 🌐 Check for white-label configuration issues The installation script must point to the domain and configuration provided in your current OTTO instructions. Do not replace its destination with a custom or white-label URL unless that URL is actively configured for your account. If the script contains an outdated white-label reference, remove it and copy the latest script from the OTTO installation instructions. This ensures the connection uses the correct Search Atlas configuration. ✅ Verify the installation 1. Open your website in a private browser window. 2. Confirm that the page loads normally and that OTTO is still active in the Search Atlas project. 3. Use your browser’s developer tools to confirm that the OTTO script loads successfully without repeated errors. 4. Test several pages, especially pages using different templates. 5. Monitor page speed after publishing the change. 🧹 If performance issues continue - Confirm that only one OTTO script is installed. - Check your theme, tag manager, plugins, and CDN for an older copy. - Clear website, CDN, and browser caches. - Confirm that the script was copied from the correct OTTO project. - Check whether other scripts are contributing to the slowdown. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🔍 Investigating Spam Links in OTTO Generated Blogs
🔍 Understanding Spam Links in OTTO Blogs Spam links can appear in blogs created by OTTO SEO when content generation pulls from unverified external sources or when link filters are not applied. This issue affects multiple sites if project settings allow broad content scraping without quality checks. 🛠️ Steps to Investigate the Problem Start by reviewing recent blog posts in your OTTO SEO projects. Check for any links pointing to low-quality or unrelated domains. Use the AI Visibility section under OTTO SEO to scan active projects and identify patterns in generated content. 1. Navigate to Left sidebar then OTTO SEO. 2. Select the affected project from the Active list. 3. Review blog output for embedded links and note any spam patterns. 4. Compare across multiple sites to see if the issue is widespread. 🚀 How to Prevent Spam Links Configure your OTTO SEO settings to restrict link sources and enable content validation before publishing. Apply these changes to all projects to avoid recurrence. - Set strict domain filters in project creation to block known spam sites. - Enable quality scoring for all generated content in the AI Visibility tools. - Review and approve links manually for new blogs until filters are tuned. - Run regular scans on all active projects to catch issues early. 📊 Monitoring and Ongoing Checks Schedule periodic audits using the Visibility and Topics sections to maintain clean content across sites. Update filters as new spam sources emerge to protect your entire account. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🗺️ Update OTTO Topical Map Seeds
🧭 How seed keywords work When you create an OTTO topical map, its seed keywords are set for that map. Updating seed keywords in Brand Vault does not change the seeds in a map that already exists. Refreshing the existing map will not apply the updated Brand Vault seeds. 🔄 Create a replacement map 1. Update the seed keywords in Brand Vault. 2. In the left sidebar, select OTTO SEO. 3. Open the topical maps area and start creating a new topical map for the page or site you want to target. 4. Use the updated seed keywords when setting up the new map, then create it. A new map is needed to use the revised seeds. The existing map remains unchanged; refreshing it does not replace its seed keywords. ✅ Check the new map Open the newly created map and confirm that it uses the intended seed keywords. If it does not, check the seeds selected during map creation. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
⚙️ Make OTTO Changes Permanent in WordPress
🔍 How OTTO changes appear on your site OTTO can apply SEO changes in two ways. A change may be served by OTTO without being saved to your WordPress SEO plugin, or it may be written into supported plugin fields using Sync to CMS. To make supported changes persist in WordPress, enable Sync to CMS before deploying them. ⚙️ Enable Sync to CMS 1. In Search Atlas, open OTTO SEO from the left sidebar. 2. Find the Sync to CMS setting and turn it on. 3. Deploy the OTTO changes you want saved to WordPress. Sync to CMS applies only to supported fields. Changes that are not supported may still be served by OTTO without being saved to your WordPress SEO plugin. 🔄 If deployed changes are not showing - Confirm that Sync to CMS was enabled when you deployed the changes. Turning it on afterward may not save changes that were already deployed; redeploy them with the setting enabled. - Check the corresponding fields in your WordPress SEO plugin to see whether the values were written there. - Allow the site to refresh, then reload the page and check the result again. - If the values are saved in WordPress but the live page still shows old content, check whether your site or browser is showing a cached version. ⚠️ Before undeploying changes Undeploying OTTO changes may not restore the values that were in WordPress before OTTO updated them. Review and record existing values before deploying, and check the WordPress SEO plugin after undeploying. Do not assume undeploying will restore previous values automatically. 💬 Need help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🔧 PRO Plan OTTO Activations Explained
🔍 Quick Answer The Search Atlas PRO Plan includes 4 OTTO activations. If you have seen or been told that the PRO Plan includes 10 activations, that information is incorrect. This article explains what an activation is, how to check yours, and what to do if you need more. 💡 What an OTTO Activation Is An OTTO activation connects OTTO SEO to one project in your Search Atlas account. Once activated, OTTO analyzes the connected website and begins implementing SEO improvements automatically. Key points to remember: - Each activation covers one project (one website). - Activations are tied to your plan tier, not to individual users on your team. - The PRO Plan includes 4 OTTO activations. - Higher-tier plans include more activations — you can compare options under Billing. 📊 How to Check Your Remaining Activations To see how many OTTO activations your plan includes and how many you have used: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing from the Avatar Menu (👤). 3. Open the Plans & Top-ups tab. 4. Review your current plan details, including your OTTO activation total and remaining balance. To see which projects already have OTTO connected, go to Home in the left sidebar and review your selected projects list. 🚀 How to Get More Activations If you manage more than four websites and need additional OTTO activations, you can move to a higher-tier plan: 1. Click your avatar in the top-right corner and select Billing. 2. Open the Plans & Top-ups tab. 3. Click Change Plan or Manage Subscription. 4. Compare the available plans and select the one that matches the number of activations you need. All billing details are shown on screen before you confirm any plan change, so you can review costs and timing before committing. ⚠️ If You Were Told the Limit Is 10 Some earlier conversations and third-party materials incorrectly stated that the PRO Plan includes 10 OTTO activations. The accurate number is 4. If this discrepancy has affected your setup or purchase decision, we recommend the following: - Verify your current plan and activation count under Billing → Plans & Top-ups. - If you need more than 4 activations, follow the upgrade steps in the section above. - If you believe your account or purchase was made based on incorrect information, reach out through the chat widget so our team can review your situation. 💬 Contact Support If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
📊 Download Detailed OTTO SEO Issue Reports
📋 Overview OTTO SEO scans your website for technical SEO issues and organises them into a clear, actionable report. You can review every issue directly inside the platform and download a detailed report to share with your team or clients. This article walks you through the full process. 🔍 Step 1: Open OTTO SEO In the left sidebar, click OTTO SEO. This takes you to your OTTO dashboard where all connected sites and their audit data are displayed. 🌐 Step 2: Select Your Website If you manage more than one site, use the site selector at the top of the page to choose the domain you want to audit. OTTO will load the most recent scan results for that domain automatically. ⚙️ Step 3: Run or Refresh the Site Audit To make sure you are working with the latest data, trigger a new scan: 1. Look for the Re-crawl or Run Audit button near the top of the OTTO dashboard. 2. Click it to start the scan. Depending on the size of your site, this may take a few minutes. 3. Wait for the progress indicator to complete before moving to the next step. If a recent scan already exists and no major changes have been made to your site, you can skip this step and use the existing results. 🛠️ Step 4: Review Technical Issues in the Dashboard Once the audit is complete, OTTO organises all detected issues by category. You will see sections covering areas such as: - Indexability — pages blocked from search engines - Meta tags — missing, duplicate, or over-length titles and descriptions - Page speed — performance factors slowing down your pages - Structured data — schema errors or missing markup - Links — broken internal and external links - Content — thin content, duplicate content, and missing headings Click any category to expand it and see a full list of affected pages along with a description of the problem and the recommended fix for each item. 📥 Step 5: Download the Detailed Issue Report To export the report: 1. Navigate to the issues section or category you want to export. To get a full report, make sure you are viewing all issues rather than a single category. 2. Look for the Export or Download Report button — typically displayed as a download icon or labelled button in the top-right area of the issues table. 3. Click the button. The report will download as a CSV or PDF file to your device, depending on the export option available. 4. Open the file to see every issue listed with its affected URL, issue type, severity level, and the proposed fix or recommended action. 💡 Tips for Getting the Most from Your Report - Sort by severity — prioritise critical and high-severity issues first for the biggest SEO impact. - Filter by category — if you want to focus on one area (for example, only meta tag issues), apply filters before exporting so your report is scoped to that category. - Schedule regular audits — run a fresh scan at least once a week to catch new issues introduced by site updates or new content. - Share with your developer — the exported report is formatted to be shared directly with a developer or technical team member, as it includes both the issue description and the fix. ❓ Frequently Asked Questions Why do I not see a Download button? Make sure the audit has fully completed. If the scan is still running, the export option may not appear yet. Wait for the progress bar to finish and then refresh the page. Can I download reports for individual issue categories? Yes. Navigate into a specific category (for example, Broken Links), then use the export option within that view to download only those issues. How often is the audit data refreshed? OTTO can run automatic scans on a set schedule. You can also trigger a manual re-crawl at any time using the Re-crawl button as described in Step 3. 💬 Need More Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🔗 Add Service Pages to OTTO Links
🔗 Overview OTTO SEO’s Internal Link Suggestions tool does not automatically import service or location pages from Brand Vault. To use these pages in link recommendations, add each one manually through Add Page. 📍 Open Internal Link Suggestions 1. In the Search Atlas left sidebar, select OTTO SEO. 2. Open the Internal Link Suggestions section. 3. Select Add Page to create a suggestion. ➕ Add a Service or Location Page 1. In the Destination page field, enter the service or location page you want to promote. 2. In the Source page field, enter the page where OTTO should place the internal link. 3. Review both URLs to confirm they are correct and use the preferred versions of the pages. 4. Save the suggestion. Repeat these steps for each service and location page. For example, you can set a service page as the destination and a related city or blog page as the source. ✅ Check Your Suggestions After saving the entries, review the Internal Link Suggestions list to confirm that each destination page has an appropriate source page. Use relevant page pairings so visitors and search engines can easily discover related content. 💡 Important Limitation Content Genius may not show your complete list of service and location pages because these pages are not automatically imported from Brand Vault into Internal Link Suggestions. This is expected behavior. Adding the pages manually is currently required. 🛠️ Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.
🔍 OTTO Searched URL Field Blank
🔎 What the field does In OTTO SEO, the Searched URL field accepts a page or image URL and looks for matching Image Alt Text issues. 🧭 Where to find it Open OTTO SEO from the left sidebar, then locate the URL search field. ✍️ How to search a URL 1. Enter the complete URL, including https:// or http://. 2. Confirm the URL points to a page or image that OTTO can access. 3. Submit the search and allow a few moments for results to load. For example: https://example.com/page or https://example.com/image.jpg. ⚠️ Why the field may stay blank A known OTTO issue can cause the field or results to remain blank or continue loading, even when a full URL is entered. This may happen because the search request is not processed correctly by the page. 🛠️ What to try - Check that the URL is complete and contains no extra spaces. - Try a different page or image URL. - Refresh the OTTO SEO page and search again. - Use the latest version of your browser. If the field remains blank or spins indefinitely after these steps, the issue may require a product fix rather than a change to your URL. 💬 Get help If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.