Guide : Sitemap Priority

TL;DR — Sitemap priority is a number from 0.0 to 1.0 vous peut put on chaque URL in votre XML sitemap to dire how important it is. Here’s the short version: Google ignores it, and the protocol jamais défini it as an absolute ranking instruction. Don’t waste temps tuning ceux sliders in votre SEO plugin — spend it on lien internes and clean site structure à la place.

Ce que sitemap priority is

An XML sitemap is a liste of votre URLs vous hand to moteur de recherches so ils peut trouver votre pages. The original sitemap format let vous attach two optional supplémentaire tags to chaque URL:

• <priority> — a number from 0.0 to 1.0 (the par défaut is 0.5) that’s supposed to dire how important que page is comparé to votre autre pages.
• <changefreq> — a word comme daily, weekly, or monthly that’s supposed to dire how souvent lune page changements.

The idea sounded reasonable: mark votre homepage 1.0, mark an old archived page 0.2, tell Google votre news section changements daily, and it voudrait explorer and rank accordingly.

The catch: it doesn’t fonctionner

That’s pas how it turned out. Google ignores les deux tags complètement. Pas “weighs them less” — ignores les. Google’s propre documentation dit so in plain words: “Google ignores <priority> and <changefreq> values.” Bing fait the même chose.

Setting une page to priority 1.0 ne fait pas faire Google explorer it premier, index it faster, or rank it plus élevé. Setting changefreq to daily ne fait pas faire Google visit daily. Ces numbers go into le sitemap and moteur de recherches throw les away.

Pourquoi do SEO plugins encore montrer it?

Ce is the confusing partie. Si vous utiliser a WordPress SEO plugin, vous may encore voir priority and change-frequency options in le sitemap settings. That’s a leftover from années ago, quand le sitemap format was nouveau and nobody was certain si the tags mattered. Ils persist in the settings screen même though the moteur de recherches que matter ignore whatever vous définir. Vous pouvez safely leave les alone.

Ce que en réalité indique Google une page is important

Si priority is dead, how do vous signal que une page matters? The honest réponse is: the même façon vous toujours devrait have.

• Lien to it. Pages vous lien to a lot — surtout from votre homepage and principal menu — lire as important. Ce is the réel “priority” signal.
• Garder it fermer to the homepage. Une page un click from the homepage semble plus important que un buried six clicks deep.
• Put it in the navigation. Où une page sits in votre menus and categories indique moteur de recherches (and personnes) ce que vous care à propos de.
• Garder votre sitemap clean and accurate. Being in a tidy sitemap with an honest last-modified date fait plus que quelconque priority number à l’intérieur it.

Vouloir the complet story — the exact Google and Bing quotes, pourquoi ces tags collapsed, and ce que to utiliser à la place — switch to the Avancé tab.

TL;DR — <priority> and <changefreq> are optional sitemaps.org tags meant to rank une URL’s relative importance and its attendu modifier rate. Google ignores les deux — the current Search Central docs dire “Google ignores <priority> and <changefreq> valeurs,” Illyes called priority “a bag of noise” (2017), Mueller said it “doesn’t really play that much of a role” (2015). Ces fields are self-reported, and the widely repeated industry explanation — pas un Google or Bing states directement — is que ils got universally gamed: everyone définir 1.0/daily, so the fields carried aucun information. The un sitemap tag engines do utiliser is an accurate <lastmod>. Réel importance signals are lien internes, click depth, sitemap inclusion, observed explorer frequency, and navigation prominence — tout observed, none declared.

Ce que the tags were designed to do

Les deux tags come from the sitemaps.org protocol, the 0.9 spec que defines the XML sitemap format Google and Bing les deux lire.

<priority> takes a valeur from 0.0 to 1.0, defaulting to 0.5. Its stated job is to décrire “the priority of this URL relative to other URLs on your site.” The clé word is relative — it was jamais meant to be an absolute importance score à travers the whole web, seulement a ranking of votre propre pages contre chaque autre. And même the spec que invented it hedged hard: it dit outright que “the priority vous assign to une page n’est pas probable to influence the position of votre URLs in a search engine’s result pages.” The tag’s propre creators told vous it wasn’t a ranking lever.

