Is there a 1,000-per-day limit on Search Console removals?
20 September 2026
If you look for a way to remove a lot of URLs from Google Search at once, you will run into the same number everywhere: Google limits you to 1,000 removal requests per 24 hours. Google's own AI Overview states it as fact, and cites the Chrome Web Store as its source.
I went looking for a primary source. I could not find one.
What Google's documentation says
The help page for the Removals and SafeSearch reports tool gives no daily cap and no per-property quota. It gives no number for how many requests you may submit at all.
The one number it does repeat is about duration, not volume:
A successful request lasts only about six months.
That is the sentence people should be quoting, and mostly aren't. A removal is a temporary hide, not a deletion. It expires on its own.
Where the 1,000 figure does appear
It appears in the store listings of the bulk removal extensions themselves. One of the most-installed ones states it directly:
Google imposes a 1000 removal limit per 24 hours.
Another repeats essentially the same claim, and tells users to split larger jobs into 1,000-URL batches, one per day. So at least one source feeding the number back into search results is a tool description — not Google.
I am not claiming to have traced the exact path from those listings into the AI Overview. I am saying the number is being repeated by parties who benefit from it being true, and that Google's own documentation does not support it.
What 300 requests actually did
On 15 September 2026 I submitted 300 removal requests against a property I own, in one sitting, through the Search Console interface.
These are measured, not estimated.
What that does and doesn't show
300 is not 1,000. One run on one property says nothing about where the ceiling is. It only shows that 300 did not reach one.
- The limit may exist above 300 and I simply didn't get there.
- It may be account-dependent or property-dependent.
- It may be a figure from the old Webmaster Tools interface that got carried forward when Google rebuilt the tool, and was never re-checked.
Any of those would be a reasonable explanation. What isn't reasonable is treating a number with no primary source as a hard constraint, and building workflows around it.
What would settle it
Someone who has actually hit a wall, and can say where. Specifically:
- At what number of requests did it stop?
- Was it exactly 1,000?
- Per property, per Google account, or something else?
- An explicit quota error, or did submissions just start failing quietly?
If you have hit it, I would like to hear the numbers — lmy8129@gmail.com. I will add what people report to this page, with or without attribution, whichever you prefer.
A note on how I ran this
The 300 requests were submitted by a Chrome extension I built, which deliberately does not assume a limit. It detects throttling when it actually happens, stops, saves progress, and tells you. That design choice is the reason I went looking for the source of the number — I did not want to hard-code someone else's folklore into a tool.
The extension is Bulk URL Removal for Search Console. It is not the point of this page, and you do not need it to check any of the above.