International SEO - Hreflang tags and URL Structure
-
Hello, I wonder if any SEO internationalisation experts can help.
We are a UK centric business with a .com domain which all our traffic currently goes to. We have been growing in the US and are therefore looking to internationalise our website by building out some US pages using the subfolder .com/us.
Since the keywords we wish to target in the US are different to the keywords we are targeting elsewhere, when implementing hreflang tags is it possible to use a different URL for the US page?
So let’s say we are targeting ‘estate car’ generally but want to target ’station wagon’ as the keyword for the equivalent US page, can the URLs be different?
Example:
- General page: www.example.com/estate-car
- US: www.example.com/us/station-wagon
Hreflang tags:
Would that be the correct implementation?
Any help or guidance would be much appreciated!
-
Thanks for your thoughtful reply.
Great - that makes sense. I will add en-gb hreflang markup too.
You raise some really good points about organisations having to think clearly about the need to undertake multi-regional / multi-lingual SEO and the potential implications of this. In our situation we've come to the conclusion that there is a business case to undertake this venture. When I joined there was already a US office and a few pages written for the US already published on our website in a different design language. Fortunately these pages were recently created and set not to allow crawling. If they were to be indexed at best they may not rank and at worst they may actually interfere with our other page rankings - as well as causing confusion for users (duplicate product / contact / client pages, different navigation structures, designs etc). In the end we decided the best approach would to be to internationalise our website and target these pages to the region / language they were designed for. But yes definitely has been a challenge!
-
In your original post, you wrote that you are a "UK-centric business". I would think you would want to be as specific as possible to make sure the search engines know to serve the most relevant pages to the UK audience. So, yes, I would definitely include a self-referencing hreflang tag. It also simplifies your process because you can just copy-and-paste the hreflang tags between the versions of the page, with no editing (you put the same exact set of tags on the British page as you do on the American).
However, I'm really only responding to your "how" question. There is also an implicit question of whether you should be doing this. I have to say that from recent experience, no matter how thorough we are with hreflang tags, the search engines inevitably serve up pages across the desired locales. For my brand, I have Australian links showing up in US searches, and US links showing up in British searches, etc. This is even with correct hreflang implementation. In our case, it is a necessity to have multiple localized sites, because we carry different inventory, at different prices, and with different policies in each region. But if that wasn't the case, I would not localize my site between US, British, and Australian English just for language variances. That is a subjective decision, but I have so many problems coming from the wrong pages being served in the wrong geographies, despite thorough hreflang tagging, that I would be very hesitant to create more localizations than absolutely necessary. This wasn't your question, I realize, and also this is purely subjective, but passing along for consideration.
-
Great - thanks for your response.
So we should include x-default markup on the relevant pages (in addition to en-us hreflang tags) to signal to the search engines to show the .com urls to those who do not have the browser language setting set to US-English and the .com/us urls to those who do?
If we don't have specific UK pages do we need to add href lang en-gb markup since x-default covers it?
-
You would want the exact same hreflang tags on both versions of each page. So, that means each has a self-referencing tag, plus an alternate tag pointing to the sister page in another locale, plus an x-default tag. The hreflang tags basically tell the search engines whcih version of the page is appropriate for which locales, and when they are on a page in one locale, it tells the search engine where it can find the equivalent pages for other locales, as well as which one is the "x-default" for any locales you haven't specified.
-
Thanks for your quick reply seoelevated! We don't actually have any specific UK pages at the moment. The main site (written in British English) is www.example.com and is where all our traffic currently goes. We have decided to build specific US pages at subfolder www.example.com/us.
I presume in this scenario it would be good practice to add x-default markup on the .com while adding hreflang en-us to the US pages?
-
Yes, that looks correct. However, I would suggest adding two more hreflang tags to each page. One for "en-gb" (pointing to your UK desired version) and one for "x-default" (pointing to whichever version you would prefer for any other nonspecified locales. You will want all 4 of these on each of the two pages (so each page would include a self-referencing tag. These 2 additional ones are optional, but I think would provide a bit more clear direction to the search engines about which page to present for which locales.
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
-
NoIndex tag, canonical tag or automatically generated H1's for automatically generated enquiry pages?
What would be better for automatically generated accommodation enquiry pages for a travel company? NoIndex tag, canonical tag, automatically generated H1's or another solution? This is the homepage: https://www.discoverqueensland.com.au/ You would enquire from a page like this: https://www.discoverqueensland.com.au/accommodation/sunshine-coast/twin-waters/the-sebel-twin-waters This is the enquiry form: https://www.discoverqueensland.com.au/accommodation-enquiry.php?name=The+Sebel+Twin+Waters®ion_name=Sunshine+Coast
Technical SEO | | Kim_Lazaro0 -
My translated pages are categorized as subpages of the originals / Importance of hreflang tags
Hi there We have a website that is originally in German, but has an English translation for all pages.
Technical SEO | | Jess_Smunch
I recently created a crawl map for it, which showed that all our translated pages are indexed as subpages of the German originals. I wonder if this is normal, or if it will have a negative impact on our SEO. If they are subpages, will Google still index and rank them with the same importance as the originals?
If not, what can I do to make them standalone pages and not subpages? Also, we have a few issues with hreflang tags that we cannot fix easily as our CMS does not give us a flexible option for editing our code. I wonder how much impact hreflang tags have on our ranking and if we can just disregards these issues? We use Hubspot as a CMS, if that matters. Thanks for your feedback!0 -
Changing site URL structure
Hey everybody, I'm looking for a bit of advice. A few weeks ago Google sent me an email saying all pages with any text input on them need to switch to https for those pages. This is no problem, I was slowly switching the site to https anyway using a 301 redirect. However, my site also has a language subfolder in the url, mysite.com/en/ mysite.com/ru/ etc. Due to poor work on my part the translations of the site haven't been updated in a long time and lots of the pages are in english even on the russian version etc. So I'm thinking of just removing this url structure and just having mysite.com My plan is to 301 all requests to https and remove the language subfolder in the url at the same time. So far the https switching hasn't changed my rankings. Am I more at risk of losing my rankings by doing this? Thanks!
Technical SEO | | Ruhol0 -
URL / sitemap structure for support pages
I am creating a site that has four categories housed in folders off of the TLD. Example: example.com/category-1
Technical SEO | | InterCall
example.com/category-2
example.com/category-3
example.com/category-4 Those category folders contain sub-folders that house the products inside each category. Example: example.com/category-1/product-1
example.com/category-2/product-1
etc. Each of the products have a corresponding support page with technical information, FAQs, etc. I have three options as to how to structure the support pages' URLs. Option 1 - Add new sub-folder with "support" added to string: example.com/category-1/product-1-support Option 2 - Add a second sub-folder off of the product sub-folder for support: example.com/category-1/product-1/support Option 3 - Create a "support" folder with product sub-folders: example.com/support/product-1 Which of these three options would you choose? I don't like having one large /support folder that houses all products. It seems like this would create a strange crawling and UX situation. The sitemap would have a huge /support folder with all of my products in it and the keywords in my category folders would be replaced with the word "support." Because I would rather have the main product pages ranking over any of the support pages (outside of searches containing the word "support"), I am leaning toward Option 2: example.com/category-1/product-1/support. I think this structure indicates to crawlers that the more important page is the product page, while the support page is secondary to that. It also makes it clear to users that this is the support page for that particular product. Does anyone have any experience or perspective on this? I'm open to suggestions and if I'm overthinking it, tell me that too. Thanks, team.0 -
Multilingual Structure
Hello fellow SEO fans, I've got a setup that I'm interested in some opinions on. I have a website which has the following setup: www.site.com (english version of the site) www.site.com/nl (dutch version of the site) Now, my experience tells me the dutch version would be written in dutch (not using Google Translate) and the meta data et al should also be in dutch. But my question is: If somebody in, say, Netherlands perform a search in english for a specific keyword, we would want the www.site.com page to appear in the SERPs, not the www.site.com/nl page, because the person has searched in english. However, because there's a www.site.com/nl page, purely the /nl page will be optimized and linked to in order to rank it higher in the SERPs for dutch searches and not english searches? But if that's the case, then the person in the Netherlands searching for the english version of the keyword, probably won't see www.site.com in the ranks because of targeting and keyword distribution? Bit of a tricky situation that I've been pondering over and can't quite put the nail on the head. Any assistance would be appreciated.
Technical SEO | | ChristopherM0 -
Formatting dynamic urls?
We have a long-time previously well-established website that was hit by panda. On one section of the site, we have dynamic urls that include %20 in them (e.g. North%20America). It's recently come to our attention that google has both a version of the url with a plus sign (+) and the version with the %20 (space) (e.g. North+America). Upon researching this, it seems that a hyphen (-) is preferable to either of the above. We obviously need to remove the %20's from the urls as they can cause issues. So, should we stick with the + sign since it's already indexed and ranking or do a 301 rewrite and change them all to hyphens instead of the plus sign? This is the one section of the site that has maintained rankings through the panda debacle, so we need to take that into consideration as we don’t want to lose the rankings that we have. Along the same lines, we have two other sections of the site that provide search results as well, though these are all formatted to use a plus sign. Is it advisable to do a 301 rewrite to change the plus signs to hyphens on these as well or just leave them alone? This particular section has lost rankings over the last year with panda updates.
Technical SEO | | Odjobob0 -
Optimal Structure for Forum Thread URL
For getting forum threads ranked, which is best and why? site.com**/topic/**thread-title-goes-here site.com**/t/**thread-title-goes-here site.com**/**thread-title-goes-here I'd take comfort in knowing that SEOmoz uses the middle version, except that "q" is more meaningful to a human than "t". The last option seems like the best bet overall, except that users could potentially steal urls that I may want to use in the future. My old structure was site.com/forum/topic/TOPIC_ID-thread-title-goes-here so obviously any of those would be a vast improvement, but I might as well make the best choice now so I only have to change once.
Technical SEO | | PatrickGriffith0 -
Canonical tags and internal Google search
Quick question: I want some pages that will have canonical tags, to show up in internal results for a Google site search that's built into the site. I'm not finished with the site, but is it correct to assume that pages with canonical will NOT show up in internal site search results, when powered by Google?
Technical SEO | | EricPacifico0