Recovering from a Google demotion: what is documented and what is folklore

When Search traffic falls sharply, the first question is usually "how do I get it back?" The question that should come first is "what happened?" Google handles four different kinds of loss in four different ways. Each has its own evidence trail and its own recovery process, and the most common mistake is fixing the wrong one.

This article sorts the four apart, gives a decision table for diagnosis, sets out what Google says recovery takes, and grades the recovery advice that circulates among SEOs. It is a method. It does not promise any outcome, and nothing here suggests a recovery is guaranteed. Google says it isn't (official guidance, RD-02).

Every claim carries one of four labels: official guidance (a platform documenting its own rules), research finding, our observation, or hypothesis. The Google pages were checked on 2026-10-06. That day the Search Status Dashboard still listed no completion for the September 2026 spam update. Re-check the pages before you rely on this after early 2027.

Four ways to lose traffic

1. A manual action

A manual action means a human reviewer at Google has decided that pages on your site break Google's spam policies (official guidance, Manual actions report, RD-06). It is the only one of the four that Google tells you about directly. The notice appears in Search Console's Manual actions report and in the message center. The report lists the type of issue and the URL patterns affected. That can be one directory or "all pages", and not every URL matching a pattern is necessarily affected (RD-06).

The list of manual action types includes unnatural links to or from your site, thin content with little or no added value, cloaking and sneaky redirects, hidden text and keyword stuffing, user-generated spam, a "major spam problems" category that names scaled content abuse, and the site reputation policy (official guidance, RD-06). Site reputation actions now work differently inside and outside the European Economic Area. Outside the EEA the affected pages may get a manual action. Inside the EEA they may be ranked separately from the main domain with no manual action (official guidance, spam policies, M1-03).

Security problems such as malware or phishing go to a separate Security Issues report. They can bring warning labels in results or browser interstitials, which also cut traffic (official guidance, Security Issues report, RD-15).

2. An algorithmic spam demotion

Most spam is handled with no human involved. Google says it detects policy violations through automated systems and, as needed, human review, and that violating sites "may rank lower" or disappear from results (official guidance, spam policies, page dated 2026-08-28, AG-04). SpamBrain is the AI-based system Google names. When Google makes a notable improvement to these systems, it calls it a spam update and lists it (official guidance, spam updates, RD-04).

Google documents no notice for this kind of demotion. The Manual actions report only covers manual actions (RD-06). So an empty report means "no human action", not "no spam problem".

Link spam updates are a special case. Google says that when its systems remove the effect of spammy links, the ranking benefit those links gave is lost, and fixing things "might not" bring an improvement, because that benefit can't be regained (official guidance, RD-04; see also DA-09). The traffic those links propped up was never going to come back.

3. A core update shift

Core updates are broad changes to Google's ranking systems, made several times a year. Google says they don't target specific sites or pages (official guidance, core updates, page dated 2025-12-10, RD-01). Google's 2021 explainer adds that pages doing worse after a core update haven't broken any guidelines and haven't had a manual or algorithmic action against them (official guidance, How we update Search, 2021-06-02, RD-03). Google's own analogy is a refreshed "top 20" list. A site that moves down isn't necessarily bad; other pages may simply now answer better.

That distinction matters for recovery. A core update loss is not a penalty with a fix and a review. It is a reassessment, and the only route Google describes is making the site more helpful overall (RD-01, RD-02).

The "helpful content system" no longer exists separately. Google lists it as retired and part of core ranking since March 2024 (official guidance, M1-11). An "HCU penalty" is not a current Google concept. Google's ranking-systems guide says its systems work mostly at page level but also use site-wide signals and classifiers. Some good site-wide signals don't mean every page ranks well, and some poor ones don't mean every page ranks badly (official guidance, ranking systems guide, RD-13).

4. A technical, measurement or demand loss

