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.

Built by Patrick Stox

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.

Choose a fixture case 30 bundled cases · no URL, upload, or live check

Simulated incident · fixture data

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

Inspect

Fixture evidence

Each source is simulated. Review the available records before choosing a next step.

Decision trail (0)

4. Current fixture evidence

Select an evidence source

Decide

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.

Simulated incident · fixture data: Every fact in these labs is invented for training. Endings connect the diagnostic method to real tools, but they do not claim a live observation, Google-only status, or business outcome.

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.

Local data

Saved targets, named lists, and recent check summaries remain only in this browser.

Next stepHTTP Status & Redirect Checker — run the same investigation on a live URL.

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.

Loading…

➕ Request a feature

New requests are reviewed before they appear here.

Feedback

ツールについて

このシミュレーターにはURL入力欄もアップロードもなく、サイトを取得せず、ライブの検出結果も生成しません。実サイトの証拠と状態を保存するのはProjectであり、ツール結果から実際の診断手順を案内するのがWorkflowです。振り返り後に、リンクされた実ツールを自分が許可された証拠で実行してください。

インデックス登録可否、クロール、リダイレクト、サイトマップ、マークアップ、キャッシュ、DNS、ボット検証、レンダリング、hreflang、ファセットナビゲーションにまたがる、決定論的で仮想的な技術SEOインシデント30件を練習します。

無料・登録不要。決定論的な証拠、妥当な意思決定、明確な運用上の結果で、説明可能な技術SEO調査を練習します。各実行は仮想フィクスチャケースであり、ライブ監査でもサイトへの予測でもありません。

機能

ガイド付き・中級・上級の技術SEOインシデント。ヘッダー、リダイレクト、canonicalシグナル、クロールサンプル、トラフィック系列、レンダリング済みHTML、タイムラインにまたがる証拠。明示的な運用上の結果を伴う、巻き戻し可能な意思決定経路。関連する公開ツールへつながるFind → Fix → Verifyの終点。
機能

仕組み

仕組み：バージョン管理されたJSONシナリオ30件が、初期ステップ、証拠アーティファクト、選択肢、結果、開放される証拠、終点を定義します。ブラウザーだけで動くシミュレーターは決定論的な状態遷移を適用し、調査した証拠と意思決定を記録します。ローカルに保存できるのはシナリオIDと決定IDだけで、ライブURL、API、モデル、Search Consoleプロパティには問い合わせません。

制限事項

シミュレーション上のインシデント・フィクスチャデータ：ラボ内の事実はすべて練習用に作成されています。終点は診断方法を実ツールへつなぎますが、ライブ観測、Googleだけが持つ状態、ビジネス上の成果を主張しません。
ステータスコード、ヘッダー、リダイレクト、ページマークアップは観測可能な公開証拠です。Googleのクロール、選択canonical、インデックス判定には検証済みSearch Consoleプロパティが必要で、これらのフィクスチャから推測しません。
シミュレーションの制限
証拠と結果はすべて作成済みフィクスチャであり、サイトの測定値ではありません。シナリオグラフは有効な調査経路や組織上の制約をすべて表せません。ラボを完了しても本番対応力の証明にはならず、別サイトで修正が効く保証もありません。Googleだけが持つ状態は公開検証の範囲外です。

よくある質問

これは自分のウェブサイトの診断ですか？

いいえ。すべてのインシデント、URL、レスポンス、タイムライン、結果はページに同梱されたフィクスチャデータです。シミュレーターはサイトを取得せず、Search Consoleデータも使いません。

シナリオを完了すれば、同じ修正が自分のサイトでも有効だと証明できますか？

いいえ。ラボは診断手順と、公開証拠で確かめられることを教えます。本番変更の前に、リンクされたツールと自分の証拠を使ってください。