Add a dried_fresh_ratio column with the canonical conversion (1 tbsp fresh = 1 tsp dried, or 3:1 fresh-to-dried). Use a tag mapping to render the ratio in a structured callout. Recipes link to herb pages assuming the ratio is correct; one canonical column means every recipe-linked page tells the same story.

Yes. Add a substitutions array column with herb slugs and use a list mapping to render them as linked chips. The relationship lets readers landing on a basil page (looking for a substitute) cross over to oregano or thyme, all driven from one canonical dataset. Slug-based linking keeps the network intact across renames.

Add a culinary_uses array column with controlled values (Italian, French, Middle Eastern, Mexican, Thai, Indian, Mediterranean) and a use_styles array (sauces, marinades, garnish, infusions, herb butter). List mappings render both as chips. Editors who try to write 'Italian cuisine' or 'pasta sauces' get caught at data-entry time because the column accepts only canonical values.

Add separate columns for sun_requirement (full sun, partial shade), soil_type, water_needs, and a growing_notes paragraph. Tag mappings render the structured columns as a quick-facts grid; a selector mapping injects the longer growing-notes paragraph for context. Recipe-focused readers ignore the gardening fields; gardening-focused readers ignore the recipe fields. Same page serves both.

Yes. Add a companion_plants array column with plant slugs (or just names if you don't have plant pages) and use a list mapping to render them as chips. Companion planting is a common gardening question; surfacing the relationships consistently helps gardeners plan beds. Slug-based linking enables cross-pages later if you build out the broader plant reference.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template. Herb queries are long-tail and herb-specific ('basil substitute', 'how to grow rosemary'), so per-herb URLs matter more than category aggregations for organic traffic.

Recipe pages link to /herbs/{slug}/ in their ingredient lists. The herb pages provide substitutions, dried-fresh ratios, and storage advice that the recipe page doesn't have to repeat. The data-driven structure ensures every linked herb has the same fields available, so recipes never link to a herb page that's missing the substitution context.

Yes. Define one page group per cuisine, /herbs/italian/{slug}/, /herbs/thai/{slug}/, /herbs/indian/{slug}/. Each pointing at a cuisine-specific dataset. Many herbs (basil, mint, cilantro) play very different roles across cuisines; separate datasets let editorial reflect that without polluting a single canonical herb page.