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

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

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

Map year, make, model, mileage, color, and reserve into a JSON-LD Vehicle and Product node via a meta mapping. Validate one lot with Google's Rich Results Test, then trust the template across the full roster.

Yes. Store the VIN and the report URL as columns and render both through selector mappings into a vehicle details block on the lot page. Buyers can pull the history without leaving the listing.

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

Each model hub lists different model years, different trims, and different mileage ranges. Give each hub a unique intro paragraph driven by the model row, and the corpus reads as a working catalog index rather than a templated swap.

Yes. Build the watch and bidding widgets once into the base WordPress page and inject the lot ID via a selector mapping into a hidden field. Watch list and bid submissions route to the correct lot in the auction backend automatically.