Post-Core-Update Recovery
Overview
A specific recovery framework for domains that lost visibility after a Google Core Update. Core insight from real March/April 2026 recovery cases: Authority items > technical hygiene. Recovery 6–12 months, not 6–8 weeks.
When to use
- VI drop correlates timely with a published Core Update (see Google Search Status Dashboard)
- Drop is broad (many keywords simultaneously, not pinpoint)
- Pages keep indexing normally, no technical break
- GSC shows no manual action
- Pattern: 1–6 weeks of decline, then bottoming out
Don't use for:
- Point keyword losses → usually on-page issue, not core update
- Drop coincides with migration / theme change / robots change → that's technical, not core
- Drop is <20 % from peak → can be normal market noise
Diagnosis decision tree
digraph diag {
"Visibility dropped?" [shape=diamond];
"Correlates with Core Update date?" [shape=diamond];
"Brand keywords also dropped?" [shape=diamond];
"Manual action in GSC?" [shape=diamond];
"CWV suddenly red?" [shape=diamond];
"Apply Recovery (this skill)" [shape=box,style=filled,fillcolor=lightblue];
"Technical problem first" [shape=box,style=filled,fillcolor=lightyellow];
"Penalty workflow, not here" [shape=box,style=filled,fillcolor=lightcoral];
"Performance-first workflow" [shape=box,style=filled,fillcolor=lightyellow];
"Market noise, observe" [shape=box];
"Visibility dropped?" -> "Correlates with Core Update date?" [label="yes"];
"Correlates with Core Update date?" -> "Manual action in GSC?" [label="yes"];
"Manual action in GSC?" -> "Penalty workflow, not here" [label="yes"];
"Manual action in GSC?" -> "Brand keywords also dropped?" [label="no"];
"Brand keywords also dropped?" -> "Technical problem first" [label="yes"];
"Brand keywords also dropped?" -> "CWV suddenly red?" [label="no"];
"CWV suddenly red?" -> "Performance-first workflow" [label="yes"];
"CWV suddenly red?" -> "Apply Recovery (this skill)" [label="no"];
"Correlates with Core Update date?" -> "Market noise, observe" [label="no"];
}
If brand keywords are intact and CWV is stable but generic keywords are broadly lost → this is the core signature of a Core Update hit.
Required diagnostic steps (day 1)
- Document the Core Update date — see https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history. Match Sistrix drop date exactly.
- Measure the Sistrix drop diff — monthly values 12 months before vs 1–3 months after the update.
- DataForSEO ranked-keywords diff — compare top positions pre vs post update. Specific URL clusters affected or distributed uniformly?
- GSC click diff — which URLs lost most traffic? Pattern visible (all blog posts? all product pages? all YMYL topics?)
- EEAT audit of lost top URLs — author visible? Sources cited? Last-updated stamp? Trust layer (About, Imprint, Reviews)?
Recovery plan (3 phases × 6–12 months)
Phase A — Authority foundation (months 1–2)
What Google especially scrutinizes in Core Updates:
- Author authority — Person behind the content, qualifications visible
- Topical authority — Site covers the topic in depth AND breadth, not just isolated pages
- Trust signals — About, Imprint, Reviews, Sources, Date stamps
- Original insight — Own data, own perspective rather than "I read elsewhere"
Concrete steps:
- Rebuild every author page: photo, bio with qualifications, list of articles, social profiles (LinkedIn/X),
Person schema
- Edit each affected top URL: author visible (+schema),
dateModified, sources with outbound links, update notes
- Strengthen About/Imprint pages: team intro, company history, location, contact — mandatory trust signals
- Sitewide: reviews/testimonials visible above the fold (manage on original platforms, NOT mirror sites)
Phase B — Topical authority hubs (months 2–4)
Goal: transform a collection of scattered pages into coherent topic hubs.
- Identify main topics (3–7 for e-commerce, 5–15 for news/publishers)
- Per topic: 1 pillar page (1500–3000 words, comprehensive) + 5–15 sub-pages (600–1500 words each, specific)
- Internal linking: sub-pages link to pillar, pillar links to all subs ("hub-and-spoke")
- If available: use
claude-seo:seo-cluster for data-driven topic identification
Phase C — Off-page authority (months 4–8)
Backlinks deliberately, not at scale:
- Manufacturer/supplier partnerships for links
- Industry communities (e-commerce: camper forums, boating blogs; news: investigations, exclusive stories)
- Local press (regional anchor, PR opportunities)
- Original studies/data — generates organic links better than anything else
What NOT to do:
- Link-building services with "100 links for €500" → leads to spam score, recovery even harder
- Reciprocal links at scale
- PBN backlinks
- Forum spam
Phase D — Technical hygiene (in parallel, lowest priority)
Only after A–C are running:
- PSI optimization (LCP, INP, CLS)
- Schema markup completeness
- Image alt texts, sitemap hygiene
These are NOT the recovery lever — Core Updates don't penalize tech, they penalize trust/authority. But technical hygiene supports the other levers.
Realistic expectations
- Visible movement typically starts only after 3–4 months in the recovery case we observed and in the public Core-Update-recovery cases referenced in
LESSONS.md. Google needs time to re-evaluate authority signals.
- Full recovery usually takes 9–18 months in the cases referenced. We are not aware of significantly faster recoveries published; if you find one, please contribute the observation back to
LESSONS.md.
- Recovery outcome in observed cases is in the 50–80 % range of pre-drop visibility. Full recovery to 100 % seems to require structural changes (new content lines, new authority sources), not just optimization of what existed before. These percentages are observations from a small case-base, not population statistics — treat them as input hypotheses, not predictions.
- Pattern: recovery comes in jumps, often timed with the next Core Update rather than gradually.
Owner communication
Don't say:
- "It'll be back to normal in 6 weeks"
- "We know the trick to fix this"
- "Sistrix score will double in 4 weeks"
Do say:
- "We measure monthly. First positive movement expected in 3–4 months."
- "This is an authority problem, not a technical problem. Fixing it takes time."
- "We're building the substance Google looks for — not the trick."
Common rationalization traps
| Statement |
Reality |
| "Let's buy 200 backlinks" |
Raises spam score, makes recovery harder |
| "Let's do a relaunch" |
More risk than upside — substance first, then form |
| "Better PSI will bring us back" |
PSI is hygiene, not the core update lever |
| "More pages = more traffic" |
False — thin content weakens authority further |
| "We did everything right" |
In a Core Update Google changes the scoring. Being "right" doesn't help. |
Related skills
- claude-seo:seo-audit — for the technical hygiene layer in Phase D
- claude-seo:seo-cluster — for topical-authority-hub identification
- seo-outreach-report — when the owner needs a printable status report
Real data points (anonymized 2026 cases)
- March/April 2026 update: mid-size DE shop lost 50 % VI in 4 weeks
- Diagnosis pattern confirmed: brand keywords stable, generic keywords broadly lost, CWV unchanged
- Recovery plan: 6–12 months, Authority-First. Tech (PSI/Schema) in parallel but not the primary lever.
- Lesson (Sistrix wording on March update): "Authority beats interchangeability"
A second real case (DE news site) showed the same pattern in April/May 2026: −60 % VI in 6 weeks, brand stability intact — news/YMYL variant of the same algo recalibration.
1---2name: post-core-update-recovery3description: Use when a website experienced a sudden visibility/ranking drop that correlates with a published Google Core Update — symptoms include broad ranking loss across many keywords in a short window (1–6 weeks), Sistrix VI dropping 30 %+ from peak, sales/leads falling despite no technical changes, the owner saying "we used to rank, now we don't" but pages still load and index normally. Distinguishes Core-Update damage from CWV/technical drops and produces a phased 6–12 month recovery plan focused on Authority and EEAT.4license: MIT5---6
7# Post-Core-Update Recovery
8
9## Overview
10
11A specific recovery framework for domains that **lost visibility after a Google Core Update**. Core insight from real March/April 2026 recovery cases: *Authority items > technical hygiene*. Recovery 6–12 months, not 6–8 weeks.
12
13## When to use
14
15- VI drop correlates timely with a published Core Update (see Google Search Status Dashboard)
16- Drop is **broad** (many keywords simultaneously, not pinpoint)
17- Pages keep indexing normally, no technical break
18- GSC shows no manual action
19- Pattern: 1–6 weeks of decline, then bottoming out
20
21**Don't use for:**
22- Point keyword losses → usually on-page issue, not core update
23- Drop coincides with migration / theme change / robots change → that's technical, not core
24- Drop is <20 % from peak → can be normal market noise
25
26## Diagnosis decision tree
27
28```dot
29digraph diag {
30 "Visibility dropped?" [shape=diamond];
31 "Correlates with Core Update date?" [shape=diamond];
32 "Brand keywords also dropped?" [shape=diamond];
33 "Manual action in GSC?" [shape=diamond];
34 "CWV suddenly red?" [shape=diamond];
35 "Apply Recovery (this skill)" [shape=box,style=filled,fillcolor=lightblue];
36 "Technical problem first" [shape=box,style=filled,fillcolor=lightyellow];
37 "Penalty workflow, not here" [shape=box,style=filled,fillcolor=lightcoral];
38 "Performance-first workflow" [shape=box,style=filled,fillcolor=lightyellow];
39 "Market noise, observe" [shape=box];
40
41 "Visibility dropped?" -> "Correlates with Core Update date?" [label="yes"];
42 "Correlates with Core Update date?" -> "Manual action in GSC?" [label="yes"];
43 "Manual action in GSC?" -> "Penalty workflow, not here" [label="yes"];
44 "Manual action in GSC?" -> "Brand keywords also dropped?" [label="no"];
45 "Brand keywords also dropped?" -> "Technical problem first" [label="yes"];
46 "Brand keywords also dropped?" -> "CWV suddenly red?" [label="no"];
47 "CWV suddenly red?" -> "Performance-first workflow" [label="yes"];
48 "CWV suddenly red?" -> "Apply Recovery (this skill)" [label="no"];
49 "Correlates with Core Update date?" -> "Market noise, observe" [label="no"];
50}
51```
52
53If brand keywords are intact and CWV is stable but generic keywords are broadly lost → this is the core signature of a Core Update hit.
54
55## Required diagnostic steps (day 1)
56
571. **Document the Core Update date** — see https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history. Match Sistrix drop date exactly.
582. **Measure the Sistrix drop diff** — monthly values 12 months before vs 1–3 months after the update.
593. **DataForSEO ranked-keywords diff** — compare top positions pre vs post update. Specific URL clusters affected or distributed uniformly?
604. **GSC click diff** — which URLs lost most traffic? Pattern visible (all blog posts? all product pages? all YMYL topics?)
615. **EEAT audit of lost top URLs** — author visible? Sources cited? Last-updated stamp? Trust layer (About, Imprint, Reviews)?
62
63## Recovery plan (3 phases × 6–12 months)
64
65### Phase A — Authority foundation (months 1–2)
66
67**What Google especially scrutinizes in Core Updates:**
68- **Author authority** — Person behind the content, qualifications visible
69- **Topical authority** — Site covers the topic in depth AND breadth, not just isolated pages
70- **Trust signals** — About, Imprint, Reviews, Sources, Date stamps
71- **Original insight** — Own data, own perspective rather than "I read elsewhere"
72
73**Concrete steps:**
741. Rebuild every author page: photo, bio with qualifications, list of articles, social profiles (LinkedIn/X), `Person` schema
752. Edit each affected top URL: author visible (+schema), `dateModified`, sources with outbound links, update notes
763. Strengthen About/Imprint pages: team intro, company history, location, contact — mandatory trust signals
774. Sitewide: reviews/testimonials visible above the fold (manage on original platforms, NOT mirror sites)
78
79### Phase B — Topical authority hubs (months 2–4)
80
81**Goal:** transform a collection of scattered pages into coherent topic hubs.
82
831. Identify main topics (3–7 for e-commerce, 5–15 for news/publishers)
842. Per topic: 1 pillar page (1500–3000 words, comprehensive) + 5–15 sub-pages (600–1500 words each, specific)
853. Internal linking: sub-pages link to pillar, pillar links to all subs ("hub-and-spoke")
864. If available: use `claude-seo:seo-cluster` for data-driven topic identification
87
88### Phase C — Off-page authority (months 4–8)
89
90**Backlinks deliberately, not at scale:**
911. Manufacturer/supplier partnerships for links
922. Industry communities (e-commerce: camper forums, boating blogs; news: investigations, exclusive stories)
933. Local press (regional anchor, PR opportunities)
944. Original studies/data — generates organic links better than anything else
95
96**What NOT to do:**
97- Link-building services with "100 links for €500" → leads to spam score, recovery even harder
98- Reciprocal links at scale
99- PBN backlinks
100- Forum spam
101
102### Phase D — Technical hygiene (in parallel, lowest priority)
103
104Only after A–C are running:
105- PSI optimization (LCP, INP, CLS)
106- Schema markup completeness
107- Image alt texts, sitemap hygiene
108
109These are **NOT** the recovery lever — Core Updates don't penalize tech, they penalize trust/authority. But technical hygiene supports the other levers.
110
111## Realistic expectations
112
113- **Visible movement typically starts only after 3–4 months** in the recovery case we observed and in the public Core-Update-recovery cases referenced in `LESSONS.md`. Google needs time to re-evaluate authority signals.
114- **Full recovery usually takes 9–18 months** in the cases referenced. We are not aware of significantly faster recoveries published; if you find one, please contribute the observation back to `LESSONS.md`.
115- **Recovery outcome in observed cases is in the 50–80 % range** of pre-drop visibility. Full recovery to 100 % seems to require structural changes (new content lines, new authority sources), not just optimization of what existed before. These percentages are observations from a small case-base, not population statistics — treat them as input hypotheses, not predictions.
116- **Pattern: recovery comes in jumps**, often timed with the next Core Update rather than gradually.
117
118## Owner communication
119
120**Don't say:**
121- "It'll be back to normal in 6 weeks"
122- "We know the trick to fix this"
123- "Sistrix score will double in 4 weeks"
124
125**Do say:**
126- "We measure monthly. First positive movement expected in 3–4 months."
127- "This is an authority problem, not a technical problem. Fixing it takes time."
128- "We're building the substance Google looks for — not the trick."
129
130## Common rationalization traps
131
132| Statement | Reality |
133|-----------|---------|
134| "Let's buy 200 backlinks" | Raises spam score, makes recovery harder |
135| "Let's do a relaunch" | More risk than upside — substance first, then form |
136| "Better PSI will bring us back" | PSI is hygiene, not the core update lever |
137| "More pages = more traffic" | False — thin content weakens authority further |
138| "We did everything right" | In a Core Update Google changes the scoring. Being "right" doesn't help. |
139
140## Related skills
141
142- **claude-seo:seo-audit** — for the technical hygiene layer in Phase D
143- **claude-seo:seo-cluster** — for topical-authority-hub identification
144- **seo-outreach-report** — when the owner needs a printable status report
145
146## Real data points (anonymized 2026 cases)
147
148- March/April 2026 update: mid-size DE shop lost 50 % VI in 4 weeks
149- Diagnosis pattern confirmed: brand keywords stable, generic keywords broadly lost, CWV unchanged
150- Recovery plan: 6–12 months, Authority-First. Tech (PSI/Schema) in parallel but not the primary lever.
151- Lesson (Sistrix wording on March update): "Authority beats interchangeability"
152
153A second real case (DE news site) showed the same pattern in April/May 2026: −60 % VI in 6 weeks, brand stability intact — news/YMYL variant of the same algo recalibration.