Sitemap Changefreq Analyzer
Analyze the changefreq, priority, and lastmod distribution of your sitemap.xml — find stale URLs and crawl-budget mistakes
Press ⌘+Enter to analyze
What Does Changefreq Actually Do?
<changefreq> is an optional field in every URL entry of your sitemap.xml that tells search engines how frequently the page is expected to change. The valid values are: always, hourly, daily, weekly, monthly, yearly, and never.
In practice, Google has publicly stated that they treat changefreq as a hint and rely more on observed change patterns. Bing weighs it more heavily. So the practical advice is: set changefreq to a realistic value (it costs nothing and helps Bing), but rely on accurate lastmod dates as your primary recrawl signal for Google.
How Should You Set Priority Values?
<priority> is a number from 0.0 to 1.0 that tells search engines the relative importance of a page within your own site. It is not a cross-site ranking signal — your priority 1.0 page is not ranked above someone else's priority 0.5 page.
The biggest mistake is setting every URL to 1.0. When everything is the most important, nothing is. The signal becomes noise and search engines ignore it. A realistic distribution looks like:
- 1.0 — Homepage only. Maybe 1-3 top conversion pages on a large site.
- 0.8 - 0.9 — Important category pages, top product pages, key landing pages.
- 0.5 - 0.7 — Most other pages. Default for content that is real but not your most strategic.
- 0.1 - 0.4 — Tag pages, archive pages, supplementary content.
Like changefreq, Google has stated they don't weight priority heavily. The real reason to set realistic priorities is internal — it forces you to think about what matters on your site, which improves how you internally link and crawl-budget your own pages.
Why Does Lastmod Recency Matter?
<lastmod> is the strongest signal you can give Google about whether a page needs re-crawling. When Google sees an updated lastmod, it knows to fetch the page again — when it doesn't, it can skip the URL and conserve crawl budget for sites that changed.
The two failure modes the analyzer flags:
- Missing lastmod on a high fraction of URLs. Usually means your sitemap generator is misconfigured. Most CMS plugins (Yoast, RankMath, Next.js' built-in sitemap.ts) include lastmod by default — if yours doesn't, fix the generator config.
- Lastmod older than 365 days on many URLs. Means either (a) your content really is stale and should be removed/refreshed, or (b) your generator is incorrectly using file-modification dates that haven't changed even though the rendered page has. Audit which is true.
For long-tail SEO, fresh content beats stale content most of the time. URLs that have not been touched in 2+ years often deserve to be removed from the sitemap entirely — let Google focus its crawl budget on your active pages.
What's a Healthy Changefreq Distribution?
For most content sites, a healthy distribution looks something like:
- daily — homepage, blog index, news index. 1-3 URLs typically.
- weekly — recent blog posts, active product pages, frequently updated docs. 10-30% of the sitemap.
- monthly — most static pages, settled blog posts, evergreen docs. 50-70% of the sitemap.
- yearly — legal pages, About, founder bio, glossary entries. 10-20%.
- always / hourly — only for genuinely real-time pages (live scores, breaking news). Most sites have zero of these.
- never — content that is genuinely frozen (e.g. a published press release from 2018 that will never change again).
If your distribution is heavily skewed (everything “always” or everything “daily”), search engines learn to ignore the field — and you lose a small but real ranking lever.
Need an AI chatbot for your website?
Hyperleap AI Agents answer customer questions, capture leads, and work 24/7.
Get Started Free