Store recipe slugs as an array per cuisine. List mapping renders them as cards or links to the relevant recipe pages. Recipes themselves typically live as WordPress posts or another SleekRank page group; the link is just the slug. If a recipe is removed, it shows as a broken link until you trim the array — most teams handle that during quarterly content audits.

Yes. Add a recipe slug to multiple cuisine rows. SleekRank just renders what's listed; nothing is exclusive. Some recipes (a pad thai variation that uses Chinese techniques, for instance) belong under multiple cuisines, and curating them in multiple places is sometimes the right editorial call. Featured-list duplication is fine; SEO concerns about duplicate content don't apply because cuisine pages are themselves unique.

No. Individual recipe posts are typically WordPress posts or another page group. Cuisine pages just curate them by slug. SleekRank handles the cuisine landing pages — history, ingredients, featured lists. Recipe authoring stays in your existing recipe workflow, whether that's standard WordPress posts, a recipe-card plugin, or another SleekRank page group with structured fields like prep time and ingredients.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new cuisine pages get crawled within hours of cache flush. Cuisine queries are competitive but the structured per-page content (history, ingredients, featured count) signals authority and helps rankings.

Yes. Maintain language-specific columns (name_en, name_es, name_fr) or separate sources per language for each language site. For multilingual recipe sites, separate sources usually scale better because translators can work in isolation. WPML or Polylang handles the URL routing alongside SleekRank's slug-based generation.

Store image URLs in the sheet and inject via selector mapping for in-page hero and meta mapping for og:image. Cuisine photography is a one-time investment — a great Italian hero photo serves the page indefinitely. CDN-hosted images perform best. For SleekPixel-rendered OG cards, pull the cuisine name and region into a templated card so social previews look consistent across cuisines.

Yes. Add a seasonal_picks array that editors update monthly and render it as a separate section above the all-time favorites list. Trending data could come from your analytics — pull the most-viewed recipes per cuisine in the last thirty days into a column refreshed weekly. Cache duration controls how fresh the page feels without hammering analytics on every render.

Treat sub-cuisines as their own rows with their own slugs (e.g. sicilian under Italian, oaxacan under Mexican). Add a parent_cuisine column so each sub-cuisine page can show "part of {parent}" linking back to the broader cuisine. Featured-recipe arrays can be specific to the sub-cuisine, giving regional pages real identity rather than feeling like Italian-with-an-asterisk.