Sitemaps for SEO

A sitemap is a structured list of the URLs on your website that tells search engines which pages exist, when they changed last, and how they relate to each other. It’s one of the oldest and simplest technical-SEO investments you can make, and in 2026 it still pays back more than it costs. This guide covers what sitemaps actually do for SEO, the difference between XML and HTML sitemaps, how to create and submit them with modern tools, and the common mistakes that render a sitemap useless.

What a sitemap does for SEO

Search engines find pages three ways: following internal links, following external links from other sites, and reading submitted sitemaps. For small, well-linked sites, the first two usually suffice. For everything larger, sitemaps become the most reliable discovery mechanism. Specifically, a good sitemap:

• Surfaces pages that might otherwise be missed — orphaned pages, deep product catalog pages, newly-published content.
• Communicates canonical URLs — tells Google which URL is the “right” one when multiple variants exist.
• Signals change frequency honestly via <lastmod> — useful for news, fast-moving e-commerce, and frequently-refreshed content.
• Accelerates indexing for new sites — Google can find and crawl your pages in days rather than months of passive discovery.
• Exposes metadata through extensions — images, videos, news items, and language alternates each have a dedicated sitemap schema.

What a sitemap doesn’t do: it doesn’t guarantee indexing, and it doesn’t directly improve rankings. Search Console will happily report “Crawled — currently not indexed” for URLs in your sitemap if Google judges them low-quality or duplicative. Sitemaps accelerate discovery; the rest is on the pages themselves.

XML vs HTML sitemaps

Two different tools for two different audiences.

XML sitemaps — for search engines

XML sitemaps follow the sitemaps.org protocol (co-developed by Google, Bing, and Yahoo in 2006). They’re machine-readable, invisible to human visitors, and the primary sitemap that matters for indexing. A minimal XML sitemap entry:

<url>
  <loc>https://example.com/page</loc>
  <lastmod>2026-04-19</lastmod>
</url>

Hard limits: 50,000 URLs per file and 50 MB uncompressed. Larger sites use a sitemap index that references multiple individual sitemap files. Gzip compression is allowed.

HTML sitemaps — for human users

HTML sitemaps are visible pages that list your site’s content with clickable links, typically linked from the footer. They exist for humans who need to navigate or find something specific, and they’re a soft SEO signal — Google can crawl them like any other page, and they help distribute internal link authority.

Old-school SEO guides claimed HTML sitemaps should have “no more than 25–45 links.” There’s no basis for that number in any current Google guidance; it’s a repeated myth from the mid-2000s. Modern HTML sitemaps can list hundreds of links — the practical limit is whatever’s useful to users. For sites of substantial size, a hierarchical HTML sitemap (category pages linking to subcategory sitemaps) reads better than a flat list of 500 URLs.

Who benefits most from sitemaps

Sitemaps deliver the most value for:

• New sites — few or no external backlinks; organic discovery would take months without a sitemap.
• Large sites — thousands of pages where not every URL is well-linked internally.
• E-commerce — product pages that sit several clicks deep under category archives.
• Sites with dynamic content — JavaScript-rendered pages or content loaded via AJAX that might be missed by bot-only crawling. (Google’s evergreen Chromium-based renderer handles JavaScript now, but a sitemap still speeds discovery.)
• News and fast-changing content — where timely indexing matters. News sitemaps are a dedicated schema with tighter limits (1,000 URLs, 2-day window).
• Multi-region sites — hreflang annotations inside the sitemap tell Google which language/region version to serve per user.

Smaller well-linked sites (under ~100 pages with clean navigation) benefit less from sitemap submission — Googlebot usually finds everything anyway. Submitting one is still low-cost insurance.

What to include and leave out

Only canonical, indexable URLs belong in an XML sitemap. That means:

• URLs that return 200 OK.
• URLs that are the canonical version (not alternates pointing elsewhere).
• URLs not blocked by robots.txt.
• URLs without noindex meta tags.

What does not belong: redirect URLs (301, 302), error pages (4xx, 5xx), parameter variants, filter URLs, session IDs, UTM-tagged URLs, admin endpoints, login pages, thank-you pages. Every junk URL in the sitemap wastes crawl budget and signals to Google that you don’t know which URLs you want indexed.

Creating a sitemap

For most sites, your CMS or static-site generator already builds one:

• WordPress: Yoast SEO, RankMath, SEOPress, or AIOSEO generate sitemaps automatically at /sitemap.xml or /sitemap_index.xml. WordPress core (5.5+) also generates a basic sitemap at /wp-sitemap.xml if no plugin is active.
• Next.js, Nuxt, Astro, SvelteKit: each has a standard sitemap plugin or built-in generator.
• Shopify, Squarespace, Wix, Webflow: sitemaps are generated and maintained automatically.
• Custom sites or static builds: a crawl-based generator like DYNO Mapper (free 14-day trial) walks your live site and generates a sitemap from the actual URL structure. Useful when the CMS’s built-in generator misses pages or when you need visual-sitemap editing alongside the XML output.

Whichever tool you use, generate an HTML sitemap too — most plugins and DYNO Mapper support both formats from a single crawl. Export the HTML sitemap and link it from your footer or near the copyright notice so human visitors can find it.

Submitting a sitemap

Reference it in robots.txt

The single zero-overhead step that benefits every crawler: add a Sitemap: directive at the end of your robots.txt file:

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

