What 19 days of logged Search Console submissions taught us about the indexing quota

By Nan Liang · 2026-10-26

Between 2026-10-07 and 2026-10-25 we logged every Search Console request-indexing submission on one account: 154 successful submissions across 19 days, with the daily cap floating between 8 and 16. The quota is account-wide, shared across every property, and it resets on a rolling 24-hour window — not at midnight.

How many URL inspection requests can you submit per day?

Between 8 and 16 per day, and the honest planning number is 11. On days when we measured the cap from a fresh pool it landed on 9, 11, 13, or 16. From 2026-10-20 to 2026-10-25 the cap was exactly 11 on six consecutive days, each ending with the 12th click rejected. The folklore number “about ten” is not wrong, but it hides the range — and the range is what breaks batch plans.

This blog published a first three-day measurement on 2026-10-12 in an earlier post; every claim in it still holds after the larger sample below.

Is the quota per account or per property?

Per account. Every property under one Google account draws from the same daily pool. On 2026-10-09 we logged sixteen successful submissions spread across four different properties — one, six, eight, and one — and the seventeenth request at 17:21 was rejected regardless of which property it targeted.

Switching sites changes nothing because switching sites is not switching accounts. In our tests, changing IP address or using an incognito window made no difference either — the only action that draws from a different pool is logging into a different Google account.

When does the quota reset?

On a rolling 24-hour window, one submission at a time — not at midnight, and not at any fixed hour. On 2026-10-16 our last submission went through at 19:11:38. The next afternoon, on 2026-10-17, a 13:42 request was still rejected, while submissions at 19:30 and 19:31 succeeded.

The popular “wait for Pacific midnight” advice fails in our data. So does the fixed-hour Beijing-time claim we tested on 2026-10-08: a 14:31 request was rejected, a 15:00:54 re-test was still rejected, and the pool only came back at 17:05. A rolling window has no reset hour; each successful submission frees its slot exactly 24 hours later.

What does hitting the limit look like?

A specific banner, and two operational details that matter. The rejection appears after the click, not before, and its wording is unambiguous — the page says the daily quota has been exceeded and asks you to try again tomorrow. A rejected click consumes nothing: on 2026-10-19 our first click was rejected at 13:45 and the account’s total consumption for that day stayed at zero.

The signature is consistent enough to plan around. When a batch ends with a rejection, stop the batch — the remaining URLs go to the next rolling window, and probing later the same day costs nothing but time. We screenshot every rejection; the table above is built from those screenshots, not from memory.

Why do some days allow 11 and others 16?

We do not know, and we will not pretend to. Sixteen went through on 2026-10-09; from 2026-10-20 through 2026-10-25 the cap was 11 every single day. Request pacing, account history, and property mix are hypotheses we have not controlled for, and our sample is one account over three weeks.

What we can say safely: the cap is stable within a stretch of days but floats across weeks. Any submission schedule built on an exact number — including “11”, our own planning value — will eventually break, which is why the batch rule is “stop at the cap, roll the rest,” not “submit N per day.”

How was this measured?

Every number in the table above is a logged click in the URL Inspection interface, recorded on the day it happened, with a screenshot for every rejection. Nothing in this page is reconstructed from memory or copied from someone else’s account. The protocol, exactly as run:

• Channel: manual and browser-automation clicks in the Search Console URL Inspection UI, one URL at a time. No API was used.
• Cap signal: only the exact daily-quota wording counts as a rejection. Nothing else — no transient errors, no progress dialogs.
• Counting: one click is one submission attempt. Rejected clicks are not counted as successes and, per the 2026-10-19 observation, consume no quota.
• Sample: one Google account, 154 successful submissions and 15 rejections between 2026-10-07 and 2026-10-25. This blog and several small tool properties sit under the same account.
• Detector honesty: on 2026-10-17 our automation flagged a quota rejection that was not one — the inspected URL’s slug happened to contain the word “quota”, and the screenshot showed a progress dialog, not the quota banner. We tightened the matcher to the exact platform wording. We publish this because a quota dataset with silent false positives is worse than a small one.

What does this data not prove?

Everything above is one account, three weeks, manual submissions. Google does not document this quota, does not promise it, and can change it without notice — these numbers describe October 2026, not a policy. If you schedule around them, re-measure on your own account first.

And if your bottleneck is producing pages worth submitting, the waste usually starts earlier: 72.6% of keyword probes return nothing, so seed choice decides how many URLs you even need in the queue. More measurement notes live on the blog; the tools we run are on /tools.

Frequently asked questions

How many URLs can you submit to Google Search Console per day?

In our measurement, between 8 and 16, with 11 as the practical planning number. Across 19 days of logged submissions on one account, from 2026-10-07 to 2026-10-25, the cap landed on 9, 11, 13, or 16 when measured from a fresh pool — and from 2026-10-20 onward it was 11 on six consecutive days, each ending with the 12th request rejected. Treat the quota as a range, plan batches for the low end, and stop the moment the banner appears.

Does the Search Console indexing quota reset at midnight?

No. Our data shows a rolling 24-hour window in which each submission frees its slot exactly 24 hours later. After our last 2026-10-23 submission at 20:37:54, the first 2026-10-24 click succeeded at 20:39:06. Waiting for Pacific midnight, or for any fixed hour, failed every time we tested it — including the 15:00 Beijing-time claim we falsified on 2026-10-08, when the pool only returned at 17:05.

Is the request indexing quota per site or per account?

Per account, shared across every property the account owns. On 2026-10-09 we logged sixteen successful submissions spread over four different properties under one account, and the seventeenth was rejected no matter which property it targeted. Changing your IP address or using an incognito window made no difference in our tests — the only way to draw from a different pool is a different Google account.

Do rejected indexing requests use up quota?

No. On 2026-10-19 our first click of the day was rejected at 13:45, and the account’s total consumption for that day stayed at zero — later checks confirmed nothing was deducted. A rejection is the quota telling you the pool is empty; it costs you a click, not a slot. That is worth knowing operationally, because you can probe whether a window has opened without spending anything.

Can you get more indexing quota with a second Google account?

Sometimes, but not a full fresh pool. Spare accounts usually own properties of their own, so their daily budget is partly spent before you arrive — in our 2026-10-08 tests, three spare accounts hit the cap on their first or fifth request. If you keep a second account for submissions, check what else it owns and measure its actual cap before counting on it. An account that already carries several properties is not a fresh account.