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
-
How to get a mobile thumbnail image next to the search result?
Hey! I noticed the last few months that a lot of google searches now show an image next to your result when on mobile. i managed to get my listing to show an image before but I made some changes to the image and site and can’t seem to get Google to ahow the new image (or any image). I’ve added the image to schema mark up and still no luck. Wouod ahyone have any advice on how to get the image picked up, or st least help increase the odds? The site is https://tourstoniagarafalls.com and you can see it on search (for me it shows on the bottom of page 1) for the keyword “Niagara Falls tours“. Thanks again!
On-Page Optimization | | Originaladam0 -
One more question about rel=canonical
I'm still trying to wrap my head around rel=canonical and its importance. Thanks to the community, I've been able to understand most of it. Still, I have a couple of very specific questions: I share certain blog posts on the Huffington Post. Here's an example: http://www.huffingtonpost.ca/cedric-lizotte/munich-travel-guide_b_13438956.html - Of course I post these on my blog as well. Here: http://www.continentscondiments.com/things-munich-classics/ - Obviously the HuffPo has a huge DA, and I'll never match it. However the original post is mine, on my blog, and not on the HuffPo. They wont - obviously - add a rel=canonical just for me and for the sake of it, they have a million other things to do. QUESTION: Should I add a rel=canonical to my own site pointing to the post on the HuffPost? What would be the advantage? Should I just leave this alone? I share blog posts on Go4TravelBlog too. Example: http://www.go4travelblog.com/dallmayr-restaurant-munich/ - but, once again, the original post is on one of my blogs. In this case, it's on another blog of mine: http://www.thefinediningblog.com/dallmayr-restaurant-in-munich/ QUESTION: Well it's pretty much the same! Should I beg Go4TravelBlog to add a rel=canonical pointing to mine? If they refuse, what do I do? Would it be better to add a rel=canonical from my site to theirs, or do I fight it out and have a rel=canonical pointing to my own post? Why? Thanks a million for your help!
On-Page Optimization | | cedriklizotte0 -
Should you 301, 302, or rel=canonical private pages?
What should you do with private 'logged in' pages from a seo perspective? They're not visible to crawlers and shouldn't be indexed, so what is best practice? Believe it or not, we have found quite a few back links to private pages and want to get the ranking benefit from them without them being indexed. Eg: http://twiends.com/settings (Only logged in user can see the page) 302 them: We can redirect users/crawlers temporarily, but I believe this is not ideal from a seo perspective? Do we lose the link juice to this page? 301 them: We can do a permanent redirect with a short cache time. We preserve most link juice now, but we probably mess up the users browser. Users trying to reach a private page while logged out may have issues reaching it after logged in. **Serve another page with rel=canonical tag: **We could serve back the home page without changing the URL. We use a canonical tag to tell the crawlers that it's a duplicate of the home page. We keep most of the link juice, and the browser is unaffected. Yes, a user might share that different URL now, but its unlikely. We've been doing 302's up until now, now we're testing the third option. How do others solve this problem? Is there a problem with it? Any advice appreciated.
On-Page Optimization | | dsumter0 -
Rel Canonical help
Is it possible to confirm this to me please? My understanding of the rel canonical tag was to tell google of duplicate content? so for instance product 1
On-Page Optimization | | TeamacPaints
www.ourdomain.co.uk/products/category/subcategory/theproduct1 Product 1a
www.ourdomain.co.uk/products/category/subcategory/theproduct1a same content just a different colour would be rel canonical'd to Product 1 as thats the main product, is my understanding correct? Now here is what I have discovered. www.ourdomain.co.uk/products/category/subcategory/theproduct1 has a rel canonical tag that reverts back to www.ourdomain.co.uk/products/ which isn't optimized as such its just a generic catalog page. This is inccorect and google will dismiss the actial product and revert to the generic catalog page? any help would be great.0 -
Rel = no follow?
I am redoing a clients website. They previous company that built it have a page with links linking back to over 30 articles on webmd Question is this doing any good for SEO and if I recreate, should these have the rel=no follow attribute?
On-Page Optimization | | scott315
Here is is current page http://www.forestparkdental.com/links/ Thanks0 -
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 -
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 -
Rel="canonical"
Can you tell me if we've implemented rel="canonical" properly? We want this to be our primary: http://www.autopartstomorrow.com/parts/6052317-r-econ-semi-met-brake-pads- while this would be duplicate and refer robots back to the URL above: http://www.autopartstomorrow.com/parts/6054284 We've added the following to both pages: <link rel="canonical" href="http://www.autopartstomorrow.com/parts/6052317-r-econ-semi-met-brake-pads- "/> Thanks
On-Page Optimization | | jonesatl0