Developer SEO Utility

sitemap.xml Generator

Enter a list of site URLs to automatically generate a sitemap.xml file for search engine submission. You can copy the XML result or download it as a file.

Generate XML Sitemap Create a sitemap.xml file that helps search engines understand your site structure.
Ready for SEO Submission Use the generated sitemap for Google Search Console, Bing Webmaster Tools, and other search engine tools.
Copy and Download Copy the generated XML code or save it directly as a sitemap.xml file.
URL Count 0 URLs
Changefreq daily
Priority 0.8
Lastmod Enabled

Sitemap Settings

Enter your site address and URL list to generate a sitemap.xml file.

Recommended Structure

It is best to include only the representative URLs you want search engines to index. Admin pages, search result pages, duplicate URLs, and parameter URLs are usually better excluded.

Used to convert relative paths into absolute URLs. Example: https://win-j.com

An optional sitemap protocol field. Google ignores changefreq, so include it only when another target search engine needs it.

An optional sitemap protocol field. Google ignores priority, and it does not directly affect search ranking.

Enter one URL per line. Both relative paths and absolute URLs are supported.

XML Items to Include

Choose which sitemap attributes to include. If you only need a simple URL list, you can disable optional fields.

Generated Result

Save the XML below as sitemap.xml and upload it to the root path of your site.

Ready
Enter your settings and click the Generate sitemap.xml button.
Practical guide

Generating a sitemap from final, public URLs

Convert a URL list into XML, resolving relative paths and removing duplicates. Select canonical, indexable pages before generating the file; the tool cannot verify their live status.

Who this helps

  • Owners of small or static sites
  • Developers preparing an XML sitemap

When to use this tool

  • Convert a reviewed list of public paths to XML.
  • Generate a sitemap without inventing last-modified dates.

From input to a checked result

  1. 1

    Prepare the final canonical URLs that should be discoverable.

  2. 2

    Enter an HTTP(S) base address if the list contains relative paths.

  3. 3

    Paste one URL per line and resolve invalid or mixed-origin entries.

  4. 4

    Leave lastmod off unless every listed page was meaningfully modified on the generated UTC date.

  5. 5

    Generate and inspect the XML, then download or copy it.

  6. 6

    Check the live file and submit it through the relevant search engine tools.

Example 1

Relative paths and duplicates

Input
Base https://example.com; /about/; /tools/; /about/
Result
Two absolute loc entries

Duplicate normalized URLs are removed. Root-relative paths start at the origin.

Example 2

A foreign URL mixed into the list

Input
Base https://example.com; /about/; https://other.example/page/
Result
A mixed-origin validation error

This generator requires one protocol, host and port, including the entered base address.

How it works

The URL parser resolves paths against the base address with a trailing slash, normalizes absolute URLs and deduplicates them. Malformed URLs, non-HTTP(S) schemes and credentials are rejected. The generator supports up to 50,000 URLs and escapes XML characters.

Limitations

  • HTTP status, canonical, robots and noindex are not fetched.
  • The uncompressed 50 MB file-size limit is not measured by this tool.
  • Optional lastmod applies the same current UTC date to every URL.
  • Google does not use the optional changefreq or priority values.
Your data

The URL list is processed locally. Exclude private addresses and secret query parameters from a public sitemap.

Related tools

Frequently asked questions

Does a sitemap guarantee indexing?

No. It supplies discovery information; eligibility and indexing are separate.

Should I enable lastmod for old posts?

Only when the generated date is their actual meaningful modification date. Otherwise leave it off.

What happens to /about/ when the base includes /blog/?

A leading slash resolves from the origin. A path without a leading slash resolves under the base directory.