How to Fix the 『Missing required hCard / hEntry』 error

How to Fix the 『Missing required hCard / hEntry』 error

Are you getting the Missing required hCard 「author」 or similar hEntry / microformat error in Google』s structured data testing tool (live results) or in Google Search Console (cached results)? This is an issue with your theme, not with any of our plugins.

Warning: Updating your theme may remove the changes you have made to core theme files. For that reason, we recommend contacting your theme developer to request a permanent fix to this issue.

Missing: author

To temporarily fix this issue for the author tag, please follow these steps:

Locate the call to the_author(); in your theme』s single.php file, it might look something like this:

Change it so that it has a class vcard author and within that another element with a class fn. The example above would become something like this:

As you can see this adds quite a bit of markup, but it would prevent that error from showing. If you are unable to locate or have trouble with this code, please contact your theme developer for assistance.

Missing: updated / entry-title / other

The requested tag is not present in your theme or is incomplete. Please contact your theme developer for assistance.

Can I Turn Off hEntry In My Theme?

In some cases, you may simply want to remove hEntry completely until your theme is updated. By adding this code to your theme』s functions.php file you will remove hEntry from being inserted into your posts. This will remove the structure of hAtom which in turn removes the hEntry data.

Shortcodes not rendering

Shortcodes not rendering

If you have shortcodes in your content that are not rendering, you could see, for instance, something like this:

[wpseo_map id="all" width="400" height="300" zoom="-1" map_style="roadmap" show_route="0" show_state="0"]

This can be caused by two things:

The plugin providing the shortcode is not active. The shortcode then won』t work.Your theme is outputting the post content without applying the needed filters on it.

Fixing your theme

If you install the What the file plugin, you can see which file in your theme is being used to render the page that has the issue. You should then open that file and see what』s there. Usually you』ll find it has something like this:

echo $post->post_content;

If that』s the case, try making it so that it properly uses the WordPress loop and the function the_content(); to output the content. If you really can』t do that, you can change the code to:

echo apply_filters( 'the_content', $post->post_content );

This would not be our preferred option though, as that』s bound to have other issues as well…

How to get Pinterest Rich Pins for your site

How to get Pinterest Rich Pins for your site

Pinterest Rich Pins show more information directly on a pin, like the price and availability of a product, the ingredients and cooking time of a recipe, and the headline and author of an article. In this article, we』ll show you how to get Pinterest Rich Pins for your site through the Yoast SEO plugin.

Table of contents

Confirm your site in PinterestHow to get Rich Pins for your siteRich Pins for my homepageAdditional information

Confirm your site in Pinterest

Before you do anything else, please make sure you have confirmed your site on Pinterest. Log in to your WordPress Dashboard, go to the Yoast SEO menu item, and click 『Social』. Then, go to the Pinterest tab of the Social settings. There, you can fill out a confirmation code to confirm your site with Pinterest. Read more about how to get the Pinterest confirmation code here.

How to get Rich Pins for your site

To get Rich Pins for your site, Pinterest must authorize your site for rich pins. Validate and apply for rich pins by following these steps: Enable Open Graph in our plugin. Go to https://developers.pinterest.com/tools/url-debugger/ Enter a URL to a page or post that contains rich pin data. Choose 『HTML tags』 and click 『Apply Now』. The validator will run and you will see a validation confirmation and apply now link. Verify the domain name is correct. Choose HTML Tags and click 「Apply Now」. You will see a confirmation that your application was processed. Pinterest will contact you after reviewing your site.

Hint: If you scroll down, you will see a sample of the information available for Rich Pins.

Rich Pins for my homepage

On your homepage, Yoast will output the following OpenGraph tags: meta property="og:type" content="website". In order to make Pinterest validate Rich Pins for the homepage, you will need to develop the ability to output 「article」 only on the homepage and place it, most likely, in your theme』s functions.php file.

To do this, you need to use the Change Yoast SEO OpenGraph Type code here: Develop Filters to Set Custom OpenGraph Tags. Please know that you may need to develop the ability.

