Hreflang hindering performance?
-
I want to add hreflang on my website but the dev guys think it will hinder performance?
Any thoughts/experience with this one way or the other?
Thanks!
-
Thanks - that could be a decent alternative to offer!
-
I'm afraid I can't offer any proof as such. I know there is an alternative way of implementing hreflang through xml sitemaps so you can avoid having to add the extra lines in the code within your pages. It's not something I've ever implemented but you can find more about it in the Using hreflang in sitemaps section of this article. Might be worth looking into.
-
I'm totally with you.... any ideas of a better response I can give them (proof from a source) that the impact on speed will be negligible?
-
Sound like a typical developers cop out when they can't be bothered to implement something! I'm no developer but I'm pretty sure an extra line of code would have very negligible impact on speed. Think of all the other different types of markup that people implement on pages, from rel=author to rich snippets, to open graph, twitter cards etc. Nobody out there says 'I'm not adding them to my pages because they'll slow the speed of the site'. Hreflang should ensure that the right page is presented in the right country SERPs and helps avoid duplication problems and that has to be worth implementing.
-
They are concerned adding an extra line of code will slow down the speed of the site...
-
Have your developers given you any further clarification on why they think hreflang might hinder performance? From my own personal experience of hreflang I have found that Google can take it's time before it shows the correct country URL in SERPs. However I did find that after a while that use of hreflang led to an increase in impressions and clicks.
Naturally rankings varied for keywords across different countries though it did appear that generally hreflang had a positive impact initially. We did experience issues with some of our keywords dropping from some of the country rankings but to be fair that was probably more related to a canonical element we implemented (but later removed on advice from Google) and Panda/Penguin issues we have been dealing with.
Perhaps if you could outline some of your developers' arguments and I may be able to address those.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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 -
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.
International SEO | | scottclark0 -
Hreflang made simple
I have a client with a Shopify site. It is a clone of the 'main' website which is a .co.uk domain. Client wants to use .com.au for Australia and New Zealand. All are English language. How should we structure hreflang tags? Or is there a better way to target the .com.au website at Australia/New Zealand?
International SEO | | muzzmoz0 -
Hreflang missing
Hi everybody, I cannot find the hreflang in the source code neither in the sitemaps but Google search console is showing me the tag. Did anyone have this problem? Or does anyone know how to check it? I scanned the site and no tool detected the hreflang in it. Thank you.
International SEO | | poliedric0 -
Google Webmaster showing error for [hreflang='x-default']
Hi There! Using [hreflang='x-default'] tag to target language specific countries on our site but Google Webmaster showing errors even implementation made as per Google guideline but one thing is not clear and we are not sure, this is the reason behind it. Error is showing up only on those pages where 'Google Parameters' are used. For example : https://www.sitegeek.com/a2hosting?grank=open 'grank=' is defined as a 'Google Parameters' and on the above page 'hreflang' tags are : Also, on page https://www.sitegeek.com/a2hosting [without Google Parameters] same above 'hreflang' tags are taken. But, There is no error on second page URL where no 'Google Parameters' in URL. Therefore, error showing on first URL where 'Google Parameters' are taken. Is this the issue or not? suggest how to remove? -- Rajiv S9vhl3T
International SEO | | gamesecure0 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
Ranking well internationally, usage of hreflang, duplicate country content
I'm trying to wrap my head around various options when it comes to international SEO, specifically how to rank well in countries that share a language, and the risk of duplicate content in these cases. We have a chance to start from scratch because we're switching to a new e-commerce platform, and we were looking into using hreflang. Let's assume an example of a .com webshop that targets both Austria and Germany. One option is to include both language and region in the URL, and mark these as such using hreflang: webshop.com/de-de/german-language-content (with hreflang de-de)
International SEO | | DocdataCommerce
webshop.com/de-at/german-language-content (with hreflang de-at) Another option would be to only include the language in the URL, not the region, and let Google figure out the rest: webshop.com/de/german-language-content (with hreflang de) Which would be better? The risk of inserting a country, of course, is that you're introducing duplicate content, especially since for webshops there are usually only minor differences in content (pricing, currency, a word here and there). If hreflang is an effective means to make sure that visitors from each country get the correct URL from the search engines, I don't see any reason not to use this way. But if search engines get it wrong, users will end up in the wrong page and will have to switch country, which could result in conversion loss. Also, if you only use language in the URL, is it useful at all to use hreflang? Aren't engines perfectly able to recognize language already? I don't mention ccTLDs here because most of the time we're required to use a .com domain owned by our customer. But if we did, would that be much better? And would it still be useful to use hreflang then? webshop.de/german-language-content (with hreflang de-de)
webshop.at/german-language-content (with hreflang de-at) Michel Hendriks
Docdata Commerce0