Many "penalties" are nothing of the sort. Google's guide to traffic drops lists technical issues (server availability, robots.txt fetching, a stray noindex), security issues, site moves, seasonality and changing interest, and Search Console data anomalies (logging errors) alongside algorithm updates and spam (official guidance, debugging traffic drops, RD-09). It notes that a misplaced noindex produces a slower drop than a site outage, because the loss only shows as Google recrawls each page. A site move can cause fluctuations for a few weeks on a medium-sized site, and longer on large ones (RD-09; our migrations article covers that case).

Google also demotes sites that receive a significant volume of valid legal removal requests (copyright, defamation, counterfeit goods, court orders) or personal-information removals involving exploitative practices (official guidance, spam policies, "Other practices that can lead to demotion or removal", RD-05). These are rare for SaaS sites, but they are documented.

How Google announces updates

The Google Search Status Dashboard lists ranking updates that Google considers relevant to site owners. Each entry has a start date and a duration once it finishes. History is kept for five years, and there's an RSS feed (official guidance, dashboard help, RD-11). Google says that when an update is listed, "often" no action is needed (RD-11).

The dashboard does not list everything. Google says it makes smaller core updates that aren't announced because they aren't widely noticeable (official guidance, RD-02). Its 2021 explainer says it ships dozens of incremental changes in a typical week (official guidance, RD-03). So a drop on a date with no announcement doesn't rule out a ranking change. A drop that lines up with an announcement doesn't prove the update caused it either.

Recent entries, as listed on 2026-10-06 (official guidance, RD-10):

Update	Started	Listed duration
September 2026 spam update	2026-09-24	still active on 2026-10-06; Google said up to two weeks
August 2026 spam update	2026-08-18	2 days, 16 hours
June 2026 spam update	2026-06-24	2 days, 1 hour
May 2026 core update	2026-05-21	11 days, 21 hours
March 2026 core update	2026-03-27	12 days, 4 hours
March 2026 spam update	2026-03-24	19 hours, 30 minutes
December 2025 core update	2025-12-11	18 days, 2 hours
August 2025 spam update	2025-08-26	26 days, 15 hours
June 2025 core update	2025-06-30	16 days, 18 hours
March 2025 core update	2025-03-13	13 days, 21 hours

Rollout lengths vary from under a day to several weeks. The last update labeled "helpful content" on the dashboard is from September 2023.

A diagnosis decision table

Work through the rows in order. The earlier ones are cheaper to check and easier to rule out (our method, hypothesis; each check relies on the documented report named).

Check	What you see	Most likely cause	Next step
Search Console Data anomalies page and the drop's date	A known logging issue covers your dates	Measurement, not traffic	Confirm with server logs or analytics; don't change the site
Security Issues report	An issue is listed	Hacked content, malware, phishing	Fix, then request a security review (RD-15)
Manual actions report	An action is listed	Manual action	Read the type and patterns; fix every affected page; reconsideration request (RD-06)
Page indexing and Crawl stats reports, URL Inspection	A spike in errors, noindex, robots.txt or server failures	Technical loss	Fix the cause; pages return as they're recrawled (RD-09)
Recent site move, redirect or URL change	Drop starts at launch	Migration	Check the redirect map against Google's common mistakes (MG-01)
Performance report, last 16 months; Google Trends for top queries	The same dip a year earlier, or queries falling across the web	Seasonality or demand	No site fix; adjust plans and forecasts (RD-09)
Clicks fell but impressions held	Fewer clicks per impression	Title, snippet or SERP layout change, AI features	Review titles and snippets; check the Generative AI report (RD-09, M1-17)
Drop starts during a listed spam update	Losses fit a pattern you recognize from the spam policies	Algorithmic spam demotion (likely, not proven)	Audit against the named policies; stop the practice; wait (RD-04)
Drop starts during a listed core update, after rollout is complete	Large position losses across many queries	Core update reassessment (likely, not proven)	Site-wide self-assessment; improve, don't patch (RD-01)
None of the above	A gradual loss with no clear date	Competition, content aging, unannounced changes	Page-group analysis against a control set

