Get your site ready for ChatGPT and friends
Create an llms.txt that explains your business to large language models, check which AI crawlers your robots.txt allows and generate a setup that keeps you visible in AI assistants without handing over your content for training.
llms.txt
—Upload it to the root of your domain so it lives at yoursite.com/llms.txt. It's plain-text Markdown, no HTML tags.
| Crawler | Root / | /blog/ | Rule that applies |
|---|
robots.txt
If you already have a robots.txt, keep your current rules and add only the AI groups. Changes take anywhere from a few hours to a few days to take effect.
Three steps and done
- 01
Create your llms.txt
Enter your name, a summary, key facts and your most important pages with a short description. Download the file and upload it to the root of your domain.
- 02
Check your robots.txt
Paste your robots.txt and see, bot by bot, whether Googlebot, GPTBot, ClaudeBot, PerplexityBot and the rest can read your site, and which rule decides it.
- 03
Apply the recommended policy
Choose whether to appear in AI answers without allowing training, fine-tune each crawler and copy the generated robots.txt.
Not every AI bot does the same thing
AI crawlers fall into three families. Training crawlers (GPTBot, ClaudeBot, CCBot, meta-externalagent, Bytespider) download content to train future models; blocking them doesn't cost you visibility today. AI search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot) index your site so it can be shown and cited when someone asks ChatGPT, Claude or Perplexity; blocking them does take you out of those answers. And user-triggered agents (ChatGPT-User, Claude-User, Perplexity-User) visit a specific page because someone asked the assistant to.
There are also two control tokens: Google-Extended and Applebot-Extended. They aren't separate crawlers; Google and Apple crawl with their regular bots and use these names only to know whether they may use your content to train Gemini or Apple's models. Blocking Google-Extended does not affect your Google rankings or your presence in AI Overviews, which depend on Googlebot.
A robots.txt file is read in groups: each bot looks for the group with its exact name and, if there isn't one, uses the User-agent: * group. Within a group, the Allow or Disallow rule with the longest matching path wins, and Allow wins ties. A common mistake is creating a group for an AI bot and forgetting to repeat your private paths: that bot no longer reads the * rules. The checker shows you exactly which rule applies in each case.
llms.txt is an open proposal (llmstxt.org) for a Markdown summary at the root of your site with the essentials of your business and links to your key pages. It isn't yet a standard every assistant reads, but it takes five minutes, helps agents that browse your site and forces you to organize the information you want AI to repeat: who you are, what you offer, where and at what price.
llms.txt builder
Summary, key facts, sections with links and an Optional section, with a live preview and file download.
Spec-accurate checker
Reads User-agent groups and * and $ wildcards, and resolves by the longest rule, just like Google and RFC 9309.
16 search and AI crawlers
Googlebot, Bingbot, GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and more.
Test any path
Besides the root, check a specific path like /blog/ or /pricing to see which bots can read it.
Recommended robots.txt
Three ready-made policies plus per-bot tweaks, with your private paths repeated in every group so nothing slips through.
Everything in your browser
We don't upload your robots.txt or your content to any server.
