GEO • Dish pages
The perfect structure for a GEO dish page
A GEO dish page is built so AI engines can quickly extract price, ingredients, allergens and verdict. It has a fixed section order and complete structured data. Below is the perfect structure for a GEO dish page, section by section — illustrated on a "Margherita pizza".
The section order (short answer)
- H1 = the dish name, clear and unique (e.g. "Margherita pizza 32 cm").
- Short answer: what it contains and for whom, in 2 sentences.
- Table with ingredients, portion size and price — exact values.
- Allergens shown clearly (gluten, lactose, etc.).
- Pros and Cons — honest, separate lists.
- Short verdict: when to choose it and when not.
- Dish FAQ + Product/Offer + Menu JSON-LD.
Table: section and its GEO role
The sections of a GEO dish page
| Section | What the AI extracts |
|---|---|
| Short answer | What the dish is |
| Ingredient + price table | The exact ingredients, portion size and price |
| Allergens | The dish's allergen list |
| Verdict | The ordering recommendation |
Common mistakes
- Ingredients and price only in the menu image — non-extractable.
- Missing allergens — loses the AI's trust and breaks labelling law.
- Product/Menu JSON-LD without offers or without image.
How 4salefood helps
- Dish page template with all GEO sections built in — ingredients, allergens, verdict.
- Menu + Product + Offer + FAQPage JSON-LD generated automatically at publish time.
- Pre-structured ingredient, allergen and verdict sections in the editor.