Pagination with parameter and rel prev rel next
-
Hi there:
I have a doubt about how using the pagination and rel prev | rel next, I will try to sum up this example of pagination:
the page number 1 is SEO friendly in order to index it, It also gets metarobots: index, follow.
The other ones (pagination), instead, have noindex, follow. In fact, these URLs are not SEO friendly because of they have the parameter "?" to set up pagination, so for this reason, in the past, It has been decided not to index them.
Would you suggest also to use rel="prev" rel="next" in this situation? Or would it be better to set up the others ones (pagination) in "SEO friendly" and then, to set up the rel prev | rel next?
Thanks a lot in advance for helping
Greetings
Francesca
-
Thank you very much!
Francesca
-
Ah... you're saying have a "View All" page but then not canonical to it? I guess my only concern about that is that then you've got another crawl path and possible duplicates. In that case, you might want to Noindex the "View All" and only have it available to users. It depends a lot on the scope of pages we're talking, as always.
-
I also agree with you, however if your view all page use more than acceptable time to load, I would still suggest having both a view all page and rel next/prev (but not the canonical aswell). By doing so you simply send your visitors hot your first page in the series, however maintaining the ability for users to view all the content.
-
Just one note here - I generally wouldn't use "View All" and rel=prev/next. It's a bit of a mixed signal. If you can create a friendly, fast-loading "View All" page, then rel=canonical the paginated URLs back to the "View All" page.
Agreed, though, that your Nofollow, Noindex is basically overriding the rel=prev/next. I've honestly heard mixed signals from people (including prominent SEOs who handle very large media sites) about how effective rel=prev/next is. I think Meta-robots is a stronger signal, so if you're really worried about duplicates, it's probably doing fine. If you want page 3 of 8 (for example) to rank for some reason, then rel=prev/next opens up that possibility, but it may also be a bit weaker cue in terms of duplication. It's a bit of a trade-off. If your currently approach is keeping pages out of the index, I'd probably leave it alone.
-
Hi Jørgen.
At the moment, I will apply rel ="prev" | rel="next" in order to set up pagination...currently pagination has "noindex, follow". I agree with you about "view all", I think it's the best option, in the future I'd like to set it up...
Thx for replying!!
Francesca
-
Hi @Red_educativa S.L.,
I would suggest using rel="prev/next" in this situation, yes.
When you are specifying a "rel" attribute you are specifying a relationship between the current document and the linked one. The value "prev" and "next" is specifying the relationship to be "The next [previous] document in a selection".
If you instead would use nofollow, google's spiders will not crawl the page. A nofollow value is "Links to an unendorsed document, like a paid link.".
However, this being said, it would be good for SEO to include a "view all" page. This will include all the content on a single page. You should then use rel="canonical" on the link to the view-all page (this will send users from search results to your view-all page. If you instead wish to use your first page in the series, you should only use rel next and prev (not rel canonical).
Have a look at this video from google for more information: http://www.youtube.com/watch?v=njn8uXTWiGg
I hope this helps.
--
Jørgen Juel
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 -
Rel-nofollow for price comparison site?
I run a price comparison site, so we have TONS of outbound links. Should my outbound links be marked with 'rel=nofollow'?
On-Page Optimization | | lancerpanz0 -
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 -
Rel="Canonical"
Hi!, We´ve just launched a new website and on this web we are using a lot Call to Actions on every page of the web and all of this CTA`s goes to the same Landing Page. (Ej: http://www.landing page.com) The problem comes when Google says this Landing Page is duplicate content because we are using some parameters like, for instance, http://www.landing page.com/?fuente=Soporteensalesforce So now we have just 1 Landing Page but Google sees 13 pages, because of this parameters and Moz alerted me that Google is seeing it as duplicate content. Yesterday I put this on the head of the only Landing Page we have so Google can see it in the proper way, as just one landing, but I don´t know if it is enough or should I do anything else? What I put on the Head: Hope someone can help me about this because I´ve tried to find a solution and this is the only thing that came up to me, and don´t know if it´s the right thing. Thanks for your time!
On-Page Optimization | | Manuel_LeadClic0 -
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.
On-Page Optimization | | inlinear
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 - prices The description text is more different... Is this the best practice in my case? Thanks for all your opinions! 🙂 best regards,
Holger0 -
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 -
Is it a good idea to rel=canonical dozens of old outdated pages?
we have dozens old outdated manual pages that still need to be up, but have terrible code issues (they're exported from word) and no image tagging, etc. there are new pages in place, so should i rel=canonical to the new pages? will this transfer any link juice to the newer, more seo-friendly ones?
On-Page Optimization | | DerekM880 -
Dynamic parameters
Our site has numerous filters and on each results page, we have the rel canonical tag. So, I'm not sure if we should concern ourselves or not about the crawl stats reporting that we have a bunch of pages that have more than two parameters. If so, do you have any suggestions? This url is an example: http://www.colemanfurniture.com/accent-occasional-furniture/accent-chairs.htm?color=20&furniture_type=213&price=16,10 Thanks!
On-Page Optimization | | thappe0