An XML sitemap is a machine-readable file that lists your site’s URLs along with metadata like last-modified dates, helping search engine crawlers discover and prioritize what to index. An HTML sitemap is a human-readable page on your site that lists your major URLs in a navigable format, designed to help visitors find content when your menu can’t show everything.
These two files share a name and almost nothing else. They serve different audiences, live in different places, and solve different problems. The confusion between them costs business owners real time, and occasionally real rankings.
What an XML Sitemap Actually Does
An XML sitemap is a structured file, usually located at yourdomain.com/sitemap.xml or /sitemap_index.xml, that tells search engines which URLs you want them to know about. Each entry can include metadata like the last modification date (lastmod), and historically change frequency and priority, though Google largely ignores the latter two.
Think of it as a curated index card you hand to Googlebot. The crawler doesn’t have to find every page through internal links alone. Submitting that file to GSC gives Google a direct, authoritative list of what you want crawled.
What it does NOT do is force indexing. Google decides what to index based on quality, uniqueness, and authority. The sitemap simply makes discovery faster.
What an HTML Sitemap Actually Does
An HTML sitemap is a regular page on your website, usually at /sitemap or linked from the footer, that lists your important URLs in a way humans can read and click. It exists primarily to help visitors who can’t find what they need through the main navigation.
The classic use case is a 5,000-product e-commerce store where the main menu shows top categories but visitors searching for something specific need a back-up route. Large publishers, university sites, and government domains often have HTML sitemaps for the same reason.
The Core Difference in One Sentence
XML sitemaps are written for crawlers. HTML sitemaps are written for people. They are not interchangeable, and one is not a “better version” of the other.
When Each One Makes Sense
- XML sitemap: almost every site benefits from one. If you have more than a handful of pages, generate it and submit it to GSC. There is no scenario where a small-business site is worse off for having a clean XML sitemap.
- HTML sitemap: most modern sites can skip it. If you run a 20-page consultancy site or a small content blog, an HTML sitemap is a relic that adds maintenance overhead without meaningful upside.
- When an HTML sitemap is worth it: large content sites with hundreds of articles across many categories, e-commerce stores with thousands of SKUs, or membership and resource sites where users genuinely need a directory-style overview.
If you’re not sure, ask: would a real visitor ever look for one? If the honest answer is no, you don’t need it.
How They Coexist
Having both is fine. They don’t compete, conflict, or confuse search engines. The XML file sits in your root directory and gets submitted to GSC. The HTML page lives in your site like any other page and gets linked from the footer.
What you should not do is build only an HTML sitemap and assume Google will treat it as a replacement. Google can crawl an HTML sitemap, but it won’t get the structured signals, the lastmod dates, or the GSC reporting that comes with a proper XML file.
How WordPress Handles Each
- XML sitemaps: WordPress core has generated a basic XML sitemap at
/wp-sitemap.xmlsince version 5.5. Yoast SEO and Rank Math replace the core sitemap with a richer version at/sitemap_index.xml, automatically including or excluding post types and taxonomies based on your settings. - HTML sitemaps: not built into WordPress core. Most SEO plugins offer an HTML sitemap feature, or you can use a dedicated plugin. If you don’t actively need one, don’t install a plugin just to have it.
Practical workflow for most WordPress small-business sites: enable Yoast or Rank Math, confirm the XML sitemap loads, submit it to GSC once, move on. Skip the HTML sitemap unless you have a clear reason.
Common Mistakes
- The XML sitemap was never submitted to GSC. Having one isn’t enough. Submitting through GSC gives you indexing reports, error notifications, and confirmation Google is processing it. Takes 90 seconds and most owners skip it.
- The sitemap includes URLs that shouldn’t be there. Noindexed pages, redirected URLs, 404s, staging leftovers. A sitemap should only contain canonical, indexable, 200-status URLs.
- Massive sitemaps with no splitting. Google’s limit is 50,000 URLs and 50MB uncompressed per file. Yoast and Rank Math handle splitting automatically; custom-built sitemaps often don’t.
- Treating an HTML sitemap as a fix for bad navigation. If users need an HTML sitemap to find your core service pages, fix the menu and the internal linking first.
The Bottom Line
Generate an XML sitemap, submit it to GSC, and keep it clean. That’s the version that actually moves the needle for discovery and indexing on a small-business site.
The HTML sitemap question is mostly a non-question for sites under a few hundred pages. If you’re running a large content operation or sizeable e-commerce store, it’s worth considering. Otherwise, focus on building navigation and internal links your visitors and Google can both follow naturally.