25. With use of rel prev/next:
> Keep in mind
Pages with rel next/prev can still be shown in results
But this is an extreme “edge case”
Can optionally use noindex
Use of rel next/prev consolidates signals across the entire series
26. View All Pagination Requirements
Annotations:
• pages 2-N specify View All as rel
View All canonical target
• View All page must load fast
• View All contains all data in the
series
pp. 2-N
27. Side Note: View Alls
> Challenges
View All pages must be fast
Big sites (esp. ecomm) sometimes dislike them
… but users love them! (if they’re fast)
33. Recommendations
> When you have a great View All
Add rel canonical targets to the View All on all component pages
in a series
Ensure the View All contains all the data found on the component
pages
Ensure the View All loads quickly
33
34. Recommendations
> When View All isn’t an option
Use the rel prev/next method to consolidate signals across the
series
Advantage over noindex method
Use self-referencing rel canonical
34
35. Recommendations
> Two more options:
Append parameters to the URL with a hash (#)
Progressive rendering as user scrolls
35
42. Takeaways:
• Identify essential and overhead
facets
• Always force the canonical path
regardless of selection order
• Build URLs according to queries
(how do your users search?)
42
43. Downsides:
• Solves nothing for decreasing
crawl overheads
• Labor intensive and error prone
43
54. Takeaways:
• Use rel canonical to signal the
preferred URL, not as a
“shortcut”
• Internal link signals should be
consistent
• Careful with self-referencing rel
canonical tags 54