Free tool
Enter a URL. We fetch the page along with its robots.txt, sitemap, and llms.txt, then run 40+ checks across technical SEO, on-page structure, schema, and AI search readiness. It takes a few seconds, and the score needs no email.
Every check is run against the HTML your server actually returns, instead of a rendered screenshot. Here is the whole list, grouped the way the score is weighted.
30% of the score
Whether a search engine can reach the page and is allowed to keep it.
30% of the score
The parts of the page a search engine reads to decide what it is about.
15% of the score
What machines are told about the page, beyond the words on it.
25% of the score
Whether ChatGPT, Claude, Perplexity, and AI Overviews can read and quote the page.
The score, the 4 category breakdowns, and the 3 highest-impact issues are free and need no signup. The rest of the report opens after you enter an email.
Between 41 and 43 checks, depending on what the page has. They cover technical crawlability, on-page structure, structured data, and AI search readiness. The full list is on this page.
Some sites sit behind bot protection that answers an unrecognised crawler with a 404 or a challenge page. When that happens we fetch the page again as a browser, audit what a browser sees, and flag the block separately. If you still see a 404, the page really is missing for everyone.
Yes. The audit tests whether robots.txt allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended, whether the content survives without JavaScript, and whether passages are shaped to be quoted. For a deeper look at crawler access alone, use the AI crawler check.
Every check carries an impact weight. A pass earns the full weight, a partial pass earns half, a failure earns none. Category scores are the percentage earned, and the headline score blends them at 30% technical, 30% on-page, 25% AI readiness, and 15% structured data.
No. It audits the single URL you enter, plus that domain's robots.txt, sitemap.xml, and llms.txt. Site-wide crawling is part of the paid engagement.
No. The only timing we report is time to first byte, which is how long your server took to send the HTML. We do not measure LCP, INP, or CLS, because those need a rendered page rather than the markup. Run PageSpeed Insights alongside this audit to cover both.
PageSpeed Insights measures loading performance on a rendered page. This audit reads what is in your HTML: tags, headings, schema, crawler rules, and how quotable the copy is. They answer different questions and it is reasonable to run both.
Yes. Pressing the button always refetches your page rather than replaying an earlier result, so a fix shows up on the next run. Each report also shows the time it was fetched.
No. The tool fetches your page the same way a search engine would, so it works on any public URL, including a competitor's.