Google updates Indexing API quotas, without opening it to ordinary articles

Google updated its Indexing API quota documentation on October 16, 2026, removing an outdated form and restating the current limits. For publishers, the important boundary remains: the API is not a general submission route for news articles, guides or category pages.

The official change log describes a documentation update. It does not announce a new indexing entitlement, a ranking change or an expansion to ordinary editorial content. Website owners evaluating an indexing service should ask what eligible page type that service actually submits.

The allowance counts notifications, not indexed pages

The current quota page lists a default of 200 publishing requests per project per day. Both URL_UPDATED and URL_DELETED consume that allowance. It resets at midnight Pacific Time, rather than at midnight in the publisher's own time zone.

Separate limits cover metadata reads and total request volume: 180 metadata requests per minute per project and 380 requests per minute per project across endpoints. The documentation says use of the API is available without payment. Those statements describe the API, not the prices an outside consultant may charge.

A successful notification also should not be recorded internally as a completed indexing result. Keep the submission log separate from evidence that a page actually appears in search. That distinction prevents a service's activity counter from becoming a misleading performance report.

Eligibility comes before a larger quota

Google's quickstart restricts the API to pages with JobPosting, or BroadcastEvent embedded in VideoObject. Adding an unrelated structured-data label to an article does not turn it into an eligible job or livestream page.

For a publication that genuinely runs a jobs board, audit that section independently. Check the page type, project ownership, notification frequency and deletion handling. A publisher with only articles has a different task: maintain discoverable links and investigate access or indexing problems through the normal search workflow.

What to check in an existing integration

Ask whoever maintains the connector to identify the project consuming quota and show which request types it sends. Confirm the reset time before diagnosing an apparent overnight failure. Treat repeated retries as an operational issue to examine, rather than a reason to buy another submission package.

If the underlying problem is that important pages have disappeared, start with a traffic-drop investigation. If the intended outcome is removal, review the difference between hiding a URL and removing it. Neither problem is solved simply by increasing the number of notifications a connector reports.