Pagination with rel=“next” and rel=“prev”
-
Hey mozzers
Would be interested to know if anyone has used the rel=“next” and rel=“prev” attributes more info here http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
If you have used it, has it worked and what are your thoughts etc:?
And for those that have used it, is it a better way of handling pagination other than the obvious of Google saying so.
Thanks
-
Hey Craig,
We implemented it recently and saw immediate effect within 24 hours. Google indexed our priority landing pages, and our paginated pages were offered up as effectively 'sitelinks'.
In effect we got one of our landing pages ranking No.1 on a strong keyword phrase, and we gained 4 extra paginated links just below the meta description.
Seems to be the best way to handle pagination.
Truly awesome, and very happy.
Croozie.
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 To Implement Pagination Properly? Important and Urgent!
I have seen many instructions but I am still uncertain. Here is the situation We will be implementing rel prev rel next on our paginted pages. The question is: Do we implement self referencing canonical URL on the main page and each paginated page? Do we implement noindex/follow meta robots tag on each paginated page? Do we include the canonical URL for each paginated page in the sitemap if we do not add the meta robots tag? We have a view all but will not be using it due to page load capabilities...what do we do with the viewl all URL? Do we add meta robots to it? For website search results pages containing pagination should we just put a noindex/follow meta robots tag on them? We have seperate mobile URL's that also contain pagination. Do we need to consider these pages as a seperate pagination project? We already canonical all the mobile URL's to the main page of the desktop URL. Thanks!
Intermediate & Advanced SEO | | seo320 -
Quick Rel Canonical Link Juice Question
Let's say I have two duplicate pages, A and B. However, A has 5 external links and B has 3 _different _external links. If I add the rel canonical tag to B, so that A is the "master page" do I also lose whatever link juice was going to B from the 3 external links?
Intermediate & Advanced SEO | | KempRugeLawGroup0 -
Yoast & rel canonical for paginated Wordpress URLs
Hello, our Wordpress blog at http://www.jobs.ca/career-resources has a rel canonical issue since we added pagination to the front page and category-pages. We're using Yoast and it's incorrectly applying a rel-canonical meta tag referencing page 1 on page 2, 3, etc. This is a known misuse of the rel-canonical tag (per Google's Webmaster Blog - http://googlewebmastercentral.blogspot.ca/2013/04/5-common-mistakes-with-relcanonical.html, which says rel-canonical should be replaced with rel-prev and rel-next for page 2, 3, etc.). We don't see a way to specify anywhere in Yoast's options to correct this behaviour for page 2, 3, etc. Yoast allows you to override a page's canonical URL, otherwise it automatically uses the Wordpress permalink. My question is, does anyone know how to configure Yoast to properly replace rel-canonical tags with rel-prev and rel-next for paginated URLs, or do I need to look at another plugin or customize the behavior directly in my child theme code? This issue was brought up here as well: http://moz.com/community/q/canonical-help, but the only response did not relate to Yoast. (We're using Wordpress 3.6.1 and Yoast "Wordpress SEO" 1.4.18)
Intermediate & Advanced SEO | | aactive0 -
Rel Next and Previous on Listing Pages of Blog
Hi, Need to know does rel next and previous is more appropriate for content based articles and not blog listings.. Like an article spread across 3 pages - there it makes sense for rel next and previous as the content of the article is in series However, for blog listing page, for pages 1, 2, 3, 4 where every page is unique as the blog has all independent listings or separate articles - does rel next and previous wont of much help Our blog - http://www.mycarhelpline.com/index.php?option=com_easyblog&view=latest&Itemid=91 This is what been said by the developer "The whole idea of adding the "next" and "previous" tag in the header is only when your single blog post has permalinks like: site.com/blog/entry/blog-post.html
Intermediate & Advanced SEO | | Modi
site.com/blog/entry/blog-post.html?page=1
site.com/blog/entry/blog-post.html?page=2 " The link in the head is only applicable when your content is separated into multiple pages and it doesn't actually apply on listings. If you have a single blog post that is broken down to multiple pages, this is applicable and it works similarly like rel="canonical" Can we safely ignore rel next and previous tag for this blog pagination for the listing pages !!0 -
How Long Does it Take for Rel Canonical to De-Index / Re-Index a Page?
Hi Mozzers, We have 2 e-commerce websites, Website A and Website B, sharing thousands of pages with duplicate product descriptions. Currently only the product pages on Website B are indexing, and we want Website A indexed instead. We added the rel canonical tag on each of Website B's product pages with a link towards the matching product on Page A. How long until Website B gets de-indexed and Website A gets indexed instead? Did we add the rel canonical tag correctly? Thanks!
Intermediate & Advanced SEO | | Travis-W0 -
URL Going Over the Last Page of Pagination - Post Webinar Discussion
**Discussion Question: **Lets say you have 33 pages of paginated content but someone lands on page 34+, what do you do? I just setup a variable on my site so when someone lands on a page that is over the page count they are redirected to the last page of the paginated content. My reasoning is the user is looking for the last page, so why not redirect them to it? Now I just saw in the latest webinar on ecommerce (by Everett Sizemore) that he recommends a 404… should I switch? Why a 404? Again, what do you guys do when you encounter this situation?
Intermediate & Advanced SEO | | BeTheBoss0 -
Use of rel=canonical to view all page & No follow links
Hey, I have a couple of questions regarding e-commerce category pages and filtering options: I would like to implement the rel=canonical to the view all page as suggested on this article on googlewebmastercentral. If you go on one of my category pages you will see that both the "next page link" and the "view all" links are nofollowed. Is that a mistake? How does nofoolow combines with canonical view all? Is it a good thing to nofollow the "sorty by" pages or should I also use Noindex for them?
Intermediate & Advanced SEO | | Ypsilon0 -
Use rel=canonical to save otherwise squandered link juice?
Oftentimes my site has content which I'm not really interested in having included in search engine results. Examples might be a "view cart" or "checkout" page, or old products in the catalog that are no longer available in our system. In the past, I'd blocked those pages from being indexed by using robots.txt or nofollowed links. However, it seems like there is potential link juice that's being lost by removing these from search engine indexes. What if, instead of keeping these pages out of the index completely, I use to reference the home page (http://www.mydomain.com) of the business? That way, even if the pages I don't care about accumulate a few links around the Internet, I'll be capturing the link juice behind the scenes without impacting the customer experience as they browse our site. Is there any downside of doing this, or am I missing any potential reasons why this wouldn't work as expected?
Intermediate & Advanced SEO | | cadenzajon1