How to Use Search Atlas to Deploy On-Page Fixes With OTTO

The short answer: on a site with a backlog of title, meta and schema fixes nobody has had time to ship, start the 7-day trial (pricing), add the OTTO pixel to the header, verify it, switch on approval mode, exclude the pages that must never change, review and deploy the first category of fixes, check the live pages after clearing caches, roll back anything wrong, then submit the sitemap and give Google 3 to 14 days before judging rankings.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

This is a how-to about letting an agent edit a live website, so it is mostly about the controls. OTTO is the agent: it reads your pages, writes the changes and, by default, deploys them on its own. Every step below is there so that a person decides what goes live. For plans and prices, see the Search Atlas glossary entry.

Before the pixel goes in:

1. Do the sum on the trial. The trial is 7 days and Starter is $99 a month billed monthly for one OTTO site, so a decision after the trial costs either nothing or $99, per the pricing page checked on 24 October 2026. Book the free 30-minute onboarding session in the first two days, while there is time to use what it covers.
2. Use the access you already have. Admin access to the CMS or Google Tag Manager to place the pixel, and the Search Console property for the site.
3. Take a baseline. Export the current title tags and meta descriptions of your top pages, and note their positions in Search Console. If a change goes wrong, that export is what you restore from and measure against.

Step 1: Create the project and copy the pixel

In the dashboard, click OTTO & Audit in the left navigation, click +Create and copy the pixel code, as the OTTO pixel page describes. The same page lists install guides for WordPress, Shopify, Webflow, Squarespace, Wix, ClickFunnels, GHL, Google Tag Manager and custom sites.

Step 2: Put the pixel in the header and verify it

Paste the snippet into the head of every page, through your theme header or a header-scripts plugin, and clear any caching plugin afterwards. Then go to OTTO SEO, SEO Automation, select the site and click Verify Pixel; a green status means the pixel is active, according to the help article on verifying the pixel. The article warns that theme switches typically overwrite header files, so re-check the pixel after every theme change.

Step 3: Switch on approval mode before the first analysis

By default OTTO SEO deploys fixes on its own; approval mode makes it wait for you to review each change, per the pixel page. Turn it on now. This is the human check that makes the rest of the workflow safe: the agent drafts, a person approves.

Step 4: Exclude the pages that must not change

Open the project overview, click the Autopilot / Smart Crawl card to open OTTO SEO Settings, scroll to URL Exclusion conditions and click + Add condition. Choose Exclude, a match type of Contains or Start With, and the part of the URL to match, then click Update Settings, as the article on excluding pages and rolling back sets out. Legal pages, checkout and pages a regulator or brand team signs off are examples. An exclusion switches off every OTTO optimisation on matching URLs, including pages added later.

Step 5: Review one category, then deploy

Work through the recommendations a category at a time, page titles first, since those are easy to check and easy to undo. Approve what reads well for a human visitor, reject what does not, and deploy. OTTO sends instructions within seconds, your CMS usually applies them in 1 to 5 minutes, and the OTTO dashboard can take another 5 to 15 minutes to show the new status, up to 30 minutes in all, according to the article on deployment timing.

Step 6: Check the live page, and roll back what is wrong

After 30 minutes, purge your caching plugin and any CDN cache, then open the changed pages in a browser. To undo one item, filter the project overview by the page's URL and click the green Deployed button on that row; to undo a whole category, use Roll back all at the top right of its table, per the rollback article. Rollback affects OTTO's changes only, not edits made outside it.

Step 7: Make sure Google can see the changes

Confirm the project is active rather than Deep Frozen, because a paused project pushes no changes. Then check that the sitemap is submitted in Search Console with a Success status, that robots.txt does not block the optimised sections, and use URL Inspection to request indexing for 10 to 15 priority URLs, as the article on changes not showing on Google recommends.

Step 8: Measure, then widen the scope

Track the target keywords in Rank Tracker and allow 3 to 14 days after indexing before drawing conclusions; the same article puts new or low-authority domains at 1 to 4 weeks for organic crawling and competitive results at 2 to 6 weeks to settle. Only when the first category holds up do you move to meta descriptions, headings and schema.

An agent that deploys on its own is sold on the hours it saves, so its default is to act. The approval step costs minutes per batch and is the cheapest insurance in this whole workflow.

What the help centre warns about

• Exclusions do not undo deployments. Changes already live stay live until you roll them back, per the rollback article.
• Caches hide deployments. Caching plugins and CDNs such as Cloudflare can serve the old page after OTTO has applied the change, says the deployment timing article.
• Unexpected automatic deployments. Some customers have reported OTTO applying changes, including keyword assignments, that they did not approve, and repeated anchor texts, according to a help article that asks you to contact support with examples.
• Thin pages stay thin. Optimised pages with fewer than 300 to 500 words of meaningful body text often still rank poorly, per the article on changes not showing on Google.

FAQ

How do I undo an OTTO change?

Click the green Deployed button on the item's row to un-deploy it, or use Roll back all on a category's table, as the rollback article describes.

Why is my deployment not showing after ten minutes?

That is common. Caching, CDN propagation, slow servers and the dashboard's polling interval all add delay, and the deployment timing article asks you to wait 30 minutes and purge caches before escalating.

How do I make OTTO pick up changes I made myself?

Go to OTTO SEO, SEO Automation, open Site Audit, Overview and click Recrawl Site. Recrawls are rate-limited, so wait and retry if the button is unavailable, per the article on verifying the pixel.