The short version: a website map for navigation is a visual list of every page on your site grouped into logical sections, built with free tools like Google Sheets, Miro, or Octopus.do, and its job is to help humans find things fast, not to please Google. Do this before you touch your menu, and you’ll cut click paths in half within an afternoon.
The confusion nobody clears up first
Most posts on this topic jump straight to “use this free sitemap generator” and hand you a tool link. That’s backwards. There are two completely different things called a “sitemap,” and mixing them up wastes hours.
An XML sitemap is a file for search engine crawlers. It’s a flat list of URLs with no visual structure, and Google reads it, humans never see it. I’ve written about how to create an XML sitemap separately because it solves an indexing problem, not a navigation one.
A website map for navigation is different. It’s a diagram, sometimes called a site map or sitemap depending on who you ask, that shows how pages connect to each other from a human’s point of view. Home leads to Services, Services leads to three sub-pages, About leads to Team and to a Contact form. This is the one that fixes menus, and it’s the one this post covers.
The client site with 47 pages and no way in
Two years ago I audited a coaching business’s WordPress site. Forty-seven published pages. The owner had been adding content for six years without ever stepping back to look at the whole thing.
I asked five people who’d never seen the site to find the contact page and book a call. Three of them gave up. The contact form existed, it was published, it worked. It just lived under a blog category called “Resources” three clicks deep, with no link from the main menu.
We spent forty minutes with a free Google Sheet listing every URL, then grouped them into six real categories instead of the fourteen menu items that had built up over the years. Bounce rate on the homepage dropped from 68 percent to 41 percent within three weeks, and calls booked through the contact form went up by nine that first month. Nothing on the site changed except the map and the menu built from it.
What you need, and it isn’t software
Here’s the part people avoid saying because it doesn’t sell a tool. You do not need paid sitemap software to fix navigation. You need forty minutes, a blank page or spreadsheet, and the willingness to click through your own site pretending you’re a stranger who’s never seen it. Every free tool below is optional. The thinking isn’t.
That said, free tools speed up the drawing once you know what you’re mapping. Here are the ones I use, all free at the tier most small sites need:
- Google Sheets: free with any Google account, best for listing every URL and tagging categories before you draw anything.
- Screaming Frog SEO Spider (free version): crawls up to 500 URLs at no cost and spits out a full list of pages, so you’re not relying on memory to find every orphaned page.
- Miro (free plan): three editable boards, unlimited team members, good for the visual box-and-line diagram once you’ve got your list.
- Octopus.do (free plan): one free sitemap project, built specifically for this job, drag and drop with no design skill needed.
- draw.io (now diagrams.net): completely free, no account limits, if you want a permanent diagram you can drop into a client report or a Google Doc.
If you’re on a low budget site builder, this is also the moment to think about whether your platform makes this easy or hard. I’ve compared both directly in Wix vs WordPress for a small business website, and menu and page structure is one of the biggest practical differences between the two once you’re past ten pages.
The five-step process
Step 1: List every single page, including the ones you forgot
Run a free crawl with Screaming Frog, or if your site is under 30 pages, click through it manually and paste every URL into a Google Sheet. Add a column for the page title and a column for last updated date. You will find pages you forgot existed. That coaching client had four blog posts from 2019 still live, still indexed, with a phone number that had changed.
Step 2: Group pages into no more than seven main categories
Seven is the practical ceiling for a top menu that people can scan. If you’ve got more than seven natural groups, some of them need to become sub-pages under a parent rather than sitting in the main navigation. This is where most sites go wrong, they let every new page earn a spot in the main menu, and five years later the menu has fourteen items and means nothing.
Step 3: Draw the actual map before you touch the menu
Open Miro, Octopus.do, or a blank page, and put your homepage at the top with a box. Draw lines down to your seven categories. Draw lines from each category down to its sub-pages. If a sub-page needs three clicks to reach from the homepage, that’s a problem you can now see instead of guess at.
This is the exact exercise I walk through in more depth in how to map your website structure before you plan new content, because the same map that fixes navigation today is what stops you from publishing pages that duplicate each other next year.
Step 4: Test it with five real people, not your team
Ask five people outside your business to find two specific things, your pricing and your contact method, and time them. If it takes more than 20 seconds on either, that page needs to move higher in the structure or get a direct link from the homepage. This single test caught the buried contact form in the story above, and it costs nothing but favours called in from friends or family.
Step 5: Rebuild the menu from the map, not the other way round
Your top navigation should mirror the top level of your map exactly. If your map has six categories, your menu has six items. Don’t add a seventh because a stakeholder likes a page, put it as a sub-item or a homepage link instead. If you’re weighing whether a landing page even needs a full navigation menu at all, I’ve laid out the case both ways in should your landing page have a navigation menu, because sometimes the right map has one path, not seven.
Where people quietly go wrong after the map is done
The map isn’t finished work, it’s a snapshot, and the uncomfortable bit nobody likes to admit is that most site maps are out of date within six months because someone adds a page without updating the diagram. Set a repeating 90-day calendar reminder to re-crawl the site and check the map still matches reality. It takes fifteen minutes with the free version of Screaming Frog and it’s the difference between a map that helps and a map that lied to you two years ago and nobody noticed.
Another spot where I see this break down: businesses add a chatbot or a live chat widget hoping it’ll paper over confusing navigation, when really the chatbot just answers the same “where’s your pricing page” question the map should have solved. If you’re considering one, I go through what works and what doesn’t in AI chatbots for small business websites, but treat it as a supplement to good structure, not a replacement for it.
What a good free map looks like in practice
For most small business sites, the finished map has:
- One homepage box at the top.
- Between five and seven main category boxes underneath it, each one matching a real menu item.
- Sub-pages nested under their parent category, never more than two levels deep from the homepage.
- A single clear path to the contact page or booking form from every single box on the map, either directly or through one click.
- Orphaned pages, the ones with no incoming links from anywhere, either deleted, redirected, or deliberately reattached to a category.
If your site also runs an email list, the same clarity matters for your sign-up and nurture pages, since a confusing site map often means a confusing subscriber journey too. I’ve compared the two most common tools for that side of things in Mailchimp vs ConvertKit, worth a read once your on-site map is sorted and you’re thinking about where email fits into the structure.
A note on doing this for a client site versus your own
When I map a client’s site, I do the crawl and the categorising myself and bring them a finished draft to react to, because business owners are too close to their own structure to see the mess objectively. If you’re doing this on your own site, ask someone outside the business, even someone who knows nothing about what you do, to do the click-through test in step 4. Their confusion is more useful data than your team’s familiarity.
Frequently asked questions
Is a website map the same thing as an XML sitemap?
No. A website map for navigation is a human-readable diagram of how pages connect, built for people clicking through your site. An XML sitemap is a machine-readable file built for search engine crawlers, and the two solve completely different problems even though they share the word “sitemap.”
What’s the fastest free tool to build a website map?
For sites under 30 pages, Google Sheets plus a hand-drawn diagram on paper or in draw.io takes under an hour. For larger sites, Screaming Frog’s free crawl (up to 500 URLs) combined with Octopus.do’s free plan gives you a full list and a visual map without paying anything.
How many items should be in my main navigation menu?
Aim for no more than seven top-level items. Beyond that, people struggle to scan the menu quickly, and pages that don’t fit those seven categories should become sub-pages instead of fighting for a spot in the main bar.
How often should I update my website map?
Every 90 days at minimum, or immediately after adding more than three new pages. A map that’s a year old usually no longer matches the live site, and an outdated map gives you false confidence that your navigation is fine when it isn’t.
