Why would the proportion of different AI crawlers intercepted by the same site differ by a few points?
Why does the blocking ratio differ by a few points for the same site blocking AI crawlers from different manufacturers? The difference is mostly due to the rule writing, not the difference in manufacturer behavior. The robots file matches by user group name, and each proxy has more than one identifier, the rules are written differently, and the blocking rate of the same site on different manufacturers naturally separates. Taking the difference in proportion as evidence that 'some crawler is stronger' is the most common misreading of this kind of statistics.
Where does the difference come from, rule writing or manufacturer behavior?
Write rules according to the identifier, only the one written in will be hit. The other entries of the same group, as long as the name does not match, will be caught as usual. The two apertures at the whole-site dimension exactly show this gap: blocking GPTBot's domain accounts for 7.9%, while blocking any one AI crawler accounts for 10.3%, with a difference of 2.4 percentage points between the two apertures. This part of the site is the batch that only wrote one, and it is not that they do not want to block, but that the rules did not cover the rest of the identifiers.
Two types of holes in user group matching
One type is a misspelling. Manufacturers use both main identifiers and derived identifiers at the same time, and the rule of writing only the main identifier is reflected in the report as 'This one blocks less'. Another type is overwriting: to save trouble, the whole station is blocked, resulting in the retrieval class and real-time retrieval class being turned off together, and the report shows 'Blocks cleanly', but the station is empty. The correction direction of the two types of pitfalls is different, so first confirm which type you belong to before making the rule.
Writing style grouped by purpose
| robots writing style | The range of identified markers | Impact on visibility |
|---|---|---|
| Prohibit individual markers one by one | Only cover the one written | The rest of the same族 identifiers are picked up as usual, and the difference in proportion is amplified |
| Grouped by purpose | A group of training class, a group of retrieval class | The difference in proportion has narrowed, and the behavior is predictable |
| Prohibition in the entire station with exceptions | All agents | Retrieval and real-time retrieval are shut down together, and the entry is blocked |
| Only tighten the entrance of the station | Index layer | The body can still be captured, but the volume of collection has decreased |
The key to grouping by purpose is grouping rather than item by item: put the training class in a section, put the retrieval class in a section, put the real-time retrieval in a section, and each section is handled separately, so that subsequent adjustments have a point
The two things to look at when checking
The first is the sitemap and crawling entry. Sitemap determines which addresses are prioritized for discovery. If the addresses in the sitemap do not match the handling in the robots section, there may be a semi-closed state where the entry is blocked and the text can still be crawled, which may look like some crawler was not blocked in the report. The second is the actual crawling record: check each entry separately by manufacturer for the number of requests and the return status, and do not draw conclusions based on a full-site summary.
In AnQiCMS and similar self-built programs, the robots configuration, site map generation, and crawling records are three independent entries. Confirm these three places in turn when making changes, do not change them all at once and then test the whole thing: changing multiple layers at once results in untraceable results.
Common questions
Question: Does the difference in proportion indicate that a certain crawler has bypassed the rules? Answer: First, check if its identifier is written in the rules. Most of the differences come from omissions, not from bypassing.
Question: How to verify after grouping by purpose? Answer: Group by the request volume and return status of each manufacturer, test once before and after the change, and do not just look at the configuration text.
Ask: Does the site map need to be changed? Answer: Yes. When the entry point of the index is inconsistent with the text processing, the difference in proportion will be misread as a manufacturer's difference.