Multilingual CMS: what to look for to keep SEO easy
Short answer Pick a platform that gives each language its own URL in a subfolder like /es/, lets you write a translated title, description and slug for every page, and adds hreflang tags and sitemap entries for you. It should never force visitors into a language. WordPress with WPML or Polylang, Wix and Webflow do this; Squarespace needs Weglot.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callMultilingual CMS checklist: the 8 features that matter
A CMS (content management system) is the tool you edit your site in: WordPress, Wix, Squarespace, Webflow, Shopify. For a second language, it has to produce what Google asks for without you touching code. Check these eight before you pick one or pay for an add-on.
| # | Feature | Why it matters | What Google says |
|---|---|---|---|
| 1 | Each language at its own URL, ideally a subfolder (/es/) | Google can only rank a version it can reach by its own address | Different URLs per language; URL parameters such as ?loc=de are "Not recommended" |
| 2 | Translated title, description and slug on every page | Searchers type in their language; the result they see should be in it too | "It's fine to use localized words in the URL" |
| 3 | hreflang tags added for you | They tell Google /es/servicios is the Spanish /services | Each version must list itself and every other version, and both must point at each other |
| 4 | Sitemap that lists every language | Helps Google find all versions | A sitemap is one of three accepted ways to list versions |
| 5 | A visible language switch, no forced redirect | Redirects can hide versions from people and Google | "Avoid automatically redirecting users" between languages |
| 6 | Menus, buttons, forms and emails translated too | Google reads the visible page to set its language | Use one language for content and navigation on each page |
| 7 | Machine translation you can edit before publishing | Raw bulk translation can count as spam | Scaled content abuse includes translating to make many low-value pages |
| 8 | Old URLs redirect when you change a slug or structure | Changing addresses later can cost rankings | (See the website migration checklist) |
Sources: Google Search Central's pages on multilingual sites, localized versions and spam policies.
The SEO rules themselves (hreflang, x-default, how much to translate) are in our multilingual website SEO guide. This page is about the tool.
Does the CMS need to handle hreflang automatically?
Yes, if you're not a developer. hreflang is a line of code in each page's header naming its other-language twins. By hand, every new page means editing every version, and one missed link breaks the pair:
"If two pages don't both point to each other, the tags will be ignored." (Google Search Central: Tell Google about localized versions of your page)
Every platform below adds the tags itself once languages are set up. Check it after launch: open a translated page, view the page source, and search for "hreflang". You should see one line per language, including the page's own.
Subfolder, subdomain or ?lang=: which URL setup to choose
Pick the subfolder (example.com/es/) unless you have a reason not to. Google lists subfolders as easy to set up and low maintenance because everything stays on one host. Subdomains (es.example.com) also work. Language parameters (example.com/?lang=es) are the one Google calls not recommended.
Watch the default. Wix makes subfolders the default and advises sites on ?lang= parameters to change; when you switch, Wix redirects the old URLs automatically (Wix Help Center). WPML lets you choose directories, a domain per language, or a parameter (WPML documentation). Weglot on Squarespace puts languages on subdomains (Weglot's Squarespace guide).
How the common platforms compare
As of November 2026, from each platform's own pages:
| Platform | How you add languages | URL setup | hreflang | Translated slugs | Price for languages |
|---|---|---|---|---|---|
| WordPress + WPML | Plugin | Folders, domains or parameter | Automatic, on all plans | Yes | €39 Blog plan (no menu translation); €99 CMS plan; a year of updates |
| WordPress + Polylang | Plugin | Folders, subdomains or domains | Automatic; x-default on the homepage only | Each translation is its own page | Free; Pro from €99 a year |
| Wix | Built-in Wix Multilingual | Subfolder by default | Automatic, with x-default | Yes, per page | Not stated on its help pages |
| Webflow | Localize add-on | Subfolder | Automatic, in pages and sitemap | Localize URLs on Advanced | From $9 a month (Essential, up to 3 languages); Advanced from $29, up to 10 |
| Squarespace | Weglot extension (version 7.1 only) | Subdomains | Added by Weglot | Weglot Pro plan and up | Weglot free to 2,000 words and 1 language; Starter $17 a month for 10,000 words |
| Shopify | Built-in languages, Translate & Adapt app | Subfolder, subdomain or domain | Automatic | Not stated | Not stated |
Sources: WPML pricing and documentation; Polylang on WordPress.org, its pricing page and blog; Wix Help Center; Webflow's pricing and Localization pages; Weglot's pricing and Squarespace guide; Shopify Help Center.
What the table means for a service business:
- WordPress: most control, most upkeep. Polylang's free version covers a small site; WPML's cheapest plan doesn't translate menus, so a Spanish page would keep an English menu.
- Wix: the simplest. Its help center has you add a localized title, description and slug on every page, and it adds hreflang and x-default tags itself.
- Webflow: cheap to start, but translated URLs need the Advanced tier. Webflow's sitemap has listed every language as its own entry since September 11, 2025.
- Squarespace: Without an extension, Weglot's guide says, you build each translated page by hand and get no language subdomains. Weglot counts words across all languages, so a 5,000-word site in one extra language needs a paid plan.
- Shopify: a fit for stores more than service businesses. Shopify says hreflang "tags are generated automatically based on your market and language configuration."
What to ask before you sign up
- Can I see a live site on this platform in two languages? View its page source for hreflang lines.
- Does each language get its own sitemap entries?
- Can I edit the machine translation before it goes live?
- Does it redirect visitors by browser language, and can I turn that off?
- Are forms, confirmation emails and booking pages translated, or only the pages?
- What does it cost per language and per word, every year?
- If you need Arabic or Hebrew: does the theme support right-to-left text? Polylang, for one, says right-to-left scripts are supported.
Example
A cleaning company on Wix adding Spanish
It turns on Wix Multilingual, keeps the default /es/ folders, and writes Spanish titles, descriptions and slugs for its 8 service pages. The work is writing the Spanish copy; Wix adds hreflang itself.
A law firm on WordPress choosing a plugin
It has 40 pages and a booking form. WPML's €99 CMS plan translates menus and text from themes and plugins; the €39 plan would leave those in English. The price includes a year of updates.
A salon on Squarespace
Its site has about 6,000 words. Weglot's free plan stops at 2,000 words, so French would need a paid plan at $17 a month or more, on subdomains rather than folders.
FAQ
Is it OK to use a translation widget like Google Translate?
Not for search. A widget that translates inside the visitor's browser gives the translation no URL of its own. Google recommends "using different URLs for each language version of a page rather than using cookies or browser settings".
Should I switch platforms just to add a language?
Usually not. WordPress, Wix and Webflow all handle it; Squarespace needs Weglot. Moving platforms changes every URL, which carries its own risk.
Can I auto-translate the whole site with AI?
As a draft, yes. Have a fluent speaker read the pages customers use to hire you. Google's spam policy targets translated pages that add little value.
Does my CMS need separate sitemaps per language?
No. One sitemap listing every version works. Google accepts hreflang in the page, in HTTP headers or in the sitemap; one method is enough.
Different for you?
- You're setting up hreflang and deciding what to translate: Multilingual website SEO.
- You're still choosing a platform: Is Wix or Squarespace bad for SEO?
- Adding languages means new URLs on a live site: Website migration checklist.
- You want to check your sitemap lists every language: What is a sitemap?
- You want the site built in two languages: Website agent.