XML Sitemaps 2026: Complete Guide to Faster Google Indexing

An XML sitemap is a file that lists the important pages on your website so search engines can find them quickly. It won't guarantee that Google indexes your pages, and it won't boost your rankings — but a clean, accurate sitemap is the fastest way to tell Google "these pages exist, and here's when they changed." For new sites and frequently updated sites, that direct line to Google's crawlers can cut indexing time from weeks to days. This guide covers everything you need: the format, what to include, how to submit it, and the mistakes that slow indexing down.

What an XML sitemap actually does

Google discovers pages in two ways: by following links from pages it already knows, and by reading sitemaps you provide. Crawling links works, but it's indirect — a new page buried three clicks deep might wait weeks for Googlebot to wander by. A sitemap hands Google the list directly.

To be precise about what sitemaps do and don't do:

They speed up discovery. Google still has to crawl each URL, but it learns about them sooner.
They help with pages links miss. New pages, pages with few internal links, and pages in deep site structures benefit most.
They communicate freshness. The lastmod date tells Google when a page last changed, which helps it prioritize recrawls.
They don't guarantee indexing. Google may still choose not to index a page it considers low-value or duplicate. A sitemap is an invitation, not a command.
They don't affect rankings. No URL gets a ranking boost for being in a sitemap.

Think of it as giving Google a map of your site instead of making it explore blindly. The map doesn't make the destination more attractive — but it does make it findable.

The basic format, line by line

