Bridge IndexNow

About Bridge IndexNow: who writes this, and how it is checked

3 min readUpdated

Bridge IndexNow is the IndexNow feature brand of Bridge CDN, and this site is its documentation: how the protocol works, which engines take part, the ways a submission can be sent and what to do when one fails. This page says who writes the material and how it is checked, because documentation you might act on should be willing to answer that.

Who writes this

The Bridge CDN team writes this site, and the same team builds the platform it describes. Pages are published under the team rather than under individual names: accuracy is a shared responsibility here, and a page is held to the same standard whoever drafted it.

How each claim is checked

Most of this site describes systems we do not run: the protocol, the engines that take part in it, and the plugins and tools that send submissions. Five rules govern how those descriptions are written, and they explain absences you may notice.

A source comes before the sentence

A statement about the protocol, an engine or a plugin is recorded in a register of facts, with the page it comes from and the date that page was read, before any text is written from it. The protocol's own documentation at indexnow.org is the source for how a submission works; each engine's documentation is the source for what that engine says it does.

Numbers come with a source or not at all

Where a source gives a figure, such as the 10,000 addresses a single request can carry, the page uses it. Where a source gives none, the page says so rather than estimating. The protocol does not publish the daily limits each engine sets for a site, and no engine says how quickly it acts on a submission, so you will not find a guess at either here.

Named products carry a date

Plugins and services change between versions. Where a page names one, it says what that product's own documentation stated and when it was read, and it says plainly when no recent statement could be found.

Google is described as it is

Google does not participate in IndexNow and receives nothing from it. Every page that mentions Google says so, and what affects discovery there instead is set out under IndexNow and Google.

Product claims are kept apart from everything else

How the protocol works and what Bridge CDN does are different kinds of statement. The second is checked against what is shipped, and its scope is stated the same way everywhere: automatic submission covers discovered and changed URLs only, enabling it imports no history, and full-site submission is manual.

What you will not find here

Promises about indexing or rankings

A submission tells an engine that an address changed. Whether the page is crawled, indexed or shown is each engine's decision, and nothing on this site says otherwise.

Pricing and plans

Those belong to Bridge CDN, where an account is created.

Comparisons between delivery networks

Those belong to Bridge CDN as well. This site compares IndexNow with the other ways of announcing pages, not one provider with another.

Corrections

Every page shows when its text last changed, and that date moves only when the text does. When a statement turns out to be wrong, the page is corrected against its source, and the register of facts records what changed. A specific report about one sentence is worth more than a general impression, and a technical correction is applied on its merits whoever sends it.

Contact

Bridge IndexNow has no separate contact address. The team is reached through Bridge CDN, where the product and the account live, and reports about this site go the same way.

Where to start

Four entry points cover most of the material: how IndexNow works for the sequence from a change to a submission, participating engines for who receives one, setup for the ways to send it, and troubleshooting for what a failure actually indicates.