Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Correct Hreflang & Canonical Tags for Multi-Regional Website English Language Only having URL Parameters
-
Dear friends, We have a multi-regional website in English language only having the country selector on the top of each page and it adds countrycode parameters on each url. Website is built in Magento 1.8 and having 1 store with multiple store views. There is no default store set in Magento as I discussed with developer. Content is same for all the countries and only currency is changed. In navigation there are urls without url parameters but when we change store from any page it add parameters in the url for same page hence there are total 7 URLs. 6 URLs for each page (with country parameters) and 1 master url (without parameters) and making content duplicity. We have implemented hreflang tags on each page with url parameters but for canonical we have implemented master page url as per navigation without url parameters Example on this page. I think this is correct for master page but we should use URL parameters in canonical tags for each counry url too and there should be only 1 canonical tag on each country page url. Currently all the country urls are having master page canoncial tag as per the example. Please correct me if I am wrong and **in this case what has to be done for master page? **as google is indexing the pages without parameters too. We are also using GEOIP redirection for each store with country IP detection and for rest of the countries which are not listed on the website we are redirecting to USA store. Earlier it was 301 but we changed it to 302. Hreflang tags are showing errors in SEMRush due to redirection but in GWT it's OK for some pages it's showing no return tags only. Should I use **x-default tags for hreflang and country selector only on home page like this or should I remove the redirection? **However some of the website like this using redirection but header check tool doesn't show the redirection for this and for our website it shows 302 redirection. Sorry for the long post but looking for your support, please.
-
This is a long and detailed query so I think, it will be best to annotate your question with my responses:
"Dear friends, We have a multi-regional website in English language only having the country selector on the top of each page and it adds countrycode parameters on each url. Website is built in Magento 1.8 and having 1 store with multiple store views." - it is probably better to go with a folder-structure based regional deployment as Google doesn't tend to weight parameter URLs very strongly at all, unless there are link / citation signals which prove the child page version (parameter based) is more popular than the parent (in which case, they can shuffle around)
"There is no default store set in Magento as I discussed with developer. Content is same for all the countries and only currency is changed. In navigation there are urls without url parameters but when we change store from any page it add parameters in the url for same page hence there are total 7 URLs." -this sounds incredibly complicated. It sounds like at some point, someone will leave or forget how things work and you will be in a big mess
"6 URLs for each page (with country parameters) and 1 master url (without parameters) and making content duplicity." - yes I can see how that would be a problem. Also you said there was no default URL, but now says there is a master URL. Surely master is default? This may need more explaining for myself or others to help your properly. By the way, something very important here - if you're just planning to use hreflangs on their own and change pricing, very often Google won't consider that a good enough effort to give you an international footprint. Google think, hmm if you really have identified these new audiences across the world, even if they speak the same language - they are different people with a different culture. Should your content really be EXACTLY the same? No. If you do bother to do different content for different audiences (even if they speak the same language) which is tailored to their cultural nuances - you will probably get more international rankings. If you don't and you're just doing the cheapest fastest thing, you have no value proposition for Google and thus don't expect to win big (or even at all)
"We have implemented hreflang tags on each page with url parameters but for canonical we have implemented master page url as per navigation without url parameters Example on this page." - just so you know, a canonical tag acts almost like no-index tags. It says to Google: I am not the main version of this page, so please never index me. Instead index this canonical URL I am linking to instead. As such, with your current implementation, all of your regional URLs will be taken out of Google's index unless popularity signals contradict your canonical tags (in which case they may be overridden). Think about it. With hreflangs you are telling Google: go over here and index my other language version. So Google goes over to another page, but that page says: Google I am not canonical, why are you even here? Go to the canonical master only don't look at me. So you are really confusing Google by telling them to index pages with Hreflangs, then telling them not to with canonical tags
"I think this is correct for master page but we should use URL parameters in canonical tags for each counry url too and there should be only 1 canonical tag on each country page url. Currently all the country urls are having master page canoncial tag as per the example. Please correct me if I am wrong and in this case what has to be done for master page? as google is indexing the pages without parameters too." - with your current implementation, Google should (most of the time, this is not absolute) only be indexing the master pages and not indexing any of the regional pages. The regional pages all tell Google that they are not canonical and not good for indexing, by using the canonical tags you are telling Google to only index the master. I would personally remove all canonical tags from all regionally appended parameter URLs. If you have parameters firing for other reasons (e.g: changing tabbed content, moving a carousel, UTM campaign tracking) then those should be trimmed out of Google's index using canonical tags. That being said; for your regional parameter URLs, it's a different story. You want your regional pages to rank - right? So don't tell Google they are non-canonical, by putting canonical tags on them pointing to the master. In-fact I might even put some of them in a Sitemap.XML and feed them to Google. I would only do this, where the regional modifier is the ONLY parameter in the URL. If there are others, I might still use canonical tags - but for just the regional modifier on its own, they should be stripped of canonical tags (if you want them to rank ever)
"We are also using GEOIP redirection for each store with country IP detection and for rest of the countries which are not listed on the website we are redirecting to USA store. Earlier it was 301 but we changed it to 302. Hreflang tags are showing errors in SEMRush due to redirection but in GWT it's OK for some pages it's showing no return tags only. Should I use x-default tags for hreflang and country selector only on home page like this or should I remove the redirection? However some of the website like this using redirection but header check tool doesn't show the redirection for this and for our website it shows 302 redirection. Sorry for the long post but looking for your support, please." - Support is here! Two main things. Firstly code 303 might be more appropriate than codes 302 or 301. I would not bother with X-Default unless you really know what you are doing, since you are already in one Hell of a mess I would not touch that yet. Fix the basics, wait for the dust to settle! Finally, all you need to do for Google is to exempt Google's user-agent of "googlebot" from your regional redirects. That way they don't get bounced around, but users still do
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
-
Worldwide and Europe hreflang implementation.
Hi Moz ! We're having quite a discussion here and I'd like to have some inputs. Let me explain the situation and what we plan to do so far. One of our client has two separate markets : World and Europe. Both pages versions will be mostly the same, except for the fact that they will have their own products. So basically, we'd want to show only the European EN version to Europe and the standard EN version to the rest of the world, same goes for FR and ES. As far as IT, DE, CS and SK, they will only be present within the european version. Since we cannot target all Europe with a single hreflang tag, we might have to do it for every single european countries. Regarding this subject, SMX Munich recently had quite an interesting session about this topic with a confirmation coming from John Mueller saying that we can target a single URL more than once with different hreflang tags. You can read more here : http://www.rebelytics.com/multiple-hreflang-tags-one-url/ So having all this in mind, here's the implementation we plan to do : www.example.com/en/ Self canonical www.example.com/fr/ - hreflang = fr www.example.com/es/ - hreflang = es www.example.eu/it/ - hreflang = it www.example.eu/de/ - hreflang = de www.example.eu/cs/ - hreflang = cs www.example.eu/sk/ - hreflang = sk www.example.eu/fr/ - hreflang = be-fr www.example.eu/fr/ - hreflang = ch-fr www.example.eu/fr/ - hreflang = cz-fr www.example.eu/fr/ - hreflang = de-fr www.example.eu/fr/ - hreflang = es-fr www.example.eu/fr/ - hreflang = fr-fr www.example.eu/fr/ - hreflang = uk-fr www.example.eu/fr/ - hreflang = gr-fr www.example.eu/fr/ - hreflang = hr-fr etc… . This will be done for all european countries (FR, EN and ES). www.example.com/en/ - x-default Let me know what you guys think. Thanks!
International SEO | | Netleaf.ca0 -
Hreflang for bilingual website in the same region/location
Hi everyone, got a quick question concerning the hreflang tag. I have a website with 2 different language versions targeting to the same region(Reason: The area is bilingual however not everyone speaks the other language fluently) Question:
International SEO | | ennovators
Can I use hreflang in that case like: Many thanks in advance0 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
Two versions of a website with different languages - Best way to do it?
I'm working on a website for a Swedish artist and her page is in Swedish, everything is in Swedish on the site, even though it's not a lot of text on the site. We would like to have the site in English too, or another version of the site in English on a separate domain, what's the best way to proceed from here? The domain name is a .se (swedish domain), would it be better to create a another domain and host the english version of the site on a .com domain? Or will we bump into problems with duplicate content if we create a replica of the swedish site in english. We're using wordpress and I know that there's translation plugins out there, is that a good option? I'm a bit clueless on how to proceed and would love some help or guidance here.
International SEO | | Fisken0 -
Upper case or/and lower case in rel="alternate" hreflang
Hi Mozzers, I have a question about the rel="alternate" hreflang tag, with an example. When I use two subfolders for two different countries/languages, for instance www.domain.com/nl-nl/ and www.domain.com/nl-en/ (for the English version) and I want to use the rel="alternate" hreflang tag, do I need to follow the ISO standards concerning Uppercase country code and Lowercase language code (en-NL)? Or is it okay to use the Lowercase country and language code (en-nl), since we also use this in the URL of the Subfolder. What does Google prefer? Thanks in advance.
International SEO | | MartijnHoving820 -
Multi Regional website - Folder strategy
Hello Seomoz people ! I've been struggling for some time now with an international website project. It's gonna be an:international website with joomla. To sum up: We have an international company The company has 13 subsidiaries worldwide (same products, different names) The company doesn't have enough resources to get 13 independent websites Some subsidiaries work in one country / one language, some others on a region (several countries, several languages) Thanks to your community we decided to: Get a main website company.com Get subsidiaries folders (middle east, oceania and south america will be easier to link to their subsidiary) .com/asia .com/middle-east .com/oceania .com/south-america .com/uk .com/usa .com/fr .com/es .com/de .com/ma .com/dz .com/it We also need to: Get some websites in different languages .com/asia-cn .com/asia-en etc. Now how do we do to manage: Regional websites (the first 4th on the upper list) Google allows to affect a website to a country not region Will they compete with the .com ? How do we set up them for google ? How do we avoid duplicate content and keep local ranking .com/asia-en/services1.html will have the exact same content that_.com/services1.html_ If we use canonical from _.com/asia-en/services1.htm_l to _.com/services1.html , d_oes that mean /asia will not rank in asia ? Hope you can help us to figure us the best solution for this good project ! Thanks a lot. Florian
International SEO | | AymanH1 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0