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 -
Help with international targeting
Hi all! Okay, so we've got a site, let's say example.com - we sell training courses worldwide with a particular focus in just 8 countries.
International SEO | | JamieM1611
Historically, we've never targeted users in different countries effectively, we've just got the example.com that floats about ranking in different countries, but our content is dynamic (obviously a big SEO no-no - we pick up the IP of the user and show the content relevant for that country without the URL's changing)
This obviously presents an SEO flaw in that we can effectively target people in our key countries effectively. So, we're introducing the targeting as subfolders (/uk/, /ie/ etc) my questions are: 1. Would this be the correct implementation of hreflang AND canonical tags for the URL: https://www.example.com/es/ 2. The second thing I was wondering is the 'international targeting' in search console. We haven't (because of our current set up) set a target country for www.example.com (because of the lack of regional targeting and dynamic catch all) - would we be better leaving that untargeted and only specifying the regional targets for the new subfolder URLs (www.example.com/us/ /uk/ etc) or should we set the .com as the USA as default? We'd be a bit weary of doing this because most of our traffic comes from the UK and South Africa, so I'm assuming it would be best to leave this alone unless someone else has a different opinion? I know Googlebot almost always crawls .coms from US, which is why we were thinking of leaving the .com as the 'catch all' and specifying the US version. 3. Finally, we do have a lot pages which don't really change at all (like the about us page) would we give these any special directives to avoid duplicate content (as the content on these won't be changing at all?) or do we just keep the structure as shown above? I.E would the about us page (even though not changing) still be (with the canonical): URL: https://www.example.com/about-us/ (x-default) ? Thanks in advance!0 -
International SEO - Alternatives to Automatic IP re-direct
Hello, When doing international SEO I've read that it's not good practice to automatically re-direct users to the correct part of the website based on their IP address. But what alternatives are there to this? Let's say you're targeting the US and the UK through multiregional SEO. What can you do to ensure that users from the US go to the US sub-directory and that users from the UK go to the UK sub-directory? In Moz's international SEO guide it says that: "If you choose to try to guess at the user’s language preference when they enter your site, you can use the browser’s language setting or the IP address and ask the user to confirm the choice. Using JavaScript to do this will ensure that Googlebot does not get confused. Pair this with a good XML sitemap and the user can have a great interaction. Plus, the search engines will be able to crawl and index all of your translated content." Can anyone explain this further? Any help would be much appreciated! Thanks in advance
International SEO | | SEOCT0 -
Internal Links Not Registering
Hey everybody. In Moz when I compare link profiles to my competitors my domain is showing up as only having 4 internal follow links, and 0 nofollow. I know for a fact this is not the case however it is disconcerting. Is there any reason why Moz wouldn't be able to pick up my internal links? Is there a difference when linking internally by "/page_a" vs actually spelling out the entire URL i.e. "https://www.mysite.com/page_a"
International SEO | | HashtagHustler0 -
International SEO Proposal
Hi, I need to create an international seo proposal and wondered what are the best bits of international SEO I should include? I have been reading up on loads of blogs wondered if anyone had some great ideas 🙂 Much appreciated.
International SEO | | karl621 -
International SEO
Anyone have any good free resources for international SEO best practices? I've read through most of the common stuff and wondered if there's anything I'm missing. We are getting ready to launch a version of our website in the UK and I could use any hints or advice that could make my life easier. My biggest question is whether to keep the sites as 1 site (single domain with sub-folder for sharing incoming link profile) or to get a .UK domain and do everything from scratch. (it seems like a sub-domain is not the way to go?). I also wonder if any of you can share things to look out for, pitfalls, mistakes, etc...? TIA for any help/answers!
International SEO | | DownPour0 -
Is it a bad idea to use characters with accents or graves within URLs?
Is there an issue using within the URL for a page words with accents or graves, for example including "Estándares"? Thanks Stuart
International SEO | | mcvicar0