A vigilant dog sits at a workstation in a quiet dim room, watching the screens late at night.
Early access · Free Chrome extension

Stop losing revenue to silent disapprovals.

Free Chrome extension. Reads disapprovals from your live Ads session. Runs the diagnostic Google's UI doesn't surface. Drafts an appeal with evidence attached. Before your client notices traffic dropped.

The problem

Disapprovals show up late. The reason shows up wrong.

You find out hours after the spend stops.

Google's email lands when you're already deep in something else. The Ads UI surfaced it earlier but you weren't in that tab. By the time you check, the campaign has lost a day of traffic.

The reason Google gives doesn't match the page you're looking at.

You open the landing page. It loads fine. You click around. Nothing's broken. The disapproval still says "destination not working." Now you're stuck explaining to a client a problem on Google's side, not yours.

You appeal blind, then appeal again.

No diagnostic evidence to attach. No clear cause to cite. The first appeal gets denied with the same vague boilerplate. You write the second one differently. It gets denied too. The afternoon is gone.

Policy Watchdog was built around these three.

What Google says · What Google means

Most disapprovals point at the wrong thing. Here's what they usually mean.

"Destination not working"

usually means:

AdsBot blocked at the CDN or firewallrobots.txt rule excluding AdsBot-Googleslow response time on Google's crawlredirect chain breaking on AdsBot's user agent

"Misleading content"

usually means:

landing page headline doesn't match ad copyprice or offer changed since the ad was approvedclaim in the ad isn't substantiated above the foldrequired disclosures missing on the destination

"Compromised site"

usually means:

third-party script flagged as maliciousSSL certificate expired or misconfiguredold subdomain still serving deprecated contenta security scanner caught something the page itself didn't

Policy Watchdog runs the diagnostic that tells you which one.

How it works

A Chrome extension that watches with you.

A Chrome extension that runs in your browser while you're working in Google Ads. Reads disapprovals from your live session. Runs the diagnostic Google's UI doesn't surface. Nothing leaves your browser. No OAuth, no servers, no account access.

  1. Install the extension.

    One click from the Chrome Web Store. The extension activates next time you open Google Ads.

  2. Open Google Ads.

    Disapprovals you get are surfaced as you work. The diagnostic for each one is one click away.

  3. See what's actually happening.

    The likely cause in plain English. The diagnostic evidence behind it: status codes, AdsBot vs browser response, robots.txt rules. A draft appeal with that evidence ready to paste into Google's Policy Manager.

Early access

Early access for agencies running multiple accounts.

Onboarding in small batches. Priority for agencies and freelancers managing multiple accounts. Drop your details and we'll reach out when it's your turn.

We'll only email you about Policy Watchdog access. No newsletters, no third parties, no marketing lists.

FAQ

Things people check before signing up.

Yes. Free during early access and free at launch. We'll add paid tiers later if there's a clear reason - premium features, team workspaces, MCC-level integrations - but the current diagnostic stays free for early-access users.

No. The extension runs in your browser and uses your existing Google Ads session, the same way you already access your account. No OAuth, no stored credentials, no data pulled to our servers. Your disapproval data stays in your browser.

Reads disapprovals from your live Ads session. Runs test requests as AdsBot-Google to compare against your browser. Checks robots.txt for AdsBot-specific rules. Reports the most likely cause for each disapproval. Drafts an appeal you can paste into Policy Manager. All locally, in your browser.

Confirmation email immediately. After that, batches open as the extension stabilizes. We prioritize based on use-case fit, not signup order. If you tell us in the optional field what you're working on, that's what we'll use to decide your batch.