Start with a visitor task

Entity-aware architecture organizes information about identifiable people, organizations, products, services, and places. It complements query research; it does not replace the words customers use or make links irrelevant. The useful question is whether the site explains the subject and the relationships a visitor needs.

Example: a home-service business

A contractor can have one parent service directory, a page for each meaningfully distinct service, examples of completed projects, and location information that reflects where the business actually works. A repair page answers a different need from a replacement page. Two pages that only swap nearby town names may add little useful information.

PageMain visitor taskUseful next step
Service overviewDecide whether the business handles the jobSpecific service
Repair serviceUnderstand fit, process, and exclusionsRelevant project example
Project exampleEvaluate actual experienceQuote request

Build the inventory

Record the current URL, main topic, intended customer, question answered, evidence, and next action. Mark overlapping pages for review. Decide whether to improve, combine, or retain them based on their purpose rather than a target word count.

Link relationships in context

Use descriptive anchors that explain the destination. A link labeled as a city-specific fencing service should not silently land on an unrelated general page. Navigation helps discovery; a relevant link inside an explanation helps the reader understand why another page matters.

Check the implementation

Check real HTML headings, lists, links, canonicals, and status codes. Structured data should describe the same service and provider as the visible page. A valid JSON block does not establish that its geographic claims are true.

Sources and scope