Build a valid XML sitemap from a URL list. Validate 1200 URLs with weekly changefreq and 0.8 priority, free offline, no signup.
Part of our SEO & Marketing collection — Explore more SEO & Marketing tools · See also: Robots.txt Generator, SERP & Open Graph Preview.
Quick answer: Sitemap Generator — XML sitemap builder Free, no signup, runs in your browser. See below for the interactive tool, 4-step guide and FAQs.
0 valid • 0 invalid
Optional
Deep dives from the Tool4SaaS blog — tested workflows, print sizes and fixes.
Reviewed by the Tool4SaaS Editorial Team — In-house reviewers who build and test every tool locally for accuracy across current Chrome, Edge, Firefox, and Safari. Last updated: . See our authors, methodology or contact us.
Only absolute https URLs qualify, one per line, validated through URL parsing. For instance, 1,200 product links such as https://example.com/shoes/red pass cleanly, while relative /blog slugs trigger warnings. Strip tracking parameters, unify trailing slashes, correct percent encoding, then export UTF-8 XML ready for Search Console submission.
No. Assembly happens completely in your browser, so 1,200 pasted addresses never travel outward. Processing continues after initial load without accounts, generates UTF-8 urlset instantly, and disappears when you close the tab. Download the file directly for site root deployment.
Output follows Google urlset schema with loc, lastmod, changefreq and priority per entry. Capacity caps at 50,000 addresses or 50MB uncompressed; a 120,000-item catalog therefore needs three splits. Assign weekly to blogs, monthly to evergreen guides, 0.8 to bestsellers, 0.3 to thin archives.
Choose weekly for frequently refreshed inventory, editorial blogs, or price-sensitive listings where crawlers benefit from rapid revisits. Select monthly for stable documentation, about pages, or evergreen tutorials that rarely shift. Daily suits news homepages, yearly fits archived legal notices. Align frequency with genuine modification cadence rather than wishful crawling.
Rejections usually stem from relative paths, 404 targets, blocked robots rules, or incorrect content type instead of XML. Verify every loc returns 200, permits crawling, uses absolute https, and stays under size thresholds. Resubmit after correcting encoding errors, removing session IDs, and confirming the Sitemap directive placement.
Build a clean XML sitemap from a pasted URL list without server roundtrips, ideal for shops, blogs, and documentation hubs launching fresh sections. Paste one absolute https address per line, for example 1,200 product links including https://example.com/shoes/red and https://example.com/shoes/blue, then assign weekly changefreq, 0.8 priority and today lastmod. Validation flags relative /blog paths, missing schemes, spaces, and duplicate slashes instantly. Reference table guides priorities: homepage daily 1.0 https://example.com/ | flagship product weekly 0.8 https://example.com/shoes/red | tutorial blog weekly 0.6 https://example.com/blog/lacing-guide | help article monthly 0.4 https://example.com/help/returns | legal archive yearly 0.3 https://example.com/legal/terms. Example one converts a 1,200-row launch list into UTF-8 urlset in seconds, ready for domain root upload. Edge handling trims blank lines and normalizes percent encoding automatically before export.
Output adheres to Google urlset schema where each url entry carries loc, lastmod, changefreq and priority, serialized as UTF-8 XML for crawler consumption. Use daily for news homepages, weekly for evolving catalogs, monthly for stable tutorials, yearly for legal archives; match stated cadence to actual modification history to preserve trust. Assign 0.8 to 1.0 for revenue drivers, 0.5 to 0.6 for supporting blogs, 0.3 to 0.4 for thin tag filters. Example two upgrades a 3,500-post magazine: homepage daily 1.0, fresh reviews weekly 0.7, evergreen guides monthly 0.5, author archives monthly 0.3, keeping total under 50,000 URLs and 50MB raw. Splitting a 120,000-address marketplace into three files prevents truncation. Edge behavior rejects non-http schemes like ftp, highlights double-encoded ampersands, and preserves query strings only when canonical.
Paste 1,200 https URLs one per line, select weekly changefreq, 0.8 priority and today lastmod, then correct flagged relative paths before downloading sitemap.xml for domain root deployment. Upload to https://example.com/sitemap.xml, confirm 200 status with XML content type, then submit via Search Console for discovery. Limitations include inability to auto-crawl sites, detect orphan pages, guarantee indexing, or bypass 50,000 URL and 50MB ceilings; very large estates still require index sitemaps and manual audits. Dynamic parameters and session IDs should be canonicalized beforehand to avoid duplication. For crawler Allow and Disallow control and Sitemap directive placement, continue with our robots file builder at /robots-txt-generator to complete discovery setup efficiently. A second validation pass catches double slashes, trailing spaces and mixed http variants before final export preparation.