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 -
Site Migration due to Corporate Acquisition
Hey everyone, Wanted to check-in on something that I've been thinking way too much about lately. I'll do my best to provide background, but due to some poor planning, it is rather confusing to wrap your head around. There are currently three companies involved, Holding Corp (H Corp) and two operating companies, both in the same vertical but one B2B and the other is B2C. B2C corp has been pushed down the line and we're focusing primarily on H Corp and B2B brand. Due to an acquisition of H Corp and all of it's holdings, things are getting shuffled and Ive been brought in to ensure things are done correctly. What's bizarre is H Corp and it's web property are the dominant authority in SERPs for the B2B brand. As in B2B brand loses on brand searches to H Corp, let alone any product/service related terms. As such, they want to effectively migrate all related content from H Corp site to B2B brand site and handover authority as effectively as possible. Summary: Domain Migration from H Corp site to B2B Brand site. Ive done a few migrations in my past and been brought in to recover a few post-launch so I have decent experience and a trusted process. One of my primary objectives initially is change as little as possible with content, url structure (outside the root) etc so 301s are easy but also so it doesn't look like we're trying to play any games. Here's the thing, the URL structure for H Corp is downright bad from both a UX perspective and a general organizational perspective. So Im feeling conflicted and wanted to get a few other opinions. Here are my two paths as I see and Id love opinions on both: stick with a similar URL structure to H Corp through the migration (my normal process) but deviate from pretty much every best practice for structuring URLs with keywords, common sense and logic. Pro: follow my process (which has always worked in the past) Con: don't implement SEO/On-page best practices at this stage and wait for the site redesign to implement best practices (more work) Implement new URL structure now and deviate from my trusted process. Do you see a third option? Am I overthinking it? Other important details: B2B brand is under-going a site redesign, mostly aesthetic but their a big corporation and will likely take 6-9 months to get up. Any input greatly appreciated. Cheers, Brent
Web Design | | pastcatch1 -
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 -
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 -
Help with Schema.org on Ecommerce Products
I’m looking for ways of using schema.org with products that have pricing options. There appear to be two main problems 1) Whilst colour, width, height and depth are all catered for, size appears to be missing – how can we mark up products that are available in sizes that aren’t necessarily covered by width/height/depth (e.g. shoe size). Also, what if the product is available in different finishes – technically, these could not properly be described as colours so how could we mark them up? 2) There doesn’t seem to be any particularly good way of marking up pricing options that are displayed on the same product detail page. For e.g. if a pricing option table is used like this: | ID | Colour | Price 001-red | Red | £3.99 001-green | Green | £4.49 001-blue | Blue | £4.99 | I can mark up each row as an offer, and give each offer a price and sku or mpn, but then I can’t use itemprop=”color” to describe exactly what the option is. Would I just use itemprop=”name” in this case and abandon color altogether (even though it’s technically supposed to be describing the colour of the product and not the name of the offer)? I suppose another way I could approach it would be to mark up each row as an individual product, and assign each one an offer with the details as described above but then the containing page would effectively look like a separate product – which it isn’t. Any help or advice on this would be very much appreciated
Web Design | | paulbaguley0 -
Footer backlinks for sites I've developed
I link back to my website via my company name on the footers of sites I develop. Lately I've been changing this to my keyword and mixing and matching. This has been done for new sites I create and old sites I've not seen any benefit so far after a couple of months. Most my clients are hosted on the same server as my main site that it links back to. 1. Is this a bad idea to link back on the same IP?
Web Design | | sanchez1960
2. Is footer backlinks to the main developer going to annoy Google?
3. Should I change my main site's server, will it help? All my competitors seem to do it and as far as I can tell they seem to get better results than I do. Because I'm now changing them the reason I see no benefit? Thanks0 -
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 -
Site-wide footer links or single "website credits" page?
I see that you have already answered this question before back in 2007 (http://www.seomoz.org/qa/view/2163), but wanted to ask your current opinion on the same question: Should I add a site-wide footer link to my client websites pointing to my website, or should I create a "website credits" page on my clients site, add this to the footer and then link from within this page out to my website?
Web Design | | eseyo0