Core Update War Room
Triage SEO volatility during confirmed ranking updates
When Google launches a core update, sites can see major swings in traffic and rankings. This recipe creates a "war room" checklist: define the baseline, segment impact, avoid premature changes, and produce a recovery roadmap once rollout stabilizes.
INGREDIENTS
PROMPT
Run an SEO core update war room plan. Output: - Impact summary (what changed, which segments, severity ranking) - Rollout-window guidance (what to pause, what's safe to fix) - Recovery roadmap for the next 30–60 days (content, tech, UX, authority) - Monitoring checklist to track stabilization Inputs: - Site type + main traffic sources: - Key templates/pages: - Search Console deltas (paste highlights): - Dates when movement started:
How It Works
This recipe operationalizes your response to ranking volatility so you don't overreact mid-rollout.
Triggers
- Confirmed core update is rolling out (or just finished)
- Organic traffic drops/spikes sharply in 24–72 hours
Inputs
- Site type (publisher, ecommerce, SaaS) and key pages/templates
- Primary KPI (clicks, leads, revenue) and seasonality notes
- Search Console exports (queries/pages) pre vs post
Outputs
- Impact summary by segment (template, intent, geo, device)
- "Do / Don't" list for the rollout window
- Post-rollout recovery roadmap (content, tech, UX, authority)
Actions / Steps
- Confirm rollout status; record start/end dates.
- Freeze "big changes" until stabilization; log only safe fixes (broken pages, indexing errors).
- Segment impact: brand vs non-brand, top templates, top query classes.
- Prioritize improvements that raise overall usefulness and clarity (not hacks).
Parameters
- Baseline window (e.g., 28 days before update)
- "Freeze" policy duration
- Severity scoring per segment
Tips
- Don't rush changes mid-rollout. Updates can take 2+ weeks to fully stabilize.
- Document everything. Pattern recognition across multiple updates is where the real insight lives.