An XML sitemap is an inventory file submitted to crawlers. It lists URLs, provides optional metadata, and leaves it up to the search engine to decide what to do with them. This distinction between a signal and a directive shapes the entire implementation strategy.
XML sitemap tags: what Google actually uses
The protocol specification provides several fields for each <url> entry. Search engines don’t treat them all the same, and confusing the two categories is a waste of configuration time.
Google ignores the priority and changefreq fields. Filling them in has no effect on crawl order or frequency. These tags, inherited from the protocol’s first version, are still syntactically accepted but have no operational effect.
The lastmod field, however, is taken into account, provided the date reflects a substantial change to the page’s main content, structured data, or internal linking. Changing the copyright year or a cosmetic template element doesn’t count. If the value is inconsistent or systematically identical across all URLs, the search engine will eventually ignore it across the entire site.
In practice, a well-built sitemap focuses on loc (the URL) and lastmod (the reliable date). Everything else is noise. We find that many automated generators still fill in priority with a default value of 0.8 for every page, which is completely pointless.
For example, Incroyable Maison’s sitemap illustrates a readable XML file listing all the pages on the site, allowing both crawlers and curious visitors to view the complete site structure.
XML sitemap file size limits and sitemap indexes
A single sitemap file can contain up to 50,000 URLs or 50 MB uncompressed. Exceeding either limit makes the file invalid, and crawlers may ignore it without explicitly warning you.
For large sites (e-commerce catalogs, directories, media sites with extensive archives), the standardized solution is a sitemap index. This parent file references multiple child sitemaps, each of which must comply with the size limits.
- Segmenting by content type (product pages, blog posts, categories) makes it easier to diagnose indexing issues affecting a specific section of the site.
- Segmenting by publication date means you only need to regenerate the current month’s file instead of recalculating everything with each update.
- An index can itself contain tens of thousands of references to child sitemaps, covering almost any existing site architecture.
Gzip compression is supported and significantly reduces the bandwidth crawlers use. The compressed file must still be under 50 MB when decompressed.
Sitemaps and indexing: a signal, not a directive
A common misconception is that a sitemap guarantees indexing. Submitting a URL in your sitemap does not force Google to crawl it. Google downloads the file and notes the candidate URLs, then decides based on its own criteria (perceived quality, crawl budget, popularity signals) whether each page is worth crawling and indexing.
A sitemap therefore doesn’t replace a coherent internal linking structure. An orphan page (one with no internal links pointing to it) listed in the sitemap is unlikely to be indexed if the search engine has no other reason to visit it. The XML file supports discovery; it doesn’t replace the site’s architecture.
Listing URLs in the sitemap that return a 404 status code, a 301 redirect, or a noindex tag sends conflicting signals. Every URL in the sitemap should return a 200 status code and be indexable. SEO audit tools flag these inconsistencies, but fixing them requires regularly cleaning up the file—not just running a one-off scan.
Specialized sitemaps: images, videos, and news
The sitemap protocol isn’t limited to HTML pages. Extensions let you describe specific types of content for vertical search engines.
- The image sitemap enriches each
<url>entry with<image:image>tags that identify images associated with the page. This makes them easier to discover in Google Images when they’re loaded dynamically or hosted on a separate CDN. - The video sitemap uses the
<video:video>namespace to provide the duration, description, thumbnail, and player URL. This format targets Google Videos and the video section of search results. - The news sitemap (
<news:news>) is for news publishers included in Google News. It specifies the title, language, and publication date of recent articles (generally published within the last two days).
These extensions can be combined in one file or placed in dedicated sitemaps, depending on the volume of content. For a site that publishes both illustrated articles and videos, separating sitemaps by content type makes maintenance and tracking in Google Search Console easier.
Robots.txt and Search Console: submitting your sitemap to search engines
You can notify crawlers about an XML sitemap in two complementary ways. The first is to add the line Sitemap: https://example.com/sitemap.xml to the robots.txt file at the root of your site. All crawlers that support the protocol will detect this declaration automatically.
The second is to submit it directly through Google Search Console (or Bing Webmaster Tools). This method offers a practical advantage: the report shows the number of URLs submitted, the number indexed, and any errors found in the file. This is the only way to get explicit feedback from the search engine about the sitemap’s validity.
Using both approaches is standard practice. robots.txt enables passive discovery by all search engines, while Search Console provides the tracking data needed for troubleshooting.
A well-maintained XML sitemap remains a straightforward but foundational technical tool. It doesn’t change a page’s ranking; it makes the page easier to discover. Its value lies in keeping the file accurate: clean URLs, reliable dates, and no dead entries. The rest comes down to internal linking and content quality.
