Updated
To recover from a Google core update, first confirm your drop lines up with the update’s dates on Google’s Search Status Dashboard, wait at least a week after the rollout finishes, then compare equal windows before and after it in Search Console, broken down by page type, to see what lost ground. Then improve those pages for people, not with quick fixes. Google says it can take several months for its systems to recognize the changes, and sometimes not until the next core update.
Most core update recovery guides online were written for an update from 2022 to 2024 and stay general. This one is a measurement plan: how to tell what an update changed on your site, what Google says helps, and what doesn’t.
What a core update is
Google describes core updates as “significant, broad changes to our search algorithms and systems” made several times a year (Google’s core updates guide). They don’t target specific sites or pages. They change how Google assesses content overall, so some pages move up and others move down. Google’s analogy is a list of the best restaurants being redone: the list changes, and restaurants that move down “aren’t necessarily bad”.
That makes a core update different from three other things that look similar in a traffic chart:
- A manual action: a person at Google applied it, and it appears in Search Console’s Manual actions report with a reason.
- A spam update: aimed at the practices in Google’s spam policies, listed separately on the Status Dashboard.
- A technical problem: pages dropping out of the index, a noindex shipped by mistake, a broken redirect. The Page indexing report shows these.
Google updates in 2026
Dates from Google’s Search Status Dashboard. The November 2026 core update was still rolling out when this page was updated on 16 November 2026.
| Update | Started | Finished |
|---|---|---|
| March 2026 core update | 27 March 2026 | 8 April 2026 |
| May 2026 core update | 21 May 2026 | 2 June 2026 |
| November 2026 core update | 10 November 2026 | Rolling out; Google said it “may take up to 2 weeks” |
| September 2026 spam update | 24 September 2026 | 8 October 2026 |
There were also smaller spam updates in March, June and August 2026; the dashboard lists each one. Google also makes smaller core updates it doesn’t announce, because they “aren’t widely noticeable”.
Step 1: Confirm the timing, and rule out everything else
A drop that starts during a rollout is a candidate, not a verdict. Before blaming the update, check:
- Manual actions and Security issues in Search Console. Both should be empty.
- The Page indexing report. A rise in “Not indexed” pages, especially Excluded by noindex tag or redirect errors, points to a site change, not an update.
- Your own changes. Releases, template edits, URL changes, a new theme or plugin, in the same weeks.
- Seasonality. Compare the same weeks last year. A dip every November is demand, not Google.
- Search Console data issues. Google lists reporting problems on its data anomalies page. One matters for 2026 comparisons: Google says a logging error prevented Search Console from accurately reporting impressions from 13 May 2025 until 27 April 2026. Clicks were not affected, but impressions, click rate and position from before and after 27 April 2026 aren’t like for like.
Step 2: Compare equal windows, leaving out the rollout
Google’s guide says to note the update’s start and end dates and to wait “at least a full week after a core update completes” before analyzing. Its own example compares a week after with a week before the update started. Longer windows are steadier. Three rules make the comparison fair:
- Equal length, in whole weeks. 21 days against 21 days, so both windows have the same mix of weekdays and weekends.
- Nothing from the rollout. The before window ends the day before the update started; the after window starts the day after it finished.
- No other update or data issue inside either window.
For the May 2026 core update (21 May to 2 June), that gives a before window of 30 April to 20 May and an after window of 3 June to 23 June, three weeks each. The before window starts after the March update ended and after the impressions logging fix. In Search Console: Performance, Date, Compare, Custom, enter both ranges.
For the November 2026 update, wait until the dashboard shows the rollout as complete, then at least a week more, before drawing conclusions.
Step 3: Break it down by page type and search
A site-wide number hides the answer. Filter the comparison by page type (a regex on the Page filter, such as ^https://example.com/listing/) and look at the queries that lost the most. The pattern points to the cause:
| What you see | What it usually means |
|---|---|
| Every page type down by a similar share | Google reassessed the site as a whole. Look at overall quality and usefulness, not one template. |
| One page type down, the rest flat | Google reassessed that template: thin city pages, near-duplicate listings, a guide section built for search. |
| Position steady, impressions down | Fewer searches, or more of the page taken by other results. Check last year’s same weeks. |
| Position worse on the same searches | A real ranking loss. See who ranks above you now and what their page has that yours lacks. |
| Fewer searches showing you, average position better | Google stopped showing you for searches where you ranked low. Usually not worth chasing. |
| Business-name searches steady, category searches down | On a directory, Google re-ranked the list pages against other sources for “category in city” searches. |
Pages that lost traffic slowly before the update are a different problem: see content decay.
Step 4: What to change
Google’s guide splits drops in two. For a small drop in position there’s “no need to take drastic action”. For a large drop, “do a deeper assessment”: go through Google’s helpful content self-assessment for the site as a whole, and ask people who aren’t connected to the site to review it honestly. What that tends to mean in practice:
- Fix the template, not the page. If one page type dropped, change what every page of that type shows: more real information, less boilerplate.
- Deal with thin and empty pages. Empty category-in-city pages, name-and-phone listings and near-duplicate city text are the usual weak spots on directories. Index bloat and zombie pages covers deciding what to keep.
- Check for pages made for search first. Google’s guide says removing whole sections may help if they were built “for search engines first, and not people”. On directories that’s usually city pages with no businesses: see doorway pages and scaled content abuse.
- Leave alone what still works. Pages that held or gained aren’t the problem.
What not to do
- Don’t disavow links. Core updates aren’t about links. Google’s disavow tool help says to use it only when you have many spammy or artificial links that have caused, or likely will cause, a manual action.
- Don’t mass-delete pages. Google calls deleting content “a last resort”, for content that can’t be salvaged. Mass deletion also removes pages that were quietly earning.
- Avoid quick fixes. Google’s guide says to avoid “quick fix” changes, such as removing page elements because of a supposed SEO rule. Rewriting every title or changing every date shows nothing new.
- Don’t change URLs now. A migration in the middle of a recovery makes it impossible to tell which change did what. Migration checklist, for later.
- Don’t judge after two weeks. Rankings move during and just after a rollout.
How long recovery takes
Google is direct about it: there’s “no guarantee” that changes lead to noticeable improvements, and for site-wide changes “it could take several months for our systems to learn and confirm” them. Because Google also ships smaller core updates it doesn’t announce, you “don’t necessarily have to wait for a major core update”, but if nothing has moved after a few months, “that could mean waiting until the next core update.”
So measure early signals while you wait. Before visits come back, these usually move first: more of your pages shown in Google each week, the searches you used to rank for showing you again, a higher share of pages indexed, and fewer pages “Crawled - currently not indexed”.
Measuring recovery with DirectoryLens
The Recovery tracker (under Advanced) scores one date against the weeks before it. Pick the date from its suggestions (drops it found in your visits, your own annotations and Google updates) or type one in. It compares four weeks before the date, with the week of the date left out, against the latest four weeks after it:
- Visits from Google, times shown, and pages shown in Google per week.
- Times shown for searches you already ranked for before the date, and how many of those searches still show you.
- Estimated indexed share by page type, the share of “Crawled - currently not indexed”, and the share crawled in the last 30 days, from daily URL inspections. A change only counts when the 95% ranges before and after don’t overlap.
Google updates appear as shaded bands on its weekly chart, and Search Console data issues that touch only one of the two periods are flagged as not comparable. Score the update’s start date; once four weeks have passed since the rollout finished, the “now” period sits entirely after it. The Traffic drops report adds the page types and pages that lost visits, each labeled with the likely reason: ranking loss, demand drop, long tail pruned or lost from search. Both are signals, not a diagnosis.
You can try both on the sample directory in the live demo.