A sitemap is a file that tells search engines which pages on your site exist, when they were last updated, and how important they are relative to each other. Without one, Google discovers your pages by following links — which works, but it’s slower, less reliable, and gives you no control over what gets indexed.
For a 5-page website on good infrastructure with clear internal links, a sitemap matters a little. For a 500-page e-commerce site with frequently changing inventory, it matters a lot. The correct mental model: a sitemap is not what gets your pages ranked. It’s what gets your pages into the consideration set for ranking. Google can’t rank what it hasn’t indexed.
Two Types of Sitemaps, Two Different Purposes
XML Sitemaps: For Search Engines
An XML sitemap is a structured file (usually located at yoursite.com/sitemap.xml) that lists your URLs in a format search engines read. It’s not for humans. It contains:
- The URL of each page
- The
lastmoddate — when the page was last modified - Optionally:
changefreq(how often the page changes) andpriority(relative importance, 0.0–1.0)
Google has said publicly that changefreq and priority are largely ignored in their crawling decisions — they use their own signals. But lastmod is useful: if you update a page and the lastmod reflects that, Google knows to recrawl it sooner.
A typical XML sitemap entry looks like this:
<url>
<loc>https://designodin.com/services/wordpress</loc>
<lastmod>2026-03-15</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>Large sites use sitemap index files — a parent file that references multiple child sitemaps. Google’s limit is 50,000 URLs per sitemap file. A site with 200,000 products would have at least 4 sitemap files referenced in a sitemap index.
HTML Sitemaps: For Visitors
An HTML sitemap is a page on your site (often at /sitemap) that lists your pages in a human-readable format. It’s a navigation aid for visitors who can’t find a page through the main navigation.
HTML sitemaps matter less for SEO than they used to — Google doesn’t give them special weight. But they’re still useful for large sites with complex navigation where visitors might get lost. For small business sites, an HTML sitemap is optional.
When Sitemaps Matter Most
New websites. A new site has no external links pointing to it and no crawl history. Google’s crawler won’t find it quickly through natural link discovery. Submitting a sitemap to Google Search Console immediately after launch tells Google the site exists and which pages to index. Without this, a new site can take weeks to appear in search results.
Large sites. Sites with hundreds or thousands of pages can’t rely on link-following for complete indexing. Crawl budget — the number of pages Google crawls per day on your site — is finite. A sitemap helps Google prioritize which pages to crawl within that budget.
Sites with orphan pages. An orphan page is one that no other page on your site links to. Google discovers pages by following links, so orphan pages are invisible to the crawler. If you have pages that don’t appear in navigation or blog feeds, the sitemap is often the only way Google finds them.
E-commerce sites. New products, retired products, out-of-stock products, variant pages — e-commerce inventory changes constantly. A dynamic sitemap that updates automatically ensures Google has an accurate picture of your current catalog.
Sites that update content frequently. A news publication or active blog that publishes daily benefits from accurate lastmod dates in the sitemap — Google recrawls pages that signal they’ve been updated.
When Sitemaps Matter Less
A 10-page business website with strong internal linking and a few quality external backlinks probably doesn’t need to worry about sitemaps as a performance lever. Google will find and index those pages through normal crawling. Having a sitemap is still good practice — it costs nothing — but it’s not going to move the needle on your rankings in the way that content quality and backlinks will.
How to Create and Submit a Sitemap in WordPress
If you’re running WordPress, sitemap generation is handled automatically by Yoast SEO or RankMath. Both create XML sitemaps, update them when you publish or modify content, and let you include or exclude specific post types or individual pages.
After installing Yoast SEO:
- Go to SEO > General > Features and ensure “XML Sitemaps” is enabled
- Visit yoursite.com/sitemap_index.xml to confirm the sitemap exists
- Go to Google Search Console > Sitemaps > Submit a new sitemap
- Enter sitemap_index.xml and click Submit
That’s the complete setup for a WordPress site. Yoast handles the rest automatically.
RankMath’s process is nearly identical. Both tools generate a sitemap index file that references separate sitemaps for posts, pages, categories, and any custom post types.
What Google Search Console Tells You About Your Sitemap
After submitting a sitemap, Google Search Console shows:
- Submitted URLs — How many URLs are in the sitemap
- Indexed URLs — How many of those Google has actually indexed
- Errors — Any pages it couldn’t crawl (404 errors, redirect chains, server errors)
The gap between submitted and indexed is worth understanding. If you submit 500 URLs and only 200 are indexed, the remaining 300 either have quality issues (thin content, duplicate content), are blocked by robots.txt, have noindex tags, or are simply awaiting a crawl.
A sitemap submission that shows many errors is a diagnostic tool, not a failure — it tells you exactly which pages have problems that need fixing.
Common Sitemap Mistakes
Including pages with noindex tags. If a page has a <meta name="robots" content="noindex"> tag, don’t include it in the sitemap. You’re telling Google two contradictory things: “here’s this URL” (sitemap) and “don’t index this page” (noindex tag). Google prioritizes the noindex instruction, but the contradiction wastes crawl budget.
Including redirected URLs. Sitemaps should contain only the canonical, live version of each URL. If a page redirects (301) to another, include only the destination in the sitemap. Including the redirect source is unnecessary overhead.
Including URLs that return 404 or 500 errors. These tell Google your sitemap is stale and your site has problems. Audit your sitemap periodically — Screaming Frog and Sitebulb both crawl sitemaps and flag issues.
Not updating the sitemap after site changes. If you add, remove, or rename pages, the sitemap should reflect that. Automated sitemaps (via Yoast or RankMath) do this by default. Manual sitemaps require manual updates.
Setting priority values incorrectly. If every page has a priority of 1.0, the signal is meaningless. Use relative values: homepage at 1.0, service pages at 0.8, blog posts at 0.6, tags and archive pages at 0.4 (or exclude them entirely).
Robots.txt and How It Relates to Sitemaps
The robots.txt file (at yoursite.com/robots.txt) tells crawlers which parts of your site they can and cannot access. A common best practice: reference your sitemap in robots.txt so any crawler that visits knows where to find it:
User-agent: *
Disallow: /wp-admin/
Sitemap: https://yoursite.com/sitemap_index.xmlThis is not a replacement for submitting to Search Console — it’s an additional discovery mechanism for crawlers that don’t use Search Console.
Pages blocked by robots.txt (with Disallow:) should not be in your sitemap. If they’re disallowed, you don’t want Google to index them. The sitemap and robots.txt should be consistent with each other.
Sitemap and Core Web Vitals: The Indirect Connection
A sitemap doesn’t directly affect your Core Web Vitals scores (LCP, CLS, FID/INP). But it affects how quickly new or updated pages get indexed — and indexed pages can be tested by Google’s crawlers for page experience signals.
If you’ve improved your site’s performance scores and want Google to re-evaluate those pages with the new scores, updating the lastmod dates in your sitemap and resubmitting to Search Console is a signal to Google that something has changed. It won’t force a Core Web Vitals reassessment immediately, but it prompts a recrawl.
You can audit your site’s performance scores before and after changes at honest.designodin.com.
FAQ
Does every website need a sitemap? Not strictly — small sites with clear internal links are discoverable without one. But there’s no cost to having a sitemap, and the benefits are real: faster indexing, better crawl budget use, and a diagnostic window into indexing problems. Every site should have one.
How do I find my sitemap? Try yoursite.com/sitemap.xml and yoursite.com/sitemap_index.xml. WordPress sites with Yoast SEO typically use sitemap_index.xml. If neither works, check your robots.txt file for a Sitemap: reference.
Do sitemaps help with SEO rankings? Indirectly. A sitemap helps Google index your pages. You can’t rank if you’re not indexed. But a sitemap doesn’t make a low-quality page rank — content quality, backlinks, and technical factors do that.
How often does Google read my sitemap?
Google doesn’t publish a specific crawl schedule for sitemaps. Resubmitting through Search Console after major changes tells Google to check again. For sites with accurate lastmod dates, Google’s crawlers use that signal to decide how often to revisit.
Should I include my blog category pages in the sitemap? It depends. Category pages that aggregate content and have some SEO value (search volume for category-level queries) should be included. Category pages that are essentially duplicates of content elsewhere, or that target queries with no volume, should either be excluded from the sitemap or given a noindex tag.
What is the maximum number of URLs in a sitemap? 50,000 URLs per sitemap file. Sites with more URLs use a sitemap index file that references multiple child sitemaps.
Can a bad sitemap hurt your SEO? Not directly. A sitemap with incorrect information (redirects, 404s, noindex pages) wastes crawl budget and causes Search Console warnings, but it won’t apply a manual penalty. Fix the issues, resubmit, and the problems resolve.
Sitemaps are one part of a correctly built WordPress site. Our custom WordPress development process includes proper sitemap configuration, robots.txt setup, and Google Search Console integration as standard — not as add-ons. If you want a site that Google can find, index, and rank correctly from day one, get started here.