Topical maps and page purpose
Give every page a reason to exist.
A topical map connects the questions your audience needs answered with the pages, evidence and routes that can answer them. It is a plan for useful content, rather than a target number of URLs.
Free learning from Semantec SEO.

Start with the website
A list of phrases is not a page plan.
Similar searches can need different answers. Different wording can describe the same task. Compare the intended reader, the question, the conditions and the result the answer needs to provide before deciding how many pages to create.
Use four inputs together: the business’s confirmed scope, suitable audience questions, the current page inventory and search observations relevant to the same context. Another website can suggest a question, but it cannot establish your service offer or justify copying its claims.
A candidate topic can become a new page, a stronger part of an existing page, a shared explanation, a consolidation or a decision to wait. Read what a topical map represents and source context and audience before expanding the list.

Make the record usable
Connect the question with a clear decision.
Give each task a stable reference so a wording change does not erase its history. Keep an existing URL separate from a proposed destination. That distinction prevents a planned page being mistaken for a published answer.
- Reader and question
- Who needs the answer, and what question or action should it address?
- Page purpose
- What must this resource explain, which conditions apply, and what belongs elsewhere?
- Current answer and action
- Retain, improve, combine, create or wait. Record the reason rather than treating every row as new content.
- Evidence and dependencies
- Identify the approved facts, specialist review, images, other answers and working contact route needed.
- Responsibility and version
- Name who confirms facts, writes, publishes and maintains the answer. Preserve the previous decision when it changes.
The topical map process develops the sequence from inputs to website review.

A worked example
One bicycle workshop. Four different tasks.
Imagine a fictional bicycle workshop. The following page choices illustrate planning decisions, with no confirmed workshop offer, price, search demand or customer outcome.
- Assess the repair service
- Explain the work the business confirms it provides, its scope and request conditions. This is a candidate service page.
- Compare repair and replacement
- Explain supported decision criteria and their limits. A separate comparison can be useful when it answers a different question from the service offer.
- Request an assessment
- Explain required information, the contact route and what follows the request. An enquiry does not automatically confirm an appointment.
- Learn what the inspection covers
- Keep a short inspection explanation on the service page when it supports that decision. A separate resource needs an independently useful question and enough supported detail.
These tasks share a subject, but their openings and next steps differ.

Check the boundaries
More coverage does not mean more pages.
Read complete answers when two pages appear to overlap. Shared words or similar titles do not establish that the resources serve the same task. Compare what each reader needs, the evidence, the conditions and the useful next step.
Keep distinct tasks separate when a combined answer would confuse the purpose. Combine material when it serves one answer more clearly together. Preserve useful explanations and review existing routes before changing their destination.
A missing estimate stays unknown; a reported zero is a reported detail. Neither settles the editorial decision. Likewise, a competitor’s missing answer is a question to investigate, not evidence for your proposed answer.
Use separate or combine decisions and the coverage review. Similar content alone is not proof of search cannibalization.

Connect the answers
Subject relationships and navigation serve different jobs.
A parent subject can contain a narrower subject without requiring a matching folder, menu item or compulsory reading path. A hub introduces the area and helps people choose. A focused resource answers its own question, including enough context for someone arriving directly.
In the workshop example, the comparison can lead to a relevant service only after explaining the choice. The service can link to request information when a visitor has enough context to judge fit. Neither link needs to appear beside every related word.
Keep the link’s promise clear and check the destination it reaches. Use hubs and support pages for page roles and navigation and architecture for usable routes.

Keep the map current
A revised plan needs a corresponding website review.
Suppose the workshop’s inspection explanation moves from a separate candidate into the service page. Retain the explanation and its limits, record the new owner, then revise the affected instructions, hub preview and proposed contextual links.
If public URLs already exist, examine their content and incoming links before deciding on redirects or canonical declarations. Editing a map does not change those routes, prove indexing or establish a search improvement.
Keep fact changes, editorial decisions, website changes and observed outcomes distinct. “Topical authority” describes a practitioner idea; this map supplies no universal authority score or ranking promise.
Read map versions and changes and content dependencies for the maintenance and production decisions.

Choose your next question
View the focused articles.
Choose the explanation that matches the decision in front of you. You can enter at any point.
what a topical map represents
Continue with the focused explanation and examples for this task.
source context and audience
Continue with the focused explanation and examples for this task.
query groups
Continue with the focused explanation and examples for this task.
page and content block decisions
Continue with the focused explanation and examples for this task.
topical map process
Continue with the focused explanation and examples for this task.
versioning the map
Continue with the focused explanation and examples for this task.
programmatic page detail
Continue with the focused explanation and examples for this task.
content dependencies
Continue with the focused explanation and examples for this task.
answer ownership
Continue with the focused explanation and examples for this task.
overlap diagnosis
Continue with the focused explanation and examples for this task.
split or merge decisions
Continue with the focused explanation and examples for this task.
coverage matrix
Continue with the focused explanation and examples for this task.
topical authority and maps
Continue with the focused explanation and examples for this task.
parent and child relations
Continue with the focused explanation and examples for this task.
hubs and support pages
Continue with the focused explanation and examples for this task.
navigation and architecture
Continue with the focused explanation and examples for this task.
canonical and indexing controls
Continue with the focused explanation and examples for this task.
Work with Semantec SEO
Commission a topical map
Semantec SEO can assess your website’s subjects, current answers and missing tasks, then provide the agreed map, page instructions and production priorities.
