Recipe Roundup Posts: How to Run One With Other Food Bloggers
A recipe roundup is a post that collects recipes on one theme, and the multi-blogger kind features dishes from other food bloggers, each with a photo, a short description and a link to the original. Most guides explain how to build the roundup block in a recipe plugin. This one covers the part nobody writes down: how to invite contributors, set deadlines, get photo permission, link fairly and launch so every contributor shares it, with a timeline and templates you can copy.

What a multi-blogger recipe roundup is (and why run one)
A recipe roundup is a themed list: "18 make-ahead Thanksgiving sides", "15 one-pot vegan dinners". You can build one from your own archive, which is a good internal linking exercise (see our internal linking guide). A multi-blogger roundup goes further: you feature other food bloggers' recipes and they help spread the post.
Why it is worth the coordination:
- Readers get a better post. Twenty tested recipes from twenty kitchens beat twenty variations from one.
- Every contributor has a reason to share. Their recipe is in it.
- It starts relationships. A roundup is the lowest-pressure way to begin working with other bloggers, and often leads to swaps and guest posts. Our blogger collaboration guide covers what comes next.
The roundup timeline at a glance
| When | Host does | Contributors do |
|---|---|---|
| 4–6 weeks before | Pick the theme, set the dates, build the invite list | — |
| 4 weeks before | Send invites with the brief and form | Reply yes or no |
| 2 weeks before | Deadline for submissions; send one reminder a few days earlier | Submit link, photo, description, permission |
| 1–2 weeks before | Check every link, edit descriptions, assemble the post | — |
| Launch day | Publish, email every contributor the link and a share kit | Share the post |
| Ongoing | Check links once or twice a year, update the post each season | Tell the host if a URL changes |
For seasonal themes, work backwards from when people start searching, not from the holiday itself. A Thanksgiving roundup published the week of Thanksgiving is late.
Running the roundup, step by step
Step 1: pick a theme that is specific and searchable
"Soup recipes" is too broad to rank and too vague to be useful. "Freezer-friendly soups for new parents" tells readers and contributors exactly what belongs. A good roundup theme:
- Is something people actually look for (type it into a search bar and read the suggestions)
- Has room for 10 to 25 genuinely different recipes
- Fits your own blog, so it makes sense on your site
- Has a natural reason to update it (a season, a holiday, a diet trend)
Step 2: build and vet the invite list
Invite more people than you need, since some will not reply. Look for bloggers whose recipes you would happily cook: people you already follow, contributors to other roundups in your niche, members of food blogger groups.
Before you invite anyone, spend a minute on their site. Is it active? Does it have a real author? Is every post stuffed with unrelated paid links? A link from your roundup is an editorial recommendation, so you want to stand behind it. The free Quality Score check shows a site's level with the evidence behind each number, which helps when you are unsure.
Step 3: send a clear invite
A good invite answers every question up front, so contributors can say yes in one reply. A template to adapt:
Subject: Featuring your [recipe type] in a [theme] roundup?
Hi [Name], I'm putting together "[working title]" on [your blog], publishing around [date]. I'd love to include your [specific recipe, if you have one in mind].
What I need by [deadline]: the recipe link, one horizontal photo you're happy for me to use, and one or two sentences on what makes it special. Here's a short form: [link].
I'll credit you by name with a link to the recipe, and I'll send you the live link on launch day. No cost and no obligation. Totally fine if it's not a fit!
[Your name], [blog]
Two rules: never make a reciprocal link a condition of inclusion, and do not charge contributors. More on why below. For more outreach wording, see our outreach email templates.
Step 4: collect submissions with a simple form
Email threads get lost. A free form tool or shared spreadsheet keeps everything in one place. Fields to collect:
- Blogger name and blog name (as they want to be credited)
- Recipe title and the exact recipe URL
- Photo upload or link, plus photographer credit if it is not the blogger
- One or two sentences in their words about the recipe
- Dietary tags if your theme needs them (vegan, gluten-free)
- A checkbox: "I own this photo and give [blog] permission to use it in this roundup with credit"
- Best email for the launch-day notice
Step 5: handle photo rights properly
This is where roundups most often go wrong. A food photo is a creative work, and the person who took it usually owns the copyright. Linking to the recipe and naming the blogger does not by itself give you the right to republish their image.
The simplest safe approach is permission: use only the photo the contributor sent you with the permission checkbox ticked. Some bloggers lean on fair use instead, but the US Copyright Office says courts decide fair use case by case and that there is no fixed safe amount you can use without permission. A written yes avoids the question entirely. Other practices that keep everyone happy:
- Use one photo per recipe, never a gallery from the original post.
- Do not crop out watermarks or edit the photo beyond resizing.
- Credit the photographer by name next to the image.
- If someone later asks you to remove their photo, do it promptly.
Step 6: link etiquette for roundups
Every featured recipe gets a link. How you link matters for readers and for search:
- Link to the recipe page, not the homepage. Readers came for the dish.
- Use the recipe name as the anchor text, such as "Smoky black bean soup". Our anchor text guide explains why descriptive anchors beat "click here".
- One clear link per recipe is enough. A second "get the recipe" button is fine; ten links to the same blog is not.
- Never require links back. Google's spam policies list "excessive link exchanges ('Link to me and I'll link to you')" as link spam. Contributors are welcome to share or link to the roundup, but it should be their choice.
- If money or anything of value changes hands (paid inclusion, a sponsor), mark those links with
rel="sponsored"as Google recommends in its guide to qualifying outbound links, and disclose it to readers. The FTC notes that disclosure can be needed even when no money changes hands, for example when people agree to promote each other, so a short note on how the roundup came together is a good habit.
Step 7: structured data and carousels (what not to expect)
Recipe plugins often offer a roundup block that can output list markup. Know the limit before you rely on it: Google's carousel documentation says that for a summary page, "all URLs in the list must point to different pages on the same domain". A roundup of other bloggers' recipes does not meet that rule, so it is not eligible for a host carousel. Two practical consequences:
- Do not add Recipe structured data for recipes that live on other people's sites. The recipe markup belongs on the page that actually has the recipe.
- If your roundup mixes your recipes and other bloggers', any list markup should cover only the items on your own domain. Many plugins handle this automatically; check your plugin's settings and test the page with Google's Rich Results Test.
The roundup still ranks as a normal page. Its strength is usefulness, not special search features.
Step 8: write the post
A roundup that is only photos and links is thin. Make it the most useful page for the theme:
- A short intro that tells readers how to use the list ("start with the first three if you're short on time").
- Group recipes into sections (by main ingredient, time, diet) rather than one long scroll.
- For each recipe: the photo, the recipe name as a link, the blogger's name, and one or two sentences of your own on why it is included. Add one practical note where you can (freezes well, ready in 30 minutes, nut-free).
- A closing section with tips for the theme: how to plan the menu, what to make ahead.
Step 9: launch so everyone shares it
On publish day, send every contributor one short email with:
- The live link
- Their position or section ("you're in the 'under 30 minutes' section")
- A ready-to-use image and a one-line caption they can paste into a post or newsletter
- A thank-you, and an open invitation for the next roundup
Then share it yourself and reply to everyone who shares it. The goodwill from a well-run launch is worth more than any single share.
Step 10: maintain it
Roundups decay: blogs move, recipes get renamed, photos disappear. Once or twice a year, click every link, replace broken entries with new contributors, refresh the intro for the season, and tell any new contributors they are in. A maintained roundup can stay useful for years; a neglected one becomes a page of broken links.
Roundup checklist
- Specific, searchable theme with room for 10–25 recipes
- Dates set by when people search, not by the holiday
- Invite list vetted, with more names than slots
- Invite with brief, deadline and form; no reciprocal links, no fees
- Written photo permission for every image, with credit
- Descriptive anchor text pointing to each recipe page
- No Recipe markup for other people's recipes
- Your own note on each recipe, grouped into sections
- Launch email with share kit to every contributor
- Link check once or twice a year
From one-off roundups to ongoing partners
A roundup is a single event: a lot of coordination for one post, and the relationships fade unless someone organizes the next round. If you would like cross-promotion with related blogs to continue between roundups, a Satelo circle is one option. Sites in the network host partner articles about related blogs and receive articles about their own in a circle, every article is labelled as partner content and its links use rel="sponsored". It is a public beta with a small network, so it works alongside your own roundups rather than replacing them.
What to do next
- Choose a theme people will search for six to eight weeks from now.
- Draft your invite list and check each blog: you will see its Quality Score and the evidence behind every number in about 30 seconds.
- Send the invite template above with a form and a firm deadline.
- If you want labelled partner articles between roundups, connect your site to Satelo for free.
FAQ
What is a recipe roundup?
A post that collects recipes on one theme, such as holiday sides or quick vegan dinners. Each entry has a photo, a short description and a link to the full recipe, either on your own blog or on other bloggers' sites.
How do I ask bloggers to be in my roundup?
Send a short invite with the theme, publish date, deadline, what you need (recipe link, one photo, a sentence or two) and a form. Promise credit and a launch-day link, and never make a link back a condition.
Can I use other bloggers' photos in a recipe roundup?
Ask first and get permission in writing. Use one photo per recipe, keep watermarks, credit the photographer and remove the photo promptly if asked.
Are recipe roundups good for SEO?
They can rank like any useful page if the theme is specific and the post adds real guidance. A roundup of other sites' recipes is not eligible for Google's host carousel, which requires every listed URL to be on the same domain.
Should roundup links be nofollow?
Editorial links you chose freely do not need special attributes. If a contributor paid to be included or the roundup is sponsored, mark those links rel="sponsored" and disclose it.
How many recipes should a roundup have?
Enough to cover the theme without filler; many themes work well with 10 to 25 genuinely different recipes grouped into sections.
Read next




Check your site's Quality Score
Free, no sign-up: a 0–100 score from mostly open data. Then add your site to Satelo and get partner articles from sites of your level.
Enter a domain like example.com
Add my site