So Outside Technology Security CMS
AnQiCMS
Online Demonstration

When the sitemap exceeds the limit, it can only be split into files, and before splitting, you need to clear which type of address.

📅 2026-11-01 👁️ 0

When the site map exceeds the number or volume limit and needs to be split into multiple files, the address that should be cleared before splitting is the page with an error status code, the address with a jump, and the page with a shielding mark. These three types of addresses only occupy volume in the file and do not bring inclusions. Clear them first and then split, which is equivalent to releasing the crawling quota from the waste state; conversely, if you split the files first and then clean up, each piece still carries the same batch of invalid addresses.

Align the upper limit口径 first

On October 30, 2026, the original text was checked and it was found that the single site map file has two strict limits of 50,000 addresses and 50 MB. Any limit exceeded must be split, and the excess part is summarized and registered through index files. That is to say, the site that reaches the top in volume first, the number of slices is determined by bytes rather than by the number of addresses, and the site with plain text addresses often exceeds the line by the number of addresses first, and the site with longer query parameters is more likely to exceed the volume first.

After the disassembly is completed, do not think that the matter is over. The same document also states that the priority and update frequency tags will be ignored by search engines, and the reliable last modified time is actually used. The benefits of disassembly come from 'each piece is smaller and caught more frequently', rather than 'can accommodate more addresses'.

Before splitting, which three types of addresses should be cleared first?

The addresses to be cleaned up Why do we occupy the quota for free The basis for judgment when cleaning up
The page that returns an error status code After crawling, a failure response is obtained, and the page itself does not enter the index Use log or batch status check to group by code, confirm whether it is permanent failure or temporary fault
The address that occurs jump It takes an extra step to capture and land on the target, which is equivalent to duplicate registration Compare the address with the final target to see if they are the same content, and only leave the final address in the map
Pages with masking marks The masking instructions and map registration are contradictory, and the quota is consumed Check the page marks and visibility settings on the back-end, and move out the whole item that should not be publicly disclosed

The common point of the three types of addresses is that they will not be included, but they still consume an opportunity to capture once. The cleanup action must be done before splitting, otherwise, after the slices are cut according to the module, each slice needs to be generated all over again

The organization method of splitting and index files

It is better to split by module than by sequence number for maintenance. The site map of AnQi Content Management System (AnQiCMS) is automatically generated, with columns, articles, and single pages each forming a file, naturally segmented by module, so the site owner does not need to manually count the number of lines. Pay attention to not having the same address repeated between segments: when the same article is hung under two columns, the standard address should be only one.

The last modified time follows the content changes and is the key to whether the segment can be crawled frequently. Changing the last modified time of a large number of addresses in one batch will make the crawling judgment distorted and reduce the revisit frequency of the segments.

How to coordinate generation and push

Splitting solves the problem of 'registering successfully', while proactive push solves the problem of 'letting the other party know as soon as possible'. New content and revised content go through the link push channel submission, which is faster than waiting for the other party to visit the map periodically. The two are complementary rather than substitute relationships. Site map is suitable for covering the full amount and bottom line, push is suitable for handling increments, separating the two according to their responsibilities so as not to appear 'the map is big but the update is slow'.

After cleaning, it is recommended to keep a record of changes: how many were deleted, how the modules were divided, the number and volume of each piece, and which types of channels were submitted on the day of push. Next time when it reaches the top again, you can directly compare which type of address is expanding.

Common questions

Question: If the volume exceeds the limit but the number of items has not reached the limit, can we only compress the volume? Answer: Yes, but if it still exceeds after compression, it needs to be divided. More effective is to remove the addresses that should not be registered, and the volume usually decreases first.

Question: Should the target address after the jump be written into the map at the same time? Answer: No, only the final address is kept in the map. Writing both at the same time is equivalent to making the same capture go through an extra jump.

Ask: Will splitting into many small files be more beneficial for inclusion? Answer: No. Too many slices will reduce the number of covered addresses each time, it is more stable to divide by module and keep each slice at a reasonable scale.

