Guide
Recipe index page: how to build a recipe archive readers actually use
Your best recipes are buried under last week's posts. Here's how to build a recipe archive and index page that helps readers find the lemon cake, the bean soup and whatever's next.
One reader remembers the lemon cake you posted last spring. Another has a can of beans, no plan, and twenty minutes. Your homepage shows your twelve newest posts. Neither of them finds anything, and both leave.
A good recipe archive fixes that. It's the page behind the Recipes link in your menu, and its job is to give every kind of visitor a way in: the one who knows what they want, and the one who only knows what's in the cupboard. Here's how to build a recipe index page that does both, without turning your website into a maze of half-empty categories.
What a recipe index page needs
At minimum, four things:
- A plain name in the main menu. "Recipes" or "Recipe Index." Clever names like "The Kitchen" make people guess.
- An all-recipes view, so someone can scan everything.
- Groups that answer different questions. More on these below.
- Descriptive titles next to the photos. A slice of cake beside a cup of tea could be anything. "Lemon yogurt cake" is what someone remembers. (Our guide to recipe photos covers picking a cover photo that still works when it's cropped into a small card.)
Search helps too, if your website has it. Before you rely on it, try it: search for a word from a recipe title, then an ingredient that's only in the ingredient list, then a phrase like "vegetarian dinner." Some site searches only match titles, and few combine two conditions. Knowing what yours can't do tells you which groups you need to build by hand.
For a good model, look at Smitten Kitchen's recipe index. It's organized under headings like Meal or Course, Ingredient, Diet, Method, Season and Holiday or Occasion. "Beans" starts from what you have. "Soup" starts from what you feel like. "Vegetarian" starts from who you're feeding. Same recipes, different doors. It also has hand-picked groups like Quick and Weeknight Favorite, which are about how a recipe fits into someone's evening.
You don't need an index that big. For a website with around forty recipes, something like this is plenty:
- All recipes
- By course: Breakfast · Dinner · Soups · Baking · Desserts
- By ingredient: Beans · Chicken · Lemon · Pasta
- By diet: Vegetarian
- Collections: Vegetarian dinners · 30-minute dinners
Choose categories from the recipes you actually have
Categories tend to pile up. You add one when you post a recipe, forget about it, and a year later your menu has Dinner, Main Dishes, Mains and an Air Fryer category with nothing in it.
Here's a small example. Say your archive holds five recipes: white bean and tomato soup, chickpea curry, mushroom pasta, roast chicken and lemon yogurt cake. Your current categories and what to do with each:
| Category | What's in it | What to do |
|---|---|---|
| Dinner | Soup, curry, pasta, chicken | Keep |
| Main Dishes | Soup, curry, pasta, chicken | Merge into Dinner. Same recipes, same job. |
| Vegetarian | Soup, curry, pasta | Keep, after checking ingredients |
| Soups | Soup | Keep, and it'll grow |
| Air Fryer | Nothing | Hide it until you've posted something |
Before you merge two similar categories, open them side by side. If Dinner also holds sides and salads while Main Dishes is only the centerpiece, the difference might be worth keeping. Similar names are a reason to look, and the contents decide.
Check diet labels against the ingredients, not the title. A white bean soup made with chicken stock isn't vegetarian as written. The same goes for sauces, stocks and toppings: fish sauce, anchovies in a dressing, gelatin in a dessert.
Separate links don't combine. Having a Vegetarian page and a Dinner page doesn't give anyone vegetarian dinners. They'd have to cross-check both lists themselves, unless your website has filters that narrow by two things at once. If that's a question your readers ask, make a hand-picked Vegetarian dinners collection: the soup, the curry and the pasta. It takes no special tools. You just have to remember to add the next qualifying recipe when you post it.
Titles people recognize
The index is mostly a list of names, so the names carry a lot of weight. Compare:
- "Sunday cake" → "Sunday lemon yogurt cake"
- "The soup" → "White bean and tomato soup"
- "Nonna's favorite" → "Nonna's baked pasta with ricotta"
Keep a distinctive name if readers already know it by that name. Just add the words that tell a new visitor what it is.
One recipe, one page, many ways in
The white bean soup can sit under Soups, Beans, Vegetarian and Vegetarian dinners. Every one of those listings should link to the same recipe page. You're repeating the invitation, not the recipe.
That matters the day you fix a typo in the salt quantity. With one page, there's one place to fix it. Keep the page's address the same when you add it to a new category, too. Moving a recipe into a new group shouldn't move the recipe.
On Crumb, each recipe can belong to one or more categories. The recipe management guide shows where to set them.
When the same recipe is posted twice
Older archives often have the same dish in two posts: the original from years ago and a "new and improved" version. That's a different problem from listing one recipe in several places, and it needs more care.
Before you retire either post, compare them line by line: ingredients, quantities, steps, notes and credits. They might be one recipe written twice, or two different dishes that happen to share a name. If one starts with dried beans and the other with canned, you can't blend the methods. Check your notes, and if they don't settle it, test the recipe again and publish the version you've confirmed. If both versions are worth keeping, give them titles that explain the difference: "White bean soup (from dried beans)" and "Quick white bean soup."
Check the credits too. If one post says "adapted from" a cookbook and the other doesn't, carry the credit onto the page you keep. Our guide to recipe copyright covers how to credit an adaptation properly.
When two posts really are duplicates, keep one and redirect the other's address to it, if your platform supports redirects. Google recommends redirecting when several pages hold the same information. Then update your index so every listing points straight to the page you kept.
Test your recipe archive in five minutes
Open your public website on your phone (not the dashboard) and try these:
- Find the bean soup by searching "bean" or "tomato."
- Start from the Recipe Index and reach the same soup through Vegetarian dinners. Do both routes open the same page?
- Find the lemon cake without knowing when you posted it.
- Pick tonight's dinner starting from an ingredient you have.
- Open three recipes at random. Does every listing lead to a complete recipe, with amounts, yield and cues for when to move on? If not, write it up properly before it goes in the index.
Wherever you got stuck, fix that one thing: a vague title, a missing category, a broken link, or a collection your search can't build for you. Do that before you add a single new category.
Then go back to the kitchen. The best thing for your archive is the next well-tested recipe, and our guide to testing a recipe before you publish it is a good place to start.