Rel Canonical tag usage on ECommerce website
-
Hello,
I have read up on the rel canonical tag and I'm ready to apply it to my site's categorization structure.
However, I'm concerned that, because my website does not have a "view all" button for our product pages, the rel canonical tag would not be appropriate.
For example, if you come to my site's main category url, you come to
At this level - you get the top 12 items in the category.
if you want to see the next page, you click a crawlable link that goes to
etc. etc.
The site does not offer a view all function.
Would applying the rel canonical tag be appropriate in this instance, or do I have to let Google crawl and index each page independantly?
Thanks.
-
Thanks! I understand what you're saying and I agree...this is exactly the method that our CMS generates these pages. The crawlable, additional pages are unique and should be crawled. This being said, from a search engine's perspective, the obvious "canonicalized" page should be the main category. I believe the robots, no index/follow is the best option for me - though I'm not exactly sure how to implement it with our CMS system..
Thanks.
-
Thanks!
Hadn't considered the robots tag like this. Unfortunately, our site's CMS system will make either of these options tough to actually implement. But it's great to know there're some options.
-
Technically, rel=prev/next is more appropriate, but it can be really tough to implement and Bing doesn't honor it.
If the paginated search pages don't have inbound links, you could just use META NOINDEX,FOLLOW on them (pages 2, 3, etc.). It's a lot easier to implement and is still very effective.
-
**if you want to see the next page, you click a crawlable link that goes to **
**mysite.com/main-category12-24 **
**The site does not offer a view all function. **
Would applying the rel canonical tag be appropriate in this instance, or do I have to let Google crawl and index each page independantly?
In this example you actually are talking about 2 different pages and in which case it can be appropriate to use the rel canonical.
Example take a look at a popular plateform like Oscommerce.
The Index.php page generates the following pages
- index.php
- category pages
- sub category pages
These are referenced by the software by the cPath (category Path) and would look much like this
- index.php
- index.php&cPath=1
- index.php&cPath=1_5
To a search engine these are all unique pages. Additionally, since many e-commerce platforms follow this type of module but also have ways to make the pages more SEO friendly you can in some cases access the same page via different URL's which is of course bad, due to duplicate content. In these case a rel canonical is very appropriate.
For example Oscommerce has a SEO friendly URL modification which turns the unspecific URL like index.php&cPath=1 into something like electronics.html However unless some sort of redirect is used you can actually access this page via either URL.
To simplify the answer the rel canonical tag is most appropriate for pages that generate dynamic URL's but content changes very little. In my examples above the pages are very different index.php and a index.php&cPath=1 page, however there can be times when you have interactions on those pages which would create a new url like say adding a product to the cart or a product selection filter, or any score of interactions that may change the url from index.php&cPath=1 to index.php&cPath=1&addToCart1&Product_ID=414&return in this case rel canonical would be very much appropriate as the page is not really changing you're just executing an action.
-
Here's an article from Google webmaster central with instructions on how to impliment it.
http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
And a quick example of implimentation by Yoast for 'Page 2' of results.
http://yoast.com/rel-next-prev-paginated-archives/
Just a quick note, on 'page 1' there should be no rel=prev (your mysite.com/main-category in this case) On on the final page there should be no rel=next. All other pages should have both.
Hope these help.
-
Wow, thanks alot I hadn't heard this was even available. Any chance you could give me a link to where I could find info. to implement?
Thanks again for your help, either way!
-
I'd impliment rel=rev and rel=next on the pages to imply that their paginated, with the first page mentioned being the first in the chain.
rel=canonical then should point to the actual url, not the view-all page.
I think that is the 'correct' implimention for paginated content since rel=prev and rel=next were introduced.
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
-
How to check if the website has duplicate content?
I've been working with the websites from couple of months and it was always in my mind if there could be a legit way to find if the website have a duplicate content. I've tried couple of websites through google but nothing worked for me. It would be much appreciated if anyone can help. Thanks
Web Design | | rajveer_singh0 -
After a website redesign, what is the impact and is it a good practice to use /v2/ naming convention?
Hi mightyful SEOMoz community. We just launched a redesign of our commercial website from https://www.data-field.com to https://www.data-field.com/v2/ All URLs from previous website were 301 permanent redirect to the appropriate page in the new website, and the root domains ( /, /v2/ ) send the users to their own language content /v2/en/, /v2/fr/, /v2/zh/ Up to here everything is fine. But then I setup the usual "Share" buttons, only to find that they were displaying a "0" count. Then I realized that it was because of the root URL change from / to /v2/ My question is the following: 1. Is using /v2/ a good practice? 2. If yes, then should I link the Social tool to https://www.data-field.com/ ( only ) instead of linking it to the actual page in the address bar? Thanks for your answers.
Web Design | | NicolasE0 -
Solutions for too many links on page (Ecommerce)?
Hello Mozzers, Most Ecommerce websites I've come across have four main link sections - Main Nav - About, Contact etc Side Nav - List of Categories + Products Footer - Useful links etc Promotional Area - Promoting Best sellers / Latest products This ends up totalling anything from 200 to 500 links. I was wondering is there a reasonable solution to hide some of the links? Or should I just ignore the warning? Thanks, Dan
Web Design | | Sparkstone0 -
Header tags - big H1s after small H2s
Just spotted bigger H1s and small H2s on a website, in the newsroom. The smaller H2 = section heading (Newsroom), the larger H1 is a news headline. Might that cause me any search engine problems?
Web Design | | McTaggart0 -
Google cache and rel alternate
http://groups.google.com/a/googleproductforums.com/forum/#!searchin/webmasters/rel$20alternate$20not$20works/webmasters/xzwTBJemPss/LyRjRCigZdYJ http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077
Web Design | | ctam
Situation:www.example.ca - canadian IP and https://www.google.com/webmasters/tools/settings:"Your site's domain is currently associated with the target: Canada" - done long time ago.<head><link rel="canonical" href="http://www.example.ca/" /> <link< span="">rel="alternate" hreflang="en-us" href="http://www.example.com/" /></link<><link rel="alternate" hreflang="en-ca" href="http://www.example.ca/" /><link rel="alternate" hreflang="en" href="http://www.example.com/" />```
www.example.com - US IP and
https://www.google.com/webmasters/tools/settings:
"Geographic target Target users in: United States" done long time ago.
<head><link rel="canonical" href="http://www.example.com/" /> <link< span="">rel="alternate" hreflang="en-us" href="http://www.example.com/" /><link rel="alternate" hreflang="en-ca" href="http://www.example.ca/" />
<link rel="alternate" hreflang="en" href="http://www.example.com/" /> Differences: Prices and some minor changes in design. cache:www.example.com - shows .ca version,
with snapshot's date after rel="alternate" had been added.
Results: In usexample.com pages do not appear in search results.
Some times www.example.ca pages do,
but they are even close so well ranked as example.com pages before. Question: What we are doing wrong?</link<>0 -
Bing free mobile website
When editing my Bing business listing, I have noticed that they offer a free mobile website. I was actually looking to build one and I'm not sure if this is what I'm looking for. I want to be able to customize it as well. Anybody tried it already? arBS3.jpg
Web Design | | echo10 -
How do you visualize website structure
How do you visualize a website structure in terms of (categories of) pages and interlinking. I use such visuals for discussing what you are actually doing now and what can be improved. I have made visuals I few times myself (basically making boxes representing categories of pages and lines representing internal links), but I found that I soon ran into a scheme of huge proportions and needed more paper and more time. Appreciate your thoughts!
Web Design | | NewBuilder2