Case Study 1 — The Page Experience Update: When Google Announced a Ranking Factor and Told Everyone It Was Minor

Type: Real, public, Tier-1 event analysis. Every factual claim about the update comes from Google's own announcements and Search Central documentation. The industry reaction is described as practitioner consensus (Tier 2). No statistic or ranking movement is invented; where the effect is uncertain, that is said plainly.

Background

For most of Google's history, "page speed" was advisory. Google had used a modest mobile speed signal since 2018, but there was no clear, published, user-centered standard that a site owner could measure themselves against. Then, on May 28, 2020, Google announced something new: it would introduce a page experience ranking signal, and at its heart would sit a set of three measurable, user-focused metrics it called Core Web Vitals — Largest Contentful Paint, First Input Delay (the responsiveness metric later replaced by INP), and Cumulative Layout Shift. Google gave the industry something it rarely gives: about a year of advance notice, published thresholds, and free tools to measure against them.

This is the origin event for everything in Chapter 16. It is also one of the most instructive case studies in the entire book — not because of what the update did, but because of the enormous gap between how loudly it was announced, how carefully Google described its size, and how muted its actual effect turned out to be.

The rollout, in Google's own words

The "page experience" signal was never Core Web Vitals alone. Google defined it as a combination of signals: the three Core Web Vitals, plus mobile-friendliness, HTTPS security, and the absence of intrusive interstitials (the pop-ups that cover content). Core Web Vitals was the new, measurable core; the rest were signals Google already used.

Google rolled it out slowly and publicly:

