Category snippet variable replacement not working

Category snippet variable replacement not working

A very important feature of Yoast SEO is that you can automatically add SEO title and meta description templates to the homepage, all (custom) post types, all (custom) taxonomies, and other pages. You can create these templates with snippet variables, which we』ve listed in this list of available snippet variables in Yoast SEO.

If you』re using the Category (or %%category%%) snippet variable in your title template and that doesn』t get properly replaced with the category』s name, this is probably due to the fact that you』re using it for a custom taxonomy that isn』t really a 「native」 WordPress category. Simply replacing it with %%term_title%% will fix the replacement.

If the issue remains, you may need to use a custom template variable as discussed here.

Error: The Following File is Blocking Your XML Sitemaps

Error: The Following File is Blocking Your XML Sitemaps

The following file(s) is/are blocking your XML sitemaps from working properly:

/PATH_TO_FILE/name.xml

Either delete them (this can be done with the "Fix it" button) or disable Yoast SEO XML sitemaps.

The Problem

Our sitemaps are created dynamically. If you have a physical sitemap file on your server, it may conflict with our sitemap function.

The Solution

If you want to use our sitemap function, please delete the physical file located at the path in the error message. You can automatically delete the file by clicking the 「Fix it」 button or manually through FTP or a file manager. If you are unsure how to delete files on your server, please contact your webhost.

Alternatively, you can disable our sitemap function and use the physical sitemap created through your preferred method.

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.

Sitemap Error: Incorrect namespace

Sitemap Error: Incorrect namespace

The error:

Your Sitemap or Sitemap index file doesn』t properly declare the namespace.

This error appears when something on your site is modifying URLs after the sitemap is generated. This is virtually impossible for us to locate or fix as it』s not something controlled by our plugin.

However, we have seen a few cases where WP Engine』s HTML post processing feature contains a line (similar to the examples below) that when removed resolves this issue but may break other things on your site. Please contact WP Engine for advice on how to exclude the sitemap namespace from this command.

#http://# => // #http://# => https://

Is your WordPress site ready for PHP 7?

Is your WordPress site ready for PHP 7?

There are a number of tools and checklists out there to verify if your site is ready for PHP 7. One of those tools is the plugin provided by WP Engine. The plugin will check whether the code of all your active plugins and themes is compatible with PHP 7.

There are a few caveats though you』d best keep in mind:

Even though the plugin is written to detect as many problems as accurately as possible, it』s not 100% reliable in detecting errors and warnings.There may be false positives detected, the plugin doesn』t check whether the code is wrapped in a PHP version check.The plugin does not execute your theme or plugin code, so it cannot detect runtime compatibility issues.

Still, it』s a great and easy way to test your site』s compatibility with PHP 7. The plugin is called PHP compatibility check by WP Engine. We recommend you test PHP 7 extensively on a staging site before updating your live site to PHP 7. If you want your host to help, but don』t know how to phrase it, you can read our example mail to request your host updating your PHP version.

Is your site hosted on Siteground?

If you are hosted on SiteGround, you can use their SG Optimizer plugin to check if your site is ready for PHP 7. You can even switch your PHP version from within the plugin! You can read more on their blog post get your WordPress on PHP 7 now.

Yoast XML Sitemaps on NGINX servers

Yoast XML Sitemaps on NGINX servers

Our plugin generates sitemaps dynamically when you enable the sitemap feature. In some cases, you may need to add server level rewrites if you receive an NGINX server error or a wrong page when loading the XML sitemaps.

If you are using Apache, please use the rules here. If you are not sure which you use, please speak to your host provider. 

Table of Contents

Do I need to add rules?
Still not working?
What are the rules?

How do I know if I need to add the rewrite rules?

The Yoast SEO XML sitemap URL uses a pretty permalink of example.com/sitemap_index.xml but, behind the scenes, this URL also has a non-pretty permalink version of example.com/?sitemap=1. If you can load and see the sitemap using the non-pretty permalink, your server is not setup to rewrite and, thus, you』ll need to add rewrite rules.

What are the NGINX rewrite rules?

