Multi-audience website, part 1: information architecture and navigation in Drupal

14.07.2026

This is part 1 of a two-part guide to designing a multi-audience corporate website on Drupal. Part 1 covers audience research, navigation strategy, and content structure. Part 2 covers user journeys, smart contact forms, and content personalization.

A multi-audience website is a single site that has to serve two or more distinct user groups whose needs barely overlap. Consider a benefits company like Edenred Polska, whose site serves three audiences at once: businesses looking to buy gift and benefit cards, individuals who already hold those cards, and merchants who accept them. A prospective corporate buyer wants product comparisons and a quote. A cardholder wants to check a balance or find support. A merchant wants partnership terms and onboarding. Same homepage, three different jobs to be done.

Get the information architecture right and every visitor feels like the site was built for them. Get it wrong and all three groups share the same frustration: too much irrelevant content, no obvious path, and a navigation bar that speaks a language they don't use. This is the first post in a two-part series for Drupal architects, UX designers, and content strategists. Here we cover how to identify your audiences, choose a navigation strategy, and structure the content in Drupal. Part 2 covers user journeys, smart forms, and personalization.

The Edenred navigation redesign referenced throughout is a planned phase rather than a finished build, so treat the examples as an illustration of the problem and the options, not a case study of a shipped solution. The same client context appears in our posts on teaching clients to think in components and how we avoided a costly Drupal rebuild.

In this article:

How do you identify and define audience segments?
Which navigation strategy fits a multi-audience website?
How do you structure multi-audience content in Drupal?
How do you test your information architecture?

How do you identify and define audience segments?

Before you touch navigation or Drupal configuration, you need a clear, evidence-based picture of who actually uses the site and what each group is trying to accomplish. Guessing here is expensive, because every downstream decision about menus, URLs, and content inherits the mistake.

Start with three sources of truth, used together:

Stakeholder interviews. Sales, support, and account teams know the real audiences because they field their questions every day. They will tell you which groups exist, which are most valuable, and where each gets stuck.
Analytics. Entry pages, top content, search queries, and exit points reveal how groups already behave, regardless of how anyone intended the site to be used. Look for clusters: support-style queries, product-research patterns, partnership pages.
User research. A handful of interviews or surveys with real members of each group surfaces the language they use and the tasks they care about, which rarely matches your internal vocabulary.

From these, build a short profile for each audience that answers three questions: who are they, what do they need, and what single action should they take? For Edenred's three groups that might be: business buyers (need product and pricing clarity, action: request a quote), cardholders (need account help and resources, action: self-serve support), and merchants (need partnership terms, action: apply).

Then map content to audiences. Go through the existing site and tag each page by which group it serves. This quickly exposes two important categories: audience-specific content that belongs to exactly one group, and shared content that serves several. The split matters because it determines whether you separate audiences structurally or route them through shared pages.

Finally, set a priority hierarchy for when audiences conflict. Screen space and homepage attention are finite. Decide up front which group leads when you can't serve everyone equally, usually the highest commercial value or the largest underserved segment. Without an explicit priority, the homepage becomes a committee compromise that serves no one.

Navigation is where multi-audience design succeeds or fails, because it is the first decision every visitor has to make. There are three viable strategies, and the right one depends on whether your users can confidently say which group they belong to. Most enterprise sites end up with a hybrid, but you need to understand each option before you combine them.

The primary menu names the audiences directly: "For business" / "For cardholders" / "For partners." Each label leads to a dedicated section with its own content and calls to action.

The strength is clean self-identification and tidy content separation. Visitors who know their category click once and land in a section built for their tasks. The weakness is the visitor who doesn't know their category, or who belongs to two. Someone who isn't sure whether they're a "business" or a "partner" stalls at the very first choice, which is the worst place to lose them.

The primary menu is organized by topic, such as products, solutions, and resources, and audience becomes a filter or tag inside each section. A resources page, for example, can be filtered to "cardholder" or "merchant" content.

This works well for people who think in topics rather than identities, which is most users searching for a specific thing. The trade-off is that it depends on a well-designed internal taxonomy: the filtering is only as good as the tags behind it, and a sloppy taxonomy produces confusing or empty results.

Strategy 3: the hybrid approach

In practice, the strongest answer for most multi-audience sites is a hybrid. Keep the primary navigation topic-based so it works for searchers and people who don't self-identify, then add audience-oriented entry points where they help: secondary navigation, audience landing pages, and hero sections that invite self-identification ("I want to buy cards for my team" / "I'm a cardholder" / "I accept Edenred cards").

