Docs
← Back to site

Setting Up Polylang

3 min readUpdated November 6, 2026

Like WPML, Polylang works with WP Super Docs automatically. Once both plugins are active, docs, products, and categories are registered as translatable with no extra configuration.

What’s translatable automatically#

  • Docs themselves (the full post, title and content).
  • Products and Categories.

Tags are not automatically translatable#

Unlike WPML (where a separate configuration file covers Tags as well), Polylang’s translatable-taxonomy registration only includes Products and Categories. If you need Tags to also be per-language under Polylang, that would need to be added as a customization, it isn’t covered out of the box the way it is under WPML.

How translation works differently under Polylang#

Polylang’s model is different from WPML’s: each language gets its own separate, independent post or term, rather than one canonical object with translated fields attached. In practice this means:

  • Category icons and meta descriptions are naturally independent per language, since each language’s category or doc is its own separate object with its own meta values, no special configuration needed for this to work correctly.
  • Status badges (New, Updated, Beta, Deprecated) are not automatically kept in sync across a doc’s translations the way they are under WPML. Since each translation is a fully separate post, setting a badge on the English version doesn’t set it on the Spanish version too. If you want badges to match across languages, either set it on each translation individually, or use Polylang’s own custom fields synchronization setting (Languages → Settings → Synchronization) to sync it automatically.

Translating a doc#

With Polylang active, use its normal translation interface, available directly on the docs list and in the doc editor, exactly as you would for a page or post. Once translated, each language version gets its own language-correct URL automatically.

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 Polylang, 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 Polylang first. If it hasn’t, Claude says so instead of guessing.

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#

Language is reflected in the URL according to however you’ve configured Polylang itself (a language subdirectory, separate domains, or a default-language-hidden setup), layered on top of WP Super Docs’ normal /docs/{product}/{category}/{doc}/ structure. This is controlled by Polylang’s own 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