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
-
Can I use rel="alternate" language tags on multiple domains?
On a page with the domain "www.example-1.com.br" (for pt-BR) I will include the following tags: That will work?
International SEO | | Ewerton.RD0 -
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 -
Is this setup of Hreflang xml sitemap correct?
Hi, I'm trying to setup hreflang for 2 domains. One is purely a US site and the other domain has the language-country as subdomains. For example: http://www.websiteUSA.com (Targets English - USA) https://www.websiteINT.com/en-CA (Targets English - Canada) https://www.websiteINT.com/fr-CA (Targets French - Canada) https://www.websiteINT/es (Targets Spanish) ..and so on and so forth for about 12 of these international URLs. I created an XML sitemap that looks something like this: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>http://www.websiteUSA.com</loc></url></urlset> <url><loc>https://www.websiteINT.com/en-CA</loc></url> <url><loc>https://www.websiteINT.com/fr-CA</loc></url> Question 1: Is this correct? In my actual file, I have all the countries listed and self-referencing. Question 2: I'm hosting this file at https://www.websiteINT.com/hreflang.xml AND at http://www.websiteUSA.com/hreflang.xml. Is this correct? Question 3: Will this help the SERPs direct english speakers from the US to http://www.websiteUSA.com while show SERPs for say English Speakers in Canada to https://www.websiteINT.com/en-CA? Question 4: For some reason, when I put up the xml site, it only listed each URL once instead of the full XML file. Should I have uploaded a text file instead? It doesn't seem to render correctly. Thank you!
International SEO | | SylviaH0 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
"Hreflang=x" tag and multinational websites
Hello, We have multiple websites targeted at multiple countries and languages, each with the correct country extension. We have a corporate blog for each of these websites, where the blogs are subdomains of the main website. Currently we have a process of rewriting our blog posts completely – while keeping the same subjects – in order to have original content on each of our blogs, although we have up to 3 blogs in the same language. These are the languages we target: French – FRANCE French – SWITZERLAND French – BELGIUM Italian – ITALY Italian – SWITZERLAND German – GERMANY German – SWITZERLAND German – AUSTRIA Spanish – SPAIN Spanish – COLOMBIA Spanish – PANAMA Czech – CZECH REPUBLIC Swedish – SWEDEN Dutch – BELGIUM / NETHERLANDS English – UK English – INTERNATIONAL The process is obviously very tedious, and not always applied rigorously – i.e. some of the texts are posted on 2-3 different blogs, creating duplicate content.
International SEO | | ESL_Education
The questions : Would there be any reason for us to privilege the use the rel="canonical" tag over the "hreflang=x" tag, thus giving privilege to a "master" version for each language? Are there any risks in using the "hreflang="x" tag for our blogs considering that the posts would be very similar, except for references to additional content? Could there be any risk that Google would consider our sites as duplicate content after all? Should we specify on each blog that we have all the above versions, or should we only specify the other markets versions in each language? For example, should we specify on our French, Swiss and Belgium blog that we have 3 different French versions, on our UK blog that we also have an international version, and so on, or should we list all versions on each of the blogs? Does the "hreflang="x" tag facilitate the indexation of each of the versions in the SERPs of their targeted market? Lastly, are there any precautions we should take in order to put this in place? Looking forward to your feedback. Best wishes, Maëlle0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
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 -
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