Sitemap Priority

What the sitemap priority tag is, why Google and Bing both ignore priority and changefreq entirely, and what actually signals a page's importance to search engines instead.

First published: Jul 2, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #5 in Discovery#25 in How Search Works#142 in Technical SEO#194 on the site
1 evidence signal on this page

Sitemap priority is the optional <priority> tag (0.0–1.0, default 0.5) in the sitemaps.org protocol, meant to rank a URL's importance relative to other pages on the same site. Google ignores it — its own docs say 'Google ignores <priority> and <changefreq> values,' Gary Illyes called priority 'a bag of noise,' and John Mueller said it 'doesn't really play that much of a role.' Bing 'largely disregards these fields' too. Even the sitemaps.org spec said priority was 'not likely to influence' rankings. Neither company states why they stopped reading them; the common industry explanation is that the values are self-reported and everyone set everything to 1.0/daily, making them statistically useless. What actually signals importance instead: internal link count and depth, inclusion in a clean sitemap with an accurate <lastmod>, observed crawl frequency in your logs, and navigation prominence. It's fine to leave both tags out of your sitemap entirely.

TL;DR — <priority> and <changefreq> are optional sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing..org tags meant to rank a URL’s relative importance and its expected change rate. Google ignores both — the current Search Central docs say “Google ignores <priority> and <changefreq> values,” Illyes called priority “a bag of noise” (2017), Mueller said it “doesn’t really play that much of a role” (2015). These fields are self-reported, and the widely repeated industry explanation — not one Google or Bing states directly — is that they got universally gamed: everyone set 1.0/daily, so the fields carried no information. The one sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. tag engines do use is an accurate <lastmod>. Real importance signals are internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., click depthCrawl depth usually means click depth — how many clicks it takes to reach a page from the homepage by following internal links. It can also mean a crawler setting that limits how many levels deep a crawl goes before it stops., sitemap inclusion, observed crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial., and navigation prominence — all observed, none declared.

Evidence for this claim The sitemap protocol defines optional priority and changefreq fields as hints relative to URLs on the same site. Scope: Sitemaps protocol semantics, independent of any engine's use. Confidence: high · Verified: Sitemaps XML format Evidence for this claim Google ignores sitemap priority and changefreq values and recommends accurate lastmod values when they can be maintained. Scope: Current Google sitemap field support. Confidence: high · Verified: Google Search Central: Build and submit a sitemap

What the tags were designed to do

Both tags come from the sitemaps.org protocol, the 0.9 spec that defines the XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. format Google and Bing both read.

<priority> takes a value from 0.0 to 1.0, defaulting to 0.5. Its stated job is to describe “the priority of this URL relative to other URLs on your site.” The key word is relative — it was never meant to be an absolute importance score across the whole web, only a ranking of your own pages against each other. And even the spec that invented it hedged hard: it says outright that “the priority you assign to a page is not likely to influence the position of your URLs in a search engine’s result pages.” The tag’s own creators told you it wasn’t a ranking lever.

<changefreq> takes one of always, hourly, daily, weekly, monthly, yearly, or never. The spec is explicit that this “value provides general information to search engines and may not correlate exactly to how often they crawl the page” — it’s “considered a hint and not a command.” Search engines were always free to recrawl a never page to check for surprises, and to ignore a daily claim if the content sat still.

So from day one these were self-reported hints the spec itself disclaimed. What happened next is that the two biggest engines stopped reading them altogether.

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

Google’s current, standing documentation is blunt. On the Build and Submit a Sitemap page, in the section on optional tags, it says: “Google ignores <priority> and <changefreq> values.” Not “gives less weight to,” not “deprioritizes.” Ignores. This is documentation, not a one-off tweet.

And it’s not new. The public statements go back years:

  • 2015 — John Mueller. In a Webmaster Central hangout, asked whether priority and frequency matter: “Priority and change frequency doesn’t really play that much of a role with Sitemaps anymore… it is much better to just specify the time stamp directly.”
  • 2017 — Gary Illyes. Asked on Twitter about the priority and changefreq fields, he replied: “we ignore those. It’s essentially a bag of noise.”

Two named Googlers, two years apart, saying the same thing the docs say today. This is settled, repeated, longstanding policy — not a rumor and not a recent change.

One footnote worth flagging: some 2017-era commentary claimed Google ignored the <lastmod> date too. That’s now outdated. Google’s current docs explicitly say Google does use <lastmod> — “if it’s consistently and verifiably… accurate.” Don’t conflate the two: <priority>/<changefreq> are ignored; an honest <lastmod> is not.

Does Bing treat it differently? No.

This is the loophole people reach for: “sure, Google ignores it, but maybe Bing still cares.” It doesn’t. Bing’s own February 2023 webmaster blog post on lastmod says that because these fields “do not accurately reflect the likelihood of a page being updated or the relative importance of a URL,” “Bing largely disregards these fields.” In the very same post Bing says it’s “revamping our crawl scheduling stack to better utilize the information provided by the lastmod tag” — exactly Google’s move. Both engines abandoned the self-reported tags and doubled down on the one they can verify.

Bing reinforced this in its July 2025 post on sitemaps in AI-powered search: XML “remains the preferred format… as it supports structured metadata like lastmod, which helps Bing assess content freshnessContent freshness is how recent or up-to-date a page is — by its original publish date, its last substantive revision, or the currency of the facts inside it. It only helps rankings when the query itself benefits from recent results (Query Deserves Freshness), and cosmetic date changes with no real update don't count. and relevance more effectively.” Again — lastmod, not priority.

Why these tags likely got ignored (an explanation, not an official one)

