Multilingual SEO Rotation (WPML / Polylang)

What it is

Multilingual SEO Rotation lets the title and meta description of a page rotate while staying in the right language and, crucially, without ever mixing languages between the title and its description. On a multilingual site this is the difference between a clean rotation and a snippet that pairs an Italian title with a German description.

Two modes exist. With a translation plugin like WPML or Polylang, each translated page is a separate post in its own language, so rotation is single-language: the variants for that page stay in the page's language. Without a translation plugin, AISA can also run a multilingual rotation on one page (a main language plus extra language variants in the pool). In both cases AISA can force synchronous rotation, where title slot N is always paired with description slot N, so the two never drift into different languages. The developer panel even tags each slot with its language code.

Where to find it

The title/description coupling (Synchronous vs Asynchronous) is set under Settings → SEO Rotation → Title / description coupling. Per-page language variants and the per-post sync flag are managed from the AISA floating panel on the editor; the panel reads the active translation plugin and offers the language list automatically. Detection uses the site's WPML/Polylang configuration.

Requirements & tier

Needs Extended SEO enabled (the base for any rotation) and a pool of at least 2 entries. Multilingual coupling matters most when WPML or Polylang is active, but the synchronous mode can be forced per post even without them. Generating language variants with AI uses your tier's normal token/credit allowance; the rotation engine itself runs on every tier where Extended SEO is available.

How to use

  1. Make sure WPML or Polylang is active (AISA detects it automatically) and Extended SEO is on.
  2. For coupled languages, set Settings → SEO Rotation coupling to Synchronous — title slot N stays bound to description slot N.
  3. Open a page and add aligned title/description variants in the AISA panel; for a one-page multilingual rotation add a variant per extra language.
  4. If you only want this page coupled, enable the per-post sync option in the panel (sets _aisa_rot_sync) instead of changing the global setting.
  5. Save and check the page in Developer Mode: each slot shows its language tag so you can confirm pairs stay in one language.

Questions people ask

  • Will my Italian title ever get a German description? Not in synchronous mode — slots are paired, so title N and description N are always the same language.
  • How does AISA know the page language? From WPML/Polylang assignment; without them it reads the page's real text and falls back to the site locale.
  • Do I rotate one multilingual page or separate translations? With WPML/Polylang each translation is its own post and rotates in its own language. Without them you can stack languages in one page's pool.
  • Why use synchronous instead of asynchronous? Asynchronous mixes titles and descriptions freely for more combinations — fine in one language, but it would mix languages, so multilingual rotations should be synchronous.
  • Does the developer panel show the language? Yes, each rotating slot is tagged with its language code.

Troubleshooting

If languages get mixed in the snippet, switch coupling to Synchronous (globally or per post). If a slot shows no language tag, the variant's language list (_aisa_rot_langs) wasn't saved for that page — re-open the panel and re-select the languages. If a translated page rotates in the wrong language, confirm the page is correctly assigned to its language in WPML/Polylang. For pairs to align, keep the title and description pools the same length — synchronous mode pairs up to the shorter of the two.

Related

What is SEO Rotation (and why it's not cloaking) · Custom rotation interval and slot cap · Supported editors and page builders.

← Back to support