Features
One script tag, and the site speaks every language
WeLocale translates the page your visitor actually receives. There is no second copy of your content, no proxy in front of your site and no DNS change. Below is what that gets you, and a straight list of what it does not.
Translation
- Automatic AI translation into 50+ languages, triggered from the dashboard rather than page by page.
- Every string is editable. Click a translation, fix it, and it is live immediately with no deploy. Editing does not charge your allowance a second time.
- Version history per string, so a bad edit is recoverable rather than final.
- Automatic page discovery. The widget picks up pages as visitors browse them, and on paid plans a crawler finds them upfront instead of waiting for traffic.
- Right-to-left support. Arabic and Hebrew flip the layout direction, not just the words.
The language switcher
- Several styles: a floating button, a horizontal bar, pills, and a flag list, with desktop and mobile variants of each.
- Draggable positioning, so it sits where it does not collide with your own UI.
- Mobile-first behaviour with thumb-sized targets and a bottom sheet rather than a cramped dropdown.
- Visitor language detection on first arrival, from browser settings.
- Removable branding on Pro and Scale. On the trial and Starter a small WeLocale badge stays.
Works with what you already have
Because we translate rendered output rather than integrating with a framework, the list of things we support is mostly "all of it". There is no per-platform plugin to wait for.
- WordPress , with a plugin in the WordPress.org directory, or the script tag
- WooCommerce, including product pages, cart and checkout
- Elementor, Divi, Bricks, Oxygen, Beaver Builder and Gutenberg
- Webflow, Wix, Squarespace, and the AI and no-code builders such as Framer, Carrd, Bolt and Lovable, where we document exactly where the snippet goes
- React, Vue and Next.js, including client-side route changes, because a route watcher re-scans on navigation
Worth being clear about one thing: only the WordPress plugin exists as a real integration. Everywhere else it is the script tag, which works but is not a marketplace app.
Performance and SEO
- The loader is one asynchronous script and does not block rendering.
- Translations cache in the browser, so repeat page views make no API call.
- The html lang attribute is set synchronously, early enough for a crawler's first pass.
- hreflang tags on Pro and Scale, so search engines know which language each page is.
What it does not do
Every tool has a shape. Here is ours, so you can rule us out quickly if one of these is a requirement.
- No translated URL slugs. Your permalinks stay in the original language. WPML , Polylang Pro and proxy-based services such as GTranslate do this and we do not.
- No per-language content. This is a translation layer. If Spanish visitors need a genuinely different page rather than a translated one, you want a multilingual CMS.
- A ceiling. Our largest plan covers 400,000 source words and 2,000,000 translated words. Above that, look at Weglot's upper tiers or an unmetered proxy service.
- It depends on our service. If your plan lapses the widget stops serving translations. Nothing is deleted, and it resumes when you come back, but the site is not multilingual in the meantime.
- No human translation marketplace. You can edit everything yourself or paste in a translator's work, but there is no professional translation workflow inside the product.
Free
Try it on a real page
- 10,000 translated words
- 3 languages
- 3,000 source words
- 1 website
- Widget scan (visited pages only)
- Language detection
- Support: community
- No auto-crawl
- WeLocale badge on your site
Starter
Launch your first translated site
- 120,000 translated words
- 10 languages
- 60,000 source words
- 2 websites
- Auto-crawl (depth 2)
- Customizable switcher
- Support: email (48h)
- WeLocale badge on your site
Pro
For serious global teams
- 600,000 translated words
- 20 languages
- 150,000 source words
- 5 websites
- Auto-crawl (depth 3)
- Page-specific translations
- All switcher styles
- SEO hreflang tags
- No badge
- Support: email (24h)
Scale
Large sites and agencies
- 2,000,000 translated words
- 50 languages
- 400,000 source words
- 8 websites
- Auto-crawl (depth 5, 500 pages)
- Page-specific translations
- All switcher styles
- SEO hreflang tags
- No badge
- Support: priority (4h)
Words are bought once. Nothing resets monthly, and editing a page you already translated does not spend your allowance again, so "translated words" means how much translated content you have, not how much you have ever generated.
Questions people ask
How does runtime translation actually work?
The widget loads asynchronously, reads the text nodes on the page, and asks our API for translations keyed by the content itself. Text is replaced in place, so React and Vue event listeners survive, and results are cached in the browser so repeat visits make no API call. Nothing is duplicated in your CMS and nothing is proxied.
Can I edit what the AI produced?
Yes, and this is the part people underestimate. Every string is listed in the dashboard with its translation, and editing one publishes immediately with no deploy. Editing does not spend your word allowance again, because the charge for a string in a language is replaced rather than added.
Does it handle SEO?
Partly, and it is worth being precise. On Pro and Scale we inject hreflang tags so search engines understand which language a page is in, and we set the html lang attribute early enough for crawlers to read it. We do not translate URL slugs, so if you need each language on its own indexed URL path, a plugin like WPML or a proxy-based service fits better.
What about right-to-left languages?
Arabic and Hebrew switch the text direction along with the text, so the layout flips rather than rendering left to right with translated words in it.
Does it work on single-page apps?
Yes. A route watcher notices client-side navigation, including history pushState and replaceState, and re-scans the new view. That is why it works on React, Vue and Next.js sites without an integration.
What are the real limitations?
No translated URL slugs, no per-language content differences, a ceiling of 400,000 source words and 2,000,000 translated words on our largest plan, and translations stop being served if your plan lapses, though nothing is deleted. Those are on the list below rather than buried.