Enter a URL and click Scan to evaluate accessibility for popular LLM crawlers, presence of structured data, page speed, and other on‑page signals.
| Item | Why it matters for LLM visibility |
|---|---|
| HTTP Status | Pages must return 200 OK for crawlers to fetch and index content. 4xx/5xx errors block inclusion in AI answers. |
| Meta robots | <meta name="robots"> tells bots whether they can index and follow links.
noindex keeps pages out of LLM training.
|
| AI‑specific meta | Tags like name="ai" content="noai" signal opt‑out from AI use; LLMs may skip such
pages. |
| Structured Data (JSON‑LD) | Schema.org markup helps models understand entities and surface richer, more accurate snippets. |
| Fetch time | Fast (<1.5 s) load improves crawl efficiency and is a quality signal; slow sites may be deprioritized. |
| H1 count | A single descriptive <h1> provides a clear topic anchor. Missing or multiple H1s
dilute relevance. |
| robots.txt – LLM Crawlers | Allows or blocks specific AI bots (GPTBot, Google‑Extended, etc.). Blocking a bot prevents it from using your content in responses. |