Editorial Policy

1. 01

   Discovery

   We choose recipe topics based on real demand: what people actually search for and what our catalog lacks — not random recipes to fill pages.

2. 02

   Research

   We gather the foundation: ingredients, techniques and reference data from documented structured sources, so the recipe is built on solid ground.

3. 03

   Draft

   The draft is written with AI assistance under strict structured templates: ingredients, quantities, units, steps, times.

4. 04

   Fact check

   Deterministic programmatic checks with no room for interpretation: unit and quantity integrity, step ordering, plausible times and temperatures, complete fields.

5. 05

   Culinary validation

   Cooking rules: physically possible temperature ranges, coherent ratios and logical techniques for the ingredient. Any violation is a rejection, never an override.

6. 06

   Publish approval

   Nothing publishes automatically: after passing the checks a recipe reaches a publish queue that requires explicit approval before it goes public.

7. 07

   Nutrition

   Nutrition values are computed from a documented reference dataset where available and clearly labelled as estimates — no invented numbers.

8. 08

   Duplicate check

   Automated checks against duplicate recipes and duplicate families: we do not publish identical copies under different names to game search engines.

9. 09

   Media

   Recipe imagery passes through its own production line with mandatory verification checks; an image is used only after its checks pass.

10. 10

    SEO

    Correct structure: unique titles and descriptions, structured data (JSON-LD) and meaningful internal linking — without keyword stuffing.

11. 11

    Quality gate

    The final publish gate re-verifies everything above in one pass; any failure stops the recipe until it is fixed.

12. 12

    Publish

    The recipe is published in every eligible language with a visible publish date, and enters the periodic review loop.

When an error is found in a published recipe — found internally or from your feedback — we fix it and update the "last updated" date on the page. We do not silently erase mistakes; material corrections go through the same pipeline that published the recipe in the first place, detailed in the corrections policy.

We re-review published recipes periodically: fresher nutrition data, language improvements or technical adjustments based on user feedback. Every update is reflected in the page date, and any material change sends the recipe back through the quality gates.

We prevent duplicates in the catalog: matching checks catch near-copies before publishing, and duplicates discovered later are merged into the best version with links redirected to it.

Older recipes are not abandoned: we periodically review the oldest or least-used ones, update their data or reassess their value. Every page shows its last-updated date so the picture is transparent to the reader.

Your feedback is a direct line into the pipeline: "Recipe feedback" messages in the contact form are reviewed and turned into real corrections or updates. Repeated feedback on a recipe sends it back through verification and repair.