WPML Glossary Setup: How to Keep Automatic Translations Consistent

If you are using WPML automatic translation on your WordPress website, you have probably noticed that the results are not always consistent. A product name gets translated differently across pages. A technical term that should stay in English gets changed. A brand name that should never be touched comes back looking wrong. This is not a bug. It is what happens when automatic translation runs without a glossary in place.

The WPML glossary is one of the most underused features in the entire plugin, and it is also one of the most valuable when you are relying on automatic translation to handle large volumes of content.

What the WPML glossary actually does

The glossary gives you control over how specific words and phrases are handled during automatic translation. You can tell WPML to always translate a term a certain way, to never translate it at all, or to keep it exactly as written regardless of the target language. That level of control matters a great deal when your site contains brand names, product terminology, legal language, or any wording that needs to stay consistent across every language you publish in.

Without a glossary, automatic translation makes its own decisions about those terms every single time. Sometimes it gets it right. Often it does not, and the inconsistencies build up across your content in ways that are time-consuming to fix manually.

When to set up the glossary

The right time to set up your WPML glossary is before you run automatic translation for the first time. If you add glossary terms after translations have already been generated, those existing translations will not automatically update to reflect the new rules. You would need to retranslate the affected content, which costs translation credits and takes time.

This is one of the reasons I always recommend getting the glossary in place as part of the initial WPML configuration, not as an afterthought once problems start appearing. It is a small investment of time upfront that saves a significant amount of correction work later.

What belongs in your glossary

Not every word needs a glossary entry. The goal is to capture the terms where inconsistency would cause a real problem. Brand names and product names that should never be translated are an obvious starting point. Technical terms that have a specific meaning in your industry and should not be paraphrased by an AI translation engine belong there too. If your site has a specific preferred translation for a term in a given language, that goes in as well.

For WooCommerce sites, this becomes even more important. Product names, attribute labels, variation names and category terms all benefit from glossary control, because inconsistency in a multilingual shop affects trust and usability in ways that go beyond a simple wording preference.

The glossary is not a complete solution on its own

It is worth being clear about what the glossary cannot do. It controls specific terms, but it does not fix structural problems with your WPML configuration. If your custom fields are not set up to translate correctly, if your URL translation is not configured properly, or if your translation preferences are not aligned with how your theme and plugins work, the glossary will not solve those issues. It is one piece of a larger setup, and it works best when the rest of the configuration is solid.

If you are finding that automatic translation is producing inconsistent or unreliable results across your site, the glossary is worth reviewing, but it is usually worth reviewing the broader WPML automatic translation setup at the same time. In many cases the glossary is fine and the real issue is elsewhere in the configuration.

Getting it right from the start

I have worked with WPML for well over fifteen years and I have seen glossary problems cause real headaches on sites that were otherwise well built. The fix is rarely complicated, but it is much easier to put the right structure in place before translations run than to clean up after the fact.

If you are setting up WPML automatic translation and want to make sure the glossary and the broader configuration are done properly from the start, I am happy to help. You can find out more about how I approach automatic translation setup on the WPML Automatic Translation Setup & Optimisation page, or get in touch directly through the contact form and we can talk through what your site needs.

Photo by Joshua Hoehne on Unsplash