Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For a modest bilingual site, start with one WordPress installation, one multilingual plugin, and a separate linked post or page for each language. Choose a consistent URL format—often language directories such as /es/—then test translations, switching, and compatibility on a staging copy before changing the live site. WordPress does not include bilingual publishing out of the box, so a plugin or a separate-site setup is needed to connect translations and let visitors switch languages.
Choose how the two languages will be organized
The simplest starting point for many small publishers and businesses is one WordPress site where each translation is a separate post or page linked to its counterpart. Editors work with familiar WordPress content, while the multilingual plugin manages language assignments and relationships.
There are other models, but they solve different problems. WordPress describes the choice as dependent on content strategy, data model, content volume, and the visitor experience you want. Its handbook’s example of 100,000 products translated into five languages producing 500,000 records illustrates how records can multiply at catalog scale; it is not a performance measurement or an expected outcome for a small bilingual site. WordPress multilingual architecture documentation
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Model | How it works | Main trade-off | Useful question |
|---|---|---|---|
| One linked post per language | Each language has its own post or page, with translations linked in a group. | Content records grow as translations are added; language-specific filtering can be more complex. | Can editors manage each translation as a normal WordPress post? |
| All languages in one post | Language versions are stored together in a single post. | Record counts stay lower, but content can be more tightly coupled; cleanup after removing a multilingual plugin can be harder, and permalinks may not translate cleanly. | Is side-by-side language editing worth those trade-offs? |
| Separate site per language | Each language runs on its own WordPress site. | Editors gain separation, but site administration is duplicated. | Does each language need enough editorial or operational independence to justify another site? |
For a small site with manageable translation volume, linked posts are usually the most straightforward arrangement to maintain. Consider another model only when its editorial or operational benefits matter more than the additional complexity.
#1 Best Overall
Select one plugin and check compatibility before launch
Use one multilingual plugin to create language assignments, connect translations, and provide a switcher. Avoid running multiple multilingual plugins together: they may use different data models, and the Polylang listing warns against keeping other multilingual plugins active when activating it.
Polylang for a manual-translation workflow
Polylang is one option for a site where a person supplies or reviews translations. Its WordPress.org listing describes language assignment, linked translations, support for posts and taxonomy content, and language-switcher blocks for content or navigation. The listing currently says it requires WordPress 6.5 or later and PHP 7.4 or later; check the live listing at installation because requirements can change. Polylang’s WordPress.org listing
WPML when its documented workflow fits
WPML is another option if its language settings, URL controls, switcher placements, workflow, or compatibility suit your site. Its setup documentation describes 65 preconfigured languages or the option to define a custom language, and switchers placed in areas including menus, footers, widgets, and content. That is vendor documentation, not an independent performance comparison. WPML language setup documentation
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTest on a staging copy
- Back up the database. Do this before changing multilingual plugins or the site’s language configuration.
- Make a staging or test copy. Install and configure the proposed plugin there first, rather than discovering theme conflicts on the live site.
- Check the theme and existing plugins. Test translated posts, navigation, custom fields, and any other site-specific features you rely on.
- Commit to one plugin only after the checks pass. If changing from another multilingual plugin, follow its migration or cleanup guidance rather than leaving both active.
WordPress’s handbook specifically recommends backing up the database and checking compatibility before adopting a multilingual setup. WordPress multilingual architecture documentation
Choose a consistent language URL format
Language can be represented in the URL as a query parameter, a directory, or a separate domain or subdomain. For example, a directory structure can use a path such as /es/. For a single-site bilingual project, directories are a practical default when the selected plugin supports them; they are not a guarantee of higher search rankings. Choose a format the plugin supports and apply it consistently. WordPress multilingual architecture documentation
After setup, inspect the URLs for every translated page and confirm the plugin connects each version to the correct counterpart. WPML also documents URL-format and multilingual SEO settings; those settings help configure the site but do not, by themselves, establish a search-ranking benefit. WPML language setup documentation
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Make the language switcher easy to find and test
Place a switcher in a predictable location, such as the primary navigation, and label choices with language names rather than relying on flags alone. Polylang lists switcher blocks for navigation or content; WPML documents placements including menus, footers, widgets, and inline content. Polylang’s WordPress.org listing · WPML language setup documentation
- Open pages that have a translation and verify switching leads to the corresponding page, not just the other language’s home page.
- Check a page that has no translation and make sure the resulting behavior is understandable to visitors.
- Test the switcher in mobile navigation as well as desktop navigation.
- Try it on pages with query parameters, such as search or filtered views, if your site uses them.
Keep the site lean without guessing at speed
A small plugin count is a useful maintenance goal, but it does not prove that a site is fast. The effect of a multilingual setup depends on its data model, translation volume, theme, hosting, caching, and other plugins. The available documentation does not establish that one multilingual plugin is universally fastest or provide an equivalent-site speed benchmark. Measure your own site before and after adding translations rather than relying on a blanket plugin-speed claim. WordPress multilingual architecture documentation
Persistent object caching is a possible hosting-level optimization, not a required addition for every bilingual site. WPML’s documentation describes using Redis when the hosting provider enables it and explains that persistent cache data can be reused between page loads. Check what your host already provides before adding another caching plugin. WPML documentation on Redis caching
Quick Recap
A practical setup checklist
- Decide who supplies and reviews each translation, and whether linked posts meet that workflow.
- Choose one multilingual plugin whose supported languages, URL options, and editing workflow suit the site.
- Back up the database and test the plugin with the active theme and other plugins on a staging copy.
- Set one URL convention and verify the language relationship for each translated page.
- Add a clearly labeled switcher and test translated, untranslated, mobile, and query-string cases.
- Check actual site performance after translations are in place; investigate the host’s existing caching support before adding more software.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
