A practical content architecture for search intent

Map the decision, not just the keyword

Keyword lists become useful when they reveal a decision path. Group searches by the question underneath them: learning, comparing, checking fit, finding a local provider, or taking action. Each group deserves a different page type and a different level of detail.

A guide that explains the problem should link naturally to a service page. A service page should answer fit questions and point to an action. The architecture is doing its job when a reader can move forward without returning to the search results.

Use a small set of page roles

Most organisations can build a durable structure with a few clear roles: cornerstone guides for broad questions, supporting articles for specific concerns, service pages for solutions, and proof pages for evidence. The roles are more important than publishing volume.

Label each draft before it is written. If two pages have the same audience, promise, and next step, combine them or give them a sharper distinction. This prevents internal competition and keeps the library navigable.

• Cornerstone: the reference a topic should point back to.
• Supporting guide: one focused question with a clear answer.
• Service page: the practical solution and next move.
• Proof page: evidence, examples, process, or credentials.

Build links as editorial recommendations

Internal links should sound like a recommendation a human editor would make. Link when the next page genuinely adds context, and use anchor language that tells a reader what they will find. Avoid a footer full of unrelated links that no one would choose.

For Hong Kong businesses, add local context links where it changes the decision: districts, languages, building types, business categories, or service coverage. This is how a library becomes a useful map instead of a pile of pages.