Sitemap Generator

A sitemap is a file that lists URLs on your website and can help search engines discover them. It does not guarantee crawling or indexing, and it is not a substitute for useful internal links.

Use XML for standard search engine submission through Google Search Console and Bing Webmaster Tools. Choose TXT for a simple URL list when that format suits your workflow. Select CSV for documentation or spreadsheet sharing; TXT and CSV do not provide XML sitemap metadata.

Publish the XML file at a URL on your site, then open the Sitemaps section for your property in Google Search Console and submit its URL. Submission does not guarantee when or whether URLs will be crawled or indexed.

Priority (0.0 to 1.0) is an optional field for relative importance within your site. Google ignores it, so it does not affect Google's crawling or indexing. Use it only if it is useful to another sitemap consumer.

changefreq describes an expected update pattern; lastmod records when the page was last significantly changed. Google ignores changefreq and priority; accurate lastmod values may be used by search engines.

Common validation failures include: missing protocol (we auto-fix to https://), malformed domain names, URLs exceeding 2048 characters, or duplicate entries. Check the error panel for specific line numbers. The tool attempts smart extraction from pasted formats, but heavily malformed source text may need manual cleanup.

The sitemap protocol limits single files to 50,000 URLs. For larger sites, create multiple sitemaps and submit a sitemap index file that references them. This tool warns when approaching limits; you'll need to split input manually and generate separate files, then combine them with an index wrapper.

Enabling the image namespace adds xmlns:image to your XML, allowing manual inclusion of image metadata per URL. This helps Google Images discover your visual content. Note: this tool enables the namespace only—you'd extend individual URLs with <image:image> tags manually or via API for full image sitemap implementation.

Enable hreflang support only if your site has language or regional variants (e.g., /en/ and /es/ versions of the same page). This adds the xmlns:xhtml namespace for alternate link annotations. Without actual hreflang tags in your source code pointing between variants, enabling this has no benefit.

No—this is a generator, not a crawler. You must provide the URLs yourself by pasting them. For automatic crawling and sitemap discovery, use dedicated SEO tools like Screaming Frog, Sitebulb, or cloud-based crawlers. This tool excels when you have a known list of URLs from CMS exports, analytics, or manual compilation.

Update whenever you publish significant new content, remove pages, or change URL structures. For actively maintained sites, weekly or monthly regeneration is typical. Automated systems often regenerate sitemaps on each build; manual users should refresh before major SEO campaigns or after content migrations.

Technically yes, but search engines generally reject cross-domain sitemaps unless you verify ownership of all domains in Search Console. Each domain should typically have its own sitemap. Subdomains (blog.example.com vs www.example.com) can be combined but are treated separately by search engines unless properly canonicalized.

lastmod reports when a page was last significantly updated. Only use an accurate date; automatically inserting today's date for unchanged pages can be misleading. The tool can populate a date, so review it before publishing.

Yes—uncompressed sitemaps must stay under 50MB. The tool estimates your output size and warns if approaching this limit. Compress large sitemaps with gzip (acceptable to search engines) or split into multiple files referenced by a sitemap index.