Content Freshness Without the Fake “Updated” Date

Classify what can decay

Mark claims that depend on laws, provider policies, prices, product capabilities, statistics, schedules, interfaces, named tools, or time-sensitive examples. Add the authoritative source and a review trigger. Separate stable principles from volatile instructions. A guide may contain both: the need for webhook idempotency is stable, while a provider dashboard path can change quickly.

Review cadence should follow consequence and change rate. Incorrect payment, privacy, safety, or legal guidance needs faster review than a benign writing example. Product pages require review after relevant releases. Search documentation pages can be checked against Google's updates log and current official guidance.

• Stable principle
• Volatile claim
• Authoritative source
• Consequence
• Calendar or event trigger

Start with the user's job and current evidence

Read the page as the intended user. Can they still understand the problem, make the decision, and complete the next step? Review search queries, support questions, CTA behavior, and product changes for evidence that the job shifted. Do not add sections merely to increase length or cover adjacent keywords.

Open every substantive source and note access date, what it supports, and whether the page moved or changed meaning. Replace secondary summaries with primary sources where possible. If a claim cannot be supported, narrow or remove it. Preserve uncertainty rather than inventing a current fact.

• User decision
• Current questions
• Product truth
• Source verification
• Unsupported-claim removal

Verify examples, links, and the real CTA

Examples can become misleading even when the general advice remains valid. Re-run instructions, open screenshots or referenced tools, and confirm limitations. Check internal and external links, redirects, MIME types where relevant, canonical, structured data, sitemap inclusion, and the primary CTA in a signed-out session.

Trace attribution through the CTA into signup or activation. A content page is operationally stale if it routes to an obsolete waitlist, missing feature, wrong host, or dead campaign. Update the CTA only when the destination is real and the surrounding language accurately reflects beta, availability, pricing, and approval boundaries.

• Examples still work
• External and internal links
• Canonical and sitemap
• Signed-out CTA
• Attribution handoff

Choose one of five editorial actions

Update when new evidence materially improves the same user job. Merge when several thin or overlapping pages should become one canonical resource. Redirect when a replaced page has a clear successor. Archive or remove when the content is unsafe, obsolete, or no longer serves the product and there is no equivalent. Leave alone when the page remains accurate and useful.

Do not preserve every old URL in the sitemap. Canonical and redirect signals should agree with internal links and the chosen content architecture. Avoid creating a new page for each minor variation when a maintained pillar and supporting guides can answer the need more clearly.

• Update
• Merge
• Redirect
• Archive or remove
• Leave unchanged

Use honest date semantics

Keep the original publication date. Change the modified date only when readers receive a material content change, not after spelling fixes, generator runs, or source checks that produce no change. Show a separate source-verified or reviewed date when useful. Explain what materially changed in a brief note for substantial revisions.

Sitemap lastmod should reflect a meaningful page update. Google guidance treats it as a signal that should be accurate. A sitewide build timestamp on every URL creates noise. Generate lastmod from the content record rather than the deployment time whenever the framework permits.

• Original publication date
• Material modification date
• Separate source-check date
• Change note
• Truthful sitemap lastmod

Protect originality and claims

Add value through an original tool, dataset, method, worked example, template, or clearly reasoned synthesis. Do not fabricate benchmark numbers, customer outcomes, or testimonials to make a refresh look substantive. FTC guidance on testimonials and reviews reinforces that endorsements and results need truthful treatment; label examples and hypothetical scenarios plainly.

If AI assists with review or drafting, retain the source ledger and human editorial responsibility. Check for invented citations, copied phrasing, stale tool descriptions, and a stronger claim than the source supports. The final author owns the page's truth regardless of which tool proposed the text.

• Original utility
• No invented outcomes
• Examples labeled
• Claim-to-source ledger
• Human accountability

Record the review and next trigger

Store page, owner, user job, sources checked, material findings, editorial action, changes, tests, CTA result, and next review trigger. Link to the version or commit when possible. A concise record helps the next reviewer understand why the page changed or remained untouched.

Use recurring schedules selectively. Review fast-decaying, high-value pages more often and trigger review after relevant product or policy changes. Sample lower-risk evergreen pages. The goal is a small, maintained library that remains defensible—not a content treadmill that changes dates faster than it improves answers.

• Page and owner
• Sources checked
• Material findings
• Chosen action
• Verification
• Next trigger

Put this into practice

Audit freshness by user job, volatile claims, source truth, examples, links, product fit, and CTA. Then update, merge, redirect, archive, or deliberately leave the page alone. Keep publication, modification, and source-check dates distinct. Honest maintenance earns trust because a reader can see that meaningful changes—not a scheduler—caused the update.