What Google and AI crawlers see of your page

Paste the address of one of your pages. We read it once, like a crawler, and tell you what Google takes from it for its results and AI Overviews, then what your robots.txt and llms.txt tell AI crawlers.

We read the page, its robots.txt and its llms.txt once, like a crawler would. Nothing is stored.

What the tool checks

On Google’s side, the criteria Google publishes itself. A page has to respond normally, be open to Googlebot in robots.txt, carry no noindex directive and be able to show with a snippet. According to Google’s documentation, that is the only technical requirement for appearing in AI Overviews and AI Mode: no special markup and no AI-specific file is needed.

On the AI crawlers’ side, what your robots.txt allows each of them, separating those that feed a search engine, those that collect content for training and those that come on a person’s request. Blocking the first takes you out of answers. Blocking the second is a choice. Then your llms.txt and the links introduced in its version 2: the file the page points to and its Markdown version, which we covered in what llms.txt v2 changes.

What it cannot check

The tool announces itself under its own name, not Googlebot’s. A site can answer Google differently, and a firewall can refuse a crawler that robots.txt allows: only your server logs show that. It doesn’t run JavaScript either. It counts the text present in the page’s code, which is what every crawler receives first.

Above all, it tells you whether a page can be cited, not whether it is. Being readable is the starting point. Citation is decided elsewhere, as our piece on AI citability shows. Connecting both to what you sell is part of our analytics and performance expertise. Unsure about your case? Let’s talk.

The address you enter is neither recorded nor kept. Criteria checked on 30 September 2026.