Comparison · Checked 9 July 2026
What does translating a Framer site actually cost?
Four ways to make a Framer site multilingual: the native Locales add-on, two subscription services, and a one-time plugin. Same questions for each: what does it cost, who owns the result, what does Google see.
| Framer Locales | Weglot | Linguana | Page Translator | |
|---|---|---|---|---|
| Pricing model | $20 per locale, per month (no annual discount found) | From €15/month (Starter, 1 language). 3 languages needs Business, €29/month | From $19/month billed yearly ($25 monthly), Starter | €29 once, no subscription |
| 3 extra languages, 1 year | $720/year | €290/year (Business, billed yearly) | $228/year (Starter includes 3 languages) | €29 total, forever |
| Where translations live | Native locales inside Framer, at /fr, /de paths | Served by Weglot on a subdomain or subdirectory. Reverse proxy is Enterprise-only | Translated static pages hosted by Linguana, on subdirectories | Real Framer pages in your own project |
| Word / page limits | No word cap. AI translation consumes your plan's credits | 10,000 words on Starter, 50,000 on Business | One-time grant of 10,000 AI credits on Starter (1 credit = 1 word). Manual translation is free | None on Pro |
| hreflang, served how | Server-rendered hreflang, lang and RTL. Translated slugs and metadata per locale | Server-side hreflang via subdomains or subdirectories | Server-side hreflang, subdirectories, translated slugs and meta tags | hreflang injected client-side by a script, not server-rendered. See the note below |
| If you stop paying | Not documented by Framer | Not documented on their pricing page | Not documented on their pricing page | Pages stay in your project, nothing breaks |
| Platform | Framer only | Any platform | Framer, Webflow and others | Framer only |
Framer renders the served lang attribute and hreflang tags from its own native Locales, and locks them: no plugin can rewrite the published HTML. Page Translator duplicates pages instead of buying native Locales, so it injects hreflang link tags with a script that runs in the browser, and sets lang and text direction client-side. Google renders JavaScript and can pick those tags up, but this is not one of the three server-side methods Google documents, and other crawlers are less reliable at it. Framer Locales, Weglot and Linguana all serve hreflang server-side. If hreflang served in the raw HTML is a hard requirement for you, that is a real argument for native Locales over this plugin, and we would rather you knew.
Honest take
When each one makes sense.
The most integrated option, and the strongest on SEO plumbing: server-rendered hreflang, translated page paths and metadata per locale, native RTL, CMS included. Every locale is editable inline on the canvas. If budget is not the constraint and you localize continuously, it is the comfortable choice.
Built for stacks that go beyond Framer. If you run several sites on different platforms and want one dashboard with a visual editor for translators, the subscription buys real workflow value. Note that Starter covers one language: three languages means the Business plan.
A cheaper subscription focused on no-code platforms, with subdirectory SEO, translated slugs and server-side hreflang. Reasonable middle ground if you accept a capped credit grant and hosting the translations outside your project.
Built for one thing: real translated pages inside your own Framer project, paid once. You own the result, Google indexes your URLs, and nothing depends on a subscription staying active. Two honest limits: hreflang is injected client-side rather than server-rendered, and CMS collections need its sister plugin, CMS Translator.
FAQ
The questions everyone asks.
Yes. Page Translator duplicates your pages at /fr, /de, /es with the content translated. They are regular Framer pages, on any Framer plan, no add-on required.
Page Translator's free plan covers 1 target language and up to 5 pages, including one instant translation run. Framer's Free plan also includes one locale to try. Either is enough to see the result on your own pages before paying anything.
Pages created by Page Translator are real pages at real URLs, so Google crawls and indexes them like any other page. Google also states that properly translated pages are not duplicate content. Indexing and hreflang are separate things: see the note above on how this plugin injects hreflang.
Nothing. The translated pages are part of your Framer project, not an overlay or a hosted copy. Uninstall the plugin and every page stays exactly where it is. The hreflang script, which lives in your project's custom code, is what stops.
No, it translates static pages. For blog posts and CMS collections, CMS Translator creates a synced translated mirror of any collection. The Translation Pack bundles both for €39.
Prices, plan names and word limits checked on each vendor's public pricing page on 9 July 2026. Neither Weglot nor Linguana documents on that page what happens to translated content after cancellation, so this table does not claim it. Plans change: verify before deciding.
Real pages. One payment. Your project.
Install free, translate one language in one click, and see the pages appear in your own Framer project.