Free browser tool

Turn a technical SEO symptom into an evidence checklist

Define the failure, choose the relevant diagnostic lanes, and record what evidence actually exists. The generator produces a Markdown scope that can be copied into a brief, ticket, proposal, or release plan.

Nothing is uploaded or fetched. The output is only as specific as the inputs you provide; blank evidence stays marked as missing instead of being guessed.

Scope input

Describe the failure you can prove

Use route labels instead of private URLs when necessary.

Diagnostic lanes

Select only lanes that can plausibly explain the symptom.

Evidence already available

Unavailable evidence will remain an explicit acquisition task.

No scope has been generated.

Useful input

One affected sample and one healthy comparison

A real comparison exposes route, template, rendering, cache, or tracking differences faster than a sitewide warning count. Use representative URLs or anonymized route labels when the project is private.

Output contract

Context, evidence, owner, change boundary, verification

The generated document separates evidence already available from evidence still required. It does not declare a root cause, promise indexing, or replace live validation.

Need the live diagnosis?

The generated scope is an intake artifact, not a completed audit.

Use it to expose missing evidence and ownership before work begins. A root cause requires comparison against the live responses, platform data, or release state named in the document.