Glossary

Glossary guide

Entity Mapping: A Practical Guide

Entity mapping is a practical way to decide which real-world things matter to a website, what can be claimed about them, and where each relationship should be made visible.

Editorial entity mapping workflow connecting an organisation, specialist, service, evidence, audience question, and canonical page

Start with the information a buyer needs to trust

Entity mapping is not a technical inventory for its own sake. It starts with the facts a prospective client needs before they can understand an offer: who is responsible, what is included, where the method has been used, which concepts shape the work, and what proof is available.

Writing these relationships down exposes gaps early. A service may be clear but lack an accountable person. A project may exist but not explain its relevance. A guide may define a concept without pointing to the service or evidence that makes it practical. Each gap has a different solution.

Use a claim, evidence, and page model

For every important entity, write the canonical name, the claim that matters, the evidence that supports it, and the page where a visitor should be able to verify it. This creates a small working map that can guide content, internal links, metadata, and structured data without inflating any one of them.

  • Organisation: define the business and its primary offer without using multiple competing descriptions.
  • Person: identify the specialist responsible for guidance or delivery and link to verifiable experience.
  • Service: explain the scope, constraints, and intended outcome in language a buyer can evaluate.
  • Evidence: connect a project, approved example, or first-party resource to the claim it supports.
  • Concept: use a guide or glossary page to explain the method, then link it back to the relevant service or example.

Use the map before changing markup

A map makes it easier to choose the next useful action. Sometimes that is a new page. Sometimes it is an internal link, an author line, a corrected service description, or a decision not to make a claim until evidence exists. Markup comes after the visible information is correct and connected.

This sequence is especially useful during a launch or migration. It reduces the chance that a changed URL, removed page, or inconsistent name breaks an important relationship that visitors and search systems relied on before the change.

Sources