To run a multilingual WordPress affiliate site, pick one of three architectures (a translation plugin on a single install, WordPress Multisite with one site per language, or separate installs) and then lock down a translation workflow that keeps affiliate links, sub-IDs and hreflang correct in every language. For most affiliate publishers adding two to five languages, a single install with a plugin that stores each translation as its own post, such as WPML or Polylang, is the practical default.
The plugin choice gets the attention, but the workflow does the damage. Broken or untracked affiliate links on translated pages, missing hreflang and stale translations are the usual problems. This guide compares the main approaches and sets out a workflow that keeps tracking intact per language.
Multilingual WordPress affiliate site setups compared
| Approach | How it works | Strengths | Weaknesses |
|---|---|---|---|
| Plugin storing translations as posts (WPML, Polylang) | Each translation is a separate post or page linked to the original | Full control per language, including different affiliate links and content; works with SEO plugins | More content to manage; plugin adds complexity and database load |
| Plugin translating rendered output (TranslatePress) | Translates the page as displayed, string by string, in a visual editor | Fast to set up; easy visual editing | Less natural for pages that need different structure or offers per language |
| Hosted translation service (Weglot) | Translations are stored and served through the provider's platform | Very quick start; machine translation built in | Ongoing subscription; translations depend on the service; less control over per-language content |
| WordPress Multisite | One network, one site per language, connected by a plugin such as MultilingualPress or by custom code | Clean separation; each language can have its own plugins, theme settings and editors | More complex to maintain; some plugins do not support Multisite well |
| Separate installs | A completely separate WordPress site per language or country | Total independence; suits ccTLDs and separate teams | Hreflang and updates must be managed manually across sites |
Check each plugin's current features and pricing on its own site; licensing models change. As of late 2026, WordPress core still has no built-in multilingual support, which remains a long-term item on the project roadmap.
WPML vs Polylang for affiliate sites
Both store translations as linked posts, which is what affiliate sites usually need, because you will often want different offers, programmes or comparison tables per language.
- WPML is a paid plugin with a broad set of add-ons, string translation, translation management and support for exporting content for professional translators. It suits larger sites and teams.
- Polylang has a free core version on WordPress.org, with a paid Pro version for extra features. It is lighter and simpler, and suits smaller sites or developers who want less overhead.
Either works. Choose on the features you need (translation management, page-builder compatibility, WooCommerce support if you sell), not on popularity. Test on a staging copy with your theme, SEO plugin, link manager and page builder before committing, because compatibility problems show up only with your exact stack.
Choosing the URL structure
All the main plugins support language subfolders (example.com/de/), and most support subdomains or separate domains too. For a single affiliate brand expanding across Europe, subfolders are usually the easiest to manage and concentrate authority on one domain. Our ccTLD vs subfolder guide covers the trade-offs, including when separate ccTLD sites justify separate installs.
Plan the rest of the structure at the same time. Each language needs its own menus, widgets, footer text, category and tag names, and translated media details such as image alt text. Decide whether comparison tables and review scores are shared across languages or maintained separately, because affiliate offers often differ by country. Getting these decisions written down before you translate saves a lot of rework later.
WordPress hreflang: getting it right
The multilingual plugins generate hreflang tags automatically when translations are linked. Your job is to check them:
- Every translated page lists itself and all its alternates, with correct language (and optional country) codes.
- An x-default points to your language selector page or main version.
- Untranslated pages do not claim alternates that do not exist.
- Canonical tags on each language version point to itself, not to the original language.
- Your SEO plugin and multilingual plugin are not both outputting hreflang, which creates conflicts.
Crawl the site with an SEO crawler after launch and check Search Console for hreflang-related problems. The full method is in hreflang for multilingual affiliate sites.
Keeping affiliate links and tracking intact per language
This is where multilingual affiliate sites most often leak revenue. Set rules before translation starts:
- Never let translators or machine translation touch affiliate URLs. Exclude link attributes from translation, or use shortcodes or link-manager slugs that the translator does not edit.
- Use a link manager with per-language destinations. A cloaked link such as /go/brand/ can resolve to the German offer on German pages and the French offer on French pages, or you can create separate slugs per language.
- Add a language sub-ID to every affiliate link (for example sub1=de), so programme reports show revenue by language. See what sub-IDs are and how to use them.
- Check that each programme accepts traffic from the target countries and that you link to the localised landing page, not the English one.
- Keep rel="sponsored" or rel="nofollow" on affiliate links in every language; check that the translation process does not strip attributes.
- Translate disclosures properly, so affiliate disclosure is clear in each language, close to the links.
Run a link audit after every translation batch. Crawl the new language folder, export all outbound links, and check that each one goes to the right programme, carries the right sub-ID and returns a working page.
A multilingual site workflow that scales
- Finalise the source page in your main language, including links and tables.
- Decide per language whether the page is a straight translation or needs different offers or sections.
- Do keyword research per language and give the translator target keywords, title and meta guidance.
- Translate: export to your translator (WPML supports translation-management exports) or draft with machine translation and send for human post-editing.
- Review as a native speaker, in the live template, on mobile.
- Swap in local affiliate links and sub-IDs, then run the link audit.
- Publish and link the translation to the original so hreflang updates.
- Track updates: when the source page changes, flag translations as needing an update. Both main plugins can show which translations are out of date.
On whether to use machine translation at step 4, read machine vs human translation for multilingual SEO.
Performance, caching and consent per language
- Caching: make sure your cache and CDN keep a separate cache for each language URL, and do not serve cached pages by cookie or browser language.
- Database load: multilingual plugins add queries; use object caching on larger sites.
- Consent banners: translate the banner and cookie policy, and check that consent choices apply across language versions on the same domain.
- Language switcher: use crawlable links to the equivalent page, not a JavaScript-only dropdown, and do not force IP-based redirects.
A worked example (hypothetical)
A sexual-wellness review site on WordPress adds German and French with Polylang in subfolders. The owner uses a link manager with /go/ slugs, sets separate destinations for each language, and adds sub1=en, sub1=de and sub1=fr. After the first month, programme reports show the French pages driving clicks but few sales; the audit finds French pages pointing to an English landing page for one merchant. Fixing that one link lifts French conversions. Without the language sub-ID, the problem would have been invisible.
Tools for link management, translation and SEO auditing are listed in our webmaster software and services directory.
Frequently asked questions
Is WordPress Multisite better than a plugin for a multilingual site?
Not usually for a small or mid-sized affiliate site. Multisite suits cases where each language has its own team, very different content or its own plugins. A single install with a translation plugin is simpler to run.
Can I use automatic translation for a multilingual affiliate site?
You can use it for drafts, but money pages need human review for quality, keywords and compliance. Exclude affiliate URLs from automatic translation in every case.
Do translated pages need different affiliate programmes?
Often. Many programmes have country-specific landing pages or separate local programmes, and some do not accept traffic from every country. Check each programme for each language before you publish.
Next steps
Set up a staging copy, install your chosen plugin, and translate one complete money page end to end, including links and sub-IDs, before you scale. More guides on multilingual SEO and localisation are in our European markets section.