Platforms

Every platform we checked, and the honest answer for each.

A pasted tag translates any site in the visitor's browser today. It cannot give you a URL per language, and that is usually what a shop owner actually wants. On these platforms it could be done properly — by pushing translations into the platform's own store and letting the platform serve the URLs. We have built that for none of them yet.

A translation API exists, so this is a build we could do

Each of these has a documented way to write translations into the platform, which is what makes a real language URL possible without a proxy.

Adobe Experience Manager

language roots (/content/site/fr)

BigCommerce

path segment on Catalyst (/fr/product); Stencil themes stay on one URL

Craft CMS

one site per language, own entry URI format

Elementor

as WordPress

Framer

path prefix (/fr, /es-MX), hreflang generated

HubSpot

subdirectory variants (/es/)

Magento

store view code in URL (/fr/)

PrestaShop

language URLs (/fr/)

Salesforce Commerce Cloud

locale in site URL

SAP Commerce Cloud

composable storefront (/en/)

Shopify

subfolders (/es/products/…)

Shopware

domain per language on a sales channel

Webflow

secondary locales at subdirectories

WooCommerce

as WordPress

WordPress

subdirectories via WPML or Polylang

Zendesk Help Center

/hc/fr-fr/

Should already work — unproven

AI app builders generate a real project with a real build step, so the build-time integration and the MCP server should apply unchanged. That loop has been run against Lovable and nothing else.

Base44

AI app builder: no platform store; Embed or Build through the MCP loop proven on Lovable (v38, 2026-08-15)

Bolt.new

Same shape as Lovable: custom MCP connector at build time

Macaly

AI app builder, same shape as Lovable

Partial — the platform serves language URLs, the write path does not reach them

Drupal

JSON:API cannot create additional translations of an existing node; contrib or custom endpoint needed

Duda

Dynamic pages read per-language external collections; static page text has no write API

Help Scout Docs

Docs API creates articles; no cross-language linking or hreflang

TYPO3

Translations are core; a write API needs an extension (nnrestapi)

No way in — a tag is all anyone can offer without a proxy

These have no API for writing translations into their own pages, so nobody can give you a URL per language here without putting a proxy in front of your whole site. Squarespace's own help page routes multilingual customers to a proxy vendor. A pasted tag still translates them for your readers: readable in every language, findable in one.

Big Cartel

Third-party script only

Bubble

App texts are static and need a redeploy; no write API for them

Carrd

Third-party script only

Dorik

Duplicate pages plus a custom-code switcher

Durable

Third-party script only

Format

Third-party script only

Ghost

One install per language is Ghost's own recommendation

Heyflow

Conditional logic per language inside one flow; no language URL

Jimdo

System and shop pages cannot be duplicated

Kajabi

A page exists in one language; duplicates by hand

LearnWorlds

Third-party script only

Onepage

No multi-language function; Weglot

Podia

No built-in support; third-party scripts

Softr

Weglot integration is the documented route

Square Online

Manual translation or the Weglot app

Squarespace

Squarespace's own help routes multilingual to Weglot

Teachable

Two languages means two schools

Thinkific

Language settings translate UI strings only, not page or lesson text

Unstack

Third-party script only

Weebly

Same builder as Square Online

Wix

Translation Content API covers an app's own entities; site page text is the Translation Manager UI only

Wix Studio

Same platform as Wix

Zoho Commerce

No native feature; third-party scripts

We could not find out

No vendor documentation turned up either way. If you use one of these, you know more than we do.

OpenBuilder

No vendor documentation found on 2026-09-13

ShopWired

Weglot writes for it; no ShopWired documentation found on 2026-09-13

That is every platform, not a shortlist

Fifty-two platforms were enumerated against their own documentation, and every one of them is on this page — including the ones where the answer is no. Two are left out with a reason written down: a dealer-site agency that builds Spanish sites by hand, and a one-page builder that is one language by design.

Where BeMyWords is the wrong choice →