URL structure of international hotel website
-
Hai all,
Question about URL structure of international hotel website in Amsterdam: hotelcitadel.nl.
Some information:
- Target group are mainly english speaking guests from UK and US. Besides that guests from the Netherlands and some other countries.
- Website in 6 languages.
- No geo-targetting; just language targetting with hreflang annotations.
Current situation:
hotelcitadel.nl = dutch language version and hotelcitadel.nl/en = english language version
We are thinking about changing this to:
hotelcitadel.nl would become english version and hotelcitadel.nl/nl would become the dutch version.
Reason: root domain hotelcitadel.nl has by far the most links,and making the root domain the english version could help the rankings in english speaking countries like UK and US.
What do you think, would this be a wise idea?
Regards, Maurice
-
Great Stephan, nice to hear and thanks again
Regards, Maurice
-
Hi Maurice,
Yes, that's right: the Hotel Nicolaas site is behaving correctly. When I visit the homepage there, everything is consistent and in English, and the language cookie is set to en-GB. Even when I manually change that cookie value to nl-NL, the content is still in English, because I'm on an English-language URL. To get Dutch content I have to visit the /nl/ directory. That's a much better setup, because there's no way to end up with duplicate English-language content: the URLs are consistent.
Best Regards,
Stephan
-
Hai Stephan,
Thanx again, very helpfull!
I still have 1 question concerning point 2.
Some months ago we rebuilt the website of a “sisterhotel”: www.hotelnicolaas.nl . As far as I can check the website of this hotel does not have the problems/strange behavior anymore as you discribe concerning www.hotelcitadel.nl Is that correct? Is the website of www.hotelnicolaas.nl behaving correctly concerning the languages?
(You will notice that we already changed the URL-structure there and that the homepage is the English version. We still have to add x-default.)
Regards, Maurice
-
Hi Maurice,
Sorry for the delay in getting back to you. To address points 2 and 3 that you've raised there:
2. I'm still seeing this behaviour on the site, and it persists across different browsers. I've attached some images to show what I'm seeing. However, if I then click on the English flag (to visit /en/), and then click the Netherlands flag, a cookie is set: jfcookie[lang]="nl". After this cookie is set, the homepage appears in Dutch for me. So it seems as though visitors to the homepage of your website are served English-language content based on the absense of a jfcookie[lang] cookie, or based on their IP address -- you would have to check with your developers which is the case -- and it's only after visiting one of the other languages and then switching back to Dutch that the homepage will appear in Dutch.
3. I don't believe you would see a rankings boost from doing this. I think that, provided x-default is correctly set (to English, in your case), and this issue with the language cookies/IP address is corrected, you can expect Google to figure out the correct page to show in the results for each country/language combination. I do hear what you're saying about most of your customers speaking English, but I also think that, given you use a ccTLD, it could create a strange user experience to have English content on the homepage and Dutch in a subfolder. And x-default largely solves the problem of most of your users speaking English. I don't think there's enough upside to justify the effort.
-
Hai Stephan,
Thanks for your suggestions.
- Add the x-default is a good idea. I’ll do that.
- Difference HTML lang and hreflang: I do not see this problem. Homepage hotelcitadel.nl: HTML=nl and content is written in dutch and not in english…Am I seeing something else then you do?
- Just to be sure that I understand you correct: What do you think about my proposed change of URL’s, wise? Will it make our website stronger for rankings in the english speaking market? Or better to leave it as it is?
Cheers, Maurice
-
Hi Maurice,
Both of these pages are on the same root domain, because you've (sensibly) used subfolders for languages, instead of subdomains. The arrangement you're thinking of switching to does sound as though it better describes target market: it'd be nice to see x-default set to english, if that's the language spoken by the majority of your visitors/target market.
When I visit the homepage as Googlebot, the hreflang is "nl", but the html lang is "en". Also, the page content appears to be in English. When I then navigate to hotelcitadel.nl/en, I get exactly the same English-language content, with html lang equal to "en" again, and hreflang "en".
The other languages work OK, and are crawlable, but you should correct the duplicate content issue between the homepage and the /en/ subfolder, and also the discrepancy between "html lang" and "hreflang" on the homepage. It should either be definitively in English, for all users, or definitively in Dutch. Perhaps you're using an IP redirect to determine language on the homepage? If so, I'd suggest not doing that. Your other languages seem to be set up OK.
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
-
Is this approach of returning different content depending on IP beneficial for international SEO?
I've decided to use sub folders for my site, and from everything I've read online it seems I shouldn't change the page content depending on IP, yet I know of a successful well funded site that hires full time SEO staff that does just that, and I'm wondering whether they know something I don’t which is helping their SEO. From everything I've read online this is the format I think I should use: mysite.com/us/red-wigs mysite.com/gb/red-wigs mysite.com/red-wigs does not exist This is the format the other site is using: othersite.com/red-wigs (from US IP address) othersite.com/red-wigs (from UK IP address) othersite.com/gb/red-wigs The content on othersite.com/red-wigs is identical to othersite.com/gb/red-wigs when loading from a UK IP address, and a lot of URLs without /gb/ are being returned when searching google. The benefit I can think of that they are gaining is US pages which are being returned for UK based searches will return the correct content. Are their any other gains to this approach? I'm concerned that if I use this approach for different languages then the radically differing content of othersite.com/red-wigs depending on the location of the crawler might confuse google - also generally changing content depending on IP seems to be recommended against. Thanks
International SEO | | Mickooo0 -
An International SEO Conundrum
Hello all, I'm looking for opinions on this. Imagine there is a website example.com in English and the company 'Example' wanted to translate some of the pages (not not all) in to Russian. So they set up example.com/ru and translate the key pages into Russian. But half of the pages on.com/ru are left in English and there are no plans to translate them. How would you handle the pages in Engish on .com/ru? My thoughts are that they should: Canonicalise to the same versions on .com, and... Remove RU hreflang tags from the pages on .com/ru which are in English Otherwise, users searching in English with Russian browser settings could land on a page in English but then navigate to a translated page in Russian (+the menu navigation items will be in Russian) = bad UX. Not to mention they would be telling Google a page is in Russain but Google would be crawling English. So IMO, the best option is to use canonicals for this so that the .com version of the page is indexed. Then when a user lands after searching in English they will always be served English pages within that session. If English speakers/searchers land on the .com/ru page that would lead to a website half in one lang and half in another. I'm aware that Google recommends not using rel="canonical" across country or language versions of your site, but I believe they are making that recommendation based on an assumption that all pages are going to be translated to another language. In this case, there is no intention to do that, ever. Thanks for your thoughts and opinions. Cheers, Gill.
International SEO | | Cannetastic0 -
International targeting
I submitted each language URL as a separated website to google webmasters, I've submitted Hreflang sitemap which has language codes only(without countries codes) each page in my website has hreflang language and country code. Should i use international target option for each language to target the countries? will that hurt the language targeting? or I have to leave international targeting option unchecked for each language? My Goal to target by languages, not countries.
International SEO | | MTBE0 -
International Targeting for Australia Problem
Hello Moz Community! I'm reaching out since I recently launched a UK and Australia version of my website. Now, each page on the website has 4 versions: 1. www.example.com 2. www.example.com/au 3. www.example.com/uk 4. www.example.com/en <-- this is a by-product of the plugin we're using, CMS is WP each page has the following 4 targeting tags on it: I looked in Webmaster Tools and we're getting an error on what appears to be every Australia page. The error states, ""au"- unknown language code. URLs for your site that have an unknown language code 'au' and their alternate URLs." In Google's own example, they have the language for Australia set as en-au [https://support.google.com/webmasters/answer/189077?hl=en} Has anyone run into this issue before? We had the alternate tag set to "au" at first, but edited the plugin so the alternate tag now says "en-au", but this still hasn't remedied the problem. Any insights into resolving this error are greatly appreciated!
International SEO | | DigitalThirdCoast0 -
Different urls for the homepage on an international website
Hi! I was wondering what would be the best strategy to solve duplicated content generated by the homepage and its differents URLS This is an international website. Now it only has one language working: Spanish, but the url structure is already ready to work with the language approach So we have now www.brand.com -> Spanish Homepage (canonical www.brand.com/es)
International SEO | | teconsite
www.brand.com/es -> Spanish Homepage (canonical www.brand.com/es)
www.brand.com/index.php -> Spanish Homepage (canonical www.brand.com/es) I would like to know if this is the correct approach of if we should add 301 redirects instead of canonical. Let's image that they want to active the /en language, so they will have www.brand.com
www.brand.com/index.php
www.brand.com/es
www.brand.com/en now what? I image they have to use hreflang, but I am a little lost with how this should work. 301? canonical? hreflang? Could you help me? Thank you! Victoria0 -
Transfer a website from WP to Joomla
Hello guy's, We have a WP website and we are moving soon to a new site that will be in Joomla.
International SEO | | WayneRooney
Our website is very big and we are ranking with more then 400 keys in all the tshirts industry in the UK.
The new website will be with the same url's and the same domain so we will not lose any of the ranking.
Within this domain we have the blogs as well and a lot of pages. I'd like to get some tips about how to make the transition as smooth as we can to avoid problems with Google ? We have more then 700 visitor a day so we can not take any risks regarding to this. Any help is welcome !!!0 -
Subdomains vs ccTLD in International SEO
I'm interested to see if anyone has any additional thoughts or recent experience on subdomains vs ccTLD for International SEO. An article I found on this site is from March 2011, so just wanted to check if this is still relevant? http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview
International SEO | | edwardlewis0 -
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