Indexing
Google Request Indexing Limits: How Many URLs Per Day, Really
Google does not publish a daily Request Indexing number, despite the 10-15 figure everyone repeats. Here are the limits Google actually documents, and what happens when you try to exceed them.

Google does not publish a daily limit for Request Indexing. The official Search Console documentation says only that "there is a daily limit to how many index requests you can submit." No number. The figures you have seen everywhere, 10 per day, 12 per day, 15 per day, come from SEO blogs and forum threads, not from Google.
That distinction matters more than it sounds, because a whole category of tooling and a popular Reddit tactic are built on top of a number Google never published. This guide separates what Google actually documents from what the industry repeats.
The limits Google actually documents
There are two different submission paths with two very different levels of documentation. Confusing them is the root of most of the bad advice on this topic.
| Search Console Request Indexing | Indexing API | |
|---|---|---|
| Documented daily limit | None published. Google says only "there is a daily limit" | 200 publish requests per day per Cloud project |
| Other documented limits | Not published | 180 read-only metadata requests/min; 380 general endpoint requests/min |
| What it accepts | Any URL on a verified property | Officially only JobPosting or BroadcastEvent in a VideoObject |
| Can you raise it? | No published mechanism | Yes, by form, but approval requires the structured data above |
| Realistic use | A handful of priority URLs | Job boards and livestream sites |
The Indexing API is the only one of the two with hard published numbers. If you want those numbers raised, Google's quota page is explicit that approval is contingent on the site using JobPosting or BroadcastEvent structured data markup. That single sentence quietly disqualifies most sites that apply.
Where the "10 to 15 per day" figure comes from
It comes from SEO practitioners observing when the "Quota exceeded" message appears, then publishing that observation as if it were policy. The number then gets cited by the next article, and the next, until it reads like documentation.
It is worth being precise about what is and is not true here:
- True: a daily limit exists. Google says so, and the "Quota exceeded" notice is real.
- True: people consistently hit it somewhere in the low double digits.
- Not established: that the limit is exactly 10, 12, or 15, that it is the same for every property, or that it is a fixed constant at all.
There is also a stale piece of news that muddies this. A Search Engine Land article titled "Google Search Console request indexing limit removed" circulates as evidence that there is no limit any more. That article is from February 2018 and describes a limit notification disappearing from the old Search Console interface, while noting the limit "remains in the help documentation on Google's own site." It is not a statement that the cap was lifted, and it predates the current Search Console entirely.
So the honest answer to "how many URLs per day?" is: an unpublished number in the low double digits, which you should not build a process around.
Re-submitting the same URL does nothing
This is the most expensive misunderstanding, because it burns the quota you do have.
Google's documentation is clear that submitting a request more than once for the same URL does not speed anything up, and that requesting indexing is not a guarantee of inclusion. Request Indexing puts a URL in a crawl queue. It does not vote for the URL, and it does not override the quality and duplication checks that happen after the crawl.
If a page has been requested once and still is not indexed after a couple of weeks, requesting it four more times will not change the outcome. The blocker is somewhere else, and it is usually one of the reasons covered in Google is not indexing my site. If Search Console shows the URL as Discovered, currently not indexed or Crawled, currently not indexed, those statuses tell you the real cause, and neither is fixed by resubmission.
The service account rotation trick, and why it is a bad idea
Search for this topic on Reddit and you will find a recurring, heavily upvoted pattern. Two representative posts:
"google search console limits you to 10 urls per day. here's how i submit 2000+ ... you can create multiple service accounts and rotate between them. 10 service accounts = 2000 submissions per day."
"created 15 google cloud service accounts (each gets 200/day = 3000/day total) ... the tool rotated across all 15 keys automatically."
The tactic is real and it does technically work in the short term. It is also explicitly named as abuse in Google's own documentation. The Indexing API quickstart states:
"Any attempts to abuse the Indexing API, including the use of multiple accounts or other means to exceed usage quotas, may result in access being revoked."
This is not an ambiguous grey area or an oversight Google has not noticed. "The use of multiple accounts to exceed usage quotas" is the exact tactic, described in the exact terms, in the sentence about revoking access. Note also that most posts promoting this method are promoting a paid tool that performs the rotation, which is worth factoring into how you read them.
There is a second problem stacked on top of the first. Even if rotation were permitted, the Indexing API officially only supports JobPosting and BroadcastEvent pages. Submitting ordinary blog posts and programmatic landing pages through it is outside its documented scope regardless of how many accounts you spread the requests across. We cover that gap in detail in what the Google Indexing API is actually for.
What to do instead, by site size
Match the method to the number of URLs. This is the part the quota debate distracts from.
- A handful of priority URLs. Use Request Indexing in the URL Inspection tool. This is exactly what it was built for. Submit once each, then leave them alone.
- Dozens to thousands of URLs. Use a sitemap. Google's guidance is direct: if you want many pages indexed, submit a sitemap. One sitemap file holds up to 50,000 URLs or 50MB uncompressed, and a sitemap index can chain many files together. Keep it clean and current, and drop URLs you do not actually want indexed. See how to submit your site to Google for the full submission workflow.
- Large programmatic sets. Quota is not your bottleneck, crawl demand and page quality are. Thousands of near-identical pages will not index because they were submitted, they will index because they are worth indexing and well linked. Start with why programmatic SEO pages do not get indexed.
- Bing, Yandex, and other participating engines. IndexNow has no comparable per-day ceiling for most publishers and removes the discovery delay entirely. It does not reach Google, which does not participate in the protocol.
The gap nobody's quota page covers
Here is what all of this misses. Every method above is a submission mechanism. Not one of them tells you what happened next.
You spend your daily quota on 12 important URLs. Did they get indexed? Search Console's Page Indexing report lags by several days and samples rather than reporting on demand. So you check manually, then forget, then check again a fortnight later. And if one of those pages silently drops back out of the index in three months, nothing tells you at all. That is the failure mode behind silent deindexing, and it is invisible to every submission tool on the market.
Submitting is the easy half. Confirming is the half that actually protects traffic.
SearchOptimo closes that loop: it re-checks the index status of every URL you care about on a schedule and alerts you the day a status changes, whether that is a submitted page finally landing or an established page quietly dropping out. You can run a free one-off check on a single URL with the Google index checker, test a whole list at once with the bulk index checker, or rule out the two most common blockers with the noindex checker and robots.txt checker.
Key takeaways
- Google publishes no Request Indexing number. The docs say only "there is a daily limit." The 10-15 figure is community observation, not policy.
- The Indexing API's 200/day is real and documented, along with 180 and 380 per-minute rate limits, but the API officially only accepts
JobPostingandBroadcastEventpages, and quota increases require that markup. - The 2018 "limit removed" article is not evidence. It described a notification vanishing from the old interface, not the cap being lifted.
- Re-submitting a URL is wasted quota. Repeat requests do not speed up indexing or improve the odds.
- Service account rotation is named as abuse in Google's documentation, in the same sentence as revoking access. Weigh that against a Reddit post selling a rotation tool.
- Use sitemaps past ~15 URLs, and fix crawl demand and quality for large sets. Quota is rarely the real bottleneck.
- Submission is not confirmation. Nothing in Search Console tells you the day a page leaves the index.
Want to stop guessing whether your submitted URLs actually landed? Start a free trial and watch every URL's index status on a schedule, or read our honest breakdown of whether automated monitoring is worth it for your site.
Frequently asked questions
- How many URLs can I request indexing for per day in Google Search Console?
- Google does not publish a number. The official Search Console documentation states only that 'there is a daily limit to how many index requests you can submit.' The widely repeated figures of 10, 12, or 15 URLs per day come from SEO blogs and forum posts, not from Google. Treat them as rough community observation, not a documented quota.
- What is the Google Indexing API daily limit?
- The Indexing API has a documented default of 200 publish requests per day per Cloud project, covering both URL_UPDATED and URL_DELETED request types. There are also rate limits of 180 read-only metadata requests per minute and 380 general endpoint requests per minute per project. You can apply for more quota via a form, but approval is contingent on the site using JobPosting or BroadcastEvent structured data.
- Can I create multiple Google service accounts to get around the indexing quota?
- This is a common tactic promoted on Reddit and by indexing tools, and Google's documentation explicitly names it as abuse. The Indexing API docs state that 'any attempts to abuse the Indexing API, including the use of multiple accounts or other means to exceed usage quotas, may result in access being revoked.' The rotation trick is not a loophole Google overlooked, it is a named violation.
- Does requesting indexing repeatedly make Google index a page faster?
- No. Google's documentation notes that submitting a request more than once for the same URL does not change anything, and that requesting indexing does not guarantee inclusion. Re-submitting a URL burns your daily quota without improving the odds. If a page is not indexing, the blocker is discovery, crawlability, or quality, not the number of requests.
- What should I use instead of Request Indexing for a large site?
- A sitemap. Google's own guidance is that if you want many pages indexed, submit a sitemap rather than individual requests. A single sitemap file supports up to 50,000 URLs or 50MB uncompressed, and you can chain multiple sitemaps with a sitemap index. Request Indexing is designed for a handful of priority URLs, not bulk submission.
Monitor your index status automatically
SearchOptimo re-checks your URLs on a schedule and alerts you when something drops. Start free, no credit card.
Start freeKeep reading

Indexing
How to Submit Your Site to Google (and Actually Get It Indexed)
Submitting your site to Google takes about ten minutes: verify in Search Console, submit a sitemap, then request indexing for priority URLs. Here's each step, and why submitting is not the same as getting indexed.
Indexing
How to Fix "Discovered – Currently Not Indexed" (2026)
Discovered – currently not indexed means Google found your URL but hasn't crawled it. The quick fixes, a decision tree for when to wait or prune, and how it differs from crawled - not indexed.

Indexing
Crawled but Not Indexed? It Is Not Your Technical Setup. It Is Authority.
If Google crawled your page but will not index it, your technical SEO is probably fine. The status itself proves it. Here is what actually decides indexing, and how to tell.