• Save
Pagination menachem-rosenbaum
Upcoming SlideShare
Loading in...5
×
 

Pagination menachem-rosenbaum

on

  • 312 views

 

Statistics

Views

Total Views
312
Views on SlideShare
306
Embed Views
6

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 6

http://static.wix.com 5
http://htmlcomponentservice.appspot.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Pagination menachem-rosenbaum Pagination menachem-rosenbaum Presentation Transcript

    • pagination rel=”next” rel=”prev” Menachem Rosenbaum http://luckyboost.com @luckyboost1 <link rel=“next” href=“pagination-guide/2”> http://luckyboost.com
    • What is the problem? Search engines see pagination as separate entities, searchers might be sent to a different page that might not be the most relevant. links and anchor text, can be diluted into the different component URLs rather than being consolidated to the one article or to the one product category.2 <link rel=“prev” href=“pagination-guide/”> <link rel=“next” href=“pagination-guide/3”> http://luckyboost.com
    • Where is the problem?Article divided into several componentpagesForum thread divided into a sequence ofURLsProduct category with items spread acrossseveral pages3 <link rel=“prev” href=“pagination-guide/2”> <link rel=“next” href=“pagination-guide/4”> http://luckyboost.com
    • How to deal with the problem? <meta name=“robots” content =“noindex, follow”> - allows crawling but not indexing rel=”canonical” - acts a strong hint for duplicate content rel=”next” and rel=”prev” - indicate the relationship between component URLs in a paginated series4 <link rel=“prev” href=“pagination-guide/3”> <link rel=“next” href=“pagination-guide/5”> http://luckyboost.com
    • Article divided into several components + noindex, follow Article Article Article Page 1/3 Page 2/3 Page 3/3 content =“noindex, follow” content =“noindex, follow”5 <link rel=“prev” href=“pagination-guide/4”> <link rel=“next” href=“pagination-guide/6”> http://luckyboost.com
    • Article divided into several components + noindex, follow Article Page 1/3  SE can see only page 1  SE will only return page 1 No control over inbounded seo6 <link rel=“prev” href=“pagination-guide/5”> <link rel=“next” href=“pagination-guide/7”> http://luckyboost.com
    • Article divided into several components + canonical Article Page 1/3 rel=“canonical“ href=“page 1/3” rel=“canonical“ href=“page 1/3” Article Article Page 2/3 Page 3/37 <link rel=“prev” href=“pagination-guide/6”> <link rel=“next” href=“pagination-guide/8”> http://luckyboost.com
    • Article divided into several components + canonical Article Article Page 1/3 Article Page 2/3 Page 3/3  SE can see all page  SE will most probably return only page 1 Partial control over inbounded seo (all goes to page 1)8 <link rel=“prev” href=“pagination-guide/7”> <link rel=“next” href=“pagination-guide/9”> http://luckyboost.com
    • Article divided into several components + rel="next“ and rel="prev" rel=“prev" href=“page 1/3” rel=“prev" href=“page 2/3” Article Article Article Page 1/3 Page 2/3 Page 3/3 rel="next" href=“page 2/3” rel=“next" href=“page 3/3”9 <link rel=“prev” href=“pagination-guide/8”> <link rel=“next” href=“pagination-guide/10”> http://luckyboost.com
    • Article divided into several components + rel="next“ and rel="prev" Article Article Article Page 1/3 Page 2/3 Page 3/3  SE can see all pages  SE can return all pages most probably page 1  Most control over inbounded seo10 <link rel=“prev” href=“pagination-guide/9”> <link rel=“next” href=“pagination-guide/11”> http://luckyboost.com
    • rel="next“ and rel="prev“ + canonical View all page pre category category v all pre category v category Page 1/3 ne Page 2/3 xt ne Page 3/3 xt11 <link rel=“prev” href=“pagination-guide/10”> <link rel=“next” href=“pagination-guide/12”> http://luckyboost.com
    • rel="next" and rel="prev“ with parameters and canonical URL: http://mysite.com/category/2?sort=popular <link rel=”canonical” href=“http://mysite.com/category/2”> <link rel=“prev” href=“http://mysite.com/category?sort=popular”> <link rel=“next” href=“http://mysite.com/category/3?sort=popular”> URL: http://mysite.com/category/subcategory/2?sort=price <link rel=”canonical” href=http://mysite.com/category/subcategory/2> <link rel=“prev” href=“http://mysite.com/category/subcategory?sort=price”> <link rel=“next” href=“http://mysite.com/category/subcategory/3?sort=price”>12 <link rel=“prev” href=“pagination-guide/11”> <link rel=“next” href=“pagination-guide/13”> http://luckyboost.com
    • Rules for rel="next“ and rel="prev" 1. The chain can’t be broken 2. Each url can be in only one pagination chain 3. The pagination attributes can only link together URLs with matching13 parameters <link rel=“prev” href=“pagination-guide/12”> <link rel=“next” href=“pagination-guide/14”> http://luckyboost.com
    • Thank you Menachem Rosenbaum menachem@luckyboost.com http://luckyboost.com Find presentation at http://bit.ly/paginate14 <link rel=“prev” href=“pagination-guide/13”> http://luckyboost.com