Lunch spans salads, sandwiches, wraps, grain bowls, soups, pasta, leftovers from dinner. The format ranges from cold meal-prep boxes to hot sit-down plates, but every recipe carries the same fields: name, format, time, ingredients, steps, photo, nutrition, portability. The midday occasion is what unites them.

SleekRank reads a lunch sheet and produces one URL per row at /recipes/lunch/{slug}/. Tag mappings carry the title, list mappings render ingredients and steps, selector mappings drop the photo and format badge (salad, sandwich, bowl, soup), meta mappings handle Recipe JSON-LD.

Format clusters keep the archive navigable. A reader on a salad page sees other salads. A reader on a meal-prep bowl page sees other meal-prep options. Portability and reheat-friendliness surface as visible tags so office lunch packers can filter for what works in a container.

Lunch traffic skews heavily toward practical filters: what is packable, what reheats well, what fits a 15-minute window, what works for a specific diet. Hand-built lunch sections struggle to make those filters real because the relevant information sits in body copy where queries cannot reach. Programmatic generation forces those traits into named columns, which means portability, format, prep time, and dietary tags become first-class filters.

Readers searching for a packable bowl get a bowl cluster filtered to packable entries; readers searching for a hot soup get the soup cluster. The Recipe schema stays valid across hundreds of lunches, the related-recipe blocks stay accurate, and the corpus grows row by row from one shared source.