If an AI crawler ignores your robots.txt rule, the file cannot stop it: robots.txt asks compliant crawlers to stay away; it is not an access-control mechanism. To keep content private, require authentication or remove it from public access. To block requests, use controls at your CDN, web application firewall (WAF), or server edge. First confirm the rule is being served for the right host, then identify the requester and preserve the evidence.
What robots.txt can—and cannot—do
The Robots Exclusion Protocol is a way for site owners to state which paths they prefer crawlers to avoid. RFC 9309 makes the boundary explicit: “These rules are not a form of access authorization.” A crawler can disregard the request, and the file neither authenticates visitors nor technically prevents a request. RFC 9309
As an Amazon Associate I earn from qualifying purchases.
That distinction matters because different goals need different controls. A crawler-specific robots rule can reduce crawling by bots that honor it. A noindex directive can address search indexing, but it does not make a page private. Authentication or removal is the appropriate boundary for material that must not be publicly accessible; a CDN, WAF, firewall, or bot-management policy can deny matching requests.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the control that matches your goal
| Goal | Control | What it does—and its limit |
|---|---|---|
| Ask compliant crawlers to avoid a path | Crawler-specific robots.txt rule |
Communicates a preference; does not compel a noncompliant client. RFC 9309 |
| Keep a page out of Google Search | Allow Googlebot to fetch the page and see a noindex directive |
Addresses indexing, not access. A robots.txt block can stop Googlebot from seeing the directive, and a blocked URL may still appear in search results. Google robots.txt documentation Google Search technical requirements |
| Keep content private | Require authentication or remove the content from public service | Controls access rather than asking a crawler to cooperate. Robots.txt and noindex are not privacy boundaries. Google robots.txt documentation |
| Deny requests at the network edge | CDN, WAF, firewall, or bot-management rule | Can block matching requests, but may also affect legitimate traffic; check what identities and purposes the policy distinguishes. Cloudflare bot concepts Cloudflare WAF custom rules |
Check that the rule applies to the site the crawler requested
- Fetch the production file. Request
/robots.txtat the exact public host and protocol involved. RFC 9309 specifies the file at the top level of a service. A rule on one subdomain does not automatically cover another. RFC 9309 - Check the scope. Confirm the rule names the intended crawler product token and disallows the intended path. Google explains that its robots rules apply to the host, protocol, and port where the file is hosted. Google robots.txt documentation
- Verify what the public actually receives. A CMS, CDN, or managed robots feature may serve a generated file that differs from the origin copy. Check the response visible through the production site and the edge policy currently in effect. Cloudflare documents managed robots features separately from request-blocking controls. Cloudflare bot concepts Cloudflare WAF custom rules
- Choose the crawler identity deliberately. Check whether the vendor separates search, training, and other retrieval. A rule aimed at one purpose may not cover another product token from the same company.
Distinguish crawler products before blocking them
OpenAI documents OAI-SearchBot for search and GPTBot for training; those identities serve different purposes. OpenAI bot documentation Anthropic documents ClaudeBot and explains how to disallow it; its instructions say to apply the restriction on each subdomain you want covered. Anthropic crawler guidance
#1 Best Overall
Do not treat a user-agent string as proof of who sent a request: it can be misleading or spoofed. Google recommends verifying Googlebot with reverse DNS or by matching source IP addresses against its published ranges. For other vendors, consult their current identity and verification guidance where available, then compare it with your logs. Googlebot verification guidance
Before deploying a long-lived block, decide whether you want to affect training, search visibility, or both. Blocking a search crawler can reduce a service’s ability to retrieve site content for search; blocking training crawlers has a different purpose. Vendor names and documented purposes can change, so recheck their current documentation when maintaining rules.
Rank #2
Block requests at the edge when a preference is not enough
A CDN or WAF can deny requests that match a policy rather than relying on a crawler to follow robots.txt. Review the active policy at the edge as well as the origin file, and test for false positives that could affect search crawlers, user-requested fetchers, or ordinary visitors. Check whether the available controls distinguish bot categories and purposes before applying a broad block. Cloudflare documents behavior-based AI bot policies and WAF custom rules, but configuration and availability can vary. Cloudflare bot concepts Cloudflare WAF custom rules
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallVendor defaults are not fixed: Cloudflare documents a default change for new domains on September 15, 2026. Confirm the current setting and its scope in your account rather than assuming a default applies to every domain or existing configuration. Cloudflare bot concepts
Rank #3
- 【Tired of constantly searching for or resetting your passwords?】 MOSA BEAR password keeper book is the perfect solution for you! This password book provides a dedicated place to securely store all your important website addresses, emails, usernames and passwords, ensuring your information is protected and easy to find. The well-designed log pages help you manage multiple accounts in a systematic way, saying goodbye to password confusion.
- 【Premium Design & Password Security】 The password book with alphabetical tabs features an anonymous cover design with no title on the cover, effectively avoiding information exposure. The password keeper design is specifically designed with password security in mind, providing space to record password hints instead of writing directly on the password itself, further protecting your important information.
- 【Simple Layout and Plenty of Space】The 160-page password logbook is designed to provide ample space to record passwords and other important information. It can store up to 414 passwords. In addition, it provides extra pages to record other information, such as email setup, card information, computer operating system information, software licenses, and more. The journal also includes 3 blank pages at the end for you to add additional notes.
- 【Palm-sized Size & Premium Quality】 This password notebook has an ideal size, 4.3" x 5.7", for carrying around, whether in a purse or pocket. Its sturdy glue binding allows the notebook to unfold smoothly and is more comfortable to use. The inner pages are made of high-quality 100GSM thick paper, which can effectively reduce ink penetration and ensure a cleaner and neater writing effect. The overall design takes into account both portability and durability, making it an ideal choice for recording important passwords.
- 【A-Z Tabs for Quick Search 】Our password book comes with alphabetical tabs to help you find the password you need quickly and easily. Alphabetically organized tabs ensure that you can quickly flip to the right section, saving you the time and hassle of searching for your password.
Keep an incident record before changing rules
Capture the evidence while the relevant requests and settings are still available. Retain unmodified logs where possible and note any rate limits, challenges, or blocks already applied.
- Timestamp and timezone for each request.
- Requested URL or path, response status, source IP, user-agent string, and request headers available in your logs.
- The exact
robots.txtversion served at the time, including the host it came from. - Relevant CDN or WAF events, active rules, and any changes made during the incident.
These details can help you distinguish a declared bot identity from the actual requester and diagnose which layer handled the request. They also give qualified counsel a factual record if you are considering a legal dispute. The sources here establish the technical limits of robots.txt, not a universal legal remedy: whether conduct creates a claim depends on jurisdiction and the circumstances. Do not assume that ignoring robots.txt alone necessarily amounts to trespass, copyright infringement, or another legal violation.
Quick Recap
Best Value
Rank #4
- Bookbound planner helps you keep track of passwords and favorite websites
- Room for over 200 entries; 3.5 x 6 inch page sizes
- User name and security questions field
- Tips for what makes a strong password; web resources; notes pages
- Printed on quality paper containing 30% post-consumer waste; black simulated leather cover; 3.63 x 6.13 x .21 inches
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

