CMS plug-ins

IndexNow can be automated with plugins written by third parties. Yandex lists them for popular systems and attaches a disclaimer worth taking literally: the Yandex Webmaster team is not responsible for how these plugins work, and problems go to their authors.

What that disclaimer means in practice

The plugin holds your key and decides what gets submitted and when. A poor one can:

• Submit every URL on every save, including pages that did not change — precisely what Yandex says not to do.
• Swallow error responses, so a wrong key or a scope violation goes unnoticed for months.
• Treat 202 Accepted as failure and regenerate the key, restarting verification indefinitely.
• Expose the key file in a location it should not be.

How to evaluate one

• Does it submit only created, updated and deleted pages, or everything?
• Does it report the HTTP response code somewhere you can see it?
• Does it handle 202 as a normal transitional state?
• Does it batch through POST, or fire one GET per page?
• Is it maintained, and by whom?

The alternative

The API is small enough that a direct integration is often less work than evaluating plugins: one POST with a JSON body, triggered on publish, update and delete. For a site with a custom publishing pipeline, that is a few hours of work with no third-party dependency holding the verification key.

The check that settles it either way

After enabling any integration, look at the discovery source in Searchable pages. If IndexNow does not appear there for recently published pages, the integration is not doing what its interface claims — regardless of what its logs say.