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
-
Why Google is not indexing each country/language subfolder on the ranks?
Hi folks, We use Magento 2 for the multi-country shops (its a multistore). The URL: www.avarcas.com The first days Google indexed the proper url in each country: avarcas.com/uk avarcas.com/de ... Some days later, all the countries are just indexing / (the root). I correctly set the subfolders in Webmaster tools. What's happening? Thanks
International SEO | | administratorwibee0 -
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 -
Include mobile and international versions of pages to sitemap or not?
My pages already have alternate and hreflang references to point to international and mobile versions of the content. If I add 5 language desktop versions and 5 language mobile versions as https://support.google.com/webmasters/answer/2620865?hl=en explains, my sitemap will get bulky. What are the pros and cons for referencing all page versions in sitemap and for include just general (English/Desktop) version in sitemap?
International SEO | | poiseo0 -
International hreflang - will this handle duplicate content?
The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties?
International SEO | | ALLee1 -
Country-specific SEO
Hi, my client offers courses that whilst based in Manchester, England are mainly attended by people in countries such as Georgia, Libya and Nigeria etc. The people that attend the courses are fluent in English. We're looking at performing country-specific SEO and I have a few queries. The plan so far: Obtain TLD's in each target country. These TLD's would be hosted on the same server as the core site based in England. Option 1: Each TLD would be a microsite with content specific to the country including geo-signals, in English. Option 2: Each TLD would 301 redirect to the core site, i.e. example.sa redirects to example.com/sa/ and this country-specific section would have relevant geo-signals. So I have 3 questions at this point: 1. Most-all of the tips I have seen about country-specific SEO assume that the content should be translated to the native tongue although in this case, the audience are fluent English speaks. Does this make a difference? Is it okay to use English and still be able to rank in country-specific search engines? 2. Between options 1 & option 2 - which would be the optimum setup? 3. Last question, if we obtain the TLD's I hear that it's not necessary to also host that TLD in the target country, is this right? Thanks.
International SEO | | lokito0 -
Website Internal Search
Hi I'm looking for ‘location search’ functionality to cover an extensive range of global locations to help increase the visibility I have been looking to use Google Places functionality, which has an extremely broad list of locations Would anyone have any experience in using Google places to power their websites internal search as well as if there is a cost to integrate it and other factors to be aware of? Thanks Simon
International SEO | | simonsw0 -
Lightbox on Home Page for Geo-Targeting
Hi -- I have a client with various international versions of their site. By adding a lightbox to their U.S. home page enabling the user to select their preferred translation (and cookie them)....does this have any negative SEO implications? It seems like a better alternative than the splash page they were using, but just want to be sure. Thanks!
International SEO | | MedThinkCommunications0 -
Targeting specific Geographic areas. Use 1 large.Com or several smaller country specific TLDs?
Hi, I have a small number of exact match domains, both country specific TLDs and also the Generic TLD dot com and dot net. They are: ExactMatch**.Com**
International SEO | | Hurf
ExactMatch**.Net** ExactMatch**.Co.Uk**
ExactMatch**.Ca**
ExactMatch**.Co.Nz**
ExactMatch**.Co.Za** We have already successfully launched our UK site using the exact match .co.uk and this is currently number 2 in the UK SERPS for the Google, Yahoo and Bing. They are/will be niche specific classified ad sites, which are Geographically targeted by country (to Engish speakers in the main) and each region is likely to have a minumum of 2,000 unique listings submitted over the course of a year of so. My question (FINALLY) is this: Am I better to build one large global site (will grow to approx. 12,000 listings) using EXACTMATCH.Com with .com - targeting US users and then geo-targeted sub directories (ExactMatch.Com/Nz etc) - each sub dir targeted to the matching geographic area in webmaster tools, or use the ccTLDs and host each site in the country with perhaps (each site growing to approx 2,000 listings) I could use the ccTLDs just for marketing/branding onlyand redirect these to the specific sub directory of the .com site? I am aware that there is one main ccTLD that I cannot get .Com.Au (as I am not a resident of Australia - and it is already in use.) so I was wondering if the single site with .Com/AU/ etc might help me better target that country? If I use each ccTLD as separate sites I suppose I could use the largely redundant .net to target Australia? Your thoughts and advice would be most welcome. Thanks! An additional bit of intormation (or two) the .com is circa 2004. The product advertised is a reasonably bulky (perhaps 6kgs boxed) physical product and therefore the seller is unlikely to want to ship globally - will this make them shy away from a global site - even one divided into global sub sections? FYI Seller can specify in their listing Will Ship To ....... I would be open to looking at using the front page of the .Com site as a page which visitors select the country they wish to buy/sell on. (IF it is the general consensus that it is better to create one large site.) Consider also please how the end user is likely to percieve the benefits to them of one LARGE SITE versus TARGETED SITE - I know the .Com would be divided into geographic sub directories, but I am not sure if they won't see an additinal benefit to the ccTLD - Does this add a degree of reassurance and relevance that a .com/ccTLD cannot provide? I suppose I am biased by the fact that ebay use ccTLDs? Thanks again - and please forgive my tone which may suggest I am playing devil's advocate here. I am very torn on this issue.0