Website translation software review Updated 2026
Weglot review 2026
Weglot remains one of the quickest ways to turn a WordPress, Shopify, Webflow or custom website into a managed multilingual experience. The appeal is speed, centralised editing and strong server-side SEO options. The trade-off is a recurring subscription tied to translated words, languages and higher-plan features.
Affiliate disclosure: this review contains affiliate links. We may receive a commission if you purchase through them, at no extra cost to you. That does not change the drawbacks, pricing cautions or alternatives covered below.
The quick answer
Is Weglot worth it?
Weglot is worth considering when launching multilingual content quickly matters more than owning every translation file and integration layer from day one. It removes much of the setup friction, but it does not remove the need for translation review, technical QA, international SEO strategy or privacy governance.
Our honest verdict
Weglot’s strongest advantage is operational simplicity. Add the integration, choose languages and the platform detects content, generates automatic translations and provides a central place to edit them. That is a very different proposition from manually rebuilding pages, duplicating templates or coordinating translation files outside the website.
The platform is also more mature than many older reviews suggest. Current plans include an AI Language Model, glossary controls, media translation, visitor redirection, statistics, translated URLs, custom languages, import/export, top-level-domain options and translation memory at different tiers. Recent integration releases have focused on Weglot 2.0 compatibility, dynamic DOM performance, XHR URL translation, search forms and language-switcher accessibility.
The main weakness is commercial rather than conceptual. A small website can be inexpensive, but a large content archive translated into several languages can move through the plans quickly. Export, custom languages and other operational safeguards are also plan-gated. Businesses should calculate translated words before installing, not after the trial has populated the dashboard.
Weglot is a strong fit when
- You need a multilingual website live quickly without rebuilding every page.
- Your organisation uses more than one website platform.
- Marketing teams need a visual editing and glossary workflow.
- Dedicated language URLs and hreflang are important for international SEO.
- You can budget for a recurring service as content and language coverage grow.
- You are prepared to review high-value, legal and conversion-focused translations.
Choose something else when
- You require all translations to remain active without an ongoing hosted service.
- Your translated word count is extremely high and cost is the overriding priority.
- You need full import/export on a lower-cost plan.
- Your organisation already runs a mature localisation platform and developer pipeline.
- Your policy prohibits third-party translation processing.
- You only need occasional manual translations on one WordPress website.
Managed website localisation
What is Weglot?
Weglot is a hosted website translation and localisation platform. It detects website content, creates an initial automatic translation and gives editors a dashboard for reviewing, replacing, excluding and organising translations.
It is broader than a conventional WordPress translation plugin because the same service can be used with WordPress, Shopify, Webflow, Wix, Squarespace and custom integrations. The exact technical method varies by platform: WordPress has a dedicated plugin, while other websites can use JavaScript, subdomains, subdirectories or a reverse-proxy arrangement.
The distinction matters. A JavaScript integration can be useful for testing or staging, but Weglot’s own documentation says it does not provide the same search-engine benefit because translations remain client-side. SEO-focused deployments need WordPress or a server-side URL structure.
Detect
Scan visible website content and identify strings, metadata and supported media.
Translate
Create an automatic baseline using available translation providers and AI tools.
Refine
Edit in the list or visual editor, add glossary rules and assign review work.
Publish
Serve translated versions through the chosen integration and language URLs.
Maintain
Synchronise new URLs, remove inactive strings and monitor language-specific content.
Current product direction
What is new in Weglot for 2026?
Recent changes are less about adding another flag switcher and more about AI quality, dynamic websites, WooCommerce reliability and accessibility.
Custom AI Language Model
Weglot now promotes a custom language model using OpenAI or Gemini to improve brand-aware translations. AI credits are linked to the plan’s translated-word allowance.
Weglot 2.0 compatibility
The JavaScript integration received several compatibility releases for Weglot 2.0 during 2026, alongside improvements to dynamic performance and target-language handling.
Better dynamic URL handling
Recent JavaScript releases added dynamic XHR URL translation and improved dynamic subdirectory behaviour, useful for interactive applications and changing content.
Switcher accessibility
The current JavaScript changelog includes language announcements with aria-live support and other accessibility improvements to the switcher experience.
WooCommerce checkout updates
WordPress plugin 6.1 changed how order language is stored so classic checkout and Store API or block checkout flows are covered more reliably.
Safer content detection
Current releases include fixes for long data attributes, link rewriting, media parsing and misconfigured dynamic selectors that could otherwise affect page output.
Core capabilities
The Weglot features that matter
The headline is automatic translation, but the product’s real value is the layer around it: detection, URLs, editing, exclusions, quality control and ongoing maintenance.
Broad language coverage
The WordPress listing advertises more than 110 languages, with Weglot selecting from providers including DeepL, Google and Microsoft according to language-pair availability.
Automatic and AI-assisted translation
Automatic translation creates the first version quickly. The Language Model can then apply brand context and preferred tone to supported text and metadata.
Visual Editor
Edit text on a preview of the website so reviewers can see where the translation appears rather than working from isolated strings alone.
Glossary and translation rules
Set phrases to always translate in a defined way or never translate, helping protect product names, technical terms and regulated wording.
Multilingual SEO structure
SEO-capable integrations create language URLs, hreflang and crawlable translated HTML. Metadata can be translated and URL slugs are available from Pro.
URL and content management
Scan missing URLs, synchronise translations, see strings associated with each page and exclude URLs, blocks or phrases from translation.
Media localisation
Replace images and supported media on translated versions when visual content, PDFs or campaign assets need a language-specific alternative.
Team workflow
Eligible plans allow team access and assignment. Professional translations can also be ordered through external providers from the workflow.
Translation memory
Extended and higher plans can reuse similar manual or professional translations, reducing repetitive review work across larger content estates.
Automatic does not mean publish without review
Machine translation can accelerate coverage, but legal statements, medical information, returns policies, product claims, local idioms and conversion copy need an accountable human review process. Treat automation as the first draft, not the final approval.
International organic visibility
Weglot and multilingual SEO
Weglot can build the technical foundation for multilingual search, but only when the correct integration is used. It cannot create local demand, links, culturally relevant content or keyword strategy automatically.
Dedicated language subdirectories
The WordPress integration uses language URLs and server-side output, allowing translated pages to be crawled and indexed with hreflang relationships.
SEO-ready non-WordPress setup
Server-side integrations create URLs such as fr.example.com or example.com/fr/ with translated content in the HTML source.
Useful for testing, weak for SEO
Weglot’s own SEO documentation says the client-side JavaScript option does not offer SEO benefits because the translations are not crawlable language pages.
What Weglot can automate
- Dedicated language URLs with an appropriate integration
- Reciprocal hreflang implementation
- Translation of metadata and page content
- Server-side translated HTML
- Language switcher and optional visitor redirection
- Translated slugs on Pro and above
What your SEO strategy must still do
- Validate search demand in each target market
- Localise rather than literally translate commercial copy
- Build regional authority and relevant links
- Review canonicals, sitemaps, redirects and crawlability
- Measure rankings and conversions by language and country
- Maintain translated content when the source changes
Need help with international SEO?
Translation creates inventory. Search performance comes from market selection, keyword research, technical validation, localised landing pages and authority. See our SEO services for strategy and implementation support.
Interactive planning tool
Weglot word count and plan estimator
Enter the approximate source-language word count and number of target languages. The estimator applies the current public word and language limits to identify the first plan that fits.
Translation scope
Use the original website word count, not the combined total.
source words × target languages
This is a planning estimate. Dynamic content, repeated variants, old translations and private or generated pages can change the dashboard total.
Estimated requirement
Business
Current public plans
Weglot pricing in 2026
Weglot charges standard plans in euros. Annual billing currently includes the equivalent of two months free. VAT is excluded, bank conversion fees can apply and existing customers may have grandfathered pricing.
| Plan | Annual price | Translated words | Target languages | Notable step-up feature | Best suited to |
|---|---|---|---|---|---|
| Free | €0 | 2,000 | 1 | AI translation and glossary basics | Very small brochure or test projects |
| Starter | €150 | 10,000 | 1 | Media translation and visitor redirection | Small websites entering one market |
| Business Popular | €290 | 50,000 | 3 | Access to professional translators | Growing marketing and ecommerce sites |
| Pro | €790 | 200,000 | 5 | Statistics and translated URL slugs | Content-rich international websites |
| Advanced | €2,990 | 1,000,000 | 10 | Import/export and custom languages | Large teams and complex content estates |
| Extended | €6,990 | 5,000,000 | 20 | Top-level domains and translation memory | Large-scale multinational publishing |
| Enterprise | Custom | Custom | Custom | Custom terms, DPA, SLA, SSO and reverse proxy | Governed enterprise deployments |
The Free plan still exists
Current documentation says the 14-day trial includes up to 10,000 words and one language. Projects below 2,000 translated words can then continue on the Free plan.
Word limits do not renew monthly
The allowance is the number of unique translated words stored across languages, not a monthly bucket of words that resets.
Feature gates matter as much as volume
A project may fit a lower word limit but still need Pro for translated slugs, Advanced for import/export or Extended for translation memory and top-level domains.
Check the live plan
Pricing and limits can change
Confirm the current euro price, word allowance, language limit, included team members and integration features before subscribing.
Translation quality
From automatic translation to publishable localisation
The tool can create language coverage quickly. Quality comes from the workflow applied after that first pass.
Generate a baseline
Automatic translation gives every detected string a starting point. Do not waste human review on pages that are not part of the market launch.
Protect terminology
Add product names, abbreviations, technical terms and phrases that must always or never be translated to the glossary.
Review in context
Use the Visual Editor for navigation, buttons and short interface copy where an isolated string can be misleading.
Prioritise commercial pages
Human-review the homepage, services, product pages, checkout, legal content and high-traffic landing pages before low-value archives.
Validate the experience
Test layout expansion, fonts, right-to-left display, search, forms, emails, account pages, filters, pop-ups and third-party widgets.
Maintain and measure
Synchronise new URLs, remove inactive translations and compare engagement, rankings and conversion rates by language market.
Portability is not equal across plans
Bulk translation import and export are available from Advanced. Weglot also states that cancelling or pausing makes translated versions inactive. Organisations with long-term localisation requirements should document an exit plan before publishing thousands of indexed language URLs.
Translation memory is not universal
Weglot’s current help documentation places translation memory on Extended and higher plans. Smaller teams should not assume every manual correction will operate like a full translation-memory system.
Platform and implementation
How Weglot fits different websites
The service is cross-platform, but the setup, SEO output and troubleshooting route are not identical.
WordPress and WooCommerce
Use the official plugin, API key and language settings. WordPress creates SEO-capable language subdirectories. Test checkout, emails, account pages, redirects, cache and custom dynamic content.
Shopify
Use the app and choose an SEO-capable subdomain or subdirectory configuration rather than relying on the JavaScript-only option for organic search.
Webflow, Wix and Squarespace
Installation is usually fast, but dynamic components, form messages, external widgets and platform-specific routing need practical QA.
Custom JavaScript websites
The client library is suitable for testing and can be customised, but production SEO requires the appropriate server-side integration. Dynamic selectors may be needed.
Interactive applications
Recent releases improve dynamic DOM and XHR URL handling. Complex SPAs should still be tested for route changes, state, hydration and content generated after load.
Enterprise architecture
Enterprise arrangements can add custom reverse proxy, SSO, DPA, SLA and security assessment requirements beyond the standard public plans.
Technical due diligence
Performance, dynamic content and maintenance
There is no honest universal claim such as “Weglot adds only 0.2 seconds”. The real effect depends on integration type, translated-page caching, page weight, third-party scripts and how much content changes after the initial HTML is delivered.
Test both language states
Benchmark the original URL and each translated URL separately. Check server response, LCP, CLS, INP, image delivery and cache behaviour.
Audit dynamic interfaces
Test search suggestions, product filters, validation messages, modals, cookie tools, chat widgets, account areas and checkout after switching languages.
Keep exclusions deliberate
Exclude private areas, irrelevant archives, duplicate components or content that should not consume translated words. Removing inactive strings can reduce plan usage.
Check cache and optimisation
Translation changes may be hidden by page cache, CDN cache or optimisation tools. Build a repeatable cache-clearing and release process.
WordPress dynamic content uses a different route
Weglot’s current dynamic-content guide says the dashboard selector workflow is for non-WordPress websites. WordPress cases may require PHP filters from the developer documentation, so do not assume adding a CSS selector in the dashboard will solve every plugin-generated string.
Governance and data protection
Weglot privacy and security
Weglot states that it is GDPR compliant, offers a pre-approved Data Processing Agreement and holds SOC 2 Type 2 certification. Its enterprise offer adds custom terms, DPA and SLA options.
Those supplier controls do not make the website automatically compliant. The website owner still needs to understand what content is processed, document the supplier relationship, restrict access, review subprocessors, set retention expectations and avoid sending sensitive information for translation without an appropriate legal and technical basis.
Practical governance checklist
- Sign or retain the current DPA
- Review the privacy policy and subprocessors
- Limit dashboard access by role
- Exclude private or sensitive areas
- Document translation review responsibility
- Plan backups and export where the plan allows
- Test account deletion and cancellation implications
Balanced assessment
Weglot advantages and limitations
Advantages
- Fast deployment without manually duplicating every page.
- Cross-platform approach for mixed website estates.
- Strong editing workflow with list, visual editor and glossary.
- SEO-capable integrations with language URLs and hreflang.
- Automatic new-content handling and URL synchronisation tools.
- Useful plan progression for statistics, translated URLs and enterprise controls.
- Current development around AI, dynamic behaviour and accessibility.
Limitations
- Recurring dependency because translations stop displaying after cancellation.
- Costs can rise sharply with words and target languages.
- Import/export is Advanced+, affecting migration planning.
- Translated slugs are Pro+, despite their SEO value.
- Translation memory is Extended+, not a standard feature for every customer.
- Dynamic content can need technical work, especially on WordPress.
- Human review remains essential for professional localisation.
Compare the operating model
Weglot alternatives
The right alternative is not simply the cheapest plugin. Choose between a managed translation layer, a WordPress-native system and a full localisation platform.
Best for deep WordPress control
A WordPress-specific multilingual system with CMS integration and automatic-translation credits. It can suit teams that prefer more of the workflow inside WordPress and accept a more involved setup.
Choose it when:
WordPress depth and a different ongoing cost model matter more than cross-platform simplicity.
Best for visual WordPress editing
A WordPress translation plugin centred on front-end visual editing, with annual premium plans and a free version for simpler sites.
Choose it when:
You only use WordPress and want a lower-cost, locally managed visual workflow.
Best for manual WordPress structure
A mature WordPress option that creates language-specific content and can connect to external machine-translation services.
Choose it when:
You want direct control over language content and are comfortable managing more of the localisation process.
Best for product localisation teams
A localisation management platform designed for developers, product managers, designers and translators working across software, content and release pipelines.
Choose it when:
Your need is broader than translating a public website and includes product strings, design files, repositories and structured workflows.
| Option | Platform scope | Setup style | Main strength | Main compromise |
|---|---|---|---|---|
| Weglot | Cross-platform | Hosted managed layer | Speed and centralised workflow | Recurring word/language pricing and service dependency |
| WPML | WordPress | WordPress-native suite | Deep CMS and ecommerce integration | More configuration and WordPress-only |
| TranslatePress | WordPress | Front-end visual editing | Accessible visual workflow | Less suitable for mixed platform estates |
| Polylang | WordPress | Language-specific content management | Local control and flexibility | More manual architecture and maintenance |
| Lokalise | Web, apps and product content | Localisation management platform | Developer and product workflow | More platform than a simple site may need |
Recommended launch sequence
How to implement Weglot properly
Installation can be quick. A dependable multilingual launch still needs discovery, staging, translation governance and post-launch monitoring.
Estimate the scope
Count source words, target languages, dynamic content and projected growth before selecting the plan.
Choose the SEO architecture
Use WordPress or a server-side subdirectory/subdomain setup for indexable language versions.
Install on staging
Connect the project, add languages, style the switcher and confirm that cache and optimisation tools behave correctly.
Exclude unnecessary content
Remove private areas, irrelevant archives, duplicated widgets and content that should remain in the original language.
Create the glossary
Define brand terms, product names, acronyms, legal phrases and words that must never be translated.
Review priority journeys
Check navigation, forms, products, checkout, account areas, emails, legal pages and conversion-focused landing pages.
Validate SEO and analytics
Crawl every language, inspect hreflang, metadata, canonicals, sitemaps, redirects and language-specific measurement.
Build ongoing ownership
Assign translation approvals, synchronise new URLs, remove inactive strings and review plan usage regularly.
Final fit check
Who should use Weglot?
Weglot is not universally the cheapest route, but it is often one of the fastest routes from one language to a maintainable multilingual website.
Marketing-led businesses
Teams that need to launch new markets quickly and let content editors manage translations without a developer for every change.
Ecommerce stores
Stores that need translated catalogues, navigation and checkout journeys across WordPress, Shopify or other supported platforms.
Agencies with mixed platforms
Agencies that want one translation workflow across several client technologies rather than a different plugin for each CMS.
Growing international sites
Businesses prepared to invest in market research, human review and SEO after the automatic translation creates initial coverage.
Our final recommendation
Weglot is excellent at removing friction
Choose it for speed, workflow and cross-platform consistency. Calculate the translated words, confirm the SEO integration and budget for human review before committing the website to a growing subscription.
Start the Weglot trial
Affiliate link — no additional cost to you
Weglot questions answered
Frequently asked questions
Current answers on pricing, word limits, SEO, translation quality, dynamic content, GDPR and cancellation.
Is Weglot free?
Weglot currently offers a 14-day trial. After the trial, a Free plan can remain active for a project with no more than 2,000 translated words and one translated language. Larger projects need a paid plan.
How does Weglot count translated words?
Weglot counts the words stored in the Translation List across every translated language. A 10,000-word source site translated into three target languages therefore needs roughly 30,000 translated words, before allowing for dynamic, repeated or previously generated content.
Is Weglot good for multilingual SEO?
It can be. WordPress and Weglot’s server-side subdirectory or subdomain integrations create dedicated language URLs, add hreflang and place translated content in crawlable HTML. A JavaScript-only integration keeps translations client-side and does not provide the same SEO benefit.
Does Weglot translate meta titles and descriptions?
Yes. With an SEO-capable integration, Weglot detects and translates SEO-relevant content including metadata. Translated URL slugs are available on Pro and higher plans and need to be generated or edited in the dashboard.
Does Weglot automatically translate new content?
Weglot can detect and generate translations as new pages are visited in a translated language, and URLs can also be synchronised from the dashboard. Automatic content translation can be disabled when a review-first workflow is required.
Can I edit Weglot translations manually?
Yes. Translations can be edited in the Translation List or Visual Editor, controlled with glossary rules, refined with Weglot’s AI Language Model, assigned to team members on eligible plans, or ordered from professional translators.
Which machine translation providers does Weglot use?
Weglot uses translation providers including DeepL, Google Translate and Microsoft Translator, selecting an available provider for the relevant language pair. Professional publishing still needs human review for terminology, legal wording, brand voice and conversion copy.
Does Weglot work with WooCommerce?
Yes. The WordPress integration supports WooCommerce, and recent plugin updates improved order-language persistence for classic and block-based checkout flows. Complex payment, account and dynamic components should still be tested on staging.
Can Weglot translate dynamic content?
Yes, but the method depends on the platform. Non-WordPress integrations can add dynamic CSS selectors in the Weglot dashboard. Weglot’s current documentation says WordPress dynamic-content cases may require PHP filters rather than the dashboard selector workflow.
Can I export my translations?
Import and export are available on Advanced and higher plans. Lower plans can edit translations in the dashboard but do not include the same bulk migration workflow, so exit planning should be considered before choosing a plan.
What happens if I cancel Weglot?
Weglot states that translated versions stop being active after cancellation or a pause, and translated pages can progressively disappear from search results. A project can also be deleted after a period of inactivity under its terms.
Is Weglot GDPR compliant?
Weglot states that it is GDPR compliant, provides a Data Processing Agreement and holds SOC 2 Type 2 certification. Website owners must still complete their own privacy assessment, document suppliers and configure consent, retention and access correctly.
Does Weglot slow down a website?
The impact depends on the integration, page complexity, caching and dynamic-content rules. Test the original and translated URLs separately with real-user and lab data rather than relying on a universal speed claim.
What are the best Weglot alternatives?
WPML, TranslatePress and Polylang are common WordPress-focused alternatives when greater local control or a different pricing model matters. Lokalise and similar localisation platforms are aimed more at structured product, design and development workflows. The best choice depends on platform, content volume, languages and internal resources.
Is Weglot worth the price?
Weglot is strongest when speed of deployment, cross-platform compatibility and a managed translation workflow are worth more than the lowest possible software cost. It becomes less attractive when a large word count, many languages or long-term subscription dependency outweigh the operational savings.
Research methodology
How this review was researched
This update removes unsupported performance, accuracy and traffic claims from the previous article. The product facts, limits and cautions were checked against current official pricing, support documentation, integration changelogs and the WordPress plugin listing.
Multilingual SEOURLs, hreflang and server-side output
JavaScript changelogCurrent integration improvements
WordPress pluginVersion, compatibility and release notes
Performance guideIntegration-specific behaviour
Security and privacySOC 2, DPA and governance information
