Build custom robots.txt directives, disallow paths, configure sitemaps, and manage crawler permissions with one-click copy and download. 100% free web diagnostics by AiMAEditz.
Build custom robots.txt directives, disallow paths, configure sitemaps, and manage crawler permissions with one-click copy and download.
The file must be placed in the root directory of your domain (e.g. https://example.com/robots.txt). Search engine bots will not recognize robots.txt placed in subfolders.
No. Robots.txt prevents search engines from crawling the page. However, if other websites link to that URL, Google may still index the address without snippet content. To ensure non-indexing, use the noindex robots meta tag.
Adding Sitemap: https://example.com/sitemap.xml at the bottom of robots.txt helps search engines automatically discover all your canonical URLs during initial crawl discovery.
Specify the bot user-agent (e.g., User-agent: BadBot) followed by Disallow: /, while keeping User-agent: * or User-agent: Googlebot with Allow: / directives.
Use the Disallow directive: User-agent: * followed on the next line by Disallow: /admin/ and Disallow: /cart/.
Crawl-delay requests bots to wait a specified number of seconds between requests. While Bing, Yandex, and Yahoo support it, Google ignores crawl-delay in favor of automatic crawl rate settings in Search Console.
Yes, if you disallow directories containing theme assets or scripts. Blocking CSS or JS prevents Google from rendering pages accurately, which can harm mobile rankings.
Yes. Directive names and URL paths in robots.txt are case-sensitive. Disallow: /Admin/ will not block crawlers from accessing /admin/.
You can test your directives using Google Search Console Robots.txt Report or Bing Webmaster Tools Robots.txt Tester before pushing changes to production.
Yes. AiMAEditz Robots.txt Generator produces clean, universal text output compatible with any CMS, static site generator, or custom web platform.