OnlineDocTranslatorGuides

Running your practice

CMS Localization: How Translators and Agencies Produce Multilingual Content Across Platforms

CMS localization is the production workflow translators and agencies use to adapt content, components, and routing across WordPress, Drupal, AEM, Contentful

CMS localization sits inside a broader service localization program as the platform-bound sub-lane that translators and agencies execute against a client's content management system. It is the production counterpart to How App Localization Works and What Clients Are Buying and Website Localization: What Translators and Agencies Actually Do on the Project, and it is scoped per field, per item, per locale — not per page.

What is CMS localization from the translator's and agency's side?

CMS localization is the CMS-specific adaptation of a website's content, components, SEO metadata, and locale routing for added markets, delivered by translators through native CMS locale editors, TMS connectors, or scripted API pipelines, and quoted per field, item, and locale. The CMS is the surface where translated content gets stored, versioned per locale, and published back to live URLs.

A translator's job on a CMS program covers five production acts:

  • Receiving a CMS export or connector job and confirming field scope.
  • Mapping source fields to target-locale fields and enforcing TM plus term base.
  • Routing low-risk segments through MT with post-edit, and keeping marketing copy human-first.
  • Preserving rich-text structure, variables, and asset slots per locale.
  • Handing back localized items with hreflang pairs intact to all alternates.

How does CMS localization sit next to website localization and content localization?

CMS localization is the platform-bound sub-lane of website localization — the CMS is the surface where translated content gets stored, versioned per locale, and published, while content localization covers the linguistic adaptation itself. The three lanes stack as follows:

LaneScopePrimary artifact
Website localizationPages, components, metadata, routingi18n-ready source files, hreflang map
CMS localizationFields, items, locales inside the CMSXLIFF export, connector job, locale editor
Content localizationLinguistic adaptation of each segmentTM, term base, style guide, QA report

For the artifact-level playbook, see Content Localization: How Translators and Agencies Produce It.

What does a translator receive when a CMS localization job starts?

Translators receive one of three handoff shapes: a CMS export file (XLIFF, JSON, CSV), a TMS connector job pre-mapped to source segments, or direct editor access to the CMS under a secondary locale. Each handoff ships with TM, term base, style guide, and a staging URL for in-context review.

  1. CMS export file — XLIFF 1.2 or 2.0 from WordPress/WPML, Drupal TMGMT, or AEM; JSON from headless platforms; CSV for small catalog jobs.
  2. TMS connector job — Content flows from Contentful, WordPress, or AEM into Lokalise, Phrase, Smartling, or Crowdin, where translators work against pre-segmented strings.
  3. Direct CMS editor access — Translators log into the CMS under a target locale and type into native per-locale fields.

Which CMS fields are usually in scope — and which get silently excluded?

In-scope fields typically cover body copy, SEO title, SEO description, slug, alt text, and any rich-text blocks marked localizable in the schema. Commonly excluded are internal admin labels, system taxonomies, image binaries without per-locale slots, and third-party widget strings that live outside the CMS.

Field typeUsually in scopeOften excluded by default
Body / rich textYes—
SEO title and meta descriptionYesSilently skipped by some connectors
URL slugYesLeft as source when auto-generated
Image alt textYesMissed when stored on the media library, not the item
Taxonomies and tagsSometimesSystem-level taxonomies default off
Third-party widget stringsNoLive outside the CMS schema
Admin labelsNoNot customer-facing

Pricing

How is CMS localization work quoted and priced?

CMS localization is quoted on field count × item count × target locales, not page count. A 300-item knowledge base with 8 localizable fields across 3 locales equals 7,200 field edits — the quoting unit that determines translator hours and connector throughput.

Line itemUS rateUnit
Translation$0.10–$0.25per source word
Review$0.04–$0.08per source word
LQA (sampled)$40–$90per 1,000 words translated
MT post-edit$0.05–$0.12per source word

What does a mid-size multilingual CMS program cost end-to-end?

