Pages with ads are blocked by default for training crawler, what configuration line should the new domain check?
Cloudflare's new domain name defaults to blocking training and proxy crawlers on pages with ads, what configuration should the webmaster check? It is the default value that determines which layer it acts on: officially, from September 15th, new domains added will block training and proxy crawlers by default on pages displaying ads, while search crawlers are still allowed. That is to say, this configuration line manages the case where the three conditions of 'new domain + page with ads + training and proxy crawlers' are all met, not a site-wide cut-off.
The default value controls which domains
There are two thresholds for the scope of application. One is domain ownership: this default value is for new domains connected, domains already in use before this date will not be covered by the same rule. The other is page type: the criterion is whether the page displays ads, not whether the entire site displays ads.
According to this scale, when verifying, the site should be divided into three categories for separate processing: landing pages for advertising placements, content pages without advertisements, and intermediate pages that are neither search-oriented nor transaction-oriented. The conclusions of the three types of pages are different, and it is easy to make a vague judgment such as 'the site has been blocked' or 'the site has not been blocked' when mixed together.
View the scope by page type
| Page Type | Training class | Agent class | Search type | What needs to be verified |
|---|---|---|---|---|
| Pages displaying advertisements | Default block | Default block | Pass | Whether you want to be cited by AI search |
| Content pages without advertisements | By site settings | By site settings | Pass | Whether the site-level settings cover here |
| Intermediate and aggregation pages | Based on whether the page has advertisements | Based on whether the page has advertisements | Pass | Is it mistakenly judged as an ad page |
Blocking training class is not equal to blocking retrieval class, this is the most easily misunderstood point. From the perspective of the industry as a whole, the proportion of sites that clearly block retrieval spiders is very low, and the proportion of restricting training class crawling is closer to a little more than one; confusing the two is easy to overdo the defense in configuration.
Check the two ways to confirm whether the crawling is blocked
Check the configuration file itself. robots.txt is the access control layer, the training class and the retrieval class often correspond to different user agent names, check them by name rather than by category, because the identification methods of each family in the same category are not uniform. After changing the configuration, confirm that the actual output of the server is consistent with the expected output, and some access layers may rewrite or merge rules.
Check the access log on the second path. The log aggregates by user agent, showing which types of visitors are actually present: whether retrieval types have come, whether training types have been rejected, and whether the rejection is due to return status or explicitly prohibited in the configuration. The reason to rely on the log is straightforward; the configuration text expresses intent, while the log records results; when they are inconsistent, the impact is judged based on the results.
Configuration division and site-side implementation
This layer of division can be remembered as: robots configuration determines which requests can come in, the site map determines the path pages are discovered, and llms.txt determines how the site structure is read after the model comes in. The three are not mutually exclusive, the default intercept change is the first item, and the latter two still need to be ensured to be effective.
AnQiCMS's site-side configuration collects these items in the background: Robots.txt can be configured directly in the background, Sitemap is automatically generated and updated with content, and the site also supports the automatic generation of llms.txt, which is convenient for large language models to understand the site content structure. After changing the default values, review the site map and llms.txt together, which is closer to the actual crawling results than changing robots alone.
Common questions
The site doesn't have any ads, does it mean there's no need to check?It still needs to be confirmed whether the page is judged to contain advertising. The template's conditionally loaded promotional units and event landing pages may trigger the judgment. When checking, sample the results according to the specific page URL.
Which item should be changed to be referenced by AI search?First check if the search category is allowed, and then see if the content structure can be read. Blocking the training category does not affect the search category crawling, but a chaotic page structure and the lack of self-contained paragraphs will still reduce the probability of reference.
How long will it take to see the effect after changing the configuration?Based on the cycle of crawling logs. Configuration changes take effect immediately, and the time for the crawler to re-read depends on each scheduler, usually it is more reliable to observe log aggregation on a daily basis.