Use a controlled-vocabulary regional_cuisines array column (Indian, Middle Eastern, Mexican, Thai, Mediterranean, North African, Central European, Caribbean) and pick one term set per site. List mappings render the array as chips. Editors who try to write 'Indian cuisine' or 'Persian-Indian' get caught at data-entry time because the column accepts only canonical values.

Yes. Either as one row per variety (slug ceylon-cinnamon, slug cassia-cinnamon) or as a single cinnamon row with a varieties array column documenting the differences. Most reference sites split into separate pages because the botanical sources differ (Cinnamomum verum vs Cinnamomum cassia) and the flavor profiles diverge significantly. The dataset shape supports either approach.

Add a heat_level column with controlled values (none, mild, medium, hot, very hot) and use a tag mapping to render it as a colored badge. For chiles specifically, also store a Scoville range column with min and max units; a separate selector mapping renders the Scoville bracket. Heat level is one of the most-asked-for spice fields, so making it visually prominent helps reader scanning.

Add a substitutions array column with spice slugs and use a list mapping to render them as linked chips. The relationship lets readers landing on a saffron page (looking for a substitute) cross over to turmeric or paprika as visual substitutes. Slug-based linking keeps the network intact across renames, and the chips link readers to other per-spice pages on the same site.

Add a whole_vs_ground column or paragraph documenting flavor-loss timelines, grinding tips (mortar and pestle, spice grinder, microplane for nutmeg), and storage advice for each form. Many spices lose their flavor much faster ground (cumin, cardamom, peppercorn); surfacing the difference consistently helps readers buy and store correctly.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template. Spice queries are long-tail and spice-specific ('cumin substitute', 'how to use saffron'), so per-spice URLs matter more than category aggregations for organic traffic.

Yes. Add separate columns for shelf_life (12 months ground, 4 years whole), storage_method (airtight, dark, cool), and freezer_safe (yes/no). Tag mappings render the structured columns as a quick-facts grid; a selector mapping injects a longer storage paragraph for context. Spice freshness is often misunderstood; structured fields make the right answer obvious.

Add a product_url column and conditionally render a 'shop this spice' CTA via a selector mapping. The reference page becomes an educational entry point that links to the commerce side without conflating the two. Keep the educational content separate from inventory state so reference pages remain useful for non-purchase intent (recipe research, gifting research, cooking exploration).