Offer Validity Dates vs. a Page's Update Date: What Actually Decides If an Offer Is Still Live

A recent ‘last updated’ stamp on a page does not tell you whether a commercial offer is still valid. This article separates the offer’s own declared validity interval from the document’s edit date, explains the documented validFrom and validThrough vocabulary in its supported Offer scope, and gives a concrete procedure for deciding whether an offer is currently live — plus what to do when the term is missing or appears expired.

The offer’s own clock, not the page’s

You land on a page that describes a discount, an incentive, or a promotional term. Near the top there is a date — ‘last updated’ or ‘last modified’ — and it is recent. It is tempting to read that freshness as proof the offer is still live. It is not. A page’s update date is a document-editing signal: it records when someone changed the page. It does not, by itself, state when a commercial offer starts or ends.

An offer’s validity is expressed through its own declared start and end terms. Schema.org defines validFrom as the date when the item becomes valid, and validThrough as the date after when the item is not valid, giving the end of an offer as one example. Those two terms describe the offer’s own clock. The page’s edit date describes the document’s clock. They are different clocks, and only one of them governs whether the offer is live.

So the reader’s decision is this: before treating a fresh-looking page as proof that an offer is live, find the offer’s declared interval and check it. If the page shows a recent edit date but no declared start or end for the offer, you do not yet have the information you need to conclude the offer is valid.

Source reference

What validFrom and validThrough actually say

The vocabulary you are looking for is documented on Schema.org. The validFrom property page states that it is the date when the item becomes valid. The validThrough property page states that it is the date after when the item is not valid, and it explicitly gives the end of an offer as an example. Read together, they describe a start and an end: the moment the item becomes valid, and the moment after which it is not.

Both properties are listed as used on the Offer type. That is the supported offer scope: when you are reading a commercial offer, these are the terms that describe its declared interval. Both properties also expect values of type Date or DateTime, so the declared term may appear as a calendar date or as a date with a time.

One more detail is worth knowing because it tells you these terms are not a Schema.org invention. Each has an equivalent property in another vocabulary: validFrom is equivalent to cmns-dt:hasStartDate, and validThrough is equivalent to cmns-dt:hasEndDate. The start/end framing is the intended reading.

Reading an offer’s interval against today’s date

With the vocabulary in hand, the decision procedure is short. Find the offer’s declared start and end. Compare the current date to both. If today is before the declared start, the offer is not yet valid. If today is after the declared end, the item is not valid. Only when today falls inside the declared interval — at or after the start and at or before the end — is the offer within its own stated window.

This is a hypothetical illustration, not a real client case or observed test. Here is a hypothetical example to make the failure mode concrete. Suppose a page carries a ‘last updated’ stamp from this week and advertises a promotional term whose declared end date has already passed. The page is fresh; the offer is not. The correct conclusion is that the offer is outside its declared interval, and the recent edit date does not change that.

This is a hypothetical illustration, not a real client case or observed test. Now the other failure mode. Suppose a page describes an offer with a declared start but no declared end. It is tempting to read ‘no end date’ as ‘open-ended offer.’ That is not what the absence of a term means. An absent end term is simply absent information; it is not a statement that the offer continues indefinitely. The same logic applies to an absent start term. Missing is missing, and it should send you to the seller rather than to a conclusion.

When the term is missing or expired: confirm with the seller

If the offer’s declared term is absent, or if it appears to have passed, the next action is to confirm the current terms with the seller. Do not infer renewal from a recent page update. The page’s edit date is not a substitute for the seller’s confirmation, because the edit date tells you about the document, not about the offer’s declared interval.

A caution about what you can and cannot conclude from the page alone. Whether a specific seller reviews or renews its offer wording is unknown from the page. You cannot tell from a recent edit date whether the seller re-checked the offer, extended it, or simply fixed a typo. Treat this as a buyer check — ask the seller — rather than as an assumption in either direction. The same applies to the opposite assumption: a stale-looking page does not prove the offer has lapsed if the declared interval is still open.

Why this matters for GEO and structured offer data

For a content or GEO team, the practical reason to care is accuracy. The validFrom property page reports usage across 100K–1M domains, and the validThrough property page reports usage across 1M–10M domains, both based on monthly aggregations from Google’s web index (Google – August 2026). These are widely used terms, which means readers and systems have a reasonable expectation that a declared interval means what it says.

Keeping an offer’s declared interval accurate is a content-accuracy concern. It is not a guarantee of AI citation, ranking, or indexing. No formatting choice, structured-data field, or page edit can promise that an AI system will surface your offer or that a search engine will rank it. What you can control is whether the declared interval on the page matches reality — and that is the part the reader is actually relying on.

If you are building the governance side of this — deciding when evidence should be updated, downgraded, or withdrawn — the GEO evidence expiry workflow covers that decision. And if the problem is propagating a corrected fact across pages, locales, and structured data, the GEO source update governance guide addresses the notification chain. Both are adjacent to this topic but answer different questions: this article is about reading an offer’s own declared interval, not about managing an evidence library.