Nut allergies are reactive, not preference-driven. Readers search for very specific safe alternatives: "nut-free pesto," "school lunchbox brownies," "sunflower butter cookies," "tree-nut-free granola." Each recipe needs a clean ingredient list, an explicit cross-contact note, and a visible swap when the standard version uses almonds, walnuts, or peanuts.

SleekRank reads a recipe sheet and generates one page per row at /nut-free/{slug}/. Tag mapping handles the title and time fields, list mapping renders the ingredient and step arrays, selector mapping fills in the school-safe badge and swap card, and meta mapping carries the Recipe JSON-LD and meta description. The base template covers the photography, hero, and disclaimer chrome.

Swap notes and cross-contact warnings live on the row. One edit to the "sunflower butter brand" cell updates every recipe that calls for it. Recipe developers maintain the sheet, the published pages stay coherent across hundreds of dishes.

Nut-free publishing has two structural problems that hand-built WordPress sites rarely solve. The first is volume. A real nut-free library covers hundreds of dishes (baking, school lunches, dinners, dressings, snacks) and each one needs accurate swap notes, cross-contact warnings, and Recipe schema.

Editors who type each page from scratch produce a corpus that reads inconsistently within the first hundred entries. The second is trust. Nut allergies are reactive, so readers scan for explicit allergen language on every page.

A site that buries cross-contact notes or skips them on some pages loses readers permanently. SleekRank moves the writing into a sheet where the safety fields live as columns and the recipe template reads them uniformly. Swap brands and school-safe flags update from one cell, and the published pages stay coherent across the corpus.

Long-tail nut-free queries (sunflower butter cookie recipe, school-safe brownie recipe, tahini pesto pasta) reward libraries that publish every variant at a clean URL with consistent allergen labelling. Recipe developers spend their time testing dishes, the platform handles the publishing side, and the trust signals readers depend on stay accurate page after page.