HTML Sitemap vs XML Sitemap: What Each Does and If You Need Both

Two different things are called a sitemap, and mixing them up leads to wasted work. An XML sitemap is a machine-readable file that lists URLs for search engines. An HTML sitemap is an ordinary web page of links that people can read. They share a name and a goal, helping someone find your pages, but they have different readers, different formats and different ways of being used.

This guide is for site owners and developers who have been told to "add a sitemap" and are not sure which one is meant. You will learn what each file is for, what search engine documentation says about them, how to decide whether your site needs one, the other or both, and how to build and check them.

Neither type makes a page rank, and neither is required. Google states that a sitemap helps search engines find content but gives no assurance that every listed URL will be crawled or indexed. An HTML sitemap is a navigation aid for people that also happens to contain crawlable links.

Before you begin

Access: the ability to publish a file at your site root, edit templates (for the footer link to an HTML sitemap) and use Search Console.
Know your size: count the pages you want in search results. Google's sitemap overview describes a site of about 500 pages or fewer as small, and says a small, comprehensively linked site may not need an XML sitemap at all.
Know your navigation: can a visitor reach every important page by clicking from the home page? A crawl or a quick audit will tell you. See orphan pages.
Risk: low. Adding either type does not remove anything from search.
Back up: keep a copy of your current robots.txt and any existing sitemap.

The difference in one table

	XML sitemap	HTML sitemap
Reader	Search engine crawlers	People (and crawlers that follow its links)
Format	XML file following the sitemap protocol	A normal web page with links
Location	Any public URL, usually the site root, for example `/sitemap.xml`	Any page, usually linked from the footer
Submitted to search engines	Yes, in Search Console or via robots.txt	No, it is simply a page
Extra data	Optional `lastmod`, plus image, video and news extensions	None
Limits	50,000 URLs and 50 MB uncompressed per file	Whatever is usable on a page
Main benefit	Discovery and monitoring	Navigation and a second route to pages

What the official documentation says

For XML sitemaps, Google describes a sitemap as a file that provides information about the pages, videos and other files on your site, which search engines read to crawl more efficiently. It lists situations where one helps: a large site, a new site with few external links, and sites with rich media or news content. It lists situations where you might not need one: a small site, a site that is comprehensively linked internally, and a site that does not need video, image or news results. Submission does not ensure crawling or indexing.

For HTML sitemaps, Google's current sitemap documentation does not describe them as a feature. That is useful to know. An HTML sitemap is not read in a special way. It is a page, and the same link rules apply as for any other page. Google discovers links in <a> elements with an href, says every page you care about should be linked from at least one other page, and notes that, for large catalogues, category pages that do not link directly to every product may leave some products undiscovered. In its e-commerce guidance, sitemaps and feeds are described as fallback sources for pages a crawler would not otherwise find.

The Web Content Accessibility Guidelines add the human angle. Success criterion 2.4.5, Multiple Ways, at level AA, asks that a page in a set of related pages can be reached in more than one way, and lists a site map among the sufficient techniques, alongside search, a table of contents and links from the home page to every page. So an HTML sitemap can support accessibility and usability even when it adds nothing for crawlers.

Step-by-step instructions

Step 1: Audit how pages are reached today

Why: the right answer depends on whether your pages are already easy to find.

Action: run a crawl starting from the home page and list every indexable URL it did not reach by following links. Compare against the URLs in your CMS or database. Pages that appear only in the database are orphans.

Confirm: you have a count of pages that are reachable by links and a count that are not.

Why: a sitemap of either type is a patch. Real navigation, category pages and contextual links serve visitors better and make the sitemap less critical. See internal linking strategy and site architecture.

Action: connect orphaned pages from relevant parents. Make category and listing pages link to the items in them with plain <a href> links.

Confirm: a re-crawl shows fewer or no orphaned pages.

Step 3: Create an XML sitemap

Why: it gives search engines a list of canonical URLs and gives you reporting in Search Console.

Action: generate a UTF-8 XML file with the canonical, indexable, HTTP 200 URLs. Use absolute URLs. Stay within 50,000 URLs and 50 MB uncompressed per file, using a sitemap index if needed. Add lastmod only when it is accurate. Publish at the site root, reference it in robots.txt with a Sitemap: line, and submit it in Search Console. Full steps are in how to create an XML sitemap; for large sites see sitemap indexes. If your CMS already produces a sitemap, as Google notes many do, use that instead of building a second one.

