How often should a food blogger email their list?
Once a week, on the same day, is the rhythm that keeps a recipe list warm; less often and readers forget who you are, more often and they unsubscribe, and the only way to sustain weekly is to fill it from the catalog.
Weekly. The rest of this is why, what the alternatives cost, and how to make weekly possible for a blog that does not publish weekly.
What each frequency does to a list
Whenever a recipe goes up. The list hears from you three times one month and not at all the next. Readers do not learn a rhythm, so every email is a surprise, and surprises get deleted. Worse, the quiet months are usually the busy cooking months, when the list would have clicked.
Monthly. Enough to not be forgotten, not enough to be looked forward to. A monthly letter has to carry too much and ends up long. Open rates on monthly recipe letters tend to be fine; clicks per subscriber over the year are low, because there are only twelve chances.
Weekly. The reader learns that Thursday is your day. She opens it because it is Thursday. Fifty-two chances a year to put dinner in front of her, each one short. This is where most of the recipe newsletters we admire have settled. Mary to add where her three lists landed and why.
Twice a week or more. Works for a few large publishers with daily content and a team. For a one-person recipe blog it doubles the work and the unsubscribes without doubling the clicks. The exception is a holiday week, when a second issue (the timeline, the leftovers) is welcome.
The same day, the same shape
The day matters less than keeping it. Pick the day your list opens email and hold it. Many recipe lists do well on Thursday or Friday, when people plan the weekend's cooking, and on Sunday, when they plan the week. Look at when your own list opens and clicks; the tool will tell you.
The shape matters too. A letter that is a roundup most weeks, a dinner plan now and then, and a story when there is one, is recognizable in the inbox. Readers know what they are getting before they open it, and that is why they open it.
Why weekly fails, and the fix
Weekly fails for one reason: the blogger believes each issue needs a new recipe, and the blog publishes two a month. So the newsletter goes out twice a month, tied to the posts, and we are back to "whenever".
The fix is to break the link between publishing and sending. An issue does not need a new recipe. It needs five old ones that belong together this week, and a reason. What to send your list when you have no new recipe is the method; the hub is the argument. A catalog of two hundred recipes has a year of weekly issues in it without repeating a theme.
When there is a new recipe, it leads the issue it belongs to. It does not get an issue of its own unless it has a story.
Skipping a week
Skip when you have nothing worth sending, not when you are busy. "Nothing worth sending" is rare if the catalog is doing the work. "Busy" is every week, and the list cannot tell the difference between a skipped week and a blog that stopped.
If you must skip, do not apologize in the next issue. Nobody noticed, and the apology tells them they should have.
The long game
A weekly letter for three years is about 150 issues. Each one puts five or six recipes in front of every subscriber. That is 800 chances for each reader to come back to the blog, and it is the reason email is the one channel a food blogger owns outright: no algorithm, no platform change, no filter deciding who sees it. Weekly is how you collect on that.