SEO

Website Sitemap: What It Is, the Three Kinds, and How to Plan One

Search for "website sitemap" and you get three different things under one name: a diagram designers draw, a file search engines read and a page visitors click. Most guides blur them. This one separates them, says which one a small business needs, and walks through planning your own with sources dated 12 November 2026.

Website Sitemap: What It Is, the Three Kinds, and How to Plan One

Key takeaways

  • "Sitemap" means three things. A visual sitemap is a planning diagram, an XML sitemap is a file for search engines, and an HTML sitemap is a page for visitors.
  • Plan first, then publish. The Nielsen Norman Group says to make the sitemap last in the information architecture work, once the structure is settled. The diagram comes before the build; the XML file comes after it.
  • Most small sites need the XML file and the diagram. Google says a site of roughly 500 pages or fewer, well linked from the home page, may not need a sitemap at all, but it costs little to have one.
  • An HTML sitemap is optional. In the Nielsen Norman Group's 2008 study only 7% of people turned to one on their own.
  • A sitemap is a hint, not a guarantee. Google says submitting one does not mean every page will be crawled and indexed.

The short answer

A website sitemap is a list or map of the pages on a site and how they connect. Before you build, you draw a visual one to plan the structure. After you launch, you publish an XML one so search engines can find your pages, and you can add an HTML one for visitors. A typical business site needs the first two and can skip the third.

Who is writing: we are Amariq, a web design studio. We plan a sitemap for every site we build, and we generate the XML file for ours from the site itself, which listed 357 addresses on 12 November 2026. The rules below come from Google's documentation and the Nielsen Norman Group, read the same day.

What the current results cover, and what is missing

On 12 November 2026, Google (US, English) showed an AI Overview, Google's own sitemap documentation, an online sitemap generator, GoDaddy and Semrush explainers, Backlinko's "19 sitemap examples" (updated 24 October 2026), Figma's sitemap template and Webflow's glossary entry. They explain the types well. What they do not do is tell a small business which type to spend time on, in what order, or how many pages a plan needs before a diagram helps. That is the aim here.

The three kinds of sitemap

Visual sitemapXML sitemapHTML sitemap
What it isA diagram of pages and how they connectA machine-readable file listing your page addressesAn ordinary web page listing your pages
Who reads itYou, your designer, your clientGoogle, Bing and other search enginesVisitors
When you make itBefore the buildAfter launch, and kept up to dateOptional, any time
Where it livesA design file or a documentUsually /sitemap.xmlA page called "Site Map"
Does it affect search?Indirectly, through a clearer structureHelps discovery; no guaranteeA little, through internal links

Visual sitemap: plan the structure first

Researchers at the Nielsen Norman Group (NN/g) describe a sitemap as a visual diagram of how a site's content is organised, used as a planning and reference tool to see how pages and sections fit together and to spot content gaps. It adds that a sitemap is one part of the wider information architecture, not the whole of it, and that it is usually shared inside a team and not shown to visitors. Its article on the subject was published on 3 September 2023 and last reviewed on 7 August 2026.

The activities NN/g lists as feeding into the structure are, in order:

  1. Content inventory. List what you have, usually at the start of a redesign.
  2. Content audit. Decide what to keep, remove or update.
  3. Naming. Settle the words you use for categories, from general to specific.
  4. Research. Card sorting, tree testing and usability testing show whether people can find things.
  5. The sitemap itself, drawn last, once the structure is clear.

Plan yours in seven steps

  1. Write down what the site must do. Get enquiries, take bookings, sell products. One line.
  2. List every page you might need, then cross out the ones nobody would look for.
  3. Group them by what a visitor wants, not by how your business is organised inside. "Prices" belongs near the top even if your accounts team calls it something else.
  4. Choose the top level. These become your main menu. Five to seven is a common range; it is a habit in design, not a standard.
  5. Put the rest underneath, one level at a time. A service page sits under Services; a case study under Work.
  6. Draw it. A box for each page, lines for parent and child. Use one colour for pages that exist, another for pages still to write.
  7. Check it against real tasks. Ask a friend to say where they would look for your phone number, your price and your return policy, pointing at the diagram.

Backlinko's guide advises limiting a planning diagram to core pages and pathways, defining a key for shapes and colours, and sharing it early, because changing a diagram is far easier than restructuring a built site. That fits with what we do: we agree the sitemap with the client before any design starts.

An example for a local service business

LevelPages
HomeHome
Top levelServices, Pricing, Work, About, Reviews, Contact
Under ServicesOne page for each main service, for example Boiler repair, Boiler install, Servicing
Under WorkIndividual case studies
Under AboutTeam, Areas we cover
Utility, in the footerPrivacy policy, Terms, Cookie notice

That is about twenty pages, and every one of them is reachable from the main menu or one level below it. A site with this structure also gives you a natural place for service pages, a contact page and a pricing page.

