Hreflang alternate as single-hop 301 - is this actually a problem?
-
First, this is not a question about whether 301 redirects pass page rank.
My question is that if your hreflang alternative page URL is a 301 redirect*, are there any downsides. In all cases with our situation, the 301 redirect is single-hop and working.
Tools, such as SEMRush seem to flag this as a non-canonical hreflang error, but I'm not able to find any cases where Google has suggested a redirecting hreflang is a problem.
I'd appreciate any information on this issue before we invest extra time on a large international site.
*In Drupal, there are scenarios where it's all but impossible to avoid having a 301 redirect in your hreflang alternate URL without significant custom work.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Targeting/Optimising for US English in addition to British English (hreflang tags)
Hi, I wonder if anyone can help? We have an e-commerce website based in the UK. We sell to customers worldwide. After the UK, the US is our second biggest market. We are English language only (written in British English), we do not have any geo-targeted language versions of our website. However, we are successful in selling to customers around the world on a regular basis. We have developers working on a new site due to launch in Winter 2021. This will include a properly managed site migration from our .net to a .com domain and associated redirects etc. Management are keen to increase sales / conversions to the US before the new site launches. They have requested that we create a US optimised version of the site. Maintaining broadly the same content, but dynamically replacing keywords: Example (clothing is not really what we sell): Replacing references to “trainers” with “sneakers”
International SEO | | IronBeetle
Replacing references ‘jumpers with “sweaters”
Replacing UK phone number with a US phone number It seems the wrong time to implement a major overhaul of URL structure, considering the planned migration from .net to .com in the not too distant future. For example I’m not keen to move British English content on to https://www.example.com/en-gb Would this be a viable solution: 1. hreflang non-us visitors directed to the existing URL structure (including en-gb customers): https://www.example.com/
2. hreflang US Language version of the site: https://www.example.com/en-us/ As the UK is our biggest market It is really important that we don’t negatively affect sales. We have extremely good visibility in SERPS for a wide range of high value/well converting keywords. In terms of hreflang tags would something like this work? Do we need need to make reference to en-gb being on https://www.example.com/ ? This seems a bit of a ‘half-way-house’. I recognise that there are also issues around the URL structure, which is optimised for British English/international English keywords rather than US English e.g. https://www.example.com/clothing/trainers Vs. https://example.com/clothing/sneakers Any advice / insight / guidance would be welcome. Thanks.0 -
Important pages are being 302 redirected, then 301 redirected to support language versions. Is this affecting negatively the linking juice distribution of our domain?
Hi mozzers, Prior to my arrival, in order to support and better serve the international locations and offering multiple language versions of the same content the company decided to restructure its URLs focused on locale urls. We went from
International SEO | | Ty1986
https://example.com/subfolder to https://example.com/us/en-us/new-subfolder (US)
https://example.com/ca/en-us/new-subfolder (CAN)
https://example.com/ca/fr-ca/new-subfolder (CAN)
https://example.com/de/en-us/new-subfolder (Ger)
https://example.com/de/de-de/new-subfolder (Ger) This had implications on redirecting old URLs to new ones. All important URLs such as https://example.com/subfolder were
302 redirected to https://example.com/us/en-us/subfolder and then 301 redirected to the final URL. According to the devs: If you change the translation to the page or locale, then a 302 needs to happen so you see the same version of the page in German or French, then a 301 redirect happens from the legacy URL to the new version. If the 302 redirect was skipped, then you would only be able to one version/language of that page.
For instance:
http://example.com/subfolder/state/city --> 301 redirect to {LEGACY URL]
https://example.com/subfolder/state/city --> 302 redirect to
https://example.com/en-us/subfolder/state/city --> 301 redirect to
https://example.com/us/en-us/new-subfolder/city-state [NEW URL] I am wondering if these 302s are hurting our link juice distribution or that is completely fine since they all end up as a 301 redirect? Thanks.1 -
Hreflang on non 1:1 websites
Hi. I have a client with international websites targeting several different countries. Currently, the US (.com) website outranks the country-specific domain when conducting a search within that country (i.e. US outranks the UK website in the UK). This sounds like a classic case for hrelang. However, the websites are largely not 1:1. They offer different content with a different design and a different URL structure. Each country is on a country-specific domain (.com, .co.uk, .com.au, etc.). As well, the country-specific domains have lower domain authority than the US/.com website - fewer links, lower quality content, poorer UX, etc. Would hreflang still help in this scenario if we were to map it the closest possible matching page? Do the websites not sharing content 1:1 add any risks? The client is worried the US/.com website will lose ranking in the country but the country-specific domain won't gain that ranking. Thanks for any help or examples you can offer!
International SEO | | Matthew_Edgar0 -
When should hreflang be deployed in this situation; now or later ?
Hi I have a question in regard to point 1 in Gianluca Fiorelli first comment on Aleyda Solis old but great international targeting article in regard to hreflang: https://mza.seotoolninja.com/blog/using-the-correct-hreflang-tag-a-new-generator-tool it would obvs be amazing if either Gianlucca or Aleyda can answer but if anyone else feels they can do so confidently then that would be great too 🙂 I'm advising someone in similar situation as that (their main brand is USA based on a .com showing up in UK searches too) and they have launched .co.uk sites (without any seo) to target UK brand searches, so obviously the .com is still dominating UK serps for brand, and the .co.uk is ranking on page 4 on average for a brand search. **BUT **before I tell them to roll out hreflang shouldn't they build up some authority etc first for their new country specific (.co.uk) site ? since they are very new and have no authority or even basic SEO and don't rank higher than page 4 for brand searches (the .com is in no1 in both usa and uk). I know hreflang needs to be used correctly here but im not sure when it should be, now or later (after authority has built up for the new uk focused sites) ? In other words I take it deploying the hreflang correctly wont simply cause these home pages to swap positions for brand search in uk (or will it) ? Im worried deploying it immediately could actually destroy the brands current page 1 serps for brand term (since will remove the .com page from the uk serp). Hence i take it its best to build up the new .co.uk sites seo/authority etc first and at least get that sites brand ranking moving up the listings before deploying hreflang on the .com, to then hopefully remove the .com listing in place of the .co.uk for brand ? OR does Gianlucca point in his comment suggest that correct hreflang usage on both sites should swap the high authority .com no1 position with the low authority .co.uk for a brand search ? Many Thanks Dan
International SEO | | Dan-Lawrence0 -
Search Console Hreflang-Tag Error "missing return tag": No explanation
Hey there, we have recently implemented hreflang on the sitemap level for our global website. The website has 57 sitemaps that are all referenced in a sitemap index file (www.buschvacuum.com/sitemap.xml). Google is showing several errors in search console ("Sitemap provided URLs and alternate URLs in 'en-AU' that do not have return tags."). However when I try to verify this I do find the return tags. Can this be caused by the fact that my hreflang tags span several sitemap files? To pick one random example (see screenshot for search console error message):
International SEO | | Online-Marketing-Guy
The Originating URL-hreflang-Tag is in www.buschvacuum.com/sitemap_3.xml, the return tag is in www.buschvacuum.com/sitemap_4.xml. It would be great if someone with experience regarding those errors could help me explaining that behavior. Thanks a lot. Jochen WXYQoUH.png0 -
Problems with the google cache version of different domains.
We have problems with the google cache version of different domains.
International SEO | | Humix
For the “.nl” domain we have an “.be” cache..
Enter “cache:www.dmlights.nl” in your browser to see this result. Following points are already adapted: Sitemap contains hreflang tag Sitemap is moved to the location www.dmlights.nl/sitemap.xml We checked the DNS configuration Changed the Content language in de response header to : Content-Language: nl-NL Removed the cache with webmastertools Resolved serverrequest errors. Can anyone provide a solution to fix this problem? Thanks, Pieter0 -
Alternate Hreflang Problem
We have two travel websites.
International SEO | | Izzet
One in English language for people living in the UK.
One in Turkish language for people living in Turkey. The major difference is:
English (UK) website shows 4+ nights accomodation prices because UK travellers never come for less than 4 nights.
Turkish website shows 1-night, 2-night, 3-night prices because Turkish travellers never stay for more than 3 nights. We are using rel="alternate" hreflang="x" tags properly on our two websites. Today, I am disappointed to see Google display the wrong result. When a user in Turkey searches a Turkish keyword on Google.com.tr;
Google is showing the English language website. When I click on Search Settings > Language;
I see that English is selected under this question:
"Which language should Google products use?" This is a big problem for us.
Many rich users in Turkey, who are more willing to buy our services, speak English fluently and they may choose to use Gmail in English. But we are losing business because these Turkish customers don't convert at all on the Enlish (UK) website because of the reason I explained above. 1) What can we do?
2) If we remove the rel="alternate" hreflang="x" tags now, will it hurt any of the websites?
We have seen an increase in Google rankings for the Turkish language website after using rel="alternate" hreflang="x" tags. Izzet0 -
Is having duplicated content on different domains a problem when using alternate tag, but no canonical?
We will be launching a couple of new language versions. I understand that ccTLD is mostly considered as best option, however I thought that to start with it might be better to launch the new language version first on a subdirectory of our established domain with strong backlink profile as it may rank much better until I can attract some strong links to new ccTLD. I would wait for the pages of new language versions to be indexed on the main domain and then after a month launch the same content paralell on the ccTLD setting up an alternate tag in the main domain pointing to the ccTLD. I would not setup any canonical tag. As I understand google would rank whatever of the 2 versions ranks higher. Should not cause duplicated content issues right?
International SEO | | lcourse
Any thoughts? EDIT:
For clarification. The language we are launching are mostly spoken in several countries. E.g. for Portuguese I would add in main domain an altnernate tag for Brazilian visitors to Brazilian ccTLD, but no alternate tag for Portuguese visitors. For Corean I would add in main domain an alternate tag for visitors in south corea, but not one for visitors in north corea.0