[Pandora]

I purchased this template today and it seems that when you insert a recipes into a post you’re then left with two identical pages at different urls. The template description says it’s SEO friendly but surely this is going to create duplicate content issues (both versions of the page have the canonical link set to their own url). It also isn’t great for usability as half the readers are going to be commenting on one version of the recipe and half on the other.

Am I missing a setting or something to stop two versions of the same recipe appearing on the site?

Thanks

[serkan]

Hello, After you install and activate the following plug-in to solve the problem of duplicate-content in the search result, you need to go to Settings> Revelanssi> Indexing page and click Build the index plug button and the problem must be solved.

https://wordpress.org/plugins/relevanssi/

Have a nice day.

[Magda_T]

Hello Serkan,
I’ve had the same problem and I’ve install Relevanssi but when I exclude cp_recipe to avoid the double results – even if a recipe is always a part of an article – the search result is not indexing ANY part of the recipe – no excerpt, no ingredients, no cooking steps.
Please help.

Thank you

[serkan]

Hi Magda_T,
You can search an alternative plugin for this feature, btw i will search an alternative one as well.
Also, you can create a ticket for plugin support;
https://wordpress.org/support/plugin/relevanssi/
Thanks for your patience.

[Magda_T]

Hello, any News?

I’ve discovered that if “Expand shortcodes when indexing” is enabled in Relevanssi indexing settings and it’s not working then it’s possible the recipe shortcode is not compatible with Relevanssi – and that’s not uncommon for shortcodes that embed posts within posts.

Any idea if the shortcode may not be compatible and if it is which type of an alternative plugin I should use?

Thanks

[serkan]

Hi,
We haven’t tested the theme with this plugin. If you have trouble, you can create a ticket and ask this issue to our plugin’s developer. I also waiting for an answer from them. We didn’t code the plugin that is why cannot modify anything before asking them.
https://wordpress.org/support/plugin/relevanssi/
Thanks for your understanding.

[Magda_T]

Thanks Serkan!
I’ve already contacted the Relevanssi support and they were very helpful even if it was not possible to solve my problem because: “The authors of the Cooked plugin have made it very strict: there’s no chance the shortcodes can be used in admin context, only in front-end. Unfortunately Relevanssi indexing happens in admin context. Thus, when Relevanssi tries to expand the shortcodes in indexing, the Cooked plugin has them disabled”.

So the problem is the Cooked plugin if I can say so…
Is there any chance to make them change the restrictions about expanding the shortcodes?

[serkan]

Hi,
I will create a ticket about this issue. I will talk to cooked plugin’s author and will keep you updated.
Thanks for your patience.

[serkan]

Hi,
Could you also create a ticket and talk to cooked plugin’s author as well?
https://wordpress.org/support/plugin/cooked/
Thanks

[Magda_T]

Hello,
I’ve already done this almost 2 weeks ago but never got a reply…
It seems quite an incorrect approach to their customers…

Maybe you’ll be more lucky.

thanks

[serkan]

Hi,
We are still waiting for a response from them. I will keep you updated when they give me an answer.
Thanks

[pau4navarro]

Looking forward to this issue as well :-)