What an XML sitemap tells search engines
An XML sitemap is a machine-readable list of URLs that you want crawlers to discover. It is especially helpful for a new site, a large archive, pages with few internal links, or content that changes on an irregular schedule. A sitemap supports discovery, but it does not force indexing and does not replace links that users and crawlers can follow through the site.
Each entry contains an absolute URL inside a loc element. Optional fields can describe when the page was last substantially modified, an expected change frequency, and its priority relative to other URLs on the same site. Search engines may treat these optional values as hints or ignore them when observed behavior differs.
How to create your sitemap
- Collect the preferred canonical URL for each indexable page on one verified site.
- Paste one absolute HTTP or HTTPS URL per line.
- Add accurate last-modified dates and other optional hints only when you have reliable values.
- Generate the XML, review the entries, and download
sitemap.xml. - Publish it on your site and submit its public URL to the relevant search-engine consoles.
Use the final public form of every URL. Keep protocol and hostname consistent, respect letter case in paths, and avoid URLs that merely redirect elsewhere. Remove fragments because servers do not receive them, and omit tracking parameters, internal search pages, duplicate filters, login screens, and any page deliberately marked noindex.
Choose useful metadata
Last modified
The lastmod value should reflect a meaningful content change, not the time the sitemap was generated or a template footer changed. Accurate dates help crawlers schedule revisits efficiently. Automatically setting every URL to today on every build weakens the signal and wastes crawl attention.
Change frequency and priority
Change frequency is an estimate, not a crawl command. Priority is a value from 0.0 to 1.0 that compares URLs within your own site; it does not raise rankings against another domain. Defaults are usually better than labeling every page daily and 1.0. Apply different values only when the site structure gives you a defensible reason.
Publishing and discovery
A common location is https://example.com/sitemap.xml. Add an absolute Sitemap line to robots.txt so compliant crawlers can find it, and submit the same address in Google Search Console or Bing Webmaster Tools. The sitemap must return a successful response without requiring authentication, and its URLs must be accessible to the crawlers you want to reach.
One sitemap file can contain at most 50,000 URLs and be no larger than 50 MB uncompressed under the standard protocol. Split a bigger collection into multiple sitemap files and list them in a sitemap index. Compression with gzip is supported by major search engines and can reduce transfer size substantially.
Use cases that benefit most
A portfolio launching with no external links can expose all project pages immediately. An online store can list canonical product and category URLs while excluding cart and faceted duplicates. A publication can maintain dependable modification dates for evergreen articles. In each case, the sitemap should mirror the indexable content strategy instead of becoming a dump of every URL the application can produce.
After publishing, monitor submitted-versus-indexed reports rather than assuming the file solved every visibility problem. Excluded URLs often point to duplicate canonicals, blocked crawling, thin content, server errors, or weak internal linking. Fix the underlying issue and keep the sitemap consistent with the corrected site.
Privacy
XML generation runs in your browser from the URLs and options you provide; the list does not need to be sent to PagesTools. Once you publish the file, every listed URL is intentionally public to anyone who can fetch it. Do not include private staging hosts, unannounced pages, access tokens, customer identifiers, or secret query parameters. A sitemap is a discovery document, not an access-control system.