Map a service website around distinct customer questions

Inventory customer questions before page names

Collect the questions people ask before choosing or contacting the business. Use inquiry conversations, sales notes, support questions and the knowledge of staff who deliver each service. Write the question in the customer’s language and note where their situation changes the answer. “Can you work with our existing system?” is more useful planning material than an internal label such as “integration solutions.”

For each question, record the intended audience, service context, answer owner, available evidence and next useful step. Some questions belong across several services and can live once in a shared process or FAQ page. Others change eligibility, preparation or outcome enough to support a dedicated service page. The content map should make those relationships visible before navigation labels or search phrases harden the structure.

Build a service-to-question matrix

Create one row per customer question and one column per service. Mark whether each answer is shared, meaningfully different or not applicable. Then add the evidence and action needed for the answer to be useful.

• Audience and situation: Who asks this question, at which point in their decision and with what existing knowledge?
• Service difference: Does the answer change the eligibility, approach, preparation, deliverable or next step?
• Evidence: Which process detail, original demonstration, specification or approved example supports the answer?
• Page purpose: What single job will the proposed page do that another page does not already perform?
• Relationship: Is this a parent topic, a distinct service, a supporting guide or a section within another page?
• Action: Which next step follows naturally, and does it differ from the action on neighboring pages?
• Owner and maintenance: Who keeps the answer accurate, and what business change triggers a review?

Use a keep, combine or separate decision

Keep an existing page when it has a clear purpose, accurate content and an audience need that remains. Improve it if evidence or explanation is weak. Combine pages when they answer the same question for the same audience and differ mainly by phrasing. Separate a service when the visitor must understand materially different fit, process, evidence or next action. The new page needs enough original substance to stand on its own.

Do not create near-identical pages for towns, industries or keyword variations when the service and answer do not change. Google’s spam policies describe doorway abuse as pages created for similar queries that funnel users to an intermediate destination. Google does not publish a checklist for deciding when a local page is useful; as a Kinetivy planning heuristic, look for real service constraints, accurate coverage, accountable ownership and information a visitor needs. Swapping a place name in repeated copy does not meet that test.

Screen a service-area page before you write it

Start with one real service area and a visitor question, not a list of place names. A separate page is useful only when the business can explain something that changes for people there and keep that explanation accurate. The worksheet below is Kinetivy’s editorial decision aid; it is not a Google ranking score or a rule published by Google.

Fill in one row for each proposed area. If the facts, audience need or owner are still unknown, record “defer” and resolve that gap before writing. If the answer stays the same across areas, keep one clear service page and add an accurate coverage list rather than repeating the page.

• Visitor question: What does someone in this area need to know before they choose, prepare or contact the business?
• Operational difference: What verified availability, travel limit, eligibility, schedule, process or service constraint changes the answer?
• Evidence and owner: Where can the fact be checked, who is responsible for it, and when will it be reviewed?
• Standalone usefulness: What can a visitor decide or do here that the main service page does not already explain?
• Next step: Is there a clear inquiry, booking or preparation action that works for this area?
• Decision: Publish a separate page, add the detail to the main service page, or defer until evidence and ownership exist.

Hypothetical example: keep the useful local detail

Imagine a hypothetical home-repair business serving two regions. One region requires appointments to be grouped around a scheduled ferry crossing, so the business has a different arrival window and a named coordinator who confirms current availability. The other region follows the same process and schedule as the business’s general coverage. If the team can keep the first region’s logistics current, a page explaining those constraints and its inquiry route may help visitors plan. The second region belongs on a shared coverage list because its service answer does not change.

This example is invented to demonstrate the worksheet; it is not research about a real business or a Kinetivy client outcome. If the coordinator cannot verify the schedule or the business stops serving the area, the page is deferred or updated rather than left as a stale search landing page.

Keep website pages separate from Business Profile eligibility

A useful website page and eligibility for a Google Business Profile are separate decisions. Google’s profile rules require in-person contact with customers during stated hours and list online-only businesses among examples that are not eligible. Its service-area guidance also asks businesses to represent their actual operations accurately. Check the current policy for the business itself; a city page does not create a physical location or make an online-only business eligible.

If a site uses LocalBusiness structured data, it should describe the real business information visible on the page and actual locations. Google’s guidance says to define each local business location as a LocalBusiness entity. Do not create a fictional location entity for every place name a page mentions, and do not promise that markup will produce a search feature.

Hypothetical example: mapping a property service site

Consider a hypothetical property-care business offering routine grounds maintenance, one-off garden clearance and interior common-area cleaning. The matrix shows that grounds maintenance and clearance have different timing, preparation, equipment and quotation questions, so they receive separate pages. Two minor mowing packages share the same buyer, process and inquiry path, so they stay as clear options within the maintenance page.

Commercial and residential maintenance are not split merely because both phrases appear in enquiries. Instead, the page explains the eligibility differences in one section. Interior cleaning has a different buyer question, delivery process and evidence, so it remains separate. A shared “How service starts” page owns contracting and onboarding questions common to all three. This is a hypothetical planning example, not a Kinetivy client result.

Turn the map into clear paths

Give each retained page a unique purpose statement, primary question, supporting evidence and next action. Use labels people can understand without knowing the company’s internal structure. A services overview can help visitors choose among distinct paths, but it should not force someone who already knows their need through an extra layer. Link related services when the relationship helps a decision rather than placing every link on every page.

Google’s SEO Starter Guide recommends organizing a site logically and using descriptive URLs and links. Apply that for people first: stable addresses should reflect durable topics, while headings and links should explain what someone will find. Avoid reshaping the hierarchy around every wording variation. When replacing existing pages, preserve useful URLs where possible and plan specific redirects for moved or combined content as part of the later redesign work.

Review the content map with this checklist

Ask a colleague unfamiliar with the draft structure to place real customer questions on the map. If the same question fits several pages equally well, clarify ownership or combine the pages. If a page has no distinct question, evidence or maintenance owner, it is not ready to publish.

• Every service page answers a distinct customer need and has enough specific material to be useful on its own.
• Shared questions have one clear home, with contextual links from relevant service pages.
• Minor variations remain options or sections unless the customer decision genuinely changes.
• No location, sector or phrase page exists only to funnel visitors through repeated content.
• Page labels, hierarchy and internal links match how customers describe and distinguish the services.
• Each page has approved evidence, a natural next action, a content owner and a review trigger.
• Existing useful URLs have a keep, improve, combine or redirect decision for future implementation.