Sitemap Mapping: The Ultimate Guide to Sitemaps

If you’re a web designer, developer, content strategist, or site owner, sitemaps are part of how you ship and maintain quality on the web. For visual sitemaps, that means a shareable diagram of how a site is organized — useful in design reviews, redesigns, migrations, and stakeholder alignment. For machine-readable sitemaps (XML, image, video, news), it means a structured file that helps search engines find every important page on your site. This guide covers both, with current 2026 tooling, protocols, and submission workflows.

What is a sitemap?

A sitemap serves two related but distinct purposes:

• For humans — a visual or hierarchical representation of a website’s structure. Used during planning, redesign, migration, and governance. Useful for IA reviews, stakeholder alignment, and on-boarding new team members.
• For search engine crawlers — a machine-readable file (typically XML) that lists the URLs on a site, with optional metadata about when each was last updated, how often it changes, and its relative priority. Used by Googlebot, Bingbot, Yandex, and other crawlers as a discovery aid alongside following links from other pages.

The two purposes use the same word but produce different artifacts: visual sitemaps are diagrams (often shared as PDFs, Figma boards, or interactive web tools), while XML sitemaps are files served at a known URL (typically /sitemap.xml or /sitemap_index.xml) that search engines fetch automatically.

What types of sitemaps are there?

Several distinct sitemap types serve different purposes:

Visual sitemaps

Visual sitemaps are diagrams that show how the pages of a site relate to each other — parent and child pages, primary navigation, content groupings. They’re shared with stakeholders in redesigns and IA reviews and used as reference documentation during build. Visual sitemaps live in dedicated tools (DYNO Mapper, Slickplan, FlowMapp, Octopus.do, Lucidchart, Figma/FigJam, Miro) rather than as files on the live site.

XML sitemaps

The standard machine-readable sitemap format, governed by the Sitemap Protocol 0.9 (sitemaps.org). An XML sitemap lists URLs with optional <lastmod>, <changefreq>, and <priority> elements. Limits: 50,000 URLs and 50 MB uncompressed per sitemap file. Sites with more URLs use a sitemap index (sitemap_index.xml) that points to multiple individual sitemaps. Most CMSes and SEO plugins generate these automatically.

HTML sitemaps

A user-facing page listing all (or major) URLs on the site, typically organized by section. Less common than they used to be — search engines now rely primarily on XML sitemaps and crawl from internal links — but still useful for very large sites and as a navigation aid for users.

Image sitemaps

An XML sitemap variant or extension that lists image URLs with optional caption, geo location, title, and license metadata. Helps Google Images discover and index visual content. Particularly relevant for e-commerce, news, and visual-content-heavy sites. Can be a standalone sitemap or extension elements within a regular XML sitemap.

Video sitemaps

Lists video content with metadata (title, description, duration, thumbnail URL, family-friendly status, country restrictions). Helps Google Video and YouTube’s discovery surfaces find embedded video content. Critical for sites with original video content that needs to rank in video search results.

News sitemaps

Specifically formatted XML sitemaps for news content, used by Google News. Includes <news:publication_date> and <news:title>; only includes articles published in the last two days. Required for inclusion in Google News carousels and mobile news boxes. Updated continuously as new articles are published.

Mobile sitemaps

Historical sitemap format for sites that maintained separate mobile versions. Google sunset support for mobile-specific sitemaps in 2018 as part of the move to mobile-first indexing — a single responsive site is now the standard, and there’s no need for a mobile-specific sitemap. If you find legacy guidance still recommending mobile sitemaps, it’s outdated.

Text sitemaps

A simple text file listing URLs, one per line. The original sitemap format pre-XML, still accepted by Google and Bing but with no metadata support. Useful for very simple sites and as a fallback. Most modern tooling generates XML sitemaps by default.

RSS / Atom feeds as sitemaps

Google and Bing accept RSS 2.0 and Atom 1.0 feeds as sitemaps. Useful for blogs and news sites where the feed already exists; the feed lists recent content with publication dates that crawlers use as a freshness signal.

Why do you need a sitemap?

The case for sitemaps depends on the type:

