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
-
How do hreflang attributes affect ranking?
We have a site in English. We are considering translating the site into Dutch. If we use a hreflang attribute does that mean we have to create a duplicate page in Dutch for each English page, or does Google auto-translate? How would duplicate pages, even if they are in a different language, affect ranking?
International SEO | | Substance-create0 -
How should I handle hreflang tags if it's the same language in all targeting countries?
My company is creating an international version of our site at international.example.com. We are located in the US with our main site at www.example.com targeting US & Canada but offering slightly different products elsewhere internationally. Ideally, we would have hreflang tags for different versions in different languages, however, it's going to be an almost duplicate site besides a few different SKUs. All language and content on the site is going to be in English. Again, the only content changing is slightly different SKUs, they are almost identical sites. The subdomain is our only option right now. Should we implement hreflang tags even if both languages are English and only some of the content is different? Or will having just canonicals be fine? How should we handle this? Would it make sense to use hreflang this way and include it on both versions? I believe this would be signaling for US & Canda visitors to visit our main site and all other users go to the international site. Am I thinking this correctly or should we be doing this a different way?
International SEO | | tcope250 -
GeoIP Redirects & hreflang
Hello, We believe we've had some issues with hreflang tags not remaining validated due to the implementation of geoIP redirects. Previously, if a user clicked a landing page on Google search that was not targeted for their territory, they would instantly be redirected to a sub path that targets their territory using geoIP redirects. We're planning to remove the initial geoIP redirects and have messaging that prompts the user to either stay on the page they've landed on, or be redirected to page that is right for their territory. However, if a user has selected to be redirected to a sub path that is targeted for their territory, they will have a cookie preference set for the IP location they've selected, and will continue to be redirected to their chosen sub path. My question is, will a crawler follow and trigger the geo preference cookie, which could potentially cause complexities in validating hreflang tags and ranking of content for the right market. Thanks.
International SEO | | SEONOW1230 -
Hreflang for selected pages?
My English site example.com has 1300 Pages I have launched a Russian transasation of the site example.ru This site has only 20 pages so far. Doubt: I need to set hreflang for all 1300 pages or only for 20 Pages of example.com that are converted to russian? Due to the limitations of the plugins avaialable I need to MANUALLY set hreflang for all 1300 pages of example.com Please guide
International SEO | | Janki990 -
Why would a site lose rankings in U.S while maintaining rankings in other English locations (Canada & Australia)
What would cause a site to lose ranking in the U.S while maintaining top (1st page) positions in other English results countries such as Canada or Australia? Is this purely penguin related because of location of backlinks or are there other significant factors that could be in play? Would this rule out Panda as a cause because it's simply an "English language" targeted algo and not location dependent like backlinks (penguin)? Appreciate any insights
International SEO | | ResumeGenius0 -
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 -
Which hreflang tag to use for .eu domain
Hi there, We're trying to solve a problem with one of our domains, we have a .eu CCTLD and we're trying to implement hreflang tags. On our US and UK sites, we use "en-us" and "en-gb", but it's not clear how to approach this european problem, as there is not a "en-eu" tag. The site is in English, but serves several European countries speaking different languages. What's the best hreflang code to use in this situation? Any help much appreciated, Thanks!
International SEO | | dennis.globalsign0 -
International SEO with .com & ccTLD in the same language
I've watched http://www.seomoz.org/blog/intern... and read some other posts here. Most seem to focus on whether to use ccTLD, subdomains or subfolders. I'm already committed to expanding my US-based ecommerce to Canada with a .ca ccTLD. My question is around duplicate content as I take my .com USA ecommerce business to canada with a second site on a .ca URL. With the .com site's preference set to USA, and the .ca site's geo preference (automatically) set to Canada, is it a concern at all? About 80% of the content would be the same. FYI, .com ranks OK in Canada now and I want .ca to outrank it in Canada. I know 'localizing' content within the same language is important (independent of duplicate content), but this might not be viable in the short run given CMS limitations. Any direct experience to help quantify the impact here between US and Canadian ecommerce? Adding: I'm not totally confident here. From this google webmaster central post it seems that canonical tags aren't needed. I tend to think nothing is truly neutral and want to be confident regarding whether to use canonicals or not. Is it helpful, harmful or harmless? My site already has internal canonical tags and having internal and external would be a pain I think. @Eugene Byun used it successfully, but would the results have been the same without? Thanks!
International SEO | | gravityseo0