What happens if we embed the recipe into a post?

Hi there,

1. What do you mean by “they dont work independently”? There should be no need to embed them into posts. We recommend just using them alongside posts.

2. The metadata is included in the recipe box, so it is present wherever the recipe box is added.

Brecht

I mean, since these are custom post types, they dont work just as fine as the regular posts; the related posts, sidebars etc.

this may cause duplicate content issue if you dont know what you are doing.

the metadata is included, I can see that from the page source, buy what I mean is does it act like a real recipe with markup if you embed them into posts? does it show up on google serps just as the real recipe?

I would like to see a real recipe plugin where you could insert your recipe into posts without generating a custom post type. but I guess this is not possible anymore.

my only concern is, no offence, but in the past, soem of the recipe plugins stole the recipes of people and served them from their own servers like they own them, and some of them sold the recipes to big brands.

I believe you don’t have that intention.

thanks

I decided to have recipes as custom post types when I started the plugin and there’s no way back now, I’m afraid.

That said, it should be possible to have them behave exactly like normal posts. Related posts, sidebars and all. If any of those aren’t working for recipes, just let me know what plugin or theme you are using. They can usually be made compatible with custom post types with just a quick code fix or by using an alternative plugin (YARPP for related posts, for example).

I’m actually not 100% sure of the post would should up as a rich snippet. The URL points to the recipe post type, so that might be an issue. I recommend not including them anyway to avoid duplicate content.

Stealing recipes is definitely not on our todo list. That might be an issue with free plugins but our business is the Premium plugin for creating recipes, so we’d be shooting ourselves in the foot if we started stealing recipes as no one would be buying our plugin anymore.

Brecht

here is my solution;

I noindex the recipes and post new posts and insert shortcode.
but the problem is, you cannot noindex the printer-friendly version.

do you have a fix for that?

Well, you could enabled the Legacy Print Mode on the Recipes > Settings > Recipe Template > Print Version page. Then there won’t be a link to the print page.

But again, I really recommend just using the recipes as is and not inserting them into posts.

thanks, but standalone recipes dont just work on my theme. so I have to insert them to posts.

plugin has great features, such as ingredient post types etc. but in the meantime, they also cause duplicate content as categories.

so I had to noindex them all. do you have a recommendation on that?

update;
I enabled legacy print mode, but its not working.

What theme are you using and what’s the exact issue with it? It’s probably just a quick fix to make it work fine for recipes. I strongly recommend going that route.

In our next update we’re adding this meta tag to the /helpers/print_template.php file, you could do that already:
<meta name="robots" content="noindex">

Brecht

<meta name=”robots” content=”noindex”>
this tag is for the legacy print mode i guess, is it true?
if so, it may not help for the actual print page.
and it would be great if you could also add nofollow and rel=”canonical” tag for the next update.

I am using “the voux” theme from themeforest.
I appreciate if you can find a quick fix.

why do you recommend recipe posts?

and how about ingredient and other custom category types?
they may also cause duplicate content but in the meantime great for google searches.

That meta tag is for the new print mode, not the legacy print one. It should be the only meta tag you need. No need to define nofollow twice.

Could upload a zip file your theme over here? I’ll have a look: https://dbinbox.com/bootstrappedventures

I recommend just using recipes because the plugin has been designed that way. You won’t have issues with duplicate content or the metadata pointing to the wrong URL. Most of our premium features (like the Meal Planner, for example) also use recipes, not posts.

What would be the issue with ingredients? I don’t see a duplicate content issue there?