Which Pagination/Canonicalization Page Selection Approach Should be Used?
-
Currently working on a retail site that has a product category page with a series of pages related to each other i.e. page 1, page 2, page 3 and Show All page. These are being identified as duplicate content/title pages. I want to resolve this through the applications of pagination to the pages so that crawlers know that these pages belong to the same series. In addition to this I also want to apply canonicalization to point to one page as the one true result that rules them all. All pages have equal weight but I am leaning towards pointing at the ‘Show All’. Catch is that products consistently change meaning that I am sometimes dealing with 4 pages including Show All, and other times I am only dealing with one page (...so actually I should point to page 1 to play it safe). Silly question, but is there a hard and fast rule to setting up this lead page rule?
-
Hello Oxfordcomma,
If you have fast page load times on the view all pages you can make those canonical. This is Google's recommendation: http://googlewebmastercentral.blogspot.com/2011/09/view-all-in-search-results.html .
If those pages can be large and cause latency issues (slow loading) the better option would be rel next/prev and none of them would be "canonical" for the others, as they would each stand on their own. You may consider at that point adding a robots noindex,follow tag to the View All page, but Google generally does a very good job of figuring this out on their own and I prefer to let them do it.
In summary: If you have good View All pages with fast load times use those as canonical, regardless of how many products you have (e.g. 5 or 25) as long as no latency issues are apparent. Use this tool to test it: https://developers.google.com/speed/pagespeed/insights . If the View All pages are too big for most of your categories to load fast go with Rel Next Prev.
Rel Next Prev info:
http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
View All Canonical info:
http://googlewebmastercentral.blogspot.com/2011/09/view-all-in-search-results.html
It can get a little more complicated if you are dealing with pagination AND faceted search or multiple URL parameters acting as filters.
-
Firstly, thanks for the response. I think I was not clear enough in my explanation. I am currently dealing with a category page for towels - showing the full mix of towels (make and brand) that the site has to offer, 50+ products e.g.
/towels (aka /towels-p1)
/towels-p2
/towels-p3
/towels-show-all (show all allows you to view all results from above pages)Meta details attached to the above are from the one source hence duplication issues.
This is why I thought poagination/canonicalization would be applicable. Thanks for reviewing my question.
-
You should rel=canonical only in cases you have duplicate content, which may be case when
1. You want to have both pages available
2. You have similar content due to some choices at your page- you have pages for 10 items and 20 items per page while this list has only 5 items in it so both pages showing same content.
3. You need to control the level of parameters you want search engines to take care of. For e.g. you have 3 parameters state, city, street but as taking all three together will give you a lot of data so you may be just going upto city even when street was there in URL.
Also you should use re=prev and rel=next for URLs with pagination.
You can read more about it at http://googlewebmastercentral.blogspot.in/2011/09/pagination-with-relnext-and-relprev.html
-
Hey there,
If each page has unique content, you don't want to use canonicalization as you wont get the "SEO Juice" from each individual page.
What I would do is modify the page title for each page.
For example, "Green Widgets - Page 2 | Cheapwidgets.com"Does that make sense?
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
-
'domain:example.com/' is this line with a '/' at the end of the domain valid in a disavow report file ?
Hi everyone Just out of curiosity, what would happen if in my disavow report I have this line : domain:example.com**/** instead of domain:example.com as recommended by google. I was just wondering if adding a / at the end of a domain would automatically render the line invalid and ignored by Google's disavow backlinks tool. Many thanks for your thoughts
Technical SEO | | LabeliumUSA0 -
Spam pages / content created due to hack. 404 cleanup.
A hosting company's server was hacked and one of our customer's sites was injected with 7,000+ pages of fake, bogus, promotional content. Server was patched and spammy content removed from the server. Reviewing Google Webmaster's Tools we have all the hacked pages showing up as 404's and have a severe drop in impressions, rank and traffic. GWT also has 'Some manual actions apply to specific pages, sections, or links'... What do you recommend for: Cleaning up 404's to spammy pages? (I am not sure redirect to home page is a right thing to do - is it?) Cleaning up links that were created off site to the spam pages Getting rank bank // what would you do in addition to the above?
Technical SEO | | GreenStone0 -
Webmasters tools - Need to update every time you add a new product/page to an ecommerce
Hi guys, I run an ecommere store and we are constantly receiving and uploading new products. Do we need to update the sitemap every time we upload a product? Google Webmasters tools shows that the number of URLs received is higher than the number of indexed URLs. They should match right? Thanks and regards
Technical SEO | | footd0 -
50,000 pages or a page with parameters
I have a site with about 12k pages on a topic... each of these pages could use another several pages to go into deeper detail about the topic. So, I am wondering, for SEO purposes would it be better to have something like 50,000 new pages for each sub topic or have one page that I would pass parameters to and the page would be built on the fly in code behind. The drawback to the one page with parameters is that the URL would be static but the effort to implement would be minimal. I am also not sure how google would index a single page with parameters. The drawback to the 50k pages model is the dev effort and possibly committed some faux pas by unleashing so many links to my internal pages. I might also have to mix aspx with html because my project can't be that large. Anyone here ever have this sort of choice to make? Is there a third way I am not considering?
Technical SEO | | Banknotes0 -
Double Slash // in URL
My client is using double forward slahes in URL like this "//" is this affecting SEO?
Technical SEO | | yanaiguana1110 -
Maximum <title>length - use full or shorten?</title>
I have a Title on a page that has more than 70 chars in it, and I also have to include the page type and brand in the title. page type: Type page header: This is the page title of the long title and I need to add more content brand: Brand Is it better to concanenate the title server-side and use a .. instead, like this? Type: This is the page title of the long title and I need to.. | Brand Or, should I put the full Title of the page so that the keywords are available for Google? example, Type: This is the page title of the long title and I need to add more content | Brand I'm trying to keep to the 70 char limit for Google. Which solution is the more ideal situation? Thanks all jonathan
Technical SEO | | JDatSB0 -
How can I prevent duplicate content between www.page.com/ and www.page.com
SEOMoz's recent crawl showed me that I had an error for duplicate content and duplicate page titles. This is a problem because it found the same page twice because of a '/' on the end of one url. e.g. www.page.com/ vs. www.page.com My question is do I need to be concerned about this. And is there anything I should put in my htaccess file to prevent this happening. Thanks!
Technical SEO | | onlineexpression
Karl0 -
Is there any issue with using the same structured data property multiple times on the same page?
Im working on implementing structured data properties into my product detail pages. (http://schema.org/Book) My site sells books and many books have both a 13 digit ISBN # and a 10 Digit ISBN. Should I apply the itemprop "isbn" to both of them or just the one with higher search volume? Some books also have multiple authors, how should I handle that?
Technical SEO | | myork07240