Guide
How to create a recipe website when your recipes already live on Instagram
Most guides assume you're starting from zero. You're not: you have the recipes, the photos and people asking for them. Here's how to create a recipe website from there, what the WordPress route really costs in money and evenings, and whether you can do it for free.
Search "how to create a recipe website" and every result starts the same way: buy hosting, install WordPress, pick a food theme, add a recipe plugin. That's good advice for someone with no recipes, no photos and no readers.
That's not you. You have a few hundred posts, a camera roll full of finished dishes, and a comment section that says "recipe please!" twice a day. What you don't have is a place where a recipe can be printed, scaled, found on Google and sent as one link. This guide is about building that, starting from where you actually are.
Crumb is our product, and it's one of the options below. Everything we say about other platforms comes from their own pricing and help pages, not from testing them ourselves. Prices checked October 14, 2026, in US dollars before tax unless noted.
The decision you're actually making
Forget Wix versus Squarespace for a minute. The real question is whether you want to run a website or publish recipes. Three questions settle it:
- How will this make money? If the plan is display ads, you need WordPress. If it's memberships, a cookbook, brand work or nothing yet, either route works.
- Do you enjoy setting things up? Some people love picking plugins and tweaking templates. Some people would rather spend Sunday cooking. Be honest about which one you are.
- Where do your recipes live right now? If the answer is "in 300 captions," the hardest part of this project is getting them out, and that should weigh more than which theme is prettiest. (When you do get to themes, test them with your own recipe rather than the demo's.)
Already paying for a Squarespace site for your photography or catering? You may not need a second website. Here's how to add a Squarespace recipe card instead.
What the WordPress route really involves
WordPress is what nearly every top search result recommends, and for good reason: it can do everything. But "WordPress" isn't one thing you buy. It's a stack you put together, and each layer has its own bill.
| Layer | A common choice | Price |
|---|---|---|
| Hosting | WordPress.com Personal | $48 a year paid upfront ($9 a month if paid monthly). Plugins allowed, domain free for year one. |
| Recipe card | WP Recipe Maker | Free. Premium is $49 a year and adds adjustable servings, star ratings and cook mode. |
| Food theme | Feast Plugin, built for food blogs | $249 a year. Free themes work too; this is the "make it fast and tidy" upgrade. |
| Display ads | WordAds | Needs WordPress.com Premium ($96 a year) and your own registered domain. |
Add it up and three realistic first years look like this:
- Lean: Personal plan + free recipe plugin = $48
- With serving scaling: $48 + $49 = $97
- The full food-blog kit: $48 + $49 + $249 = $346
Self-hosting elsewhere changes the hosting line, and watch the renewal. SiteGround's entry WordPress plan, for example, was €2.99 a month for the first prepaid year and €15.99 a month at renewal when we checked. That's more than five times the starting price.
The bigger cost is the one without a price tag. Here's the first-time setup list:
- Choose a plan and connect your domain.
- Install and configure a theme: fonts, colors, header, menu, homepage layout.
- Install the recipe plugin and pick or customize its card template.
- Set up the print view and jump-to-recipe button.
- Create your categories and an About page.
- For every recipe: write the post, then fill the recipe card fields inside it.
And the ongoing list: update plugins and themes, renew licences, and fix whatever breaks when two of them disagree. Paid licences matter here. WP Recipe Maker's plugin keeps working if you stop paying, but the updates and support stop. If you like this kind of work, it's genuinely satisfying. If you don't, it's a second job.
For a wider comparison including Wix and Squarespace, compare the recipe website builders side by side. For every line of the budget, see what a recipe website really costs.
What "recipe card with schema" means for Google
Every guide tells you to get a recipe plugin "for schema." Here's what that actually is.
When Google reads a recipe page, it looks for a hidden block of Recipe structured data: the same recipe again, written in a format a machine can't misread. For a simple bean dish it looks something like this:
{
"@type": "Recipe",
"name": "Lemony baked white beans with crispy crumbs",
"image": ["https://yourkitchen.com/photos/white-beans.jpg"],
"recipeYield": "4 servings",
"prepTime": "PT10M",
"cookTime": "PT35M",
"recipeIngredient": ["2 cans (400 g each) white beans, drained", "4 tbsp olive oil, divided"],
"recipeInstructions": [{ "@type": "HowToStep", "text": "Heat the oven to 200°C (400°F)." }]
}
Google only requires name and image. Ingredients, steps, times and yield are recommended, and they're what make a recipe eligible for the richer results with a photo, cook time and ratings. Eligible is the key word: Google decides whether to show them.
You never type this by hand. A recipe plugin on WordPress, or the recipe editor on a recipe-first builder, writes it from the fields you fill in. That's the real point for you: there's no way to attach any of this to an Instagram caption. A recipe only becomes something Google can understand as a recipe once it's on a page with a card. Our recipe schema guide shows how to check yours.
Can you create a recipe website for free?
Yes to building one. Mostly no to running one, and the catch is always the same: someone else's ads, or no recipe card.
- WordPress.com Free gives you a site at a wordpress.com address, but free sites show WordPress.com ads to your visitors, and installing plugins needs a paid plan. No plugin means no WP Recipe Maker card.
- Crumb lets you build and preview your whole website free, for as long as you like. New direct signups get 30 days public free with no card, then it's $15 a month to stay public.
So the honest version: build for free, see if you like it, and budget at least $48 a year (WordPress.com Personal) to keep a clean recipe website online. If you want your own .com somewhere other than WordPress.com, add roughly $11 a year.
When Crumb is the right pick, and when it isn't
Crumb was built for exactly the creator this guide started with, so here's the fair version.
It fits if:
- Your recipes are in captions. You can paste a caption and get a recipe draft, or connect a public Creator or Business Instagram account and bring in recipes from up to your 500 most recent posts as drafts. Imported recipes still need checking. Our guide to moving your Instagram recipes onto a website walks through it step by step.
- You want recipe cards, printing, serving scaling and the structured data above without installing anything.
- You'd rather start from a finished food blog theme than a blank template, and switch later without moving a recipe.
- You'd rather sell memberships than run ads. Crumb takes 8% of membership payments, plus Stripe's fees.
Pick something else if:
- You want ad income. Crumb has no display ads and nowhere to paste ad code.
- You want full control. You can't add plugins or custom code, and recipe pages use a fixed layout.
- Cash is the main constraint. Twelve months of Crumb Pro is $180, against $48 for WordPress.com Personal.
- You want to take everything with you. You can export your subscriber list, but not your recipes and photos yet.
Get one recipe page right before you move the rest
Whatever you choose, don't start with fonts. Start with the dish people ask about most, and make its page complete: a clear name and photo, servings and times, every ingredient with an amount, and steps with temperatures, pan sizes and a "you'll know it's done when" cue. If you aren't sure a step is right, test the recipe before you publish it.
Once that page works, the template for the next fourteen is sitting right there. Moving them is its own job, with its own shortcuts and traps, so it has its own guide.
How to make money from a recipe website
The three main routes pull you toward different platforms, so decide early:
- Display ads pay by traffic, so they reward big search numbers, and they need WordPress or similar.
- Memberships charge your most loyal readers for extra recipes. They depend on how much people trust you more than on how many visit.
- Your own products and partnerships, like a digital cookbook or brand work, need a website mostly as a place to send people.
How recipe creators make money compares them in detail.
Before you commit: check the exit
Moving 200 recipes later is painful on any platform. WordPress.com can export your posts as an XML file that other platforms import. Crumb can't export recipes yet. Keep your original photos and recipe text somewhere of your own either way, and check what your platform can export before the collection gets big.
So which should you pick?
If ads are the plan, or you enjoy tinkering, take WordPress.com Personal with the free WP Recipe Maker plugin, and build your most-requested recipe this weekend. If your recipes are stuck in captions and you'd rather spend the weekend cooking than configuring, start a Crumb website free, paste in that same recipe, and see how it looks before you pay anything.
Either way, once your recipes have a home, our complete guide to recipe SEO is how you get them found.