• For visual sitemaps: planning and IA work needs a shared visual artifact. Without one, design reviews fall back on prose descriptions or per-page wireframes that don’t convey overall structure.
• For XML sitemaps: Google’s and Bing’s own documentation specifically recommends XML sitemaps for sites that are large, new, have rich media (images, videos), have pages not well-linked internally, or are otherwise hard for crawlers to discover via internal links alone. For small static sites with strong internal linking, the SEO benefit of an XML sitemap is marginal but still positive.

Search engine optimization

An XML sitemap helps search engines discover URLs, especially newly published or hard-to-reach pages. It also lets you signal which pages exist and when they were last updated. The sitemap is a discovery aid, not a ranking factor — being in the sitemap doesn’t boost rankings, but being missing means the URL may not be discovered or may be discovered slowly.

Website design and redesign

A visual sitemap is the foundational artifact in any redesign or new-site project. It aligns stakeholders, surfaces missing pages, and identifies content that should be retired or restructured. Without it, design teams build out pages without a clear sense of how they fit together.

Content planning

Visual sitemaps support editorial planning by making the content estate visible. Editors and content strategists can spot gaps, identify topic clusters, and plan content roadmaps against the existing structure rather than in a vacuum.

Who uses sitemaps?

Sitemaps serve different roles across the web team:

Content managers

Use visual sitemaps to plan content calendars, audit existing content, and coordinate across multiple authors. XML sitemaps surface what’s actually been indexed and surface gaps in coverage.

Web developers

Implement and maintain XML sitemap generation (often via CMS or framework plugins), set up robots.txt sitemap declarations, and ensure sitemap files validate against the Sitemap Protocol schema.

UX designers and information architects

Live in visual sitemap tools — DYNO Mapper, Slickplan, FlowMapp, Octopus.do, Lucidchart — building and revising the structural design of a site. The sitemap precedes the wireframes and is referenced throughout the design process.

Project managers

Use the sitemap as a project artifact — to scope, estimate, track, and communicate progress. Pages on the sitemap roughly correspond to deliverables on the project plan.

SEO and digital marketing teams

Submit XML sitemaps via Google Search Console, Bing Webmaster Tools, Yandex Webmaster, and IndexNow. Monitor sitemap-coverage metrics for indexing issues. Diagnose discovery and crawling problems.

Accessibility and governance teams

Visual sitemaps support content audits, accessibility audits, and overall web governance — providing a shared map of what exists across the site. DYNO Mapper’s accessibility testing ties the sitemap to per-page WCAG 2.2 conformance scanning.

How to create a sitemap

Creating visual sitemaps

Use a dedicated visual-sitemap tool: DYNO Mapper, Slickplan, FlowMapp, Octopus.do, or general-purpose tools like Lucidchart, Figma/FigJam, Miro, or Mural. Most generate sitemaps from a starting URL by crawling, or let you build them manually for sites in planning. The output is typically shareable as PDF, PNG, or interactive web link.

Creating XML sitemaps

Most modern CMSes and SEO platforms generate XML sitemaps automatically:

• WordPress ships with native XML sitemap support since WordPress 5.5 (May 2020) at /wp-sitemap.xml. Most sites override this with the more flexible sitemap output from Yoast SEO, RankMath, or All in One SEO.
• Shopify, Squarespace, Webflow, Wix, Framer all generate XML sitemaps automatically.
• Custom-built sites can use generators like Screaming Frog SEO Spider, XML-Sitemaps.com, or programmatic generation in the framework (Next.js, Astro, Nuxt all have plugins).

For a manually-maintained site, the basic XML structure is:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-01-15</lastmod>
  </url>
</urlset>

Creating HTML sitemaps

Either generate from your XML sitemap (most CMSes can render an HTML page from the sitemap data), build manually for small sites, or use a plugin (Yoast SEO and RankMath both offer HTML sitemap shortcodes for WordPress).

Creating image sitemaps

Either as a standalone image sitemap or as <image:image> elements within a regular XML sitemap. Most major SEO plugins (Yoast SEO, RankMath, Shopify) include image URLs in the main sitemap automatically. For e-commerce and visual-content-heavy sites, verify your sitemap output includes images.

Creating video sitemaps

Video sitemaps require structured metadata (title, description, content URL or player URL, duration, thumbnail). Either use a CMS plugin that supports them or generate manually following Google’s video sitemap documentation. Pair with VideoObject structured data on each page for the strongest video discoverability.

