{Asad Webs}
← Toolz / SEO & Web / Robots.txt Generator
SEO·11

Robots.txt Generator

Build your robots.txt group by group — one group per crawler, rules as rows. The file updates live as you type. A group with an empty Disallow means “allow everything”.


Check an existing robots.txt

Enter any site address and we fetch its current /robots.txt and break it into groups. (This checks a live file — it does not read the builder above.)

Build a robots.txt file visually: pick a crawler, add Allow and Disallow rules, set a crawl delay, then copy or download the result. No syntax to memorise.

UNDERSTAND YOUR RESULTS

Robots.txt Generator — Build Crawler Rules Visually guide

Build a robots.txt file visually: pick a crawler, add Allow and Disallow rules, set a crawl delay, then copy or download the result. No syntax to memorise.

How to use this tool

  1. Start with the first rule group. Choose a user-agent — the star means every crawler; pick a named bot such as Googlebot, Bingbot or GPTBot to write rules for that crawler only.
  2. Add Disallow rows for paths bots should not crawl (checkout, account, admin and search-results paths are common) and Allow rows for exceptions inside them. Paths start with a slash and are matched as prefixes.
  3. Add more groups for other crawlers, set a crawl-delay if a bot is hammering a small site, and add your sitemap address at the bottom.
  4. Copy the generated file or download it as robots.txt, place it in your site’s root, and use the checker below to confirm what crawlers will see.

A worked example

To keep every bot out of a checkout while still letting them see the shop around it: one group for all crawlers with Disallow: /checkout/ and Disallow: /account/, a second group for GPTBot with Disallow: / to keep AI training crawlers out entirely, and the sitemap line at the end. The generated file keeps the groups in the order you built them.

How it works

robots.txt is a plain-text protocol: groups of user-agent lines followed by Allow, Disallow and Crawl-delay rules, with the sitemap line independent of any group. The generator assembles exactly that text from your rows, live as you type: an empty group with no rules means "allow everything", and in real crawlers the most specific matching rule wins. The optional checker fetches an existing /robots.txt through our protected fetcher — robots files are plain text, which the fetcher accepts — and breaks it into its groups for review.

Frequently asked questions

Where does robots.txt live?

At the root of your host: https://example.com/robots.txt. It must be a plain-text file at exactly that address — one per host, including separate ones for subdomains.

What is the difference between Disallow and noindex?

Disallow stops crawling; noindex (a meta tag or header) stops indexing but requires the crawler to load the page. To remove a page from results, allow crawling and use noindex — blocking it in robots.txt hides the noindex from the crawler.

Can I block AI crawlers with it?

Yes — add a group naming the AI crawler (for example GPTBot or ClaudeBot) with Disallow: / as its only rule. Compliant AI crawlers honour it, and the user-agent list in the generator includes the common AI bots.

What does crawl-delay do?

It asks a crawler to wait that many seconds between requests. Google ignores it (use Search Console’s settings there), but Bing, Yandex and many smaller bots respect it. Leave it empty unless a bot is overloading you.

Why does the checker say no robots.txt was found?

The file may genuinely be absent (every crawler then defaults to "everything allowed"), the site may have answered our fetch with an error, or the file may be served under a different host. Check the address in a browser to confirm.