Hey Sandra,

I think you should be able to add images through Divi by following these steps:

1. Go to the page or post where you want to add the process shots.
2. Open the Divi Builder and click to add a new section or row.
3. In the row, click to add a Module and select the Image module.
4. Upload your process image.

If you want to display multiple images in a more visually appealing grid or gallery, you can try using Divi’s Gallery Module :

• Add a new row and select the Gallery module.
• Upload your process shots, and Divi will automatically organize them in a grid or slider format, depending on the style you choose.

Let me know if that works!

For the life of me I can’t figure out how to auto-generate responses and set up workflows for ManyChat. I want to be able to have someone comment on my post (a keyword), and then it will generate a DM to ask them for their email and they’ll be sent a link to the PDF. I can’t get it to work. And the ManyChat site doesn’t have great tutorials. Help!

I’d like to have an SEO audit done on my site and have my core web vitals ‘checked’? I don’t particularly even know what that means/entails but I’d love more info! Who are the best resources/people to do this? I know Casey Markee of course but I’m sure he probably has a pretty long waitlist.

Hi all,

I’m just wondering if anyone else is using Divi for their blog, and are you able to show process shots on your site?  I don’t love Divi (my website developer used it) as I find it restricting for my technically-challenged mind.  I’ve searched for answers and followed the screen recording for how to add blocks, but I just can’t access it.

I’ve taken a screenshot to show you what I have available -does this make sense?

Thanks,

Sandie

Hi Chelsea, I actually wrote a blog post about a similar topic, with a focus on maximizing content from one recipe. The recipe I used as an example is a butternut squash harvest salad. The recipe can be broken into 4 recipes (how to cut butternut squash, air fryer butternut squash, maple tahini dressing, and fall harvest salad). So the way I’ll go about it is by writing individual posts for the dressing, the air fryer butternut squash, and how to cut butternut squash. For the salad recipe, I’ll write the salad ingredients + maple tahini dressing & air fryer butternut squash as links to their own recipe post. The “how to cut butternut squash” will only be linked to the air fryer butternut squash recipe. This is a great approach for internal linking as well. Then you can link the dressing to other salad recipes. In the same way, you can link the how-to-cut butternut squash to other recipes that require the cubed squash.

I hope this makes sense and it’s not too confusing.

Sounds like a plan! 🤩 Happy to help, Chelsea!

Hey Kathryn!

The short answer is that it’s okay to use a longer title if it makes sense from both an SEO and user experience perspective. Yoast’s recommendation on title length is generally about ensuring that your title doesn’t get truncated in search results, which typically display the first 50–60 characters of a title. Longer titles might get cut off, potentially reducing their impact or making them less compelling to users.

That said, Yoast’s focus is more on the visual appearance in search results rather than the SEO value of the title itself. So, a long title might get flagged, but it doesn’t necessarily mean it’s bad for SEO—just that it might not be ideal from a click-through perspective if it’s cut off. More on that here!

I hope that helps!

Do you subscribe to
Dianne Jacob’s Substack newsletter? In today’s newsletter, she shared an email with Emily Weinstein (the Editor in Chief of NYT Cooking and Food). These questions/answers were so enlightening (and also just such a good reminder)!

Q. Your staff doubled between 2020 and now. Why is that?

A. The one-word answer is video. There are about 17 people now who work in video. In 2020 there were two.

Do you think food writers need to be good on video?

A. I don’t. These are really different skills. We work with freelancer writers who don’t have video skills.

Food writers need to hone an expertise, such as writing on Substack, that allows you to directly connect with people who want to cook your food and support your endeavors. Video makes a lot of sense, but you have to find your platform and work hard and strategically at it.

Especially this: “Food writers need to hone an expertise, such as writing on Substack, that allows you to directly connect with people who want to cook your food and support your endeavors.“

Such a straightforward way to describe what we’re all trying to do!

Thank you, this helps. In my full meal post I only optimized it for the protein KW, so I think I’m going to split out the instructions for the two sides and rewrite/photograph everything separately. Then I’ll use internal links to connect them. They’re all relatively low volume, but since I’m new and my domain authority is still low, it seems like it may be more search friendly to have three separate recipes (especially because the protein portion might appeal to someone, and the two sides might not).

This will also help me in my strategy for tackling other meals like this where there isn’t a KW that encompasses each part.

Hey Chelsea,

What a great question! I think you can definitely make this work without risking duplicate content or confusing your readers.

If you’re putting together a complete meal (protein, grain, side), you can create the main recipe post that combines each element. In this post, you can provide instructions for preparing the full meal — protein + grain + side — and then offer links to the individual recipe posts for each component. So instead of duplicating the full protein recipe in the main post, you could say something like: “For the full protein recipe, click here,” and then link to the standalone protein recipe. This avoids duplication because you’re not copying the content but rather linking to it.

If you do choose to write individual posts for each of the components (protein, grain, salad, dressing), you won’t be dinged for duplication as long as each post is unique and serves a different purpose. For example:

• The protein recipe post should focus on preparing just the protein with its own specific details.
• The side post (grains or greens) should focus on that side dish, with instructions specific to that recipe.
• If the same ingredients are used in both posts, make sure each post is framed differently. For instance, the protein post might be about the preparation of chicken, while the meal post would be about combining the chicken with the other components.

As for the salad and dressing, this is similar to the protein/grain dilemma. I’d approach this with the same strategy:

• If the salad and dressing are closely tied (as in the salad uses the dressing), then a single post for both could work. You can provide the full recipe for both the salad and the dressing in one post.
• If the dressing can stand alone and is versatile across other recipes, then it might be worth creating a separate post for the dressing. You can link back to the dressing recipe from the salad post, and vice versa!

I hope that helps!