Often the person Gibraltar Email List for the hreflang sitemap takes the main site they know to multiply the URLs by replacing the language-country directory in the URLs assuming there is a full match. However, when you notice that pages are missing from a language / country site, you must decide whether you want to place other replacement pages or if you prefer to combine the main URL offering content for other countries. Verification tools that do not validate correctly Variations in the structure of URLs also cause some headaches. You hope everyone uses the same URL structures as the main site, but the reality is that many sites don’t think about international versions and use different URL structures.
This happens frequently on the same domain name, so you can imagine how difficult it is to try to group pages from different domain names correctly. The differences in URL structures don’t just happen between sites, but as we just said, within the same site. Examples of irregular URL structures : mysite.com/en/categorie/page1.html mysite.ca/categorie-html Most validation tools do not crawl the site to confirm that the URLs entered in the hreflang attributes are correct or really exist. They don’t check if any of the URLs are redirected or if the page has a different URL in the canonical tag .
They Tell Search Engines
So they just look at what you entered in the hreflang attribute. If that makes sense, it returns the page without any issues. These tools only work when you are absolutely sure that the URLs used are all correct. Cannibalization between your sites One of the most important goals in using hreflang is to ensure that the correct language / country page appears in search results based on the location of users. You need to deliver the right content to users based on where the Google search is performed. For your business, it’s also about driving conversions for your business in the right place so that the local team can benefit.
If a wrong language / country page appears in the search results, the page will generate a conversion or a purchase which will be processed by one of your teams located in another country. For example, when your page created for the US market appears in search results in Japan, the site visitor will likely leave the page immediately and click on another blue link in Google’s organic results. In this case, you have just lost a potential customer. It gets even trickier when you have multiple websites in the same language targeting different countries. An example of this would be when someone searches in Spanish in Costa Rica,
Individual Websites May Have Their Own Voice Assistants
but a page designed for Mexico appears in the search results. Since it is in Spanish, a site visitor can fill out the form with a question or request regarding the product. But since the address on the form is not in Mexico, the Costa Rican office will never get this information. One of the main factors behind this cannibalization is the incomplete implementation of hreflang. Research by HREFLangBuilder in 2019 found that 42% of global sites implemented hreflang only on the homepage and key category pages, leaving product pages to be handled at Google’s whim.
Nobody updates the hreflang Unfortunately, it is often the case that the hreflang list is not reviewed and validated before being put online. This also happens with XML Sitemaps files. I’m sure many of you have seen an error message saying URLs sent through Sitemap are returning 404 errors in your Search Console report . Indeed, your website grows over time with the addition of new content. As a result, new pages are added or removed from the site, but it is rare that there is an automated method to update the hreflang. There may be more unique content on some language / country websites.