XML sitemap: what sitemap.xml does for discovery
An XML sitemap is a machine-readable file listing web addresses and optional associated information for search engines. It supports discovery and crawling, but does not guarantee that every listed page will be indexed or appear in results.
Also known as: Sitemap · sitemap.xml
At a glance
- A sitemap supports discovery; it does not switch indexing on.
- List appropriate canonical addresses you want available in search.
- Use lastmod for real content changes, not the time the sitemap was generated.
On this page

When a sitemap helps
A new website may have few incoming links. A larger site may make discovery of every important article or product harder. Google describes sitemaps as useful in situations like these. Sitemap overview
The file helps search engines discover addresses. It does not replace visitor navigation or make an empty page useful. An HTML sitemap for people and an XML file for crawlers are different interfaces.
“In the sitemap” means the website lists the URL. Actual crawling and indexing require separate evidence.
A minimal example
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/guides/window-measurements</loc>
<lastmod>2026-10-23</lastmod>
</url>
</urlset>
This is fictional. urlset contains entries, url represents one entry and loc contains its complete address. lastmod is optional. The http namespace identifier does not instruct the website to abandon HTTPS. Sitemaps protocol
The date assumes a real change on that day. Use actual addresses and dates. Escape XML-sensitive characters such as & as &.
Which addresses belong?
List the canonical URLs of content intended for search, rather than every campaign-parameter variation.
Distinguish finished public pages from planned topics and internal workspaces. Listing an unfinished article does not publish it, and retaining a deleted URL does not make it available. Automated generation should follow the actual content state.
What lastmod means
lastmod represents a page’s modification, not the sitemap’s generation time. Google uses consistently accurate values reflecting significant changes and ignores priority and changefreq. Building a sitemap
Do not reset every date daily when nothing changed. If a reliable modification date is unavailable, omit the optional field instead of inventing one. A higher priority value does not purchase a better ranking.
Example: five finished guides
Imagine a workshop publishing five furniture-care guides while planning ten more. The five have complete content, working pages and useful navigation. The other ten are only topic ideas.
List the finished pages, then add each new guide when ready. If two guides are later combined, update the list accordingly. This keeps discovery signals aligned with publication; it does not guarantee simultaneous indexing.
Discovery and verification
Submit the sitemap through Search Console or reference it in robots.txt. Check that the file can be fetched and processed. The protocol allows up to 50,000 URLs and 50 MB uncompressed per file; a sitemap index can organize multiple files.
Successful processing is not successful indexing of every entry. Investigate an absent page individually. Review website architecture, orphan pages, pagination and faceted navigation alongside the URL list.
IndexNow notifies supporting search engines about changes; it is not a general Google indexing switch. llms.txt is a separate proposed reference format that Google Search currently ignores. Neither replaces useful content and internal links.