How to organise a website menu: labels, order and depth

Menus usually grow by accident. A page gets added for a new service, another for a campaign, a third because a customer asked a question twice, and nobody ever goes back to reorganise. Two years later the menu has eleven items in no obvious order. To organise a website menu properly you need to make four decisions in sequence: what goes in, how items are grouped, what they are called, and how deep the structure goes.

This article walks through those decisions with the small, practical judgement calls that come up along the way.

Start with an inventory, not a menu

Open a spreadsheet and list every page on the site. Add four columns: the page title, its purpose in a few words, monthly visits from your analytics, and whether it currently appears in the menu.

The list almost always contains surprises. Pages nobody remembers creating, two versions of the same service, a policy page linked from nowhere. Mark each row as keep, merge, retire or rewrite before you go any further, because organising a menu around pages you intend to delete wastes everyone's time.

A rough guide for small business sites: anything with almost no visits and no strategic purpose does not need a menu slot, and probably does not need to exist.

Group pages the way customers think, not the way you are organised

Internal structure leaks into menus constantly. Businesses group by department, by supplier, by the order in which products were launched, or by which team owns the page. Customers have no idea about any of that.

Take the pages marked keep and cluster them by the job a visitor is trying to do. A typical set of clusters for a service business looks like: understanding what you offer, checking whether you are credible, working out cost, getting in touch, and getting help after buying. For an online store the clusters are usually browsing products, understanding delivery and returns, and account or order matters.

Two rules help at this stage. A group with only one page inside it should usually become a single menu item rather than a dropdown. A group with more than seven or eight pages probably contains two groups that have not separated yet.

Name items in the customer's words

Labels are where most menus fail. Three patterns cause the trouble.

Invented or internal names

Product names, programme names and internal jargon mean nothing to a first-time visitor. "Solutions", "Offerings" and "Our ecosystem" are equally empty. Say what the thing is: "Website design", "AMC plans", "Spare parts".

Clever labels

A menu is not the place for personality. "Our story" is understood, but "The journey so far" makes people pause, and a pause in a menu is a small failure.

Labels that overlap

If two items could plausibly contain the same page, visitors will click the wrong one. "Services" beside "What we do" is the classic example. Merge them.

To find the right words, look at the search terms bringing people to the site in Google Search Console, the phrases customers use in enquiry emails and WhatsApp messages, and the words competitors use for the same thing. Keep labels to one or two words where possible, since long labels wrap awkwardly in a horizontal bar. Where a keyword genuinely matches how customers speak, using it in the label is helpful for both readers and search engines, but never stuff a phrase into a menu that sounds unnatural when read aloud.

Decide the order deliberately

Items at the start and end of a menu get noticed more than those in the middle, so order is a real choice rather than an alphabetical accident.

A workable default for a small business site is: what you sell first, proof second, cost third, contact last. That puts the highest-value pages where attention lands and keeps the contact item in its conventional final position, where people look for it.

Two adjustments are common. If one service earns most of your revenue, give it its own top-level item rather than burying it inside a dropdown. If enquiries are the single goal of the site, the last item can be a button styled differently from the rest, which is a design decision rather than a structural one, but it belongs in the same conversation.

Resist ordering by internal importance. The director's message does not belong before the product pages.

Choose how deep the structure goes

Depth is about how many levels a visitor passes through to reach a page. Most small business sites need only two: top-level items and one dropdown level under some of them.

• One level suits sites with fewer than about eight pages. No dropdowns, nothing hidden.
• Two levels suit most service businesses and small catalogues. Every page is reachable in two clicks from anywhere.
• Three levels are justified for large product catalogues, documentation and news portals with many sections, and should be handled with a wide panel rather than a dropdown inside a dropdown.

Nested dropdowns that open sideways are the pattern to avoid. They are difficult to control with a mouse, awkward with a keyboard and close unexpectedly on touchscreens. If you find yourself needing a third flyout level, the answer is usually a landing page for the group that lists its children as links.

Whenever a dropdown exists, make the parent item lead somewhere useful. A "Services" parent that opens a list but cannot itself be opened frustrates anyone who wants an overview, and it wastes a page that could rank well in search.

Handle the mobile version as part of the same plan

The same structure has to survive inside a narrow panel. Long dropdowns become endless scrolling, so decide in advance whether groups collapse into accordions, whether the panel scrolls, and how a parent page is reached when tapping the parent expands its children instead of navigating. A separate small link labelled with the group name, or an "All services" item at the top of the expanded list, solves that neatly.

Keep the structure identical across devices. Hiding items on mobile because space is tight teaches visitors that the site behaves differently on their phone, which is rarely the impression you want.

Write the structure down before you build it

Put the final menu in a simple indented list in a document, with the destination URL beside each label, and circulate it before anyone touches the site. Structural disagreements are much cheaper to settle in a document than in a live template.

Review the list once or twice a year and whenever you add a service, because menus decay quietly. If you are restructuring a site with a large catalogue and are unsure how the categories should nest, our team works through this during planning for online store development projects.

Frequently asked questions

Should every page be reachable from the menu?

No. Policies, thank-you pages, individual blog posts and campaign landing pages are better reached from the footer, from within content or from search. A menu holds the routes people need regularly, not an index of the site.

How do I decide between one menu item and a dropdown?

Count the child pages. One or two children usually work better as separate top-level items or as links on a landing page. Three or more related children justify a dropdown, provided the parent also has a page of its own.

Is it better to sort menu items alphabetically?

Only for long lists people scan by name, such as a directory of brands or locations. For a business menu, ordering by importance to the customer beats alphabetical order, which just hides your best pages in the middle.

What should I do with an old page I am removing from the menu?

Decide whether it still earns traffic. If it does, keep the page and link it from a relevant parent page. If it is redundant, merge the useful content into another page and redirect the old address so existing links and search results still work.