Home » SEO » Blog Structured Data and SEO – A Primer

Blog Structured Data and SEO – A Primer

We often say that effective SEO is the sum of many little things done right.

One of the many little things that can improve SEO is called structured data. While there are many types of structured data, we’ll focus on the types used for blog posts.

We’ll also provide some ideas about how you can feed more authority into your blog posts’ structured data.

First, let’s take a look at what structured data is.

About Structured Data

Think of structured data as “under the hood” information about your blog post for search engines.

Blog Post Structured Data Under The Hood

As you probably know, HTML stands for HyperText Markup Language. Structured data is some additional markup that can be added to your blog post’s HTML.

Just like the HTML that underlies every blog post, structured data markup is invisible to human readers (unless they decide to view your page source) — but it is visible to search engine bots that crawl your page. It gives search engine bots information that is not visible on the surface.

Structured data markup elements, as specified by Schema.org, can be used in many different ways, including for Organizations, Products, Events, LocalBusiness, Reviews, Videos, and FAQs.

Structured data is added to the head section of your post in a format called JSON-LD (JavaScript Object Notation for Linked Data). Technically, JSON-LD what’s known as an HTML script tag.

Schema.org provides a validator that generates structured representations of any JSON-LD that it finds. Structured representations are more easily readable by humans than scripts. They also display any warnings or errors.

It’s important to note that just because structured data shows up in the Schema.org validation tool, it doesn’t always mean that Googlebot or other search engine bots will recognize it as structured data.

The to see what Google recognizes is done by using Google’s Rich Results Test tool.

How is Structured Data Added to Blog Posts?

Here is how to automatically add structured data to posts on the two most used blogging platforms.

Structured data can be manually added, but that introduces a maintenance component.

WordPress

The most commonly used way for adding structured data to WordPress posts is by way of the Yoast SEO plugin. Yoast SEO automatically generates a detailed structured data script for each blog post.

If you’re not a Yoast user, the Schema plugin can be used to add BlogPosting markup to your blog.

Some WordPress themes generate structured data. Since we use Yoast SEO, we disabled the structured data that our theme auto-generates.

Wix

Wix provides instructions for how to automatically add structured data to every post.

Compared to Yoast, Wix generates a relatively compact blog post markup — about 30 lines compared to Yoast’s well over 200 lines.

Here’s an example of Wix post markup from this blog post.

Let’s look at the sections of structured data that are common to both Yoast SEO and Wix.

WebPage

Yoast SEO has a global and per post selector for Article Type. Selections include ‘Article’, ‘Blog Post’, ‘News Article’, and ‘Scholarly Article.’

Several WordPress sites that we manage display the generic ‘WebPage’ type, no matter what Article Type is selected in Yoast. (One of the vagaries of WordPress is that plugins can stomp on one another).

LabelContents
@typeWebPage
@idhttps://demo.crmswitch.com/inbound-marketing/wordpress-page-experience/#webpage
urlhttps://demo.crmswitch.com/inbound-marketing/wordpress-page-experience/
headline WordPress Page Experience: Retaining Beauty While Reducing Bloat 
datePublished2022-04-09T12:01:10+00:00
dateModified2022-04-16T13:54:06+00:00
descriptionHow can you get a page builder look on your WordPress site, yet achieve a performance score that makes Google happy?
wordCount703
thumbnailUrlhttps://demo.crmswitch.com/wp-content/uploads/2022/04/wordpress-page-experience.png
articleSectionSEO
inLanguageen-US

The date values are important, as these inform the search engine bot how recently the content was created or updated.

The articleSection value is a reflection of the blog post’s category. This is important information for search engines, especially when the blog post’s category is not part of the URL.

The Blog Post’s Author

This part of the mockup gives the search engine bots some author information that is not found on the human-readable page.

LabelContents
author
@typePerson
@idhttps://demo.crmswitch.com/#/schema/person/0ceb6596635cc2b0b2923a70e2e67a0a
nameJohn Abbott
sameAshttps://www.linkedin.com/in/jabbott/
sameAshttps://twitter.com/jabbott
sameAshttps://www.wikidata.org/wiki/Q123456789
image
@typeImageObject
inLanguageen-US
url https://secure.gravatar.com/avatar/d8ee6c2281f85fadaf886c509f3dbe4e?s=96&d=mm&r=g
contentUrlhttps://secure.gravatar.com/avatar/d8ee6c2281f85fadaf886c509f3dbe4e?s=96&d=mm&r=g
captionJohn Abbott

The Author sameAs Property

The ‘sameAs’ property does not appear in Wix’s ‘BlogPosting’ markup.

In WordPress, Yoast automatically uses some of the information it finds in the Contact section of the WordPress User Profile for the post’s author. This information is added to the markup with the Schema.org ‘sameAs’ property.

According to Schema.org, the ‘sameAs’ property is the “URL of a reference Web page that unambiguously indicates the item’s identity. E.g. the URL of the item’s Wikipedia page, Wikidata entry, or official website.”

TIP: The author’s ‘sameAs’ URLs may be an authority signal to the search engines.

Therefore, be sure to add the author’s LinkedIn page to their WordPress User Record at a minimum. Add their Twitter handle if they are active on Twitter.

If the author has a Wikidata page, it’s probably okay to add that to the Wikipedia field in the author’s profile for the purposes of getting the URL onto the schema.

If you happen to have an author who has a Wikipedia page (such as your CEO), that could be a bonus for authority.

The Author’s Image

WordPress doesn’t have a way to simply upload an image of an author to the author’s user profile. The user has to create a WordPress.com account and upload a headshot in order for the image to appear on a WordPress.org site as a Gravatar.

However, the Gravatar image file is a point of reference for the search engines.

In Wix, the author’s headshot can be easily uploaded from a local drive.

The Post’s Image

An image section is used to describe your blog post’s primary image. This will be the featured image if you have one. If you don’t have a featured image, it will be the first image found.

image
@typeImageObject
@idhttps://inbound.crmswitch.com/page-performance-score/#primaryimage
url https://inbound.crmswitch.com/wp-content/uploads/2018/11/wordpress-page-speed.png
width1280
height720

A best practice is to use featured images that are at least 1,000 pixels wide. But don’t make your images too large, as that can negatively affect your post’s SEO.

Publisher and Logo

Here is a simple Wix-like version of the section that informs search engine bots about the organization’s website that is hosting the blog content.

publisher
@typeOrganization
nameCRM Switch
logo
@typeImageObject
urlhttps://inbound.crmswitch.com/wp-content/uploads/2021/04/crm-switch-logo.png

Yoast SEO takes this section much further than Wix by nesting it within a broader ‘isPartOf’ property and ‘WebSite’ type. The plugin also adds company-level ‘sameAs’ references such as the company’s LinkedIn page and its Facebook page.

If your organization has a Wikipedia page, that could be an authority bonus that flows down to your blog content.

Be sure to add your company’s social profiles under Social – Yoast SEO > Account tab > Organization social profiles so they will be picked up by the schema-generator.

Conclusion

The subject of schema and blog post markup goes a lot deeper than what we have covered here. If you examine Yoast’s markup, you’ll see many more sections.

Whether Wix’s compact approach or Yoast SEO’s detailed markup is better for SEO is a difficult question to answer.

But most will agree that it’s better for SEO to have some level of blog post structured data rather than none.

Follow the author or comment on LinkedIn or Twitter