Store recipe slugs as an array per occasion. 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, which most teams handle during quarterly content audits.

Yes. Add a recipe slug to multiple occasion rows. SleekRank just renders what's listed; nothing is exclusive. A turkey recipe belongs under Thanksgiving and also under dinner-party, and curating it in multiple places is the right editorial call. Featured-list duplication is fine; SEO concerns about duplicate content don't apply because occasion pages themselves are unique.

No. Individual recipe posts typically live as WordPress posts or another page group. Occasion pages just curate them by slug. SleekRank handles the occasion landing pages: intro, menu suggestions, featured lists, time considerations. Recipe authoring stays in the existing recipe workflow, whether that's standard posts, a recipe-card plugin, or another SleekRank page group with structured prep time and ingredient fields.

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 occasion pages get crawled within hours of cache flush. Occasion queries spike around the relevant date and stay evergreen across years, which makes the pages especially rewarding to maintain.

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 work in isolation. WPML or Polylang handles 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. Occasion photography is high-impact (a beautifully styled Thanksgiving table sells the page), so CDN-hosted images perform best. For SleekPixel-rendered OG cards, pull occasion name and season into a templated card so social previews look consistent across the catalog.

Yes. Add a seasonal_picks array that editors update during the relevant window (Thanksgiving picks updated in October) and render it as a separate section above the all-time favorites list. Trending data could come from analytics: pull the most-viewed recipes per occasion in the last thirty days into a column refreshed weekly. Cache duration controls freshness.

Treat related occasions as their own rows with their own slugs. Add a parent_occasion or related_occasions column so each page can show "see also" links between related contexts. Featured-recipe arrays can overlap or differ; sometimes Friendsgiving warrants more casual recipes than the formal Thanksgiving list.