Pagination or View All
-
Right now our site is using ajax and we need to change it so all 200+ products will get crawled not just the first 52 on page first page. We are looking at doing the rel=next/ rel=previous or doing it so we have a link going to the View all product page. Or maybe doing the rel=next/ previous and using the canonical to point to the view all etc. I have read http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1663744 and http://googlewebmastercentral.blogspot.com/2011/09/view-all-in-search-results.html about it.
Now we are trying to figure out what is the best option. Thought. Here is our site. http://www.rockymountainatvmc.com/t/49/-/181/750/Motorcycle-Tires-All Also if we do not do the rel=next just make the view all items as a link that google can crawl is there a way to still have our current url be the one for view all items but only show 52 item unless the click view all items and not have it look like cloaking?
Hope this made sense.
-
lol. Hey Derek!
Ya, I would assume that page ranks well since its a single url and doesnt change based on the ajax/java functionality. Getting into multiple urls in search results based on categories, filters and groupings gets real hairy real fast. I would recommend thinking through this before you do it. Google will start to index all the page variations (even with canonicalization in place) and then you start getting duplicate content, or unwanted indexed pages.
i would still use the "view all" or make sure that you have a good internal linking structure along with the canonical tagging to get the information architecture pointing to the right spots still.
Hit me up at our next event and lets chat a bit about it.
-
Hey Ryan it is good to see you. I am Derek from SLC/SEM.
No it is ajax right now for the filter and different pages. We are going to give the pages different urls and we might give the filter different urls too. Would you recommend giving the filters their own URLs too?
Overall it looks like doing the "view all" is the best option. I am thinking of the best way to do that. For example right now this url (http://www.rockymountainatvmc.com/t/43/81/165/723/ATV-Tires-All) ranks pages one number 4 on google for the target key work ATV tires. So we want to keep that page as the view all.
But they want to have it so when people click on the link in the nav. it takes them to the page with only 52 products and not all of them.
What would you suggest?
-
I have experimented with various methods and best practices here across multiple site. Here is my suggestion:
1. Do both the rel next/prev and the view all option. In my testing the rel next/prev doesnt really have much impact alone, but doing both rel tags and the canonical to the view all could work great. Google wont really want to pay attention to the paginated content, even when you try to rel next/prev.
However, i did check your site out and it currently doesn't look like you are changing urls based on filters or anything. Are you saying that you are changing that? Would still do both, and then point some additional links to the view all page from some static internal pages and some external sources.
-
If we do the view all option we do not want to have to do a rel=canonical and the current url to the new "view all" and possibly lose rankings.
thoughts?
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
-
Query string category pagination
I've been reading some posts on the merits and pitfalls of using rel=prev, rel=next and canonical, but I just wanted to double check the right solution. example.com/birth-announcements example.com/birth-announcements?p=2 example.com/birth-announcements?p=3 With a small selection of products on each variation. So at the moment there is a canonical on all of them to the base example.com/birth-announcements. The problem is we are having difficulty getting the products within p=* indexed. I don't think from all I read that rel=prev/rel=next is the way to go. Would the solution (or best way to go) be to create a "view-all" filter and set that to be the canonical URL, so all product URLs are in clear focus for Google. The volume of products won't (shouldn't) have too much of an impact on page load. Or am I wrong and rel=prev/rel=next is a feasible solution?
Technical SEO | | MickEdwards0 -
Is Pagination & thin text issue affecting our traffic?
We at Pricebaba, have different price lists for different brands of phones for which we have done pagination. We are worried if we're suffering from the thin text issue. Could you help us check if it's done correctly? Pricelist page link: http://pricebaba.com/mobile/pricelist/samsung-price-list
Technical SEO | | RuchitaMahimkar0 -
Specific question about pagination prompted by Adam Audette's Presentation at RKG Summit
This question is prompted by something Adam Audette said in this excellent presentation: http://www.rimmkaufman.com/blog/top-5-seo-conundrums/08062012/ First, I will lay out the issues: 1. All of our paginated pages have the same URL. To view this in action, go here: http://www.ccisolutions.com/StoreFront/category/audio-technica , scroll down to the bottom of the page and click "Next" - look at the URL. The URL is: http://www.ccisolutions.com/StoreFront/IAFDispatcher, and for every page after it, the same URL. 2. All of the paginated pages with non-unique URLs have canonical tags referencing the first page of the paginated series. 3. http://www.ccisolutions.com/StoreFront/IAFDispatcher has been instructed to be neither crawled nor indexed by Google. Now, on to what Adam said in his presentation: At about minute 24 Adam begins talking about pagination. At about 27:48 in the video, he is discussing the first of three ways to properly deal with pagination issues. He says [I am somewhat paraphrasing]: "Pages 2-N should have self-referencing canonical tags - Pages 2-N should all have their own unique URLs, titles and meta descriptions...The key is, with this is you want deeper pages to get crawled and all the products on there to get crawled too. The problem that we see a lot is, say you have ten pages, each one using rel canonical pointing back to page 1, and when that happens, the products or items on those deep pages don't get get crawled...because the rel canonical tag is sort of like a 301 and basically says 'Okay, this page is actually that page.' All the items and products on this deeper page don't get the love." Before I get to my question, I'll just throw out there that we are planning to fix the pagination issue by opting for the "View All" method, which Adam suggests as the second of three options in this video, so that fix is coming. My question is this: It seems based on what Adam said (and our current abysmal state for pagination) that the products on our paginated pages aren't being crawled or indexed. However, our products are all indexed in Google. Is this because we are submitting a sitemap? Even so, are we missing out on internal linking (authority flow) and Google love because Googlebot is finding way more products in our sitemap that what it is seeing on the site? (or missing out in other ways?) We experience a lot of volatility in our rankings where we rank extremely well for a set of products for a long time, and then disappear. Then something else will rank well for a while, and disappear. I am wondering if this issue is a major contributing factor. Oh, and did I mention that our sort feature sorts the products and imposes that new order for all subsequent visitors? it works like this: If I go to that same Audio-Technica page, and sort the 125+ resulting products by price, they will sort by price...but not just for me, for anyone who subsequently visits that page...until someone else re-sorts it some other way. So if we merchandise the order to be XYZ, and a visitor comes and sorts it ZYX and then googlebot crawls, google would potentially see entirely different products on the first page of the series than the default order marketing intended to be presented there....sigh. Additional thoughts, comments, sympathy cards and flowers most welcome. 🙂 Thanks all!
Technical SEO | | danatanseo0 -
Which Pagination/Canonicalization Page Selection Approach Should be Used?
Currently working on a retail site that has a product category page with a series of pages related to each other i.e. page 1, page 2, page 3 and Show All page. These are being identified as duplicate content/title pages. I want to resolve this through the applications of pagination to the pages so that crawlers know that these pages belong to the same series. In addition to this I also want to apply canonicalization to point to one page as the one true result that rules them all. All pages have equal weight but I am leaning towards pointing at the ‘Show All’. Catch is that products consistently change meaning that I am sometimes dealing with 4 pages including Show All, and other times I am only dealing with one page (...so actually I should point to page 1 to play it safe). Silly question, but is there a hard and fast rule to setting up this lead page rule?
Technical SEO | | Oxfordcomma0 -
Any Positive Experiences with Rel=Next Rel=Prev for pagination?
Hi Mozzers! Can you share your experience and observations in implementing rel=next rel=prev on sites you've worked on?
Technical SEO | | SparkplugDigital0 -
Pagination question
I have a website http://www.example.com with pagination series starting with page1.html upto page10.html. With backlinks to some of the pages ( page1.html, page2.html----page7.html). If i include rel="next" and rel="prev" on page1.html to page10.html pages. Will value of those links will be transfered to http://www.example.com This is what i interpret from http://bit.ly/mUOrn2 Am i right ?
Technical SEO | | seoug_20050 -
Is this tabbed implementation of SEO copy correct (i.e. good for getting indexed and in an ok spot in the html as viewed by search bots?
We are trying to switch to a tabbed version of our team/product pages at SeatGeek.com, but where all tabs (only 2 right now) are viewed as one document by the search engines. I am pretty sure we have this working for the most part, but would love some quick feedback from you all as I have never worked with this approach before and these pages are some of our most important. Resources: http://www.ericpender.com/blog/tabs-and-seo http://www.google.com/support/forum/p/Webmasters/thread?tid=03fdefb488a16343&hl=en http://searchengineland.com/is-hiding-content-with-display-none-legitimate-seo-13643 Sample in use: http://www.seomoz.org/article/search-ranking-factors **Old Version: ** http://screencast.com/t/BWn0OgZsXt http://seatgeek.com/boston-celtics-tickets/ New Version with tabs: http://screencast.com/t/VW6QzDaGt http://screencast.com/t/RPvYv8sT2 http://seatgeek.com/miami-heat-tickets/ Notes: Content not displayed stacked on browser when Javascript turned off, but it is in the source code. Content shows up in Google cache of new page in the text version. In our implementation the JS is currently forcing the event to end before the default behavior of adding #about in this case to the url string - this can be changed, should it be? Related to this, the developer made it so that typing http://seatgeek.com/miami-heat-tickets/#about directly into the browser does not go to the tab with copy, which I imagine could be considered spammy from a human review perspective (this wasn't intentional). This portion of the code is below the truncated view of the fetch as Googlebot, so we didn't have that resource. Are there any issues with hidden text / is this too far down in the html? Any/all feedback appreciated. I know our copy is old, we are in the process of updating it for this season.
Technical SEO | | chadburgess0 -
Best way to Handle Pagination?
At the moment I my blog is paginated like so: /blogs > /blogs/page/2 > /blogs/page/3 etc What are the benefits of paginating with dynamic URLs like here on SEOmoz with /blog?page=3
Technical SEO | | NickPateman810