Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

When is an HTML sitemap useful in addition to a website’s primary navigation?

When the site holds more than its menus can show, and visitors need a way to see the whole of it on one page. An HTML sitemap is a page for people: a structured list of the site’s sections and important pages, with links. It helps on large, content-heavy sites where the primary navigation reaches only the top levels, where pages sit several clicks deep, or where visitors arrive unsure which section holds what they want. It also gives every listed page one more ordinary link from a page near the top of the site. On a small site whose menu already lists everything, it duplicates the menu and can be left out.

Complex navigation and deep links

Signs that an HTML sitemap would earn its place:

  • The site has hundreds or thousands of pages, and the main menu covers a fraction.
  • Important pages are four or more clicks from the home page.
  • Sections are organized in a way newcomers do not expect, such as by department.
  • The site is a reference: documentation, a knowledge base, a public body’s information.
  • Site search is weak or absent.
  • Analytics show visitors using the footer or search heavily to find main sections.

It also helps discovery. Google’s link guidance says “Every page you care about should have a link from at least one other page on your site” (Google’s guidance on crawlable links and anchor text). A sitemap page that links to section indexes, which link on to their pages, shortens the path to deep content. It supplements contextual links and does not replace them. A page whose only link comes from a sitemap is still poorly connected.

Reader-oriented directory design

Design it as a directory someone will read, not as a dump of URLs.

A hierarchy for a content-heavy site, a regional council’s public website in this illustration:

/site-map/

Residents
  Waste and recycling
    Collection days
    Bulky item collection
    Recycling centers
  Housing
    Apply for housing
    Repairs
    Rent payments
  Council tax
    Pay your bill
    Discounts and exemptions

Businesses
  Licenses and permits
    Food premises
    Street trading
  Business rates

Planning and building
  Search applications
  Apply for permission
  Building control

About the council
  Councillors
  Meetings and minutes
  Budgets and spending
  Jobs

Each line is a link. Three levels at most.
Sections with many pages link to their own index page instead of listing every item.

Principles:

  • Follow the site’s real structure, in the order visitors think in.
  • Use plain headings and nested lists.
  • Use each page’s own name as the link text.
  • Limit depth. Where a section contains hundreds of items, such as news or products, link to the section’s index and not to every item.
  • For very large sites, split into one sitemap page per main section.
  • Link to it from the footer of every page.

Accessibility and maintenance

An HTML sitemap is recognized in accessibility guidance as one of the ways to locate content. The W3C’s guidelines include a criterion that more than one way be available to find a page within a set of pages (W3C Web Content Accessibility Guidelines 2.2), and the W3C’s explanatory document for that criterion lists a site map among its sufficient techniques, alongside a table of contents and a search function (W3C’s explanation of Success Criterion 2.4.5).

For it to serve that purpose:

  • Mark it up as headings and lists, so screen reader users can move through it by structure.
  • Keep link text meaningful out of context.
  • Make sure it works without scripts.
  • Keep it readable on a phone.

Maintenance decides whether the page helps or misleads.

Approach Advantage Risk
Generated from the CMS's page tree Stays current automatically May include pages that should not be listed
Maintained by hand Curated Goes out of date
Generated, with exclusion rules Current and curated Needs the rules kept up

Rules for a generated sitemap: exclude pages set to noindex, pages behind login, redirects, error pages, thank-you pages, and expired content. Check it on a schedule for broken links.

When not to create one

A counterexample, a small business site:

Home
Services
  Drain cleaning
  Water heaters
  Leak repair
About
Reviews
Contact

Eight pages, all reachable from the main menu, with the three service pages in its Services dropdown. A sitemap page would list the same eight links a visitor has just seen. It adds a page to maintain and nothing else.

Decide with the conditions.

Condition Create an HTML sitemap?
Every page is reachable from the main menu No
The site has a few dozen pages in a clear structure Not needed
Hundreds of pages, several levels deep Yes
A reference or public-information site Yes
A large store Yes, for categories and help pages; not for every product
Navigation is confusing and being redesigned Fix the navigation first; a sitemap can help in the meantime
The page would be built only for search engines No; that is the XML sitemap's job

Two misuses to avoid.

  • Treating the page as a place for keyword links. A sitemap filled with phrases written for rankings, or with every location and service combination, is a link block, not a directory.
  • Using it to compensate for a broken structure. If pages are unreachable through normal navigation and content links, the structure is the problem.

Check after publishing.

  1. Crawl the sitemap page: every link returns 200, none redirects.
  2. Compare it with the site’s actual sections: nothing important missing, nothing retired still listed.
  3. Look at analytics for visits to the page and clicks from it. A sitemap nobody uses on a small site can be retired.
  4. Confirm it is linked from the footer.

An HTML sitemap and an XML sitemap share a name and little else. The XML file is a machine-readable list submitted to search engines, with different rules about what it should contain. How that file supports discovery is explained in the guide to how an XML sitemap supports URL discovery on a very large website.

The criterion: build an HTML sitemap when a visitor could not see the shape of the site from its menus. If the menus show everything, they already are the site map.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *