- Joined
- Feb 23, 2021
- Messages
- 49
- Likes
- 30
- Degree
- 0
---
I asked chatbot and apparently I was listing the main entity in the wrong place. This validates but I'm still unsure if this is the best route.
I.e. maybe removing or disabling a graph piece is better so there's not multiple types of schema. I'm going to reference mainentityofpage for now, but interested to hear if there's a better way, or which way is the best.
--
Here's what chatbot said:
It's generally not recommended to have two conflicting schema types on the same page, as it can confuse search engines and affect your site's SEO performance. Therefore, it's important to ensure that you have only one primary schema type per page.
To reference your custom schema as the main entity, you can use the mainEntityOfPage property. This property specifies the main entity of the page, which can be any schema.org type, including your custom schema. In your case, you can modify your script to include the mainEntityOfPage property as follows:
Code:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Page Title",
"url": "https://example.com/page",
"mainEntityOfPage": {
"@type": "MedicalWebPage",
"publisher": {
"@type": "Organization",
"name": "NAME OF BRAND",
"logo": {
"@type": "ImageObject",
"url": "https://MYSITE.COM/LOGO/"
}
},
"headline": "A CATCHY YET AUTHORATATIVE HEADLINE",
"description": "META DESCRIPTION HERE",
"author": {
"@type": "Person",
"name": "NAME OF AUTHOR"
},
"lastReviewed": "2023-02-15T10:30:24Z",
"url": "https://MYSITE.COM/THE-ARTICLE-THAT-WAS-MEDICALLY-REVIEWED/",
"dateModified": "2023-02-15T10:30:24Z",
"reviewedBy": {
"@type": "Person",
"name": "Dr. SO AND SO, MD",
"sameAs": [
"https://SOCIALPROFILE1/",
"https://DOCTORPROFILE2/",
"https://SOCIALPROFILE3/",
"https://MYSITE.COM/MEDICALLY-REVIEWED-PAGE-OF-DR-SO-AND-SO"
]
}
}
}
</script>Note that I've wrapped your existing script inside the mainEntityOfPage property, and changed the top-level @type to "WebPage" to indicate that this is the main schema type for the page.
This tells search engines that the primary content of the page is a MedicalWebPage, which is defined by your custom schema.
Regarding deduplication, you can use the @id property to assign a unique identifier to your schema, and then use that identifier to reference it in other schema types on the same page. However, I don't see any duplicate schema in the code you provided, so it shouldn't be an issue in this case.
Once you've made these changes, you can test your schema using the Google Rich Results Test tool (https://search.google.com/test/rich-results). This tool will show you any errors or warnings with your schema, which you can then fix.
