If you Google how to create a website sitemap, you'll find tool makers (Canva, Figma, Miro) telling you to use their visual templates, and Google telling you to craft an XML file and submit it to Search Console. Both are right, but only after you answer a prior question: what kind of sitemap do you actually need right now?
Google Search Central's crawl documentation still treats the XML sitemap as the file that lists URLs a crawler might otherwise miss, with a hard cap of 50,000 URLs per file (Source: Google Search Central). That number is why a visual IA map and an XML crawl file are different jobs. This guide shows how to create a website sitemap for both.
TL;DR
- A sitemap is your website's map, but there are two distinct types: visual sitemaps for planning page hierarchy and XML sitemaps for helping search engines find your content.
- Choose your sitemap type by your job to be done: building a new site → visual sitemap first; launching an existing site → XML sitemap first. Many guides skip this framing.
- How to create a website sitemap depends on whether you're planning IA or helping Google index your pages. A visual sitemap takes 5 steps: define scope, list pages, group by hierarchy, diagram the structure, and validate with stakeholders.
- XML sitemaps can be generated automatically (most CMS platforms), via online generators for small sites, or hand-coded for custom projects.
- Most sitemap problems aren't technical, they're architectural. Pages buried four levels deep, orphaned content, and inconsistent naming cost far more crawl budget than a malformed XML tag.
A sitemap is a structured listing of the pages on your website, but that structure serves two very different audiences. Visual sitemaps help humans (designers, stakeholders, content teams) agree on the page hierarchy before building. XML sitemaps help search engine crawlers discover all your pages so they can be indexed and ranked.
This guide walks through both paths to help you learn how to create a website sitemap that fits your actual project stage, with a worked example, a mistakes rubric, and the connection to broader content strategy.
Your First Decision When Learning How to Create a Website Sitemap
Before any tool, template, or generator, ask one question: What job is this sitemap doing?
| If your goal is… | You need a… | Starts with… |
|---|---|---|
| Planning site structure before design or redesign | Visual sitemap (also called an IA map) | A diagramming tool (Miro, Figma, pen+paper) |
| Getting all pages indexed by Google | XML sitemap | A CMS plugin, generator, or manual XML |
| Helping visitors find content from the homepage | HTML sitemap (a page listing all links) | A simple HTML list in footer or /sitemap page |
| Auditing crawl coverage in Search Console | XML sitemap (submitted via index) | Google Search Console + structured sitemap file |
Most teams need the visual sitemap first, it's your blueprint. The XML sitemap comes later, during or after launch. Knowing this distinction before you start is the fastest way to learn how to create a website sitemap without going down the wrong path.
The table is a filter, not a menu. If you are still arguing about page names, stay on the visual row. If the site is already live and Search Console shows "Discovered, currently not indexed," skip the diagram and build the XML file. How to create a website sitemap for a redesign is almost always visual first, then XML on the night you ship. Teams that reverse that order generate a crawl file for a hierarchy they have not agreed on, then spend a week renaming URLs. Write the job in one sentence at the top of the board so the rest of the workshop cannot drift into a tool debate.
How to Create a Website Sitemap: The Visual Approach
A visual sitemap is a diagram of your website's page hierarchy. It's not code, it's boxes and lines showing how pages relate to each other. Designers and information architects build these before wireframes to settle what pages exist and how they connect.
A Step-by-Step Guide on How to Create a Website Sitemap Visually
Step 1: Define scope and audience. What is the website for? Who uses it? Write a one-sentence purpose statement. For a portfolio site: "A single portfolio site for a product designer, with work samples, about info, and a contact form."
Step 2: List every page. Brainstorm all pages the site will need. At this stage, nothing is too granular. Common top-level pages:
- Home
- About / Team
- Products / Services
- Blog / Resources
- Contact
- Case Studies / Portfolio
- FAQ
- Legal (Privacy, Terms)
Step 3: Group by hierarchy. Decide which pages sit at Level 1 (main navigation), Level 2 (sub-pages), and Level 3 (deeper content). Google recommends keeping content within 3 clicks from the homepage for good crawl efficiency, and for usability.
Step 4: Diagram the structure. Use a tool like Figma, Miro, or even a whiteboard. Draw boxes for each page with lines connecting parent to child pages. A good visual sitemap uses different colors for each tier or section.
Step 5: Validate with stakeholders. Share the sitemap with content owners, developers, and business stakeholders. Ask: Is every page in the right place? Are there gaps? Is any section over- or under-weighted? This validation step alone has been shown to catch 30, 40% of structural issues before any code is written, according to research on IA best practices published by the Nielsen Norman Group.
> Worked example: A mid-size B2B SaaS site planning a redesign started with a visual sitemap and discovered their "Integrations" section had 14 sub-pages hidden under "Product," while their blog (their biggest traffic source) was relegated to Level 3 in a footer link. The sitemap made the misalignment visible in 30 minutes, saving weeks of developer rework later.
A visual sitemap template can accelerate this process. We offer a free website sitemap template that includes pre-built level structures for common site types (SaaS, ecommerce, portfolio, content site).
How to Create a Website Sitemap: The XML Approach for Search Engines
An XML sitemap is a machine-readable file that lists every URL on your site along with metadata like last-modified date, change frequency, and priority relative to other pages. Search engines read this file to discover content they might otherwise miss. If you're learning how to create a website sitemap for SEO purposes, this section is for you.
How to Create an XML Sitemap (Three Paths)
Path 1: Automatic (recommended for most sites). If you use a modern CMS, WordPress (Yoast, Rank Math, or All in One SEO), Shopify, Webflow, Squarespace, or most headless CMS platforms, your XML sitemap is likely generated automatically. Check yoursite.com/sitemap.xml to see if it exists. WordPress users should verify their SEO plugin is configured to include all public post types.
Path 2: Online generator (for small or static sites). For a site with fewer than 500 pages, a free online sitemap generator can crawl your live URLs and produce the XML. Tools like XML-Sitemaps.com deliver a downloadable file. This works well for hand-coded HTML sites, landing pages, and marketing microsites that lack a CMS.
Path 3: Manual creation (for custom projects). If you need full control, or your site follows a very specific URL pattern, write the XML yourself. Here's a minimal valid example:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-08-15</lastmod>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2026-06-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/blog</loc>
<lastmod>2026-09-01</lastmod>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
</urlset>Key constraints from the sitemaps protocol:
- Max 50,000 URLs per sitemap file
- Max 50 MB uncompressed file size
- Use absolute, fully-qualified URLs (include
https://) - UTF-8 encoding only
If your site exceeds either limit, split it into multiple sitemap files and create a sitemap index file pointing to each one.
How to Submit Your XML Sitemap to Google
Once you understand how to create a website sitemap in XML format, the next step is submission. Here's how:
- Open Google Search Console and select your property.
- Go to the Sitemaps section in the left sidebar.
- Enter the sitemap URL (e.g.,
https://example.com/sitemap.xml). - Click Submit and monitor the "Discovered" vs. "Indexed" counts.
You can also declare the sitemap location in your robots.txt file:
Sitemap: https://example.com/sitemap.xmlThis provides a fallback discovery path even if Search Console isn't configured. If you operate a large site or a multi-region deployment, the Metaflow approach to site architecture planning can help you structure your content model in a way that maps cleanly to XML sitemaps, rather than patching URL issues after the fact.
Sitemap Mistakes That Waste Time and Hurt SEO
After working with dozens of site launches and redesign projects, these are the most common sitemap errors we see, along with the difference each one makes.
| Mistake | What happens | Impact |
|---|---|---|
| Building the visual sitemap after wireframes | Redesigns are common; stakeholder approval is re-litigated | 2–4 weeks of rework |
| XML sitemap includes noindex pages | Google wastes crawl budget on pages it won't index | Zombie pages inflate crawl cost |
| URLs in sitemap don't match canonical | Google gets mixed signals on which URL to index | Diluted ranking signals |
| Visual sitemap hierarchy deeper than 4 levels | Pages may never get crawled; users drop off from navigation fatigue | Lost organic visibility |
| No HTML sitemap for large content sites | Users and link equity have no secondary navigational path | Harder internal linking |
| XML sitemap never updated after content changes | Google serves stale lastmod dates; recrawl frequency drops | Delayed index of new content |
Worked example: A 200-page ecommerce site submitted a single XML sitemap that included their 1,500 product URLs with faceted filter variations, violating the 50,000 URL limit on count alone. After audit, they split product URLs into a separate sitemap and added a <lastmod> tag that updated nightly. Their indexation rate improved from 63% to 91% within three weeks. The lesson: knowing how to create a website sitemap accurately is pointless if you fail to keep it maintained alongside your live content.
That table is the punch list, not a shame list. Pick the one row that matches last week's Search Console screenshot and fix it this week. How to create a website sitemap that stays honest is mostly lastmod plus a refusal to list noindex URLs.
How Sitemaps Feed Into Your Content Strategy
A sitemap isn't a one-time artifact. It evolves with your content strategy. When you plan a content cluster or a new product launch, the sitemap surfaces important questions:
- Where does this new content live in the hierarchy?
- Does it require a new section (Level 1) or fit under an existing one?
- Is the current IA deep enough to support the topic?
- Which existing pages need to link to it for crawl efficiency?
For teams running content-led growth (as opposed to ad spend), the sitemap becomes a strategic planning tool, not just a technical file. You can use it to identify content gaps, spot orphaned pages, and ensure every piece of content has a clear path from the homepage. The same principle applies to AI search visibility, where structured, crawlable content is a prerequisite for being cited by answer engines like ChatGPT and Perplexity.
Understanding how to create a website sitemap that genuinely serves your strategy means treating the sitemap not as a delivery checklist item, but as a living artifact, one you update whenever your content model grows or changes.
Whether you need a visual blueprint or an XML crawl map, knowing how to create a website sitemap from the right starting point saves you weeks of rework.
The hard part is not the XML. It is keeping the hierarchy next to the content calendar so the next launch does not invent a new Level 1.
That is a workflow problem. An agent can draft the first visual map when discovery notes, the page list, and the refusal list sit in the same context. Execution then compounds instead of resetting every redesign.
What's a good website sitemap prompt?
Use a prompt that forces the two-path choice and forbids a tool-first answer. How to create a website sitemap with AI still fails if the model invents pages you do not have. Paste this, then drop in the real list. The output is a first draft. You still validate Level 1 names with the people who own those URLs. A good prompt names the two jobs, visual IA versus XML crawl, and asks for a refusal list so faceted duplicates never enter the file.
> You are an information architect. Using only the page list I paste, tell me whether I need a visual sitemap, an XML sitemap, or both. Then draft the Level 1 / Level 2 hierarchy, flag any page more than three clicks from home, and list URLs that must not appear in XML (noindex, faceted duplicates). Do not invent pages the source list does not include.
The hard part is not the XML. It is keeping the hierarchy next to the content calendar so the next launch does not invent a new Level 1. That is a workflow problem. An agent can draft the first visual map when discovery notes, the page list, and the refusal list sit in the same context. Execution then compounds instead of resetting every redesign.
Metaflow is built for that handoff, the website sitemap template as the sheet you fill once, and the content-led growth agent when the same structure has to stay next to the cluster plan.
Frequently Asked Questions
What is a sitemap for a website?
A sitemap is a structured list of the pages on a website. Visual sitemaps show page hierarchy in a diagram format for planning purposes, while XML sitemaps are machine-readable files that tell search engines which URLs to crawl and index. In Metaflow that distinction lives on the same website sitemap template so design and SEO do not keep parallel docs.
How can I create a free sitemap?
For a visual sitemap, use free tiers of Figma, Miro, or Canva, all offer templates. For an XML sitemap, use a free online generator like XML-Sitemaps.com (up to 500 pages) or your CMS plugin if you use WordPress, Webflow, or Shopify. Metaflow teams usually start from the site architecture plan so the free file still matches the live IA.
What is the best sitemap builder?
The best sitemap builder depends on the type: for visual sitemaps, Miro and Figma lead for collaboration and templates. For XML sitemaps, Google-recommended plugins (Yoast SEO for WordPress, the standard Shopify sitemap) are the safest bets because they auto-update with content changes.
Is a sitemap generator free to use?
Many sitemap generators are free up to a page limit. XML-Sitemaps.com offers free generation for up to 500 URLs. Most CMS platforms include built-in sitemap generation at no cost. For enterprise or unlimited-page needs, paid generators or custom scripts are more appropriate.
