Page Experience Signals

Page Experience Signals are a group of Google ranking factors that measure how users actually experience a page — including Core Web Vitals, mobile usability, HTTPS, and intrusive interstitials.

Also known as: page experience, UX ranking signals, Google page experience

Page Experience Signals are a group of Google ranking factors that measure how users actually experience a page beyond its content relevance. The current set includes Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift), mobile usability, HTTPS, and the absence of intrusive interstitials. Together they form a quality envelope that influences rankings as a tiebreaker among relevance-equivalent pages.

What Page Experience Signals Are

Page experience signals are a group of Google ranking factors that measure how users actually experience a page beyond its content relevance. The current set includes Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift) measuring loading, interactivity, and visual stability; mobile usability covering touch targets and readability; HTTPS for secure connections; and absence of intrusive interstitials that block content. The exact set has evolved over time, with Core Web Vitals being the most-discussed component. Together they form a quality envelope that acts as a tiebreaker among relevance-equivalent pages, especially on mobile.

How Page Experience Signals Work

Page experience signals work by capturing what content-quality signals can’t see: a relevant, well-written page that loads slowly, jumps around as elements load, traps users on tiny touch targets, or hides content behind interstitials provides a worse experience than an equally-relevant page that doesn’t. Page experience signals quantify those problems and let Google rank around them. The effect is rarely dramatic on its own but consistently shifts rankings at the margins, especially on mobile. Each component evaluates separately and the signals apply at the URL level rather than the domain level, so some pages on a site can pass while others fail.

Common Pitfalls and Misconceptions

A common mistake is treating page experience as a single switch that’s either on or off. The signals are continuous and they apply at the URL level, not the domain level — some pages on a site can pass while others fail, and rankings adjust accordingly. Site-wide averages obscure the per-page reality, which is where the actual ranking impact lives. Another error is relying on lab tests instead of field data. Lab tests use a single device profile, network, and clean cache; field data reflects many devices, networks, and cache states across real users. Field data is what Google uses for ranking, and it’s almost always slower than lab numbers suggest.

Page Experience Signals in Practice

The mature practice is to monitor page experience as a portfolio metric, prioritize fixes on high-value pages (those earning real impressions and traffic), and build performance into the development pipeline so regressions don’t ship to production unnoticed. Teams that wire Core Web Vitals into deployment as a performance budget catch regressions in hours; teams that audit quarterly catch them in months. The discipline matters more than any single optimization, because page experience is a perpetual maintenance problem: every new feature, ad tag, and third-party script is a chance for the envelope to degrade. AI answer engines weight similar quality signals.

Back to the Glossary

Common questions.

What are Google's page experience signals?

Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift) measure loading, interactivity, and visual stability. Other page experience signals include mobile usability, HTTPS, and absence of intrusive interstitials. The exact set has evolved over time; Core Web Vitals are the most-discussed component.

How important is page experience as a ranking factor?

It's a real but modest factor, acting primarily as a tiebreaker among relevance-equivalent pages. Strong content still outranks weak content on similar performance. But pages that fail page experience signals consistently underperform their content quality would predict, especially on mobile where Google primarily evaluates the signals.

Is page experience a single ranking signal or a group?

A group. Each component (LCP, INP, CLS, mobile usability, HTTPS, interstitials) is evaluated separately and contributes to the overall page experience signal. Failure on one component doesn't equal failure overall, but persistent failures across multiple components produce more visible ranking effects than any single failure.

How do you measure page experience?

Search console's Page Experience report (and the underlying Core Web Vitals report) gives a portfolio view across the site. PageSpeed Insights tests individual URLs against both lab and field data. CrUX (Chrome User Experience Report) provides field data Google actually uses for ranking. Lab tools are useful for diagnosis; field data is what counts for ranking.

Why do lab and field page experience scores often disagree?

Lab tests use one device, one network, and a clean cache. Field data reflects many devices, networks, and cache states across many users. Real users typically experience slower performance than lab tests show, especially on sites heavy with third-party scripts, ads, or personalization that don't fire in synthetic tests. Field data is the truth.

What's the most common page experience failure on B2B sites?

INP (Interaction to Next Paint) failures from heavy JavaScript blocking the main thread, often caused by marketing tags, chat widgets, and personalization scripts. CLS failures from images without dimensions or late-loading ad units are also common. LCP failures usually trace to unoptimized hero images or render-blocking resources.

How do page experience signals interact with AI search?

AI answer engines tend to cite sources that are also strong on technical fundamentals — broken or slow sites correlate with weaker editorial discipline. Page experience is part of the broader quality envelope AI engines weight, even when it isn't a direct citation signal. Strong page experience supports both classic ranking and AI citation share.

Related Terms

Let’s talk about what your next quarter could look like.

Tell us what you’re working on. A senior practitioner reads it, not an SDR queue, and replies, usually within one business day.

Reviewed personally, not routed through a queue.
A conversation about what you’re actually working on, not a generic pitch.
No pressure, just a chance to talk it through.