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. Sales team workflow stays unchanged.

The slug includes a stock number or consignor code. The example slug 30bbl-jvnw-unitank-stock-712 uses brand and stock number so multiple identical capacities coexist on the site. The sheet needs a stable identifier column.

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

Yes. Store gallery URLs as a 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; the row drives the slides.

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

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 any missing fields so you can patch the sheet rather than the template.

Each broker runs its own page group with its own URL prefix. The shared underlying unit may show up at three URLs, each with its own price. If the broker wants a canonical URL across all three, set rel=canonical on the duplicates 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.