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 or a shop management tool that runs nightly export jobs.

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 badge shots, shell interior shots, and hardware shots as separate URLs. The base page handles the layout; the data only supplies URL strings, with no per-kit 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 or month.

Each page is unique by badge type, shell sizes, finish, condition, and price. Two 1965 Ludwig Downbeat kits have different badges, different finishes, different wraps, 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. Each kit ranks independently for its own identifiers.

Yes. Run a second page group at /vintage-ludwig-drums/{slug}/ filtered to Ludwig rows, a third at /vintage-slingerland/{slug}/, and so on. The data source supports a filter expression so one inventory sheet feeds multiple maker-specific URL patterns without duplicating rows or maintaining parallel data sets for each maker across the entire shop catalog.

Yes. Map maker, era, shell sizes, price, availability, and image to a JSON-LD Product block via a meta mapping. Google treats vintage 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 kit page automatically across the catalog.

Add shell_sizes and badge columns to the source data. A selector mapping renders shell sizes as a chip row in the spec table and badge as a labeled chip. Vintage drum buyers care intensely about both for dating and value; making them scannable on every listing lifts conversion compared to burying them in a description paragraph that few buyers actually scroll through carefully.

Yes. Add a serial and a date_confirmation column with values like badge-verified or interior-stamp. Use selector mappings that render both on the spec table. Vintage drum dating is a real authentication concern; making the seller's confidence level visible on every listing builds trust with buyers and reduces inquiry back-and-forth before a kit ships out of the shop.