AI Tools 15 Jul 2026  ·  2 min read

How to Build a Multilingual WordPress Site with AI and Polylang

Editor
X in ↗
How to Build a Multilingual WordPress Site with AI and Polylang
How to Build a Multilingual WordPress Site with AI and Polylang 15 Jul 2026
TL;DR — A multilingual WordPress site with Polylang normally requires double the content management work: create the post, create the translation, link them, set language on each, repeat for taxonomy terms. With 6 Polylang MCP abilities, an AI agent handles all of this in the same workflow as the original post creation — creating both language versions and linking them as a single operation.

Polylang is the most widely used multilingual plugin for WordPress. It works well manually for small sites. It becomes painful at scale: every post requires a second post in each additional language, language assignment on both, and a translation linkage operation. For a site publishing in two languages weekly, that’s roughly 3x the content management overhead.

The 6 Polylang Abilities

  • wds/set-post-language — Assigns a Polylang language to a post by post ID and language code
  • wds/link-translations — Links posts as translation pairs: {"en": 123, "de": 456}
  • wds/get-post-translations — Returns the full translation map for a post (useful for finding the DE ID from an EN post)
  • wds/set-term-language — Sets language on a taxonomy term (category or tag)
  • wds/link-term-translations — Links taxonomy terms as translation pairs
  • wds/get-term-translations — Returns the translation map for a term

The Bilingual Content Workflow

A complete EN+DE post pair, created by an agent in a single session:

  1. Create EN post via wds/create-post — returns post_id (e.g. 500)
  2. Set EN language: wds/set-post-language({post_id: 500, language: "en"})
  3. Create DE post via wds/create-post with translated content — returns post_id 501
  4. Set DE language: wds/set-post-language({post_id: 501, language: "de"})
  5. Link: wds/link-translations({translations: {en: 500, de: 501}})

Step 5 gives Polylang the information it needs to generate hreflang tags and language switcher links correctly. Skip it and the two posts exist as independent unlinked pages.

Taxonomy Translation

Polylang also requires language assignment and translation linking on categories and tags. wds/set-term-language and wds/link-term-translations handle this for both post taxonomy and WooCommerce product taxonomy. An agent setting up a new content cluster can create EN categories, create DE counterparts, and link them — all before creating the first post.

Hreflang and Canonical Alignment

For DACH-region sites specifically: English pages should resolve at /slug/ and German pages at /de/slug-de/. Polylang handles this when languages are correctly configured and posts are linked. The MCP abilities ensure the linking step is never missed — because it’s part of the automated creation workflow, not a separate manual step that gets forgotten.

WDS MCP Content Manager Pro is the only WordPress MCP plugin with full Polylang coverage for both posts and taxonomy terms.

AI translation multilingual WordPress Polylang WordPress MCP