Why navigation deserves deliberate planning

Website navigation is the system that helps visitors understand what a business offers, decide where to go next and return to information they have already seen. It includes the main menu, page names, links within content, calls to action, the footer and the relationships between pages. Navigation is therefore more than a row of links at the top of a screen. It is a visible expression of the site’s structure and priorities.

A small website can still become difficult to use when its pages are added one at a time without an overall plan. A services page may use different terms from the homepage. Contact details may appear only in the footer. Important information may be placed under a vague label such as More. Visitors then have to interpret the site before they can use it.

Clear navigation reduces this interpretive work. It can also support search engine discovery, because a consistent hierarchy helps systems understand how pages relate to one another. Good navigation does not require a large budget or a complex platform. It requires decisions about audience needs, business priorities and the language used to describe each page.

Start with visitor tasks, not internal departments

The first planning question should be what visitors need to do, rather than how the business is organised internally. A small business may think in terms of sales, operations and administration, while visitors may be looking for a service, a price indication, opening information, evidence of suitability or a way to make contact.

List the main tasks that the website must support. Typical tasks include:

  • understanding what the business provides;
  • checking whether a service is suitable for a particular need;
  • finding prices, areas served, opening times or availability;
  • reviewing evidence such as qualifications, methods, previous work or policies;
  • asking a question or requesting a quotation;
  • finding practical information after an enquiry has been made.

Rank these tasks by importance and frequency. The main menu should make the most important destinations easy to identify, but it does not need to contain every page. Less frequent information can be reached through contextual links, a footer menu or a clearly labelled secondary area.

This task-based approach also helps resolve disagreements about menu items. If a proposed label reflects an internal team name but does not describe a visitor task, it may belong in the organisational structure rather than the primary navigation.

Create a simple page architecture before designing screens

A page architecture is a map of the site’s pages and their relationships. It should be prepared before detailed visual design, because design cannot compensate for an unclear structure. Start with a list of existing and planned pages, then group them by the questions they answer.

For many small businesses, a useful starting structure may include:

  • Home, which establishes the offer and directs visitors to the main paths;
  • Services or Products, with separate detail pages where visitors need more explanation;
  • About, covering relevant background, approach and credentials without becoming a general biography;
  • Work, Projects or Case studies, where examples help people assess suitability;
  • Information, for pricing guidance, frequently asked questions, delivery areas or processes;
  • Contact, with practical methods and realistic expectations about responses.

These are patterns, not mandatory categories. A professional service may need a detailed process page, while a local shop may prioritise location and opening information. The correct structure depends on what visitors need to decide.

Keep each page responsible for a clear purpose. If two pages answer almost the same question, combine them or distinguish their purposes explicitly. Duplicate pages create uncertainty for visitors and can make maintenance harder.

Design the main menu around a small number of meaningful choices

The primary menu should expose the main routes through the site, not act as a complete inventory of every page. A short menu is not automatically better, but each additional choice increases the need for clear grouping and prioritisation.

Useful decisions include:

  1. Choose the pages that support the most important visitor tasks.
  2. Order items according to likely use and decision sequence, not internal hierarchy.
  3. Place the contact or enquiry route where it remains easy to find.
  4. Use a dropdown only when it clarifies a genuine group of related pages.
  5. Keep secondary resources, legal information and less frequently used pages outside the main menu when appropriate.

For a small site, a menu might contain Services, How it works, About, FAQs and Contact. Another site might need Shop, Delivery, Returns and Support. The labels should follow the visitor’s vocabulary and the site’s actual content.

Do not hide essential information simply to make the menu look minimal. The goal is not the fewest links. The goal is a manageable set of choices whose meaning is apparent before a visitor clicks.

Choose labels that describe destinations precisely

A menu label is a promise about what a visitor will find after selecting it. Labels should be specific enough to set expectations and familiar enough to be understood without specialist knowledge.

Common labels such as Services, Products, About and Contact can work when the surrounding context is clear. More descriptive labels may be preferable when they answer a concrete question, such as Domestic plumbing, Pricing and availability or Delivery information.

Avoid labels that rely on internal language, promotional claims or unexplained abbreviations. Words such as Solutions, Resources and Explore may be suitable in some contexts, but they are broad. If a visitor cannot predict the content from the label, the page may be harder to find.