Prior to any changes on your site we recommend making a backup of your site or performing the work first on a staging site. If you need to create a staging site or need to backup your site, we suggest speaking to your host provider for more information. Please also know, that any changes made to your theme may be overridden in the next theme update.

It is highly suggested to use a child theme. If you are not sure how to use a child theme, please speak with your theme developer.

Additional information

Pinterest no longer supports price variations or ranges unless you are using a feed partner like Shopify.WooCommerce SEO supports Price, Availability, and Currency as Pinterest Rich Pins, described in this guide.

How do I prevent sitemaps from being cached?

How do I prevent sitemaps from being cached?

Most cache plugins will, by default, be set up to not cache sitemap files. In the rare case your plugin or server is caching the sitemap,  please add an exclusion for the sitemap files to your cache plugin. The steps vary by cache plugin, so please select your cache plugin below.

When finished, be sure to clear your caching from your plugin, theme, server, browser, or CDN such as Cloudflare. If you are not sure how to clear your server caching, please speak with your host provider. If you need to clear your browser caching, this guide on how to clear your browser』s cache may help.

Table of contents

W3 Total Cache
WP Super Cache
WP Rocket
Another plugin or method
Disable transient caching

W3 Total Cache

By default, W3 Total Cache is setup to not cache the Yoast sitemaps. Enabling some W3 Total Cache features may cause the sitemaps to be cached.

404 errors for static objects

If you』re using the setting 『Do not process 404 errors for static objects with WordPress』, please add the following to the 『404 error exception list』 under Performance > Browser Cache > General (section).

Minify

If you』re using W3 Total Cache to minify your pages, please add the following to the 「Never minify the following pages:」 setting under Performance > Minify > Advanced (section).
sitemap(_index)?.xml(.gz)?[a-z0-9_-]*sitemap[a-z0-9_-]*.(xml|xsl|html)(.gz)?([a-z0-9_-]*)?.xml

WP Super Cache

Go to Settings  > WP Super Cache and click on the Advanced tab.  Scroll down to the section where it says 「Add here strings (not a filename) that forces a page not to be cached」 and add the following:index.phpsitemap(_index)?.xml(.gz)?[a-z0-9_-]*sitemap[a-z0-9_-]*xml|xsl|html)(.gz)?([az0-9_-]*?)sitemap([a-z0-9_-]*)?.xml

WP Rocket

WP Rocket offers sitemap preloading. Learn more here.

To prevent WP Rocket from caching the sitemaps, go to Settings > WP Rocket > Advanced Rules > Never Cache URL(s) and exclude the following:

/(.*)sitemap(.*).xml
/(.*)sitemap.xsl

Other cache plugin or method

If you are using a different plugin or caching is done at the server level then contact the plugin developer or your hosting company for support.

Yoast and your privacy (GDPR)

Yoast and your privacy (GDPR)

As of the 25th of May 2018, EU citizens have more control over what data companies store and process about them due to the GDPR. At Yoast, we have always aimed to store as little personal details as possible. Our plugin itself stores no personal data, only website data. The personal data we might have from you is the data you have provided. In this manner, no DPA or Data Processing Agreement is needed. You can review our DPA Article on how we handle compliance.

All the information you have provided is available for you in MyYoast. Every customer and newsletter subscriber of Yoast has the option to log in and see things like courses you are subscribed to and course progress, plus the option to download purchased products and invoices.
Note that most of this all isn』t personal data. In the Account section in MyYoast, you will also find an overview of the product subscriptions you have, and an overview of your orders. In the Profile > Danger zone section, we have created the option to download a CSV file with details like the address details you have provided us when purchasing products. Furthermore, your newsletter subscription is located in the profile section as well for your convenience.

In case you have any more questions about your personal details or for instance would like to change the email address we use to contact you, feel free to use our contact form to get in touch. We』re happy to help!

What is the GDPR?

