In short. A Webflow secondary locale can use a page-specific URL slug edited in that locale's Page settings.

Definition: Yes. A Webflow page in a secondary locale can have its own URL slug. The page inherits settings from the primary locale by default, then the slug can be edited for that locale in Page settings.

Key facts

Webflow says each page includes its localized variants in the <head> so search engines can understand how the pages relate, as described in its localized SEO and locale routing documentation.
Page settings are inherited from the primary locale by default, and Webflow lists the page slug as a setting that can be edited independently on a secondary locale in its page settings documentation.
A locale subdirectory is a URL slug. Webflow sets it to a language code such as /en by default, or to a locale code such as /en-us when a country is set, according to its locale management documentation.
Webflow page URLs support lowercase Latin letters and numbers, so a translated slug is subject to the platform's URL character rules in its Page URLs documentation.

How do locale subdirectories and page slugs work together?

Webflow's locale documentation separates the locale subdirectory from the page slug. The locale subdirectory identifies the locale, while the page slug identifies the page path within that locale. A localized URL can therefore be represented as:

/<locale-subdirectory>/<localized-page-slug>

Webflow's locale documentation gives /en and /en-us as subdirectory examples and says that the subdirectory can be customized without changing the site's language code. Its page settings documentation defines the page slug as the URL path for the page in the selected locale. Together, those settings allow a page to use a locale-specific path alongside a locale-specific subdirectory.

The locale subdirectory must remain distinct from page, folder, and CMS Collection slugs. Webflow states that a conflict gives precedence to the locale subdirectory. A published locale also needs publishing enabled before its subdirectory appears in the automatically generated sitemap.

How do you edit the slug for one locale?

Webflow's page settings documentation documents this workflow for a secondary locale:

Open the Locale view dropdown in the top bar.
Choose the locale to edit.
Open the Pages panel.
Hover over the page and click Edit page settings.
Change the slug and save the page.

Webflow says that these edits apply to the selected locale. The same page settings article states that automated translation is available for the page name, SEO title, SEO description, and Open Graph fields, while automated translation is unavailable for the page slug. The slug must therefore be edited in the selected locale's page settings.

What should be checked before publishing?

First, check the locale's subdirectory and publishing status in Localize panel > Locales. Webflow's locale management documentation says that only locales with publishing enabled appear in the Locale list element, and its localized SEO documentation says that only published locale subdirectories appear in the automatically generated sitemap.

Next, check links that lead to the localized page. Webflow's localized SEO and locale routing documentation says that page-level routing applies to links whose Link setting is Page or Collection page. A direct URL in link settings does not route visitors to the locale-specific page. If the page does not exist in a selected locale, Webflow routes the visitor to that locale's subdirectory, which the documentation describes as the locale homepage.

Finally, check the saved path against Webflow's Page URLs rules. Static page URLs support lowercase Latin alphabet characters from a to z and numbers from 0 to 9. Non-Latin input is converted to Latin characters, special non-letter and non-number characters are removed, and uppercase characters are converted to lowercase characters.

FAQ

Can you translate a Webflow page slug automatically?

Webflow's page settings documentation says automated translation is unavailable for the page slug. The slug can still be edited in the selected locale's Page settings.

Does a localized slug replace the locale subdirectory?

No. The locale subdirectory identifies the locale, and the page slug identifies the page path in that locale. Webflow's locale documentation and page settings documentation describe both settings separately.

What happens when the localized page is missing?

Webflow's localized SEO and locale routing documentation says that the visitor is routed to the locale subdirectory when the page does not exist in that locale. Page-level routing applies to Page and Collection page links.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer

Can a Webflow localized page use a translated URL slug?