Christopher Abraham home
Christopher Abraham

SEO consultant: technical SEO, indexing, schema, and AI search

Hit by a 2026 Google update? A recovery checklist that works

Google confirmed two core updates and four spam updates between March and October 2026. When traffic falls in a year like that, the first instinct is to change everything at once. Resist it. Recovery starts with knowing which update, if any, actually touched you, and which pages took the loss. Here is the order I work in when a client calls with a graph that points down.

1. Line the drop up with the calendar

Open Google's Search Status Dashboard and note this year's ranking updates: a spam update on March 24, the March core update from March 27, the May core update from May 21, and spam updates starting June 24, August 18, and September 24. Then open Search Console, set the date range to sixteen months, and compare. A drop that begins within a few days of a rollout's start is a strong lead. A drop that began weeks before one, or on the day a redesign launched, points somewhere else.

2. Rule out the reporting quirks

3. Decide which kind of update it was

The two kinds behave differently. A core update re-ranks pages against each other; losses tend to spread across many queries and pages, often by moderate amounts. A spam update applies detection systems for policy violations; losses are usually steep, fast, and concentrated in the sections that triggered them. Also check Search Console's Manual actions report. Algorithmic hits stay off that report, so an empty report plus a cliff on a spam update date tells you an automated system made the call.

4. Find the pages that lost

In the Performance report, compare the two weeks after the update with the two weeks before, by page. Sort by lost clicks. Usually a minority of pages accounts for most of the loss, and they share something: the same template, the same author, the same type of content, or the same section of the site. That shared trait is the real finding.

5. Match the losers against the spam policies

Read Google's spam policies with that list of pages open. The ones that matter most this year:

If any of these describe the losing pages, remove or rewrite them before anything else. A policy problem outweighs every improvement elsewhere.

6. Fix in order of value

  1. Delete or consolidate thin and duplicate pages, redirecting any with links or traffic to the closest strong page.
  2. Rewrite the pages worth keeping with what only you can add: real examples, photos, numbers, procedures you follow, and the name of the person who knows the subject.
  3. Check access for every crawler you care about, Googlebot, Bingbot, and the AI search crawlers, at the robots.txt, CDN, and firewall levels.
  4. Make structured data honest: every claim in the markup should be visible on the page.

7. Set the right expectations

Google describes core updates as broad changes that don't target specific sites, and says it can take several months for its systems to confirm that improved content is helpful; if nothing moves after a few months, the next core update is the one to watch. Spam systems reassess too, after the problems are gone. Keep a dated change log so each later movement can be tied to a specific fix. Avoid the panic moves: buying links, mass-deleting pages that performed well, or rewriting the whole site in a week.

What I'd watch next

Expect another core update before the year ends, and more enforcement against manipulation of AI answers. Sites built on original work have done well through all of 2026; sites built on volume have struggled. For the AI side of visibility, see my AI search checklist, or send me the domain and the date your traffic changed.

Sources