An XML sitemap does not guarantee the crawling, indexing, or ranking of a URL. We regularly observe sites that submit a large sitemap file to Google Search Console without seeing any improvement in their visibility. The sitemap remains a tool for URL discovery, not a positioning lever. Understanding this distinction changes the way we build and maintain this file.
XML Sitemap and URL Governance: Filter Before Submitting
The common reflex is to generate an automatic sitemap that lists all the URLs of the site. This is a technical mistake. An effective sitemap contains only canonical, indexable URLs without redirection.
Further reading : Everything You Need to Know About the Legal Steps and Obligations of Online Self-Entrepreneurs
In practice, we recommend systematically excluding the following pages from the file:
- URLs with 301 or 302 redirection, which point to another destination and pollute the crawl budget
- Pages returning a 404 or 410 code, indicating deleted content that the bot does not need to revisit
- Non-canonical versions (pages with UTM parameters, sorting variants, duplicate paginations) that conflict with the canonical tag
- Pages protected by a noindex, as their presence in the sitemap sends a contradictory signal to the search engine
This logic transforms the sitemap into a URL governance tool rather than a simple inventory. On an e-commerce site with thousands of product listings, the gain in crawl efficiency is measurable in the Search Console exploration reports. You can observe the difference by consulting the sitemap of Communisation, which illustrates a structured file with filtered URLs.
See also : Origin, history, and meanings: everything you need to know about the name Lisa
Native WordPress Sitemap or SEO Plugin: What Technical Choice
Since WordPress 5.5, the CMS generates a native XML sitemap accessible at /wp-sitemap.xml. This built-in feature covers posts, pages, and basic taxonomies.
The native sitemap has a clear limitation: it does not manage images, videos, or granular URL exclusions. For a simple blog with a few dozen pages, it is sufficient. As soon as the site incorporates multimedia content or exceeds a few hundred URLs, an SEO plugin (Yoast, Rank Math, SEOPress) takes over with a more comprehensive sitemap.
We observe a common trap: allowing the native sitemap and the SEO plugin sitemap to coexist. Both files are then submitted to Google, which can generate duplicates in the index. The solution is to disable the native WordPress sitemap via a filter in the functions.php file or through an option in the plugin.
Video Sitemaps and Google News: Two Distinct Use Cases
General articles on sitemaps rarely address specialized formats. A video sitemap and a Google News sitemap serve different technical needs than the classic XML sitemap.
Video Sitemap for Multimedia SEO
A video sitemap declares specific metadata: title, description, thumbnail URL, duration, publication date. This information allows Google to display video content in the Videos tab of search results and in rich snippets.
Without this dedicated sitemap, the crawling of embedded videos depends entirely on JavaScript rendering, which slows down their discovery, especially if they are hosted on a third-party platform.
Google News Sitemap
A site listed in Google News must provide a specific sitemap containing only articles published in the last two days. This file uses the news namespace and includes the article title, language, and publication date.
Mixing news articles with permanent pages in a single sitemap file dilutes the signal sent to the News crawler. Separating the files is a practice we apply across all editorial sites.
Submitting and Monitoring a Sitemap in Google Search Console
Generating a clean sitemap is not enough. Submission in Google Search Console allows you to verify that the file is read correctly and that the URLs it contains are indeed processed.
After submission, the index coverage report displays three categories to monitor:
- Submitted and indexed URLs, which confirm that the sitemap fulfills its role of discovery
- Submitted but not indexed URLs, which signal a content quality issue, a conflicting canonical, or insufficient crawl budget
- Sitemap reading errors (invalid XML format, inaccessible URLs), which block the processing of the entire file
A persistent gap between submitted URLs and indexed URLs indicates that the sitemap contains pages that Google deems irrelevant. Cleaning the file by removing these URLs improves the reliability of the signal sent to the engine.
The robots.txt file must also declare the location of the sitemap via the Sitemap: directive, which many configurations omit. This declaration allows robots from all search engines (not just Google) to locate the file without going through Search Console or Bing Webmaster Tools.
A well-filtered, submitted, and regularly monitored sitemap remains one of the few technical tools with low maintenance costs and measurable returns in exploration reports. The difficulty is not in creating it, but in keeping it updated as the site evolves.