A crawler asks for a page
GPTBot, ClaudeBot, PerplexityBot or a fetcher acting for a person requests /pricing.
Setup takes minutes and needs no changes to your pages.
The scan fetches your pages as each major AI crawler would and records what it receives, what it is refused and what is missing.
Three problems to fix first. Two take under ten minutes.
No file found at /llms.txt.
LLMReady writes it from your sitemap and top pages.
GPTBot is allowed. ClaudeBot and PerplexityBot are blocked by a firewall rule.
412 URLs listed, all return 200.
Add LLMReady at your CDN or edge, or send logs. It works with any platform. Every AI request is classified the same day.
| Connect with | You get |
|---|---|
| Free scan | The report and the fixes. No connection needed. |
| Server logs | AI traffic analytics, alerts and attribution. |
| CDN or edge | Everything above, plus bot policy, identity checks and agent pages. |
Crawlers get agent pages that stay current. You get a weekly report on crawl success, refused requests and the visits and sales AI answers send back.
curl -A GPTBot https://acme-supply.example/pricingHTTP/2 200 content-type: text/markdown# Pricing> Acme Supply sells reusable packaging to small food businesses. ## Plans- Starter, $19 a month, one location- Growth, $59 a month, up to five locations llms.txt found Markdown found JSON-LD found
GPTBot, ClaudeBot, PerplexityBot or a fetcher acting for a person requests /pricing.
The user agent is checked against the vendor's published IP ranges, so a fake name is caught.
Your per-bot rule says allow, limit or block, with a reason that is logged.
Allowed bots get the agent page: clean markdown and structured data. People get your normal site.
Bot, page, status, bytes and any AI referral are stored for the report.
Leave your email and you will hear when your spot is ready.