Translate a Bubble Website Without Coding: Which Tool Fits
Bubble's App texts only cover short labels. See which plugin or service translates a full Bubble site with a URL per language and hreflang tags.
Bubble's built-in App texts can translate short strings such as headers, menus and button labels, but Bubble's documentation says they are meant for shorter content, not long articles or product descriptions. For a full website, most non-coders need a translation plugin or a SaaS service, and the key check is whether each language gets its own indexable URL with hreflang tags. Lantis bills per active language, but Bubble is not among the platforms it names, so test it on a copy of your app before paying.
Key points:
- Split the work: keep App texts for short interface labels and use a full-page tool for blog posts and long service pages.
- Check the URLs first: if every language shares one address behind a switch, the SEO job is not done.
- Budget for your word count: Weglot's allowance is source words multiplied by destination languages, so the real cost grows with each language.
- Test before you buy: Lantis does not name Bubble among its platforms, so run any tool on a copy of your app first.
Can Bubble's built-in App texts translate a whole website?
Bubble has a native translation system called App texts. It can be used for a single language, or each string can be translated into other languages, so every label in the app gets a version per language. It needs no third-party tool, which makes it the natural starting point for an app with a small interface.

The limits show up on a full website. App texts are static data, so the app must be redeployed whenever one of them changes. Bubble's documentation describes them as meant for shorter content like headers, menu options and button labels. A site with blog posts, long service pages or product descriptions turns every text edit into a redeploy, and that becomes slow to maintain.
In practice, App texts suit navigation, buttons, form labels and short headings. Long body copy, legal text and articles are better handled by a tool built for full-page translation, while App texts keep covering the interface.
How do you export and import translations without breaking the app?
Bubble lets you export all app strings to a CSV file, edit them and import them back. An outside translator can then work on the file without access to the Bubble editor, so the file becomes the handoff point between you, the translator and the app.
The import step has a trap, and Bubble's manual states it plainly:
"Importing a CSV overwrites all strings, even where a cell is left empty." — Bubble's manual
If a translator leaves a cell blank, the existing translation for that string can be erased. Before each import, keep a copy of the current export, and ask translators to fill every cell, even where the text is unchanged.
When a string has no translation for the active language, Bubble shows "(no translation)" in its place. Visitors see this on any page where a label was missed. Check every language after the import, not only the home page, and include pages that are only reachable after login or after a click.
Does each language get its own URL?
Bubble's native language switch works through a URL parameter, by adding lang=code to the address, or through a language field on the user, according to Bubble's manual. It does not create a separate URL per language by default. A search engine may then see a single address whose content changes, which is a weak base for ranking in each language.
Some translation plugins aim to solve this. An older Bubble forum thread reports that Bubble's SSL certificate did not support Weglot's subdomain setup, which would switch translated URLs to HTTP. The thread is old and the problem may no longer apply, but it is a reason to load a translated page and confirm it opens over HTTPS.
Vendors say they handle the SEO side. Bubble's blog on the Weglot plugin says Weglot adds hreflang tags and translates your metadata. Linguise says that each page gets unique URLs, alternate links and HTML tags, and ConveyThis says it generates SEO-optimized subdirectories and implements hreflang tags. Linguise and ConveyThis describe this on their own marketing pages.
If you also want to decide whether translated slugs matter for ranking, this guide on translating URLs and slugs covers the question in general terms.
A simple check works for any tool: open a translated page, view its source and look for the language URL, the hreflang tags and the translated title and description. If the language versions share one address, or the hreflang tags are missing, the tool is not doing the SEO job.
How do plugins and services compare on installation and cost?
Installation differs more than the marketing suggests, and each route changes your setup differently.
The plugin route is the shortest path for most non-coders. According to Bubble's blog, you add the Weglot plugin to your app, and it detects the content, translates it with neural machine translation and shows the result under language subdomains.
The DNS route is different. Linguise's Bubble integration uses an automatic DNS setup and a link added in the app settings. This is a different installation method from pasting a single line of code, so check what changes on your domain before you start.
The browser route is the weakest for search. Some Bubble plugins translate the page in the browser. One free plugin on the Bubble forum says it relies on the Google Translate widget for all translations, so its results depend on that widget's behavior. That can be enough for a quick reading of a page, but it gives you little control over what search engines index in each language.
Weglot's paid plans start at 15 euros per month, according to a 2026 pricing guide. The price depends on volume more than on the plan name: the translated word count is calculated as source words multiplied by the number of destination languages, so the allowance grows with each language you add.
The language limits matter too. A pricing analysis from Glopal says Weglot's caps step up unevenly: 1, then 3, then 5, then 10, then 20 languages. Weglot's free plan covers a small website in one language, with a 2,000-word limit. The same Glopal analysis says professional human translation is billed separately from around 0.13 euros per word, while AI translation is included in the plan.
The table applies the same criteria to each option.
| Option | Installation | URL per language | Starting price |
|---|---|---|---|
| Bubble App texts | Built into Bubble, no extra tool | No separate URL by default; lang=code parameter | The sources consulted do not detail it |
| Weglot plugin | Add the plugin to the app | Language subdomains, with hreflang tags, per Bubble's blog | 15 euros per month, per the 2026 guide |
| Linguise | Automatic DNS setup plus a link in app settings | Unique URLs per page, per Linguise | The sources consulted do not detail it |
| ConveyThis | Bubble plugin | SEO-optimized subdirectories and hreflang, per ConveyThis | The sources consulted do not detail it |
| Free browser plugin | Plugin using the Google Translate widget | The sources consulted do not detail it | Free |
| Lantis | One line of code, no DNS change | Own URL per language, with hreflang and sitemaps | 3 euros per month for one language |
What does Lantis cost, and what should you test on Bubble?
Lantis is an AI translation and multilingual SEO service. It charges only for active languages: 3 euros per month for one language, 2.50 euros per language per month for 2 to 9 languages, and 2 euros per language per month for 10 or more. The Agency plan costs 49 euros per month for up to 20 websites, with up to 5 languages each.
There is no limit on websites or visitors. Each language includes 500,000 words, and an extra block of 500,000 words costs 1 euro as a one-time payment. Lantis has no lock-in period and refunds the full amount within 14 days of each payment. It translates with Gemini by default and also offers Claude, DeepL and DeepSeek, with more than 60 languages available. More than 150 active websites are translated with Lantis.
On the SEO side, Lantis gives each language its own URL and generates hreflang tags and sitemaps automatically. It also includes a visual editor to correct translations, a glossary per language, exclusion of pages or blocks, and analytics on visitors' languages. It installs by pasting one line of code, without changing DNS or the design.
Lantis names Framer, Webflow, Shopify and WordPress, and says it works on any website. Bubble is not among the platforms it names, so paste the line into a copy of your app, then check the language URLs, the hreflang tags and the translated metadata before you pay.
If you want a plugin that Bubble's own blog presents for Bubble apps, Weglot is the better-documented choice today. Its cost rises in steps as you add languages and words. Lantis includes 500,000 words per language and sells extra 500,000-word blocks for 1 euro, so it also has a word limit. Compare both against your own word count. For a wider view of when AI translation suits a business site, this comparison of AI and manual translation sets out the trade-offs and costs.
Is machine translation good enough, and how do you review it?
Machine translation is fast, but quality varies. Sommo's tech guide to Bubble localization says plugin localization is time-efficient, but that the translation quality could be better, and that some languages may have problems even when the plugin supports them.
For a business site, review the pages that carry revenue or legal weight: the home page, pricing, checkout, terms and privacy text. Weglot sells professional human translation separately, which suits those pages if you want a person to check them, at around 0.13 euros per word according to Glopal. Other tools offer an editor where you correct the machine output yourself.
A workflow a non-coder can run:
- Let the tool translate the whole site.
- Open each language and read the key pages in that language, not in the source language.
- Fix errors in the tool's editor, or in the CSV for App texts, and keep a copy of the previous version.
- Add a glossary entry for product names and terms that must stay unchanged.
- Recheck after any large edit to the source pages.
A label that is correct in the source language can read oddly once translated, so a native speaker should look at each language before launch.
Next steps
- Count your source words and list the languages you need. Multiply them to see how much each tool must translate, and check the price at that volume, not at the starting price.
- List what has to be translated: interface labels, long pages, database content and metadata. Keep App texts for the labels and choose a full-page tool for the rest.
- Install any candidate on a copy of your app and view the source of a translated page. Look for one URL per language, hreflang tags and a translated title and description.
- Export your current App texts to CSV and save the file before any import, so a blank cell cannot erase a translation you cannot recover.
- If you want to see how Lantis handles URLs and hreflang, paste its one line of code into that copy and run the same checks; its checklist for switching translation tools without losing SEO lists what to compare before and after.
Frequently asked questions
Does Bubble's built-in translation work for SEO, or do I need a plugin?
App texts translate strings, but the native language switch uses a lang=code URL parameter or a language field on the user, and it does not create a separate URL per language by default, according to Bubble's manual. For per-language indexable URLs and hreflang tags, you need a plugin or a service that provides them.
How do I export and import translations in Bubble without breaking the app?
Export all strings to CSV, have the translator fill every cell and import the file back. Bubble's manual warns that an import overwrites every string, including empty cells, so keep a copy of the previous export. Afterwards, open each language and look for "(no translation)" in place of any text.
Is machine translation good enough for a business website, or do I need human review?
It is a good first pass, but quality varies by language and tool. Sommo's tech guide says plugin translation quality could be better. Review your highest-value pages, such as pricing, checkout and legal text, in the target language, with a native speaker if you can.
How many translated words will my Bubble site need?
Count the words in your source site and multiply by the number of languages, which is how Weglot's translated word count is calculated. A site of 10,000 source words in three languages therefore needs 30,000 translated words. Lantis includes 500,000 words per language, and an extra 500,000 costs 1 euro as a one-time payment.
Sources
- Bubble manual: App texts translations
- Bubble + Weglot: Create Multilingual No-Code Web Apps (Bubble Forum)
- Bubble + Weglot: Create Multilingual Web Apps With No-Code
- Automatic website translation for Bubble.io (Linguise)
- AI-powered Bubble Translator (ConveyThis)
- Bubble Language Translator plugin (Bubble Forum)
- Weglot Pricing Calculator: Plans, Costs and Squarespace Checks
- Weglot pricing in 2026: what it really costs to scale (Glopal)
- Weglot Pricing 2026 (G2)
- Tech Guide to Bubble App Localization & Translation (Sommo)
Pon tu web en varios idiomas hoy.
Una línea de código. SEO real por idioma. Traducción con IA. Sin tarjeta para empezar.