Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Infinite Scrolling vs. Pagination on an eCommerce Site
-
My company is looking at replacing our ecommerce site's paginated browsing with a Javascript infinite scroll function for when customers view internal search results--and possibly when they browse product categories also. Because our internal linking structure isn't very robust, I'm concerned that removing the pagination will make it harder to get the individual product pages to rank in the SERPs.
We have over 5,000 products, and most of them are internally linked to from the browsing results pages in the category structure: e.g. Blue Widgets, Widgets Under $250, etc.
I'm not too worried about removing pagination from the internal search results pages, but I'm concerned that doing the same for these category pages will result in de-linking the thousands of product pages that show up later in the browsing results and therefore won't be crawlable as internal links by the Googlebot.
Does anyone have any ideas on what to do here? I'm already arguing against the infinite scroll, but we're a fairly design-driven company and any ammunition or alternatives would really help.
For example, would serving a different page to the Googlebot in this case be a dangerous form of cloaking? (If the only difference is the presence of the pagination links.) Or is there any way to make rel=next and rel=prev tags work with infinite scrolling?
-
Hi Guys,
I was going to post a separate question here., but this thread seems to have answer the questions very well.
My client has infinite scrolling on his product pages but also have rel="prev" and rel="next" (but no actual physical page 1, page 2, page 3) buttons. I was just reading the rel="prev" and rel="next" should be in the in this case anyway. Does this mean we don't need actual buttons?
I am confirming the date this was put on, as I can't see any reduction in pages indexed which is one of the concerns above.
Regards
Neil
-
Thanks for your replies everyone.
We weren't sure if Google would look at JS removing the page navigation as cloaking or not, so that's still a bit of a concern. We were reading Rand's post from 2008 on the subject http://www.seomoz.org/blog/white-hat-cloaking-it-exists-its-permitted-its-useful and Matt Cutts' replies on the subject. We know it was a few years ago, but he still seemed to be saying to be over-cautious with that kind of thing.
Should we be worried about cloaking if we use JS to "hide" the page nav?
-
The correct way to handle this (and quite frankly, any javascript functionality) is to build it to work without javascript (keep the pagination), then have the javascript remove the pagination and implement infinite scrolling. This ensures that visitors with JS disabled get the full experience of the site, search engines can easily crawl your full catalog, and users with JS enabled get the "enhanced" experience you desire from a UX standpoint.
It's not an "either or" scenario. You can absolutely have an easily indexed site that extensively uses JS.
-
You should have both. Keep the paged navigation at top, but keep the infinite scroll. Now you have the best of both worlds.
Although, I don't think the infinite scroll would end up 'delinking' thousands of pages. How often do you see store.com/category/page/6 in results, anyway? If it's a popular term, it's going to be for the main category landing page.
Serving up different content to Google is always a bad idea unless you have a good reason. This problem doesn't qualify.
-
Its a bit technical but you can go through this https://developers.google.com/webmasters/ajax-crawling/ to make sure the dynamic page that you generate is actually indexable by Google.
That said 5000+ products infinite scroll is a bit scary and I would look at using rel=next and rel=prev for the pagination ( http://googlewebmastercentral.blogspot.com.au/2011/09/pagination-with-relnext-and-relprev.html )
I am not too sure what you mean by " internally linked to from the browsing results pages in the category structure: e.g. Blue Widgets, Widgets Under $250, etc. "
If you are referring to ability for users to sort through those products by picking one of the options like Blue Widgets, Widgets Under $250, etc. I would suggest rel canonical those pages to the base page . This should get you started http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394
-
you are coprrect, this will lead to de-indexing of your pages, unless your scroll page has every product on it at load, but this would mean a slow page for users. I assume that you are going to get pages on scroll via ajax or somthing on demand.
You would need to have to have other pages that link to the products.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Have Your Thoughts Changed Regarding Canonical Tag Best Practice for Pagination? - Google Ignoring rel= Next/Prev Tagging
Hi there, We have a good-sized eCommerce client that is gearing up for a relaunch. At this point, the staging site follows the previous best practice for pagination (self-referencing canonical tags on each page; rel=next & prev tags referencing the last and next page within the category). Knowing that Google does not support rel=next/prev tags, does that change your thoughts for how to set up canonical tags within a paginated product category? We have some categories that have 500-600 products so creating and canonicalizing to a 'view all' page is not ideal for us. That leaves us with the following options (feel it is worth noting that we are leaving rel=next / prev tags in place): Leave canonical tags as-is, page 2 of the product category will have a canonical tag referencing ?page=2 URL Reference Page 1 of product category on all pages within the category series, page 2 of product category would have canonical tag referencing page 1 (/category/) - this is admittedly what I am leaning toward. Any and all thoughts are appreciated! If this were in relation to an existing website that is not experiencing indexing issues, I wouldn't worry about these. Given we are launching a new site, now is the time to make such a change. Thank you! Joe
Web Design | | Joe_Stoffel1 -
Using Button Links vs Sidebar Menu
I have a services page with a lot of rich text and a slideshow of images. Currently, I am using a column of buttons to various services, and am wondering if a sidebar menu would be more effective for Google to crawl and rank?
Web Design | | cinchmedia0 -
Moving to new site. Should I take old blog posts with me?
Our company website has needed a complete overhaul for some time now and the new one is almost ready to go live. We also have a separate "news" site that is houses around 800 blog posts and news items. (That news site will be thrown away because it's on a completely different domain and causes confusion.) So we have a main site with about 100 decent blog posts and a separate news site with 800 poor posts. I plan on bringing all the main site blog posts over to the new site (both WordPress), but my question is whether or not to bring over the news site posts? All, handful, none? Another issue is the news site doesn't have Google Analytics, so I'm not sure if any posts actually generate traffic, but I can from the main site we do get some referrals from it. As far as quality of content goes, it's poor. Not sure who wrote it all, but it's mainly text press releases that aren't very interesting. Is it worth bringing over for SEO purposes or simply delete the site and create a mass redirect so all of those pages will direct to the new website's blog page? Any help is greatly appreciated.
Web Design | | codyfrew0 -
How long should an old site redirecting to a new site remain activated on a server?
Once I switch a site to a new domain (with links to corresponding/relative pages), will I have to keep the old site live forever for those links to work, or how long should I wait before I inactivate the old site on our server?
Web Design | | jwanner0 -
301 Redirect all pictures when moving to a new site?
We have 30,000 pictures on our site. Moz will return 404's on some occasionally, but Google seems to ignore those. Should I 301 redirect all those images when we move to a new site lay-out? Appreciate your views!
Web Design | | Discountvc0 -
Wordpress: Pages vs Posts vs Portfolio
Hi All, I'm looking to put pen to paper and design my main structual template for my website. I will be creating the new site in Wordpress. My understanding of Wordpress is broken into the Static Pages, Posts and Portfolio. Static PAGE
Web Design | | Mark_Ch
Static one off content.
No tags, categories or archived Posts
content entries, which is listed in reverse chronological order.
Update post entry to maintain overall freshness of your website.
tags, categories & archived Portfolio
????? Question What are the benefits of a portfolio page over Static Pages & Posts When creating feature rich articles should i use static pages, posts or portfolio. Thanks Mark0 -
Best way to indicate multiple Lang/Locales for a site in the sitemap
So here is a question that may be obvious but wondering if there is some nuance here that I may be missing. Question: Consider an ecommerce site that has multiple sites around the world but are all variations of the same thing just in different languages. Now lets say some of these exist on just a normal .com page while others exist on different ccTLD's. When you build out the XML Sitemap for these sites, especially the ones on the other ccTLD's, we want to ensure that using <loc>http://www.example.co.uk/en_GB/"</loc> <xhtml:link<br>rel="alternate"
Web Design | | DRSearchEngOpt
hreflang="en-AU"
href="http://www.example.com.AU/en_AU/"
/>
<xhtml:link<br>rel="alternate"
hreflang="en-NZ"
href="http://www.example.co.NZ/en_NZ/"
/> Would be the correct way of doing this. I know I have to change this for each different ccTLD but it just looks weird when you start putting about 10-15 different language locale variations as alternate links. I guess I am just looking for a bit of re-affirmation I am doing this right.</xhtml:link<br></xhtml:link<br> Thanks!0 -
Mobile Site Pages: Word Count Help
Hi there I am doing a mobile website for a client and they asked me what the dieal word count would be per page. They are SEO conciosu but we are not doing SEO on this site. I would just like to know a general rule of thumb. Regards Stef
Web Design | | stefanok0