Yes. Google Sheets is a supported data source. Share the sheet read-only with the SleekRank service account, paste the sheet ID into the page group config, and SleekRank pulls rows on each cache refresh. The sales team workflow stays unchanged.

Include stock number or consignor code in the slug. The example 5000gal-mueller-tank-stock-204 uses brand, capacity, and stock so multiple identical tanks coexist on the site. The sheet needs a stable identifier column for the slug.

Freight is destination-specific, so the page renders a freight calculator block in WordPress rather than a static figure. The block reads unit weight and dimensions from the row via a selector mapping and calls a freight API client-side.

Yes. Store gallery URLs as comma-separated string or JSON array in the row. Map the column to a list mapping that pushes URLs into the existing WordPress slider block. The block stays one element in the editor; the row drives the slides.

Yes. Add a status column with values available and sold. Configure the page group to render sold rows with a sold-badge variant via a conditional selector. The URL stays indexed, the schema price clears, and a sold tag appears in the listing.

Yes if the row carries the required Product fields. Map slug, name, image, brand, condition, offers price, and offers priceCurrency. The rich results test flags missing fields so you can patch the sheet rather than the template.

Yes. Each broker runs its own page group with its own URL prefix. The same underlying row may show at two URLs, each with its own price. If a canonical is needed, set rel=canonical on the duplicate via a meta mapping.

Add a status column. Filter the page group on status equals available. Units in inspection stay in the sheet but do not render URLs. When the inspector flips the status, the next cache refresh creates the page automatically.