AI Readiness Checklist: 12 Fixes That Get You Cited
AI readiness is how prepared a page is to be found, read and cited by AI assistants. This checklist covers the twelve highest-leverage fixes, ordered so each one builds on the last.
Retrievability: let AI in
An engine that cannot fetch your page cannot cite it. Start at the gate.
- Allow AI search crawlers in robots.txt — OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot. Blocking them removes you from live answers.
- Decide deliberately about training crawlers (GPTBot, ClaudeBot, Google-Extended). Blocking is a legitimate IP stance, but it slows how fast models learn your brand.
- Publish an llms.txt at your domain root listing your most citable pages with one-line descriptions.
- Remove accidental noindex directives — a noindex page is invisible to both Google and AI retrieval.
Extractability: give AI something to lift
Once the engine is in, structure decides whether anything is quotable.
- Add Organization schema site-wide with name, url, logo, contactPoint and sameAs.
- Add Article schema on content pages with headline, author, datePublished and dateModified.
- Add FAQPage schema wherever you genuinely answer questions.
- Open every H2 section with a one-to-two sentence direct answer, under 30 words.
- Convert steps into numbered lists and comparisons into real tables.
Trust: give AI a reason to pick you
Between two extractable pages, engines cite the one with stronger provenance.
- Show a visible author byline and mirror it in schema.
- Display published and updated dates in <time> elements.
- Cite authoritative sources — standards bodies, government data, major references — with descriptive anchor text.
Frequently asked questions
How long does it take to see AI citations after these fixes?+
Live-retrieval engines like Perplexity can cite you within days of a fix because they fetch pages at question time. Training-data effects take months. Fix retrievability and extractability first — they pay off fastest.