Holistic page-experience self-assessment mirroring Google's own question list: Core Web Vitals, HTTPS, intrusive interstitials, mobile usability, content prominence, and ad distinguishability. Use when user says "page experience", "UX signals", "interstitials", "mobile friendly", or "HTTPS check".
Holistic page-experience self-assessment mirroring Google's own question list: Core Web Vitals, HTTPS, intrusive interstitials, mobile usability, content prominence, and ad distinguishability. Use when user says "page experience", "UX signals", "interstitials", "mobile friendly", or "HTTPS check".
allowed-tools
["Read","Bash","WebFetch"]
Page Experience Self-Assessment
Google retired the standalone "page experience ranking signal" framing.
Per https://developers.google.com/search/docs/appearance/page-experience there
is no single page experience signal — Google's core ranking systems look
at a variety of signals that align with overall page experience. Of these,
Core Web Vitals are used by ranking systems; other aspects (HTTPS,
interstitials, mobile usability) don't directly boost rankings but make the
site more satisfying to use, which aligns with what ranking systems reward.
Evaluation is generally page-specific, with some site-wide assessments.
This skill runs Google's own self-assessment question list against a URL.
Google's Self-Assessment Questions
#
Question
How this skill checks it
1
Do your pages have good Core Web Vitals?
Delegate to seo-core-web-vitals skill (field data at p75)
2
Are your pages served in a secure fashion?
HTTPS, redirect, certificate, mixed content
3
Does your content display well on mobile devices?
Viewport meta, responsive markup, font size, tap targets
4
Does your content avoid excessive ads that distract from or interfere with the main content?
Ad density heuristics on HTML (manual confirmation advised)
5
Do your pages avoid using intrusive interstitials?
Interstitial heuristics on initial HTML
6
Can visitors easily distinguish the main content from other content?
Above-fold content prominence, labeled ads
Inputs
Input
Required
Notes
URL
Yes
Single page; page experience is evaluated per page
Mobile or desktop focus
No
Default mobile — interstitial rules target mobile entry from search
No fixed-width layouts (width=1024 style viewports, large fixed px containers).
Base font size ≥ 12px legible (16px recommended); tap targets ~48x48px.
For deeper checks, cross-reference the seo-technical skill (category 5).
Run interstitial heuristics on the initial HTML (the case Google
penalizes is a pop-up covering the main content when a user enters from
mobile search):
Fixed/absolute full-viewport overlays in initial HTML: elements with
position:fixed or position:absolute combined with top:0 +
width:100%/100vw + height:100%/100vh, high z-index.
Is meaningful main content present in the initial HTML above the fold,
or is the first viewport dominated by ads/promos/navigation?
Are ad containers distinguishable/labeled (e.g., "Advertisement",
aria-label, distinct containers)?
Count ad-network script includes (adsbygoogle, GPT, taboola, outbrain,
mgid) as an ad-pressure signal. These are heuristics — note that final
judgment needs visual review.
Delegate CWV measurement to the seo-core-web-vitals skill and import
its PASS/FAIL verdict for question 1. Do not duplicate the measurement here.