# Robots.txt generator

> Build a robots.txt file: allow or block paths per crawler, add your sitemap, and test which URLs a rule blocks. Copy or download. Free, in your browser.

Canonical: https://toolspace.tech/robots-txt-generator/
Last updated: 2026-10-25

Build a robots.txt file group by group: pick the crawlers, add the paths they may or may not fetch, and list your sitemap. Then test any URL against it, or paste an existing file to test that. Runs in your browser.

This is an interactive tool that runs in the browser: [open the Robots.txt generator](https://toolspace.tech/robots-txt-generator/) to use it. Nothing typed into it is uploaded.

## Worked example

Keep crawlers out of a shop’s cart and account pages but leave the help section open, and point them at the sitemap.

**groups**

```
User-agent: *
  disallow /cart/
  disallow /account/
  allow /account/help/
Sitemap: https://example.com/sitemap.xml
```

**robots.txt**

```
User-agent: *
Disallow: /cart/
Disallow: /account/
Allow: /account/help/

Sitemap: https://example.com/sitemap.xml
```

Testing /account/help/returns gives “allowed”: Allow: /account/help/ is longer than Disallow: /account/.

## Common mistakes

### Disallow: / on the live site

A file copied from staging with Disallow: / asks every crawler to stay away from the whole site. Check before you deploy.

### Expecting a specific group to add to *

A Googlebot group replaces the * group for Googlebot; it doesn’t add to it. Rules you want everywhere must be in each group.

### Using it to hide private pages

robots.txt is public and only a request. Anyone can read it, and it lists exactly the paths you’d rather keep quiet. Protect private pages with a login.

### Wrong place or case

The file must be at /robots.txt on each host (and each subdomain), and paths are case-sensitive: /Admin and /admin are different.

## How it works

1. **Start from a preset or a blank group:** Allow all, block all, block a folder, or block a list of AI crawlers. Each group names one or more user-agents and their Allow and Disallow paths.
2. **Add sitemaps and check the file:** Sitemap lines go at the end. The finished file updates as you edit; copy it or download robots.txt for the root of your site.
3. **Test a URL:** Enter a path and a crawler name to see whether it may fetch it and which line decided. Paste a live robots.txt to test that instead.

## Questions

### How does a crawler decide between Allow and Disallow?

Under RFC 9309, the rule with the longest matching path wins, whichever comes first in the file. If an Allow and a Disallow match with the same length, Allow wins. No matching rule means the URL is allowed.

### Which group applies to a crawler?

Only one: the group whose User-agent matches the crawler’s name (case doesn’t matter). If there isn’t one, the * group applies. A crawler with its own group ignores the * rules entirely, so repeat any shared rules in it.

### What do * and $ mean in a path?

* matches any run of characters, and $ at the end means the URL must end there. Disallow: /*.pdf$ blocks URLs ending in .pdf but not /file.pdf?download=1.

### Does robots.txt hide a page from search results?

No. It asks crawlers not to fetch URLs, but a blocked URL can still be listed if other pages link to it. To keep a page out of results, let it be crawled and use a noindex meta tag.

### Does Google use Crawl-delay?

No, Google ignores Crawl-delay. Some other crawlers, such as Bing’s, read it as seconds to wait between requests. It isn’t part of RFC 9309.

## Related

- [Meta tag generator](https://toolspace.tech/meta-tag-generator/)
- [Regex tester](https://toolspace.tech/regex-tester/)
- [URL encoder](https://toolspace.tech/url-encoder-decoder/)
- [Slug generator](https://toolspace.tech/slug-generator/)