The GDPR or European Union』s General Data Protection Regulation is a major change in the way we process personal data, in the sense that we all need to be clear about what data we process and where we process that in what way. Openness about what we do with your personal data. That makes all the sense in the world to us. Here』s Wikipedia『s summary:

The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) is a regulation by which the European Parliament, the Council of the European Union and the European Commission intend to strengthen and unify data protection for all individuals within the European Union (EU). It also addresses the export of personal data outside the EU.

In short, as an individual, you need to be able to get proper insights into what personal data of yours is processed by for instance Yoast, for what purpose and how. And you have the right to have old and irrelevant data deleted (「forgotten」) as well. So if you want your personal data removed from our systems, we must act on that request. This applies to every company that has EU customers or stores any other personal data of EU residents.

Strict take on privacy issues

At Yoast, we take privacy very seriously. Always have, and that is why we store and process as little details as we can to be able to work with/for you. You』ll rarely find us asking excessive details that we really don』t need for that.

As a general rule, do not give us personal data. Not your own, not your customers』 and not your visitors』. (We actually put this in our Terms of service.) This may sound strange but for most things, we just do not need personal data. And under the GDPR, you should not give us personal data if it is not needed. If we do need personal data, we will ask first.

One of the things that we will be more strict on, for instance, is that we won』t accept people』s own personal login details. You』ll be amazed how many people simply send their own login details over email. This isn』t secure in any way, as you will understand.

With the GDPR, we need you to be in the driving seat in these cases. It』s your (customer』s/employee』s) data. You need to be able to control our access to your website, which means you need to create a login for your website especially for us, for the time of the assignment (so just to fix something in support, or for us to be able to configure our plugin). When that assignment is done, we will let you know and we』ll insist that you remove our login details as they are no longer needed. It』s your responsibility to remove these, as that isn』t something we can control. On our side, we will make sure to remove these login details from our records.

This is about personal data, not website data

Please note, that most details we do have access to in our line of work, relate to website data, not personal data. The login details procedure as described in the previous section is especially needed in case of an online shop that stores customer data as well. As we want a solid procedure for this, we apply this procedure to all websites, just to make sure we and you are not overlooking that tiny piece of personal information you stored and made accessible for us by that login.

GDPR targets that personal data. Where it comes to website data: we need that data to further optimize your website. No personal data is needed for that, so please don』t make this data accessible to us. If you really have to, follow the procedure as described. Of course, we will not touch that data in any way that』s not agreed on. For instance, if we need to use the data for testing purposes, we』ll need to agree to this use in writing. And we』ll agree on what happens with that data after testing if needed.

We will respect your rights

You have the right to inspect the data we store. On request, we will give you a complete overview of personal data we have of you, and copies as we have them. If you then see errors in that data, we will happily correct it. (Unpaid invoices do not count as errors. Just kidding.)

As mentioned before, you also have the right to be forgotten. You have the right to have us remove your personal data from our records. We will, of course, act appropriately on your request. But please note that, under the GDPR, we are allowed to keep the data we need to do our work. So if you, for instance, have an active Yoast plugin and want support, we are allowed to store your name, email address and the like for that purpose. The same goes for your invoice: tax regulations require us to store these for at least seven years after your purchase. But that just goes for the invoice data itself. Other data we will delete as soon as we no longer need it.

When the personal data in question is from your employees or customers, then they have these rights and you are responsible for ensuring they can exercise them. Tell us beforehand, so we can conclude a data processing agreement to figure out the best way of working here. Do not send us other people』s personal data without a data processing agreement in place.

Security regulations

The GDPR requires us to take 「adequate」 security measures to protect all personal data we store. All our websites are secured using SSL/https, something we have been recommending for all websites, not just for GDPR but also for SEO reasons. We are monitoring site security and security certificates to make sure your data is as safe and secure as possible.

Needless to say that this page will be adjusted after every step we take in the process of GDPR compliance, for instance, if anything changes in the GDPR rulings. Any questions about the GDPR can be sent to us via our contact page.

How to install Yoast WooCommerce SEO for WordPress

