Should Hreflang x-default be on every page of every country for an International company?
-
UPDATED 4/29/2019 4:33 PM
- I had made to many copy and pastes. Product pages are corrected
Upon researching the hreflang x-default tag, I am getting some muddy results for implementation on an international company site older results say just homepage or the country selector but….
My Question/Direction going forward for the International Site I am working on: I believe I can to put x-default all the pages of every country and point it to the default language page for areas that are not covered with our current sites. Is this correct?
From my internet reading, the x-default on every page is not truly necessary for Google but it will be valid implemented.
My current site setup example:
https://www.bluewidgets.com Redirects to https://www.bluewidgets.com/us/en (functions as US/Global)Example Countries w/ code Site:- 4 countries/directories US/Global, France, Spain
Would the code sample below be correct?
-
https://www.bluewidgets.com/us/en/ (functions as US/Global)
-
US/Global Country Homepage - https://www.bluewidgets.com/us/en/
-
US/Global Country Product Page(s) This would be for all products - https://www.bluewidgets.com/us/en/whizzer-5001/
-
http://www.bluewidgets.com/us/en (functions for France)
-
France Country Homepage - https://www.bluewidgets.com/fr/fr/
-
France Country Product Page(s) This would be for all products- https://www.bluewidgets.com/es/es/whizzer-5001
-
http://www.bluewidgets.com/us/en (functions as Spain)
-
Spain Country Homepage - https://www.bluewidgets.com/es/es/
-
Spain Country Product Page(s) This would be for all products - https://www.bluewidgets.com/es/es/whizzer-5001
Thanks for the spot check
- Gravy
-
Yes, your understanding of x-default is correct. The purpose of including it everywhere you have alternate HREFLANG links, is to handle any locales you don't explicitly include (to tell the search engine which is the default version of the page for other non-specified locales). And it should be included on each version of the page, along with the other specified alternate links for each locale. Alternatively, you could collect all of these centrally into the sitemap file, rather than inserting into each page. Both types of implementation are valid (but anecdotally I've had better luck with on-page tags instead of sitemap implementation).
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
-
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 targeting
I'm offering an international service to any country from any destination, The website main language is English and i have 4 other languages as subdirectories, https://beassistance.com https://beassistance.com/de/ https://beassistance.com/es/ https://beassistance.com/fr/ https://beassistance.com/ru/ I'm looking to target by language not country, Should i choose "unlisted" for all the subdirectories? my second question regards the meta tags , my current meta tag rel="alternate" hreflang="ru-ru" href="https://beassistance.com/ru/" /> And i'm thinking about using rel="alternate" hreflang="ru" href="https://beassistance.com/ru/" /> Is that best practice to target by the language? Update I already have Hreflang Sitemap <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" <br="">xmlns:xhtml="http://www.w3.org/1999/xhtml">
International SEO | | MTBE
<url><loc>https://beassistance.com</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url></urlset> <url><loc>https://beassistance.com/de/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/fr/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/es/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/ru/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url>1 -
Hreflang problem?
Hello, We do have a client with a site in multiple versions (one domain per country). French and Spanish versions work really fine, but the problem comes up with the .com and .co.uk versions. This is my hreflang piece of code: When I go to Google.co.uk and search the exact match domain keyword "how much cost an app", I only find the howmuchcostanapp.com domain (1st or 2nd page) instead of howmuchcostanapp.co.uk. The UK one is not appearing! This is very strange. I have spent a lot of time trying to solve this, but I don't know what else to do. Thanks a lot in advance for your comments and help!
International SEO | | Yeeply.com0 -
Targeting Countries in the Middle East
Hi guys, I have a client based in the Middle East using a generic top level domain (.com), and they want to target multiple countries in the GCC (UAE, Saudi Arabia, Kuwait, Qatar etc). I’m thinking that using the hreflang tag would be the best solution here, however the pages will mostly have the exact same content. There will only be slight changes on some pages in terms of using localised title tags [client service] followed by [targeted country], h1's and meta descriptions. Is this the correct approach? And if so should this be implemented side wide or can it be implemented on selected pages only? The site will be in English only.
International SEO | | Jbeetle0 -
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
International SEO | | mlehr0 -
Canonical and hreflang mess of international desktop and mobile site versions
Hello, I have an interesting case and I am lost in it. There are two versions of the site: desktop and mobile. And there are also international versions: English and Spanish. I'm stuck at implementation of canonical tags. Currently my setup has the following: English (default) desktop page has these: English Mobile page has these: Spanish Desktop version: Spanish Mobile version: But I somewhat feel that I messed the things... Could you guys point me to what I did wrong and explain how to set it right? Also, if you know URLs of blog posts or articles, where similar case is explained - share with me please.
International SEO | | poiseo0 -
Targeting International Markets on the Web
Hello Moz community, I have a popular news website that we are looking to target multiple countries (all English first). So I know (1) a hosting provided (ip address) in that country and (2) a target extension (.co.uk) will help us. Am I missing anything else that can help when targeting international markets? What I'm struggling with is the duplicate content. I can't copy the content over to the extension because of the bad practice of duplicate content. Is it possible to have the same content on both websites and let Google know that it lives at the .com extension? If so, would those websites containing duplicate content still rank? And we would want to target different languages later (for example Spanish). This would be different content because it is in a different language, correct? Thanks for your help Moz community! Cole
International SEO | | ColeLusby0 -
Are Subdomains better or SubDirectories better for an international website ?
Can anyone explain why the structure of your website: yourbrand.com/es/category is better than es.yourbrand.com for multi language and multi country website.
International SEO | | Tushar_P0