A worried parent and a practising clinician land on the same homepage. One wants a plain answer, fast. The other wants the evidence, the guidance, the detail. Serve one well, and you usually let the other down. That is the problem many organisations live with, and it doesn’t need a second website to fix.
Professional bodies, charities, universities and public sector organisations run into this more than most. A royal college speaks to the public and to its members. A charity speaks to people in crisis and to the professionals who refer them. A university speaks to a nervous applicant and to the academic they will study under. Same organisation, same content library, two people who could not be more different in what they need and how they read.
The dual-audience trap
The trade-off is to pick a side. You design for the audience you talk about most in meetings, and the other one makes do. Or you try to please both at once and produce a homepage that is a committee in web form: a bit for everyone, a clear path for no one.
A third option is to split the site in two. A public site and a professional portal, separate front doors, separate teams looking after each. Sometimes that is the right call. More often, it doubles your maintenance, splits your search authority, and creates the awkward moment when a professional reads a public page (or the reverse) and finds it was written as if they don’t exist.
None of these is a proper design decision.
Start with the journeys, not the content
The mistake is thinking the two audiences need different content. Usually they need the same underlying subject approached from a different angle, at a different depth, with a different first step.
Take a health condition. The public wants to know what it is, whether they should worry, and what to do next. A professional wants clinical guidance, referral criteria, and the latest position statement. That is one topic and two journeys, not two topics.
So map the journeys first. For each audience, write down what they arrive worried about, what a good outcome looks like for them, and the single next step you want them to take. Do that honestly and the site almost designs itself, because you stop asking “where does this content go” and start asking “who is this moment for”.
Let people self-select early, without a wall
Once you know the journeys diverge, give people a way to say which one they are on. Early, obvious, and low-commitment.
This does not mean a splash screen demanding “Are you a member or not?” before anyone can get in. Those get clicked through at random and teach you nothing. It means designing entry points that speak plainly enough that people recognise themselves. A public visitor should see language and a first step that fit their world. A professional should find their way to depth without wading through introductory material written for someone else.
The test is simple. Can each person tell, within a few seconds, that a path shaped for them exists here? If they cannot, they might assume the site is for the other lot and leave.
The same word means different things
Here is where dual-audience design gets tricky, and where most sites come unstuck. The two audiences often use the same words to mean different things, and different words to mean the same thing.
To the public, “referral” might mean, “How do I get seen?” To a professional, “referral” means the criteria and the form. Search for “assessment”, and a parent wants to know what will happen to their child; a clinician wants the assessment tool. If your search treats those as one query and returns one blended list, both people scroll past the half that isn’t for them and will likely conclude you don’t have what they came for.
So you have to design the vocabulary, not inherit it. Write down the terms each audience actually uses, in their own words, and map them to your content. Then make your navigation and your search respect the difference: same term, but the results and the labels bend toward whoever is asking. Meet people in their own language and the site feels like it understands them. Force them to learn yours, and you have added a tax to every visit.
We did exactly this for the Royal College of Speech and Language Therapists. The RCSLT website serves the public and the profession from a single content library, and the vocabulary problem above is theirs in miniature: the same search term means one thing to a worried parent and another to a practising clinician. We ran the user research and redesigned the information architecture, the navigation and the search around those two journeys rather than around the organisation’s internal structure, so each audience can reach the depth it needs without the other’s content being walled off.
Search and navigation that respect both
Navigation is where the two journeys either stay clean or collapse into mush. A few things that hold up in practice:
- Label by intent, not by internal structure. Your org chart is not a menu. “For professionals” beats a department name nobody outside the building recognises.
- Keep the shared spine, branch at the leaf. Common subjects can share a top-level home, then split into a public explanation and a professional resource lower down. One tree, two branches, no duplicated maintenance.
- Make search context-aware where appropriate. If someone has clearly entered a professional area, weight their results accordingly rather than dropping them back into a general pool.
- Signpost across, do not trap. A professional should be able to reach the public explanation to share with a client, and a public visitor should never hit a locked door with no explanation. Divergent journeys, porous walls.
The point is not clever technology. It is judgement about who is asking and what they are actually trying to do.
When splitting really is the right answer
Sometimes two sites is the honest choice. If the professional audience needs authentication, member-only tools, transactions or data that has no business sitting near the public content, a separate application makes sense. If the two audiences share almost no subject matter, forcing them under one roof helps nobody.
The rule of thumb: split when the content, access model, or maintenance diverge. Do not split just because the two audiences feel different. Feeling different is a design problem, and design solves it more cheaply than a second site you have to run forever.
The payoff
Get this right and something useful happens. Each audience feels the site was built for them, which builds trust before you have said a word about who you are. Your content works harder because one well-structured library serves two journeys instead of two half-maintained libraries serving one each. And the people running the site stop refereeing the endless “but what about our audience” argument, because the answer is built into the structure.
It is careful work. Mapping journeys, designing vocabulary, and getting search to behave is not glamorous, but it is the difference between a site that serves everyone reasonably and one that serves nobody quite well enough.
If you are wrestling with a site that has to speak to two very different audiences, we are happy to talk it through. A free 30-minute call, no pitch, just a look at where the friction is and what would help.