This exposes the sitemap to every crawler that reads robots.txt — Googlebot, Bingbot, and AI crawlers like GPTBot, ClaudeBot, and PerplexityBot. Multiple Sitemap: lines are allowed if you have separate indexes for different content types.

Google Search Console

1. Open Google Search Console (renamed from Google Webmaster Tools in May 2015).
2. Select your verified property.
3. Open Indexing → Sitemaps.
4. Enter the sitemap URL (sitemap.xml or similar) and click Submit.
5. Status appears as “Success”, “Has errors”, or “Couldn’t fetch”. Use URL Inspection to diagnose specific issues if the status isn’t “Success”.

You don’t need to re-submit when content changes. Google re-reads the sitemap on its own cadence, picking up updates from the Last-Modified HTTP header and the <lastmod> values inside.

Bing Webmaster Tools

Yahoo Search has been powered by Bing since 2009, so one submission covers both. Go to Bing Webmaster Tools, verify the site, and submit the sitemap under Sitemaps → Submit sitemap.

IndexNow (Bing, Yandex, and others — not Google)

Launched in 2021 by Microsoft, IndexNow is a push protocol that notifies participating search engines the instant a URL is created, updated, or deleted. Adopted by Bing, Yandex, Seznam, and Yep — not Google. Most modern WordPress SEO plugins (Yoast, RankMath, SEOPress, AIOSEO) have built-in IndexNow support; toggle it on and skip the polling delay entirely. For sites that care about Bing traffic or AI search (ChatGPT’s web search uses Bing’s index), IndexNow is worth adopting alongside traditional sitemap submission.

The ping endpoint is dead

Older guides often tell you to “ping” Google at https://www.google.com/ping?sitemap=... whenever you update a sitemap. Google deprecated that endpoint in June 2023. It now returns a 404. Any automation or SEO plugin still pinging that URL is calling dead code. Google picks up changes via the sitemap’s Last-Modified HTTP header instead; no manual action is needed after the initial submission.

Bing also retired its equivalent ping endpoint in favor of IndexNow.

Monitoring in Search Console

After submission, the Sitemaps page shows processing status and URL counts. The Indexing → Pages report is where you actually learn whether URLs are being indexed. For each non-indexed URL, Google gives a specific reason:

• Crawled — currently not indexed — Google crawled it but chose not to index (usually a quality decision).
• Discovered — currently not indexed — Google knows about it but hasn’t crawled yet.
• Excluded by noindex tag — remove the noindex if you want it indexed.
• Blocked by robots.txt — check your robots.txt rules.
• Duplicate without user-selected canonical — add an explicit rel="canonical".
• Page with redirect — remove the URL from the sitemap; add the destination URL instead.

A healthy sitemap has a high ratio of indexed URLs to submitted URLs. When that ratio is poor, the Pages report tells you why — and the fix is usually on the page, not the sitemap.

Common sitemap mistakes

• Including non-canonical URLs. Every redirect, 404, or canonicalized-elsewhere URL wastes crawl budget and confuses reporting.
• Gaming <lastmod> to force re-crawling. Updating the date without content changes hurts sitemap credibility; Google downweights sitemaps that do this.
• Setting <priority> and <changefreq> on everything. Google effectively ignores both. They’re not harmful, but they don’t help either — and many modern generators omit them entirely.
• Forgetting to update after a site migration. Old URLs linger in the sitemap; new ones are missing. Regenerate after every migration.
• Blocking the sitemap in robots.txt. Obvious, but it happens when a staging Disallow: / gets copied to production.
• Submitting multiple competing sitemaps. Pick one canonical sitemap structure. Duplicates confuse reporting without helping discovery.
• Treating a sitemap as a ranking lever. It’s a discovery mechanism, not a ranking input. Submitting more URLs doesn’t rank any of them higher.

Frequently asked questions

Do I need both XML and HTML sitemaps?

XML is the important one — it’s what search engines use for discovery. HTML sitemaps are a nice-to-have for human navigation and a secondary internal-linking signal, but they’re not required for indexing.

Where should the sitemap live?

At the root of the domain, typically https://example.com/sitemap.xml or /sitemap_index.xml. Subdirectory locations work, but root is the universal convention.

How often should the sitemap update?

Automatically, whenever content changes. Every major WordPress SEO plugin and static-site framework handles this for you. Manual sitemaps should be regenerated after each content push, with <lastmod> values accurately reflecting actual page changes.

Does submitting a sitemap improve rankings?

No. Sitemaps accelerate discovery, not ranking. A well-discovered URL still needs strong content, relevance, and authority to rank well. See our on-page optimization guide for what actually drives ranking.

What about AI search engines — do they use sitemaps?

Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot, CCBot) honor robots.txt including the Sitemap: directive, so a sitemap referenced there is discoverable by all of them. There’s no standardized AI-specific sitemap submission UI yet.

Bottom line

A sitemap in 2026 is cheap, valuable, and mostly automatic. Generate one with your CMS or a tool like DYNO Mapper, reference it in robots.txt, submit it once to Google Search Console and Bing Webmaster Tools, enable IndexNow if your plugin supports it, and let the rest happen on its own. Keep the sitemap clean — only canonical indexable URLs — and monitor the Pages report to catch indexing problems while they’re still small. The old advice about pinging endpoints, strict HTML-sitemap link limits, and priority values belongs to an SEO era that ended years ago. The current practice is simpler than it was a decade ago, and it still works.