What a link chain can contain
A single saved row may connect several surfaces: an album, a catalog result, a raw marketplace listing, a reformatted agent link, and a checkout page. Those pages can change independently. A link chain is useful only when you know what role each page plays today.
- Presentation
- An album or catalog page that helps identify or visually inspect an item.
- Source
- A raw marketplace or product listing that may provide options, seller context, and price basis.
- Reformatted link
- A third-party route that imports or translates a source URL for another interface.
- Checkout
- The surface where current transaction terms, payment, and protection are actually presented.
Capture the chain before comparing it
Save the original URL for each page, not only the last redirect. Record the visible title, item code, selected option, seller or uploader name when shown, and review date. If a page redirects, preserve both the starting and destination URLs.
Run four match checks
- Identity: Do the product type, code, construction, color, and distinctive details agree?
- Option: Are size, color, quantity, model, and package configuration aligned?
- Price basis: Does the number refer to one item, a range, a deposit, a minimum quantity, or a different variant?
- Page owner: Are seller, uploader, storefront, contact, or watermark details consistent—or at least not contradictory?
A match in one field does not cancel a mismatch in another. A shared photograph is especially weak when the code, option, or source page differs.
Assign one status
Key fields agree
Identity and selected option align, and no page introduces a material contradiction. Record what was checked and the review date.
Evidence is incomplete
The pages may refer to the same item, but a code, option, price basis, or source owner still needs confirmation.
A material field conflicts
The product, code, option, seller, or price basis differs. Separate the pages into different rows or archive the chain.
How to treat redirects and reformatted links
A reformatted link can be convenient, but it is not the evidence source. Compare its underlying marketplace URL with the raw listing whenever possible. Confirm that the item ID, selected option, displayed price, and seller context were not lost or replaced during import.
- Keep the raw source URL in its own field.
- Do not infer current stock from a successful import.
- Do not infer seller verification from a familiar agent interface.
- Recheck the destination when a redirect changes.
Worked example: similar photos, different option
An album shows a black shoulder bag with silver hardware. The source page opens a listing with the same silhouette, but its selected option is brown with gold hardware. The chain is not matched. It may become resolved after selecting the correct option, but until then the row should say “unresolved—variant conflict,” not “confirmed.”
Copy-ready audit record
Album or catalog URL: [link]
Raw source URL: [link or missing]
Other route: [agent / redirect / checkout link]
Identity check: [agree / conflict / unknown]
Option check: [agree / conflict / unknown]
Price-basis check: [agree / conflict / unknown]
Owner check: [agree / conflict / unknown]
Status: [matched / unresolved / mismatched]
Reviewed: [date]