Hreflang Alternate & Pagination
-
Hi everybody,
So I'm setting up hreflang tags on an ecommerce site. The sites are in the USA and Canada. The Canadian site will have fewer products than the American site, meaning that there won't be as many pages in each category as there are on the American site. What is the correct way to handle hreflang tags on these extra category pages?
To put this another way, the American site may have a category with 3 pages of products, while the Canadian equivalent only has 2 pages of products. What happens to this extra American category page (example.com/widget-category/page-3) ?
Does it get an hreflang tag linking to the first page of the equivalent Canadian category (example.ca/widget-category/)?
Does it not get any hreflang tags because it has no true Canadian counterpart?
Does it matter at all if it has a canonical tag pointing to the first page in the series anyway (example**.com**/widget-category/)?
Thanks,
Andrew B.
-
Canonicals and hreflangs must be treated separately.
My rule, and this what I said at LearnInbound, from where SEMRush tweeted the tweet you embedded in your post, is this:
-
First set up and/or solve all canonicalization issues your site may have;
-
Once you have solved the canonicalization issues, you can work on implementing the hreflang only on canonical URLs (not canonicalized)
In that case of pagination the pages 1, 2, 3, 4, et al have self-referential rel="canonical", so - ideally - the hreflang must reference to the corresponding pages 1, 2, 3, 4, et al of the same pagination in the other country and/or language version.
Finally, you are correct regarding the "view all" being the canonical URL of a paginated series.
-
-
You are right. I didn't know about the right way to paginate with canonical. But the point about Hreflang stands. Don't use Hreflang and canonical together on the same page. If you are using canonical to point to the "View All" version, then use Hreflang on the "View all" versions, and not on the individual pages.
-
"Page-2 and Page-3 on the US site should use rel canonical to point to US Page-1. And Page-2 on CA site should use rel canonical to point to Page-1 on CA."
Sorry to say, but this is wrong. Having this configuration will lead the Googlebot to not index or follow anything on page-2 or page-3 because only page-1 is the canonical page. Use either canonical to "page-all" (if existent) or rel="prev"/"next" (sometimes useful with Robots-Tag with noindex,follow for page-2, page-3 ...)
See > Mistake 1: rel=canonical to the first page of a paginated series
https://webmasters.googleblog.com/2013/04/5-common-mistakes-with-relcanonical.html# -
Don't use canonical and hreflang together. I blogged about this very issue: https://hreflang.org/use-hreflang-canonical-together/
What this means for you is that even for Page-2 (for both US and CA), if you are using rel canonical to say that Page-2 is a duplicate of Page-1, then do not use hreflang on Page-2. Using both canonical and hreflang on page-2 will only confuse Googlebot.
In your case, only use hreflang on the canonical versions of the page. i.e., Page-1 on both US and CA sites should point to each other using hreflang. Page-2 and Page-3 on the US site should use rel canonical to point to US Page-1. And Page-2 on CA site should use rel canonical to point to Page-1 on CA.
-
That makes perfect sense! Thanks Gianluca (hope to see you at Mozcon again this year btw!).
-
The example.com/widget-category/page-3 URL cannot have as href in its hreflang="en-CA" the example.ca/widget-category/page-1 because also this other URL - example.com/widget-category/page-1 - has that Canadian URL as href (moreover, that is the correct href for its hreflang="en-CA").
Hence, if you follow your first idea, you will be having a URL (the canadian first page of the paginated list) that will have two different hreflang annotations ( <rel="alternate" href="example.com/widget-category/page-1" hreflang="en-US">and <rel="alternate" href="example.com/widget-category/page-3" hreflang="en-US">, which is totally uncorrect, because you are telling Google to use two URLs for English speaking users in the USA, instead of one.</rel="alternate"></rel="alternate">
Sincerely I wouldn't worry that much. If you are using the rel="prev"/"next", Google will consider the third page of the US listing as a all with the first two pages, hence it should not start showing it in the index.
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
-
When should hreflang be deployed in this situation; now or later ?
Hi I have a question in regard to point 1 in Gianluca Fiorelli first comment on Aleyda Solis old but great international targeting article in regard to hreflang: https://moz.com/blog/using-the-correct-hreflang-tag-a-new-generator-tool it would obvs be amazing if either Gianlucca or Aleyda can answer but if anyone else feels they can do so confidently then that would be great too 🙂 I'm advising someone in similar situation as that (their main brand is USA based on a .com showing up in UK searches too) and they have launched .co.uk sites (without any seo) to target UK brand searches, so obviously the .com is still dominating UK serps for brand, and the .co.uk is ranking on page 4 on average for a brand search. **BUT **before I tell them to roll out hreflang shouldn't they build up some authority etc first for their new country specific (.co.uk) site ? since they are very new and have no authority or even basic SEO and don't rank higher than page 4 for brand searches (the .com is in no1 in both usa and uk). I know hreflang needs to be used correctly here but im not sure when it should be, now or later (after authority has built up for the new uk focused sites) ? In other words I take it deploying the hreflang correctly wont simply cause these home pages to swap positions for brand search in uk (or will it) ? Im worried deploying it immediately could actually destroy the brands current page 1 serps for brand term (since will remove the .com page from the uk serp). Hence i take it its best to build up the new .co.uk sites seo/authority etc first and at least get that sites brand ranking moving up the listings before deploying hreflang on the .com, to then hopefully remove the .com listing in place of the .co.uk for brand ? OR does Gianlucca point in his comment suggest that correct hreflang usage on both sites should swap the high authority .com no1 position with the low authority .co.uk for a brand search ? Many Thanks Dan
International SEO | | Dan-Lawrence0 -
When should hreflang be deployed in this situation; now or later ?
HiI have a question in regard to point 1 in Gianluca Fiorelli first comment on Aleyda Solis old but great international targeting article in regard to hreflang: https://moz.com/blog/using-the-correct-hreflang-tag-a-new-generator-toolit would obvs be amazing if either Gianlucca or Aleyda can answer but if anyone else feels they can do so confidently then that would be great too :)I'm advising someone in similar situation as that (their main brand is USA based on a .com showing up in UK searches too) and they have launched .co.uk sites (without any seo) to target UK brand searches, so obviously the .com is still dominating UK serps for brand, and the .co.uk is ranking on page 4 on average for a brand search.**BUT **before I tell them to roll out hreflang shouldn't they build up some authority etc first for their new country specific (.co.uk) site ? since they are very new and have no authority or even basic SEO and don't rank higher than page 4 for brand searches (the .com is in no1 in both usa and uk).I know hreflang needs to be used correctly here but im not sure when it should be, now or later (after authority has built up for the new uk focused sites) ?In other words I take it deploying the hreflang correctly wont simply cause these home pages to swap positions for brand search in uk (or will it) ? Im worried deploying it immediately could actually destroy the brands current page 1 serps for brand term (since will remove the .com page from the uk serp).Hence i take it its best to build up the new .co.uk sites seo/authority etc first and at least get that sites brand ranking moving up the listings before deploying hreflang on the .com, to then hopefully remove the .com listing in place of the .co.uk for brand ?OR is Gianlucca saying in his comment that correct hreflang usage on both sites should swap the high authority .com no1 position with the low authority .co.uk for a brand search ?Many ThanksDan
International SEO | | Dan-Lawrence0 -
Is it compulsory to use hreflang attribute for Multilingual site? What if I do not use such tag?
Hello Everybody, My main site - abcd.co.uk and other sites are like this se.abcd.co.uk, fr.abcd.co.uk, es.abcd.co.uk etc Now if I donot use hreflang for Multilingual site then google will consider it as subdomain or duplicate site? But content of the sites are in different language. Thanks!
International SEO | | wright3350 -
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 -
External URLs in hreflang sitemap questions
I'm currently putting together an international sitemap for a website that has an set up like the following: example.com/us
International SEO | | Guyboz
example.com/au
example.com/ca
example.co.uk
example.se I'm planning on including the hreflang tags within sitemaps for each domain, to make sure google serves up the right version. However, I'm a bit sceptical about including the non .com domains within the .com sitemap - and the other way round for .co.uk and .se sitemaps. The way I've been doing it follows the following example: <url><loc>http://www.example.com/us/</loc></url> Putting in the .co.uk and .se domains within the .com sitemap just doesn't feel right - is this actually the right way to do it? Thanks in advance 🙂0 -
Google Analytics & Webmaster Tools Filtering
I've just set up a client who uses internationalization on Google Webmaster tools and Google Analytics. For easier management they opted to use subfolders rather than subdomains or cctlds. So I set up a Google Analytic Property, with one Unfiltered profile, and another 3 profiles filtered per language. With the main language English being exclude anything starting /fr/ /de/ as it resides on root. The filters seem to work fine; however after linking this to the Google Webmaster Account to be able to access Search Engine Optimization I do not seem to get any language filtered data. I was wondering if someone had any idea or possible solution to this problem. As I would expect to at least have the Landing Pages if not exactly the keywords filtered by the same criteria that the rest of the data is being filtered. I know there's also an option to create a separate webmaster tools account, however this way I still cannot filter just the English; and I cannot link it to all the separate profiles.
International SEO | | jonmifsud0 -
Is having duplicated content on different domains a problem when using alternate tag, but no canonical?
We will be launching a couple of new language versions. I understand that ccTLD is mostly considered as best option, however I thought that to start with it might be better to launch the new language version first on a subdirectory of our established domain with strong backlink profile as it may rank much better until I can attract some strong links to new ccTLD. I would wait for the pages of new language versions to be indexed on the main domain and then after a month launch the same content paralell on the ccTLD setting up an alternate tag in the main domain pointing to the ccTLD. I would not setup any canonical tag. As I understand google would rank whatever of the 2 versions ranks higher. Should not cause duplicated content issues right?
International SEO | | lcourse
Any thoughts? EDIT:
For clarification. The language we are launching are mostly spoken in several countries. E.g. for Portuguese I would add in main domain an altnernate tag for Brazilian visitors to Brazilian ccTLD, but no alternate tag for Portuguese visitors. For Corean I would add in main domain an alternate tag for visitors in south corea, but not one for visitors in north corea.0 -
Can I point some rel alternate pages to a 404?
Hi everyone, I'm just setting up a series international websites and need to use rel="alternate" to make sure Google indexes the right thing and doesn't hit us with duplicate content. The problem is that rel="alternate" is page specific, and our international websites aren't exact copies of the main UK website. We've taken out the ecommerce module and a few blog categories because they aren't relevant. Can I just blanket implement rel="alternate" and let it sometimes point to a 404 on the alternate websites? Or is Google going to find that a bit weird? Thanks,
International SEO | | OptiBacUK
James0