How many URLs can you request indexing per day? Every article that answers this gives you a number, usually ten or twelve, and none of them says where the number came from. I went and checked, and the honest answer is that Google has never published one.
What Google does publish is three other numbers, for three other channels, and those are the ones worth knowing, because on any job big enough for the cap to hurt you the manual button is not where the work gets done anyway.
What Google actually says about the Request Indexing limit
The Search Console help page for the URL Inspection tool says exactly this: “There is a daily limit to how many index requests you can submit.” That is the whole statement. No figure, no reset time, no clarification about whether the allowance belongs to the property or to the person clicking.
The Search Central documentation on asking Google to recrawl adds one more sentence worth having: “there’s a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won’t get it crawled any faster.” Again, a quota exists, and again there is no number attached to it.
So when a post tells you the limit is ten or twelve or twenty per day, that is somebody’s observation being passed along as documentation. My own observation, from running this every working day, is that it is around a dozen before the tool cuts me off, and I have said so on this site. I am labelling it here as what it is: a pattern I see, not a published figure, and not something to build a process around. Two things about it are genuinely uncertain and I am not going to pretend otherwise. Whether the allowance resets on a rolling window or at a fixed hour, and whether it attaches to the property or to the user account, are both unstated by Google, and the trade posts contradict each other on both.
There is one documented restriction that does bite, and almost nobody mentions it. The same help page says: “You cannot request indexing if the page is considered to be non-indexable in the live test.” The tool runs a live check before it lets you submit, so a page carrying a noindex tag, a robots block or a redirect will refuse the request outright. If you are working a list without checking status first, you will burn attempts discovering that.
The three limits Google does publish
Three of those four rows deserve a note.
The URL Inspection API cannot request indexing. This is the misunderstanding I correct most often. Google’s launch post for the API says it “will return the indexed information” for a URL, and that is all it does. It reads status. It does not press the button. So its 2,000 a day is a diagnostic budget, not a submission budget, and no amount of it substitutes for the manual cap.
The URL Inspection API has no per-user quota. Search Analytics has one; this API does not. The limits are per site and per Cloud project. Adding more verified users to the property does not multiply your inspections, which is the workaround people reach for and it does not work. Verifying more properties genuinely does, because the 2,000 is per site, so a large domain split into sensibly scoped properties has a larger combined budget than the same domain as one property.
The Indexing API is not for normal pages. Its quota page states 200 publish requests per day per project, and the API is documented for JobPosting and BroadcastEvent page types only. The 200 sounds generous next to a dozen, right up until you read which pages it applies to. I have written up what the Indexing API does and does not do for ordinary pages separately, because it is sold as a general indexing shortcut constantly and it is not one.
What the cap actually forces you to do
The cap is a rationing problem, not a limit problem, and once you see it that way the daily number stops mattering very much.
The largest job I have run was a baby products store: 1,006 manual submissions across 118 days. Divide it out and the average day is around nine URLs. That was never a volume exercise. Every morning the question was which handful of URLs deserved that day’s slots, and the answer came from a ledger, not from the top of a list. The full routine is in the anatomy of that 118-day indexing job.
The priority order I settled on, in order:
- New pages and genuinely fixed pages. These are the only two categories where the button reliably does something. A page Google has crawled and declined is not going to change its mind because you asked twice, which is the boundary I set out in does request indexing actually work.
- Pages that were indexed and dropped out. These are the expensive ones and they are silent. Nothing alerts you.
- Nothing else. Pages sitting in crawled and currently not indexed do not get slots. They get content work or they get left alone.
The two habits that save the most slots are both about not spending them:
Inspect before you request. Because of the live non-indexable check, a page with a stray noindex or a canonical pointing elsewhere will reject your submission anyway. Checking status first turns a wasted attempt into information. That is the reason I built the bulk URL inspection tool on this site: paste the list, get the real statuses back in one pass, then decide what is worth a slot. The wider comparison of ways to do that at scale is in bulk URL inspection tools.
Move the bulk through sitemaps. Sitemaps have no per-day quota, and they are the only channel that scales to a catalogue. Segmenting sitemaps by template or by section, keeping lastmod honest, and then reading submitted against indexed per sitemap does more for a large site in a month than the manual button does in a year. The button is for the pages you are actively arguing about.
The honest summary
Google publishes a limit for the URL Inspection API and a limit for the Indexing API. It does not publish one for the button. If your plan depends on knowing that number exactly, the plan is aimed at the wrong channel: a dozen a day, whatever the true figure turns out to be, was never going to clear a backlog. Ration it toward the pages that are new or actually fixed, and let the sitemap carry everything else.
Sources
- Google Search Console Help, URL Inspection Tool, for “There is a daily limit to how many index requests you can submit” and “You cannot request indexing if the page is considered to be non-indexable in the live test”, checked 6 September 2026. Note that no figure is given for the limit
- Google Search Central, Ask Google to recrawl your URLs, for “there’s a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won’t get it crawled any faster”, checked 6 September 2026
- Google Search Console API, Usage limits, for the URL Inspection quotas of 2,000 queries per day and 600 queries per minute per site, and 10,000,000 queries per day and 15,000 per minute per project, and for the absence of a per-user quota on this API, checked 6 September 2026
- Google Search Central, Indexing API quota and pricing, for the 200 publish requests per day per project, checked 6 September 2026
- Google Search Central Blog, The URL Inspection API, for the API returning indexed information rather than submitting URLs, checked 6 September 2026
