How Do You QA a Localized Webflow Site Before Launch?

Check five things for every locale before launch. URLs: each locale has its subdirectory and publishing turned on, and no page, folder or Collection uses the same slug. Content: every static page and CMS item exists, is translated and is published, or is deliberately held back, in that locale. SEO: localized titles, descriptions, slugs and Open Graph, plus hreflang from page tags or the sitemap. Links: internal links use Page or Collection page link types so routing works, and no webflow.io staging URLs remain. Redirects: each locale path gets its own 301 rule.

This guide is for the web or marketing lead launching a second or third language on a Webflow site with Webflow Localize. The problems below came up in our own client work: locale paths that 404, CMS items missing in one language, and staging links left in translated content. Every Webflow behaviour is linked to Webflow's own documentation.

What usually breaks on a localized Webflow site?

Three problems came up in separate client conversations this year:

1. A locale path that returns a 404. Usually a slug clash between a locale subdirectory and a page, folder or Collection, or a secondary locale whose publishing was never turned on.
2. Content missing in one locale. CMS items are separate per locale, so an item deleted, drafted or never translated in one language simply is not there, and a Collection list on that locale shows fewer items than the editor expects.
3. Staging links in translated content. A translator or reviewer copies a link from the webflow.io staging domain into rich text, and it ships to the live site.

None of these show up when you preview only the primary locale. Use the checklist below, with one column of ticks per locale.

How do locale subdirectories and routing work?

Each locale has a subdirectory: its URL slug. Webflow's guide to managing locales says it defaults to the language code (such as /fr) or the locale code when a country is set (such as /fr-ca), and you can change it without changing the site's language code. Two rules from the same article catch teams out:

• Do not reuse a locale's slug. If a Collection, folder or page uses the same slug as a locale subdirectory, the locale wins and the Collection, folder or page returns a 404.
• Publishing is per locale. Each secondary locale has its own publishing status, and publishing a secondary locale requires a Localize add-on. Only locales with publishing enabled appear in the Locale list element.

Routing follows rules you cannot override. Webflow's Localized SEO and locale routing article says locale routing uses 302 redirects with no native way to change that. Automatic domain-level routing, which sends a visitor with a Spanish browser preference to the Spanish homepage, is included on Enterprise and Advanced Localize plans. If a locale has a country set (for example French (Canada)) but the visitor's browser only says French, they are routed to the primary locale instead; Webflow recommends adding a language-only locale alongside country-specific ones.

At page level, the Locale list element and Page or Collection page links route visitors to the same page in their chosen language. If that page does not exist in the locale, the visitor lands on that locale's homepage.

How do you check hreflang and the sitemap?

Webflow generates the signals for you, as long as you leave them on. According to its locale routing article, Webflow sets the HTML lang attribute per locale, adds page-level hreflang tags listing each page's localized versions, and adds hreflang entries to the auto-generated sitemap. You can turn automatic generation on or off, and set a custom base URL, in the Localize panel under SEO. Webflow notes that you only need one signal, page tags or sitemap entries, though using both is fine.

Two exceptions to watch:

• A custom sitemap does not get hreflang automatically. Webflow says you need to add the tags yourself or use another method.
• Locales without publishing enabled do not appear in the auto-generated sitemap.

Whichever method you use, Google's rules for localized versions of a page apply:

Google also says it does not use hreflang or the HTML lang attribute to detect a page's language; it reads the content. A page whose body is still in English will not be treated as French because of its tags.

Paste one page's hreflang tags, or one URL entry from your sitemap, into the checker below.

How do you make sure every CMS item exists in every locale?

Start from how Webflow models it. Webflow's Localize Collection content article explains that a Collection and its fields are shared across all locales, but each locale has its own set of Collection items. An item created in the primary locale exists in all locales; an item created in a secondary locale exists only there. Secondary locales inherit field values until someone edits them.

That leads to five checks:

1. Deletions travel. Deleting an item in the primary locale deletes it from every locale. To hide an item in the primary language only, set it to Draft there instead.
2. Publishing status is per locale. An item can be staged in one locale and a draft in another, so confirm status in each.
3. Exports are per locale. Webflow says a CSV export contains only the items in the current locale view. Export each locale and compare item counts and slugs side by side.
4. Imports can target one locale or all. When you import a translated CSV, choose deliberately; Webflow's CMS import guide explains how matching item IDs link items across locales.
5. Collection lists follow the locale. A list shows the current locale's items, unless its settings use Use primary locale. Check lists on every locale's pages, not just the primary.

