A content update can be judged once its 28-day after window has fully ended and Search Console's newest days have settled, which Penlid puts at 38 days after the change goes live. Google gives no fixed time for a content update to affect rankings, so wait for completed windows, not a hoped-for number of days.
- Penlid measures a change 38 days after it goes live: 28 days of after window, a 7-day allowance of our own and about 3 days of reporting lag (Penlid, SEO test calculator, read 30 October 2026).
- Google says collected Search Console data is usually available in 2–3 days (Google, Search Console Help, read 30 October 2026).
- Google gives ranges, not a deadline, for a change to show in Search: some changes can take effect in a few days and others could take several months (Google, Search Central, read 30 October 2026).
- Google recommends waiting at least a full week after a core update completes before analyzing your site in Search Console (Google, Search Central, read 30 October 2026).
Does Google say how long a content update takes to show in search?
No: Google gives ranges, not a fixed time, for how long a change takes to show in search. For a large drop in position, its debugging guide says some changes can take effect in a few days while others could take several months, and that you will likely want to wait a few weeks before analyzing Search Console again. Its core update guidance adds that there is no guarantee that changes you make will have a noticeable impact in search results. Our reasoning: with no published end date, "wait 30 days" is a convention you choose, not a Google deadline.
What are you actually waiting for after you publish a change?
You are waiting on four separate clocks: Google fetching the page again, Search Console collecting your days, those days settling, and your own after window filling.
| Clock | What it waits for | Published figure | From |
|---|---|---|---|
| Crawl | Google fetches the page again | Requested: a few days to a few weeks. In general: several days to several months | Google, Search Central |
| Reporting | Search Console collects the days | Usually available in 2–3 days | Google, Search Console Help |
| Settling | The newest days stop changing | Google: the newest data is sometimes preliminary and may change in the next few hours. Penlid allows 7 days | Google, Search Console Help; Penlid |
| Window | The after window fills | 28 days, from the day after the change | Penlid |
Our reasoning: the crawl is the one clock you cannot schedule, so Penlid counts its windows from the day the change goes live, and a slow crawl shows up as a quiet start to the after window rather than a longer wait.
Why does Penlid read a change 38 days after it goes live?
Penlid reads a change at day 38 because that is 28 days of after window plus two margins: a 7-day allowance for the newest days to settle and about 3 days of Google reporting lag (28 + 7 + 3 = 38). The 7 is our own allowance, not a Google figure.
- 28 days. The after window is days 1 to 28, with the day of the change left out. Our reasoning: four whole weeks hold each weekday four times, and Google suggests weekly or monthly granularity for comparing date ranges because it dampens day-of-week effects.
- 7 days. Google's About the data article says the newest data is sometimes preliminary and may change in the next few hours, and the SEO test calculator's page says Google gives no time by which a day is final, so Penlid allows 7. Our reasoning: that is longer than the 2–3 days Google gives for collection, so it errs toward waiting a little long.
- 3 days. Google says collected data is usually available in 2–3 days, and Penlid takes the top of that range.
The SEO test calculator prints the day for any change date you pick. The day-by-day path of the did-it-work tool needs the 56 days before each change and the 28 days after it, so export on or after day 38 and every day in your after window is at least 10 days old. For the whole procedure, see how to tell if a content update worked.
Does a low-traffic page need to wait longer?
No: the wait is the same 38 days at any traffic level, but how often a real lift is found depends on traffic, the size of the lift, the number of comparison pages and how far untouched pages drift apart.
| Clicks a day | About clicks in 28 days | Real lift | Drift between pages | Comparison pages | Found |
|---|---|---|---|---|---|
| 4 | 112 | +50% | none | 6 | 61.23% |
| 4 | 112 | +50% | none | 8 | 70.02% |
| 4 | 112 | +80% | none | 6 | 92.01% |
| 400 | 11,200 | +10% | none | 6 | 99.95% |
| 4 | 112 | +80% | 15% | 6 | 59.65% |
| 400 | 11,200 | +80% | 15% | 6 | 82.20% |
Read the table, from the Penlid methodology, as what one 28-day window buys, not as a promise. At 4 clicks a day, eight comparison pages find a +50% lift 70.02% of the time against 61.23% for six, and drift between pages cuts a +80% lift from 92.01% to 59.65%. The SEO test calculator's page says this drift does not shrink as a page gets bigger, and the methodology's text reports a +80% lift with drift found only 82.20% of the time even at 400 clicks a day.
Penlid's windows are fixed at 28 days and the methodology does not measure longer ones, so we do not claim that waiting longer turns "we cannot tell" into an answer. If your page resembles a row with a low Found figure, size the test with the SEO test calculator before you change it, and see how much traffic a page needs and inconclusive SEO tests.
Does a Google update change how long you should wait?
A Google update changes when you can read the update, not when you can read your edit. For a core update, Google recommends waiting at least a full week after a core update completes
, then comparing that week with the week before the rollout began. The three latest core updates took about 12 to 18 days to roll out.
| Entry | Began | Ran for |
|---|---|---|
| May 2026 core update | 21 May 2026 | 11 days 21 hours |
| March 2026 core update | 27 Mar 2026 | 12 days 4 hours |
| December 2025 core update | 11 Dec 2025 | 18 days 2 hours |
If a rollout overlaps your after window, your edit and the update share the same days, and waiting does not move the window. Penlid sets your page against untouched comparison pages, but the methodology says matching on pre-period behavior removes a lot of confounding and cannot remove all of it: a change that happens to coincide with something else page-specific will still be misattributed. Our reasoning: an update need not move every page equally, so note the overlap beside the result and read it with more doubt. See measuring what a Google update did to your site for the update itself.
What should you leave alone while you wait?
Leave the changed page and its comparison pages alone until the after window ends.
- Do not edit the page again. If you change a page twice within 56 days, the SEO test calculator says Penlid refuses to measure it.
- Do not edit the comparison pages. Pages changed from 56 days before the change to 28 days after it are left out and counted, and fewer than three untouched pages left means "not measurable".
Example (illustrative numbers)
These counts are invented to show the arithmetic; they are not data from any site. A page is rewritten on 14 April (day 0). Its after window is 15 April to 12 May (days 1 to 28), the 7-day allowance runs to 19 May (day 35) and the reporting lag to 22 May (day 38), so the read date is 22 May (28 + 7 + 3 = 38).
Before the change the page earned 1,372 clicks in 28 days and four untouched pages earned 6,244 together. After it, the page's weekly clicks were 318, 349, 427 and 527, and the untouched pages' were 1,572, 1,599, 1,587 and 1,573. Each row sets the running total against the before total pro-rated to the same days (1,372 × 7 ÷ 28 = 343).
| Days read | Page, before | Page, after | Untouched, before | Untouched, after | Versus prediction |
|---|---|---|---|---|---|
| 7 | 343 | 318 | 1,561 | 1,572 | −7.9% |
| 14 | 686 | 667 | 3,122 | 3,171 | −4.3% |
| 21 | 1,029 | 1,094 | 4,683 | 4,758 | +4.6% |
| 28 | 1,372 | 1,621 | 6,244 | 6,331 | +16.5% |
For day 28: 1,621 ÷ 1,372 = 1.181 for the page and 6,331 ÷ 6,244 = 1.014 for the untouched pages, so 1.181 ÷ 1.014 = 1.165, or +16.5% versus what the untouched pages predict. The sign flips between week 2 and week 3 because this invented page starts slowly and then climbs, so a read at day 7 or 14 would have called the edit a loss.
The ramp is invented: real pages can climb, fade or stay flat. Penlid's estimator also works page by page on log ratios and adds a 95% interval and p-value, which we have not computed for invented counts.
What this cannot tell you
- The 38 days are our rule, not Google's. Google publishes ranges and no deadline. Our reasoning: a window longer than our fixed 28 days gives another event more time to land on the page, so longer is not shown to be better.
- A day-38 read describes days 1 to 28. Google says some changes could take several months, so an unclear result cannot rule out a later effect. Our reasoning: if Google fetches the page late, the early days of the window cannot show the edit's effect, which dilutes the measured lift.
- Waiting does not remove other causes. Seasonality, regression to the mean in pages picked because they were declining, a link, a news event, an update or an edit nobody recorded can still be credited to your change.
- The detection figures come from simulated sites. The SEO test calculator says real daily counts are somewhat more variable than its simulations assume, and it makes no promise about rankings.
Questions people also ask
How long does a Google update take to roll out?
Across the eight latest ranking entries on Google's Search Status Dashboard when we read it on 30 October 2026, rollouts lasted from 19 hours 30 minutes to 21 days 17 hours. The three core updates among them took between 11 days 21 hours and 18 days 2 hours. For any update you care about, use the start and end dates the dashboard records rather than a general estimate.
How long should you wait after updating content before checking results?
Wait for four full weeks of data after the edit plus about ten more days for the newest days to settle, which is 38 days in total. That is Penlid's rule rather than a Google deadline: the 28 days match the length of the before window, and the extra ten give the newest days time to stop changing.
Is a week long enough to judge a content update?
Usually not. Google's one-week figure is the pause it recommends after a core update completes, not a rule for judging one page. Relative counting noise falls as traffic rises: a page earning 4 clicks a day collects about 28 clicks in a week (4 × 7), and the square root of 28 is about 5.3, or 19% of the total (our arithmetic, if counts are Poisson as the SEO test calculator assumes). Even a busy page's newest days may still change.
How long does it take Google to see changes to a page?
Google publishes no fixed time. It says a requested crawl may take a few days to a few weeks, that crawling in general can take several days to several months, and that repeating a request for the same URL does not speed it up. You cannot wait for a date Google does not publish, so count your windows from the day you published; a slow crawl then shows up as a quiet start to the after window.
How long should you wait before deciding a content change failed?
Wait the full 38 days, then read the result as worded. A clearly negative figure versus what the untouched pages predict says the page did worse than comparable pages over those days. "We cannot tell" says the data could not separate the change from chance, not that the change did nothing; for a page with 10 or more clicks before the change, Penlid then names the smallest lift the measurement could have detected, while below 10 clicks it gives a direction and no size, and with no clicks no measurement. The guide to inconclusive SEO tests covers what to do next.
Sources
- Performance report (Search results): About the data, Google, Search Console Help, read 30 October 2026.
- Performance report (Search results): Troubleshooting data discrepancies, Google, Search Console Help, read 30 October 2026.
- Performance report (Search results): Advanced filtering and comparison, Google, Search Console Help, read 30 October 2026.
- Google Search's core updates and your website, Google, Search Central, read 30 October 2026.
waiting at least a full week after a core update completes
- Debugging drops in Google Search traffic, Google, Search Central, read 30 October 2026.
- Ask Google to recrawl your URLs, Google, Search Central, read 30 October 2026.
- AI features and your website, Google, Search Central, read 30 October 2026.
- Google Search Status Dashboard, Google, Search Status Dashboard, read 30 October 2026.
- Methodology: how we measure, and what we can't, Penlid, read 30 October 2026.
- Did that content change actually work?, Penlid, read 30 October 2026.
- SEO test calculator, Penlid, read 30 October 2026.