Google Indexing API

The Google Indexing API tells Google when a URL is new, updated, or removed so it can crawl sooner. It does not force indexing or rankings. PageIndexer pairs it with Search Console so sitemap URLs get submitted automatically instead of one-by-one in URL Inspection.

What the Google Indexing API does

You send a URL_UPDATED or URL_DELETED notification for a page. Google can use that signal to schedule a crawl sooner than waiting for the next sitemap poll or link discovery. The API is a notification channel, not a guarantee that the page will enter the index.

Crawl and index are still separate. Google may fetch the URL and still skip indexing for quality, duplication, or other reasons. Background: what page indexing is.

Official scope vs practical use

Google's docs describe the Indexing API for pages with JobPosting or BroadcastEvent (livestream) markup. That is the supported, publicly documented scope. Google Indexing API documentation

Teams still use Search Console URL Inspection and related submission paths for everyday URLs. PageIndexer connects your Search Console property, watches the sitemap, and submits URL update notifications for pages you enable. Results vary by site. Use the API to speed discovery, not as a promise that every URL type is officially covered.

What Google documents

Job postings and livestream / BroadcastEvent pages in the Indexing API guide.

What PageIndexer automates

Search Console connected sites: sitemap sync, automated URL_UPDATED notices, status checks, and resubmits when quota allows.

Google Indexing API vs IndexNow

These are different channels. Using the wrong one for the engine you care about wastes setup time.

  • Google Indexing API - Notifies Google. Needs a Google Cloud project, the API enabled, and a service account with access to your Search Console property.
  • IndexNow - Notifies Bing and other participants. Does not notify Google. Uses a key file on your domain.

Most sites that care about both Google and Bing use both. Bing-side detail: IndexNow setup guide. Full sitemap automation: website indexer.

How to set up the Google Indexing API

Doing it yourself means creating a Google Cloud project, enabling the Indexing API, creating a service account, adding that account in Search Console, then calling urlNotifications:publish. PageIndexer handles the service account side; you still grant access in Search Console. Walkthrough: set up PageIndexer.

Quotas and common failures

  • Quotas - Publish calls are rate-limited. Large sites queue and retry. Going over quota returns errors until the window resets.
  • Permission errors - Service account missing from Search Console users, wrong property selected, or API not enabled on the Cloud project.
  • URL not ready - Submitting before the page returns HTTP 200, or while blocked by robots.txt or noindex, wastes quota.
  • Crawled, not indexed - The notification worked; Google chose not to keep the page. Improve content and uniqueness instead of sending more pings.

How PageIndexer uses the Google Indexing API

  1. Connect Google Search Console and enable the sites you want monitored.
  2. Grant the generated service account access, then turn on auto-index.
  3. New and changed sitemap URLs are submitted through the Google Indexing API (and IndexNow for Bing). Status is checked over time. Resubmits run when pages drop or stay unindexed, within quota.

See live timing data from submitted URLs on Google indexing statistics.

Who the Google Indexing API helps

Teams that publish product, locale, or content URLs often and are tired of requesting indexing one URL at a time in Search Console. Agencies managing many Search Console properties. Anyone who already knows IndexNow covers Bing, not Google.

See pricing for plans, or sign up to connect Search Console and start submitting URLs.