Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Pagination: Rel Next/Prev, Rel Canonical and Google Indexing

         

Ekon

12:07 pm on Jan 25, 2014 (gmt 0)

10+ Year Member Top Contributors Of The Month



Hello All,

I am trying to optimise my own ecommerce website and I have some questions regarding pagination, canonical tags and indexing of pages.

Below is what I have added to my category pages :

Category Page URL: http://example.com/flowers

<link rel="canonical" href="http://example.com/flowers" />
<link rel="next" href="http://example.com/flowers?page=2" />

Pagination Category 2 Page URL : http://example.com/flowers?page=2


<link rel="canonical" href="http://example.com/flowers?page=2" />
<link rel="prev" href="http://example.com/flowers"/>
<link rel="next" href="http://example.com/flowers?page=3" />


Below are the Questions :

1- Does this canonical tag <link rel="canonical" href="http://example.com/flowers?page=2" /> in the coding of this URL : http://example.com/flowers?page=2 create any problem , should I leave it as it is or change it to <link rel="canonical" href="http://example/flowers"/>


2- When I search in google using the site:http://example.com/flowers it shows me all the pagination pages as well :

http://example.com/flowers?page=2
http://example.com/flowers?page=3
http://example.com/flowers?page=4


3- Does this effect my rankings in search results ?


Any help would be appreciated .

Thanks.

[edited by: aakk9999 at 1:47 pm (utc) on Jan 25, 2014]
[edit reason] Please use example.com to avoid autolinking [/edit]

aakk9999

2:33 pm on Jan 26, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Welcome to WebmasterWorld, Econ!

The way you use rel prev/next is correct, I would not change anything.

Here are the answers to your questions:

1) On your page 2, leave your canonical as it currently is. It is there to canonicalise URLs such as http://example.com/flowers?page=2&some-unwanted-parameter=something to your page 2 URL. Do not have canonical of subsequent pages point to the first page of pagination or you risk links on subsequent pages not followed and content ignored.

2) If you are searching for these pages using the site: and inurl: commands then I think it will show all paginated pages it indexed. But for "usual" types of searching (some flower keyword) it should consolidate link juice and show most appropriate page to the searcher. In my experience, for paginated lists this is always page 1.

Pagination
https://support.google.com/webmasters/answer/1663744?hl=en [support.google.com]
Use rel="next" and rel="prev" links to indicate the relationship between component URLs. This markup provides a strong hint to Google that you would like us to treat these pages as a logical sequence, thus consolidating their linking properties and usually sending searchers to the first page.


3) All things equal, it should improve ranking as it consolidates linking properties. Also, if you have lots of pagination pages on the site, Google may see these as thin pages, whereas use of rel prev/next make Google understand these pages better. But note that Google says that rel prev/next are just hints. And if your pages 2 onwards do not get links, there are no external linking properties to consolidate.

Ekon

3:11 pm on Jan 26, 2014 (gmt 0)

10+ Year Member Top Contributors Of The Month



Great thanks for clarifying it in such a professional way.