Quality Score is a 1–10 rating Google attaches to each search keyword, summarising how relevant your ads and landing page are to the searches that trigger them. It is built from three components, each rated on a three-step scale — above average, average, below average: expected clickthrough rate, ad relevance and landing page experience. The number is free diagnostics from the only party that sees the whole auction. It is also, read as a single digit, the most over-interpreted number in PPC.
How Quality Score works
The three components answer three different questions:
- Expected CTR — when your ad shows for this keyword, does it get clicked as often as a well-matched ad should?
- Ad relevance — does the ad's text actually speak to the keyword's intent?
- Landing page experience — does the page behind the click deliver what the ad promised: relevant, navigable, honest?
On the relationship to money, precision matters. The live auction does not read your visible Quality Score. Ad Rank — which sets position and what a click costs — combines your bid with quality signals computed in real time, per auction, per query, per context. Quality Score is a keyword-level aggregate of the same family of signals, published for your benefit. So the causation runs one way: improve the underlying relevance, the auction-time signals improve, positions and click prices follow — and the visible score moves as a symptom. Chasing the number for its own sake gets the direction backwards. No myth survives that framing: there is no fee for a low score and no trophy for a ten.
Why the 1–10 number misleads and the components do not
Averaging destroys the diagnosis. A five might be a strong ad on a slow, thin landing page — or a great page behind an ad that never mentions the keyword. Opposite problems, same digit. The components name the failing part, which is the whole job of a diagnostic. The number also goes null on low-volume keywords, showing a dash where a score would be, while component reads often still exist. And because the score is keyword-level, one digit can hide wide variation across the actual queries matching that keyword.
The account-wide component pull, in one prompt
The Quality Score workflow was always sound and always tedious: pull every keyword's three components, group by failure mode, fix in priority order. The tedium is what an API-connected assistant removes. Component ratings are ordinary API fields, so one prompt returns the account-wide table — every keyword, three components, spend attached, sorted so "below average landing page experience with real spend" rises to the top. That turns Quality Score from a number you glance at into a worklist you clear; the full workflow is here.
What actually moves each component stays human. Expected CTR: sharper headlines against the keyword's intent, better responsive search ad assets. Ad relevance: tighter ad-group themes, so ads can speak directly to their keywords. Landing page experience: speed, mobile behaviour, and a page that pays off the ad's promise. An AI can find every weak component and draft every fix — the judgement about what your page should promise remains yours. Component-level review belongs in any structured account audit, which is where most people discover the score they ignored was itemising their problems all along.
Frequently asked questions
Is a low Quality Score charged as a penalty?
No fee is levied. The mechanism is the auction: Ad Rank combines your bid with real-time quality signals, so ads Google predicts to be less relevant need higher bids for the same positions — costlier auctions, not a surcharge. Quality Score is the visible proxy for those signals. Improve the failing component and the economics improve with it; there is no fine to pay off.
Should I pause or delete low Quality Score keywords?
Not on the number alone. First read which component fails — a below-average landing page experience and a below-average expected CTR call for different fixes — and check whether the keyword converts. A converting keyword with a mediocre score is doing its job; fix the component. A non-converting keyword with weak components is the real cut candidate.
Try it on your own account for a week
The full set of tools for the week, so you can see what it actually does — and it still cannot delete anything. No cost, no card, no contract: you connect your own Google account and can withdraw the access whenever you like.
- Up to 5 accounts
- One week
- Full tools
- No card
- Autonomous agentsLevels of autonomy in Google Ads management, which optimisation work is safe unattended versus which needs approval, and why irreversible actions should not be automated.
- Google Ads MCP serverWhat a Google Ads MCP server is, how free self-hosted servers compare to a hosted one, the full tool list AdCopilot exposes, and what you need to connect.
- Connect ClaudeStep-by-step instructions for adding a Google Ads MCP connector to Claude Desktop, claude.ai and Claude Code, including what to ask it first and how to revoke access.
- Connect ChatGPTStep-by-step instructions for adding a Google Ads MCP connector to ChatGPT, what it can read and change, and how to withdraw access.