XML sitemap: tell search engines what you have

Google's "Build and submit a sitemap" page, read on 12 November 2026, sets out the rules.

QuestionGoogle's answer
Which formats?XML, RSS, mRSS and Atom 1.0, or a plain text file of addresses. Google has no preference
How big can one file be?50 MB uncompressed or 50,000 URLs. Larger sites split into several files tied together by a sitemap index
What does Google ignore?The priority and changefreq tags
What about lastmod?Used only if it is consistently and verifiably accurate. A change to a copyright date does not count
What belongs in the file?Fully qualified addresses of pages you want in search results, preferably the canonical version, UTF-8 encoded
Where does it go?Anywhere, but the site root is recommended, because a file only affects addresses in its own folder and below unless you submit it in Search Console
How do I submit it?In the Search Console Sitemaps report, through the Search Console API, or by adding a Sitemap line to robots.txt

Google's overview page makes a point the generators rarely do: you may not need a sitemap. It says a site of roughly 500 pages or fewer, counting only pages you want in search, where every important page is linked from the home page, may not need one, while a new site with few links from elsewhere, or one with rich media, may benefit. It also says a sitemap "doesn't guarantee" every item will be crawled and indexed.

In practice, many website platforms can make one for you, so look in your platform's SEO settings first. Our robots.txt guide shows the one line that points to it. If a page is missing from search, a sitemap alone will not fix it; our guide on why your website is not showing on Google lists the usual causes. For Bing, see Bing Webmaster Tools setup.

HTML sitemap: optional, and mostly for lost visitors

An HTML sitemap is a regular page, usually linked from the footer, that lists the main pages in a hierarchy. NN/g's Jakob Nielsen studied them and wrote up the findings in "Site Map Usability" on 1 September 2008. The numbers are old, but they remain the best-known measurement:

FindingNumber
People who turned to a site map on their own7% in the second study, down from 27% in the first
People who found a page listing every part of the site, when asked67%
Task success with a multi-column layout against a single column61% against 47%

NN/g's advice was to call the page "Site Map" everywhere you link to it, keep it plain and static, and show the structure in one compact view. It still recommended one because it is the only feature that gives a true overview of a site's content and helps people who are lost. Backlinko adds that an HTML sitemap is not a substitute for good design. If your menu already works, you do not need one; if your site is large or deep, it is worth adding.

Which should you make?

Your situationDo this
Planning a new site or redesignA visual sitemap, before anything is designed
Any live siteAn XML sitemap, submitted in Search Console and listed in robots.txt
A large site, or one with deep levelsAdd an HTML sitemap
A tiny site, a single pageSkip the diagram; an XML file is still harmless

A website sitemap checklist

CheckDone?
Purpose of the site written in one line
Every page listed, then pruned
Pages grouped by what visitors want
Five to seven main menu items
Diagram drawn and shared before design
XML sitemap exists and loads at /sitemap.xml
It lists only pages you want in search, with full addresses
lastmod dates are accurate, not faked
Submitted in Search Console and linked from robots.txt
HTML sitemap, if used, is called "Site Map" and linked from the footer

Our website redesign SEO checklist and website audit checklist show where the sitemap fits when a site is rebuilt or reviewed.

How Amariq can help

Before any design starts, we draw the sitemap with you and agree it. The finished site goes live with its XML file in place, on whichever platform fits your plans. A quote comes from the scope, not the clock, and the work becomes yours on final payment. See our web design service for how a project runs.

Frequently asked questions

What is a website sitemap?

A list or map of the pages on a site and how they connect. It can be a diagram used for planning, an XML file for search engines or a page for visitors.

What is the difference between an XML sitemap and an HTML sitemap?

An XML sitemap is a file for search engines that lists page addresses, usually at /sitemap.xml. An HTML sitemap is an ordinary page for people, carrying a link to each main page.

Is a sitemap necessary for SEO?

Not always. Google says a site of roughly 500 pages or fewer that is well linked from the home page may not need one, and that a sitemap does not guarantee pages are crawled or indexed. It is still a cheap hint, especially for a new site with few links pointing to it.

How do I find a website's sitemap?

Try the address followed by /sitemap.xml, then look at the robots.txt file, where a Sitemap line often gives the exact location. If you run the site, your platform's SEO settings or Search Console will show it.

How do I submit a sitemap to Google?

Add it in the Search Console Sitemaps report, submit it through the Search Console API, or put a Sitemap line with the full address in your robots.txt file.

How many pages should a sitemap have?

An XML file can hold up to 50,000 addresses or 50 MB uncompressed before you need to split it. A planning diagram has no published limit; as Backlinko advises, keep it to core pages and pathways, and group them into sections if it grows large.

Does Google use priority and changefreq?

No. Google's sitemap page says it ignores both. It uses lastmod only when the date is consistently and verifiably accurate.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles