Should you really ditch priority and frequency in your XML sitemaps?

Why is Google moving away from priority and frequency?

The and tags were originally designed to guide search engines on the relative importance of pages and their update frequency. The issue? Most CMS and sitemap generators fill them with generic or fanciful values. An e-commerce site marks all its product listings as priority="1.0", while a WordPress blog assigns changefreq="monthly" to articles that are never updated.

Google eventually found that these signals provided no reliable information. Rather than interpreting them, the engine relies on its own prioritization algorithms: page popularity, crawl history, internal links, behavioral signals. Therefore, the two tags have become unnecessary noise in XML files.

What does the lastmod timestamp change in practice?

The tag indicates the date a URL was last modified. When filled out accurately, it allows Google to quickly detect updated content and reprioritize its crawl accordingly. Instead of randomly crawling the entire site, the bot can target URLs that have been recently modified.

This is particularly useful on large sites where crawl budget is a concern. If you update an article, add a promotion on a product page, or correct errors, an accurate lastmod speeds up the process. Conversely, an incorrect or missing timestamp dilutes information and makes the sitemap less usable.

Is this timestamp really as ‘crucial’ as Mueller claims?

The word “crucial” can be misleading. A sitemap with lastmod does not guarantee indexing or ranking. Google remains free in its choices: it can crawl a page without lastmod if it receives fresh links, or ignore a URL with a recent lastmod if it is deemed irrelevant.

However, in a context where priority and changefreq are no longer useful, lastmod becomes the only applicable temporal signal in the sitemap. If you must choose where to focus your efforts, that's where to concentrate. Think of it as an optional but effective accelerator, not a vital requirement.

• Priority and changefreq are now ignored by Google, so there’s no need to keep them.
• The lastmod indicates modified pages and optimizes crawl budget.
• An exact and honest timestamp is essential: no fanciful dates to “force” the crawl.
• Lastmod remains a signal among others, not a magical lever for indexing.
• Large sites with frequent updates benefit the most from this practice.

Is this statement consistent with field observations?

Yes, unsurprisingly. For several years, SEOs have noticed that playing with priority or changefreq doesn’t change indexing delays at all. Google Search Console doesn’t even display these values in coverage reports anymore, indicating that the engine has abandoned them internally. Mueller's statement merely formalizes a practical reality that is already established.

However, the impact of lastmod is less universal than one might think. On smaller sites (a few hundred pages), Google crawls the entire content regularly. Lastmod then provides marginal gains. It's on large sites (thousands of URLs) that the difference becomes noticeable: server logs support that the bot shows increased responsiveness to freshly timestamped URLs.

What nuances should be applied to this recommendation?

First point: the lastmod must reflect a real modification. Updating the timestamp each night on all pages to simulate freshness is counterproductive. Google quickly detects that the content has not changed (via checksums, the DOM, text snippets) and will end up ignoring your sitemaps. You lose credibility.

Second nuance: some platforms generate fanciful lastmod values. WordPress, by default, sometimes uses the publication date instead of the actual modification date. WooCommerce may update the timestamp with every stock change, creating unnecessary noise. [To verify] Thus, it is important to audit the logic of sitemap generation before blindly trusting the displayed dates.

In what cases does this rule not apply?

If you manage a purely static site with no updates (a static showcase site, archived documentation), lastmod loses its relevance. Likewise, on a new site with few pages, Google crawls intensely at the beginning: the absence of lastmod does not slow anything down.

Finally, if your technical infrastructure does not allow for proper tracking of changes (legacy CMS, unreliable external sitemap generation), it is better to omit lastmod than to display false dates. A sitemap without lastmod remains valid and usable, while a sitemap with erroneous timestamps becomes suspicious.

What should you do with your sitemaps?

Start by removing priority and changefreq from your XML files if your sitemap generator allows it. These tags bloat the file without adding value. If your CMS adds them automatically and you cannot disable them, leave them but do not spend any time on them: Google ignores them.

Next, enable lastmod and configure it to reflect the actual modification date of the content. This often involves light development: hooks in the CMS, triggers in the database, or custom generation scripts. Test on a few pilot URLs and check the logs to see if Google reacts to the changes.

How can you check if your lastmod is functioning correctly?

First step: manually inspect your XML sitemap and compare the displayed dates with the actual modification history. If all URLs have the same date or an absurd date (future or too old), the mechanism is broken.

Second step: analyze your server logs to observe Googlebot's behavior. Modify a page, update the sitemap with a new lastmod, then monitor if the bot crawls this URL in the following hours or days. On a well-configured site with a good crawl budget, the effect is measurable. If nothing changes, either Google is not prioritizing your site, or the lastmod is not being interpreted (incorrect format, strange timezone, chronological inconsistency).

What mistakes should be avoided in managing timestamps?

Don't fall into the trap of “fake lastmod”: updating the date every night on all pages to simulate freshness is a Black Hat tactic that can be detected and penalized. Google compares the actual content and detects the absence of substantial modification.

Also, avoid non-standard date formats. The lastmod must follow the ISO 8601 standard (YYYY-MM-DD or with time and timezone). An exotic format may be silently ignored. Lastly, do not overload your sitemaps with unnecessary URLs (duplicate parameters, infinite paginated pages, non-indexable resources): a clean and lightweight sitemap crawls better than a bloated file packed with noise.

• Remove or ignore the priority and changefreq tags in your XML sitemaps.
• Enable and configure the lastmod to reflect actual modification dates.
• Test the consistency of generated timestamps by comparing sitemap and editorial history.
• Analyze your server logs to measure the impact on Googlebot's behavior.
• Never use fictional lastmod to trick the engine, as this degrades trust.
• Respect the ISO 8601 format to avoid interpretation errors.