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?
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
-
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 -
Compare to Front End view source contain more tageting keywords any impact on seo?
Hi All, I am using chrome browser and in my category page when i search my keyword like example Acer Laptop it is showing me 40 searches for that keyword in front end while in view source it is showing 100. Now for same category of my competitor page when i search Acer Laptop it shows 20 searches in front end and 300 in view source. So my question is - Is it a good practice I have seen my competitor page he is using tab button where lot of geunine content is there that is the reason hiss view source keyword search is more. So will it impact on seo?
Technical SEO | | miteshseo0 -
YouTube vs. LimeLight - What are the SEO pros and cons of each platform for on-site video viewing?
Are there any SEO benefits of hosting on-site videos using LimeLight? I know the various benefits of using YouTube but before going forward with a site redesign I want to hear what others have to say. Thanks, Jake
Technical SEO | | JakeMatulewicz1 -
Pagination when not needed
Hello Moz, Odd one for you today. I've a site with has pagination (rel= next / prev) however its not being used correctly. I'll give you some examples: lets assume its a 5 page site with a home page, about us etc. The home page has a rel="next" tag on it leading to the next tab (about us) this goes all the way down to the final tag (contact us). Normally you use these tags for pages e.g page 1 - 5 but how much will they affect being used in the way above I'm thinking site structure. Just to add there is no view all on it either though this would make no sense in the way it is being used. Normally I would remove but the client wants to know why and I wanted to articulate better then "because its wrong" As always Moz - thanks!
Technical SEO | | GPainter0 -
Meta description not showing as per view source on Google results
On our website recyclingbins.co.uk the meta decsription of the homepage under view source is - Recycling bins offers the largest range of recycling bins for schools, homes, offices and other venues. With free delivery on everything and lowest prices guaranteed.
Technical SEO | | imrubbish
But if you searched for our website in Google the meta description it shows is: Offers recycling binsfor offices, schools and the home. Someone has already suggested it must be cached. I do not think this could be possible as we are fairly regularly crawled and it has been like this for weeks and weeks. No one seems to have much idea. could you possibly share any light? I am not concerned from an SEO perspective, but more from a click through perspective.Thank youJon0 -
How to handle pagination for a large website?
I am currently doing a site audit on a large website that just went through a redesign. When looking through their webmaster tools, they have about 3,000 duplicate Title Tags. This is due to the way their pagination is set up on their site. For example. domain.com/books-in-english?page=1 // domain.com/books-in-english?page=4 What is the best way to handle these? According to Google Webmaster Tools, a viable solution is to do nothing because Google is good at distinguishing these. That said, it seems like their could be a better solution to help prevent duplicate content issues. Any advice would be much welcomed. 🙂
Technical SEO | | J-Banz0 -
Should all pagination pages be included in sitemaps
How important is it for a sitemap to include all individual urls for the paginated content. Assuming the rel next and prev tags are set up would it be ok to just have the page 1 in the sitemap ?
Technical SEO | | Saijo.George0 -
Rel=cannonical vs. noindex.follow for paginated pages
I"m working on a real estate site that has multiple listing pages, e.g. http://www.hhcrealestate.com/manhattan-beach-mls-real-estate-listings I'm trying to get the main result page to rank for that particular geo-keyword, i.e. "manhattan beach homes for sale". I want to make sure all of the individual listings on the paginated pages, 2,3, 4 etc. still get indexed. Is it better to add to all of the paginated pages, i.e.manhattan-beach-mls-real-estate-listings-2, manhattan-beach-mls-real-estate-listings--3, manhattan-beach-mls-real-estate-listings-4, etc. or is it better to add noindex,follow to those pages?
Technical SEO | | fthead91