Does the order of URLs and priority in XML sitemaps really affect Google's crawling?

What makes Google's clarification challenge years of SEO practices?

The XML sitemap is often viewed as a fine-tuning lever — a file where every detail counts. For years, SEOs have carefully ordered their URLs by supposed importance, placing strategic pages at the top of the list, and assigning priority values between 0.0 and 1.0 in the hope of influencing Googlebot's behavior.

John Mueller cuts through this illusion. The order in which you list your URLs? Google doesn't care. The priority value you assign to each URL? Same. What really matters in determining crawl frequency is Google's internal algorithm — not your suggestions in an XML file.

How does Google really decide which pages to crawl first?

Google uses a set of internal signals far more sophisticated than what you can express in a sitemap. Internal PageRank, content freshness, the actual popularity of pages (measured by internal and external links), modification history, observed update rates — these are what truly drive crawl budget.

Your sitemap remains useful, but its role is strictly declarative: to inform Google about which URLs exist, along with their last modified dates. That's all. It's not a prioritization tool; it's an inventory. Google discovers the URLs and then applies its own crawling logic, independent of what you've written in the file.

Does the lastmod parameter have any real influence?

Unlike priority, lastmod (last modified date) is used by Google — but with caution. If your dates are consistent and reliable, they help Googlebot identify recently updated pages that may deserve a quick recrawl. But be careful: if you systematically lie by updating lastmod when the content hasn't changed, Google will eventually ignore this signal too.

This is the subtlety: Google only trusts the sitemap indications if they reflect reality. A lastmod that jumps every day on a static page? You lose the algorithm's trust. An artificially inflated priority? It never served any purpose anyway.

• The order of URLs in the XML sitemap has no influence on Google's crawling.
• The priority parameter is not taken into account by Google to determine crawl frequency.
• Lastmod can be used, but only if your data is reliably consistent over time.
• Google relies on its own internal signals (PageRank, freshness, popularity) to drive the crawl.
• The sitemap remains useful as a declarative inventory, not as a prioritization tool.

Is this statement consistent with field observations?

Yes, absolutely. For years, empirical tests have shown that changing the order of URLs in a sitemap does not alter the observable crawl behavior in logs. Deep pages with poor linking remain scarcely crawled even if you place them at the top of the sitemap, while popular pages with good internal linking are crawled frequently regardless of their position in the XML file.

Priority, on the other hand, has always been a folkloric parameter. Many CMS platforms automatically generate it with arbitrary values — which speaks volumes about its real relevance. If Google really used it, we would observe clear correlations between high priority and crawl frequency. Spoiler: they do not exist. [Verified] through the analysis of millions of log lines across various sites.

What nuances should we add to this claim?

Mueller's statement is clear, but it overlooks a crucial point: the sitemap does influence initial discovery. A URL that is absent from your internal linking but present in the sitemap can be indexed thanks to the latter. In this case, the order still doesn't matter, but the mere presence in the file makes a difference.

Another nuance: Google may use other information from the sitemap besides priority or order — particularly hreflang tags in multilingual sitemaps, or structured data for video and image sitemaps. These elements are taken into account. So don't throw the baby out with the bathwater: a well-structured sitemap remains an asset, just not for the reasons we once believed.

In what cases might this rule seem not to apply?

On sites with a very large crawl budget limitation (millions of pages, low authority), some SEOs have observed that submitting separate sitemaps for different sections of the site seemed to influence the crawl. Be careful: it's not the order or priority that matters, it's the act of segmenting information into several more digestible files and strategically submitting certain sitemaps via Search Console at the right time.

In these cases, what changes the game is the freshness of the submitted file (which can trigger a recrawl), not the internal hierarchy of the XML. It's a matter of timing and segmentation, not of assigned priority. [To be confirmed] with your own logs if you're in this limited crawl scenario — but don’t confuse correlation with causation.

What should you do with your XML sitemaps today?

Stop wasting time on the order of URLs and priority values. Focus on the quality and accuracy of your sitemap: only list indexable URLs (200, canonical to themselves), exclude duplicates, redirects, pages blocked by robots.txt or noindex. A clean sitemap is worth more than a fanciful "optimized" sitemap.

Ensure that your lastmod dates reflect actual content modifications. If you can't guarantee the reliability of this data, it's better to omit it than to lie. Google prefers the absence of information to misleading information that will end up being ignored anyway.

What mistakes should you absolutely avoid in managing your sitemaps?

Do not multiply sitemaps unnecessarily thinking it improves crawling. A single well-organized sitemap of 50,000 URLs is preferable to 10 poorly maintained sitemaps of 5,000 URLs. Segmentation only makes sense if it meets a clear editorial logic (by language, by content type) or a technical constraint (limit of 50,000 URLs).

Avoid including non-canonical URLs, paginated pages without added value, or URLs with superfluous parameters. Every URL in your sitemap should be a page you want to see indexed — not a comprehensive inventory of all the technically accessible URLs on the site. Quality > Quantity.

How can you check if your sitemap is really useful to Google?

Analyze your server logs to see which URLs from the sitemap are actually crawled and how often. If certain sections of your sitemap are never visited by Googlebot, that's a signal: either these pages lack internal signals (links, freshness), or they are not of interest to Google. The sitemap will not save them.

Compare the coverage rate between URLs submitted via sitemap and URLs discovered through natural crawling. If your internal linking is solid, the two lists should largely overlap. If the sitemap uncovers many orphan pages, it's your site architecture that needs reworking, not your XML file.

• Only list indexable URLs: 200, canonical to themselves, accessible.
• Exclude all redirects, blocked pages, duplicate or low-value content.
• Only use lastmod if you can guarantee its reliability over time.
• Segment your sitemaps by editorial logic or language, not to "optimize" crawling.
• Regularly analyze your logs to identify which submitted URLs are actually crawled.
• Prioritize fixing your internal linking if the sitemap reveals too many orphan pages.