An XML sitemap generator turns a plain list of your page URLs into the structured XML file search engines use to discover and understand your site. This free tool takes URLs pasted one per line, applies the change frequency, priority, and last-modified date you choose, and outputs a valid sitemap.xml file you can copy and upload in under a minute β no plugins, no command line, no account required.
Arb Digital builds and audits sitemaps as a standard part of every technical SEO engagement, and the most common issue we find isn't a missing sitemap β it's a stale or dishonest one: URLs that 404, lastmod dates that never change, or thousands of low-value pages diluting the URLs that actually matter. This generator is deliberately simple so you stay in control of exactly what goes in.
What This XML Sitemap Generator Does
You paste your URLs into the text box, choose a default change frequency and priority that will apply to every URL, pick a last-modified date, and the tool builds a complete <urlset> document β each URL wrapped in a <url> element containing <loc>, <lastmod>, <changefreq>, and <priority> tags, formatted exactly to the sitemaps.org protocol that Google, Bing, and every other major search engine reads. Invalid or blank lines are automatically skipped and reported so you know exactly what made it into the final file.
How to Use It
- Gather your URLs. Pull them from your CMS, a crawl export, or your site's navigation. Use full absolute URLs, including
https://. - Paste one URL per line into the text box. There's no practical limit for this tool, though sitemap files themselves cap at 50,000 URLs.
- Set your defaults. Choose a change frequency and priority that apply to the whole batch, and pick a last-modified date.
- Generate and review. Check the URL count and confirm nothing was skipped as invalid.
- Copy, upload, and submit. Save the output as
sitemap.xmlat your domain root, add aSitemap:line to robots.txt, and submit the URL in Google Search Console.
The Sitemap XML Format, Explained
A sitemap is just XML β a structured, machine-readable list. The outer <urlset> tag declares the sitemap namespace, and each page gets its own <url> block. Inside that block, <loc> is the only required field β the full, absolute URL of the page. The other three fields are optional metadata: <lastmod> (when the page last changed), <changefreq> (how often it's expected to change), and <priority> (a 0.0β1.0 relative importance score compared to other URLs on your own site). This structure is unchanged since the protocol's introduction and remains the reference every generator, including this one, builds against.
A Sitemap Is a Suggestion, Not a Command
This is the single most important thing to understand about sitemaps, and it's frequently misunderstood: submitting a URL in a sitemap does not force Google to crawl it, index it, or rank it. A sitemap is a hint β a list of URLs you're telling search engines about and, implicitly, vouching for as worth crawling. Google's own sitemap documentation is explicit that inclusion in a sitemap is not a guarantee of indexing.
Where sitemaps genuinely help: large sites with tens of thousands of pages, brand-new sites with few external links pointing in yet, sites with pages buried deep in the navigation that internal linking doesn't surface well, and sites that publish content frequently and want fast discovery of new URLs. Where a sitemap does almost nothing: a small site of a few dozen pages that's already well linked internally and externally. Google will find and crawl those pages through normal link-following regardless of whether a sitemap exists. Build one anyway for the other benefits, but don't expect a sitemap alone to fix an indexing problem rooted in content quality or site structure.
Priority and Changefreq Are Mostly Ignored Now
Years ago, <priority> and <changefreq> were treated as meaningful signals. Today, Google has stated plainly that it largely ignores both fields β setting every URL to priority 1.0 doesn't make Google crawl your site more, and an inflated changefreq of "hourly" on a page that changes once a year won't fool the crawler into visiting more often; if anything, a pattern of dishonest changefreq values can quietly erode how much Google trusts the rest of the file. Include them because the protocol allows it and some other search engines still read them, but don't treat them as a lever for ranking or crawl priority.
The one field that still carries real weight is <lastmod> β but only when it's accurate. Google has said it will use lastmod to help decide whether a page needs to be recrawled, but only if the dates in your sitemap consistently correspond to real content changes. A sitemap where every URL shows today's date regardless of whether the page changed trains Google to distrust the field entirely, which defeats its purpose. Set lastmod honestly, and update it only when content on that specific page actually changes.
Sitemap Limits and Sitemap Index Files
Per the sitemaps.org protocol, a single sitemap file is capped at 50,000 URLs and 50MB uncompressed. If your site has more URLs than that, split them into multiple sitemap files β often organized by content type, such as sitemap-posts.xml, sitemap-products.xml, and sitemap-pages.xml β and reference all of them from one master sitemap_index.xml file that points to each child sitemap. This tool generates a single flat sitemap; for sites well under 50,000 URLs it's exactly what you need, and for larger sites you can run separate batches through it and hand-assemble the index file, or ask your development or SEO team to automate index generation directly from your CMS.
Submitting Your Sitemap
Once your sitemap.xml is live at its final URL, do two things. First, add a line to your robots.txt file: Sitemap: https://www.example.com/sitemap.xml β this lets every crawler that reads robots.txt discover the sitemap automatically, even ones you never manually submit to. Second, log into Google Search Console, go to the Sitemaps report, and submit the sitemap URL directly β this is still the most reliable way to get Google's attention on a new or updated sitemap and to monitor how many submitted URLs actually get indexed versus excluded.
After submission, watch the "Discovered vs. Indexed" numbers in that report over the following days. A healthy sitemap usually sees the majority of its URLs move to "Indexed" within a couple of weeks, assuming the content itself is unique and useful. If a large share sit in "Discovered β currently not indexed" or "Crawled β currently not indexed" for a long stretch, that's a signal worth investigating β it usually points to thin content, duplicate pages competing with each other, or a crawl budget problem on a very large site, rather than anything wrong with the sitemap file itself.
Sitemaps for Different Content Types
Not every URL belongs in the same sitemap, and larger sites benefit from separating them by type even before hitting the 50,000-URL limit. A common structure splits sitemaps into pages, blog posts, and products (if you run an ecommerce catalog), each with its own realistic changefreq default β a static "About Us" page might reasonably be "yearly," while a product page with fluctuating stock and pricing is closer to "weekly" or "daily." This tool applies one changefreq and priority to a whole batch at a time, so for a mixed site the practical workflow is running separate batches through it β one for static pages, one for blog content, one for products β and combining the outputs, or assembling them into a proper sitemap index file if the total volume justifies it.
Image and video sitemaps are a separate, optional extension of the same protocol that adds <image:image> or <video:video> tags inside each <url> block, helping those specific assets get discovered through Google Images and Video search. Most sites don't need this extension unless visual or video content is a meaningful traffic channel, but it's worth knowing it exists as a separate layer on top of the standard sitemap this tool generates.
Sitemaps and Canonical Tags Must Agree
One inconsistency that quietly undermines a lot of otherwise well-built sitemaps: listing a URL in the sitemap while that same page's <link rel="canonical"> tag points to a different URL. That mismatch tells Google two contradictory things at once β "this URL matters, I'm listing it" via the sitemap, and "this URL is not the authoritative version, defer to another one" via the canonical tag. Google generally trusts the canonical tag over sitemap inclusion when they conflict, so the practical effect is that the sitemap listing gets ignored anyway, but the contradiction still adds noise that can slow down how much Google trusts the rest of your sitemap. Before generating a sitemap for a site with any URL parameters, filters, or pagination, spot-check a sample of the URLs you're about to include and confirm their canonical tags point to themselves, not somewhere else.
A correct sitemap is a small piece of the puzzle. Arb Digital audits crawlability, indexation, site architecture, and Core Web Vitals as part of every SEO engagement.
See Our SEO Services All Free ToolsCommon Mistakes to Avoid
- Including non-canonical or redirected URLs. Only list the final, canonical, 200-status URL for each page β never a URL that redirects or duplicates another page.
- Listing noindex pages. A URL that's tagged noindex has no business in a sitemap; the two signals contradict each other and waste crawl attention.
- Letting the sitemap go stale. A sitemap full of deleted or moved pages teaches Google that your sitemap isn't trustworthy, which can reduce how much attention future updates get.
- Setting every priority to 1.0. It has no measurable effect and just adds noise to the file.
- Forgetting to reference it in robots.txt. A single line saves you from relying purely on manual Search Console submission.
- Exceeding 50,000 URLs in one file. Split into multiple sitemap files plus a sitemap index instead of truncating your URL list.
Related Free Tools From Arb Digital
Reference your new sitemap correctly with the robots.txt generator. If you're cleaning up old or duplicate URLs before building your sitemap, the htaccess redirect generator handles 301s properly. Verify pages are actually indexed with the Google cache checker, check your on-page tags with the meta tag generator, add structured data with the schema markup generator, or browse our full free online tools hub.
Frequently Asked Questions
No. A sitemap is a suggestion, not a command. It tells search engines a URL exists and is worth considering, but indexing still depends on content quality, crawl budget, and whether the page is otherwise accessible and worth showing in results.
Very little today. Google has said it largely ignores both fields. Include them because the protocol supports them and some other engines still read them, but don't expect them to influence crawl frequency or rankings.
Probably, but the benefit is smaller than for large sites. A well-linked small site will usually get fully crawled without one. Sitemaps matter most for large sites, new sites with few inbound links, and sites with pages that are hard to find through normal navigation.
Up to 50,000 URLs and 50MB uncompressed per the sitemaps.org protocol. Larger sites split URLs across multiple sitemap files and list them all in a master sitemap index file.
No. Only include final, canonical, indexable URLs that return a 200 status. Redirected, noindexed, or duplicate URLs send contradictory signals and can reduce how much search engines trust the rest of the file.
Upload it to your domain root, add a Sitemap line to your robots.txt file so any crawler can find it automatically, and submit the URL directly in Google Search Console's Sitemaps report for the most reliable and trackable submission.
