Yoast SEO 12.7: Cleaning up and fixing bugs + sale!

Yoast SEO 12.7 is out today — signaling the last release of 2019. This release is all about cleaning up and fixing bugs. Since we have a two-week release schedule, we can quickly respond to any bug we might find. In this post, you’ll find out more about this release. Plus, you can get Yoast SEO Premium for cheap in our Holiday Calendar sale: today only!

On the importance of bug fixing

We’ve always prided ourselves in releasing a product of high quality. Unfortunately, issues do pop up and we do our best to solve these depending on the severity of the issue. This is one of the reasons we have a two-week release schedule. For some, it might feel we release way too often, but for us, this is a great way to get fixes out as quickly as possible, without having to resort to patch releases. Having a good system in place for handling and resolving bugs is one of the pillars of coding awesome, stable software.

Every release, we fix a number of bugs from our backlog, plus a selection of new ones that need attention. In Yoast SEO 12.7, we also fixed a couple of bugs with the input of Saša Todorović. These concerned a bug where sub-sitemaps were rendered for non-public custom post types, plus a bug where nested gallery images were not included in the image count in the sitemap. In addition to the bug fixes, we improved the security of the plugin by adding output escaping.

Save 25% on Yoast SEO Premium: today only!

This holiday season, we’re counting down with an awesome holiday calendar. Each day, you get a nice surprise — ranging from free webinars to discount on Yoast products. December 10 — which is today! —, you’ll get a whopping 25% discount on Yoast SEO Premium. Now is the time to get acquainted with features that’ll help save time and improve your work, such as:

Of course, with Yoast SEO Premium you’ll also get access to our awesome support team.

Check out our holiday calendar! We have awesome treats for you

Update now to Yoast SEO 12.7

That’s it for this release of Yoast SEO. We’ve fixed a number of bugs and cleaned up the code to make Yoast SEO perform even better. Don’t forget to take advantage of today’s discount on Yoast SEO Premium! It’ll surely help you kick-start your new year! 

The post Yoast SEO 12.7: Cleaning up and fixing bugs + sale! appeared first on Yoast.

Yoast SEO 12.6: Getting help in the plugin is now easier

In Yoast SEO 12.6, we’re activating our new beacon for help documentation. This tool helps answer the questions you might have about using Yoast SEO. It’s easy to use and very friendly. Just hit that big purple question mark and search! Other improvements in Yoast SEO 12.6 includes a number of fixes and enhancements. Read on to find out more.

New way of helping you 

Our previous help center was not always as apt to provide the best answers to your questions. In Yoast SEO 12.6, we’ve removed the old help center and in its place added a beacon powered by HelpScout. This beacon — you’ll notice the big purple question mark in the lower right-hand corner —, is quick, smart and very helpful.

The new beacon allows us to present not only helpful articles for our knowledge base, but also from our SEO blog, for instance. This lets you not only access a ton of information about what you are working on, but also provides you with enough context to explain why you are doing this — or why the plugin does what it does.

So if you search for something in the new beacon, you’re searching all the content we have. Hopefully, the results will be satisfactory! In addition, Yoast SEO Premium subscribers can contact our support team from the beacon. Please let us know what you think. The beacon is now available in all our plugins.

Fixes and enhancements

Today, we’re updating all our SEO plugins. For Yoast SEO, we’re continuing our work on several larger projects and focussing on behind-the-scenes improvements in 12.6. In addition, we’ve fixed several bugs and added a couple of enhancements, like the aforementioned help beacon. 

Other notable changes are the new description property we’ve added to the schema’s WebSite node. This means your site’s tagline can now be part of your site’s graph, giving search engines extra context about it. We’ve improved the Meta Robots Advanced field in the advanced section of the metabox by simplifying the options and wording around that feature.

