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 -
NoIndex or Rel=Canonical Pagination
Hello, I had a question about noindex and Rel=Canonical on category page pagination. On my site, the category page the meta="robots" has "Index,Follow" tags and the rel="canonical" is the main category page, but when a user sorts the page the meta="robots" changes to "NoIndex, Follow." My question is should the sorted page be name="robots" content="INDEX,FOLLOW" /> since the rel="canonical" is pointing to the main page?? Or does it matter that it is NoIndex?? Any thoughts on this topic would be awesome. Thanks. Main Category Page
On-Page Optimization | | chuck-layton
https://www.site.com/category/
name="robots" content="INDEX,FOLLOW" />
rel="canonical" href="https://www.site.com/category/"/> Name Sorted Page
https://www.site.com/category/?dir=asc&order=name
name="robots" content="NOINDEX, FOLLOW" />
rel="canonical" href="https://www.site.com/category/">0 -
Should you do on-page optimization for a page with rel=canonical tag?
If you ad a rel=canonical tag to a page, should you still optimize that page? I'm talking meta description, page title, etc.
On-Page Optimization | | marynau0 -
I still don't understand how rel=canonical works. Help?
So here's the deal. I write for many different outlets. I also have many different pages on my blog that have duplicates (authorized, of course). On my blog, I have many different pages that redirect to "the original" content. I've only recently discovered the existence of rel=canonical. However I don't understand how it works. I have very specific questions. Can anyone help? If, on my blog, I have a blog post that's the original. And another website has the same content, used with authorization. If I want to tell search engines that the original content is on MY blog, what can I do? Is the only solution to ask the owner of the other blog to add a rel=canonical in the header of the specific post? If, on my blog, I have a blog post that's NOT the original. Do I simply add rel=canonical to the header, then add a link to the original in the body? If, on my blog, I have THE FIRST 300 WORDS of a blog post, then add a link saying "to read the whole article, click here" with a link pointing to the original, do I need to have a rel=canonical tag somewhere? Does it HAVE to be in the header? Can rel=canonical be used in the - What penalties are included with having duplicate content of my work everywhere on the web? I've been trying to find specifics, but can't. Thanks for the help. I'm quite confused, as you can see.
On-Page Optimization | | cedriklizotte0 -
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 -
Pagination for image galleries
We have photo galleries that load new URLs with new content/photo on each page, yet I'm still seeing "duplicate meta description" in GWT for each separate URL in the gallery. Will rel="next" rel="prev" take care of this? Just want to confirm as it requires a CMS upgrade/release.
On-Page Optimization | | Aggie0 -
Rel canonical Issue
I have a huge rel canonical issue showing up on my website, and I'm not sure that I fully understand why. To my knowledge, this is something that comes about when alternate urls are used to link to the same page. However, this is not a technique that I've used with my website, yet it's still raising a flag on just about every page. http://bit.ly/jYyTYN Can anyone enlighten me on what's causing this? Thanks
On-Page Optimization | | JayAdams320 -
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