Dynamic collection adding "/en" in the URL automatically

Hi there,

I am having an issue with my dynamic links, I did not add any language tags, but when I publish the site, it has “/en” after the domain link and before my collection and ends up with " Page Not Found."

Can anyone tell me why this is happening? I will be really happy if someone can help me with this.
I am not sure if it’s Webflow bugs I never experienced this before.

Main project page,

When you click any of this projects, it should land below url

Instead it’s landing on this, adding an extra “/en”


1 Like

It’s a new bug connected to the migration to localization, I’m floored that such a major bug isn’t fixed after more than a week. This has the potential to do some serious SEO damage as well.

As a temporary fix, use this code, in the before-/body custom code area.
I’d probably put it site-wide so that it’s easy to add now, and then remove later once localization is fixed.

Note that when localization is fixed, your site will work fine even with this fix-code. However if you actually use localization it will be important to remove this so that your language-specific path redirects work as intended.

<!-- TEMPORARY /en/ bug fix 
     Remove once Webflow fixes localization. 
// Find all /en/... links within collection list items
const links = document.querySelectorAll('.w-dyn-item a[href^="/en/"]');
links.forEach(link => {
    // Remove the /en prefix
    link.href = link.href.replace('/en', '');

Question, are you using automated sitemap generation?
I wanted to check if this has broken the sitemap as well but I’m not seeing CMS pages listed at all.
That’s better than broken /en/ links though. :thinking:


My approach here is probably the best to safeguard your SEO, so Google doesn’t try indexing invalid URLs and de-list all of your CMS pages. However you could back it up with a wildcard redirect like this just in case anything slips through;



Hey Michael, the script worked! Thanks!! However, I’m still having trouble getting the sitemap to work, even with the 301 redirect. Sitemap here: https://www.coffeeclozers.com/sitemap.xml

I’m worried about our SEO suffering. Do you think I should just create my own sitemap until the bug is fixed?

Also, I was referencing the localization documentation here and now I’m not sure if this is a feature or a bug?? I couldn’t figure out how to create different locales for our CMS.

Weird, so, yes, Webflow’s generated sitemap is indicating that all of your pages are under /en including your homepage. Search engines will just get 404’s on those pages.

Temporarily using a static sitemap is one quick way to fix it. Copy, edit, paste.
You MIGHT be able to hack that with this redirect as well, in this case I’d try-


^ In some cases this wildcard formation will capture the entire path e.g. /blog/something rather than /en/(.*) which just captures a single path-segment between the /'s.

You might need an additional /en/ for the homepage.

Have you contacted support? I understand that for some users facing this bug support can add you to the localization beta, and that appears to resolve it.

1 Like

Thanks for the response! Still not working so I’m going to contact support and maybe do the static sitemap in the meantime. Thank you :blush: