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 deal with rel=canonical when using POST parameters
Hi there,
On-Page Optimization | | mjk26
I currently have a number of URLs throughout my site of the form: https://www.concerthotels.com/venue-hotels/o2-academy-islington-hotels/256133#checkin_4-21-2024&checkout_4-22-2024&rooms_1&guests_2&artistid_15878:256133 This sends the user through to a page showing hotels near the O2 Academy Islington. Once the page loads, my code looks at the parameters specified in the # part of the URL, and uses them to fill in a form, before submitting the form as a POST. This basically reloads the page, but checks the availability of the hotels first, and therefore returns slightly different content to the "canonical" version of this page (which simply lists the hotels before any availability checks done). Until now, I've marked the page that has had availability checks as noindex,follow. But because the form was submitted with POST parameters, the URL looks exactly like the canonical one. So the two URLs are identical, but due to POST parameters, the content is slightly different. Does that make sense? My question is, should both versions of this page be marked as index,follow? Thanks
Mike0 -
Is the meta title written only for google (try to stuff in as many keywords as possible) or is there a user experience aspect as well?
Is the meta title written only for google (try to stuff in as many keywords as possible) or is there a user experience aspect as well?
On-Page Optimization | | whiteonlySEO0 -
Rel="canonical" at the same page
Hello Everyone!! We have a Joomla Site and in the template we have a php function that create the **link rel="canonical" **and in the href inserts the same page url. For example, if the we do a search and the url have some cookies. That Url is gonna be the **rel="canonical" **for that page. Is it working correctly? We need an advice to to set it up correctly! Thanks!
On-Page Optimization | | mycostaricalink0 -
What is the danger of adding rel="prev" and rel="next"...
Our search results pages are, unfortunately, heavily indexed by Google. While the long term plan is to replace these somehow with our product pages, in the short term we are doing all we can to improve things. One of our issues is that we don't have a canonical link or rel="next" or rel="prev" on these pages. Would like to add these to consolidate duplicate content as well as help Google drill down within these pages to crawl the links within them. The concern is... If ten people arrive at our site via: http://www.oursite.com/?goodstuff=puppies&page=1 and 10 people also arrive at our site via: http://www.oursite.com/?goodstuff=puppies&page=2 Would adding rel="next" and rel="prev" potentially have a damaging effect on us by removing one of these entry points and therefore removing 10 potential visitors? Or would it still show both links, but instead would show the canonical in both locations? In short, could adding these tags actually backfire? Thanks very much! Craig
On-Page Optimization | | TheCraig0 -
Photon for Wordpress experience
Has anyone tried switching on the Photon for Wordpress CDN/image caching feature? If so, did you experience any problems and have you noticed any improvements?
On-Page Optimization | | pugh0 -
Pagination on related content within a subject
A client has come to us with new content and sections for their site. The two main sections are "Widget Services" - the sales pages, and "Widget Guide" - a non-commercial guide to using the widgets etc. Both the Services and Guide pages contain the same pages (red widgets, blue widgets, triangle widgets), and - here's the problem - the same first paragraph. i.e. ======== Blue widget services Blue widgets were invented in 1906 by Professor Blue. It was only a coincidence that they were blue. We stock a full range of blue widgets, we were voted best blue widget handler at widgetcon 2013. Buy one now See our guide to blue widgets here Guide to blue widgets Blue widgets were invented in 1906 by Professor Blue. It was only a coincidence that they were blue. The thing about blue widgets as they're not at all like red widgets at all. For starters, they're blue. Find more information about our blue widgets here ======== In all of these pages, the first paragraph is ~200 words and provides a great introduction to the subject, and the rest of the page is 600-800 words, making these pages unique enough to justify being different pages. We want to deal with this by declaring each page as a paginated version of a two page article on each type of widget (using rel=prev/next). Our thinking is that Google probably handles introuctions/headers on paginated content in a sensible way. Has anyone experienced this before? Is there any issues on using rel="prev" and rel="next" when they're not strictly paginated?
On-Page Optimization | | BabelPR0 -
[HTML Gurus] Is the only nofollow = rel="nofollow"?
From my knowledge only way an HTML link is nofollow is using rel="nofollow". I was wondering if you have a link , is there anything you can put OTHER than rel="nofollow" within the <a></a>tags that make a link nofollow?
On-Page Optimization | | William.Lau0 -
Do you use <nofollow>and rel=nofollow?</nofollow>
I just read http://www.thoughtmechanics.com/does-nofollow-attribute-work-google-says-yes-studies-say-otherwise/ . Is it really better to avoid using nofollow for local links (from one site to itself)?
On-Page Optimization | | fleetway0