在 Schema.org 中为 MedicalWebPage 指定医疗专业 [英] Specifying medicalSpecialty in Schema.org for MedicalWebPage

问题描述

我正在构建一个医疗网页，我正在尝试构建页面架构.

I'm building a medical webpage and I'm trying to build out the page schema.

这是我现在所拥有的:

<script type="application/ld+json">
    {
    "@type":"MedicalWebPage",
    "audience":{
        "@type":"Patient",
        "@context":"https://schema.org"
    },
    "specialty":{
        "@type":"MedicalSpecialty",
        "@context":"https://schema.org"
    },
    "@context":"https://schema.org",
    "@id":"#/MedicalWebPage"
    }
</script>

但是，每个页面都有特定的医学专业，例如心血管或助产学，但我不知道如何做到这一点.我尝试了以下方法，但出现错误:

However, each page has a specific medical specialty like cardiovascular or midwifery, but I can't figure out how to do that. I've tried the following, but I get errors:

    "specialty":{
        "@type":"MedicalSpecialty",
        "@context":"https://schema.org",
        "content":"Cardiovascular",
    },


    "specialty":{
        "@type":"Cardiovascular",
        "@context":"https://schema.org"
    },


    "medicalSpecialty":{
        "@type":"Cardiovascular",
        "@context":"https://schema.org"
    },


    "specialty":{
        "@type":"MedicalSpecialty :: Cardiovascular",
        "@context":"https://schema.org"
    },


    "specialty":{
        "@type":"MedicalSpecialty > Cardiovascular",
        "@context":"https://schema.org"
    },

以下有效，但我不确定我是否会获得与我希望实现的相同的 SEO 好处:

The following works, but I'm not sure if I'm going to get the same SEO benefit as what I'm hoping to accomplish:

    "specialty":"https://schema.org/Cardiovascular",

谢谢！

推荐答案

在撰写本文时，schema.org 的这个区域似乎还没有真正清理到足以有固定答案的程度.您的问题还有一些动人的部分:

As of this writing it appears this area of schema.org is still not really flushed out enough for there to be a solidified answer. There's also a few moving pieces to your question:

• 它是否在测试工具中得到验证?
• 是否按照 schema.org 的建议正确实施?
• 它对搜索引擎有价值吗?

这个有点像兔子洞.从我查了一下，一切似乎都暗示 MedicalSpeciality 应该与 Hospital、MedicalOrganization、Physician 有关> 或 MedicalClinic.您可以看到 https://schema.org/MedicalSpecialty 本身列出的内容.这让我相信 MedicalSpeciality 确实最好应用于那些，而不是应用于 MedicalWebPage.

This one is a bit of a rabbit hole. From what I've looked up, everything seems to imply that MedicalSpeciality should be related to Hospital, MedicalOrganization, Physician, or MedicalClinic. You can see that listed on https://schema.org/MedicalSpecialty itself. This led me to believe MedicalSpeciality is really best applied to those vs. being applied to MedicalWebPage.

话虽如此 - MedicalSpeciality 是 Specialty 的子集，可以应用于 WebPage/MedicalWebPage.

Having said that - MedicalSpeciality is a subset of Specialty which can be applied to WebPage / MedicalWebPage.

我认为您最初是在正确的轨道上，这是我所做的修改.此代码在结构化数据测试工具中验证:

I think you were initially on the right track and here is the modification I made. This code validates in the Structured Data Testing Tool:

<script type="application/ld+json">
    {
    "@type":"MedicalWebPage",
    "audience":{
        "@type":"Patient",
        "@context":"https://schema.org"
    },
    "specialty":{
        "@type":"MedicalSpecialty",
        "@context":"https://schema.org",
        "name":"Cardiovascular"
    },
    "@context":"https://schema.org",
    "@id":"#/MedicalWebPage"
    }
</script>

当然，name 可以是任何东西，并且不会将其与 Schema 中的 Cardiovascular 明确联系起来 - 所以这不完全是您想要的.此外，虽然它在 结构化数据测试工具中进行了验证，但 Google 还推出了新的 Rich Snippets Results 工具 应该是替代品(但在我看来真的很缺乏 - 我在那里没有成功的测试片段).

Of course, name can be anything and doesn't specifically tie it to Cardiovascular from Schema - so not exactly what you'd want. Also while it validates in the Structured Data Testing Tool, Google also came out with the new Rich Snippets Results tool which is supposed to be the replacement (but in my opinion is really lacking - I've had no success testing snippets there).

我愿意查看更多具体/官方示例，但正如您可能从 https://schema.org 看到的那样 真的没有.

I'd be open to see more concrete/official examples but as you've probably seen from https://schema.org there really isn't any.

这将引导我进入下一部分以及为什么我以我以前的方式开始回答..

That leads me to this next section and why I started my answer off the way I did..

我在几个月前发现了这个 GitGub 线程(在撰写本文时)，由 schema.org 的贡献者撰写，主题为 MedicalSpecialty.我认为这很清楚地表明，即使是 schema.org 自己也没有真正提出如何映射医疗结构化数据的最终解决方案.

I discovered this GitGub thread from a few months ago (as of this writing), written by a contributor to schema.org on the topic of MedicalSpecialty. I think this pretty clearly states that even schema.org themselves haven't really flushed out a final solution to how medical structured data should be mapped.

在 schema.org 之上仍然需要清除细节 - 然后是谷歌和其他搜索引擎实现它的完全独立的问题.基于那个 GitHub 线程，看起来将来会有更多内容出现，但我现在不愿投入太多精力(这部分只是我的意见).通常，当谈到结构化数据和 Google 时，我通常认为它的主要好处只会来自 他们正式支持，其他任何事情最多只会产生轻微的影响.

On top of schema.org still needing to flush out the details - there is then the completely separate issue of Google and other search engines implementing it. Based on that GitHub thread it looks like there will be more to come in the future but I'd be hesitant to put much weight into at the moment (this part is just my opinion). Typically when it comes to structured data and Google, I usually assume it's main benefits are only going to come from what they officially support and anything else will have light impact at best.

另外 - 虽然我认为从代码的角度询问如何实现结构化数据适合这里，但这真的是在作为一个 SEO 特定问题的边缘摇摇欲坠，通常被认为是离题的 SO.我建议在 https://webmasters.stackexchange.com/

Also - While I think asking how to implement structured data from a code perspective fits here, this is really teetering on the edge of being an SEO specific question which is considered off-topic on SO generally. I'd suggest asking more SEO related questions around schema.org over at https://webmasters.stackexchange.com/

这篇关于在 Schema.org 中为 MedicalWebPage 指定医疗专业的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！