In the post What is a valid Hreflang? I covered how hreflang markup is to be used and what language and region codes are valid. It's a good, succinct list of valid codes. This page has more information because it includes the names of countries and languages that are represented by the various codes. For| Hreflang Testing Tool | Hreflang implementation guide and testing tool
In a previous post on how redirects cause Hreflang problems, we looked at how automatic redirection based on IP address geolocation or cookies can lead to bots being unable to crawl and access all your pages. In this post, we will look at other kinds of redirects and canonicals, and the Hreflang return tag problems| Hreflang Testing Tool | Hreflang implementation guide and testing tool
The Hreflang testing tool now has a new feature that many SEOs needed, especially those who work on large websites with thousands of URLs — exporting test results to an Excel file. When you analyze a large number of errors, it's not always easy to present all the information in a digestible format. I'm under| Hreflang Testing Tool | Hreflang implementation guide and testing tool
Many websites try to make the user's life easier by automatically redirecting her to the language/region version of their content that they infer based on IP address. But this approach is full of SEO pitfalls you should know about. In other words, the road to hell is paved with good intentions. If you do automatic| Hreflang Testing Tool | Hreflang implementation guide and testing tool
Over the few months that the Hreflang testing tool has been live, I have noticed an erroneous pattern repeat itself in the URLs that SEOs submit for testing: many people use URLs with and without trailing slashes interchangeably. This is wrong. http://www.example.com/de and http://www.example.com/de/ are technically 2 separate URLs. Google treats them as 2 separate| Hreflang Testing Tool | Hreflang implementation guide and testing tool
The Situation Multinational company has one website for each country it operates it. These websites use country-specific TLDs (e.g. example.au, example.ca, example.co.uk, example.de and so on). Websites contain information about the company's various products. The product pages for .de are in German but the pages for .ca, .au, .co.uk and .us are all in English.| Hreflang Testing Tool | Hreflang implementation guide and testing tool
One of the most common mistakes that occur in Hreflang implementations is the lack of return links. Google Webmaster Tools may report this as No Return Tags or Missing Return Tags. As evident from questions in online forums, a lot of webmasters do not understand what this error means. Here's a simple explanation. Let's say| Hreflang Testing Tool | Hreflang implementation guide and testing tool
There are seemingly countless ways to screw up Hreflang implementation. While rel=canonical is a little more straightforward, webmasters and SEOs have been known to make mistakes there too. So using Hreflang and canonical tags together seems like a potential minefield of problems. In this post, we will look at how to handle situations that involve both| Hreflang Testing Tool | Hreflang implementation guide and testing tool
Sometimes users of our Hreflang testing tool see an error like this and get baffled: Invalid hreflang (en_US) found in HTML. Why is en_US incorrect? Because the correct way to write a language code is with dashes, not underscores. The correct value is en-US. What are valid values for Hreflang? A valid hreflang can be| Hreflang Testing Tool | Hreflang implementation guide and testing tool
There are many mistakes you could make when implementing Hreflang tags on your website. Via the online Hreflang testing tool, we try to catch as many of them as we can. Here's a list, complete with how to fix each type of problem. Page-level errors Some errors can be noticed simply by looking at an| Hreflang Testing Tool | Hreflang implementation guide and testing tool