Operations · document 15

Submission Center

In the workspace: /submission-center

Availability

Included on Advanced

This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.

What it is for

When you publish or change a page, you can tell the search engines rather than wait to be found. This is where that happens, using each provider official channel and nothing else. It is also the page that states plainly what those channels actually do, because the industry sells submission as a shortcut to being indexed and it is not one.

How to use it

Verify the project first. Submission is an instruction about a hostname, so this platform will not send one for a site you have not proven you control.
Paste the URLs, one per line, up to one hundred. Every one must belong to the project hostname; a mixed batch is refused rather than partly sent.
Choose the provider actions you want. Each checkbox states what that provider will do, and an unavailable one says which connector is missing.
Run the batch and read the outcomes per URL and per provider. A cooldown applies to each URL and provider pair, so repeating a submission achieves nothing.

Reading the result

Each provider does a different thing, and the outcome names which. IndexNow is a change notification to Bing and the engines that participate. Google returns the indexed state it already holds for one page, which is an inspection and not a request. Yandex accepts a recrawl request into its own queue. An accepted outcome means the provider took your message, and nothing more than that.

What it cannot tell you

None of this makes a page get indexed. Notification tells an engine something changed; the engine still decides whether to crawl, and whether to index what it crawls. The Google Indexing API is deliberately absent from this page because Google restricts it to job postings and livestream events, and offering it for ordinary pages would be selling an endpoint that does not apply. Submission also cannot repair a page a crawler is refused: fix the reachability first, then tell them.

What it keeps

Every batch and every per-URL outcome, so that what was sent, when, to which provider, and what came back is auditable afterwards. That record is the point: an instruction sent on your behalf with no trace of it would be indistinguishable from one that was never sent.