Pescatarian readers cook fish and shellfish as the primary protein and plants as the foundation. Every recipe needs a clear protein source, a sustainability note on the seafood used, and macros that lead with protein and omega-3 content. Cross-filter by sustainability rating and fish family is the discovery shape, so the metadata is the navigation layer of the library.

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

Sustainability sourcing lives on the row alongside the ingredients. One edit to a 'salmon source recommendation' cell updates every recipe that calls for it. Recipe developers maintain the sheet, the published pages stay coherent across hundreds of dishes.

Pescatarian publishing sits at the intersection of cuisine and ethics. The reader picks dishes by fish family, by season, and by sustainability standing, and a corpus that surfaces only one of those filters loses the other readers. Hand-built sites rarely keep all three current because the editor cost of maintaining sourcing notes across hundreds of posts is too high.

The corpus drifts: some recipes carry sustainability ratings, others skip them, omega-3 values are guessed on some pages and precise on others, and Recipe schema is patchy. Programmatic generation removes that drift because the sourcing rating and the fish family live as columns on the row, and the template reads them the same way every time. Long-tail pescatarian queries (sustainable salmon dinner, high-omega-3 lunch, Mediterranean seafood recipes under 30 minutes) reward libraries that publish every variant at a clean URL with consistent metadata.

The publishers who maintain the recipes in a sheet ship the filtered indexes for free as a byproduct of consistent tagging, and the editorial side gets to focus on developing and photographing recipes rather than maintaining metadata.