<priority>

The <priority> element is a hint to crawlers about a URL's importance relative to other URLs on the same site. The scale is 0.0 (least important) to 1.0 (most important). The default is 0.5.

It doesn't influence rankings

This is the single most-misunderstood field in the sitemap spec. <priority> does not affect search rankings or crawl priority for Google, and Google has confirmed this repeatedly:

• 2017 — John Mueller: "We ignore <priority>."
• 2023 — Search Central reaffirmed in their sitemaps doc.

Ranking is determined by content quality, links, user signals, and Core Web Vitals. Sitemap <priority> is not a ranking signal and never was.

Why it exists in the spec

The 2005 sitemap.org protocol was an attempt to standardize hints for crawlers. <priority> was meant as relative importance within your site — your homepage at 1.0, deep product pages at 0.3 — so a crawler with limited budget would visit the high-priority URLs first.

In practice, search engines built their own crawl scheduling from authority, internal linking, and click-through data. The field became inert almost immediately, and Google was open about ignoring it.

When you'd still set it

• Self-documentation. Some teams use <priority> as a way to flag canonical/important pages in their own audits.
• Niche crawlers. Same caveat as <changefreq> — some smaller search engines and archivers read it literally.

Common mistakes

• Setting every page to 1.0. Defeats the (already-irrelevant) purpose. Treat it like a budget: if you must set it, 1.0 should be one or two URLs, not all of them.
• Believing it boosts rankings. It doesn't. Time spent computing <priority> is better spent on <lastmod> accuracy.
• Conflating crawl priority with ranking. Even if <priority> affected crawl scheduling (it doesn't), being crawled more often doesn't make a page rank higher.

What SitemapHost does

SitemapHost does not emit <priority> by default. The XML schema accepts it if you explicitly pass it, but we don't infer or fabricate values.