--- title: LolaCore for Polylang canonical_url: https://lolacore.com/lolacore-for-polylang/ last_updated: 2026-07-10T08:27:30+00:00 plugin_version: 1.2.2 --- # LolaCore for Polylang LolaCore for Polylang · Free Add-on · Requires LolaCore Polylang links the pages. Lola translates them. =============================================== LolaCore for Polylang lets you translate a full page into a linked Polylang draft by asking in plain language: Gutenberg blocks, Elementor widgets, headings, buttons, the lot. Polylang keeps the languages, URLs, and translation groups. Lola does the copy work, segment by segment, with your approval before anything saves. [ Get it free → ](https://lolacore.com/install-lolacore-for-polylang) [ See what Lola can do → ](#polylang-demo) ● 17 capabilities● Gutenberg and Elementor● wp-admin and MCP ![LolaCore for Polylang](https://lolacore.com/wp-content/uploads/2026/07/lolacore-polylang.png) The Problem Polylang solved the structure. The content is still on you. ----------------------------------------------------------- Polylang gives you multiple languages, linked posts, clean URLs, and a language switcher. That part works. Translating an Elementor page means opening it, reading ninety widgets, and writing a linked Spanish draft with the layout intact. Done by hand, that is where the hours go. So you open the English homepage in one tab. You open the Spanish slot in another. You copy a headline, paste it into a translation tool, paste it back into a heading block, fix the markup you just broke, move to the next widget, repeat. On an Elementor page with ninety segments, that is an afternoon. On a client site with twelve pages in three languages, it is a line item you cannot bill for. Agencies feel this as margin leak: every new language multiplies maintenance hours. Store owners feel it as backlog: the French catalog exists in Polylang, but the landing pages never caught up. Categories get translated in isolation while builder pages stay half done. This is where LolaCore for Polylang comes in. You ask Lola to translate a page. She walks the block or widget tree, extracts every text segment in order, shows you a preview in the approval card, and writes a linked draft. Structure stays on the server. Only the copy changes. Demo What changes when Lola has Polylang ----------------------------------- Translating the homepage without opening Elementor ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaHomepageTranslate the homepage to Spanish. Keep the layout, draft only.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Your front page is *NarBaal | Summit Zero* in English, 95 text segments across headings, body copy, buttons, and labels, built with Elementor. I will create a linked Spanish draft with the same structure. Here is a short preview of the translation. Approve to save as draft?Yes.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Done. Spanish draft saved and linked to the English original. Review it in Elementor or publish when you are ready. French is still missing for this page.You never counted widgets or hunted for the front-page ID. Lola resolved the homepage, read the translation slot, translated every segment, and left the layout intact. Finding what is still missing before a client call ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaCoverageHow much of the site is still missing in Spanish?![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Spanish coverage: about two thirds of pages, no posts yet, most categories done, one tag still open. The page *Our backpacks* already has a Spanish draft. Portuguese is still missing for that page.Translate *Our backpacks* into Portuguese. Draft only.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)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. Approve to save as draft?The first question answered where the gaps are. The second filled one of them in the same conversation. No spreadsheet, no Polylang screen tour. Translating a category before the pages that depend on it ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaTermsWe need the Equipment category in Spanish before we finish the backpacks landing page.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Found *Equipment* in English. No Spanish slot yet. I will create a linked Spanish term: *Equipamiento*. Parent category stays aligned with your hierarchy. Preview: *Equipamiento*, archive title and description translated. Approve?Yes.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Done. Spanish category linked. Your backpacks page can now point to the right archive path when you translate it.Taxonomies and pages share the same workflow. Lola checks the slot, respects the tree, and links the translation group Polylang expects. MCP The same translation work, from Claude Code or Cursor ----------------------------------------------------- Claude Code · LolaCore MCP · client-narbaal-productionReaching client-narbaal-production.> translate the homepage to Spanish on this site. keep the layout, draft only● Reading site settings Front page is "NarBaal | Summit Zero" (English, Elementor)● Reading translation group 95 text segments, no Spanish slot yet● Translation preview ready Linked Spanish draftDone. Spanish draft saved and linked to the English original. Layout preserved across all 95 segments. Review in Elementor or publish when ready. French is still missing for this page. Want me to check sitewide coverage next?> yes, what's still missing in French across the whole site?● Coverage audit French: most categories done, two landing pages open, one tag still missing. "The Material" has no French slot yet.Want me to translate "The Material" next, or start with the open landing pages?>Natural language in, translation out. Claude Code or Cursor handles the reasoning on your existing subscription. Lola on the site handles Polylang structure, segment extraction, drafts, and confirmation. The reasoning runs on your subscription, so each client install works without provider keys of its own. Fleet You do not run one multilingual site. You run a fleet of them. -------------------------------------------------------------- If you manage client sites from Claude Code or Cursor, each Polylang install becomes another site Lola can reach over MCP, each with its own languages, memory, and translation rules. You stay in one IDE. Lola works site by site, the same way she does inside wp-admin. This is the pattern from [Connect your WordPress fleet to Claude Code](https://lolacore.com/wordpress-fleet-claude-code-mcp/): one MCP server per client, named so you recognize it at a glance, each install isolated. Claude Code · LolaCore MCP · 4 client sites connected> on client-montpeak, translate all the landing pages to French and Portuguese. drafts only, keep the layoutsStarting with client-montpeak.● Coverage 4 landing pages, French and Portuguese both missing on all four● "About us" French draft saved (23 segments, Gutenberg, layout intact)● "About us" Portuguese draft saved (23 segments)● "Services" French draft saved (41 segments, Elementor)…Montpeak: 4 landing pages × 2 languages, all saved as linked drafts. Nothing published. Ready for your review in wp-admin on each page.> good. now on client-narbaal, just the homepage to Spanish for nowSwitching to client-narbaal.● Front page 95 Elementor segments, Spanish draft saved and linked French still open on that page. Want me to leave it or queue it for later?> leave French for now. save today's session to memory on both sites● Memory saved client-montpeak and client-narbaal> Site A gets a batch of landing pages in two languages. Site B gets one homepage in Spanish. Same afternoon, same IDE, two separate Polylang installs, two separate memories. That is fleet-scale translation without opening eight wp-admin tabs. > Each client site is a separate install. Add LolaCore for Polylang on the sites that run Polylang, connect each MCP server to your editor, and start talking. Positioning Polylang runs your languages. You describe the translation. Lola does the rest. ------------------------------------------------------------------------------- Polylang handles the structural side of multilingual WordPress: languages, URLs, switchers, linked posts, hreflang. That layer stays Polylang's. The translation itself has always been hand work. Open the source page, open the target slot, move the copy across segment by segment, keep the layout together. On an Elementor homepage that is ninety widgets and an afternoon. Now you describe the page you want in the second language and Lola does that hand work for you. She reads the translation group, extracts every segment in order, and writes a linked draft with the layout intact. Same plugin, same data. You stopped clicking and started talking. For agencies that means one assistant across client sites: coverage audits, full-page translation, term linking, from wp-admin chat or from Claude Code when you run a fleet. For site owners it means the Spanish version of your Elementor homepage can exist by Friday instead of living on a to-do list. Polylang keeps language routing, slug sharing, and switcher markup. Lola works one layer up, on the copy, through Polylang's public `pll_*` API. The same one your theme already uses. How it works Chat → approval card → draft → publish -------------------------------------- 1. **You ask** in plain language: translate this page, add a language, show coverage, link these terms. 2. **Lola reads** Polylang's translation groups, extracts ordered text segments from Gutenberg or Elementor, and checks whether a slot already exists. 3. **You review** an approval card with target language, title, segment count, and a preview sample of the translation. 4. **Lola writes** a linked draft by default. Nothing goes live until you publish in WordPress or explicitly ask her to. The same four steps run in wp-admin chat and through MCP. Same guardrails, same confirmation before writes. Cross-domain A translated page is only useful when the rest of the site keeps up. -------------------------------------------------------------------- A homepage in Spanish still needs its meta descriptions in Spanish if search matters. An Elementor-built page needs the Elementor plugin active so Lola can read the widget tree. A block theme runs its templates through the same segment pipeline. Lola routes across domains when sibling add-ons are active. ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaCross-domainTranslate the homepage to Spanish and make sure the SEO fields are filled in on the new draft.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Homepage translation is ready as a Spanish draft: 95 segments, layout preserved. I can open the Spanish draft's Yoast fields next and write a meta description from the translated title and your store name. Want me to draft that too before you publish? Polylang made the language slot. Elementor kept the layout. [LolaCore for SEO](https://lolacore.com/lolacore-for-seo/) filled the fields search engines read. Lola connected three layers in one conversation because the add-ons declare affinity with each other. The same pattern applies with [LolaCore for SEO](https://lolacore.com/lolacore-for-seo/) (meta on translated posts), [LolaCore for FSE](https://lolacore.com/lolacore-for-fse/) (block theme templates), [LolaCore for ACF](https://lolacore.com/lolacore-for-acf/) (custom fields on translated content), and [LolaCore for Elementor](https://lolacore.com/lolacore-for-elementor/) (page building from chat). One assistant, one memory, multiple domains. [Part of the free add-on ecosystem](https://lolacore.com/add-ons/). Install only the domains your site uses; Lola routes across them when active. Capabilities When this add-on is active, Lola can do 17 things across 4 areas ---------------------------------------------------------------- These are Lola's abilities with Polylang, what she does on your site when the add-on is running. She handles the calls. You describe the outcome. Languages and settings (8) Lola lists your languages with locales and defaults. She adds, updates, or removes a language. She reads your Polylang settings (URL mode, hide default, sync fields, translated post types and taxonomies) and updates them when you ask. She configures which custom post types and taxonomies participate in translation. Posts and pages (4) This is the core value. Lola reads a post's translation group, missing languages, ordered text segments, and whether the page is Gutenberg or Elementor. She creates a linked translation draft with the translated title and every segment: block JSON or Elementor widget text preserved, layout unchanged when [Elementor](https://wordpress.org/plugins/elementor/) is active. She assigns a language to a post or links existing posts into one translation group. Terms (4) Lola works with categories, tags, and custom taxonomies. She reads term translation groups and looks them up by name in the default language. She assigns a language, creates a linked translation, or links existing terms across languages, parent hierarchy respected. Coverage (1) Lola audits translation coverage per language: posts and pages by type, plus categories and tags. She tells you which full pages still need work before you start clicking. Gutenberg and Elementor Elementor pages, translated widget by widget -------------------------------------------- **Gutenberg:** Lola extracts text from headings, paragraphs, buttons, lists, columns, cover blocks, and nested block content. Block attributes and structure stay on the server. She replaces copy inside the layout. **Elementor:** an Elementor homepage is ninety widgets of copy. When [Elementor](https://wordpress.org/plugins/elementor/) is active, Lola reads the widget tree, clones the page structure on the server, and translates the text inside headings, text editors, buttons, HTML widgets, and the rest, segment by segment. Validated in production: 87 segments on a material page, 95 on a homepage, layout intact. Who does what Two products, one workflow -------------------------- Polylang handlesLola handles (with this add-on)Languages, URLs, switchersFull-page translationLinked posts and termsSegment-by-segment copy in draftshreflang and translation groupsCoverage audits across content typesWhat appears in the Polylang UIElementor widget trees (when [Elementor](https://wordpress.org/plugins/elementor/) is active)The add-on is free and uses Polylang's public API on whatever edition you already run. Lola works one layer up: she does the translation work you would otherwise do by hand. Knowledge pack Lola loads domain context when this add-on is active ---------------------------------------------------- The zip ships a playbook and a skill Lola registers automatically: how Polylang models languages and sync fields, plus the canonical workflow. Coverage when you need a site-wide picture, a translation-slot check before creating duplicates, draft-first, parents before child terms. They load when the add-on is active and guide Lola's decisions in chat and MCP. Safety Nothing publishes without your approval --------------------------------------- Every write runs through LolaCore's confirmation flow. Lola shows target language, title, segment count, and a preview sample. You approve or cancel. New post and page translations save as drafts unless you explicitly ask to publish. An existing translation slot is protected: a write against an occupied slot stops with a clear error instead of overwriting. Read actions (listing languages, reading coverage, inspecting translation groups) run directly. They make no changes. Requirements What you need ------------- [LolaCore](https://wordpress.org/plugins/lolacore)Free, active on the same sitePolylangActive and configured with at least one languageWordPress7.0 or higherPHP8.1 or higher[Elementor](https://wordpress.org/plugins/elementor/)Active on the site for Elementor-built page translation **AI provider, two paths:** **wp-admin chat:** configure an AI provider in WordPress (Settings → Connectors). Lola sends source text to your chosen provider when generating translations. **MCP via Claude Code or Cursor:** no AI provider keys needed on each WordPress site. The reasoning runs on your Claude or Cursor subscription. Lola on the site executes Polylang abilities, previews, and drafts. Same guardrails either way. Source text goes straight from your site to the AI provider you configured. For developers If you already run Polylang in code or from your IDE ---------------------------------------------------- Most of this page is written for people who experience translation as hours in the admin, not as API calls. First, every ability Lola gains from this add-on runs against Polylang's public `pll_*` API. The translation groups she creates are indistinguishable from ones you would build through the Polylang UI or in custom code, down to the linked posts and terms. Second, all 17 abilities are exposed through LolaCore's bundled MCP server. Connect Claude Code, Cursor, or any MCP client to your LolaCore site and those Polylang tools appear alongside everything else LolaCore exposes. Slot checks and draft defaults apply the same way as wp-admin chat. Third, MCP mode runs on your IDE subscription for the reasoning, with no provider configured in WordPress. Lola on the site handles execution, memory, and confirmation. That is what makes fleet work practical: connect each client site once, name the server, and translate from plain language. The wp-admin chat and the IDE are two entry points to the same Lola. Use whichever fits the moment. Frequently asked questions Questions --------- Do I need anything besides LolaCore and Polylang? No. Install the add-on, activate it, and Lola discovers the Polylang capabilities automatically. For Elementor-built pages, translation runs when [Elementor](https://wordpress.org/plugins/elementor/) is active on the site. No settings page, no API keys specific to this add-on. How does Lola work alongside Polylang? Polylang stays installed and runs your languages, URLs, switchers, and translation groups. Lola works on top of it and does the translation itself. Two products, one workflow. Can I review translations before they go live? Yes. That is the default. Lola shows a preview in the approval card and saves new translations as drafts. You review in the block editor, Elementor, or chat, then publish when you are satisfied. Does it work with Gutenberg and Elementor? Yes. Gutenberg pages are handled natively. Elementor pages use the same flow when [Elementor](https://wordpress.org/plugins/elementor/) is active on the site. Can I use this from Claude Code or Cursor without configuring AI in WordPress? Yes. Over MCP, your IDE subscription handles the reasoning. Lola on the site executes the Polylang abilities with the same guardrails as wp-admin chat. Provider keys in WordPress Connectors are not needed for that workflow. Can I manage translations across multiple client sites from one IDE? Yes. Connect one MCP server per client site, name them clearly, and work site by site in plain language. Each site keeps its own memory and Polylang configuration. See [Connect your WordPress fleet to Claude Code](https://lolacore.com/wordpress-fleet-claude-code-mcp/) for the full setup. Is this affiliated with the Polylang team? No. Polylang is a registered trademark of WP SYNTEX. LolaCore for Polylang is an independent add-on built by LolaCore. It is not affiliated with, endorsed by, or sponsored by WP SYNTEX or the Polylang team. Polylang links the pages. Lola translates them. ----------------------------------------------- Install the add-on and Lola discovers all 17 Polylang capabilities automatically. No configuration needed. [Get it free →](https://lolacore.com/install-lolacore-for-polylang)Don't have LolaCore yet? LolaCore is the free AI agent that lives inside your WordPress admin. It reads your site, takes action with your approval, and remembers everything across sessions. [Get LolaCore free →](https://wordpress.org/plugins/lolacore) Polylang is a registered trademark of WP SYNTEX. LolaCore for Polylang is an independent add-on built by LolaCore. It is not affiliated with, endorsed by, or sponsored by WP SYNTEX or the Polylang team.