Process decision learning

Keep source evidence current for the claim it supports

Source freshness control records when evidence was observed, where and when its statement applies, and what age or event requires another review. It prevents an old saved observation from silently becoming an unqualified current claim.

Use it for changing products, prices, policies, laws, officeholders, platform features, availability, search observations and analytics. Keep the source, scope, owner and decision about stale support attached to the record.

Read the freshness policy examples

By Kevin Maguire · Published by Semantec SEO

Keep the saved observation, context and observation time beside the source record.

Source notebook and version folders beside a pencil, magnifier and distinct record cards. — Observation, effective period and review trigger are different parts of the evidence record.

Keep observation, applicability and review timing separate

The date a source was checked is different from the period its statement covers. A recently retrieved page can describe an old release or a future policy. A source that remains reachable can still leave a recorded claim too old or differently scoped for current use.

Observation records what was checked

Keep the source URL, file, dataset or system, the observed version, method and date. A later visit to the same address is a new observation only when the relevant content and context are reviewed; changing a timestamp cannot refresh an extracted claim.

Effective dates define applicability

Record when the price, policy, appointment, release or other statement applies. Publication date and observation date do not automatically establish that effective period. Preserve market, jurisdiction, plan, version, currency or measurement window when those change the claim.

Review timing is a local control

Choose a maximum usable age, a scheduled review or a named event according to the claim’s volatility and consequence. Time and event triggers can apply together. A source can change before the planned date, and a scheduled date arriving does not prove the fact has changed.

History and current use have different limits

A dated saved observation can remain evidence of what the source stated at that time. It may no longer support an unqualified current claim. Preserve the historical record while reviewing its use for current claims, rather than erasing the saved observation or relabelling it as a new observation.

Set a freshness policy for the claim, not just the source format

The following classes are an illustrative process vocabulary, not universal expiry intervals. No listed source has been checked here, and no monitoring schedule has been created. A single source can contain claims with different volatility, applicable periods and review needs.

Illustrative source policy by claim volatility and trigger
Class and example claim	Review or expiry basis	Action before current use
Stable: an identified historical record for a stated period.	The record can remain useful for that historical claim, while corrections, changed identity evidence or version replacement can reopen its interpretation.	Preserve the dated version and scope. Do not treat historical stability as proof of a current operating state.
Slow change: a maintained definition or documented method.	Use the owner’s review policy and reopen when the terminology, source authority or method changes.	Confirm the intended source version and its applicability to the claim being made.
Moderate change: functions documented for a product release or plan.	A new release, changed plan or revised documentation can reopen the claim before the next scheduled check.	Verify the exact product version, plan and supported operation; do not carry a family statement into every variant automatically.
Fast change: current price or availability.	Set an appropriate period for current use and a trigger for source changes, based on the offer and its consequences. A previous saved observation is not current merely because its URL works.	Recheck the controlling offer, date, market, currency and terms before presenting it as current; otherwise hold the claim or use a clearly dated historical description where useful.
Event driven: policy, law or officeholder state.	A revision, effective date, appointment or other named event can reopen the claim regardless of elapsed age.	Consult the controlling source for the applicable period and scope. Use the responsible specialist when interpretation or approval requires it; a recent date alone cannot settle the statement.
Live or contextual: a search result or analytics observation.	The claim belongs to its query, location, device, session or measurement window and observation time.	Record that context and limit the statement to the observation. Obtain suitable new evidence before claiming the same pattern is current or general.

These dimensions can overlap. A source can be monitored for events and also receive a rule that limits its usable age. The policy should state the allowed use, trigger, responsible owner and action when support is stale, rather than relying on a class label alone.

Recheck a saved pricing record before calling it current

In this hypothetical example, a comparison draft uses a pricing table saved six months earlier. The source URL still resolves, so the draft labels the amounts current. That proves reachability, not that the recorded offer still applies. No price, provider or source has been verified here.

Magnifying glass over an unmarked document beside a reference book and a blank calendar. — Recheck the exact source statement and offer scope before calling an old saved observation current.

Review the controlling source again

Identify the current product or plan and its official offer context. Compare the relevant amount, currency, market, tax treatment, period and conditions. A fresh observation must address the claim, not merely establish that a page loads.

Keep stale different from false

The old saved observation may still accurately record the former offer. Its age alone does not prove that the amount changed. Mark the current claim as needing evidence under the policy; do not invent either a price change or a fresh confirmation.

Choose a supported description

If suitable current evidence is obtained, record the new observation and applicable scope. If not, hold the current comparison or present the dated historical snapshot only when it serves a legitimate historical purpose and is clearly qualified. Do not let its presentation imply a current purchasable offer.

Retain the policy and owner

Record source identity, claim classes, observed and effective dates, volatility, maximum age or event trigger, limitation and current state. Name the responsible owner, missing dependency, next check and action for the dependent draft or release.

Two navy archive boxes beside an unnumbered clock and blank record card. — Preserve historical evidence when current use needs new review.

Route expired support to a bounded decision about renewed checks

When evidence no longer meets the policy for its intended use, mark that use as stale and identify the work that consumed it. Preserve the former saved observation and approval as history. Renewed checks can confirm the statement, change its scope, replace its source or leave it unresolved.

Classify the claim and source. Identify what the source can support, how fast that claim can change and the consequences of presenting an outdated state. Do not assign the same window to all prices, definitions, policies and historical records.
Record the observation and applicable period. Keep method, date, source version and relevant market, release or measurement context beside the extracted statement. Distinguish a future effective date from a current state.
Define time and event triggers. Set the local review rule and earlier reopening events, such as a product release, policy change or contradictory observation. Name the monitoring or manual route and who owns it. A missing alert is not evidence that nothing changed.
Resolve or restrict stale consumption. Recheck the controlling source, replace unsupported evidence, narrow the claim to the supported historical context or defer the current assertion. Do not treat stale support as current evidence simply because the next team is ready.
Check affected downstream work again. Identify drafts, tables, graph assertions, recommendations and approvals that relied on the source. Repair the affected units and bind the new acceptance to the new evidence. Retain unrelated accepted work when its support remains applicable.
Close with evidence and a next trigger. Record the new observation or unresolved result, responsible reviewer, current usability, limits and next review event. Expiry changes the allowed use; it does not erase the previous evidence or manufacture an external outcome.

Questions about freshness and expiry

Does a working URL prove that the information is current?

No. Confirm the relevant statement, source version and applicable scope. A reachable address can serve changed, old or differently scoped content.

Should every source expire after the same number of days?

No. Use claim volatility, consequence, scope and known events. The article’s classes illustrate a policy design; they do not establish universal time limits.

Is old evidence necessarily false?

No. It can remain valid historical evidence while failing the policy for an unqualified current claim. Retain the dated saved observation and review the intended use.

Can an event reopen a recent source?

Yes. A release, policy change, appointment or contradictory observation can make a recent saved observation insufficient for a new current claim before the scheduled review date.

Does fresh evidence guarantee SEO outcomes?

No. It supports a bounded current or historical statement. It does not guarantee indexing, rankings, citations, search features, traffic or conversions.