robots.txt Builder

Generate a robots.txt file controlling crawler access to your site

Builds a valid robots.txt from crawl rules per user agent, allow and disallow paths, an optional crawl-delay, and a sitemap URL, then lets you copy or download the file for your site root.

Where does robots.txt go?

It must live at the root of your domain, served as text at https://example.com/robots.txt. Crawlers only read it from that exact location, not from subfolders.

robots.txt, built correctly

robots.txt is the file crawlers read first to learn which parts of your site they may fetch. A small mistake — a stray Disallow: / or a malformed path — can deindex an entire site, so it pays to generate it cleanly. This builder produces a valid file from simple inputs and lets you copy or download it.

How it works

The Robots Exclusion Protocol groups directives under one or more User-agent lines. This builder emits a single group: a User-agent line, then one Disallow: line per disallow path and one Allow: line per allow path. Paths are matched as prefixes from the site root, so Disallow: /admin blocks /admin and everything beneath it. An optional Crawl-delay line is added when you set a positive number. Finally a Sitemap: directive with your absolute sitemap URL is appended at the end, which applies regardless of user-agent group.

Tips and example

To allow the whole site, leave the disallow box empty. A generated file looks like this:

User-agent: *
Disallow: /admin
Disallow: /cart
Allow: /admin/help
Crawl-delay: 10
Sitemap: https://example.com/sitemap.xml

Always verify the result in Google Search Console’s robots.txt tester before deploying — and remember that blocking a URL here does not remove it from the index if it is already cached or linked elsewhere.