Keep labels grammatically and conceptually consistent. If one menu item names a service, another should not name an internal department unless there is a clear reason. Use either singular or plural forms consistently where possible. Check labels in isolation, because they may also appear in mobile menus, breadcrumbs, search results or accessibility tools.

Important links should not depend only on colour or visual position. The Web Content Accessibility Guidelines, published by the World Wide Web Consortium, define requirements and guidance for perceivable, operable, understandable and robust web content. The current WCAG 2.2 Recommendation was published in 2023. Clear link names contribute to understandable navigation, especially for people using screen readers or navigating by keyboard.

Give each page a clear role in the structure

A page should answer a defined group of questions and provide a sensible next step. This does not mean every page needs a sales message. It means visitors should be able to understand why the page exists and how it relates to the rest of the site.

A service page, for example, can explain who the service is for, what is included, what affects the process, what information is needed and how to enquire. A separate pricing page can explain the factors that influence cost without repeating all service descriptions. An about page can establish relevant experience and working principles, while a project page can show how a particular type of work was approached.

Use headings to make the page’s internal structure visible. The main page heading should state the subject clearly. Subheadings should divide the content into meaningful sections, such as What is included, Who it is for, Timescales and Next steps. Heading order should reflect hierarchy rather than visual size.

Every important page should connect to at least one logical next step. A visitor reading about a service may need a link to process information, related services or contact details. These links should be placed where they make sense in the content, not only in a repeated footer.

Use internal links to show relationships between pages

Internal links help visitors move through related information and help clarify the site’s architecture. They are especially useful when the main menu cannot contain every route.

Use link text that describes the destination. Read more gives little information when repeated several times, while See the commercial cleaning process communicates purpose. Link text should remain understandable when read without the surrounding paragraph, a useful consideration for people who navigate with assistive technology.

Link related pages in both directions when that relationship is useful. A service page can link to the relevant process page, and the process page can link back to the services it covers. Avoid adding links merely to increase the number of clickable elements. Each link should help answer a question or support a likely next action.

Check internal links during every content review. A renamed page, changed URL or deleted service can produce broken paths. A small site can manage this with a simple content inventory that records the page title, address, purpose, owner of the update and review date.

Plan mobile navigation as a primary experience

Mobile navigation is not simply a desktop menu reduced in size. A small screen changes how many choices can be displayed at once, how easily people can select a link and how much context is visible around the menu.

Use a clearly identifiable menu control when the full navigation cannot remain visible. Its purpose should be apparent, and the expanded menu should be easy to close. Interactive controls need sufficient size and spacing for touch use. The interface should also work with a keyboard and should show a visible focus indicator.

Do not place essential information only in a hover interaction. Hover behaviour is unavailable to many touch users and is not a reliable substitute for an explicit action. Dropdowns should have a clear relationship between their parent label and their child pages, with a predictable way to open and close them.

Test the navigation with realistic content. Long service names, translated terms, text enlargement and narrow screens can expose problems that are not visible in a design mock-up. The W3C advises testing accessibility with a combination of automated tools and human evaluation. A practical review can include keyboard-only use, zoom or text enlargement, mobile screen sizes and a screen reader check where possible.

Separate navigation from calls to action

Navigation helps visitors choose where to go. A call to action asks them to take a particular step, such as requesting information, booking a consultation or adding an item to a basket. The two can support each other, but they serve different purposes.

Making every menu item a call to action can make the site feel demanding and can obscure basic information. A better structure usually allows people to explore the offer while keeping one or two important actions visible. The wording should describe the action accurately. Request a quotation is more specific than Get started when the next step is a quotation request.

Set expectations near forms and contact actions. Explain what information is needed, whether an alternative contact method exists and when a response should normally be expected if that information is known. Avoid promising a response time that cannot be maintained.

Calls to action should not be the only route to key information. A visitor may need to understand the service, accessibility arrangements or terms before deciding to enquire. Good navigation supports informed movement through the site rather than forcing every visitor into the same route.

Use the footer for secondary but important information

The footer is a useful place for links that need to remain available but do not belong in the primary menu. Depending on the site, it may include contact details, location information, opening times, privacy information, accessibility information, terms, delivery details and social channels.

