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
-
What website changes (technical) SEOs can ignore confidently? Google's perspective!
Hi community members, I am looking after SEO at our company and there are lots of changes happening about our website; especially technical changes. It's hard for me to look after every deployment of the website like change of server location, etc. We generally agree that every change related to website must be notified by SEO to understand the ranking fluctuation and how search engines welcome them. I just wonder what technical deployments of a website I could confidently ignore to save time and give a go ahead to technical team without interrupting or waiting for my approval. Thanks
Web Design | | vtmoz1 -
Creating a new website, but I'd like to control it under a different domain.
I'd like to control it under the domain of another website with a higher DA. Can I create the new website (website A) and do an immediate re-direct to another website (website B)? Or would I be better at putting it as a subdomain? Such as www.websitea.websiteb.com? Cheers all, Rhys
Web Design | | SwanseaMedicine0 -
Is there a best practice for how to set up an Age Restriction prompt for a website (vape equiptment)
I am working on a website that sells vape equipment and supplies and is required to have an age restriction (birthday) prompt in order to enter the site. Is there a 'best practice' way to implement this?
Web Design | | RandolphMorris0 -
Rel=next and rel=prev meta tags
Hi,
Web Design | | RocoClothing
We have recently implemented the rel=next and rel=prev meta tags on the
category pages of our website. Currently for example if on page 2 we have the following: href="http://www.rococlothing.co.uk/boys/boys-suits/" />
href="http://www.rococlothing.co.uk/boys/boys-suits/?p=1" />
href="http://www.rococlothing.co.uk/boys/boys-suits/?p=3" /> For each page we are using the same canonical tag which is the url for
the 1st page in the category.
Is this the correct way to impletment it or should the canonical tag for
page 2 be as follows: href="http://www.rococlothing.co.uk/boys/boys-suits/?p=2" /> I have also seen some companies ommiting the canonical tag on pages
after page 1 and just using the prev and nexts. Could anyone advise as to what the ideal implementation would be for this? Regards
Patrick0 -
New Website Redesign: Any Design Comments or SEO Suggestions?
Hi! We recently launched our new website after MONTHS of work. Now that it is live, we are looking to fine tune the design and SEO efforts. This is our new website. And for reference, this is our old website. Any and all comments on design and SEO would be greatly appreciated. Thank you for your help! Mike
Web Design | | Mike.Goracke0 -
Too Many On Page Links, rel="nofollow" and rel="external"
Hi, Though similar to other questions on here I haven't found any other examples of sites in the same position as mine. It's an e-commerce site for mobile phones that has product pages for each phone we sell. Each tariff that is available on each phone links through to the checkout/transfer page on the respective mobile phone network. Therefore when the networks offer 62 different tariffs that are available on a single phone that means we automatically start with 62 on page links that helps to quickly tip us over the 100 link threshold. Currently, we mark these up as rel="external" but I'm wondering if there isn't a better way to help the situation and prevent us being penalised for having too many links on page so: Can/should we mark these up as rel="nofollow" instead of, or as well as, rel="external"? Is it inherently a problem from a technical SEO point of view? Does anyone have any similar experiences or examples that might help myself or others? As always, any help or advice would be much appreciated 🙂
Web Design | | Tinhat0 -
ECommerce and microdata
Last year I rolled my own online shop and I included schema.org microdata for all the products. My Google ranking continued to improve during that period, but I was doing a number of improvements, so I can't say how much was due to the microdata. My store continues to grow so I moved to an eCommerce solution. I opted to go with Volusion. Much to my surprise, about the only SEO feature they have implemented is SEO friendly URLs. They have not implemented microdata, which is pretty surprising given that all their sites are geared towards products. I would think it would be very easy for them to span the product name, description, price, etc, with a product schema. I called CoreCommerce, a Volusion competitor, and they have not implemented microdata either. Why are these large eCommerce providers ignoring microdata? Are there eCommerce solutions that have implemented microdata? Do large online retailers like Amazon and Buy use microdata? Is there any data that shows the SEO benefits of implementing microdata for an online store? Best,
Web Design | | ChristopherGlaeser
Christopher0 -
Website redesign testing environment
An external company is redesigning our website. They have a draft version active in a folder on their website to enable us to view it (example: www.externalcompanywebsite.com/ourwebsite/). There is no permission required to view the website, anyone with the url could just go there. I am not sure if they're using the robots.txt to block crawlers, or if they're blocking specific ip addresses. If the engines are allowed to crawl their website and they index pages of our draft website, does that affect our website negatively in the future once we host it on our domain?
Web Design | | jdossetti0