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
-
What is the best meta description for Category Pages, Tag Pages and Main Article?
Hi, I want to index all my categories and tags. But I fear about duplicating the meta description. for example: I have a tag name "Learn Stock Market", a category name "Learning", and a main article "What is Stock Market". What is your suggestion for meta description of these three pages that looks great for seo google?
On-Page Optimization | | mbmozmb0 -
Landing page separate from product page
Hello there, I have a wordpress website with a woocommerce plugin. I have 4 landing pages that describe my products and at the end of the pages, I have a CTA to my product page. is it bad for SEO? my website: https://relationadviser.ir
On-Page Optimization | | Aaron.be1 -
Why are http and https pages showing different domain/page authorities?
My website www.aquatell.com was recently moved to the Shopify platform. We chose to use the http domain, because we didn't want to change too much, too quickly by moving to https. Only our shopping cart is using https protocol. We noticed however, that https versions of our non-cart pages were being indexed, so we created canonical tags to point the https version of a page to the http version. What's got me puzzled though, is when I use open site explorer to look at domain/page authority values, I get different scores for the http vs. https version. And the https version is always better. Example: http://www.aquatell.com DA = 21 and https://www.aquatell.com DA = 27. Can somebody please help me make sense of this? Thanks,
On-Page Optimization | | Aquatell1 -
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 -
Listing all services on one page vs separate pages per service
My company offers several generalized categories with more specific services underneath each category. Currently the way it's structured is if you click "Voice" you get a full description of each voice service we offer. I have a feeling this is shooting us in the foot. Would it be better to have a general overview of the services we offer on the "Voice" page that then links to the specified service? The blurb about the service on the overview page would be unique, not taken from the actual specific service's page.
On-Page Optimization | | AMATechTel0 -
Noindex child pages (whose content is included on parent pages)?
I'm sorry if there have been questions close to this before... I've using WordPress less like a blogging platform and more like a CMS for years now... For content management purposes we organize a lot of content around Parent/Child page (and custom-post-type) relationships; the Child pages are included as tabbed content on the Parent page. Should I be noindexing these child pages, since their content is already on the site, in full, on their Parent pages (ie. duplicate content)? Or does it not matter, since the crawlers may not go to all of the tabbed content? None of the pages have shown up in Moz's "High Priority Issues" as duplicate content but it still seems like I'm making the Parent pages suffer needlessly... Anything obvious I'm not taking into consideration? By the by, this is my first post here @ Moz, which I'm loving; this site and the forums are such a great resource! Anyways, thanks in advance!
On-Page Optimization | | rsigg0 -
Add content as blog post or to product pages?
Hi, We have around 40 products which we can produce plenty of in-depth and detailed "how to"-type pieces of content for. Our current plan is to produce a "How to make" style post for each as a long blog post, then link that to the product page. There's probably half a dozen or more of these kind of blog posts that we could do for each product. The reason why we planned on doing it like this is that it would give us plenty of extra pages (blog posts) on their own URL which can be indexed and rank for long tail keywords, but also that we can mention these posts in our newsletter. It'd give people a new page full of specific content that they can read instead of us having to say "Hey! We've updated our product page for X!", which seems a little pointless. Most of the products we sell don't get very many searches themselves; Most get a couple dozen and the odd few get 100-300 each, while one gets more than 2,000 per month. The products don't get many searches as it's a relatively unknown niche when it comes to details, but searches for the "categories" these products are in are very well known (Some broad terms that cover the niche get more than 30,000+ searches a month in the UK and 100,000+ world wide) [Exact].
On-Page Optimization | | azu25
Regarding the one product with more than 2,000 searches; This keyword is both the name of the product and also a name for the category page. Many of our competitors have just one of these products, whereas we're one of the first to have more than 6 variations of this product, thus the category page is acting like our other product pages and the information you would usually find on our product pages, is on the category page for just this product. I'm still leaning towards creating each piece of content as it's own blog post which links to the product pages, while the product pages link to the relevant blog posts, but i'm starting to think that it may be be better to put all the content on the product pages themselves). The only problem with this is that it cuts out on more than 200 very indepth and long blog posts (which due to the amount of content, videos and potentially dozens of high resolution images may slow down the loading of the product pages). From what I can see, here are the pros and cons: Pro (For blog posts):
1. More than 200 blog posts (potentially 1000+ words each with dozens of photos and potentially a video)..
2. More pages to crawl, index and rank..
3. More pages to post on social media..
4. Able to comment about the posts in the newsletter - Sounds more unique than "We've just updated this product page"..
5. Commenting is available on blog posts, whereas it is not on product pages..
6. So much information could slow down the loading of product pages significantly..
7. Some products are very similar (ie, the same product but "better quality" - Difficult to explain without giving the niche away, which i'd prefer not to do ATM) and this would mean the same content isn't on multiple pages.
8. By my understanding, this would be better for Google Authorship/Publishership.. Con (Against blog posts. For extended product pages):
1. Customers have all information in one place and don't have to click on a "Related Blog posts" tab..
2. More content means better ability to rank for product related keywords (All but a few receive very few searches per month, but the niche is exploding at an amazing rate at the moment)..
3. Very little chance of a blog post out-ranking the related product page for keywords.. I've run out of ideas for the 'Con' side of things, but that's why I'd like opinions from someone here if possible. I'd really appreciate any and all input, Thanks! [EDIT]:
I should add that there will be a small "How to make" style section on product pages anyway, which covers the most common step by step instructions. In the content we planned for blog posts, we'd explore the regular method in greater detail and several other methods in good detail. Our products can be "made" in several different ways which each result in a unique end result (some people may prefer it one way than another, so we want to cover every possible method), effectively meaning that there's an almost unlimited amount of content we could write.
In fact, you could probably think of the blog posts as more of "an ultimate guide to X" instead of simply "How to X"...0 -
H1 Tags on Volusion Product Pages
So I'm working with a client who has no heading tags on his site and I'm wondering if there is an ideal method to implementing these on the product pages specifically, as the wording I ideally want to specify is is the product title, which i can't really code with an H1. Has anyone run into this issue? If so, what was your solution? Also, how vital are these heading tags on the product pages, anyways? If the Volusion SEO expert could chime in, that would be much appreciated. Thanks everyone!
On-Page Optimization | | BrandLabs0