Most business websites are organised the way the business sees itself: Home, About, Services, Projects, Contact. Customers don’t move through a site like that. They arrive halfway through a decision, often on a deep page from Google, with one question to answer before they take the next step. Designing around the website customer journey means knowing those questions at each stage, and making sure a page answers every one and points somewhere sensible next.
You need a spreadsheet, Google Analytics, Search Console and an honest hour with whoever answers your enquiries. The method works for a new website or a redesign.
The short answer
To design a website around the customer journey:
- List your audiences by the decision each is making.
- Write down their questions at four stages: recognising the problem, comparing options, deciding, and after enquiring.
- Note where they enter the site at each stage.
- Map your pages to those questions to find gaps, overlaps and dead ends.
- Give every page a clear next step, plus a lower-commitment alternative.
- Plan for decisions made over several visits and by several people.
- Check the map against real behaviour with GA4 path exploration and sales conversations.
What a website customer journey map is (and isn’t)
In service design, customer journey mapping usually traces the whole relationship, from the first advert to renewal; a user journey map zooms in on one task, such as booking an appointment. Website planning needs something more specific: a map connecting each question customers ask to the page that answers it, and each page to the next step. It shapes your sitemap, navigation and calls to action, so it belongs before anything is designed.
Remember that journeys aren’t linear: people skip stages, loop back and return weeks later, often on another device.
The four stages in plain language
Buyer journey stages are often labelled awareness, consideration and decision. Plain labels work better, and a fourth stage catches what many websites forget.
| Stage | What the visitor is thinking | Pages that usually answer it |
|---|---|---|
| Recognising the problem | “Is this worth fixing? What are my options?” | Guides, articles, problem-led parts of service pages |
| Comparing options | “Which approach suits us? Who does this well? Roughly what does it cost?” | Service pages, comparisons, case studies, pricing |
| Deciding | “Can I trust them? What exactly do I get?” | Pricing, process, proof, FAQs, contact |
| After enquiring | “Did that go through? Who will reply, and when?” | Thank-you page, confirmation email |
How to map your website customer journey in seven steps
1. List your audiences by the decision they’re making
Your audiences should come straight from your website strategy, grouped by the decision they are making rather than by demographics. A manufacturer might serve procurement managers comparing suppliers, engineers checking specifications and distributors looking for a partner. Keep it to two to four primary audiences; job seekers and suppliers need a route, but shouldn’t shape the homepage.
Include the whole buying group. The person who finds you is often not the person who signs, so list everyone involved in the decision.
2. Write down the questions at each stage
For each audience, list the questions in their own words. Read your last 20 or 30 enquiries, ask whoever answers them what new customers always ask first, and scan the queries in Search Console’s Performance report.
Write questions, not topics. “Pricing” is a topic. “Can we afford the version we actually need?” is a question, and it tells you what the page must show: a price range per option, what drives the cost and what is included.
For a facilities manager planning a new factory building, it might look like this:
| Stage | Questions in the customer’s words |
|---|---|
| Recognising the problem | Design-and-build, or a separate architect and contractor? |
| Comparing options | Have they built factories this size? Can we see examples? |
| Deciding | What’s in the quote, and what isn’t? Who will be our contact? |
| After enquiring | What do they need from us before a site visit? |
3. Note where people enter the site
Entry points deliver visitors at different stages. Organic search brings researchers and comparers to articles and service pages; word of mouth often arrives through a search for your name, close to deciding; forwarded links drop a second decision-maker onto a deep page; AI assistants and AI search features may link to a page they drew on.
To see your front doors, open the Landing page report in GA4 (Reports › Engagement) and the Pages tab of Search Console’s Performance report. Click a busy entry page, then switch to Queries: “what is design-and-build” signals an early researcher, while your business name plus “reviews” signals someone close to deciding.
Any page can be someone’s first, so each entry page must make sense to a newcomer: what this is, who it’s for, why to believe it and where to go next. Our comparison of landing pages, homepages and service pages covers which page type suits each traffic source.
4. Map your pages to the questions and find the gaps
Bring it together in a spreadsheet, one row per question:
| Column | What to write | Example |
|---|---|---|
| Audience | Who is asking | Facilities manager |
| Stage | One of the four | Deciding |
| Question | In the customer’s words | “What’s in the quote, and what isn’t?” |
| Entry points | How they usually arrive | Forwarded link, return visit |
| Answering page | The page that answers it, or “none” | Design-and-build service page |
| Answer quality | Answered, partly or not at all | Partly: exclusions not listed |
| Next step | The main action from that page | Request a site visit |
| Smaller step | A lower-commitment alternative | Download a sample quote |
| Evidence | What analytics or sales show | Comes up in most first calls |
Sort by answer quality and look for four patterns:
- Gaps: questions no page answers. Price, process and “what happens after I get in touch” are the usual suspects.
- Dead ends: articles that simply stop, or a form that leads to a bare “Thanks”.
- Overlaps: three pages answering one question half-well. Merge them.
- Buried answers: the answer exists, but only in a PDF or on a page linked from the footer, which is often a navigation design problem.
Then walk each conversion path, from a typical entry page to an enquiry, on your phone, noting every moment you had to guess.
5. Give every page a next step, and a smaller one
A journey stalls when a page answers its question and stops. Every page needs a primary next step that fits the stage, plus a lower-commitment alternative. These smaller actions, such as viewing pricing, downloading a specification or starting a chat, are often called micro-conversions: they show a journey moving forward, and give people who aren’t ready to enquire something useful to do instead of leaving.
| Page type | Primary next step | Lower-commitment alternative |
|---|---|---|
| Guide or article | The related service page | A related guide or checklist |
| Service page | Request a quote or consultation | See pricing or a relevant case study |
| Case study | Discuss a similar project | Explore the related service |
| Pricing page | Ask for a quote | Compare what each option includes |
| Thank-you page | What happens next, and when | Something useful to read meanwhile |
Match the ask to the stage: an early-stage article offering only “Contact us” asks too much, too soon. Keep one primary action per page, with the alternative visibly quieter. Don’t gate the basics: an email wall in front of a price range costs more trust than it earns.
Our call-to-action best practices cover wording and design, and website lead generation covers the offers and contact channels behind them.
6. Plan for several visits and several people
Considered purchases rarely happen in one sitting. Someone finds you on their phone, forwards the link to a colleague, and returns a week later to compare you with two others.
Make pages easy to find again and forward. Clear titles and stable URLs let people bookmark and share what they saw, and a short summary at the top of long pages helps the colleague who missed the first visit.
Give each role a route to its answers. The person checking cost wants prices and terms; the technical lead wants specifications; the decision-maker wants proof. Our guide to B2B website design goes further into buying groups.
Keep the journey whole in every language. Members of one buying group may read different language versions, so each needs the full journey, not a cut-down translation of the homepage.
7. Validate the map with GA4 and your sales team
A journey map built in a meeting room is a hypothesis. Test it.
Path exploration. In GA4’s Explore section, a path exploration shows the routes people take. Start from a key entry page to see where visitors go next, or from an ending point, such as your enquiry event, to see what they viewed before it. If almost nobody reaches pricing before enquiring, your sales team is probably answering price questions on every first call.
Funnel exploration. Define the steps you expect (service page, pricing, contact form, submission) and see where people drop out between them. Both explorations depend on enquiries and micro-conversions being tracked as events; mark the important ones as key events so they also appear in standard reports (see tracking enquiries in GA4). Treat the numbers as directional: consent choices and ad blockers hide some visits, and small sites have small samples.
Sales conversations. Analytics shows what people did, not why. Any question sales still answers on every first call is a gap on the website. Ask a few recent customers what they read, who else was involved and what nearly stopped them.
Revisit the map every quarter; it becomes the backlog for ongoing conversion rate optimisation.
A buyer journey in practice
A property developer’s website we redesigned shows the method at work. The old site took nine seconds to load, broke on phones, and enquiries could only come by phone, with nothing tracked.
Buying a home maps closely onto the four stages: shortlisting projects, comparing units and prices, deciding whom to trust, then arranging a viewing. The redesign organised the site around the questions buyers ask, in the order they ask them: which project, which unit, and how much. Every project got its own page with floor plans and transparent pricing, plus an enquiry form and a LINE chat button, with every enquiry tracked in GA4.
Buyer enquiries rose 40% in the three months after launch, and load time fell from nine seconds to two. The journey work wasn’t the only change, and that is the point: a map tells you what each page must do, but pages still have to be fast, work on phones and be measured. Read what a property developer’s website needs for the buyer’s questions page by page, or the full case study.
A customer journey checklist for any website
Turning the map into a better website
If your map shows missing answers, weak next steps or absent tracking, fix them on the site you have. If the structure itself fights the journey, with navigation built around your organisation chart and templates that can’t hold prices or proof, patching rarely lasts.
That is when a website redesign, planned around your customers’ questions, earns its cost. We audit first, keep what already works and redirect every old URL to protect the search visibility you’ve built. For an outside view before you decide, ask for a free website audit: a plain-language report on your site’s speed, mobile experience, Google visibility, security and how easily visitors can get in touch, emailed within two business days.