Ask: Should the temporary event page be included in the map? Answer: After going offline, the event page with a屏蔽 mark should be removed from the map, only relying on the mark is not enough, and registration and masking existing at the same time is contradictory.

Related articles

Several thousand articles need to be moved, should it be imported using a compressed package or a table?

When moving thousands of articles, the basis for choosing between compressed package import and table import is not the quantity but the material form: batch import using ZIP compression packages for text with attachments and rich text, and batch import using Excel tables for neatly organized fields. First align the content model and custom fields, and then use the import interface for title duplication check to control duplicates, and only the failed batches can be safely rerun.

2026-11-01

When starting a site with a container image, should the default port and background address be changed together?

When starting a station using a container image, whether to change the default port and backend address at the same time depends on where the traffic comes from: After the site is behind the reverse proxy, the container listening on port 8001 only needs to match in the mapping, the default port does not need to be changed; what needs to be received is the exposed surface of the backend address. Before going online, enable the built-in protections such as JWT authentication, sensitive word filtering, captcha, and rate limiting first, and then verify it once from the external network.

2026-11-01

How to plan the column structure and classification for a single backend to manage multiple sites without conflict

When managing multiple sites with a single backend, the place where column structure and classification are most likely to interfere with each other is when reusable definitions and isolated data are mixed together. This article explains by separating the shared layer and the isolation layer: the definition of the content model can be reused across multiple sites, the classification tree, column aliases, and visibility range should be planned independently for each site, batch operations at the whole-site level are disabled by default and explicitly enabled per site, and a landing sequence and a corresponding table are provided.

2026-11-01

Can deleted articles be retrieved, and how are drafts, pending publication, and recycling stations divided?

Deleted articles can usually be retrieved: In the AnQiCMS backend, deleting formal documents is not a physical deletion, but moving them to the recycle bin, from which they can be restored. Each of the four document statuses has its own boundaries - formal documents are visible to the public, drafts are only in the background and preview links contain the preview tag, pending publication waits for the set time to take effect, and the recycle bin accommodates deleted content. This article explains the appropriate operations for each and the safe sequence for bulk cleaning.

2026-11-01

How to import articles from the old station table once, if the fields do not match

The order of handling the mismatch of fields when importing the exported table of the old station to the new system is: first select the channel and then discuss mapping, the three columns of fixed title, alias, and category must be mapped, then determine the default value strategy for custom fields, and finally use title search to check if it already exists to avoid repeated imports and sample check the import results

2026-11-01

The active push protocol is only supported by a few search engines, does another one count as a push?

The active push protocol informs search engines about which URLs have changed, requests priority crawling, but only a few participate. The one that does not participate will not change the crawling and inclusion judgment just because you have sent a notification. You need to separate discovery and inclusion, follow the engine's分流 actions, let the sitemap be responsible for the bottom line, push for incremental, and then use each result to check whether it has really entered the index after the push.

2026-11-01

The page shows that it has been crawled but not indexed, is it a broken link or a quality demotion?

Being crawled means the crawling link is working, and not being indexed is often the result of quality judgment: the system may reduce the number of indexed pages when it is worried about the quality of the entire site. The handling is in order, first分流batch pages by subject, then decide to rewrite, merge, or withdraw, while cleaning up the low-quality content collected, converging the repeated carrying pages and anchor text in the keyword library, and finally resubmitting and keeping a record for observation.

2026-11-01

On the day of replacing the host, the domain resolution needs to be moved, and how long in advance should the cache time be reduced to be safe.

The key to migrating domain name resolution is not on the day of the switch, but in advance, by lowering the caching time of the resolution to make both new and old sides converge to the same record as soon as possible. Generally, adjust the cache value one to two days in advance, let the old environment run for a few days after the switch, and hand over the redirection and site map to the new address. Email records are easiest to miss, the effective window is uncertain, and after the switch, you need to check the inclusion status with each search engine separately.

2026-11-01