Chris Thompson helped us fix a PHP Warning that pops up when using an empty string in the OpenGraph frontend output. We’ve also upped some of our requirements. We’ve set the minimum required WordPress version to 5.2, and the minimum PHP version to 5.6.20. Last but not least, we now show a notification to encourage Internet Explorer 11 users to use another browser as we are no longer supporting that browser.

Yoast SEO 12.6: update now

That’s Yoast SEO 12.6 in a nutshell. We’ve ironed out some kinks and introduced a massively enhanced help center based on beacons. Please update to the latest version whenever you’re ready!

The post Yoast SEO 12.6: Getting help in the plugin is now easier appeared first on Yoast.

Search Console showing errors in your product structured data?

Google’s recent run of enhancement reports in Search Console gives you lots of insights into how your site is performing in search. Sometimes, though, it gives you stuff to think about, like errors or improvements to make. For instance, if you run an online store, you’re bound to have come across this structured data error: “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified.” There’s a very easy solution for this if you run WooCommerce and Yoast SEO: our WooCommerce SEO add-on.

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error in Google Search Console 

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” happens for a lot of online stores. It means that Google misses several properties in your product schema implementation. By not offering these, your product listings will not reach their full potential in search. This way, Google has a hard time tying all the product-specific properties together to paint a full picture of your product. In some cases, though, they manage, but why let them figure it out? Fixing this becomes imperative if you want a better chance of standing out. 

Who doesn’t want a product listing like the one pictured below?

Valid product schema might lead to eye-popping rich results like this one from Reverb

Oftentimes, however, invalid or incomplete structured data might cripple your perfomance in search. Errors are all too common, like the one in the screenshot from Search Console below.

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error is very common

Help is at hand: Yoast SEO & WooCommerce SEO

WooCommerce is huge in the WordPress world. According to W3Techs, 15% of all WordPress sites run an online shop on the WooCommerce platform. That’s amazing. We have a plugin that helps customers improve their online store: WooCommerce SEO. This addon ties neatly into Yoast SEO, including the big schema graph we build for every site. It also greatly improves the product schema output by WooCommerce. 

If your site runs on WooCommerce and Yoast SEO you need WooCommerce SEO. Besides all the cool behind-the-scenes improvements, it fixes that dreaded “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error for you: automatically! It gives Google everything it needs to figure out your products are products and thus increases your chances of getting those important rich results.

Why you should fix this error

Google is increasingly betting on schema structured data to help understand the world. If your site offers search engines enough context about what’s on it, the rewards could be great: rich results. And for some types, visibility on other devices like smart speakers or visual assistants.

Getting your product schema right, means you can get these types of results. The one earlier in this article is from Reverb and shows a nicely formed product rich results, with breadcrumbs, product information, ratings and reviews, pricing details and an in-stock message. This is all powered by product schema. 

Reporting on the performance of products 

To help you track how your products are doing, Google recently added a Product enhancement report to Search Console. This report lets you know if your products are correctly structured and, therefore, eligible for rich results. This week, Google also announced that it will allow you to see the performance of your product in the search results. You can now find a new Product line in the Search Appearance section of the Search Performance section. 

Search Console now has a product results view in Search Appearance

This report shows exactly how well your products are doing: how many impressions did they have and how many clicks? This is invaluable data to improve your product listings. 

Fix the error and check your listings

Seeing the product schema error in Search Console? Using Yoast SEO and WooCommerce? Well, you’re in luck. The WooCommerce SEO add-on is the glue that ties the product schema structured data between those two platforms together. It fixes that dreaded error and gives you a better chance at getting your products noticed in Google!

The post Search Console showing errors in your product structured data? appeared first on Yoast.

Yoast SEO 12.5.1: Patch release for time-offset issue

Today, we’re releasing Yoast SEO 12.5.1. It contains a patch to make sure the publication date of your posts is picked up correctly by Google, so the right time will be shown in the search results. Currently, the time shown in the results might differ from the actual publication time, depending on the time zone you’re in. This patch release is mostly important for news sites, as on these sites the exact timing of the article matters the most.

