Is this the correct way of using rel canonical, next and prev for paginated content?
-
Hello Moz fellows,
a while ago (3-4 years ago) we setup our e-commerce website category pages to apply what Google suggested to correctly handle pagination.
We added rel "canonicals", rel "next" and "prev" as follows:
On page 1:
On page 2:
On page 3:
And so on, until the last page is reached:
Do you think everything we have been doing is correct?
I have doubts on the way we have handled the canonical tag, so, any help to confirm that is very appreciated!
Thank you in advance to everyone.
-
Fantastic, thank you Paul! Those links are very useful, and I might have already read those when I setup those canonicals (I jut forgot after a few years to have worked on that!)
I'll check them out carefully again
Appreciated your help and prompt reply
All the best,
Fabrizio
-
Yup, that's exactly correct - just the way you first proposed.
And if you want it straight from the horse's mouth, here's Google's own description of implementation best practice for your exact situation:
rel="next" and rel="previous" on the one hand and rel="canonical" on the other constitute independent concepts.Both declarations can be included in the same page.
For example, http://www.example.com/article?story=abc&page=2&sessionid=123 may contain:
Note the canonical for the page is self referential to the version of the page including the basic variable that defines the actual page, leaving out the more dynamic variable of sessionID - the same way you'd want to leave out the dynamic size or colour variables, for example, which are specific to only that visit.
From https://webmasters.googleblog.com/2011/09/pagination-with-relnext-and-relprev.html
With a big whack of followup confirmation in this discussion with Google Engineer Maile Ohye https://productforums.google.com/forum/#!msg/webmasters/YbXqwoyooGM/0XTh-gIxS7YJDon't forget you can also use the tools in GSC to help GoogleBot understand which of your URL variables are indexable and which should be ignored. Only helps Google itself, but hey, every little bit counts
Good luck!
Paul
-
Thank you Paul, so, what I have been doing so far is correct, right? Here it is again, please, confirm so I can close this thread:
On page 1:
On page 2:
On page 3:
And so on, until the last page is reached:
Is this the correct way to do it then?
-
You want to have each of your paginated category pages include a self-referential canonical tag, Fabrizo, for exactly the reason you mention - to protect the paginated pages from additional variables creating more dupe indexed pages.
Paul
-
Thank you for your reply, but I am sorry Logan, I am confused, you said:
Regarding your recent question about links, a self-referring canonical on those pages will handle that.
So, if I had to follow what you said above, I should add the following canonicals on these pages:
Page 1:
http://www.mysite.com/category/
Page 2:
http://www.mysite.com/category/?cp=2
Page 3:
http://www.mysite.com/category/?cp=3
But then you said that I don't have to put any canonicals except for the first page... so, I am confused... sorry!
Fact is, all pages may have extra parameters that could cause duplicates, therefore, how can I tackle that without adding a canonical on each page pointing to the "clean" URL without extra parameters? I hope you understand what I mean...
-
No, you do not need a canonical on any page other than page=1. Refer to Andy's set of examples above. What he laid out is exactly how I markup for pagination.
-
Thank you Logan.
So, even if I am on page 4, the canonical must points always to the root? I think I read somewhere that it should point to the page URL without the extra parameters like this:
http://www.mysite.com/category/?cp=4
Am I wrong?
-
Yes, you only need the canonical tag on the root (as a self-referring canonical) and on page=1 of your paginated URLs. Regarding your recent question about links, a self-referring canonical on those pages will handle that.
Example:
On this URL- http://www.mysite.com/category/?cp=4&orderby=title&view=list
Canonicalize to- http://www.mysite.com/category/
Hope that's helpful!
-
I am sorry, but I haven't received an answer to my last inquiry above, I can't close this thread.
-
Another question: what about links on those pages that can take the crawl to possible duplicate because of parameters added to the URL like:
http://www.mysite.com/category/?cp=4&orderby=title
http://www.mysite.com/category/?cp=4&orderby=title&view=list
etc.? That's probably why we added the canonical I talked about above.... your thoughts?
-
Sorry, it is my understanding I have to leave the canonical just on the first page, is that correct?
Thank you again.
-
Oh, thank you Andy and Logan! So, can I remove the canonical tag altogether?
Thank you so much!
All the best,
Fabrizio
-
I'm with Logan here, Fabrizio. Rel next & prev pagination removes the need to canonical as well. So it would look like this:
Page 1:
Page 2:
Page 3:
It's Google way of understanding that there are similar pages that you wish to lead visitors to.
-Andy
-
Hi,
You don't need the self-referring canonical tags on each of the paginated URLs. Other than that it looks good to go.
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
-
Taken a canonical off a page to let it rank with new unique content - what more can I do?
A week ago, I took a canonical off of a page that was pointing to the homepage for a very big, generic search term for my brand as we felt that it could have been harming our rankings (as it wasn't a true canonical page). A week in and our rankings for the term have dropped 7 positions out of page 1 and the page we want to rank instead is nowhere to be seen. Do I hang fire? As such a big search term, it's affecting traffic, but I don't want to make any rash decisions. Here's a bit more info: For arguments sake, let's call the search term we're going after 'Boots', with the URL where the canonical was placed of /boots. The canonical went to the root domain as we sell, well... boots. At the time, the homepage was ranking for Boots on page 1 and we wanted to change this so that the Boots page ranked for that term... all logical right? We did the following: Took off mentions of Boots from meta on the homepage and made sure it was optimised for on the boots page. Took the canonical off of /boots. Used GSC to fetch & ask Google to recrawl "/boots". Resubmitted the sitemap. Do I hang fire on running back to the safety of ranking for boots on the homepage? Do I risk keyword cannibalisation by adding the search terms back to the homepage?
Intermediate & Advanced SEO | | Kelly_Edwards0 -
Can cross domain canonicals help with international SEO when using ccTLDs?
Hello. My question is:** Can cross domain canonicals help with international SEO when using ccTLDs and a gTLD - and the gTLD is much more authoritative to begin with? ** I appreciate this is a very nuanced subject so below is a detailed explanation of my current approach, problem, and proposed solutions I am considering testing. Thanks for the taking the time to read this far! The Current setup Multiple ccTLD such as mysite.com (US), mysite.fr (FR), mysite.de (DE). Each TLD can have multiple languages - indeed each site has content in English as well as the native language. So mysite.fr (defaults to french) and mysite.fr/en-fr is the same page but in English. Mysite.com is an older and more established domain with existing organic traffic. Each language variant of each domain has a sitemap that is individually submitted to Google Search Console and is linked from the of each page. So: mysite.fr/a-propos (about us) links to mysite.com/sitemap.xml that contains URL blocks for every page of the ccTLD that exists in French. Each of these URL blocks contains hreflang info for that content on every ccTLD in every language (en-us, en-fr, de-de, en-de etc) mysite.fr/en-fr/about-us links to mysite.com/en-fr/sitemap.xml that contains URL blocks for every page of the ccTLD that exists in English. Each of these URL blocks contains hreflang info for that content on every ccTLD in every language (en-us, en-fr, de-de, en-de etc). There is more English content on the site as a whole so the English version of the sitemap is always bigger at the moment. Every page on every site has two lists of links in the footer. The first list is of links to every other ccTLD available so a user can easily switch between the French site and the German site if they should want to. Where possible this links directly to the corresponding piece of content on the alternative ccTLD, where it isn’t possible it just links to the homepage. The second list of links is essentially just links to the same piece of content in the other languages available on that domain. Mysite.com has its international targeting in Google Search console set to the US. The problems The biggest problem is that we didn’t consider properly how we would need to start from scratch with each new ccTLD so although each domain has a reasonable amount of content they only receive a tiny proportion of the traffic that mysite.com achieves. Presumably this is because of a standing start with regards to domain authority. The second problem is that, despite hreflang, mysite.com still outranks the other ccTLDs for brand name keywords. I guess this is understandable given the mismatch of DA. This is based on looking at search results via the Google AdWords Ad Preview tool and changing language, location, and domain. Solutions So the first solution is probably the most obvious and that is to move all the ccTLDs into a subfolder structure on the mysite.com site structure and 301 all the old ccTLD links. This isn’t really an ideal solution for a number of reasons, so I’m trying to explore some alternative possible routes to explore that might help the situation. The first thing that came to mind was to use cross-domain canonicals: Essentially this would be creating locale specific subfolders on mysite.com and duplicating the ccTLD sites in there, but using a cross-domain canonical to tell Google to index the ccTLD url instead of the locale-subfolder url. For example: mysite.com/fr-fr has a canonical of mysite.fr
Intermediate & Advanced SEO | | danatello
mysite.com/fr-fr/a-propos has a canonical of mysite.fr/a-propos Then I would change the links in the mysite.com footer so that they wouldn’t point at the ccTLD URL but at the sub-folder URL so that Google would crawl the content on the stronger domain before indexing the ccTLD domain version of the URL. Is this worth exploring with a test, or am I mad for even considering it? The alternative that came to my mind was to do essentially the same thing but use a 301 to redirect from mysite.com/fr-fr to mysite.fr. My question is around whether either of these suggestions might be worth testing, or am I completely barking up the wrong tree and liable to do more harm than good?0 -
Rel=canonical on pre-migration website
I have an e-commerce client that is migrating platforms. The current structure of their existing website has led to what I would believe to be mass duplicate content. They have something north of 150,000 indexed URLs. However, 143,000+ of these have query strings and the content is identical to pages without any query string. Even so, the site does pretty well from an organic stand point compared to many of its direct competitors. Here is my question: (1) I am assuming that I should go into WMT (Google/Bing) and tell both search engines to ignore query strings. (2) In a review of back links, it does appear that there is a mish mash of good incoming links both to the clean and the dirty URLs. Should I add a rel=canonical via a script to all the pages with query strings before we make our migration and allow the search engines some time to process? (3) I'm assuming I can continue to watch the indexation of the URLs, but should I also tell search engines to remove the URLs of the dirty URLs? (4) Should I do Fetch in WMT? And if so, what sequence should I do for 1-4. How long should I wait between doing the above and undertaking the migration?
Intermediate & Advanced SEO | | ExploreConsulting0 -
Should I be using meta robots tags on thank you pages with little content?
I'm working on a website with hundreds of thank you pages, does it make sense to no follow, no index these pages since there's little content on them? I'm thinking this should save me some crawl budget overall but is there any risk in cutting out the internal links found on the thank you pages? (These are only standard site-wide footer and navigation links.) Thanks!
Intermediate & Advanced SEO | | GSO0 -
Is a Rel Canonical Sufficient or Should I 'NoIndex'
Hey everyone, I know there is literature about this, but I'm always frustrated by technical questions and prefer a direct answer or opinion. Right now, we've got recanonicals set up to deal with parameters caused by filters on our ticketing site. An example is that this: http://www.charged.fm/billy-joel-tickets?location=il&time=day relcanonicals to... http://www.charged.fm/billy-joel-tickets My question is if this is good enough to deal with the duplicate content, or if it should be de-indexed. Assuming so, is the best way to do this by using the Robots.txt? Or do you have to individually 'noindex' these pages? This site has 650k indexed pages and I'm thinking that the majority of these are caused by url parameters, and while they're all canonicaled to the proper place, I am thinking that it would be best to have these de-indexed to clean things up a bit. Thanks for any input.
Intermediate & Advanced SEO | | keL.A.xT.o0 -
Duplicate content within sections of a page but not full page duplicate content
Hi, I am working on a website redesign and the client offers several services and within those services some elements of the services crossover with one another. For example, they offer a service called Modelling and when you click onto that page several elements that build up that service are featured, so in this case 'mentoring'. Now mentoring is common to other services therefore will feature on other service pages. The page will feature a mixture of unique content to that service and small sections of duplicate content and I'm not sure how to treat this. One thing we have come up with is take the user through to a unique page to host all the content however some features do not warrant a page being created for this. Another idea is to have the feature pop up with inline content. Any thoughts/experience on this would be much appreciated.
Intermediate & Advanced SEO | | J_Sinclair0 -
Content not indexed
How come i google content that resides on my website and on my homepage and my site doesn't come up? I know the content is unique i wrote that. I have a feeling i have some kind of a crawling issue but cannot determine what it is. I ran the crawling test and other tools and didn't find anything. Google shows me that pages are indexed but yet its weird try googling snippets of content and you'll see my site isnt anywhere. Have you experienced that before? First i thought it was penalized but i submitted the reconsideration request and it came back clear, No manual spam action found. And i did not get any message in my GWMT either. Any thoughts?
Intermediate & Advanced SEO | | CMTM0 -
Rel="prev" and view all question
Okay, I've read the posts by Google about the new prev, next tags and the suggestion for using a view all option. I've also read the posts here on SEOMoz on the topic but none of them quite address what we have. First, Some of our main categories are very large (over 6000 pieces of jewelry) so a view all option would take forever to load be completely useless to a visitor. Second, our category home pages provide (here's an example😞 A description of the category with links to important sections and articles A row of new items A dozen of the popular items from the category. Links to related articles if applicable. So we have a real category home page with content instead of just categories that start immediately with pages of product. Should we set the canonical url for all of the browse pages to the main category page, create a view all page or just use the next and previous rel tags with the category home pages as the first in the series?
Intermediate & Advanced SEO | | IanTheScot0