Yes. Export the catalog as CSV and point SleekRank at it via a file data source. Configure the column that holds the slug, set a cache duration, and the plugin renders one page per row. Re-upload the CSV when stock changes, or schedule pulls from a Google Sheet kept in sync with your inventory system.

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 the URL strings. No per-listing image upload.

Remove the row from the sheet. On the next cache refresh, the URL returns 404 and drops from the sitemap automatically. If you want a soft sold-out badge instead, keep the row but set an availability field to sold; the selector mapping renders the badge and disables the buy button.

Each page is unique by cultivar, variegation grade, parent plant, and price. As long as the lead paragraph, photos, and structured data differ per row, this is not duplicate content. Variegation grade alone provides meaningful per-page variation across cuttings of the same cultivar.

Yes. Add a parent_plant_slug column and use a selector mapping to render a link to the mother plant's URL. The mother plant gets its own page via a separate row in the same sheet, creating an internal linking graph that helps Google understand cultivar relationships.

Yes. Map cultivar, price, availability, and image to a JSON-LD Product block via a meta mapping. Google treats plant cuttings as Products and surfaces them in shopping rich results when offers, availability, and price are present. Validate once with the Rich Results Test.

Keep the shipping disclaimer block on the base WordPress page so every cutting inherits the latest copy. Add a column for prohibited_states if some cultivars are restricted, and render a warning via a conditional selector mapping when that field is non-empty.

Yes. Run a second page group at /monstera/{slug}/ filtered to Monstera rows from the same sheet, and a third for Philodendron. The data source supports a filter expression so one inventory sheet feeds multiple URL patterns without duplicating rows.