What’s the issue?

If you’ve updated to WordPress 5.3 and published a number of new posts, you might have seen an incorrect publication time of your article in the search results. This issue is caused by a faulty time offset, which might be originating from Yoast SEO (Premium) and/or WordPress 5.3.

A lot of work went into WordPress 5.3 to update the way it handles dates and times. Unfortunately, this change was not without issue. Both Yoast SEO 12.5 as well as WordPress 5.3 have a bug which leads to outputting a slightly offset publishing time.

The WordPress issue will be fixed in WordPress 5.3.1. We thought it best to push out an update for our plugins as soon as possible. So if you update to Yoast SEO 12.5.1 the issue will be fixed, even if you’re still on WordPress 5.3. Our News SEO plugin already had everything in order, so this was unaffected by this issue.

For which kind of sites is this patch release important?

The exact publication time of an article isn’t crucial for most sites. If your site is a news site though, bringing the latest news on hot topics, you probably want to show in the search results that your article is the most recent article on that topic. If this applies to your site, we’d recommend updating it to Yoast SEO (Premium) 12.5.1. If you have another type of site, feel free to update as well, as it’s always best to have the latest version of our software running on your site. 


If you have a news site we recommend to update to Yoast SEO 12.5.1.

The post Yoast SEO 12.5.1: Patch release for time-offset issue appeared first on Yoast.

Yoast SEO 12.5: Behind the scenes improvements

These last couple of months here at Yoast SEO HQ have all been about building better things. Behind the scenes, we’re making good progress at getting our flagship plugins ready for the future. While we’re busy building the future, we also stick to our regular two-week release schedule, which means it’s time to introduce Yoast SEO 12.5.

Fixing bugs and behind the scenes scaffolding

Yoast SEO 12.5 is one where most of the work went on behind the scenes. We’re working on improving our codebase and will be releasing something cool pretty soon. To get that done, we need to do some cleaning up. 

Besides getting ready for future releases, we’ve fixed a number of bugs. One of those bugs happened for terms where keywords and snippet preview data would be synced across all languages in a MultilingualPress multisite environment. Another bug misplaced visually hidden text in several elements inside the Snippet Preview. We’ve also deprecated the old Search Console integration as that won’t be returning in that same shape or form.

A reminder about support for older versions of WordPress 

With yesterday’s release of WordPress 5.3, we will return to our initial position of only supporting the latest two versions of WordPress. In this case, that’s WordPress 5.2 and WordPress 5.3, and not versions before that. This means we’ll end our support for WordPress 4.9, which we’ve supported longer than usual to allow people to transition to WordPress 5.0 and ease over people to the classic editor or block editor. Luckily, the vast majority of you have probably updated to the latest versions.

In WordPress 5.2, the core team upped the minimum PHP requirements from an ancient 5.2 to the slightly less ancient 5.6. By supporting the last two versions of WordPress, we can now develop our software using PHP 5.6. This means that we can develop faster and more securely. Read Joost’s post on supporting older versions of WordPress.

Update now to Yoast SEO 12.5

Yoast SEO 12.5 is a fairly basic release with lots of stuff going on in the background. We’ve fixed a number bugs and helped Yoast SEO get ready for future improvements.

The post Yoast SEO 12.5: Behind the scenes improvements appeared first on Yoast.

Yoast SEO 12.4: Image in snippet preview

After releasing several updates to our snippet preview in previous releases, Yoast SEO 12.4 now shows an image for your post in the mobile snippet preview, just like Google would. We have several other improvements and fixes for you in store with Yoast SEO 12.4. Find out more!

Featured image in the mobile snippet preview

Not too long ago, Google made several changes in the way they present results on mobile. To mimic that, we started updating our snippet preview. In the latest iteration, we see a favicon (added in Yoast SEO 11.5, enhanced in 12.1) and new font sizes (added in 12.1).

