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
-
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 -
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 -
What Next after Weekly Crawl Errors Fixed?
Hi MoZ Community! Moz weekly crawl used to report following errors : I have fixed them all over the time. Can somebody give an idea what to do next with the help of Moz or away from Moz to improve my optimization practices. I believe this is just start of the SEO. Or how is it if I focus link building efforts and start fighting for keywords. Also any suggestions about the web? Tanveer | Duplicate Page Content 4XX (Client Error) Title Missing or Empty 5XX (Server Error) Missing Meta Description Tag Duplicate Page Title Title Element Too Long (> 70 Characters) Title Element Too Short Meta Refresh Temporary Redirect |
On-Page Optimization | | Sequelmed0 -
Is it convinient to use No-Index, Follow to my Paginated Pages?
I have a website http://www.naukrigulf.com and it has a lot of Paginated pages on its SERP and most of paginated pages are getting indexed in Google SERP. Is it beneficial to use No-Index, Follow to keep the link equity to main (first page), although we have already used rel=next and rel=prev. If Answer is "yes" is their any harm by using no-index, follow with rel=next, rel=prev.
On-Page Optimization | | vivekrathore0 -
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 -
Almost all pages showing under Notices Rel Canonical - why???
Hi, I'm just going through my latest crawl since my new site launch and havce noticed almost all of my websites pages are listed under the notices rel canonical section, Why is this? All pages have the unique pages titles followed by the site name in the title, for example: Product | Site name All pages have unique meta descriptions and content (although we only offer lots of differt varients of the same product). Is this something I should be worried about?
On-Page Optimization | | EclipseLegal0 -
Rel Canonical
I will be quick and to the point. I am clearly a novice. I received a notice on my seomoz account that I had 12 pages with a Rel Canonical issue. It seems serious. Can this be a quick fix? Any thoughts? Below is the site address. petbarnpdx.com Thanks in advance for any input on this! Dave
On-Page Optimization | | APICDA0 -
The SEO and CRO Value of an Image Next to Page Content
If given the choice to add an attractive stock photo to a conversion focused page, do the pros out number the cons in terms of SEO and CRO. Some pros are that you can include the keyword in the image filename and image alt tag. It can also increase user experience by making the page more attractive. Some cons might be that it increases page load time which can have a negative impact on SEO and user expereience. Also the visitor might get distracted away from the lead form button.
On-Page Optimization | | SparkplugDigital0