Anywhere structured. Google Sheets and Airtable work well for editor-first teams, MySQL or PostgreSQL work well when rubs overlap with a larger inventory system, and a flat JSON file in the repo works for static catalogs. SleekRank reads any of them via the matching data source type.

Either a type field on each row (dry vs paste) or separate rows for each version with a shared parent slug. Most catalogs use separate rows because each version pulls its own long-tail traffic and the comparison itself becomes a third page.

Yes. Store ratios in one canonical unit per row and render a client-side unit toggle in the base page. The data stays consistent and the template handles conversion at view time.

Yes, when the Recipe JSON-LD is populated correctly. SleekRank renders it from the same row that feeds the page, so as long as name, ingredients, and instructions are on the row, the schema is valid and rich-result eligible.

Each ingredient in the array carries a product slug. A list mapping renders the ingredient name as a link to the product page, so a rub recipe naturally drives spice sales without manual interlinking.

Store a price field per spice and a quantity per ingredient, then compute total cost in a build step and cache it on the row. SleekRank reads whatever the row contains, so the cost calculation lives in the source pipeline.

A single heat_level field per row (low, medium, high, or a numeric scale) drives the page badge, the index filter, and the schema keyword. Editors set one value and the platform handles the three downstream uses.

Yes, that is the point of separating data from layout. Editors work in Google Sheets or Airtable. The WordPress side handles only the template, so recipe testers and product managers never need a CMS account.