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 script 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, neck, key work, 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 step 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 in the week.

Each page is unique by serial, year, pad condition, finish, and price. Two Selmer Mark VI tenors have different serials, different ages, different overhauls, and different photos. As long as the description, photos, and structured data differ per row, this is not duplicate content in the eyes of search engines and each horn ranks independently for its own identifiers and pad history.

Yes. Run a second page group at /saxophones-for-sale/{slug}/ filtered to saxophone rows, a third at /clarinets-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 over time.

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

Add pad_age_years and last_overhaul columns to the source data. A selector mapping renders pad age as a chip and last overhaul as a labeled cell in the spec table. Saxophone and clarinet buyers care intensely about pad health for playability; making both scannable on every listing lifts conversion compared to a vague description paragraph buried halfway down the page.

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. Woodwind buyers care about tone, response, and intonation. 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 at render time.