Create an XML Sitemap Online
An XML sitemap helps search engines discover the important URLs on your website. This free XML Sitemap Generator creates a standards-based XML sitemap from the URLs you provide, with optional lastmod, changefreq, and priority fields.
Unlike a crawler-based generator, this tool does not attempt to crawl your website from the browser. You provide the URLs you want included, and the sitemap is generated locally in your browser.
XML Sitemap Generator
Create a clean, standards-based XML sitemap from your own URL list — privately in your browser, with no sign in, no account, no API and no server-side crawler.
What Is an XML Sitemap?
An XML sitemap is a structured XML file that lists URLs you want search engines to discover and consider for crawling. It can also provide additional information such as when a URL was last modified.
For Google, a sitemap is primarily a URL-discovery and crawling signal. It does not guarantee that a URL will be crawled, indexed, or rank in search results. Google for Developers
A typical XML sitemap uses the standard sitemap namespace:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
</url>
</urlset>
The sitemap protocol requires the XML document to use the standard <urlset> structure and include a <loc> element for each URL. Sitemap values must also be properly escaped and the file must use UTF-8 encoding. Sitemaps
Why Use an XML Sitemap?
A sitemap can be particularly useful when a website has many pages, recently added URLs, a complex structure, or pages that may be difficult for search engines to discover through internal links alone.
Google notes that sitemaps can be especially helpful for large or newer websites and sites with complex structures or specialized content. Google for Developers
A sitemap should complement your website rather than replace good technical SEO.
Your important pages should still be:
- Accessible to search engines
- Internally linked
- Canonicalized appropriately
- Not unintentionally blocked
- Useful and indexable
- Included in the sitemap when they are intended for search results
For a broader technical review, you can also use the XML Sitemap Analyzer to inspect an existing sitemap and the Indexability & Crawlability Analyzer to investigate crawl and indexing signals.
How to Create an XML Sitemap
1. Enter Your Website URL
Enter the main website address, such as:
https://example.com/
The tool uses this information to establish the expected website host.
2. Add Your Page URLs
Enter the absolute URLs you want to include, with one URL per line.
For example:
https://example.com/
https://example.com/about/
https://example.com/contact/
https://example.com/blog/
Google recommends using fully qualified absolute URLs rather than relative paths in sitemaps. Google for Developers
3. Choose Optional Sitemap Data
You can choose whether to include:
- Last modified date
- Change frequency
- Priority
The tool lets you control these fields rather than forcing them into every generated sitemap.
4. Generate the Sitemap
Select Generate Sitemap to create the XML document.
The tool processes the URL list in your browser, removes duplicate entries, checks the URL host, generates properly escaped XML, and validates the resulting XML structure before presenting the output.
5. Copy or Download the XML
Once the sitemap has been generated, you can copy the XML or download the sitemap file for use on your website.
What This XML Sitemap Generator Checks
The generator is designed to prevent several common sitemap construction problems before you save the file.
Duplicate URLs
Repeated URLs are removed so the generated sitemap contains a clean URL list.
Absolute URLs
The tool expects complete URLs rather than entries such as:
/about/
Instead, use:
https://example.com/about/
This follows Google’s recommendation for fully qualified sitemap URLs. Google for Developers
Host Consistency
The generator checks that URLs belong to the website host you specified. Sitemap protocols generally require URLs in a sitemap to belong to the same host, subject to the protocol’s cross-site submission rules. Sitemaps
XML Escaping
Characters that have special meaning in XML need to be escaped correctly. The generated sitemap handles XML escaping so URLs can be represented safely inside the XML document. Sitemaps
XML Structure
The generated document uses the standard sitemap XML namespace and validates the resulting XML structure in the browser.
XML Sitemap Size Limits
A single sitemap has important size limits.
| Limit | Maximum |
|---|---|
| URLs per sitemap | 50,000 |
| Uncompressed sitemap size | 50 MB |
| Encoding | UTF-8 |
These limits are defined by Google’s sitemap guidance and the Sitemap protocol. Google for Developers
If your website exceeds these limits, split the URLs across multiple sitemap files and use a sitemap index where appropriate. Google provides a separate sitemap-index workflow for larger URL inventories. Google for Developers
Should You Add lastmod, changefreq, and priority?
These fields are not equally useful.
lastmod
lastmod tells search engines when the corresponding URL was last modified.
It can be useful when the date is accurate and consistently maintained. Google says it can use reliable lastmod information when determining when pages were updated. Google for Developers
Do not add an invented date simply to populate the field.
changefreq
The sitemap protocol supports changefreq, but Google does not use this field for crawling. Google for Developers
It can still be included when another consumer of the sitemap expects the standard field, but it should not be treated as a Google ranking or crawling control.
priority
priority is also part of the sitemap protocol, but Google ignores it for crawling. Google for Developers
Changing a page’s priority to 1.0 does not make Google rank that page higher.
What This Tool Does Not Do
This tool is intentionally different from a server-based website crawler.
It does not automatically crawl every page of a website from the browser.
That distinction matters because a browser-based tool cannot reliably retrieve and inspect every arbitrary website. Cross-origin restrictions, robots policies, authentication, JavaScript rendering, server behavior, and other technical conditions can prevent a browser from accessing a complete site inventory.
Instead, this generator gives you direct control over the URLs that enter the sitemap.
That makes it useful when you already have a URL inventory from:
- A CMS
- A website export
- A spreadsheet
- A crawl
- A migration project
- A content inventory
- An existing sitemap
- A developer-generated URL list
If you already have an XML sitemap and want to inspect its contents, use the Sitemap URL Extractor or XML Sitemap Analyzer.
XML Sitemap vs Website Crawler
These tools solve different problems.
| Task | XML Sitemap Generator | Website Crawler |
|---|---|---|
| Create sitemap XML | Yes | Usually |
| Accept a prepared URL list | Yes | Not always |
| Automatically discover pages | No | Yes |
| Analyze existing sitemap | No | Sometimes |
Generate lastmod fields | Yes, optional | Depends on crawler |
| Browser-local generation | Yes | Depends on implementation |
| Requires crawling the website | No | Usually |
| Best for controlled URL inventories | Yes | Not necessarily |
If you already know which URLs belong in your sitemap, generating the XML directly can be simpler than running a full crawl.
Which URLs Should Go in a Sitemap?
Do not treat your sitemap as a list of every URL your website can technically produce.
A better approach is to include the URLs you want search engines to consider for search results.
Google recommends including the canonical URLs you want to appear in Search. Google for Developers
Before adding a URL, ask:
- Is this an important page?
- Is the page publicly accessible?
- Is this the preferred canonical URL?
- Do I want this URL considered for search?
- Is the URL returning the correct page?
- Is it unnecessarily duplicated by another URL?
- Is the URL blocked or excluded from indexing?
A sitemap cannot compensate for poor URL architecture.
Common XML Sitemap Mistakes
Using Relative URLs
Incorrect:
/products/
Better:
https://example.com/products/
Google specifically recommends fully qualified absolute URLs. Google for Developers
Adding URLs You Do Not Want in Search
A sitemap should not become a dumping ground for every URL generated by your website.
Avoid including URLs that you deliberately do not want search engines to consider.
Assuming a Sitemap Guarantees Indexing
A sitemap is a discovery signal, not an indexing guarantee.
Google explicitly states that submitting a sitemap does not guarantee that Google will crawl or index the URLs inside it. Google for Developers
Using Fake lastmod Dates
Do not update every lastmod value simply because you regenerated the sitemap.
Use dates that genuinely represent meaningful page changes.
Treating priority as a Ranking Factor
Google ignores the priority and changefreq sitemap fields. They should not be used as a substitute for content quality, internal linking, canonicalization, or other SEO fundamentals. Google for Developers
Forgetting Sitemap Maintenance
A sitemap can become outdated as your website changes.
Review it after:
- Website migrations
- URL restructuring
- Large content updates
- New sections
- Content removals
- Major CMS changes
- Domain changes
Where Should You Put Your Sitemap?
Google recommends placing a sitemap at the site root when practical, for example:
https://example.com/sitemap.xml
A sitemap can also be hosted elsewhere within the site hierarchy, but its location can affect which URLs it covers unless it is submitted through Search Console. Google for Developers
After uploading the file, you can make the sitemap discoverable through Google Search Console or reference it from your robots.txt file.
For example:
Sitemap: https://example.com/sitemap.xml
Google supports sitemap submission through Search Console and sitemap declarations in robots.txt. Google for Developers
XML Sitemap and Internal Linking Work Together
A sitemap should not be used as a replacement for internal links.
Google can discover URLs through links as well as sitemaps. A strong website architecture makes important pages reachable through normal crawlable links, while the sitemap provides an additional URL-discovery signal. Google for Developers
For technical SEO, it is useful to review the sitemap alongside your Robots.txt Analyzer and Canonical URL Checker.
This helps you investigate whether important URLs are:
- Discoverable
- Crawlable
- Canonicalized correctly
- Included in the sitemap
- Internally linked
- Intended for indexing
A Practical Sitemap Workflow
For a controlled website sitemap, use this workflow:
Build URL inventory → Remove unwanted URLs → Confirm canonical URLs → Generate XML → Validate → Upload → Submit → Monitor
Step 1: Build the URL Inventory
Collect the important URLs from your CMS, website database, existing sitemap, crawler, spreadsheet, or migration inventory.
Step 2: Clean the List
Remove:
- Duplicate URLs
- Unwanted parameters
- Test pages
- Temporary URLs
- URLs you do not want indexed
- Incorrect hostnames
- Obsolete URLs
Step 3: Confirm Canonicals
Make sure the URL you are adding represents the preferred version of the page.
Step 4: Generate the XML
Paste the final URL inventory into the XML Sitemap Generator and create the sitemap.
Step 5: Validate the Output
Review the generated URL count, duplicate count, file size, and validation status before downloading the file.
Step 6: Publish the Sitemap
Upload the generated XML file to your website in the appropriate location.
Step 7: Submit or Reference It
Submit the sitemap through Google Search Console or reference it through robots.txt.
Step 8: Monitor the Sitemap
After publication, review sitemap processing and investigate unexpected errors or URL changes in your technical SEO workflow.
Privacy and Browser Processing
The XML Sitemap Generator is designed for browser-based sitemap creation.
Your URL list is processed by the tool in your browser rather than being sent to a PKCapra sitemap-generation API.
This is useful when you want to prepare a sitemap without creating an account or sending your URL inventory to a separate sitemap-generation service.
However, the tool does not replace your responsibility for checking the URLs before publication. A technically valid XML sitemap can still contain URLs that are unsuitable for indexing.
Frequently Asked Questions
What is an XML Sitemap Generator?
An XML Sitemap Generator creates a properly structured XML sitemap from a list of website URLs. The resulting file can then be published and submitted to search engines.
Is this XML Sitemap Generator free?
Yes. The PKCapra XML Sitemap Generator is designed as a free browser-based utility for creating sitemap XML from a prepared URL list.
Does the tool crawl my entire website?
No. It does not automatically crawl arbitrary websites. You provide the URLs you want included.
Can I create a sitemap without coding?
Yes. Enter your website URL and page URLs, select the optional sitemap fields you need, generate the XML, then copy or download the result.
How many URLs can an XML sitemap contain?
A single sitemap can contain up to 50,000 URLs and cannot exceed 50 MB uncompressed. Larger URL inventories should be split into multiple sitemap files. Google for Developers
Does Google require an XML sitemap?
No. Google can often discover well-linked pages without a sitemap. Sitemaps become more useful as websites become larger, newer, more complex, or harder to discover through internal links. Google for Developers
Does an XML sitemap improve rankings?
A sitemap is not a direct ranking boost. It helps search engines discover URLs and provides information about the URLs you want considered for crawling. Google does not guarantee crawling, indexing, or ranking from sitemap submission. Google for Developers
Should I use lastmod?
Use lastmod when you can provide an accurate modification date. Reliable modification information can help search engines understand when a URL has meaningfully changed. Google for Developers
Does priority improve SEO?
No. Google ignores the priority value in XML sitemaps. Google for Developers
Does changefreq tell Google how often to crawl a page?
No. Google does not use the changefreq field for crawling. Google for Developers
What should I do if my sitemap has more than 50,000 URLs?
Split the URLs across multiple sitemap files and use a sitemap index where appropriate. Google supports sitemap index files for managing larger sitemap sets. Google for Developers
Where can I check an existing XML sitemap?
Use the XML Sitemap Analyzer to inspect an existing sitemap and investigate its URLs and technical signals.
Create Your XML Sitemap
A good sitemap starts with a clean URL inventory. Make sure the URLs you provide are absolute, belong to the intended site, represent pages you want search engines to consider, and stay within the sitemap size limits.
Use the XML Sitemap Generator above to create, validate, copy, and download your sitemap XML.
For broader technical SEO work, explore SEO & Website Tools or browse all free online tools to continue your workflow.