Sitemap Generator
Quick Access to SEO Tools
Go straight to the SEO utility you need.
How to Use the Sitemap Generator
Enter your website URL
Enter your website URL.
Configure crawl settings
Configure crawl settings.
Generate and download the sitemap.xml
Generate and download the sitemap.xml.
Sitemap Generator — Create XML Sitemaps for Search Engine Crawling
An XML sitemap is essentially a roadmap for search engines. It lists every important URL on your site along with metadata — the last time the page was updated, how frequently it changes, and how it ranks in importance relative to your other pages. When Google or Bing are deciding what to crawl and in what order, a well-structured sitemap gives them a head start.
Not every site needs one. A personal blog with 30 pages and solid internal linking? Google will find everything through normal crawling. But a growing e-commerce store with 5,000 product pages, or a news site publishing 50 articles a day, or a newly launched site with zero backlinks — those absolutely benefit from a sitemap. This tool generates a valid Sitemaps.org-compliant XML file that you can upload to your site's root directory and submit to Google Search Console and Bing Webmaster Tools.
Anatomy of an XML Sitemap
A basic XML sitemap entry looks like this:
<url><loc>https://example.com/about</loc><lastmod>2026-06-15</lastmod><changefreq>monthly</changefreq><priority>0.7</priority></url>
Each <url> block contains the page URL (<loc>) and optional metadata. The <loc> must be a fully qualified absolute URL with the https:// protocol. Using http:// when your site has migrated to HTTPS, or using relative paths, will cause issues. The <lastmod> date uses ISO 8601 format (YYYY-MM-DD) — don't fake it. If Google detects that your <lastmod> dates don't reflect actual content changes, it will start ignoring the tag entirely.
For large sites (over 50,000 URLs or 50MB uncompressed), you'll need to split your sitemap into multiple files and create a sitemap index file that lists them all. The sitemap index uses the same XML namespace but wraps <sitemap> elements instead of <url> elements. Many CMS platforms and SEO plugins handle this splitting automatically.
Priority and Changefreq — What They Actually Do
The <priority> tag ranges from 0.0 to 1.0 and signals the relative importance of a page within your own site. Here's the reality: Google has publicly stated it largely ignores this tag. It was designed to help crawlers prioritize pages on massive sites, but in practice, Google uses its own PageRank-based signals to determine crawl priority. Still, setting sensible values costs nothing and can help smaller crawlers like Yandex or Bing's crawler.
A practical priority scheme: homepage at 1.0, main category pages at 0.8, important sub-pages at 0.6–0.7, individual articles or product pages at 0.5, and utility pages (privacy policy, terms of service) at 0.3. Don't set everything to 1.0 — that defeats the purpose.
<changefreq> hints at how often the page content changes. daily fits news homepages and active blogs; weekly works for pages updated a few times a month; monthly for static pages like About or Contact; yearly for rarely changed legal pages. Again, Google treats this as advisory — its own crawl scheduler is based on observed update frequency, not what you declare.
Image and Video Sitemaps
Beyond the basic URL list, you can extend your sitemap with specialized namespaces to help search engines understand non-text content on your pages.
Image sitemaps use the image:image namespace to list images on each page. This is particularly useful if your images are loaded via JavaScript or aren't discoverable through standard HTML <img> tags. An image sitemap entry includes the image URL, caption, title, and license information. For e-commerce sites, this can help product images appear in Google Image Search.
Video sitemaps use the video:video namespace to provide metadata about embedded videos — title, description, thumbnail URL, duration, and upload date. This helps Google Video Search understand and index your video content. Without video markup, Google relies on page text and YouTube metadata (if the video is hosted there) to understand what the video is about.
For most standard websites, the basic URL-only sitemap is sufficient. Image and video sitemaps are most valuable for media-heavy sites, news publishers, and e-commerce catalogs.
Submitting to Google Search Console and Bing
Generating the sitemap is step one. Getting it indexed is step two. Here's the process:
Google Search Console: Go to the "Sitemaps" section in the left sidebar, enter your sitemap URL (like https://example.com/sitemap.xml), and click "Submit." Google will queue it for processing. You'll see the sitemap status in the dashboard — check it after a day or two to confirm Google successfully read the file. Common errors: the sitemap contains URLs that return non-200 status codes, or the file is too large (over 50MB uncompressed).
Bing Webmaster Tools: Navigate to "Sitemaps" and submit your sitemap URL. Bing also supports the Sitemap: directive in robots.txt, which you can add alongside your sitemap submission for redundancy.
Keep it updated: When you add or remove significant pages, update your sitemap and resubmit it. Don't manually edit XML — use a generator, a CMS plugin, or a build script that regenerates the sitemap from your site's content database. Stale sitemaps (listing URLs that 404 or redirect) waste crawl budget and look sloppy.
Frequently Asked Questions About Sitemaps
https://example.com/sitemap.xml. Search engines expect to find it there. If your site is on a CDN or uses server-side routing, make sure the file isn't blocked by a catch-all route rule. After uploading, verify by visiting the URL directly in your browser — you should see the XML content.
sitemap-index.xml) that references each sub-sitemap. In practice, most small to medium sites fit comfortably in a single file. WordPress with Yoast or Rank Math generates sitemap index files automatically when you hit the limit.
noindex tags, duplicate content, thin content, or canonical tags pointing elsewhere won't be indexed even if they're listed in your sitemap. Think of the sitemap as an invitation — Google decides whether to show up.
<lastmod> date should only update when the page content actually changes — don't update it just because you regenerated the sitemap file. Most CMS plugins handle this automatically.
Sitemap: https://example.com/sitemap.xml to your robots.txt file ensures all crawlers (not just Google, which already checks Search Console submissions) can find your sitemap. It's a simple best practice that takes one line and costs nothing. Place it outside any User-agent block — the Sitemap: directive is global and should appear at the top or bottom of the file.
robots.txt file tells search engines what not to crawl (keep out of these directories). You need both: the sitemap guides crawlers to your important content, and robots.txt keeps them away from admin panels, login pages, and staging environments. They work together as part of a comprehensive crawl strategy.