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 inspects the public homepage and supporting files it can reach. The audit reports observable technical signals without predicting whether an AI system will cite or recommend the site.
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
Checks whether a sitemap and any llms.txt file are available at the public locations the audit tests.
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 inspects public homepage crawl access, selected crawler directives, structured data, sitemap and llms.txt availability, content clarity, and performance signals. These checks describe technical readiness; they do not show whether an AI system will cite or recommend the site.
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 audit identifies observable technical and content issues on the public homepage; the Snapshot separately samples recommendation and citation behavior.
What happens after I run the audit?
You get an instant score, a section-by-section read, and a list of observed issues and suggested fixes. Technical fixes are written so a webmaster or IT partner can understand what to change next.