# How to Translate a WordPress Website for Free

> Learn how to translate a WordPress website for free, compare manual and automatic options, and understand the limits for SEO and WooCommerce.

- URL: https://www.lingowp.com/blog/translate-wordpress-website-free/
- Author: Amine Sayagh
- Category: Guide
- Published: 2026-10-11
- Language: en

Yes, you can translate a WordPress website for free, but the best method depends on what “translated” means for your business.

A small bilingual brochure website can often be translated manually with a free multilingual plugin. A WooCommerce store, however, needs more than translated paragraphs: products, categories, checkout messages, menus, URLs, and SEO information may all require attention.

Some free tools create proper language versions you manage inside WordPress. Others simply replace the visible text in the visitor's browser without creating indexable translated pages.

This guide, published by LingoWP, explains the differences so you can choose a free workflow without discovering critical limitations halfway through the project.

## Can you really translate WordPress for free?

A free implementation is realistic when:

- You need one additional language.
- The website contains a manageable number of pages.
- You can translate or review the content yourself.
- You do not need an agency workflow.
- Your theme and essential plugins work with the chosen solution.
- You are willing to perform some configuration and testing.

“Free” usually refers to the plugin or translation software. It does not eliminate the time required to translate, review, update, and test the site.

Automatic translation may also involve an external API, word allowance, usage quota, or paid upgrade once the site grows.

## Four common free approaches

| Approach | Best for | Main limitation |
|---|---|---|
| Manual multilingual plugin | Small sites where you can write the translations | Requires translation and maintenance time |
| Visual translation plugin | Bilingual sites and users who prefer editing the rendered page | Free edition may limit additional languages or automation |
| Browser-based machine translation | Quickly helping visitors understand the page | Translations may not have indexable URLs or editorial control |
| Limited hosted free plan | Very small websites needing automatic translation | Word and language limits |

These options solve different problems. A free language widget is not necessarily a free multilingual SEO system.

## Option 1: Create the translations manually

Manual translation is usually the most sustainable free method for a small website.

A multilingual plugin can provide the language structure, while you create or enter each translation yourself. This avoids machine-translation charges and gives you control over business terminology, calls to action, and product information.

Polylang's free WordPress plugin supports multilingual content with multiple languages, but its official plugin page states that WooCommerce compatibility requires the separate premium Polylang for WooCommerce add-on.

This approach is a reasonable fit for:

- A service website with five to twenty pages
- A portfolio
- A local business serving two language communities
- A blog with only selected articles translated
- A project where translation quality matters more than speed

The tradeoff is time. Every translated page must be created, reviewed, connected to its source version, and updated when the original changes.

## Option 2: Use a free visual translation plugin

A visual translation interface lets you open the front end of the website, select visible text, and enter its translation.

TranslatePress currently offers a free edition that supports two languages in total: the original language and one translation language. Its WordPress.org page says the plugin can translate page output, forms, shortcodes, page-builder content, and WooCommerce content through a front-end editor.

Its current listing also describes a free allowance of 2,000 AI-translated words. The free plugin can integrate with the Google Translate API using your own API key, but external API access is separate and may have its own costs or conditions.

This option is attractive when:

- You want one additional language.
- You prefer working directly on the rendered page.
- Your website uses a page builder.
- You need to see translations in context.
- You operate a relatively small WooCommerce store.

Before committing, test dynamic elements such as forms, popups, variation selectors, checkout notices, and account pages.

## Option 3: Add instant automatic translation

Some free plugins use machine translation in the visitor's browser. This can make a website readable in many languages with very little setup.

GTranslate's free version provides a language selector and automatic translation, but its official site says the translated pages do not receive separate URLs and the translations are not stored. It therefore describes the free version as lacking the SEO benefits of its paid, URL-based versions.

This type of solution can be useful when:

