Google Removes Indexing API Approval Instructions

Google has removed the Indexing API approval form and application instructions from its documentation, leaving developers without clear guidance on how to obtain permission for access or request higher quotas.

The change was made on 16 October 2026. Although Google updated its documentation to reflect current quota limits and remove an outdated form, it has not clarified whether the approval requirement itself has changed.

What Has Changed?

Previously, Google’s quota documentation explained that the Indexing API provided an initial allowance for testing and required additional approval for wider use and resource allocation. It also included a section explaining how to request approval and additional quota.

Following the update, these instructions have disappeared. Google’s quickstart guide no longer lists approval and quota requests as part of the initial setup process, while its usage documentation has also removed references to the approval process.

The documentation changes leave developers with unanswered questions about how to apply for access and whether existing applications are still being reviewed.

Which Quota Limits Remain?

Google’s documentation continues to list the default API limits for each project:

Daily allowance: 200 publishing requests, including updates and removals.
Per-minute allowance: 180 metadata requests and 380 requests across all endpoints.
Daily reset: The quota renews at midnight Pacific Time.

The API remains restricted to pages containing JobPosting or BroadcastEvent structured data within a VideoObject. Google’s spam policies also continue to apply, and developers are warned against attempting to bypass submission limits by using multiple accounts.

Google’s job posting guidance still recommends the Indexing API for job posting URLs, while sitemaps remain an option for broader website coverage.

Why Does This Matter?

The removal of the approval instructions creates uncertainty for developers, particularly job board operators who rely on the API to notify Google about new or updated listings.

Some job board operators previously reported waiting months for responses to their approval requests, with no clear indication of when a decision might arrive. The latest documentation changes offer no clarification on the status of pending applications or whether projects without approval can use their default quotas for live content.

As a result, developers may find it more difficult to determine the correct process for obtaining access or increasing their request limits.

What Should Developers Do Next?

Developers can check their project’s current quota through the Google API Console, which remains linked from the documentation.

For now, monitoring Google’s Indexing API documentation and changelog is the most practical way to stay informed about any changes to the approval process or future guidance on requesting higher quotas.