Six months’ notice is the work, not the wait
Structure and markup refreshed for current answer engines; the original analysis is preserved.
Google almost never tells you a ranking change is coming before it arrives. This month it did: the page experience signal becomes a ranking factor in May 2021, about six months out. That advance notice is itself the message. Google warns you ahead of time only when the change takes real work to prepare for and cannot be fixed overnight — so the six months is not slack to relax in. It is roughly how long the work actually takes.
the short answer
Google confirmed the page experience signal becomes a ranking factor in May 2021 — about six months’ notice, which Google almost never gives. The notice is the message: Google pre-announces only when a change rewards work you must do and that work takes time. The six months isn’t slack — it’s roughly how long the measure-fix-remeasure loop takes, since the field data Google judges you on lags fixes by weeks. Start now; finish before May.
key takeaways
- Google confirmed that the page experience signal becomes a ranking factor in May 2021 — about six months’ advance notice, which Google almost never gives.
- The notice itself is the message: Google pre-announces only when a change rewards work you must actively do, and when that work genuinely takes time.
- Ranking changes normally reach you after the fact — a core update as it rolls out, or unannounced. A dated pre-announcement is the rare case where you can prepare.
- The six months is not slack. It is roughly how long the measure-fix-remeasure loop takes, because the field data Google judges you on lags real fixes by weeks.
- Use the window as a work plan that ends before May: measure against the thresholds, fix by template, then leave margin for the field data to catch up.
the runway, read correctly
The window between the two dates is not empty time. Most of it is the work, and the tail of it is the measurement catching up to the work — which is why finishing in May is finishing late.
The idea, in four parts
What Google said and what is unusual about it; why the advance notice is the real signal; the trap of a distant deadline; and how to spend the runway. Open each part.
01 What Google said, and what’s unusual about it
This month Google put a date on something it had been discussing since the spring: the page experience signal will become a ranking factor in May 2021. The signal bundles together the Core Web Vitals introduced earlier this year — measures of loading, interactivity, and visual stability — with user-experience signals Google already used, namely mobile-friendliness, HTTPS, and the absence of intrusive interstitials. As part of the same announcement, Google said pages will no longer need to be in the AMP format to appear in the Top Stories carousel on mobile; any page that meets the page experience bar becomes eligible, which is a meaningful vote of confidence in these metrics. All of that is worth knowing, but it is not the part that should change how you act this month, because the components have been on the table for a while. The genuinely notable thing is the shape of the announcement itself: Google named a future change and attached a date to it, roughly six months out, before any of it takes effect. If you have followed Google for any length of time, you know how rarely that happens. The company is normally tight-lipped about what is coming and when. So the first thing to register is not the contents of the page experience signal — which others have explained at length — but the mere fact that you were told in advance at all. That fact carries information, and it points in a clear direction: this is a change Google expects you to prepare for, and it has handed you the time to do it.
02 Why advance notice is the real signal
To see why the pre-announcement matters, contrast it with how ranking changes usually reach you. The typical pattern is retrospective. A core update is announced as it begins rolling out, not before, so the most you get is confirmation that movement underway is real — you still cannot have prepared for it. And the great majority of the adjustments Google makes, thousands in a year, are never announced at all; you infer them, if you notice them, by watching your metrics shift and reasoning backward toward a cause. Against that backdrop, a dated pre-announcement is a different animal entirely: you are told what is changing and when, with months to act, before a single ranking moves. Google reserves that treatment for a specific kind of change, and recognising the kind is the whole point. It pre-announces when the change rewards something you have to build rather than something you already have, and when building it takes real time. Page experience fits exactly. You cannot conjure good Core Web Vitals on demand; reaching them can mean reworking how pages load and render and hold their layout steady, which is engineering, not a setting you toggle. To spring that on the web the day it took effect would punish everyone for not having a time machine. The advance notice, then, is not a courtesy detached from meaning — it is Google telling you three things at once: this matters enough to warn you about, it is something you can prepare for, and here is the runway. The notice is the signal. The contents are just what the signal is about.
03 The trap of a distant deadline
Here is where a predictable mistake creeps in. A human hears May 2021, notes that it is half a year away, files it under later, and moves on to things that feel urgent now. That instinct is wrong, and the reason is a fact about measurement that the calendar hides: the six-month window is not a generous buffer, it is approximately how long the work takes for a site that genuinely has work to do. Improving page experience is a loop — measure where you stand, diagnose what is hurting you, do the engineering, then measure again — and the loop has built-in latency at both ends. The fixes themselves can be substantial, touching templates, scripts, images, fonts, and third-party embeds rather than a single line. But the subtler delay is in the measurement. The data Google will actually judge you on is field data: real measurements gathered from real visitors to your pages, aggregated over a trailing window of weeks. That means an improvement you ship today does not register in your scores today; it registers gradually, as new visitor data accumulates and the old data ages out. Ship a fix in late April and the change may simply not be reflected in the field data by the time May arrives — you did the work and still get measured on your old numbers. This is why a distant deadline is more dangerous than a near one: it invites you to spend the very runway that the work requires sitting idle, and then to discover, too late, that the latency you ignored has run out the clock. The deadline is not far away in any way that helps you. Measured in the work it demands and the lag before that work shows, it is close.
04 How to spend the runway
Treat the next months as a measurement-led plan that finishes comfortably before May rather than arriving at it. Begin by measuring honestly against the published thresholds: open the Core Web Vitals report in Search Console to see which pages and page groups fall short on loading, interactivity, or visual stability, and use PageSpeed Insights and Lighthouse to diagnose why. Weight the field data — the real-world numbers from actual visitors — above any single lab run, because the field data is what the ranking change will read. Then prioritise by impact: because most page experience problems live in a template rather than a lone URL, group your pages by template and fix the templates carrying your most important traffic first, so one piece of engineering lifts many pages at once. Do the work, ship it, and then deliberately watch the field data recover over the following weeks — the part people forget — because that trailing measurement, not the moment your code merged, is what confirms you actually moved. Schedule backward from May so your final fixes land with weeks of margin for the data to catch up, not days. And hold the whole effort in proportion: Google has been clear that page experience is one factor among many, that a fast page will not outrank a more relevant one on speed alone, and that strong content is not sunk by an imperfect score — so resist the pull to chase a perfect number at the expense of the substance that ranks you in the first place. A known date and a measurable bar are a gift precisely because they let you plan; turning them into a paced schedule that ends early, with margin for the measurement to confirm the work, is the discipline the AC Group has worked by for 27 years.
Why this is a measurement problem, not a panic
It would be easy to read a dated ranking change as a reason to panic, and easy in the other direction to file it under someday and forget it. Both responses miss what the announcement actually hands you, which is something rare and useful: a known bar and a known date. Most of the time you are measuring in the dark — watching positions move and guessing at causes, with no target and no timeline. Here you have both. You know exactly what is being measured (loading, interactivity, visual stability, alongside the older experience signals), you can measure your own pages against those bars today, and you know when it starts to count. That turns an anxious unknown into a planning problem, which is a far better problem to have.
The discipline, then, is to treat the notice as a measurement and scheduling exercise rather than an emotion. Where do you stand against the thresholds now; which templates carry the gap; how long will the fixes take; and how much margin must you leave for the field data to reflect them before the date? Answer those and the deadline stops being a source of dread or procrastination and becomes a project plan. Reading an advance notice as the gift of a target and a timeline — and converting it into a paced schedule rather than a scramble — is the measurement discipline the AC Group has worked by for 27 years.
What to do with this
Start measuring now, not in spring. Pull your Core Web Vitals report in Search Console to see which pages and page groups fail on loading, interactivity, or visual stability, and use PageSpeed Insights and Lighthouse to understand why — trusting the field data, gathered from real visitors, over any single lab run, because the field data is what the change will read. Group the failures by template, since most fixes live in a template rather than a single URL, and start with the templates that carry your most important traffic so one repair lifts many pages.
Then do the engineering, ship it, and watch the field data recover over the following weeks — that trailing measurement, not the merge, is your real confirmation. Schedule backward from May so your last fixes land with weeks to spare, and keep the effort in proportion: page experience is one factor among many, a fast page does not outrank a more relevant one on speed alone, and strong content is not sunk by an imperfect score, so do not let a perfect-number chase crowd out substance. The thing Google handed you this month is a target and a date; the right response is a plan that uses every week of the runway and finishes early, with margin for the measurement to confirm the work. Turning a known deadline into that paced plan is the discipline the AC Group has worked by for 27 years.
Reading the notice, plainly: quick answers
What did Google announce this month?
Google confirmed a date for its page experience update: the set of page experience signals will become a ranking factor starting in May 2021. Those signals combine the Core Web Vitals introduced earlier this year — loading, interactivity, and visual stability — with existing user-experience signals Google already used, including mobile-friendliness, HTTPS security, and the absence of intrusive interstitials. None of the individual pieces is brand new; what is new is the commitment to fold them into ranking on a stated date, roughly six months from now. Google also said that with this change, pages will no longer need to be built in the AMP format to be eligible for the Top Stories carousel on mobile — any page meeting the page experience criteria can qualify — which signals real confidence in these metrics as a measure of quality. But the detail worth dwelling on is not the contents of the signal, which have been discussed since the spring; it is the timing of the announcement. Google told the web what is changing and when, well before it happens. That is unusual enough to be the real story, and the rest of this note is about why the advance notice matters more than the signal it concerns.
Why is it significant that Google gave advance notice?
Because Google almost never does it, and the exception tells you something. The way ranking changes normally reach you is after the fact: a core update is announced as it begins rolling out, not months ahead, and most of the thousands of smaller adjustments Google makes each year are never announced at all. You usually learn that something changed by watching your data move, then working backward to guess why. A pre-announcement with a date attached inverts that completely — you know what is changing and when, before it lands. Google does this only in particular circumstances, and they are revealing: it pre-announces when the change rewards something site owners must actively build, and when that building genuinely takes time. You cannot improve your Core Web Vitals overnight; it can require engineering work on how pages load, render, and stabilise, and then weeks more for the measurement to catch up. Announcing the change the moment it took effect would be unfair, because no one could have prepared in time. So the advance notice is not generosity for its own sake; it is a signal that this is the kind of change you are expected to prepare for, that preparation is possible, and that Google has given you the runway to do it. Reading the notice itself as information — not just its contents — is the start of using it well.
May 2021 is months away — can’t I deal with it later?
That instinct is exactly the trap the date sets, and it is worth resisting on the basis of how the work and the measurement actually behave. The six-month window is not padding; it is roughly the duration of the task for a site that has real work to do. Improving page experience is a measure-diagnose-fix-remeasure loop, and each turn of that loop has latency. You measure where you stand, identify what is hurting loading or stability or interactivity, do engineering work that may touch templates, scripts, images, and third-party embeds, then ship it — and then you wait, because the field data Google actually uses to judge you is gathered from real visitors over a trailing window of weeks, so an improvement you ship today does not show up in your scores immediately. If you start in, say, April, you may make the fixes but have no time for the field data to reflect them before the change takes effect, which means you arrive at May still measured on your old, worse numbers. Treating a distant deadline as permission to wait misunderstands that the lag is built into the system. The sites that benefit from the notice are the ones that start now, finish well before May, and leave enough margin for the measurement to catch up. The runway is the work; spending it as idle time is how you waste it. Helping clients read a deadline like this correctly — as a work schedule, not a faraway date — is what the AC Group has done for 27 years.
How should I use the next six months?
Use them as a measurement-driven work plan that ends comfortably before May, not in it. Start by measuring where you actually stand against the published thresholds: pull your Core Web Vitals report in Search Console to see which pages and page groups are failing on loading, interactivity, or visual stability, and corroborate with PageSpeed Insights and Lighthouse for diagnosis. Crucially, weight what the field data — the real-world measurements from actual visitors — tells you over what a single lab test shows, because the field data is what Google will judge you on. Then prioritise: group your pages by template, since most fixes apply to a template rather than a single URL, and tackle the templates that drive the most important traffic first. Do the engineering, ship it, and then — this is the part people skip — watch the field data recover over the following weeks, because that trailing measurement is the true confirmation, not the moment your code merged. Plan backward from May so that your last fixes land with enough margin for the data to reflect them. And keep perspective: page experience is a real factor but not the dominant one, and Google has been explicit that a great experience will not rescue thin content while strong content is not sunk by an imperfect score — so do not let a perfect-score chase crowd out the substance that matters more. Turning a known deadline and a measurable threshold into a paced plan that finishes early is the measurement discipline the AC Group has worked by for 27 years.
A note on sources and timing
This is written in November 2020, just after Google attached a date — May 2021 — to its page experience update. The description of the signal (Core Web Vitals for loading, interactivity, and visual stability, combined with mobile-friendliness, HTTPS, and the avoidance of intrusive interstitials), the opening of Top Stories to non-AMP pages, and the role of field data gathered from real visitors all follow Google’s own announcements this year. The point that matters here is not the contents of the signal but the rarity of the advance notice, and what that rarity implies: Google pre-announces when a change must be prepared for and that preparation takes time. The durable lesson outlasts this one deadline — when you are given a target and a date, the window is the work, not the wait — the measurement discipline the AC Group has worked by for 27 years.