Google Indexing API

The Google Indexing API: what it’s for, and what to use instead

It’s officially for job postings and livestreams only. Here’s what it does, how to set it up for those, and what actually gets other pages indexed.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

The Google Indexing API lets a site tell Google directly that a page was added, updated or removed, so Google can schedule a fresh crawl. Officially it can only be used for pages with JobPosting structured data or livestream videos (BroadcastEvent embedded in a VideoObject), and Google runs spam detection on every submission. For any other site, including a business directory, use clean sitemaps with accurate dates, strong internal links and Search Console’s Request indexing instead.

Short version: job boards and livestream sites can use it, and should. Everyone else: plugins and “instant indexing” services that push ordinary pages through it are using it outside Google’s rules, a 200 response guarantees nothing, and abuse can get access revoked.

What the Indexing API does

It has three calls (Using the Indexing API):

A successful call returns HTTP 200, which Google describes as meaning it may try to recrawl the URL soon. It doesn’t mean the page will be indexed. You can batch up to 100 notifications in one request, but quota counts each URL.

POST https://indexing.googleapis.com/v3/urlNotifications:publish
Content-Type: application/json

{
  "url": "https://jobs.example.com/listing/line-cook-austin-tx",
  "type": "URL_UPDATED"
}

Who it is for, officially

Google’s documentation states that the Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject. Those pages change fast: a job gets filled, a livestream starts and ends. The API exists so they don’t sit in search results after they expire.

In September 2024 Google added a warning to the same documentation: all submissions undergo rigorous spam detection, and any attempt to abuse the API, including using multiple accounts to get around quotas, may result in access being revoked (Search Engine Roundtable’s report of the change). The usage page also says Google’s spam policies apply to content submitted through the API.

What about using it for other pages?

Some WordPress plugins and paid indexing services send any URL through the Indexing API: blog posts, products, directory listings. The API often accepts the call, because accepting a notification isn’t the same as acting on it. Here is the honest picture:

Quotas and cost

Quota (per Google Cloud project)Default
Publish requests (URL_UPDATED and URL_DELETED), per day200
getMetadata requests, per minute180
All requests, per minute380

The API is free: Google says all use is available without payment. The daily publish quota resets at midnight Pacific time. Source: Indexing API quota and pricing.

How to set it up, for job and livestream pages

If your site really does publish job postings (a job board is a kind of directory) or livestreams, the setup from Google’s prerequisites is:

  1. Create a Google Cloud project and enable the Indexing API (Google’s setup tool does both).
  2. Create a service account in that project and download its key, in JSON format.
  3. In Search Console, under the property’s owners, use Add an owner to add the service account’s email address as a delegated owner. It must be an owner of the property, not a user.
  4. Get an OAuth access token for the service account and send URL_UPDATED when a job or livestream page is published or changed, and URL_DELETED once it returns 404 or 410 after the job is filled.
  5. Make sure every page has valid structured data. Google’s job posting documentation lists the required properties, and expired jobs need to be removed or marked expired.

Two errors account for most failed setups. A 403 permission error means the service account isn’t an owner of the Search Console property that contains the URL: add it as an owner (not a user) of that exact property. A 429 error means the project’s daily quota is used up; it resets at midnight Pacific time.

Job boards: the directory case where it fits

A job board is a directory of job listings, and it is the one kind of directory the Indexing API was built for. Jobs open and close quickly, and an expired job left in Google’s results wastes the searcher’s time. The workflow:

A general business directory that also has a jobs section can use the API for the job pages only. Business listings, city pages and blog posts stay on sitemaps and internal links.

The Indexing API compared with the other options

