Should the new article be submitted to the search engine actively, and which companies does this protocol cover?
After a new article is published, should you actively submit it to search engines? Which companies are covered by the IndexNow protocol? It is worth submitting, but it only solves the discovery phase: The role of this protocol is to immediately notify that there is a new change in content, shortening the time waiting for the next convenient crawling. The participating parties are represented by Microsoft Bing, including Bing, Naver, Seznam.cz, Yandex, and Yep, Google does not support this immediate notification protocol, so it cannot replace the crawling and inclusion path for other engines.
What part does the active submission solve?
New pages enter the index through two paths: the crawler discovers along the links, or reads from the site map. The former depends on the structure of internal links, and the latter depends on the rhythm of files being read. The submission action directly communicates 'There is new content or content has been changed', which is more beneficial for time-sensitive content, such as announcements, event pages, and time-sensitive articles. It does not guarantee the inclusion result, which is still determined by the quality of the content and the structure of the site.
Which engines are involved, and what path is taken for unsupported ones
| path | Applicable engines | Content suitable for submission |
|---|---|---|
| Instant notification protocol | Bing, Naver, Seznam.cz, Yandex, Yep | New release, major update, address migration |
| Site exclusive submission tool | According to the backend capabilities of each engine | Incremental submission in coordination with the site map |
| Site map backup | All engines | Full range of standardized addresses, columns and language versions |
For engines that do not support real-time notification protocols, rely on in-site links, standardized addresses and site maps together, do not take the submission volume as the prerequisite indicator for the inclusion volume.
分工 of push and site map
The link push is responsible for incremental updates: new articles, articles with changed timestamps, and articles with changed addresses; the sitemap is responsible for full coverage backup, listing the standard addresses that are expected to be indexed. The content scope of both should be consistent. If error pages, redirect pages, or addresses to be published are mixed into the sitemap, it will waste both crawling and indexing quota. In scenarios with multiple sites or languages, maintain them separately by site, and do not mix two sets of addresses in the same submission.
What frequency is worth pushing
Low frequency update sites have more direct benefits, you can push once for each release; high frequency sites need to control the scale of submission, only push truly changed addresses, and repeated submission of old addresses will not bring additional benefits. When changing addresses after the revision, first set up the jump relationship and then push the new addresses to avoid old and new addresses entering the submission list at the same time.
What conditions does the site need to meet first inside?
The benefit of the submission action depends on whether the site can be read smoothly. Three things need to be in place first: the static rules should fix the address format, so that the same content does not produce multiple addresses due to different parameters; anchor text and internal links should allow new articles to have an entry on the day of publication, rather than relying only on submission; link promotion should be attached to the publishing action, and the same should be supplemented during site redesign and address change, to avoid only promoting new content and missing the direction of old addresses.
Common questions
Can active push replace the sitemap?No, promotion is an incremental notification, and the sitemap provides full and standardized addresses.
How long will it take to be read?Depends on the processing rhythm of each engine, it is recommended to observe the changes in the inclusion list instead of checking the submission receipt.
Should un发布的 content be pushed?No, drafts and pending publication status have no significance in external inclusion. Submit the formal document first.
Where should you look first if the submission fails?First check if the address returns normally, whether it is consistent with the standard address, and then check the key and site ownership configuration.
Is the small station worth accepting?Yes, the proportion of changes submitted each time for low-frequency updated sites is higher, and the benefits in the discovery stage are more direct than those of large stations.