Does IndexNow submit to Google? No, and here is why

The plain answer

No part of IndexNow reaches Google.

Submissions travel as an ordinary HTTPS request to the engines that take part in the protocol. Google is not among them, so a submission is neither delivered to it, nor queued for it, nor partially honoured by it. There is no mode, plan, or configuration in which that changes, and a provider claiming otherwise is describing something else under this protocol's name.

This is worth stating without hedging because the hedged version is actively harmful. A page saying that submission "notifies major search engines" lets a reader conclude the opposite of the truth while remaining technically defensible, and the reader finds out weeks later, having spent that time believing a change was announced when it was not.

Why it is structured this way

Participation is each engine's decision, not a technical limitation.

The protocol is open: any engine can accept submissions, and the ones that do have chosen to. Google has not, and the reasons are its own to state rather than ours to guess. What can be said accurately is that the absence is a policy position rather than an incompatibility, so nothing about your site, your configuration, or your provider is the cause.

That distinction matters more than it looks. An incompatibility is something somebody could fix, which is why the assumption that one exists sends people looking for the fix. A decision by another party is not a fault in anything you control, and treating it as one is how an afternoon disappears into comparing settings that were all correct.

That also means there is no workaround, and the phrase is worth being blunt about. Sending the same submission through a different route, enabling more participants, or using the shared api.indexnow.org endpoint changes which participating engines receive it, and none of those makes a non-participant into a participant.

It is also why the question keeps returning in a particular form. People ask whether a specific provider or plugin can do it, on the reasonable assumption that a limitation of one implementation might not be a limitation of another. Here it is neither: the boundary sits at the protocol, above every implementation of it, so the answer is the same for all of them.

What this means in practice

Two consequences, and they point in different directions.

If Google is your only concern, this protocol is not your mechanism. That is the honest answer, and knowing it now is worth more than any amount of detail about how submission works. Nothing on this site will change that conclusion, and a page that led you around it before admitting so would have wasted your time.

The corollary is worth stating too, because it saves a second round of investigation: there is nothing further to evaluate here. Comparing providers, reading their documentation, or asking support about it produces the same answer each time, since the boundary is not theirs to move.

If other engines matter to your audience, the calculation is separate. Participation costs almost nothing once configured, and the value is timing on the engines that do take part. Whether that is worth having depends on where your readers search, which is set out under which engines take part. The mechanics of what a submission does and does not claim are on how it works.

Those two are not in tension, though they are often read as if they were. A site can reasonably conclude that IndexNow is worth enabling and that it does nothing at all for the engine it cares about most, both at once and without contradiction.

What affects discovery on Google instead

Here the honest answer is narrow, and this page will not pad it out to look more generous than it is.

Google discovers changes its own way, on its own schedule, using its own signals, and it provides its own tools for site owners who want to ask about a specific address. Those belong to Google's documentation rather than to ours, and pointing at them accurately means pointing at them by name rather than paraphrasing behaviour that changes without notice.

What can be said generally, and holds regardless of engine, is that discovery follows from being reachable and being linked. A page that is served reliably, is not excluded by your own configuration, and is referenced from somewhere already known is in the best position anybody can put it in. That is not a trick, and it is not specific to any engine, which is exactly why it survives changes in engine behaviour.

There is no additional lever, and any product claiming one is claiming influence over decisions that are not for sale. Where a page changed and you want it looked at sooner, the tools the engine provides for that purpose are its own, and using them is the whole of what is available.

FAQ