Yoast SEO 13.1: Schema.org structured data enhancements

Yoast SEO 13.1 and WooCommerce SEO 12.6 are out today! In these two updated SEO plugins, you’ll find several fixes and enhancements, mostly focused at improving our Schema.org structured data implementation. In this post, you can learn more about the latest versions of Yoast SEO and WooCommerce SEO.

Yoast SEO 13.1

Back in Yoast SEO 11.0, we launched an innovative and expansive Schema.org implementation for Yoast SEO. For the first time ever, we can build a complete graph for a site and present it to a search engine on a silver platter. In subsequent releases, we fine-tuned the structured data implementation and we are continuously making improvements. You can find more technical detail on our implementation on Schema.org markup documentation.

In Yoast SEO 13.1, we’ve fixed a number of bugs and added a couple of enhancements in our Schema.org implementation. For one, we now set the Schema HowTo name and Article headline to the post title with a fallback to “No title”. In addition, we’ve added the inLanguage property to the Schema CreativeWork pieces. We try to determine the language of a specific piece of content in various ways, including the WordPress site language settings. This paves the way to handle a form of internationalization using Schema.org structured data.

WooCommerce SEO 12.6

Today, we’re also releasing WooCommerce SEO 12.6. This time, we’ve fixed a number of bugs and enhanced the Schema.org implementation. In WooCommerce SEO 12.5, we added the possibility to add a product identifier to your product, which makes it possible to output that number in the product Schema.org. In the 12.6 release, we’ve added some explanatory copy above the input fields for GTIN, ISBN et cetera to make this feature a little clearer.

At the end of this week, we’ll be raising the price of the Yoast WooCommerce SEO plugin. Are you serious about selling online? Get it today for only $49! That’ll save you some serious $$$. Don’t miss this chance…

Another enhancement to the structured data powers is the possibility to choose if you want to display the price in Schema.org structured data and OpenGraph with tax included. Simply check the box for the setting and you’re good to go.

WooCommerce SEO now lets you choose between tax or no tax for output in structured data

For bug fixes, we fixed a bug where the internal linking and additional keyphrase functionality went missing from the product edit page. Also, we fixed a bug where the meta description and Twitter and Facebook description could still contain HTML tags and redundant spaces.

Update your plugins

That’s it for today’s releases! We’ve enhanced both Yoast SEO and WooCommerce SEO, while also fixing a number of bugs. Please review the changes and update the plugins at your convenience. Thanks for using Yoast SEO!

Even better SEO with Yoast SEO Premium!

  • Optimize your site for the right keywords for your users
  • Avoid dead links in your site
  • Get previews for sharing on Twitter and Facebook
  • Content quality and link suggestions as you write
More info

5 Responses to Yoast SEO 13.1: Schema.org structured data enhancements

  1. Nate
    Nate  • 1 month ago

    Is this update removing meta descriptions? Seems very buggy

  2. mayaREguru
    mayaREguru  • 1 month ago

    I can’t even get the “advanced” tab to extend to put any information into Yoast. The same for the other tabs. Looking into reverting to 13.0. Also had a very weird config error come up on Monday that took our PHP down.

  3. Elton Daniel Oliv
    Elton Daniel Oliv  • 1 month ago

    Mine is giving error!

    I get the critical error message as soon as I updated

  4. Tony Hisir
    Tony Hisir  • 2 months ago

    Thank you for the update for both Yoast SEO Premium and WooCommerce SEO. It is the best SO plugins yet you are still working on them to make them better. I appreciate it.

  5. Robert N. Bryant
    Robert N. Bryant  • 2 months ago

    The keywords and links aren’t recognized in the structured data. For example Yoast gives you an error and says your focus keyphrase is not in the first paragraph of your article when it is…