Sitemap changefreq: What It Does and Whether Google Uses It

Is your sitemap configured correctly? Run a free analysis to check changefreq, lastmod, and every other signal Google uses.

What Is changefreq in a Sitemap?

The changefreq element is an optional tag in the XML Sitemap protocol. It is meant to give search engine crawlers a hint about how frequently a particular URL is likely to change. The idea is simple: if you tell Googlebot that your homepage changes hourly, it might visit more often than a blog post you published once and never touched again.

The sitemap specification defines seven valid values for changefreq, and they must be used exactly as listed — any other value is invalid and will be ignored by compliant crawlers:

• always — The page changes every time it is accessed (suitable for real-time feeds)
• hourly — The page changes multiple times per day
• daily — The page changes roughly once per day
• weekly — The page changes roughly once per week
• monthly — The page changes roughly once per month
• yearly — The page changes very rarely
• never — The page is archived and will never change (suitable for static PDFs or historical records)

The protocol specifies that changefreq is a hint, not a command. Crawlers are free to ignore it entirely. As we will see, Google does exactly that.

Does Google Use changefreq?

The short answer is: not meaningfully. Google's official documentation describes changefreq and priority as values that "might be ignored" by Google. In practice, Google's Search Advocate John Mueller has been more direct in public statements. He has confirmed on multiple occasions that Google mostly ignores changefreq and uses its own internal signals to make crawl scheduling decisions.

The reasoning makes sense when you think about Google's scale. Google crawls billions of URLs across the web. It cannot afford to trust every webmaster's self-reported update frequency — that information is too easily manipulated and too often wrong. Instead, Google has built sophisticated models that predict how often a page is likely to change based on actual observed behavior over time.

Setting changefreq to "daily" on every page of your site — a common SEO cargo-cult practice — will not result in daily crawls. Google's systems will observe how often your content actually changes and schedule crawls accordingly, regardless of what your sitemap says.

What Actually Controls Crawl Frequency

If Google ignores changefreq, what does it use instead? Several real signals determine how often Googlebot visits your pages:

Page popularity and traffic signals. Pages that receive a lot of clicks from Google Search are crawled more frequently. Google infers that popular pages matter more and that keeping them fresh benefits users.

Link authority and PageRank. Pages with many high-quality inbound links — both internal and external — are crawled more often. Authority is a strong proxy for importance.

Historical update patterns. Google remembers how often a page has changed in the past. If your category page consistently updates every weekday, Googlebot will learn that pattern and schedule recrawls accordingly. This is far more reliable than any sitemap hint.

Crawl budget allocation. Googlebot allocates a crawl budget to each site based on server response time, site health, and overall authority. Pages that load slowly, return errors frequently, or live on low-authority domains get crawled less often regardless of any sitemap settings.

Accurate lastmod dates. When you provide a lastmod value in your sitemap and it accurately reflects when the page was meaningfully updated, Google uses it. A real content update signals that recrawling is worthwhile.

The changefreq Values Explained

Even if Google largely ignores them, it helps to understand what each value is designed to communicate so you can make informed decisions about whether to include them.

When changefreq Can Still Help

