Product

One crawl.Three scoreboards.

ProvenVisible is an AI visibility operating system: it measures how search engines and answer engines see your site, explains every gap with evidence, and follows each fix through to a verified result.

What it does

Built to be checked, not believed.

Deterministic diagnosis

126 checks run against your crawled pages. Each one states how it could be proven wrong, so a finding is an argument you can audit, not a verdict.

Three scoreboards, one page

Classic SEO, answer-engine readiness (AEO) and generative citation (GEO) are scored separately, plus a combined Health Score. Improving one rarely hurts another: you see which.

The model never sets the score

Scores come from the check registry, not from a language model. AI findings appear as advisory notes with an AI badge and carry no points.

Fixes, not recommendations

For each finding ProvenVisible drafts the actual change (the meta text, the schema block, the llms.txt file) with the evidence beside it. You approve; nothing ships on its own.

Four ways to connect

Cloudflare (we set it up), a WordPress plugin, an edge middleware line, or a pull request to your repo. ProvenVisible can only serve text-shaped changes, never scripts.

Verified, or it does not count

After a change goes live, ProvenVisible fetches the page and checks the change is really there. Until it is seen, the fix stays 'approved', never 'verified'.

The closed loop

From invisible to measurable.

Most tools stop at the list of problems. The value is in the last two steps: actually changing the page, and proving the change moved something.

  1. 01Crawl: Discover pages, classify them, and keep a content hash so later drift is visible.
  2. 02Diagnose: Run the registry. Findings carry severity, evidence and a falsifiability note.
  3. 03Measure: Track how answer engines cite you for the prompts your buyers actually use.
  4. 04Fix: Draft the change, show before and after, wait for your approval.
  5. 05Re-measure: Confirm the change is live, then score again and compare.

Safety

What ProvenVisible is not allowed to do.

Connecting a tool to your live site is a real risk, so the limits are enforced in code: in our API, in the manifest, and again inside each connector.

  • It cannot run JavaScript on your site. Script payloads are rejected at three separate layers.
  • It can only write plain-text files (.txt, .xml, .json) at your site root, no arbitrary paths.
  • Structured data is accepted only as valid JSON-LD, parsed and re-checked before it is served.
  • Nothing is published without your approval, and every change can be rolled back.
  • A change that cannot be seen live is never reported as verified.