How to fix: Landing page experience (Quality Score component)

TL;DR

Landing page experience is one of three Quality Score components Google uses to rank your ads, alongside Expected CTR and Ad Relevance. When a meaningful share of your keywords show Below Average landing page experience, Quality Score drops, Ad Rank suffers, effective CPC rises across affected ad groups, and Smart Bidding starts optimizing against an inflated cost baseline. The fix combines Core Web Vitals work (page speed, mobile usability) with on-page content relevance (keyword presence in headings and body) and basic trust signals (HTTPS, transparent navigation).

Why it matters

Google calculates Quality Score from three signals: Expected CTR, Ad Relevance, and Landing page experience [1]. Each is bucketed as Above Average, Average, or Below Average versus competitors over the trailing 90 days. Landing page experience specifically measures "how relevant and useful your landing page is to people who click your ad" [1].

The mechanism that hurts you is Ad Rank. Ad Rank multiplies your bid by Quality Score, so a 1-point QS drop on a keyword that converts at 5% can raise your effective CPC by 10-30% to hold the same average position. On Smart Bidding campaigns, the algorithm then learns against the inflated CPC baseline and either pulls back impression share to hit your tCPA or accepts the worse unit economics to hit your conversion volume target. Either way, you lose efficiency.

Compounding the issue: landing page experience is the slowest QS component to fix. Expected CTR and Ad Relevance respond to ad copy changes within days. Landing page changes (Core Web Vitals work, content rewrites, mobile usability fixes) often take 2-4 sprints to ship and 14-30 days for Google to re-evaluate after deployment. This is why the rule fires at high severity when 30% or more of keywords show Below Average landing page experience — it's a multi-sprint remediation, not a quick toggle.

This rule is the campaign-and-page-level version of the broader Quality Score framework. For the cross-component diagnostic (which of the three QS components is dragging on a specific keyword), see QS components diagnostic. For keyword-level Quality Score breakdown, see Keyword Quality Score is low.

How to fix

1. Diagnose Core Web Vitals on top-spend landing pages

Open Google PageSpeed Insights at pagespeed.web.dev and run the top 5-10 landing pages by spend. Target the 75th percentile thresholds [2]:

Largest Contentful Paint (LCP) under 2.5 seconds
Interaction to Next Paint (INP) under 200 milliseconds
Cumulative Layout Shift (CLS) under 0.1

Pages failing any of these on mobile field data are a near-guaranteed cause of Below Average landing page experience.

2. Fix mobile usability gaps

In Chrome DevTools, toggle device emulation (Pixel 7 or iPhone 14 viewport) and verify:

Body text is legible without pinch-zoom (16px minimum)
Tap targets are at least 48 by 48 pixels with adequate spacing
The viewport meta tag is set correctly
No horizontal scroll on any breakpoint
Forms are usable on touchscreen (no hover-only states)

Google's mobile usability evaluation is automated and unforgiving — one broken tap target on the primary CTA is enough to push a page to Below Average.

3. Rewrite headings and intro copy for keyword relevance

Google evaluates landing page content relevance by checking whether the keyword phrase appears in semantically meaningful page elements: H1, H2, H3, and the first body paragraph. Rewrite each top-spend landing page so:

The H1 contains or paraphrases the primary ad keyword
At least one H2 includes a close variant
The first 100 words of body copy mention the keyword phrase at least once naturally
The page actually delivers on what the ad promised — no bait-and-switch from "free trial" to "request a demo"

Generic landing pages serving 50 different ad groups are the most common cause of Below Average across the account. Either split into keyword-themed landing pages or use dynamic text replacement to mirror the search query.

4. Compress assets and defer non-critical resources

Concrete page speed wins that move the needle on LCP:

Convert hero images to WebP or AVIF (typically 50-70% smaller than JPEG at equivalent quality)
Lazy-load images below the fold with loading="lazy"
Defer non-critical JavaScript with defer or async
Inline critical CSS, defer the rest
Enable text compression (Brotli or Gzip) at the CDN edge
Preconnect to third-party origins you load fonts or analytics from

If you're on Cloudflare, Vercel, or Cloudflare Pages, most of these are toggles in the platform dashboard, not engineering work.

5. Verify trust signals

Google's landing page experience evaluation includes basic trust checks. Confirm:

HTTPS is enforced site-wide with HSTS (no mixed content)
Privacy policy linked from footer, accessible in one click
Contact information is visible or one click away
Navigation back to the homepage is obvious
No interstitial popups blocking the primary content above the fold (especially on mobile)

These are not optional — they are explicit signals Google uses to filter out low-quality landing pages.

6. Verify the fix after 14 days

Google re-evaluates landing page experience on a rolling basis, but expect 14 days minimum for changes to reflect in Quality Score columns. In Google Ads UI, navigate to Keywords, click Columns, expand Quality Score, and enable Landing page exp. (current). Confirm:

Below Average keyword count dropped under 15% of total impressions
Quality Score average rose by 1-2 points on affected keywords
Effective CPC on those keywords dropped 10-25%

If no movement after 21 days, the issue is content relevance (step 3), not page speed.

Common mistakes

Treating landing page experience as a page speed problem only. Page speed is necessary but not sufficient. A blazing-fast page that doesn't match the ad's promise will still rate Below Average. Content relevance and trust signals matter equally.
Using one generic landing page for all ad groups. A homepage or category page serving 50 different keyword themes will rate Below Average across most of them. Either build keyword-themed landing pages or use ad customizers and dynamic text replacement.
Optimizing for desktop PageSpeed score and ignoring mobile field data. Google evaluates landing page experience primarily on mobile field data (real Chrome users), not desktop lab tests. A mobile PageSpeed score of 85 with poor field data is worse than a 65 with good field data.
Treating Quality Score as a vanity metric. QS is a real bid multiplier inside Ad Rank. A 1-point change moves real CPC dollars. It's not a diagnostic dashboard widget.
Recommending pop-up consent banners that cover above-the-fold content. Aggressive interstitials trigger Google's intrusive interstitial penalty on mobile, which is a direct hit to landing page experience.

FAQ

Q: How long until landing page experience updates after I fix the page?
A: Minimum 14 days, typically 21-30 days for full re-evaluation. Google needs new field data from Chrome users hitting the updated page before it re-rates.

Q: Does removing the keyword from the URL slug hurt landing page experience?
A: No. Google evaluates on-page content, not URL slugs. URL slugs help SEO, not Quality Score.

Q: Will Smart Bidding fix this for me automatically?
A: No. Smart Bidding optimizes against the Quality Score it observes — it cannot raise QS by changing bids. Landing page work is upstream of bidding.

Q: Can I see landing page experience per keyword?
A: Yes — Google Ads UI, Keywords tab, Columns, Quality Score, Landing page exp. (current). Both current and historical variants are available.

Q: Does redirecting old URLs hurt landing page experience?
A: A single 301 redirect typically does not. Chains of 2+ redirects measurably increase LCP and can push pages to Below Average.