Google Ads: Quality Score, Relevance, and High-Intent Account Structure

What Quality Score Actually Measures (and Why Chasing the Number Is a Trap)

Quality Score is Google’s estimate of how useful your ad and landing page are for a given keyword — not a grade you “optimize” in isolation. Chasing the number while leaving catch-all ad groups, vague RSAs, and generic landing pages in place is how teams burn hours without moving CPC or lead quality.

Three components drive the score, with roughly estimated weights: Expected CTR ~39%, Landing Page Experience ~39%, and Ad Relevance ~22%. Improving Expected CTR or Landing Page Experience has about twice the impact on Quality Score as improving ad relevance alone. That sequencing matters: fix the heavy components first.

Baseline the room you are in. Across a large 2026 sample, the average Quality Score sits at 5–6. Roughly 36% of all Google Ads keywords currently carry a score of 5 or below. A 7+ puts an advertiser ahead of most competitors — useful context when a dashboard full of 5s feels like failure rather than the default starting point.

Treat Quality Score as a triage map. Below-average landing experience points to message match, speed, and proof. Weak expected CTR points to headlines, assets, and query-to-ad continuity. Weak relevance points to theme drift inside the ad group. The label names the break; your Google Ads account structure and pages fix it.

Resist “score goals” in OKRs. A KPI like “average Quality Score 8” encourages cosmetic restructures and keyword deletions that hide problems instead of fixing them. Prefer KPIs like CPC at target position on money themes, qualified CPL, and booked-job rate — then use Quality Score components to explain movement.

If you only raise bids to “buy” better positions on low-score themes, you pay a premium for misalignment. Structure, ad relevance, and landing page experience are cheaper levers than bid inflation — which is why this playbook starts with themes and pages before diagnostics theater. For the broader failure patterns that usually sit underneath a weak score, see why most Google Ads campaigns fail.

Theme ad groups and RSA assets around a single service intent

Tight groups beat catch-all ad groups

High-intent keywords only stay high-intent if the ad group theme stays tight. When a single ad group contains unrelated services, you lose the ability to write specific ads and dedicated landing pages. The platform shows generic copy and visitors land in vague experiences. Split themes so each group has one main intent to solve.

Account structure in 2026 has largely shifted from old-style Single Keyword Ad Groups (SKAGs) to Single Theme Ad Groups (STAGs) — typically 5–15 closely related keywords grouped around one intent. Pooling clicks and conversions into one themed group gives Smart Bidding a richer dataset and helps the algorithm exit the learning phase faster than a thin SKAG grid of near-identical singles.

That does not mean SKAGs are dead. They still make sense narrowly for an account’s 10–20 highest-value, highest-volume keywords where the extra management overhead is worth the precision. A hybrid approach is now common: STAGs for most of the account, SKAGs for the top handful of money terms.

RSA assets should echo the same service intent. Headlines that name the job type, geography honesty, and the next step beat brand slogans that could sit on any service. Use pinning thoughtfully on RSAs to keep legal or offer claims accurate — not to freeze every asset into a rigid Frankenstein.

Negatives protect the theme. If “furnace repair” sits next to “AC install” queries inside one group, relevance and expected CTR both suffer. Tight themes plus disciplined negatives are how Google Ads account structure stays readable for humans and trainable for Smart Bidding.

Name themes the way customers search: service + modifier (emergency, replacement, near me) when volume supports it, not internal product codes. That naming discipline makes RSA writing and landing H1s obvious — and makes STAG boundaries easier to defend in account reviews.

When you rebuild themes, do it in waves tied to revenue — not a big-bang restructure of every campaign overnight. Pair structural cleanups with paced budget discipline from how to scale Google Ads without wasting budget so learning phases and spend ramps do not collide.

Make landing pages the proof point for the keyword theme

Expected CTR can rise; landing experience is where deals happen

Landing page experience is roughly ~39% of Quality Score — equal weight to Expected CTR and nearly double the weight of Ad Relevance (~22%). Even strong ads falter on slow or generic pages. Pair each high-value ad group to a page that includes clear proof and a CTA that matches the query stage.

Because Expected CTR and Landing Page Experience each outweigh Ad Relevance, fixing those two has about twice the score impact of polishing relevance alone. Teams that only rewrite headlines while leaving a soft homepage as the landing URL are working the smaller lever.

Message match is the first landing test: the H1 and first screen should continue the keyword theme and the ad promise — same service, honest geography, same next step. Expected CTR rises when ads feel continuous with the query; landing experience rises when the page proves the claim and makes action easy.

Proof and speed are commercial, not cosmetic. Reviews, licenses, before/after, response-time claims, and a clear click-to-call or form path belong above the fold for phone-first service buyers. LCP and mobile layout failures show up as “below average” landing experience for a reason — the page is the deal room.

Map one primary landing URL per high-intent theme. Shared “services” blobs force every keyword into the same vague proof set and drag both Quality Score and conversion rate. Dedicated pages are how landing page experience and ad relevance reinforce each other instead of fighting.