A footer should not become a second unstructured sitemap. Group links under clear headings and remove duplicates that add no value. Legal and privacy pages should be easy to find, but they should not be mixed with service categories in a way that makes the main offer harder to understand.

Ensure that information repeated in the footer is accurate and consistent with the rest of the site. Conflicting opening times, addresses or contact methods reduce confidence and may cause practical problems. Date content that changes, such as seasonal hours or temporary arrangements, and assign responsibility for reviewing it.

Review the structure with simple evidence

Navigation decisions should be tested rather than based only on personal preference. A small business can carry out useful checks without commissioning a large research project.

Ask a few people who resemble the intended audience to complete specific tasks, such as finding a service, locating pricing information or identifying how to make an enquiry. Do not explain the structure while they are testing it. Observe where they look, which labels they hesitate over and whether they can describe what they expect to find before selecting a link.

Useful review methods include:

  • Content inventory: record every page, its purpose, its parent category and its last review date.
  • Card sorting: ask participants to group page topics and name the groups, which can reveal the terms they naturally use.
  • Tree testing: test whether people can find a topic in a text-based hierarchy without visual design distractions.
  • Analytics review: examine navigation paths, searches and pages where visitors leave, while remembering that such data shows patterns rather than individual intentions.
  • Accessibility checks: review keyboard operation, focus visibility, link purpose, heading structure and responsive behaviour.

When interpreting evidence, distinguish between a problem with the label, a problem with the content and a problem with the overall hierarchy. Renaming a link will not solve a page that does not answer the question implied by its title.

A practical workflow for improving an existing website

Navigation improvements are easier to manage when treated as a sequence of decisions rather than a single redesign exercise.

  1. Collect the current pages. Include pages that are not visible in the main menu, such as older campaigns, forms and downloadable documents.
  2. Record each page’s purpose. Write one sentence describing the visitor question it answers.
  3. Identify overlaps and gaps. Combine duplicate pages and note important questions that have no clear destination.
  4. Group the remaining pages. Use visitor language and test whether the groups make sense without explanation.
  5. Draft menu labels. Keep them concise, specific and consistent.
  6. Map internal links. Connect related pages and define a sensible next step for each important page.
  7. Test the draft structure. Use task-based checks on desktop, mobile and with keyboard navigation.
  8. Publish in manageable stages. Prioritise confusing or high-use routes first, then review the whole structure after changes.

Keep a record of the decisions and the reasons for them. This prevents the structure from gradually returning to internal terminology when new pages are added.

Navigation checklist for a small business website

Before publishing or revising a site, check the following points:

  • Can a new visitor identify the main offer from the homepage?
  • Do the primary menu labels describe destinations in familiar language?
  • Are the most important visitor tasks supported by a clear route?
  • Does every major page have a distinct purpose?
  • Can visitors find practical contact, location or availability information?
  • Are related pages connected with descriptive internal links?
  • Does the menu work on narrow screens and with keyboard navigation?
  • Are dropdowns, buttons and focus states understandable without relying on colour or hover?
  • Are changing details dated or assigned a review schedule?
  • Have people outside the planning process attempted realistic tasks?

The best navigation is not necessarily the most fashionable or visually elaborate. It is the structure that makes the site’s content legible, supports different ways of browsing and remains maintainable as the business changes.

Frequently asked questions

How many items should a small business put in its main menu?

There is no universal fixed number. Include the destinations that support the most important visitor tasks, then group related pages when necessary. If the menu becomes difficult to scan or requires several layers of unexplained dropdowns, the information architecture needs review.

Should the homepage appear in the menu?

It can be useful, particularly when visitors may arrive on internal pages and need a clear route back. A recognisable logo or site name may also link to the homepage, but this should not be the only route if users may not understand that convention.

Are generic labels such as About and Services a problem?

Not automatically. They work when the site context makes their meaning clear and the pages contain what visitors expect. More descriptive labels are preferable when a generic term hides important distinctions or when several services need separate routes.

Should every page have a prominent button?

No. Important actions should be easy to find, but a page may primarily provide information. Use a prominent action when it reflects the visitor’s likely next step, and provide supporting links for people who need to explore before making contact.

How often should website navigation be reviewed?

Review it whenever services, locations, contact methods or business priorities change. A scheduled review is also useful, with the frequency determined by how often content changes. The review should include links, labels, page purpose, mobile behaviour and accessibility checks.