
3DSkillUp
Web Design

Resolve overlapping service names before website design. Map customer needs, clarify each offer and agree useful labels before planning pages and layouts.
When several service names appear to describe the same work, resolve their boundaries before drawing the website layout. Start by identifying what a customer needs, what each offer includes and why someone would choose one route over another. A clearer set of labels gives the design a structure it can communicate.
This matters when a business has grown through new teams, packages or acquisitions. The website may have accumulated names from different periods without explaining their relationship. A visitor should not need to understand that history to work out which service is relevant.

Build an inventory of the terms currently used in the main menu, service pages, homepage cards, brochures and enquiry process. Include names that customers use in messages or conversations, where you have that evidence. Record the URL and the person responsible for each offer.
Keep the first inventory descriptive. If you immediately rewrite every label, you can lose the evidence of where the confusion began. “Workplace solutions” might appear in the menu, “Office design” on the page and “Space planning” in the quotation template, even though all three refer to one service.
Add a plain-language description beside every name: who it helps, the situation that brings them to the business, the work included and the next step. Where the team cannot explain those details consistently, mark the entry as unresolved.
The homepage content checklist is useful here because it connects each service introduction with an audience, scope and destination. Those decisions should be available before a designer starts arranging cards.
Similar wording does not always mean duplicate services. Two offers might share a method while helping different customers. A broad service may contain a smaller deliverable. A term may describe a project stage instead of something a customer can commission separately.
Use the distinction below to decide what kind of problem you have:
| Relationship between names | Question to resolve | Possible website treatment |
|---|---|---|
| Two names for the same offer | Would the customer receive the same work through either route? | Agree one public name and explain familiar alternatives in the copy |
| A service and something it includes | Can the smaller item be commissioned on its own? | Make it a section or a clearly explained subservice |
| Different stages of one engagement | Is each stage a separate buying decision? | Explain the process, with separate pages only where useful |
| The same service for different audiences | Does suitability or scope materially change? | Keep the service clear and add audience-specific guidance where needed |
| A method presented as a service | Is the customer choosing the technique or the result? | Introduce the method within the relevant offer |
Treat this as a discussion aid. The right structure depends on how the business actually works. Do not merge distinct services simply because their current descriptions are vague; clarify the difference first.
For each entry, complete a sentence in the customer’s voice: “I need help with…” Then describe the information that person needs to decide whether the service fits.
A useful distinction should survive this exercise. If two entries have the same audience, situation, deliverables and enquiry route, ask why they need separate top-level labels. The answer may reveal a real difference, or it may reveal a distinction that exists only inside the company.
GOV.UK’s guidance on naming services recommends using the language of users and understanding their task; it also notes that naming difficulties can expose unclear scope. For a commercial website, the relevant principle is to establish the customer’s task before selecting a public label. You do not need to copy government naming conventions.
Customer language is evidence, not an instruction to reproduce every phrase verbatim. People may use an inaccurate technical term. Choose wording that is understandable and accurate, then explain the familiar term where that helps them recognize the offer.
Consider a fictional commercial interiors company with four labels: “Workplace Design,” “Space Planning,” “Office Refurbishment” and “Workplace Strategy.” At first glance, all four seem to promise a better office.
During the inventory, the team establishes that workplace strategy is a separate planning engagement, space planning is normally included in its design service, and refurbishment refers to the delivery of agreed physical changes. Those facts create a more useful structure.
The website could introduce three principal offers: “Workplace Strategy,” “Office Interior Design” and “Office Refurbishment.” The design page would explain space planning as part of its scope. If space planning can also be purchased separately, the page should explain when that option is appropriate and how to enquire.
This is an illustrative planning exercise, not a client case study or a universal recommendation for that industry. The decision follows the fictional company’s confirmed offer. A different company may legitimately organize the same words differently.
Write the reason for every decision beside the proposed label. “Included within design unless commissioned separately” is more useful to the next editor than “We preferred three cards.”
A row containing “Consultancy,” “Commercial Clients,” “Installation” and “Premium Package” mixes service type, audience, activity and pricing tier. Each label might be meaningful, but together they ask the visitor to compare different kinds of choices.
Choose the main organizing principle around the customer’s first useful decision. Service types can lead, while industries or customer groups provide secondary routes. A package can be explained within the relevant service unless it is genuinely the way customers choose the offer.
One service can be linked from more than one relevant place. You do not need to duplicate its page every time it suits a different audience. For example, an industry overview can explain the context and link to the existing service detail.
Once the groups are meaningful, decide whether category filters or a simpler list of links is appropriate. A filter cannot establish the distinction between offers that the business has not yet defined.
Create a plain list of the proposed service names and short descriptions. Give a suitable newcomer a realistic task without repeating the exact label you want them to choose. Ask where they would look and what they expect to find.
Include at least one task that sits near a disputed boundary. For the fictional interiors company, someone who needs to explore options before committing to a redesign might reasonably consider strategy or design. Listen to the explanation rather than treating every different first click as a failure.
If several routes are plausible, the page may need a comparison sentence or a shared overview. If people consistently misunderstand a label, revise the wording or scope explanation. A small qualitative review can identify confusion; it does not establish a conversion forecast.
The guide to testing whether a first-time visitor understands an offer provides neutral prompts and a way to separate observations from proposed fixes. Use it before visual polish makes an unclear structure feel settled.
Create a short reference containing the approved public name, one-sentence explanation, included work, exclusions that matter, parent group and destination. Add the decision owner and any familiar alternative terms that belong in the body copy or search system.
Apply the agreed language to menus, headings, cards and enquiry options. Exact wording can vary with context, but each route should describe the same offer. A short menu label can lead to a more detailed page title if their relationship is obvious.
Then use the website navigation planning guide to connect the service groups with projects, preparation content and contact. Decide which links belong in the footer rather than the main menu after the service structure is clear.
Renaming a visible label does not automatically require changing its URL. If pages are merged or retired, plan the destination of each existing address with the developer, preserve useful content and update internal links. Keep that migration decision separate from the visual exercise of shortening a label.
No. They may have distinct audiences, deliverables or buying stages. First establish whether a customer has a meaningful reason to choose one over the other. Merge only when the separation adds no useful distinction and the business confirms the offers are equivalent.
Yes, if it remains appropriate. Pair it with a clear explanation of the work and the customer it serves. An established name does not have to carry the entire explanation, but a newcomer should be able to understand the offer without prior brand knowledge.
Return to customer tasks, scope and evidence from real enquiries. Record the unresolved business decision and identify who can settle it. Moving the disagreement into a larger dropdown does not resolve what the website is meant to communicate.
SavianoDesign’s Web Design service connects content structure, page hierarchy and responsive visual design for a complete homepage or website. Explore the Web Design portfolio to see how clear routes and focused page layouts work together.
Discuss your website with SavianoDesign and share the current URL, your service list and the names customers most often confuse. That gives the brief a practical starting point before the first layout.
Web Design · 9 min read
Choose between category filters and service links using visitor tasks, clear groups and practical tests. Plan a service directory people can actually use.
Web Design · 8 min read
Decide which links belong in the footer or main menu on a website with many services. Prioritize visitor tasks and keep essential information easy to find.
Web Design · 8 min read
Plan website navigation with clear menu labels, useful page groups and mobile behaviour. Includes a practical route map and a checklist for testing.
Have a website in mind?