Freshness in Google Search: when to update a page

Decide when a page needs new facts. Separate freshness, result deduplication, original reporting and canonical selection before changing content or dates.

Published 2026-04-06
·
Updated 2026-10-28
·
4 min read

A release guide can need an urgent correction while a five-year-old explanation remains useful. Before updating either page, ask: what has changed in the answer the reader needs? A newer timestamp is not evidence that the answer improved.

Freshness depends on the query

Google describes freshness systems for searches where recent information is expected. Its ranking-systems guide also describes systems for reducing repeated results and surfacing original content. These serve different purposes; they are not a single age-based score.

For a software compatibility query, check the current supported versions. For a stable definition, check whether the explanation is still accurate. This is a practical way to prioritize maintenance, not a published Google formula or a fixed updating interval.

A result-selection map: which evidence comes first?

Use this table to choose an investigation. The observations are starting points, not diagnoses of a particular website.

Observation and questionEvidence and useful action
Facts changed. Does the page still answer the current query?Compare the current primary source with the exact outdated passage. Correct the affected facts and explain their scope.
Similar listings are absent. Could result deduplication be relevant?Save the query, date, result format and pages compared. Record the observation before inferring an indexing problem.
A copy appears instead. Which URL did Google select as canonical?Check the indexed URL Inspection result, content and canonical signals. Investigate conflicting signals on genuinely similar pages.
A new summary and an old report both appear. What first-hand evidence does each provide?Identify original interviews, data, methods and source links. Make the original contribution verifiable and preserve attribution.

Google’s canonicalization overview explains how similar pages can be grouped during indexing. This differs from reducing repetition among search results. A single search screenshot cannot establish which process explains a missing listing.

Deduplication does not justify merging useful pages

Separate an indexing question from a content question. A page can answer a different reader need even when it uses similar vocabulary. Compare the main content and purpose before treating two URLs as duplicates.

For truly duplicate or very similar pages, Google’s canonical guidance describes redirects, canonical annotations and sitemap signals. Google can still select a different canonical. Do not point every related article at one URL, or use canonical markup as a way to claim authorship. The duplicate-content guide explains common URL variants in more detail.

Original reporting can remain useful as a story develops

Google’s 2019 explanation of original reporting describes work to make significant original journalism more visible, including alongside newer coverage. It is historical context, not a promise that the first publisher always ranks first.

For your own article, identify what readers can verify: the source interview, the measurement method, the underlying documents or the original analysis. Attribution and evidence help readers distinguish reporting from a summary. They do not provide an originality score or guarantee a search position.

A worked example: update the fact that changed

Hypothetical example: a guide explains how to export a report. A software release moves the export control, but the file format stays the same. A separate article contains original research about that format.

Update the guide’s instructions and affected screenshots. Check whether older supported versions need a separate note. Keep the research article if its findings remain accurate and its purpose differs. Changing both articles’ dates or combining them would not solve the reader’s immediate problem: finding the current control.

This example illustrates an editorial decision; it is not a measured ranking experiment.

Dates should describe the page’s actual history

Google’s byline-date guidance recommends clear visible dates and consistent structured data. Publication and modification dates describe the page, not the date of an event mentioned in it. Google uses several signals to estimate dates and does not guarantee displaying the date you supply.

Keep the original publication date when revising an article. If facts, instructions or analysis materially change, label the update accurately and make the corresponding markup agree. Check the rendered page as well as the CMS field. Do not describe a routine review as a new publication.

After an update, save the changed passage and its source. When assessing later performance, keep query, page and comparison periods consistent and consider other changes. A before-and-after traffic difference alone cannot establish that freshness caused it. The Google Search systems overview provides the broader context; the algorithm guide explains the limits of page and site-level evidence.

For a short definition, see freshness in the glossary.

Q&A

Does newer content always rank better?

No. Google's freshness systems serve queries that call for recent information. A newer publication date alone does not establish that a page is more useful.

Does a missing second listing prove a freshness problem?

No. Result deduplication, canonical selection and other causes need different evidence. Check the query and the affected URLs before rewriting the page.

Should I change the date when I review a page?

Keep the original publication date. Use an update date for a substantive revision, and keep visible dates consistent with structured data. A review without a material change does not make the content newly published.

Privacy & Cookies

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies.