Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Canonical or hreflang?
-
I have four English sites for four different countries, UK, Ireland, Australia and New Zealand and I want to share some content between the sites. On the pages that share the content, which is essentially exactly the same on all 4 sites, do I use the hreflang tags like:
or do I add a canonical tag to the other three pointing to the "origin", which would be the UK site?
I believe it is best practice to use one or the other, but I'm not sure which make sense in this situation.
-
Hello!
I found one amazing article about Canonicals and Hreflangs for International Store. It might be helpful. -
I feel like my question isn't being understood here.
I understand the difference between the two and if the sites were for example English and Spanish I would get which to use, but the hreflang tag sub-divides languages into individual regional variants, in my case en-GB, en-IE, en-AU and en-NZ.
So, my question is which to use when the "base" language is the same, so in all essence, the article is basically identical, with the odd regional spelling variation, e.g. colour and color, tossed in?
-
Canonical tags are used to signal the official version of a URL whereas hreflang tags are used to match the correct piece of content to region-specific users speaking another language. However, it's important to remember that the hreflang attribute and canonical tags are just signals or hints and are not directives.
-
In this case I'll choose Hreflang because work in differents languages.
-
So, you are saying to use both which seems to be contrary to all the articles I've read about this, which seem to suggest you should only use one or the other, but never really talk about this particular scenario.
-
you canoncial every page by defualt and hreflang it
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
-
Quick Fix to "Duplicate page without canonical tag"?
When we pull up Google Search Console, in the Index Coverage section, under the category of Excluded, there is a sub-category called ‘Duplicate page without canonical tag’. The majority of the 665 pages in that section are from a test environment. If we were to include in the robots.txt file, a wildcard to cover every URL that started with the particular root URL ("www.domain.com/host/"), could we eliminate the majority of these errors? That solution is not one of the 5 or 6 recommended solutions that the Google Search Console Help section text suggests. It seems like a simple effective solution. Are we missing something?
Technical SEO | | CREW-MARKETING1 -
Robots.txt in subfolders and hreflang issues
A client recently rolled out their UK business to the US. They decided to deploy with 2 WordPress installations: UK site - https://www.clientname.com/uk/ - robots.txt location: UK site - https://www.clientname.com/uk/robots.txt
Technical SEO | | lauralou82
US site - https://www.clientname.com/us/ - robots.txt location: UK site - https://www.clientname.com/us/robots.txt We've had various issues with /us/ pages being indexed in Google UK, and /uk/ pages being indexed in Google US. They have the following hreflang tags across all pages: We changed the x-default page to .com 2 weeks ago (we've tried both /uk/ and /us/ previously). Search Console says there are no hreflang tags at all. Additionally, we have a robots.txt file on each site which has a link to the corresponding sitemap files, but when viewing the robots.txt tester on Search Console, each property shows the robots.txt file for https://www.clientname.com only, even though when you actually navigate to this URL (https://www.clientname.com/robots.txt) you’ll get redirected to either https://www.clientname.com/uk/robots.txt or https://www.clientname.com/us/robots.txt depending on your location. Any suggestions how we can remove UK listings from Google US and vice versa?0 -
Spanish United States Vs Puerto Rico Hreflang
Hey Moz, So we are trying to figure out weather it is the same if we have Hreflang for "US-ES" vs "US-PR", IF we do "US-PR" for Puerto Rico for its own links we then have to create 3 parts to our site, PR Spanish PR English US Spanish We looked at Apple as an example and they had a "Latin America" for their Hreflang and labeled everything has either "es-419" is that the same concept as having just "us-es" for Puerto Rico? ( see attached screenshot ) We are trying to figure out what would be more effective and weather or not "US-ES" search results will appear for Puerto Rico also. PZVwg16
Technical SEO | | uBreakiFix0 -
Rel Canonical, Follow/No Follow in htaccess?
Very quick question, are rel canonical, follow/no follow tags, etc. written in the htaccess file?
Technical SEO | | moon-boots0 -
Hreflang Tag great for Google, what about Bing or others?
I've read that the Hreflang Tag is all the rave for International solutions on a per page basis. I haven't read much about what International agencies are using for non-Google search engines such as Bing. Is the common language meta tags the only solution? would love to see an article that addresses this
Technical SEO | | MikeSEOTruven0 -
Duplicate title-tags with pagination and canonical
Some time back we implemented the Google recommendation for pagination (the rel="next/prev"). GWMT now reports 17K pages with duplicate title-tags (we have about 1,1m products on our site and about 50m pages indexed in Google) As an example we have properties listed in various states and the category title would be "Properties for Sale in [state-name]". A paginated search page or browsing a category (see also http://searchengineland.com/implementing-pagination-attributes-correctly-for-google-114970) would then include the following: The title for each page is the same - so to avoid the duplicate title-tags issue, I would think one would have the following options: Ignore what Google says Change the canonical to http://www.site.com/property/state.html (which would then only show the first XX results) Append a page number to the title "Properties for Sale in [state-name] | Page XX" Have all paginated pages use noindex,follow - this would then result in no category page being indexed Would you have the canonical point to the individual paginated page or the base page?
Technical SEO | | MagicDude4Eva2 -
Screaming From occurences and canonicals what does it all mean
Bonjourno from Wetherby UK... Ive used a package called screamong frog to diagnose canonical errors but can anyone tell me what this means? http://i216.photobucket.com/albums/cc53/zymurgy_bucket/understand-occurances-canonical.jpg Thanks in advance. David
Technical SEO | | Nightwing0 -
Hreflang on non-canonical pages
Hi! I've been trying to figure out what is the best way to solve this dilemma with duplicate content and multiple languages across domains. 1 product info page 2 same product but GREEN
Technical SEO | | LarsEriksson
3 same product but RED
4 same product but YELLOW **Question: ** Since pages 2,3,4 just varies slightly I use the canonical tag to indicate they are duplicates of page 1. Now I also want to indicate there are other language versions with the_ rel="alternate" hreflang="x" _element. Should I place the _rel="alternate" hreflang="x" _on the canonical page only pointing to the canonical page with "x" language. Should I place the _rel="alternate" hreflang="x" _on all pages pointing to the canonical page with the "x" language? Should I place the _rel="alternate" hreflang="x" _on all pages and then point it to the translated page (even if it is not a canonical page) ? /Lars0