Skip to content

01 / Free site scan

One URL.
A clearer starting point.

We read the public site, inspect up to 150 pages, and show which conditions we could actually measure.

01 Fetch

Read public pages and supporting files.

02 Evaluate

Apply checks where inputs are available.

03 Report

Show evidence, coverage and limits.

The scan boundary

See what was inspected.

Public inputs
We inspect public page responses and supporting files such as robots.txt and sitemaps. A blocked page, missing input or failed fetch limits the evidence.
Coverage
Inspected pages and discovered URLs are different counts. Finding a URL in a sitemap does not mean we read it.
Free scan allowance
Anonymous visitors get 1 fresh scan per site per month. A free account gets 2 fresh scans per site per month.
Free view
Category scores and selected findings are visible. Sealed findings and hidden affected-page details require a paid report.
Scope
Up to 150 pages per site. Private account pages, unavailable pages and the rest of a larger site are outside the inspected scope.

What this does not tell youA public-page scan does not measure rankings or AI citations. Uninspected pages are not passes.

From input to evidence

What arrives in the report.

A measured score

An equal-weight fraction of conditions that had usable inputs, with applicability kept explicit.

Read the scoring boundary

Findings in order

Gate, Core, Amplifier and Hygiene group the observations so you can decide what to inspect first.

Open the check catalog

A next step

Open generic repair guidance, review a full report or prepare a developer handoff.

Meet the repair guide

Category scores and selected findings. No email required.