3 ms·
The essays at the top of recipes are about creating "romance", and often are intended for people as much as (or more than) SEO. They are intended to create empa
by WorldMaker 7y ago
The essays at the top of recipes are about creating "romance", and often are intended for people as much as (or more than) SEO. They are intended to create empathy from the recipe reader toward the writer and establish certain bonafides, most of which are inconsequential to the recipe itself but help separate one recipe website and/or one recipe author/collector/distributor from another. It's actually something that goes way back in recipe books, where a lot of classic, well respected recipe books for centuries have always put the work into an introduction chapter describing the author, what their passions are, how they approach recipes. It helps sell recipe books and helps aspiring and/or home chefs see things like "oh, this author is just like me" or "if this person can make this recipe, so can I". It's just that on the internet when you are looking for one specific recipe that "introduction chapter" starts to have to move into every single recipe because people aren't going to pick up your website or blog like a book, they are going to go straight to a single page. Though even that isn't entirely unique in the world of cookbooks: there are also old traditions of narrative recipe books that treat the cookbook as a diary of sorts laying out the author's discovery and interest in every single recipe. Sometimes people want a story to go with your dry lists of ingredients and otherwise boring step-by-step directions.
It emphasizes the art in cooking, that it isn't just boring "food chemistry", but that it is a way for people to connect to each other. Even if it didn't help with SEO, there are probably lots of recipe bloggers that would do it anyway because it shows passion, love for the art, narrative hooks for the reader to explore who they are, their creativity, and/or their other interests outside of just their kitchen.
- criddell 7y agoWhat works in one medium isn't necessarily the best choice for a different medium. Books and web pages have unique constraints and use cases. Everything you've described sounds like the experience I want from a great cook book. It's something I will browse and spend time with. On the web I just want information. I got there with a specific search and I'm not there to learn about the author. The essays probably wouldn't bother me if they would put the recipe first. If you have a great story about why sage is your favorite herb put that after the recipe. I don't care, but I suppose somebody might.
- WorldMaker 7y agoI was thinking that for a while too, but started to swing back towards caring for how a post frames the recipe. There are an infinite variety of the same basic recipes, and how do you choose between any given two of them? The people and the art around them, where the recipe came from, what the recipe author was trying to capture, thought processes to follow that might lead me along to what I'm hoping to capture in my own cooking, etc. There is no objective evaluation of what makes a "good recipe", it is all subjective. The UX balance of that is obviously tough, and probably more such posts should have a "skip to the recipe" button. Sometimes it seems like a technical expertise challenge that a lot of these recipe blogs are basic (or worse) off-the-shelf CMSes and some of the ugliest blog platforms humanity has built, and there isn't enough flexibility or training to do something so basic in those platforms. Also, some of them legitimately have audiences that read every post as a blog, and the day-to-day audience isn't intended to be "I'm in a hurry, I just need this one recipe today", but "follow my stories and I include recipes to go along with them". It's sometimes tough to make both audiences happy, and that day-to-day audience is more regular and likely the better one to focus on for the most sustainable revenue/readership.
- dhimes 7y agoI agree with you. I wish I didn't. I enjoy the romantic side that WorldMaker points to, but the fact is that when I'm looking up a recipe on the web I'm just trying to make it. All I want talked about is whether or not it's authentic or (say) made differently for American tastes, possible substitutions, etc. I'm not proud that this is what I've become.