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:
- In Search Atlas, navigate to the OTTO section and locate the relevant project and page.
- Review the optimizations that OTTO has deployed for that page, including any heading, title, or content changes.
- Open your website builder and navigate to the same page.
- Manually replicate each change—update headings (H1, H2, H3), meta titles, and descriptions to match what OTTO deployed.
- Save and publish the page in your builder.
- 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:
-
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.