A website glossary brief defines which specialist terms a business needs to explain, where those explanations belong and who approves their meaning. Customers may encounter unfamiliar abbreviations, materials or service names while comparing an offer. A useful glossary removes that obstacle without making every visitor read a separate dictionary before understanding the service page.
For a company planning website development in Kenya, prepare the vocabulary around actual customer questions. This guide concerns editorial definitions and navigation, rather than a technical search feature or a claim that creating many term pages will improve rankings. The examples are illustrative content decisions, not definitions of a particular client's products.
Start with words that affect a buying decision
Ask customer-facing staff which terms repeatedly need explanation. Collect the wording customers actually use alongside the terminology in product sheets and proposals. Prioritise words that change someone’s understanding of suitability, scope or the next step, rather than listing every technical expression the team knows.
Choose a small initial set and identify the page where each term matters. A material name may need explanation beside a product choice. An internal project acronym may not belong on the public website at all. Removing unnecessary jargon can be more useful than writing a definition for it.
Do not treat search impressions as proof that visitors need a glossary entry for every phrase. Review the existing pages and real support questions before adding content. The objective is a clearer decision journey, not a target number of pages or a guaranteed increase in organic traffic.
Write definitions for the intended reader
Begin with a plain explanation of the term in the business's context. Avoid defining one unfamiliar expression with several more. Where a term has different meanings across industries, state which meaning applies to the service or product being discussed.
Use an illustrative example only when it helps explain the distinction. Label it appropriately and avoid turning it into a claim about work the business has completed. A short comparison can clarify why two similar terms are not interchangeable without inventing performance statistics or customer outcomes.
Keep the definition separate from promotional copy. Someone seeking the meaning of a technical phrase should receive that explanation before a sales invitation. If the term affects an actual offer, link to the maintained service page instead of copying every price, condition and package inclusion into the glossary.
Prepare a term and approval register
Record the preferred public term, accepted abbreviation, definition, relevant service page and approval owner. Add common alternatives so editors can recognise when different words refer to the same concept. The register should support consistency rather than force unnatural repetition of one exact phrase.
Identify terms that require a specialist reviewer. The writer can simplify language, but should not change the underlying technical meaning or invent a compliance definition. Have the responsible business expert approve important distinctions before the text is published.
For regulated or safety-related subjects, obtain appropriate authoritative review and scope the content carefully. This worksheet does not establish legal or technical standards. If the business cannot support a reliable public definition, flag the uncertainty for resolution instead of filling the gap with a confident guess.
Decide between inline help and a separate glossary
A brief explanation beside the first relevant use may be enough for an essential term. Readers should not need to leave a service page merely to discover what its main offer means. Reserve a separate glossary for vocabulary that benefits from a maintained reference or appears across several journeys.
Choose whether the glossary is a single organised page or a set of genuinely useful individual entries. Do not create a thin page for every abbreviation only to expand the website. Consider how much explanation exists and whether a visitor can find the term efficiently on a phone.
W3C's content structure guidance describes semantic structures including description lists for related terms and descriptions. Ask the developer to select an appropriate structure for the actual content, rather than styling disconnected boxes to resemble a definition list.
Connect explanations to useful page context
Link a term from places where an explanation helps the visitor. Use a clear label so people can predict the destination. Avoid turning every repeated occurrence into another link, which can make ordinary paragraphs harder to read without adding useful navigation.
On the glossary itself, offer a route back to the relevant service or product information. A person arriving directly from a shared link should understand why the definition matters. The destination should reflect the term's actual use, not lead every entry to a generic quotation form.
Keep the website FAQ content brief as a separate editorial tool. A definition explains a term; an FAQ answers a practical question. Some subjects need both, but the pages should provide distinct help rather than repeat the same paragraphs under different headings.
Handle abbreviations and related terms consistently
Decide how the full term and abbreviation appear on first use. A specialist reader may recognise the short form immediately, while a new customer may not. Test the wording with the intended audience instead of assuming that staff familiarity represents customer understanding.
Where two terms overlap, explain the boundary rather than create contradictory entries. A synonym can point to the preferred definition, while a genuinely different concept needs its own explanation. Record that relationship so a future editor does not accidentally merge distinctions that matter to the service.
Review the website service comparisons brief when terminology appears in package tables. A glossary should clarify the criteria, not conceal an unclear comparison. Important differences and conditions still belong where the buying decision is made.
Review the real mobile reading journey
Use the actual approved terms and definitions in the design review. Long abbreviations, product names and explanatory sentences can behave differently from sample text. Check that alphabetical navigation, category labels or in-page links remain understandable at the agreed phone sizes.
Ask a reviewer to find one term, explain its meaning and return to the relevant service information. Record where they hesitate. This is more useful than asking whether the glossary looks complete, because the task exposes unclear labels and missing context.
Include keyboard and accessibility review through the project's agreed evaluation scope. Definitions should remain available without relying only on hover tooltips. If expandable sections are used, the implementation should communicate their operation and preserve access to the explanation across supported interaction methods.
Maintain definitions when the service changes
Assign a reviewer for substantive updates and a clear correction route. A changed process or product range can alter how a term is used. The glossary and the pages linking to it should be reviewed together rather than treating definitions as permanent content that never needs attention.
Track where important terms appear, especially in downloadable documents or comparison tables. Correcting the glossary alone may leave an old proposal template describing the concept differently. The content owner should decide which placements need revision and which historical documents remain unchanged with appropriate context.
At handover, provide the term register, approval evidence and navigation decisions. Request a website project quotation with the proposed vocabulary and customer tasks. That allows the team to scope the content and presentation around a useful reference, without promising that a glossary alone will create enquiries or replace clear service writing.
Frequently asked questions
Does every website need a glossary?
No. Use one when specialist vocabulary creates a real reading problem. Clear wording and short inline explanations may be sufficient for a smaller site.
Should definitions contain prices?
Usually link to the maintained offer where appropriate. Avoid creating another conflicting place to update changing commercial information.
Can a glossary replace FAQs?
They serve different purposes. Definitions explain terms, while FAQs answer practical questions about the offer or process.
Who should approve technical meanings?
Assign someone with the relevant business knowledge. Writers and designers can improve clarity without becoming the authority for unsupported technical claims.