All insightsWeb Design

Choose Website Navigation Labels and Page Titles That Point to the Same Thing

A page can have a short menu label and a fuller heading while keeping the same meaning. Build a naming record and check what each field actually changes.

Chrome signpost with ivory, lavender and glass arrows pointing towards one doorway, beside the headline Name the page. and supporting text Clear labels. One destination. ZXP is embedded in the base.
Original conceptual illustration of different labels leading to the same website destination.

A visitor selects “Services” and arrives on a page headed “A better way forward.” The design may be attractive, but the wording makes them work out whether they reached the right place. Clear page names give the route and the destination a recognisable connection.

When you review names with your designer, separate the menu label, the main heading on the page and the HTML page title. They have different jobs and may use different wording. They should still describe the same content, without adding services or promises the page cannot support.

Know which piece of text you are changing

The navigation label is the link someone chooses in a menu. It needs enough context to distinguish its destination from neighbouring links. A short label can work well when the surrounding menu makes its meaning clear.

The main heading, usually marked as an H1, introduces the page after someone arrives. It has room to be more specific than a menu item. Supporting copy can carry the brand's tone while the heading confirms what the page is about.

The HTML title is a separate piece of page information, commonly shown in a browser tab. A content editor may call its field “SEO title” or “page title”. Ask the developer which output that field actually controls. W3C's Page Titled guidance explains how descriptive titles help people identify and distinguish pages.

Google's displayed title link is another step. Google generates it automatically using several sources, which can include the HTML title and visible headings. Its title-link documentation recommends descriptive, concise titles and explains why the search result may use different wording. Editing an “SEO title” field does not guarantee the exact text Google will show or a change in ranking.

Name a destination people can recognise

Start with what is on the page. “Curtain alterations” describes a service; “Transform” asks the visitor to infer one. A distinctive phrase can still have a place in the design, but it should not carry the whole burden of telling someone where a link goes.

Compare proposed names beside the other menu items. Two labels that both sound like a general service overview may be difficult to choose between. If “What we do” and “Solutions” lead to different pages, explain that difference in ordinary words before approving either label.

Do not solve a crowded menu by making every label so broad that it loses meaning. Consider whether related pages belong in a clearly named group. The grouping should reflect the content people need, rather than a business's internal reporting structure.

W3C's Link Purpose guidance describes how link text and its context help people understand a destination. It also recommends continuity between a link and the title of the page it opens. That gives the review a useful question: does the destination fulfil the expectation created by the label?

Make a naming record for each page

Use five fields: the page's job, its existing URL, the menu label, the visible main heading and the HTML title. Add a note for any service fact that still needs confirmation. Keeping these fields together lets the owner and designer review the relationship instead of approving each phrase in isolation.

Imagine a fictional curtain studio with separate pages for made-to-measure curtains and alterations to existing curtains. The business and wording below are invented. They demonstrate a naming decision, not a live website test or a ZXP client result.

For the first page, the job is to explain the studio's made-to-measure curtain service. The proposed menu label is “Made-to-measure curtains”, the H1 is “Made-to-measure curtains for your home”, and the HTML title is “Made-to-measure curtains | Example Studio”. The longer heading introduces a residential scope that the fictional owner has confirmed. The title adds the invented business name so it can be recognised outside the menu.

For the second page, the job is to explain changes to existing curtains. The proposed menu label is “Curtain alterations”, the H1 is “Curtain alterations and repairs”, and the HTML title is “Curtain alterations | Example Studio”. This row contains a problem: the owner has confirmed alterations but has not confirmed repairs. Remove “and repairs” from the draft heading until the actual offer is settled. A more descriptive heading is only helpful when its extra detail is true.

Keep the existing URL recorded separately for both rows. Changing the displayed wording does not, by itself, require a new address. If a URL change is proposed, have the developer explain the redirect and link-update work before approving it. Do not accidentally turn a copy edit into a site migration task.

Let each label use the space it needs

The menu, page and browser tab do not have identical surroundings. A menu may already sit under a clearly named service group, while a browser tab needs to distinguish the page from several other open tabs. Shortening one field can be sensible without shortening all of them.

Preserve the recognisable subject across those versions. “Curtain alterations” can lead naturally to a main heading that expands on curtain alterations. A page called “Our approach” needs an explanation of the business's approach, rather than an unexplained list of prices or a contact form.

Avoid repeating keywords to fill the HTML title. Google recommends distinct titles that describe each page and warns against keyword stuffing and repetitive boilerplate. There is no fixed character count that guarantees the whole title will display: Google can truncate its title link to fit the device. Write the clearest useful title, then inspect the actual output.

Review the route and the arrival together

Give someone a task without naming your preferred menu item. For the fictional studio, ask where they would look to find out whether existing curtains can be shortened. Record which label they choose, what they expect to find and whether the page answers that expectation. Leave the result blank until someone actually tries it.

If the person chooses the expected page but still cannot find the answer, the problem may be in the content. If two labels seem equally plausible, revise the distinction and test it again. One observation can identify a useful problem; it cannot establish how every customer will behave.

Read the heading with the first paragraph as well. W3C's Headings and Labels guidance calls for headings that describe topic or purpose. Ask the implementer to check the underlying heading structure separately. Accurate wording and correct markup are both relevant, and this naming exercise is not a complete accessibility audit.

For controls, keyboard behaviour and narrow-screen obstructions, use the separate guide to testing a mobile website menu around customer tasks. Those checks have a different job from deciding what the links should say.

Hand over the exact wording and check it in place

Send the approved naming record with the URL for each page and a clear instruction about which fields change. After the edit, check the visible menu, the main heading and the actual HTML title. Do not assume saving a field in the editor updated every part of the website.

Check other menus and repeated links for inconsistent old names. Keep any proposed URL changes separate, and record what was actually changed. Search-result wording can take time to update and may differ from your title, so use the website itself to verify the edit first.

For a broader website design project with ZXP, bring the current pages and the labels that cause uncertainty. You can include the naming record when you prepare your project brief. It gives the discussion a concrete set of destinations to clarify.

THE READING LIST

Sources & references

  1. 01
  2. 02
  3. 04
ZXP

A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.

FROM IDEAS TO ACTION

Give each page a recognisable name

Bring your current pages and the labels that leave visitors guessing.

Prepare your project brief