XML Sitemap Generator

Create standards-compliant XML sitemaps ready for Google Search Console and Bing Webmaster Tools. Manage lastmod dates, change frequencies, and export clean XML code in seconds.

Indexed URLs (5)
Generated sitemap.xml

The Sitemaps.org Protocol v0.9 Architecture

Jointly introduced by Google, Microsoft, and Yahoo, the Sitemaps.org protocol establishes a uniform XML schema allowing webmasters to explicitly declare which pages are available for crawling.

Without a sitemap, search engine web crawlers must discover pages by traversing hyperlinks from the homepage. On complex single-page applications (SPAs) or deep architectural hierarchies, isolated "orphan" pages may never be discovered. An authoritative XML sitemap guarantees 100% crawl discovery.

Sitemaps.org XML Schema Tag Reference & Guidelines

XML TagSpecification FormatDescription & Crawler UsageRequirement
<loc>https://example.com/pageAbsolute canonical URL of the pageMandatory
<lastmod>YYYY-MM-DD (W3C Datetime)Date of most recent content updateStrongly Recommended
<changefreq>daily, weekly, monthly...Estimated update frequency hintOptional
<priority>0.0 to 1.0Relative importance within this domainOptional

Sitemap Index Architecture for Large Sites

When a website exceeds 50,000 URLs, use a master sitemap-index.xml that links to sub-sitemaps: e.g. /sitemap-articles.xml, /sitemap-products.xml, and /sitemap-categories.xml. This modular setup allows Google Search Console to display indexing ratios per content section.

Accurate lastmod Maintenance

Never mass-update the <lastmod> tag to the current date if the content has not changed. Search engines penalize false lastmod updates by ignoring the tag entirely for your domain. Only update lastmod when substantive text or code changes occur.

Sitemap Production Deployment Checklist

✓Include ONLY canonical URLs that return an HTTP 200 OK status code
✓Exclude all 301 redirects, 404 broken pages, and noindexed URLs
✓Use W3C datetime format (YYYY-MM-DD) for all <lastmod> tags
✓Declare the sitemap URL in your robots.txt file
✓Submit the sitemap directly to Google Search Console and Bing Webmaster Tools
✓Ensure file size does not exceed 50 MB (uncompressed) or 50,000 URLs

Frequently Asked Questions

Expert answers regarding XML sitemaps, indexation, and search crawler discovery.

What is an XML Sitemap and why is it necessary for Google indexing?

An XML Sitemap is a machine-readable document adhering to the Sitemaps.org Protocol v0.9 that lists all canonical URLs on a website along with metadata (such as when the page was last updated). It ensures search engine crawlers like Googlebot and Bingbot discover new and updated pages immediately, rather than relying solely on internal link discovery.

What are the official limits for a single XML Sitemap file?

Under the official Sitemaps.org specification, a single sitemap file can contain a maximum of 50,000 URLs and must not exceed 50 MB in uncompressed file size. For websites with more than 50,000 URLs, you must split URLs across multiple sitemap files and link them together using an XML Sitemap Index file (`<sitemapindex>`).

Why is the <lastmod> tag so important in modern SEO?

The `<lastmod>` tag specifies the W3C datetime format (YYYY-MM-DD) when the content was last meaningfully modified. Googlebot uses `<lastmod>` to calculate crawl urgency: if `<lastmod>` matches the timestamp of the last crawl, Googlebot can skip re-rendering the page, saving valuable crawl budget for recently updated pages.

Does Google respect the <priority> and <changefreq> tags?

Gary Illyes and John Mueller from Google have stated that Googlebot primarily focuses on `<loc>` (the URL) and `<lastmod>`. While `<priority>` and `<changefreq>` are largely ignored by Googlebot, other search engines - such as Bing, Yandex, and Baidu - continue to use these tags to schedule crawl cadence.

Should non-canonical or redirected (301) URLs be included in a sitemap?

No! A sitemap should ONLY contain canonical URLs that return an HTTP 200 OK status code. Including 301 redirects, 404 pages, or URLs with `noindex` tags creates conflicting signals in Google Search Console, triggering 'Submitted URL marked noindex' or 'Page with redirect' warnings.

Where should the sitemap be located on a server?

Host the sitemap at the root directory: `https://yourdomain.com/sitemap.xml`. In addition, always declare the sitemap location inside your `robots.txt` file (e.g., `Sitemap: https://yourdomain.com/sitemap.xml`) to facilitate automatic discovery across all search bots.

How do I submit my sitemap to Google Search Console?

Log in to Google Search Console, select your domain property, navigate to 'Indexing' -> 'Sitemaps' in the left sidebar, enter `sitemap.xml` in the 'Add a new sitemap' field, and click Submit.

How often should sitemaps be regenerated?

Sitemaps should be regenerated dynamically whenever new articles, products, or landing pages are published. Modern web frameworks like Next.js automatically generate and serve dynamic sitemaps at `/sitemap.xml` during runtime.

Need Automated Continuous Audits?

Upgrade from Single-Check to Automated DAST Vulnerability Scanner

Full-scale active fuzzing for OWASP Top 10, SQLi, XSS, SSRF & BOLA. Scale with automated schedules, Slack alerts, 150+ monthly credits, and compliance PDF exports on our paid tiers.

Headless Chromium SPA crawlerActive OWASP Top 10 fuzzingAutomated SQLi & XSS verification
Explore Paid Plans (from $9/mo)Launch Free Instant DAST Scan

Strengthen Your Technical Search Foundation

WeSecureX provides free developer utilities to audit search engine indexing, inspect security headers, and prevent duplicate content penalties.

Robots.txt GeneratorCanonical Tag GeneratorHreflang Tag GeneratorView All Tools