Each region row references a parent cuisine slug (Tuscany under Italian, Sichuan under Chinese). Selector mapping renders a "part of {parent} cuisine" link back to the cuisine hub. The cuisine and region surfaces share the same recipe pool, so featured recipes can overlap (a Tuscan ribollita appears on both the Italian cuisine page and the Tuscany region page).

Yes. Add a recipe slug to multiple region rows. SleekRank just renders what's listed; nothing is exclusive. Some recipes (a fusion that draws from Sichuan and Hunan techniques, for example) belong under multiple regions, and curating them in multiple places is sometimes the right editorial call.

No. Individual recipe posts typically live as WordPress posts or another page group. Region pages just curate them by slug. SleekRank handles the region landing pages (geography, signature ingredients, featured lists). Recipe authoring stays in the existing recipe workflow.

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 region pages get crawled within hours of cache flush. Region queries are lower volume than cuisine queries but high intent, which often makes them more valuable per visitor.

Some culinary regions (the Levant, Andean cuisine) cross national borders. Add a countries array (instead of a single country column) and render via list mapping. The page header renders "spanning {country list}" instead of a single country flag. Editorial framing matters because national identity around food is sometimes contested.

Store image URLs in the sheet and inject via selector mapping for in-page hero and meta mapping for og:image. Region photography (a Tuscan hillside, a Sichuan market) is high-impact, so CDN-hosted images perform best. For SleekPixel-rendered OG cards, pull region name and country into a templated card so social previews stay consistent.

Yes. Add a seasonal_picks array per region that editors update quarterly (Sicilian summer recipes, Tuscan autumn dishes). Render the seasonal block above the all-time favorites list. Trending data could come from analytics: pull the most-viewed recipes per region in the last thirty days into a column refreshed weekly.

Treat micro-regions as their own rows with their own slugs and a parent_region column pointing back to Tuscany. Each micro-region page renders "part of Tuscany" linking back to the broader region, alongside its own featured recipes. The hierarchy reads naturally: cuisine, region, micro-region. URLs at /recipes/region/{slug}/ work for all levels via slug uniqueness.