A site map is a structured outline of every page on a website and how those pages connect. There are two distinct types: a visual site map used during design to plan navigation and hierarchy, and an XML sitemap used by search engines to discover and index pages. A good site map clarifies content strategy for humans and accelerates discovery for crawlers — both versions matter, and most websites need both.
What Is a Site Map?
A site map is a representation of a website’s content structure. Depending on context, the term means one of two very different things:
- Visual site map (design) — a diagram showing every page on the site and the relationships between them. Used during planning to define information architecture, navigation, and page hierarchy.
- XML sitemap (SEO) — a machine-readable file listing every URL on the site. Submitted to Google Search Console and Bing Webmaster Tools to help search engines discover and index pages efficiently.
Both site map types serve the same underlying purpose: making the structure of your website explicit and discoverable. The visual version is for designers, stakeholders, and content strategists. The XML version is for crawlers and ranking algorithms.
Visual Site Maps
A visual site map is one of the first deliverables in a web design project. Before any pixel is placed or any line of code is written, the design team produces a hierarchical diagram showing every planned page and how users will move between them. This document anchors every subsequent design decision.
What a Visual Site Map Contains
- Every top-level page (Home, About, Pricing, Blog, Contact)
- Sub-pages and how they relate to parent pages
- Utility pages (Privacy, Terms, 404, Search Results)
- Logged-in vs logged-out flows when relevant
- Notes on page templates and content types
- Optional priority or traffic estimates per page
Why It Matters
A clear visual site map prevents downstream chaos. Stakeholders can spot missing pages, redundant content, and confusing navigation before the design team has invested in mockups. Developers can scope estimates against the page count. SEO teams can map keyword targets to pages. Content teams know exactly what they need to write.
For larger sites, the visual site map becomes the foundation for information architecture — the discipline of organizing content so users can find what they need without thinking.
Tools for Building Visual Site Maps
- FigJam / Figma — free, collaborative, integrates with the rest of the design tool stack.
- Miro — strong for whiteboard-style collaboration with stakeholders.
- Lucidchart — purpose-built for diagrams with templates for site maps.
- Whimsical — clean and fast for simple sites.
- FlowMapp — dedicated site mapping tool with template libraries.
XML Sitemaps
An XML sitemap is a structured file that lists every URL on your site that you want indexed by search engines. The format is standardized (sitemaps.org protocol) and supported by Google, Bing, Yandex, and most other crawlers.
What an XML Sitemap Contains
For each URL, the sitemap can include:
- loc — the page URL (required)
- lastmod — when the page was last modified
- changefreq — how often the page typically changes (largely ignored by Google in 2026)
- priority — relative importance from 0.0 to 1.0 (also largely ignored)
Example XML Sitemap Entry
<url>
<loc>https://example.com/pricing</loc>
<lastmod>2026-05-20</lastmod>
</url>Sitemap Index Files
Large sites split their sitemap into multiple files referenced by a sitemap index. Google enforces a 50,000-URL and 50MB limit per individual sitemap file. E-commerce sites and large blogs typically have separate sitemaps for products, categories, posts, and images, all referenced by a master sitemap-index.xml file.
How to Create an XML Sitemap
You almost never write a sitemap by hand. Modern platforms generate one automatically:
WordPress
Plugins like Yoast SEO, Rank Math, and All in One SEO generate sitemaps automatically at /sitemap_index.xml. Each plugin lets you exclude specific post types, taxonomies, or individual URLs.
Framer
Framer generates a sitemap automatically at /sitemap.xml when you publish your site. All published pages are included by default. You can exclude specific pages via the page settings.
Webflow
Webflow generates sitemaps automatically at /sitemap.xml. You can toggle auto-generation off and provide your own custom sitemap if needed.
Next.js, React, and Custom Sites
Generate the sitemap at build time using libraries like next-sitemap. For dynamic content, build a route that produces sitemap XML on demand.
Shopify
Shopify generates sitemaps automatically at /sitemap.xml. Products, collections, pages, and blogs each get their own sub-sitemap.
Submitting Your Sitemap
After generating your sitemap, submit it to search engines so they can discover it:
- Verify your domain in Google Search Console.
- Navigate to Sitemaps in the left sidebar.
- Enter your sitemap path (typically sitemap.xml or sitemap_index.xml) and submit.
- Repeat in Bing Webmaster Tools.
- Add a reference to your sitemap in your robots.txt file: Sitemap: https://example.com/sitemap.xml
Google typically processes new sitemap submissions within a few days. Errors and indexed URL counts appear in Search Console under the Pages report.
Visual Site Map Examples
Small Business Website (5 pages)
- Home
- About
- Services
- Portfolio
- Contact
For a 5-page site, a flat hierarchy is enough. No sub-pages, no nesting. The site map fits on one screen and the user can reach any page from the main nav.
SaaS Marketing Site (20-30 pages)
- Home
- Product
- Features
- Integrations
- Security
- Solutions
- For Marketing Teams
- For Sales Teams
- For Support Teams
- Pricing
- Customers (case studies)
- Blog
- About
- Contact
This shape encourages narrow, deep navigation rather than a flat list of 25 nav items.
E-Commerce Site (100+ pages)
An e-commerce site adds product pages, category pages, search results, and account pages. Sitemap planning becomes a strategic SEO exercise — see our website navigation design guide for how to handle large product hierarchies.
Common Site Map Mistakes
Confusing Visual and XML Sitemaps
Clients sometimes ask for a “sitemap” and get an XML file when they wanted a visual diagram. Always clarify which version you need before estimating the work.
Including Non-Indexable Pages in XML
Don’t list pages that have a noindex tag, are blocked by robots.txt, or return non-200 status codes. Each broken URL in a sitemap signals carelessness to search engines.
Forgetting to Update lastmod
Out-of-date lastmod dates suggest the site is stale. Modern sitemap generators handle this automatically; manual XML edits often don’t.
Submitting Too Frequently
You don’t need to resubmit your sitemap every time you publish a post. Google re-crawls submitted sitemaps regularly. Re-submit only if you’ve made structural changes.
Hiding the Sitemap from Crawlers
If your robots.txt blocks /sitemap.xml, crawlers cannot read it. Verify your sitemap is publicly accessible.
Building a Site Map Without Content Strategy
A site map that lists every page someone could imagine is not a strategy — it’s a brain dump. Each page should map to a user goal or a business goal. Pages that serve neither should be cut or merged.
Site Map Best Practices
- Limit hierarchy depth. Three levels is plenty for most marketing sites. Deeper hierarchies bury content where users won’t find it.
- Group related pages. Solution pages live together. Resource pages live together. Don’t intersperse them randomly.
- Plan for growth. A blog category structure that works at 20 posts breaks at 200. Design the categorization for the size you expect to reach.
- Match navigation to site map. Your global nav, footer, and breadcrumbs should reflect the planned hierarchy.
- Keep XML sitemaps clean. Only include canonical, indexable, 200-status pages.
- Use separate sitemaps for distinct content types. Pages, posts, products, and images each in their own file when site size justifies it.
- Reference sitemaps in robots.txt. One line at the bottom of robots.txt directs every crawler to the right file.
Site Maps and SEO
An XML sitemap doesn’t directly improve rankings — it improves discoverability. Pages that are already linked from other pages on your site will likely be found without a sitemap. The sitemap is most valuable for new sites, pages that aren’t well-linked internally, and large sites where crawl budget matters.
Visual site maps influence SEO indirectly. A well-planned hierarchy clusters related content (helpful for topical authority), produces sensible URL structures, and supports a navigation that distributes link equity efficiently.
HTML Sitemaps
A third, less-common type of sitemap is the HTML sitemap — a human-readable page listing every URL on the site. They were popular in the early 2000s as an accessibility aid and crawler hint, but in 2026 they’re rare. Most sites get the same benefit from good internal linking and clear navigation.
HTML sitemaps still make sense for very large sites (1,000+ pages) where a flat directory of URLs helps users find specific pages they can’t locate through the main nav.
Frequently Asked Questions
Do I need a sitemap if my site is small?
For SEO, an XML sitemap is still recommended even for small sites — it ensures Google discovers every page quickly. For design, a visual sitemap is overkill for a 3-page site but valuable as soon as the site has more than ~5 pages or any kind of hierarchy.
How often should I update my XML sitemap?
If you’re using a modern CMS or site builder, the sitemap updates automatically every time you publish, edit, or delete a page. You don’t need to think about it. For manual sitemaps, regenerate whenever you make structural changes.
What’s the difference between sitemap.xml and robots.txt?
A sitemap tells search engines what pages exist and where to find them. A robots.txt file tells search engines which paths they may or may not crawl. They work together: robots.txt grants permission, sitemap.xml provides the inventory.
Can a website have multiple sitemaps?
Yes. Large sites typically split sitemaps by content type (pages, posts, products, images, video) and reference all of them from a master sitemap index file. Each individual sitemap can hold up to 50,000 URLs.
Planning a new website and need help with the site map and information architecture? See our pricing or reach out — we build Framer sites with thoughtful structure from day one.