XML Sitemap Generator

After 11+ years working in technical SEO—from enterprise e-commerce platforms to independent publishing sites, from global agencies to freelance projects—one bottleneck kept recurring across every engagement: creating and maintaining accurate, up-to-date XML sitemaps was unnecessarily complex.

Developers spent hours configuring WordPress plugins or writing custom scripts. SEO analysts relied on online crawlers that were slow for large sites, required authentication, or limited URL counts. Content managers lacked control over when and how to update the sitemap after publishing new pages.

We tested dozens of existing solutions and found two problematic extremes: auto-crawling generators (useful but slow for large sites and prone to failure on authenticated or JavaScript-heavy sites) or manual XML editors requiring advanced technical knowledge. What was missing: a tool that's fast, precise, and gives you full control without compromising privacy.

That's why we built the RankBox Sitemap Generator. The approach is different: you stay in control. Paste your site's URLs (exported from your CMS, database, or crawl tool), configure lastmod with precision—knowing exactly what Google values—and download a valid, optimized sitemap.xml. No slow auto-crawling, no external server uploads, no complications.

Whether you're a developer updating the sitemap post-deploy, an SEO specialist auditing indexation structure, or a content manager publishing new landing pages: this tool transforms a technical process into a simple 30-second task.

In an era where data leaks and exposure of site architecture are real security concerns, the RankBox Sitemap Generator uses a fundamentally different architecture than most online tools.

How Local (Client-Side) Processing Works:

1. Zero data transmission: When you paste URLs and configure your sitemap, everything stays in your browser's memory. No data is sent over the internet. 2. Native JavaScript generation: Your browser processes URL validation, XML formatting, and sitemap.xml creation entirely locally. 3. Instant download: The file generates as a Blob (Binary Large Object) in your browser and becomes available for immediate download. 4. Automatic cleanup: Close the tab or refresh, and all URLs are wiped from memory. We don't create logs, store history, or track which sites you generate sitemaps for.

• GDPR & CCPA compliant: Since no personal data or site structure is processed externally, there's no international data transfer or privacy risk.
• Enterprise security: Companies can generate sitemaps for development sites, intranets, or NDA projects without exposing architecture.
• Real-time speed: Without crawl time or upload/download latency, generation is instant—limited only by your device's capability.
• Works offline: After the page loads, you can use the generator without any internet connection.

Verify it yourself: open browser DevTools (F12), navigate to the "Network" tab, and generate a sitemap. You'll see zero requests sent during the process.

The interface is designed for speed, but following a structured workflow ensures a valid, SEO-optimized XML sitemap.

Step 1: Paste Your Site URLs

• Export from your CMS: Pull URLs from WordPress, Shopify, Webflow, or other platforms
• Extract from tools: Use data from Screaming Frog, Sitebulb, or Google Analytics
• Paste manually: For small sites, paste URLs one per line

Correct format:

https://yoursite.com/ https://yoursite.com/about https://yoursite.com/products/product-1 https://yoursite.com/blog/article-example

Pro tip: Include only canonical URLs (200 OK). Exclude redirects (301/302), 404 pages, and URLs with session or tracking parameters.

Step 2: Configure Last Modified Date (lastmod)

The lastmod field is the only metadata Google actually considers—and only when it's consistently accurate.

• Today (2026-05-16): Sets current date for all URLs (useful for new sites or bulk updates)
• Custom: Define a specific date (YYYY-MM-DD)
• Omit: Exclude lastmod entirely (not recommended for sites with updated content)

• New site: Use "Today" for all URLs
• Targeted update: Use "Custom" with the actual last modification date
• Static content: If pages never change, you can omit lastmod

⚠️ Critical: Google ignores lastmod if you update all dates every time you generate a sitemap without real page changes. Be precise!

Step 3: Adjust Advanced Settings (Optional)

Google officially states that changefreq and priority are ignored by its indexing algorithm. However, you can include them if desired:

• always - For pages changing on every load (rare)
• hourly - For news feeds or real-time data
• daily - For blogs with daily publishing
• weekly - For most sites (recommended default)
• monthly - For static institutional pages
• yearly - For rarely updated content
• never - For archived or historical pages

