By Scott Sumner | AI Findability | Published September 22, 2026

Editorial illustration of an editor holding a purple date stamp over an old document, showing why a new date is not a substitute for updated advice.

A content refresh should make an existing page more useful, not merely make it look newer. If you use AI to update your website, start with the facts and advice that need changing before touching the publication date.

Answer: Refresh content when the facts, instructions or reader needs have changed. Verify sources, improve the useful parts and describe meaningful revisions. Changing the date without substantially changing the content is a warning sign in Google’s people-first content guidance.

The practical question is not “Can we rewrite this?” It is “What would a reader do differently after the update?” That gives both your editor and your AI tool a better job.

Jump ahead

Why a newer date is not a content strategy

An old article can still be accurate. A newly dated article can still recommend a discontinued service. Age is a reason to inspect a page, not a verdict on its usefulness.

Google’s guidance on helpful content explicitly asks whether you are changing page dates to make content seem fresh when it has not substantially changed. It lists that practice as a warning sign of search engine-first publishing.

The same guidance rejects the idea that adding lots of new content or removing older content simply to make a site seem fresh will improve its rankings overall. That does not mean you should never publish or remove anything. It means the age of your inventory is a poor substitute for evaluating what it does for readers.

I would not buy a content-refresh service measured only by how many pages received a new timestamp. I would want to know which incorrect claims were fixed, which missing answers were added and which decisions became easier.

This is not a claim that every date change triggers a penalty. Google’s documentation does not promise a specific ranking result for your next edit. The recommendation is simpler: improve the answer instead of dressing up its age.

Which pages deserve attention first

Start where outdated information can influence a real buying decision. A service comparison with old inclusions deserves attention before an accurate explanation of a basic concept, even if the explanation is older.

Build a small review list from pages used in proposals, sales conversations, search visits and customer support. For each page, record the decision it helps someone make and the claims most likely to expire.

  • Service and pricing explanations: check what is included, what is excluded and whether the described offer still exists.
  • Software instructions: follow the steps in the current interface rather than asking AI to modernize the wording.
  • Comparisons: verify the capabilities and limitations of each option against current primary sources.
  • Research-led articles: inspect the underlying study date, scope and whether newer evidence changes the conclusion.
  • Case studies: preserve the date and circumstances of the result. A historical result should not quietly become a claim about present performance.

Choose review intervals based on how quickly the subject changes. A vendor comparison may need more frequent checks than an explanation of your consulting method. There is no universal calendar that makes every article current.

A useful review can also conclude “leave this alone.” Do not rewrite a clear, correct paragraph merely to prove someone worked on it.

What a useful refresh actually changes

Consider a fictional agency guide called “How to choose a booking system.” It says a basic plan includes SMS reminders and tells readers to enable them under Settings.

Now imagine the supplier has moved reminders to a paid add-on and changed the setup flow. Replacing the introduction and putting this year’s date at the top leaves the expensive mistake intact.

A real refresh would verify the current plan details, correct the recommendation, explain the additional requirement and test the revised instructions. If the article compares several products, the editor should check whether the change affects that comparison too.

A useful update note might say: “Updated the reminder setup steps and clarified that SMS requires a separate add-on.” That note describes the hypothetical work. It is not a template to paste onto an unchecked page.

The reader now knows something that matters. The business also has a defensible explanation of why the update date changed.

By contrast, swapping “helpful” for “useful,” expanding the introduction and adding another generic conclusion do not resolve the original problem. More words are not evidence of more value.

How to use AI without inventing an update

AI can help compare an existing article with current source material. It can identify claims to check, draft revisions and produce a readable change log. But a fluent rewrite is not evidence that the facts were verified.

Give the tool the current page and the specific sources you want compared. If it cannot open a source, have it mark the claim unverified rather than fill the gap from memory. Use an approved workspace for any private business documents.

Here is a practical starting prompt:

Review this article against the supplied current sources. Do not rewrite it yet. List each potentially outdated claim, its location, the supporting source and the proposed correction. Distinguish factual changes from optional style edits. If the sources do not settle a claim, mark it unverified.

Preserve accurate historical statements and original case-study dates. Do not invent new results, prices, features or personal experience. After the proposed factual changes are approved, draft only the necessary revisions and a plain-English note explaining what changed for the reader.

Have someone who understands the offer or workflow check the proposed corrections. For a product tutorial, that means trying the steps. For your own service page, it means confirming the actual service, not treating a competitor’s website as the source of truth.

A useful comparison sheet has the old claim, the proposed replacement, its evidence and its effect on the reader. If the fourth column is empty throughout, you may be commissioning a style edit rather than a substantive refresh. Style edits can still be worthwhile. Call them what they are.

What to check before republishing

Separate the original publication date from a meaningful update date. Google’s publication-date guidance recommends a prominent, clearly labeled visible date and consistent machine-readable dates. Those dates should describe the page’s publication or update, not an event mentioned inside it.

Ask your web team how the CMS handles those fields. An automatic save timestamp and a deliberately displayed editorial update date are not necessarily the same thing. Your template should not announce a major refresh every time somebody fixes a comma.

Google says it uses several factors to estimate when a page was published or significantly updated. Supplying a date helps communicate the information; it does not force Google to display your chosen date in search results.

Before the revised page goes live, compare it with the previous version. Check that corrections are present, source links work and important qualifications survived. Keep the existing URL when the page still serves the same purpose. Do not turn routine editing into an unnecessary URL migration.

Then inspect the public page, not only the editor. Read the headline, visible date and update note together. A reader should not have to guess whether “new” means new evidence or new formatting.

For AI Findability, the sensible objective is an accurate, understandable page that is worth citing or recommending. There is no guarantee that a fresh date will produce an AI citation. Our AI Findability approach starts with making the business and its evidence clear, not pretending a timestamp can supply authority.

One useful place to start

Pick one article your sales team still sends to prospects. Check the claim most likely to change the buyer’s decision. Fix that first, and describe the correction honestly.

If you need help deciding which pages deserve a rewrite, repair or no change at all, the Findability OS Audit is the starting point for a wider review. A smaller, well-maintained set of useful answers can be a better asset than a busy publishing calendar nobody trusts.

Sources and scope

Both sources were checked September 22, 2026. This is evergreen editorial guidance, not a new Google update announcement. The booking-system example is fictional. The review workflow and prioritization advice are Sumner.ai’s recommendations, not guaranteed ranking factors.

Production note: This article was prepared with AI assistance using the linked Google documentation. The example illustrates an editorial decision, not a reported client result.