ES
navigate Enter open Esc close
SEO Tool

XML Sitemap Generator & Validator

Create and validate XML sitemaps for Google Search Console compliant with sitemaps.org standards.

Technical Standard Reviewed · Last review: August 29, 2026Official sources: Google Search Central· Sitemaps.org

1. Paste your URL list (one per line):

2. Default parameters:

Complete Technical Guide to XML Sitemaps: Architecture, Indexing Signals & Search Console Integration

An XML Sitemap is a standardized, machine-readable protocol file hosted on your web server that provides search engine crawlers (Googlebot, Bingbot, Yandex) with a comprehensive blueprint of your website’s indexable architecture. Beyond listing URLs, sitemaps communicate crucial metadata including the last modification timestamp (``), publication frequency (``), and relative indexing priority (``).

For e-commerce stores, news publications, and content networks with complex architectures, a clean XML sitemap ensures search engines discover deep catalog pages, prevent orphaned content from remaining unindexed, and prioritize crawl budget on recently updated, high-value commercial URLs.

The Sitemaps.org 0.9 XML Protocol Specification

Every valid XML sitemap must adhere strictly to the schema definition published at http://www.sitemaps.org/schemas/sitemap/0.9:

  • <urlset>: The root XML wrapper enclosing all individual URL nodes, declaring the official XML namespace.
  • <url>: The parent container representing each individual page entry.
  • <loc>: The mandatory fully-qualified absolute URL (must include https:// protocol and exact domain). Relative URLs like /contact/ are strictly invalid.
  • <lastmod>: The W3C Datetime timestamp (e.g., YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZD). Googlebot heavily relies on this tag to decide whether to re-crawl existing cached pages.
  • <changefreq>: Expected update frequency (always, hourly, daily, weekly, monthly, yearly, never).
  • <priority>: Relative importance score ranging from 0.0 to 1.0 (default is 0.5, homepage is typically 1.0).

Crawl Budget Optimization & Orphan Page Elimination

Search engine spiders operate under resource limits known as crawl budget—the number of simultaneous HTTP requests a bot dedicates to your server without causing performance degradation. Listing URLs cleanly in an XML sitemap eliminates orphan pages (pages lacking incoming internal links from the main navigation) and allows Googlebot to bypass complex JavaScript menu trees, driving indexation velocity for newly released products or time-sensitive articles.

XML Sitemap Limits & Sitemap Index Files (`<sitemapindex>`)

The protocol enforces hard limits: a single sitemap file cannot contain more than 50,000 URLs and must not exceed 50 MB uncompressed. Enterprise platforms with hundreds of thousands of URLs solve this by structuring a Sitemap Index file (e.g., sitemap_index.xml) that references categorized sub-sitemaps (e.g., sitemap-products.xml, sitemap-categories.xml, sitemap-blog.xml).

Critical Quality Rules: What NEVER to Put in an XML Sitemap

Maintaining high sitemap hygiene is vital to avoid coverage warnings in Google Search Console:

  • No Non-Canonical URLs: Never include duplicate or filtered URLs containing tracking parameters.
  • No Redirects (301/302): Every URL in the sitemap must return a clean HTTP 200 OK status code.
  • No Blocked Pages (Noindex / 404): Including pages with noindex robots tags or broken 404 links creates contradictory indexing signals.
  • No Inaccessible or Staging URLs: Localhost links or password-protected admin URLs must be strictly filtered out.

Google Search Console & Robots.txt Deployment Workflow

Once your sitemap.xml is generated and uploaded to your root directory, declare its absolute URL at the end of your robots.txt file (e.g., Sitemap: https://example.com/sitemap.xml). Next, log into Google Search ConsoleIndexingSitemaps, enter the URL path, and submit to verify status and track discovered URL coverage.

Practical Example

Example 1: Generating a Standard XML Sitemap for Corporate Business Site
Input: URLs: https://example.com/ (Priority 1.0) | https://example.com/services/ (0.8) | https://example.com/contact/ (0.5)
Output / Result: Clean XML document starting with <?xml version="1.0" encoding="UTF-8"?> and valid <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> tags

Provides Googlebot with immediate, validated discovery paths for primary business landing pages.

Example 2: Fast Re-Indexing via Accurate Lastmod Timestamps
Input: Updated Article URL: https://example.com/blog/seo-guide/ | Lastmod: 2026-08-28 | Changefreq: weekly
Output / Result: XML <url> block including <lastmod>2026-08-28</lastmod> date stamp

Signals search crawlers that fresh content has been published, triggering priority re-crawling.

How to Generate an XML Sitemap in 4 Steps

1

Paste Canonical URLs

Paste your list of absolute HTTPS website URLs (one URL per line) into the input field.

2

Set Frequency & Priority

Choose your default change frequency (e.g. weekly), priority rating (e.g. 0.8), and lastmod date.

3

Generate XML Markup

Click "Generate sitemap.xml" to synthesize a fully compliant sitemaps.org protocol file.

4

Download & Submit to Google

Download your `sitemap.xml`, upload it to your server root, and submit its URL in Google Search Console.

Frequently Asked Questions about XML Sitemaps

What is an XML Sitemap and why is it essential for Google SEO?

An XML Sitemap is a machine-readable protocol file listing all authoritative, indexable URLs of your website. Submitting your sitemap directly to Google Search Console and Bing Webmaster Tools accelerates new page discovery, directs crawl budget efficiently, and communicates page update timestamps via ``.

What are the limits on maximum URLs and file size for an XML sitemap?

According to the official sitemaps.org protocol, a single sitemap.xml file can contain up to 50,000 URLs and cannot exceed 50 MB in uncompressed size. Websites exceeding these thresholds must use a Sitemap Index file (``) linking to multiple sub-sitemaps.

Should non-indexable (noindex, 404, 301) URLs be included in sitemap.xml?

No. An XML sitemap should exclusively contain canonical, indexable 200 OK URLs. Including redirecting (301/302), broken (404), or noindexed URLs wastes search bot crawl budget and triggers coverage warnings in Google Search Console.

How does Google interpret `<priority>` and `<changefreq>` tags in 2026?

While Googlebot primarily relies on the `` timestamp and internal link equity rather than strictly obeying `` or ``, these tags remain valuable standardized hints for other search engines like Bing, Yandex, and Baidu.

Where should the sitemap.xml file be uploaded and linked on a web server?

Upload `sitemap.xml` directly to your website root directory (e.g., `https://yourdomain.com/sitemap.xml`). In addition, declare its location inside your `robots.txt` file (using `Sitemap: https://yourdomain.com/sitemap.xml`) and submit it to Google Search Console.

Share this tool

Help others by sharing this free tool.