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
-
Can I safely asume that links between subsites on a subdirectories based multisite will be treated as internal links within a single site by Google?
I am building a multisite network based in subdirectories (of the mainsite.com/site1 kind) where the main site is like a company site, and subsites are focused on brands or projects of that company. There will be links back and forth from the main site and the subsites, as if subsites were just categories or pages within the main site (they are hosted in subfolders of the main domain, after all). Now, Google's John Mueller has said: <<as far="" as="" their="" url="" structure="" is concerned,="" subdirectories="" are="" no="" different="" from="" pages="" and="" subpages="" on="" your="" main="" site.="" google="" will="" do="" its="" best="" to="" identify="" where="" sites="" separate="" using="" but="" the="" is="" same="" for="" a="" single="" site,="" you="" should="" assume="" that="" seo="" purposes,="" network="" be="" treated="" one="">></as> This sounds fine to me, except for the part "Google will do its best to identify where sites are separate", because then, if Google establishes that my multisite structure is actually a collection of different sites, links between subsites and mainsite would be considered backlinks between my own sites, which could be therefore considered a link wheel, that is, a kind of linking structure Google doesn't like. How can I make sure that Google understand my multisite as a unique site? P.S. - The reason I chose this multisite structure, instead of hosting brands in categories of the main site, is that if I use the subdirectories based multisite feature I will be able to map a TLD domain to any of my brands (subsites) whenever I'd choose to give that brand a more distinct profile, as if it really was a different website.
Web Design | | PabloCulebras0 -
How do elements that are displayed when scrolled impact SEO?
Hi, We are wanting to implement Animate.css and Wowjs on our site and were concerned about the SEO impacts. Basically when the page is loaded, if the element is not within the viewport then the HTML tag (i.e. div tag) have a style="visibility: hidden" and once the element is within the viewport it will change to have style="visibility: visible". Would having the style="visibility: hidden" negatively impact SEO?
Web Design | | KendallHershey0 -
Is having a site map page necessary?
Hello all! So I know having a sitemap XML file is important to include in your robots.txt file. I also know it is important to submit your XML sitemap to Google and Bing. However, I am wondering if it is beneficial for your site's SEO value to have a sitemap page displayed on your website? Or is this just a redundant action if you have already done the above two actions with your XML sitemap? Thanks in advance!
Web Design | | Myles920 -
Should I Redirect Pagination?
Working on a redirect map for a client moving platforms and they have all of their category pagination indexed - no canonical link and no rel next/prev's on any of them. Should I redirect the pagination pages to the main category page on the new platform? Or Should I allow the pagination to de-index itself type of thing? Thoughts and experience?
Web Design | | paul-bold0 -
Hiding content until user scrolls - Will Google penalize me?
I've used: "opacity:0;" to hide sections of my content, which are triggered to show (using Javascript) once the user scrolls over these sections. I remember reading a while back that Google essentially ignores content which is hidden from your page (it mentioned they don't index it, so it's close to impossible to rank for it). Is this still the case? Thanks, Sam
Web Design | | Sam.at.Moz0 -
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 -
From Google Sites to Wordpress - Anyone Ventured this SEO terrain?
We have a few sites in Google Sites - and they are ugly! We have a majority (40+) of websites in Wordpress. But we have a few websites just stuck on Google Sites, and since Google won't let you fully edit the HTML, add scripts, or implement any technology since 2000, we want to move. The sad problem - the Google sites are ranking well. We rank well in Manhattan, Atlanta, Dallas, and Philadelphia. The problem is - the sites do not give much room for growth - and the bounce rate is high because they are so ugly. Has Anyone moved from Google sites to Wordpress? Should we just stay with Google and bite the ugly bullet? My fear is that these sites will not allow for growth. It is hard to update them and even harder to make them look nice. To get a sample - beware: www.counselingphiladelphia.com Even another reason to leave: The slider is non-semantic and terrible SEO. Google won't allow a slider script with tags and a hrefs, so the only way to implement a slider is through a Google Docs Presentation that keeps sliding. I know - terrible SEO (#donthate) but we needed something. Any advice and thoughts would help! Thanks Mozzers!
Web Design | | _Thriveworks0 -
Forms vs. Buttons
We are an IT services firm. A conversion for us is completion of a lead form. Generally speaking, is it better to have a form to fill out in the sidebar on most organic pages, or a button that takes you to a lead form? I see both used, which do you think converts better?
Web Design | | CsmBill0