Experiences with pagination rel=next and prev
-
I have read about people saying that using the rel next and prev tags did not take any positive effect on their sites...
In my case I do not have a typical pagination 1,2,3 but a site about tours in the amazon where each tour-description is divided into a page with
- an overview,
- itinerary,
- Dates & Prices
so instead of Site 1,2,3 Buttons I have the Btns: Tour Overview, Itinerary, Prices
So as all the of pages belong together I thought the rel=next & prev tags will be useful.
Also I want to avoid duplicate content when the page title of the three is pretty similar. Right now the Title is like this:
Amazon Tour XXX YYYY
Amazon Tour XXX - itinerary
Amazon Tour XXX - pricesThe description text is more different...
Is this the best practice in my case?
Thanks for all your opinions!
best regards,
Holger -
Hi Everett,
thanks a lot you your input!
Holger
-
Having looked at the site I can see that the content is more than unique and useful enough. Great job on that!
By using "rel next / prev" in this way you are giving Google the signal that you want the first page (i.e. rio-negro-amazonas-regenwald-expedition-uebersicht.php ) to rank higher than the other two pages for most searches, but that the other pages are unique and should stay indexed. If this is what you intend then I think it is a great plan. However, if all of the pages are equally important, and if each has its own search terms to target, it may be better to let the subsequent pages stand on their own.
It sounds like this is working for you at the moment. Thank you for sharing your findings with us!
-
Hi Everett,
yes you are right, the URLs have their own self-referencing rel canonical.
The URLs are:Rio Negro Expedition
Overview-Page:
http://www.amazonasabenteuer.de/amazonas-expeditionen/rio-negro-amazonas-regenwald-expedition-uebersicht.phpItinerary-Page:
http://www.amazonasabenteuer.de/amazonas-expeditionen/rio-negro-amazonas-regenwald-expedition-reiseablauf.phpDates & Prices Page:
http://www.amazonasabenteuer.de/amazonas-expeditionen/rio-negro-amazonas-regenwald-expedition-reisedaten-preise.php -
Thank you for sharing your direct experience with this strategy.
Do all of these URLs share the same rel canonical tag, or do they each have their own self-referencing rel canonical? I am assuming they each have their own if they are all showing up for searches.
It would really help if you could share the domain so we could have a look. However, as long as the content on each page is not "thin" and is mostly unique to that page I think this strategy would be fine.
-
Hi Everett,
thanks for answering. I also thought just using one page but each subject gets pretty long so using pagination with rel=next / prev as I also want to "indicate the relationship between component URLs" seems to be the best practice in this case.
I'm also using the canonical tag... so the otherway round, what could be a negative effect in my case? I put now one tour online and I can't see any negative effect. The pages have been indexed and google shows them up for my keywords.
I was hoping that somebody has done experiences and can talk about. At this moment I have no negative effects about this practice and a would recommend it.
-
Hello Holger,
I apologize for the wait on this. We rely on the community to help answer questions, but sometimes nobody is able to help out in a timely manner so we answer them ourselves as well.
I do not think rel next/prev is the best solution for the situation described. I think the best practice would be to have all of that content on one page. You could change the view of the content (such as when someone clicks the "itinerary" tab) by adding a hash symbol (#) to the URL (e.g. amazon-tour/#itinerary amazon-tour/#prices) to avoid duplicate content issues and make the landing page more robust and useful. You might combine this with the use of a rel canonical tag for that page.
Please let me know if you still need assistance with this question. Again, sorry about the wait!
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
-
The correct way to rel=canonical
When adding the rel=canonical tag to a landing page inside a folder, should the tag read: or With or without the index.php? TY KJr
On-Page Optimization | | KevnJr1 -
Is there a limit to the number of duplicate pages pointing to a rel='canonical ' primary?
We have a situation on twiends where a number of our 'dead' user pages have generated links for us over the years. Our options are to 404 them, 301 them to the home page, or just serve back the home page with a canonical tag. We've been 404'ing them for years, but i understand that we lose all the link juice from doing this. Correct me if I'm wrong? Our next plan would be to 301 them to the home page. Probably the best solution but our concern is if a user page is only temporarily down (under review, etc) it could be permanently removed from the index, or at least cached for a very long time. A final plan is to just serve back the home page on the old URL, with a canonical tag pointing to the home page URL. This is quick, retains most of the link juice, and allows the URL to become active again in future. The problem is that there could be 100,000's of these. Q1) Is it a problem to have 100,000 URLs pointing to a primary with a rel=canonical tag? (Problem for Google?) Q2) How long does it take a canonical duplicate page to become unique in the index again if the tag is removed? Will google recrawl it and add it back into the index? Do we need to use WMT to speed this process up? Thanks
On-Page Optimization | | dsumter0 -
Pagination for product page reviews
Hi, I am looking to add pagination on product pages (they have lots of reviews on the page). I am considering using rel="next/prev, to connect the series of review pages to the main product page. I unfortunately don't have a view-all page for these reviews or the option to get one - the reviews refresh on the same product page (by clicking whatever number page of reviews). This means each page has the exact same description content and everything else, but with different reviews. In this case is rel=next a good option? The format currently would be: On example.com/product link rel="next" href="http://example.com/product?review-p2" On example.com/product?review-p2 link rel="prev" href="http://example.com/product, link rel="next" href="http://example.com/product?review-p3 etc. Would this be a good format for product page reviews? I see rel=nextprev commonly used on ecommerce category/list pages but not really on the paginated reviews on product pages, so I thought I would see if anyone has advice on how best to solve this. I'm also wondering if it would be best to not combine this with a canonical tag on all the different review pages pointing to the product page, seeing as the reviews are actually different (despite the rest of the content being identical). I am hoping to pick up longer tail traffic from this, I figure by connecting the pages and not using canonicals that this way I could get more traffic from the phrases used in the reviews. By leaving out the canonicals, is it possible a user searching for phrases that might be deeper in the series, to land on, say, ?review-p4? Any thoughts if this would drive more traffic? Thanks!.
On-Page Optimization | | pikka0 -
Is Rel=Canonical the answer???
Hey Mozzers, Can you help me with something please. I have some important content going live next week for a client. We work on there blog optimisation and this piece of content is going live on both the blog and parent site. The parent site has huge DA in comparions to the blog. I want to get the traffic directed to the blog and get the blog ranking - bare in mind the content is exactly the same so it is dupe. If I want to get the blog ranking above the parent site and to direct the traffic here is a cross domain Rel=Canonical the answer? Has anyone else had this issue? Thanks Bush
On-Page Optimization | | Bush_JSM0 -
Which pages should use rel="canonical" links?
I have many pages showing up as multiple content. Most of the them belong to product pages for my store, login pages that show up everywhere on the site, etc. I know that I need to use the rel=canonical link in the header but after searching the forum I'm still unsure of what pages need it. Is it the pages that I don't want searched/crawled by Google or the other way around? Thanks! Crystal
On-Page Optimization | | COfashionista0 -
Should I worry about duplicate titles on pages where there is paginated content?
LivingThere.com is a real estate search site and many of our content pages are "search result" - ish in that a page often provides all the listings that are available and this may go on for multiple pages. For example, this is a primary page about a building: http://livingthere.com/building/31308-Cocoa-Exchange Because of the number of listings, the listings paginate to a second page: http://livingthere.com/building/31308-Cocoa-Exchange?MListings_page=2 Both pages have the same Page Title. Is this a concern? If so is there a "best practice" for giving paginated content different titles? Thanks! Nate
On-Page Optimization | | nate1230 -
SEO and Pagination on search results
Hi Our new site is still in beta mode, and I just wanted to check from an SEO perspective that on search results and on the pagination at the bottom of the page, is there anything we need to do so its compatible with the search engines and not have duplicate content issues etc I have implemented search friendly URL's, but I would welcome any other issues or suggestions you have that will help improve the sites SEO performance The URL of a search results page is http://www.cheapfindergames.com/category-arcade-and-platform
On-Page Optimization | | ocelot0