---
title: "Google Indexing API: What It Does and When to Use It"
description: "Understand Google's supported Indexing API use, notification responses, approval requirements, and how it differs from URL Inspection."
canonical_url: "https://requestindexing.com/google-indexing-api"
last_updated: "2026-10-08"
---

> Index of every page on this site: [llms.txt](https://requestindexing.com/llms.txt)

The Google Indexing API notifies Google when an eligible URL changes or disappears. Eligible means a page with `JobPosting`, or `BroadcastEvent` embedded in `VideoObject`. Ordinary website pages are outside that supported use, as [Google's quickstart](https://developers.google.com/search/apis/indexing-api/v3/quickstart) defines it.

If you publish ordinary articles, read [what to use for blog posts instead](https://requestindexing.com/indexing-api-for-blog-posts). For eligible job listings or livestream pages, start with one notification.

## A notification for one job listing

Suppose you update a job listing at `https://example.com/jobs/42`. Your client sends an authenticated POST to `https://indexing.googleapis.com/v3/urlNotifications:publish` with this body:

```json
{
  "url": "https://example.com/jobs/42",
  "type": "URL_UPDATED"
}
```

The body alone is only part of the call. The [Indexing API setup tutorial](https://requestindexing.com/google-indexing-api-tutorial) adds the credentials and sends it.

A successful response means Google may attempt to recrawl the URL. It does not prove that a crawl happened or that Google indexed the page. The metadata endpoint reports notification history, so a recent timestamp there cannot establish indexing either. See [Google's request and response meanings](https://developers.google.com/search/apis/indexing-api/v3/using-api).

To see whether Google returns the page in search, run a `site:` search for it with one of the [free indexing tools](https://requestindexing.com/tools). The [Google Index Checker](https://requestindexing.com/tools/google-indexing-checker) checks one URL. The [Bulk Indexing Checker](https://requestindexing.com/tools/bulk-indexing-checker) checks up to 10 URLs, or the first 10 URLs of a sitemap. The [Site Indexing Report](https://requestindexing.com/tools/site-indexing-report) estimates the indexed page count for a whole domain. Each result is an estimate from public search output, not a URL Inspection result.

An accepted notification does not set an indexing deadline. [October 2026 conference reporting](https://www.seroundtable.com/google-crawling-indexing-serving-data-42225.html) lists roughly 1.5 hours as typical for indexing processes, with slow cases reaching months or never.

Earlier discovery and crawling stages can delay that work. The figure does not measure notification-to-indexing time or API speed. See [Google Search timelines](https://nuxtseo.com/learn-seo/google-search-timelines).

## Choose the correct Google interface

| Interface                          | What you use it for                                  | What the result tells you                                                |
| ---------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------ |
| Indexing API                       | Notify Google about changed or deleted eligible URLs | Notification receipt                                                     |
| Search Console URL Inspection tool | Inspect a URL and manually request indexing          | Inspection information; a request remains subject to Google's processing |
| URL Inspection API                 | Read stored index information programmatically       | Information about the version Google has in its index                    |

Google recommends [manual URL Inspection for a few URLs and sitemaps for many](https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl). The [URL Inspection API](https://developers.google.com/webmaster-tools/v1/urlInspection.index/inspect) has no live-test or request-indexing operation.

When you evaluate an indexing tool, ask which of these interfaces its request button calls. The [Indexly and SEO Gets comparisons](https://requestindexing.com/comparisons) check that against each vendor's documentation.

## Before you build

Google's documented setup uses a Cloud project with the API enabled, a service account, Search Console ownership, and the `https://www.googleapis.com/auth/indexing` scope. The service account needs delegated ownership of the property. Cloud project permissions and Search Console ownership are separate. Follow the [prerequisites](https://developers.google.com/search/apis/indexing-api/v3/prereqs).

The default publish quota is 200 requests per day per project for onboarding and testing. Google requires additional approval for usage and resource provisioning. Check the [approval and quota page](https://developers.google.com/search/apis/indexing-api/v3/quota-pricing) before planning a production integration.

To send one notification from code, start with the [Node.js example](https://requestindexing.com/google-indexing-api-node-js). Once that works for your eligible content, move on to [bulk requests with a result for each URL](https://requestindexing.com/bulk-submit-urls-google-indexing-api).

## When a page is removed

Use `URL_DELETED` after the URL returns `404` or `410`, or includes `noindex`. This tells Google about the removal; it does not prove removal has finished. The current [usage documentation](https://developers.google.com/search/apis/indexing-api/v3/using-api) covers those prerequisites.

*Correction, 15 September 2026: This guide now separates notification receipt from indexing and includes Google's approval requirement. Earlier descriptions of general-page use and guaranteed response timing were unsupported.*

## Sitemap

See the full [sitemap](https://requestindexing.com/sitemap.md) for all pages.
