Page Experience
Page experience is Google's umbrella term for a set of signals describing how it feels to use a page beyond its raw content. It bundles Core Web Vitals together with mobile-friendliness, HTTPS, and the absence of intrusive interstitials.
Page experience is Google's catch-all name for how a page feels to use, separate from whether the content is any good. It rolls up several signals into one idea: does this page load well, behave on mobile, run on a secure connection, and avoid shoving annoying pop-ups in your face? Content still answers whether you deserve to rank. Page experience is more about not actively sabotaging yourself. It is not a single score you can look up either. It is a collection of signals Google considers together, and the measurable, named pieces are the ones worth your attention, because they are the ones you can actually act on. Everything else in this entry is just naming those pieces and putting them in priority order.
What page experience includes
There are four named components, and you should be able to rattle them off. Core Web Vitals cover loading, interactivity, and visual stability. Mobile-friendliness covers whether the page works properly on a phone. HTTPS covers whether the page is served over a secure connection. And the absence of intrusive interstitials covers whether you block your own content with a pop-up the moment someone arrives. None of these is exotic. They are table stakes, which is exactly why failing one looks careless to Google. A modern site is expected to be secure and usable on a phone by default, so a missing certificate or a layout that breaks on mobile is not just a lost signal, it is a tell that nobody is minding the store. That perception is the part you want to avoid as much as the metric itself.
- Core Web Vitals: loading (LCP), interactivity (INP), and visual stability (CLS).
- Mobile-friendliness: whether the page works properly on a phone.
- HTTPS: whether the page is served over a secure connection.
- No intrusive interstitials: no pop-ups that block the content as soon as you arrive.
Page experience rarely makes a weak page rank. It mostly stops a strong page from being held back.
Here is the honest, 20-years-in version of how much weight it carries. Page experience is a real signal, but it is a tiebreaker, not a trump card. Google has been clear that relevant, helpful content can rank even with mediocre page experience. Where it bites is when two pages are otherwise comparable, or when bad experience is so bad it drives users back to the search results. That bounce is the real cost. A pop-up that sends people straight back to Google does more damage through that behavior than the page experience signal itself ever could, because it teaches Google your page does not satisfy the searcher. So I do not obsess over a perfect score. I make sure nothing on the page is actively pushing people away, and then I put my real energy back into the content, which is where rankings are actually won or lost. Page experience protects a good page. It does not create one.
warningWATCH OUT
Intrusive interstitials are the easiest page experience own goal. A full-screen pop-up the instant someone lands on your page hurts both rankings and conversions. Delay it, shrink it, or drop it.
- 1Confirm the site runs entirely on HTTPS with no mixed-content warnings.
- 2Check mobile usability and Core Web Vitals in Search Console for your main templates.
- 3Audit for interstitials and pop-ups that block content on entry, especially on mobile.
targetShmul's priority order
Get content and relevance right first, always. Then treat page experience as the polish that protects those rankings. I have never seen a site rescued by page experience alone, but I have watched plenty of good pages get quietly throttled by slow loads and aggressive pop-ups. The whole thing compresses to four words: secure, fast, mobile, unblocked. Tie these signals into the full checklist in my technical SEO playbook.
Want this handled by someone who has measured search for 20 years?
Work with me