CONTACT US
info@toolspivot.comADDRESS
Ward No.1, Nehuta, P.O - Kusha, P.S - Dobhi, Gaya, Bihar, India, 824220Build a robots.txt that does what you mean: current search and AI crawlers, ready-made starting points, wildcard patterns, and checks that catch the mistakes which take sites out of Google. It is built in your browser.
We request the robots.txt of that site from our server and show exactly what came back.
Leave a robot on "General rules" unless you need it treated differently.
| * stands for any run of characters, including none. $ marks the end of the address. Without it a rule matches everything that starts with the path. | |
/*.pdf$ | every address ending in .pdf |
/*? | every address that has a query string |
/thank-you$ | that one page, but not /thank-you/more or /thank-you?x=1 |
/*/feed/ | a feed in any folder |
/*?sort= /*&sort= | sorted listings, wherever the parameter appears |
/private/ | the folder and everything in it. /private (no final slash) would also match /private-notes |
| When two rules match, the longer one wins. If they are the same length, Allow wins. Paths are case-sensitive: /Page and /page are different. | |
Google ignores Crawl-delay. Bing and some others follow it.
Used to show where the file goes and to complete sitemap addresses.
A robots.txt generator is a free online tool that builds properly formatted crawler instruction files for your website's root directory. It produces valid User-agent, Disallow, Allow, Sitemap, and Crawl-delay directives through a point-and-click interface, so you don't need to memorize syntax or worry about typos. ToolsPivot's Robots.txt Generator supports 15+ individual search engine bots and lets you set per-crawler rules, restricted directories, and sitemap references in under a minute, with no account required.
Set the default crawl rule: Choose whether all robots should be "Allowed" or "Refused" by default. This sets the baseline behavior for every crawler that visits your site.
Pick a crawl delay: If your server struggles with heavy bot traffic, select a delay interval (5, 10, 20, 60, or 120 seconds). Leave it on "No Delay" for most sites.
Add your sitemap URL: Paste the full address of your XML sitemap. If you don't have one yet, the sitemap generator can create one for you. Leave the field blank if your sitemap isn't ready.
Configure individual bots: ToolsPivot lists 15 specific crawlers, including Googlebot, Google Image, Google Mobile, MSN Search, Yahoo, Baidu, and Naver. Set each one to "Allowed," "Refused," or "Same as Default" depending on your needs.
Enter restricted directories: Type the folder paths you want blocked from crawling, one per line. Paths are relative to the root and need a trailing slash (for example, /wp-admin/ or /checkout/).
Copy and upload: The generated robots.txt output appears instantly. Copy the text, save it as a file named robots.txt, and upload it to your website's root directory via FTP or your hosting file manager.
This tool converts your preferences into a properly structured robots.txt file that follows the Robots Exclusion Protocol (RFC 9309). Here's what you get from the interface:
Global allow/refuse toggle: One setting controls the default behavior for all bots at once. This produces the User-agent: * directive with either an empty Disallow (allow all) or Disallow: / (block all).
15 individual bot controls: Separate dropdown menus for Googlebot, Google Image, Google Mobile, MSN Search, Yahoo, Yahoo MM, Yahoo Blogs, Ask/Teoma, GigaBlast, DMOZ Checker, Nutch, Alexa/Wayback, Baidu, Naver, and MSN PicSearch. Each can override the global default.
Crawl-delay configuration: Five preset delay options (5s, 10s, 20s, 60s, 120s) keep aggressive crawlers from overloading your server. Bing and Yandex respect this directive; Google ignores it in favor of Search Console settings.
Sitemap declaration: A dedicated field adds the Sitemap: directive so crawlers find your XML sitemap directly from the robots.txt file.
Restricted directory input: Up to 7 directory paths can be entered to generate Disallow rules. The tool adds proper formatting and trailing slashes automatically.
Instant output preview: The generated file appears in a text box as soon as you click the button. Copy it directly or save it as a .txt download.
No syntax guessing: A single misplaced slash in a hand-coded robots.txt can block your entire site from Google. The generator handles formatting, so the output is always valid against RFC 9309 specifications.
Per-bot control: Most free generators only give you a wildcard User-agent. ToolsPivot lets you set different rules for 15 named crawlers, which matters when you want Googlebot to index everything but Baidu to stay out.
Zero registration: No email, no account, no trial period. Open the page, configure your rules, and grab the output. That's it.
Crawl budget savings: Blocking low-value directories (admin panels, search result pages, tag archives) focuses crawler attention on pages that actually need to rank. Pair this with a full SEO audit to see where your crawl budget goes.
Server protection: The crawl-delay feature keeps bots from hammering small hosting plans. A 10-second delay between requests can prevent 503 errors during traffic spikes.
Works with any platform: The output is plain text that works on WordPress, Shopify, Magento, Wix, custom-built sites, and anything else with a web-accessible root directory.
Sitemap integration built in: Adding a Sitemap directive inside robots.txt is how Google discovers your pages faster. The field pre-formats the line correctly, saving you from common URL formatting mistakes. Combine it with page authority checks to verify your key pages are getting the crawl attention they deserve.
The output from ToolsPivot's generator contains four main directive types. Understanding each one helps you verify the file before uploading it.
User-agent identifies which crawler a rule applies to. An asterisk (*) targets all bots. Specific names like Googlebot or Bingbot let you write rules that only apply to one search engine. Each User-agent line starts a new rule group, and all Disallow/Allow lines below it belong to that group until the next User-agent appears.
Disallow blocks a specific path. Writing Disallow: /wp-admin/ prevents bots from crawling anything inside that folder. An empty Disallow (with no path after it) means "allow everything," which trips up beginners who assume it means "block everything." The distinction matters: Disallow: / blocks your whole site, while Disallow: (empty) blocks nothing.
Allow creates exceptions inside blocked directories. If you disallow /wp-admin/ but need admin-ajax.php accessible for WordPress functionality, you add Allow: /wp-admin/admin-ajax.php above the Disallow line. Google processes the most specific matching rule, so the Allow wins for that single file.
Crawl-delay tells compatible bots to wait between requests. A value of 10 means "wait 10 seconds between page fetches." Google doesn't follow this directive (use Google Search Console's crawl rate setting instead), but Bing, Yandex, and several smaller crawlers do.
After generating your file, test it using Google Search Console's robots.txt report or a third-party validator. You can also check how search engines view your site with the spider simulator to confirm nothing important is accidentally blocked.
About 22% of websites have at least one robots.txt error, according to SEO audit data from large-scale crawl studies. Some mistakes are subtle. Others can wipe your site from search results overnight.
Blocking your entire site by accident. This happens more than you'd expect. Someone types Disallow: / under User-agent: * and forgets that the slash means "everything." On staging sites, that's intentional. On production? It's a disaster. Always double-check that your production robots.txt doesn't carry over staging rules.
Blocking CSS and JavaScript files. Years ago, SEO advice said to block /wp-content/ and /wp-includes/ from crawlers. That advice is outdated. Google needs to render your pages the same way a browser does, and blocking stylesheets or scripts prevents that. If Googlebot can't render your page, it can't rank it properly. Run a page speed check after updating your robots.txt to verify nothing broke.
Using robots.txt to hide pages from search results. Blocking a URL with Disallow stops crawling, not indexing. If other sites link to a page you've disallowed, Google can still index that URL based on the anchor text alone. For pages you truly want hidden from search results, use a noindex meta tag or password protection instead.
Forgetting case sensitivity. Path matching in robots.txt is case-sensitive. /Photos/ and /photos/ are two different directories. If your server uses mixed-case folder names, your Disallow rules need to match exactly.
Missing the trailing slash on directories. Disallow: /admin blocks anything starting with /admin, including /administrator/ and /admin-tools/. Disallow: /admin/ blocks only the /admin/ folder and its contents. The trailing slash controls scope, and getting it wrong either overblocks or underblocks. Check your index status after any robots.txt change to catch problems early.
Yes, 100% free with no usage caps or registration. Open the tool, configure your settings, and copy the generated output. There's no premium tier or feature gating. You get the full set of 15 bot controls, crawl-delay options, and sitemap integration at no cost.
Place the file in your website's root directory so it's accessible at yourdomain.com/robots.txt. On WordPress, you can upload it via FTP to the same folder that contains wp-config.php. On Shopify, edit the robots.txt through the theme's robots.txt.liquid file. Most hosting control panels (cPanel, Plesk) have a file manager that lets you upload directly.
Not directly, but it improves crawl efficiency. Blocking low-value pages (admin areas, internal search results, duplicate parameter URLs) lets search engines spend their crawl budget on pages that actually drive traffic. Sites with thousands of pages see the biggest impact because crawlers have limited time per visit. Run a broken link check alongside your robots.txt update for a cleaner crawl path.
No. Robots.txt prevents crawling, not indexing. If external sites link to a page you've blocked with Disallow, Google can still show that URL in search results using information from those links. To remove a page from search results entirely, add a noindex meta tag or use Google Search Console's URL removal tool. The meta tag generator can help you build correct noindex tags.
Review it whenever you change your site's URL structure, add new sections, migrate domains, or install plugins that create crawlable pages. For most sites, a quarterly review is enough. E-commerce stores with frequent product additions should check monthly to make sure new category pages aren't accidentally blocked.
A robots.txt file tells crawlers where not to go. A sitemap tells crawlers where they should go. They work together: the robots.txt file points to your sitemap URL, and the sitemap lists every page you want indexed. Both belong in your root directory, and both should stay updated.
Google ignores the Crawl-delay directive entirely. To control Googlebot's crawl rate, use the crawl rate setting in Google Search Console. Bing, Yandex, and several smaller search engines do follow Crawl-delay, so it's still worth setting if your server is resource-limited.
Yes. AI training crawlers from OpenAI (GPTBot), Anthropic (ClaudeBot), and Common Crawl (CCBot) respect robots.txt rules. Add a User-agent: GPTBot section with Disallow: / to block OpenAI's crawler from accessing your content. ToolsPivot's generator handles standard search engine bots; for AI-specific rules, add them manually to the generated output before uploading.
Block /wp-admin/ but allow /wp-admin/admin-ajax.php. Many WordPress themes and plugins rely on admin-ajax.php for front-end functionality like form submissions and infinite scroll. Blocking it entirely can break features visitors interact with. The correct syntax is Allow: /wp-admin/admin-ajax.php followed by Disallow: /wp-admin/ in that order.
Use Google Search Console's robots.txt report to verify that Google can fetch and read your file. You can also type yourdomain.com/robots.txt in any browser to confirm the file is accessible. For a more thorough check, run the schema markup generator to add structured data that reinforces how search engines interpret your site.
Yes. Each subdomain needs its own robots.txt file in its own root directory. The file at www.example.com/robots.txt only applies to www.example.com. A separate subdomain like blog.example.com requires its own robots.txt at blog.example.com/robots.txt. This is part of the Robots Exclusion Protocol defined in RFC 9309.
Search engines crawl everything they can find. No robots.txt is treated the same as a file that allows all access. For small sites with fewer than 500 pages, this is usually fine. Larger sites benefit from a robots.txt because it helps crawlers prioritize important pages over admin panels, staging content, and duplicate URLs. Check your site's domain authority and keyword rankings to measure the impact of crawl management changes.
CONTACT US
info@toolspivot.comADDRESS
Ward No.1, Nehuta, P.O - Kusha, P.S - Dobhi, Gaya, Bihar, India, 824220