Yes. Export the AOS member listing to CSV or keep grower inventory in Google Sheets, and point SleekRank at either source. Configure the slug column and a cache duration that matches your bloom cycle and sales updates, and the plugin renders one indexable page per plant with parentage context.

Add columns for pod_parent, pollen_parent, and awards as a JSON list. Selector mappings render the cross as a clear parentage block, and a list mapping renders the awards as a structured table. Collectors see the full lineage and award history without searching the AOS database manually for citations.

Remove the row or set a status column to sold. On the next cache refresh, removed rows drop to 404 and clear from the sitemap. Status-based sold badges work if you want to preserve the URL and the inbound links from prior society forum shares or auction site posts that drove buyers to the listing.

Yes. Add a stage column with values like flask, compot, seedling, blooming_size, near_bloom, and division. A selector mapping renders the stage as a colored badge in the H1 area and lets collectors filter or search by exactly the maturity they want to acquire for their growing conditions.

Yes, when genus, species, stage, parentage, awards, pot size, and parent flower photos vary per row. Per-plant variation is the point. Add a notes field per plant with growing observations and each page has plenty of unique signal to rank against flat AOS member directory pages for the long tail.

Yes. Map genus, price, availability, and image to a JSON-LD Product mapping. Google indexes orchids as commercial offers when the schema is present. Add additionalProperty entries for stage and award count so the rich result reflects the maturity and lineage context that collectors search for in their queries.

Keep CITES and import rules on the base WordPress page so every plant inherits the latest documentation requirements. Add a column for cites_required and render a conditional notice via a selector mapping when a species needs CITES paperwork for international or interstate shipping to specific destinations.

Yes. Run a second page group at /cattleya-orchids/{slug}/ filtered to Cattleya rows, and a third at /orchid-flasks/{slug}/ filtered to stage equals flask. The data source supports filter expressions so one grower catalog feeds multiple URL patterns without duplicating rows or maintaining parallel inventory sheets.