How it works
Six checks. One score.
We fetch your client's site the way AI crawlers do — then grade what they find. The same six checks run on every site, so every client gets the same report. Scan the site, show the client the report, then monitor it with a fresh report every month.
Crawler access
What the site's robots.txt says, and what crawlers actually get. We read the site's robots.txt to see which AI crawlers it's told to stay out: GPTBot, ClaudeBot, PerplexityBot and the rest. Then we fetch the page and check whether each one can really get in. The report shows both side by side, so you can spot a site that welcomes AI on paper but blocks it in practice.
Structure
One main headline, sub-headlines in order, and the page's sections labeled — header, menu, main content, footer — so AI can tell what the page is about and pull answers from it.
Metadata
The page title and description, the one web address the page should be known by, how the page looks when it's shared, and the client's business facts in a format machines read (schema) — the signals AI uses to understand and quote a page.
Content
Content depth, and whether the about, contact, and pricing pages exist and are linked — what gives AI something worth citing.
FAQ signals
Question-and-answer content with FAQ schema — the format AI assistants cite most.
Performance
Load speed and page weight — slow pages get crawled less and trusted less.
The scan
A scan, step by step
We fetch the page
We fetch the client's page with a plain HTTP request, the way AI crawlers do, and score what that fetch returns.
We read the site's robots.txt
We read the site's robots.txt for the ten AI crawlers we test, then check with a live fetch whether each one can really get in.
We also render the page
We also render the page in a real browser and compare it with the plain fetch, so the report shows how much of the site's content depends on JavaScript.
We score the six checks above, each 0–100, and combine them into one 0–100 score.
The weights are on the methodology page.
You get the score, the top fixes first, and every other finding ranked after them.
A token is used only when the scan completes.
The report
Ranked by impact.
Every report opens with a 0–100 score, then the top fixes, ranked by impact, with every other finding listed after them. The biggest wins come first — each with the exact change to make and, where useful, ready-to-paste code like robots.txt rules or JSON-LD schema. One token pays for one completed scan. If a scan errors out, the token stays in your balance.
The monitor
A fresh report every month.
For the clients you keep, monitoring re-checks the site and emails a monthly PDF report you can hand to the client: the score at the start of the month and now, what changed, the fixes completed with their dates, and the next actions. Turn on white-label and it carries your name and logo. Between reports, you get an alert when a site's score drops or a new issue appears.