A free sitemap generator lets you build a correct XML sitemap in minutes, with no account and no signup. You enter your site address, generate the file, upload it to your site root, and submit it to Google Search Console and Bing Webmaster Tools. That is the whole job. The rest of this guide shows you how to do each step right, so search engines can read the file without errors.
If you want to skip the reading and just get the file, use the free sitemap generator from CrawlGuards. It builds the XML for you. The steps below explain what to check before you submit it, because a sitemap with broken links or wrong dates can do more harm than no sitemap at all.
What a Sitemap Is
A sitemap is a simple XML file that lists the pages on your site that you want search engines to find. Each entry usually has a page URL and, when you know it, the date the page was last changed. Search engines use that list as a map. It helps them discover pages they might otherwise miss, especially on a new site or a site with weak internal links.
Think of it like a table of contents. It tells a crawler, here are the pages that matter, and here is where they live. It does not tell the crawler what the pages mean. That job belongs to the page content itself, its title, and the links pointing to it.
What a Sitemap Is Not
A sitemap does not guarantee indexing. Submitting a page in a sitemap is a suggestion, not an order. Google and Bing still decide which pages to crawl and which to show in results, based on quality, usefulness, and whether the page adds something new. A thin page listed in a perfect sitemap will still stay out of the index if search engines judge it low value.
A sitemap also does not fix other problems. It will not rescue pages blocked by robots.txt, pages behind a login, or pages that return errors. It will not make duplicate pages rank. It will not replace internal links. If your site navigation is broken, fix that first. The sitemap is a helper, not a shortcut.
Rule to remember: a sitemap helps search engines find good pages faster. It cannot make a bad page good.
Do You Actually Need One?
Not every site needs a sitemap, but most sites benefit from one. You almost certainly need one if any of these apply:
- Your site is new and has few or no outside links pointing to it.
- Your site has a large number of pages, or pages buried deep in categories.
- Your pages change often, such as a blog, news section, or store with new products.
- Your site uses a lot of images, video, or other media you want discovered.
- Your internal linking is thin, for example a one-page menu that relies on JavaScript.
Small sites with a handful of well-linked pages can often get by without one. Even then, a sitemap costs little and gives you a clear report in Search Console about which submitted pages were actually indexed. That feedback alone is worth having.
Before You Generate Anything
Five minutes of prep saves a round of fixes later. Work through this list before you open the generator.
1. Decide which pages belong in the file
Include pages you want in search results: your homepage, main service or category pages, blog posts, product pages, and key landing pages. Leave out thank-you pages, login pages, admin pages, cart and checkout steps, internal search result pages, and any page you have marked noindex. If a page should not appear in search, it should not appear in your sitemap either. Mixed signals confuse crawlers and waste your crawl budget on pages you never wanted indexed.
2. Clean up the URLs
Use the final, canonical version of each URL. That means the same protocol for every entry, either https throughout, and a consistent choice on www versus non-www and trailing slashes. Do not list both the http and https version of the same page. Do not list a redirect as if it were a final page. Each URL in the file should return a 200 status when opened, not a 301, 404, or 500.
3. Know your size
One sitemap file can hold up to 50,000 URLs and must be no larger than 50 MB uncompressed. Most small and medium sites fit in one file with room to spare. If you are over either limit, you need a sitemap index file instead, which is covered below. Do not try to squeeze a huge site into one file by trimming at random. Split it cleanly by section instead.
4. Check your robots.txt
Your robots.txt file should not block the pages you plan to list. A quick way to check is to open your robots.txt file and read the Disallow lines, or test a few URLs with a checker. The robots.txt tester can help you confirm whether a given URL is allowed or blocked before you submit anything. If you need to build or fix the file itself, the robots.txt generator creates a clean version you can paste in place.
Step-by-Step: Build Your Sitemap in Minutes
Here is the workflow, start to finish. It works whether you use the CrawlGuards tool or another generator you trust.
- Enter your site address. Open the free sitemap generator and enter your homepage URL exactly as it appears in the browser, including https and your www choice. A wrong base address is the most common reason a generated sitemap fails.
- Let the tool crawl your site. The generator follows your internal links and collects the pages it can reach. Give it a minute on a larger site. If it finds far fewer pages than you expect, check your navigation. Pages with no links pointing to them cannot be found by a crawler, and often cannot be found by visitors either.
- Review the URL list. Scan the list before you download it. Remove test pages, staging URLs, tag pages with no value, and any URL with tracking parameters stuck on the end. Keep the list to pages you would be happy to see in search results.
- Set lastmod dates honestly. The lastmod field should show the real date a page last changed in a meaningful way. A typo fix does not count as a change worth reporting. If you do not know the true date, leave lastmod out rather than guessing. Search engines use lastmod when it is accurate, and they learn to ignore it when it is not.
- Download the XML file. Save it with a clear name, usually sitemap.xml. Open it in a text editor or browser and confirm it looks like proper XML, with one url entry per page, and no broken tags or stray characters at the top.
- Upload it to your site root. Place the file so it is reachable at yourdomain.com/sitemap.xml. Most hosts let you upload through a file manager or FTP. If you use WordPress or another content system, check whether it already generates its own sitemap first, so you do not end up with two competing files.
- Open the URL in your browser. Visit the full sitemap address and confirm it loads as XML, not as a download error or a 404 page. If the browser shows an error, fix the file before you submit it anywhere.
- Submit it to Google and Bing. In Google Search Console, go to the Sitemaps report and submit the sitemap URL. In Bing Webmaster Tools, do the same under Sitemaps. Submission takes seconds, and both tools will then report back on errors and indexed pages.
- Add it to robots.txt. Add one line to your robots.txt file pointing to the sitemap location, for example:
Sitemap: https://yourdomain.com/sitemap.xml. Replace yourdomain.com with your real domain. This line helps any crawler that checks robots.txt first, and it costs nothing to include.
That is the full process. For a typical small site, the whole thing takes under ten minutes once the page list is clean.
What a Good Sitemap Entry Looks Like
A basic entry is short. Here is an example of the shape a correct file follows:
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://yourdomain.com/guides/sitemap-basics/</loc>
<lastmod>2026-10-20</lastmod>
</url>
</urlset>Each page gets its own url block. The loc field holds the full page address. The lastmod field holds the date, in year-month-day form. You may also see changefreq and priority in older examples. Google has said it ignores priority and changefreq for ranking purposes, so do not spend time tuning them. Focus on accurate URLs and accurate lastmod dates. Those are the fields that actually help.
For the full technical spec, see the official protocol at sitemaps.org and Google's guide at Google Search Central. Both are short reads and worth bookmarking.
One File or a Sitemap Index?
If your site fits under 50,000 URLs and 50 MB, one file is enough. Keep it simple. A single sitemap.xml at the root is easy to check, easy to submit, and easy to replace when you update it.
Once you cross either limit, use a sitemap index. An index file is a small XML file that lists your other sitemap files, like a table of contents for sitemaps. For example, a store might split by section: one file for products, one for categories, one for blog posts. The index then points to each of those files, and you submit only the index URL to Google and Bing. Search engines follow the index and read each listed file.
Split by logic, not by random chunks. Group related pages together so that when one section has an error, you can find and fix that one file without touching the rest. Keep each child file under the same 50,000 URL and 50 MB limits, and keep all of them on the same domain as the index.
Image, Video, and News Sitemaps in Brief
The standard sitemap covers web pages. Three extensions cover other content types, and most sites only need the first one, if any.
Image sitemaps
An image sitemap lists images on a page, including images loaded by JavaScript that a crawler might otherwise miss. This matters most for photography, product, and portfolio sites where image search brings real traffic. For a normal blog post with a few inline images, the standard sitemap plus good alt text is usually enough.
Video sitemaps
A video sitemap gives details about videos on your pages: title, description, length, and thumbnail. It helps video content appear in video search results. If video is a side feature on your site rather than the main product, you can skip this until video becomes a bigger traffic source.
News sitemaps
A news sitemap is only for sites approved for Google News, and it covers articles published in the last two days. Unless your site publishes news and is part of Google News, you do not need one. A regular sitemap already covers your articles for normal search.
Start with a solid standard sitemap. Add an extension only when that content type is a real part of your traffic plan.
How to Check Your Sitemap After Upload
Do not assume the upload worked. Check it three ways.
- Open it in a browser. Visit yourdomain.com/sitemap.xml. You should see structured XML. If you see your homepage instead, your server may be rewriting the request, and the file may not be where you think it is.
- Check Google Search Console. In the Sitemaps report, look for a Success status, the number of discovered URLs, and any errors. A common early result is a small number of indexed pages. That is normal on a new site. Indexing grows over days and weeks, not minutes.
- Check Bing Webmaster Tools. Bing has its own Sitemaps section with a similar status report. Submit there too, since Bing powers its own search results and feeds other search partners. One submission does not cover both engines.
If either tool reports errors, read the exact error message before changing anything. The most common errors are simple: a URL that redirects, a URL that returns 404, a file that is too large, or an XML tag that was not closed. Fix the specific URLs listed, re-upload, and resubmit. There is no need to regenerate the whole file when only a few entries are wrong.
Common Mistakes That Waste a Good Sitemap
Most sitemap problems come from the same short list. Avoid these and you are ahead of most sites.
- Listing pages you blocked elsewhere. A page in the sitemap but blocked by robots.txt, or marked noindex, sends a mixed message. Keep the three in agreement: sitemap, robots.txt, and page-level index settings should all point the same way.
- Listing redirect chains and error pages. Every URL should return 200. A sitemap full of 301s and 404s tells crawlers the list is stale, and they will trust it less next time.
- Stale lastmod dates. Setting every page to today, or to the date you generated the file, is worse than leaving lastmod out. Search engines notice when lastmod does not match real changes, and they stop using it as a signal.
- Forgetting to update it. A sitemap is not a one-time task. When you publish new posts or remove old pages, regenerate the file or let your content system update it. A sitemap that still lists deleted pages is a sign the site is not maintained.
- Submitting it once and never looking back. The Search Console report is the point. Check it after a week, then monthly. A sudden drop in discovered URLs often points to a server or plugin problem you want to catch early.
- Using a sitemap as a substitute for links. Orphan pages with no internal links may still get discovered through a sitemap, but they rank poorly without links. Link new posts from a category page or a related article, and let the sitemap do the rest.
What to Do After Generating
Generating the file is half the work. The follow-up is what turns it into results.
- Submit the sitemap to Google Search Console and Bing Webmaster Tools, and add the Sitemap line to robots.txt.
- Link new pages internally from relevant category pages and related posts, so crawlers and readers can reach them by more than one path.
- Check the Sitemaps report after a few days for errors, then again after two weeks to see how many submitted pages are indexed.
- Regenerate or update the file whenever you add a batch of new pages or remove old ones. On a blog, that usually means updating it with each publishing round.
- If a page stays unindexed for weeks despite being in the sitemap, look at the page itself. Check its content depth, its title, whether it duplicates another page, and whether it has any links pointing to it. The sitemap did its job by making the page discoverable. The page still has to earn its place.
That last point matters most. Site owners often blame the sitemap when a page does not rank. In most cases the sitemap worked fine, and the page needs better content, a clearer purpose, or stronger internal links. Fix the page, keep the sitemap accurate, and give search engines time to re-crawl.
Choosing a Generator Without Signing Up
You do not need an account to build a sitemap. A good free generator should let you enter a URL, crawl the site, review the list, and download clean XML, with no email wall and no forced trial. Watch out for tools that cap the free version at a tiny number of pages and then push a paid plan before you can download anything useful. For most small sites, the free tier of a straightforward tool is enough.
Also check what the tool does with your data. A generator that only crawls your public pages and returns a file is doing a simple job. One that asks for site login details or server access is asking for more than this task needs. Keep it simple, keep the file on your own server, and keep a copy of the downloaded XML so you can compare it after future updates.
Frequently Asked Questions
Does a sitemap guarantee my pages will be indexed?
No. A sitemap helps search engines discover pages, but indexing depends on content quality, uniqueness, links, and crawl capacity. Think of it as handing over a map. The map helps, but the destination still has to be worth visiting.
Where should I put my sitemap file?
Put it at your site root, so it is reachable at yourdomain.com/sitemap.xml, and add a Sitemap line to robots.txt pointing to that address. Submit the same URL in Google Search Console and Bing Webmaster Tools. Keeping one canonical location avoids confusion when tools check for it.
How often should I update my sitemap?
Update it whenever your page list changes in a meaningful way: new posts, new products, removed pages, or changed URLs. For an active blog, that means updating with each publishing batch. For a stable brochure site that rarely changes, a check every few months is enough.
What is the limit for a single sitemap file?
One sitemap file can contain up to 50,000 URLs and must be no larger than 50 MB before compression. If you exceed either limit, split the site into several sitemap files and list them in a sitemap index file, then submit the index.
Do I need a sitemap if my site is very small?
Not strictly, but it still helps. A small site with clear navigation and a few outside links will usually get crawled without one. Even so, a sitemap gives you a clean indexing report in Search Console and helps new pages get found faster, so most small sites are better off having one.
Start with the free sitemap generator, review the URL list, upload the file to your root, and submit it to both search engines. That simple routine, repeated as your site grows, keeps your pages discoverable without extra tools, accounts, or cost.
