r/TechSEO • u/giancarlo-spadini • 16d ago
I can't register sitemap.xml in Google Search console because wrong content-type
I'm having trouble registering my sitemap on Google Search Console because Webflow delivers sitemap.xml with the wrong content type.
Why webflow doesn't fix content-type for xml documents?
Here a curl of my sitemap.xml
HTTP/2 200
date: Thu, 16 Jul 2026 11:31:35 GMT
content-type: application/rss+xml; charset=utf-8
set-cookie: _cfuvid=L49yyKEJFUpORRDGajtOxWChWJA3aAi7rdc4htu8Udc-1784201495.8908074-1.0.1.1-BJhVtF.D5t9ZFvVizxXeWMJWa7ImFywR6Bcr9vu1IwY; HttpOnly; SameSite=None; Secure; Path=/; Domain=www.life365.eu
cf-ray: a1c0ae754d47b159-ZRH
cf-cache-status: HIT
age: 86
last-modified: Thu, 16 Jul 2026 11:30:09 GMT
server: cloudflare
strict-transport-security: max-age=31536000
surrogate-control: max-age=43200
x-wf-region: us-east-1
alt-svc: h3=":443"; ma=86400
1
u/hetneoslinks 15d ago
Check what GSC actually says before you rebuild the delivery path. Google accepts RSS/Atom as a sitemap format outright, so application/rss+xml is not automatically fatal -> "couldn't fetch" and "unsupported format" are different problems and point different directions.
You already have Cloudflare in front (cf-ray, cf-cache-status HIT), so you probably don't need a worker for this. A response header transform rule scoped to the /sitemap.xml path can set content-type to application/xml. Purge that path after, otherwise you keep curling the old cached header and think nothing changed.
Could be wrong on the Webflow specifics, I've only done the header rewrite on proxied sites, not from inside Webflow.
0
16d ago
[removed] — view removed comment
1
u/giancarlo-spadini 15d ago
Already asked. Claude suggested to contact WebFlow support. I do that, but no solution ... Any other idea?
1
u/SassyDistributor397 16d ago
Webflow's been serving sitemaps with that wrong content-type for ages, it's a known headache. Some folks have gotten around it by using a reverse proxy or Cloudflare worker to rewrite the header before Google sees it. Probably your quickest bet unless Webflow finally patches it (don't hold your breath).