A mid-size program covering 5 languages and 50,000 words budgets at $25,000–$75,000 end to end, with TM leverage, turnaround speed, and certification requirements shifting the mix between translation, review, and LQA line items. The range widens when the client needs continuous publishing, connector maintenance, or dedicated reviewers per locale.

Get a quote

How does CMS localization work across the major CMS platforms?

CMS localization splits by platform into three handoff patterns: native locale editors (Webflow, Shopify, Craft), plugin-driven multilingual trees (WordPress with WPML or Polylang, Drupal), and connector-driven headless pipelines (Contentful, AEM, dotCMS) that stream content into a TMS over API.

CMSLocalization surfaceTranslator handoff
WordPressWPML, Polylang, TranslatePressXLIFF export or TMS connector
DrupalCore multilingual + TMGMTNode UI or XLIFF via TMGMT
Adobe Experience ManagerLanguage copies + MSMXLIFF to connected TMS
ContentfulLocale-keyed JSON per fieldGraphQL/REST or TMS connector
Craft CMSSites + locales modelIn-CMS editor or export
dotCMS / Strapi / SanityHeadless locale fieldsAPI payload or TMS connector
ShopifyTranslate & Adapt, MarketsNative editor or Translation API
WebflowNative secondary-locale editingField-by-field in CMS Collections

How does WordPress multilingual localization work for translators?

WordPress localization runs through WPML, Polylang, or TranslatePress plugins that duplicate posts per locale and expose XLIFF export for translators. Agencies connect WPML's translation management module to a TMS or receive XLIFF bundles the translator imports into memoQ, Trados, or Phrase. Custom fields and page-builder blocks need explicit "translatable" flags, or they ship untranslated.

How does Drupal multilingual localization work for translators?

Drupal ships multilingual as a core module set — Language, Content Translation, Configuration Translation, Interface Translation — that marks fields translatable per content type. Translators work either in Drupal's node translation UI per locale or through TMGMT connectors that export segments to a TMS. Configuration strings (menus, blocks, views) run through Configuration Translation and are easy to forget during scoping.

How does Adobe Experience Manager handle CMS localization?

Adobe Experience Manager runs localization through its language-copy and MSM (Multi Site Manager) framework, with translation projects pushing XLIFF or AEM-native payloads out to connected TMS platforms (Lokalise, Phrase, Smartling). Translators work against the exports and reviewers validate in AEM's preview environment. Live Copy inheritance from the master branch is the knob that controls what the translator sees per locale.

How does Contentful and headless CMS localization work?

Headless CMS localization — Contentful, Strapi, Sanity, dotCMS — stores each field as locale-keyed JSON exposed over GraphQL or REST, so translators receive either CMS exports or TMS connector jobs rather than editing in a visual designer. The client's front-end queries the correct locale at render time. React and Next.js front-ends consume this data directly; see React i18n: How Translators Fit Into a React Localization Pipeline and JS Localization: How Translators Fit Into a JavaScript i18n Pipeline.

Where do Shopify and Webflow fit as CMS-specific sub-lanes?

Shopify and Webflow are CMS-specific sub-lanes with their own native locale editors and distinct quoting rules. Shopify runs through Markets, Translate & Adapt, and the Translation API. Webflow runs through native secondary-locale editing per CMS item, field by field. Both are scoped as separate production lanes inside a broader program — the deep dives live in How Shopify Localization Works and What It Means for Your Agency and How Webflow Localization Works and What Translators Need to Know.

When should an agency move from a native CMS editor to a TMS platform?

Agencies escalate from native CMS locale editors to a TMS (Lokalise, Phrase, Smartling, Crowdin) when four triggers hit:

  1. Secondary locale count exceeds roughly five.
  2. CMS item count passes a few hundred per collection.
  3. The client requires TM leverage and fuzzy-match reporting.
  4. Continuous-publishing SLAs demand automated string sync.

