Websites with Two Distinct Audiences: Resolving Competing User Journeys Before Drawing the First Layout

A website serving two distinct audiences needs an agreed route for each before the first layout is drawn. Start with what each visitor wants to accomplish, which information they need and where their next step differs. Then decide which pages can be shared and where a separate route earns its place.

This is a common planning problem for businesses working with both private clients and professional partners, or with buyers and suppliers. Giving both groups a homepage button can help, but only after the destinations and their content make sense. The following process turns those decisions into a brief that a designer can use.

Describe the tasks behind the audience labels

Write down why each group arrives, what they already know and what they need to decide. “Homeowners” describes a group; “check whether this studio can help renovate an occupied home” describes a task. The second statement gives you something to organize content around.

Collect evidence from suitable enquiries, recurring questions and conversations with people who use the site. Remove personal details from examples shared in the brief. Team opinions can suggest useful questions, but mark them as assumptions until you have checked them with likely visitors.

GOV.UK’s guidance on learning about users and their needs recommends understanding what people are trying to do and grounding needs in research. Applied to a business website, that means investigating the task before deciding that two internal customer segments require two public sections.

Also record overlap. An architect may be researching a supplier for a client and planning their own home improvement. A visitor can belong to both audiences. Your structure needs to support movement between routes without asking people to choose a permanent identity.

Map two complete journeys on one page

Use a small table to describe the route from arrival to a useful next step. Include likely entry pages: visitors may land on a project or service page without seeing the homepage.

This fictional example concerns a lighting studio serving homeowners and interior designers. It illustrates a planning method, not an existing client project or measured result.

Decision	Homeowner planning a renovation	Interior designer specifying a project
Starting question	Can you help me choose lighting for my home?	Can you support the specification and supply process?
Likely entry	Residential service page or project	Specification guide or professional service page
Information needed	Scope, process, examples and how advice begins	Technical documentation, responsibilities and project coordination
Relevant evidence	A residential project with an explained brief	A project showing the studio’s actual contribution to a specification
Next step	Send an outline of the home and intended work	Send a project brief and the documentation required

Now examine the gaps. If both routes end at “Get in touch,” clarify what each person should send and who will respond. If a page is shared, make sure its opening explains enough for someone arriving from either direction.

The table should expose content you need to collect before design starts. An empty evidence column cannot be solved by giving a card a more prominent position.

Separate shared content from audience-specific decisions

Some information belongs in one place: the business introduction, a common process, general contact details or a project relevant to both groups. Other information changes materially by audience, such as the available service, required documents or way an enquiry is handled.

Keep a shared page when the answer is substantially the same. Link to the relevant section or add a short introduction explaining why it matters to that route. Create a separate page when the visitor needs a different explanation, evidence or next action. Rewording the same paragraph twice rarely creates a useful distinction.

Where service names are causing the split, first resolve overlapping service labels. Two teams using different names for the same offer may need clearer terminology rather than separate journeys.

Where audiences need different proof, curate different entry points into the work. A single case study can support both routes if it explains the project clearly. The guide to organizing a growing portfolio shows how to keep one project record while presenting relevant selections.

Choose the point where the journeys separate

Audience choice belongs where it helps people predict the next page. Sometimes that is the main navigation. Sometimes a service overview gives visitors enough context before presenting two routes. A homepage split is useful only when the distinction is understandable immediately.

Consider these three patterns:

• Audience routes: useful when people recognize the labels and the offer differs substantially, such as separate information for private clients and professional partners.
• Task routes: useful when identity overlaps but the actions are distinct, such as discussing a new project or requesting technical information.
• A shared overview with contextual branches: useful when visitors first need the same explanation, then choose the detail relevant to them.

Avoid a mandatory entry screen that hides the rest of the website behind an audience choice. Give people a clear way to explore the other route, and make deep links understandable on their own. The website navigation planning guide explains how main routes and contextual links can support one another.

Do not confuse audience selection with location selection. If both groups can use several branches, that is a separate decision. Plan shared and local information across multiple locations so a visitor does not have to guess whether a branch also determines their customer category.

A language choice needs its own plan: two languages do not automatically mean two different audiences. The guide to bilingual website language switching explains how to pair equivalent pages, preserve the visitor’s task and handle content that is not yet translated.

Agree priority without making one route disappear

Two audiences do not automatically need equal space everywhere. Agree the main commercial purpose of the page and the consequences of making another route hard to find. Document that choice before discussing which card should be larger.

For example, a business may primarily seek new client enquiries while maintaining an important partner route. The homepage can lead with the client offer and provide an explicit partner link. The partner page should still be complete, easy to reach and useful when shared directly.

Write a short decision statement for the brief: “The homepage introduces residential lighting advice first; professional specification support remains visible in the main navigation and has its own overview.” That is a decision the team can review. “Make it work for everyone” leaves the designer guessing.

Keep calls to action specific to the destination. “Discuss a home project” and “Ask about specification support” explain more than two identical buttons labelled “Start.” Use the business’s actual vocabulary and response process when writing the final copy.

Different journeys may reach different people. Before adding profile links, clarify those responsibilities with the guide to explaining team roles to website visitors, including when a shared enquiry route is the clearer choice.

Test the routes before testing visual polish

Prepare a plain page outline or linked text prototype. Ask likely visitors from each audience to complete a realistic task, including someone whose needs cross the boundary. Avoid telling them which audience label to choose.

Useful prompts include: “You are comparing suppliers for this project. Where would you look first?” and “What would you expect to happen after following this link?” Observe the route and ask what information is still missing before contact.

Record the distinction between a misunderstood label, missing content and an unclear next step. Each suggests a different revision. The guide to testing first-time visitor comprehension provides a practical way to capture observations without treating a small review as a statistical experiment.

Repeat key tasks from a direct service-page entry and a project-page entry. During implementation, check the same routes on a narrow screen and with keyboard navigation. A successful desktop homepage choice does not establish that the whole journey works.

Turn the decisions into a layout brief

Hand over the audience tasks, entry points, proposed page list and the purpose of each destination. Mark shared content, audience-specific information, missing evidence and the person responsible for supplying it.

Add the proposed labels, CTA wording and routes back to shared pages. Include unresolved questions explicitly. If nobody knows whether partners use the same enquiry address, confirm the process before designing two contact treatments.

The brief is ready for layout when each priority task has a plausible starting point, the content needed to progress and an honest next action. Visual design can then establish hierarchy, rhythm and emphasis around agreed decisions.

Common questions

Does a website with two audiences need two homepages?

Usually you can start with one clear homepage and distinct destination pages. Separate homepages or sites need a stronger reason, such as substantially different offers and separately maintained content. Test whether a shared introduction and visible routes already meet the need.

Should visitors have to choose their audience before browsing?

Only make a choice necessary when it changes what they can meaningfully do. For a public business website, visible routes and an easy way to switch are often more helpful than a compulsory gate, especially when a person belongs to both groups.

Can both audiences share the same contact page?

Yes, if it explains what each should send and how the enquiry is handled. Distinct links can lead to that page with clear context. A separate contact page is useful when the response process or information required genuinely differs.

Plan your website journeys with SavianoDesign

SavianoDesign’s Web Design service connects audience needs, content structure and responsive layouts as part of a complete homepage or website project.

Explore the Web Design portfolio and contact Francesco about your website. Share your current site, the two audiences you serve and a few typical questions from each. That provides a useful starting point for agreeing the pages, design and any front-end implementation.