No. Ranking decisions live entirely in your data. SleekRank only orders the filtered swaps by the rank column you maintain. The editorial work of deciding whether yogurt or sour cream is the better buttermilk swap stays with your test kitchen; the template just executes the order in the sheet.

Yes, that is a normal pattern. "Greek yogurt" might appear on /substitute-for/buttermilk/, /substitute-for/sour-cream/, and /substitute-for/mayonnaise/, each with its own ratio and notes. Keep one row per swap-ingredient pair in the swaps sheet; edits to a row affect only the page where that pair appears.

Carry boolean columns on the swaps sheet like is_vegan, is_gluten_free, and is_dairy_free. Render badges from those columns, and let the template show a filter UI that hides swaps where the relevant flag is false. The same data drives both the badges and the filter consistently.

Append a row to the ingredients sheet with slug, name, category, and intro. Add its swap rows to the swaps sheet with ratios, notes, and dietary tags. After cacheDuration elapses or you clear the items table, /substitute-for/{slug}/ resolves and lands in the sitemap on the next rewrite flush.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new ingredient rows start getting crawled after the next rewrite flush.

Yes. Use meta mapping at og:image pointing to a per-ingredient image URL column, or pair with SleekPixel and a templated suffix so /substitute-for/buttermilk/ and /substitute-for/cornstarch/ each render their own preview with ingredient name and swap count without manual asset work.

Yes. Add the JSON-LD block to the base template once and inject ingredient-specific values like name and swap steps through selector or meta mappings. Each /substitute-for/{slug}/ renders its own valid schema sourced from the matching ingredient and swap rows.

Delete the row from the swaps sheet, or flag it inactive with a status column the list mapping respects. Flush the cache and the swap disappears from every substitute page simultaneously. Keep an archive column if you want to retain the row for historical context without rendering it.