How to Define Your Website Audience

A website cannot be clear to everyone at once. It needs to prioritise the people the business can genuinely help and give them the information required to make a decision. Defining an audience is therefore not a branding exercise. It determines the pages, examples, language, functionality and calls to action the website needs.

You do not need elaborate fictional personas with invented names and hobbies. You need evidence about real customer situations.

Begin with the customers the business wants

Review recent customers, enquiries and sales conversations. Identify which work was:

• profitable and operationally suitable;
• a good match for the team's skills;
• likely to be repeated or referred;
• completed without avoidable conflict;
• aligned with the direction of the business.

Do not define the website audience only by who has bought in the past. A business may want to stop attracting certain low-value or unsuitable work. The website should support the intended direction, provided the offer and evidence are real.

Group people by situation, not only demographics

Age, job title and location may matter, but buying situations are usually more useful for website planning.

Examples include:

• a homeowner dealing with an urgent fault;
• a director comparing suppliers for a planned project;
• a referred prospect checking credibility;
• a returning customer looking for support;
• a buyer who already knows the product specification;
• a beginner who needs the problem explained first.

Two people of the same age and income may need completely different pages because one is researching and the other is ready to act.

Describe the audience in practical terms

For each priority group, answer:

Audience questions that affect the website

Question	Why it matters
What are they trying to achieve?	Defines the page purpose and useful next step.
What do they already understand?	Sets the level of explanation and terminology.
What makes them hesitate?	Identifies evidence, reassurance and missing information.
What would make the business unsuitable?	Helps qualify visitors honestly and reduce wasted enquiries.
Where and when do they use the site?	Affects mobile design, urgency, location information and contact options.
Who else influences the decision?	Shows whether the content must support a partner, manager, finance team or technical reviewer.

Use evidence already available

Useful evidence may come from:

• questions asked in calls and emails;
• form submissions and booking notes;
• sales objections;
• customer-support records;
• reviews, including critical ones;
• search terms and landing pages in Search Console;
• on-site search queries;
• reasons quotations are accepted or declined;
• conversations with staff who deal directly with customers.

Treat analytics as one input, not a complete picture. A high-traffic audience may still be commercially unsuitable, while valuable referred prospects may appear in small numbers.

Define the primary and secondary audiences

Most small websites should have one primary audience and a limited number of secondary groups.

For example:

• Primary: owners of small retail businesses in the UK who need a straightforward replacement website.
• Secondary: office managers gathering options on behalf of the owner.
• Not a priority: start-ups seeking complex custom software or international enterprise procurement.

Stating who is not a priority is useful. It prevents the site from promising capabilities the business does not want to deliver.

Map questions to pages

Convert audience needs into website content.

From customer question to page requirement

Customer question	Possible page or component
Do you handle my type of problem?	A specific service page with scope, examples and exclusions.
Do you serve my location?	Clear service-area information, not a list of thin location pages.
Can I trust you?	Verifiable credentials, relevant work, genuine reviews and a transparent process.
What will it cost?	Prices, ranges, cost factors or an honest explanation of the quotation process.
What happens after I contact you?	A process section and useful form confirmation.
Is this suitable for a beginner?	Plain-language explanations and definitions near the decision point.

Choose language the audience understands

Use the customer's language without imitating every phrase literally. Explain specialist terms the first time they appear. Prefer concrete descriptions over internal labels.

For example, “We carry out a discovery phase” may mean little to a small-business owner. “We review your goals, existing content, required pages and technical constraints before proposing the structure” explains the actual work.

Do not simplify by removing important limitations. Plain English should make the decision clearer, not make the offer sound easier than it is.

Account for accessibility and confidence

People may use the website with different devices, connection speeds, reading confidence and access needs. Audience planning should therefore consider:

• clear headings and predictable navigation;
• readable text and sufficient contrast;
• keyboard access;
• useful labels and error messages;
• captions or transcripts where relevant;
• alternatives to phone-only or form-only contact where the business can support them;
• important information that does not depend on colour or hover.

These are not only technical concerns. They affect whether a real person can understand and complete the task.

Validate assumptions before committing

Speak to a small number of real customers or prospects. Show them a draft page or page plan and ask them to explain:

• what they believe the business offers;
• whether it seems relevant to them;
• what information is missing;
• what would stop them taking the next step;
• where they would click next.

Do not ask only whether they “like” the design. Preference is less useful than comprehension.

Create a concise audience statement

Use this format:

Our primary website audience is [specific group] who need to [task or outcome]. They usually arrive with [level of knowledge or situation], need evidence of [trust requirement], and should be able to [primary action]. We are not primarily targeting [excluded group or project type].

Keep this statement in the website brief. Use it to assess page ideas, examples, terminology and features. If a proposed section does not help the priority audience make a better decision, it may not deserve space in the first version.