// free tool
See your site the way a crawler and an answer engine see it.
One URL, no signup, no email wall. We fetch the page from our own server and read only what a crawler would read. Then you get every check we ran, including the ones you passed.
Run an audit
What happens when you press the button
- 01
Fetch
Normally three requests, from our server, with a user agent that says who we are. robots.txt comes first, and if it disallows us for that page we stop there. Then the page itself, then /llms.txt.
- 02
Read it the way a crawler does
The initial HTML only. We run none of its JavaScript. Vercel and MERJ found that none of the OpenAI, Anthropic, Meta, ByteDance or Perplexity crawlers render JavaScript. Gemini and Applebot do. Anything your site paints after load is invisible to the ones that do not.
- 03
Report
Every check is marked pass, needs work, fail or for information, next to the evidence it was decided from. There is no score, and nothing is hidden because it passed.
The full catalogue is on themethodology page. It lists every check, what it looks at and the source behind it.
What it cannot tell you
Being straight about this is the point of publishing the method at all.
- Core Web Vitals. A single server-side fetch runs no browser, so it measures none of LCP, INP or CLS. It reports the HTML weight and how long our server waited for it. Field data comes from the Chrome UX Report and Search Console, not from us.
- Whether a fix will move a ranking. We report what is in the way. Nobody, including us, can promise what removing it does.
- Whether an answer engine cites you. The audit checks whether an engine may fetch and read the page. It does not put any question to an engine, so it cannot say what one answers.
- Anything behind a login, a paywall, a geo-block, or a rule in your robots.txt that tells our crawler to stay out. We respect all four.
Want the findings fixed?
The audit is the free part. The work istechnical SEO andanswer engine optimization.
Book a strategy call