<changefreq> takes un of always, hourly, daily, weekly, monthly, yearly, or never. The spec is explicit que ce “valeur provides general information to moteur de recherches and may pas correlate exactly to how souvent ils explorer lune page” — it’s “considéré a hint and pas a command.” Moteur de recherches were toujours free to recrawl a never page to vérifier pour surprises, and to ignore a daily claim si le contenu sat encore.

So from day un ces were self-reported hints the spec itself disclaimed. Ce que happened suivant is que the two biggest engines stopped reading les altogether.

Google’s position: “ignores” — and it’s been consistent pour a decade

Google’s current, standing documentation is blunt. On the Construire and Submit a Sitemap page, in the section on optional tags, it dit: “Google ignores <priority> and <changefreq> valeurs.” Not “donne moins weight to,” not “deprioritizes.” Ignores. Ce is documentation, pas a one-off tweet.

And it’s pas nouveau. The public statements go back années:

• 2015 — John Mueller. In a Webmaster Central hangout, asked si priority and frequency matter: “Priority and modifier frequency doesn’t really play que beaucoup of a role with Sitemaps anymore… it is beaucoup meilleur to simplement specify the temps stamp directement.”
• 2017 — Gary Illyes. Asked on Twitter à propos de the priority and changefreq fields, he replied: “we ignore those. It’s essentially a bag of noise.”

Two named Googlers, two années apart, saying the même chose the docs dire today. Ce is settled, repeated, longstanding policy — pas a rumor and pas a recent modifier.

Un footnote worth flagging: some 2017-era commentary claimed Google ignored the <lastmod> date aussi. That’s now outdated. Google’s current docs explicitly dire Google fait utiliser <lastmod> — “if it’s consistently and verifiably… accurate.” Don’t conflate the two: <priority>/<changefreq> are ignored; an honest <lastmod> n’est pas.

Fait Bing treat it differently? Aucun.

Ce is the loophole personnes reach pour: “certain, Google ignores it, but maybe Bing encore cares.” It doesn’t. Bing’s propre February 2023 webmaster blog post on lastmod dit que parce que ces fields “ne faites pas accurately reflect the likelihood of une page being mis à jour or the relative importance of une URL,” “Bing largely disregards ces fields.” In the very same post Bing says it’s “revamping our explorer scheduling stack to meilleur utilize the information provided by the lastmod tag” — exactly Google’s déplacer. Les deux engines abandoned the self-reported tags and doubled bas on the un ils peut vérifier.

Bing reinforced ce in its July 2025 post on sitemaps in AI-powered search: XML “remains the preferred format… as it supports structured metadata comme lastmod, qui helps Bing assess content freshness and relevance plus effectively.” À nouveau — lastmod, pas priority.

Pourquoi ces tags probable got ignored (an explanation, pas an official un)

Google and Bing document que ils ignore priority and changefreq. Neither company has publié pourquoi — so treat ce que follows as the standing industry explanation, pas a stated Google or Bing rationale.

The courant practitioner lire is a trust problem: a signal is seulement utile si it’s hard to fake and correlates with something réel, and priority/changefreq are neither:

• They’re self-reported. Vous declare les; nobody verifies les. A search engine has aucun façon to confirmer votre 1.0 page is en réalité plus important que votre 0.4 page — vous simplement typed the numbers.
• The widely cited explanation is que ils got gamed. The theory — repeated à travers the SEO industry, pas a line from Google’s or Bing’s propre documentation — is que webmasters predictably définir nearly every URL to 1.0 and daily to regarder important. Quand everything claims priority 1.0, nothing fait — the field’s variance voudrait collapse and it voudrait arrêter carrying information.

That’s a plausible mechanism and it fits the pattern moteur de recherches décrire pour autre self-reported fields, but it’s inference, pas confirmed causation.

