AI crawler access
Checks robots rules and crawler directives that can block ChatGPT, Claude, Gemini, Perplexity, and other AI systems from reading your public site.
Technical readiness
What this audit checks
Drifter reads your public homepage the way an AI system would: can it reach the page, understand the facts, find the right supporting files, and turn official content into a useful answer for travelers?
Structured data
Looks for schema that helps systems identify the place, organization, website, FAQs, and other facts travelers may ask about.
Sitemap and llms.txt
Confirms crawlers can discover the canonical site map and any machine-readable guidance your team publishes for AI systems.
Content clarity
Reviews whether the homepage explains who the place is for, what visitors can do, and which official pages support trip-planning questions.
Performance and access
Flags slow or fragile pages that make it harder for crawlers and travelers to reach the content they need.
FAQ
Common audit questions
What does the free AI Readiness Audit check?
It checks whether AI systems can crawl, interpret, and cite your public homepage. The report covers AI crawler access, structured data, sitemap and llms.txt discovery, content clarity, and performance signals.
Do I need llms.txt to appear in AI answers?
No. The audit checks llms.txt because it is useful guidance for some systems and teams, but the baseline is still a crawlable, indexable site with clear official content.
Can this guarantee that AI will recommend us?
No. No audit can guarantee placement in AI answers. The point is to find the technical and content gaps that make it harder for AI systems to trust, cite, and explain your official site.
What happens after I run the audit?
You get an instant score, a section-by-section read, and a prioritized fix list. Technical fixes are written so a webmaster or IT partner can understand what to change next.