An HTML sitemap lists all the pages available on a website as clickable links, organized by section. On Equitorne, this page brings together content related to equine industries, services, and practical resources. The question is: does this linear list of links really make information easier to find, including on mobile or with a screen reader, or does it reveal pages that the main menu doesn’t show?
HTML sitemap and XML sitemap on Equitorne: two separate pages
These two elements are often confused. An XML sitemap is a technical document intended for Google’s indexing robots. It isn’t displayed as a navigable page and has no use for human visitors.
The HTML sitemap, on the other hand, presents text links organized by topic. This is the page you visit when you’re looking for a specific section without using the dropdown menus.
| Criterion | HTML sitemap | XML sitemap |
|---|---|---|
| Audience | Human visitors | Search engines |
| Format | Web page with clickable links | Technical file that isn’t displayed |
| Keyboard navigation | Possible (links can be tabbed through) | Not applicable |
| Usefulness on mobile | Scrollable list of links | None for users |
| Updates | Manual or semi-automatic | Usually automatic |
When you visit the Equitorne website, you’re viewing the HTML version. The XML sitemap never appears in your browser unless you enter its technical URL directly.

Mobile navigation on the Equitorne sitemap: linear list versus dropdown menu
On a phone screen, multi-level dropdown menus can cause practical problems. Nested subcategories require precise taps, and a misplaced tap often sends you back to the home page. The sitemap avoids this problem with a scrollable vertical list, where each link has its own line.
This linear structure offers a measurable benefit: fewer actions are needed to reach a page buried deep in the site. Instead of navigating three menu levels (category, subcategory, page), you just scroll and tap once.
Potential pain points on small screens
A linear list isn’t perfect. If the sitemap contains dozens of links without any visual grouping, scrolling becomes tedious. Two factors determine how easy it is to read on mobile:
- Section headings that break the list into identifiable blocks, making it possible to jump straight to the section you’re looking for
- Clickable areas large enough to prevent accidental taps on nearby links
- Whether the page includes a search function, which can make up for a long list when you know the exact term
Without topic-based sections, a sitemap loses its advantage on mobile once it contains more than a few dozen pages.
Screen reader accessibility: what a well-structured sitemap reveals
Screen readers (NVDA, VoiceOver, JAWS) navigate a web page by following the order of its HTML code. A dropdown menu with complex JavaScript can be opaque to these tools: submenus don’t always open, and “open/closed” states aren’t consistently announced.
An HTML sitemap is an accessible alternative by default because it relies on native web elements: text links grouped into lists. A screen reader can go through them one by one, announce their labels, and let users navigate between section headings with keyboard shortcuts.
What it takes to make a sitemap truly accessible
A sitemap isn’t automatically accessible. Heading hierarchy must be respected (H2 followed by H3, with no skipped levels) so screen readers can offer a page outline. If all the links are at the same level, with no section markup, users hear a flat list of dozens of items with no landmarks.
Link labels matter too. A link called “Learn more” or “Click here” conveys no information out of context. A screen reader that lists all the links on a page displays only their anchor text. Clear labels such as “Competition calendar” or “Breeder directory” make the sitemap genuinely navigable.

Pages that are hard to find without the Equitorne sitemap
The sitemap does more than duplicate the main menu. It makes pages visible that don’t appear in any menu, either because they were created after the navigation was last updated or because they’re too specific to fit into a three-level hierarchy.
This is particularly common on sites that regularly publish new content, such as technical guides, news articles, and event pages. This content exists but remains hidden from the menu, accessible only through internal search or the sitemap.
Broken links: the risk of an outdated sitemap
A sitemap that isn’t updated after a redesign or a reorganization of sections accumulates broken links. Each dead link undermines user trust and makes the page useless for navigation.
- Regularly check that every link in the sitemap leads to an existing page, not a 404 error
- Update labels when a section is renamed to avoid confusion between the old and new names
- Remove entries for deleted pages instead of leaving them in place
A regularly updated sitemap remains a reliable navigation tool. One that’s abandoned after it’s created becomes a trap that frustrates users.
The Equitorne sitemap provides a direct shortcut to all published content, including pages not listed in the main menu. Its effectiveness depends on two practical factors: sections with clear labels and updates that keep pace with new publications. On mobile and with a screen reader, it’s the quality of the structure—not simply its existence—that determines whether the sitemap does its job.



