Sitemap.xml won't use Global Canonical Tag URL

[oodavid (David King)]

The Global Canonical Tag URL is set to https://www.flowmobile.app.

For proxying reasons we publish our site to two domains:

• https://blog.flowmobile.app
• https://www.flowmobile.app

The Global Canonical Tag URL correctly adds the <link rel="canonical"> element to the head on both domains, like so:

<link href="https://www.flowmobile.app/" rel="canonical"/>

However the sitemap.xml both use blog.flowmobile.app as the hostname:

• https://blog.flowmobile.app/sitemap.xml
• https://www.flowmobile.app

I expect the Global Canonical Tag URL to affect the sitemap.xml URLs as well as add the <link> element. Is there another setting for this?

[memetican (Michael Wells)]

Hey @oodavid , that sounds like a bug I posted in 2017, here-

Sitemap.xml is not domain-specific (so Google errors on it)

I’ve just published a new website which is bound to two domain names SYGNAL.COM and SYGNAL.TECH. I have Sitemap auto-gen turned on, and I’m currently registering the site through Google Search Console (aka Google Webmaster) and adding the sitemaps. Google is giving me an error on the Sitemap because the in-sitemap hostnames don’t match the requesting hostname. If you look at the Sitemap on SYGNAL.COM… http://sygnal.com/sitemap.xml You can see that it references SYGNAL.TECH rather than SYGNA…

@nealwhite was kind enough to properly post it as a bug report;

Sitemaps Invalid w/ Multiple Custom Domains

First - Webflow is incredible. Amazing work and kudos to the entire team. So I’ve come across two problems with how Webflow generates sitemaps when there are multiple custom domains (without setting the primary domain): First, we publish sites to a staging.* URL for client reviews/approvals, then to www for production. However, custom domains appear to be sorted alphabetically, and the one highest in the list appears to be used in the sitemap.xml file. So our sitemap.xml on www.* is full of st…

So far no solution. Probably a good one for you to re-raise.

Incidentally, I haven’t found any workable hacks, either. If I have e.g. 10 domains on a site, and they all have to be separate, it appears somewhat random which domain appears in the sitemap.xml. However they all get the same one, regardless.

I’ve tried publishing all domains, and then just publishing ONE domain by itself, in the hopes that this would override all 10 sitemap.xml to contain the domain I want. No dice.

Your only option may be to copy your sitemap.xml, search-and-replace your domains, and then paste it into your site config explicitly.

[oodavid (David King)]

Thanks memetician, I’ll see if I can raise that ticket

[Sean_Van_Guilder]

I have a site that is having this issue. How can I get this fixed?

[memetican (Michael Wells)]

There is no way to fix it natively within a single Webflow-hosted site. Even if you switch to manually-generating the sitemap, it will deliver the same sitemap for all of the hostnames you have mapped to it.

The best way to think of it is that, effectively, Webflow only works 100% correctly if you set a default domain.

If there’s some reason you can’t do that, your options are;

• Reverse proxy, to change that sitemap.xml by hostname
• Export and host the site elsewhere where you can have domain-specific sitemaps
• Duplicate the site, and host two copies, on the separate domains