OTTO deploys SEO fixes directly to your live site via the OTTO Pixel or Cloudflare integration. This article explains the enable/disable toggle, deployment timing, update frequency, and the difference between OTTO fixes and AI-generated content. # **⚙️ What does it mean when OTTO is "enabled"?** The OTTO toggle controls whether your **already-deployed fixes** render live on your website — it does not deploy new fixes. **A fix can be in one of three states:** 1. **Recommended** — surfaced by OTTO but not yet applied 2. **Deployed** — saved to OTTO, but only live if the toggle is ON 3. **Live** — deployed + toggle ON = rendering on your site 🟢 **When OTTO is turned ON:** - All previously deployed fixes (technical, content, schema, links) begin rendering on the site - The OTTO Pixel becomes active. OTTO supports two rendering modes: - **Client-side via the OTTO Pixel** — JavaScript injection seen by users and JS-rendering bots like Googlebot - **Edge-level via the Cloudflare DNS integration** — raw HTML modification seen by all crawlers, including non-JS AI bots such as ChatGPT, Perplexity, and Claude. Note: AI crawlers and non-JS bots only see edge-rendered content, not JS-injected fixes. 🔴 **When OTTO is turned OFF:** - Fixes remain saved in your dashboard - Nothing renders live — your site reverts to its pre-fix state - Useful for testing, staging, or temporary pauses ⚠️ **Cloudflare sync issue:** If your site unexpectedly reverts to its pre-fix state while the OTTO toggle remains ON, this may be a known sync issue with the Cloudflare integration. Contact support — do not repeatedly re-toggle, as the root cause is unrelated to the toggle state. ⚠️ **Cloudflare double-encoding fix:** If special characters (such as & or apostrophes) appear as raw HTML entities on your site, this was caused by a double-encoding bug in the Cloudflare Worker script. The fix has been deployed — disconnect and reconnect your Cloudflare integration from OTTO settings to apply it. ⚠️ **Edge rendering and H1 fixes:** Edge-level rendering applies to most fix types including Title Tags, Meta Descriptions, and Schema. To confirm AI crawlers see an updated H1, use a raw HTTP fetch tool (e.g. `curl`) to check the edge-rendered HTML before and after deployment. ⚠️ **Key reminder:** The toggle activates or deactivates rendering of already-deployed fixes — it does not deploy new fixes. 💡 **Deploy workflow:** 1. In the OTTO dashboard, make your optimizations. 2. Click **Deploy** next to each fix to push it to your site. 3. Confirm the main OTTO toggle (top of the dashboard) is set to **ON** — this activates rendering of all deployed fixes. Both steps — Deploy **and** toggle ON — are required for changes to appear on your live site. Editing a previously deployed fix requires re-deploying it; toggling ON/OFF alone will not push new edits. # **✅ How can I verify whether OTTO fixes have been deployed?** Verify whether OTTO fixes are live on your site using built-in tools or browser inspection. **Three ways to check deployments:** 1. **Search Atlas Chrome Extension** - Scan the page to see which fixes are active - View deployed schema, content blocks, and technical optimizations 2. **Browser Inspection (Chrome DevTools)** - Open the **Elements tab** and check for OTTO-injected HTML (e.g., schema markup in ``, updated headings) - Confirm the OTTO script is loading in the **Network tab** 3. **Support Team Assistance** - Message our team — we'll confirm deployments and troubleshoot any rendering or caching issues ⚠️ **Unexpected injected content:** If OTTO is adding unexpected text to your site (e.g. modified headings), check your deployed fixes in the OTTO dashboard. Fixes such as Heading Length may alter visible heading text — undeploy the relevant fix to remove the content from the frontend immediately. 💡 **Pro Tip:** OTTO changes are client-side rendered and won't appear in your CMS. Always verify on the live site. # **⏱️ How long does deployment take? Do fixes stay live?** OTTO offers flexible deployment options, whether you're fixing one page or your entire site. Timing depends on the deployment method you use. ⚡ **Single Fix Deployment:** - Instantly pushed to your site - Ideal for testing or reviewing changes page by page - Changes are visible as soon as the page is refreshed 📦 **"Deploy All" (bulk deployment):** - Deploys a batch of selected fixes across multiple pages - May take a few minutes to propagate, depending on: - The number of fixes - Your site's pixel load time - CDN or browser caching 💡 **Pro Tip:** After a bulk deploy, clear your browser cache or open a new incognito window to verify live rendering. Fixes stay live as long as the OTTO Pixel is active and your subscription is valid. # **🔄 How often does OTTO update with new fixes or issues?** OTTO continuously syncs with your **Site Audit** crawl schedule to detect and suggest new opportunities — but not all features refresh automatically. **What updates with each crawl:** - 🛠️ **Technical issues** (e.g., broken links, redirects, loading errors) - 🔗 **Internal link suggestions** (anchor updates, orphaned pages) - 🔍 **Missing keywords** (from content vs. ranking gaps) These refresh every time your site is re-crawled, based on your configured schedule (daily, weekly, or manual). **What does not auto-refresh:** - 🗺️ **Topical Maps** and **semantic models** - Generated using a snapshot of GSC + NLP data - Do not auto-update with new queries or rankings - To update, **rebuild the Topical Map** manually **Where to manage crawl settings:** - Go to **OTTO SEO > All Sites > Select your project > OTTO Settings (Crawl Parameters)** - Choose how often OTTO checks for new technical or keyword insights 💡 **Pro Tip:** Set crawls weekly for dynamic sites, or monthly for stable ones. # **🤖 What is the difference between OTTO fixes and AI-generated content?** Search Atlas separates SEO automation into two functions — **OTTO Fixes** and **AI Content Creation** — each serving a distinct purpose in your strategy. ## **⚙️ What are OTTO Fixes?** - **Purpose:** Improve existing site elements for SEO - **What it does:** - Optimizes titles, meta descriptions, H1s, and canonicals - Adds schema markup, alt text, internal links, and keywords - **Custom HTML** — via the OTTO Agent, you can create and deploy custom HTML blocks. HTML is validated before deployment and can be previewed prior to going live. - **How it's applied:** Injected into your live site via the OTTO Pixel or plugin — visible to Google and users instantly - **Example:** Fixes 90 title tags across your site in seconds without changing your CMS ## **✍️ What is AI-Generated Content?** - **Purpose:** Create new SEO-optimized content at scale - **What it does:** - Generates blog posts, product pages, landing pages, and press releases - Writes using AI models guided by SEO context, keywords, and tone - **Where it's stored:** Accessible in the **Content Assistant** — publish to WordPress, export, or schedule - **Scalable tools:** Use **Topical Maps**, **Hyperdrive**, or **Bulk Writers** for mass content output ## **🧠 Summary** - **OTTO** = real-time technical SEO improvements to existing pages - **AI Content** = new, long-form content creation based on strategy and prompts They are complementary. OTTO strengthens on-page elements, while Content Genius expands your site's footprint with new content. OTTO handles technical SEO fixes on live pages; Content Genius creates new articles and long-form content based on your strategy. **🎯 You now know how to enable, deploy, and verify OTTO fixes on your live site — and when to reach for AI content creation instead. Contact the Search Atlas support team if fixes aren't rendering as expected, or explore the OTTO dashboard to start optimizing today.**