Recipe pages are built for search engines without you configuring anything. This is what Savorible publishes on every recipe, and the two fields you can override.
What happens automatically
- Recipe structured data. Every published recipe carries schema.org/Recipe markup: name, description, author, photo, prep, cook and total time, servings, ingredients, and the steps as sections. Only fields you filled in are included — nothing is invented to look complete.
- A page title and description built from your recipe title and short description.
- A canonical address for the recipe, so one recipe is one URL.
- Open Graph tags, so a link shared on social sites shows the title, description and photo.
What you control
- The recipe title and short description, which are what most recipes should rely on.
- SEO title and SEO description in the metadata form, when you want the search result to read differently from the page. Add recipe metadata
- Course, cuisine and keywords, which are added to the structured data.
- Internal links, through tags and related recipes. How related recipes work
Drafts, unhosted blogs and visibility
Drafts have no public address at all. A blog with nothing paying for it is not served to readers and asks search engines not to index it, so nothing is exposed while you are still building.
You can also set the blog itself to unlisted or private under Settings. Unlisted blogs stay reachable by URL but are kept out of search results. Private blogs are only shown to people with access.
Strategy, as opposed to fields
This article covers what the product does. For what to write and what to ignore, the Savorible blog has the long version: Food Blog SEO: What Actually Matters.