Visual Sitemap vs XML Sitemap: What's the Difference?
Visual sitemap vs XML sitemap: what each one is, who it is for, when to use it, how to make one, and how a planning sitemap becomes the file search engines use.
"Sitemap" means two different things in web projects. A visual sitemap is a diagram of a site's pages and how they relate, made for people. An XML sitemap is a machine-readable file that lists a site's URLs, made for search engines. The comparison of visual sitemap vs XML sitemap comes up because both share a name, and teams often assume one replaces the other. They don't. They do different jobs at different stages of a project, and the best results come from making one lead into the other.
This guide explains each type, when to use it, how to make it, and how they connect, with a worked example for a fictional online store, Jenny's Pet Supplies.
What is a visual sitemap?
A visual sitemap is a diagram of a website's structure. Each page is a box or card, and lines show which pages sit under which. It usually starts with Home at the top and branches out into sections and sub-pages.
A good visual sitemap also shows:
- Navigation zones: main navigation, utility pages (search, account, cart) and footer pages (privacy, terms).
- Page types: whether a page is a product listing, an article, a contact page, and so on.
- Status: which pages are drafted, in review or approved.
- Notes: decisions and open questions, such as "Prices change each season".
Its audience is people: clients, project managers, designers, writers, developers. Its job is to help them agree the structure of a site before it is built, or to understand the structure of a site that already exists.
What is an XML sitemap?
An XML sitemap is a file, usually at /sitemap.xml, that lists the URLs on a site you want search engines to find. It follows the sitemaps.org protocol, which the major search engines support. Each entry can include the last modified date, and multilingual sites can add hreflang links that point to each language version of a page.
A minimal XML sitemap looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.example.com/</loc>
</url>
<url>
<loc>https://www.example.com/shop/dogs</loc>
</url>
</urlset>
Large sites split their URLs across several files and list them in a sitemap index. Its audience is crawlers. It has no layout, no hierarchy lines and no notes. Its job is to help search engines discover pages, especially new pages or ones that are poorly linked.
Visual sitemap vs XML sitemap at a glance
| Visual sitemap | XML sitemap | |
|---|---|---|
| Audience | People: clients, teams, stakeholders | Search engine crawlers |
| Format | Diagram (on screen, PDF or image) | XML file at a public URL |
| Shows hierarchy | Yes, with parent and child pages | No, it is a flat list of URLs |
| Includes unpublished pages | Yes, including planned pages | No, only public, indexable URLs |
| Includes notes and status | Often | No |
| When it is made | During planning, before the build | After launch, usually generated by the CMS |
| Main purpose | Agree and communicate structure | Help pages get discovered and indexed |
When to use each
Use a visual sitemap when
- You are planning a new website and need to agree what pages it will have.
- You are redesigning a site and want to compare the current structure with the proposed one.
- You need client sign-off on navigation before design starts.
- You are briefing designers, writers or developers on the scope of the work.
- You want to track content progress page by page across a large site.
Use an XML sitemap when
- Your site is live and you want search engines to find all its important pages.
- The site is large, or has pages that few other pages link to.
- You have just launched or migrated a site and want new URLs crawled quickly.
- The site has several languages and you want to tell search engines which pages are translations of each other.
Most sites need both: a visual sitemap during planning and an XML sitemap once the site is live.
How to make a visual sitemap
- Start with Home and the main navigation. List the top-level sections you expect visitors to look for first.
- Add sub-pages. Under each section, add the pages it contains. Keep labels short and written for visitors.
- Separate utility and footer pages. Search, account and cart pages don't belong in the main tree. Nor do legal pages.
- Mark page types. Note which pages share a layout, as these will share a template.
- Check depth and balance. Important pages should be reachable within two or three clicks. A section with 40 children and one with two may need rebalancing.
- Review it with stakeholders. Share it, collect comments on specific pages, and revise.
- Get approval before content and design start.
You can draw a visual sitemap on a whiteboard, in a general diagram tool or in a dedicated sitemap builder. For redesigns, start from the existing site: import its current XML sitemap, or crawl it, to get the current structure as a starting point.
How to make an XML sitemap
- Let the CMS generate it. Most content management systems can produce an XML sitemap automatically, either built in or through an extension. This is the most reliable option, because it updates as pages are published.
- Include only canonical, indexable URLs. Leave out redirects, noindex pages, duplicates and pages behind a login.
- Use full, absolute URLs, including the protocol and domain.
- Split large sites. A single sitemap file is limited to 50,000 URLs and 50 MB uncompressed. Use a sitemap index above that.
- Add hreflang links for language versions if the site is multilingual.
- Tell search engines where it is. Reference it in
robots.txtand submit it in each search engine's webmaster tools. - Keep it current. A sitemap full of removed or redirected URLs wastes crawl effort.
How the two relate
The visual sitemap is the plan. The XML sitemap is one of the outputs of that plan once the site exists. If the planning sitemap includes each page's slug, its path in the hierarchy and whether it should be indexed, you already have almost everything an XML sitemap needs.
The relationship also runs the other way. When you redesign a site, the old site's XML sitemap is a quick way to see what exists today. Importing it into a visual sitemap tool turns a flat list of URLs into a tree you can review, reorganise and plan from. See the website content migration guide for how that fits into a full redesign.
Example: Jenny's Pet Supplies
Jenny's Pet Supplies is a fictional family-run pet store chain with five stores, an online shop, a grooming salon and monthly adoption days. Here is part of its visual sitemap, written as an outline:
- Home
- Shop
- Dogs
- Dog food
- Dog toys
- Cats
- Cat food
- Cat toys
- Dogs
- Grooming Salon
- Book an appointment
- Adoption Days
- Stores
- Store locations
- About us
- Contact
- Shop
- Utility pages: Search, My Account, Cart
- Footer pages: Delivery & Returns, Privacy Policy, Terms
In the visual version, each of these is a card. The team can see that "Book an appointment" sits under Grooming Salon, that Cart is a utility page rather than part of the main navigation, and which pages are still in draft.
The XML sitemap for the same site, once live, is a flat list of public URLs such as /shop/dogs/dog-food, /grooming-salon/book-an-appointment and /delivery-returns. It leaves out My Account and Cart, because those pages aren't useful in search results and are usually set to noindex. If the site also had a Spanish version, each entry would carry hreflang links to its translation, for example /es/tienda/perros.
How PagePot helps
PagePot's visual sitemap builder has separate bands for main, utility and footer pages, page types, statuses and notes on each card. You can start a project by importing an existing XML sitemap (including sitemap indexes and .gz files), and the hierarchy is built from the URL paths. When the plan is ready, you can export the visual sitemap as a PDF or PNG for people, and a search-engine sitemap XML with hreflang links for other languages. Slugs, robots settings and other search fields are planned per page in SEO planning.
FAQ
What is the difference between a visual sitemap and an XML sitemap?
A visual sitemap is a diagram of a site's pages and hierarchy, made for people planning or reviewing the site. An XML sitemap is a file listing public URLs, made for search engines to discover pages.
Do I need both a visual sitemap and an XML sitemap?
Usually, yes. A visual sitemap helps your team and client agree the structure during planning. An XML sitemap helps search engines index the site once it is live. They don't replace each other.
Does a visual sitemap help SEO?
Not directly, because search engines never see it. Indirectly it helps a lot: it leads to a clear hierarchy, sensible URLs and good internal linking, all of which matter for search.
Can I turn an XML sitemap into a visual sitemap?
Yes. Because URLs usually follow the site's folder structure, a tool can read the paths and rebuild the tree. This is a fast way to map an existing site before a redesign.
Where should an XML sitemap be located?
Usually at the root of the site, at /sitemap.xml. Reference it in your robots.txt file and submit it to search engines through their webmaster tools.



