What page experience means in Google's guidance
Google Search Central's page on page experience opens with a statement of intent: its core ranking systems look to reward content that provides a good page experience. It then advises site owners not to focus on only one or two aspects, but to check whether they provide a good experience across many, and offers a set of self-assessment questions:
- Do your pages have good Core Web Vitals?
- Are your pages served in a secure fashion?
- Does your content display well on mobile devices?
- Does your content avoid using an excessive amount of ads that distract from or interfere with the main content?
- Do pages avoid using intrusive interstitials?
- Is your page designed so visitors can easily distinguish the main content from other content on the page?
The same page answers the questions people ask about weight. It says there is no single page experience signal; the ranking systems look at a variety of signals that align with overall experience. It says evaluation is generally page by page, though some assessments are site-wide. And it says Google Search always seeks to show the most relevant content even if its page experience is sub-par, while for queries with plenty of helpful content available a great page experience can contribute to success.
That is the whole of what this guide relies on. It does not assign weights, and it does not treat any single question as a ranking factor with a measurable effect. Google's guidance on helpful content, which includes a section on page experience and asks in its presentation questions whether content displays well on mobile devices and whether ads distract from or interfere with it, makes the same point from the content side: the experience is part of whether a page serves the person who arrives. The quality of the content itself, and who stands behind it, is covered in the E-E-A-T and content quality guide.
Secure connections
The question is whether pages are served securely, which in practice means over HTTPS with a valid certificate and nothing on the page loaded over an insecure connection. Most sites passed this long ago, so the failures that remain are partial:
- Mixed content. An HTTPS page that loads an image, script, font or embed over HTTP. Browsers block or warn about some of it, and the page is not fully secure.
- Leftover HTTP addresses. Old internal links, canonical tags, sitemap entries or redirects that still use HTTP and rely on a redirect to reach the secure version.
- Secondary hosts. A subdomain for a shop, a help centre or a campaign microsite that was never moved to HTTPS or whose certificate has lapsed.
- Forms posting to insecure endpoints, which browsers flag to the person filling them in.
Search Console's reports on HTTPS status and a crawl that records the protocol of every resource find these quickly. Moving a site from HTTP to HTTPS is a URL change, and the site migrations guide treats it as one.
Displaying well on mobile devices
The question here is about the page as a phone user sees it, not about how Google indexes mobile pages, which the cited guidance does not describe. A page displays well on a phone when the viewport is set so the layout fits the screen, text is readable without zooming, tap targets are large enough and far enough apart for a thumb, nothing is wider than the screen so no sideways scrolling is needed, and the content a desktop visitor gets is not missing or hidden behind extra taps.
The commonest failures are template-level: tables and embeds that overflow, navigation and filter panels that cover the content, buttons placed where thumbs miss them, and long blocks of boilerplate that push the main content several screens down. Review on real phones at the widths your visitors use, not only in a desktop browser narrowed to phone width. The speed and mobile guide for landing pages covers thumb reach, forms and layout for conversion; the same rules make a page display well for search visitors.
Interstitials and overlays
An interstitial is anything that stands between the visitor and the content they came for: a full-screen sign-up box on arrival, an app download prompt that fills the screen, a dialog that must be dismissed before reading starts. Google's question is whether pages avoid intrusive ones, and the word that matters is intrusive. A visitor who clicks a result expecting a recipe and gets a full-screen form has been interrupted before the page has done anything for them.
General practice separates overlays by what they cover and when they appear:
| Overlay | Usually intrusive? | Why |
|---|---|---|
| Full-screen box on arrival, before any content is visible | Yes | Blocks the content the visitor came for |
| Large box covering most of a phone screen after a short delay | Usually | Same effect on a small screen, slightly later |
| A banner using a modest strip of the screen | Rarely | Content remains readable |
| An offer shown after the visitor has scrolled or finished reading | Rarely | Appears after the page has served its purpose |
| A notice the site is required to show, such as a cookie consent request | Depends on size | Necessary, but it can still be compact |
Phones change the answer. A box that sits politely in the corner of a desktop screen can cover the whole of a phone screen, so overlay rules should be set per device. Whether an overlay is worth what it costs in interrupted visits is a question for a test, and the exit-intent popup experiment shows how to read sign-ups and revenue together rather than sign-ups alone.
App download prompts are the commonest phone overlay, and the guide to web-to-app journeys shows how to replace an arrival overlay with a small banner or a prompt after engagement, aimed at the customers the app actually serves.
Advertising and the main content
Two of the questions are about the relationship between the main content and everything around it: whether ads distract from or interfere with the content, and whether the main content is easy to distinguish. Ads are not the problem in themselves; the problem is placement and density that make the visitor work to find what they came for. Patterns that fail both questions:
- Ads stacked above the content, so the first screen on a phone shows a heading and then advertising.
- Ads inserted between every paragraph or between steps of a method, breaking the thread.
- Sticky ads that cover text as the visitor scrolls, especially on small screens.
- Ads that look like content, such as native units styled as related articles without a clear label.
- Ads that load late and push the content down, which also shows up as layout shift in Core Web Vitals.
- Recommendation widgets and newsletter boxes placed so densely that the article becomes the smaller part of the page.
The fixes are design decisions: a limit on units above the main content, clear labels, reserved space for every slot so nothing shifts, and a visual treatment that makes the main content plainly the main thing. On commercial pages, the same discipline applies to promotional banners, cross-sell carousels and chat widgets, which compete with the content just as ads do.
Where Core Web Vitals fit
Core Web Vitals are the one question with a metric attached. Google's documentation describes them as a set of metrics measuring real-world loading performance, interactivity and visual stability, says they are used by its ranking systems, recommends achieving good results for success with Search and a good experience generally, and states that good results do not guarantee good rankings. The Core Web Vitals guide covers the three metrics, the thresholds, the field data behind the assessment and the fixes by template, and the troubleshooting page for a slow Largest Contentful Paint works through the causes of slow loading one at a time. This guide does not repeat them.
The link between the metrics and the other questions is practical. Late-loading ads and overlays are among the common causes of layout shift; heavy ad and consent scripts slow responsiveness; a hero image pushed down by a promotional banner can become the slowest element. Fixing interstitials and ad placement often improves the metrics as a side effect, which is a reason to review the questions together.
Reviewing a template against the questions
Page experience is set by templates, so the review runs one template at a time: the article, the product, the category, the Landing PageThe page a visitor arrives on from a campaign, built to turn that visit into one action.. Load a representative page on a phone and on a desktop, as a first-time visitor with no cookies, and answer each question from the table.
| Question | What to check on the template | How to check | Typical fix |
|---|---|---|---|
| Good Core Web Vitals? | Status of the template's URL group | Search Console's Core Web Vitals report; field data | Per the Core Web Vitals guide |
| Served securely? | HTTPS throughout, no insecure resources, valid certificate on every host | Crawl recording protocols; browser security panel | Update resource URLs, redirect HTTP, renew certificates |
| Displays well on mobile? | Viewport, readable text, tap targets, no overflow, content parity | Real phones at common widths | Responsive tables and embeds, larger targets, trimmed boilerplate |
| Avoids intrusive interstitials? | What covers the content on arrival, and when | First visit on a phone with no cookies | Banner instead of full-screen box; delay until engagement |
| Ads not interfering? | Units above and within the main content; sticky units | Screenshot of the first two screens on a phone | Fewer units above content; no sticky units over text |
| Main content distinct? | Whether the content starts near the top and is visually primary | Ask someone unfamiliar where the content begins | Labels, spacing, move widgets below the content |
Record the answer per question and per device, with a screenshot, so the next review can compare.
Mossbeacon Recipes reviews its article template
Mossbeacon Recipes, an invented recipe publisher, reviews its recipe template on a mid-range phone with no cookies. The first screen shows the title and a full-screen newsletter overlay; once it is dismissed, three ad units and a video player sit above the ingredients, and the method starts on the fifth screen. Core Web Vitals pass for the template, so nobody had looked further. The team replaces the arrival overlay with a banner shown after the visitor reaches the method, limits units above the ingredients to one, reserves space for every ad slot and adds a jump-to-recipe link under the title. Over the following month, the share of mobile visits that reach the method rises from 38% to 57%, and visits that leave within ten seconds fall from 41% to 29%. Rankings are not part of the measure: the change was made for the visitor, and engagement is what it moved.
Common mistakes
- Treating page experience as Core Web Vitals. The metrics are one question of six; a fast page behind a full-screen overlay still fails.
- Expecting a ranking jump from a single fix. Google describes no single signal and puts relevance first; the reason to fix the experience is the visitor.
- Reviewing on desktop only. Overlays, ad stacks and overflowing tables are phone problems first.
- Reviewing pages instead of templates. The template produces the experience on every page that uses it.
- Testing with a returning visitor's cookies, which hides the overlays and consent prompts a first-time visitor from search sees.
- Letting ads and widgets accumulate. Each unit is approved alone; together they bury the content.
- Forgetting secondary hosts. A help centre or shop on a subdomain with lapsed HTTPS undermines the rest.
