Live data from Hacker News

Pagination with rel=“next” and rel=“prev”

googlewebmastercentral.blogspot.com

1–10 of 35 posts

Re: Pagination with rel=“next” and rel=“prev”

#2
An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Re: Pagination with rel=“next” and rel=“prev”

#6

An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Although the linked article on view all pages http://googlewebmastercentral.blogspot.com/2011/09/view-all-... says they are going to try to make search results point at unpaginated content as thats what users want...

Re: Pagination with rel=“next” and rel=“prev”

#7

An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Well, not just that. I imagine browsers implementing keyboard shortcuts that automatically go to the next or previous pages.

Re: Pagination with rel=“next” and rel=“prev”

#8
post #7

An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Well, not just that. I imagine browsers implementing keyboard shortcuts that automatically go to the next or previous pages.

I've used the "Link Widgets" plugin for Firefox, which does a very good job of guessing and setting alt+pgup/pgdn to forward and back.

Re: Pagination with rel=“next” and rel=“prev”

#9
post #7

An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Well, not just that. I imagine browsers implementing keyboard shortcuts that automatically go to the next or previous pages.

I've been hoping for this for many years. Without requiring new buttons or keys, an interesting strategy would be to make the "history forward" gesture/key/button follow the "next" link. Assuming sane use of next and previous this works well for viewers that start at the beginning. What to do for the "back" function is ambiguous when previous doesn't match to history, as in a case where a viewer lePt Ito the middle of content via a search.

Re: Pagination with rel=“next” and rel=“prev”

#10
post #7

An interesting aspect is if Google's treatment of these links incentivizes publishers to add them, then browsers (or browser extensions) will also be able to use them to defeat the purpose of pagination in the first place, e.g. by having something like Readability slurp all the pages into a view-all page.

Well, not just that. I imagine browsers implementing keyboard shortcuts that automatically go to the next or previous pages.

Opera has that already — Forward button becomes "Fast Forward" and if you use Spacebar to scroll to the bottom, it will automatically follow "next" link.

Ironically, HTML5 recently dropped bunch of link relationships because of lack of browser and search engine support.

Post reply on HN