Google Indexing API and backlinks

What the Indexing API is

The Indexing API is a Google Search Central interface that lets a site owner tell Google directly that a page was published, changed or deleted, so Google can schedule a fresh crawl. Google introduced it on June 26, 2018 for job posting pages, because job listings expire quickly and stale listings frustrate searchers. Support for livestream pages was added later the same year.

The current documentation is explicit about scope: the API "can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject." Every other kind of page, including blog posts, product pages and the third-party articles that carry backlinks, falls outside it.

How a request works

A client authenticates with a Google Cloud service account that has been added as an owner of the property in Search Console, then sends a JSON body to the publish endpoint:

POST https://indexing.googleapis.com/v3/urlNotifications:publish
{ "url": "https://example.com/jobs/42", "type": "URL_UPDATED" }

Three operations exist:

Up to 100 calls can be combined into one batch request. The default quota for onboarding and testing is 200 publish requests per day per project; anything beyond that needs Google's approval form, and Google notes the quota "may increase or decrease based on the document quality."

Why it does not fit backlinks

A backlink sits on a page someone else controls: a guest post, a directory listing, a press release mirror. Three requirements of the API rule that page out.

1. Ownership. The service account must be an owner of the Search Console property containing the URL. The person who earned the link is almost never an owner of the linking site.
2. Page type. Even on a site the caller owns, only job posting and livestream pages qualify. An article with a link in it is neither.
3. Policy. Google's usage guidelines state that its spam policies apply to submitted content and that callers must not "circumvent our submission limits, such as by using multiple accounts." Those same spam policies list "using automated programs or services to create links to your site" as a link scheme.

So the API is not a backdoor indexing channel for links. Readers looking for what does reach third-party pages should start with the definition of a backlink indexer and the mechanics in how indexers generate crawl signals.

How the API came to be associated with link indexing

For several years after launch, a common SEO tactic was to send arbitrary URLs through the API anyway, since publish calls returned 200 regardless of page type and Googlebot often fetched the URL shortly afterwards. Scripts, plugins and some commercial indexers spread the technique, frequently rotating many service accounts to multiply the 200-request daily quota. The history of backlink indexing covers how this fit into earlier methods such as ping services.

Google's current documentation closes each of those gaps in writing: the page-type restriction, the approval step for quota beyond testing, the warning against using multiple accounts, and the statement that spam policies apply. This wiki does not state a date for when enforcement changed, because Google has not published one in the sources cited here.

What happens to misused requests

Google's documentation does not describe penalties for submitting ineligible pages beyond the policy text above. What it does say is that a 200 response is only a statement that a recrawl may happen. A crawl is also not an index decision; the distinction is laid out in crawling vs indexing. A page that Google fetches through any channel still has to pass canonical selection and quality evaluation before it appears in results.

Legitimate alternatives for owned pages

For pages on a site you control, Google's own channels are:

• An XML sitemap with accurate lastmod values, which Google says it uses as a signal for scheduling crawls of known URLs.
• The Request Indexing button in Search Console, which has a per-property daily limit; see URL Inspection limits.
• Internal links from pages Google already crawls.

For pages you do not control, none of those apply, which is the gap that third-party indexing services fill. Bing, Yandex and others accept IndexNow pings, but Google does not take part; see IndexNow and backlinks.

Where IndexChex stands

IndexChex, the publisher of this wiki, does not use the Indexing API. Its submission service generates crawl signals by other means, guarantees that Googlebot crawls the submitted URL, and leaves the indexing decision to Google. Confirming the outcome afterwards is a separate step described in verifying backlink indexation.