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.

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. The base page is the design surface; the data only supplies URL strings. No per-ukulele image upload, no reprocessing, and the marketplace hosted images keep working without any extra storage on your own server.

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 serial number, year, condition, finish, and price. Two Kamaka HF-3 tenors have different serials, different ages, different setups, 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 instrument as its own page and rank accordingly for specific identifiers.

Yes. Run a second page group at /tenor-ukuleles/{slug}/ filtered to tenor rows and a third at /concert-ukuleles/{slug}/ filtered to concert rows. 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 size category in the same catalog.

Yes. Map brand, model, size, price, availability, and image to a JSON-LD Product block via a meta mapping. Google treats ukuleles 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 ukulele page automatically without any extra per-listing work.

Add body_wood and top_wood columns to the source data with values like Hawaiian koa, mahogany, mango, or acacia. Use a selector mapping that targets the spec table on the base page and renders each value as a colored chip. Players care about wood for tone; making it scannable on the listing lifts conversion compared to a buried paragraph in a description block.

Yes. Add an audio_url column with a SoundCloud or YouTube link. Use a selector mapping that swaps the iframe src on the base page for that row. Ukulele buyers care about tone, and a short clip per instrument lifts conversion and time-on-page. Empty values hide the audio block via a conditional mapping that checks for a non-empty field value at render time on every request.