Cocina vs HostEvery episode of the show turned into a recipe people can search for

Design and development of the site at Azirgo SAS for the production company La Jungla: episode system, technical SEO and structured data, measurement and deployment.

Cocina vs Host is published on YouTube: every week a guest who cannot cook takes on a real Ecuadorian recipe alongside Dina Muñoz. Everything people search for - what was cooked, what goes into it, how it is made - was trapped inside the video. YouTube titles also do not work as search titles: some reach 90 characters with the brand and others are so short they do not say what the episode is about. And brands that wanted to sponsor the show had nowhere to write.

• A home page with the latest episode in the hero, the pillars of the format, photos from the set, the six most recent episodes, a host section, a wall of every guest who has been through the kitchen and frequently asked questions.
• An episode archive and a page per episode: the guest and their role, the dish of the day and its difficulty, the production challenge, the video, a long summary, the episode write-up, the recipe with ingredients and step by step, and timestamped moments that open the video at that minute.
• Frequently asked questions for each episode generated from its own data - what is cooked, what goes into it, the step by step, who the guest is and how long it runs -, shown on the page and marked up as FAQPage with the same text.
• A profile of the host, Dina Muñoz, with her bio, her career told in stages, her social accounts and her latest episodes.
• Contact built for sponsors: WhatsApp and email with the message already written, the studio address and a Google map that only loads on interaction or as it nears the screen. A WhatsApp bubble with a sponsorship message sits on every page.
• An RSS feed and llms.txt generated from the same episode collection, so they never have to be updated by hand when an episode comes in.
• A script that generates episode files in bulk from a list of links or from the CSV that YouTube Studio exports, and another that turns each episode's thumbnail into the background photo of its header.

Astro 7 with Tailwind v4 and MDX, built on the Astro Theme Cactus architecture with an episode system of its own. The show's copy, host, social accounts and contact details live in a single data module, and the episodes in an MDX collection. It deploys in Docker on Railway, behind Cloudflare.

Each episode page is designed to answer what people search for after watching the video, or instead of watching it.

• Each episode is an MDX file whose name is the URL, validated by a schema: number, guest, recipe, challenge, topics, moments and its own questions. A new episode is added by copying an earlier one, and a draft shows in development but never in production.
• The search title of each episode page builds itself: it tries candidates - with the brand, with the dish, with the main dish - and the first one that lands between 50 and 60 characters wins. Padding it would mean inventing text, and blind truncation leaves titles that Google cuts off.
• Each episode's FAQ is built from the data on its page rather than written by hand: nothing can go stale or contradict the recipe, and what people read and what is marked up as FAQPage is exactly the same text.
• The site runs on the Node adapter, like the rest of La Jungla's sites, but every content page is prerendered: it is faster, and it is the condition for Astro to inject a hash-based CSP with no unsafe-inline. That is why analytics is bundled as a module rather than an inline script.
• Three separate entities in the graph - the show, the production company and the host -, each with a stable @id and only its own accounts in sameAs. Mixing them tells Google an account belongs to someone it does not, and for a while the contact page sent people to the production company's accounts as if they were the show's.

• YouTube titles that do not work for search: up to 90 characters with the brand, or so short they do not say what the episode is about. Long ones get their own SEO title on the episode; for short ones, the dish completes the title.
• Keeping a strict CSP with GA4, Clarity, the YouTube player and the Google map living on the same site, without opening it up with unsafe-inline.
• Letting an episode with no recipe - the best-moments compilation - live in the same template without breaking the page, the FAQ or the schema.

The site is in production with the show's complete archive: every episode has its page with recipe, moments and FAQ, and it goes into the sitemap, the RSS feed and llms.txt without touching anything else. Brands reach WhatsApp with the sponsorship message already written, from any page.