A sitemap is an XML file, usually named sitemap.xml and placed at your site root (https://example.com/sitemap.xml). Here's a minimal valid 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-10-01</lastmod>
  </url>
  <url>
    <loc>https://example.com/blog/seo-guide</loc>
    <lastmod>2026-09-28</lastmod>
  </url>
</urlset>

Each <url> block has:

<loc> (required). The full URL, including https://. Must be on the same domain as the sitemap (or a verified subdomain setup).
<lastmod> (recommended). The date the page last changed, in YYYY-MM-DD format. This is the most useful optional tag — keep it honest.
<changefreq> (optional). How often the page changes: always, hourly, daily, weekly, monthly, yearly, never.
<priority> (optional). A number from 0.0 to 1.0 indicating the URL's importance relative to other pages on your site.

Now the important part: Google ignores changefreq and priority. Google has stated this publicly — its crawlers decide what to crawl based on their own signals, not your declared priorities. Including them is harmless but pointless. lastmod, on the other hand, is genuinely used: an accurate last-modified date helps Google decide what deserves a fresh crawl. If you include lastmod, make sure it reflects reality — a sitemap where every page claims to have changed today trains Google to ignore your dates.

The full technical specification lives at sitemaps.org, and Google's own sitemap documentation covers how Google specifically uses them.

What to include — and what to leave out

A sitemap should list the pages you want indexed. That sounds obvious, but most sitemaps are polluted with URLs that shouldn't be there. Include:

Your homepage and main landing pages.
Blog posts, articles, guides, and documentation.
Product and category pages (for stores).
Any page that earns traffic or could earn traffic.

Leave out:

Pages blocked by robots.txt. Listing a URL in your sitemap while disallowing it in robots.txt sends contradictory signals. Google generally follows the robots.txt block.
Noindex pages. If a page has a noindex tag, don't list it. You're telling Google "index this" and "don't index this" at the same time.
404s and redirects. Only list URLs that return a 200 status. Redirect chains and dead pages in a sitemap waste crawl budget and erode trust in the file.
Non-canonical URLs. If the canonical version of a page is URL A, list A — not the parameterized or duplicate variants.
Thin utility pages. Tag archives, empty category pages, pagination beyond what's useful, internal search results. If you wouldn't want it in search results, don't put it in the sitemap.

A good rule: your sitemap should roughly match the set of pages you'd be happy to see ranking. For most small sites, that's tens or hundreds of URLs — not thousands.

Size limits and when you need a sitemap index

The sitemap protocol sets hard limits per file: 50,000 URLs or 50 MB uncompressed, whichever comes first. Most sites never come close. But if you do outgrow a single file, you don't cram — you create a sitemap index, a file that lists your 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-10-01</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-products.xml</loc>
    <lastmod>2026-09-30</lastmod>
  </sitemap>
</sitemapindex>

You then submit the index file, not the individual sitemaps. Common practice is to split by content type (posts, pages, products) so you can spot problems per section. Note: this guide focuses on sitemap fundamentals — large sites with millions of URLs need additional strategies around index files, crawl budget, and prioritization, which deserve their own treatment.

Submitting your sitemap to Google

Google will eventually find a sitemap at the standard location, but submitting it directly is faster and gives you reporting. Two methods:

Google Search Console (recommended). Go to Indexing → Sitemaps, enter the sitemap URL (just the path, e.g. sitemap.xml), and click Submit. Google starts processing within hours and typically shows status within a day or two. The Sitemaps report then tells you how many URLs were discovered and flags errors.
The robots.txt Sitemap directive. Add a line to your robots.txt: Sitemap: https://example.com/sitemap.xml. This points every crawler — not just Google — to your sitemap. Do this in addition to Search Console submission, not instead of it.

Bing has its own submission flow in Bing Webmaster Tools, and the robots.txt directive covers Bing's crawler automatically.

If you don't have a sitemap yet, a sitemap generator can build one from your URLs in minutes — much more reliable than hand-writing XML.

Keeping your sitemap fresh

A sitemap is a living file. The best setups regenerate it automatically:

WordPress: SEO plugins like Rank Math and Yoast generate and update sitemaps automatically when you publish or edit content. If you use one, check that it's active — some sites accidentally run two sitemap systems that conflict.
Other CMSs: Most platforms have a sitemap plugin or built-in feature. Enable it and verify the output URL.
Custom sites: Generate the sitemap in your build or deploy process, or on a schedule (a nightly cron job works). The generation script should pull from the same source of truth as your site — your database or content files — so it can never drift.

Whatever the setup, lastmod should update when the page content actually changes — not on every deploy, and not never. A lastmod that always says today is as useless as one frozen in 2021.

Common sitemap mistakes that slow indexing

Listing noindex or blocked pages. The single most common error. Audit: every URL in your sitemap should be indexable, crawlable, and returning 200.
Stale lastmod dates. If your dates don't reflect real changes, Google learns to distrust them — and you lose the freshness signal.
Including redirect chains. List the final destination URL, not the old URL that redirects to it.
www vs. non-www (or http vs. https) mismatches. Sitemap URLs must use your canonical domain exactly. Mixed variants look like errors.
Submitting once and forgetting. Check the Search Console Sitemaps report monthly. Errors like "couldn't fetch" or "unsupported file format" sit unnoticed for months on neglected sites.
One giant sitemap for everything. Under the limits it's fine technically, but splitting by content type makes debugging far easier when something goes wrong.
Blocking the sitemap in robots.txt. Rare but real: a broad Disallow rule that accidentally covers /sitemap.xml. Test your robots.txt with a robots.txt tester after any change.

How to check whether it's working

After submitting, use Search Console to verify:

Sitemaps report: shows status (Success, with the discovered URL count), last read date, and any errors.
Pages report (Indexing → Pages): shows how many submitted pages are actually indexed vs. discovered-but-not-indexed. A large gap means Google found your URLs but chose not to index many of them — that's a content quality signal, not a sitemap problem.
URL Inspection tool: paste any specific URL to see its crawl and index status, plus the referring sitemap.

Give a new sitemap one to two weeks before judging results. If submitted pages still aren't indexed after that, the issue is almost never the sitemap — it's usually thin content, duplication, or weak site authority.

Image, video, and news sitemaps: a brief note

The protocol supports extensions for images, video, and news content. In practice: most sites don't need them. Google discovers images through normal crawling of pages that contain them. Video sitemaps are worth considering if video is central to your business and you want rich video results; Google News sitemaps only matter if you're an approved Google News publisher. For everyone else, a clean standard sitemap is the whole job.

Troubleshooting slow indexing

If Google is slow to index your new pages, work through this list in order:

Is the page in your sitemap, with a current lastmod?
Is the sitemap submitted in Search Console with a Success status?
Does the URL return 200, load quickly, and render fully?
Is it linked from somewhere — your homepage, a category page, a recent post? Internal links still drive crawl priority.
Is the content original and substantial? Google routinely skips indexing thin or near-duplicate pages regardless of sitemaps.
Use URL Inspection → "Request indexing" for a handful of priority URLs. (It's a nudge for individual pages, not a bulk solution — don't spam it.)

Sitemaps are plumbing: invisible when they work, blamed for everything when they don't. Keep yours clean, current, and honest, and it will quietly do its job — getting your pages discovered faster so your content can compete.

Frequently asked questions

Does a sitemap guarantee my pages will be indexed?

No. A sitemap helps Google discover your URLs faster, but Google still decides what to index based on quality, uniqueness, and site authority. Think of it as making sure Google sees your pages — what happens next depends on the pages themselves.

Do small websites need a sitemap?

Yes, especially new ones. Small sites with few backlinks are the hardest for crawlers to discover through links alone. A sitemap is free, takes minutes to set up, and removes discovery as a bottleneck.

Should I use priority and changefreq tags?

You can, but Google ignores both. The only optional tag worth your attention is lastmod — and only if the dates are accurate. Spend the effort on keeping lastmod honest instead of tuning priority values nobody reads.

How often should my sitemap update?

Automatically, whenever content changes. Manual sitemap maintenance always drifts out of date eventually. Use your CMS's built-in sitemap feature or a scheduled generation script.

Can I have more than one sitemap?

Yes. Use a sitemap index file to list multiple sitemaps, split by content type (posts, products, pages). You can submit up to 50,000 sitemaps in a single index, each holding up to 50,000 URLs.

Why does Search Console show "Discovered – currently not indexed" for my sitemap URLs?

Google found the URLs via your sitemap but hasn't crawled or indexed them yet — or chose not to. For new sites this often resolves with time and more authority. If it persists across many URLs, the cause is usually thin or duplicate content, not the sitemap.

XML Sitemaps in 2026: The Complete Guide to Faster Google Indexing