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
-
Migrating to a tag-driven global website - Need opinions!
We currently have a global site that is set up this way: Subfolders to designate countries. Content in same language is re-published on other country websites. Since we are re-launching at the end of the year, we are doing away with re-publishing content on different country sites and will just maintain a single copy of our content (to be populated on different pages using content tags). We are planning on doing this so that there is no need to apply href-lang tags on our content. My questions: Is maintaining just a single instance of an article good for a global website? What are the possible complications that may come up from this approach? Since there is only one version of the article that is being indexed, is a rel-canonical tag even needed? Should href-lang tag still be applied to high level pages (homepage, etc) to ensure that the correct homepage shows up in the appropriate geography? This question is quite long, so any feedback will be helpful. Thanks!
International SEO | | marshdigitalmarketing0 -
International SEO Setuo
Hi Guys i have a client who is looking to be found in multiple English speaking countries I.e .co.uk, .com and .com.au At first I advised they would need unique content for each to avoid duplication but then the client showed me this site http://welleco.com/ this is setup via shopify on a multisite. All the sites have the same content and are all indexed. My question is can this be done in WordPress? Via something like WPML. And would it need to have seperte hosting and a seperate site or can this be done by something like IP redirect. Can someone advise if this is good practice or maybe suffer other ways? Thanks in advance.
International SEO | | nezona1 -
International SEO - Targeting US and UK markets
Hi folks, i have a client who is based in italy and they set up a site that sells travel experiences in the sout of Italy (the site currently sit on a server in Italy). The site has been set up as gTLDs: www.example.com They only want to target the US and the UK market to promote their travel experiences and the site has only the english version (the site does not currently offer an italian version). If they decide to go for the gTLDs and not actually change to a ccTLDs (which would be ideal from my point of view) how are the steps to be taken to set this up correctly on GSC? They currently only have one property registered on GSC: www.exapmple.com therefore i guess the next steps are: Add new property - www.example.com/uk and and set up geo targeting for UK Existing property - www.example.com/ set up geo targeting for US In case the client does not have the budget to optimise the content for american and british languages, would still make sense to have 2 separate property in GSC (example.com for US market and example.com/uk for UK market)? Few considerations: Add canonical tag to avoid duplicate content across the two versions of the site (in the event there is no budget to optimise the content for US and UK market)? Thank you all in advance for looking into this David
International SEO | | Davide19840 -
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 -
Need help with search results for US site for a compnay that has many international sites
I am tasked with optimizing a US site for a company that has many international sites. Currently, if you search for just the main company name and don't include "USA" in your search, it won't even give you the US site on the SERP. It displays the Italian, French, etc etc sites - even though I'm searching on Google in the US with a preferred language of Engilsh. Unfortunately I don't have any control over the other sites, only the US one. Is there anything I can add to the US site (aside from setting the country code in GSC) so that when someone searches from within the USA, they get the US site and not all of the other ones? thanks!
International SEO | | SEOIntouch0 -
Website Migration
Are there any SEO issues with fdmgroup.com that I should address? We recently migrated to a new website redesign. Thanks.
International SEO | | fdmgroup0 -
Anchor text for international SEO
HI I am looking to rank sites in multiple foreign search engines. I am thinking about the anchor text strategies I need to employ. My key phrase: golfschläger (golf club) I am targeting a German page (written in German). Would Google understand that if I use the anchor text “golf club” to my German “golfschläger” page, it is infact the same word and therefore give anchor text benefits to that page, or for anchor text benefits to pass does the anchor text have to be in the same language? thanks for any help!!!!
International SEO | | Turkey0 -
Internationally targetted subdomains and Duplicate content
A client has a site they'd like to translated into French, not for the french market but for french speaking countries. My research tells me the best way to implement this for this particular client is to create subfolders for each country. For ease of implementation I’ve decided against ccTLD’s and Sub Domains. So for example… I'll create www.website.com/mr/ for Mauritania and in GWT set this to target Mauritania. Excellent so far. But then I need to build another sub folder for Morocco. I'll then create www.website.com/ma/ for Morocco and in GWT set this to target Morocco. Now the content on these two sub folders will be exactly the same and I’m thinking about doing this for all French speaking African countries. It would be nice to use www.website.com/fr/ but in GWT you can only set one Target country. Duplicate content issues arise and my fear of perturbing the almighty Google becomes a possibility. My research indicates that I should simply canonical back to the page I want indexed. But I want them both to be indexed surely!? I therefore decided to share my situation with my fellow SEO’s to see if I’m being stupid or missing something simple both a distinct possibility!
International SEO | | eazytiger0