FIGURE C16.1 — "The Page Experience rollout"                    [after Google's public announcements]
  May 2020        Announced. Core Web Vitals + thresholds published a year ahead.
  Jun–Aug 2021    MOBILE rollout, gradual, completing by end of summer 2021.
  Feb–Mar 2022    DESKTOP rollout, completing by end of March 2022.
  With it         AMP dropped as a REQUIREMENT for the Top Stories carousel — any qualifying page
                  could now appear, judged partly on page experience instead of a mandated format.
  2023–2024       Google retired the standalone "page experience report," folded guidance into a
                  simpler "understanding page experience" page; FID was replaced by INP in Mar 2024.

Two parts of that timeline changed real behavior. First, the AMP change: before this update, appearing in the coveted "Top Stories" carousel on mobile effectively required publishers to build AMP (Accelerated Mobile Pages, a stripped-down Google-backed page format — covered in Chapter 17). The Page Experience update removed that requirement, letting any page compete if it met the criteria. For publishers, this was the headline: a hated mandate lifted. Second, Google published the thresholds — LCP under 2.5 s, and so on — which, for the first time, turned "make it fast" into a specific, gradeable target.

The issue: Google worked hard to lower expectations

Here is what makes this case unusual, and why it is the anchor for §16.7. When companies announce a new ranking factor, the surrounding industry usually inflates it into a must-do emergency. Google, unusually, spent the run-up doing the opposite — actively managing expectations downward.

Across its documentation and its representatives' public communication, Google repeated a consistent set of qualifications, every one of which maps onto this chapter's "honest weight":

  • Page experience would be a tiebreaker — it would help distinguish between pages that were otherwise similar in relevance and quality, not vault a weak page over a strong one.
  • Great, relevant content would still win. Google stated that a page with the best, most relevant content would still be able to rank well even if its page experience was subpar. Page experience would not override relevance.
  • It was one of many signals, and relevance remained far more important.

📄 Read the Report

text FIGURE C16.2 — "A ranking factor announced with the brakes on" [after Google Search Central] THE SOURCE Google's Page Experience announcements + Search Central "page experience" guidance. WHAT'S THERE A new confirmed ranking signal (Core Web Vitals + mobile-friendly + HTTPS + no intrusive interstitials), a year of notice, published thresholds, free tools — AND repeated statements that it is a tiebreaker that will NOT override great, relevant content. WHAT IT SHOWS Google confirming a page-experience ranking signal is Tier-1 fact. Google ALSO telling you, in writing, that it is modest is the same Tier-1 source. Both are true. WHAT IT DOESN'T It does NOT publish a weight, a position-gain number, or any promise that fixing Core Web Vitals will move a specific ranking. The magnitude is deliberately left small and unquantified. THE MOVE Fix Core Web Vitals for users and take the tiebreaker nudge — but do not reorder your priorities above content and relevance to chase it. Believe Google's own sizing. THE LESSON The most authoritative source both CONFIRMED speed as a ranking factor and CAPPED how much you should expect from it. Read the whole sentence, not just the exciting half.

What it shows

When the mobile rollout actually happened in the summer of 2021, the widely-reported experience across the SEO community was: not much visibly changed in the rankings. This is practitioner consensus rather than a figure anyone can prove, and it is exactly what Google's own framing had predicted. There was no great reshuffling in which fast pages leapt over slow ones; relevance and quality kept doing the heavy lifting, and Core Web Vitals nudged among near-equals — quietly, at the margins, mostly invisibly.

Three lessons fall out of this, and they are the spine of §16.7:

  1. A "confirmed ranking factor" and a "big ranking factor" are not the same thing. Core Web Vitals is genuinely, officially a ranking signal — and genuinely, officially minor. The industry's instinct to treat every confirmed factor as an emergency is precisely the folklore this book fights (theme 3).
  2. The real payoff of the update was user experience, not rankings. The sites that benefited most were the ones that used the pressure as an excuse to fix genuinely bad experiences — slow servers, jumpy layouts, unresponsive pages — and reaped better engagement and conversions. The ranking nudge was a bonus on top of a real UX win.
  3. Google can be the source that deflates a myth. People who read only the headline ("Google makes speed a ranking factor!") over-invested. People who read the whole announcement ("...as a tiebreaker that won't override great content") calibrated correctly. The primary source told you the honest weight; most of the industry just didn't read to the end of the sentence.

Outcome

The Page Experience update settled into the background exactly as its modest framing implied. Google eventually retired the dedicated page-experience report in Search Console and folded its advice into a simpler "understanding page experience" document — a quiet admission that the topic did not need the elaborate scaffolding the launch had suggested. And in March 2024, Google swapped FID for INP, tightening the responsiveness metric because FID had turned out to flatter almost everyone (the story in §16.3). Core Web Vitals lived on, useful and real, as one measured tile of page experience — never the dominant factor the initial excitement had imagined.

The lesson

Read the whole announcement, and believe the source about magnitude, not just existence. Core Web Vitals is the rare ranking factor whose own inventor told you, up front and in writing, how much to weight it: a tiebreaker, secondary to relevance and quality, worth doing chiefly for your users. The practitioners who came out ahead were not the ones who chased the greenest score; they were the ones who fixed the genuinely broken experiences, banked the conversion gains, and spent the rest of their energy on the content and authority that actually decide rankings. The update is, in miniature, the argument of this entire chapter.

Discussion questions

  1. Google gave a full year of notice, published thresholds, and shipped free tools before the Page Experience update. Why would a company telegraph a ranking change so far in advance — and how does that behavior fit the "aligned incentives" argument from Chapter 1?
  2. The update both confirmed speed as a ranking factor and capped how much to expect from it — from the same Tier-1 source. How should that shape the way you present Core Web Vitals to a client who has read only the exciting headline? Draft one honest sentence you would put in a proposal.
  3. Removing the AMP requirement for Top Stories was, for publishers, the biggest practical effect of the update. Why might dropping a mandated fast format in favor of a measured experience signal be better for the open web — and what did publishers have to do differently as a result? (Chapter 17 covers AMP.)
  4. The observed ranking effect was widely described as "muted." How would you distinguish, honestly, "the effect was small" from "we couldn't detect the effect" — and which does the evidence actually support?
  5. In 2024 Google replaced FID with INP because FID "flattered everyone." What does it tell you about trusting any single green metric that a Core Web Vital could be so easy to pass that Google retired it? Tie your answer to the field-versus-lab distinction in §16.5.