Here are examples of the rewrite rules you may need on NGINX servers. If you』re unsure where to add these rules, please contact your webhost or server admin for assistance.

If you already have rewrites in your NGINX config file, you can add these to the same section using the basic code. If you do not have rewrite rules or have an add-on like News SEO, you may need part or all of the expanded code further below.

Basic Code

# Rewrites for Yoast SEO XML Sitemap
rewrite ^/sitemap_index.xml$ /index.php?sitemap=1 last;
rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 last;

Expanded Code

#Yoast SEO Sitemaps
location ~ ([^/]*)sitemap(.*).x(m|s)l$ {
## this rewrites sitemap.xml to /sitemap_index.xml
rewrite ^/sitemap.xml$ /sitemap_index.xml permanent;
## this makes the XML sitemaps work
rewrite ^/([a-z]+)?-?sitemap.xsl$ /index.php?yoast-sitemap-xsl=$1 last;
rewrite ^/sitemap_index.xml$ /index.php?sitemap=1 last;
rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 last;
## The following lines are optional for the premium extensions
## News SEO
rewrite ^/news-sitemap.xml$ /index.php?sitemap=wpseo_news last;
## Local SEO
rewrite ^/locations.kml$ /index.php?sitemap=wpseo_local_kml last;
rewrite ^/geo-sitemap.xml$ /index.php?sitemap=wpseo_local last;
## Video SEO
rewrite ^/video-sitemap.xsl$ /index.php?yoast-sitemap-xsl=video last;
}

Remember that you might have to modify this if you are running WordPress in a subfolder.

Still not working?

If you』ve added the redirects above and the pretty permalinks do not load, the issue is likely to do with other settings on your server. Please contact your
webhost or server admin for assistance.

How to backup your (WordPress) site

How to backup your (WordPress) site

If you didn』t know yet, backing up your site is very important. Something can always go wrong. For example, when updating your site, installing a new plugin or adding some custom code. At such times it is useful to have a recent backup of your (WordPress) site at hand. You can even save this backup in different places for extra security.  It makes sure that if something goes wrong you have a fresh copy of your site you can restore and move on like nothing ever happened.

Table of contents

Why are backups of your site important?Creating a backup through your hostCreating a backup by using a WordPress pluginVideo: How to backup your WordPress site

Want to learn more about WordPress? Our FREE WordPress for beginners training is here to help. Find out how to set up your own site, learn the ins and outs of creating and maintaining it, and more. This training is part of our free training subscription, take a look at all online SEO training subscriptions!

Why are backups of your site important?

In the video below, we explain why backups of your (WordPress) site are important. This video is part of our free WordPress for beginners training.

Creating a backup through your host

Most good hosting companies will offer a backup tool or automated service for their customers. They usually allow users to set automated backups from within their control panel. We have a list available with popular WordPress hosting partners vetted by Yoast. If you want to know more about creating backups trough your host, we』d suggest you contact your hosting company.

Creating a backup by using a WordPress plugin

A benefit of using WordPress is that there are several plugins that offer a great backup solution. At Yoast, we recommend and have good experiences with BlogVault as this tool offers many great features. Such as creating staging sites and easy migrations.

Some other great backup plugins for WordPress are:

BackupBuddyUpdraftPlusBackupWPUpDuplicatorVaultPress

Video: How to backup your WordPress site

If you want to see exactly how to go about making a backup of your WordPress site, check the video below. This video is part of our free WordPress for beginners training.

Why did you charge me when my purchase failed?

Why did you charge me when my purchase failed?

Our payment provider (Adyen) sends a request to the issuing bank for either a $0 or a $1 authorization (different banks permit different amounts) to verify that the card is issued and the bank will allow it to be authorized. Regardless of whether or not the authorization is declined, Adyen reverses that authorization request immediately.

However, even if the bank declines the authorization, some people may still see an authorization for $1 on their credit card statement. The important thing to remember is that this is not a charge, and it will disappear from their statement; depending on the bank, it will be removed from their statement in anywhere from a few minutes to a few weeks.

Please note that Adyen can send a request for €1, which (depending on the current exchange rate) may show up as a transaction slightly over $1. (See current exchange rate)

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.