SEO Incident Simulator
Free, no signup. Practice a defensible technical SEO investigation with deterministic evidence, plausible decisions, and clear operational consequences. Every run is a hypothetical fixture case—not a live audit or a prediction about your site.
- 1Choose a caseStart with a bundled incident.
- 2Inspect evidenceReview the unlocked fixture records.
- 3DecideChoose the next diagnostic action.
- 4DebriefCarry the method into a real tool.
Migration traffic collapse
A site relaunch is followed by a sharp organic-landing-page decline. Work from the affected URLs outward before changing sitewide settings.
Difficulty: intermediate
What this lab practices
- Establish a launch baseline
- Prioritize lost landing pages
- Flatten redirect chains before measuring recovery
Fixture evidence
Each source is simulated. Review the available records before choosing a next step.
Decision trail (0) decisions made
Select an evidence source
The launch date and landing-page drop line up. What should the incident team do first?
Inspect the available fixture evidence before choosing an action.
Runs entirely in your browser — nothing you paste is uploaded or stored. Progress may be saved in this browser as scenario and decision IDs only; fixture bodies and visitor input are never stored. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
How to use it
- Choose a scenario and read its learning objectives before making a decision.
- Inspect the available fixture evidence instead of guessing from the incident summary.
- Select the smallest safe next action. Consequences unlock evidence, advance the investigation, or end the path.
- At an ending, compare the evidence you found, the corrective action, and the suggested verification tool.
- Restart or rewind to test why another path is weaker. Completion is a training sequence, not a performance score.
Example scenario Fixture data
The guided Canonical conflict and index loss lab inventories five disagreeing signals for a fictional product URL. Its shortest defensible path is:
Find: HTML and HTTP canonicals disagree; navigation points to a redirecting /shop/ URL; the sitemap and redirect agree on /products/.
Fix: use /products/widget-a consistently in HTML and HTTP canonicals, sitemaps, and internal links while preserving the one-hop redirect.
Verify: retest the public signals with the Canonicalization Checker, then use Search Console for Google's selected canonical.
Every URL, date, response, and outcome in that report is invented fixture data.
What the simulation shows
An evidence artifact contains labeled facts and optional rows with a fixture observation date. A consequence explains what a choice establishes or leaves uncertain. An ending separates find, fix, and verify, records missed evidence, and names the shortest diagnostic path. It does not predict traffic recovery, crawling, indexing, or rankings.
How it works
Thirty versioned JSON scenarios define their initial step, evidence artifacts, choices, consequences, unlocked evidence, and endings. The browser-only simulator applies deterministic state transitions, records inspected evidence and decisions, and can save only scenario and decision IDs locally. No live URL, API, model, or Search Console property is queried.
Features
- Guided, intermediate, and advanced technical SEO incidents.
- Evidence spanning headers, redirects, canonical signals, crawl samples, traffic series, rendered HTML, and timelines.
- Rewindable decision paths with explicit operational consequences.
- Find → fix → verify endings linked to the relevant public tool.
Limits of the simulation
- All evidence and outcomes are authored fixtures, not measurements from your site.
- The scenario graph cannot represent every valid investigation sequence or organization constraint.
- Completing a lab does not certify production readiness or prove a fix will work elsewhere.
- Google-only states remain outside public verification and are called out as such.
Frequently asked questions
Is this a diagnosis of my website?
No. Every incident, URL, response, timeline, and outcome is fixture data bundled with the page. The simulator does not fetch your site or use your Search Console data.
Does completing a scenario prove the same fix will work on my site?
No. The labs teach a diagnostic sequence and identify what public evidence can establish. Apply the linked tools and your own evidence before making a production change.
Why does the simulator distinguish public checks from Search Console?
Status codes, headers, redirects, and page markup are observable public evidence. Google’s crawl, selected canonical, and index decisions require a verified Search Console property and are not inferred by these fixtures.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
Feature requests for SEO Incident Simulator
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Giới thiệu công cụ
Estmột simuladhoặc tiene no URL field o upload, fetches no site, y produces no en vivo finding. Projects son donde thực tế-site bằng chứng y trạng thái belong y persist; Whoặckflows guide một thực tế diagnostic sequence desde một herramientmột resultado. Only después de el debrief, elegir một linked thực tế herramientmột y ejecución lo con tu own authhoặcized bằng chứng. Thực hành técnico SEO incidente diagnosis con treintmột determinista, hypotical fixture cases spanning khả năng lập chỉ mục, thu thập dữ liệu, redirecciones, sitemap, đánh dấu, bộ nhớ đệm, DNS, bot verificación, kết xuất, hreflang, y điều hướng o bộ lọc. Gratuito, no registro. Thực hành một defensible técnico SEO investigación con deterministmột bằng chứng, plausible decisions, y bhoặcrar operational consequences. Every ejecución es một hypotical fixture case—no một en vivo auditmột o một prediction about tu site.
Tính năng
- Guided, intermediate, y advanced técnico SEO incidentes. Evidence spanning cabeceras, redirecciones, puedeónicmột tín hiệu, thu thập dữ liệu samples, traffic series, rendered HTML, y timelines. Rewindable decisión paths con explicit operational consequences. Tìm → choặcregir → verificar endings linked một el relevant công khai herramienta.
- Features
Cách hoạt động
How lo whoặcks Thirty versioned JSON scenarios define su initial step, bằng chứng artifacts, choices, consequences, unlocked bằng chứng, y endings. El browser-only simuladhoặc applies deterministmột trạng thái transitions, registros inspected bằng chứng y decisions, y puede guardar solo scenario y decisión IDs locally. No en vivo URL, API, model, o Search Console propiedad es queried.
Hạn chế
- Simulated incidente · fixture datos: Every fact in se labs es invented parmột training. Endings connect el diagnostic método một thực tế herramientas, pero y hacer no claim một en vivo observation, Google-only trạng thái, o business outcome.
- Status codes, cabeceras, redirecciones, y páginmột đánh dấu son observables công khai bằng chứng. Google’s thu thập dữ liệu, seleccionadmột puedeónica, y índice decisions require một verificadmột Search Console propiedad y son no inferred by se fixtures.
- Limits de el simulation
- All bằng chứng y outcomes son authhoặced fixtures, no measurements desde tu site. El scenario graph no puede represent cadmột válido investigación sequence o hoặcganization constraint. Completing một lab hace no certify production readiness o prove một choặcregir will whoặck elsewhere. Google-only states permanecer outside công khai verificación y son called out as such.
Câu hỏi thường gặp
Is estmột một diagnosis de my website?
No. El labs teach một diagnostic sequence y identify what công khai bằng chứng puede establish. Apply el linked herramientas y tu own bằng chứng antes de making một production cambio.
Why hace el simuladhoặc distinguish công khai comprobaciones desde Search Console?
No. Every incidente, URL, respuesta, timeline, y outcome es fixture datos bundled con el página. El simuladhoặc hace no fetch tu site o dùng tu Search Console datos.