ContentsTap to jump to a section＋
- This documents current limits; Google does not announce a quota increase.
- The default is 200 publish requests per day per project, shared by URL updates and deletions.
- Use the API only for supported page types, not as a universal replacement for sitemaps.
A documentation change with a clear date
Google Search Central’s October 16, 2026 changelog records an update to the Indexing API quota page to reflect current limits and processes and remove an outdated form. Teams following old integration material should review their references.
The changelog does not announce a quota increase or general submission access. A successful API notification does not guarantee indexing or ranking.
The published default limits
The page specifies 200 publish requests per day per project, shared by URL_UPDATED and URL_DELETED. Default read-only metadata requests are limited to 180 per minute per project; the overall limit is 380 requests per minute per project. Daily quota resets at midnight Pacific Time.
Friday Works recommends accounting across all jobs using a project. Update and deletion workers share the daily allowance. These are documented defaults; verify the actual configuration rather than assuming every project is identical.
Eligible page types remain essential
Google’s usage guide limits the API to pages containing JobPosting or BroadcastEvent embedded in VideoObject. The October 16 documentation update is not permission to send every service page or ordinary blog article.
For other content, use the appropriate sitemap, internal-linking and crawlability practices. Friday Works advises against selling guaranteed indexing on the strength of a successful request or paid submission script.
Audit the integration that is actually running
Identify the Cloud project, service-account owner and quota-error logs. Check API responses before retrying. Uncontrolled repeated submissions obscure diagnosis and share the remaining request allowance unpredictably.
An eligible workflow receiving duplicate queue entries should establish which record needs notification and which has already been processed. This is Friday Works’ implementation recommendation, not a newly announced Google queue requirement.
Check page outcomes separately
Record eligible URLs, actual limits, scheduled reset behavior and an error owner. Investigate canonical, access restrictions and indexing decisions independently of API response success.
The article shows Google’s real documentation rather than a fabricated quota table. This October 18 report retains the October 16 change date and makes no quota-growth or traffic-growth claim.
References
Sources used in this guide
We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.
- Search Central documentation changelog — 16 October 2026Google ↗︎
- Indexing API quota and pricing — updated 16 October 2026Google ↗︎
- Indexing API usage and supported page typesGoogle ↗︎
- Original screenshot of Google Developers quota documentation; proportional resize and neutral margin; no table reconstructionGoogle Developers / captured by Friday Works ↗︎
- Documentation content CC BY 4.0; screenshot includes factual page branding for identificationGoogle Developers ↗︎