XML sitemaps

An XML sitemap is a machine-readable file listing the addresses a website wants search engines to know about, which is why this specific SEO document is called an XML sitemap rather than just “sitemap”. Its job is discovery — helping a search engine like Google learn that an address exists — and it does nothing at any later stage.

An XML sitemap is not the sitemap agreed with a supplier during scoping. That other kind of sitemap is a planning document about which pages will exist and how they nest, written for people, not for Google or any other search engine. It is covered on the sitemap as a document. The two share a word and nothing else, and hearing “the sitemap is done” can mean either — the XML sitemap or the planning sitemap.

What XML sitemaps contain, and what the file lists

One entry per address, with the address itself as the only genuinely important field. Optional fields record when the page last changed and how often it is expected to change.

The optional fields are worth a caution. A last-modified date that updates every night on a page that has not changed is noise, and platforms produce that pattern routinely. A change-frequency hint that says every page changes hourly is not believed and does not need to be.

What the list of URLs does and does not do

Claim	True?
Helps search engines discover addresses	Yes, particularly ones with few internal links
Forces pages to be indexed	No
Improves ranking	No
Speeds up indexing of a new page	It can help discovery; it does not compel storage
Replaces internal linking	No, and a page that is only in the sitemap is a page nothing links to

The last row is the one worth acting on. If a page appears in the sitemap and is linked from nowhere on the site, that is a structural defect. The sitemap is compensating for it, rather than solving it. That page is an orphan, and the fix is a link from somewhere sensible.

Where the sitemap XML file lives, and how to submit XML to Google Search Console

An XML sitemap conventionally lives at the root of the domain, at an address ending in sitemap.xml, and is referenced from robots.txt so a crawler finds it without being told. It is also submitted directly through Google Search Console, which additionally reports how many of the listed URLs Google has actually indexed.

That last number is the useful one for SEO purposes. A sitemap listing sixty addresses of which twelve are indexed is a diagnosis: discovery is working and something later is failing. Without the XML sitemap submitted to Search Console, that comparison is unavailable.

The contradictions worth checking before pages get indexed

A sitemap should agree with the rest of the site. Three disagreements occur regularly and all three are visible in a search console.

Listed pages that carry a noindex instruction. The site is saying “know about this” and “do not store this” at once.

Listed pages that redirect. The address in the file is not the address of the page. The file is stale.

Listed pages that do not exist. Deleted pages left in a generated file, usually because the generation is cached.

None of these is catastrophic. All of them indicate that nobody is looking at the file, which is the more useful finding.

What the file cannot express

Three limits are worth knowing before anyone attributes more to the file than it does.

It carries no instruction about indexing. Listing an address is a suggestion that it exists, not a request that it be stored, and there is no field that makes the request stronger.

It says nothing about the relationship between pages. A sitemap is a flat list; the parent-and-child structure that a reader navigates is expressed by internal links and by the addresses themselves, not here.

It expresses no priority that is acted upon. The optional priority field is a hint that is widely ignored, and setting every page to the highest value communicates nothing at all.

Multiple sitemaps, index files, and how crawlers use them

Large sites split the list across several files with an index file pointing at them. A small business site does not need this and will not encounter it unless a platform generates it by default, which several do.

Where a platform generates separate files for pages, posts, images and categories, the thing to check is whether the categories and archives listed are pages you actually want in search results. Platform-generated archive pages are a common source of thin, near-duplicate addresses.

Whose job the sitemap is, and where it sits in SEO

On nearly every modern platform the file is generated automatically and stays current without intervention. The build obligation is therefore small: confirm it exists, confirm it lists the right addresses, confirm it is referenced from robots.txt, and submit it once.

What is not automatic is anybody looking at the indexed-versus-submitted figure afterwards. That is an ongoing check rather than a build task. It belongs in whatever maintenance arrangement exists — the shape of those arrangements is on website maintenance cost.

What to check on your own site

Type your domain followed by /sitemap.xml. If a list of addresses appears, the file exists. Read ten of them and confirm they are pages you want found. Then check the same file is named in your robots.txt, which is on blocking and excluding pages.

If nothing appears at that address, check /sitemap_index.xml, which is the other common convention, before concluding it is missing.

A quick recap of what the sitemap file actually does

An XML sitemap is one file, and its job is narrow: list the URLs a site wants a crawler to find, in a format Google and other search engines can read automatically. Submitting the sitemap through Search Console tells Google where that file lives and lets it report back how many of the listed URLs it has actually indexed. The sitemap itself does not crawl anything and does not index anything — it is a list a crawler reads, not a process a crawler runs. Confusing “the sitemap is submitted” with “the pages are indexed” is the single most common misunderstanding this page exists to correct.

What to do next

Add two lines to the launch checklist. The sitemap exists and lists only pages intended for search results. And it has been submitted in a search console owned by the business. The second half of that sentence is the part that gets skipped, and the reason it matters is on measuring what search engines did. What a build should include generally is on services.