An XML sitemap is a file that lists every important page on your website so search engines can find and crawl them efficiently. Sitemaps improve indexing speed, help search engines discover orphan pages and provide metadata that guides crawl prioritization for better SEO performance.
What an XML Sitemap Does
An XML sitemap acts as a roadmap for search engine crawlers. It tells Google, Bing and other search engines exactly which pages exist on your site, when they were last updated and how important they are relative to each other. Without a sitemap crawlers rely entirely on following links to discover your pages. If a page has no internal links pointing to it (an orphan page) crawlers may never find it.
The sitemap protocol is an open standard created in 2005 and adopted by all major search engines. A basic XML sitemap looks like this:
<?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-04-11</lastmod>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/about/</loc>
<lastmod>2026-03-15</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
</urlset>Key Sitemap Elements
Each URL entry in a sitemap can include four elements:
- loc (required) is the full URL of the page
- lastmod (optional) indicates when the page was last modified. Google uses this to decide whether to recrawl a page
- changefreq (optional) suggests how often the page changes. Google has confirmed it largely ignores this field
- priority (optional) indicates relative importance within your site on a scale of 0.0 to 1.0. Google has also confirmed it largely ignores this field
In practice loc and lastmod are the two elements that matter. Google pays attention to accurate lastmod dates and uses them to schedule recrawls.
Why Sitemaps Matter for SEO
Faster Indexing of New Content
When you publish a new page or blog post your sitemap updates to include it. When Googlebot next checks your sitemap it discovers the new URL and crawls it. This is faster than waiting for Googlebot to follow internal links to the new page. For sites that publish frequently (daily or weekly) this speed advantage compounds over time.
Crawl Budget Optimization
Google allocates a crawl budget to each site based on size, authority and server capacity. Your sitemap helps Google spend that budget efficiently by directing crawlers to your most important and recently updated pages. Without a sitemap Google may waste crawl budget on low-value pages (like tag archives or parameter-based URLs) while missing important content.
This matters most for larger sites. A technical SEO audit often reveals that sites with thousands of pages have significant indexing gaps because crawlers cannot discover all content through links alone.
Orphan Page Discovery
An orphan page has no internal links pointing to it. Crawlers that rely on link-following will never find it. Sitemaps solve this by providing a direct URL list. If you include an orphan page in your sitemap Google can still discover and index it. (Though the better fix is to add proper internal links to that page.)
Search Console Insights
Submitting your sitemap to Google Search Console gives you indexing data you cannot get any other way. The Index Coverage report shows how many of your sitemap URLs are indexed, which are excluded and why. This diagnostic data is essential for identifying and fixing indexing problems.
How to Create an XML Sitemap
WordPress Sites
WordPress generates a basic XML sitemap by default at /wp-sitemap.xml since version 5.5. However the built-in sitemap lacks advanced features. Most SEO practitioners use a plugin for better control:
Yoast SEO generates comprehensive sitemaps at /sitemap_index.xml with separate sitemaps for posts, pages, categories and custom post types. It automatically excludes noindex pages and updates when you publish new content.
Rank Math offers similar functionality with additional control over which post types and taxonomies to include. Access the sitemap at /sitemap_index.xml.
Both plugins handle sitemap generation automatically. Once configured you do not need to manage the sitemap manually.
Custom and Static Sites
For non-WordPress sites you have several options:
- Screaming Frog SEO Spider crawls your site and generates a sitemap file you can upload to your server
- XML-Sitemaps.com generates sitemaps for sites up to 500 pages for free
- Custom scripts can generate sitemaps programmatically. Most web frameworks have sitemap generation libraries
For a Node.js site you might generate a sitemap during the build process:
// sitemap-generator.js
const { SitemapStream, streamToPromise } = require('sitemap');
const { createWriteStream } = require('fs');
const sitemap = new SitemapStream({
hostname: 'https://example.com'
});
// Add URLs
sitemap.write({ url: '/', lastmod: '2026-04-11', priority: 1.0 });
sitemap.write({ url: '/about/', lastmod: '2026-03-15', priority: 0.8 });
sitemap.write({ url: '/blog/', lastmod: '2026-04-11', priority: 0.9 });
sitemap.end();
// Write to file
const writeStream = createWriteStream('./public/sitemap.xml');
sitemap.pipe(writeStream);Sitemap Index Files
Individual sitemaps have a 50,000 URL limit and a 50MB uncompressed file size limit. Larger sites use a sitemap index file that references multiple individual sitemaps:
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.com/sitemap-posts.xml</loc>
<lastmod>2026-04-11</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap-pages.xml</loc>
<lastmod>2026-04-01</lastmod>
</sitemap>
</sitemapindex>Most SEO plugins generate sitemap index files by default, splitting URLs by content type (posts, pages, categories) for cleaner organization.
Submitting Your Sitemap to Search Engines
Google Search Console
- Log into Google Search Console
- Select your property
- Navigate to Sitemaps in the left menu
- Enter your sitemap URL (e.g.,
/sitemap.xmlor/sitemap_index.xml) - Click Submit
Google Search Console shows the submission status, the number of discovered URLs and any errors in your sitemap. Check this report monthly to catch issues early.
Bing Webmaster Tools
The process is nearly identical in Bing Webmaster Tools. Submit your sitemap URL under the Sitemaps section. Bing also supports automatic sitemap discovery through IndexNow, a protocol that pings Bing when content changes.
Robots.txt Declaration
Add your sitemap URL to your robots.txt file so any crawler can find it without needing a manual submission:
User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xmlThis is especially important for search engines where you cannot submit sitemaps through a webmaster console.
Sitemap Best Practices
Only Include Indexable Pages
Every URL in your sitemap should return a 200 status code and should not have a noindex tag. Including URLs that redirect, return 404 errors or are set to noindex wastes crawl budget and confuses search engines. Audit your sitemap regularly to ensure it only contains clean, indexable URLs.
Keep lastmod Dates Accurate
Only update the lastmod date when you make a meaningful content change. Changing a single comma and updating the lastmod teaches search engines to distrust your dates. When lastmod dates are accurate Google uses them to prioritize which pages to recrawl. When they are unreliable Google ignores them entirely.
Match Your Sitemap to Your Canonical URLs
If your canonical URL uses https://www.example.com/page/ your sitemap should use the exact same format. Mismatches between sitemap URLs, canonical tags and the actual rendered URLs create confusion that slows indexing.
Use HTTPS URLs
All URLs in your sitemap should use HTTPS. If you have redirects from HTTP to HTTPS include only the HTTPS destination URLs.
Compress Large Sitemaps
Gzip compression reduces sitemap file sizes significantly. Most servers can serve sitemap.xml.gz files. Search engines support gzipped sitemaps natively. This reduces bandwidth for both your server and the crawler.
Common Sitemap Mistakes
Including Noindex Pages
Adding a URL to your sitemap tells search engines “please index this page.” Adding a noindex tag to that same page tells search engines “do not index this page.” These conflicting signals waste crawl budget and indicate poor technical SEO hygiene.
Broken URLs in the Sitemap
URLs that return 404, 301 or 500 status codes should never appear in your sitemap. Google Search Console flags these as errors. Clean them up by removing deleted pages and updating URLs that have moved.
Stale Sitemaps
A sitemap that has not been updated in months loses its value. If you publish a new blog post every week but your sitemap still shows last month’s content Google will not discover your new posts through the sitemap. Use a CMS plugin or automated build process that regenerates the sitemap whenever content changes.
One Giant Sitemap
Cramming all URLs into a single file makes debugging harder and can cause processing issues if the file is large. Split your sitemap into logical groups: one for blog posts, one for service pages, one for product pages. This makes it easier to diagnose indexing issues in Search Console because you can see which sitemap’s URLs are causing problems.
Forgetting Image and Video Sitemaps
If your site relies heavily on images or video content consider extending your sitemap to include image and video elements. Image sitemaps help Google discover images that might not be found through regular crawling. Video sitemaps improve your chances of appearing in video search results.
Monitoring Sitemap Health
Submit your sitemap to Google Search Console and check the report monthly. Look for:
- Error count which should be zero. Any errors need immediate attention
- Valid URLs which should closely match the total URLs in your sitemap
- Excluded URLs and the reasons for exclusion. Some exclusions are expected (canonicalized pages) but others indicate problems
- Last read date which shows when Google last processed your sitemap. If it has not been read recently there may be an accessibility issue
Pair sitemap monitoring with regular SEO audits to catch issues before they impact rankings. If you want a professional review of your sitemap and overall technical SEO health, request a free audit from our team.
Frequently Asked Questions
Does every website need an XML sitemap?
Small sites with strong internal linking may not strictly need one but every site benefits from having an XML sitemap. It gives search engines a complete list of your indexable pages, helps them discover new content faster and provides metadata like last-modified dates that improve crawl efficiency.
What is the difference between an XML sitemap and an HTML sitemap?
An XML sitemap is a machine-readable file designed for search engine crawlers. An HTML sitemap is a human-readable page on your site that lists links to all your pages for visitor navigation. Both serve different purposes. XML sitemaps help with crawling and indexing. HTML sitemaps help users find content.
How often should I update my XML sitemap?
Your sitemap should update automatically whenever you publish, update or delete content. Most CMS platforms and SEO plugins handle this automatically. If you manage your sitemap manually update it every time you make a content change. Stale sitemaps with outdated lastmod dates reduce their usefulness for search engines.
Should I include every page in my XML sitemap?
No. Only include pages you want search engines to index. Exclude admin pages, login pages, duplicate content, paginated archive pages and any page with a noindex tag. Including non-indexable URLs wastes crawl budget and sends confusing signals to search engines about which pages matter.
Related: SEO guide and SEO FAQ
Need help with this?
Quake Media helps businesses across Vancouver and Canada with SEO, PPC and custom web development. Get a free audit and see where your site stands.
