Yes. Run a second page group with /wine-auctions/producer/{slug}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where producer matches the slug and renders every lot from that estate. One catalog, two URL patterns, no duplicate maintenance.

Use a status column with values like upcoming, live, sold, withdrawn. Route sold lots to /wine-auctions/past/{slug}/ via a second page group while removing them from the live one. The lot history persists as social proof and provenance reference, the live listings stay clean.

Yes. Store image URLs as a JSON array column. A list mapping renders them into whatever gallery block you built on the base WordPress page, whether slider, lightbox, or grid. The data supplies URLs only, the gallery design lives in the theme.

Map producer, vintage, region, reserve, and currency into a JSON-LD Product with an Offer node via a meta mapping. Validate one lot with Google's Rich Results Test, then trust the template across the entire catalog.

Provenance is usually a paragraph or a list of prior owners; condition notes are typically a short paragraph plus a numeric score. Store both as columns and render them through selector and list mappings into the dedicated sections on the lot template.

If the platform exposes a CSV export or a REST endpoint for lots, SleekRank can pull from either as the data source. The bidding interface keeps living in the auction software; SleekRank only owns the public marketing and SEO layer.

Each region hub lists different producers, different vintages, and different price ranges. Give each hub a unique intro paragraph driven by the region row, and the corpus reads as a real catalog index rather than a templated swap.

Yes. Build the watch and bidding widgets once into the base WordPress page, then inject the lot ID via a selector mapping into a hidden field. Watch requests and bids on each lot URL route to the correct lot in the auction backend automatically.