You’re looking for a specific page on a website, but the main menu isn’t helping. You type a few words into the site’s search bar, but the results aren’t useful. The sitemap, often tucked away in the footer, lists all the pages available on a site and organizes them by section. Knowing how to read it can save you time and help you find content that isn’t highlighted in the usual navigation.
HTML sitemap structure: what you actually see
Before getting into the technical details, let’s look at what a sitemap looks like to visitors. An HTML page displays a hierarchy of links, often as nested lists. Each level represents a depth within the site: the main category, then the subcategory, then the individual page.
Take a website specializing in agricultural equipment. Its sitemap might list the main product categories at the top level (fencing, animal feed, tools), followed by subcategories at the second level, and finally product pages. Browse the Agri Systems sitemap and you’ll see this structure in action: sections are grouped by topic, so you can go straight to the page you’re looking for without clicking through several menu levels.
An HTML sitemap is designed for human visitors, not robots. Many guides fail to make this distinction clear. An XML sitemap, on the other hand, is a technical file intended for search engines to help them index a site. They share the same name, but their audiences and formats have nothing in common.
Read link labels to choose the right page
You’ve found the sitemap. You scroll down the page and see dozens, sometimes hundreds, of links. How do you find the one that matches what you need?
The answer lies in the link labels. A well-named link clearly describes its destination page. If you read “Electric Fence Installation Guide,” you know what to expect. A link labeled “Learn more” or “Page 12,” on the other hand, tells you nothing.
WCAG criterion 2.4.4 (an international web accessibility standard) recommends that each link be understandable from its text alone or from its immediate context. This isn’t just a technical requirement for people using screen readers. It’s a readability principle that benefits all visitors.
Look for logical groupings
Well-designed sitemaps use section headings or hierarchical lists to separate topics. As you browse the page, first look for the section heading that matches your subject. This narrows down the area you need to explore.
A poorly organized sitemap, by contrast, displays a flat list of links with no grouping. In that case, your browser’s search function (Ctrl+F or Cmd+F) becomes your best ally. Type a keyword related to what you’re looking for, and your browser will highlight the matches on the page.
Keyboard navigation and sitemap accessibility
Have you ever tried browsing a web page without a mouse? Pressing Tab moves you from one link to the next. On a sitemap with hundreds of links, navigating by keyboard without a heading structure quickly becomes exhausting.
WCAG 2.2 (criterion 2.4.5) requires a site to offer several ways to find a page: the main menu, a search bar, and a sitemap. These three options complement one another. A sitemap isn’t a replacement for the menu; it’s an alternative when the menu isn’t enough.
For a sitemap to be genuinely usable, it needs to meet a few technical requirements that you can check yourself:
- Sections are marked up with actual headings (H2, H3), not just bold text. This allows assistive technologies to jump from one section to another.
- Links are organized into HTML lists (ul/li tags), providing a structure that screen readers can announce (“list of 8 items”).
- Every link can be reached using a keyboard, with a visible focus indicator (an outline or a color change when the link is selected).
If a sitemap doesn’t meet these requirements, it may still be usable for sighted visitors with a mouse, but it excludes part of the audience.
HTML sitemap or XML sitemap: which one do you need?
These two formats are often confused. Here’s the simple rule: if you’re a visitor looking for a page, the HTML sitemap is the one that helps you. If you manage a site and want Google to index all your pages, the XML sitemap works behind the scenes.
An XML sitemap is a file that can be read by crawlers. It contains a list of the site’s URLs, sometimes with metadata (last modified date, update frequency). Visitors normally never need to view it.
When an HTML sitemap is more useful than the menu
A sitemap can be especially valuable in certain situations:
- The site contains hundreds of pages, and the menu only shows the main categories.
- You know roughly what a page is called but don’t know which section it belongs to.
- The site’s internal search engine doesn’t work well or doesn’t exist.
- You’re exploring a site for the first time and want to understand the breadth of its content before browsing section by section.
In these cases, a sitemap gives you an overview that neither the menu nor search can provide as directly.
Find the sitemap link on any website
Most sites place a link to their sitemap in the footer. Look for labels such as “Sitemap,” “Site map,” or “Site index.” Some sites don’t offer a visible HTML sitemap but still have an XML sitemap that you can access by adding “/sitemap.xml” to the end of the site’s address.
If you can’t find either one, the site probably hasn’t considered it useful to create a sitemap. In that case, use Google’s site: search operator (for example, site:example.com keyword) to explore the domain’s indexed pages. It’s not technically a sitemap, but it serves a similar purpose: listing existing pages and letting you choose one.
A sitemap remains an underrated navigation tool. It doesn’t replace a good menu, but it makes up for its limitations. When a site is large and you know what you’re looking for but not where to find it, a sitemap is often the quickest route.
