Robots.txt Generator

Builds a robots.txt for your CMS and checks it with the same parser, so you see not only the text but which URLs it blocks. Every line has an explanation.

We will fill in the service paths of this engine: the admin panel, cache, and system folders. The sets do not block the site's content — the checkboxes below handle that.

Type the address in full — the one that actually opens. It cannot be built from the domain: one site keeps its sitemap at /sitemap.xml, another at /sitemap_index.xml. If you have no sitemap, leave the field empty — a made-up address is worse than a blank.

What to block
List several paths comma-separated or one per line.
List several paths comma-separated or one per line.
List several paths comma-separated or one per line.
Add your own rules Collapse your own rules

One rule per line. Write it in full (Disallow: /folder/) or just the path: we will add what's missing — the leading slash and the Disallow word.

Needed when a blocked folder contains something that must reach the search results. Here a bare path becomes Allow. When rules overlap, the longer one wins, so the exception will work.

Fine-tuning Collapse fine-tuning

Only Yandex understands it: it will glue together addresses that differ only by these parameters. List them separated by & without spaces. The line will go into a separate User-agent: Yandex block.

Google does not support this directive, as its own help pages say, and Yandex asks you to set the crawl speed in Yandex Webmaster. Set it only if your server truly can't keep up.

Check the result on your own URLs Collapse the URL check

We will run the generated file through our own parser and show which URLs got blocked and which stayed open.

A generator that checks itself

The file you build is parsed right away by the same engine that runs our robots.txt validator. You see not just the text but what it does: how many rules it contains, whether there are syntax errors, and which addresses end up blocked. Enter your own URLs and confirm that the pages you need stay open.

Every line explained

Next to the file sits a breakdown: which folder is closed and why. A file whose origin you cannot explain is a risky thing to put on a live site. One extra line can drop an entire section from search results.

Presets for CMS engines

For WordPress, 1C-Bitrix, Joomla, OpenCart, DataLife Engine, MODX, Drupal, PrestaShop, Magento, Webasyst, uCoz and Tilda the generator adds the standard service sections: the admin panel, cache, system folders, and service URLs with parameters. The presets leave your content alone. Whether to close search results, the cart, or tag pages is your call.

What we do not add

The Host directive is deprecated by Yandex, and the main mirror has long been set with redirects and the canonical tag, so the generator has no field for it. Crawl-delay is not supported by Google, and Yandex asks for crawl speed to be set in its webmaster tools. The field is still there, but it stays empty, with a warning next to it.

What to do with the finished file

Download it and place it in the root of your site, where it must open at an address like example.com/robots.txt. After uploading, check the file again by its URL. That way you confirm the server returns the file itself and not an error page.

Rate this tool

Help us get better

Other tools