Creating news sitemaps

News publishers use specialized news-sitemap tooling — most major news CMSes (WordPress with Yoast News SEO, Drupal with appropriate modules, custom news platforms) generate news sitemaps automatically. The format includes <news:publication_date> and <news:title> elements; articles only appear for two days after publication.

Creating mobile sitemaps

Skip this. Google sunset mobile-sitemap support in 2018 with the move to mobile-first indexing. A single responsive site with a regular XML sitemap is the modern standard. If you encounter older guidance recommending separate mobile sitemaps, it’s out of date.

Sitemap generators

DYNO Mapper

DYNO Mapper is a visual sitemap generator and content audit platform. Crawl any site (public or behind authentication including SharePoint, Microsoft 365, Okta) and produce a visual sitemap, content inventory, and accessibility report in one workflow. Strong fit for IA, governance, redesigns, migrations, and ongoing content audits. Subscriptions for individuals, organizations, and enterprise.

Writemaps

Writemaps is a focused visual sitemap and content-planning tool. Build sitemaps collaboratively with your team, share with stakeholders, and use them as living documents during design and content production. Particularly strong for early-stage planning before a build.

Screaming Frog SEO Spider

Screaming Frog is the dominant desktop SEO crawler. The free tier crawls up to 500 URLs; paid licenses unlimit the crawl. Generates XML sitemaps from any crawl, exports to CSV/Excel, and integrates with Google Analytics, Search Console, and PageSpeed Insights. The standard tool in most SEO teams’ toolkits.

PowerMapper / SortSite

PowerMapper produces visual sitemaps from a crawl; SortSite (from the same company) does broader site auditing including accessibility, browser compatibility, and SEO checks. Strong fit for organizations that want one vendor across multiple QA dimensions.

XML-Sitemaps.com

Long-running free online tool for generating XML sitemaps from a starting URL. Free tier handles up to 500 URLs; the paid Unlimited tool handles larger sites. A reliable choice when you need a one-off sitemap without installing software.

WordPress XML sitemap plugins

WordPress shipped native XML sitemap support in 5.5 (May 2020) at /wp-sitemap.xml. Most WordPress sites override this with one of the major SEO plugins for richer features and better customization:

• Yoast SEO — the most-installed SEO plugin; generates a comprehensive XML sitemap with image/video extensions and granular per-content-type controls.
• Rank Math — Yoast’s most prominent competitor; similar features with a different UX.
• All in One SEO (AIOSEO) — third major option; long-running and well-maintained.
• XML Sitemaps by Auctollo — the legacy “Google XML Sitemaps” plugin still exists for sites that want a sitemap without a full SEO plugin.

Sitemap Writer Pro

A standalone Windows desktop application focused on XML sitemap creation, including support for video, image, and news sitemap variants. Pricing has historically been low (around $25 base); verify current pricing on the site. Useful for static-site maintainers who don’t want a CMS-coupled sitemap generator.

Other modern visual sitemap tools

• Slickplan — visual sitemap builder with content brief and design-mockup attachment, IA-focused.
• FlowMapp — visual sitemap, user-flow, and personas in one platform.
• Octopus.do — newer entry, particularly fast and easy to use for sketch-stage sitemaps.
• Lucidchart — general-purpose diagramming with sitemap templates.
• Figma / FigJam, Miro, Mural — collaborative whiteboarding tools commonly used for sitemaps in distributed teams.

How to submit sitemaps to search engines

Once you have an XML sitemap, you need to make search engines aware of it. Three main approaches:

• Submit via webmaster tools — Google Search Console, Bing Webmaster Tools, Yandex Webmaster.
• Declare in robots.txt — add a line like Sitemap: https://example.com/sitemap.xml. All major crawlers respect this.
• IndexNow — instant index notification protocol for participating search engines (Bing, Yandex, Naver, others).

1. How to submit to Google

Google Search Console is the primary submission point. The interface has been redesigned multiple times since 2018; the current flow:

