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

Use a status column with values like upcoming, live, sold, withdrawn, passed. Route sold lots to /estate-auctions/past/{slug}/ via a second page group while removing them from the live one. The hammer price persists as comparable history, the live listings stay clean.

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

Map maker, category, dimensions, condition, and provenance into a JSON-LD Product node via a meta mapping. Validate one lot with Google's Rich Results Test, then trust the template across the entire catalog.

Store provenance as a JSON array of ownership entries with date, owner, and source columns. A list mapping renders them as a timeline on the lot page, and the same data feeds the structured data schema.

If the platform exposes a CSV export or a REST endpoint for lots, SleekRank can pull from either. Bidding stays in the auction software; SleekRank owns the public catalog and SEO layer.

Each category hub lists different makers, different estates, and different price ranges. Give each hub a unique intro paragraph driven by the category row, and the corpus reads as a working catalog index rather than a templated swap.

Yes. Build the inquiry form once into the base WordPress page and inject the lot number via a selector mapping into a hidden field. Inquiries from each lot URL route to the specialist responsible for the category automatically.