Does Google support the Crawl-delay directive?
No. Google's crawlers ignore Crawl-delay entirely, even though this tool lets you add it. Some other search engines, like Bing, may honor it - only set it if you're targeting a non-Google crawler.
Generate a clean and Google-compliant robots.txt file for your website. Easily create allow or disallow rules, add sitemap URLs, and download the file instantly free with no login required.
If this tool isn’t working as expected, please take a screenshot of the error and report the problem here so we can investigate and improve it.
A misconfigured robots.txt file can accidentally block search engines from crawling your entire website - or fail to protect admin pages and staging environments from indexing. This tool generates a syntactically correct file using the directives search engines recognize (User-agent, Allow, Disallow, Sitemap), eliminating manual writing errors.
One caveat worth knowing: this tool also lets you add a Crawl-delay value, but Google does not support or read the Crawl-delay directive at all - some other search engines (like Bing) may honor it, so only add it if you're specifically trying to slow down a non-Google crawler.
A robots.txt generator creates a properly formatted robots.txt file for your website - controlling which pages search engine crawlers can access, which to ignore, and where the sitemap is located. This tool builds one User-agent group per file using Allow, Disallow, Crawl-delay, and Sitemap directives - the core directives search engines actually read.
Select allow or disallow rules for specific paths under one user-agent at a time.
Add crawl delay and sitemap URL if required.
Instantly preview the generated robots.txt file in real format.
Copy the robots.txt content or download it as a file.
Click Allow All, Block All, or Block Admin to load a ready-made rule set for user-agent "*", then adjust from there.
Type a user-agent name (e.g., "Googlebot", "GPTBot", or "*" for all bots), then add Allow or Disallow rules with a path - each rule set applies to the one user-agent you've entered.
Optionally add your Sitemap URL and a Crawl-delay value in the Global Settings section - both are appended to the output.
Check the live preview on the right, then click Copy Code or Download File to get your robots.txt.
Best For
Input
User-agent: *, Rules: Allow /, Disallow /admin, Disallow /wp-admin, Sitemap: https://example.com/sitemap.xmlOutput
User-agent: *
Allow: /
Disallow: /admin
Disallow: /wp-admin
Sitemap: https://example.com/sitemap.xmlRules are automatically sorted alphabetically by path in the output, regardless of the order you added them in.
Use the Block Admin preset or add your own Disallow rules for paths like /admin or /staging.
Type the bot's exact user-agent name (e.g., GPTBot) and add Disallow rules for it - build and copy one bot's block at a time.
Add your Sitemap URL in Global Settings so it's included as a Sitemap line in the file.
Problem
Solution
The tool builds one User-agent group at a time - to give different bots different rules, generate and copy each group separately, then combine them yourself in the final file.
Problem
Solution
Google does not read the Crawl-delay directive at all - it only has an effect on crawlers that support it, such as Bing's.
Problem
Solution
This clears the entire preview, not just the Crawl-delay line - use a positive number, or leave the field blank.
Problem
Solution
An invalid URL is flagged with a red border and also clears the entire preview until it's fixed or removed.
Problem
Solution
Disallowing a URL only blocks crawling - it doesn't guarantee the page stays out of the index. Use a noindex meta tag on the page itself to control indexing.
The Allow All, Block All, and Block Admin presets cover the most common starting points - load one and adjust the rules from there instead of starting blank.
The User-agent field accepts any text, so you can target a specific crawler like Googlebot, Bingbot, or an AI crawler like GPTBot or CCBot by typing its exact name.
Since Google ignores this directive entirely, only set it if you're trying to slow down a different bot that's overloading your server.
After publishing your robots.txt at your site's root, use Search Console's own tools to confirm Google can read it as expected - this generator doesn't validate the file against a live crawler itself.
All rules you add apply to a single User-agent value - there's no way to configure multiple bots with different rules in one generated file. Build and combine multiple groups manually if you need that.
The Crawl-delay directive is included if you set it, but Google's crawlers ignore it entirely - only some other search engines may honor it.
The tool generates syntactically correct output but doesn't test it against your actual site or verify how any specific crawler will interpret it.
There's no built-in button or list for AI crawlers - you target them by typing their exact user-agent name yourself, the same way as any other bot.
This generates a robots.txt file only - it doesn't prevent an already-indexed page from appearing in search results (that requires a noindex tag, not a robots.txt rule).
Both of these input states clear the entire output, not just the affected line - double-check these two fields if the preview unexpectedly goes empty.
Both control search engine behavior, but they do fundamentally different jobs.
| Disallow (robots.txt) | Noindex (meta tag on the page) | |
|---|---|---|
| What it controls | Whether crawlers are allowed to request the URL | Whether the page is allowed to appear in search results |
| Can the page still be indexed? | Yes - if other sites link to it, it can still be indexed without being crawled | No - noindex reliably keeps it out, but only if the page can still be crawled to see the tag |
| Where it lives | One shared file at your site's root | A meta tag on each individual page |
Which should you use?
Use Disallow to manage crawler traffic and server load; use noindex when your actual goal is keeping a specific page out of search results.
The most common question is what robots.txt can and can't do. It controls which pages crawlers are allowed to request - it does not remove a page from Google's index by itself (a blocked page can still appear in search results if other sites link to it; use a noindex meta tag to actually keep a page out of the index). The FAQ below also covers crawl-delay, AI crawlers, and where to place the file.
No. Google's crawlers ignore Crawl-delay entirely, even though this tool lets you add it. Some other search engines, like Bing, may honor it - only set it if you're targeting a non-Google crawler.
No. Disallowing a URL only tells crawlers not to request it - a blocked page can still appear in search results if other sites link to it. To keep a specific page out of the index, use a noindex meta tag on that page instead.
Yes. Type the bot's exact user-agent name (for example, GPTBot, CCBot, or Google-Extended) into the User-agent field and add Disallow rules for it. There's no dedicated AI-crawler preset - you configure one bot's rules at a time, the same way as any other user-agent.
Not in a single generation. This tool builds one User-agent group at a time - generate and copy the rules for each bot separately, then combine the groups yourself into one final robots.txt file.
At the root of your domain (e.g., https://example.com/robots.txt) - search engines only look for it there, not in a subfolder.
Leave your email so we can prioritize similar tools and updates.
Trending tools will appear as visitors explore the catalog.
Your recently visited tools will show up here.