Choosing a theme or plugin for a multilingual WordPress website requires more than checking whether the product can be installed and displayed. A product may work correctly with one page, yet leave custom fields, interface labels, forms, URLs, or WooCommerce workflows unavailable for translation. This is why WPML compatibility should be treated as a practical workflow question rather than a simple marketing label.
The official WPML theme and plugin directories provide a useful first screening step. However, a directory listing does not guarantee that every version, builder configuration, extension combination, or customization will behave identically on your website. The most reliable decision combines documented compatibility information with a controlled staging test that reflects the actual content and functions of the site.
Why WPML Compatibility Should Be Checked Before Installation
WPML compatibility can affect the complete multilingual experience. It may involve translated pages, custom fields, post types, taxonomies, shortcodes, widgets, theme options, plugin strings, forms, emails, language-specific URLs, and ecommerce data. A product can appear to load normally while still producing untranslated labels or missing content in another language.
Compatibility Is a Workflow Question
Checking only whether a page renders is not enough. Consider what the selected theme or plugin creates, stores, changes, or displays. The evaluation should include the WordPress editor, the translation workflow, and the public front end. A translation that appears complete in the dashboard but is missing from the visitor-facing page is not a successful result.
For this reason, test the product on a staging site or use a backup before activating it on a production multilingual website. The objective is not to prove that a product works in every possible configuration. It is to verify that the actual site stack supports the workflows that matter to its owners, editors, customers, and visitors.
Use the Official WPML Theme and Plugin Directories
Begin with the relevant official WPML directory. WPML maintains a directory of compatible themes and a separate directory of recommended plugins. These catalogues can help narrow a comparison before installation, especially when several products appear to offer similar functions.
Checking Themes
Search for the exact theme in the WPML theme compatibility directory. Review the available filters, including industry and page builder, when they are relevant to the planned website. A theme-specific translation guide can also clarify how theme content, theme text, builders, or theme options are handled.
Do not rely only on the theme author or product category. Confirm the exact product information and relate it to the planned configuration. If the site will use a particular builder, custom templates, or additional plugins, those combinations still require validation on staging. A tested theme is useful evidence, but it is not a universal promise for every customization or future release.
Checking Plugins
Search the WPML plugin directory by plugin or developer name where applicable. Use functionality and compatibility filters to focus the comparison. The directory includes products from areas such as ecommerce, forms, page building, SEO, membership, and performance, but the relevant question remains whether the documented integration covers the functions required by your website.
Open any product-specific WPML information before installing or configuring the plugin. Note which content types, fields, strings, or workflows are described. If a plugin works with WooCommerce, forms, memberships, or dynamic content, compare the documentation with the exact processes the site will use rather than assuming that one compatible component covers the entire stack.
What WPML-Tested Compatibility Actually Tells You
WPML-tested compatibility means that a theme or plugin has been included in WPML compatibility documentation or a relevant directory as a product tested for multilingual use. This is stronger than an unsupported general claim, because the integration has been considered in relation to multilingual content and product data.
The technical scope may include making custom fields, post types, taxonomies, shortcodes, meta keys, and strings available for translation. Some compatible products can include a wpml-config.xml file that defines which data should be translatable. This helps WPML understand product-specific content, but it does not remove the need to test the actual site configuration.
Look Beyond the Directory Label
Compatibility settings are mainly relevant to less-popular products, very recent releases, or websites showing specific translation symptoms. Many major themes and plugins can work without manual compatibility configuration, while other products may require additional attention when important fields or strings are not exposed correctly.
Check whether the integration covers the content types used by the website. A builder, extension, custom template, or combination of products may change the result. Treat the tested status as evidence of tested integration, not as a guarantee for every version, customization, extension combination, or future update. Do not change compatibility settings or add custom configuration without a backup and a clear understanding of the affected fields and content types.
How to Test an Unlisted Theme or Plugin on Staging
A product that does not appear in the WPML directory should not automatically be treated as incompatible. The directory is a screening resource, not a universal pass-or-fail checker for every theme and plugin. An unlisted product needs a more deliberate review before it becomes part of a production multilingual stack.
First, check the product author’s documentation for WPML or multilingual support. Then identify what the product stores or displays. The relevant elements may include custom fields, post types, taxonomies, shortcodes, widgets, forms, emails, visible labels, and dynamic or JavaScript-generated output.
Build a Small Test Translation
Use staging to create a representative test rather than translating an entire website. Include the types of content the product actually controls. WPML’s test-translation guidance covers areas such as page content, custom fields, taxonomies, hard-coded theme and plugin text, widgets, and admin strings.
After sending the content through the translation workflow, verify the result on the front end. Check that the translated values return to the correct fields and appear in the expected locations. Repeat the test with the product’s main user journey, such as submitting a form, viewing dynamic content, or moving through a store process. The purpose is to find gaps before they affect production visitors.
Check Strings and Hidden Product Data
Strings are text outside ordinary posts, pages, and taxonomy terms. They can include theme labels, plugin labels, form labels, error messages, button text, and other interface text. A page may be translated while these elements remain in the original language, so they deserve a separate check.
Also verify that important custom fields and product data are exposed for translation. If visible labels are missing, WPML documents string scanning and Admin Texts Translation workflows that can help locate text outside standard content. If important fields remain unavailable or behave unpredictably, consult the relevant product or WPML support resources before making manual configuration changes.
Multilingual Features to Test Before Launch
Before deployment, test a complete visitor workflow rather than one translated page. The exact checklist depends on the selected theme, plugins, builder, content model, and store configuration, but the following areas cover common sources of multilingual problems.
Content, Interface, and SEO Checks
Start with the content visitors and editors use most often. Confirm that translations are available and displayed correctly for page content, custom fields, taxonomies, menus, widgets, and theme or plugin strings. Review forms, validation messages, error messages, button text, and dynamic output. JavaScript-generated text also needs attention if it appears on the front end.
Test language switching from representative pages and confirm that translated URLs and slugs lead to the correct language version. Where relevant, verify translated SEO metadata, language-specific URLs, hreflang behavior, and sitemap output. These checks help identify problems that are not visible in the WordPress editor or translation dashboard.
- Confirm that translated content returns to the correct front-end locations.
- Check menus, widgets, labels, forms, buttons, and error messages in each required language.
- Review custom fields, taxonomies, dynamic content, URLs, and slugs.
- Verify relevant SEO metadata, hreflang behavior, and sitemap output.
WooCommerce Workflow Checks
For WooCommerce websites, the test must follow the customer journey. Review translated products, variations, categories, and tags, then continue through the cart and checkout. Check shipping methods, payment methods, customer-account pages, and order emails. Extension-generated strings can introduce additional untranslated labels or messages.
Do not treat a successful product translation as proof that checkout or transactional communication works correctly. Test the visible front end and the complete store flow on staging. Pay attention to language switching during the journey, product data shown in the cart, checkout labels, and the content received after an order process.
- Test products, variations, categories, and tags.
- Check the cart, checkout, shipping methods, and payment methods.
- Review customer-account pages and order emails.
- Check strings added by WooCommerce extensions and verify the complete front-end workflow.
Decision Rules for Choosing Between Products
When comparing products, prefer a theme or plugin with clear WPML documentation and relevant directory information when that documented scope matches the needs of the site. This does not mean that an unlisted product is unusable. It means that the unlisted option requires additional validation before deployment.
Compare the testing and configuration effort for the actual theme, plugins, builder, content types, forms, URLs, and WooCommerce processes. A product with a documented integration may still need site-specific testing, while an unlisted product may work for a limited use case after a controlled review. Base the decision on verified workflow coverage, not on unsupported claims that one product is universally best or safest.
A Practical Selection Record
Keep a short record for each product considered. Note its directory status, product-specific WPML guidance, tested workflows, missing strings or fields, and any required configuration. Record the tested product versions and integrations, but do not infer future compatibility without checking current documentation or testing.
This record makes product comparison more objective. It also helps identify which parts of the site need retesting after changes. Keep WPML, the selected theme, plugins, and WooCommerce components updated according to their respective vendors, while treating each new release as something to verify rather than as automatically compatible.
WPML-compatible plugins and themes should be selected through a two-stage process: first check the official WPML directories and product-specific guidance, then validate the actual configuration on staging. A tested status indicates documented multilingual testing, but it does not guarantee every customization, extension combination, or future release. For unlisted products, review the author’s documentation and run a focused test translation covering fields, taxonomies, strings, forms, front-end output, URLs, and store workflows. Before launch, verify language switching, SEO-related behavior, and WooCommerce processes from the visitor’s perspective. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.