Choosing a WPML language URL format is a structural decision, not just a visual preference. WPML supports three principal approaches: placing languages in directories, assigning a separate domain or subdomain to each language, and adding a language value as a URL parameter. Each option affects hosting, DNS, SSL, maintenance, usability and the way multilingual pages are represented.
There is no universally best format for every WordPress website, WooCommerce store or agency project. The practical choice depends on whether the site should remain under one primary domain, whether the team controls DNS and hosting, and whether different languages represent distinct country markets or brands. This guide compares the options and outlines the checks that help prevent broken language URLs.
WPML Language URL Formats at a Glance
The three supported structures
WPML provides three main URL structures. With language directories, a translation appears in a virtual path such as example.com/es/. The site remains under one hostname, while the language is represented in the URL path. These directories are virtual: they do not require physical folders or separate WordPress installations.
With separate domains or subdomains, a language uses another hostname, such as example.de or de.example.com. This model can fit a country-market or brand strategy, but it requires preparation outside the WordPress dashboard, including DNS, hosting and SSL configuration.
The third option uses language query parameters, for example example.com/?lang=es. This generally requires fewer server changes, but the language is less clearly expressed in the path or hostname. WPML treats these as alternative site-wide formats. A configuration should not freely combine domain-based languages with directories or parameters. Mixing domains and subdomains is supported.
How to Choose the Right Format for Your Site
One domain versus multiple hostnames
Start with the operating model of the website rather than with an unsupported claim about rankings or performance. Language directories are a practical consideration when one primary domain, centralized hosting and relatively simple ongoing maintenance are priorities. They keep language routes under one hostname, but still depend on URL rewriting and suitable permalink settings.
Domains or subdomains may be appropriate when translations represent distinct country markets, brands or domain strategies. They require a team that can manage DNS records, hosting mappings and SSL coverage for the additional hostnames. Country-specific domains can provide clear country targeting, while subdomains create a separate URL namespace without necessarily making country targeting obvious. These are infrastructure and targeting considerations, not a guarantee of a particular SEO result.
Language parameters may be considered when server constraints make the other options difficult. They usually require fewer server changes, but their URLs are less readable and provide less clear URL-based language segmentation. Before changing an established format, review existing language URLs and inbound links. Prepare a backup and rollback plan, because incorrect redirects or mappings can make translated pages inaccessible.
Language Directories: Requirements and Setup Checks
Directory activation checklist
A WPML language directory is a virtual URL path. Do not create physical language folders and do not install a separate WordPress copy for each translation. The website must instead route requests through WordPress and the server’s rewrite mechanism.
WPML states that directory URLs require URL rewriting and a non-default, or “pretty”, permalink structure. WordPress and the server also need appropriate access to read and write relevant files or folders used for rewrite handling and validation. On Apache installations, rewrite support includes checking the applicable mod_rewrite configuration. This is a prerequisite to verify with the hosting administrator rather than an assumption about every host.
Before activation, check the following in order:
- Confirm that WordPress uses a non-default or “pretty” permalink structure.
- Confirm that URL rewriting is enabled on the server.
- Check that WordPress and the server can manage the relevant rewrite files or folders.
- Verify that WPML’s validation request can complete normally.
- Check whether a CDN, cache or security layer is changing or blocking that request.
These checks address routing rather than translation quality. A directory activation failure can result from rewrite support, permissions, unsuitable permalinks or interference during validation. Make changes only with a backup and rollback plan, particularly when rewrite or filesystem settings are involved.
Domains and Subdomains per Language
Domain mapping before WPML assignment
A domain-based WPML setup requires each additional domain or subdomain to be connected to the website through DNS and hosting configuration. The hostnames must resolve to the same WordPress site before they are assigned as language URLs. SSL coverage is also required for each translation domain or through a suitable multi-domain certificate.
Use a controlled order of operations. First connect the domains through DNS and hosting. Then confirm certificate coverage and test the additional hostnames. Before language mapping is enabled, WPML expects those hostnames to display the same site without redirecting to the primary domain. This allows the domain-based configuration to be validated rather than hiding a mapping problem behind a redirect.
After the technical mapping is ready, assign the hostnames in WPML and test each language. WPML validates domain-based configurations, so incomplete DNS propagation, an incorrect hosting mapping, missing SSL coverage or a redirect to the primary domain can prevent the intended setup from working.
Plan the format consistently across the site. Mixing domains and subdomains is supported, but WPML does not allow a mixed configuration in which some languages use domains while others use directories or URL parameters. Do not add manual redirects that stop the mapped hostnames from displaying the same WordPress installation during validation. DNS, SSL and redirect changes should have a backup and rollback plan.
Language Parameters: When They May Still Be Practical
Language parameters append a language value to the URL, such as ?lang=es. Their main practical advantage is that they generally require fewer server changes than language directories or separate domains. This can matter when the site owner has limited control over rewrite rules, DNS or hosting configuration.
The trade-off is URL clarity. A parameter is less immediately readable than a language directory or a dedicated hostname, and it provides less clear URL-based segmentation for multilingual pages. For that reason, parameters are best treated as a constrained option when clearer structures are not feasible, not as a universal recommendation or a guaranteed SEO solution. Test the format on the actual site with its active theme and plugins before applying it to every language route.
SEO and Usability Safeguards for Any Format
Post-configuration crawl and navigation review
The selected WPML language URL format should be accompanied by explicit multilingual signals. Google’s general guidance recommends signals such as hreflang, sitemaps and links between equivalent language versions. Localized URLs and visible links between language pages help users and crawlers reach the intended version instead of relying on assumptions.
Do not rely only on automatic redirection based on an IP address or browser language. Such behavior can prevent visitors and crawlers from reaching the language version they requested. If automatic redirection is used, test it carefully and confirm that direct access to every language URL remains possible.
After a configuration change, review each language homepage and representative internal page. Check that the language switcher points to the corresponding translation, canonical URLs identify the intended page, and hreflang output connects equivalent versions correctly. Also review sitemaps, localized URLs and redirects. These checks are safeguards, not a promise of rankings for any particular WPML language URL format.
Troubleshooting Broken WPML Language URLs
A structured pre-launch test
When language URLs fail, diagnose the configuration according to the selected format. For directories, begin with the permalink structure, URL rewriting and WordPress/server permissions. Confirm that physical folders have not been created for virtual language paths and that manual redirect rules are not conflicting with WPML routing. If activation fails during validation, check whether a CDN, cache or security layer is altering the request.
For domains and subdomains, verify DNS resolution, hosting mapping and SSL coverage. Confirm that the additional hostnames reach the same WordPress installation and do not redirect to the primary domain before WPML mapping is enabled. A parameter setup requires a different review: confirm that the parameter remains present in language-switcher links and that the active theme and plugins handle the selected URLs as expected.
Use this pre-launch order:
- Test hostname resolution, SSL coverage and unwanted redirects where domains or subdomains are used.
- Test every language homepage and representative internal URL.
- Review canonical URLs, hreflang output and sitemap references.
- Confirm that the language switcher links to the correct equivalent pages.
- Repeat the checks after each rewrite, DNS, caching or redirect change.
There is no single fix for every hosting provider, CDN, caching layer, theme, page builder or SEO plugin. Host-specific DNS, SSL, rewrite and permission issues may require the relevant technical administrator. Keep a backup and rollback plan before changing settings that can affect access to the site.
In summary, directories suit a centralized one-domain setup when pretty permalinks and URL rewriting are available. Domains and subdomains fit teams prepared to manage DNS, hosting and SSL for distinct hostnames, while language parameters may help in constrained environments but offer less clear URL segmentation. Whichever WPML language URL format you select, test every language route before launch, including redirects, canonical URLs, hreflang, sitemaps and switcher links. Clear signals and direct links between language versions support both navigation and multilingual site organization. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.