Google Indexing API
Most articles about the Google Indexing API skip the part that matters. So here it is first.
Google's Indexing API is officially supported for two things only: pages carrying JobPosting structured data, and pages carrying BroadcastEvent markup for live streaming videos. That is the documented scope. It is not a general purpose "tell Google about my new page" endpoint, however many plugins market it as one.
If you run a recruitment site or you livestream, the API is excellent and you should use it. If you run anything else, the rest of this page is for you.
What the API actually does
The Indexing API lets you send Google two kinds of notification directly, without waiting for a crawl:
URL_UPDATED— this page is new, or its content has changedURL_DELETED— this page is gone, drop it
Google responds quickly. For job postings, where a role might be live for eleven days, that speed is the entire point. A listing that takes a fortnight to index is a listing nobody ever saw.
Setup runs through Google Cloud: create a project, enable the Indexing API, create a service account, download the JSON key, then add the service account as a delegated owner of the property in Search Console. It is more involved than most SEO tasks but it is well documented and a competent developer will have it working in an afternoon.
The default quota is 200 URLs a day. You can request more, and Google will consider it on the basis of demonstrated need.
What happens if you use it for other page types
This is where the honest answer diverges from the popular one.
Plenty of WordPress plugins will happily push every post you publish through the Indexing API, and plenty of people report that it works. It sometimes does. Google has never committed to honouring those requests, has said explicitly that the API is for the two supported content types, and there is no obligation on them to keep accepting anything else.
You are building on a foundation that could be withdrawn without notice and without recourse. For a hobby blog that is a reasonable gamble. For a business that depends on organic traffic, it is an odd risk to accept when the upside is speed you could get by other means.
There is also a practical ceiling nobody mentions. Even if the API worked perfectly for every page type, 200 URLs a day is 6,000 a month. That covers a modest publishing schedule. It does not cover an existing archive of 40,000 product pages, and it never re-covers anything: the API is a notification of change, not a standing instruction.
What the API cannot do at all
The API answers the question "has something changed?" It has nothing to say about the much more common problem, which is a page that has not changed, was published eighteen months ago, was indexed at the time, and has since quietly dropped out.
That happens constantly, particularly on large sites. Google reassesses. Crawl priorities shift. A page that earned its slot in 2024 loses it in 2026 and no notification fires, because from your side nothing happened.
No change-triggered mechanism can catch that. Not the Indexing API, not IndexNow, not a sitemap ping. They all key off an event, and the absence of an event is exactly the failure mode.
What to use instead
For most sites, the realistic options are:
| Method | Covers | Ceiling |
|---|---|---|
| Sitemap | Everything, passively | Google decides when to read it |
| Search Console request indexing | One URL at a time | Roughly ten to twenty a day |
| Indexing API | Job postings and live streams | 200 a day |
| IndexNow | Changed pages, on Bing and partners | Google does not participate |
| Daily submission | Every URL, every day | None |
Where Daily Indexing fits
We crawl your entire site once a day, rebuild the sitemap from every page on it, and keep it current so Google can discover it. Changed URLs are pushed to Bing, Yandex, Naver and Seznam through IndexNow. Not just the pages that changed. All of them, every day.
That covers the archive problem the API cannot touch, and it does not depend on Google tolerating a use of their API that they have not sanctioned.
No developer, and no access to your hosting. We work from your domain name. The one thing that has to live on your own site is your IndexNow key, which is a one-click plugin on WordPress or two lines added by hand anywhere else. Set up within one working day, from £29 a month, no VAT to add.
For the alternatives, see request indexing in Search Console, how to index your website on Google, and Bing indexing and IndexNow.