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 -
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 -
Getting the Titles and Headings Right on Product Pages. Userbility vs SEO
Hey Mozzers, I am optimising a chaotic section of the site including many similar products. Writing unique content etc. The titles and urls were all over the place so my first job was to tidy them up so I could make some sense of the situation, especially as sometimes they didn't even match! I should point out were on Magento, so product name = Both the Heading and Title of the page, the meta title can be set separately. When i refer to title I mean both <title>and <h1></strong><br /><br />Before they existed as such<br />URL: domain.com/200-x-0-5-g-rs-232-balance.html<br />TItle: PC-1234 200 x 0.5g x 0.3 RS-232 Balance<br /><br />This format was (Product Code, Capacities, Resolutions, Accuracy, Product Title)<br /><br />The issue was all 60 products in a page followed this format. Navigating through the page was a nightmare and was just a jumble of numbers and highly confusing even to me who learnt what they all mean, especially when you had 8 products from the same range you got presented with<br /><br />APC-1234 200 x 0.5g x 0.3 RS-232 Balance<br />APC-1235 500 x 1g x 0.3 RS-232 Balance<br />APC-1236 1000 x 2g x 0.3 RS-232 Balance<br />APC-1238 5000 x 10g x 0.3 RS-232 Balance<br />APC-1239 10000 x 15g x 0.3 RS-232 Balance<br />APC-1210 20000 x 25g x 0.3 RS-232 Balance<br />APC-1211 50000 x 50g x 0.3 RS-232 Balance</p> <p>I changed them to something more user friendly.<br /><br />URL: domain.com/200g-precision-balance.html<br />Title: 200g Precision Balance<br /><br />This has seen the following benefits<br />- URL is now clear and means something to the user<br />- Product titles are easy to navigate and the page is more pleasing to the eye<br />- The jumble of numbers in the title are now all labelled and shown below each product listing in bullet point so the user can see the basic spec of a product without having to decipher any titles<br /><br />Upon reflection I has a couple of concerns I was hoping you could discuss, I am wondering if I have made the titles too simple.<br />1) I have no product code in the title<br />We have our own products manufactured and sell existing brands with their own product codes. Some of these can be lengthy. Adding them makes them hard to the eye and the page looked cramped.<br /><br />The codes are listed beneath each product title on category pages and on a list on the actual product page, but no where in the titles. <br /><br />2)None of our products have a brand listed in the title<br />None of the products on the site had brand names in anything but the images when i started and as such it snuck under my radar. But should i pre-fix all titles with a brand name?<br /><br />Should </p> <p>URL: domain.com/200g-precision-balance.html<br />Title: 200g Precision Balance</p> <p>become</p> <p>URL: domain.com/BRAND1-200g-precision-balance.html<br />Title: BRAND1 200g Precision Balance<br /><br />My instinct tells me to change things to include brands as its useful to the customer and should have an SEO benefit, but to leave out product codes as they are accessible to the customer where they are now and dont make things messy and unreadable.<br /><br />As always, thanks for the input!</p></title>
On-Page Optimization | | ATP0 -
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 -
Home page or landing page?
Hello, I want to ask a question related to that - Should we put keywords in the home page title if we wish to position another landing page better for particular keywords? I have read in one website about SEO that it's good the main keywords of your website to be positioned in homepage title also. f.e. Let's say we have website about web-design and our company is named Company Ltd. The title of the home page is "Company Ltd. - Web design, SEO, etc" We have also another inner page named "Web design | Company Ltd.". So should we leave the first page name only "Company Ltd." and the landing page's name "Web design | Company Ltd." . I don't know if they both have the same keyword in their title they won't compete with each other.
On-Page Optimization | | HrishikeshKarov0 -
Different page for each product colour?
Hi Guys, I've just read an ecommerce article that suggests it's a good idea to have a different page for each colour that the product comes in. However surely this will mean duplicate content? What are your thoughts? Have you put this tactic into motion and how did it go? Thanks, Dan
On-Page Optimization | | Sparkstone0 -
How to Define Best URL Structure for Product Pages?
I am working on my website to edit structure with help of Google's search engine optimization starter guide. There is really good instruction to define URL structure which help us to perform well over Google's organic search. I have resolved issues regarding category pages but, I have confusion to define best URL structure for product pages. My website's product page URL structure is as follow. http://www.vistastores.com/marketumbrellas-californiaumbrella-slpt758-f13-red.html http://www.vistastores.com/homefurniture-winsomewood-93630.html URL structure is constructed with following terms. 1. Root Category Name (Market Umbrellas or Home Furniture or ....) 2. Brand Name 3. Manufacturer Part Number I am not happy with this structure and also not performing well over Google's organic search. I am thinking to include product name or title tag in URL after root domain. But, it may create very long URL and create issues in organic search display. Does it really matter to perform well over Google's organic search? How can I define best URL structure for product pages?
On-Page Optimization | | CommercePundit0 -
Creating New Pages Versus Improving Existing Pages
What are some things to consider or things to evaluate when deciding whether you should focus resources on creating new pages (to cover more related topics) versus improving existing pages (adding more useful information, etc.)?
On-Page Optimization | | SparkplugDigital0
