Why .vercel.app projects get immediate Quota Exceeded error in Google Search Console

(edited)

The Problem

I launched this project on March 3, 2026. I am getting an immediate "Quota Exceeded" error in Google Search Console.

This happened on my very first indexing request. I have used 0/10 of my daily manual requests. My sitemap.xml is submitted and has 11 valid URLs, but nothing is being crawled.

Technical Check

robots.txt is clear (allows Googlebot).
sitemap.xml is live and accessible.
Using Next.js 16.1 on a standard .vercel.app subdomain.

Is there a known bug or a “neighborhood” block affecting .vercel.app subdomains right now? I cannot manually index even one page.

Any advice on how to trigger the first crawl would be appreciated.

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

https://vercel.com/docs/projects/domains/troubleshooting

You can also use v0 to narrow down the possibilities.

reply to #2

I’ve looked into the issue, and it seems like the “Quota Exceeded” error is likely due to a few things. It could be a temporary limit on Google’s side for indexing requests, or there might be some restrictions on the .vercel.app subdomain for the initial crawl.

Here’s what I suggest we do to fix it:

Wait for a Day or Two: Sometimes, Google resets its quota after a short period, so it might just need a little time.
Check the Crawl Status: We can use the URL Inspection Tool in Google Search Console to see if Googlebot is able to access the site.
Look for Any Server Errors: I’ll check the Vercel logs to make sure there’s no issue preventing Googlebot from crawling.
Resubmit the Sitemap: I can try removing the current sitemap and submitting it again to see if that triggers the crawl.
Get External Links: Sometimes, sharing the URL on other platforms can encourage Googlebot to crawl the site faster.

Let me know if you’d like me to start with any of these steps, or if you have any other questions.

I got the same issue, something makes me think that search console also have quota on domain level, which in this case would be vercel.app . So i decided to do it the way it should be done and let google crawl the website by providing it with sitemap.xml

Leaderboard Champion

Hey **cicada7778**👋

This isn’t really a Vercel/domain issue — the “Quota Exceeded” error is coming from Google’s side, not .vercel.app. The domain troubleshooting guide is useful, but mainly for DNS/config issues, which doesn’t seem to be the case here. Honestly, best move is to wait a bit and let Google crawl it naturally, and try sharing a few links (Twitter, GitHub, etc.) to trigger discovery. Also worth testing one URL with the inspection tool to confirm Googlebot can access it.

This topic is closed. It no longer accepts new replies.

Here’s what I suggest we do to fix it:

Wait for a Day or Two: Sometimes, Google resets its quota after a short period, so it might just need a little time.
Check the Crawl Status: We can use the URL Inspection Tool in Google Search Console to see if Googlebot is able to access the site.
Look for Any Server Errors: I’ll check the Vercel logs to make sure there’s no issue preventing Googlebot from crawling.
Resubmit the Sitemap: I can try removing the current sitemap and submitting it again to see if that triggers the crawl.
Get External Links: Sometimes, sharing the URL on other platforms can encourage Googlebot to crawl the site faster.

Let me know if you’d like me to start with any of these steps, or if you have any other questions.