DIRECT ANSWER
A website serves several customer types for one service by separating what changes from what stays the same. The business's identity, credentials, process and contact details are written once as a shared foundation. Each customer type gets its own entrance, named by situation, with the questions, examples and proof that apply to it. Every entrance leads to one intake that records which situation applies.
Key terms
- Customer type
- A group of customers whose situation, questions or decision differ enough from others' to change what a website must show them. Two groups that share the same decision, questions and next step are one customer type for website purposes.
- Situation entrance
- A link or page that opens a customer type's pathway by naming the visitor's situation in their own words, such as "I just bought my second rental."
- Customer pathway
- The route one kind of visitor takes through a website, from the page where they arrive to a next step with the business. Full entry: How Many Customer Pathways Does Your Website Need?
- Convergence point
- A page, form or tool where more than one pathway ends, such as a single intake that records which situation the visitor came from. Full entry: How Many Customer Pathways Does Your Website Need?
What changes and what stays the same
A business that sells one service to several kinds of customers asks its website to do two jobs. Each customer needs to see that the business understands their situation, and the site needs to remain recognizably one business. Fragmentation starts when those jobs pull apart. A site that tells a separate story for each customer type repeats itself and drifts out of agreement. A site that tells one general story leaves each visitor to work out whether it applies to them.
The way through is to divide the content by what actually varies. A customer type earns its own entrance when it changes the visitor's customer decision, the questions they ask or the next step they take. That is the same test that separates customer pathways. Everything that does not vary belongs to the shared foundation.
| Content | Where it lives | Reason |
|---|---|---|
| Identity, credentials and licenses | Shared foundation | Every customer type is evaluating the same business |
| How the service is delivered | Shared foundation, with notes where steps differ | The process is common; documents and timing may vary |
| How pricing is set | Shared foundation | One method explained once; the examples can vary |
| Policies, privacy and security | Shared foundation | The rules apply to every client |
| Contact and intake | One shared intake | A single convergence point records which situation applies |
| The situation, in the visitor's words | Customer-type entrance | This is how a visitor recognizes the page is for them |
| Questions asked before deciding | Customer-type entrance | Different situations raise different questions |
| Examples and proof | Customer-type entrance | Proof persuades when it matches the visitor's situation |
| Deadlines and timing | Customer-type entrance, where they differ | Timing often drives the decision |
Keeping one business on every page
Fragmentation shows up as repeated pages, claims that disagree from one page to the next and visitors who cannot tell which section applies to them. Five practices prevent it.
- Write the shared foundation once. Credentials, process, pricing method and policies live on their own pages, and every customer-type page links to them. A fact changed in one place stays consistent everywhere, which makes keeping content accurate a single task.
- Keep one identity throughout. WCAG 2.2 asks that navigation repeated across pages appear in the same relative order each time, and that controls with the same function be identified consistently [2][3]. The same discipline applies to voice and design. A customer-type page that looks or sounds like a different company weakens trust in the whole site.
- Name entrances by situation. Internal category names ask visitors to translate. Nielsen Norman Group's research on audience-based navigation recommends audience labels that are mutually exclusive and free of jargon, wording such as "for business owners" that makes the audience clear, and audience sections only where the content is unique to that audience [1].
- Give overlapping visitors a route across. Visitors may fit several groups or none [1]. A business owner who also holds rental property belongs on two pages. Each customer-type page links to the others where situations overlap, and topic or service routes stay available for visitors who would rather not choose a group.
- End every entrance at one intake. A single inquiry that asks which situation applies serves every customer type and tells the business who is reaching out before the first conversation. The choice between an intake form and an assessment is covered in which tool fits, and the fields it should ask for in understanding who is reaching out.
Duplication and search
Customer-type pages that repeat the same text under a different label add little for visitors, and little for search. During indexing, Google groups near-duplicate pages and selects one representative version [4]. Its spam policies describe doorway abuse as pages built to rank for similar searches that lead visitors to intermediate pages less useful than the destination they wanted [5]. A customer-type page earns its place by answering the questions that customer type actually asks. The shared foundation carries everything else.
Applications
A CPA firm serving four customer types
Illustrative example. A CPA firm provides tax preparation and tax planning for athletes, business owners, real estate investors, and individuals and families. The discipline is the same throughout. The situations differ.
| Customer type | The situation in their words | Questions specific to them | Proof that matters to them |
|---|---|---|---|
| Athletes | "I signed my first endorsement deal" or "I played in several states this year" | How endorsement and multi-state income is handled; what records to keep | Experience with athlete income and its timing |
| Business owners | "I need help every month of the year" | Bookkeeping, payroll, quarterly estimates, entity choices | Ongoing client relationships and a monthly process |
| Real estate investors | "I just bought my second rental" | Property records, depreciation, timing of a sale | Experience with property-holding clients |
| Individuals and families | "Our situation changed this year" | What documents to gather, how fees are set | A clear process and stated response times |
The homepage names the service and opens four situation entrances. Each customer-type page holds its own questions and proof and links to the shared pages: credentials, how an engagement works, how fees are set, and the firm's secure client portal for documents. All four entrances end at one guided inquiry that asks which situation applies and a few high-level questions, with no documents requested on the website itself, the same handoff discipline applied to sensitive information. An athlete who also owns a business sees links to both pages and can select both situations in the inquiry.
A photographer with three kinds of clients
Illustrative example. A photographer shoots weddings, business headshots and family sessions. The craft, equipment, editing process and booking policy are common to all three. What varies is timing, since this photographer books weddings up to a year ahead and headshots within the week; what the client needs to see, from full wedding galleries to consistent headshot backgrounds; and the next step, which is a date check, a team booking or a session request. Three customer-type pages share one portfolio structure, one page explaining how pricing is set and one booking policy, and each opens from a situation entrance on the homepage.
Limits and edge cases
- Customer types that change nothing. When two types share the decision, the questions and the next step, separate pages repeat content. Both can be named in the copy of one page.
- Customer types that change the service itself. When the work delivered differs by customer type, along with the conversation around it, the business may be offering separate service lines, which are organized by service and then by customer.
- Visitors who will not choose a group. Some visitors prefer to start from a question or a service. Topic and service routes remain available beside the situation entrances [1].
- Regulated professions. Accountants, attorneys, financial advisers and medical practices may face rules on advertising specialties and client types. Confirm the wording with the relevant licensing board before publishing customer-type claims.
- Sensitive information. Customer-type pages invite detail. The website's intake asks high-level questions only and directs documents to the client portal.
- Rare customer types. Each type carries its own answers to maintain. A type that appears a few times a year can be a section on a shared page until it appears more often.
Sort shared and customer-type content
Name the customer types, then mark each kind of content as the same for everyone or different by customer type. The tool sorts the content into the shared foundation and the customer-type layer and suggests a structure.
Sort shared and customer-type content
List your customer types. For each kind of content, decide whether it is the same for everyone or differs by customer type. Shared content forms the foundation. If the situation, questions, intake or next step differ, give each customer type its own entrance.
The structure suggestion follows the rule in this entry. Separate entrances are worth building when the situation, the questions, the intake or the next step differs by customer type. Smaller differences, such as proof and timing, fit within sections of shared pages.
How So It Sticks applies this
We separate the shared foundation from the customer-type layer before writing the pages. Each customer type gets a situation entrance with its own questions and proof, and every entrance ends at one inquiry that tells the business which situation the visitor is in. Start a Project Brief and list the kinds of customers your service supports.
Sources and method
The shared foundation model, the five practices, the examples and the tool are So It Sticks editorial frameworks. The examples are illustrative and describe no real business, and they make no statement about tax rules. Each linked source supports only the statements numbered beside it. Sources verified October 15, 2026.
- Nielsen Norman Group: Audience-Based Navigation: 5 Reasons to Avoid It
- W3C: Understanding Success Criterion 3.2.3, Consistent Navigation
- W3C: Understanding Success Criterion 3.2.4, Consistent Identification
- Google Search Central: In-depth guide to how Google Search works
- Google Search Central: Spam policies for Google web search