In short. Webflow can keep an individual static page in draft for one selected locale until you stage it for publication.
Definition: A locale-specific draft is a status that keeps an individual Webflow static page out of publication for one selected locale. The other locale versions remain governed by their own page status.
Key facts
- Webflow documents this control for Enterprise Localize customers and applies it to individual static pages in a selected locale in its localized draft page documentation.
- A draft page is excluded from publishing, and a visitor to its URL receives a 404 error.
- Draft pages are omitted from sitemaps and RSS feeds, and Webflow says this prevents indexing.
- The draft status is changed to “stage for publish” in the selected locale before publishing the site makes the page live.
- Webflow's localized SEO and locale routing documentation says that only locale subdirectories with publishing enabled appear in the auto-generated sitemap.
How do you set one static page to draft in a locale?
Select the locale first, open the page, and use its settings. Webflow's documented path is:
Page settings > Save dropdown > Set the page to draft in current locale
The page article describes the sequence as choosing the locale, opening the page's settings, clicking the Save dropdown, and choosing the current-locale draft option. This makes the status specific to the selected locale rather than changing the page's status across every locale.
What happens when the site is published?
The draft locale is excluded from publication. Anyone visiting that locale's page URL gets a 404 error, while the draft page is also absent from sitemaps and RSS feeds. Webflow's documentation says that if a primary page is set to draft, its hreflang tag is removed.
To make the page live, select the locale where the draft lives and change its status from draft to “stage for publish in current locale.” Publishing the site then makes the newly staged page live. The localized SEO documentation says Webflow updates its localized-page signals when the site is published, and that only locale subdirectories with publishing enabled appear in the automatically generated sitemap.
What should you check on links and redirects?
Draft status does not remove links to the localized page automatically. Webflow gives the example of an English “Terms of Service” page that has no Spanish version: a link on the Spanish home page needs to be removed or updated. This matters when a page is drafted in one locale while navigation or footer content still points to its old URL.
Redirects for previously published pages are also manual. Webflow says those redirects are not automatic and that a 301 redirect needs to be set up manually when necessary. Its routing documentation separately says that when a page does not exist in a locale, page-level routing sends the visitor to that locale's subdirectory, with the Spanish homepage given as the example for a missing Spanish page.
Related terms
FAQ
Can one locale be drafted while another stays published?
Yes. The control is applied after you choose a locale, and Webflow describes it as setting an individual static page to draft in the current locale.
Does a draft locale appear in the sitemap?
No. Webflow says draft pages do not appear in sitemaps or RSS feeds. Its localization documentation also limits the auto-generated sitemap to locale subdirectories with publishing enabled.
How do you publish the drafted locale later?
Select the locale where the draft page lives, change the status to “stage for publish in current locale,” and publish the site. Webflow says the newly staged page then becomes live.
Sources
- Webflow, "Set individual static pages to "draft" status in specific locales", July 02, 2026
- Webflow, "Localized SEO and locale routing", July 02, 2026
Check how a page reads to answer engines. Open the GEO score analyzer