Anywhere structured. Google Sheets and Notion suit editorial teams without engineers; JSON files in the theme suit static archives; REST endpoints suit teams already running a recipe service. SleekRank reads any of these via the matching source type.

Yes. Add a wok-material column and split related-recipe clusters by that field. Some recipes apply to both materials, others (high-heat sears that ruin non-stick coatings) only run on carbon steel, and the filter keeps the clusters honest.

Yes. A meta mapping pointing at a JSON-LD script tag produces full Recipe schema per page, including name, recipeIngredient, recipeInstructions with step timings, recipeYield, and totalTime drawn from the row. Google's recipe rich results pick it up cleanly.

Store a heat note per row and a reusable safety block keyed by burner type. A selector mapping drops the right note into every recipe, so home-burner adaptations and high-output-burner recipes carry the right context.

Yes. Add an ingredient-link column or a JSON map of ingredient slugs to affiliate URLs, then run a list mapping over the ingredients block. New ingredients inherit links automatically when added to the map.

Add an aliases column and either render the aliases inline or redirect alias slugs to the canonical URL via your normal WordPress redirect plugin. The canonical row still owns the schema and the structure.

Each page targets a different dish, so internal competition stays low. Recipes that share a method sit inside related-recipe clusters that pass intent between them rather than competing for the same query.

The source system owns history. Google Sheets keeps version history, Notion logs edits, and JSON in git carries commit history. SleekRank reads current state on each cache cycle, so a test-kitchen change rolls out site-wide on the next refresh.