An important research question emerges: What is the difference between an Article and a Blogposting in schema.org parlance? A secondary question also emerges: What is the difference between an scholarly article and a nomral article? And thirdly How do I show that "this" web-page is about a published article but is not the article itself?
- https://searchengineland.com/schema-org-vs-what-google-supports-know-the-difference-video-333326
- https://www.similartech.com/compare/article-schema-entity-vs-blogposting-schema-entity
- https://moz.com/blog/json-ld-for-beginners
- https://www.hallaminternet.com/add-article-schema-markup-to-blog-posts/
- https://developers.google.com/search/docs/guides/intro-structured-data#technical-guidelines
- https://webmasters.stackexchange.com/questions/106351/blog-and-blogposting-for-google
- https://webmasters.stackexchange.com/questions/107877/which-schema-org-type-is-right-blog-or-blogposting-for-a-simple-blog-articl
- https://blog.hubspot.com/marketing/structured-data
- https://www.contentkingapp.com/academy/schema/
- https://developers.google.com/search/docs/data-types/article
- https://developers.google.com/search/docs/data-types/video
- https://builtvisible.com/micro-data-schema-org-guide-generating-rich-snippets/
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"potentialAction": {
"@type": "SearchAction",
"target": "//localhost:1313/?q={search_term_string}",
"query-input": "required name=search_term_string"
},
"url": "//localhost:1313/"
}
</script>
Here is the problem: This is not really an article page as in this is not the publication. The publication was somewhere else. This page simply describes, summarizes and points to the actual scholarlyArticle. So, I think this page should be simply a webpage in schema.org parlance.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "//localhost:1313/publication/2016-open-source-code/"
},
"headline": "Open Source Code Serving Endangered Languages",
"datePublished": "2016-05-23T00:00:00Z",
"dateModified": "2016-05-23T00:00:00Z",
"author": {
"@type": "Person",
"name": "Richard Littauer"
},
"publisher": {
"@type": "Organization",
"name": "Academic",
"logo": {
"@type": "ImageObject",
"url": "//localhost:1313/images/icon_hu0b7a4cb9992c9ac0e91bd28ffd38dd00_9727_192x192_fill_lanczos_center_2.png"
}
}, ;
"description": "We present a database of open source code that can be used by low-resource language communities and developers to build digital resources. Our database is also useful to software developers working with those communities and to researchers looking to describe the state of the field when seeking funding for development projects."
}
</script>
There needs to be a metadata element in the header to indicate if this is just blog post, a reivew, or an opinion article. https://schema.org/OpinionNewsArticle ; https://schema.org/ReviewNewsArticle
- Wordcount: https://gohugo.io/functions/countwords/