What Is sitemap.xml?

A sitemap.xml file is an XML document that lists the pages on your website, along with optional metadata about each page such as when it was last updated, how often it changes, and its relative importance. Search engine crawlers use this file to discover and index your pages more efficiently.

While crawlers can find pages by following links on your site, a sitemap provides a direct, authoritative list of every URL you want indexed. This is especially valuable when some pages are not well-connected through internal links, or when your site is new and has few inbound links from other sites.

When Is a Sitemap Essential?

Not every website needs a sitemap to rank well, but there are situations where having one makes a significant difference:

Large sites with hundreds or thousands of pages where crawlers might not discover everything through links alone
New websites that have few external backlinks and infrequent crawler visits
E-commerce and media sites that add new product or article pages frequently
Sites with poor internal linking where some pages may be isolated from the main navigation
JavaScript-heavy sites where content is rendered dynamically and may be harder for crawlers to reach

For small, well-linked sites with fewer than 50 pages, a sitemap is less critical but still considered a best practice.

XML Sitemap Structure

The structure of a sitemap.xml file is straightforward. Here is a complete 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-03-18</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/about</loc>
    <lastmod>2026-03-01</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://example.com/blog/getting-started</loc>
    <lastmod>2026-03-15</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>

Element Reference

Element	Required	Description
`<urlset>`	Yes	Root element with the sitemaps.org namespace
`<url>`	Yes	Container for each page entry
`<loc>`	Yes	Full, absolute URL of the page (must start with https://)
`<lastmod>`	Recommended	Last modification date in ISO 8601 format (YYYY-MM-DD)
`<changefreq>`	Optional	Hint about update frequency (always/hourly/daily/weekly/monthly/yearly/never)
`<priority>`	Optional	Relative priority within your site (0.0 to 1.0)

Understanding lastmod, changefreq, and priority

The lastmod element is the most valuable of the three optional fields. Search engines use it to decide whether they need to re-crawl a page. Always set it to the actual date of the last meaningful content change. Artificially updating lastmod without real changes erodes crawler trust and can slow down re-crawling of genuinely updated pages.

Google has publicly stated that it ignores changefreq and priority values entirely. However, other search engines like Bing may still reference them, so including them is not harmful and can be marginally beneficial.

How to Create a Sitemap

Manual Creation

For very small sites, you can write sitemap.xml by hand in any text editor. This approach works but does not scale well, since you need to manually add and remove entries whenever pages change.

Online Generators

Free tools like XML-Sitemaps.com can crawl your site and generate a sitemap.xml file automatically. The downside is that you need to regenerate the file periodically to keep it current.

CMS Plugins

If you use WordPress, plugins handle sitemap generation automatically:

Yoast SEO generates and maintains a sitemap index with sub-sitemaps for each post type
Rank Math provides automatic sitemap generation with image sitemap support
Google XML Sitemaps is a lightweight plugin focused solely on sitemap generation

All of these update the sitemap whenever you publish or modify content.

Next.js App Router

Next.js makes sitemap generation straightforward with a dedicated app/sitemap.ts file:

// app/sitemap.ts
import { MetadataRoute } from 'next';

export default function sitemap(): MetadataRoute.Sitemap {
  const baseUrl = 'https://example.com';

  const staticPages = [
    { url: baseUrl, lastModified: new Date(), changeFrequency: 'weekly' as const, priority: 1.0 },
    { url: `${baseUrl}/about`, lastModified: new Date(), changeFrequency: 'monthly' as const, priority: 0.8 },
  ];

  // Dynamic pages from your data source
  const posts = getAllPosts();
  const blogPages = posts.map((post) => ({
    url: `${baseUrl}/blog/${post.slug}`,
    lastModified: new Date(post.date),
    changeFrequency: 'yearly' as const,
    priority: 0.6,
  }));

  return [...staticPages, ...blogPages];
}

This approach keeps your sitemap in sync with your content automatically. Every time the site builds or the route is requested, the sitemap reflects the current state of your pages.

Sitemap Index Files

A single sitemap file can contain a maximum of 50,000 URLs and must not exceed 50 MB in size. For larger sites, you need 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-pages.xml</loc>
    <lastmod>2026-03-18</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-blog.xml</loc>
    <lastmod>2026-03-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-products.xml</loc>
    <lastmod>2026-03-10</lastmod>
  </sitemap>
</sitemapindex>

Splitting sitemaps by content type (pages, blog posts, products) makes it easier to monitor crawl status and diagnose indexing issues for each section of your site.

Submitting to Google Search Console

After creating your sitemap, submit it to Google Search Console to ensure Google discovers it promptly.

Sign in to Google Search Console
Select your property
Navigate to "Sitemaps" in the left sidebar
Enter your sitemap URL and click "Submit"

After submission, Search Console displays the sitemap status (success or error), the number of discovered URLs, and how many have been indexed.

Declaring Your Sitemap in robots.txt

Adding a Sitemap directive to your robots.txt file helps all crawlers, not just Google, find your sitemap automatically:

User-agent: *
Allow: /

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

This is especially useful for search engines that do not have a webmaster tools interface.

Common Mistakes to Avoid

Including noindex Pages

If a page has a noindex meta tag or X-Robots-Tag header, it should not appear in your sitemap. Including it sends conflicting signals: "please index this page" (sitemap) versus "do not index this page" (noindex). Remove noindex pages from your sitemap.

Faking lastmod Dates

Some sites update the lastmod date on all pages daily regardless of actual changes. This causes crawlers to stop trusting your lastmod values, which means genuinely updated pages may not be re-crawled promptly. Only update lastmod when the content has actually changed.

URL Inconsistencies

Your sitemap URLs must match your canonical URLs exactly. If your site uses https://example.com/page (without trailing slash), do not list https://example.com/page/ (with trailing slash) in your sitemap. Mismatched URLs waste crawl budget and can create duplicate content issues.

Listing Broken or Redirected URLs

Pages that return 404 errors or 301 redirects should not be in your sitemap. Regularly audit your sitemap to remove URLs that no longer resolve to a 200 status. This keeps your sitemap clean and ensures crawl budget is spent on live pages.

Forgetting to Update the Sitemap

A stale sitemap that does not include new pages defeats the purpose of having one. If you manage your sitemap manually, set a reminder to update it whenever you add or remove pages. Better yet, use an automated generation method.

Checking Your Sitemap with IndexReady

The IndexReady scoring tool automatically checks whether your site has a valid sitemap.xml as part of its SEO analysis (scored out of 6 points in the SEO category). Simply enter your URL to get a comprehensive SEO and GEO audit that includes sitemap validation. If you are unsure whether your sitemap is set up correctly, IndexReady can help you identify issues quickly.

Summary

An XML sitemap is a foundational SEO element that helps search engines discover and index your pages efficiently. While it does not directly influence rankings, it ensures that your content is found, especially for large sites, new sites, and pages with limited internal links.

Modern tools and frameworks make sitemap generation almost effortless. Whether you use a CMS plugin, an online generator, or a framework like Next.js, there is no reason to skip this essential step. Set up your sitemap today and submit it to Google Search Console.

FAQ

Can my site rank without a sitemap.xml?

Yes, search engines can discover your pages through links without a sitemap. However, a sitemap improves crawl efficiency and helps new pages get indexed faster. It is a low-effort, high-value addition to any site.

How often should I update my sitemap?

Your sitemap should reflect your current site structure at all times. With CMS plugins or framework-based generation, updates happen automatically when you publish or modify content. If you maintain your sitemap manually, review it at least once a month.

Can I include images and videos in my sitemap?

Yes, the sitemap protocol supports extensions for images (<image:image>) and videos (<video:video>). Image sitemaps are particularly useful for sites that rely on image search traffic, as they help search engines discover images that might not be found through standard crawling.

What are the size limits for a sitemap file?

A single sitemap file can contain up to 50,000 URLs and must be no larger than 50 MB (uncompressed). If your site exceeds these limits, use a sitemap index file to split your URLs across multiple sitemap files.