IndexNow and Yandex: a default you rarely need to touch

Why it is a default rather than an option

Three participants are offered as choices, and this one is not.

Seznam, Naver, and Yep are off by default: you enable them when they match your audience. Yandex and Bing are simply on. The line between the two groups is not popularity in the abstract but whether there is a decision worth putting in front of somebody, and for these two there is not.

That is worth unpacking, because "default" often means "we picked for you". Here it means something narrower. A submission costs you nothing, obliges you to nothing, and creates no risk of being treated worse for having sent one. When every branch of a decision leads to the same outcome, presenting it as a choice adds a setting to understand and returns nothing for it. The other three are offered as a choice precisely because their branch does differ, as the optional engines sets out.

Whether it matters for your site

The honest answer is that your own data has it and this page does not.

Any claim about where an engine is used, by whom, and in what share is a claim with a date on it, and a page that made one would be quietly wrong within a year of being written. What does not go stale is the method: look at where your existing visitors arrive from, and at which search sources already send you anybody at all. If this engine appears there, it matters to you. If it does not, it does not, and no general statement about markets changes either answer.

That check is worth doing once rather than reasoning about repeatedly. It takes minutes, it uses data you already have, and it settles a question that otherwise gets re-argued every time somebody new looks at the configuration.

There is a second case the data will not show you, and it is worth naming: publishing in a language or for a market you are trying to enter rather than one you already reach. Existing traffic cannot tell you about an audience you do not have yet. That is a judgement about intent rather than a measurement, and it is the one situation where the answer comes from your plans instead of your analytics.

What leaving it on costs

Nothing that shows up anywhere, which is the reason the default stands.

Submission happens as part of announcing a change you were making anyway. One additional destination does not add a step to your publishing, does not require anything on the page, and does not change what visitors receive. There is no per-engine setup to maintain, because verification uses the same /<key>.txt file on your own hostname that every participant checks.

The mirror of that is also true and less often said: switching it off buys you nothing either. If an engine is irrelevant to you, submissions to it are already producing nothing, and stopping them turns nothing into nothing while adding a setting that differs from the default for no reason anybody will remember in six months. Configuration that deviates without a reason is the kind that gets rediscovered during an unrelated incident.

What is identical, and what is not

From your side, nothing here is engine-specific.

The same HTTPS submission, the same verification against the same file, the same scope: automatic submission covers discovered and changed URLs only, enabling it imports no history, and full-site submission is manual. Anything you set up for one participant is already in place for the others, which is why this section is short.

What differs between engines lives on their side and is not visible from yours. How quickly a participant acts on an announcement, whether it fetches the address at all, and what it does with what it finds are its own decisions on its own schedule. Those differences are real, but they are not settings, not observable from your configuration, and not something a provider can adjust on your behalf. The boundary between the announcement and the engine's decision is set out on how it works.

The practical consequence is that troubleshooting is never engine-specific either. A submission that fails, fails for a reason on your side, and the same checks apply whichever participant was involved. Those are covered on the Bing page, which describes them once for all of them.

What to expect

Timing on discovery, on the engines that participate, and nothing else.

For a site publishing frequently and reaching readers who use this engine, changes can be learned about sooner than by ordinary revisiting. For a site whose audience is elsewhere, the accurate expectation is no observable difference, and the reason the setting stays on anyway is that no observable difference is also the cost.

What it does not touch is ranking, which is decided on the engine's criteria and unaffected by any announcement. And Google is not part of this at any setting, a fact worth repeating here because the assumption survives being told once.

FAQ