What it looks like
An XML sitemap is a file made for search engines, not for visitors. It usually lives at /sitemap.xml. A minimal one with two pages looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.example.com/</loc>
<lastmod>2026-09-14</lastmod>
</url>
<url>
<loc>https://www.example.com/repot-a-houseplant</loc>
<lastmod>2026-08-02</lastmod>
</url>
</urlset>
Each url block holds one address. The lastmod line is the date the page last changed. Most site builders create and update this file for you.
Why it matters
- It helps pages get found. Crawling starts with knowing that an address exists. A sitemap is useful for new pages and for pages with few links pointing to them.
- It is a list of suggestions, not a promise. Being in the sitemap does not guarantee indexing.
- It does not replace links. An internal link tells a search engine that the page exists and that it matters to you.
- It has limits. One file may list up to 50,000 addresses. Larger sites split the list into several files.
- Some fields are ignored. Google ignores
priorityandchangefreq, so there is no point in tuning them.
COMMON MISTAKEListing every address the site has. A sitemap should contain only pages you want indexed. Leave out redirects, error pages and pages marked noindex.
How to check yours
- Type your domain followed by
/sitemap.xmlinto your browser. If nothing loads, look for aSitemapline in your robots.txt file. - Skim the list. Are your important pages there?
- Open a few of the addresses. Each should load directly, without a redirect or an error.
- Submit the sitemap in Google Search Console under Sitemaps, and read the report for problems.
The lesson XML sitemaps: what to include and what to leave out goes through each choice.