XML sitemap

Also called sitemap

Reviewed 31 Oct 2026 By Madiha Fatima 3 min read Check it yourself: yes, free

3 min

Definition

An XML sitemap is a file on your website that lists the pages you want search engines to know about, with the date each one last changed. It is written for machines, not visitors. Search engines read it to discover new pages quickly and to notice updates, instead of waiting to stumble on them by following links.

Listing a page in a sitemap does not make it rank or even guarantee it is indexed. It is a hint about what matters. Leaving out a page you care about is the mistake that costs you.

An XML document following the sitemaps.org protocol: <urlset> of <url> entries with <loc> and optional <lastmod>, up to 50,000 URLs or 50 MB per file, grouped by a sitemap index. Google ignores <priority> and <changefreq> but does use an accurate <lastmod>. Reference it in robots.txt and submit it in Search Console.

Include only canonical, indexable, 200-status URLs. Redirected, noindexed, 404 or non-canonical URLs in the sitemap send mixed signals and show up as errors or excluded pages. Most CMS SEO plugins generate one automatically; the work is making sure the right post types are included and the junk (tags, attachments, paginated archives) is not.

<url><loc>https://example.com/services/emergency-towing/</loc><lastmod>2026-10-31</lastmod></url>

Short version: the list of pages you want found, handed over in advance.

Why it matters for your business

A page Google never finds
is a page that never earns.

Search engines find most pages by following links, which works when a page is well linked and fails quietly when it is not. A new service page sitting three clicks deep with no link from the menu can go unvisited for weeks. The sitemap is how you hand over the full list and say these are the pages, this is when they changed, please come and look.

It is also a diagnostic. When Google Search Console says you submitted eighty pages and indexed thirty, you have a number to argue with. Which fifty, and why not? The answers are usually thin content, duplicates or pages blocked by mistake, and each has a fix. Without the sitemap you have no baseline to compare against.

Generating a sitemap takes a plugin and a minute. If it appears as a chargeable task in a proposal, it should be a small one. Checking that it is correct and complete is the part worth paying for, as part of an SEO audit.

Example

A towing company adds six area pages
and nobody tells Google.

What the owner sees

Six new pages, one per suburb the trucks cover, each with the local number and response time. Published on a Friday. A month later none of them shows up for any search and the owner is told it takes time.

/towing/northside/
/towing/riverside/
/towing/airport-district/
... not in sitemap, not linked from the menu

What Google sees

Nothing. The pages were built with a page builder in a custom post type the sitemap plugin was not set to include, and the only links to them are from a footer that loads by script. With the post type added to the sitemap and the pages linked from the service menu, Google requests them within days and the suburb searches start to appear in Search Console.

How to check it on your site

Four checks, no tools to pay for.

Tick each one as you go. 0 of 4 checked on your site.

Open the sitemap in your browser
Type your domain followed by /sitemap.xml or /sitemap_index.xml. A good result is a list of your pages, posts and products with recent dates. A bad result is a not-found page, a list of only blog posts or a list full of tag pages and image attachments you never meant to rank.
Count what is missing
Open your own menu and service pages and check that each one appears in the sitemap. New service pages, location pages and products are the usual absentees. Anything you want found and cannot see in the list is a fix for whoever manages the site.
Read the Sitemaps report
In Google Search Console, choose Sitemaps. Status should read Success with a discovered page count close to the number of real pages you have. Couldn't fetch, or a count far below your real pages, means the file is wrong or the wrong file was submitted.
Compare submitted with indexed
In the Pages report, filter to pages in the submitted sitemaps and look at the Not indexed reasons. Crawled, currently not indexed usually means thin or duplicate content. Blocked or Redirect reasons mean the sitemap lists addresses it should not.

Where this shows up in practice.

Technical SEO Website not showing on Google

A missing or broken sitemap is one of the plain reasons, with the fix in order.

Expectations How long SEO takes

Discovery is the first wait in the timeline, and the sitemap is how you shorten it.

Service SEO & AI search

Sitemap and index coverage are checked in month one and reported every month after.

Related service

Sitemap setup and index coverage are part of the technical audit in month one of the SEO service, and every site we build ships with one. Prices are on the price list, not on a call.

See the SEO service

Reviewed by Madiha Fatima, founder of 99creatix

Every entry in this glossary is written and checked by the person who runs the agency, reviewed at least once a quarter and dated. Last reviewed 31 October 2026.

Spotted an error or a term we are missing? Tell us and it is fixed within the week.

Did this explain it?

Next step

Not sure Google knows
all your pages?

Fifteen minutes with your Search Console. We will compare your sitemap with your real pages, show you what is indexed and what is not and tell you why, before you decide anything.

Book a 15-minute fit call Back to the glossary

A page Google never findsis a page that never earns.

A towing company adds six area pagesand nobody tells Google.

Four checks, no tools to pay for.

Usually in the same sentence.

Where this shows up in practice.

Not sure Google knowsall your pages?

A page Google never finds
is a page that never earns.

A towing company adds six area pages
and nobody tells Google.

Not sure Google knows
all your pages?