Answer-readiness checker

Why paste HTML instead of a URL

Because a browser cannot fetch someone else’s page. Same-origin policy blocks it, and routing the request through a server would mean sending your page to us, storing it, and asking you to trust that we did not. Pasting the source keeps the whole thing on your machine — nothing leaves the tab.

Get the source with Ctrl/Cmd + U on the page you want to check, or curl -s https://example.com. Use curl if you want the honest answer: it shows what a crawler receives, before JavaScript runs. If your content is missing from that, no amount of on-page optimisation will help.

What it actually checks

Each check is something that measurably affects whether a page can be quoted, not a proxy for it:

• Title length — beyond roughly 60 characters, search results truncate it.
• Meta description — 50 to 160 characters. Shorter wastes the slot; longer gets cut mid-sentence.
• One h1 — the heading outline is how a machine works out what the page is about. Several h1s, or none, and there is no answer to that.
• Heading order — jumping h2 to h4 breaks the outline even though it looks fine to a reader.
• Extractable answers — a short, self-contained paragraph directly after a heading. This is the single strongest signal for answer-engine capture, and the one most pages miss.
• Image alt coverage — missing alt text is an accessibility failure first and a lost description second.
• Structured data — whether any valid JSON-LD is present, and which types.
• Word count — thin pages struggle to be cited regardless of structure.

What it does not do

It does not produce a single score out of a hundred. A composite number invites optimising the number instead of the page, and it hides which of eight different things is wrong. You get the individual results and can decide what matters.

It also cannot tell you whether your content is good. Structure is necessary and nowhere near sufficient — a perfectly shaped page saying nothing useful will be ignored by engines and readers alike.