Check website

Content freshness: how dates affect rankings and AI answers

·4 min read

Content freshness matters when the searcher expects recent information, such as news, new releases, prices or anything that changes yearly, and barely matters for stable topics. Google runs "query deserves freshness" systems for those queries, and it reads your page's date from a visible byline and from datePublished and dateModified in structured data. Show an honest date, keep the markup in sync with it, and change it only when the content really changes. A new date on an old page fixes nothing.

When does content freshness affect rankings?

Freshness affects rankings only for queries where recency is part of what the searcher wants. Google's ranking systems guide describes several "query deserves freshness" systems and gives two examples. Someone searching a movie that just came out wants recent reviews, not articles from when filming started. A search for "earthquake" normally returns preparation advice, but right after a quake it shifts to news.

So check the query, not your page. Search your target phrase and look at the dates on the top results.

What the results show What it tells you
Mostly pages from the last few weeks Freshness weighs heavily. Plan regular updates
A year or a version number in most titles Readers expect the current edition. Update yearly
Pages from several years ago The topic is stable. Spend your time elsewhere

AI answers follow the same logic. Google's AI Overviews and AI Mode draw on its index, and Google calls optimizing for them "still SEO". A clear date also lets any engine or reader judge whether a statistic on your page is current.

How to show dates Google can read

Give Google one date in two places that agree. The byline dates guide asks for a visible date featured prominently, labeled with words like "Published" or "Last updated", and for datePublished and dateModified in the page's Article or BlogPosting markup.

<p>Published <time datetime="2026-03-03">March 3, 2026</time>.
Updated <time datetime="2026-10-08">October 8, 2026</time>.</p>
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to set up a staging site",
  "datePublished": "2026-03-03T09:00:00+01:00",
  "dateModified": "2026-10-08T14:30:00+01:00"
}

The rules from that guide that people break most often:

  • The visible date and the structured date must match. Generate both from the same field in your CMS.
  • Never use a future date, and never use the date of an event the page describes. The date is when the page was published or changed.
  • A time is optional, but if you give one, include the correct time zone.
  • If Google picks the wrong date, cut down the other dates on the page, such as related post dates in the sidebar.

The full Article markup, with authors and images, is in the article schema guide.

Don't fake updates

Changing a date without changing the content is the oldest freshness trick, and Google names it directly. Its helpful content guidance asks whether you change the date of pages "to make them seem fresh" when the content has not substantially changed.

The usual culprit is a template. Some WordPress themes and static site generators set dateModified to the build time, so every post claims it was updated today. Check a post you haven't touched in a year. If its markup says yesterday, fix the template.

The same honesty applies to sitemap lastmod. Google uses it only when it is consistently accurate, so a sitemap that stamps every URL with today's date teaches Google to ignore it. The details are in the XML sitemap guide.

How to spot content decay

Content decay is a page losing traffic over months because its information aged, newer pages answer better, or the query moved on. Find it in Search Console.

  1. Open the Performance report and compare the last 3 months with the same 3 months a year earlier.
  2. Sort pages by the drop in clicks.
  3. For each page near the top, check whether impressions fell too. Falling impressions mean lost rankings. Steady impressions with fewer clicks point to a weaker title or an AI answer taking the click.
  4. Search the page's main query and read what now ranks above you.

Then reread the page. Outdated prices, old screenshots and a "best tools of 2024" title in 2026 are what decay looks like up close.

How to refresh a page properly

Refresh a page by fixing what is wrong, then change the date. Fixing a typo is not an update.

  1. Replace outdated numbers with current ones and name their source.
  2. Rewrite steps that no longer match the product or interface.
  3. Add the subtopics the pages above you cover and you don't.
  4. Update the year in the title, H1 and headline markup if the page is about the current year.
  5. Keep the URL. A new URL throws away the links and history the old one earned.
  6. Set the visible "Updated" date and dateModified to today, and update the sitemap lastmod.

Leave accurate evergreen pages alone. An old date on a correct page costs nothing. For making the refreshed passages easy for AI engines to quote, see how to write content that gets cited.

Check your page's date signals

Our Content Freshness Checker fetches one URL and reads every date signal on it: datePublished and dateModified in JSON-LD, article meta tags such as article:modified_time, microdata, <time> elements, visible labels like "Updated March 3, 2026" and the Last-Modified header. It flags a missing visible date, missing structured dates, future dates, a dateModified before datePublished, visible and structured dates more than two days apart, and times without a time zone. Pages last updated six months or a year ago, and titles naming a past year, come back as prompts for review, not errors.

A run costs 5 credits. It reads the HTML your server returns for that one page. It does not decide what to update, rewrite anything, track changes over time or see your Search Console traffic, so finding decay still starts in the Performance report.

Keep reading