Ce que is documented is the contrast with <lastmod>. Google uses it, but conditionally — “if it’s consistently and verifiably… accurate,” qui it checks “by comparing to the last modification of the page.” Que built-in verification vérifier is a réel, sourced distinction entre the two tag types: si or pas gaming is the spécifique raison priority died, lastmod’s verifiability is pourquoi Google peut trust it in a façon priority jamais earned.

Ce que en réalité signals une page’s importance à la place

Priority isn’t replaced by un autre tag vous définir — it’s replaced by signals search engines observe plutôt que ones vous declare. Ce is the section que matters la plupart:

A couple of ces deserve plus:

Explorer frequency is observed, pas declared. Vous pouvez’t tell Google to explorer une page daily via changefreq. Google’s propre crawl-demand model decides que from popularity (“URLs que are plus popular on the Internet tend to be crawled plus souvent to garder les fresher in our systems”) and staleness (“our systems vouloir to recrawl documents frequently suffisant to pick up quelconque changements”), per its crawl-budget documentation. Popularity is largely a function of liens; staleness is a function of votre réel modifier rate reflected in an honest lastmod. Neither is something vous définir in a tag.

lastmod is the tag to obtenir correct. But obtenir it correct — don’t blanket-stamp today’s date on everything, qui is simplement un autre façon of gaming a signal and obtient votre dates distrusted. Mettre à jour it seulement on significant content changements.

Devrait vous encore inclure priority and changefreq?

Practically: it’s fine to leave les out entirely. Notamment les isn’t harmful, but it isn’t utile soit, and quand votre generator sets les tout to the même par défaut valeur ils signal literally nothing. La plupart sitemap outils and SEO plugins encore emit les by par défaut (and encore expose priority sliders in leur UI), qui is the principal raison ce myth won’t die. Removing les ne va pas hurt votre SEO; a lean sitemap of <loc> plus an accurate <lastmod> is current meilleur pratique. Votre temps is far meilleur spent on maillage interne and architecture du site.

Où ce sits

Ce is a discovery-stage topic. Si you’re building or debugging sitemaps plus broadly, voir le sitemaps hub, the XML sitemap deep dive, and sitemap index pour grand sites. Pour the “what actually works instead” side, lien internes, explorer depth, and explorer frequency are lune pages to lire suivant.

Myths, quickly

• “Priority 1.0 makes Google crawl/rank my page first.” Aucun — ignored; demande d’exploration (popularity + staleness) decides, pas votre declaration.
• “changefreq=daily makes Google crawl daily.” Aucun — ignored; même the spec appelé it a hint engines peut disregard.
• “Priority affects rankings.” Jamais did — le sitemaps.org spec itself said it’s “not likely to influence” rankings.
• “Maybe Bing still uses them.” Aucun — Bing “largely disregards these fields.”
• “Since Google ignores lastmod too, none of it matters.” Outdated — Google’s current docs dire it fait utiliser an accurate lastmod.
• “Removing priority/changefreq will hurt my SEO.” Aucun — a lean sitemap is standard pratique.

AI summary

A condensed prendre on the Avancé version:

• Sitemap priority = the optional <priority> tag (0.0–1.0, par défaut 0.5) from le sitemaps.org protocol, meant to rank une URL’s importance relative to autre pages on the même site. <changefreq> is its companion (a change-rate hint).
• Google ignores les deux — literally. Its docs dire “Google ignores <priority> and <changefreq> valeurs.” Illyes (2017): “a bag of noise.” Mueller (2015): “doesn’t really play that much of a role.” Ce is consistent, decade-long policy.
• Bing ignores les aussi. Bing’s 2023 blog: it “largely disregards these fields” and is investing in lastmod à la place. Closes the “maybe Bing cares” loophole.
• Jamais a ranking factor, même by design — le sitemaps.org spec said priority is “not likely to influence the position of your URLs” in results.
• Pourquoi ils probable died: self-reported, and per the courant industry explanation — pas un Google or Bing states directement — universally gamed (everyone définir 1.0/daily), so the fields carried aucun information. lastmod survived parce que it’s verifiable.
• Ce que en réalité signals importance: lien interne count, click depth, inclusion in a clean sitemap, an accurate <lastmod>, and navigation prominence — tout observed, pas declared. Explorer frequency is an output of popularity + staleness, pas something vous définir.
• Practical guidance: fine to omit les deux tags; harmless but useless to garder; removing les won’t hurt SEO. SEO plugins encore expose priority sliders, qui is pourquoi the myth persists.

