Yes. Reverb lets shop owners export inventory as CSV. Point SleekRank at that file via a file data source, set the slug column, configure cache duration, and the plugin renders one page per row. Re-upload the CSV when stock changes or feed a Google Sheet kept in sync with Reverb through Zapier, a shop management tool, or a scheduled export job that runs nightly.

Store image URLs in one column as a comma-separated list or a JSON array, then use a list mapping that fans them into your existing slider, masonry, or lightbox block. Include bell shots, valve detail, and serial number shots as separate URLs. The base page handles the layout; the data only supplies URL strings, with no per-horn image upload required on the seller's part.

Remove the row or mark availability as sold. On the next cache refresh, the URL returns 404 and drops from the sitemap. If you prefer a soft sold badge, keep the row and set availability to sold; the selector mapping renders the badge and disables the buy button while preserving the URL for buyers who bookmarked the page from a Google result earlier that week.

Each page is unique by serial, year, condition, finish, and price. Two Bach 180S37s have different serials, different ages, different setups, different wear, and different photos. As long as the description block, photos, and structured data differ per row, this is not duplicate content. Search engines treat each horn as its own page and rank each independently for its identifiers.

Yes. Run a second page group at /trumpets-for-sale/{slug}/ filtered to trumpet rows, a third at /trombones-for-sale/{slug}/, and so on. The data source supports a filter expression so one inventory sheet feeds multiple URL patterns without duplicating rows or maintaining parallel data sets for each family across the entire shop catalog.

Yes. Map maker, model, family, price, availability, and image to a JSON-LD Product block via a meta mapping. Google treats brass instruments as Products and surfaces them in shopping rich results when offers, availability, and price are present. Validate once with the Rich Results Test and the schema applies to every generated horn page across the catalog without any extra work.

Add bore_size and key columns to the source data. A selector mapping renders each as a chip in the spec table on the base page. Brass buyers care deeply about bore for resistance and key for repertoire fit; making both scannable on the listing lifts conversion compared to burying them in a description paragraph that few buyers actually scroll through carefully.

Yes. Add an audio_url and video_url column with SoundCloud or YouTube links. Use selector mappings that swap the iframe src on the base page for that row. Brass buyers care about tone and response, and a short clip or video per horn lifts conversion and time-on-page meaningfully. Empty values hide the audio or video block via a conditional mapping that checks for a non-empty value at render time.