# Google Indexing API

Category: [Crawling & Indexing](https://seo-geo-glossary.com/en/glossary/category/crawling-indexing/) › [Sitemaps & feeds](https://seo-geo-glossary.com/en/glossary/category/crawling-indexing/sitemaps-feeds/) · Also known as: Indexing API, Google Indexing API

The **Google Indexing API** is an interface that lets site owners notify Google directly when a page is added, updated or removed. Google documents it only for pages with `JobPosting` structured data and for livestream pages that use `BroadcastEvent` inside `VideoObject`. For all other content, Google's documentation points to sitemaps.

## How does the Indexing API work?

Access needs a service account, verified ownership of the site in Search Console and an access token. Google gives a default quota for testing, 200 units according to the quickstart, and requires an approval request for more. The API has these operations:

- Publish a notification (`URL_UPDATED` or `URL_DELETED`)
- Get the status of a notification
- Send batches of up to 100 requests

Quota is counted per URL, whatever the batch size. A deletion request should only be sent after the page returns 404 or 410, or carries a `noindex` tag.

## Example

```http
POST https://indexing.googleapis.com/v3/urlNotifications:publish
{
  "url": "https://example.com/jobs/data-analyst",
  "type": "URL_UPDATED"
}
```

A job board sends this request when a posting goes live or changes, and `URL_DELETED` when the position is filled and the page returns a 410.

## Can the Indexing API be used for other pages?

Google's documentation lists only the two content types above. Third-party guides sometimes describe it for any URL, and Google warns that abuse can lead to revoked access. For other pages, the documentation recommends submitting XML sitemaps.

## Common mistakes

- **Using it for unsupported page types.** Google documents the API only for the two types above.
- **Missing verification.** Ownership of the site must be verified in Search Console first.
- **Deleting live pages.** A deletion needs a 404, 410 or noindex first.
- **Wrong content type.** Every call to the endpoint must send `application/json` as the Content-Type header.
- **Circumventing the quota.** Google asks site owners not to get around the submission limits, for example by using multiple accounts.
- **Skipping sitemaps.** Google still recommends submitting sitemaps for the whole site.

## Related terms

- [IndexNow](https://seo-geo-glossary.com/en/glossary/indexnow/index.md)
- [Indexing](https://seo-geo-glossary.com/en/glossary/indexing/index.md)
- [Request indexing](https://seo-geo-glossary.com/en/glossary/request-indexing/index.md)
- [XML sitemap](https://seo-geo-glossary.com/en/glossary/xml-sitemap/index.md)
- [JobPosting schema](https://seo-geo-glossary.com/en/glossary/jobposting-schema/index.md)

## Sources

- [Indexing API Quickstart – Google Search Central](https://developers.google.com/search/apis/indexing-api/v3/quickstart)
- [Using the Indexing API – Google Search Central](https://developers.google.com/search/apis/indexing-api/v3/using-api)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/google-indexing-api/