Chronic kidney disease readers are usually managing sodium, potassium, and phosphorus per meal under guidance from a renal dietitian. Recipes that ship without those three values are not just unhelpful, they are unsafe to use as a planning tool. The sites that win in renal search show the three numbers consistently per dish and group recipes by mineral band so a planner can build a day inside the catalog.

SleekRank reads a recipe sheet that carries one row per dish with slug, name, sodium_mg, potassium_mg, phosphorus_mg, protein_g, servings, prep_min, plus ingredient and instruction arrays. Each row becomes a URL at /recipes/kidney-friendly/{slug}/. Selector mappings push the three minerals plus protein into the nutrition card. A meta mapping carries the same numbers into Recipe JSON-LD nutrition fields. List mappings render the ingredients ul and the step-by-step ol on every page.

Editorial workflow keeps clinical contributors close to the data. A renal dietitian maintains the sheet; cache flush picks up changes on the next refresh; sitemap entries update automatically. Cluster pages (low-potassium dinners, low-phosphorus breakfasts) emerge as filtered list mappings rather than hand-built category posts. Retired recipes return 404 so stale clinical claims do not linger.

Chronic kidney disease audiences are not browsing for fun. Most are managing a real clinical context where eating wrong can mean a hospital admission. Recipe pages that ship without sodium, potassium, and phosphorus per serving are useless as planning tools, and worse, they erode trust permanently when a reader needs the data and cannot find it.

Hand-built per-post renal catalogs fail in exactly the way that hurts most. A writer types 320 mg potassium on the card but 380 mg in the JSON-LD because two drafts had different figures. A cluster page for low-potassium dinners silently includes a 540 mg dinner because the manual taxonomy was last refreshed before the new recipes shipped.

A guideline update from a kidney foundation lowers a threshold and only the most recent recipes reflect it. Programmatic generation eliminates the class of error because the three minerals, the CKD stage, the cluster bands, and the JSON-LD all read from one row in the sheet. A renal dietitian updates the row; every surface updates together on the next cache cycle.

Cluster pages emerge as filtered list mappings against the same source data. Retired recipes return 404 instead of lingering with outdated mineral figures. A small clinical-editorial team can maintain a real renal catalog without taking on a developer's worth of taxonomy maintenance work.