On a phone, a service website's navigation should do three things within the first screen: show what the business does, let a visitor reach the two or three pages most people want without opening anything, and offer a one-tap way to call or message. For most small and mid-sized service businesses that means a slim sticky header with the logo, a visible call or WhatsApp button and a clearly labelled "Menu" control, plus a short row of key links or a bottom bar for the most-used pages. Everything else can sit in the menu, provided it is organised the way customers think, not the way your company is structured. As a website designer in Pune, this is the part of a site we see go wrong most often: menus copied from the desktop layout, headers that cover a third of the screen, and call buttons too small to tap. This guide explains how to get it right.
It is written for owners and marketing leads of service businesses (clinics, interior designers, coaching institutes, CA firms, contractors, B2B suppliers) who are planning a new site or a redesign and want to brief their designer properly.
Why mobile navigation deserves its own design, not a shrunk desktop menu
On most service websites we work on, phones bring the majority of visits, and in India the share is often higher still because so much traffic comes from Google Maps, Instagram and WhatsApp links. Yet navigation is usually designed on a wide desktop screen first and then "made responsive", which in practice means the horizontal menu collapses into a three-line icon and every link is dumped into a long list.
That shortcut has real costs:
- People use hidden navigation less. In Nielsen Norman Group's usability study of hidden versus visible navigation, mobile participants used the navigation in 57% of cases when it was fully hidden behind a menu icon, against 86% when some links were visible and the rest hidden (a "combo" pattern). Content discoverability dropped by more than 20% when navigation was hidden, and tasks took longer.
- Search engines index the mobile version. Google uses the mobile version of a page for indexing and ranking. If your mobile menu drops links to important service pages that your desktop menu shows, those pages may receive fewer internal links in the version Google actually reads.
- Visitors arrive in the middle of the site. Someone who taps a Google result for "physiotherapy for knee pain Kothrud" lands on a service page, not the homepage. The header is the only constant on every page, so it has to work as a map from anywhere.
None of this means hamburger menus are wrong. It means the menu cannot be the only way around the site.
Start with what visitors are trying to do
Before drawing any layout, list the five or six things real visitors come to do. You can find them in three places:
- Analytics: the most-visited pages after the homepage, and the pages visited just before an enquiry.
- Search Console: the queries that bring people to the site. If most of them name a specific service, that service should be easy to reach.
- Your phone and WhatsApp: what people ask when they call. "Do you do X?", "What are your timings?", "Where are you?", "How much does it cost?"
A typical list for a Pune clinic might be: find the treatment they need, check the doctor's credentials, see timings and location, book or call. For a B2B fabrication supplier: check capabilities, see past work, download a catalogue, send an enquiry. These tasks decide what goes in the header, what goes in a visible shortcut row and what can wait in the menu.
The anatomy of a good mobile header
Keep it slim
A header on a phone should usually be somewhere around 56 to 72 pixels tall. Logos designed for desktop are often too wide and too detailed; a compact version of the logo, or the wordmark alone, usually reads better. Avoid stacking a top bar with email and address above the main header on mobile. That information belongs in the footer and on the contact page.
What belongs in it
For most service businesses, the header holds:
- The logo, linking to the homepage.
- One primary action: a call button, a WhatsApp button or a "Book" button, depending on how your customers prefer to get in touch. Pick one for the header; a second can live in a bottom bar.
- A menu control, ideally with the word "Menu" next to or below the icon. A labelled control is clearer to visitors who do not recognise the three-line symbol, and the label costs very little space.
Search is worth adding to the header only if the site has a large amount of content, such as a hospital with dozens of departments or a supplier with hundreds of products. For a 15-page service site, a search box is clutter.
Sticky or not
A sticky header, one that stays at the top as you scroll, keeps the call button and menu within reach on long service pages. It also takes screen space from the content on every scroll. Two common compromises work well:
- Shrink on scroll: the header reduces to a thinner bar once the visitor starts scrolling.
- Show on scroll up: the header hides as the visitor scrolls down and reappears as soon as they scroll up, which is usually the moment they are looking for it.
Whatever you choose, test it on a small Android phone, not only on the designer's large iPhone. A header that looks fine at 430 pixels wide can cover a large part of the screen at 360 pixels, especially when a cookie banner or chat widget is also fixed to the screen.
There is also an accessibility rule here. WCAG 2.2 added Success Criterion 2.4.11, Focus Not Obscured (Minimum), at level AA: when someone moves through the page with a keyboard or switch device, the item that has focus must not be entirely hidden by content the author has fixed on screen, such as a sticky header or footer. In practice, set a scroll padding at the top of the page equal to the header height so focused links and in-page anchors are not tucked underneath it.
Visible shortcuts: the "combo" pattern in practice
The research above favours combination navigation: a few important links visible, the rest in a menu. On a phone there are three practical ways to do that.
A shortcut row under the header
A single horizontal row of three or four short links ("Services", "Our work", "Fees", "Contact") just below the header. It works when the labels are short. If they do not fit on a 360-pixel screen without shrinking text, use fewer links rather than a horizontally scrolling strip, which many visitors never notice can scroll.
A bottom action bar
A fixed bar at the bottom of the screen with two to four actions, for example Call, WhatsApp, Directions and Book. This puts the most important actions where thumbs naturally rest on a large phone. It suits businesses where the next step is contact rather than reading: clinics, salons, repair services, coaching centres. Keep it to actions, not page links, and make sure it does not cover the site's own cookie banner, chat widget or form submit buttons.
We cover the details of tap-to-call and WhatsApp buttons, including tracking them as conversions, in our guide to click-to-call and WhatsApp buttons on mobile service websites.
In-page links on the homepage
The first screen of the homepage can itself act as navigation: a short headline, then large tappable cards for your main services. This is not a substitute for a header menu, but it is often how most visitors move from the homepage to a service page.
Designing the menu itself
Organise by what customers buy, not by your departments
The most common menu problem we see is a structure that mirrors the company: "About", "Divisions", "Solutions", "Industries", "Resources". Visitors do not know which of those contains the thing they want. Instead:
- Put services first, named in the words customers use. "Kitchen interiors" rather than "Modular solutions". "GST registration" rather than "Indirect tax advisory" if that is what people search.
- Group services only when you have more than about seven. Two or three groups, each with a clear label, are easier than one long list.
- Put "About", "Careers" and "Blog" lower in the menu. They matter, but they are not why most people opened it.
Choosing between accordion and drill-down menus
When the menu has sub-items, there are two main patterns:
- Accordion: tapping a section expands its sub-links in place, below the heading. Visitors can see where they are and collapse it again. This suits menus with two levels and a modest number of links.
- Drill-down: tapping a section slides in a new panel showing only its sub-links, with a "Back" control. This suits large menus with three levels, such as a hospital or a large product catalogue, but it hides context, so the back control and the current section name must be obvious.
Do not make the parent label do two jobs. If "Services" both opens a sub-menu and links to a services overview page, many visitors will tap it expecting one and get the other. A common solution is to keep the parent label as a toggle and add "All services" as the first item in its sub-menu.
Keep it short
A useful rule of thumb is that the top level of the mobile menu should fit on one phone screen without scrolling. If it does not, the menu is doing too much. Move rarely used links, such as policy pages, downloads and press mentions, to the footer.
Show contact details inside the menu too
Many visitors open the menu looking for a phone number or address. Placing the phone number, a WhatsApp link and the address at the bottom of the open menu means they find it there rather than closing the menu and scrolling to the footer.
Tap targets, text and spacing
Navigation is the most-tapped part of any site, so sizing matters.
- Target size. WCAG 2.2 Success Criterion 2.5.8 (Target Size, Minimum), at level AA, asks for pointer targets of at least 24 by 24 CSS pixels, or enough spacing around smaller targets. That is a minimum, not a goal. Platform guidance from Apple (44 by 44 points) and Google's Material Design (48 by 48 density-independent pixels) is closer to what feels comfortable, and we design menu links and header buttons at around that size.
- Spacing between links. Stacked menu links need enough vertical space that a thumb does not hit the neighbouring item. Full-width rows with generous padding are easier than tightly packed text links.
- Text size. Menu labels should be at least as large as body text, typically 16 pixels or more. Small, light-grey menu text is one of the most common contrast failures we find in audits.
- Icons with labels. Icons alone (a house, a phone, a chat bubble) are ambiguous to many visitors. Pair them with one-word labels, especially in a bottom bar.
Accessibility and how the menu behaves
A mobile menu is an interactive component, and it has to work for people using screen readers, keyboards and voice control as well as thumbs.
- Use a real button for the menu toggle, with an accessible name ("Menu" or "Open menu") and an
aria-expandedstate that changes when the menu opens. - Move focus sensibly. When the menu opens, focus should move into it; when it closes, focus should return to the toggle. The Escape key should close it.
- Do not trap people. Visitors must be able to close the menu without choosing a link, with a visible close control.
- Prevent background scrolling while a full-screen menu is open, so the page does not move underneath.
- Respect reduced motion. Long slide-in animations can be uncomfortable for some people. Honour the
prefers-reduced-motionsetting and keep transitions short.
These points also matter for search engines. Links should be ordinary <a href> links present in the page's HTML, not elements that only become links after JavaScript runs on a tap. Google's mobile-first indexing documentation is explicit that Google won't load content that requires user interactions such as clicking, swiping or typing. Menu links that are in the HTML but visually collapsed are fine; links that are fetched only when someone opens the menu may not be seen.
Keeping mobile and desktop navigation consistent for SEO
Google's guidance is to make sure the mobile site contains the same content as the desktop site. Navigation is part of how your pages link to each other, so:
- Keep the same important links in both versions. If the desktop mega menu links to twelve service pages, the mobile menu should reach the same twelve, even if they sit one level deeper.
- Do not build two separate menus that drift apart. Many themes output one menu for desktop and another for mobile. Over time someone updates one and forgets the other. Where possible, render one menu structure and style it differently by screen size.
- Use breadcrumbs on deep pages. On a phone, breadcrumbs give visitors a way back up the structure without opening the menu, and they reinforce the site's hierarchy. Our guide to internal linking, breadcrumbs and site architecture covers how to plan this.
- Put supporting links in the footer, not in hidden blocks. A clear footer with service links, contact details and policies is useful to people and gives every page a consistent set of internal links.
If you are reorganising a menu on an existing site, check that no important page loses all its internal links in the process. A page linked only from the old menu can quietly lose visibility.
How to test mobile navigation before launch
You do not need a research lab. A short, structured test catches most problems.
Five-task hallway test
Ask three to five people who do not work for you, ideally similar to your customers, to complete five tasks on their own phones while you watch without helping:
- Find out whether you offer a specific service.
- Find your fees or how pricing works.
- Find your location or service area.
- Contact you.
- Find one piece of proof, such as a past project or a review.
Note where they hesitate, what they tap first and whether they open the menu at all. If several people miss the same thing, the design needs to change.
Device and condition checks
- Test on at least one small, older Android phone and one recent iPhone.
- Test in portrait and landscape.
- Increase the phone's text size setting and check that labels do not overlap or get cut off.
- Test with the cookie banner and any chat widget active.
- Tab through the site with a keyboard on desktop at a narrow window width.
- Turn on a screen reader (TalkBack or VoiceOver) and open and close the menu.
After launch: watch real behaviour
Session recording and heatmap tools such as Microsoft Clarity show where people tap and whether they open the menu. Look for repeated taps on things that are not links (a sign people expect them to be), menu opens followed by immediate exits, and rage clicks around the header. We describe how to use these tools on service sites in our guide to Clarity heatmaps and session recordings.
What this costs and how long it takes
On a new website, mobile navigation is part of the design and development scope and should not be a separate line item. When you brief a designer, ask to see the mobile header and menu designed explicitly, not only the desktop homepage.
On an existing site, a navigation redesign usually involves:
- Planning: reviewing analytics, search queries and enquiry data, then drafting a new menu structure. Typically one to three days.
- Design: mobile and desktop header, menu, bottom bar and footer. Typically two to four days including one round of revisions.
- Development and testing: building the components, checking accessibility and testing across devices. Typically two to five days, depending on the platform. A WordPress theme with clean menu support is quicker than a site built with heavily customised page builder popups.
As a rough guide, a focused navigation redesign on an existing small service site in Pune might fall somewhere between ₹15,000 and ₹60,000, depending on the number of pages, the platform and how much of the header and footer must be rebuilt. These are indicative ranges, not a quote; the real figure depends on the site. If the underlying theme makes clean navigation impossible, it may be more economical to treat it as part of a wider redesign.
A short brief you can give your designer
If you are commissioning a new website or redesign, include something like this in your brief:
- Our visitors' top tasks are: (list three to five).
- On mobile, the header must show the logo, a [call / WhatsApp / book] button and a labelled menu control, and stay under about 70 pixels tall.
- The first screen must give access to our main services without opening the menu.
- The menu must reach every page linked from the desktop menu, organised by service, with contact details at the bottom.
- Menu links must be normal HTML links, and the menu must work with a keyboard and screen reader.
- Tap targets should be at least 44 by 44 pixels where space allows.
- Please show us the mobile header, open menu and footer as designs before development starts.
How we approach navigation on Govindani projects
When we design a service website, we plan the mobile header, menu and footer from the visitor's tasks before we design the desktop layout, and we test the navigation on small Android phones as well as larger devices before launch. If your current site is hard to use on a phone, or you are planning a new one, see our website creation service and our SEO service for how navigation fits into the wider structure, or contact us and call 092019 58274 to talk it through.
Frequently asked questions
Is a hamburger menu bad for a mobile website?
Not by itself. The problem is when it is the only navigation. Usability research by Nielsen Norman Group found people used navigation less and found content less often when it was fully hidden. Keep a hamburger menu for the full list, but also show a call button and a few key links or service cards without opening it.
Should my website header be sticky on mobile?
Often yes, because it keeps the call button and menu within reach on long pages. Keep it slim, consider shrinking it or showing it only when the visitor scrolls up, and make sure it does not cover focused links or form fields. Test it on a small phone alongside any cookie banner or chat widget.
How many items should a mobile menu have?
As few as possible. The top level should fit on one phone screen without scrolling, usually around five to seven items. Group services if you have many, and move policies, downloads and minor pages to the footer.
Does mobile navigation affect SEO?
Yes. Google indexes the mobile version of your pages, so links that exist only in the desktop menu may carry less weight. Keep important pages reachable from the mobile menu, use normal HTML links rather than links loaded on tap, and add breadcrumbs and a clear footer.
What size should buttons and menu links be on mobile?
WCAG 2.2 sets a minimum of 24 by 24 CSS pixels for pointer targets, or enough spacing around them. For comfortable tapping, aim for roughly 44 to 48 pixels in height for menu links and header buttons, with space between neighbouring links.
Sources:
- Nielsen Norman Group: Hamburger Menus and Hidden Navigation Hurt UX Metrics (2016)
- Google Search Central: Mobile-first indexing best practices
- W3C: Understanding WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum)
- W3C: Understanding WCAG 2.2 Success Criterion 2.4.11 Focus Not Obscured (Minimum)
- Apple Human Interface Guidelines: Accessibility
- Material Design 3: Designing for accessibility
About the author: written by the Govindani Infotech design and development team in Pune, who design and build service business websites, e-commerce stores and NGO platforms, and who audit mobile navigation and accessibility as part of every website project.