Plan a Shopify website by listing the decisions buyers need to make, assigning each question a primary page, and recording the evidence and next step that page needs. Review this map before choosing layouts. It gives the team a way to explain why a page belongs in the site and what information is still missing.
Here, a sitemap means the planned pages and their relationships. The working document can be a table: buyer question, page, supporting evidence and next action. It connects business knowledge with the work a designer and content team can actually prepare.
Which buyer decision should the plan start with?
Start with a specific situation. “Business buyers” is too broad to tell you which information comes first. A person checking whether a product fits an intended use needs different information from someone who has selected a product and wants to discuss a project.
Use sales questions, approved product materials and existing-site evidence where available. Record their sources. When the team proposes a question without customer evidence, label it as a planning assumption and review it with someone who understands the buying process.
Our guide to ICP and buyer personas explains the audience distinction. For the page plan, take the next practical step: write the question the visitor must answer before moving forward.
What should a buyer-question map contain?
Give each row a question, a primary destination, the information needed to answer it and a useful next step. Add an owner and source reference in your working file so a missing fact has somewhere to go.
The following is a hypothetical planning example for a supplier of modular shelving. These are questions and required inputs, not verified product capabilities or a GRC customer case.
| Buyer question | Primary page | Evidence to prepare | Useful next step |
|---|---|---|---|
| Could this system suit our stockroom? | Product or series page | Confirmed dimensions, configuration options and applicable limits. | Check the relevant use conditions or prepare a project question. |
| What should we consider for a narrow room? | Application guide | A clearly labeled layout example, its assumptions and details the supplier needs to assess. | Review a relevant product, then prepare the room information. |
| What should we send for a project discussion? | Contact or project-brief page | The information actually required by the business, such as intended use, selected system and available room plan. | Use the business's confirmed contact channel. |
This table exposes work that a list of page names can hide. If nobody can confirm a product limit, the row contains a factual gap. If the next step has no destination, the visitor's path is unfinished. Resolve these issues before committing to the layout.
How do questions become page responsibilities?
Group questions by the decision they help the buyer make. A product page can own product-specific facts and conditions. An application page can explain a use situation and direct the reader to relevant products. A contact page can explain what to bring to a conversation and how to start it.
In the diagram, each question has a primary answer location. This is a responsibility map, not a rule that every question requires a new URL.
Several related questions may belong on one page when they support the same decision. Separate them when the purpose, evidence or useful next step changes enough to justify an independent page. Repeating the same introduction across several URLs does not establish a distinct role.
Where do the homepage and navigation fit?
Use the homepage to orient a first-time visitor: what the business offers, who it serves and where to investigate further. The detailed answer can live on a product, application or service page. A visitor arriving directly on an inner page should still understand its purpose and how to continue.
Choose navigation labels that help readers recognize those destinations. Shopify's menus and links documentation explains how menus organize links to products, collections, pages and articles. Menu configuration implements the agreed structure; the team still needs to decide what each destination should do.
How do you connect the pages into a useful path?
Walk through a buyer situation from more than one entry point. In the shelving example, a visitor on a product page may need application context. Someone reading a layout guide may need the relevant product details before contacting the supplier.
Follow the arrows in this illustrative path. Each link should answer a question raised by the page the reader is currently viewing.
Write the link text to describe its destination, such as “check configuration details” or “prepare your project brief,” when that is what the destination provides. Google's link guidance recommends descriptive anchor text and contextual internal links. A connected page plan can support navigation and discovery; it does not guarantee search visibility or inquiries.
What needs to be confirmed before design starts?
Review the map with the people responsible for product information, sales context and website delivery. For each proposed page, check:
- What decision does this page help the reader make?
- Which source supports each important answer, and who confirms it?
- Does an existing page already answer the same primary question?
- What should the reader do next, and does that destination exist?
- Which content is ready, and which missing input affects the page's usefulness?
Keep unresolved facts visible in the brief so the designer knows which content depends on further confirmation. Invented specifications should never appear as finished copy.
When should Shopify templates enter the plan?
Consider templates after the content responsibilities are clear. Pages with a common information structure may share a template while presenting their own content. Other pages may need a different arrangement.
Shopify's template documentation explains that templates use sections, available controls depend on the theme, and template changes affect the pages assigned to them. The implementation team should therefore review both the content model and the actual theme before committing to the design. This article's map defines the requirement; it does not approve a theme change.
What should you bring to a website planning discussion?
Bring the current website, the main products or services, a few source-backed buyer questions and the materials that support their answers. Mark assumptions and unresolved facts. An existing site also needs a review of which pages should remain, change or connect differently.
You can then discuss a concrete plan: which pages have distinct responsibilities, what evidence each needs and how a visitor can move toward a useful conversation. GRC's Shopify website services connect website strategy, page architecture, implementation and handover. To review your requirements, bring this first map and Discuss your project.
