Recovering From a Google Core or Spam Update
To recover from a Google update, first confirm that the update caused the drop, then work out which kind of update it was, because the fix differs. A core update reassesses content quality across the site and has no single fix. A spam update or manual action points at a specific policy violation that you must remove. Recovery is possible in all three cases, and it is rarely quick.
- Match the date of your drop to Google's Search Status Dashboard before blaming an update.
- Core update: nothing is broken. Google now rates other pages higher. The work is improving content, often over months.
- Spam update or manual action: find the violation, remove it fully, and for manual actions file a reconsideration request.
- Do not make panicked sitewide changes during a rollout. Wait until it finishes, then diagnose by page and by query.
First, confirm it was an update
Check the date. Google lists confirmed ranking updates, with start and end dates, on its Search Status Dashboard (status.search.google.com/summary). If your drop began inside a rollout window, an update is a likely cause. If it began two weeks earlier, look elsewhere.
Rule out the ordinary causes before you go further. Many drops blamed on updates turn out to be one of these.
- Tracking broke: a tag was removed, a consent banner changed, or analytics was reconfigured. Compare analytics with Search Console clicks. If Search Console is steady, your tracking is the problem.
- A site change: a redesign, new URLs without redirects, a noindex tag, a robots.txt edit, or a canonical change.
- Seasonality: compare with the same weeks last year, not with last month.
- Fewer clicks, same rankings: AI answers and other search features can lower click-through while impressions and position hold. That is not a penalty.
- One big page or one big query lost ground to a new competitor.
In Search Console, compare the two weeks after the rollout finished with the two weeks before it started. Wait for the rollout to end, since positions move during it. A quick technical pass with our free audit tool will catch a stray noindex or a broken canonical on a key page.
Core update, spam update or manual action?
These are three different events. Only one of them sends you a message.
| Core update | Spam update | Manual action | |
|---|---|---|---|
| What it is | A broad change to how Google's systems assess content | An improvement to automated spam detection | A human reviewer at Google found a policy violation |
| Are you notified? | No | No | Yes, in the Manual actions report in Search Console |
| Typical pattern | Gradual or stepped change across many pages and queries | Sharp drop, often for specific sections or page types | Sharp drop or removal for affected pages or the whole site |
| What fixes it | Better, more useful content. No specific fix exists | Removing the practice that breaks the spam policies | Removing the violation and filing a reconsideration request |
| Recovery timing | Often months. Sometimes not until a later core update | Can take months, as automated systems relearn the site | After Google reviews the request, which can take days to weeks |
Always open the Manual actions and Security issues reports first. If both are clear, you are dealing with an algorithmic change.
Recovering from a core update
Google's guidance is direct: pages that drop after a core update have not broken a rule, and there may be nothing to fix. Other pages are now judged more helpful. The route back is to make your pages the better answer, then wait for the systems to reassess.
- Find what dropped. In Search Console, compare before and after by page, then by query. Note whether the loss is sitewide or concentrated in one section or one type of search.
- Look at what replaced you. Search the affected queries and read the winners. Are they more specific, more current, written from first-hand experience, or better at answering quickly?
- Assess your pages honestly against Google's self-assessment questions for helpful, reliable, people-first content (developers.google.com/search/docs/fundamentals/c…).
- Improve the pages worth keeping: add original detail, first-hand evidence, clear authorship, current facts and a direct answer near the top.
- Deal with the weak pages. Merge overlapping pages, and remove or noindex pages that exist only to catch searches. Do not delete pages simply because they are old.
- Fix experience problems that get in the reader's way: intrusive ads, slow templates, content hidden behind interactions.
- Give it time. Google says improvements can be recognised in days or may take several months, and that the largest changes may only show after another core update.
Here is a worked example. An online retailer loses a third of its non-branded clicks during a core update. The page-level comparison shows product pages are steady. The loss is almost entirely in 140 short blog posts written to target search phrases, many of them overlapping. The plan: merge them into about 25 thorough guides, redirect the old URLs, add real product testing notes and photos, and stop publishing posts that exist only for a keyword. That is months of work, and it is the honest answer.
This is content work more than technical work. Our content strategy page describes how we decide what to keep, merge and rewrite.
Recovering from a spam update or manual action
Here there is something specific to remove. Read Google's spam policies and compare them with what has been done on your site, including by past agencies. Be honest with yourself at this step, because partial clean-ups tend to fail.
| Common cause | What it looks like | The clean-up |
|---|---|---|
| Scaled content abuse | Many pages produced mainly to rank, with little original value, however they were written | Remove or substantially rewrite. Noindex is a stopgap, not a fix |
| Doorway pages | Near-identical pages for every city or variation, funnelling to one offer | Consolidate into pages that are useful on their own |
| Link spam | Bought links, link exchanges at scale, paid guest posts with followed links | Ask for removal or nofollow where you can. Disavow the rest if you have a manual action or clear evidence of harm |
| Site reputation abuse | Third-party content hosted on your site to trade on its ranking strength | Remove it or block it from indexing |
| Expired domain abuse | An old domain bought for its links and filled with unrelated content | Usually not recoverable. Build on a domain with an honest history |
| Hacked content | Pages or links you did not create | Fix the security hole, remove injected content, check the Security issues report |
For a manual action, the report names the issue and gives example URLs. Fix the whole pattern, not only the examples. Then file a reconsideration request that says what happened, what you removed and how you will prevent it. Short, factual and documented works best.
For an algorithmic spam hit there is no request to file. Google says sites that change may see improvement over a period of months as automated systems learn that the site now complies. If a past agency built links you cannot explain, our link building and digital PR page describes the kind of links that do not create this risk.
What not to do
- Do not make large changes while the update is still rolling out.
- Do not delete content in bulk by age or word count. Judge pages by usefulness.
- Do not change every URL, title and template at once. You will not know what helped.
- Do not switch domains to escape. Problems tend to follow the content, and redirects carry signals across.
- Do not disavow links on the strength of a third-party toxicity score alone.
- Do not pay for a guaranteed recovery. Nobody outside Google can promise one.
- Do not add an author box and an updated date and call it done. Surface changes without better content do not address the cause.
A realistic recovery plan
| When | Work |
|---|---|
| Week 1 | Confirm dates, rule out tracking and site changes, check manual actions and security issues |
| Weeks 2 to 3 | Page and query comparison, review of what now ranks, list of pages to improve, merge or remove |
| Months 1 to 3 | Do the content and clean-up work in priority order, starting with pages closest to revenue |
| Ongoing | Track non-branded clicks by section. Review again after the next confirmed core update |
If you work with an agency, this is a fair moment to review them as well. Our guide on whether your SEO agency is working gives the checks. A drop caused by tactics they chose, such as bought links or mass-produced pages, is a different conversation from a drop that hit a well-run site.
If you want an outside diagnosis, a one-time full audit with a 90-day plan is listed on our pricing page, and you can book a strategy call first. We will tell you what we think happened and whether recovery work is worth funding. We cannot promise a return to previous rankings, and neither can anyone else.
Questions
How long does it take to recover from a core update?
Google says some improvements can take effect within days, while others take several months, and the biggest changes may only appear after a later core update. Core updates are released several times a year. Plan for a quarter or more of steady work.
Can a site recover fully?
Some do, some recover partly and some do not. Google notes that improvements do not guarantee recovery, because rankings are relative to other pages. The work still makes the site better for the visitors you have.
Did Google penalise my site?
Only a manual action is a penalty in the strict sense, and you would see it in Search Console. A core update drop is a reassessment, not a punishment.
Should I remove all AI-written content?
Google's policies target content made mainly to manipulate rankings with little value, however it was produced. Judge each page on whether it helps a reader and adds something original. Remove or rewrite the ones that do not.
Is the disavow tool still worth using?
For most sites, no. Google ignores most spam links automatically. Use it when you have a manual action for unnatural links, or when you know links were bought and cannot be removed.