So Outside Technology Security CMS
AnQiCMS
Online Demonstration

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

📅 2026-11-01 👁️ 0

The active push protocol is only supported by a few search engines. Does the one that doesn't participate count as being pushed? No. The role of active push is to inform which websites have been added or changed, request priority crawling. Engines that do not participate in the push will not receive this notification, and can only rely on sitemaps and regular crawling to discover addresses, and the inclusion judgment will not change accordingly. We should separate the discovery and inclusion, according to the分流 actions of the engine, push is responsible for the increment, and the sitemap is responsible for the bottom line.

Discovering and indexing are not the same thing

The solution to discovery is whether the engine knows if the address exists; the solution to inclusion is whether it is willing to put the address into the index and give it a ranking. Active push belongs to the discovery phase, which makes the engine prioritize crawling, but it does not mean that the content is definitely included in the index, nor does it mean that the inclusion quality will improve.Engines that do not participate in the agreement take a different discovery path: periodic submission of sitemap files, plus regular crawling guided by link relationships. The difference between the two paths lies in timeliness, not treatment: the participating parties receive change signals earlier, and the non-participating parties rely on periodic coverage.It is a common misreading to treat items not pushed as not included, with two stages of retrieval and quality judgment in between.

Participants on the day's scale

The IndexNow official site states the scope for the day, the participating parties of this agreement are Microsoft Bing, Naver, Seznam.cz, Yandex, Yep;Through it, search engines can learn which websites have changed and thus prioritize crawling. The mainstream engine not on the list is not involved in the parties, notifying it is like sending a message to an object that does not listen to this channel.The scope of judgment should fall on the day of retrieval: the list of participants will expand or contract with cooperation, and it needs to be reviewed again after a while, do not continue to use the old list to arrange the actions for the whole quarter.The list only specifies who will receive the notification, it does not involve each family's quota and inclusion standards, those two things need to be checked with each family's explanation.

The process of分流 by engine

The core of分流 is to assign different change types to different channels, the following table lists the channels and verification methods of each party.

Change type Engines participating in the agreement Engines not participating Verification method
New content online Push new address actively sitemaps submitted periodically index results checked item by item
minor content modification active update push sitemaps update time field crawling record comparison
address change set 301 redirect first then push new address replace sitemaps with new address redirect link and status check
Page Offline Moved out of site map after push Site map removed Observation period for results retention

Add new content through active push, assign existing content and modifications to site map coverage, first establish a 301 redirect relationship from the old address to the new address, then push the new address out, so that the participating parties can switch to the new link as soon as possible. Submit batch changes by type separately, handle one case at a time, and it is easy to locate the link when an error occurs. The link push on the AnQiCMS side and the automatic generation of Sitemap correspond to these two channels, the static rules and 301 redirect configuration maintain the address consistency, to avoid the pushed address from being different from the actual accessible address.

How to verify after pushing

Check the two results: whether the notification has been received and whether the index has really changed. The first part looks at the processing results returned by the engine, with separate counts for successful submissions and failures;In the days after submission, use each site to query and confirm one by one whether the address has entered the index. Handle three cases separately: not crawled, supplement the site map and check if robots have blocked the path;Caught without collection, it belongs to content and quality judgment issues, which are not solved at the notification stage; for those who have changed the address, confirm that the 301 redirect has taken effect and the old address no longer appears in the site map.Document the verification results, mark the search date and submission batch, for easy comparison of share changes in the next round.

Common questions

Ask: Is an engine that does not participate in the active push protocol considered to be pushed?

Answer: No. Notifications sent out are not received by it, and the discovery of this type depends on the site map and regular crawling, with the inclusion judgment following its own chain of command.

Ask: Should the site map continue to be submitted?

Answer: Yes. The site map is a fallback channel, covering existing inventory and modifications, while active push only handles increments. Both need to be maintained simultaneously to avoid missing addresses.

Ask: What should be pushed when changing addresses?

Answer: First, configure the 301 redirect from the old address to the new address, and then push the new address; the old address should be removed from the site map, and the redirect relationship should be retained until the reference is cleared.

Ask: If the push was not indexed, is it because the link is broken?

Answer: It may not be a link problem. First, confirm whether it has been crawled, then judge the quality, and only when the notification and crawling are normal and the index does not move, do you need to check whether the configuration has an intercept.

Related articles

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

The site map exceeds the single file limit and must be split into multiple files using an index file for aggregation, but before splitting, it is necessary to clean up three types of addresses: pages with error status codes, redirect addresses, and pages with屏蔽 marks that are written into the map. The cleaning order is wrong, and the each file after splitting is still wasting crawling quota, the collection efficiency will not improve.

2026-11-01

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 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