Sitemap generator

Paste your URLs; get a valid XML sitemap. No crawler to wait on, no page-count limit, nothing to install. Copy it, save it as sitemap.xml, and submit it to Search Console.

Generated Sitemap

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
</urlset>

Sitemap Best Practices

  • •Save as sitemap.xml in your root directory
  • •Submit to Google Search Console and Bing Webmaster Tools
  • •Update regularly when adding new pages
  • •Include in your robots.txt file

WHAT IS AN XML SITEMAP GENERATOR?

An XML sitemap generator turns a list of page URLs into the structured file search engines use as a reading list for your site. You supply the addresses. The tool wraps each one in the <url> and <loc> tags the sitemap protocol requires, adds the namespace declaration at the top, and hands you a file that validates.

Writing one by hand is possible. It's also miserable after about the twelfth page, and a single unescaped ampersand will invalidate the whole thing.

Here's what a sitemap does and doesn't do, because this trips people up constantly.

It does help discovery. Search engines find most pages by following links, and that works well for a well-linked site. It works badly for pages nobody links to a new post before it's promoted, a landing page reached only from paid ads, a deep product variant six clicks from the homepage. A sitemap gives those pages a direct route in.

It doesn't guarantee indexing. Google treats a sitemap as a suggestion, not an instruction. Thin or duplicate pages listed in a sitemap still get ignored. You'll see this in Search Console as "Discovered, currently not indexed," and adding the URL to a sitemap a second time won't change it.

It doesn't improve rankings either. A sitemap helps a page get found. What happens after that is down to the page.

The sitemap protocol sets two hard limits: 50,000 URLs and 50 MB uncompressed per file. Larger sites split their URLs across multiple sitemaps and list those files in a sitemap index. Most sites never come close.

One more thing worth knowing. Of the four fields the protocol allows, Google only pays attention to <loc> and <lastmod>, and it only trusts lastmod if your dates have proven accurate over time. changefreq and priority are ignored outright. Plenty of SEO guides still treat them as meaningful. They aren't, at least not for Google.

HOW TO USE THE SITEMAP GENERATOR

Step 1 — Enter your domain. Full URL with https://. Whatever you enter becomes the base for any relative paths below.

Step 2 — Paste your URLs, one per line. Full URLs or relative paths, your choice. If you're pulling from a CMS export or a crawl report, paste the whole column — duplicates and blank lines get cleaned up automatically.

Step 3 — Cut what shouldn't be there. Before you generate, strip out: tag and category archives with nothing on them, paginated series pages, internal search results, thank-you pages, anything set to noindex, and any URL that redirects. A sitemap of 200 genuinely useful pages beats one with 2,000 pages of filler.

Step 4 — Decide on lastmod. If your CMS tracks real modification dates, use them. If you'd be entering today's date across the board for pages you haven't touched in a year, leave the field blank. An inaccurate lastmod is worse than none, because Google learns to distrust it.

Step 5 — Generate and check the summary. Look at the URL count and the validation messages. If the tool flagged skipped lines, it's usually a typo or a missing protocol.

Step 6 — Save it as sitemap.xml. Exactly that filename, all lowercase. Upload it to your root directory.

Step 7 — Point robots.txt at it. Add Sitemap: https://yourwebsite.com/sitemap.xml on its own line. Position doesn't matter.

Step 8 — Submit it. Google Search Console → Sitemaps → paste the URL → Submit. Same idea in Bing Webmaster Tools. Come back in a few days and read the coverage report, which is where the useful information lives: how many URLs were submitted, how many were indexed, and why the rest weren't.

SITEMAP GENERATOR EXAMPLES

Example 1 — A small business site

Nine pages, no blog, nothing complicated. This is the most common case by a wide margin.

Input

Domain: https://hillcrestroofing.com

/

/roof-repair

/roof-replacement

/gutter-installation

/storm-damage

/service-areas

/about

/reviews

/contact

Output

<?xml version="1.0" encoding="UTF-8"?>

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

  <url>

    <loc>https://hillcrestroofing.com/</loc>

  </url>

  <url>

    <loc>https://hillcrestroofing.com/roof-repair</loc>

  </url>

  <url>

    <loc>https://hillcrestroofing.com/roof-replacement</loc>

  </url>

  <!-- remaining six URLs follow the same pattern -->

</urlset>

No lastmod here, and that's deliberate. A nine-page brochure site rarely changes, and fabricating dates would only teach Google to ignore the field.

KEY FEATURES AND CAPABILITIES

No crawl, no waiting. Crawler-based generators queue your site and email you a link twenty minutes later. This one runs the moment you paste.

No page limit: Free sitemap tools usually cap you at 500 URLs. There's no cap here, and files over 50,000 URLs get split with an index automatically.

Valid XML, properly escaped Namespace declaration, UTF-8 encoding, escaped reserved characters. It passes validation without edits.

Automatic cleanup: Duplicates removed, whitespace trimmed, malformed lines flagged rather than silently included.

Optional lastmod, changefreq and priority: Available if your workflow needs them, off by default, with honest notes about which ones search engines actually read.

Sitemap index for large sites: Splitting and index generation handled for you.

Runs in your browser: Client-side, so your URL list never leaves your machine. Useful when you're working on a client site under NDA.

Free, no account: No signup, no email capture, no credit limit.

FAQ:

Where do I put the sitemap file?

In your root directory, so it's reachable at yourwebsite.com/sitemap.xml. It can technically live elsewhere, but a sitemap can only list URLs from the directory it sits in or below, so the root is simplest.

Do I have to name it sitemap.xml?

 No, any filename works as long as you tell search engines where it is through robots.txt or Search Console. sitemap.xml is the convention, and crawlers check for it by default, so there's rarely a reason to use anything else

How often should I update it?

Whenever the set of pages changes. Adding a post, retiring a product, restructuring a section: regenerate and re-upload. If you publish daily, automating it through your CMS is a better long-term answer than doing it by hand.

My sitemap is submitted, but pages still aren't indexed. Why?

A sitemap gets pages discovered. It doesn't get them indexed. If Search Console shows "Discovered, currently not indexed," the issue is usually thin content, near-duplicate pages, weak internal linking, or a crawl budget stretched across too many low-value URLs. Adding the URL again won't fix any of those.

Does a sitemap help my rankings?

 Not directly. It improves the odds of a page being found and crawled, which is a prerequisite for ranking but not a ranking factor itself.

Related tools:

Try Hreflang Tag Generator by Rext AI for sites serving multiple languages or regions.

Try Content Outline Generator by Rext AI to plan the pages before you list them with Rext AI content outline generator.