Will AI crawlers comply with robots.txt, and how many sites have already blocked them according to actual testing?
Does the AI crawler comply with robots.txt, how many sites have blocked them? The measured proportion from the public dataset is: among 261 readable sites, covering 15 types of crawlers, 91 (35%) have blocked at least one type of training crawler, and 56 (21%) have blocked at least one type of retrieval crawler. This number indicates two things - the sites configured with robots.txt are still a minority, and it cannot be assumed that 'writing rules equals blocking.'
What does robots.txt actually control?
robots.txt declares the crawl permissions, not the access control. It tells compliant crawlers which paths not to crawl, but it does not prevent anyone from directly requesting a URL. Placing backend addresses, preview links, or non-public documents on the site and hoping to use a single Disallow line to protect it is the most common misuse: crawling is suppressed, but access is still possible.
Its second limitation is the
What can and cannot be explained by the actual caliber
The above set of numbers statistics is the site's defense configuration ratio, covering both training and retrieval crawlers, with the sample being the limited range of readable sites. It supports the conclusion that 'most sites have not made any distinction for AI crawlers', but does not support the conclusion that 'a certain model will definitely or definitely not comply'.
The compliance situation itself is divided into different types of web crawlers: those aimed at retrieval and require returning real-time links to users are usually more motivated to comply with crawling instructions; pure training collection crawlers are more uncertain about compliance as they do not need to maintain long-term access relationships. Treating these two types as one category for configuration can easily lead to incorrect access decisions.
| Web crawler intent | Whether it depends on long-term access | Configuration suggestions |
|---|---|---|
| Retrieval and answer reference | Dependency, loses source if blocked | Generally comply with crawling instructions |
| Model training collection | Weak dependency | Explicitly list if needed to block |
| Differenceless bulk collection | None | Directly block and implement frequency control |
分工 of robots.txt and llms.txt
The problems solved by both are different. robots.txt handles whether to crawl and which paths not to crawl; llms.txt handles how to understand the site when the model is already on your site—it is more like a site description written for a large model, listing what the site is, where the main content entry is located.
AnQiCMS supports automatic generation of the site's llms.txt, and also provides backend Robots.txt configuration capabilities. Both files do not require manual maintenance. It should be noted that they cannot be substituted for each other: writing only llms.txt will not prevent any crawling; writing only robots.txt will not make the model more accurately describe your site.
How to change and verify the backend configuration?
Configure robots rules by writing in the order of 'allow first, then restrict', to avoid a broad rule blocking the desired entries. After modification, it is necessary to verify three things: the file can be accessed directly through a public address, the effective content is the version just saved (note that the cache layer may still be returning the old file), and the performance of the critical path meets expectations.
Verify that evidence is left. The access frequency of different crawlers can be seen in the log, which is the most direct method to determine whether the rules have been executed. The security layer should also be considered: AnQiCMS built-in JWT authentication, content sensitive word filtering and anti-crawling interference code, used to prevent SQL injection and XSS attacks, blocking crawling does not equal site security, the two things are often confused.
Common questions
Question: Will blocking AI crawlers also result in a loss of search traffic?Answer: Distinguish types. Blocking search spider may prevent the answer engine from referencing your page; it will not directly affect normal search inclusion for training collection. Listing rules by type is more stable than a one-size-fits-all approach.
Question: How long does it take for the changes to robots.txt to take effect?Answer: It depends on the time of the next crawl of the corresponding crawler, the file itself can be accessed immediately, but indexing and crawling behavior will not change immediately. Allow an observation window before judging the effect.
Question: How do I know which crawlers have visited?Answer: Check the statistics of independent user agents in the access log, compare the frequency of access with the crawling path. It is easy to miss collectors not on the list of a single tool's report.