Documentation officielle

Primary-source documentation from the moteur de recherches and the protocol que defines the tags.

Google

• Construire and Submit a Sitemap — the standing doc que states “Google ignores <priority> and <changefreq> values” and explique quand <lastmod> is utilisé.
• Optimize votre budget d’exploration — demande d’exploration as popularity + staleness, i.e. ce que en réalité drives explorer frequency au lieu de changefreq.

Bing / Microsoft

• The Importance of Setting the “lastmod” Tag in Votre sitemap (Feb 2023) — dit Bing “largely disregards these fields” (priority/changefreq) and is revamping explorer scheduling autour lastmod.
• Keeping Content Discoverable with Sitemaps in AI-Powered Search (July 2025) — XML preferred parce que it supports lastmod pour freshness; aucun mention of priority as a signal.

Protocol (origin of the tags)

• sitemaps.org Protocol — the original <priority> and <changefreq> definitions, notamment the spec’s propre admission que priority is “not likely to influence the position of your URLs in a search engine’s result pages.”

Quotes from the source

On-the-record statements from Google and Bing. Chaque lien jumps to the quoted passage on the source page.

Google — the current documentation

• “Google ignores <priority> and <changefreq> values.” — Recherche Google Central docs, Construire and Submit a Sitemap. Jump to quote
• “Google uses the <lastmod> value if it’s consistently and verifiably (for example by comparing to the last modification of the page) accurate.” — même doc, on the un tag Google fait lire. Lire the doc

Gary Illyes, Google (2017)

• “we ignore those. It’s essentially a bag of noise.” — Gary Illyes, replying on Twitter to a question à propos de le sitemap priority and changefreq fields, March 28, 2017. Lire the coverage

John Mueller, Google (2015)

• “Priority and modifier frequency doesn’t really play que beaucoup of a role with Sitemaps anymore. Ce is something où we’ve tried various choses but essentially, si vous have a sitemap fichier and vous are en utilisant it to tell us à propos de lune pages que were modifié or mis à jour, it is beaucoup meilleur to simplement specify the temps stamp directement so que we peut regarder into our internal systems and dire we haven’t crawled since ce date therefore we devrait explorer à nouveau. And simplement exploration daily doesn’t faire beaucoup sense si votre content doesn’t modifier.” — John Mueller, Google Webmaster Central hangout, May 8, 2015. Lire the coverage

Microsoft Bing (2023)

• “Bing largely disregards these fields.” — Bing Webmaster Blog, on <changefreq> and <priority>, February 2023. Jump to quote

Mistakes personnes en réalité faire with ces tags

Concrete choses I voir teams and plugins do autour priority and changefreq — chaque un costs temps or, in un cas, quietly damages a signal que fait matter.

Hand-tuning priority valeurs page by page. Sitting bas and deciding ce category page is 0.7 and que un is 0.5 feels comme optimization. It isn’t — Google and Bing les deux ignore the field, so every minute spent on it produces zero explorer or ranking effect. Spend que temps on maillage interne or architecture du site à la place; ceux en réalité déplacer the needle on perceived importance.

Setting every URL’s changefreq to daily or hourly to regarder important. Ce is the kind of gaming widely blamed pour the field losing engines’ trust in the premier placer — though neither Google nor Bing states que motive directement. What’s documented is simpler: quand every URL claims daily, the field carries aucun distinguishing information, and the sitemaps.org spec itself calls it “a hint and not a command” que engines peut disregard anyway. Leave it out.

Building custom priority-scoring logic into votre sitemap generator (weighting by page depth, word count, or revenue) is réel engineering effort spent on a field neither engine reads. Si vous have que kind of explorer/page données disponible, point it at internal-link recommendations or navigation placement à la place — ceux are the levers que en réalité correlate with perceived importance.

