top of page

Website Menus: Name Pages So Customers Can Find Your Service

Writer: Briccitly
Briccitly
3 days ago
3 min read
An illustrative menu with one option highlighted by a glowing path toward a service.

A service page's name makes a promise before the click. If a menu uses words the team understands but customers cannot connect to their own needs, difficulty begins before the offer is explained. Reviewing these names is a task involving content and business organization.


Instead of choosing words that sound modern, start with search situations. What does the person want to solve? Which expression would they use when speaking to customer service? Which page can address that need? The answers help determine labels and reveal overlapping offers.


Website menu labels: list Needs Before Organizing Departments


Our suggestion is to write each service on a card and record a prospective customer's question beside it. Avoid copying the corporate presentation: describe the concrete situation. Then group cards by related search needs and check whether the group helps locate an offer or merely reproduces the team's internal divisions.


Fictional example: a maintenance company has two areas named “Operations” and “Projects.” Someone looking for gate repairs has no way to know which one to choose. The team experiments with organizing pages by service while retaining department information in the company presentation.


Make the Name Point to Recognizable Content


W3C advises that headings and labels describe their topic or purpose. Applied to editorial work, this principle calls for a simple check: does menu text help people anticipate what they will find on that page? W3C: descriptive headings and labels


“Solutions” can work as a grouping label, provided subsequent options explain the offers. “Transform your tomorrow,” meanwhile, would require interpretation before revealing a service. This does not mean abandoning brand language. A campaign phrase can appear in the page's communication while the menu uses a name that makes the destination recognizable.


Build a Navigation Matrix


The table below is a proposal for the fictional company. Each row connects a need to a page that needs to exist. The names are candidates for testing; there is no universal structure to copy for every company.


Search situation

Candidate menu name

Page heading

What needs to be explained

My gate stopped working

Gate maintenance

Automatic gate maintenance

Types of service and next steps

I need a new system installed

Gate installation

Automatic gate installation

Scope and information for discussing the project

I want to see completed work

Completed projects

Installation and maintenance projects

Context for each project presented

I know what I need and want to talk

Contact

Talk to the team

Available channels and customer service guidance


If the same situation appears under two items, describe the difference. “Support” and “Maintenance” may indicate different company offers, but they need an understandable distinction. When even the team cannot explain that boundary without a long conversation, first review how the offers are organized.


Keep the Promise After the Click


W3C recommends making link purpose identifiable and observes that similar names for a link and its destination help maintain continuity. The page therefore needs to confirm the menu choice with a compatible heading and a service explanation. W3C: link purpose


When reviewing our matrix, open each page and ask: “Is this the offer the name announced?” If the item says installation, the opening content should explain that activity. A page beginning with a generic company description makes visitors do the work of confirming they have reached the intended place.


Also record how the name appears on service cards and footer links. If the company uses three different expressions for the same offer, assess whether there is an understandable reason. Our editorial criterion is to maintain one main name and explain complementary terms in the content.


Test the Choice Without Presenting the Organization Chart


Prepare brief situations and show only the menu to someone who did not participate in its organization. Ask where they would start and what they expect to find. Do not reveal the option considered correct before their answer. This exercise is a qualitative draft review, rather than market research or a prediction of results.


  • Choose one situation for each service and another the company does not handle.

  • Record the person's first choice and reasoning.

  • Compare their expectation with the page's actual content.

  • Record confusion between similar options and words they did not understand.

  • Change one name or grouping at a time and reassess the corresponding situation.


Check Navigation on the Finished Website


W3C recommends consistent names, ordering and destinations across screen versions, along with appropriate identification of menus and the current page. Implementation needs to preserve these relationships when navigation collapses on mobile. W3C: menu structure


Review the journey on desktop and mobile, including opening groups and arriving at pages. To start today, select your menu's vaguest item and write down which offer it should announce. This decision guides both the name and content. Explore Briccitly's website service to organize this work within the project. Briccitly website creation



Comments


bottom of page