• Sign in to Google Search Console with your Google account.
• If you haven’t added the property yet, click Add Property and choose Domain (preferred — covers all subdomains and protocols) or URL prefix. Verify ownership via DNS, HTML file, HTML tag, Google Analytics, or Google Tag Manager.
• Once verified, navigate to Sitemaps in the left sidebar.
• Enter the sitemap URL (e.g., sitemap.xml or sitemap_index.xml) and click Submit.
• Search Console will report submission status, the URLs discovered, and any indexing issues.

Google Webmaster Tools was rebranded to Search Console in May 2015; if you encounter old guidance referring to Google Webmaster Tools, it’s the same product.

2. How to submit to Yahoo!

Yahoo Search has used Bing’s search index since the Microsoft-Yahoo Search Alliance announced in 2009 (and rolled out 2010-2011). Yahoo Site Explorer was discontinued in November 2011. There’s no separate Yahoo sitemap submission today — submit to Bing instead and Yahoo Search results will use the same data.

3. How to submit to Bing

Bing Webmaster Tools (now called Bing Webmaster Tools, redesigned in 2020) is the submission point for Bing, Yahoo, DuckDuckGo (which uses Bing’s index for some result types), and AOL Search:

• Sign in to Bing Webmaster Tools with a Microsoft account.
• Add your site (you can also import sites from Google Search Console for faster setup).
• Verify ownership via XML file, HTML meta tag, or DNS.
• Once verified, go to Sitemaps in the left sidebar.
• Enter the sitemap URL and click Submit.

Bing Webmaster Tools also includes URL Inspection, Site Scan, and Backlink data — useful complements to Google Search Console for full-coverage SEO monitoring.

4. How to submit to Ask.com

Ask.com retired its general search index around 2010 and now operates as a Q&A site rather than a competitive web search engine. There’s no Ask.com sitemap submission today; submitting to Google and Bing covers the major search audiences in English-speaking markets.

5. How to submit to Yandex

Yandex Webmaster remains the dominant submission point for the Russian and CIS markets:

• Sign in to Yandex Webmaster with a Yandex account.
• Click + to add a site; enter the URL.
• Verify via meta tag, HTML file, or DNS.
• Navigate to Indexing > Sitemap files.
• Add your sitemap URL and submit.

Yandex’s share of the Russian search market remains substantial; if you serve Russian-speaking audiences, Yandex submission is non-optional. (Note: Yandex N.V. announced restructuring in 2024 separating its Russian operations from international assets; the Yandex Webmaster service remains operational for Russian-market sites.)

6. IndexNow protocol (Bing, Yandex, Naver, Seznam)

IndexNow (introduced October 2021) is an open protocol for instantly notifying search engines about new, updated, or deleted URLs. Currently supported by Bing, Yandex, Naver, Seznam, and Yep; not Google. Participating sites generate an API key, host it at the site root, then POST URLs to the IndexNow endpoint when content changes — search engines pull the change within minutes rather than waiting for the next crawl. Many CMSes (WordPress via plugin, Cloudflare via integration) support IndexNow automatically.

7. Declare your sitemap in robots.txt

The simplest signal — add a line to /robots.txt:

Sitemap: https://example.com/sitemap.xml

All major crawlers (Google, Bing, Yandex, Baidu, DuckDuckGo) respect this. Multiple Sitemap: lines are allowed for sites with multiple sitemaps.

International and multilingual sitemaps

Sites serving multiple languages or regions need extra sitemap discipline. Two main approaches:

• hreflang annotations within the XML sitemap. Each URL entry includes <xhtml:link rel="alternate" hreflang="..."> elements pointing to equivalent pages in other languages or regions. This is Google’s preferred method for declaring language and regional alternatives at scale, and avoids cluttering the HTML <head> of every page with hreflang tags.
• Separate sitemaps per language or region. Useful when content lifecycles differ across locales — e.g., the German site updates more often than the Japanese site. Combine with a sitemap index pointing to all language sitemaps.

Common pitfalls in international sitemaps: missing return tags (every hreflang reference must be reciprocated by the target page), incorrect locale codes (use ISO 639-1 language codes plus optional ISO 3166-1 Alpha 2 region codes — “en-US” not “en_us”), and including non-canonical URLs in hreflang declarations.

Verify hreflang implementation with Google Search Console’s International Targeting report (under Legacy Tools and Reports) and external tools like Sistrix or Merkle’s hreflang testing tool.

