I hate cooking sites that put a novel in front of the recipe. I get that you’re trying to tell a story about how you found it or some history to it. I landed on your site from Google because i know what I want to make and I’m ready to make it.
There is an entire contingent of food bloggers and cooks who will make it their mission to cancel you on Twitter. Don't believe me? Look what happened Recipeasly[1][2][3]
[1]: https://www.washingtonpost.com/food/2021/03/02/recipeasly-fo...
[2]: https://www.theguardian.com/media/2021/mar/01/food-website-t...
It's witchcraft, really. Tine wrote a hell of a parser!
You don't realize it, but the stories are all written because Google ranks a recipe higher if if has more content like that.
Don't blame the authors. Blame search engines.
Fortunately, it's incredibly easy to scroll down to the recipe itself.
Another comment here suggests it could be around copyright. Does adding unrelated jargon to the page give you any meaningful extra protection of the mere ingredients list and instructions though? It strikes me adding a life story might protect the life story, but not the actual (seemingly unprotectable) recipe.
Or is there another reason? I'm intrigued as it seems to be a standard playbook, yet one which presumably costs money and time in writing unique content that's relevant enough to avoid users bouncing...