- Immediate visitor comprehension is the priority.
- You do not need translated pages to rank independently.
- You do not need to edit every machine translation.
- The website is informational rather than transaction-critical.
- You understand that visitors and search engines may experience the translations differently.

It is less suitable when translated landing pages are expected to attract organic traffic or when inaccurate wording could affect a purchase, contract, safety instruction, or support request.

## Option 4: Use a permanently free plan with limits

Some hosted translation services offer a free tier for very small websites.

As checked on October 9, 2026, Weglot's official pricing page listed a free plan for up to 2,000 translated words and one translated language. Its documentation said sites exceeding that word limit must reduce their translated content or upgrade for translations to continue displaying.

This can work for:

- A one-page website
- A small event site
- A temporary campaign
- A product microsite
- Testing a translation workflow before investing

Count your words before selecting this route. A website that appears small can exceed 2,000 words once headers, footers, forms, policies, products, and repeated interface strings are included.

## Which free option should you choose?

### For a small business website

Use a free manual or visual translation plugin if you only need one additional language and can review the translation yourself.

Prioritize these capabilities:

- Translated pages with stable URLs
- A visible language switcher
- Translated navigation
- Control over page titles and descriptions
- A clear way to update translations later

### For a blog

Decide whether every article needs translation. Translating only your most valuable evergreen posts can keep the project manageable.

The language switcher should not promise a translated article when only the homepage exists in that language. Test how the selected plugin handles missing translations.

### For a WooCommerce store

Be more cautious. Check whether the free solution covers:

- Products and variations
- Categories and attributes
- Cart and checkout
- Account pages
- Payment and shipping labels
- Store emails
- SEO metadata
- Inventory and product synchronization

Do not assume that general WordPress multilingual support automatically includes complete WooCommerce compatibility. Polylang, for example, explicitly requires its premium WooCommerce add-on, while TranslatePress currently describes WooCommerce compatibility in its free WordPress.org listing.

These are product claims from their respective official sources. Test your exact theme, extensions, checkout configuration, and payment methods on a staging site.

## Step-by-step free workflow

### 1. Back up the website

Create a full backup before installing a multilingual plugin. If possible, test on a staging copy first.

Avoid activating multiple multilingual plugins together. They may use incompatible methods to store languages, rewrite URLs, or select the active locale.

### 2. List everything that needs translation

Do not count only the visible page paragraphs. Include:

- Header and footer
- Navigation menus
- Forms and validation messages
- Buttons and calls to action
- Cookie notices
- SEO titles and descriptions
- Image alt text
- Error pages
- Legal pages
- Emails

For WooCommerce, add products, attributes, checkout messages, payment instructions, shipping information, and transactional emails.

### 3. Choose the target language carefully

Start with the language most valuable to your current customers. One complete, maintained translation is usually better than several incomplete ones.

Choose whether you need:

- A language only, such as French
- A regional variant, such as French for Belgium
- Different commercial content for different markets

Translation and regional adaptation are not always the same project.

### 4. Install one multilingual solution

Select the plugin that matches your editing preference and website type. After activation:

1. Confirm the original language.
2. Add the translation language.
3. Configure the URL format.
4. Add the language switcher.
5. Translate one test page.
6. Verify the result before translating the rest of the site.

Do not translate the entire site until the test page, menu, mobile header, and URLs behave correctly.

### 5. Translate the essential pages first

Start with the pages closest to conversion:

1. Homepage
2. Main service or product pages
3. Contact page
4. About page
5. Pricing or delivery information
6. Legal and policy pages
7. Checkout-related content

Review headings, buttons, forms, and navigation in context. A technically correct translation can still be too long for its design or unsuitable for the customer's expectations.

### 6. Add and test the language switcher

Place the switcher somewhere visitors can find consistently, usually in the main navigation or mobile menu.

Test it from:

- The homepage
- An internal page
- A translated post
- A page without a translation
- A product page
- The cart and checkout
- A mobile device

