Skip to main content

Landing Page Match Score

What it does

The Landing Page Match Score fetches a landing page URL, extracts its title, H1, and body content, then scores how well the page reinforces a target keyword and supplied ad copy. The output is a 0-100 score plus per-dimension breakdown — keyword in title, keyword in H1, keyword density in body, ad copy alignment, and conversion path presence (form, CTA buttons). It’s the same logic Google’s “landing page experience” Quality Score component runs on, approximated heuristically.

Common situations

You’re launching a new keyword and want to verify the assigned landing page is aligned before paying for clicks. The score reveals whether the keyword phrase appears in the title and H1 (the strongest signals), and whether the body content addresses the keyword’s intent.

A keyword has Quality Score 5 with “Below Average” landing page experience, but you’re not sure why. Run the URL through the match score; usually the keyword phrase isn’t in the title, the H1 is generic, or the page targets a different intent.

You’re handing a campaign over to a client and the agency is producing landing pages. The match score is a quick way to verify each page is keyword-aligned before launch — much faster than walking through each one manually.

A campaign uses a generic homepage as the landing page for many keywords. The match score will reveal that the homepage is “below average” for most specific keywords because no homepage can be specifically aligned to many different terms. The fix is dedicated landing pages.

You’re auditing a competitor’s landing page strategy — what page they use for which keyword. Running their pages through the match score reveals their alignment discipline; weak alignment is an opportunity to outrank them with better pages.

What you need to know

Google’s Quality Score includes a component called “landing page experience” that measures how well the landing page serves the searcher who clicked the ad. Above-average pages are relevant, useful, easy to navigate, and trustworthy. Below-average pages send mixed signals (the keyword doesn’t appear) or have functional issues (slow, poor mobile experience, content unrelated to the ad).

The match score approximates the relevance dimension specifically — the dimension that’s controllable and structurally important. Speed, mobile-friendliness, and trust signals are covered by other tools (the Mobile-Friendly Test, SSL Checker, HTTP Headers Inspector in the SEO suite).

The five components scored:

Keyword phrase in title (30 points): the strongest single signal. The exact target keyword phrase appearing in the page’s <title> tag tells Google the page is specifically about that topic. Generic titles (“Home | Acme Corp”) fail this even if the page is otherwise relevant.

Keyword phrase in H1 (25 points): second-strongest. The page’s main heading should reflect what the searcher is looking for. Pages where the H1 is a brand mention or generic category name (rather than the keyword’s topic) score lower.

Keyword tokens in body (15 points): less weighted because token presence alone isn’t strong evidence of intent match — but absence is strong evidence of mismatch. Pages where the keyword’s main words don’t appear at all score zero on this dimension.

Ad copy alignment with body (15 points): the page should reinforce the ad’s message. If the ad promises “Free shipping over £50” and the page never mentions free shipping, the click experience is incoherent. Token overlap between ad copy and body content captures this.

Conversion path (15 points): split between form presence (8 points) and CTA buttons (7 points). The page should make the next step obvious; pages without forms or visible CTAs score zero on conversion path even if relevance is high.

The 0-100 final score is the sum of the five components. 80+ is strong; 60-80 is workable but improvable; below 60 indicates structural issues likely affecting Quality Score.

What the score doesn’t capture:

  • Page speed. Use TTFB & Server Response Time for that.
  • Mobile-friendliness. Use Mobile-Friendly Test.
  • Trust signals (SSL, security badges, social proof). Partially covered by SSL Certificate Checker.
  • JavaScript-rendered content. The score reads the server’s initial HTML; sites with heavy client-side rendering may have content that’s invisible to the score (and to Googlebot’s first crawl).

The combination of high match score + fast loading + mobile-friendly + visible trust signals correlates strongly with above-average landing page experience in real Quality Score scoring.

Frequently asked questions

What’s a good match score?

80+ for active campaign use. 70-80 is acceptable for less competitive keywords. Below 60 needs work — the page is sending mixed signals to Google about what it’s about.

Why does the score weight title and H1 so heavily?

Because Google’s signal does. The title tag is the strongest single relevance indicator — search engines have used it as the primary topic signal for two decades. The H1 is the on-page reinforcement. Pages that nail both score above average on landing page experience almost regardless of other factors.

Should every keyword have its own landing page?