• Values from 0.0 to 1.0
• Default is 0.5
• Use 1.0 for homepage, 0.8-0.9 for main pages, 0.3-0.6 for secondary content

Note: Including these fields doesn't hurt, but provides no measurable SEO benefit. Focus on accurate lastmod.

Step 4: Generate & Validate

• Validates each URL format (must be absolute with https://)
• Checks for duplicate URLs
• Formats XML per sitemaps.org protocol
• Displays a preview of the generated file

• ✅ URLs must be absolute (with https://)
• ✅ Maximum 50,000 URLs per file (Google limit)
• ✅ Maximum size: 50MB uncompressed
• ✅ Well-formed, valid XML

Step 5: Download & Deploy

• Copy XML: Copy code to paste directly on your server
• Download sitemap.xml: Download the ready file

Where to place the file: 1. Upload to domain root: https://yoursite.com/sitemap.xml 2. Test by accessing the URL directly in browser 3. Reference in robots.txt: Sitemap: https://yoursite.com/sitemap.xml 4. Submit in Google Search Console

To maximize the tool's value, it's essential to understand how sitemaps work and when they're truly necessary.

What Is an XML Sitemap?

An XML sitemap is a structured file that lists all important URLs on your site and provides metadata about each—primarily when it was last updated (lastmod). It acts as a navigation map for search engine crawlers (Googlebot, Bingbot, etc.), ensuring all pages are discovered and indexed.

Example XML structure:

<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://yoursite.com/</loc> <lastmod>2026-05-16</lastmod> </url> <url> <loc>https://yoursite.com/about</loc> <lastmod>2026-05-10</lastmod> </url> </urlset>

XML Sitemap vs. HTML Sitemap vs. RSS Feed

Three main sitemap formats exist, each with a specific purpose:

Important: XML sitemaps don't replace good internal linking, and HTML sitemaps don't replace XML for technical SEO. Use both when appropriate.

When You REALLY Need a Sitemap

Not every site needs a sitemap, but these scenarios benefit significantly:

🆕 New Site (<6 months old)

Newly registered domains have low domain authority and few backlinks. A sitemap accelerates initial page discovery by Google, reducing indexation time from weeks to days or hours.

📝 Blog with Frequent Publishing

New posts can take days to be crawled organically through internal links. A sitemap notifies Google immediately about new content, accelerating indexation and allowing posts to appear in results faster.

🛒 E-commerce with Extensive Catalog

Seasonal products, temporary promotions, and dynamic category pages need rapid discovery to avoid missing sales opportunities. A daily-updated sitemap ensures new products are indexed before marketing campaigns launch.

🔀 Site with Complex Architecture

Deep pages (4+ clicks from homepage) or pages with few internal links can become "orphaned"—Google won't discover them through traditional crawling. The sitemap explicitly references these pages, guaranteeing indexation.

🌐 Multilingual Site

Use hreflang in the sitemap to help Google understand language and regional versions of each page. This is cleaner than adding hreflang tags to every HTML page.

📰 News Site or Dynamic Content

For sites publishing multiple times daily, a separate news sitemap can accelerate indexation of urgent content.

Many tools highlight changefreq and priority as essential features. Google's official Search Central documentation is clear: these two fields are largely ignored by the indexing algorithm.

Sitemap Fields: Real SEO Impact

• How often a page changes (by analyzing change history)
• A page's importance (by analyzing internal links, backlinks, traffic)

Focus on what matters: Invest time in keeping lastmod accurate. If you update lastmod for all pages every time you generate a sitemap—even without real changes—Google will learn to ignore that signal too.

🛒 E-commerce (Shopify, BigCommerce, WooCommerce)

Challenge: Catalogs with thousands of products, dynamic filter/category URLs, seasonal products that come and go.

• Export active product URLs from your CMS
• Generate sitemap daily or after adding new products
• Separate sitemaps by type: products.xml, categories.xml, blog.xml
• Use sitemap index for sites with >50,000 URLs

Real example: A fashion e-commerce with 15,000 products. Instead of relying on auto-crawling (slow and error-prone), export active URLs from your database, paste into RankBox, configure lastmod with the last inventory update date, and generate the sitemap in 30 seconds.

📝 Blogs & Content Publishers (WordPress, Ghost, Substack)

Challenge: Frequent publishing (daily or multiple times daily), need for rapid indexation of urgent content.

• Integrate sitemap generation into your publishing workflow
• After publishing a post, regenerate the sitemap automatically
• Use precise lastmod for each post (publish or update date)
• Create a dedicated sitemap for recent posts

Recommended workflow: Configure a WordPress hook that, after publishing/updating a post, exports modified URLs, calls RankBox via API (if available in the future) or generates locally, and uploads the updated sitemap.

🏢 Corporate & Institutional Sites

Challenge: Static sites with few updates, but need to ensure all pages are indexed—especially after redesigns or migrations.

• Generate sitemap after migration or redesign
• Validate that all important pages are included
• Exclude old pages that were removed (return 404)
• Update sitemap only when structural changes occur

Tip: For static institutional sites, updating the sitemap monthly or quarterly is sufficient. No need for complex automation.

🔧 Developers & SEO Agencies

Challenge: Managing sitemaps for multiple clients, each with different needs, tight deadlines, and specific requirements.

• Standardize sitemap generation across all projects
• Create configuration templates by site type
• Ensure GDPR/CCPA compliance (no client data uploads)
• Integrate into deployment workflow: generate sitemap before pushing to production

Professional workflow: Create a "/sitemaps" folder in your project repository, generate the sitemap locally with RankBox, commit to version control, and deploy alongside code. This ensures traceability and versioning of the sitemap.

Follow these guidelines based on Google's official documentation and 11+ years of hands-on experience:

1. Include Only Canonical URLs (200 OK)

• ✅ URLs returning status 200
• ✅ Canonical version of each page (no session parameters)
• ✅ HTTPS URLs (if site uses SSL)

• ❌ Redirects (301/302)—Google already knows the destination
• ❌ 404 or 410 pages—wastes crawl budget
• ❌ Pages with noindex—contradictory to include in sitemap
• ❌ Duplicate URLs (with/without www, http/https)

2. Keep lastmod Accurate & Consistent

• ✅ Update lastmod only when content changes significantly
• ✅ Use ISO 8601 format (YYYY-MM-DD)
• ✅ Sync with actual modification date on server

• ❌ Update lastmod for all pages every time you generate sitemap
• ❌ Use random or inconsistent dates
• ❌ Omit lastmod entirely (misses opportunity to signal updates)

3. Split Large Sitemaps (>50k URLs)

• ✅ Create multiple sitemaps by content type:
• sitemap-posts.xml (blog)
• sitemap-products.xml (e-commerce)
• sitemap-categories.xml (categories)
• sitemap-pages.xml (institutional pages)
• ✅ Reference all in a sitemap index:

<?xml version="1.0" encoding="UTF-8"?> <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <sitemap> <loc>https://yoursite.com/sitemap-posts.xml</loc> <lastmod>2026-05-16</lastmod> </sitemap> <sitemap> <loc>https://yoursite.com/sitemap-products.xml</loc> <lastmod>2026-05-16</lastmod> </sitemap> </sitemapindex>

• Up to 50,000 URLs per sitemap file
• Up to 50MB uncompressed per file
• Up to 500 sitemaps in one sitemap index

4. Reference in robots.txt & Submit to Search Console

• ✅ Add to robots.txt:

Sitemap: https://yoursite.com/sitemap.xml

• ✅ Submit in Google Search Console:
• Access GSC → Sitemaps
• Paste full sitemap URL
• Click "Submit"
• Monitor status and errors

• robots.txt: Ensures crawlers discover sitemap automatically
• Search Console: Allows monitoring errors, indexed URLs, and processing status

5. Monitor & Fix Errors Regularly

• "URLs excluded by user": Sitemap URLs with noindex or redirects
• "Crawl errors": URLs returning 404, 500, or timeout
• "Last read": If outdated (weeks ago), re-submit sitemap

• Fix URLs with errors
• Remove excluded pages from sitemap
• Regenerate and re-submit

Follow this step-by-step process to ensure your sitemap is processed correctly:

Step 1: Upload the File

Place sitemap.xml in your domain root:

https://yoursite.com/sitemap.xml

Test: Access the URL directly in browser. You should see formatted XML (or download starts).

Step 2: Reference in robots.txt

Add this line to your robots.txt (in domain root):

Sitemap: https://yoursite.com/sitemap.xml

Verify: Access https://yoursite.com/robots.txt and confirm the line is present.

Step 3: Submit in Google Search Console

1. Access Google Search Console 2. Select the correct property (domain) 3. In sidebar, click "Sitemaps" 4. In "Add a new sitemap" field, paste full URL: sitemap.xml or https://yoursite.com/sitemap.xml 5. Click "Submit"

Initial status: "Pending"—Google hasn't processed it yet.

Step 4: Wait for Processing

• "Last read": Date/time of last processing
• "Indexed URLs": How many sitemap URLs were actually indexed
• "Status": Should be "Success" (green)

Step 5: Monitor Errors & Fix

• URLs with crawl errors (404, 500, timeout)
• Redirects (301/302)
• Canonical issues (duplicate URLs)

• Fix problematic URLs on site
• Regenerate sitemap with valid URLs
• Re-submit in GSC

Step 6: Update When Needed

• Add new pages
• Significantly modify existing content
• Remove pages (return 404)

• Regenerate sitemap
• Upload new file (replace old one)
• Re-submit in GSC (optional, but accelerates re-crawling)

❌ "Sitemap could not be read"

Possible causes: 1. File not in domain root 2. Incorrect URL in GSC 3. Blocked in robots.txt (Disallow: /sitemap.xml) 4. XML syntax error 5. Server returns 500 or 403 error

• ✅ Verify file is accessible at https://yoursite.com/sitemap.xml
• ✅ Test XML in online validator (e.g., xml-sitemaps.com/validator)
• ✅ Check file permissions (should be 644)
• ✅ Confirm no block in robots.txt
• ✅ Re-submit in GSC with correct URL

⚠️ "URLs excluded by user"

• Have <meta name="robots" content="noindex"> tag
• Redirect (301/302) to another URL
• Return 404 or 410 error
• Are blocked in robots.txt

• Review sitemap and remove URLs with noindex
• Replace redirecting URLs with final destination (301 target)
• Remove URLs that no longer exist (404)
• Unblock URLs in robots.txt if you want them indexed

🔄 "Last read: weeks ago"

• Low domain authority
• Limited crawl budget
• Sitemap not referenced in robots.txt
• Too many invalid URLs in sitemap (Google "gives up" reading)

• Re-submit sitemap in GSC
• Verify it's in robots.txt
• Remove invalid URLs (404, noindex, redirects)
• Improve domain authority with quality backlinks
• Reduce URL count if very large (>10k)

📉 "Indexed URLs < Submitted URLs"

• Content quality
• Relevance and search intent
• Crawl budget (limit of pages crawled per day)
• Page authority (backlinks, traffic)
• Duplicate or thin content

• Focus on including only valuable pages (exclude tags, archives, filters)
• Improve content quality of non-indexed pages
• Build backlinks to important pages
• Check for accidental robots.txt blocks
• Use "Inspect URL" tool in GSC to diagnose specific pages

For complex sites, these strategies elevate your indexation strategy:

Sitemap Index for Large Sites

For sites with >50,000 URLs, create multiple sitemaps and reference them in a sitemap index:

Recommended structure:

/sitemap-index.xml (main file) /sitemap-posts.xml (blog posts) /sitemap-products.xml (products) /sitemap-categories.xml (categories) /sitemap-pages.xml (institutional pages)

• Separate monitoring by content type in GSC
• Selective updates (only regenerate changed sitemap)
• Better organization and maintenance
• Scalability (up to 500 sitemaps in index)

Hreflang in Sitemap for Multilingual Sites

For sites with multiple language versions, add hreflang tags in the sitemap:

Example:

<url> <loc>https://yoursite.com/product</loc> <xhtml:link rel="alternate" hreflang="en" href="https://yoursite.com/product" /> <xhtml:link rel="alternate" hreflang="es" href="https://yoursite.com/es/producto" /> <xhtml:link rel="alternate" hreflang="fr" href="https://yoursite.com/fr/produit" /> </url>

• Cleaner than adding hreflang to every HTML page
• Centralized and easy to maintain
• Helps Google understand relationship between language versions

Note: Requires additional namespace in XML:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">

Specialized Sitemaps by Content Type

Separate sitemaps to simplify monitoring and updates:

• sitemap-news.xml: Only posts published in last 48h (for Google News)
• sitemap-images.xml: Pages with important images (for Google Images)
• sitemap-videos.xml: Pages with video (for Google Videos)
• sitemap-main.xml: All other pages

Advantage: Selective updates—only regenerate news sitemap with each new publication, keep others static.

Do I need a sitemap if my site has fewer than 100 pages?

For small sites with good internal linking, a sitemap is optional—Google usually crawls everything organically. But generating and submitting a sitemap has no cost and ensures no important page is missed. We recommend doing it as precaution, especially if the site is new (<6 months).

How often should I update my sitemap?

Whenever you add new pages or significantly modify existing content. For blogs publishing daily, generate with each new post. For static institutional sites, updating monthly is sufficient. lastmod should only change when the page actually changed.

What's the URL limit for a sitemap?

Google supports up to 50,000 URLs per sitemap file, with maximum size of 50MB (uncompressed). For larger sites, create multiple sitemaps and reference them in a sitemap index—an XML file listing other sitemaps. GSC accepts up to 500 sitemaps per index.

Does a sitemap directly improve Google rankings?

No. A sitemap is a discovery and indexation tool, not a ranking factor. It helps Google find your pages, but doesn't influence result positions. What improves rankings is content quality, authority, user experience, and other on-page and off-page SEO factors.

Can I have more than one sitemap for the same domain?

Yes, and it's recommended for large sites. You can have a main sitemap and specific ones—for example, one for blog posts, one for product pages, one for images. All should be referenced in robots.txt and submitted in Google Search Console.

How do I remove a URL from the sitemap?

Simply delete the URL from sitemap.xml, regenerate the file, and re-submit in Google Search Console. Google will remove the reference on next read. If the page was deleted from site, ensure it returns 404 or 410 to avoid unnecessary crawling.

Does sitemap work for subdomains?

Yes, but each subdomain (blog.yoursite.com) is treated as a separate domain by Google. You need to generate and submit a specific sitemap for each subdomain in the corresponding Google Search Console property.

How do I validate my sitemap before submitting?

• ✅ XML is well-formed (correct syntax)
• ✅ All URLs are accessible (200 OK)
• ✅ Namespaces are declared correctly
• ✅ No duplicate URLs
• ✅ lastmod is in ISO 8601 format (YYYY-MM-DD)

Should I include changefreq and priority in sitemap?

Google officially states it ignores these fields. Including them doesn't hurt, but provides no measurable SEO benefit. If you want to keep them for compatibility with other search engines (Bing, Yandex), you can include them. Otherwise, focus only on loc and lastmod.

What's the difference between XML sitemap and robots.txt?

• robots.txt: Tells crawlers what not to crawl (blocking)
• sitemap.xml: Tells crawlers what should be crawled (discovery)

Use both: robots.txt to block admin pages, tests, or private content; sitemap.xml to ensure indexation of important content.

Can I compress sitemap with GZIP?

Yes! Google accepts sitemaps compressed with GZIP (extension .xml.gz). This is useful for large sitemaps (>10MB), reducing download time and bandwidth usage. Just ensure your server sends the correct HTTP header (Content-Encoding: gzip).

How do I generate sitemap automatically in WordPress?

Plugins like Yoast SEO, Rank Math, and All in One SEO generate sitemaps automatically. However, if you prefer full control or have a static site, use RankBox to generate manually and upload via FTP. RankBox advantage: local processing, no plugin dependency, and total privacy.

Sitemap creation is fundamental for technical SEO, but it's part of a larger optimization ecosystem. Explore other free tools we've built:

• Page Optimizer: Preview and optimize how your site appears in Google with real-time title and meta description simulation.
• Word Counter: Analyze keyword density, reading time, and text structure for your content.
• Image Converter: Convert images between JPG, PNG, and WebP with client-side processing—zero uploads to servers.
• Redirect Checker: Identify redirect chains that waste crawl budget and slow down your site.

About RankBox: An independent project built by SEO practitioners with 11+ years of hands-on experience. Our tools are 100% free, processed locally in your browser, and focused on privacy. No sign-ups. No server uploads. No complications.