π What this article covers
Google sometimes disapproves ads with a Compromised Site status when its systems see unexpected scripts, links, buttons, redirects, or content that looks hacked or cloaked. This article explains how to review OTTO deployments for the dates in question, how those changes are applied, whether AdsBot can see different content than visitors, and whether to freeze or roll back OTTO before you appeal.
π How to get the full change list
Search Atlas stores deployment history separately for each project, but a public help article cannot list the changes on your projects, and the dashboard does not provide a dated history you can filter and export. Open each project separately. In each fix category, select Deployed and review the page URL, original content, and OTTO suggested fix for each live fix. Repeat this for both projects so nothing is missed.
For each deployed fix, note the page URL, the fix category, the original content, and the OTTO suggested fix. Pay special attention to:
- Links added, removed, or rewritten, including outbound and button destinations
- Buttons or calls to action, including new labels and target URLs
- Scripts, tags, or pixels inserted into the page or sitewide
- Redirects, canonical tags, hidden text, or content shown only to some visitors
If the in-product log does not show the detail you need for those dates, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. Include both project names and the date range so the team can pull the same deployment record.
βοΈ Server-side or client-side
OTTO does not use one method for every change. Each deployment is labeled by what it edits. Use that label rather than assuming every update is in the HTML source.
- With the WordPress plugin, Cloudflare Worker, or CMS sync, OTTO changes are applied to the page before it is served. Visitors and AdsBot generally receive the same markup. The JavaScript installation instead applies changes in the browser.
- With the JavaScript installation, OTTO adds or rewrites links, metadata, and content after the browser loads the page. A crawler that does not run that script the same way can see different content than a person.
Use the installation method to judge how the changes are delivered, not words in the deployment record. The WordPress plugin, Cloudflare Worker, and CMS sync change the served page. The JavaScript installation changes it in the browser. Review any fix you cannot identify before you appeal.
π€ What AdsBot can see
Google Ads uses its own crawler, often called AdsBot, to check the landing page. It does not always execute JavaScript the same way Chrome does, and it can visit at a different time than your own test. That means client-side OTTO changes can be missing, partial, or different in the copy AdsBot stores.
Compare three views of each affected landing page:
- The live page in a normal browser, including buttons and link targets
- The raw page source, before scripts run
- Googleβs recorded view, such as the ad destination preview or a fresh fetch after you pause new changes
Look for third-party scripts you do not recognize, pop-ups, auto-downloads, cloaking, doorway pages, or links that do not match the visible button. A mismatch is a common reason a site is flagged even when the visible page looks fine to you.
βΈοΈ Freeze or roll back before you appeal
Stop deploying new OTTO changes on both projects before you appeal. Turn off Smart Crawl so OTTO stops scanning and generating new suggestions. Also turn off Autopilot so it does not publish new fixes automatically. Leave the site stable so Google re-crawls one known version, and do not keep publishing fixes while the review is open.
Do not roll back every OTTO change by default. Ordinary title, meta description, and on-page SEO edits rarely explain a Compromised Site label. In each category, open Deployed and click Deployed on only the individual fixes that add or change scripts, unexpected links, buttons to other domains, redirects, or injected content. Use Roll back all only when the whole category should be removed. Remove any code you cannot identify, then recrawl the landing page yourself.
After the site is stable, appeal in Google Ads. State that you reviewed deployments on November 2β3, paused further OTTO changes, removed any unverified scripts or links, and that the current source matches what visitors see. Keep the freeze in place until the disapproval clears.
π¬ If you still need the deployment record
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.