If you translate with Webflow's AI, read the mode carefully. Webflow's translation guide warns that switching to continuous translation can replace existing translations, including ones your team wrote, and that translation takes time to process, so a completed publish does not mean every translation has finished.

Which links and URLs need a second look?

Links are where routing quietly fails. Webflow's routing article says automatic page-level routing only works when the link setting is Page or Collection page; a link typed as a direct URL does not route visitors to the locale-specific page. Check these:

• Navigation, footer and buttons use Page or Collection page link types, not typed URLs.
• Rich text links written by translators often contain hard-coded paths such as /en/pricing or full URLs. Search each locale's rich text for your own domain and for locale paths.
• Staging URLs. Search all content, in every locale, for webflow.io. These links work in preview and break the moment a reader or crawler follows them from the live site.
• Links to pages that do not exist in a locale. On Enterprise Localize plans you can set a static page to draft in one locale. Webflow's article on drafting pages per locale says it does not remove links to that page automatically, so update them in that locale.

How do redirects work across locales?

Separately. Webflow's routing article says 301 redirects are relative to the root domain and do not apply to localized slugs or subdirectories. If you want /old-url and /fr/old-url to both reach a new page, you need two rules.

So when a page's slug changes, or a page is removed, write one row per locale in the redirect map. If you translate slugs per locale, which Webflow's page settings guide allows, the old path in each row is the localized slug, not the primary one. The same article notes that AI translation is not available on page slugs, so slugs are always a human decision. Our redirect map guide covers mapping and CSV import in detail; Webflow also notes that draft pages in a locale do not get redirects automatically.

What should a translator or reviewer check?

Machine translation gets the words in; a human reviewer makes them right. Give reviewers this list for each locale:

Webflow's page settings guide notes that custom code can be localized per page, which is useful for locale-specific tracking or consent tools. If you use it, check that each locale runs the code you expect.

What should you monitor after launch?

The first weeks after a locale goes live tell you whether search engines see it the way you intended:

• Sitemap. After each publish, open the sitemap and confirm each locale's URLs and hreflang entries are present.
• Page indexing. In Search Console's Page indexing report, look for 404s and excluded URLs inside each locale folder.
• Performance by page. In the Performance report, use the Pages tab to compare locale folders' clicks and impressions over full, equal periods.
• Content drift. After each primary-locale update, check whether secondary locales need the same change, especially if they no longer inherit the edited fields.

Our technical SEO launch checklist covers the rest of launch day, and our post on what Webflow localization costs covers plans and budgets.

How ActiveSet does it

ActiveSet is a Webflow Premium Partner based in Bengaluru, India. We built and launched HeartFocus on Webflow in May 2024 with English and French localization, CMS and forms, moved the project into the client's own workspace with an editor guide, and have delivered updates since. Localization also features in other builds, including a three-language site we developed for a design studio. Builds are reviewed on staging with Markup.io before launch.

If you are adding a language to a Webflow site, see Webflow localization.

Sources

• Webflow Help Center, Manage your site's locales, updated 22 Jul 2026, checked 14 Oct 2026
• Webflow Help Center, Localized SEO and locale routing, updated 2 Jul 2026, checked 14 Oct 2026
• Webflow Help Center, Localize Collection content, updated 2 Aug 2026, checked 14 Oct 2026
• Webflow Help Center, Localize page settings, updated 2 Jul 2026, checked 14 Oct 2026
• Webflow Help Center, Translate your site content, updated 29 Sep 2026, checked 14 Oct 2026
• Webflow Help Center, Set individual static pages to "draft" status in specific locales, updated 2 Jul 2026, checked 14 Oct 2026
• Webflow Help Center, How do I import content into the Webflow CMS?, updated 18 Aug 2026, checked 14 Oct 2026
• Google Search Central, Tell Google about localized versions of your page, checked 14 Oct 2026
• Google Search Console Help, Page indexing report, checked 14 Oct 2026
• Google Search Console Help, Performance report (Search results), checked 14 Oct 2026