Alongside asking AI models about you, a scan audits your own website for AI-readiness. The audit fetches at most three URLs — your robots.txt, your llms.txt and your homepage — and runs 9 checks.

The checks

P0 — blockers

  1. Reachability (reach) — your homepage must respond successfully. If it doesn't, nothing else matters: models and their crawlers can't read a site that's down or erroring.
  2. HTTPS (https) — the site must resolve to an https:// URL. Unencrypted sites are penalized or skipped by most crawlers.
  3. AI crawler access (robots) — your robots.txt is checked against known AI crawler user-agents. Blocking them means opting out of AI answers entirely. A missing robots.txt passes (nothing is blocked); explicit blocks fail, partial blocks warn.

P1 — high impact

  1. llms.txt (llms) — an emerging convention: a plain-text file at /llms.txt that tells language models what your site is about. Easy to add — our free generator creates one.
  2. Local/organization schema (schema_local) — JSON-LD structured data (LocalBusiness, Organization or a specific business type) that tells models unambiguously who you are, where you are and what you do.
  3. Title & meta description (title) — your homepage needs a real title and a meta description of reasonable length; these are heavily weighted signals of what your business is.
  4. NAP consistency (nap) — name, address and phone must be findable on the homepage (visible text, tel: link or schema). If you have one but not the other, the check warns.

P2 — worth fixing

  1. FAQ schema (schema_faq) — FAQPage structured data marks question-and-answer content, exactly the format AI answers are built from.
  2. H1 heading (h1) — the homepage should have a proper top-level heading; it anchors what the page (and business) is about.

Reading the results

Each check reports pass, warn or fail with its severity (P0/P1/P2). Fix P0 fails first — they gate everything else. The dashboard turns fails into concrete page-level prescriptions you can work through and verify.