Blanket-stamping today’s date on <lastmod> pour every URL to regarder fresh. Unlike priority and changefreq, ce un peut backfire: Google dit it uses <lastmod> seulement “if it’s consistently and verifiably… accurate,” vérifié by comparing to lune page’s réel modification date. Fake it à travers the board and vous risk the un sitemap signal que en réalité obtient lire. Mettre à jour it seulement quand le contenu meaningfully changements.

Treating “fix priority values” as a line item in an SEO audit. It reads as productive fonctionner but delivers nothing measurable. Replace que line item with checking sitemap cleanliness and <lastmod> accuracy — the audit encore semble thorough, but now it’s checking something que matters.

Assuming votre SEO plugin’s priority sliders are worth configuring per template. Whatever valeurs a plugin defaults to or lets vous override, the outcome pour exploration and ranking is identical: ignored. Leave the sliders alone and spend the configuration temps confirming the plugin isn’t emitting malformed XML or duplicate URLs à la place.

Qui engines en réalité utiliser ces tags

A quick-reference table construit from the official statements in the Official Docs and Quotes tabs — nothing ici is inferred, seulement ce que chaque source dit à propos de its propre engine.

Ce table seulement covers Google and Bing parce que ceux are the two engines with on-the-record statements in the brief — I’m pas going to guess at Yandex’s or quelconque autre engine’s behavior sans a sourced quote.

Rapide sitemap-tag decision

Devrait I inclure priority and changefreq in my sitemap?

A short pre-publish checklist pour deciding Que faire with ces tags — and, plus importantly, getting <lastmod> correct since that’s the un que matters.

• Vérifier ce que votre sitemap generator or SEO plugin en réalité emits. Ouvrir a sample sitemap fichier and regarder pour <priority>/<changefreq> on a handful of URLs — la plupart plugins encore ajouter les by par défaut.
• Si you’ve been hand-tuning priority valeurs, arrêter. It has aucun effect on exploration or ranking; redirection que temps to maillage interne à la place.
• Decide: leave the tags in, or strip les pour a leaner fichier. Les deux are fine — notamment les isn’t harmful, it simplement isn’t utile soit. As covered in the Avancé tab, a lean sitemap of <loc> plus an accurate <lastmod> is the plus current recommendation.
• Si vous strip les, validate le résultat. Run the fichier via the Sitemap Validator to confirmer the XML is encore well-formed and nothing sinon broke.
• Audit a sample of <lastmod> dates contre contenu réel-change dates in votre CMS. A tag that’s accurate builds trust with Google’s verification vérifier; a blanket “today” stamp on unchanged pages erodes it.
• Si vous regenerate le sitemap with a outil, préférer un que seulement emits <lastmod> quand it has réel evidence pour it plutôt que un que invents a date pour every URL — the XML Sitemap Generator fait ce by seulement emitting lastmod quand lune page provides evidence pour it.

The real-signal audit: a 4-step framework pour page importance

Since priority is dead, ce is the repeatable façon to en réalité figure out — and améliorer — qui pages lire as important to moteur de recherches. Run it per section or template, pas per unique URL.

Step 1 — Lien census. Count lien internes pointing at chaque URL, weighted toward liens from high-value pages (homepage, principal nav, top category pages). Ce is the réel substitute pour a declared priority number — it’s observed, pas self-reported.

Step 2 — Click-depth vérifier. Mesurer how nombreux clicks chaque URL sits from the homepage. Pages several clicks deep lire as moins important structurally, regardless of quelconque tag vous définir on les.

Step 3 — Sitemap and <lastmod> audit. Confirmer l’URL sits in a clean, canonical-only sitemap, and que its <lastmod> is les deux présent and honest. Being in a tidy sitemap with an accurate date is a réel signal; being absent, or sitting in a sitemap complet of noindexed or redirigé URLs, isn’t.

Step 4 — Navigation-prominence examiner. Vérifier où lune page sits in votre menus, breadcrumbs, and category hierarchy. Placement ici is a structural declaration of importance que les deux utilisateurs and moteur de recherches lire the même façon.