The one thing missing from the current snippet preview in Yoast SEO is that of an image. For some search results on mobile, Google will now show the main image next to it. In Yoast SEO 12.4, we automatically use your featured image to mimic the way Google does this now. We’ll use the first image in your content if you haven’t set a featured image. Remember, this only works in the mobile snippet preview.

The mobile snippet preview now uses the featured image

Schema structured data content blocks

Our Schema structured data content blocks for the block editor have proven to be a valid way to quickly get rich results for these types of content. The two current content blocks, namely FAQ and HowTo blocks, are incredibly easy to add, update and publish. They give you valid structured data for that content and thus a great chance of getting rich results. Be sure to try them out! In Yoast SEO 12.4, we’ve improved the findability of the blocks in the block editor library to help even more people find and use them.

Find the Yoast SEO structured data content blocks in the WordPress library

Fixes and enhancements

For this release, we had several users contributions. Emily Leffler Schulman suggested to change the readability score for empty content from “Needs Improvement” with a red icon to “Not Available” with a gray icon. This makes it less confronting for users. Emily also updated the URLs used to ping Google and Bing about the location of a sitemap. Steven Franks added information to the Twitter settings to make it more clear why you should enable Open Graph. Thanks both!

We also fixed a number of bugs in this release. One of these bugs made it impossible to set Twitter and Facebook images for attachment pages. Another bug concerned the visibility of a nested paragraph in the “noindex” metabox warning. Plus, we clear up the last of the Google+ data, there was still some leftovers in the settings export.

Update to Yoast SEO 12.4

That’s Yoast SEO 12.4 for you! We’ve updated the mobile snippet preview with the latest changes by Google and we fixed several bugs. A number enhancements makes Yoast SEO a little bit easier to use. Update to the latest version at your convenience!

The post Yoast SEO 12.4: Image in snippet preview appeared first on Yoast.

Yoast SEO 12.3: Transition words in Hungarian

While some of our checks are independent of languages, Yoast SEO has special skills to adapt the various content analyses to different languages from around the world. In Yoast SEO 12.3, we’re taking the first steps to add another language to the list: Hungarian. In addition, this release features a number of enhancement and fixes. Read on to find out more!

Yoast SEO is learning a new language: Hungarian

Every time we plan on adding a language, we need to see how and what we need to do to get it to work in the plugin. Not every language follows the same rules, so we do research and test how to best go about adding a new one. We have a team of linguists, assistants and developers doing the hard work. Their team lead, Manuel Augustin, recently wrote a post describing how we make Yoast SEO understand your language.

That’s not to say we do everything by ourselves. We truly value community input and we need it if we want to reach our goals. In this release, you’ll see one of those community efforts. Thanks to the hard work of 9abor, we can now say our first words in Hungarian! We start off by adding support for the transition word assessment for this language. More to come.

On our knowledge base, you can find the complete list of all available languages and a guide on how you can make Yoast SEO available in your language.

Other fixes and improvements

Yoast SEO 12.3 features a number of fixes and enhancements. In Yoast SEO Premium, we fixed a bug that prevented you from interrupting the internal linking tool during updating. We’ve improved user input validation feedback and suggestions for error correction.

Plus, we’ve added a new floating Save changes button on Yoast SEO admin pages. You’ll this when the normal button isn’t visible in the browser window. We’ve added a new filter called wpseo_sitemap_http_headers which allows filtering the HTTP headers we send for XML sitemaps. Last but not least, Weston Ruter added a code change to add the CSS for the Yoast SEO admin bar to the AMP dev mode. This makes sure that the CSS will always load properly, even if there is a lot of CSS on a page.

Update now to Yoast SEO 12.3

Yoast SEO 12.3 is out today and brings a number of improvements. We’ve started to add support for a new language, namely Hungarian. In addition, we’ve improved input validation and added some changes that will help the admin bar load at all times. Hope you enjoy this release!