Two warnings for the last three rows. First, a matching date is a correlation. Google's own guidance frames core updates as something a traffic change "correlates with", not something you can confirm (RD-01). Second, a site can have more than one problem at once. A spam demotion and a core update drop can overlap, and so can a technical fault and either of them.

How Google says to read a core update in Search Console (official guidance, RD-01, RD-09):

1. Wait until the dashboard shows the update has finished, then wait at least another full week.
2. Compare a week after the update with a week before it started.
3. Look at your top pages and queries. A small drop, such as position 2 to 4, needs no drastic action. Google recommends not changing content that's already performing well. A large drop, such as position 4 to 29, calls for a deeper assessment.
4. Check search types (Web, Images, Video, News) separately.
5. Sort pages by clicks lost to see whether the loss is site-wide, a section, or one important page.

What Google says recovery requires

Manual action: fix everything, then ask

This is the only path with a defined process (official guidance, RD-06):

• Fix the issue on every affected page. Google says a partial fix will not earn a partial return. If there are several actions, fix all of them.
• Make the pages reachable. Affected pages should not need a login, sit behind a paywall, or be blocked by robots.txt or noindex.
• Write a reconsideration request that explains the exact issue, describes what you did, and documents the result. For "major spam problems", Google asks for examples of bad content removed and good content added.
• Timing. Google says most reviews take "several days or weeks". Link-related requests can take longer. Don't resubmit while a request is pending.
• For unnatural links, make a good-faith effort to remove links first. Google says that disavowing every backlink without trying to remove any "might lead to rejection" (RD-06).
• If you bought the site, fix the issues and say in the request that you recently acquired it (RD-06, RD-14).

Revoking a manual action removes the action. It doesn't restore the traffic that bad links or thin pages once brought. Nothing Google publishes promises a return to earlier positions (RD-04, RD-02).

Algorithmic spam demotion: comply and wait

There is no request to file. Google says sites that see a change after a spam update should review the spam policies, and that changes "may help" if its automated systems "learn over a period of months" that the site complies (official guidance, RD-04). Google gives no fixed period. "Months" is the only time word it uses.

Core update: improve the site as a whole, without quick fixes

Google's guidance (official guidance, RD-01):

• Self-assess the whole site, not just the pages that fell, using the people-first questions. Ask someone unaffiliated with the site to do the same (see M1-09).
• Study the pages that lost the most, and the pages that now rank above them.
• Avoid quick fixes, such as removing an element because you heard it was bad for SEO.
• Improve content meaningfully. Rewriting or restructuring for readers is the example Google gives.
• Delete as a last resort. Google says deletion is only for content that can't be saved. It adds that if you're thinking of deleting whole sections, those sections were probably made for search engines first, and removing them may help your good content perform better.

Timing, in Google's words (official guidance, RD-02): some changes take effect in a few days. It could take "several months" for Google's systems to confirm that the site as a whole now produces helpful content. If a few months pass with no effect, that "could mean waiting until the next core update", although smaller, unannounced core updates can also lift a site. Google adds that there's no guarantee of noticeable impact, because results change constantly. That is the full extent of Google's documented recovery timeline. Any figure more precise than this comes from someone else.

Pruning or rewriting? Google ranks rewriting and restructuring above deletion (RD-01). In practice, our approach is this (hypothesis). Rewrite pages that answer a real query your buyers have but answer it poorly. Merge near-duplicates into one stronger page. Remove, or noindex, pages that exist only to rank and that no buyer would miss. Record which pages got which treatment, so you can later compare each group against pages you didn't touch.

Disavow: rarely

Google's disavow help page says most sites won't need the tool, and that it can harm performance if used wrongly. Google suggests disavowing only when you have a considerable number of spammy, artificial or low-quality links and they have caused, or likely will cause, a manual action (official guidance, disavow links, RD-12). Remove links at the source first. A new disavow file takes "a few weeks" to be processed, and it applies per property (RD-12). Disavowing links on the strength of a third-party "toxicity" score has no basis in Google's documentation (RD-12; see also our DA, DR and Trust Flow article).

