Tools
Tools
One working tool, and an honest list of the ones that are specified but not built. Everything here runs in your browser; nothing is sent anywhere.
A statement of what is and is not currently implemented on this site, checkable by using the links below.
Every tool on this site runs entirely in your browser. Nothing you type is transmitted, stored or logged, because there is no endpoint to transmit it to.
What tools are available on this site?
One: the answer search, which takes a question and returns the passage from this site that answers it, with its source, evidence grade and last-reviewed date. It runs in your browser against a static index.
Four others are designed and not yet implemented — a schema generator, a page readiness scorer, an entity consistency checker, and a channel payback calculator. They are listed below as unbuilt because a tools page listing things that do not exist is the kind of thing this site criticizes elsewhere.
Built
Answer search — ask a question in plain language and get the passage that answers it, quoted rather than generated, with the page it came from, its evidence grade and the date it was last reviewed. Runs on a static index downloaded once; your question never leaves the page.
Specified, not built
These are described honestly rather than teased. None exists yet.
| Tool | What it would do | Status |
|---|---|---|
| Schema generator | Produce a connected JSON-LD graph with stable identifiers, rather than the disconnected per-page blocks most generators emit | Not built |
| Page readiness scorer | Check a page for question headings, standalone answer sentences, sourced figures, heading hierarchy and schema presence | Not built |
| Entity consistency checker | Compare how an organization describes itself across its own properties and flag the mismatches | Not built |
| Channel payback calculator | Compare paid, organic and AI-visibility economics on your own numbers, with no default benchmarks | Not built |
Why they come last
Each of these is more useful attached to a content cluster that explains what it is measuring and why. A readiness scorer that outputs a number nobody can interpret is a toy; the same scorer linked to the pages explaining each check is a teaching tool.
So the order is deliberate: pillars first, tools afterwards.
The constraint all of them share
Everything client-side. No account, no upload, no storage, no key.
The calculator in particular would take financial inputs, and there is no version of this site where a visitor's revenue figures are posted to a server. If a tool cannot be built to run locally, it does not get built.