The post Yoast SEO 12.3: Transition words in Hungarian appeared first on Yoast.

How we make Yoast SEO understand your language

One of the key features of Yoast SEO is the content analysis. The analysis consists of multiple checks that give you SEO and readability feedback on the texts you write on your website. Some of these checks are language-independent. For these, we don’t need to create specific versions for, say, French and English. For others, it is necessary to adapt them for each language. In this article, I’ll explain our research and development process for the expansion of Yoast SEO checks for different languages. You’ll also learn how you can contribute to help Yoast SEO understand your language!

Foundations of our analysis

In principle, all of our checks are rule-driven. They consist of analyses that run in the browser. This has the advantage that all user data stays in your local environment and is processed there. There’s no need to upload anything to an external server.

The challenging part of this approach is that we can only operate based on predefined rules. Since we don’t know exactly what texts these rules operate on, we need to make sure to define the rules in advance in such a way to cover all necessary cases.

When adapting an analysis to a new language, we not only need to review linguistic and stylistic rules for that language but also translate them into new text processing rules. This might sound very abstract at the moment, but I’ll provide a concrete example below!

Developing a check for Yoast SEO

Let’s start with an outline of the kind of research that is needed to create a check in the first place. When reading the following example, don’t worry if you don’t get all the linguistic lingo right away! This is just an example to illustrate the formation of rules. I’ll explain all the terms you need to know.

Example: passive voice

Let’s take passive voice as an example. In our analysis, we check whether you have too many sentences that contain passive voice. It’s not necessary to know exactly what passive voice is at this point – I explain the necessary points below. However, if you want to know all the ins and outs you can read this article on how to recognize passive voice and why we advise you to avoid it.

Imagine that we’re tasked with creating this check from scratch. We want to give a clear recommendation on a text that someone just wrote. To give such a recommendation, the most important point is to figure out which sentences contain passive voice, and which don’t. As a little sneak peek, here’s an example of a passive sentence.

The cake was eaten by the child.

No idea yet what makes this sentence a passive sentence? Or maybe you do know what makes this particular sentence passive, but can you give a full definition of passive sentences in English? Let’s dive into the issue to discover all the rules and exceptions!

Discover the rules

How do we know that the sentence above is passive? And how can we teach our analysis to recognize this, too? To answer the first question, language research comes into play. Going through some dusty old grammar books (or the digital equivalent of it), we can establish the following rule: a passive sentence in English is formed by an auxiliary verb and a past participle. In addition, we learn that the auxiliary always comes before the participle. Well, that’s great for a start! But now you might ask yourself: what’s an auxiliary verb? And what the heck is a past participle? Good questions! Since it’s not really obvious for a human, you can be sure that software doesn’t know, either. But that’s okay since we’ll teach it how to recognize them.

Translating the rules into logic and data

Now that we’ve discovered some grammatical rules, we want to know how we can translate them into logic that our text analysis can operate on. So we do some more research and figure out that an auxiliary verb used for passive voice is basically any form of the verb to be (was, is, been, etc.). Fortunately for us, that’s a pretty short list. For participles, that looks a bit different. A past participle is a verb form such as loved in has been loved and created in has been created. Basically, any verb can be made into a participle. In this case, a word list isn’t really feasible. It’s better to formulate a more general rule. In its most simple form, the rule could be “find a word that ends in -ed”. Such a rule can be translated into a pattern that we can match with a regex for example. Done! Right? Well, almost…

False negatives, false positives, and how to avoid them

The general rule we’ve established for discovering participles will cover lots of cases, such as cooked, talked, or invented. It won’t be quite sufficient, however. With only this rule in place, you’d get both false positives and false negatives.

False positives arise when your rule matches things it’s not supposed to match. Our word ending in -ed rule would also result in words such as bed being matched. This isn’t actually a past participle. In fact, it’s not even a verb. So we need to filter out exceptions to the rule. We can do this by creating a list of words ending in -ed that aren’t past participles.