The circumvention trap: new domains, subdomains and redirects

One piece of advice comes up whenever a site is hit: move the content (or the whole business) to a fresh domain, redirect selectively, and start clean. Some practitioners argue that this protects the brand. Google's documents point the other way.

The policy. Google's spam policies include a "Policy circumvention" section. If a site keeps trying to bypass the spam policies, Google may restrict features such as Top Stories and Discover and take broader action in Search, including removing more sections of the site. Its examples of circumvention include using existing or new subdomains, subdirectories or sites to keep violating the policies, and any other method of continuing the same behavior (official guidance, spam policies, RD-05).

The one documented case of moving content. For the site reputation policy, Google spells out what moving content does (official guidance, RD-07, RD-08):

• Moving the content into a subdirectory or subdomain of the same site doesn't resolve the issue, and Google says it may be seen as circumvention, with broader action as a possible result.
• Moving it to another established site can pass the problem on to that site, if it has its own reputation and the content is still third-party in nature.
• Moving it to a new domain with no established reputation is "far less likely" to be a problem, as long as the new site follows the spam policies.
• Don't redirect the old URLs to the new location, because that may bring the issue back. If you link from the old site, add nofollow.
• You still need to file a reconsideration request for the original action.
• Within the EEA, not taking these steps is not treated as circumvention in itself (RD-07).

Note what this does and does not allow. Google accepts relocating third-party content that broke a host-specific policy, without redirects, to a domain that follows the rules. It does not describe moving a demoted site to a new domain with redirects as a way to recover. And it says a new site used to keep violating the policies is circumvention.

Why redirects can't be a clean escape. Google says ranking signals such as PageRank and incoming links pass appropriately across 301 redirects (official guidance, crawling and indexing FAQ, RD-14; see also MG-01). Its Change of Address tool forwards signals from the old site to the new one for 180 days (official guidance, MG-07). A redirect exists to carry the old site's history across. Whether an algorithmic demotion travels with a redirect, Google does not say in any document we found (RD-19). If you can't keep the problem from following you, the move just costs you a migration.

What the documents do support. Fix the problem where it is. If you bought a domain with a spammy past, check its Manual actions report before you move anything onto it, and file a reconsideration request explaining the change of ownership if needed (official guidance, site moves, RD-16; RD-14). Better still, check a domain's history before you buy it: our domain pre-purchase checklist covers the free checks.

Documented versus folklore

Claim you'll hear	Status	What the sources say
"A core update means you did something wrong."	Contradicted by official guidance	Pages that lose in a core update haven't violated guidelines or had a manual or algorithmic action (RD-03).
"You'll get a notice if Google penalized you."	Only true for manual actions	Manual and site reputation actions are notified in Search Console (RD-06, M1-03). Google documents no notice for algorithmic spam demotions or core updates (RD-04, RD-06).
"Recovery has to wait for the next core update."	Partly documented	Some changes show in days; it can take several months; if months pass, it "could mean" waiting for the next core update; smaller unannounced updates can also help (RD-02).
"Recovery takes one to three years and gets back about a third of the traffic."	Hypothesis (contested)	Some practitioners describe long, partial recoveries; others report full rebounds. No primary dataset found. Google publishes no rate or timeline beyond RD-02 (RD-18).
"Delete all your thin content to recover."	Overstated	Google calls deletion a last resort, after rewriting or restructuring; deleting content made for search engines may help (RD-01).
"Disavow your toxic links on day one."	Contradicted by official guidance	Disavow only for a considerable volume of bad links tied to a real or likely manual action; misuse can harm you (RD-12).
"Fix a few pages and request review to get part of the traffic back."	Contradicted by official guidance	Fixing only some pages will not earn a partial return (RD-06).
"Move to a new domain and redirect; the penalty stays behind."	Red flag: circumvention	Circumvention via new sites, subdomains or subdirectories may bring broader action (RD-05). Google advises against redirects even in the one documented content move (RD-07, RD-08). Signals pass through 301s (RD-14).
"A penalty on one site spreads to every site in the same Search Console account or with the same owner."	Hypothesis (unverified)	Mostly anecdote among practitioners; Google has published nothing either way that we found (RD-17). Don't plan around it, and don't rely on its absence to run a risky site next to your main one.
"Manual actions are basically gone; it's all algorithms now."	Contested; manual actions still documented	Google's current help page lists manual action types, including site reputation and "major spam problems" (RD-06). It says most spam is caught automatically (RD-06).
"Publishing too fast triggers a spam filter."	Hypothesis	Google publishes no velocity threshold. Scaled content abuse is defined by purpose and value, not pace (M1-02, M1-23).
"The HCU penalty is still on your site."	Outdated	The helpful content system was folded into core ranking in March 2024 (M1-11).
"Update your dates so Google sees the site as fresh."	Contradicted by official guidance	Google lists changing dates without substantial changes as a warning sign (M1-09).
"No announcement, so it can't be an update."	Contradicted by official guidance	Smaller core updates aren't announced; incremental changes ship weekly (RD-02, RD-03).