The switcher should take the visitor to the equivalent translated page whenever one exists, rather than returning them to the homepage without explanation.

### 7. Check multilingual SEO

If organic search matters, confirm that each language version has its own crawlable URL.

Google recommends separate URLs for different language versions, along with `hreflang` annotations that connect corresponding pages. It also recommends visible links that allow users to choose another language.

Check whether your free setup supports:

- Separate URLs
- Correct canonical URLs
- Reciprocal `hreflang`
- Translated SEO titles and descriptions
- Multilingual sitemap entries
- Links between equivalent pages

A browser-only translation widget may help visitors but does not necessarily create pages that search engines can index.

### 8. Review the translation manually

Machine translation can be a useful starting point, but review at least:

- Homepage messaging
- Product names
- Prices and units
- Delivery conditions
- Returns information
- Legal statements
- Forms and validation errors
- Checkout buttons
- Payment instructions

Pay particular attention to text that affects a customer's decision or creates an obligation.

## What may prevent the project from remaining free?

A free setup can become insufficient when you need:

- More languages
- Automatic translation beyond a free allowance
- Full WooCommerce integration
- Translated URL slugs
- Advanced multilingual SEO
- Translation-team permissions
- Professional support
- Translation memory or terminology management
- Large-scale import and export
- Automatic synchronization after content changes

There is nothing wrong with starting free. The important part is choosing a structure that will not force you to rebuild every translation if the site later needs a paid workflow.

## Frequently asked questions

### Can WordPress translate a website automatically for free?

WordPress itself does not automatically translate complete website content. A plugin or external translation service is required. Some plugins provide limited free automation, while others support free manual translation.

### Can I translate a WordPress site without a plugin?

Yes, but you would need to create and maintain the language routing, content versions, navigation, switcher, and SEO signals yourself. That is rarely the simplest option for a small business owner.

### Is Google Translate enough for a multilingual website?

It may be enough when visitors only need an approximate on-screen translation. It is usually insufficient when you need editable translations, dedicated language URLs, controlled terminology, or multilingual SEO.

### Can I translate WooCommerce for free?

A small bilingual store may be possible with a free tool that supports WooCommerce, but coverage varies. Test products, variations, categories, cart, checkout, account pages, emails, payment methods, and shipping extensions before relying on it.

### Will a free translation plugin improve international SEO?

Only if it creates accessible language-specific pages and supports the necessary SEO structure. A language selector alone does not guarantee that translated content can be indexed.

## Conclusion

The most reliable way to translate a small WordPress website for free is to use one multilingual plugin, begin with one additional language, translate the essential pages manually, and test the switcher and URLs carefully.

Free automatic widgets are faster, but their translated output may not be stored, editable, or indexable. Limited free plans can work for very small sites but require close attention to word and language limits.

For a WooCommerce store, examine the full customer journey before choosing. The plugin may be free, but incomplete checkout, product, or SEO translation can be more costly than the subscription you avoided.

## Related guides

- [How to translate a WordPress site without a plugin](/blog/translate-wordpress-site-without-plugin/)
- [Add a language switcher to your WordPress menu](/blog/add-language-switcher-wordpress-menu/)
- [Does Loco Translate include a language switcher?](/blog/loco-translate-language-switcher/)

## Sources

*Checked on October 9, 2026.*

- [WordPress.org: Polylang plugin page](https://wordpress.org/plugins/polylang/)
- [WordPress.org: TranslatePress plugin page](https://wordpress.org/plugins/translatepress-multilingual/)
- [TranslatePress: Automatic translation documentation](https://translatepress.com/docs/automatic-translation/)
- [WordPress.org: GTranslate plugin page](https://wordpress.org/plugins/gtranslate/)
- [GTranslate: Free and paid version differences](https://gtranslate.io/)
- [Weglot: Pricing and free-plan limits](https://www.weglot.com/pricing)
- [Google Search Central: Managing multilingual sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)