Chapter 6: Localization (2.B)
Exam topic 2.B: Understand how localization affects content structure and routing.
Exam topic 2.B: Understand how localization affects content structure and routing.
Key terms: Locale settings, subdirectory routing, localized SEO settings, locale switcher.
Weight: 2% of the exam (about 1 question). The guide says localization is assessed at a conceptual level: when multi-language support is needed and how it affects site structure and routing.
This is the smallest topic on the exam, so this chapter focuses on the concepts and decisions rather than every setting.
6.1 Translation vs. localization
- Translation converts words into another language.
- Localization adapts the whole experience for a locale: language, but also currency, date/number formats, imagery, legal text, phone numbers, and even which pages or products exist.
A locale is a language, optionally combined with a region: fr (French), fr-CA (French as used in Canada), en-GB, es-MX. The region matters when spelling, pricing or regulations differ.
When does a site need localization?
- The audience spans languages or regions with different expectations.
- The business wants to rank in search engines for other languages or countries.
- Legal requirements: some regions require content in a local language.
A browser translation plugin or a client-side translation widget isn’t localization. Search engines don’t index those translations, and you get no control over quality or local content.
6.2 How Webflow Localization is structured
- Primary locale: the site’s default language, served at the root (
example.com/about). - Secondary locales: additional locales, each served in a subdirectory:
example.com/fr/about,example.com/es-mx/about. - The same page structure is shared across locales. You localize content (text, images, links, alt text, SEO fields) per locale rather than building separate pages. Locale-specific overrides, such as a different image or a hidden element, are possible where needed.
- CMS content can be localized per item and per field, so a Blog Post has a French version of its title, body and SEO fields.
- Localized URLs (slugs) can be translated, e.g.
/fr/a-proposinstead of/fr/about, depending on plan. - Machine translation can produce first drafts, which humans should review.
Why subdirectories?
| Structure | Example | Notes |
|---|---|---|
| Subdirectory | example.com/fr/ |
Shares the main domain’s authority; one site to manage. Webflow’s native model |
| Subdomain | fr.example.com |
Often treated more like a separate site |
| Country domain (ccTLD) | example.fr |
Strong country signal, but separate domains and authority to build |
| Separate Webflow sites | — | Duplicated design and content; maintenance grows with every locale |
For the exam: localization in Webflow means one site, multiple locales, subdirectory routing. Duplicating the site per language is the anti-pattern.
6.3 Localized SEO
Each locale needs its own discoverable, correctly labelled pages:
- Localized meta titles, descriptions and Open Graph settings per page and per CMS item. A French page with English metadata is a poor result.
hreflangannotations tell search engines which URL serves which locale (and which is the default), so French searchers get the/fr/page. Webflow Localization generates these for localized pages, along with the rightlangattribute on the<html>element.- Sitemap entries include localized URLs.
- Localized slugs can help relevance and click-through (“tarifs” vs “pricing”).
- Don’t auto-redirect by IP or browser language to the point where users and crawlers can’t reach other locales. Suggest a locale, and let people choose.
The lang attribute also matters for accessibility: screen readers use it to choose the correct pronunciation.
6.4 The locale switcher
A locale switcher (a list of locales the site renders automatically) lets visitors switch to the same page in another locale.
Best practices:
- Label locales in their own language (“Français”, “Español”), not in the current page’s language.
- Don’t use flags alone. Flags represent countries, not languages (Spanish is spoken in many countries; Switzerland has four national languages).
- Link to the equivalent page in the other locale, not to its homepage.
- Make it keyboard accessible and visible in the header or footer.
6.5 Design considerations
- Text expansion: German and French text often runs 20–35% longer than English. Layouts with fixed widths or heights break. Flex/grid layouts with flexible widths survive (Chapter 1).
- Right-to-left languages (Arabic, Hebrew) need mirrored layouts and
dir="rtl". Plan for this before you build. - Images with embedded text can’t be translated. Use real text over images.
- Fonts must support the character sets you need (e.g. Vietnamese diacritics, Cyrillic, CJK).
- Formats: dates (
03/04/2026is ambiguous), currencies, units.
6.6 Localization and the rest of the site
| Area | Impact |
|---|---|
| CMS | Fields are localized per item; plan which fields need translating (body, SEO) vs. shared (dates, numbers, switch fields) |
| Forms | Labels, placeholders, success/error messages per locale; route submissions appropriately |
| Components | Component text and properties need localized values |
| Redirects | Old language-specific URLs (from a previous setup) need 301s to new locale paths |
| Custom code | Scripts that output text must handle locale (read document.documentElement.lang) |
| Analytics | Segment by locale path (/fr/) to measure each market |
Practice questions: Localization
Q1 A company wants its site to rank in Google France and Germany with properly translated content. Which approach is most appropriate in Webflow?
Show answer
Answer: b. Native localization gives real, indexable, translated pages in subdirectories with localized SEO. (a) client-side widgets aren’t indexed reliably and offer no quality control. (c) duplication multiplies maintenance and splits authority. (d) mixed-language pages confuse users and search engines.
Q2 With subdirectory routing and English as the primary locale, what is the typical URL of the French version of /pricing?
Show answer
Answer: b. Secondary locales live in subdirectories, optionally with localized slugs. (a) subdomains aren’t Webflow’s native localization routing. (c) query parameters are weak locale signals. (d) separate country domains aren’t created automatically.
Q3 (Multi-select) Which are part of localized SEO? (Choose three.)
Show answer
Answer: a, b and c. Localized metadata, hreflang and correct lang attributes are the core of international SEO. (d) English metadata on French pages hurts relevance and click-through.
Q4 What’s the main problem with using only flags in a locale switcher?
Show answer
Answer: b. A flag shows a country, not a language. Use language names written in their own language. Flags can be a secondary visual at most.
Q5 After adding German, several buttons and nav items overflow their containers. What’s the most likely cause and fix?
Show answer
Answer: a. Text expansion is normal in localization. Flexible layouts (flex/grid with auto sizing, wrapping) handle it. (b), (c) and (d) are false.
Q6 (Multi-select) Which CMS fields usually need localized values for a blog post? (Choose two.)
Show answer
Answer: a and b. Readable content and SEO metadata are language-dependent. (c) and (d) are usually shared across locales.
Q7 Why does the lang attribute matter beyond SEO?
Show answer
Answer: b. Assistive technology uses lang for pronunciation, and it’s a WCAG requirement (3.1.1 Language of Page). (a), (c) and (d) are false.
Q8 A visitor in Spain lands on the English homepage. Which behaviour is most user- and SEO-friendly?
Show answer
Answer: b. Suggesting without forcing respects user choice and keeps every locale crawlable. (a) forced IP redirects trap users (travellers, expats) and can stop crawlers from seeing other locales. (c) and (d) are poor for users and SEO.
Q9 When is region-specific localization (e.g. es-MX vs es-ES) justified rather than a single es locale?
Show answer
Answer: b. Regional locales are worth it when content actually differs by region. Otherwise a single language locale is simpler. (a), (c) and (d) are wrong.
Q10 A legacy site used example.com/french/about. After moving to Webflow Localization (/fr/about), what should you add?
Show answer
Answer: a. Changed URLs always need 301 redirects to preserve links and search equity. (b) search engines need redirects to transfer signals. (c) would remove French pages from search. (d) is irrelevant.
Q11 A hero image contains English marketing text baked into the graphic. What’s the localization issue and the better approach?
Show answer
Answer: b. Text baked into an image is fixed in one language and isn’t accessible as text. Real text (or localized variants with localized alt text) solves both problems.