Use two columns. The country column holds Greece, Italy, Spain, Lebanon, Morocco, and so on. A region column holds broader groupings (Eastern Mediterranean, Western Mediterranean, North Africa). Cluster pages can run on either column via separate URL patterns, so navigation supports both levels of specificity.

Yes. A contains_seafood boolean column and a vegetarian boolean column drive cluster URLs like /mediterranean/seafood/ or /mediterranean/vegetarian/. The base recipe page shows a badge for each so readers can scan for fit at a glance.

Store an olive_oil_note column at the recipe level for dishes where the grade matters (raw applications like dressings or finishing). The note renders below the ingredients list. For cooked dishes where the grade matters less, leave the column blank and the template skips the note block.

Eligibility requires valid Recipe schema, image quality, and overall site authority. SleekRank produces compliant JSON-LD from the data fields uniformly. The carousel decision is Google's and favours established recipe domains, but the structured-data prerequisite is handled.

Yes. A season column (spring, summer, fall, winter) drives a season badge and a seasonal cluster URL pattern. Mediterranean cooking is seasonally driven, so the cluster pages tend to match how readers actually plan meals.

No. Tradition notes come from the source. They should be written by someone with knowledge of the regional cuisine, not generated. SleekRank handles publishing, not authorship of cultural context.

Yes. Store the video URL as a column and inject it via selector mapping into a video block in the template. The Recipe schema also accepts a video field that meta mapping can populate from the same column.

Yes. Add a related_slugs array per row that lists related recipes (same country, same ingredient, same dish type). A list mapping renders them as a card cluster at the bottom of each page so internal linking stays current as the sheet grows.