What is Robots.txt?
A robots.txt file is a plain text file placed at the root of your website (e.g., example.com/robots.txt) that communicates with search engine crawlers and other web robots. It follows the Robots Exclusion Protocol (REP), telling crawlers which pages or sections of your site they are allowed or not allowed to access.
When a search engine bot like Googlebot visits your website, the first file it looks for is /robots.txt. This file acts as a set of instructions, guiding crawlers on how to interact with your site content.
Basic Robots.txt Example
User-agent: * Allow: / Disallow: /admin/ Disallow: /private/ Sitemap: https://example.com/sitemap.xml
Why Robots.txt Matters for SEO
Your robots.txt file plays a crucial role in how search engines interact with your website. Here's why it matters:
Crawl Budget Management
Search engines allocate a limited crawl budget to each website. Robots.txt helps you direct crawlers to your most important pages, ensuring they don't waste time on low-value URLs like admin panels, search results pages, or duplicate content.
Indexing Control
While robots.txt doesn't directly control indexing (use noindex for that), it controls what gets crawled. Preventing crawling of certain pages is the first step in managing what appears in search results.
Server Load Reduction
By blocking crawlers from accessing resource-heavy pages or unnecessary sections, robots.txt helps reduce server load, improving performance for real users and other crawlers.
Sitemap Discovery
Including your sitemap URL in robots.txt provides a direct signal to search engines, helping them discover and index all your important pages faster and more efficiently.
What We Check
Our robots.txt checker evaluates your file against the signals that matter most for SEO, grouped from must-fix down to polish. Here's what each one means:
Must-fix
1. File Exists
Your robots.txt file must be accessible at the root of your domain. Without it, crawlers have no guidance on how to interact with your site, potentially missing important directives about crawling permissions and sitemap locations.
2. User-Agent Directive
At least one User-agent directive must be present. This tells specific crawlers which rules apply to them. The wildcard User-agent: * applies rules to all bots.
3. No JS/CSS Blocking
Blocking JavaScript or CSS files prevents search engines from rendering your pages correctly. Google needs to execute JS and load CSS to understand your content and layout, so blocking these resources severely hurts your rankings.
Recommended
4. Sitemap Reference
Including a Sitemap: directive in your robots.txt helps search engines discover your sitemap without needing to guess its location. This improves crawl efficiency and content discovery.
5. Sitemap Accessible
If your robots.txt references a sitemap, that sitemap must actually be accessible and return valid XML. Broken sitemap references waste crawler resources and prevent efficient page discovery.
6. Proper File Structure
Your robots.txt must follow the syntax defined in RFC 9309 (the Robots Exclusion Protocol standard). Proper structure prevents parsing errors and ensures all crawlers correctly interpret your directives.
Polish
7. File Size Under 500KB
Search engines may truncate or ignore robots.txt files larger than 500KB. Keep your robots.txt concise and focused on essential directives. Most well-configured robots.txt files are well under 10KB.
Common Robots.txt Mistakes
Even experienced webmasters make these mistakes. Here are the most common robots.txt errors that can hurt your SEO:
Blocking CSS and JavaScript
Using Disallow: /*.css$ or Disallow: /*.js$ prevents Google from rendering your pages. This was common advice in the early 2000s but is now harmful. Google needs these resources to properly evaluate your content.
Blocking Googlebot Entirely
Using User-agent: Googlebot with Disallow: / blocks all Google crawling. This will remove your entire site from Google search results. Only use this intentionally (e.g., staging environments).
Missing Sitemap Directive
While not strictly required, omitting the Sitemap: directive means search engines must discover your sitemap through other means (like Google Search Console). Adding it provides a reliable fallback for all crawlers.
Using Robots.txt Instead of Noindex
Blocking a page via robots.txt prevents crawling but doesn't prevent indexing. If other sites link to a blocked page, Google may still index it (with limited information). Use noindex meta tags for pages you truly want excluded from search results.
Overly Complex Rules
Having hundreds of disallow rules can make your robots.txt difficult to maintain and debug. It also increases the file size unnecessarily. Keep rules concise by using directory-level blocking instead of individual page rules where possible.
HTTP 429 & 5xx Errors on robots.txt
If your server returns a 429 (Too Many Requests) or 5xx (Server Error) when crawlers try to fetch robots.txt, search engines will temporarily treat your entire site as blocked. This means no pages will be crawled until the error resolves. Ensure your robots.txt endpoint is always available and not behind aggressive rate limiting.
Wrong Content-Type for robots.txt
Your robots.txt must be served with a Content-Type: text/plain header. Some servers or SPAs incorrectly serve it as text/html, which causes certain crawlers to reject the file entirely. Verify your server configuration sends the correct Content-Type.
2025 Robots.txt Best Practices
The landscape of web crawling is evolving rapidly with AI crawlers and updated standards. Here are the current best practices:
AI Bot Management
With the rise of AI models, new crawlers like GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended, and Bytespider (ByteDance) are accessing websites to train language models. You can selectively block these in robots.txt:
# Block AI training crawlers User-agent: GPTBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: Google-Extended Disallow: / # Allow regular search crawlers User-agent: Googlebot Allow: /
Consider your content strategy before blocking AI crawlers — some also power AI search features that could drive traffic to your site.
RFC 9309 Compliance
RFC 9309, published in September 2022, is the first formal internet standard for the Robots Exclusion Protocol. Key requirements include:
- The file must be served at
/robots.txton the root domain - Content-type should be
text/plain - File size should not exceed 500 KiB (kibibytes)
- Lines are separated by CR, LF, or CRLF
- The
Allowdirective is officially recognized (not just a de facto standard) - Crawlers should cache the file for a reasonable period
Regular Auditing
Audit your robots.txt quarterly or whenever you make significant site changes. Common triggers for a re-audit include launching new sections, migrating domains, updating your CMS, or noticing unexpected indexing behavior in your SEO audit.