How to Translate a Website for Free?

Three legitimate free options exist for translating a website: DeepL Free (500,000 characters/month, manual paste), Google Translate Web (unlimited, manual export), and free-tier multilingual plugins like Polylang Free or Loco Translate. Only one of these — DeepL Free with manual native review and proper hreflang — produces a site that ranks. The other two destroy your SEO within 90 days through duplicate content, missing language tags, or machine-output indexing failures. For DTC brands targeting Amazon FBA EU, "free" usually costs more than a managed migration once the conversion losses are tallied.

---

The short answer: one option ranks, two destroy SEO

There are three legitimately free routes to translate a website. DeepL Free with manual review is the only one that produces SEO-ready output. Google Translate widgets and free-tier plugins ship duplicate content or unreviewed machine output that Google penalises within 30-90 days.

Here is the ranked benchmark of free options for a 25-page ecommerce site:

• DeepL Free + manual review + WordPress (Polylang or WPML free): 500,000 characters/month free quota, native-quality output, proper hreflang via plugin. Ranks well. Cost: 40-80 hours of manual work per language.
• Google Translate Web + manual export + native review: Unlimited free quota, weaker base translation than DeepL (especially for German and Italian), proper hreflang requires manual implementation. Ranks if reviewed natively. Cost: 50-100 hours per language plus heavier review burden.
• Google Translate widget (the iframe button): Zero work, immediate deployment, ships unindexable JavaScript-rendered content with no hreflang. Destroys SEO. Never use on production.
• Free machine-translation plugins (Translatepress free, GTranslate free): Auto-translate without review, no glossary, ship duplicate content flags. Destroys SEO. Avoid.

Only the first two routes are viable. The widgets and free-tier auto-translate plugins fail Google's Quality Rater thresholds.

Route 1: DeepL Free with manual review

DeepL Free gives you 500,000 characters per month of translation API access. For a 25-page DTC site averaging 200 words per page that is enough to translate the entire site twice over. The output is the strongest machine baseline available, particularly for German and Italian.

The workflow is straightforward. You export your site copy into a flat document, paste sections into DeepL Free in 5,000-character batches, and copy the output back into your CMS. The free tier limits at 500,000 characters/month and resets monthly — enough for a typical multilingual launch in batches across two months. DeepL outperforms Google Translate by 15-25% on European language benchmarks, with output requiring meaningfully less editing per page. The catch: DeepL Free has no API access (paid tier only), no glossary management, and no formality control. You also need a native speaker to review the output — not optional. Plan 30-45 minutes of native review per 1,000 words. See our DeepL vs ChatGPT comparison for engine benchmarks.

Route 2: Google Translate Web with manual export

Google Translate's web interface is unlimited and free. You paste source text, copy the translated output, and manually integrate. The base translation is weaker than DeepL — particularly on German compound nouns and Italian formal register — but it costs nothing.

The workflow mirrors DeepL but with weaker output. Google Translate accepts up to 5,000 characters per submission with no monthly cap. You batch your copy through the interface, paste output back into your CMS, then run native review. Reviewers report Google output requiring 20-40% more editing time than DeepL on the same source text — what you save in API quota you pay in editor hours. For Spanish and Portuguese the gap closes; for German, Italian, and Polish, DeepL is stronger. Google Translate Web does NOT render hreflang tags, generate sitemaps, or handle URL structure — all technical SEO infrastructure is on you. The widget version is a separate tool with separate problems, covered in our Google Translate website risks analysis.

Route 3: free-tier WordPress multilingual plugins

WordPress has two genuinely free multilingual plugins worth considering: Polylang Free and Loco Translate. Both let you create translated post and page versions with proper hreflang, multi-locale sitemap, and language switcher widgets. Auto-translation is NOT included on the free tier.

Polylang Free handles unlimited languages, generates correct reciprocal hreflang on translated pages, and integrates with most WordPress themes. The free tier does NOT include WooCommerce product translation (paid Polylang Pro at €99/year required) or automatic post translation. Loco Translate handles theme and plugin string translation with no language limit. The combination of Polylang Free for posts/pages, Loco Translate for theme strings, and DeepL Free for the actual translation work covers the full free stack. Total time investment for a 25-page site across 2 languages: 60-90 hours. This is the only "free" path that produces an SEO-clean multilingual deployment. Read our WPML vs Polylang comparison for the plugin matrix.