Measuring a recovery without fooling yourself

A recovery story told from before-and-after numbers alone is weak evidence. Rankings move with every update, season and competitor launch. If traffic comes back after your fix, the fix may or may not be why (our method, hypothesis).

1. Freeze a baseline. Export 16 months of Performance data by page and query before you change anything (Google's drops guide suggests the 16-month view; the API or bulk export keeps longer history, RD-09).
2. Group pages by treatment. Rewritten, merged, removed, untouched. Keep the untouched group as a rough control.
3. Log every change with its date, next to each listed Google update (RD-10).
4. Compare like with like. Equal-length windows, the same search type, a week after any rollout completes (RD-01).
5. Track business outcomes separately: qualified signups, activation and retention by organic landing page. Recovered clicks that don't convert aren't a recovery.
6. Report what you saw as an observation. "Rewritten pages regained more clicks than untouched pages after the May 2026 core update" is an observation. "Rewriting caused the recovery" is a claim one site can't support.

Checklist

Diagnose:

• Data anomalies page checked for the drop dates.
• Security Issues and Manual actions reports checked.
• Page indexing, Crawl stats and URL Inspection checked for technical faults.
• Recent migrations, redirects and releases ruled in or out.
• 16-month view and Google Trends checked for seasonality.
• Drop dates lined up against the Status Dashboard, with rollouts complete plus a week.
• Losses mapped: site-wide, a section, or a few pages.

Recover:

• Manual action: every affected page fixed, pages crawlable, reconsideration request explains the issue, the fix and the evidence.
• Spam demotion: the practice stopped everywhere, including on other domains and subdomains.
• Core update: whole-site self-assessment, ideally by someone outside the team; rewrite before deleting.
• Disavow only for a real or likely link-based manual action.
• No domain hops, subdomain moves or redirects meant to escape a demotion.

Measure:

• Baseline exported before changes.
• Treatment groups and an untouched control set.
• Change log dated against update rollouts.
• Business outcomes reported separately from clicks.

If you'd like a second pair of eyes on a traffic drop, RankPropel's audit and baseline sprint includes the diagnosis steps above and a measurement baseline. The method works the same if you do it yourself.

Sources

Google Search Central: core updates and your website (page dated 2025-12-10), spam updates, spam policies (including "Site reputation policy" and "Policy circumvention"; page dated 2026-08-28), debugging drops in Search traffic, ranking systems guide, using the Search Status Dashboard, crawling and indexing FAQ, site moves with URL changes (page dated 2026-08-20), creating helpful, people-first content, Updating our site reputation abuse policy (blog, 2024-11-19). Google Search Status Dashboard, Ranking history. Google, How we update Search to improve your results (2021-06-02). Search Console Help: Manual actions report, Security Issues report, disavow links, Change of Address tool. All retrieved 2026-10-06.