False negatives, on the other hand, emerge when our rule fails to match things that we want to match. Consider irregular past participles such as written, seen, or heard. These don’t end in -ed, so they wouldn’t be found with our rule. Again, we need a word list to make sure to also pick up those participles.

Rules: check. Exceptions: check.

So now we already have one general rule, plus two exceptions. And this example is still an oversimplification. In our actual implementation of this check, there are even more factors that we take into account when determining whether a sentence contains passive voice.

You see that for one check in the analysis, there’s a lot of preceding research that needs to happen before we can start implementing the check in our software. And then that’s only for one language. There’s still all other languages for which we also want to be able to carry out this analysis.

Teaching Yoast SEO to understand more languages

When adapting a check for a new language, we might be faced with one of two situations:

  1. Only new data (usually word lists) need to be supplied to the existing logic.
  2. Both new data and new logic are needed.

In the first scenario, expanding a check to a new language might be done after a day or two of research. In the second scenario, it can require just as much time as implementing the check in the first place. The problem is that languages can differ not only in the words they use to express a certain concept – such as passive voice – but also the grammatical constructions they use for it. I’ll provide examples for both scenarios below.

Adapting only data

Fortunately, not all assessments need completely new logic when adapting them to a new language. Whenever possible, we set them up to make them as much “plug and play” as possible. An example of an assessment that is relatively easy to adapt to a new language is the transition word assessment. This assessment checks whether a transition word or group of words (e.g., words such as however, to summarize) from a specific list are present in that sentence. This mechanism is basically the same across languages. To make it work, we just need to supply a list of transition words for a given language, and voilà, it works.

Adapting both logic and data

Going back to the passive voice analysis, we see that adapting this check to a new language gets a bit more complicated. Here, we’d need to change quite a bit of logic depending on the language analyzed. In Dutch, for example, you still use auxiliary verbs and participles to express passive voice, but, unlike English, the auxiliary can also come after the participle. In Russian, you can spot passive voice relatively accurately by virtue of the form of the verb alone. So it’s not necessary to look at auxiliaries. So for all these languages, not only do you need different data, but you need different logic to carry out the analyses. This means that you need both, additional research and technical implementation. Just supplying new language data won’t suffice here. You also need to adapt the string processing rules that operate on this data.

Do you want Yoast SEO to speak your language?

There are a number of ways to help us expand Yoast SEO functionality for your language! As you saw in the explanation above, some checks can be expanded relatively easily by adding the necessary language data. If you speak a language other than English, you can send in language data using one of our forms. We’ll then review this data and, if possible, implement it. This means that with your help, we can add language-specific Yoast features for your language!

If you’re a developer, you can also directly contribute to our codebase. You can find more detailed instructions in our article on making features available for your language. We’re looking forward to your contribution!

Read more: How to use the content analysis in Yoast SEO »

The post How we make Yoast SEO understand your language appeared first on Yoast.

Yoast SEO 12.2: Fixes, improvements and more

Yoast SEO 12.2 is a release full of the regular bug fixes and enhancements, but also a new addition to meta robots. Last week, Google announced a new way to give publishers more control over what the search engine can show in the results. This change, however, seems not driven by customer demand, but rather by law. Find out what this is all about and why we chose to automatically opt sites in for this.

Adding a line in meta robots

Google is turning to the meta robots tag to comply with a new European copyright law. Previously, publishers had to explicitly opt out if they wanted to prevent Google from using their content to present it in search results. Thanks to the new European copyright law, we see Google asking sites to opt in if they want it to use their content, images and videos in snippets. France is the first to roll out its version of this copyright law, starting today.

“When the French law comes into force, we will not show preview content in France for a European news publication unless the publisher has taken steps to tell us that’s what they want.” — Google’s Richard Gingras on the French Google blog.