Confirm: the Search Console Sitemaps report shows Success.

Step 4: Decide whether an HTML sitemap earns its place

Why: it costs maintenance, so it should solve a real problem.

Action: consider one when any of these is true:

Your site is large or deep, and visitors struggle to find sections.
You want an extra, simple route to every main section for accessibility.
You cannot easily make every important page reachable through the main menu and category pages.

Skip it when your site is small, the menu already reaches everything, and users have a working search. A small brochure site seldom needs one.

Confirm: you can state in one sentence what the page will do for visitors.

Step 5: Build the HTML sitemap well

Why: a badly built one is just a long list nobody uses.

Action:

Create a normal page, for example /site-map, and link it from the footer so it sits on every page.
Group links by section with headings that match your navigation.
Use plain <a href> links with descriptive text. Google asks for anchor text that is descriptive and avoids generic text such as "click here".
Include the pages people actually look for, not every tag and parameter URL.
For very large sites, show top-level sections and link to deeper listing pages rather than putting tens of thousands of links on one page.
Generate it from your content system where possible, so it never lists deleted pages.

<nav aria-label="Site map">
  <h2>Shop</h2>
  <ul>
    <li><a href="/shop/mugs">Mugs</a></li>
    <li><a href="/shop/plates">Plates</a></li>
  </ul>
  <h2>Help</h2>
  <ul>
    <li><a href="/help/shipping">Shipping and returns</a></li>
    <li><a href="/contact">Contact us</a></li>
  </ul>
</nav>

Confirm: every link works, and the page is reachable in one click from any page.

Step 6: Keep both consistent

Why: disagreement between files and pages produces confusing signals.

Action: list the same canonical URLs in both. Do not include redirected, noindexed or blocked URLs in either. If you remove a page, remove it from both. Do not submit the HTML page as a sitemap in Search Console; submit only the XML file.

Confirm: a script that compares the two lists shows no mismatch beyond intentional differences.

Step 7: Monitor

Why: both types go stale.

Action: check the Sitemaps report after changes, and re-crawl the HTML sitemap page monthly for broken links. See sitemap 404 and 500 errors.

Confirm: no listed URL errors or redirects.

Final verification checklist

You know which problem each sitemap solves on your site.
The XML sitemap lists only canonical, indexable, 200 URLs, within size limits.
The XML sitemap is referenced in robots.txt or submitted in Search Console.
Navigation already reaches your important pages, or the gaps are logged.
The HTML sitemap, if present, is linked site-wide and grouped sensibly.
All HTML sitemap links are real anchors with descriptive text.
No deleted, redirected or noindexed URL appears in either sitemap.
Neither sitemap is described as a ranking tool.

Common mistakes to avoid

Submitting the HTML page as a sitemap. Search Console expects a sitemap file.
Relying on a sitemap to fix poor navigation. Fix the links.
Dumping every URL on one HTML page. Group by section and keep it usable.
Listing parameter and duplicate URLs. Use canonical addresses only.
Letting the XML file go stale. Generate it from live data.
Assuming a sitemap forces indexing. Google says it does not.
Building an HTML sitemap with script-only links. Crawlers and assistive tools need real anchors.
Forgetting accessibility. A site map is one of the techniques for multiple ways to reach pages.

Frequently asked questions

Do I need both?

Not necessarily. Many small sites need neither file as separate work, because navigation reaches every page and their CMS already produces an XML sitemap. Larger sites usually benefit from the XML file, and some choose an HTML page for visitors.

Does an HTML sitemap help SEO?

Google's documentation does not present it as a ranking factor or special feature. It can help people and, through its links, help crawlers reach pages. Judge it by whether visitors use it.

Is `sitemap.html` the same as `sitemap.xml`?

No. They are different things. A sitemap.xml file holds XML in the sitemap format for crawlers. A sitemap.html page, or any page you call a site map, is an ordinary web page of links for people.

Can Google use a text file instead of XML?

Yes. Google's build guide lists text files with one URL per line, as well as RSS, mRSS and Atom feeds, alongside XML. XML is the most versatile because it supports extra data for images, video, news and localized versions.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.