A website strategy decides whether a new site grows the business or simply looks better than the old one. Yet most website planning starts elsewhere: a competitor’s homepage someone admires, a new logo, the old menu copied across. The questions that matter come later, if at all. Who is the site for? What should they do? How will anyone know it worked?
A strategy answers them first, in writing, before anyone designs a page. This guide takes each decision in turn and ends with a one-page template to fill in before you commission a new site or a rebuild.
The short answer
A website strategy is the set of decisions that tie a website to business outcomes: who the site serves, what it must get them to do, and how you will know it worked.
A simple website strategy framework breaks that into six decisions, taken in this order:
- Role. The site’s main job in the business.
- Audiences. The groups that matter most, and the questions they need answered.
- Actions. What each audience should do next, and what counts as qualified.
- Content and languages. The pages, proof and languages needed first.
- Measures and owners. The numbers you track, and who is responsible.
- Roadmap. What launches first, what follows, and how the site keeps improving.
A good website strategy fits on one page. If yours runs to twenty, it has turned into a brief or a project plan.
What a website strategy is, and what it isn’t
Strategy is the first of the ten ingredients of a good website because the other nine, from UX and design to SEO and conversion, aim at the audiences, actions and measures it sets. Without that shared target, each specialist optimises for something different: the designer for looks, the developer for features, the SEO for traffic.
It isn’t a sitemap, a look or a feature list. Those come later, in the documents that follow it:
| Document | What it answers | When it’s written |
|---|---|---|
| Website strategy | Why the site exists, for whom, and what success means | Before anything else |
| Website brief | What you want providers to plan, build and price | Before you ask for proposals |
| Discovery | What the evidence says about users, content and technical limits | At the start, before design begins |
| Project plan | Who does what, in which stage, by when | Once a provider is chosen |
The website brief turns the strategy into something a provider can quote.
Decisions 1 to 3: who the site serves and what they should do
1. The site’s role in the business
Most business website goals come down to one of a handful of jobs, and each job leads to a different site.
| Main job | Typical business | What it changes |
|---|---|---|
| Win new enquiries | Professional services, B2B, construction | Service pages built for search, clear calls to action |
| Take bookings or orders | Clinics, hospitality, retail | A short path to book, visible prices and availability |
| Reassure and qualify | Referral-led firms, high-value sales | Detailed proof, process pages, fast contact |
| Support a sales team | Property, manufacturing, education | Pages salespeople can send, answers to repeat questions |
Pick one main job and at most one secondary job, then write it as a single sentence: our website exists to [job] for [audience], so that [business outcome]. For example: “Our website exists to win qualified enquiries from companies planning a new factory, so that our sales team spends its time on real projects.”
Also name the processes the site must feed, such as enquiries into a CRM or bookings into a calendar. For many businesses the website is where customers first ask, book or leave their details, which makes it a practical starting point for digital transformation in a growing business.
Check it yourself. Look at your last 20 new customers. How did each first hear of you, and did they visit the website before getting in touch? Mostly search means the site’s job is to be found. Mostly referrals means its job is to reassure.
2. Priority audiences and their questions
Define audiences by what they are trying to decide, not by age brackets or invented personas. A manufacturer might list procurement teams comparing suppliers, engineers checking specifications and overseas distributors seeking a partner. Put them in order, so that when two audiences want different things from the homepage, the strategy has already said who wins.
For each priority audience, list the questions they need answered before they act, in their words. The best sources are close to hand:
- The questions your sales team hears on every first call
- The reasons you lost deals you expected to win
- The queries in Google Search Console’s Performance report
- Messages from customers who nearly didn’t buy
Those questions become your content plan and navigation. They matter for search too: a page that answers a real question plainly is easier for search engines and AI assistants to match and to quote. Mapping them along the website customer journey shows which page should answer each.
3. Key actions
Choose one primary action per audience, such as requesting a quote, and a lighter one for people not ready yet, such as downloading a capability statement. Offer the channels your customers actually use, from forms to calls to chat apps, and decide who replies and how quickly.
Then define a qualified action. Ten enquiries from outside your service area are worth less than two from buyers with a real project. Writing down what qualified means (budget, location, timing, type of project) keeps everyone optimising for the right thing and tells your forms which questions to ask.
Conversion rate optimisation turns these actions into a steady flow of enquiries; the strategy makes sure you optimise the right ones.
Decisions 4 and 5: what the site says and how you’ll know it worked
4. Content and language priorities
Give every priority question a home: a service page, a pricing explanation, a project page or an FAQ. Any existing page that answers no priority question and supports no key action is a candidate to cut or merge.
Plan the proof early. Project write-ups, photographs of your own work and certifications take longest to produce and persuade most. List what you have, what you need and who will create it; a website content plan turns that list into a schedule.
Choose languages deliberately. Serve the languages your customers use when they search and decide, not only the one your team works in, and decide which pages need every language. Each version needs its own indexable pages, titles and search optimisation, as planning a multilingual website explains. A translate button is not a language strategy.
5. Measures and owners
For each key action, choose one business measure and record a baseline, such as qualified enquiries per month or the share that become sales. Add a few diagnostic numbers that explain movement: conversion rate on key pages, clicks from non-brand searches, Core Web Vitals results. Website KPIs explains which numbers matter and which are vanity.
Set up tracking on the current site now, even if you plan to replace it: form submissions, phone taps and chat clicks recorded as key events, GA4’s term for conversions. GA4 conversion tracking shows how. Without a baseline, nobody can say whether the new site worked.
Then name owners. An owner is a person, not a department:
| Area | What the owner does |
|---|---|
| Strategy | Signs off this page and settles conflicts |
| Content | Keeps each section accurate and current |
| Enquiries | Makes sure every enquiry gets a reply, on time |
| Numbers | Reviews the measures monthly |
| Technical care | Keeps updates, backups, security and access in order |
If you can’t put a name next to a row, that work won’t happen after launch.
Decision 6: plan a website roadmap, not a launch date
Treat the website as a product that keeps improving, not a project that ends at launch. Launch is version one: the smallest site that does its main job well. The roadmap decides what follows.
| Stage | What it typically includes |
|---|---|
| Launch | Priority pages in priority languages, proof, tracked enquiry routes, speed and SEO foundations |
| Next | Fixes based on real data, more project pages, remaining languages or sections |
| Later | Booking or CRM integrations, self-service tools, an AI assistant once its source content is solid |
Keep the “later” column honest. Features move forward when the numbers or your customers justify them, not because a competitor added them.
Then set a rhythm, checking the measures monthly and the site against the strategy each quarter, and budget for it from the start. A site nobody works on soon falls behind the business. Continuous improvement keeps it current in small, lower-risk steps instead of a disruptive rebuild every few years.
A one-page website strategy template
Copy this into a document and fill in the middle column. The right-hand column shows a hypothetical construction firm.
| Decision | Your answer | Example |
|---|---|---|
| Role | Our website exists to … for … so that … | Win qualified enquiries from companies planning a new factory |
| Priority audiences | 1. … 2. … 3. … | Operations directors, procurement teams, consulting engineers |
| Their top questions | Five per audience, in their words | “Have you built something like ours?” “How do you control cost overruns?” |
| Key actions | Primary, plus one for people not ready yet | Request a consultation; download the capability statement |
| Qualified means | Location, size, timing, budget | A confirmed site and a start date within a year |
| Content priorities | Pages and proof needed first | Sector pages, three detailed project pages, a process page |
| Languages | Which languages, for which pages | Every key page in each language its buyers use |
| Measures | Business measure, baseline, direction | Qualified enquiries per month, against last year’s count |
| Owners | A name per area | Sales director signs off; marketing manager owns content |
| Roadmap | Launch, next, later | Core pages; project stories; CRM connection |
Blank rows show what to settle first. Most get answered in a website discovery phase, where analytics, customer questions and existing content are reviewed before design starts and the price is fixed.
Frequently asked questions
How is a website strategy different from a digital marketing strategy?
A digital marketing strategy covers every channel, from search and social media to email and advertising. A website strategy covers the site’s role within it. Most channels send people to the website, so the two must agree on audiences and actions, or campaigns pay for traffic the site can’t convert.
Who should write the website strategy?
The business should own it: someone senior enough to settle disagreements between departments, with input from the people who talk to customers. A good web partner will test and sharpen it, but can’t invent your business goals.
Does a small website need a strategy?
Yes, just a shorter one. A five-page site still has a job, an audience and an action that counts as success. Small sites often gain the most, because every page has to earn its place.
How often should you review a website strategy?
Compare the site with it every quarter. Rewrite the strategy itself when the business changes, such as a new service, a new market or a different kind of customer, and question it if the key numbers stay flat for two quarters despite changes to the site.
What to do next
Fill in the template, even roughly. Then read why website projects fail: most causes, from unclear goals to nobody owning the site after launch, trace back to the decisions above. The Strategy & Planning hub lists every guide in this series.
When you are ready to build, our website design and development work starts from these decisions and turns them into structure, content, design and SEO that pull in one direction. Bring your one-page strategy, or the rows you couldn’t fill in, to a free 30-minute consultation and we’ll work through the gaps with you.