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
-
Have Your Thoughts Changed Regarding Canonical Tag Best Practice for Pagination? - Google Ignoring rel= Next/Prev Tagging
Hi there, We have a good-sized eCommerce client that is gearing up for a relaunch. At this point, the staging site follows the previous best practice for pagination (self-referencing canonical tags on each page; rel=next & prev tags referencing the last and next page within the category). Knowing that Google does not support rel=next/prev tags, does that change your thoughts for how to set up canonical tags within a paginated product category? We have some categories that have 500-600 products so creating and canonicalizing to a 'view all' page is not ideal for us. That leaves us with the following options (feel it is worth noting that we are leaving rel=next / prev tags in place): Leave canonical tags as-is, page 2 of the product category will have a canonical tag referencing ?page=2 URL Reference Page 1 of product category on all pages within the category series, page 2 of product category would have canonical tag referencing page 1 (/category/) - this is admittedly what I am leaning toward. Any and all thoughts are appreciated! If this were in relation to an existing website that is not experiencing indexing issues, I wouldn't worry about these. Given we are launching a new site, now is the time to make such a change. Thank you! Joe
Web Design | | Joe_Stoffel1 -
What Website Platform would you use?
We are considering 1 maybe 3 websites (1 new 2 redesign) there are so many options with technology rolling over every 3 years it seems. Here are my obstacles: Wordpress: dynamic but easily hacked, often needs updating Joomla: attractive, but cumbersome to manage Custom: sleek and easier to manage, but gets outdated quickly Here are some variables: 80+ products, E-Commerce, Dynamic, Blog, Tons of images, SEO friendly, MUST not lose our rankings! OK, Moz friends, What do you recommend?
Web Design | | KevnJr0 -
Are jobsite themes harder to optimize than say a traditional website?
Until recently I have enjoyed a great deal of success with SEO on my websites and clients websites. SEO is more of a hobby than a profession for me however I am really struggling with my latest website www.securityjobsuk.co.uk - The keywords are easy, 1. security jobs and 2. security vacancies. The site has vanished off radar completely since I used the jobify theme. Has anyone had similar experience with job boards? Do they require more TLC / expert attention?
Web Design | | SJUK0 -
Does meta "Expires" tag affect website cacheing or indexing?
One of our client has a meta expire tag across all pages of their website. Does that tag affect the website overall caching or indexing? Their website pages including home page is crawled every 10 days, however the website is popular high traffic websites, receiving 240,000 visits/month. Please advise what impact this tag will have on the website indexing and caching? Thanks Atomic Team
Web Design | | JamesDixon700 -
Best Practice For Website Redesign & Migration
Hi, I'm looking to redesign my current live website to a new Wordpress site using "Studiopress Enterprise Theme". I'm new to Wordpress and therefore will be embarking on lots of testing & development.
Web Design | | Mark_Ch
I do not want to hurt my current live website whilst testing the new Wordpress site. However, it would be nice to bring the test site into the current live environment without changing untold urls, etc. Question
What is the best practice to setup this new Wordpress environment for my domain: www.sampledomain.co.uk How would you restrict Google, Bing, etc from indexing, etc. whilst testing in the live environment. What other consideration should I be aware of Thanks Mark0 -
Does Google follow links inside a <noscript>tag?</noscript>
I'm looking at making an embedable calculator and asking users to embed it to their website. I had the idea of using javascript to include the calculator which would also conatain a text link back to my site in order to gain some back links. If it's possible Google won't see the link (as they may not execute the javascript), is it safe to place the link in the <noscript>tag? If so, Will it be indexed and will Page Rank be passed?</span></p> <p>Thanks in advance for your answers. </p> <p>Anthony</p> <p><span style="color: #5e5e5e;"><br /></span></p></noscript>
Web Design | | BallyhooLtd0 -
Changing H1 Tag based on referrer
Hello, I need some quick help and advice. We're going through a website re-design, and we have a few H1 tags set on some of our inner pages. The team is ok with these, however they want to change the H1 tag if the user gets to that page from a page within the site. Example:
Web Design | | uSell
When the referrer is our site (www.domain.com), the H1 tag = Go to Step 2 When the referrer is anything else, the H1 tag = Welcome to our site I'd like to keep the H1 tag as the SEO rich keyword text we agreed on (in this case "Welcome to Our Site"), however our developers don't think its directional enough and wants to change it based on the user path. I'm ok with the suggestion, however I want to make sure that if we choose the option with the referrer that this doesn't impact our SEO efforts. I'm assuming the referrer will changed based on how the bot gets to the page, but i'm not certain and was wondering if anyone had some thoughts on this.. Any help is greatly appreciated. Thanks...0 -
Ajax pagination and filters for ecommerce site
Hi There, Is it ok to use ajax for product filters and pagination? In this case url doesn't change when you navigate to 2nd or 3rd page also when you filter by colours, etc. If not what's your advise?
Web Design | | Jvalops0