Recipe and Food Blog Recovery After the Helpful Content Update

Food blogging was hit harder than almost any other independent category. Many sites lost most of their traffic in a fortnight and have not come back.

The reason is specific to how recipe sites are built. Understanding it is the difference between a recovery and another year of rewriting.

Why recipe sites were hit so hard

The helpful content system judged sites, not pages. That is what made it so damaging for recipe blogs specifically.

• Huge archives of similar recipes. Forty versions of chocolate chip cookies, each a separate page, each nearly identical.
• Long preambles. A personal story, then tips, then substitutions, then the recipe at the bottom. Written for scroll depth, not the reader.
• Ad-dense layouts that pushed the actual method below several screens.
• Recipes with no first-hand evidence. Stock photos, no testing notes, nothing showing the dish was actually made.

No single one of these is a violation. Together, across a whole site, they describe a site built to rank rather than to help — which is exactly what the system was designed to detect.

Why rewriting recipes does not work

This is the trap most food bloggers fell into.

They improved their best recipes — better photos, tighter intros, cleaner cards. The ratio of weak to strong pages barely moved. A site with 200 good recipes and 1,500 thin ones is still mostly thin.

The fix is composition, not polish. Measure where you stand with the index bloat ratio before touching a single recipe.

The recovery, in order

1. Consolidate near-duplicate recipes. Forty cookie recipes become one strong page with variations, and the rest redirect to it. Merge, do not delete.
2. Put the recipe near the top. A jump link is not enough. Lead with what the reader came for.
3. Cut the preamble to what genuinely helps. Testing notes and why a step matters stay. The life story goes.
4. Show you made it. Your own photographs of each stage, what went wrong in testing, real timings from your kitchen.
5. Reduce ad density above the method. This is the hardest commercially and among the most important.
6. Fix the recipe schema. Correct structured data for ingredients, times and ratings.

Step one matters most and is most often skipped, because consolidating hundreds of recipes feels like throwing work away. It is not. The links and history carry forward through the redirects.

The honest part about ads

Most recipe sites earn from display ads, and fewer ads means less revenue per visitor.

That is a real trade-off and I will not pretend otherwise. But revenue per visitor on a demoted site is revenue per visitor on almost no visitors. The calculation usually favours fewer ads on more traffic.

Test it on one section first rather than the whole site. Measure, then decide.

The second wave: AI answers

Recipe sites now face a second, separate pressure.

Simple factual recipe queries — cooking times, conversions, basic ratios — increasingly get answered directly in search. That is displacement, not a demotion, and it does not recover at a core update.

If your positions held and clicks fell, read traffic dropped but rankings the same before doing any HCU-style work. They need opposite responses.

How long it takes

Longer than anyone wants.

• The work: two to four months for a large archive.
• The reassessment: the next core update after it is done. As of late October 2026, none has run since May.
• Google’s own guidance: three to six months after a core update.

The wider method is in how to recover from the helpful content update, and the September 2023 update itself is covered in the September 2023 helpful content update.

What to keep when you consolidate

• Keep the strongest URL as the destination: the one with the most links and the steadiest traffic.
• Carry over the best of the others: a useful variation, a tested substitution, a reader question worth answering.
• Redirect every merged URL to the destination with a permanent redirect.
• Update internal links so they point straight at the destination rather than through the redirect.

Do not merge recipes that are genuinely different dishes. Consolidation is for near-duplicates, not for cutting page count for its own sake.

Done properly, readers land on one better page and lose nothing they used. Search engines see one clear answer where they used to see forty competing ones.

Show the cook, not just the dish

The strongest recipe pages prove someone made the food.

• Process photographs taken in your own kitchen, including the messy stages.
• What went wrong in testing, and how you fixed it.
• Tested variations, with what changed in the result.
• A named recipe developer, with their background.

That is the experience a scraped or AI-written recipe cannot fake, and exactly what quality systems are built to reward.

Travel sites face a similar mix of seasonality and AI displacement: travel and hospitality site recovery.