Google Search Console Can't Fetch Sitemap.xml on Vercel

Has anyone experienced issues with Google Search Console showing "Couldn't fetch" for sitemap.xml on websites hosted with Vercel?

I've noticed this across multiple sites hosted on Vercel. When submitting a sitemap to Google Search Console, Google often reports that it cannot fetch the sitemap, even though:

The sitemap.xml URL is publicly accessible
The sitemap returns HTTP 200
robots.txt correctly references the sitemap
There are no redirect loops or authentication restrictions
URL Inspection works normally

What puzzles me is that when I host similar websites on traditional hosting providers, Google usually fetches and processes the sitemap much faster. On Vercel, however, some sites take weeks or even close to a month before the sitemap is successfully fetched.

Has anyone else encountered this issue?

Is there a known Vercel-specific cause?
Are there any recommended configurations or headers to check?
Is there any way to encourage Google to fetch the sitemap more quickly?

For context, most of these sites are built with Next.js and hosted entirely on Vercel.

Any insights would be greatly appreciated. Thanks!

Hi ธนมน,

I’d treat this as a crawler-specific fetch check rather than a general Vercel hosting issue, especially if the same URL returns 200 in a browser.

A few things I’d test from a terminal for one affected site:

curl -I -L https://example.com/sitemap.xml
curl -I -L -A "Googlebot" https://example.com/sitemap.xml
curl -sL https://example.com/sitemap.xml | head

The response should be:

HTTP 200
Content-Type: application/xml or text/xml
No auth/challenge/cookie requirement
No redirect to a different host than the one submitted in Search Console
XML body starts with <urlset> or <sitemapindex>

I’d also make sure the robots.txt sitemap URL matches the exact canonical property you submitted in Search Console. For example, don’t mix these unless redirects are clean and intentional:

https://example.com/sitemap.xml
https://www.example.com/sitemap.xml
http://example.com/sitemap.xml

For Next.js sites, I’d also check whether the sitemap is being generated dynamically and depends on slow CMS/API/database calls. If it does, try making it static or cached, because Google may report “Couldn’t fetch” even when manual browser tests work later.

Google’s sitemap requirements are here:

https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap

If all of those checks pass, this may simply be Search Console lag/state rather than Vercel blocking Google. In that case I’d resubmit the exact sitemap URL, wait a few days, and compare with server logs or Vercel logs to see whether Googlebot is actually requesting /sitemap.xml.