Why would the proportion of different AI crawlers intercepted by the same site differ by a few points?

📅 2026-11-01 👁️ 0

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.

Related articles

The proportion of AI crawler interception changed between two months, is it changed by the default value of the platform or the webmaster?

The same batch of domain names has changed the proportion of AI crawler interception in two months, most of which come from the launch of platform default values, not from webmasters changing configurations one by one. By looking at the direction of change, it can be distinguished: the displacement is concentrated on the training and proxy sides, while the search class has not moved much. When comparing, first lock the same caliber and the same industry level, and then confirm the configuration of robots files, platform classification switches, and in-site exit one by one, changing one and measuring one to attribute.

2026-11-01

After a website is attacked, it is necessary to restore the backup, should the vulnerability be patched first or the data be restored first?

The order of disposal is to first cut off the entry that can be reused again, install the affected programs and extensions, and then recover from a known good backup. Restoring data will bring back the time points with backdoors, and the repeated infections are mostly caused by this. After recovery, it is also necessary to check the accounts, scheduled tasks, and modified files, and confirm whether the deleted content still stays in the recycle bin.

2026-11-01

Should the new article be submitted to the search engine actively, and which companies does this protocol cover?

The proactive submission resolves the section of

2026-11-01

Where is the difference in construction costs between static pages and dynamic sites, and who has higher post-maintenance costs?

The price range of static sites during the construction period is lower, while dynamic sites are expensive in terms of backend, database, and security patches; during the operation period, the situation is reversed, where the content update of static sites depends on technical intervention, and dynamic sites require continuous upgrades and backup work. Sites with frequent updates are more suitable for content systems with backend and scheduled publishing, separating the update actions from the development time.

2026-11-01

Is there any advertisement on the page, and will it change whether the AI crawler can read the content?

Whether there is advertising on the page will indeed change whether the AI crawler can read the content: the new platform default value treats whether to display advertising as a judgment condition, the pages with advertising are intercepted by default for training and proxy types, and the search type continues to pass. This rule is not in the robots file, but occurs on the platform side, so there may be two sets of visibility in the same site with advertising templates and without advertising templates, and it should be checked separately according to the template.

2026-11-01

The new default intercept value only manages new domains, old domains need to be moved manually.

The new default blocking value on the platform only applies to newly connected domains, while the old domains already on the platform need to manually fetch and control this layer: first confirm the current effective values for training, proxy, and search categories separately, then merge them with the existing robots rules on the site, and finally verify with the real return status. The default value will not automatically overwrite existing configurations, assuming it has already taken effect is the most common judgment error.

2026-11-01

Why do we need to tighten the registration entry first and then patch the multi-site user registration open?

The reason why a multi-site with open user registration needs to tighten the registration entry first and then patch it is because the triggering conditions of this kind of risk are written together: registration is open, and ordinary users can create new sites. Closing the registration during the patch window period and restricting the permission to create new sites can directly cut off the attack entry; after patching, it is also necessary to check back on the sites that have been created and to synchronize the backup and permission review.

2026-11-01

Why is it necessary to limit server access to internal network addresses in the place where external links can be filled in the background?

The place where external links can be filled in the background needs to limit the server's access to the internal network address because the server will replace the user to retrieve this address: Once the link verification is bypassed, the request can be sent to the link-local address range, exposing the internal network service to external inputs. The verification should be done both at the time of writing and before the request, and then supplemented by the outgoing network limit, especially for entry points such as importing and remote image retrieval, which should be separately controlled.

2026-11-01