How to install Yoast WooCommerce SEO for WordPress

Thank you for purchasing Yoast WooCommerce SEO. Please make sure you』ve installed Yoast SEO or Yoast SEO Premium already, as it is required for the add-on plugin to work.

Table of Contents

Download the add-on
Download is a folder, not a zip
Install the add-on
Install through Composer

See also:

Connect the subscription
Configure the add-on

Download the add-on

You can download the add-on in the download section of My Yoast. When you click the download button of your add-on in My Yoast, you will either be prompted to select a folder to save the zipped file or your browser will save the zip file automatically to your download folder. You will need to know where the file downloaded during the installation.

You can always visit the download section of My Yoast, should you wish to download the plugin again.

My download is a folder, not a zip file

If you』re downloading one of our plugins and instead of a .zip file you get a folder, your computer is unzipping the archive immediately. The steps to change this behavior depend on the browser you use to download the file. After you change the behavior using the steps here, return to your email and download the plugin again.

Install the add-on

Installing the add-on is a little different than the free plugins because it』s a downloadable plugin and not one found in the free WordPress plugin repository. To install the add-on, go to Plugins → Add New → Upload Plugin to browse for the zipped file and click Install Now. Log in to your WordPress website. When you』re logged in, you will be in your 『Dashboard』. Click on 『Plugins』. On the left-hand side, you will see a menu. In that menu, click on 『Plugins』. Click on 『Add New』. The 『Plugins』 settings will expand providing you additional options. Click on 『Add New』.* If you do not see the 『Add New』 option, your site is part of a network. Please install the plugin through the network admin under 『My Sites』 > 『Network Admin』 Click the 『Upload Plugin』 button near the top of the screen.  Click the 『Choose File』 button. Browse to the folder where you saved the plugin download and select the plugin zip file. Click 『Install Now』. This make take a while so be patient. Click 『Activate Plugin』. If you have a network install, you will see the option to 『Network Activate』. To activate the plugin for all sites within the network, click 『Network Activate』. Otherwise, go to the individual site』s plugin list and click 『Activate Plugin』. Please follow the steps to connect your subscription to the installed and activated add-on on your site.

Install through Composer

Want to install our premium plugins via composer? See this post for more information on how to do that.

How to sign up for the Yoast Translate Slack?

How to sign up for the Yoast Translate Slack?

Yoast Translate Slack is the main communications channel for everything related to Yoast Translate. You can find the validators for your language, ask general and language-specific questions and just chat with like-minded people. All you have to do to be in touch with the community is signing up for Yoast Translate Slack. That』s easy!

There are two steps in creating an account for Yoast Translate Slack.

Creating a chat.wordpress.org email address(you can skip this step if you』re already on the WordPress Slack)Creating your Yoast Translate Slack account

Creating an @chat.wordpress.org email address

Creating your own @chat.wordpress.org email address is quite simple.

Go to https://make.wordpress.org/chat/Scroll down to 『Joining the WordPress team on Slack』 and click the link to Log in (if you aren』t logged in already)Note: If you don』t have a WordPress.org account yet, you canregister for free.Log in on WordPress.orgOnce logged in, you』ll be taken back to https://make.wordpress.org/chat/ where the contents of 『Joining the WordPress team on Slack』 have changed.You are now presented with the 『fine print』. After reading it, just click 『I understand. Please send me an invite.』 to continue.You』re now taken to the confirmation page and will receive your first email on your [email protected] email address.You can now use your [email protected] email address to create a Yoast Translate Slack account.

Creating your Yoast Translate Slack account

Once you have your [email protected] email address signing up for the Yoast Translate Slack is really easy. You』ll be chatting with other translators before know it! Go to https://yoasttranslate.slack.com/signup/ Fill in your wordpress.org username (to complete it to ) Open your email to confirm your email address by clicking the big green button. You can now fill in your username and password and click . Welcome to Yoast Translate Slack!

False positives and negatives in the German passive analysis

False positives and negatives in the German passive analysis

