Quota
Fix: Indexing API quota exceeded (429 RESOURCE_EXHAUSTED)
HTTP 429 — "Quota exceeded for quota metric 'Publish requests' and limit 'Publish requests per day'."
The default Indexing API project gets 200 publish requests/day and 600/minute. A 429 means you hit one of those. Spread submissions across days, request a quota increase through Google's form, and use sitemaps for the long tail. Because each project has its own 200/day, running on your own Cloud project gives you your own full quota.
A 429 from the Indexing API means you've run into a rate limit, not a permissions wall. There are two separate quotas, and the error message tells you which one you tripped: a daily cap and a per-minute burst cap.
The two quotas
- Publish requests per day — 200 by default, per Cloud project. This is the one most people hit.
- Publish requests per minute — 600 by default. You'll only see this if you fire requests in a tight loop with no throttling.
Both are per Google Cloud project, not per property and not per Google account. That detail matters: a project's 200/day is yours alone, which is exactly why pooling submissions through a shared third-party account is fragile — everyone shares one cap. Running on your own project means the 200/day is entirely yours.
What to do about it
- Read the message: "per day" vs "per minute" tells you whether to wait until the daily reset (Pacific midnight) or just throttle your loop.
- If it's the per-minute cap, add a small delay between requests or cap concurrency — 600/min is generous if you pace it.
- If it's the daily cap, prioritize. Submit your highest-value or most-recently-changed URLs first; the rest can wait for tomorrow's reset.
- Request a quota increase: Google Cloud Console → IAM & Admin → Quotas, filter for the Indexing API, select the Publish requests quota, and submit an increase request with a justification.
- Cover the long tail with a sitemap. Sitemaps don't burn Indexing API quota and still tell Google the URLs exist — use the API for the pages that need a crawl now, sitemaps for everything else.
Search Console's manual "Request indexing" gives you roughly 10–20 requests a day. The Indexing API's 200/day is an order of magnitude more — quota exhaustion usually means you're operating at a scale where batching and prioritization, not the manual button, is the answer.
IndexerNow runs on your own Google account, your own Cloud project, and your own quota — we never pool submissions through a shared account. Connect your GSC and push the URL through Google's Indexing API in two clicks.
Connect your own GSC and index nowFrequently asked
When does the daily Indexing API quota reset?
At midnight Pacific Time. If you hit the 200/day publish cap, the counter resets then and you can submit again.
Can I get more than 200 requests per day?
Yes — request a quota increase in Google Cloud Console under IAM & Admin → Quotas for the Indexing API. Approval isn't guaranteed; a clear justification (site size, legitimate use) helps.
Does each Search Console property get its own quota?
No. The quota is per Google Cloud project, shared across all properties that project's service account owns. To get a separate 200/day, you'd use a separate project.