Return

Sitemap Generator

Website Base URL

Enter your website's base URL (e.g., https://example.com). This will be prefixed to all URLs in the sitemap. Use the Import button to upload a CSV or TXT file with URLs in format: path, priority, changefreq, lastmod (only path is required). For example: /contact, 0.5, monthly, 2026-03-20

URL Entries

Ready to Generate Sitemap

Add URL entries above, configure priorities and change frequencies, then click Generate Sitemap to create a valid XML sitemap file for your website.

Early Website Discovery (1990s Early 2000s)

In the early days of the World Wide Web, search engines relied primarily on hyperlinks to discover new web pages. Crawlers would start from a seed list of known websites and follow links from page to page. This method meant that pages without any external links, often called orphan pages, remained invisible to search engines. Webmasters had limited control over which pages got indexed and when.

The Robots Exclusion Protocol, introduced in 1994, gave webmasters a way to block crawlers using robots.txt files, but it provided no mechanism to actively suggest URLs for indexing. This created a significant gap in search engine optimization, particularly for large websites with dynamic content or deep directory structures that crawlers might never reach. [Wikipedia, Robots Exclusion Standard]

The Sitemap Protocol Launch (2005)

In June 2005, Google introduced the Sitemap Protocol, a groundbreaking initiative that allowed webmasters to submit lists of URLs directly to search engines. The protocol used XML format with elements for location, last modification date, change frequency, and priority. This gave webmasters unprecedented control over how search engines discovered and crawled their content.

Later in 2005, Yahoo and Microsoft announced support for the same protocol, creating a unified standard. In November 2006, the三家 companies formally announced the Sitemap Protocol 0.9 under a joint public license. The protocol was submitted to Sitemaps.org, which became the official repository for documentation and specifications. [Sitemaps.org, Official Protocol] [Wikipedia, Sitemaps]

Evolution and Adoption (2006 Present)

