I'm curious what the community thinking is on this point. While infinite scrolling may present a user-friendly tool for listing a large number of entries, isn't there potentially a downside from an SEO perspective IF the content in question doesn't have its own single entry screen which would expose an SEO-friendly semantic URL?
For blogs posts, for example, a common URL structure might be domain.com/blog to list most recent entries and a single blog post might be domain.com/blog/comments/entry-utl-title. EE then gives you a simple way to generate category-sorted lists using the category segment with something like domain.com/blog/category/category-url-title (and if you use addons you can also potentially achieve parenting segments, but not natively). I have to assume that the category url titles themselves are good for SEO as well, all things being equal.
A suggestion I was given for filtering content on the front end - particularly around filtering content with combinations of categories or other entry data - was a jQuery plugin called Isotope (in place of using EE's native advanced search, for example). It's a really interesting functionality for the user on the front end, but it got me thinking about the single-category-at-a-time URL structure I've often used. With an EE implementation of something like the isotope jquery plugin to use tags to filter and sort your list, the category URLs, no longer exist, do they? Or do you retain them as fallback if the user has javascript turned off? I'm wondering if you are giving up something by going that route, or is the combination of list view and single entry view enough?
