If you are using Yoast SEO for your WordPress to optimize your search visibility, you may also utilize the breadcrumbs feature.
Many WordPress website use custom post types (CPT) to organize their content.
A typical bug that may appear when you combine custom post types with Yoast SEO breadcrumbs is a wrong slug or title for the CPT. Most of the time, this comes from modifying your CPT information (e.g. the title).
Example: the breadcrumbs may show “Animals / Sea / Zebra” but you had recently corrected the category name so that it should be “Animals / Land / Zebra”.
This bug can easily be fixed like this:
1. Download, install, and activate Yoast Test Helper plugin
Go to your WordPress backend at example.com/wp-admin and navigate to Tools > Yoast Test.
On this page, find the section Yoast SEO (the one with the grey button collection). Find the button Reset Indexables tables & migrations and hit it.
3. (optional) Re-run SEO data optimization
The first two steps of this guide should already have resolved your issue. You can test this by going to your website and checking it.
It is recommended to re-run Yoast’s SEO data optimization once to complete your maintenance. Navigate to Yoast’s general settings at Yoast SEO > General. You should see a notification that offers a button to start SEO data optimization. Click it and you’re done.
WordPress Multisite is a powerful tool to build your network of websites easily.
Every single website within your multisite network will have its dedicated URL and title. This is how you would usually set them.
Configuring blog title in WordPress Multisite
You can configure your website’s blog title in a WordPress Multisite environment similar to how you’d do it with a regular WordPress website.
Enter the admin dashboard of the corresponding website at example.com/wp-admin.
Navigate to Settings > General.
Enter your desired site title
Configuring the blog URL in WordPress Multisite
To edit the blog URL of a single website within your WordPress Multisite installation you need to access the Network Admin. Once there, you can follow these simple steps to configure your blog URL.
Navigate to Sites > All Sites.
Click Edit below the corresponding website.
Enter your desired Site Address (URL).
[Bugfix] Fix WordPress Multisite wrong blog titles and URLs
You may occasionally come across the case that changing the blog title and/or URLs of your multisite websites does not become effective.
The most obvious reason for this is a broken WordPress Multisite configuration. Make sure that you have configured your wp-config.php and your .htaccess files as specified under Settings > Network Setup within the Network Admin of your Multisite.
If everything is correctly set up, the next step would be to disable all plugins and check if this helps.
If the error still persists, there is another place where the bug may sit:
Navigate to the filesystem of your website.
Check if there are any files under wp-content/mu-plugins.
Create a copy of all those files in a safe place (outside of your WordPress installation).
Delete one after the other of these files and find out which one causes the bug.
Hint: If there is a file memcache-fix.php the chance is high that this file causes the trouble.
Hosting your custom fonts by yourself is an important step to making your website more independent of third-party services. Webfonts have always been reasonably easy to implement with WordPress. There are many plugins helping you with this task.
Thanks to the new generation of WordPress themes, the block themes, hosting your custom fonts got even more simple. The theme.json of your child theme is the best place to define custom fonts.
When you are adding your custom fonts to your website, you may ask yourself which font file format you should upload. Typical bundles from webfont providers contain multiple files very often. These may be of type WOFF, WOFF2, EOT, TTF, or SVG.
A typical CSS code to load your custom font files has previously looked something like this.
But is it essential to upload so many font files to your website?
Let’s have a quick look at the different font formats and their characteristics.
Font format comparison
For the font format comparison, we have used the font Noto Sans (v27) from Google Fonts. This is also the default primary text font in our Base FSE theme for WordPress. In this comparison, we have used only the Latin Unicode range in the regular (400) font weight. The font files have been generated with the amazing google-webfonts-helper by Mario Ranftl.
Browser support has been verified with caniuse.com in July 2022 based on the global percentage of all users (based on data of visitors of caniuse.com). We have only verified support for reasonably modern browsers in our comparison (IE9+, Edge, Firefox 3.6+, Chrome 5+, Safari 5.1+, Opera 11.5+). If you are building a website for historic browsers you may have other priorities than optimizing your font formats for best performance.
When we’re comparing the results, we can see that we have several font formats with very high compatibility across browsers. It is obvious that Opera Mini does not support any of the investigated font formats. Other than that, Internet Explorer is the only browser that does not support WOFF2, the best format when it comes to performance (smallest file size).
Even if since June 15, 2022, Internet Explorer has retired, there are still many users out there. Especially in corporate contexts where the end-user may not always have control over the software installed on their device, this may be the case. Therefore, as of 2022, we believe the ideal font format set-up should still take support for IE into consideration.
WOFF me up, baby!
The clear winners of our font format comparison are WOFF and WOFF2. If there was no Internet Explorer, WOFF2 would be the only format we’d need for modern browsers. The best-in-class performance of WOFF2 in terms of compressing font files to the smallest file size makes this font format the best choice for your website.
Smaller font file sizes will help you to reduce the overall load of your website. This leads to a faster website and better page speed.
A typical recommendation based on the results of our comparison would be to only upload WOFF2 and WOFF font files to your website. WOFF2 is the default format for most of your visitors. WOFF is the fallback for Internet Explorer users. If you are looking at our results with the font Noto Sans only, you could even come to the conclusion to use WOFF2 and EOT as the fallback font format (EOT was slightly smaller than WOFF). But the file size results may be different for different fonts and Unicode ranges. We’d still recommend going for WOFF as the fallback font simply to stick with only modern font formats. At the same time, WOFF will help you to increase compatibility with very old versions of other browsers.
The result of this comparison is clear: WOFF2 plus WOFF as the fallback are the only font formats you will need to upload to your website.
A word on font file optimization
Now that we know that WOFF2 plus WOFF may be the best constellation for performance-optimized font files, we must talk about how we can optimize even further within those file formats.
Fonts come in different flavors. They may be regular, bold, or italic. And there are different Unicode ranges (e.g. Latin, Vietnamese, or Cyrillic). Some modern fonts are available as variable fonts.
Typically, a visitor to your website will not need the full Unicode range in all font variations all the time. A single page of your website may only utilize a small subset of these possibilities. Therefore, splitting font files by font variation and Unicode range is a best practice to follow. Doing so will help you to reduce the file sizes transferred. And saving kilobytes is the ultimate goal of optimizing font files.
If you are planning to use a font that is available at Google Fonts, we recommend giving google-webfonts-helper a try for optimizing and splitting your font files easily.