Freshness means the same product is still reachable
A spreadsheet row is fresh only when its current destination still represents the product family and option the row describes. A page can return a successful response while showing a different item, a generic marketplace screen or a seller storefront. Technical availability is therefore the first test, not the conclusion. Open the final page and compare the meaning of its title, first image, identifier and option structure.
Record both the stored URL and the final URL after redirects. If they differ, decide whether the change is harmless tracking cleanup, a canonical product address or a move to unrelated content. Do not update the checked date until the destination has passed the identity test. A timestamp attached only to a network response creates false confidence and makes the next editor repeat the same work.
Keep the evidence fields separate while you work: source URL, final destination, visible product identity, exact option, displayed price, domestic freight and check time. A blank field is an open question, not permission to copy a value from a similar listing. This record makes a later recheck faster and prevents a spreadsheet snapshot from being mistaken for a current seller promise.
Prioritize rows by buyer impact
Begin with links placed on prominent pages, links receiving outbound clicks, products used in multiple category routes and rows that have redirected before. These entries can mislead more visitors than a quiet archival row. A second group includes volatile listings with many options or unusually low displayed prices, because their visible headline may outlive the variant that produced it.
Use a simple queue with last checked date, traffic importance, prior result and next action. This turns maintenance into a controlled review rather than random browsing. The queue also shows when a large spreadsheet is carrying more stale inventory than the team can responsibly inspect. A smaller active set with clear evidence often produces better clicks and fewer immediate returns to search.
Use three result labels: matched, partial and mismatch. Matched means the destination and required option agree with the saved record. Partial means the product family is plausible but one decision field is missing. Mismatch means the page is dead, redirected to another item or no longer carries the intended choice. Only matched candidates should proceed without another question.
Separate link state from listing state
Link state describes whether the address loads, redirects or fails. Listing state describes whether the expected product, option, price field and domestic delivery information are still present. Keep those outcomes in separate columns. A working link with a missing size is not healthy for a buyer who needs that size, while a clean redirect to the same canonical item can remain usable after documentation.
Add a short reason code such as exact match, option removed, price unclear, login blocked, seller page, product changed or dead. Reason codes make patterns visible: one marketplace may change URL formats while one seller repeatedly replaces listings. They also support selective repair. Editors can fix a stable canonical redirect quickly and retire an identity mismatch without arguing over a vague pass-or-fail label.
Do not turn price, sales activity, a familiar image or inclusion in an index into a quality claim. Those signals can help prioritize inspection, but they do not prove construction, authenticity, seller service or the condition of the unit that reaches the warehouse. The useful comparison is evidence quality and order readiness, not an unsupported best-product ranking.
Recheck price, quantity and domestic freight
Displayed price needs the selected option and quantity context. Marketplace pages may lead with the cheapest variant, a wholesale tier or an expired promotion. Open the option selector, note the intended color or model, set the relevant quantity and capture the price that corresponds to that exact combination. Keep currency and check time in the same record.
China domestic freight is a separate live field. A row that preserves product price but omits seller-to-warehouse delivery can understate the first payment. Do not manufacture a zero when the field is hidden or calculated later. Mark it unknown and require a checkout recheck. The goal is not to publish a permanent total; it is to show which components a buyer must confirm before paying.
Before payment, save the live page and the option text that the ordering flow accepts. If the source cannot be parsed and a manual order is needed, treat every typed field as buyer-supplied. Compare the resulting order summary against the saved record before money moves. A near match is still the wrong instruction when size, color, model or quantity differs.
Handle redirects without hiding history
When a destination changes, preserve the previous address in the maintenance log and store the current final address separately. This protects the audit trail and helps identify whether the old row was genuinely repaired. If the new page is a different item, do not overwrite the row just because the replacement looks similar. Create a new candidate with its own image, ID and checked date.
If a marketplace requires sign-in or serves different content by region, report that limitation. Another reviewer may be able to verify the page from an active account, but absence of access is not evidence of stock. Use partial status until the identity and required option can be seen. This prevents a blocked page from being promoted as verified merely because it once worked.
Write one explicit stop condition for every shortlist. Examples include a missing measurement, an unexplained redirect, a price attached to the wrong quantity tier, an unavailable color or a product identifier that cannot be reconciled. Stopping is a valid research result. It is cheaper than relying on warehouse photos to solve an uncertainty that existed before purchase.
Publish only the result a buyer can use
A buyer-facing row should expose the category, concise item label, destination, last meaningful check and any limitation that changes the decision. Internal repair notes, tracking parameters and speculative seller commentary do not belong in the visible title. Write descriptions that match search intent: help the visitor locate and verify a route, not promise quality or availability that the index cannot control.
Remove or clearly label rows that remain partial after the review window. Keeping every old link visible may increase the numerical size of a spreadsheet, but it dilutes trust and sends users to dead ends. A useful freshness program measures confirmed destinations, unresolved rows and retirements. Raw row count is not a success metric when the objective is qualified clicks to a live product page.
At warehouse arrival, use the saved listing as the reference for QC rather than relying on memory. First confirm identity and option, then inspect condition and the details that matter for use. Request an additional photo or measurement only when it can change the keep-or-return decision, and review the active account promptly because seller eligibility and return timing still apply.
Use a repeatable monthly review
Schedule a broad review for stable rows and a faster cycle for high-click or previously unstable destinations. Each pass should reopen the link, compare identity, inspect the intended option, record live commercial fields and set the next review date. Changes discovered through user reports should enter the same queue so emergency fixes do not bypass documentation.
Track outcomes over time: match rate, partial rate, mismatch rate, redirect rate and outbound click-through after repair. If a category earns impressions but few product clicks, improve titles and candidate relevance before adding more rows. If clicks are high but mismatches rise, shorten the refresh interval. The maintenance record then connects SEO traffic with the quality of the destination experience.
Maintain the page as a dated research route. Reopen high-use links first, follow redirects, compare identity and option structure, and update a checked date only after a real review. If a link changes, label or remove it instead of silently replacing the destination while preserving the old image or product ID. Transparent maintenance is more valuable than a larger but ambiguous list.