Below those thresholds, the native editor is faster to staff and cheaper to run. Above them, field-by-field editing stops scaling — the pattern is covered in depth on the Webflow guide. For the program-level view of connector choice and vendor orchestration, see Localization Management: How Translators and Agencies Run Multi-Locale Programs.

How does machine translation fit into a CMS localization pipeline?

Machine translation enters CMS localization as a pre-translate stage routed through the TMS or CMS connector, with post-editing by a human translator and LQA sampling before publish. The split by content class:

  • MT with post-edit — product catalog entries, support knowledge base, legal boilerplate, release notes.
  • Human-first with TM leverage — marketing surfaces, landing pages, email templates, campaign copy.
  • Transcreation — taglines, hero copy, brand-voice statements.

Translation memory leverage reporting — fuzzy match percentages, repetition analysis, 101% context matches — sits in the TMS, not the native CMS. That is one of the four escalation triggers above.

What locale, hreflang, and ISO code rules apply inside the CMS?

Each localized URL must emit hreflang pairs back to all alternates including itself, using ISO 639-1 language codes plus optional ISO 3166-1 country codes written as es-MX, pt-BR, fr-CA. The CMS is where this discipline either holds or breaks at release — most connectors silently skip the self-referential pair and the x-default declaration.

  • Language-only pair: es, fr, de.
  • Language + region pair: es-MX, pt-BR, fr-CA, en-GB.
  • Default fallback: x-default pointing at the source locale.
  • Reciprocity: every alternate URL lists every other alternate, plus itself.

How is quality assured on CMS localization output?

Quality runs through two gates: review and LQA, aligned to ISO 17100. Review covers every segment at $0.04–$0.08 per source word. LQA samples output at $40–$90 per 1,000 words translated against an MQM-style scorecard.

MQM dimensionWhat the reviewer checks
AccuracyMistranslation, omission, addition
FluencyGrammar, spelling, punctuation per locale
TerminologyTerm base adherence
Locale conventionDates, numbers, currency, measurement
StyleRegister, voice, style-guide fit

The three defects native CMS editors create — untranslated SEO metadata, broken rich-text structure per locale, and asset slots left in the source locale — are the first items on the scorecard for CMS lanes.

What breaks at scale in CMS localization and how do translators flag it?

Three failure modes scale badly in CMS production. Translators flag them during scoping, not after publish.

  • Linear translator hours past a few hundred items — field-by-field editing stops being viable; escalate to TMS connector.
  • Right-to-left and CJK layouts — Arabic, Hebrew, Japanese, Chinese, and Korean need per-locale component variants and font declarations.
  • Continuous content changes — new publishes re-trigger translation on segments the client thought were frozen.

Secondary limits include no bulk asset swap in most native editors, rich-text restructure limits when source blocks shift, manual RTL CSS, and per-locale font loading at the theme level.

The questions below address recurring client confusions translators field during scoping — platform coverage, automation scope, and the boundary between native CMS tools and a TMS.

Frequently asked questions

What is a localization service?

A localization service adapts content — text, images, dates, currency, and formatting — so it feels native to a target market, going beyond word-for-word translation. For translation agencies and freelance translators, this means handling CMS-exported strings, glossary management, style guides, and locale-specific QA. Certified translation production adds a layer of legal accountability, requiring credentials, stamps, or notarization depending on the jurisdiction. Localization projects typically span multiple file formats (XLIFF, JSON, PO) and platforms such as WordPress, Webflow, or Contentful.

What does CMS stand for in software?

CMS stands for Content Management System — software that lets teams create, edit, and publish digital content without writing code. In a translation and localization workflow, the CMS is the system translators must integrate with or extract content from; common examples include WordPress, Drupal, Contentful, Webflow, and Sanity. Most modern headless CMSs expose content via API, enabling translation management systems (TMS) or CAT tools to pull strings directly, reducing copy-paste errors and version-control problems.