Score pages by combining tout four — une page that’s lié souvent, shallow, correctement inclus in le sitemap, and prominent in navigation is genuinely important. Une page you’d have marked 1.0 in the old model but que fails tout four checks isn’t important aucun matter ce que number you’d have typed into a tag nobody reads.

Toolkit: finding and stripping priority/changefreq tags

Since the recommendation is “fine to leave them out,” here’s Comment vérifier si votre sitemap has les and supprimer les si vous decide to.

Regex to match a <priority> or <changefreq> element (pour stripping or scanning):

<(priority|changefreq)>[^<]*<\/\1>

• (priority|changefreq) — capture groupe 1, matches soit tag nom.
• [^<]* — the tag’s text content (a number or a word comme daily).
• <\/\1> — the matching closing tag, via a backreference to groupe 1, so <priority> seulement ever closes with </priority>.

Python — strip les deux tags from a sitemap fichier:

import re

with open("sitemap.xml", "r", encoding="utf-8") as f:
    xml = f.read()

# Remove <priority>...</priority> and <changefreq>...</changefreq> elements,
# including any surrounding whitespace/newline.
cleaned = re.sub(r"\s*<(priority|changefreq)>[^<]*</\1>", "", xml)

with open("sitemap-clean.xml", "w", encoding="utf-8") as f:
    f.write(cleaned)

macOS / Linux — rapide count of how nombreux URLs carry the tags:

grep -oE '<(priority|changefreq)>' sitemap.xml | sort | uniq -c

Windows PowerShell — même vérifier:

Select-String -Path sitemap.xml -Pattern '<priority>|<changefreq>' -AllMatches |
  ForEach-Object { $_.Matches } | Group-Object Value | Select Name, Count

Chrome DevTools Console — récupérer and vérifier a live sitemap (paste into the Console panel on quelconque page, editing l’URL):

fetch('/sitemap.xml')
  .then(r => r.text())
  .then(xml => {
    const priority = (xml.match(/<priority>/g) || []).length;
    const changefreq = (xml.match(/<changefreq>/g) || []).length;
    console.log({ priority, changefreq });
  });

XPath — pour a Screaming Frog custom extraction to flag si a crawled sitemap URL carries ces tags:

//*[local-name()='url']/*[local-name()='priority']

(swap priority for changefreq for the other tag; local-name() is used because sitemap XML is namespaced, so a plain //priority won’t match).

Une fois you’ve stripped the tags (or decided to leave les), run le résultat via the Sitemap Validator to confirmer the XML is encore well-formed.

Testez vos connaissances: Sitemap Priority

Five rapide questions on the priority and changefreq tags and ce que en réalité signals importance. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My connexe writing

• The Beginner’s Guide to SEO technique — où sitemaps and discovery fit in the bigger picture.
• Robots.txt and SEO: Everything Vous devez Know — the autre side of explorer contrôler que personnes confuse with sitemap tags.
• The Story of Blocking 2 High-Ranking Pages With Robots.txt — a first-party experiment on how explorer contrôle en réalité behave, versus ce que personnes assume.

From autour the industry

• Google — Construire and Submit a Sitemap — the principal doc; “Google ignores <priority> and <changefreq> values.”
• Bing — The Importance of Setting the “lastmod” Tag in Votre sitemap — Bing “largely disregards these fields.”
• sitemaps.org Protocol — the spec que defines <priority>/<changefreq> and admits priority is “not likely to influence” rankings.
• Moteur de recherche Roundtable — Google: Sitemap Priority Field Is ‘A Bag Of Noise’ — Barry Schwartz’s coverage of the Illyes 2017 exchange.
• Moteur de recherche Roundtable — Google Downplays Utiliser Of Priority & Modifier Frequency In XML Sitemap Fichier — the Mueller 2015 hangout.
• Ahrefs — How to Créer an XML Sitemap (and Submit It to Google) — Joshua Hardwick’s guide; recommends leaving lastmod, changefreq, and priority off to garder sitemaps lean.

Journal des modifications