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
-
Question on Pagination - /blog/ vs /blog/?page=1
Question on Pagination Because we could have /blog/ or /blog/?page=1 as page one would this be the correct way to markup the difference between these two URL? The first page of a sequence could start with either one of these URLs. Clarity around what to do on this first page would be helpful. Example… Would this be the correct way to do this as these two URLs would have the exact content? Internal links would likely link to /blog/ so signal could be muddy. URL: https://www.somedomain.com/blog/
Technical SEO | | jorgensoncompanies
<link rel="canonical" href="https://www.somedomain.com/blog/?page=1"> URL: https://www.somedomain.com/blog/?page=1
<link rel="canonical" href="https://www.somedomain.com/blog/?page=1"> Google is now saying to just use the canonical to the correct paginated URL with page number. You can read that here:
https://developers.google.com/search/docs/advanced/ecommerce/pagination-and-incremental-page-loading But they do not clarify what to do on /blog/?page=1 vs /blog/ as they are the exact same thing. Thanks for your help.0 -
Paginated pages are being indexed?
I have lots of paginated pages which are being indexed. Should I add the noindex tag to page 2 onwards? The pages currently have previous and next tags in place. Page one also has a self-referencing canonical.
Technical SEO | | WTH0 -
Canonical Url Structure Vs. Google Search View
I recently set up a new site and set the "preferred" domain in Google Webmasters to show URLs WITHOUT the WWW for google search purposes. In the confirmation email from google, this confused me: "This setting defines which host - www or not - should be considered the canonical host when indexing your site." In the website, we have cononical URLS at the top of every page in the header, but still have the WWW in those. Any issues with that?
Technical SEO | | vikasnwu0 -
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 -
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 -
Best Way to Break Down Paginated Content?
(Sorry for my english) I have lots of user reviews on my website and in some cases, there are more than a thousand reviews for a single product/service. I am looking for the best way to break down these reviews in several sub-pages. Here are the options I thought of: 1. Break down reviews into multiple pages / URL http://www.mysite.com/blue-widget-review-page1
Technical SEO | | sbrault74
http://www.mysite.com/blue-widget-review-page2
etc... In this case, each page would be indexed by search engines. Pros: all the reviews are getting indexed Cons: It will be harder to rank for "blue widget review" as their will be many similar pages 2. Break down reviews into multiple pages / URL with noindex + canonical tag http://www.mysite.com/blue-widget-review-page1
http://www.mysite.com/blue-widget-review-page2
etc... In this case, each page would be set to noindex and the canonical tag would point to the first review page. Pros: only one URL can potentially rank for "blue widget review" Cons: Subpages are not indexed 3. Load all the reviews into one page and handle pagination using Javascript reviews, reviews, reviews
more reviews, more reviews, more reviews
etc... Each page would be loaded in a different which would be shown or hidden using Javascript when browsing through the pages. Could that be considered as cloaking?!? Pros: all the reviews are getting indexed Cons: large page size (kb) - maybe too large for search engines? 4. Load only the first page and load sub-pages dynamically using AJAX Display only the first review page on initial load. I would use AJAX to load additional reviews into the . It would be similar to some blog commenting systems where you have to click on "Load more comments" to see all the comments. Pros: Fast initial loading time + faster loading time for subpages = better user experience Cons: Only the first review page is indexed by search engines ========================================================= My main competitor who's achieving great rankings (no black hat of course) is using technique #3. What's your opinion?0 -
Rel next prev, should i nofollow pagination links
Hi Everyone. When implementing rel next and prev on pagination pages, should I make the pagination links themselves no followed? Have seen people saying yes and no so just want a final answer! Thanks
Technical SEO | | Sayers0 -
Best usage of rel canonical in case of pagination for content list ?
I've looked at most of the question in the Q&A who speak about pagination but didn't find a clear answer to my concern. So here is my question : On the website i work for, we have list of recipes with this info for each recipe : picture, title, type, difficulty, time and author. 10 recipes per pages and X pages for each list. Would you use link rel canonical on page X with first page as value ? (i've seen this answer in one question here)
Technical SEO | | kr0hmy
Or canonicalize to page X keeping each page of the list in the index ?
Would the content be seen as duplicate if we don't use rel canonical and just add page X in the title? Or would it be unique enough with all the infos? Thanks for your help on this !0