This article gives an overview of the cases in which the Yoast SEO passive voice assessment for German will yield incorrect results. We always strive for results that are as accurate as possible. However, because of the irregularities in human language, it will never be possible to get our analysis 100% right.

Below you find a list of cases in which our analysis will either incorrectly detect passive voice in sentences that aren』t really passive (false positives) or in which it will fail to detect passive voice in sentences that are actually passive (false negatives).

It』s not necessary to know about all of those cases to write a good text. Rather, this overview is intended to give you some clues in case you』re wondering why certain sentences are not correctly detected by the passive voice analysis.

Passive voice in German

To help you understand the false positives and negatives, here is a quick explanation of how the passive voice assessment works. The passive voice assessor in German looks for sentences containing a passive auxiliary and a past participle (a passive verb).

Passive auxiliaries are words such as 『werden』, 『bekommen』 or 『kriegen』 and they function as 『helper words』 to the main passive verb.

Past participles are the main verbs of a passive form. They are verb forms such as 『geschrieben』 or 『verkauft』 that usually start with a prefix like ge-, er- or ver- and and in a suffix like -t or -en.

False positives in Yoast SEO for German

The passive voice assessment of Yoast SEO will incorrectly detect a passive voice in the following cases:

1. When a sentence contains a past participle, as well as the word 『werden』 as a main verb.

The word 『werden』 has two meanings. It can be used as an auxiliary verb when forming passive sentences, such as in the example below.

「In dieser Zeit wurde eine bestimmte Kultur gelebt.」

Or, it can be used as a main verb meaning 『to become』:

「Rund 2.500 Jahre ist es her, dass Siddharta Gautama, der zum Buddha wurde, gelebt hat.」

The passive voice assessor cannot distinguish between the two uses. As a result, it will incorrectly mark a sentence such as the one about Buddha as containing a passive.

2. When a word that can be a passive verb also has additional meanings.

There are several cases when a word that looks exactly like a passive verb can combine with an auxiliary and result in a false positive.

For example, some passive verbs can also function as adjectives, such as the word 『gezielt』 in the following sentence:

「Deswegen bekommen Verkäufer auch regelmäßige Trainings, in denen sie gezielt an der richtigen Attitude arbeiten.」

Some third person singular and Futur I Aktiv Indikativ verbs can also have the same form as passive verbs. Therefore, sentences such as the ones below will also result in false positives:

「Das kann zu einer echten Lawine werden, die uns überrascht.」

「Das werde ich behalten.」

In all of these cases, the passive voice assessor cannot tell the difference between those sentences, and sentences where words like 『überrascht』 are used as passives, such as this one:

「Ich wurde von ihm überrascht.」

3. When a sentence contains both a passive auxiliary and a word that is not a verb but starts with ge-, er-, ver-, ent-, be-, her-, über- or zer-, and ends with -t.

We』ve tried our very best to make sure words such as 『Gefecht』 are not categorized as a passive participle. However, our very extensive list can never cover all exceptions. Please let us know if you』ve found a missing word, and we will gladly add it to our exception list.

4. When a sentence contains both a passive auxiliary as well as a verb ending in -iert that is not a passive verb.

Verbs ending in -iert are often passive verbs, such as in the following example:

「Ich würde gratuliert.」

However, they can also be third person singular verbs in the present tense, such as:

「Wenn Dich dieses Angebot wirklich interessiert, würde ich auf die website gehen.」

As the passive voice assessor treats most verbs ending with -iert as passive verbs, the second type of sentence will result in a false positive.

5. When a passive auxiliary and a participle occur in different clauses which are not separated by a conjunction.

When an auxiliary and a participle occur in different clauses, such as in the example below, they can never form a passive.

「Deswegen bekamen Verkäufer auch regelmäßige Trainings, in denen sie an der richtigen Attitüde gearbeitet haben.」

If the two clauses are separated by a conjunction such as 『aber』, the passive voice assessor will know that the auxiliary and the participle do not belong together.

