<h4>Why this plugin exists</h4>
<p>Original Plugin (discontinued): https://de.wordpress.org/plugins/json-ld-for-article/</p>
<p>Sadly, the original plugin is not being developed anymore. So I decided to fix some bugs like invalid markup,<br />
    missing tags, putting objects into fields instead of just URLs for images, and implementing for more than just<br />
    articles.</p>
<p>Also, this plugin plays nicely with <a href="https://de.wordpress.org/plugins/yet-another-stars-rating/" rel="nofollow ugc">YASR – yet another star rating</a>. It will<br />
remove yasr’s invalid jsonld-syntax and instead use YASRs rating.</p>
<p>All requests are being cached and purged on page update/edit etc.</p>
<p><a href="https://waffle.io/bmhm/wp-jsonld" rel="nofollow ugc"></a></p>
<h4>Original description</h4>
<p>Search engines such as Google are using structured data markup in many ways—for example, to create rich snippets in search results. Search results with rich snippets will improve your click through rates and increase the number of visitors on your website.</p>
<p>It has been a tedious task to add the complicated Schema.org markup to your website – sometimes it wasn’t even possible due to technical constraints. Now, thanks to <strong>JSON-LD</strong>, almost any website can enjoy the benefits of structured data. For WordPress users it’s even easier thanks to this plugin.</p>
<p>JSON-LD for Article is simply the easiest solution to create valid schema.org microdata markup on your WordPress site automatically from your web content and its metadata. All you need to do is install and activate the plugin, and it will generate JSON-LD markup of your posts that Google and other search engines can use for rich snippets using the schema.org for articles.</p>
<p>Some WP themes include traditional schema.org markup embedded in the html code the theme produces. If you are using one of these themes, this plugin is probably not necessary. If the markup produced by the theme contradicts the data specified in the JSON-LD, the added information might be not be helpful at all. Thus you should check the markup provided by the theme before adding possibly unnecessary JSON-LD to your site.</p>
<p>On the other hand, if you use a custom theme, it is easier to use the functionality provided by the plugin than to invent the wheel again and add the markup in html. Very often, this leads to html code that is difficult to read and is not valid structural markup according to Google’s validator.</p>
<p>Our plugin:</p>
<ul>
<li>Helps your site to earn rich snippets in Google’s SERP.</li>
<li>Does not depend on other plugins or external code.</li>
<li>Is simple to install: plug-and-play, no need to configure anything.</li>
</ul>


wp-jsonld

wp-jsonld is the continuation of the simplest solution to add valid schema.org microdata as JSON-LD-script to your blog posts and articles.

<p>Powerful, flexible, XHTML-compliant, server-side code highlighting, credits for everything<br />
but ‘making it a plugin’ go to <a href="http://jpipes.com/index.php?/archives/216-Syntax-Highlighting-and-Allowing-HTML-in-Comments.html" rel="nofollow ugc">Jay Pipes</a><br />
and <a href="http://geshi.org/" rel="nofollow ugc">GeSHi</a>.</p>
<h4>Features</h4>
<ul>
<li>Highlight sources of any language</li>
<li>automatically, server-side (no javascripts)</li>
<li>XHTML-Compliant, <code><div></code>, <code><ul></code>, <code><span></code> with class-attributes and a css-file are used for styling    </li>
<li>optionally add a heading for every code-block</li>
<li>optionally specify line-number offset (BREAKS XHTML COMPLIANCE)</li>
<li>optionally don’t display line-numbers</li>
<li>set per-codeblock if the code is html_entity_encoded or not</li>
<li>only parses <code><pre></code>-tags with the <code>lang=</code>-attribute, thus does not interfere with any regular preformatted contents you might have</li>
<li>degrades beautifully through <code><pre></code>-tags (if you keep the sources clean, that is)</li>
<li>all settings through logical, valid arguments for the main container</li>
<li>comes with generic cross-browser CSS (tested: IE5.5+, FF, Safari, Opera)</li>
</ul>
<h4>Version History</h4>
<ul>
<li>1.3: Thanks to a tipp now the link-path to the stylesheets is correct, sorry for the inconvenience</li>
<li>1.2: Leading whitespace isn’t stripped anymore (indents as well as newlines), when there’s no title the title-div is not being generated anymore</li>
<li>1.1: Solved the issue with single-quotes being changed to typographical quotes</li>
</ul>
<h4>Known Issues</h4>
<p>While the plugin is basically XHTML 1.0 Strict compliant there’s just no way of getting the offset-based line-numbering to display without inadequate (ab)use of javascript and css hacks, so be warned that <em>IF you use the line-number offset, your documents will <strong>NOT</strong> validate</em> because of the forbidden <code>start=</code>-attribute for the <code><ol></code>!</p>
<h3>Documentation</h3>
<p>More on the <a href="http://blog.kno.at/tools/highlight-source-pro/" rel="nofollow ugc">Highlight Source Pro Page</a></p>


Highlight Source Pro

Powerful, XHTML-compliant, server-side code highlighting for pretty much all languages

wp-jsonld vs Highlight Source Pro