XML Sitemap: What It Is and How to Make One for Free

By Neha·Published October 6, 2026

A wholesaler who supplies fifty shops does not expect each shopkeeper to walk through the godown and guess what is in stock. He sends a list. An XML sitemap is that list, written for Google instead of a shopkeeper: every page on your website that you want found, one address per line.

Most owners have heard the word and filed it under "technical things my developer handles". Fair enough. But a sitemap is one of the few technical jobs you can check yourself in ten minutes, and when it is wrong, new pages can sit unnoticed for weeks. Below are the questions people actually ask about it, answered in the order they usually come up.

What is an XML sitemap, really?

It is a plain file, normally found at yourwebsite.in/sitemap.xml, that lists the addresses of your pages. XML is just the format, a strict way of writing a list so that a machine can read it without guessing. Opened in a browser it looks like this:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yourwebsite.in/</loc>
    <lastmod>2026-09-28</lastmod>
  </url>
  <url>
    <loc>https://yourwebsite.in/services/root-canal</loc>
    <lastmod>2026-08-14</lastmod>
  </url>
</urlset>

Each block is one page. The "loc" line is the address. The "lastmod" line is the date the page last changed in a real way. That is the whole idea. Customers never see this file. It exists for search engines.

Does a small website need one?

Honest answer: a five-page site with a clear menu will be found without it. Google follows links, and if every page is one click from the home page, the crawler gets there.

A sitemap starts to matter when any of these is true:

• The site is new and no other website links to it yet.
• You have more than a couple of dozen pages, such as an online shop or a blog.
• Some pages are buried, reachable only through a search box or three levels of menus.
• You add or change pages often, like weekly offers or new products.

Even for a tiny site we would still make one. It takes minutes, it costs nothing, and it gives you something useful in return: once you submit it in Google Search Console, Google reports back on those exact pages. You can see which were accepted and which were refused, and why.

What belongs in the sitemap, and what does not?

This is where most sitemaps go wrong. The file should list only pages you want a customer to land on from Google.

Put in: the home page, each service or product page, category pages, the contact and about pages, and every blog post.

Leave out:

• Pages that redirect somewhere else.
• Pages that show a "not found" error.
• Pages you have marked noindex, meaning you asked Google not to show them.
• Thank-you pages, cart, checkout and login pages.
• Two addresses for the same page, such as one with www and one without.
• Search-result and filter pages with long question-mark addresses.

A sitemap full of dead or duplicate addresses does not get you punished, but it teaches Google that your list cannot be trusted, and a list that cannot be trusted gets read less often. The sitemap checker finds your sitemap, counts its pages and flags the addresses that should not be in it.

How do I create a sitemap for my website?

It depends on what the site is built with. If you do not know, the website technology checker will tell you.

WordPress. Recent versions make a basic one automatically at /wp-sitemap.xml. If you use Yoast or Rank Math, the plugin replaces it with a better one at /sitemap_index.xml. You do not need to build anything, only to check it.

Shopify, Wix, Squarespace. All three generate the sitemap for you and update it when you add products or pages. Type your address followed by /sitemap.xml to see it.

A hand-coded site or a simple page builder. Here you make it yourself. Paste your page addresses into the sitemap generator and it gives you a ready sitemap.xml file to upload into the main folder of your site, next to the home page.

If you are writing your own, three rules keep you out of trouble. Use the full address including https. Use one version of each address only. And put a real date in lastmod, not today's date on every page, because Google learns to ignore dates that always say "changed today".

How do I submit a sitemap to Google?

Two steps, and both are free.

1. Open Google Search Console and choose your website. If you have not set it up, our Search Console guide for beginners covers verification.
2. Click Sitemaps in the left menu, type the address of your sitemap, and press Submit.

Within a day or two the status should read "Success" with a count of the pages found. If it says "Couldn't fetch", the usual causes are a typing mistake in the address, a robots.txt rule blocking the file, or a site that was slow to respond when Google called.

Add one more line while you are at it. In your robots.txt file, write Sitemap: followed by the full sitemap address. Then every search engine finds it, not only Google. The robots.txt guide explains that file.

Bing, which also feeds results into several AI assistants, accepts something faster as well. With IndexNow you can tell Bing the moment a page is added or changed. The IndexNow submitter does it without an account. Google does not use IndexNow, so for Google the sitemap remains the main route.

My sitemap is submitted. Why are pages still not on Google?

Because a sitemap is an invitation, not an order. Google reads the list, visits the pages when it chooses, and then decides page by page whether each one is worth keeping. Submitting a sitemap does not guarantee a page appears, and it does nothing for rankings by itself.

When listed pages are missing from search, work through these in order:

1. Wait a little. A brand-new site can take from a few days to a few weeks.
2. Check the page is allowed. A noindex tag or a robots.txt block overrides the sitemap.
3. Check the page says something. A page with two lines of text and a phone number often gets "Crawled, currently not indexed", which is Google's polite way of saying it saw nothing worth saving.
4. Check other pages link to it. A page that appears in the sitemap but in no menu and no other page looks unimportant. Our guide to internal linking shows how to fix that.

The Google index checker tells you which of your pages Google has saved and gives a plain reason for each one it left out. For the longer version, read website not showing on Google.

How often should it be updated?

If a plugin or platform makes your sitemap, it updates itself and you can forget it. If you built the file by hand, update it whenever you add, remove or rename a page. A sensible habit for a hand-built site is to recheck it after any redesign and otherwise every few months, at the same time as you run through an on-page SEO checklist.

Redesigns are the dangerous moment. Old addresses get renamed, the sitemap keeps pointing at the old ones, and suddenly half the list leads to error pages.

Frequently asked questions

Is an HTML sitemap the same as an XML sitemap?

No. An HTML sitemap is a normal web page with links to your pages, made for human visitors. An XML sitemap is a file made for search engines. Small sites rarely need the HTML kind if the menu is clear.

How many pages can one sitemap hold?

A single file can list up to 50,000 addresses. Larger sites split the list into several files and link them from a sitemap index. A small business will never get near the limit.

Do "priority" and "changefreq" matter?

Google has said it ignores both. Many generators still add them, and they do no harm, but do not spend time tuning them. The address and an honest last-modified date are what count.

Does having a sitemap improve my Google ranking?

Not directly. It helps Google discover pages sooner and report problems to you. Ranking still depends on what is on the page, how fast it loads and who links to it.