Add Schema markup to blog

[Marcolì]

Hi,

I'm looking for a tool like Yoast SEO because I need to implement some schema markup (J-SON) on my articles. 

Anyone has tried something similar? 

Thanks!

[JAbitbol · Accepted solution]

Hey @Marcolì, I came across this very late but just in case others are also looking for guidance:

1) If you're looking to add schema markup to individual blog pages instead of the template you can add it by heading to the "settings section" in your post page. Navigate to the advanced section and drop the script into the "additional code snippets" section.

2) Hubspot made an update a while back that auto-applies Article Markup to all blog pages. 

That said, if you are looking to add additional markups like video you can do this by following the steps in 1). 

[SaltySteve · Accepted solution]

Have you tried Schema Helper for HubSpot?  The functionality is limited, and the support is nearly non-existent, but it's inexpensive and saves marketers from needing to figure out how to structure & write JSON code or open individual page headers to add many of the most common schemas.  Monthly by month subscription is easy to cancel if you don't love it, so may be worth a try.

[ChrisChin_LLF · Accepted solution]

probably way late for you, but in case anyone else wants to know how to deal with this, it's been my afternoon project and you can add this directly to your blog template and it will auto generate blogposting schema.

<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "{{content.title}}",
"description": "{{content.metaDescription}}",
{% if content.use_featured_image %}
"image": [
"{{content.featured_image}}"
],
{% endif %}
"datePublished": "{{content.publish_date|datetimeformat('%Y-%m-%d')}}",
"dateModified": "{{content.updated|datetimeformat('%Y-%m-%d')}}",
"author": {
"@type": "Person",
"name": "{{content.blog_post_author.full_name}}",
"url": "{{content.parent_blog.root_url}}/author/{{content.blog_post_author.slug}}"
},
"publisher": {
"@type": "Organization",
"name": "YOUR COMPANY NAME HERE",
"logo": {
"@type": "ImageObject",
"url": "YOUR LOGO HERE"
}
}
}
</script>

[AWynn9]

Hi Folks,

We're attempting to rollout schema markups across our blog, where we've prviously had none. I made a few edits to the templated solution provided in this post and successfully verified the schema markups with Google's Rich Results Test and the Schema.org validation tools. My concern however, is the dateModified field now reflects the moment I posted the updated schema, despite not making any revisions to the content in the blog itself.

Is there any downside or potential risk to applying this markup to our blog theme itself and subsequently all blog pages without making any large enough edits or changes to the content itself? For example, we have many blogs from ~2016- in this case the datePublished field is still accurate, however it now shows lastModified as today.

Before applying these markups to all blog posts, are there risks of being penalized for having all dateModified fields across hundreds of blogs to be updated at the same time? If so, does anyone have any proposed workarounds to not including the schema updates in the dateModified snippet? Thanks!

[Humashankar · Accepted solution]

Hi @AWynn9 

When updating content, it's crucial to follow a best practice to maintain accuracy and avoid potential issues.

• To avoid sending misleading freshness signals, it's recommended to only use the dateModified field for genuine content changes.

Bulk-updating old posts can pose a risk, even if it rarely triggers penalties. To mitigate this, consider one of two approaches: either update the dateModified field to reflect actual edits or omit it altogether, while ensuring the datePublished field remains accurate to maintain context about the original publication date.

Best Regards

[AWynn9]

Hi @Humashankar,

That's exactly what I was after- thank you for the quick response and information! I believe I'll omit the dateModified field for the blog template all together and instead look at manually adding it in when we make substantial changes to the content (past or future).

Also thanks to @Victor_Becerra for looping in the assistance, appreciate you both!

Best,
Alex

[Victor_Becerra]

Hi @AWynn9 
Thank you for reaching out to the Community!
I'd like to invite some community members who are subject matter experts to join this conversation.
@Shubham_Sharma @Humashankar @franksteiner79 - Would you be able to share any insights on this? Your expertise would be greatly appreciated.
Best,
Victor

[SaltySteve · Accepted solution]

Have you tried Schema Helper for HubSpot?  The functionality is limited, and the support is nearly non-existent, but it's inexpensive and saves marketers from needing to figure out how to structure & write JSON code or open individual page headers to add many of the most common schemas.  Monthly by month subscription is easy to cancel if you don't love it, so may be worth a try.

[JAbitbol · Accepted solution]

Hey @Marcolì, I came across this very late but just in case others are also looking for guidance:

1) If you're looking to add schema markup to individual blog pages instead of the template you can add it by heading to the "settings section" in your post page. Navigate to the advanced section and drop the script into the "additional code snippets" section.

2) Hubspot made an update a while back that auto-applies Article Markup to all blog pages. 

That said, if you are looking to add additional markups like video you can do this by following the steps in 1). 

[Crystal_Hopper]

Hi @JAbitbol! I'm not quickly finding proof for your point #2 that markup is being auto applied to blog pages. Can you post an article or information to show that from HubSpot? Thanks!

[STierney]

Hey @Crystal_Hopper - thanks for following up here!

I'm also not seeing this documented, but I'm intrigued by @JAbitbol's update! I'm hoping we do have a resource that outlines this somewhere for reference.

Shane, Senior Community Moderator

[Teun]

Hi @Marcolì ,

What schema markup do you want to add?

You can add the required markup by adding some code to the head or footer of the blog post template.

[Marcolì]

Hi @Teun ,

I would like to add article and breadcrumbmarkup (with JSON-LD). So it would be a dinamic markup based on type of article.

[Teun]

HI @Marcolì ,

Could you tell me a bit about where you set the 'type' of the article? Is it based on the blog topics? Do you have an example of one of your articles?

[Marcolì]

Hi, for example: I would put that JSON on every article, at least taking automatically the title and description (it's ok to put in the end of the body):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://blog.example.com/blog-example"
  },
  "headline": "This is an example",
  "description": "This is a description aboutn this blog post.",
  "image": "https://blog.example.com/example-image.jpeg",  
  "author": {
    "@type": "Organization",
    "name": "Example author",
    "url": "https://www.blog.example.com/example-author"
  },  
  "publisher": {
    "@type": "Organization",
    "name": "",
    "logo": {
      "@type": "ImageObject",
      "url": ""
    }
  },
  "datePublished": "2022-07-26"
}
</script>

[ChrisChin_LLF · Accepted solution]

probably way late for you, but in case anyone else wants to know how to deal with this, it's been my afternoon project and you can add this directly to your blog template and it will auto generate blogposting schema.

<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "{{content.title}}",
"description": "{{content.metaDescription}}",
{% if content.use_featured_image %}
"image": [
"{{content.featured_image}}"
],
{% endif %}
"datePublished": "{{content.publish_date|datetimeformat('%Y-%m-%d')}}",
"dateModified": "{{content.updated|datetimeformat('%Y-%m-%d')}}",
"author": {
"@type": "Person",
"name": "{{content.blog_post_author.full_name}}",
"url": "{{content.parent_blog.root_url}}/author/{{content.blog_post_author.slug}}"
},
"publisher": {
"@type": "Organization",
"name": "YOUR COMPANY NAME HERE",
"logo": {
"@type": "ImageObject",
"url": "YOUR LOGO HERE"
}
}
}
</script>