What Is an XML Sitemap and How to Submit One

An XML sitemap is a file that lists the pages on your website you want search engines to discover. It is written in a structured format that crawlers read easily, and it acts as a directory of your important URLs. For small, well-linked sites the benefit is modest, but for large sites, new sites, or sites with pages that are hard to reach through normal links, a sitemap is one of the most reliable ways to help Google and Bing find everything worth indexing.

What an XML sitemap does

The sitemap gives search engines a clean list of URLs plus optional signals such as when each page was last modified. Crawlers normally discover pages by following links, so any page buried deep in your structure, or not linked well internally, can be slow to find. A sitemap short-circuits that by handing over the list directly. It does not replace good internal linking — it complements it — and it is especially valuable right after a launch or a large content push.

The format itself is simple: an XML file wraps a list of <url> entries, each holding a <loc> element with the page address and, optionally, a <lastmod> date. Older sitemap tags for change frequency and priority exist, but Google has said it largely ignores them, so there is little point fussing over those values. An accurate lastmod date is more useful, because it helps crawlers understand when a page genuinely changed and is worth re-fetching. Keep it honest, though: if every URL claims to have changed today, the signal becomes noise and crawlers learn to ignore it.

Does a sitemap guarantee indexing?

No. This is the most important thing to understand. A sitemap aids discovery: it helps Google find your URLs. It does not force indexing: Google still decides, page by page, whether each URL is worth including based on quality, uniqueness, and other signals. Listing a page in your sitemap is a request for attention, not a command. If important pages are not being indexed, the sitemap is rarely the fix — the answer usually lies in content quality, internal links, or crawlability rather than in the sitemap file.

What should and should not go in a sitemap

Include only URLs you genuinely want indexed. That means:

• Canonical URLs — the master version of each page, matching your canonical tags.
• Pages that return a 200 (OK) status and are not blocked from indexing.
• Your real, current URLs with the correct protocol and trailing-slash format.

Leave out redirected URLs, 404s, noindexed pages, and pages blocked in robots.txt. A sitemap full of non-indexable URLs sends mixed signals and wastes crawl budget. Most content platforms and SEO plugins generate and update a valid sitemap automatically, so check what your site already produces before building one by hand.

How do you submit a sitemap to Google?

Submit it through Google Search Console. Open the property for your site, go to the Sitemaps report, enter the sitemap’s URL (commonly sitemap.xml or sitemap_index.xml), and submit. Google will fetch it and report how many URLs it discovered and any errors. Do the same in Bing Webmaster Tools for Bing. You can and should also reference the sitemap in your robots.txt file with a Sitemap: line, which lets any crawler find it without a manual submission.

After submitting, check back on the Sitemaps report over the following days. It shows whether Google could read the file, how many URLs it found, and when it last fetched it. If the count is far lower than the number of pages you expected, that is a signal to investigate — often the sitemap is listing URLs Google is choosing not to index, or the file contains errors. The report is a genuinely useful diagnostic, not just a submission receipt, so revisit it whenever indexing questions come up.

How often should a sitemap update?

It should update whenever your set of indexable URLs changes — when you publish, delete, or move pages. Automatically generated sitemaps handle this for you, refreshing as you add or remove content. If you maintain a sitemap manually, update it on the same schedule you publish; a stale sitemap that lists dead pages or omits new ones undercuts the whole point. Large sites can split their URLs across multiple sitemap files gathered under a sitemap index, which keeps each file within size limits and easier for crawlers to process.

Do small sites even need a sitemap?

Often they benefit less, but there is little downside to having one. If your site is small and every page is reachable within a few clicks from the homepage, Google can usually find everything through links alone. A sitemap still helps as sites grow, and it gives you the useful Search Console report showing what Google discovered and indexed. Because sitemaps, canonicals, and robots.txt work together, keep them consistent, and treat the sitemap as one item on a broader technical foundation like your structured data and schema setup.

The bigger point is that a sitemap is a discovery aid, not a growth tactic. It will not lift a page that is not earning its place, and it cannot compensate for weak content or a site so poorly linked that users struggle too. Set it up correctly, keep it clean and current, and then spend your effort where the real gains are: strong internal linking, genuinely useful pages, and a crawlable, fast site. The sitemap simply makes sure nothing worthwhile goes unnoticed.