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
-
Important pages are being 302 redirected, then 301 redirected to support language versions. Is this affecting negatively the linking juice distribution of our domain?
Hi mozzers, Prior to my arrival, in order to support and better serve the international locations and offering multiple language versions of the same content the company decided to restructure its URLs focused on locale urls. We went from
International SEO | | Ty1986
https://example.com/subfolder to https://example.com/us/en-us/new-subfolder (US)
https://example.com/ca/en-us/new-subfolder (CAN)
https://example.com/ca/fr-ca/new-subfolder (CAN)
https://example.com/de/en-us/new-subfolder (Ger)
https://example.com/de/de-de/new-subfolder (Ger) This had implications on redirecting old URLs to new ones. All important URLs such as https://example.com/subfolder were
302 redirected to https://example.com/us/en-us/subfolder and then 301 redirected to the final URL. According to the devs: If you change the translation to the page or locale, then a 302 needs to happen so you see the same version of the page in German or French, then a 301 redirect happens from the legacy URL to the new version. If the 302 redirect was skipped, then you would only be able to one version/language of that page.
For instance:
http://example.com/subfolder/state/city --> 301 redirect to {LEGACY URL]
https://example.com/subfolder/state/city --> 302 redirect to
https://example.com/en-us/subfolder/state/city --> 301 redirect to
https://example.com/us/en-us/new-subfolder/city-state [NEW URL] I am wondering if these 302s are hurting our link juice distribution or that is completely fine since they all end up as a 301 redirect? Thanks.1 -
International SEO & Duplicate Content: ccTLD, hreflang, and relcanonical tags
Hi Everyone, I have a client that has two sites (example.com & example.co.uk) each have the same English content, but no hreflang or rel="canonical" tags in place. Would this be interpreted as duplicate content? They haven't changed the copy to speak to specific regions, but have tried targeting the UK with a ccTLD. I've taken a look at some other comparable question on MOZ like this post - > https://moz.com/community/q/international-hreflang-will-this-handle-duplicate-content where one of the answers says **"If no translation is happening within a geo-targeted site, HREFLANG is not necessary." **If hreflang tags are not necessary, then would I need rel="canonical" to avoid duplicate content? Thanks for taking the time to help a fellow SEO out.
International SEO | | ccox10 -
International SEO Mobile directory
I was wondering, What if I went with international sub-directory route (not ccTLD), for example: sitename.com/fr (fr being france)...But the question is, what's the best practice for MOBILE?sitename.com/mobile/frORsitename.com/fr/mobileORm.sitename.com/fr Again, ccTLD is not an option (currently, sites are in ccTLD but we are now transitioning to sub folders)Now, the next question is WHY is it best practices for it to be sitename.com/mobile/fr or sitename.com/fr/mobile or m.sitename.com/fr ? Please cite source. Thanks!
International SEO | | ggpaul5620 -
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 -
Multi-Country Duplicate Content
Hello, We have an ecommerce site that serves several countries on the same .com domain - US, UK and CA. We have duplicate content across these countries because they are all English speaking so there is little variance in the pages and they each sell most of the same products. We have implemented hreflang into our sitemaps but we need to address the duplicate content. We were advised to canonicalize our UK and CA pages back to the duplicate US pages (our US pages account for the majority of our traffic and sales). This would cause the UK and CA pages to fall out of the index but the visitor would still be taken to the correct country's page due to the hreflang. I'm leary about doing this because they are across countries. Is this ok to do? If not, how do we address the duplicate content since they are not on their own CCTLD's?
International SEO | | Colbys0 -
Moving webserver to another country and downtime
Hi all, We are going to move our server location to another country, and our webpage will be down for about 24 hours. Is there anything that I should be aware of with SEO while doing this?
International SEO | | helgeolaussen
Any way to tell SE that our site will be down, without having alot of errors in Webmaster tools etc? Best regards, Ceran0 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
SEO for different English spiking countries
Hi, I'm trying to target my SEO to several English spiking countries (Canada, UK, Australia, South Africa and so..) and I came across a big dilemma: should I tray to build a local version of my website for each country, or perhaps I should stay with my one .COM website and re-direct all the English-local-countries with 301 (if anyone will tray to go into the local domain)? The thing is that obviously the best practice to get high ranking is to be local, but what should I put in those sites and who can I avoid duplicate content and user confusion? On the other hand, do you think I can really get high ranking with one website for all those countries, and how? Thanks, Itay Drory.
International SEO | | RAN_SEO0