A supplier's product page can remain available while its Merchant Center product record expires. The page and the record belong to different systems, and they answer different questions. One says that a website still serves the content. The other determines whether the submitted product data remains current for its intended use.
For a team managing an international catalogue, this distinction prevents a familiar detour: asking the website editor to fix an issue that actually sits in product-data maintenance. It also prevents the reverse mistake of extending a record that represents an offer the business no longer intends to sell.
This discussion applies to merchants already using Google Merchant Center. A general B2B brochure site without that integration does not acquire a product-expiry problem merely because a product page exists.
Compare the requested date with the processed state
Google's ProductAttributes reference distinguishes the submitted expirationDate from the actual expiration date exposed through product status as googleExpirationDate. The documentation notes that the actual date may be earlier when the submitted date is too far in the future.
The practical implication is narrow but important: looking at the outgoing request is not enough. An integration may have sent the date the team expected while the processed record has a different effective date. Inspect both for the same item before deciding that the platform ignored a change or that the website is unavailable.
Start by establishing that expiry is actually the reported issue. Failure to find a product in a search result does not identify the cause. A display problem can have other explanations, and a date-field theory should not replace the status information available for the affected item.
Make sure the comparison concerns the same product identity, language and target market. International catalogues can contain similar-looking entries whose treatment differs. A healthy record for another destination does not resolve the status of the entry under investigation.
Keep page maintenance, offer dates and record expiry separate
A product description may be edited without changing the commercial offer. A promotion may end while the product remains on sale. A product record may expire while its landing page continues to load. These events can coincide, but they do not have to.
If a team uses one undifferentiated “updated” date, responsibility becomes unclear. The content editor may believe that a page revision renewed the item. The feed operator may assume that an unchanged product needs no attention. The marketer may be talking only about a sale period. Each person can report completion while the original problem remains.
Trace the most recent intended product submission and its resulting status. If the product is still offered, determine whether the expected maintenance or synchronization occurred. If it has been withdrawn, check whether the website still presents outdated terms as current. Restoring distribution is not the right objective for an offer that should no longer be active.
Time-zone interpretation also deserves attention around a deadline. A local calendar date and a timestamp can describe different moments unless their offsets are understood. Compare like with like before treating a difference of hours as a missing day. This is especially relevant when a China-based operations team coordinates with an overseas marketing team.
Fix the reason, not just the visible symptom
Setting a distant date or creating a new identifier may seem quicker than investigating the old record. Neither action explains why it expired. Both can distract from a broken maintenance process or an outdated commercial decision.
First ask whether the business still intends to sell this item under the stated conditions. Then correct the relevant data or synchronization problem and inspect the processed result. Keep the original identifier where appropriate instead of using a new identity as a generic reset button.
Do not use expiry as a substitute for every availability state. A product awaiting manufacture raises a different buyer question from a record that has reached the end of its effective life. Our discussion of made-to-order products and stock claims deals with that supply promise. Treating the two issues separately helps sales and technical teams avoid answering different questions under the same label.
Finally, choose evidence that matches the repair. A screenshot of a functioning landing page proves little about the product record. Check the affected item's processed state and then the relevant channel behavior. Distribution may involve additional conditions, so a corrected date alone is not a promise of immediate exposure.
There is no need to refresh the public article or product-page date simply to make the website appear new. The useful change is the one that restores an accurate, maintainable product record for an offer the business still stands behind.
Sources
Google for Developers, Merchant API ProductAttributes, documentation updated September 4, 2026. The distinction between submitted and actual expiration dates is the source-backed technical point; the troubleshooting sequence is operational analysis.