Guide · Search Console quota

How many "Request indexing" can you submit a day? 14 rounds of records over 10 days, and what happened after

Updated 2026-11-12 · kagentx

Short answer

Google officially says only that Request indexing has a daily limit, with no number and no reset time. In our 14 rounds of records between 2026-11-03 and 12, the most we got through in one round was 18; when the quota message appeared, the number already submitted ranged from 0 to 18, with no fixed number; "16:00 Beijing time reset" explains most records but three do not fit. We cannot conclude whether submitting helps: 7 of the 8 kagentx pages we could not submit on 11-03 got indexed on their own, and most of what MochiStamp submitted were recrawl requests for pages already indexed.

How many Request indexing submissions can you make a day?

Google gives no number, only a daily limit. In the 14 rounds we have records for between 2026-11-03 and 11-12, the most we got through in one round was 18, and 5 rounds got through none or only 1; when the "quota exceeded" message appeared, the number already submitted ranged from 0 to 18, so there is no fixed number.

Official wording (read 2026-11-12): Search Central's "Ask Google to recrawl your URLs" says "there’s a quota for submitting individual URLs", and the URL Inspection help page says "There is a daily limit to how many index requests you can submit". Neither gives a number, nor says whether it is counted per account or per property, or when it resets.

Date and round (Beijing time)SubmittedWhen the quota message appeared
11-03 afternoon10Appeared at the 13th submission (including 2 accidental duplicate submissions); 8 kagentx pages were not submitted
11-04 morning (from 10:15)0Tried 7 more, all showed the quota message
11-04 evening (from 19:14)11No message; another 7 pages were already indexed, not submitted
11-05 morning (from 10:13)0The very first one showed the message
11-05 evening (from 19:14)1Message from the 2nd (3 tried in a row)
11-06 morning (from 10:14)10No message
11-06 late afternoon (from 17:15)52 showed "daily quota exceeded"
11-07 morning7No message
11-07 late afternoon (from 17:14)1From the 2nd, all three properties showed it (around 17:30)
11-09 morning12MochiStamp 6, Gamma 5, kagentx 1; message from Gamma's 6th and kagentx's 2nd
11-09 late afternoon (from 17:20)6kagentx 2, MochiStamp 1, Gamma 3; message at kagentx's 3rd and MochiStamp's 2nd; also two "Something went wrong" errors
11-10 morning9MochiStamp 6, kagentx 3; no message
11-11 late afternoon (from about 17:30)18MochiStamp 10, Gamma 6, kagentx 2; all three properties showed the message in the end
11-120Not submitted: the previous window was used up, saved for the evening round

11-08 was a Sunday and has no record. The three sites use the same Google account, and the operator's other sessions also submit, so the counts in the daily reports may not be the account's total for the day; we cannot confirm this.

For the earlier three days, 11-03 to 05, see How do you get a new website indexed by Google? How many indexing requests can you send a day?.

Is the quota counted per account or per property?

Our records do not fit one fixed number. By property, the number already submitted in the same round when the message appeared: MochiStamp at least 1 and at most 10, Gamma AI Slide at least 0 and at most 6, kagentx at least 0 and at most 4 (we counted these round by round from the daily reports, which do not record the time of each submission). If the quota were one number for the whole account, the three properties should not differ like this; if each property had its own, the same property should not sometimes show the message at 1 and sometimes not at 10.

A reasonable guess is that both are at work: the quota has its own algorithm, plus other sessions on the same account using it up. We cannot tell them apart, so we record only the facts: the docs say nothing, and our records show no stable number. Also, the 11-11 daily report notes that Pagent and kagentx sit under the same domain property and share the quota.

When does the quota reset? Does "16:00 Beijing time" fit?

Our earlier statement was a reset at midnight Pacific time (16:00 Beijing time); that was an inference and the docs do not say. Checking it against these 14 rounds, some fit and some do not:

Fits (consistent with a 16:00 reset)Does not fit
11-04 morning (10:15) message, evening (19:14) 11 went through11-05 evening (19:14, after 16:00): message after only 1 submitted
11-05 morning (10:13) message on the first one11-06 morning (10:14): 10 went through, although the message had just appeared on the evening of 11-05, which by a 16:00 reset is the same window
11-09 late afternoon (17:20, after 16:00): 6 could be submitted again11-07 late afternoon (17:14, after 16:00): message at the 2nd

So 16:00 is only a working assumption that explains most of the records, not a confirmed fact. Two things can make it look wrong: other sessions used up the quota in that period, and the quota may not reset by the day at all (for example a rolling window), which we have not tested. If you plan around it, treat it as a rough hint: start with the pages you want most each time and stop when the message appears.

Does submitting help?

