# Every Page Has a Purpose: Engineering Websites That Educate, Persuade and Convert

B2B buyers tend to need answers to the same questions. A working hypothesis for a reusable website blueprint, where every page has a defined job.

Every few years, a business commissions a new website. A team gathers requirements, debates the sitemap and asks someone to write the About page.

Then the next business does the same. And the next.

Yet the people visiting B2B websites are trying to answer much the same questions:

- What does this business do?
- Is it relevant to my circumstances?
- Does it understand my problem?
- How does its work happen?
- Why should I trust it?
- What happens if I get in touch?

If the questions recur, the structure that answers them could recur too. That is the hypothesis this article explores.

Most B2B businesses may share enough communication requirements to support a reusable website blueprint. Each business would then adapt it to suit.

Standardising the logic is different from standardising the look. Two houses can both have a front door, a kitchen and somewhere to sleep, and still look nothing alike.

## A website is a communication system

Page names describe content. They rarely explain why a page exists.

An About page is often treated as a home for company history. Its job is to establish credibility and communicate the business's point of view.

A case study describes a completed project. Its job is to provide evidence that the business can deliver an outcome.

Even a glossary has a persuasive role. It helps customers understand unfamiliar concepts, so they can make a more informed decision.

That leads to a principle:

> Every page should have a job. Every content block should contribute to that job.

A page can do more than one job. A case study builds trust and shows how a business works. But if nobody can name a page's job, that is worth investigating.

We approach websites the way an engineer approaches any system: define what each part must do, then build it. We've written before about [treating each page as a persuasive document](/blog/your-website-is-a-persuasive-document/). Purpose comes first, and the argument follows from it.

## The homepage is the clearest example

The homepage is often briefed as a summary of the business. In practice, it does several jobs at once:

- It establishes the business's central idea.
- It sets an emotional starting point that suits the business and its customers.
- It tells visitors where they are.
- It offers paths to explore, based on what the visitor is trying to do.
- It directs people towards the information relevant to their circumstances.

One more job tends to go unnoticed. The homepage is a reset.

When a visitor gets lost three pages deep, they click the logo. They go home to start again.

[In an earlier article](/blog/your-homepage-should-suck/) we argued that the homepage is for orienting, not persuading. The reset extends that idea. People return to it whenever they need to reorient, not only when they first arrive.

That makes the pathways the most important part of the page. Visitors might explore by industry, business size, problem, desired outcome or service.

The right pathways come from how customers think about their situation. A buyer rarely frames a problem the way a company's org chart does.

Our own homepage tries this. Its routes are written in the visitor's words, such as "I need a website" and "I need to be found".

## From buyer journeys to interconnected knowledge

The marketing funnel is a useful model. It describes how a customer moves from awareness to consideration to decision.

We've used it to [give each page a role in the customer journey](/blog/structuring-your-website-for-purpose-and-performance-a-funne/). That still holds. But nobody experiences a website in one prescribed sequence.

A prospective customer might arrive through a case study and read a glossary definition. Then they look at a service, visit the About page and leave. Three weeks later, they come back through a search result.

Research points the same way. Google's study of purchase decisions found that people ["loop through these twin modes of exploration and evaluation"](https://business.google.com/us/think/consumer-insights/navigating-purchase-behavior-and-decision-making/), repeating the cycle as often as they need.

B2B buying shows a similar pattern. In [Gartner's research](https://www.gartner.com/en/sales-service/insights/buyer-enablement), 95% of buying groups reported revisiting decisions at least once as new information emerged.

So a website works better as a network of connected information than as a single line.

A case study links to the service that delivered it, the industry it belongs to and the problem it solved. It also links to the people who did the work. Each link is a relationship a visitor can follow, in whatever order suits them.

The distinction worth keeping:

- **The buyer journey** describes how a customer's understanding and intent change over time.
- **The website architecture** describes the information, and the relationships between it, that support those changes.

Both are useful, and they answer different questions. One name for the second is a knowledge graph. The name matters less than designing the connections deliberately.

## The case for a reusable blueprint

If pages are defined by purpose, a first version of the blueprint looks like this. It is a starting hypothesis, not a claim that every B2B website needs every page.

| Page type | Primary communication role |
|---|---|
| Homepage | Orient, establish the central idea and guide exploration |
| Problems and needs | Demonstrate understanding and relevance |
| Services | Explain how the business delivers value |
| Who we help | Establish contextual relevance |
| How it works | Reduce uncertainty about engagement and delivery |
| Case studies | Provide evidence and demonstrate capability |
| About and people | Establish credibility, identity and trust |
| Insights and resources | Educate and develop understanding |
| FAQs and glossary | Resolve questions and clarify concepts |
| Contact and enquiry | Make the next action clear and easy |
| Legal and policies | Communicate obligations and build transparency |

The roles are the useful part. A business might combine problems with its services pages, or fold "How it works" into each service. The page can move. The job still needs doing somewhere.

Standardising these requirements does not standardise a business's personality. The blueprint says a visitor needs evidence. It doesn't say what that evidence is, how it is told or what it looks like.

The next step is to define the content requirements inside each page. Then the model needs testing against real businesses.

## From conversations to content

This is where a blueprint becomes practical. If we know what information a persuasive website needs, we know what to ask for.

Website projects often slow down at the same point. The client is asked to write their About page, or supply copy for each service.

That is a hard request. Most people know their business deeply and still find it difficult to write about.

A blueprint turns that request into a set of conversations. Each person in the business holds different knowledge:

| Who | What they know | Where it goes |
|---|---|---|
| CEO or founder | The central idea, the point of view, where the business is heading | Homepage, About |
| Sales team | The questions prospects ask, their objections, why deals are won | Services, FAQs, problem pages |
| Customer service | What confuses customers after they buy | Glossary, FAQs, resources |
| Delivery managers | How the work happens day to day | How it works, case studies |

That knowledge can be organised into a content model: a structured record of what the business knows, mapped to the pages that need it. Writers then turn it into clear, customer-facing copy.

Over time, the same model supports continuous improvement. When sales hears a new objection, it has somewhere to go.

Website content becomes something maintained, rather than something rewritten every few years.

## Start simple, then evolve

There is a temptation to over-engineer this.

The longer-term ambition is a system where structured conversations with a business produce an accurate model of it. The website's content and architecture would then emerge from that model.

That may be where this ends up. It isn't where to start.

The practical starting point is a useful B2B content template. Give every page a clear purpose, and use it to build better websites now. Then test it against real projects and improve it.

The underlying idea is straightforward. A website shouldn't only hold information about a business. It should organise that information around what customers need to understand to make a decision.

We'll keep testing the blueprint and write up what we learn, including the interview process and the deeper model behind it. If you try it on your own website, we'd like to hear where it holds and where it breaks.

## Sources

- [How people decide what to buy lies in the 'messy middle' of the purchase journey](https://business.google.com/us/think/consumer-insights/navigating-purchase-behavior-and-decision-making/) — Think with Google, 2020
- [Buyer Enablement](https://www.gartner.com/en/sales-service/insights/buyer-enablement) — Gartner