Google is not the only crawler that reads your sitemap. Bing, Yandex, DuckDuckGo (which uses Bing's index), and various smaller search engines also process sitemaps — and some of them may honor changefreq more literally than Google does.

If your site has significant traffic from Bing or is targeting markets where Yandex is relevant (Russia, Eastern Europe), a thoughtfully set changefreq may provide a marginal crawl benefit from those engines. It is a low-cost signal to include if accuracy matters.

For brand new sites with no established crawl history, any hint that helps crawlers understand your site's update cadence could theoretically help during the initial discovery phase. That said, the benefit is speculative and should not be prioritized over more impactful SEO work.

changefreq vs lastmod: Which Matters More

This is the most important comparison to understand. While Google ignores changefreq, it does pay attention to lastmod — but only when the dates are accurate.

When Google sees a lastmod date that is more recent than its last crawl of that URL, it treats that as a signal that recrawling is worthwhile. John Mueller has confirmed this behavior: accurate lastmod dates help Google understand which pages have been updated and are therefore higher priority for recrawling.

The critical word is accurate. Many CMS platforms automatically update lastmod on every sitemap regeneration, even for pages that have not changed. This pollutes the signal and causes Google to distrust your lastmod values over time. If you set lastmod, it must reflect genuine content changes — not template updates, not sitemap regeneration timestamps.

In a head-to-head comparison: an accurate lastmod is one of the most useful things you can put in a sitemap. A changefreq value, for Google at least, is nearly worthless. If you can only invest effort in one, invest it in getting lastmod right.

Common changefreq Mistakes

Even though Google ignores changefreq, the way sites misuse it reveals broader misunderstandings about how sitemaps work. Here are the most common errors:

Setting everything to "daily" as cargo cult SEO. This is by far the most widespread mistake. Site owners — or their plugins — blanket every URL with <changefreq>daily</changefreq> hoping it will force more frequent crawling. For Google, it changes nothing. For crawlers that do honor the value, it is simply inaccurate for most pages.

Mismatching changefreq with actual update frequency. Labeling a page "hourly" when it has not been updated in three years is at best useless and at worst a signal to crawlers that your sitemap data cannot be trusted. Inaccurate metadata compounds over time.

Omitting lastmod and relying on changefreq instead. Some sites include changefreq but skip lastmod entirely. This is the wrong trade-off. Lastmod is the tag Google actually uses; changefreq is the one it ignores. If you are going to include only one, make it lastmod.

Using invalid values. Values like "biweekly", "quarterly", or "sometimes" are not in the sitemap protocol specification and will be ignored or flagged as errors by strict sitemap validators.

XML Examples With Correct Usage

Here is an example of a well-structured sitemap entry that includes both lastmod and a reasonable changefreq value. Note how changefreq is set to match the actual update cadence of each URL type, and lastmod reflects the genuine last modification date:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <!-- Homepage: changes frequently -->
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-05-01</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>

  <!-- Blog post: rarely changes after publication -->
  <url>
    <loc>https://example.com/blog/how-to-fix-sitemap-errors</loc>
    <lastmod>2025-11-15</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.7</priority>
  </url>

  <!-- Product listing: updated weekly with new stock -->
  <url>
    <loc>https://example.com/products/</loc>
    <lastmod>2026-04-28</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>

  <!-- Static legal page: almost never changes -->
  <url>
    <loc>https://example.com/privacy-policy</loc>
    <lastmod>2024-03-01</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>

</urlset>

Compare that to the common anti-pattern where every URL gets "daily" regardless of actual update frequency:

<!-- AVOID THIS PATTERN: cargo-cult "daily" on every URL -->
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <url>
    <loc>https://example.com/privacy-policy</loc>
    <lastmod>2026-05-01</lastmod>  <!-- Fake: regenerated today -->
    <changefreq>daily</changefreq>  <!-- False: this page hasn't changed in 2 years -->
  </url>

  <url>
    <loc>https://example.com/blog/old-post-from-2019</loc>
    <lastmod>2026-05-01</lastmod>  <!-- Fake: CMS regeneration date -->
    <changefreq>daily</changefreq>  <!-- False: 7-year-old archived post -->
  </url>

</urlset>

The second pattern trains Google to distrust your sitemap metadata entirely. Once Googlebot observes repeatedly that a "daily" updated page has not changed in years, it will stop trusting your changefreq and lastmod signals across the whole site.

Recommendations: What to Do Instead

Given everything above, here is a clear set of actionable recommendations for how to handle changefreq on your site:

For most Google-focused sites: omit changefreq entirely. It adds no value for Google and creates maintenance overhead. A cleaner sitemap with accurate lastmod dates is more useful than a cluttered one with fictional changefreq values.

Focus your effort on accurate lastmod. Configure your CMS or build process to only update lastmod when the page content itself changes — not on every sitemap rebuild, template change, or CMS upgrade. This is harder to implement but far more valuable.

Let Google learn your real update cadence. Google is good at this. If you publish new blog posts every Tuesday, Google will figure that out from observed behavior and schedule recrawls accordingly. You do not need to tell it via a hint it ignores.

If you target Bing or Yandex significantly, include changefreq — but make it honest. Map each URL type to its actual update frequency. A legal page should be "yearly", not "daily". A live pricing page might genuinely be "hourly". Accuracy matters most when crawlers actually use the value.

Fix real crawl problems first. If you are concerned about Googlebot not crawling your pages quickly enough, the most impactful fixes are: improving page speed, fixing crawl errors (4xx, 5xx responses), building internal links to important pages, and earning external links. Tweaking changefreq is at the very bottom of the priority list.

Find Out What Your Sitemap Is Actually Telling Google

SitemapFixer checks your lastmod accuracy, changefreq consistency, URL health, and more — in seconds.

Related Guides

• XML Sitemap Tutorial: How to Create and Submit a Sitemap
• Sitemap lastmod: How to Use It Correctly for SEO
• Sitemap priority: Does Google Use It and Should You Set It?
• HTML Sitemap vs XML Sitemap: Key Differences Explained
• Mobile Sitemap: How to Ensure Google Crawls Your Mobile Pages