After you ship a new landing URL, give the component a full learning window before judging the score. Same-day QS panic after a page swap creates thrash. Watch LPE status, bounce and conversion, then decide whether the page or the ad still needs work.

For local service queries, align the page to how people actually search in-market — not a national brand story. That continuity is covered in depth in align Google Ads with local search intent.

Use diagnostics without obsessing over the label

Action follows the break you can see in components

Diagnostics tell you which component is broken — they are not a weekly vanity report. If a theme shows “below average” on landing experience, look at LCP, mobile layout, and message match. If ad relevance lags, refresh headlines with customer language, not brand jargon. If expected CTR is weak, check query match, RSA coverage, and whether the theme is too broad.

The financial case for acting on those breaks is concrete. Ads rated above average on both landing page experience and ad relevance had CPCs roughly 36% below average for the same non-branded keywords. Alignment is a cost lever, not a branding exercise.

Moving a keyword’s Quality Score from 5 to 7 can cut CPC by more than 40% at the same ad position. That is often cheaper growth than raising bids to force the same position on a weak score. Fix structure and pages first; then let bids work on healthier foundations.

Review cadence should match risk. At-risk themes — high spend, low score, or falling CTR — deserve a two-week look in active accounts, faster during launches. Cosmetic “everything must be 10/10” sweeps waste time when commercial outcomes are already strong.

Write actions next to the label: “below average LPE → replace landing URL / fix LCP / rewrite H1 match,” not “improve Quality Score.” The auction does not reward intention; it rewards clearer relevance and usefulness.

Ignore single-keyword flukes when spend is tiny. Prioritize themes by cost and opportunity: a Quality Score 4 on a $50/month keyword is not the same fire as a 4 on a $5,000/month theme. Diagnostics without prioritization become busywork.

When creative fatigue is dragging expected CTR across many themes, structural diagnostics alone will not save you — rotate assets with a real system. See PPC creative rotation so RSA refreshes stay disciplined.

Measure commercial outcomes, not the score alone

A high score with bad leads is still failure

A high Quality Score with bad leads is still failure. Some tight themes may still show “average” while producing great pipeline. Do not restructure for cosmetic reasons. Structure for business outcomes and user clarity first.

Score and CPC are inputs. Qualified lead rate, booked estimates, close rate, and blended CAC are the scoreboard. A theme at Quality Score 8 that floods the inbox with tire-kickers is worse than a 6 that books profitable jobs — as long as you are not paying a reckless premium for the 6.

Segment outcomes by intent tier. Brand and high-intent service themes should clear different bars than broad research queries. Judging every keyword by the same Quality Score threshold ignores how Google Ads account structure is supposed to separate intents.

When you improve landing page experience or ad relevance, read conversion and lead quality in the same window as the score change. If CPC drops but qualified pipeline does not rise, you may have improved auction metrics without improving the offer or the handoff.

Keep a short commercial dashboard next to QS columns: spend, CPL, qualified rate, and revenue or booked jobs by theme. That pairing stops score theater and keeps Google Ads management work tied to margin.

Share that dashboard with sales weekly during structure projects. If score and CPC improve but sales complains about lead fit, pause the next theme expansion until the offer or qualification path catches up — Quality Score never replaces a broken handoff.

Use Quality Score to find fixable breaks; use pipeline to decide whether the theme deserves more budget. That is how high-intent keywords stay funded without mistaking a UI label for growth.

How the Three Components Actually Break Down

Expected CTR (~39%) estimates how likely your ad is to be clicked versus competitors for that keyword. Levers: tighter themes, RSA headlines that mirror high-intent keywords, strong assets, and negatives that keep mismatched queries out. Weak eCTR often means the ad does not sound like the search — or the group is too broad to write a sharp ad.

Landing Page Experience (~39%) estimates how useful and relevant the page is after the click. Levers: message match, mobile usability, load speed, clear CTA, and proof that supports the promise. This is where deals happen. Fixing LPE moves Quality Score as much as eCTR and roughly twice as much as relevance-only work.

Ad Relevance (~22%) estimates how closely the ad matches the intent of the keyword. Levers: theme purity, headline language that names the service, and avoiding catch-all groups where one RSA must cover unrelated jobs. Relevance matters — it is just the smaller weight, so it should not consume the whole optimization calendar before eCTR and LPE are healthy.

Highest-leverage sequencing follows the weights: stabilize themes and RSA coverage (eCTR), attach proof-rich landing URLs and fix speed/match (LPE), then tighten residual relevance gaps. Reversing that order is how teams polish ad copy on a broken page and wonder why CPC barely moves.

Document the lever you pulled against each component so the next review is faster: “split STAG,” “new lander,” “RSA headline refresh,” “negatives for DIY queries.” Quality Score work compounds when the account has a memory.

Re-check components after each structural change. A new landing URL can lift LPE while a messy RSA still caps eCTR. Diagnostics are a loop, not a one-time audit — especially when you expand high-intent keyword coverage inside STAGs.

Browse more operational patterns across our Google Ads guides when you want account-level playbooks that sit next to this Quality Score framing — from failure modes to creative rotation and local intent match.