The hybrid acknowledges the core reality of Edenred's challenge: users can't always easily place themselves in one of your internal categories. The buyer and the cardholder may not think of themselves in those terms at all. A hybrid gives confident users a fast lane while never blocking the rest behind a category choice they can't make.

How do you structure multi-audience content in Drupal?

Once the strategy is set, Drupal gives you a clean toolkit for implementing it. The central architectural decision is whether to separate audiences by content type or by taxonomy.

Content types versus shared types with audience taxonomy. Resist the temptation to create a separate content type per audience ("business page," "cardholder page," "merchant page"). That triples your maintenance and fragments shared content. The more scalable pattern is a small set of shared content types (page, article, resource) plus an audience taxonomy vocabulary that tags each piece with the group or groups it serves. One content model, flexible audience targeting.

Taxonomy design. Plan at least three dimensions: audience (business, cardholder, merchant), content category (product, support, partnership, resource), and product type where relevant (meal cards, gift cards, reward cards). Keep each vocabulary broad enough to be useful and narrow enough that editors can tag consistently without a manual.

URL structure. Decide between audience-based paths (/business/..., /cardholders/...) and topic-based paths (/products/..., /support/...). Audience-based URLs reinforce a strategy-1 or hybrid structure and read clearly, but they force you to pick one audience per page, which breaks down for shared content. Topic-based URLs are more flexible for shared pages but lean on navigation and filtering to convey audience. Match the URL strategy to the navigation strategy rather than choosing them independently. When audiences also need separate domains or subdomains, see our guide to multisite, Domain Access, or headless setups in Drupal.

Menus. Drupal's menu system supports the hybrid model directly: a main menu organized by topic, optional audience menus for dedicated sections, and contextual or secondary menus within each area. Keep the main menu short; depth belongs in section navigation, not in the global header.

Views for audience-specific listings. Use the Views module to generate dynamic, audience-filtered listings without custom code: "all resources tagged cardholder," "all partnership documents for merchants." Because the listings read from the audience taxonomy, they stay current automatically as editors tag new content, and they power the filtering that makes strategy 2 and the hybrid work.

This combination, shared reusable components plus an audience taxonomy plus Views, lets one Drupal site present genuinely different experiences to different groups while keeping a single, maintainable content model behind the scenes. When one audience needs gated files or a partner login area, the same segmentation logic extends into a Drupal extranet without rebuilding the content model.

How do you test your information architecture?

An information architecture is a hypothesis until real users from each audience confirm it. For a multi-audience site, testing matters even more, because a structure that feels obvious to a business buyer can be opaque to a cardholder. Validate before launch and keep measuring after.

Card sorting tells you how each audience naturally groups your content. Run it with real participants from every segment, not just internal staff, because internal teams have absorbed the company's own categories. Where business buyers and cardholders sort the same content differently, you've found a place the hybrid navigation needs to bridge.

Tree testing checks the reverse: given your proposed menu structure, can a user from each audience actually find the content they need? Give participants realistic tasks ("find out how to order meal cards for your employees," "check your card balance," "apply to accept the cards") and measure success and the paths taken. Failed tasks point straight at the labels and groupings to fix.

Analytics review grounds the testing in real behavior. After launch, examine where each audience segment enters and exits, which navigation paths they take, and where they drop off. Segment the data by audience; a healthy overall conversion rate can hide one group struggling badly.

Iterative refinement ties it together. Information architecture for a multi-audience site is never finished at launch. Treat the first structure as version one, watch how the three groups actually move through it, and adjust labels, menus, and taxonomy based on evidence rather than opinion. The goal is steady improvement in how efficiently each audience reaches its one key action.

Planning a multi-audience website on Drupal?

This series draws on our work with a multinational benefits company whose Drupal site has to serve business buyers, individual cardholders, and merchant partners from a single platform, where a navigation and information-architecture redesign is part of the planned next phase. The principles here, evidence-based audience profiles, a hybrid navigation strategy, and a shared content model driven by an audience taxonomy and Views, are how we approach that kind of complexity.

If your site is trying to serve several distinct audiences and none of them feels fully at home, the fix usually lives in the information architecture, not the visual design. Our team specializes in structuring complex Drupal sites so each audience finds its path quickly. Visit our Drupal development services to talk through your own multi-audience challenge. Continue to part 2 for user journeys, smart contact forms, and content personalization per audience.