Utinzo

Robots.txt Generator

Generate a robots.txt file to control how search engine crawlers access your website.

Did this tool work for you?

How to use this calculator

  1. 1

    Enter your sitemap URL.

  2. 2

    Set which paths to disallow (admin pages, private areas, etc.).

  3. 3

    Choose whether to block AI training crawlers and bad bots.

  4. 4

    Set a crawl delay if your server needs breathing room.

  5. 5

    Copy or download and upload as robots.txt to your site root.

Frequently asked questions

What does each setting write into the file?

The access select decides the main group: “Allow all” and “Same as allow all” write User-agent: * followed by one Disallow line per path you list and one Allow line per allowed path, while “Block everything” writes User-agent: * with Disallow: /. A crawl delay above 0 adds a Crawl-delay line to the main group. The two bot options append one separate group per name. A sitemap URL adds a Sitemap line at the end.

Is the first select about Googlebot specifically?

No. Its label now reads “Access for all crawlers (User-agent: *)” because every option applies to the wildcard group. Nothing in the output names Googlebot. A crawler that has its own group, such as the AI and tool bots below, follows that group instead of the wildcard group.

Why do I get a bare Disallow: line when I list no paths?

An empty Disallow value means nothing is disallowed for that group. The tool writes it when the disallow box is empty so the User-agent: * group is not left without a rule. If you list paths, they replace it.

How do I enter several paths?

Separate them with commas or put each on its own line. Each one gets a leading / if it lacks one, so *.pdf is written as /*.pdf. Allow paths use the same rules. Paths are not tested against your site, so a typo is written as typed.

Does blocking a path keep it out of search results?

No. robots.txt controls crawling, not indexing. A blocked URL that other pages link to can still be indexed without its content. To keep a page out of results, use a noindex directive on a page that crawlers are allowed to fetch.

Which bots are in the built-in lists, and are the names reliable?

AI list: GPTBot, ChatGPT-User, Google-Extended, anthropic-ai, Claude-Web, CCBot, Omgilibot, FacebookBot, PerplexityBot, YouBot. Other list: AhrefsBot, SemrushBot, MJ12bot, DotBot, BLEXBot, Nikto. These are the tool’s lists, not a vendor-verified catalogue; names change and crawlers are added, so confirm each against the operator’s documentation. The AI list mixes training crawlers with fetchers that act on a user’s request, and Google-Extended is a robots.txt token that does not affect Google Search inclusion.

Does Crawl-delay work, and is robots.txt a security measure?

Googlebot ignores Crawl-delay, though some other crawlers read it; the tool writes only whole seconds above 0. robots.txt is a public file that compliant crawlers choose to follow. Anyone can read it, so listing a private path there advertises it. Protect private areas with authentication.

About robots.txt generator

What the robots.txt generator writes, line by line

Anatomy of the generated file

The file starts with two comment lines, then the main group beginning User-agent: *. Under it come one Disallow line per blocked path, one Allow line per exception, and a Crawl-delay line when you set a whole number above 0. Next, if enabled, come the AI group list and the other-bot list, each bot as its own group containing Disallow: /. The Sitemap line goes last. If the sitemap URL does not start with http:// or https://, the tool adds a comment line telling you to supply a full URL.

The built-in bot lists

Each enabled list writes User-agent and Disallow: / pairs for the names below.

Names written by the two bot options
OptionNames writtenNote
Block AI training crawlersGPTBot, ChatGPT-User, Google-Extended, anthropic-ai, Claude-Web, CCBot, Omgilibot, FacebookBot, PerplexityBot, YouBotMixes training crawlers and request-driven fetchers; verify names with each operator
Block known bad botsAhrefsBot, SemrushBot, MJ12bot, DotBot, BLEXBot, NiktoIncludes commercial SEO crawlers; a scanner such as Nikto is unlikely to obey the file

Worked example: the default settings

With nothing changed, the main group disallows /admin/, /private/ and /wp-admin/, followed by ten AI groups and six other-bot groups, so the file contains 17 User-agent groups in total and no Sitemap line because none was entered. Every listed bot is blocked from the whole site, while all other crawlers can reach everything except the three paths.

Worked example: custom paths, an exception and a delay

Enter the disallow paths /cart/, /search and *.pdf on three lines, allow /search/help, set the crawl delay to 10, switch both bot options off and add https://example.com/sitemap.xml. The result is the wildcard group with Disallow: /cart/, Disallow: /search, Disallow: /*.pdf, Allow: /search/help and Crawl-delay: 10, then the Sitemap line. Under the standard matching rule, where the longest matching path wins, /search/help is allowed even though /search is disallowed. Choose “Block everything” instead and the group collapses to Disallow: /.

Limits to keep in mind

The generator does not read your site, so it cannot say which paths exist or whether a rule blocks something you need. It does not test URLs against the file. Upload the result at the root of each host, for example https://example.com/robots.txt, because every host and protocol has its own file. Afterwards fetch it with the robots.txt checker to confirm it is being served.

Robots.txt Generator – Utinzo

Learn more from an authoritative source:

Google Search Central
Related tools

Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →