Mapping Questions to Pages
Every question in your backlog needs one home. Some deserve their own page, most belong as a section of an existing one, and a few belong in an FAQ. Getting this map right avoids pages competing with each other.
Three possible homes
- A dedicated page when the question is a topic in its own right with search demand and depth (for example "custom software development cost in Trichy").
- A section on an existing page when it is part of a bigger topic (for example "how long does ERP implementation take" on the ERP service page).
- An FAQ entry when the answer is short and the question is a supporting detail.
One question, one owner
If two pages answer the same question in depth, they compete and the engine may pick neither. Keep a simple sheet: question, owning URL, heading used, date answered. When a new page is planned, check the sheet first.
Use the hub and spoke pattern
A hub page answers the broad question briefly and links to spoke pages that answer the detailed ones in depth. The hub wins the short definition answer, the spokes win the specific how and cost answers, and internal links tell the engine how they relate.
Low demand, short answer: FAQ. High demand, deep answer: its own page.
Pro tips
- Keep a question to URL map in a shared sheet and check it before writing anything new.
- Link from the hub to each spoke with the question itself as the anchor text.
- Move a strong FAQ entry to its own page when its search demand grows.
Common mistakes
- Writing a new blog post for every question, creating dozens of overlapping pages.
- Answering the same question differently on the service page and the blog.
- Hiding important answers only inside collapsed FAQ accordions with no heading.
Give each question one owning page: a dedicated page, a section or an FAQ entry, organised as hubs and spokes and tracked in a simple map.