'Plant-based' covers a wider audience than vegan: readers who eat plants by default, sometimes include dairy or eggs, and often filter for whole-food versus processed. Every recipe needs a clear protein source (legumes, tofu, tempeh, seitan, nuts), a whole-food flag where the dish qualifies, and allergen tags for common cross-filters like gluten and soy.

SleekRank reads a recipe sheet and generates one page per row at /plant-based/{slug}/. Tag mapping handles the title and times, list mapping renders ingredient and step arrays, selector mapping fills in the macro card and whole-food badge, and meta mapping carries the Recipe JSON-LD and meta description. The base WordPress page handles photography and chrome.

Recipe developers maintain the sheet where protein-source and whole-food fields are easy to compare across the corpus. A new dish ships as a new row. The badges, macro card, filtered indexes, and Recipe schema all read from the same source.

Plant-based publishing is the wide tent of dietary content, and the audience is heterogeneous. Some readers are strict whole-food, others lean flexitarian, and most cross-filter by protein source, allergen, and cook time. A hand-built site usually serves one slice of that audience well and fails the rest because the editor effort to keep every dimension current is too high.

The corpus drifts within a hundred recipes: protein sources are inconsistently tagged, whole-food framing varies by author, and allergen badges appear on some posts and not others. Programmatic generation removes that drift because the protein source, the whole-food flag, and the allergen tags all live as columns, and the template reads them uniformly. Long-tail plant-based queries (whole-food plant-based lentil dinner, soy-free plant-based protein, plant-based meal under 30 minutes) reward libraries that publish every variant at a clean URL with consistent metadata.

The publishers who maintain recipes in a sheet ship those filtered indexes as a byproduct, and the editorial side gets to focus on developing recipes rather than maintaining metadata across hundreds of posts.