Terminology management for docs teams
One vocabulary across your docs, your product, your support and every translation.
Glossage keeps one glossary of approved terms, with definitions and translations, and applies it where documentation, support and localisation teams write. It also finds where the same concept goes by different names.
No account. No card. No sales call.
- One glossary of approved terms
- Enforced where people write
- Drift found across docs and help centre
Does your content call the same thing by the same name everywhere?
Answer fifteen questions about how terms are chosen, used and translated across your docs, product interface, help centre and languages. See your score and what to put in place first. Runs in your browser. No account, no card, no call.
Method: yes scores a question in full, partly scores half and no scores nothing. Each question is weighted from one to three by how far an inconsistency there tends to spread, across pages and then across languages, and the score is the weighted share, as a percentage. Unanswered questions are left out.
The problem
Large content estates drift.
The same feature is called three things across the docs, the product interface and the help centre, support articles contradict the manual, and every inconsistency multiplies across every language at translation time, where it costs real money per word.
Style guides exist as a document nobody consults.
Who it is for
Documentation teams
Docs teams at software and hardware companies with more than 300 pages of content.
Support teams
Teams whose help centre articles need to agree with the manual and the product interface.
Localisation teams
Teams publishing in more than one language, where every inconsistency multiplies at translation time and is paid for per word.
Terminology enforced in the writing workflow
A living glossary applied where content is written, instead of a style guide that exists as a document nobody consults.
- 01
A living glossary
Approved terms with definitions, forbidden alternatives and translations per language.
- 02
Suggestions while writing
Terms are enforced as inline suggestions in the writing tool.
- 03
Checks in pull requests
For docs-as-code, terminology is enforced in pull requests.
- 04
Interface strings included
The product's own interface strings are held to the same glossary.
- 05
Drift and contradictions
It detects drift across the whole estate, finds terms in use that are not in the glossary, and flags contradictions between the docs and the help centre.
- 06
Translation memory alongside
Translation memory is maintained alongside the glossary, so terminology decisions propagate rather than being re-litigated per language.
How it works
Glossage, from the first step to the result.
- 1
Get the drift report
It crawls your public docs and help centre and returns the inconsistencies.
- 2
Build the glossary
Approved terms, definitions, forbidden alternatives and translations.
- 3
Enforce where people write
Inline suggestions, pull request checks and interface strings.
- 4
Keep languages aligned
Translation memory carries each terminology decision across languages.
Pricing
Start with a free drift report on your public docs, then enforce a glossary across your content estate.
Drift report
Freeany public docs site
The inconsistencies in your docs and help centre.
- Contradictory statements
- Terms likely to be mistranslated
Glossary
Recommended$249per month
For one content estate.
- Glossary enforcement
Multi-language
$690per month
For content in more than one language.
- Translation memory
Enterprise
Customwith integrations
Integrated with your localisation and content systems.
- Localisation pipeline integration
- Content management system integration
Prices in USD.
Questions people actually ask
What does the free drift report show?
For any public documentation site, it crawls the docs and help centre and returns the inconsistencies: the same concept named differently across pages, contradictory statements, and the terms most likely to be mistranslated.
Where is the glossary enforced?
As inline suggestions in the writing tool, in pull requests for docs-as-code, and in the product's own interface strings.
Does it find terms we have not defined?
Yes. It finds terms in use that are not in the glossary.
How does it help with translation?
Each approved term carries translations per language, and translation memory is maintained alongside, so terminology decisions propagate rather than being re-litigated for every language.
What does it cost?
The report is free. 249 dollars a month covers one content estate with glossary enforcement, and 690 dollars a month covers multiple languages with translation memory.
Is there an enterprise plan?
Yes. Enterprise plans include integrations into the localisation pipeline and content management systems.
Why should I trust the terminology drift check?
The score comes from your own answers, worked out in your browser. It does not read your content. The free Terminology Drift Report crawls a public docs site and help centre and returns the actual inconsistencies.
Does your content call the same thing by the same name everywhere?
Answer fifteen questions about how terms are chosen, used and translated across your docs, product interface, help centre and languages. See your score and what to put in place first. Runs in your browser. No account, no card, no call.
Open the free toolIt runs in your browser. Glossage never sees your inputs.