Questions

What the audit measures, what the Fix Kit contains, and how it differs from the tools you may already pay for.

Is it really true that AI crawlers do not run JavaScript?

For most of them, yes. Two exceptions do render JavaScript: Google-Extended, which inherits Google's rendering infrastructure, and Apple's Applebot-Extended. GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot and the rest fetch raw HTML and parse it. That is why a site can rank perfectly well in Google Search and still be absent from AI answers: the two pipelines do not see the same page.

How is this different from an AI visibility tracker?

Those tools monitor what AI systems say about your brand across a set of prompts, billed monthly. Crawlable measures whether AI systems can read your site at all, and generates the files to fix it, billed once. They answer different questions, and this one comes first — prompt monitoring on a site a crawler cannot read tells you only that you are absent.

Does llms.txt actually do anything?

It depends who you ask, and the audit is honest about that. Google has publicly said llms.txt does not help with its AI features. Anthropic and OpenAI both publish llms.txt files for their own developer sites and recommend them for agent workflows, and Perplexity has been observed using them. It is one small file, it can only help the agent case, and it carries no risk — so the audit flags a missing one as a warning rather than a failure, and generates it for you either way.

What does the free scan include?

One page of your choice, fetched as a non-rendering crawler, plus your robots.txt and llms.txt. You get the real score, the real findings and the real per-page numbers. What it does not include is the multi-page crawl and the generated fix files.

How many pages does a paid audit cover?

Up to 40, sampled across your sitemap so the audit covers your homepage, docs, product and blog rather than 40 near-identical URLs from one section. On most sites that is enough to tell you everything a full crawl would about AI readability, because rendering problems are template-level, not page-level.

Will the crawl hurt my site?

No. It is at most 40 page fetches at four concurrent connections, plus your robots.txt, llms.txt and sitemap — roughly fifty requests in total, with a polite user agent and a per-request timeout. That is a fraction of what a single search engine crawl does in an hour.

Can I share a report with a client?

Yes. Every report has its own link that anyone can open with no login and no account. The generated fix files stay private to your licence — a client can read the findings without being able to download the kit.

How is payment and tax handled?

Checkout runs on a hosted payment page, so Crawlable never sees or stores a card detail. VAT and sales tax are calculated and remitted for your country automatically, and you get a proper invoice. Your licence key is stored only as a hash, plus its last four characters so you can tell your keys apart.

What if the audit finds nothing wrong?

Then you have confirmation, which is worth something, and a generated llms.txt and robots.txt you did not have before. Sites built on Astro, Gatsby, WordPress and well-configured Next.js often score in the 80s and 90s. The audit is only surprising when it is bad.