What I needed
I run paid search for a medical practice I work with. Over a few months, almost every expensive mistake we found was a page problem, not an ad problem.
A lead form that was capped so short most of it was hidden. Ads sent to a general site page with no form while a dedicated landing page existed for the same service. A price on the page that didn't match the price list. A treatment name in the site menu that got every ad pointing at that page limited.
Each one got found by hand. Usually weeks late. I wanted the pipeline to find them first.
Start with what Google says, not what I think Google says
Before building anything I had Claude read the actual support.google.com pages: the Quality Score pages, the landing page experience guide, the mobile page, and the destination requirements and misrepresentation policies.
Quality Score is a diagnostic, not a KPI. Google says so directly. You're not supposed to average it or chase it. You use it as a filter on the keywords that spend or convert, and when one of its three parts is "Below average" you fix that part.
The exact search phrase doesn't need to be on the page. My own audit checklist flagged a page when the keyword wasn't in the H1. Google never said that. I deleted the rule.
And the mobile-friendly test that one of the reports leans on is retired. The column still shows up, it just reads zero everywhere now.
All of that went into one file: each rule, the Google page it came from, who checks it, and how bad a miss is. Everything else points to that file instead of repeating it, because two copies of a rule drift apart.
The check
The script fetches a page the way Google's crawler does. Google calls it AdsBot. It's the bot that decides if your ad is allowed to run, and it plays by slightly different rules than the normal search crawler. It ignores the catch-all section of robots.txt, for example, so only a rule that names AdsBot can block it. I didn't know that until I had Claude walk me through the crawler docs.
Then it checks the things a fetch can actually answer:
- Does the page load for AdsBot, stay on the same domain, and land in the same place once the tracking parameters are added?
- Are there banned terms on it, menu included?
- Is there a form near the top, is the form box capped short, is there a tap-to-call link?
- Does every price on the page appear in the practice's price list?
- Mobile speed, which only warns. My call: a slow page is worth knowing about, not worth stopping a launch over.
Each finding gets a level. BLOCK means Google would disapprove the ad. FIX means it hurts the page. WARN is speed.
Where it runs
A check you have to remember to run is a check that doesn't run.
So it runs on its own when:
- a new campaign goes live (the go-live script refuses on a BLOCK)
- any script changes the page an ad points to
- draft ad copy is about to upload (if an ad quotes a price or offer the page doesn't show, it stops)
- someone edits a live page that gets ad traffic
- every Monday, across every live page, plus the flags Google itself has put on the ads
There's an override, but you have to type a reason, and the reason gets logged.
The deeper scored audit, the one that looks at navigation, pop-ups, and whether the reviews are real, only runs on brand new pages or pages the quick check flags. Running it on everything every week would just be noise.
What the first run found
The first Monday-style sweep found a pricing page linked from a sitelink that promotes a treatment Google bans in ads. Google's policy is flat on it: a page promoting it can't be an ad destination. Nobody had connected the sitelink to the policy.
It also found a set of blog pages that the dynamic ads were sending people to. They name a common prescription medication, and my reference file called that medication banned. So I went back to Google's own drug lists, and it's on the prescription list, which is allowed on a page in the US. Only bidding on the drug name needs certification. My file was wrong. Those pages also got plenty of clicks and zero leads, so they're coming out of the dynamic ads anyway.
And the price check caught an offer whose end date on the page didn't match the end date on the promotion attached to the ads. One of them was going to stop showing early.
The part I'll keep
Every rule traces to a Google page. Every place an ad can get pointed at a page runs the same check. And Quality Score now gets saved each week, so when a page's score drops I can see what changed on the page right before it.
It took most of a day. Most of that was reading Google, not writing code.