XML Sitemap: What It Is, How to Create One, and How to Submit It to Google

What Is an XML Sitemap?

An XML sitemap is a structured file (usually named sitemap.xml) that lists all the URLs on your website that you want search engines to discover and index. It uses a standardized XML format defined by the sitemaps.org protocol, which was jointly developed by Google, Yahoo, and Microsoft back in 2006.

Think of it like a table of contents for a book. A reader can find chapters by flipping through pages, but a table of contents makes it faster and ensures nothing is missed. Similarly, search engine crawlers can discover your pages by following links, but a sitemap guarantees they know about every important page—including ones that might be buried deep in your site structure or have few internal links pointing to them.

Here is the critical distinction: a sitemap is a suggestion. It tells search engines which pages you consider important and would like indexed. It does not guarantee indexing. Google will still evaluate each page on its own merits—content quality, crawlability, canonical status, and so on. But without a sitemap, you are relying entirely on Google's crawling to discover your pages, and for large or frequently updated sites, that is not a gamble worth taking.

Why Sitemaps Matter for SEO

Google's own documentation states that sitemaps are especially useful in four scenarios:

• Your site is large. When you have thousands of pages, crawlers may not discover new or recently updated pages through normal crawling alone.
• Your site has isolated pages. If some pages are not well linked from other pages on your site, a sitemap helps crawlers find them.
• Your site is new. New websites have few external links, making it harder for crawlers to discover them organically.
• Your site uses rich media or appears in Google News. Sitemaps can provide additional metadata about videos, images, and news articles.

Beyond discovery, sitemaps serve another purpose that is often overlooked: they communicate freshness. The lastmod tag tells Google when a page was last modified. If you update it accurately, Google can prioritize re-crawling pages that have actually changed, rather than wasting crawl budget on stale content.

I worked with a news publisher that was adding 50-100 articles per day. Before implementing a properly configured sitemap with accurate lastmod dates, new articles took 4-8 hours to appear in Google. After the sitemap was set up correctly, that dropped to 15-30 minutes. The sitemap did not make Google crawl faster in absolute terms—it helped Google understand which pages needed immediate attention.

Anatomy of a Sitemap: Tags and Structure

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-02-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/about</loc>
    <lastmod>2026-01-10</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.5</priority>
  </url>
</urlset>

Let me break down each tag:

• <loc> (required): The full, absolute URL of the page. Must include the protocol (https://) and must match the canonical URL.
• <lastmod> (optional but recommended): The date the page was last meaningfully modified. Use W3C datetime format: YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+00:00. Only update this when the content actually changes—not on every page load.
• <changefreq> (optional): How frequently the page is expected to change. Values: always, hourly, daily, weekly, monthly, yearly, never. Google has publicly stated that it largely ignores this tag, so it is not worth spending time on.
• <priority> (optional): A value between 0.0 and 1.0 indicating the relative importance of a page within your site. Google also largely ignores this, but some other search engines may use it as a minor signal.

In practice, I recommend focusing on loc and lastmod. The other two tags are technically part of the spec but provide minimal SEO value with modern search engines.

Creating Your First Sitemap

There are three main approaches to creating a sitemap, depending on your technical setup:

Option 1: Use a Generator Tool

For small to medium sites (under 500 pages), a generator tool is the fastest approach. Our Sitemap Generator crawls your website and produces a ready-to-use sitemap.xml file. You upload it to your server root and you are done.

Option 2: CMS Plugins

If you use WordPress, Yoast SEO or Rank Math will generate and maintain your sitemap automatically. For other CMS platforms, there are similar solutions. The advantage of this approach is that the sitemap updates automatically when you publish or edit content.

Option 3: Programmatic Generation

For custom-built applications, you generate the sitemap from your database or routing configuration. Most web frameworks have libraries for this. In ASP.NET Core, you can create a middleware or endpoint that queries your database and outputs XML. In Next.js, the next-sitemap package handles this elegantly.

Regardless of the approach, the output should be placed at https://yourdomain.com/sitemap.xml and referenced in your robots.txt file:

User-agent: *
Allow: /

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

Sitemap Index Files: When and Why

A single sitemap file has two hard limits:

• Maximum 50,000 URLs per sitemap file.
• Maximum 50 MB uncompressed file size.

If your site exceeds either limit, you need to split your sitemap into multiple files and create a sitemap index that references them:

<?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-02-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-posts.xml</loc>
    <lastmod>2026-02-17</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-products.xml</loc>
    <lastmod>2026-02-16</lastmod>
  </sitemap>
</sitemapindex>

Even if your site is well under the limits, splitting sitemaps by content type is a good practice. It makes it easier to diagnose indexing issues in Google Search Console, where you can see coverage statistics per sitemap file. If your blog posts are not getting indexed, you can quickly check whether the blog sitemap is the problem without wading through thousands of product URLs.

Submitting to Google and Bing

Google Search Console

1. Sign in to Google Search Console.
2. Select your property (make sure you are using the correct protocol and domain).
3. In the left sidebar, go to Sitemaps under the Indexing section.
4. Enter your sitemap URL (e.g., sitemap.xml or sitemap_index.xml).
5. Click Submit.

After submission, Google will show the status (Success, Has errors, or Could not fetch) and the number of discovered URLs. It typically takes a few days for Google to fully process a new sitemap.

Bing Webmaster Tools

The process is nearly identical in Bing Webmaster Tools. Navigate to Sitemaps in the left menu, enter your sitemap URL, and submit. Bing also supports automatic sitemap discovery through your robots.txt file.

Passive Discovery

Even without manual submission, search engines will find your sitemap if it is referenced in your robots.txt file. This is why including the Sitemap: directive in robots.txt matters—it is your backup submission method that requires zero manual work.

Common Sitemap Issues and Fixes

Including noindex or redirected pages

Your sitemap should only contain pages that return a 200 HTTP status and do not have a noindex meta tag. Including 301 redirects, 404 errors, or noindex pages in your sitemap sends mixed signals to search engines and wastes crawl budget.

URL mismatches with canonical tags

If a page's canonical tag points to a different URL than what is in the sitemap, Google will be confused. Make sure sitemap URLs match their corresponding canonical URLs exactly—including trailing slashes, www vs non-www, and http vs https.

Stale lastmod dates

Setting all lastmod dates to "today" every time you regenerate the sitemap destroys its usefulness. Google will eventually learn that your lastmod dates are unreliable and start ignoring them. Only update lastmod when the page content actually changes.

Sitemap too large or timing out

If your sitemap takes too long to generate or the file is too large, Google may fail to fetch it. Use gzip compression (serve as sitemap.xml.gz) and split into multiple files if needed. Most web servers handle gzip automatically, but verify by checking the Content-Encoding header.

Best Practices for Ongoing Maintenance

1. Automate sitemap generation. Manual sitemaps become stale fast. Use a CMS plugin or build generation into your deployment pipeline.
2. Monitor in Search Console. Check your sitemap status weekly. Look at the ratio of submitted vs. indexed URLs—a large gap indicates issues.
3. Keep it clean. Only include URLs you want indexed. Every unnecessary URL in your sitemap dilutes the signal.
4. Use accurate lastmod. This is the most underused feature. Accurate dates help search engines prioritize fresh content.
5. Combine with robots.txt. Your robots.txt and sitemap should tell a consistent story. Do not list URLs in the sitemap that are blocked by robots.txt.

Getting your sitemap right is not glamorous work, but it is one of those foundational SEO tasks that pays dividends over time. Use our Sitemap Generator to create yours in seconds, pair it with a properly configured robots.txt, and let search engines do what they do best—find your content and show it to the people searching for it.