The archive is the asset. If you've been blogging for years, you're sitting on dozens — maybe hundreds — of tested, photographed, reader-loved recipes. Search traffic may rise and fall with algorithm changes, but that library is yours, and it can become a product readers buy directly from you.
Do I have to rewrite everything?
No. Paste a blog post URL and mykitchen.bio fetches the page and turns the recipe into a structured draft. PDFs work too — an old ebook, a recipe card collection, a printout scan of your notes typed up. Text recipes use 1 recipe unit each, so an archive converts quickly: the Starter plan's 40 text recipes a month covers a serious back-catalog project (pricing →).
What should go in the cookbook?
Curate, don't dump. Your twenty best one-pan dinners beats your hundred most recent posts. Readers pay for the editing — the promise that everything inside works. Group by how people actually cook: weeknights, seasons, occasions.
Why would readers pay when the blog is free?
Because the product is better than the blog. No ads, no life story, no scrolling — a clean cookbook with cook mode: servings that scale, steps they can check off, a screen that stays awake at the stove. And it's direct: every buyer joins your customer list, not a platform's. Your recipes, your cookbooks, your customer list — export everything, anytime.
Can it keep earning?
Yes — publish it as a living cookbook. Readers subscribe (from $9/month or $35/year), and every new recipe you add flows into their book automatically. Your archive starts the book; your ongoing work keeps it selling.