Page Experience Signals

CMS-specific implementation guides

Operational runbooks translating this playbook onto each major CMS, including hosting edges, authoring workflows, and integration seams that typically move rankings and AI retrieval outcomes.

Prefer a CMS-wide lens before tackling another topic? Review every SEO & GEO playbook surfaced for WordPress, Shopify, Webflow, Drupal, HubSpot CMS, Contentful, or Adobe Experience Manager.

What Are Page Experience Signals?

Page experience signals are a set of UX-focused ranking factors Google uses to assess how users experience a page beyond its content. They include Core Web Vitals, HTTPS security, mobile-friendliness, and the absence of intrusive interstitials. Together, they form Google's Page Experience system — a ranking layer on top of content relevance.

Why Page Experience Matters for AI-Era SEO

AI search systems are built on Google's overall quality assessment of pages. A page with excellent content but poor page experience is less likely to be surfaced in AI Overviews or featured prominently in AI-driven search. Google's quality raters explicitly assess page usability — slow, clunky, or interstitial-heavy pages fail both users and algorithms.

The Full Page Experience Checklist

• Core Web Vitals — LCP, INP, and CLS (see the Core Web Vitals playbook for details)
• HTTPS — All pages must be served over HTTPS; HTTP pages receive a ranking penalty
• Mobile-friendliness — Pages must be usable on mobile; Google uses mobile-first indexing
• No intrusive interstitials — Full-screen popups that block content on mobile are penalized; cookie banners, age gates, and login walls that cover the full screen trigger this signal
• Safe browsing — Pages with malware or deceptive content are penalized or removed from index

Mobile-First Indexing Implications

Google indexes the mobile version of your page first. If your mobile experience is degraded — slower, content is hidden, or structured data is missing — those gaps affect how your page is indexed and ranked, even for desktop users. Mobile-first means your mobile experience is your SEO experience.

• Audit HTTPS status — Use Screaming Frog to find any HTTP pages or mixed content issues; force HTTPS via .htaccess or server config
• Run a mobile-friendliness test — Use Google's Mobile-Friendly Test tool (search.google.com/test/mobile-friendly) for key pages
• Check for mobile usability issues in GSC — Review the Mobile Usability report; fix text too small to read, clickable elements too close, and content wider than screen
• Audit interstitials — Test on mobile; any full-screen overlay before content is accessible is a risk; replace with slide-in banners or inline notifications
• Fix Core Web Vitals — See the Core Web Vitals playbook for detailed steps on LCP, INP, and CLS
• Check safe browsing status — Use Google's Safe Browsing Checker (transparencyreport.google.com/safe-browsing/search) for your domain
• Verify structured data on mobile — Use Google's Rich Results Test on mobile user agent to ensure structured data is present and valid in the mobile version
• Mixed content — An HTTPS page that loads HTTP resources (images, scripts, fonts) shows as insecure in browsers and can trigger ranking issues
• Desktop-only structured data — Some CMS implementations serve different HTML to mobile; verify your schema markup appears in the mobile-rendered source
• Aggressive cookie consent banners — Full-screen cookie walls that block content on mobile trigger the intrusive interstitial penalty; use a bottom banner instead
• Unoptimized mobile images — Serving desktop-sized images to mobile users tanks LCP and wastes bandwidth; use responsive images and modern formats
• Ignoring GSC Mobile Usability errors — Tap targets too close together and font sizes too small are real usability signals that affect rankings
• Google Search Console — Mobile Usability report, Core Web Vitals report, HTTPS issues
• Google Mobile-Friendly Test — Per-page mobile usability check
• Google Safe Browsing — Domain-level malware and phishing check
• Screaming Frog — HTTPS audit and mixed content detection

How much does page experience affect rankings?

Google has described it as a tiebreaker between pages with similar relevance — not a primary ranking factor. In highly competitive SERPs where many pages have similar content quality, page experience can be the deciding factor. For most sites, fixing glaring issues (HTTP, mobile usability) has more impact than marginal CWV improvements.

Does page experience affect AI Overviews?

Indirectly. AI Overviews draw from pages Google already trusts and ranks highly. Pages with poor page experience signals are less likely to rank well overall, which reduces their likelihood of appearing in AI Overviews. It's not a direct AI Overview signal, but it affects the underlying ranking that feeds AI Overview selection.

What is the intrusive interstitial penalty exactly?

Google penalizes pages where an interstitial (popup, overlay, or banner) covers the main content immediately after the user navigates from search results, specifically on mobile. Cookie consent banners are exempt if they don't cover the full screen. Age verification gates and login walls that block all content are not exempt.

How a News Publisher Recovered Traffic by Fixing Interstitials

A digital news publisher was experiencing lower-than-expected mobile organic traffic despite strong content and rankings. An audit revealed that their newsletter signup popup appeared on mobile immediately after a user arrived from a search result, covering the full screen before any content was visible. This triggered Google's intrusive interstitial penalty specifically for their mobile search traffic. After replacing the full-screen popup with a slide-in bottom banner that appeared after 30 seconds of reading, their mobile organic traffic improved measurably over the following 60 days. The fix took 2 hours of development time.