Hello Vercel team,
Google Search Console has reported Could not fetch, Unknown type, and zero discovered URLs for https://dabastudio.eu/sitemap.xml since October 5, 2026. Project: daba-studio (Hobby).
On October 11 we verified HTTP 200, application/xml, no redirects, well-formed XML and 57 unique URLs. All 57 pages return 200, their checked canonical URLs match, and no noindex was found. Robots.txt allows access and references the sitemap. Domains show Valid Configuration. Bot Protection is inactive and there are no custom firewall rules. Available firewall aggregates show allowed Google traffic and allowed /sitemap.xml requests, but cannot identify the response to each actual sitemap fetch. We found no evidence of denied Google traffic.
Google live inspection successfully fetches the XML sitemap. A diagnostic identical XML alias https://dabastudio.eu/sitemap-check.xml and plain-text sitemap https://dabastudio.eu/sitemap.txt with the same 57 URLs were submitted today and currently show the same GSC error. The text sitemap passed Google live inspection at 22:00:26 Europe/Amsterdam (20:00:26 UTC), October 11, 2026. These live tests use Google-InspectionTool, which does not establish what the actual sitemap-fetching service receives.
The Hobby dashboard does not expose complete individual static/CDN request records. Empty runtime logs do not establish that Google never requested these files.
Could Vercel investigate actual Google sitemap-fetching requests, distinct from Google-InspectionTool, for /sitemap.xml, /sitemap-check.xml and /sitemap.txt? Please establish whether requests reached Vercel and what they received: timestamps, host, method, HTTP status, cache result, mitigation action/reason and request IDs. Please check denied/challenged requests, transport errors and non-200 responses. If these records cannot be inspected on Hobby, what concrete diagnostic path is available?
The cause remains unconfirmed. We request diagnosis before changing protection settings or billing. Thank you.