The obvious SEO move was eight recipe collection pages, and 37 of our 38 recipes suit low FODMAP, so we built none of them
Munchable has 38 recipes , each with its own page, and the index groups them by meal: breakfast, lunch, dinner, snack. The obvious thing to build instead is a collection per condition. Eight conditions, eight landing pages, eight head terms that people genuinely search, each one a tidy list of recipes that suit that pattern. It is the standard content play and it writes itself. I measured the…
Munchable has 38 recipes, each categorized by meal: breakfast, lunch, dinner, and snack. Building collection pages for each condition would yield eight pages with 38 recipes each, targeting eight search terms. Eight collection pages provide eight head terms that people search for genuinely. The overlap between conditions and recipes was measured, revealing that 37 of the 38 recipes are low FODMAP and 38 of them suit IBD.
Eight collection pages were planned, but only six would contain at least 34 recipes. This approach would result in near-duplicate content, compete with each other, consume crawl budget, and provide weak answers for strong queries. Grouping recipes by meal type is more appropriate, as people search for conditions and look for dinner.
The decision to group by meal rather than by condition was documented in the code, and the number of collection pages would be revisited when the recipe library is large enough for per-condition lists to genuinely diverge.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
