Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Multilingual CMS: what to look for to keep SEO easy

Updated · 6 min read

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 call

Multilingual 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.

#FeatureWhy it mattersWhat Google says
1Each language at its own URL, ideally a subfolder (/es/)Google can only rank a version it can reach by its own addressDifferent URLs per language; URL parameters such as ?loc=de are "Not recommended"
2Translated title, description and slug on every pageSearchers type in their language; the result they see should be in it too"It's fine to use localized words in the URL"
3hreflang tags added for youThey tell Google /es/servicios is the Spanish /servicesEach version must list itself and every other version, and both must point at each other
4Sitemap that lists every languageHelps Google find all versionsA sitemap is one of three accepted ways to list versions
5A visible language switch, no forced redirectRedirects can hide versions from people and Google"Avoid automatically redirecting users" between languages
6Menus, buttons, forms and emails translated tooGoogle reads the visible page to set its languageUse one language for content and navigation on each page
7Machine translation you can edit before publishingRaw bulk translation can count as spamScaled content abuse includes translating to make many low-value pages
8Old URLs redirect when you change a slug or structureChanging 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:

PlatformHow you add languagesURL setuphreflangTranslated slugsPrice for languages
WordPress + WPMLPluginFolders, domains or parameterAutomatic, on all plansYes€39 Blog plan (no menu translation); €99 CMS plan; a year of updates
WordPress + PolylangPluginFolders, subdomains or domainsAutomatic; x-default on the homepage onlyEach translation is its own pageFree; Pro from €99 a year
WixBuilt-in Wix MultilingualSubfolder by defaultAutomatic, with x-defaultYes, per pageNot stated on its help pages
WebflowLocalize add-onSubfolderAutomatic, in pages and sitemapLocalize URLs on AdvancedFrom $9 a month (Essential, up to 3 languages); Advanced from $29, up to 10
SquarespaceWeglot extension (version 7.1 only)SubdomainsAdded by WeglotWeglot Pro plan and upWeglot free to 2,000 words and 1 language; Starter $17 a month for 10,000 words
ShopifyBuilt-in languages, Translate & Adapt appSubfolder, subdomain or domainAutomaticNot statedNot 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

  1. Can I see a live site on this platform in two languages? View its page source for hreflang lines.
  2. Does each language get its own sitemap entries?
  3. Can I edit the machine translation before it goes live?
  4. Does it redirect visitors by browser language, and can I turn that off?
  5. Are forms, confirmation emails and booking pages translated, or only the pages?
  6. What does it cost per language and per word, every year?
  7. 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?

Keep learning

NextHreflang and duplicate content: stop language versions competingWhen Google treats your translated or US and Canadian pages as duplicates, how hreflang and canonical tags work together, and how to check.

Do it yourself

International SEO checklist: set up your site for other countriesEight steps to get found in another country: keywords per market, URL setup, hreflang codes, local signals, local links and tracking by country.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Managing multi-regional and multilingual sites
  2. Google Search Central: Tell Google about localized versions of your page
  3. Google Search Central: Spam policies for Google web search
  4. Wix Help Center: Optimizing SEO settings for multilingual sites
  5. Wix Help Center: Editing your multilingual site's URL structure
  6. WPML: Language URL format options
  7. WPML: How to add hreflang in a WordPress website
  8. WPML: Customize URLs, slugs, and SEO
  9. WPML: Pricing
  10. WordPress.org: Polylang plugin
  11. Polylang: Pricing
  12. Polylang blog: Hreflang tag attributes and Polylang (2023)
  13. Webflow: Localization
  14. Webflow: Plans and pricing
  15. Webflow Updates: Improved sitemap support for localized sites (2025)
  16. Weglot: Squarespace multilingual site guide
  17. Weglot: Pricing
  18. Shopify Help Center: International SEO for markets
  19. Shopify Help Center: Localization and translation