This is the clearest explanation of pagination I've seen. Thank you!

Great video. I was searching google to find an answer for pagination - only this video from "google" was complete !! And yes, i do like you cheerful face. Happy smiling :)

The world of SEO is awesome! I love this strategy for building my business!

Because a "view all" page of 150,000 results is obviously beyond "intense" from a page load standpoint and not practical. rel=canonical should not apply to listings beyond 5-10 pages, and is mostly applicable to limited content like e-commerce pagination. And the Google Search does not have rel=prev and rel=next links of it's own either, probably due to the pagination consisting of dynamic links. The scope of this question mostly apply to static links and limited pagination.

Thanks Maile Ohye, wonderful resources to overcomes pagination & Indexing.

Merci Maile Ohye pour cette excellente (et sympathique) vidéo. Thank's very much for this very useful video !

Thanks, rel prev, rel next is added!! ..now if only my source will render in search as inspected in console.

Too many people get this SOOOO wrong! seeing this video up now was like getting a boat-load of ponies, kittens, puppies and unicorns delivered to my doorstep, because I can no refer back to Maile's video whenever they argue with me about canonicals and pagination, instead of saying "Maile even says the methods I'm recommending are best practices!" :-)

What about the "Load more" buttons using AJAX techniques to fetch more items? Would like to see a video on that.

Thanks Maile for sharing this great video.

Great Video! Its something i definitely need to have a look at for our site which has multiple listings. In google results i see "Page 5...." "page 6..." for our categories. im guessing its because google is reading each page separately and not as one category. Back to the drawing board.

What if I have only partially duplicated content? My website has pagination where products are changing when you click next page but header (title and desc) of the category stays the same for every page. Google also sees this as duplicate content even though it is only partially duplicated.

Thanks Maile. Great explanation and I like the available options.

Thank you, things are getting some what more clear

Thanks Maile - this is very helpful getting a clear understanding of how Google wants us to treat paginated pages. Would these suggestions also apply for paginated pages that list, for example, lawyers in NYC - there is nothing special about these paginated pages other then more listings of lawyers - Perhaps, the best idea for these paginated pages is a norobots tag that read nofollow, index.

could this be used to link together similar videos? by using the rel=next and the pointing the href to a similar page so that when users find the original page it will also link that with another page they might be interested in.

@geminigeektube But you asked for a "View all" feature, not a "View 1000". Even so, 1000 results per page is ridiculous. No regular user would use that, hardly anyone goes beyond the first 10 or 20 results as it is. For non-standard uses, there's the API and other services.

If you have component pages and a view-all page, shouldn't you be combining rel="next" and rel="prev" as it should AND (not OR like in the video (10:42)) rel="canonical" linking to the view-all page on each component page? To send searchers to the relevant component page, and give the juice to the canonical view-all page that includes everything from all component pages? Like in 12:28, or will Google not index the component pages, so the only page available in Google for searchers is the view-all page?

@Die1101 do a research before commenting ? "Sorry, Google does not serve more than 1000 results for any query. (You asked for results starting from 1250.)" this what google says when you change the start var to > 1000 !

For these paginated items, what if you have an option to display the number of items per page? Say, the total number of items is 17, and the user opted to display 20 items in a page to see all of them in one page. What should I use, canonical or next/prev?

my data base is huge , i have tons of pages , what would happen if use view all options......ah it will hang , give me some better option what is good for seo pagination or scroll , think as user not as programmer or designer

Will this matter today with all the changes that Google has made, or is this still relavant today

Great video.

I really enjoyed watching your video on SEO.I'm brand new to this stuff.Where should I start?

each page within a paginated series should canonicalize to itself, so /page/2/ has a canonical pointing to /page/2/. Should page 2 etc. be in the google search results? or Not , please confirm

i wonder why "google search results" don't have a view all pages ? if visitors love "view all" pages so "intense" !

What about offset pagination? Could you give me some hints on how to tackle this specific approach?

Don`t be confuse if you would like to make your website to be the top rank. This site will guide you to construct your site to the top one. Search "speed rank seo" on google.

讲得非常详细，非常感谢。

Why on minute 14:24 the following option is not a valid one?? example.com/article?story=x&page=2&sid=123

Thanks for the information, very useful video

@geminigeektube You can set it up to 100 results per page. You don't want 13,000,000 results in a single page.

I liked this so send web users back to relevant page If not, For me

Well, for one: google doesn't index google search listings I guess. :]

How does Bing/Yahoo treat this implementation?

Anyone tried the MoboRank (do a search on google)? I've heard several unbelivable things about it and my friend improve his website's google ranking with it.

I think you're confusing Google with Microsoft. Windows is made by Microsoft. ...but even employees from Microsoft use Mac's.

very good

pagination is not cool anymore, people are happy to scroll 100 feet long pages

Not using Chromebooks, eh? :D

capable video

Important: this video should be deleted please. It is outdated. Please see the note on webmasters.googleblog.com/2011/09/pagination-with-relnext-and-relprev.html for more information, saying "Note: The information in this post is outdated. Rel=prev/next is not an indexing signal anymore."

Thanks :D

...lol.