The official position is no guarantee: the help page says a request "does not guarantee" the page will appear, a page that fails the live test as non-indexable cannot be requested, and indexing typically takes about a day, sometimes around two weeks. What we saw in our records, all small samples that only show what we saw:

  • Many pages we could not submit got indexed on their own. On 11-03, 8 kagentx pages were not submitted because of the quota: when checked on the morning of 11-04, 1 was indexed; by the evening of 11-04, 6 more were indexed; the remaining 1 was submitted. So 7 of the 8 were indexed without being submitted, within one to two days.
  • Another example: /fa/phrases/kazoku, deepened on 11-07, was not submitted that day (quota full) and a spot check on 11-09 found it indexed.
  • Most pages MochiStamp submitted were already indexed and were deepened, then re-crawled on request (6 pages on 11-09, 6 on 11-10 and 10 on 11-11; the daily reports say "all already indexed"), not new pages.
  • The daily reports did not check back page by page how many days it took from submission to indexing, so we have no such number.

Impressions do not show a clear difference either. Take the MochiStamp pages deepened on 2026-11-09 (7 submitted, 17 not; Search Console data via our local dashboard): average daily impressions over the 7 days before, against the single day 11-10:

Pages deepened on 2026-11-09PagesAverage daily impressions, 7 days beforeImpressions on 11-10
Indexing requested that day732.6108.0
Not submitted that day (quota full)17141.3209.0

Both groups rose, but the whole site's daily impressions also rose over the same period, from an average of about 343 over 11-02 to 11-08 to 627 on 11-10. After deepening there is only one day of data, "submitted" was chosen by our priority rather than at random, and the dashboard's page table keeps only about 25 URLs a day, so this table cannot answer whether submitting helps. For an example page, see MochiStamp's LINE sticker size guide.

The quota is used up: what about new pages?

  1. 1. Submit "not yet indexed" pages first, then deepened pages that are already indexed

    Evidence: from 11-09 the daily reports record each page's status at the time of submission; for already indexed pages the request only asks for a recrawl, and new pages we did not submit were often indexed on their own (see above). This is our trade-off, not official advice.

  2. 2. Let the sitemap say which pages changed

    For many URLs the docs recommend a sitemap; give each URL a lastmod, see How do you write a trustworthy sitemap lastmod?.

  3. 3. Let internal links help the crawler find pages

    Link new pages from pages that are already indexed so the crawler can follow the links. Evidence: in the 11-03 kagentx example above, most of the pages we did not submit got indexed on their own.

  4. 4. Use IndexNow to notify other search engines

    IndexNow does not notify Google; it notifies Bing, Yandex and others, see What is IndexNow, and does it matter for AI search?.

  5. 5. Do not submit the same URL a second time

    The docs say repeated requests are no faster; on 11-03 one accidental action submitted the same page twice and wasted quota. After closing the dialog, wait 2 seconds before clicking.

  6. 6. If stuck at "Discovered - currently not indexed", look at the cause first

    First look at whether the page itself has a problem, then decide whether to request, see “Discovered – currently not indexed”: what to do? Discovered vs Crawled.

For where a new site's first batches of search clicks come from, see How long until a new site gets its first 100 search clicks? Four sites, real numbers.

What are the limits of these numbers?

  • One Google account, three domain properties, 14 rounds over 10 days; no per-submission timestamps within a day.
  • Other sessions use the same account, so the counts in the daily reports may not be the account's total for the day.
  • "Reset at 16:00" is an inference with records that fit and records that do not.
  • We did not check back page by page how many days indexing took after submission, and there was no random control, so we cannot say whether submitting helps.
  • The impressions table keeps only about 25 URLs a day, and after deepening there is only one day of data.

How many days Search Console data is behind and why the latest days look low is in How many days is Search Console data behind? Why are the latest days low?.

Which new pages got impressions sooner, those with an indexing request or those without, is in Does manually requesting indexing get a page impressions sooner? 83 new pages across three sites.

FAQ

How many Request indexing submissions can you make a day in Search Console?

No number is given, only a daily limit. In our records from 2026-11-03 to 12, the most we got through in one round was 18, and when the quota message appeared the number already submitted ranged from 0 to 18.

When does the quota reset?

Not stated. We schedule around midnight Pacific time (16:00 Beijing time), which explains most of our records, but 3 of the 14 rounds do not fit, so it is only a working assumption.

Is the quota counted per account or per property?

Not stated. In our records, the number already submitted in the same round when the message appeared was at least 1 and at most 10 for MochiStamp, at least 0 and at most 6 for Gamma AI Slide, and at least 0 and at most 4 for kagentx, with no stable number.

Will the page be indexed once I submit a request?

No guarantee. The official help page says submitting a request does not guarantee the page will appear, and pages judged non-indexable cannot be requested. Of the 8 kagentx pages we could not submit on 11-03, 7 were indexed on their own within a day or two.

What if the quota is used up?

Submit a sitemap with proper lastmod values, link to new pages from internal pages, and submit the "not yet indexed" pages first. IndexNow does not notify Google, only Bing, Yandex and others.

Can I submit the same URL several times?

There is no point. The docs say repeated requests for the same URL are no faster, and they use up quota.

Sources

kagentx

Do AI answers
mention you?

An evaluation asks ChatGPT, Perplexity and Claude your buyers' questions (with web search on) and records who they recommend, which pages they cite and whether you are among them. Basic $1, results usually in 2–3 minutes.