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.
Pagination for product page reviews
-
Hi,
I am looking to add pagination on product pages (they have lots of reviews on the page). I am considering using rel="next/prev, to connect the series of review pages to the main product page.
I unfortunately don't have a view-all page for these reviews or the option to get one - the reviews refresh on the same product page (by clicking whatever number page of reviews). This means each page has the exact same description content and everything else, but with different reviews. In this case is rel=next a good option?
The format currently would be:
link rel="next" href="http://example.com/product?review-p2"
link rel="prev" href="http://example.com/product, link rel="next" href="http://example.com/product?review-p3 etc.
Would this be a good format for product page reviews? I see rel=nextprev commonly used on ecommerce category/list pages but not really on the paginated reviews on product pages, so I thought I would see if anyone has advice on how best to solve this.
I'm also wondering if it would be best to not combine this with a canonical tag on all the different review pages pointing to the product page, seeing as the reviews are actually different (despite the rest of the content being identical).
I am hoping to pick up longer tail traffic from this, I figure by connecting the pages and not using canonicals that this way I could get more traffic from the phrases used in the reviews. By leaving out the canonicals, is it possible a user searching for phrases that might be deeper in the series, to land on, say, ?review-p4? Any thoughts if this would drive more traffic?
Thanks!.
-
Hi Mihai,
Thanks for your reply. I also have parameter URL's on some of these pages, which are mainly used when I send email campaigns to the same targeted pages, but with slightly modified content such as a custom banner on it. These pages are all noindexed but are helpful for targeted campaigns. In these cases the landing page still has the same paginated reviews series at the bottom.
How would I treat these? For example:
http://www.example.com/product?custombanner
In these situations would i use the following for the paginated review URL's?:
http://www.example.com/product?custombanner&review-p2 in conjuction with a canonical tag to http://www.example.com/product?review-p2, or could I just leave it as pointing to http://www.example.com/product?review-p2 (ie no need to have unique review pages for the parameter pages with canonicals)?
Thanks
-
Thanks Mihai, that's exactly what I was thinking. I'll go ahead with this.
Now that this is all solved I can go relax by the pool and take it easy
-
Hey pikka,
You can actually use both rel=next/prev and rel=canonical on the same webpage, but you have to be careful on how you use them.
If you don't have a view-all page, then DO NOT use rel=canonical on the review-pX page to point to the main product page. That's like saying "This page has identical content as the other one, so please disregard this one and use the other instead". It's somewhat of a 301 redirect, which would DEINDEX your review-pX pages.
However, using rel=next/prev is perfectly fine, and it's actually the recommended method when there's no view-all page. You can still use rel=canonical but only to point to the current review page (so basically you would use this just to filter out session IDs or any other parameters that lead to duplicate content).
So, in your case, you should use them like this (let's say we're on page 3):
<-- current page, "clean" url
<-- previous page, can contain parameters
<-- next page, can contain parametersDo NOT use this:
Hope this helps, here's the Google support page on this issue and Maile Ohye's excellent video explaing it.
PS: Almost forgot, regarding your avatar:
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
-
FAQ page structure
I have read in other discussions that having all questions on an FAQ page is the way to go and then if the question has an answer worthy of its own page, you should abbreviate the answer and link to the page with more content. My question is when using some templates in WP, they have a little + button you can click and it reveal the answer to the question. Does this hurt SEO versus having all text visible and then using headers/subheaders? An example of the + button https://fyrfyret.dk/faq/
On-Page Optimization | | OrlandSEO1 -
Is it better to keep a glossary or terms on one page or break it up into multiple pages?
We have a very large glossary of over 1000 industry terms on our site with links to reference material, embedded video, etc. Is it better for SEO purposes to keep this on one page or should we break it up into multiple pages, a different page for each letter for example? Thanks.
On-Page Optimization | | KenW0 -
Product content length & links within product description
Hello, I have questions regarding content length and links within descriptions. With our ecommerce site, we have thousands of products, each with a unique description. In the product description, I have links to the parent category and grandparent category (if it has one) in the main product text which is generally about 175 words. Then I have a last paragraph that's about 75 words that includes links to our main homepage and our main product catalogue page. Is the content length long enough? I used to use text that was 500 words, and shortening it I still rank when launching new products, so I don't think an increase in text length will have any additional benefit. I do see conflicting information when I do searches, with some people recommending a minimum of 300 words and some saying to try and go a 1000 for category pages. In regards to the links, I noticed a competitor has stopped following this format, so I'm unsure if I should keep going too. Is it too many links to have each of the products link back to the main catalogue and homepage? Is it good to have links with anchor text to the categories a product is in? There are breadcrumbs on the page with these links already. There are already have heaps of links on our pages (footer, and a right sidebar with image links to relevant categories), so my pages do get flagged for too many links. Thanks!
On-Page Optimization | | JustinBSLW0 -
How do you make product pages unique when there are thousands of products?
When an ecommerce site has 200 product pages, this is fine. It's time consuming, but I can write 200 unique paragraphs describing the product and it's not an insane amount of work for one person. But when there are 10,000+ product pages... what is the best way for one person to go about this? Risk the page being thin and just bullet point a couple of "need-to-know" info bits, or take the time to prioritise what products could benefit the most from the unique content and get cracking with a paragraph for each? Or do you just forego having truly unique copy on each product page and just aim to optimise the category pages for the longtail? Just wondering how you guys deal with thousands of product pages really. Starting to feel as if I should re-evaluate my strategy and wanted to get some idea on what others are doing... Notes: Product pages already have reviews, helps with adding more unique user-generated content to each page. There's dynamic content e.g. "You may be interested in...", "Related products", etc.
On-Page Optimization | | Ria_3 -
Is it convinient to use No-Index, Follow to my Paginated Pages?
I have a website http://www.naukrigulf.com and it has a lot of Paginated pages on its SERP and most of paginated pages are getting indexed in Google SERP. Is it beneficial to use No-Index, Follow to keep the link equity to main (first page), although we have already used rel=next and rel=prev. If Answer is "yes" is their any harm by using no-index, follow with rel=next, rel=prev.
On-Page Optimization | | vivekrathore0 -
One site with one product or multi product website
Lets suppose that i have 10 NICHE products under me. Should i make one site for each product or one site overall. If i make 1 site for each product i get several advantages Domain name has keyword Title tags etc will be dedicated to one keyword only. Disavantage - Backlinking for each domain will become tougher. Advantage of one site onl Good management Seo / backlinks becomes easier Blogging to attract traffic becomes easier Can target a lot of keywords through business blogging Disadvantages Can become messy with unimportant keywords gaining importance. SO WHAT DO YOU THINK??? One site per product or One site for all products?
On-Page Optimization | | hith2340 -
Related products - random products or static
Hello, I was curious about where to get related products from. Currently I just grab some random products from the same category. Would there be any benefit to always linking to the same related products on a product page? Thanks
On-Page Optimization | | nux0 -
How to handle Meta Tags on Pagination... page 2,3,4....
Seems that SEOMoz reports are considering my paginated pages as duplicate Meta Tags. For example, I have a product catalog with 5 paginated pages. Obviously the content on each page is unique and the URL ends in =4, =5 for the page number, but the Title and Description are the same for all the pages. Any suggestions on how to handle this? The pages other than page 1 are not indexed, so it should not be a big deal. But wondering if I should programatically ad the page number to the additional pages to show a difference?
On-Page Optimization | | paddlej0