ESC

Robots.txt Configuration

User-Agent Blocks
Sitemap URLs
Crawl Delay
Quick Add Paths

Generated robots.txt

Configure your rules to generate robots.txt...
All processing happens in your browser. No data is sent to any server.

Usage Examples

Allow All Crawling

A simple robots.txt that allows all search engines to crawl all pages of your website with a sitemap.

Block Sensitive Folders

Block admin, private, API, and temp folders from crawling while allowing the rest of the site.

Multi-Agent Rules

Different rules for different search engines with multiple user-agent blocks and multiple sitemaps.

Features

Visual Builder

Build your robots.txt visually with dropdowns, buttons, and an intuitive interface

Multiple User-Agents

Support for multiple user-agent blocks with different rules for each crawler

Validation

Validate your robots.txt for common issues and syntax errors

Privacy First

All processing happens locally in your browser, no data sent to servers

How to Use?

1

Configure Rules

Select user-agents and add allow/disallow rules for paths you want to control.

2

Add Sitemaps

Add your sitemap URLs so search engines can discover all your pages efficiently.

3

Copy or Download

Copy the generated robots.txt or download it as a file. Place it in your website root directory.

Frequently Asked Questions

robots.txt is a plain text file placed at the root of your website that tells search engine crawlers which pages or sections they may or may not access. It follows the Robots Exclusion Protocol, which all major crawlers (Googlebot, Bingbot, DuckDuckBot) respect by convention. You do not strictly need one — if the file is absent, crawlers treat everything as allowed. But having a robots.txt lets you block low-value pages (admin areas, search results pages, duplicate content), add your sitemap URL so crawlers find it automatically, and set crawl-delay to protect server resources.

robots.txt blocks crawling, not indexing. A page blocked by Disallow can still appear in Google search results if other sites link to it — Google may index the URL without crawling its content, showing a result with no title or description. To fully prevent a page from appearing in search results, use the noindex meta tag: <meta name="robots" content="noindex">. For maximum coverage, use both: block crawling in robots.txt and add noindex to prevent indexing through direct discovery.

It must be in your website's root directory and accessible at https://yourdomain.com/robots.txt. Crawlers look for it at exactly that URL — a file in a subdirectory (e.g. /blog/robots.txt) will be ignored. For a subdomain, each subdomain needs its own robots.txt at its own root (e.g. https://blog.yourdomain.com/robots.txt). After uploading, verify by visiting the URL directly in your browser.

Disallow tells crawlers not to access a specific path. Allow overrides a Disallow for a more specific path within the same user-agent block — useful when you want to block a folder but allow a specific file inside it. For example: Disallow: /private/ then Allow: /private/public.html permits only that one page. When both rules match a URL equally specifically, Allow takes precedence. Without any Allow or Disallow directives, everything is permitted by default.

No. A common mistake is adding Disallow: /*.css and Disallow: /*.js to robots.txt. Googlebot needs to fetch CSS and JavaScript to render your pages and understand their content. Blocking these files can cause Google to see a broken version of your site, which may hurt your rankings. Only block files and paths that you genuinely do not want crawled — admin areas, internal search result pages, duplicate filtered URLs, staging paths.

Crawl-delay sets a minimum number of seconds a crawler should wait between requests to your server. For example, Crawl-delay: 10 tells the bot to pause 10 seconds between page fetches. This reduces server load from aggressive crawlers. Note that Googlebot ignores Crawl-delay in robots.txt — to control Googlebot's crawl rate, use Google Search Console's crawl rate settings instead. Crawl-delay is respected by Bingbot, Yandex, and many smaller crawlers.

Yes. Each User-agent block applies only to that crawler. User-agent: * applies to all crawlers as a default. You can then add specific blocks that override the defaults — for example, User-agent: Googlebot with its own set of Allow/Disallow rules, and User-agent: Bingbot with different rules. When a crawler finds multiple matching blocks (a specific one and the wildcard), it follows the most specific match. Add multiple user-agent blocks using the "Add User-Agent Block" button.

No. All configuration and file generation happens in your browser with JavaScript. Your URLs, paths, and sitemap addresses never leave your machine. There is no server-side processing, no storage, and no accounts. Copy the result or use Download to save the file — once you close the tab, the configuration is gone.

What is a Robots.txt Generator?

A robots.txt generator helps you build the robots.txt file that controls which parts of your site search engine crawlers can access. Instead of writing the syntax by hand, you pick user agents, add allow/disallow rules, drop in your sitemap URLs, and the tool generates the file for you.

Key Features

Multiple user-agent blocks with different rules per crawler. Quick-add buttons for common paths like /admin/, /api/, and /tmp/. Sitemap URL management. Crawl-delay configuration. Built-in validation to catch syntax errors before deploying. Presets for allow-all, block-all, and block-folders scenarios.

Common Use Cases

Blocking admin panels and API endpoints from crawlers. Adding sitemap URLs so search engines find all your pages. Setting different rules for Googlebot vs other bots. Adding crawl delay for bots that hit your server too hard.

Tips

Always include your sitemap URL. Don't block CSS and JS files that search engines need to render your pages. Test your robots.txt with Google Search Console's robots.txt tester. Remember that robots.txt is public, so don't use it to hide sensitive URLs.

Privacy

Everything runs in your browser. No URLs or rules are sent to any server.

Security and Privacy

Your data security is our priority

Local Processing

All processing happens in your browser

No Data Transfer

Your data is not sent to our servers

No Data Storage

No data is stored or shared

SSL Encryption

SSL encryption for secure connection

Next Step

Also on MoreOnlineTools