While it currently “only” impacts several hundred publishers in France, it’s not hard to predict that more countries might roll out similar laws and implementations. This may even reach beyond just news sites in Google News. As this development potentially affects many countries, we’ve decided to make a change for all Yoast SEO users.

We will add the following line to the robots meta tag on every page unless that page was already set to noindex or nosnippet:

max-snippet:-1, max-image-preview:large, max-video-preview:-1

By adding this piece of code, we make sure that every site using Yoast SEO is automatically opting in for this change. Now, you’ll be ready for the implementation of this law in Europe and your content will continue to appear in Google search results.

Read Joost’s post on what this change means for Google, for us and the web.

Enhancements and fixes: plus, free courses!

There’s more of course, with the majority being bug fixes. We’ve updated the configuration wizard that helps you set up Yoast SEO. We’ve combined some steps and added a reminder to take our free Yoast SEO for WordPress plugin training.

Did you say free? Yes, I did! Everyone can now learn everything there is to learn about the #1 WordPress SEO plugin by the people who built it. There’s lots to discover, but it’s all very easy to learn. Go try it! While you’re in the Yoast SEO Academy, you might as well check out our other brand-new, free course: WordPress for beginners.

Find out all the changes in the changelog for Yoast SEO 12.2.

Update to Yoast SEO 12.2

This release focuses mainly on fixing bugs, but also introduces a new meta robots tag. This tag automatically opts in sites for Google to continue to use their content like text, images and videos in the snippets. It is a change driven by a new European copyright law that goes into effect in France first, with many countries expected to follow in the near future.

The post Yoast SEO 12.2: Fixes, improvements and more appeared first on Yoast.

Robots meta changes for Google

Sometimes Google does announcements about new features and we go “huh, why did they do that?” This week we had one of those. Google introduced a new set of robots meta controls, that allows sites to limit the display of their snippets in the search results. There is a reason for that, but they buried that reason far, far away.

With their newly introduced robots meta controls, you can “say” things like: I don’t want you to show more than 200 characters from my site! Or: I don’t want you to show images from my site. None of this made sense to us. Why would anyone who truly wants to optimize for Google’s search results, do any of that?

A French copyright law

Suddenly, we make a dramatic plot twist: France turns out to have introduced a new copyright law, which is the first implementation of Europe’s new copyright law. I am not a lawyer, but as Google explains it in this blog post, it requires for publishers to opt in to a display of their snippets, whereas in the past you had to opt out. Note that that blog post is in French, on their French blog, but there’s an English version in the bottom of that post.

It turns out that you can also use these new robots meta features to opt in to all those displays. Basically, use the meta robots to opt in to have your snippet text, videos and images being displayed at all.

robots meta?

Robots meta is hard enough as it is, read our ultimate guide to understand what you can do with it.

Because this French law implements the new European law, chances are that the other implementations of this copyright law across Europe are going to require similar action. This would mean more countries would need to opt in if they don’t want to loose their snippets. We don’t know that, of course, but of course: better safe than sorry.

A simple change to Yoast SEO

Because this potentially affects so many countries, we’ve decided to make a change for all Yoast SEO users. Every page will have the following robots meta bit added to its robots meta string if that page was not already set to noindex or nosnippet:

max-snippet:-1, max-image-preview:large, max-video-preview:-1

This makes sure that nobody runs into unexpected surprises and we’re ready for implementations of this law around Europe.

I want to change that robots meta value

If you want to change that robots meta value, we have a filter in our code that allows you to programmatically change that. That filter is called wpseo_robots, should you want to play with it.

You are opting in by using Yoast SEO

We realize that this means that we’re opting you in to all of these snippet features in Yoast SEO. I think it’s fair to say that if you use Yoast SEO to optimize your search results, we can assume that that’s what you want. At the same time, you might want somewhat more granular control over these values, if that’s true, please let us know in the comments!

The Yoast SEO release containing this change will be 12.2. This will be released next Tuesday, October 1.

The post Robots meta changes for Google appeared first on Yoast.