SEO TOOL

Sitemap XML Generator

Build XML sitemaps to help search engines discover and index your website pages. Set change frequency, priority, and last modification dates.

URL Entries

URL 1
URL 2
sitemap.xml
<?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-28</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.5</priority>
  </url>
  <url>
    <loc>https://example.com/about</loc>
    <lastmod>2026-03-28</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.5</priority>
  </url>
</urlset>

Sitemap Info

2
Valid URLs
2
Total Entries

Mapping Your Website for Search Engine Discovery

The Roadmap Search Engines Need

An XML sitemap is a machine-readable index of every important URL on your website. While search engines discover pages by following links, research shows that orphan pages(pages with no internal links pointing to them) make up 10–25% of content on typical websites. These pages are invisible to crawlers without a sitemap. Google processes billions of URLs daily and uses sitemaps as a priority signal—URLs listed in your sitemap get crawled faster than those discovered through link following alone. For a new website, submitting a sitemap can reduce initial indexing time from weeks to just 2–4 days.

Understanding the XML Structure

<url>
  <loc>https://example.com/page</loc>
  <lastmod>2024-01-15</lastmod>
  <changefreq>weekly</changefreq>
  <priority>0.8</priority>
</url>

Each URL entry contains four possible elements. <loc>is the only required field—the full canonical URL. <lastmod> tells crawlers when the content last meaningfully changed (use W3C datetime format: YYYY-MM-DD).<changefreq> hints at how often the page updates (hourly, daily, weekly, monthly, yearly, never). <priority>ranges from 0.0 to 1.0 and tells crawlers the relative importance within your own site—it does not affect rankings between different websites. Google has stated they primarily use <loc> and <lastmod>, and largely ignore changefreq and priority.

The 50,000-URL Limit and Sitemap Indexes

A single sitemap file is capped at 50,000 URLs and 50 MB uncompressed (per the sitemaps.org protocol). For larger sites, you create a sitemap index filethat references multiple sitemap files—up to 50,000 sitemaps in a single index, giving you a theoretical maximum of 2.5 billion URLs. Best practice is to segment sitemaps logically: one for blog posts, one for product pages, one for category pages. This makes it easy to monitor crawl coverage in Google Search Console, where you can see exactly how many URLs from each sitemap have been indexed. A site with 8,000 products might use sitemap-products.xml and sitemap-blog.xml referenced from a sitemap-index.xml.

The lastmod Accuracy Problem

Google's Gary Illyes has stated that lastmod is the most valuable sitemap signal—but only when accurate. Many CMS platforms auto-update lastmod timestamps whenever any minor edit occurs (fixing a typo, changing a category tag), training Google to distrust the signal for that domain. When Google detects that lastmod dates are unreliable, it may ignore them entirely and fall back to its own crawl schedule. The fix is to only update lastmod when the page's main content meaningfully changes. A blog post that receives a substantial update should get a new lastmod; a sidebar widget change should not. Accurate lastmod dates can accelerate re-indexing of updated content from days to hours.

Frequently Asked Questions

How do I submit my sitemap to Google and Bing?

There are three methods. First, add a Sitemap: https://example.com/sitemap.xmldirective to your robots.txt file—this is the most widely supported method across all search engines. Second, submit directly via Google Search Console (Sitemaps section) or Bing Webmaster Tools (Submit Sitemaps). Third, use the Search Console API for programmatic submission. Google also supports ping: send a GET request to https://www.google.com/ping?sitemap=YOUR_SITEMAP_URL. After submission, monitor the “Coverage” report in Search Console to track how many submitted URLs are actually indexed.

Should non-indexable pages appear in my sitemap?

No. Your sitemap should only contain canonical, indexable URLs that return a 200 HTTP status code. Exclude pages with noindexmeta tags, 301/302 redirects, 404 error pages, paginated URLs (use rel=next/prev instead), URL parameter variations, and non-canonical duplicate content. Including non-indexable URLs sends mixed signals—you are telling Google “index this” via the sitemap while simultaneously saying “don't index this” via the noindex tag. Google Search Console will flag these as “Submitted URL marked noindex” errors.

Does the priority tag actually influence Google rankings?

Google has officially stated that they do not use the priority tagas a ranking factor. The priority value (0.0–1.0) is a hint to crawlers about relative importance within your own site, not a way to boost rankings. Setting every page to priority 1.0 is equivalent to setting none—when everything is a priority, nothing is. If you use it, reserve 1.0 for your homepage, 0.8 for key landing pages, 0.6 for regular content, and 0.3–0.4 for archive or tag pages. Bing has indicated they may use priority as a minor crawl scheduling hint, but it has no effect on actual search result positioning.