Google and Bing document that they ignore priority and changefreq. Neither company has published why — so treat what follows as the standing industry explanation, not a stated Google or Bing rationale.

The common practitioner read is a trust problem: a signal is only useful if it’s hard to fake and correlates with something real, and priority/changefreq are neither:

  • They’re self-reported. You declare them; nobody verifies them. A search engine has no way to confirm your 1.0 page is actually more important than your 0.4 page — you just typed the numbers.
  • The widely cited explanation is that they got gamed. The theory — repeated across the SEO industry, not a line from Google’s or Bing’s own documentation — is that webmasters predictably set nearly every URL to 1.0 and daily to look important. When everything claims priority 1.0, nothing does — the field’s variance would collapse and it would stop carrying information.

That’s a plausible mechanism and it fits the pattern search engines describe for other self-reported fields, but it’s inference, not confirmed causation.

What is documented is the contrast with <lastmod>. Google uses it, but conditionally — “if it’s consistently and verifiably… accurate,” which it checks “by comparing to the last modification of the page.” That built-in verification check is a real, sourced distinction between the two tag types: whether or not gaming is the specific reason priority died, lastmod’s verifiability is why Google can trust it in a way priority never earned.

What actually signals a page’s importance instead

Priority isn’t replaced by another tag you set — it’s replaced by signals search engines observe rather than ones you declare. This is the section that matters most:

SignalWorks?Why
Internal linkAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. countYesPages linked more often, from more places, read as more important. Real “priority.”
Click depth (distance from homepage)YesPages closer to the homepage are seen as more important and get crawled more readily.
Inclusion in a clean XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags.YesBeing in a tidy, canonical-only sitemap is the real signal — not any number inside it.
Accurate <lastmod>YesThe one sitemap tag engines use — but only when it’s verifiably honest.
Navigation / architecture prominenceYesPlacement in menus, breadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., and category hierarchy signals importance structurally.
Observed crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. (in logs)Reflects itHow often botsA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. actually recrawl a URL reflects perceived importance — it’s an output, not an input.
<priority> tagNoIgnored by Google and Bing. Self-reported, widely believed to be gamed into meaninglessness.
<changefreq> tagNoIgnored by Google and Bing. A “hint” both engines disregard.

A couple of these deserve more:

Crawl frequency is observed, not declared. You can’t tell Google to crawl a page daily via changefreq. Google’s own crawl-demand model decides that from popularity (“URLs that are more popular on the Internet tend to be crawled more often to keep them fresher in our systems”) and staleness (“our systems want to recrawl documents frequently enough to pick up any changes”), per its crawl-budget documentation. Popularity is largely a function of links; staleness is a function of your real change rate reflected in an honest lastmod. Neither is something you set in a tag.

lastmod is the tag to get right. But get it right — don’t blanket-stamp today’s date on everything, which is just another way of gaming a signal and gets your dates distrusted. Update it only on significant content changes.

TIP Validate the sitemap field that is still worth maintaining

The validator can catch malformed lastmod values and structural XML problems. It cannot determine whether a valid-looking date reflects a real, significant content change.

Paste or fetch the sitemap in my Sitemap Validator, fix invalid lastmod values, and remove ignored priority/changefreq clutter if it complicates the export. Sitemap Validator Free

  1. Validate XML structure, absolute loc values, and lastmod formatting.
  2. Compare valid dates with the pages’ actual meaningful changes.
  3. Keep the export lean and monitor whether search engines continue trusting the dates.
A formatted date is only the first gate; it must also be an honest modification date.

Should you still include priority and changefreq?

Practically: it’s fine to leave them out entirely. Including them isn’t harmful, but it isn’t helpful either, and when your generator sets them all to the same default value they signal literally nothing. Most sitemap tools and SEO plugins still emit them by default (and still expose priority sliders in their UI), which is the main reason this myth won’t die. Removing them will not hurt your SEO; a lean sitemap of <loc> plus an accurate <lastmod> is current best practice. Your time is far better spent on internal linkingLinks between pages on the same site. and site architectureSite architecture is how a website's pages are organized, categorized, and interlinked. It controls how crawlers discover pages, how link equity flows, and how clearly search engines understand each page's topical context. Silo structure, hub and spoke, and topic clusters are the three common models..

Where this sits

This is a discovery-stage topic. If you’re building or debugging sitemaps more broadly, see the sitemaps hub, the XML sitemap deep dive, and sitemap indexA sitemap index is a sitemap of sitemaps — a single file that lists your other sitemap files instead of listing URLs directly. It's how large sites stay under the 50,000-URL / 50MB-per-sitemap limit while submitting just one file. for large sites. For the “what actually works instead” side, internal links, crawl depth, and crawl frequency are the pages to read next.

Myths, quickly

  • “Priority 1.0 makes Google crawl/rank my page first.” No — ignored; crawl demandCrawl demand is the 'want' side of crawl budget — how much a search engine wants to crawl a site or URL, driven by popularity, staleness, and perceived inventory (plus temporary spikes from site moves). It's distinct from crawl rate/capacity, the 'can' side. (popularity + staleness) decides, not your declaration.
  • changefreq=daily makes Google crawl daily.” No — ignored; even the spec called it a hint engines can disregard.
  • “Priority affects rankings.” Never did — the sitemaps.org spec itself said it’s “not likely to influence” rankings.
  • “Maybe Bing still uses them.” No — Bing “largely disregards these fields.”
  • “Since Google ignores lastmod too, none of it matters.” Outdated — Google’s current docs say it does use an accurate lastmod.
  • “Removing priority/changefreq will hurt my SEO.” No — a lean sitemap is standard practice.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.