Yes if practical. Dedicated landing pages per keyword theme score higher than generic pages serving many keywords. The exception: closely-related variants (“running shoes” and “running shoes for men”) can share a page if the page addresses both naturally.

What if my keyword has many close variants?

Group them into themes and build a landing page per theme. “Running shoes” might be one theme; “trail running shoes” another; “marathon running shoes” a third. Each gets its own page. Within each theme, close variants can share.

How is this different from Google’s actual Quality Score signal?

Google uses the page’s full rendering, real CTR data, navigation patterns, and trust signals beyond what the score measures. The match score covers the relevance component specifically — the part you can control through copy and structure. It’s a reliable predictor of the relevance dimension, not the full Quality Score.

Will the score work on JavaScript-heavy sites?

Partially. The score reads the server’s initial HTML response. Sites that hydrate content client-side may have keyword-relevant text that’s not in the initial HTML; the score won’t see it. This is also what Googlebot sees on first crawl, so the score’s view often aligns with what Google’s relevance signal sees.

Can a page score 100?

Theoretically yes if all five dimensions are above their thresholds. In practice, 90+ is uncommon and usually means the page is over-optimised in a way that’s brittle (keyword stuffed in title and H1 and body density). 80-90 is the practical maximum for natural pages.

Does the score consider page intent?

Indirectly, through ad copy alignment. If the ad promotes a product and the landing page is a category browse, ad copy alignment is low even if keyword match is strong — meaning the page is “about” the topic but not “for” the searcher’s specific intent.

Common problems

Problem: Match score is 65 but Google’s Quality Score landing page experience is “Above Average”.

Google considers more than just relevance — fast loading, mobile-friendliness, and your account’s historical landing page performance contribute. A page can score 65 on relevance specifically but be above average overall because the other factors are exceptional.

Problem: Match score is 85 but Google’s score is “Below Average”.

Most often the issue is page speed, mobile experience, or a security/trust issue (no HTTPS, security warnings) that the relevance score doesn’t measure. Run the page through PageSpeed Insights and the SEO suite’s mobile and SSL tools to surface those.

Problem: Score reports keyword in title but title is generic.

The token overlap measure can pass on partial matches. If the keyword is “marathon running shoes” and the title is “Best Running Shoes | Acme”, the body word “running” matches but the full intent doesn’t. Aim for the full keyword phrase in title, not partial token presence.

Problem: Conversion path is zero but the page has obvious CTAs.

The score detects <form> elements and elements with class names like btn or button, plus [role="button"]. Pages using custom-styled <a> or <div> elements as buttons (without those class names or roles) won’t be detected. Standardise on semantic HTML for accessibility and to be detected by tools like this one.

Problem: Page has the keyword everywhere but conversion rate is low.

High keyword match plus low conversion usually means the page is keyword-relevant but not intent-relevant. The searcher landed on a page about the topic but didn’t find what they were specifically looking for. Audit the page’s call-to-action and primary content against the searcher’s specific need.

Tips

  • The keyword phrase in the title and H1 is the highest-leverage edit. If those two are right, the rest of the score usually follows.
  • Build dedicated landing pages per keyword theme. Generic pages serving many keywords score lower across all of them.
  • Reinforce the ad copy on the landing page — the page should remind the searcher of what the ad promised, not surprise them with different messaging.
  • Don’t keyword-stuff to push the score higher. The score is a guide, not a target. Pages optimised for the score above 90 often read awkwardly to humans.
  • Speed and mobile-friendliness matter as much as relevance. Run the page through Mobile-Friendly Test and TTFB & Server Response Time alongside this score.

Related tools in this suite

The Quality Score Estimator covers the broader Quality Score picture; this tool is the focused landing-page-experience component. The RSA Tester is upstream — getting the ad copy right is necessary for the ad-to-page alignment dimension to score well.

What this looks like at scale

For a single landing page, the score is fine. For a content set with hundreds of landing pages, alignment should be enforced at template level — page slugs derived from the keyword theme, titles and H1s programmatically generated from the page metadata. The WordPress development service covers this kind of templated approach to ensuring landing-page alignment doesn’t drift over time.

Take it further

If a portfolio of landing pages has chronic match score issues, the underlying problem is usually that pages are written by humans without a discipline that ensures keyword-and-intent alignment. Talk through the situation and we can scope what the structural fix looks like.