Docs
← Back to site

Setting Up WPML

3 min readUpdated November 21, 2026

WP Super Docs is fully compatible with WPML out of the box. With WPML active, there’s no separate “connect” step, everything below is registered automatically as soon as both plugins are active.

What’s translatable automatically#

  • Docs themselves (the full post, title and content).
  • Products, Categories, and Tags, all three taxonomies get their own translation UI in WPML, so each language can have its own product names, category names, and tags.
  • Category icons, so a language that reads right-to-left or uses non-Latin text can have its own icon value if needed.
  • Meta descriptions (the SEO description field), translatable per language.

What’s shared instead of translated#

  • Status badges (New, Updated, Beta, Deprecated) are copied across translations rather than translated, since a badge represents the state of the doc itself, not language-specific text. The badge’s displayed label is still shown in the reader’s own language, only the underlying status value is synced across all translations of a doc.

Translating a doc#

With WPML active, open any doc and use WPML’s normal translation interface (the language column in the docs list, or the translation editor) exactly as you would for a page or post. Once a translation exists, the doc automatically gets a language-correct URL, and readers see the right language version based on WPML’s language switching.

Screenshot shows a “MULTILINGUAL” section listing WPML (not installed) and Polylang (not installed) plugins with brief descriptions and links for each. The section notes WP Super Docs supports both plugins for language-correct URLs.

Translating docs with Claude#

If Claude is connected (see Connecting Claude to Your Docs (MCP)), it can create a doc’s translation and write it in one step. Ask, for example: “Translate Installing Lumen Booking into German.”

Claude reads the original, then creates the translation:

  • Linked to the original in WPML, the same as a translation you add yourself.
  • In the right place: the original’s product and category in the target language. If that product or category has no translation yet, Claude creates it first, linked to the original (this needs an Administrator account, the same as creating products and categories in WordPress).
  • With the translated title, content, SEO title and description, and address (slug) in that language.
  • With the original’s featured image, tags, status badge, version and position in the sidebar. An internal-only doc stays internal-only.

Claude keeps code, images and videos exactly as they are in the original. A translation is created as a draft, unless you’ve let Claude publish and ask it to; it is only published once it is linked, so a half-made translation never goes live.

Claude can also tell you each doc’s language and which translations are missing, and update an existing translation like any other doc.

The original doc must have a language set in WPML first. If it hasn’t, Claude says so instead of guessing.

Translating admin-facing text#

A handful of settings-page text fields are exposed to WPML’s String Translation tool (under WPML → String Translation), so wording you’ve typed into settings can also be localized per language:

  • Brand text
  • Announcement banner text and URL
  • Popular section heading and intro text
  • Footer tagline and copyright text

Anything not on this list (most settings, like which features are enabled) applies sitewide regardless of language, since those are configuration choices rather than reader-facing text.

A share image per language#

On a multilingual site, Settings → SEO → Share images has a row under Docs homepage for each language. Set one to show a translated image when the docs homepage is shared in that language. See Share Images.

URLs#

Doc, product, and category URLs automatically resolve to the correct language’s version behind the scenes, on top of your normal /docs/{product}/{category}/{doc}/ structure. Exactly how the language itself appears in the URL (a subdirectory, a subdomain, or a query parameter) is controlled by WPML’s own language URL settings, not by WP Super Docs.

Was this helpful?

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only