ToolWhat it doesWho it is forLimit
Indexing APINotifies Google that a page changed or was removedJob posting and livestream pages only200 publish requests a day by default
Request indexing (URL Inspection)Asks Google to recrawl one URLAny site, for a few important changed pagesUnpublished daily limit, about 10 to 12 in practice
URL Inspection APIChecks whether a URL is indexed and why; can’t request indexingAny site, for checking at scale2,000 per site per day
XML sitemapLists your URLs and when they changedEvery site50,000 URLs or 50MB per file
IndexNowNotifies participating engines of changed URLsBing, Yandex, Naver, Seznam.cz, Yep, Amazon; not GooglePer engine

What directories and other sites should use instead

  1. Fix why pages aren’t indexed. Most stuck pages are either not crawled yet (discovered, not indexed) or read and passed on (crawled, not indexed). Neither is solved by notifying Google.
  2. Link to new pages from pages Google already crawls often. A new listing linked from its city and category pages gets found on Google’s next visit to those pages.
  3. Keep sitemaps accurate. Only canonical, indexable URLs, split by page type, with a lastmod date that changes when the content really changes. Google uses lastmod to schedule recrawls once it trusts the dates. See sitemaps in robots.txt and sitemap read errors.
  4. Request indexing for a handful of high-value pages after you change them.
  5. Check with the URL Inspection API that it worked, for a sample of each page type.
  6. Use IndexNow for Bing and the others. Google isn’t an IndexNow participant, but Bing is, and a single submission is shared with every participating engine. See Bing indexing.

Why Google indexing can take so long

Google doesn’t guarantee it will crawl, index or show any page, and it doesn’t accept payment to crawl a site more often. On a new or large site, Google crawls what it thinks is most worth crawling first. Pages deep in pagination, linked from nowhere but the sitemap, or similar to thousands of other pages wait longest. Shortening that wait comes from links and page quality, not from notification tools.

How DirectoryLens helps

DirectoryLens never sends URLs to the Indexing API or to indexing services. It uses Google’s read-only URL Inspection API to check your pages every day, and builds a Request indexing queue: not-indexed URLs ranked by how much their page type is worth and how stuck they are, each with its flags and an Open in Search Console button. When you request indexing there, mark it in DirectoryLens and it tracks how many days Google takes to index the page.

Request indexing queue: not-indexed URLs ranked best first with their state, referring URL count, a Weak internal links flag and an Open in Search Console button.
The request queue: the best not-indexed URLs first, why each is stuck, and a direct link into Search Console. Sample directory from the live demo.

To check a list of URLs right now, use the bulk index checker. For every indexing status and its fix, see the page indexing issues guide.

Questions

Can I use the Google Indexing API for any page?

Officially no. Google’s documentation says it can only be used for pages with JobPosting or BroadcastEvent embedded in a VideoObject. Submissions go through spam detection, and abuse can get access revoked.

Is Google indexing free?

Yes. Google doesn’t charge to crawl or index pages and doesn’t accept payment to crawl a site more often or rank it higher. The Indexing API is free too.

How do I submit my website to Google for indexing?

Verify the site in Search Console, submit an XML sitemap in the Sitemaps report, list it in robots.txt, and link to every important page from your site. Use URL Inspection’s Request indexing for a few key pages.

Why is Google indexing taking so long?

Google crawls what it judges most worth crawling first, and doesn’t guarantee indexing. New sites, weakly linked pages and pages similar to many others wait longest. Crawling can take a few days to a few weeks.

How does Google indexing work?

Google finds URLs through links and sitemaps, crawls them, then decides whether to add each page to its index, choosing one canonical URL among duplicates. Only indexed pages can appear in search results.

What is the Indexing API quota?

By default 200 publish requests (updates and removals) per day per Google Cloud project, 180 metadata requests per minute and 380 requests per minute in total.

Does Google support IndexNow?

No. IndexNow is used by Bing, Yandex, Naver, Seznam.cz, Yep and Amazon. For Google, use sitemaps, internal links and Search Console.

Know what to ask Google to index first.

Connect Search Console and DirectoryLens ranks your not-indexed pages by value and tracks how long each takes once you request it.

Explore the live demo →

5 days free · no card needed · ends on its own