For a modest bilingual site, the simplest maintainable setup is usually one WordPress installation, one multilingual plugin, and a clear URL convention such as /es/ for Spanish pages. WordPress does not handle linked translations and language switching out of the box, so a multilingual plugin or a separate-site architecture is needed. Choose the content model first, test the plugin with your theme and existing plugins on a staging copy, and only then switch the live site.
Choose how translations will be organized
The right structure depends on how editors work, how much content you have, and whether each language needs to operate independently. WordPress’s multilingual handbook describes three common approaches; for most small sites, linked posts in one installation are the practical starting point.
As an Amazon Associate I earn from qualifying purchases.
| Structure | How it works | Main trade-off | Useful when |
|---|---|---|---|
| One post per language, linked together | Each translation is a regular WordPress post or page connected to its counterparts. | Content records grow with translations, and filtering content by language can be more involved. | Editors want to work with familiar WordPress posts and pages. |
| Multiple languages in one post | Language variants are stored together within a single post. | It can be harder to clean up when removing the multilingual system, and permalinks may not be translatable. | Side-by-side language editing is important enough to accept tighter coupling. |
| A separate site for each language | Each language has its own WordPress site. | Editors and administrators must manage multiple sites. | Languages need substantial editorial or operational independence. |
The WordPress handbook illustrates how linked-post models can increase records at scale: 100,000 products translated into five languages would yield 500,000 records. That is an example of database growth, not a small-site performance benchmark or a prediction that a bilingual blog will run slowly. The handbook’s framework is to choose according to content strategy, data model, content volume, and visitor experience. Read the WordPress multilingual handbook.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Select one multilingual plugin and test compatibility
For manual translations on a small site, Polylang is one documented option: its WordPress.org listing describes language assignment, linked translations, support for posts and taxonomy content, and switcher blocks for navigation or content. The listing states WordPress 6.5 or later and PHP 7.4 or later; check the live listing before installation because requirements can change. See Polylang’s WordPress.org listing.
WPML is another option if its language and URL controls, switcher placements, or documented workflow fit your needs. Its setup documentation describes 65 preconfigured languages or the option to define a custom language, and switchers in locations such as menus, footers, widgets, and content. These are vendor-documented capabilities, not independent evidence that it is faster or better for every site. See WPML’s language setup documentation.
Do not run two multilingual plugins at once. They can use different data models, and Polylang’s listing warns against leaving other multilingual plugins active when activating it. Before changing the live site, make a database backup and test the selected plugin with your theme and other plugins on a staging or test copy. WordPress’s handbook specifically recommends compatibility checks and a database backup.
Set a consistent language URL format
WordPress documents three common ways to represent a language in a URL:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Query parameter: for example,
?lang=es. - Subdirectory: for example,
/es/. - Separate domain or subdomain: a distinct web address for each language.
For a single-site bilingual project, subdirectories are an approachable default if the chosen plugin supports them. This is a practical configuration choice, not a guarantee of better search rankings. Pick one format, configure it in the plugin, and check that every translated page uses it consistently and is linked to the correct counterpart. WPML documents URL formats and multilingual SEO settings, but the format alone does not establish a search-performance benefit. WordPress URL structure guidance and WPML’s URL setup details.
Add a language switcher visitors can understand
Place the switcher somewhere predictable, such as the primary navigation or footer. Polylang provides switcher blocks for navigation and content; WPML documents placements including menus, widgets, footers, and inline content. Prefer clearly written language names over flags alone, since a flag may not identify a language accurately for every reader.
Check the switcher on translated and untranslated pages, in mobile navigation, and on pages with query parameters. When a translation exists, confirm that the switcher opens that corresponding page; when none exists, confirm that the resulting behavior is sensible for your site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep the plugin footprint—and performance claims—grounded
A multilingual plugin is a necessary part of this setup, not a reason to install a stack of language add-ons by default. Start with the features the site actually needs: linked translations, language URLs, and a visible switcher. Add another plugin only for a separate requirement that the multilingual tool or your current setup does not cover.
There is no equivalent-site speed benchmark in the cited documentation establishing that one multilingual plugin is always fastest. Actual performance depends on the site’s content volume, theme, hosting, other plugins, and caching. Test the finished site under its real conditions rather than assuming the translation model will cause—or solve—a speed problem.
Best Value
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
Persistent object caching is also conditional, not a mandatory extra plugin. WPML’s Redis documentation says persistent cache data can be reused between page loads, but Redis must be enabled by the hosting provider. Check what your host already supports before adding a caching component. Read WPML’s Redis caching documentation.
Quick Recap
Set it up safely
- Choose the editorial model. For a typical small bilingual site, plan one linked post or page per language in one WordPress installation.
- Back up and stage. Create a database backup and use a staging or test copy for the plugin and theme compatibility check.
- Install one multilingual plugin. Verify its current WordPress and PHP requirements and deactivate any conflicting multilingual plugin as directed by its documentation.
- Configure languages and URLs. Select the two languages and the supported URL format you intend to keep.
- Link translations and add the switcher. Translate representative pages and place the switcher in a consistent location.
- Test real visitor paths. Check page relationships, untranslated pages, mobile navigation, and relevant query parameters. Fix issues on staging before applying the setup to the live site.
- Review site behavior after launch. Check the actual pages and hosting environment before considering any additional performance tooling.
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.