In 2007, Google expanded the Sitemap Protocol to support news articles, videos, and images through specialized extensions. News sitemaps allowed publishers to submit time sensitive content, while video and image sitemaps provided metadata for rich media. Bing and Yandex (Russia's leading search engine) also adopted these extensions.

In April 2009, the protocol was updated to version 0.9, which remains the current standard. Key innovations included support for sitemap index files, allowing websites with more than 50,000 URLs to submit multiple sitemap files. Google announced that over 1.5 billion URLs were being submitted daily through the protocol. Today, sitemaps are considered a foundational element of technical SEO, supported by all major search engines including Baidu and Yandex. [Google, Sitemap Overview] [Bing, Sitemaps Help]

The Core Principle: Proactive Discovery

Traditional web crawling relies on following hyperlinks. A sitemap reverses this relationship. Instead of waiting for crawlers to find your pages through external links, you actively tell search engines about every URL you want indexed. This is particularly valuable for pages deep within directory structures, content behind forms, or pages with limited external links. [Google, Build a Sitemap]

The process begins when a webmaster creates an XML file following the sitemap protocol specification. This file lists URLs along with optional metadata: when each page was last modified (lastmod), how frequently the content changes (changefreq), and the page's relative importance within the website (priority). The webmaster then submits the sitemap location to search engines through webmaster tools or by placing the sitemap URL in the robots.txt file.

Submission and Crawling Integration

Search engines use sitemaps to supplement, not replace, regular crawling. When a search engine receives a sitemap submission, it validates the XML syntax and fetches the file. The URLs are added to the crawl queue, but discovery through links remains important. Google states that sitemaps do not guarantee inclusion or specific crawl frequency, but they significantly improve discovery, especially for new websites or pages with few backlinks.

The priority hint helps search engines allocate crawl budget effectively. A page with priority 1.0 might be crawled more frequently than a page with priority 0.1, but search engines ultimately determine ranking based on content quality and relevance, not priority metadata. The changefreq hint indicates how often the webmaster expects the page to change, helping crawlers schedule revisits. [Sitemaps.org, Protocol Specification]

Sitemap Index Files for Large Websites

A single sitemap file is limited to 50,000 URLs and 50 megabytes uncompressed. Websites exceeding these limits must create a sitemap index file, which lists up to 50,000 individual sitemap files. The index file follows similar XML syntax with sitemapindex as the root element and sitemap entries containing loc and lastmod elements. This hierarchical structure supports websites with millions of URLs, such as e-commerce platforms or large publishers.

Compression and Performance

Sitemap files can be compressed using gzip to reduce bandwidth and storage. The compressed file receives a .gz extension, but the filename inside must be sitemap.xml. Search engines automatically detect and decompress gzipped sitemaps. This is particularly important for large sitemaps, as compression typically reduces file size by 70 to 80 percent. [Google, Large Sitemaps]

XML Namespace and Root Elements

Protocol Version: 0.9 (Current Standard) | Schema Location: http://www.sitemaps.org/schemas/sitemap/0.9

Every sitemap must declare the XML namespace xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" within the urlset root element. The XML declaration with encoding="UTF-8" is required. Example structure: <?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">...</urlset> [Sitemaps.org, XML Tag Definitions]

URL Entry Elements

loc (Location): Required. The full URL of the page including the protocol (http or https). Must be properly escaped according to XML standards. Maximum length is 2048 characters. Example: <loc>https://example.com/about-us</loc>

lastmod (Last Modified): Optional. The date the page was last modified. Use ISO 8601 format: YYYY-MM-DD for dates or YYYY-MM-DDThh:mm:ssTZD for date and time. Timezone offset (TZD) is recommended for precise timing. Google recommends using lastmod to help crawlers detect changes. Example: <lastmod>2026-03-20</lastmod>

changefreq (Change Frequency): Optional. Hint to search engines about how frequently the page content changes. Valid values: always, hourly, daily, weekly, monthly, yearly, never. Always means the page changes on every request. Never should be used for archived content. This element does not affect crawl frequency but helps crawlers prioritize. Example: <changefreq>weekly</changefreq>

priority (Priority): Optional. The relative importance of a page within your website. Valid range is 0.0 to 1.0. Default value is 0.5. Priority only affects crawling within your site, not compared to external sites. Google recommends using priority to indicate relative importance of pages on your site. Example: <priority>0.8</priority> [Google, Sitemap URL Set]

Sitemap Index File Structure

For websites with more than 50,000 URLs, create a sitemap index file. The root element is <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">. Each sitemap entry contains <sitemap><loc> and optional <lastmod>. Index files support up to 50,000 entries. This allows websites to scale to 2.5 billion URLs (50,000 sitemaps × 50,000 URLs per sitemap).

Protocol Limits and Validation

Maximum URLs per sitemap: 50,000 | Maximum file size (uncompressed): 50 MB | Allowed characters in URLs: ASCII only. Non ASCII characters must be percent encoded. | XML escaping required: Ampersands (&), less than (<), greater than (>), single quotes ('), double quotes (") | Recommended encoding: UTF-8 | Compression: gzip allowed (.gz extension)

Sitemap files exceeding 50 MB or 50,000 URLs must be split into multiple sitemap files. Use the sitemap index file to list all individual sitemaps. All sitemap URLs must be in the same domain or subdomain as the sitemap location. Cross domain sitemaps are not allowed. [Sitemaps.org, Sitemap Index]

Specialized Sitemap Extensions

News Sitemap: For news articles published within the last 48 hours. Requires additional namespace xmlns:news="http://www.google.com/schemas/sitemap-news/0.9". Includes news:publication, news:publication_name, news:title, news:publication_date, and news:keywords.

Video Sitemap: For video content. Namespace xmlns:video="http://www.google.com/schemas/sitemap-video/1.1". Elements include video:thumbnail_loc, video:title, video:description, video:content_loc, video:duration, video:view_count, and video:publication_date.

Image Sitemap: For images embedded in pages. Namespace xmlns:image="http://www.google.com/schemas/sitemap-image/1.1". Elements include image:loc, image:caption, image:geo_location, image:title, and image:license. Multiple images can be listed per URL entry.

These extensions require separate schemas and are validated individually. Not all search engines support all extensions. Google supports all three, while Bing supports video and image sitemaps. [Google, News Sitemap] [Google, Video Sitemap]