01
Why glossary control matters
Machine translation can be fluent but inconsistent. Product names, brand terms, abbreviations, chemical names, plugin names and technical phrases need deterministic treatment across languages.
Translation Quality WordPress multilingual translation
Glossary for WordPress.
Protect brand names, product terms, technical vocabulary and do-not-translate strings across every localized page. This page is written for real WordPress usage: admin screens, REST operations, translation tables, SEO outputs, frontend rendering and global growth workflows.
Glossary visualized
Page-specific SVG based on real Verto workflow.
Version OKPage-specific SVG based on real Verto workflow.
Product context
/products/verto/glossary/Built for practical multilingual WordPress operations.
Keep product names, brand terms and terminology consistent. The goal is not only to translate strings, but to keep localized URLs, SEO signals, provider cost, review quality and frontend performance aligned.
02
Glossary enforcement
Verto can enforce glossary mappings after translation when the source term exists but the model leaves the target term wrong or untranslated. Enforcement applies to visible text rather than HTML tags and attributes.
03
Do-not-translate rules
Operators can maintain terms such as LemonX, WordPress or shortcode placeholders that should not be translated by providers.
Key features
What this Verto page covers.
Every module is represented with content and a matching SVG card so the page reads like a product document rather than a plain marketing landing page.
Glossary source-to-target mappings
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Post-translation glossary enforcement
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Do-not-translate list
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Brand and product term control
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Structural QA for missing glossary terms
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Textarea round-trip settings
Glossary helps teams handle this requirement in a WordPress-native multilingual workflow.
Recommended workflow
WordPress adminHow teams should use this feature.
The workflow below matches how operators usually work inside WordPress: configure, scan, queue, review, publish, cache and report.
01
Add brand and product termsDesigned for repeatable operations inside the LemonX Verto admin workflow.02
Add glossary target equivalentsDesigned for repeatable operations inside the LemonX Verto admin workflow.03
Add do-not-translate strings and placeholdersDesigned for repeatable operations inside the LemonX Verto admin workflow.04
Run translationsDesigned for repeatable operations inside the LemonX Verto admin workflow.05
Flag rows missing enforced termsDesigned for repeatable operations inside the LemonX Verto admin workflow.06
Approve or edit review rowsDesigned for repeatable operations inside the LemonX Verto admin workflow.Plugin data model
Connected to real plugin structures.
This page is mapped to Verto’s real settings, REST endpoints, database tables, services or frontend rendering behavior. That makes the content suitable for Google SEO, AEO inclusion and developer trust.
| Source | Meaning |
|---|---|
| Options | glossary, glossary_enforce, do_not_translate and qa_flag_review. |
| QA behavior | Rows can be marked review when enforced glossary terms are missing. |
| Scope | Visible text is enforced without changing tags or attributes. |
| Default DNT examples | LemonX, WordPress and {{shortcode}} are included by default. |
SEO & AEO readiness
Structured for search engines and answer engines.
The page includes a descriptive title, meta description, canonical URL, Open Graph metadata, FAQ structured data, SoftwareApplication structured data and BreadcrumbList structured data.
- Clear definitions near the top of the page.
- Question-style FAQ content for AI answer extraction.
- Internal links to adjacent product features.
- Plugin-version and WordPress-context signals for trust.
- Original SVG scenes instead of generic small decorative icons.
Search-friendly content, answer-ready structure and product evidence in one page.
FAQ
Common questions about Glossary.
Can glossary rules protect brand names?
Yes. Use do-not-translate for terms that must remain unchanged and glossary pairs for controlled equivalents.
Does enforcement change HTML tags?
No. Enforcement is designed for visible text, not tags or attributes.
Can glossary failures be reviewed?
Yes. QA flags can mark rows as review when glossary expectations are not met.
Is this useful for B2B websites?
Yes. Technical terms, product grades, model names and industry vocabulary benefit strongly from glossary control.
Build multilingual WordPress growth with LemonX Verto.
Use Glossary as part of a complete multilingual workflow: languages, provider chain, translation queue, review, SEO, cache, search and LemonX ecosystem integration.