- Issue created by @gravityBites
- πΊπΈUnited States DamienMcKenna NH, USA
Moving this to the Schema.org Metatag issue queue instead of Metatag.
- πΊπΈUnited States DamienMcKenna NH, USA
Schema.org Metatag's data structures are output in the page header as JSON-LD, what is output in the page's body text is not strictly relevant to the module's output.
You might disable the RDF module and see if the error goes away.
- π¨π¦Canada gravityBites
As an added question:
I've noticed the Schema.org module outputs in the<script type="application/ld+json"></script>
both the"@type": "Recipe",
and"@type": "Article",
in the Article and Recipe content types. This causes errors in my Rich Results Test. For example, an article will contain the"@type": "Recipe",
and then provides empty recipe tags that Rich Results Test doesn't like. How can I stop the module from producing both the"@type": "Recipe",
and"@type": "Article",
in all content? - πΊπΈUnited States DamienMcKenna NH, USA
To work around that problem (#4) you need to add default configurations for each content type; go to the main Metatag configuration page (admin/config/search/metatag), click the "Add default meta tags" link, select the content type you want to configure, then modify them as needed.
- πΊπΈUnited States DamienMcKenna NH, USA
I reviewed the output from the rich results test: https://search.google.com/test/rich-results/result/r%2Fguided-recipes?id...
It's hard to tell which data structure it's complaining about, because of the duplicate structures. Once you adjust the configuration so each content type has its own configuration it'll be easier to audit the output.
I also think there's a conflict between the RDF module's output and the JSON+LD output from Schema.org Metatag, if you remove the RDF module it'll also make this easier to review.
- π¨π¦Canada gravityBites
Thank you so much for your help in this matter.
I will do as you suggested, add default configurations for each content type and remove the RDF module.
If I run into any further issues with Metatags, I will be sure to ask. - Issue was unassigned.
- πΊπΈUnited States DamienMcKenna NH, USA
You're very welcome! Please let us know how it works out, I'm interested to know.
- π¨π¦Canada gravityBites
Thanks again for all your help. Everything is fixed and now working as expected. However, I had to uninstall the recipe module in order to uninstall the RDF module, as the recipe module was dependent on it. But I managed to recreate the recipe content type and am pretty happy with it. I now have to start re-entering the recipes, but fortunately, I have only had twelve entered so far, so it won't be a huge task.
- Status changed to Fixed
over 1 year ago 9:44am 30 May 2023 - πΊπΈUnited States DamienMcKenna NH, USA
Oh, I didn't even think of that, I figured the recipe content type was something you manually created.
Glad it's working correctly with just the Schema Metatag module suite.
Automatically closed - issue fixed for 2 weeks with no activity.