Both are supported. Reverb shops can export listings as CSV and SleekRank reads that file. Shops that maintain tech notes in a Google Sheet can share read-only with the SleekRank service account and SleekRank pulls on each cache refresh.

Include year and stock in the slug. The example fender-twin-reverb-1973-stock-415 uses brand, model, year, and stock so multiple identical amps coexist on the site. The sheet needs a stable identifier column for the slug to be deterministic.

Tube date codes is a list column in the row, one entry per tube position. Map it via a list mapping that renders a tube table with position and date code. Buyers can verify originality without leaving the URL or contacting the shop for photos directly.

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

The page group renders any amp type. Add a type column to the row. The template adjusts spec fields conditionally via a selector mapping, so heads show output transformer impedance options and combos show speaker config, all in the same URL pattern.

Yes if the row carries required Product fields. Map slug, name, image, brand, condition, offers price, and offers priceCurrency. The rich results test flags any missing fields so the shop patches the tech notes rather than the template per amp.

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.

Add a status column. Filter the page group on status equals available. Amps on the bench stay in tech notes but do not render URLs. When the bench check passes, the next cache refresh creates the page automatically without staff manual intervention.