New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Automatically generate Schema.org JSON-LD markup for WordPress content. | You have to log in to add a translation. | Details |
Original untranslated
Automatically generate Schema.org JSON-LD markup for WordPress content.
You have to log in to edit this translation. |
|||
| ↑ | Schemify | You have to log in to add a translation. | Details |
Original untranslated |
|||
| After uploading Schemify to your WordPress instance, activate it via the Plugins screen in wp-admin. | You have to log in to add a translation. | Details | |
Original untranslated
After uploading Schemify to your WordPress instance, activate it via the Plugins screen in wp-admin.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| <strong>Schemify aims to automate the generation of JSON-LD objects for content within WordPress.</strong> Its flexible structure and reasonable defaults enables drop-in support for structured data, regardless of the WordPress theme. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Schemify aims to automate the generation of JSON-LD objects for content within WordPress.</strong> Its flexible structure and reasonable defaults enables drop-in support for structured data, regardless of the WordPress theme.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The best part? There's no need to change the markup within our theme! | You have to log in to add a translation. | Details | |
Original untranslated
The best part? There's no need to change the markup within our theme!
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Fortunately, the other approach for adding structured data is much more straight-forward in a theme, as it's simply a JSON-LD object: | You have to log in to add a translation. | Details | |
Original untranslated
Fortunately, the other approach for adding structured data is much more straight-forward in a theme, as it's simply a JSON-LD object:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| While that may not <em>seem</em> 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/"><code>get_avatar()</code></a>, which means extra work to get the necessary <code>itemprop</code> attribute in place. | You have to log in to add a translation. | Details | |
Original untranslated
While that may not <em>seem</em> 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/"><code>get_avatar()</code></a>, which means extra work to get the necessary <code>itemprop</code> attribute in place.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| If I wanted this information to use Schema.org markup, it would look something like this: | You have to log in to add a translation. | Details | |
Original untranslated
If I wanted this information to use Schema.org markup, it would look something like this:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Consider the following author information, which might appear at the bottom of a blog post: | You have to log in to add a translation. | Details | |
Original untranslated
Consider the following author information, which might appear at the bottom of a blog post:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| There are two approaches to adding structured data to a website: via the markup or <a href="http://json-ld.org/">JSON for Linking Data (JSON-LD)</a>. | You have to log in to add a translation. | Details | |
Original untranslated
There are two approaches to adding structured data to a website: via the markup or <a href="http://json-ld.org/">JSON for Linking Data (JSON-LD)</a>.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Or, at least it would be, if it weren't for Schemify. | You have to log in to add a translation. | Details | |
Original untranslated
Or, at least it would be, if it weren't for Schemify.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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">WordPress</a>, for instance, <a href="https://ma.tt/2015/11/seventy-five-to-go/">powers roughly a quarter of the web</a>, but implementing structured data across hundreds of thousands of themes would be a nightmare. | You have to log in to add a translation. | Details | |
Original untranslated
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">WordPress</a>, for instance, <a href="https://ma.tt/2015/11/seventy-five-to-go/">powers roughly a quarter of the web</a>, but implementing structured data across hundreds of thousands of themes would be a nightmare.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| With the major search engines and communities behind it, we're all marking up everything with appropriate structured data now, right? | You have to log in to add a translation. | Details | |
Original untranslated
With the major search engines and communities behind it, we're all marking up everything with appropriate structured data now, right?
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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">Schema.org</a>, a collaborative, community-driven standard for structured data. | You have to log in to add a translation. | Details | |
Original untranslated
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">Schema.org</a>, a collaborative, community-driven standard for structured data.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.