Free AI Extractability Checker for Any Page
Billion Game
Book a strategy call

{{ col.title }}

{{ feature.tag }}

{{ feature.title }}

{{ feature.copy }}

{{ feature.cta }} {{ feature.cta }}
Runs in your browser · nothing uploaded

See what an AI crawler actually reads

Paste your page source. This strips it back to what a crawler that does not execute JavaScript would see, then scores whether each passage is answer-first, self-contained, and quotable — the three things that decide whether a retrieved page gets used in a generated answer.

Your page source {{ inputSize }}

Open your page, view source, copy the whole thing, paste it here. Use view-source, not inspect element — the inspector shows the DOM after JavaScript has run, which is the opposite of what we are measuring.

What a non-JavaScript crawler reads {{ survivedLabel }}
{{ plainText }}
Nothing to read

{{ noTextWhy }}

{{ plainNote }}

Extractability {{ overallLabel }}
{{ m.name }} {{ m.read }}
{{ m.note }}

{{ overallNote }}

Findings {{ findingCount }}
{{ f.tag }} {{ f.title }}

{{ f.detail }}

{{ f.fix }}

Nothing flagged. Content survives without JavaScript, headings are answered directly, passages stand alone, and there are specific figures to quote. That is the profile of a page an answer engine can use.
Passage by passage Retrieval scores passages, not pages — so each heading is graded on its own
Heading First sentence under it Verdict
{{ h.tag }} {{ h.text }} Question form {{ h.first }} {{ h.verdict }} {{ h.why }}

{{ noHeadingsWhy }}
Why raw HTML, not the DOM

Google renders JavaScript. Most AI crawlers do not. That single asymmetry means a page can index perfectly in search and be invisible to an answer engine, which is why the inspector is the wrong place to check — it shows you the page after the scripts have run.

What this tool cannot tell you

Whether you will actually be cited. It judges structure, and structure is necessary rather than sufficient. It also cannot see whether a crawler is allowed to fetch you at all — that is a robots.txt question, and a blocked page scores nothing regardless of how well it is written.

No tabs on this page

Every result is visible at once, deliberately. Putting analysis behind accordions on a tool that flags content hidden behind accordions would be a strange choice, and the same logic applies to your pages.

Method

How the four scores are calculated

Stated openly so you can disagree with it. These are heuristics, not measurements of engine behaviour, and nobody outside the labs has the real weights.

Score What it measures Why it matters
{{ r.a }} {{ r.b }} {{ r.c }}
Our stack

Billion Game runs your work through the same instruments the best in-house teams use.

Licences are on us, and every export we pull from them is yours to keep.

{{ s.alt }}
✎

Be wary of any agency whose reporting is a tool dashboard with their logo on it. Tools measure; they do not decide what matters, and every one of these will happily generate a hundred findings that change nothing. What you are paying for is the judgement about which three of those hundred are worth your developers’ time.

FAQ

Questions about extractability

The fuller argument sits on our answer engine optimisation page, and the content-side discipline on generative engine optimisation.

{{ f.a }}

This checks one page. The question is whether you are cited at all.

Free AI visibility report: your category prompts run across four engines, plus a crawler access check and an extractability pass on your key pages. 72 hours.

Get the free report Or the measured version