CitablePRACTICAL GUIDE · UPDATED 10 OCTOBER 2026
AI search readiness checklist: inspect, fix and verify
Use this checklist on one important page before spending money on AI visibility services. Keep a dated baseline, fix observed problems and verify outcomes in the right reporting tools.
1. Pick a page and a real customer question
Choose a published service page or article that answers something your audience actually asks. Write the question down. Review whether the page provides a useful answer, a clear author or organization, and evidence for its claims. A technical score cannot judge whether your answer is useful.
Record: the exact URL, question, review date and intended action, such as reading a guide or contacting your business.
2. Save a baseline audit
Run a free Citable audit and download the dated report before leaving. Inspect coverage as well as points. An unknown result needs investigation; it is not proof of a missing feature. Citable checks one page and bounded discovery files without running website JavaScript.
Record: measured failures, unknown checks and the report date. Avoid treating an entire domain as audited from a single page.
3. Fix access and discovery first
Read the robots.txt result for the exact path and the sitemap evidence. Preserve private-path restrictions and decide search permissions separately from training permissions. Check page-level indexing directives and access protection with your developer and webmaster tools; the Citable checklist is not a complete indexing diagnosis.
Example: a protected fetch should be investigated before concluding that your sitemap is missing. Allowing a search tool does not prove that it visited your page.
4. Make the page understandable and truthful
Review the title, description, heading structure and canonical address. Put the useful answer where visitors can find it, backed by specific examples or first-hand evidence. Use JSON-LD checks to inspect basic parsing, then validate detailed schema separately. Markup should describe facts visible on the page.
For WordPress: use the WordPress workflow to review visibility settings, plugin markup and the actual sitemap location.
5. Compare after a specific change
Change one issue, publish and rescan the same final URL. Keep before and after reports together. In your change log, separate “technical check improved” from “search traffic improved”. Do not change your content or remove protections just to reach 100.
Our measured example: on 10 October 2026, Citable's production homepage returned 100/100 with 100% coverage in our eight-check audit. That verifies this checklist at that time. It does not show improved rankings, AI citations or a proven before-and-after marketing result.
6. Verify outcomes outside the scanner
- Google Search Console: inspect indexing, impressions, clicks and queries for your verified property.
- Bing Webmaster Tools: inspect search reporting and any available AI Performance data for your property.
- Your website analytics: examine referral sources and completed actions. Missing referral information can hide a source; do not label all direct visits as AI traffic.
Submitting a sitemap or IndexNow notification helps report URLs to a search engine. It is not confirmation that a page was indexed or cited.
What you do not need to buy
No paid Citable subscription is required during this public beta. Google advises applying foundational SEO to its AI search experiences and does not require llms.txt or special AI files. Neither a file nor a perfect audit score guarantees inclusion.
Official Google AI search guidance · Our scoring method and limits