Dinner covers the biggest surface area of any meal: pasta dishes, roasts, stir-fries, sheet-pan suppers, curries, grain bowls, tacos, casseroles, soups served as mains. The cuisines, courses, and cook times vary widely, but the recipe shape stays constant. Name, course, cuisine, time, ingredients, steps, photo, nutrition.

SleekRank reads a dinner sheet and ships one URL per row at /recipes/dinner/{slug}/. Tag mappings carry the title, list mappings render ingredients and steps, selector mappings drop the photo, course badge, and cuisine label, meta mappings handle Recipe JSON-LD.

Course, cuisine, and time clusters keep the archive navigable. Weeknight cooks filter by total time. Weekend cooks filter by complexity. The corpus grows row by row, and the related-recipe blocks read from the same source that renders the visible page.

Dinner is the most-searched meal slot, and the search intent is heavily filterable. Weeknight cooks want fast, low-effort meals. Weekend cooks want longer, more complex projects.

Cuisine enthusiasts want depth in a specific tradition. Diet-focused readers want macro-aligned options. Hand-built dinner sections cannot serve those intents well because the filters live in unstructured body copy.

Programmatic generation moves the filter-worthy fields into named columns: total time, cuisine, course, dietary tags, complexity. The Recipe schema stays valid across thousands of dinners, the cuisine and time clusters stay accurate, and the navigation reads from the same source set that feeds the page content. The site grows in long-tail dinner coverage row by row, and the editorial team focuses on testing recipes rather than copy-fitting the WordPress editor.