Check your page type prior to setting up Google Cloud. Ordinary pages need Search Console or sitemap discovery instead. Even for eligible content, an accepted notification doesn't confirm a crawl or indexing.
Who Can Use the Google Indexing API?
Eligibility depends on the page's actual content, not on whether a plugin may send requests. Google's supported cases involve job postings and livestreaming events. Adding their structured-data labels to unrelated pages doesn't make those pages eligible.
| Page or Situation | Eligible for Google's Indexing API? | Appropriate Next Step |
|---|---|---|
An actual job listing with qualifying JobPosting structured data |
Yes, if Google's content and access requirements are met | Configure the API to notify Google when the listing is published, updated, or removed |
A genuine livestreaming event represented by BroadcastEvent embedded in VideoObject |
Yes, if it meets the documented requirements | Use the API for eligible event changes |
| A regular article, product page, service page, or business homepage | No | Use normal crawling and sitemap discovery; eligible property owners may request a recrawl via Search Console |
| A prerecorded video page without a qualifying livestreaming event | No, not on that basis alone | Use the normal discovery and indexing workflow |
| A backlink donor article on another publisher's site | No general API route, and you don't control the publisher's property | Check the source page separately; ask its publisher to address site-side problems |
| A page made to look like a job posting only to gain API access | No legitimate eligibility | Correct the content classification instead of attempting to bypass Google's requirements |
A job board may notify Google about a newly published vacancy using URL_UPDATED, then send a removal notification when the URL is properly removed or marked noindex. Its category pages, articles, and contact page are not eligible merely since they share the domain.
The livestream exception also doesn't cover every video page. Check the official API scope and structured-data requirements.
Decision rule: Without genuine qualifying content and property ownership, don't implement the official API for that URL. Connecting to the endpoint doesn't change eligibility.
How to Set Up the Google Indexing API
Implementation requires a Google Cloud project, a service account with access to the relevant Search Console property, and OAuth authentication. Pasting a generic API key into a plugin isn't equivalent.
- Confirm that the pages qualify. Check the actual job listing or livestreaming-event content, its structured data, and whether the URLs are under a property you control. Be sure the pages are genuinely available or have the appropriate removal state.
- Create or select a Google Cloud project. Enable the Indexing API for that project. Keep standalone project environments and permissions organized instead of sharing privileged credentials casually.
- Create a service account. This identity will authenticate your requests. Protect any credentials or private keys you use and don't expose them in WordPress pages, public repositories, or client-side JavaScript.
- Verify the site in Search Console and grant ownership access. Google's prerequisites require you to verify the property and add the service account as a delegated owner. Cloud project access by itself isn't proof that you may notify Google about a particular domain.
- Obtain an OAuth access token. Authenticate API calls with the scope
https://www.googleapis.com/auth/indexing. A generic API key and an OAuth bearer token are not interchangeable in this workflow. - Review your quota and request approval. Google's initial allowances support onboarding and testing; production usage requires the appropriate approval and available quota. Start with a valid eligible URL and examine the actual response prior to processing a queue.
Follow Google's authentication guide and current client libraries for Python, PHP, or other languages instead of copying outdated authentication snippets.
What About WordPress and Rank Math?
A Google Indexing API plugin, such as a WordPress or Rank Math-based integration, may simplify configuration or request submission. It may't broaden Google's eligible content types. Check what the particular plugin sends, how it stores credentials, which pages it selects, and whether those pages meet Google's rules. A plugin's success message may describe a submitted notification, not an indexed page.
Prior to automating, confirm qualifying content, ownership, authorization, a valid token, and sufficient approved quota.
Submit Updates, Removals and Status Requests
The API separates update, removal, and notification-status operations.
| Action | API Request | What It Does | What It Does Not Prove |
|---|---|---|---|
| Notify Google about a new or updated eligible page | URL_UPDATED using POST /v3/urlNotifications:publish |
Records an update notification and may prompt Google to recrawl | That Google has fetched, indexed, or ranked the page |
| Notify Google that an eligible page was removed | URL_DELETED using the same publish endpoint |
Records a removal notification once the URL meets removal prerequisites | That the page immediately disappears from every search result |
| Read the latest notification information | GET /v3/urlNotifications/metadata?url=ENCODED_URL |
Returns the most recently received update/removal notifications for the specified URL | The URL's live Google index status |
To read notification metadata, send an authenticated GET request with the page URL encoded in the url query parameter. For example: https://indexing.googleapis.com/v3/urlNotifications/metadata?url=https%3A%2F%2Fexample.com%2Fjobs%2F123. This endpoint reports notifications Google previously received for that URL, not whether the page is indexed.
As an example, a notification about a real, eligible job listing uses a JSON body like this:
{
"url": "https://example.com/jobs/123",
"type": "URL_UPDATED"
}
Send authenticated JSON to https://indexing.googleapis.com/v3/urlNotifications:publish with application/json and the required url and type fields.
For removal, prepare the page first. Before sending URL_DELETED, the page URL must return HTTP 404 or 410, or the page must contain a noindex robots meta tag. These conditions apply to the source page, not to the API response. A notification doesn't replace proper removal.
What Does a Successful Response Mean?
An HTTP 200 from the publish endpoint indicates that Google accepted the API call and returned notification metadata. It doesn't say the page is indexed. The metadata endpoint records notification receipt, not a subsequent crawl or index decision.
| Evidence You Have | Supported Conclusion | What Remains Uncertain |
|---|---|---|
HTTP 200 for URL_UPDATED |
Google accepted the notification | Whether or when Googlebot revisits the URL |
| Notification metadata with a timestamp | Google recorded the latest request of that type | Whether the page was crawled or indexed |
| A verified Googlebot request in server logs | Googlebot requested the URL at an observed time | Whether the content was selected for indexing |
| Search Console's indexed information for a verified property | Google's own reported indexed state and canonical selection | Whether the page will appear or rank for a particular query |
Where you need Google's diagnostic information for a URL you own, use the Google URL Inspection Tool. Its indexed record and live-test results answer distinct questions, so an API notification or a successful live test should not be presented as an indexing verdict. A standalone third-party index check is a distinct type of signal again.
Quotas, Limits and Batch Requests
A Google Indexing API quota is a limit on permitted API operations, not a promise that Google will index the same number of pages. The official quota documentation, updated July 16, 2026, describes initial default allowances for onboarding and testing, with extra approval required for broader usage.
| Documented Limit | Initial Default Or Rule | Practical Meaning |
|---|---|---|
| Publish notifications per project | 200 per day by default | Includes both update and removal notifications; further usage requires approval |
| Read-only metadata requests | 180 per minute per project by default | Controls how frequently notification information may be queried |
| All API requests | 380 per minute per project by default | Standalone request-rate ceiling still applies |
| Batch request size | Up to 100 API calls in one batch | Reduces connection overhead; it doesn't make 100 URL operations count as one quota unit |
These are initial defaults, not guaranteed production entitlements. Check your project's actual quota and approval. Google offers the official API without payment, but eligibility restrictions still apply.
A batch handles multiple eligible URLs efficiently; it doesn't permit unlimited ordinary-page submissions. Google's format also limits the size of each part. Batching never removes validation or quotas.
Google explicitly warns against circumventing limits, such as via multiple accounts. Where you need higher capacity, use its approval process instead of credential rotation or unsupported workarounds.
Why an Indexing API Request Fails
When the Google Indexing API isn't working, start by identifying which layer failed: page eligibility, ownership, authentication, request format, available quota, or the later indexing decision. These require distinct remedies.
| Symptom Or Response | What To Investigate | Useful Next Action |
|---|---|---|
| The URL is a normal article, product page, or unrelated backlink donor URL | Unsupported content type | Stop using the official API for that page; select the ordinary discovery route |
400 bad request |
Invalid URL, missing field, malformed JSON, unsupported notification type | Check the endpoint, url, type, and JSON content type against Google's specification |
401 unauthorized |
Missing, expired, or incorrect OAuth access token | Refresh authentication and check the required OAuth scope |
403 forbidden |
Missing API access, property ownership, or a quota-related restriction | Read the response's error reason. For access or ownership errors, confirm API configuration, the verified property, and delegated-owner permissions; for quota errors, check the project's approved limits |
429 too many requests |
The request rate or available quota has been exceeded | Check the reported error reason, reduce request frequency, and review the approved quota allocation |
| A removal notification is rejected | The source page has not met removal prerequisites | Make the page URL return HTTP 404/410 or apply a noindex robots meta tag prior to notifying Google |
HTTP 200, but the page isn't indexed |
The notification was received, but indexing is a standalone Google decision | Inspect the page and Google's available indexed information; don't resend blindly |
A 500 or 503 response may reflect a temporary service problem; use controlled retries and Google's error guidance instead of flooding the endpoint. For particular responses and rejection messages, refer to Google's Indexing API errors.
A distinct script or plugin may't confer ownership or eligibility. And an error-free notification isn't a positive indexing decision.
What to Use for Pages That Do Not Qualify
Most ordinary websites don't need the official Indexing API. The better option depends on whether you own the page, whether you have to help Google discover many URLs, and whether your real question is about submission or verification.
| Your Page Or Goal | Better-Fit Workflow | Why |
|---|---|---|
| An eligible live job posting or qualifying livestreaming page | Official Google Indexing API | Supported update and removal notifications for time-sensitive content |
| One significant page on a Search Console property you control | Request indexing for a URL | Official manual recrawl request, subject to eligibility and Google's decision |
| Many ordinary pages on your own site | Submit and manage XML sitemaps | Scalable discovery signal without pretending every URL requires an API notification |
| A page with uncertain crawl, canonical, or indexing status | Google URL Inspection Tool | First-party diagnostics for verified properties instead of notification metadata |
| A selected list of ordinary URLs for an independent delivery workflow | Nuclear Link Indexer URL indexing delivery | A standalone commercial processing service, not Google's official Indexing API |
| A public URL on someone else's domain | Contact its publisher for site-side issues; use permitted independent observation | Your Search Console property and API credentials don't confer control over the publisher's URL |
Nuclear Link Indexer is independent of Google. Its technical pre-check, URL delivery, and recorded Googlebot observations are not official Indexing API operations. Its separate paid Google Index Checker uses a limited site:-based signal, not verified Search Console indexing data.
Use Google's official API only for genuinely eligible pages with the required permissions. For everything else, select the appropriate discovery, manual request, or diagnostic workflow and judge the outcome using evidence that answers your actual question. No notification or submission service controls Google's decision to index a page.