How do I localize CMS items in Webflow?

In Webflow, CMS item localization is managed through the Localization panel, where you select a locale and then edit each CMS field's translated value directly in the Designer or via the CMS editor. Webflow's built-in localization (available on the Localization add-on plans) lets you create locale-specific slugs, rich text, images, and metadata per collection item. For agencies handling large volumes, Webflow also supports CSV export/import and an API endpoint for CMS items, so translators can work in their preferred CAT tool and push translations back programmatically.

Can Webflow automatically translate all CMS fields across locales?

Webflow does not automatically translate CMS fields — human or machine translation must be applied separately to each locale. The platform flags untranslated fields and can optionally fall back to the primary locale's content until a translation is published, preventing blank pages. Agencies typically export CMS content via Webflow's API or CSV, run it through a TMS or a first-draft generation tool, and then import the translated strings back. This workflow keeps certified translations auditable, which matters when the output will carry a translator's stamp or signature.

How does Webflow Localization handle CMS item translation and updates?

Webflow Localization tracks each CMS item per locale and marks fields as 'needs update' whenever the source content changes, signalling translators that a revision is required. Each locale version of a CMS item can have its own slug, SEO meta, and rich-text content, with Webflow serving the correct version based on the visitor's locale setting or URL prefix. For agencies, the key workflow consideration is maintaining parity between source updates and translated copies — Webflow surfaces out-of-date locales in the editor, but the actual re-translation task falls to the human or assisted-translation pipeline.

What are the different types of localization?

The main types of localization are website/software localization, document and legal localization, multimedia localization (subtitles, dubbing), game localization, and marketing/transcreation. For working translators and agencies, the most common revenue streams are document localization (contracts, certificates, legal filings — often requiring certified translations) and software/CMS localization (UI strings, help content, landing pages). Each type demands different file formats, glossary disciplines, and QA checks; certified document translation additionally requires credential verification and, in many jurisdictions, a signed declaration of accuracy.

What is the best CMS for a multilingual website?

WordPress with WPML or Polylang, Contentful, and Drupal are widely regarded as the strongest CMS options for multilingual sites used by translation agencies and their clients. WordPress dominates by sheer market share and plugin ecosystem; WPML integrates with most major TMS tools and supports certified-translation workflows through structured field management. Headless CMSs like Contentful and Sanity are favoured for developer-led projects because their API-first architecture makes it straightforward to push translated strings — including certified document text — directly from a translation management system.

How much does WPML cost?

WPML is priced in three tiers: the Multilingual Blog plan at around $39/year, Multilingual CMS at around $99/year, and the Agency plan at around $199/year. The CMS and Agency tiers include the String Translation and Translation Management modules that agencies need for professional workflows, including integration with external TMS platforms. Prices are subject to change; agencies handling certified translation projects should evaluate whether WPML's translation memory and glossary features reduce per-word production costs enough to justify the higher tier.

Is there a free multilingual plugin for WordPress?

Yes — Polylang and TranslatePress both offer free versions that support basic multilingual WordPress setups. Polylang's free tier handles posts, pages, categories, and tags in multiple languages, while TranslatePress free supports two languages with a visual front-end editor. For agencies producing certified translations, these free tools handle content delivery but lack the TMS integrations, translation memory, and glossary management available in paid tiers (Polylang Pro, TranslatePress Developer, or WPML), which are typically needed for scalable, auditable professional workflows.

What are the top 5 CMS platforms?

The most widely used CMS platforms are WordPress, Shopify (for e-commerce), Wix, Webflow, and Drupal, with WordPress alone powering roughly 40% of all websites. For translation agencies and localization teams, WordPress and Drupal are the most common targets because of their mature multilingual ecosystems; Webflow is increasingly relevant for agency client sites; and headless options like Contentful and Sanity are growing in enterprise localization pipelines. Understanding which CMS a client uses directly shapes the file-format strategy and integration tooling a translator or agency must deploy.

Related