llms.txt Generator
Build a clean, spec-compliant llms.txt — the curated file that tells ChatGPT, Claude and Perplexity which of your pages matter. Discover pages, keep the best, describe them, export
Build a valid robots.txt with the right allow/disallow rules, crawl-delay and sitemap line — with warnings for the mistakes that accidentally block your whole site from Google.
Build a correct robots.txt with real control over AI crawlers — block model-training bots while staying citable in ChatGPT, Claude and Perplexity. Live mistake-checking, llms.txt reference, 100% in your browser.
Quick strategy
Blocked paths
Sitemaps
AI stack
AI crawlers
The distinction most tools miss: training bots feed model training, search bots decide whether AI engines can cite you, and user bots fetch pages a person opened.
Search engines
processed in your browser · never uploaded
Target all crawlers with *, or set specific rules for Googlebot, Bingbot and others.
Block admin, cart or staging paths; allow the rest. Add your sitemap URL so crawlers find it.
Take the robots.txt and upload it to your site root, where it must live at yoursite.com/robots.txt.
We ran the same files through the popular alternatives first. These are the gaps we found, and what this tool does instead.
It warns you before you ship a rule that blocks everything — the single most common, most costly robots.txt mistake.
test: add "Disallow: /" and watch the warningBlocked pages can still be indexed if linked elsewhere; robots.txt controls crawling, not indexing. The tool flags this so you use noindex where it belongs.
test: read the note when you disallow a pathBoth are built in, so your robots.txt points crawlers to your sitemap and sets a polite crawl rate in one file.
test: add your sitemap URL and see it appendedA robots.txt file sits at your site root and is the first thing a search-engine crawler checks when it arrives. It tells crawlers which parts of your site they may and may not request — useful for keeping bots out of admin, cart, staging or search-results pages, and for managing crawl budget on large sites. It’s a small file with outsized consequences: get it right and crawlers focus on what matters; get it wrong and you can hide your whole site from Google.
That last point is the single most common robots.txt disaster: a stray Disallow: / under User-agent: * blocks every crawler from your entire site — usually left behind from a staging setup. This tool warns you before you export that rule. Just as important is a misconception worth clearing up: robots.txt controls crawling, not indexing. A page you block here can still appear in Google if other sites link to it — so to actually keep a page out of results, use a noindex meta tag and leave it crawlable, rather than blocking it in robots.txt.
One modern rule that trips people up: don’t block your CSS and JavaScript. Older guides told you to disallow theme and asset folders, but Google now needs to render your pages the way a visitor sees them — block those files and it can’t, which can hurt your rankings. A good robots.txt today leaves assets crawlable, blocks only what genuinely shouldn’t be crawled, and points to your sitemap. This tool builds exactly that, and everything runs in your browser with nothing uploaded.
When you’re done, upload the file to your site root — it only works at yoursite.com/robots.txt, never in a subfolder. Building out the rest of your technical setup? The XML Sitemap Generator and llms.txt Generator handle the other two root files crawlers look for.
A plain-text file at your site root that tells search-engine crawlers which parts of your site they may or may not crawl. It's the first file most crawlers check when they visit.
No — this is the biggest misconception. It controls crawling, not indexing. A blocked page can still appear in search if other sites link to it. To keep a page out of results, use a noindex meta tag instead, and don't block it in robots.txt.
Disallow: / under User-agent: *, which blocks your entire site from every crawler — often left over from a staging setup. This tool warns you before you export that rule.
At your site root, so it's reachable at yoursite.com/robots.txt. It only applies to that exact location; it can't live in a subfolder.
Yes. Adding a Sitemap: line pointing to your sitemap URL helps crawlers discover it. You can include it here in one step.
No. Older advice said to disallow theme and asset folders, but Google now renders your pages the way visitors see them — if it can't load your CSS and JS, it may misjudge the page and your rankings can suffer. Keep assets crawlable and only block things that genuinely shouldn't be crawled.
Modern WordPress needs very little. WordPress already blocks the sensitive admin internals itself, so you mainly want a Sitemap: line pointing to your sitemap, and perhaps a disallow for genuinely private paths. Don't block /wp-content/ or /wp-includes/ as old guides suggested — that blocks the CSS and JS Google needs.
Build a clean, spec-compliant llms.txt — the curated file that tells ChatGPT, Claude and Perplexity which of your pages matter. Discover pages, keep the best, describe them, export
Generate correct hreflang tags for multilingual and multi-region sites — as HTML link tags or an XML sitemap block — with validation that catches the mistakes Google flags.