Freshness Is a Promise You Keep, Not a Date You Set

Does republishing an old page with today’s date actually help you show up in AI answers? Sometimes. A newer date can make a page look more relevant to an AI system, even when the content itself has not changed. But simply changing the timestamp is not a reliable freshness strategy.

The better approach is to show when a page has genuinely been reviewed, updated, or verified. For professional firms with valuable evergreen content, freshness should reflect real maintenance rather than cosmetic recency. That means keeping stable information stable, updating only what has changed, and making your dates tell the truth.

Why a date moves a machine at all

AI answers are not ranked the way a search results page is. They are assembled from fragments the model chooses to trust and surface, and when it is choosing among sources that all look correct, it reaches for shortcuts. Recency is one of the strongest. In one controlled study, researchers changed nothing about a set of passages except adding a line with a newer publication date, and watched individual passages climb dozens of positions in an AI reranker on the strength of the date alone. In a quarter of head-to-head comparisons between equally relevant passages, the model flipped its preference to the newer-looking one. Nothing about the content had improved. It simply looked more current.

Larger models showed the bias more strongly, probably because they absorbed more of a web where newer dates really do correlate with relevance. The lesson is not that dates are magic. It is that a machine treats a fresh timestamp as a proxy for quality, and it cannot tell a genuinely updated page from one whose date you quietly changed.

Why “new” is the wrong goal for a professional firm

Here is where the shortcut turns against you. In a professional practice, many of your most valuable pages are meant to be stable:

• How probate works in your state
• What a revocable trust actually does
• The steps in a real estate closing

These topics do not change often, and their value comes from being settled and accurate. Constantly making them look new solves a problem you do not have.

Recency bias can even work against your strongest pages:

• A thorough, two-year-old explainer may lose visibility to a thinner page published last month.
• When two sources appear equally relevant, the newer date can become the tiebreaker.
• Depth can lose to freshness even when the older page is still completely accurate.

I have seen this happen with an authoritative trust explainer. The page had gone untouched for two years because the underlying law had not changed, yet it kept slipping out of AI answers while a shallower, newly dated competitor page was quoted instead.

The firm’s first instinct was to rewrite it. It did not need rewriting. It needed an honest signal that the information had been reviewed and still held.

Protecting strong evergreen pages from that trap is part of the content work we do at meanderingSapien. The principle is simple: do not treat every page as though newer automatically means better.

Design freshness; do not fake it

The fix is not to update more often. It is to make freshness mean something. Two moves do most of the work.

1. Separate the evergreen core from what actually changes

Keep the stable parts of the page stable:

• Definitions
• Core principles
• Standard processes
• Steps that rarely change

Then add a small current-state section for information that does change, such as:

• Fees
• Regulatory updates
• Recent legal changes
• New services

Update only that section when something real changes. A short “What changed recently” note near the top can signal freshness without rewriting an accurate page unnecessarily.

2. Make your dates reflect a real review

A “Published on” date only tells readers when the page first appeared. It does not confirm that the information is still current.

Use clearer verification signals instead, such as:

• “Last reviewed”
• “Last verified”

These tell readers and machines that someone has actually checked the information. Google’s structured data also distinguishes between when an article was first published and when it was meaningfully modified, so your dates should reflect genuine changes rather than a cosmetic timestamp update.

Take a page explaining what a revocable living trust does. The evergreen core- what it is, how it differs from a will, and who it may suit- can stay unchanged. A filing fee, amended statute, or newly available service can sit in the current-state section and be updated when needed.

The result is a page that stays stable where accuracy matters and current where circumstances change. The freshness signal now maps to something real rather than cosmetic.

A cadence that matches how your content changes

Not every page needs the same rhythm, and the steady publishing cadence we build with clients is about real coverage, not cosmetic churn. Map your pages to review cycles that fit what they are:

• Fee schedules and anything tied to current pricing: Review promptly whenever they change; verify quarterly otherwise.
• Regulatory and compliance explainers: Verify on a quarterly rhythm, and update immediately when a rule actually shifts.
• Foundational how-it-works content: A semi-annual check is usually enough, since the underlying concepts hold.
• Comparison and “best” style pages: Review more often, because those queries carry the strongest recency signal of all.

During each review, confirm the core claims still hold. If nothing changed, update the “Last verified” date and leave the content alone. If something did change, revise the current-state section and note it. The date now reflects substance, which is the only kind of freshness a machine should reward and the only kind that survives a closer look. Getting this rhythm right is a large part of a content engagement we run.

Freshness is a promise, and machines are starting to check it

A timestamp is a claim. A fresh date tells a machine “this reflects the current state,” and the firms that win the freshness game are the ones whose dates are true. Re-dating a stale page might buy a brief lift, but it also teaches your readers, and over time the engines, that your dates mean nothing. Earned freshness compounds; faked freshness erodes the very trust the rest of your content is working to build.

So keep your evergreen core stable, verify it on a rhythm that fits each page, and let your dates say only what is true. That is how our own blog is maintained, and it is the version of “keep your content fresh” I am willing to stand behind.

If you want help identifying which pages need updating, which only need verification, and where freshness may be affecting your AI visibility, book a call with meanderingSapien.

Frequently Asked Questions

Should I remove publication dates from my firm’s pages?

No, keep them, but add “Last reviewed” or “Last verified.” This shows the page has been checked without pretending it is new.

Does updating a page’s date help it appear in AI answers?

It can; AI systems may use recency as a relevance signal, but changing the date without reviewing the content creates a weak signal.

Which pages are most exposed to recency bias?

Pricing, comparison, “best,” and “latest” pages are especially sensitive. Evergreen explainers can also lose visibility to newer pages.

How often should a professional firm update its content?

Review pricing and regulatory content quarterly or when something changes. Foundational explainers can be checked every six months.

What should I do if nothing has changed?

Review the facts, update the “Last verified” date, and leave the content intact. Do not rewrite a page just to make it look new.