Sitemap XML Best Practices: Priority, Changefreq and Lastmod Explained
By Toy Wen Da, Co-Founder · · 7 min read · scored 92/100
Sitemap XML best practices boil down to three things. List only canonical, indexable URLs, keep the lastmod date honest, and stop worrying about priority and changefreq. Google treats both as hints it mostly ignores. Start by auditing what's already in your sitemap, not by adding more tags to it.
Start by Checking What's Actually in Your Sitemap
Before you touch any settings, look at the file itself. SearchBlueprint's free XML sitemap generator crawls your site and shows you the URL list it would produce. It flags which pages are getting picked up, which are missing, and whether redirected or blocked pages have snuck in. Run your own site through it and compare the output against your live sitemap.xml before you change anything inside your CMS.
This matters because most sitemap problems aren't really about XML syntax. They're about which URLs ended up in the file in the first place.
How to Fix Your Sitemap Inside Your Own Site
If You're on WordPress
Most WordPress sites generate their sitemap through an SEO plugin rather than by hand. In Yoast SEO, the sitemap toggle lives under the plugin's general settings, in the section that controls site features. Turning it on gives you an automatically updated sitemap index with no manual maintenance. Rank Math works the same way. Once the sitemap feature is active, a dedicated sitemap settings area appears. It lets you choose which content types (posts, pages, categories) get their own sub-sitemap.
Either plugin regenerates the file automatically every time you publish or update a page, so lastmod stays accurate without you touching it.
If You're on Shopify, Wix or a Custom CMS
Shopify and Wix both generate a sitemap automatically at a fixed URL and don't give you manual control over individual tags. Your main job is confirming it exists and that it isn't blocked. On a custom-built or headless site, your developer needs to generate the sitemap dynamically from your database of published, indexable pages. It shouldn't come from a static file someone edited by hand months ago.
Submitting the Sitemap and Updating robots.txt
Once the file is correct, two steps make sure Google can find it:
- Add the sitemap's location to your
robots.txtfile, so any crawler checking that file first knows where to look. - Submit the sitemap URL directly in Google Search Console, under the Sitemaps section, so you can monitor indexing status over time.
Google has been direct about this. Using a sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed." Submitting it just removes one excuse a page has for never getting discovered.
Priority, Changefreq and Lastmod: What Each Tag Actually Does
These are the three optional child tags inside every <url> block, and they're the source of most sitemap confusion. lastmod must follow the W3C Datetime specification, the same ISO 8601-based standard used across web protocols. Here's what each one is actually worth doing.
| Tag | What It Tells Google | Does Google Use It | Recommendation |
|---|---|---|---|
lastmod |
The date the URL's content last changed, in W3C datetime format | Yes, helps Google judge content freshness and recrawl priority | Keep accurate and automated; never set it to "today" on every page |
changefreq |
How often you expect the page to change (always, hourly, daily, weekly, monthly, yearly, never) | Largely ignored; treated as a loose hint at best | Leave it to your CMS's default or skip it entirely |
priority |
A 0.0–1.0 score of how important you consider the URL relative to others on your site | Effectively ignored by Google | Not worth manually curating; don't waste time hand-tuning this |
The pattern is clear: lastmod is the one tag worth getting right. changefreq and priority are legacy parts of the sitemap protocol that search engines never leaned on heavily. Even though the official sitemaps.org protocol still lists them as valid, that doesn't make them worth tuning.
When Your Site's Own Tools Are Enough, and When They're Not
This is the honest part. Your CMS's built-in sitemap, or a quick run through a free checker, is genuinely enough when:
- You're checking a single URL that's missing from search results and want to confirm it's in the sitemap.
- You just published a page and want to verify it was picked up by the next automatic sitemap regeneration.
- Your site has a few hundred pages, good internal linking, and a plugin like Yoast or Rank Math already handling generation.
It's not enough when:
- You're auditing a site with thousands of URLs and need to see which pages are indexable versus blocked, redirected, or duplicate. At that scale, a one-off manual check misses patterns.
- The problem is recurring: pages keep dropping out of the sitemap after a migration, a redesign, or a CMS change. Nobody's tracking why.
- You need to cross-reference sitemap inclusion against actual Search Console indexing data, not just confirm the file exists.
A large site with a thin internal link structure benefits most from active sitemap monitoring. So does a new site with few external links pointing to it. Google itself lists these as the cases where a sitemap carries more weight.
Common Sitemap XML Mistakes to Avoid
| Mistake | Why It's a Problem | Fix |
|---|---|---|
| Listing non-canonical or redirected URLs | Sends Google to the wrong version of a page, wasting crawl attention | Include only 200-status, canonical URLs |
| Forgetting to update the sitemap after a migration | Old URLs linger; new ones never get submitted | Regenerate and resubmit the sitemap as part of your migration checklist |
| Omitting important pages | Pages without strong internal links may go undiscovered | Cross-check your sitemap against your full indexable URL list |
| Never submitting to Google Search Console | Removes one of the simplest discovery signals available | Submit the sitemap URL and monitor it under Search Console's Sitemaps report |
| Hand-building a sitemap manually | Easy to miss UTF-8 encoding, exceed the 50,000-URL cap, or leave out new pages | Use a plugin or generator that rebuilds the file automatically |
Duplicate title tags across pages cause a related but separate problem. Google can see two "different" URLs in your sitemap that actually serve near-identical content. If that's happening on your site, it's worth fixing the underlying title tag duplication before you worry about sitemap tags at all.
Mobile and Image Sitemaps: Extra Considerations
A mobile XML sitemap isn't a separate file in most modern setups. If your site is responsive (the same URL serves both desktop and mobile), your one sitemap already covers it. Separate mobile sitemaps were mainly relevant to old dedicated mobile-URL setups (like an m. subdomain), which most sites have retired.
Image sitemaps are a different story and still worth doing deliberately if images matter to your traffic. Think product photos, infographics, or editorial images that could show up in Google Images. Rather than cramming image tags into your main file by hand, use a dedicated guide. Building an image sitemap Google will actually read covers the exact tag structure.
FAQs
Does sitemap priority actually affect my Google ranking?
No. Priority is a self-reported 0.0–1.0 value you set, and Google doesn't use it as a ranking signal. It was never a ranking factor to begin with, Google said as much as early as 2008.
What's the correct changefreq for a blog post versus a static page?
If you set it at all, "weekly" is a reasonable default for blog posts. "Monthly" works for static pages like your About or Contact page. In practice, Google largely ignores this tag, so getting it slightly wrong won't hurt you.
How many URLs can one XML sitemap file hold?
Up to 50,000 URLs, and the uncompressed file must stay under 50MB. Once you exceed either limit, split the content into multiple sitemaps and list them in a sitemap index file.
Do I need a separate mobile XML sitemap?
Only if your site still serves a separate mobile URL structure, like an m. subdomain. If your site is responsive and uses the same URLs for desktop and mobile, one sitemap covers both.
Will submitting my sitemap guarantee my pages get indexed?
No. Google is explicit that using a sitemap doesn't guarantee every URL in it gets crawled and indexed. A sitemap improves discovery and efficiency; it doesn't override quality or crawlability issues on the page itself.
Run Your Sitemap Through a Real Check
List the right canonical URLs, keep lastmod honest, and stay under the size caps. That covers the bulk of sitemap xml best practices worth caring about; priority and changefreq are secondary. If you want a clear picture of where your own sitemap stands against these rules, talk to the team. You'll get a sample report that shows exactly what's in your file today.
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.