Sitemap troubleshooting and best practices

Common XML sitemap issues and fixes:

• Sitemap couldn’t be read — check the URL is reachable, returns HTTP 200, has correct Content-Type (text/xml or application/xml), and validates against the Sitemap Protocol XSD schema.
• Discovered, currently not indexed — the URL was found but Google declined to index it. Usually a content-quality, duplication, or canonicalization issue rather than a sitemap problem.
• Crawled, currently not indexed — Google fetched the page but didn’t include it. Check for thin content, low-quality signals, and conflicting canonical or noindex tags.
• URL is not on Google — verify it’s in the sitemap, declared in robots.txt, not blocked by robots.txt or noindex, and reachable via internal links.
• Noindex pages in sitemap — the sitemap should only contain canonical, indexable URLs. Don’t include pages with noindex meta tags or pages canonicalized elsewhere.
• HTTP vs HTTPS mismatches — every URL in the sitemap should match the canonical protocol and hostname. Mixed http/https or www/non-www URLs in the sitemap cause confusion.
• Stale <lastmod> values — only include lastmod when it accurately reflects content changes. Faking lastmod values to trick crawlers into refreshing has been actively documented by Google as ineffective and potentially counterproductive.

Best practices:

• Include only canonical, indexable URLs.
• Keep individual sitemap files under 50,000 URLs and 50 MB; split into multiple sub-sitemaps if larger.
• Update <lastmod> only when the page’s actual content has meaningfully changed.
• Submit to Google Search Console and Bing Webmaster Tools, declare in robots.txt, and use IndexNow if your content updates frequently.
• Don’t include URLs that 301 redirect, return 404, or are blocked by robots.txt.
• Audit sitemap-coverage metrics monthly to catch new indexing issues early.

Frequently asked questions

Do I need both a visual sitemap and an XML sitemap?

They serve different purposes. A visual sitemap is for humans (planning, IA, stakeholder review); an XML sitemap is for search engines (discovery and indexing). Most sites benefit from both, but the contexts in which each is created and used are quite different.

Where should my XML sitemap live?

Convention is /sitemap.xml at the site root, or /sitemap_index.xml for an index file pointing to multiple sub-sitemaps. WordPress’s native sitemap is at /wp-sitemap.xml. The exact path doesn’t matter as long as it’s consistent and declared in robots.txt and webmaster tools.

How often should I update my XML sitemap?

Whenever content changes. Most CMS-generated sitemaps update automatically as new content is published. The <lastmod> field should reflect the actual last-modified date of each URL — Google uses it as a freshness signal.

Will an XML sitemap improve my rankings?

No — sitemaps help with discovery and crawling, not ranking. A page in the sitemap gets discovered faster, but ranking depends on content quality, backlinks, technical SEO, Core Web Vitals, and a long list of other factors. The sitemap is necessary infrastructure, not a ranking lever.

What about AMP sitemaps?

AMP (Accelerated Mobile Pages) usage has declined sharply since Google removed the AMP requirement for the Top Stories carousel in June 2021. Most major publishers have moved away from AMP. If you don’t already have AMP, there’s no SEO reason to add it; if you do, separate AMP sitemaps are still supported but increasingly less relevant.

Is IndexNow worth the setup effort?

For high-update sites (news, e-commerce, large content libraries), yes — IndexNow gets new content into Bing, Yandex, and other participating engines within minutes rather than days. Google doesn’t support IndexNow (they continue to recommend their own URL Inspection API for Search Console), so the benefit is for non-Google traffic.

Final words

Sitemaps remain foundational web infrastructure in 2026 — both the visual kind (for humans) and the XML kind (for search engines). The standards (Sitemap Protocol 0.9, IndexNow) have proven durable; the tooling (visual: DYNO Mapper, Slickplan, FlowMapp, Octopus.do; XML: native CMS support plus Yoast SEO, RankMath, Screaming Frog) has matured into a comfortable default stack. Submit your XML sitemap to Google Search Console and Bing Webmaster Tools, declare it in robots.txt, and consider IndexNow if your content updates frequently and you care about non-Google search visibility. For visual sitemap work, pick the tool that fits how your team collaborates and use it as the foundation of your IA, governance, and ongoing content-audit work.