Steve Grunwell

Structured data allows developers and publishers to mark up content in a way that it’s easy for machines to understand. Proper use of structured data <a href="https://developers.google.com/search/docs/guides/intro-structured-data" rel="nofollow ugc">enables third-parties like Google to parse reviews, event data, and contact information in meaningful ways</a>, ensuring you’re getting the most “bang” out of your publishing buck.
Fortunately, the major players in the Search game, including Google, Microsoft, Yahoo!, and Yandex) came together in the early 2010s to form <a href="http://schema.org/docs/about.html" rel="nofollow ugc">Schema.org</a>, a collaborative, community-driven standard for structured data.
With the major search engines and communities behind it, we’re all marking up everything with appropriate structured data now, right?
Unfortunately, the process of implementing Schema.org in a site — especially one driven by dynamic content — is less than straightforward. <a href="https://wordpress.org" rel="ugc">WordPress</a>, for instance, <a href="https://ma.tt/2015/11/seventy-five-to-go/" rel="nofollow ugc">powers roughly a quarter of the web</a>, but implementing structured data across hundreds of thousands of themes would be a nightmare.
Or, at least it would be, if it weren’t for Schemify.
<h4>What does Schemify do?</h4>
There are two approaches to adding structured data to a website: via the markup or <a href="http://json-ld.org/" rel="nofollow ugc">JSON for Linking Data (JSON-LD)</a>.
Consider the following author information, which might appear at the bottom of a blog post:
<pre><code> 
 
 <a href="https://stevegrunwell.com" rel="author nofollow ugc">Steve Grunwell</a>
 Steve is the Director of Technology at Growella. When he's not working, you can find him speaking at conferences, roasting coffee, or spending time with his wife and daughter
 
</code></pre>
If I wanted this information to use Schema.org markup, it would look something like this:
<pre><code> 
 
 <a href="https://stevegrunwell.com" rel="author nofollow ugc">Steve Grunwell</a>
 Steve is the Director of Technology at Growella. When he's not working, you can find him speaking at conferences, roasting coffee, or spending time with his wife and daughter
 
</code></pre>
While that may not seem like a lot of work, that’s still a lot of extra markup being added. Even worse, a lot of that markup might normally be generated by WordPress helper functions like <a href="https://developer.wordpress.org/reference/functions/get_avatar/" rel="nofollow ugc"><code>get_avatar()</code></a>, which means extra work to get the necessary <code>itemprop</code> attribute in place.
Fortunately, the other approach for adding structured data is much more straight-forward in a theme, as it’s simply a JSON-LD object:
<pre><code> 
 {
 "@context": "http://schema.org",
 "@type": "Person",
 "name": "Steve Grunwell",
 "url": "https://stevegrunwell.com",
 "image": "https://secure.gravatar.com/avatar/88ea4e10ed968136228545d7112d82cb?s=200",
 "description": "Steve is the Director of Technology at Growella. When he's not working, you can find him speaking at conferences, roasting coffee, or spending time with his wife and daughter"
 }
 
</code></pre>
We simply generate this JSON-LD object and append it to our document’s <code><body></code>. When Google or anyone else who supports JSON-LD structured data parses our page, they can immediately understand that Steve Grunwell is a person and determine his website, avatar, and biography.
The best part? There’s no need to change the markup within our theme!
Schemify aims to automate the generation of JSON-LD objects for content within WordPress. Its flexible structure and reasonable defaults enables drop-in support for structured data, regardless of the WordPress theme.

Schemify

Adding schema to a site no longer has to be an afterthought. This plugin took our structured data game to the next level and I look forward to seeing how it helps improve our search ranking!

As advertised

Automatically generate Schema.org JSON-LD markup for WordPress content.

JS Morisset

Is Google Search reporting invalid Schema markup from your theme templates?
Do you need to remove old Microdata and RDFa markup from your theme templates?
Do you need to remove duplicate social or SEO meta tags from your webpage?

By default, the WPSSO Strip Schema Microdata (WPSSO SSM) add-on can remove old Schema Microdata and RDFa markup from the webpage. The settings page also allows for the optional removal of duplicate / conflicting Schema markup and meta tags from the webpage head or body sections.
WPSSO SSM filters the webpage dynamically, allowing you to activate or deactivate the add-on to enable or disable the removal of old Schema Microdata, RDFa, and duplicate meta tags. The WPSSO SSM webpage filter is very fast – generally running in under 0.003 seconds.

<h3>WPSSO Core Required</h3>
WPSSO Strip Schema Microdata is an add-on for the <a href="https://wordpress.org/plugins/wpsso/" rel="ugc">WPSSO Core plugin</a>, which creates extensive and complete structured data to present your content at its best for social sites and search results – no matter how URLs are shared, reshared, messaged, posted, embedded, or crawled.

WPSSO Strip Schema Microdata

Remove Schema Microdata and RDFa from the webpage for better Google Rich Results using Schema JSON-LD markup.

Schemify vs WPSSO Strip Schema Microdata