The proportion difference of AI crawlers in different industries is very large, who should we compare with?
The proportion difference of AI crawler across different industries is very large, who should we compare with? We should compare with the baseline of the same industry and purpose, and not take the average value of the whole site as a reference. The measurement of a document covering 1,103 sites on the day shows that only 18.9% of the sites explicitly block at least one major AI crawler; however, when broken down by industry, the blocking ratio of news and media sites is 61.0%, and for development tool sites it is only 2.9%. Applying the same average value to these two industries will lead to completely opposite conclusions.
Why should the blocking rate be analyzed by industry?
Another issue with the average value of the entire site is that it mixes two completely different strategies. The position of the publishing industry comes from content as an asset: the text is taken in bulk for model training, which is equivalent to giving one's own production costs to the other party, and therefore the interception ratio is naturally high. Another analysis of large publishing institutions on the same day gave the strength of this industry, with sixty out of seventy surveyed publishing institutions explicitly restricting at least one type of AI crawler that has been configured, and fifty-seven of them are completely blocked.
Development tools and document sites are opposite. Their income comes from being searched and cited, and the appearance of their own interface descriptions and tutorials in the answers is effective traffic, so the interception rate is very low. Determine your position first, whether you are closer to one side: selling content, or attracting customers through content.
Training and retrieval should be separated.
The premise of grouping is to know the division of labor between two types of crawlers. The criteria on the day of verification were written very clearly: training and retrieval are now separated into separate crawling agents, which can block GPTBot, Google-Extended, and ClaudeBot used for training, while retaining the qualification for AI retrieval citations. Writing both in the same rule block is the most common source of misjudgment - originally intended to reject corpus collection, but as a result, the citation position in the answer was also lost.
| Intention | The desired effect | Handling of robots.txt | Judgment basis |
|---|---|---|---|
| Rejecting corpus collection | Not for training | Separately blocking training agent entries | Is the text your sellable asset? |
| Keep the cited content | Enter the answer source | Allow search agents to pass | Whether traffic is brought by answer exposure? |
| Protect user data | Do not capture interaction with the background | Precisely block the path prefix | Whether it contains login, forms, and private content? |
| Observe unknown agents | Take a good look before deciding | Conservative release of public paths | Whether there is UA and request volume records |
Be aware that there is also a hierarchy within the publishing industry: complete blocking and partial restriction are two positions, and the choices of institutions of different scales in the same industry are also different. When benchmarking, choose the level that is close to your content form, not just the industry name.
What if you choose the wrong benchmark
The three most common mistakes.
The first type is to take the practice of large stations as a baseline. The blocking of leading publishing institutions relies on brand and bargaining power, and they can withstand the results of being omitted by AI answers; small and medium-sized sites rely on answer exposure to bring visits, and copying the blocking is equivalent to giving up traceable traffic.
The second type is to treat the average of the entire site as its own industry's number. The above two differences show that such misreading is easy to occur: the interception rate of less than 20% of the entire site, when applied to media sites, will underestimate the risk, and when applied to development tool sites, it will overestimate.
The third type is to only look at the interception without looking at the output. Blocking the crawling agent does not mean blocking the collection, and the content of the page can still be bulkily taken away in other ways.
How to determine the strategy of this site
Determining the strategy requires two steps: one for the access layer and one for the content layer, with each layer handling its own affairs.
The access layer uses robots.txt to define boundaries: group by family, separate training and search classes, and accurately block background paths and result pages. After changing the rules, check the logs to confirm that the families allowed are consistent with expectations.
The content layer manages whether the collected content can be used directly after collection. Anti-crawling interference codes are inserted into the text to be unobtrusive to individuals and effective for bulk copying,配合sensitive word and content review, so that the text taken away does not retain its original form. The significance of this layer lies in: robots.txt can only take effect on agents that comply with the protocol, while interference codes face those who do not comply with the protocol.
Review it once at the end of the quarter. The industry baseline and the agent list are changing, and the grouping that was reasonable last year may not be suitable this year.
Common questions
There is no concept of traffic budget, do you need to manage the crawler?Yes. Web scraping requests also consume server resources, and unrestricted batch requests will occupy the response of real users.
Is it the safest to block all of them?No. Blocking search agents will also lose the opportunity to be cited, and collection will not stop because of this, but will become an untraceable, uncontrolled part.
Will the interference code affect the reading of real people?Proper configuration will not affect it. Its goal is to distort the entire copied text, while the presentation layer remains the same for normal access.
How often should the rules be reviewed?It is recommended to do so quarterly. The renaming and addition of agents are frequent, and too long an interval will cause the rules to deviate from the actual distribution.