Example: 「Deswegen bekamen Verkäufer auch regelmäßige Trainings, aber darin haben sie nicht an der richtigen Attitüde gearbeitet.」

However, if there is no conjunction, such as in the first example, the assessor will mistake that sentence for a passive.

False negatives in Yoast SEO for German

1. Passive sentences with a participle starting with ge-, er-, ver-, ent-, be-, her-, über- or zer-, and ending in -st .

To avoid marking many second person present tense verbs as passive participles, we』ve decided to exclude all verbs ending with -st (except for those ending in -sst, e.g. 『abgeblasst』) as a participle. Unfortunately, this means that the few participles that do end in -st and that we haven』t added to the exception list yet, won』t be found.

2. Passive sentence with an irregular participle.

Our list with irregular passive participles includes all irregular participles (not ending in -t) we could find. However, we are quite sure we might have missed some of them. Please let us know if you found any passive participles that are not detected.

False positives in the English passive analysis

False positives in the English passive analysis

This article gives an overview of the cases in which the Yoast SEO passive voice assessment for English will yield incorrect results. We always strive for results that are as accurate as possible. However, because of the irregularities in human language, it will never be possible to get our analysis 100% right. Below you find a list of cases in which our analysis will incorrectly detect passive voice in sentences that aren』t really passive (false positives).

It』s not necessary to know about all of those cases to write a good text. Rather, this overview is intended to give you some clues in case you』re wondering why certain sentences are not correctly detected by the passive voice analysis.

Passive voice in English

To help you understand the false positives and negatives, here is a quick explanation of how the passive voice assessment works. The passive voice assessor in English looks for sentences containing a passive auxiliary and a past participle (a passive verb).

Passive auxiliaries are formed using a form of 『to be』 or 『to get』. They are 『helper verbs』 to the main passive verb.

Past participles are the main verbs of a passive form. They are verb forms such as 『written』 or 『used』.

False positives in Yoast SEO for English

The passive voice assessment of Yoast SEO will incorrectly detect a passive voice in the following cases:

1. When a sentence has a passive auxiliary and a participle, but those words serve different functions in that particular sentence.

For example, in a sentence like 「A URL is removed by Google」, the words 『is』 and 『removed』 form a passive voice. However, it can happen that those two words occur in a sentence together, but with different functions:

「If a URL returns a 410, Google is far more certain you removed the URL on purpose.」

In this sentence, the word 『is』 describes a property of Google (「Google is far more certain」) and the word 『removed』 describes an action that 『you』 did. Therefore, 『is』 and 『removed』 do not belong together and cannot form a passive voice. However, the passive voice assessor does not know this and incorrectly analyses the sentence as containing a passive.

Below is another example of a case when two words that could form a passive do not actually belong together:

「There is a page saying 「content not found」.」

In this sentence, the word 『is』 describes the presence of a page, and the word 『found』 is part of the message displayed by that page. However, the passive voice assessor cannot separate the text in between quotes from the main content of the sentence. Therefore, it incorrectly thinks that the words 『is』 and 『found』 are forming a passive. In comparison, a sentence where 『is』 and 『found』 do form a passive would be something like 「The girl is often found sleeping.」.

2. When a word that can be a past participle also has additional meanings.

For example, the word 『left』 can be a past participle of 『to leave』 and can form a passive in sentences like 「The book was left in the library.」. However, 『left』 is also a noun (as in, the opposite of 『right』), and if it occurs after an auxiliary, the passive voice assessor will mistake it for a passive verb:

「The content part of this website is structured correctly, but the sidebar on the left is using a reversed structure.」

In another example below, the word 『(a)re』 and the word 『done』 form the expression 『you』re done』, meaning something like 『you have finished』:

「You don』t just optimize for Google search, then boom you』re done.」

This is not a passive, as it does not describe an action done to the person. Nevertheless, the passive voice assessor will analyse it as a passive. This is because it cannot differentiate between such sentences, and sentences where 『done』 does function as a passive verb. An example of the latter would be 「The passive analysis is done by the plugin.」