Polylang already gives your site multiple languages, linked posts, and clean URLs. The pages are where the hours go. Hero copy, feature lists, CTAs, and FAQs sit inside dozens of Gutenberg blocks or Elementor widgets, far below the page title. Copy-pasting between tabs breaks block markup. Translating categories on their own leaves the site half done.

You ask Lola to translate a page and she does the whole thing, segment by segment, into a linked Polylang draft. Gutenberg block structure and Elementor layout stay intact on the server; only the text changes. Ask for a Portuguese version of a landing page, or a linked Spanish category when the taxonomy still needs work. She reads Polylang’s translation groups, shows a sample in the approval card, and holds it as a draft until you publish.

Same Polylang. Same structure. You stopped tab-hopping and started asking.

This is an addon. It needs LolaCore and Polylang active on the same site. Polylang Pro works too; the addon uses the same pll_* APIs on both editions.

For walkthroughs and example conversations, see lolacore.com/lolacore-for-polylang.

One addon, two surfaces: wp-admin and MCP

Every ability is available in the Lola chat inside WordPress admin and through LolaCore’s MCP server. Same 17 tools, same guardrails, same confirmation before writes. Use whichever surface fits your workflow; you do not learn two different products.

Example: coverage and a page translation

The exchange below is the same whether you type in wp-admin or call the abilities from Cursor or Claude Code. Names instead of database IDs keep it readable for everyone on the team.

In wp-admin (Lola chat):

You: How much of the site is still missing in Spanish?

Lola: Spanish coverage: about two thirds of pages, no posts yet, most categories done, one tag still open. The page Nos sacs à dos already has a Spanish draft (Nuestras mochilas). Portuguese is still missing for that page.

You: Translate Nos sacs à dos into Portuguese. Keep the layout, draft only.

Lola: I will create a linked Portuguese draft from the French original: the full page, with title, headings, body copy, and buttons (8 text segments). Gutenberg block layout preserved. Here is a short preview of the translation. Approve to save as draft?

From an MCP client (same site, same abilities):

You: Run translation coverage for Portuguese, then translate the page Nos sacs à dos.

Lola: Coverage first: 0% of pages in Portuguese. Nos sacs à dos has no Portuguese slot yet; the French page has 8 segments across headings, paragraphs, and buttons. I prepared the full-page Portuguese draft with the same structure. Confirm execution?

She checks the translation slot before creating duplicates and preserves layout server-side, with the same rules on both surfaces.

Full pages: Gutenberg blocks and Elementor

This addon is built for full-page translation. Lola walks the page tree, extracts every translatable text segment in order, translates them, and writes them into a linked Polylang draft. You review the whole page in the block editor or Elementor before publishing.

Gutenberg: Headings, paragraphs, buttons, lists, columns, cover blocks, and nested block content. Block JSON, attributes, and structure are preserved; Lola replaces copy inside the layout, not the layout itself.

Elementor: When Elementor is active, the same flow reads the Elementor widget tree and clones the page structure server-side. Text inside headings, text editors, buttons, and other widgets is translated segment by segment while the layout stays intact.

Categories and tags are supported too, useful for navigation and archives. The core value is translating complete pages without rebuilding them by hand.

What Lola does with Polylang: 17 abilities

Ask her for any of these in chat or over MCP.

Languages and settings (8 abilities)

Lists your languages with their locales, the default flag, and optional post counts.
Adds, updates, or removes a language. Sets the default one.
Reads your Polylang settings: URL mode, hide default, sync fields, translated post types and taxonomies.
Updates those settings and configures which custom post types and taxonomies are translatable.

Posts and pages (4 abilities): full-page translation

Reads a post’s translation group, its missing languages, the ordered source_segments (every text block on the page), and whether the page is built with Gutenberg or Elementor.
Creates a linked translation draft with the translated title and all page segments, Gutenberg blocks or Elementor widget text preserved and layout unchanged.
Assigns a language to a post, or links existing posts into one translation group when languages are already assigned.

Terms (4 abilities)

Reads category or tag translation groups, and looks them up by name in the default language.
Assigns a language to a term, or creates a linked translation.
Links existing terms across languages.

Coverage (1 ability)

Audits translation coverage per language: posts and pages by type, plus categories and tags, so you know which full pages to translate next.

Built-in domain knowledge

The addon ships a playbook and a skill Lola loads when working in this domain: how Polylang models languages and sync fields, and the canonical workflow (coverage first, check the slot, draft-first, parents before child terms). You do not configure them; they register when the addon is active.

You approve before anything publishes

Every write runs through LolaCore’s confirmation flow. Lola shows target language, title, and a short preview of the translation sample. You approve or cancel. New translations save as drafts unless you explicitly ask to publish. An existing translation slot is protected; a write against one stops with a clear error.

Third-party addon, not affiliated with Polylang

Polylang is a registered trademark of WP SYNTEX. LolaCore for Polylang is an independent addon built by LolaCore. It is not affiliated with, endorsed by, or sponsored by WP SYNTEX or the Polylang team. You install Polylang separately from WordPress.org.

What you need

WordPress 7.0+
PHP 8.1+
LolaCore, active
Polylang (Free or Pro), active
Elementor (optional) — required to translate Elementor-built pages

External Services

AI Providers (translation and chat)

When you ask Lola to translate content or chat about your site, text is sent to whichever AI provider you configured in WordPress’s built-in AI settings (Settings Connectors). LolaCore does not operate its own translation servers.

Data sent to your provider when translating:

Source post or term text (titles, ordered text segments, excerpts when provided)
Your chat messages and tool parameters
Relevant memory facts if Lola needs site context

Data this addon keeps on your server:

WordPress passwords, database credentials, and wp-config secrets
Unrelated post content beyond what you asked to translate

When this happens: Only when you send a chat message or execute a translation ability (chat or MCP). No background translation jobs.

Supported providers: Same list as LolaCore (OpenAI, Anthropic, and others you enable in Connectors). Use each provider’s terms and privacy policy.