What the Google Translate widget actually does to your SEO

The Google Translate widget — the JavaScript "translate this page" button — renders translations client-side via iframe injection. Google's crawler indexes the source HTML, not the rendered translation. Your translated content never enters the index. SEO contribution: zero. Conversion uplift in the UK English market: marginal.

This is the most common "free translation" mistake in DTC. The widget feels like it works because users see translated text in their browser. Google's crawler does not see translated text — it sees the original English HTML with a JavaScript hook. None of your German, French, or Italian content enters the search index. You get zero organic traffic from non-English markets and zero brand visibility on Google.de, Google.fr, or Google.it. Search Engine Land has documented case studies of brands losing 60-80% of potential international traffic relying on the widget. The full mechanism lives in our Google Translate website risks deep-dive. Never deploy the widget on a production ecommerce site.

How Eldris Website handles "free vs managed"

We benchmark every prospect's options openly. For brands with engineering capacity and time, the DeepL Free + Polylang stack is genuinely viable. For brands wanting to launch in 10 days with zero translation management, our managed pipeline pays back faster.

Our managed migration costs £997 activation plus £149/month at the Growth tier, with the 4-language bundle adding 15% activation discount. This covers full-site translation across DE/FR/IT/ES with native human review, hreflang on day one, multi-locale sitemap submitted to Search Console, and 10-working-day delivery. The honest comparison: the DeepL Free route saves £4,500 in year-one software but costs 60-90 hours per language of internal time. At £40/hour across 4 languages, that's £9,600-14,400 in opportunity cost. For most founders the managed route is genuinely cheaper. For Amazon FBA EU sellers we coordinate with EU EPR registration. Book a comparison call and we'll quote both routes.

Frequently asked questions

Is DeepL really free?

DeepL Free is genuinely free up to 500,000 characters/month of translation. Beyond that quota you pay for DeepL Pro starting at €8.74/month. The free tier is enough for a 25-page site with 200 words/page translated twice per month, covering most multilingual launches. What the free tier does NOT include: API access (Pro only), glossary management, formality control, or document upload beyond basic types. For manual paste-and-edit workflows, DeepL Free outperforms Google Translate on most European language pairs.

Will Google penalise me for using free translations?

It depends on what "free" means. DeepL Free output that has been native-reviewed and properly tagged with hreflang is indistinguishable from paid translation as far as Google is concerned — no penalty applies. Auto-translated machine output without review, deployed at scale, hits Google's Quality Rater thresholds and gets de-indexed within 30-90 days. The penalty mechanism is documented in our machine translation SEO penalty guide. The variable is review, not the engine.

What's the cheapest way to translate a Shopify store?

Shopify Translate & Adapt is free for 2 languages with auto-translation. Beyond 2 languages costs roughly £8/month per language. For an Amazon FBA EU launch covering DE/FR/IT/ES, the total app cost lands at £24-32/month. The catch is that you still need native review of the auto-translated output if you want it to rank, which adds 30-45 hours per language. See our translate Shopify store guide for the workflow.

Can ChatGPT translate a website for free?

ChatGPT Free can translate text but is not a website translation tool. There is no batch processing, no hreflang generation, no CMS integration, and no glossary management. The free tier has rate limits that make a 25-page translation slow. ChatGPT translations can be high quality on European languages with prompt engineering, but you still need a workflow tool for integration. Read our DeepL vs ChatGPT translation comparison for benchmarks.

How long does free website translation actually take?

For a 25-page DTC site translated into 1 additional language using DeepL Free plus Polylang Free with native review: 40-80 hours of total work. That breaks down as 8 hours of content extraction, 4 hours of DeepL batching, 20-40 hours of native review, 6 hours of CMS integration, and 4-8 hours of QA. For 4 languages (DE/FR/IT/ES) plan 200-300 hours total. At £40/hour internal labour, that is £8,000-12,000 in opportunity cost — roughly equivalent to a managed migration at our Growth tier with zero internal effort.