Canonical tag vs 301
-
What is the reason that 301 is preferred and not rel canonical tag when it comes to implementing redirect. Page rank will be lost in both cases. So, why prefer one over the other ?
-
page 1 points to page 2 that points back to page 1.. this or simular situations will make fubar for Google
you can actualy do the same with 301's but it's wayyyy easier to notice.. the rel is allot harder to notice if you do something wrong since it only affects google/bing
-
Thanks. Will you please elaborate how it's possible to make an infinite loop with rel's.
-
301 is a redirect so if you change the url you 301 redirect it to the new url in case links have been built to the old url.
rel canonical is a tag that tells Google this page has similar content to another page to help duplicate content issues, usually used on re-ordering functionality and paging.
-
The quick response to this, is that with 301 your fairly sure that all bots (not only google/Bing) will understand and apart from that it's way easier to manage the 301's then it is to manage rel's. Both should work without a problem but there are allot of pitfalls with rel's fore instance it's possible to make an infinite loop with rel's.
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
-
X Default on hreflang tags
Hi guys, I would like to clarify something about hreflang markups and most importantly, x-default. Sample URLs:
Intermediate & Advanced SEO | | geekyseotools
http://www.example.com/au/collection/dresses (Australia)
http://www.example.com/us/collection/dresses (United States)
http://www.example.com/uk/collection/dresses (United Kingdom) Sample Markups: Questions:
1. Can I use my AU page as x default? I noticed that some x default are US. Note that my biggest market is AU though.
2. If I indeed use AU page as x default, and the user is searching from China, does it mean that Google will return my AU page?
3. Can you spot any issues with these markups I made? Anything that I need to correct. Keen to hear from you! Cheers,
Chris0 -
How (or if) to apply re canonical tags to Shopify?
Anyone familiar with Shopify will understand the problems of their directory structure. Every time you add a product to a 'collection' it essentially creates a duplicate. For example... https://www.domain.com/products/product-slim-regular-bikini may also appear as: https://www.domain.com/collections/all/products/product-slim-regular-bikini https://www.domain.com/collections/new-arrivals/products/product-slim-regular-bikini https://www.domain.com/collections/bikinis/products/product-slim-regular-bikini etc, etc It's not uncommon to have up to six duplicates of each product. So my question is twofold: Firstly, should I worry about this from an SEO point of view? I understand the desire to minimise potential duplicate content issues and also in focussing the 'juice' on just one page per product. But I also planned on trying to build the authority of the collection pages. If I request Google not to index the product pages which link off the collections, does this not devalue these collections pages? Secondly, I understand the correct way to fix these is using 'rel canonical' tags, but I'm not clear about HOW to actually do this. Shopify support has not been very helpful. They have provided two different instructions, so just added to the confusion (see below). Shopify instruction #1: Add the following to the theme.liquid file... <title><br />{{ page_title }}{% if current_tags %} – tagged "{{ current_tags | join: ', ' }}"{% endif %}{% if current_page != 1 %} – Page {{ current_page }}{% endif %}{% unless page_title contains shop.name %} – {{ shop.name }}{% endunless %}<br /></title>
Intermediate & Advanced SEO | | muzzmoz
{% if page_description %} {% endif %} Shopify instruction #2: Add the following to each individual product page... So, can anyone help clarify: The best strategic approach to this inherent SEO issue with Shopify (besides moving to another platform!)? and If 'rel canonical' tags is the way to go, exactly where and how to apply them? Regards, Murray1 -
Canonical Vs No Follow for Duplicate Products
I am in the process of migrating a site from Volusion to BigCommerce. There is a limitation on the ability to display one product in 2 different ways. Here is the situation. One of the manufacturers will not allow us to display products to customers who are not logged in. We have convinced them to let us display the products with no prices. Then we created an Exclusive Contractor section that will allow users to see the price and be able to purchase the products online. Originally we were going to just direct users to call to make purchases like our competitors are doing. Because we have a large amount of purchasers online we wanted to manipulate the system to be able to allow online purchases. Since these products will have duplicates with no pricing I was thinking that Canonical tags would be kind of best practice. However, everything will be behind a firewall with a message directing people to log in. Since this will undoubtedly create a high bounce rate I feel like I need to no follow those links. This is a rather large site, over 5000 pages. The 250 no follow URLs most likely won't have a large impact on the overall performance of the site. Or so I hope anyway. My gut tells me if these products are going to technically be hidden from the searcher they should also be hidden from the engines. Does Disallowing these URLs seem like a better way to do this than simply using the Canonical tags? Any thoughts or suggestions would be really helpful!
Intermediate & Advanced SEO | | MonicaOConnor0 -
Rel=prev/next and canonical tags on paginated pages?
Hi there, I'm using rel="prev" and rel="next" on paginated category pages. On 1st page I'm also setting a canonical tag, since that page happens to get hits to an URL with parameters. The site also uses mobile version of pages on a subdomain. Here's what markup the 1st desktop page has: Here's what markup the 2nd desktop page has: Here's what markup the 1st MOBILE page has: Here's what markup the 2nd MOBILE page has: Questions: 1. On desktop pages starting from page 2 to page X, if these pages get traffic to their versions with parameters, will I'll have duplicate issues or the canonical tag on 1st page makes me safe? 2. Should I use canonical tags on mobile pages starting from page 2 to page X? Are there any better solutions of avoiding duplicate content issues?
Intermediate & Advanced SEO | | poiseo1 -
301 Redirect / Canonical loop on home page?
Hi there, My client just launched a new site and the CMS requires that the home page goes to a subfolder - clientsite.com/store. Currently there is a redirect in place such that clientsite.com -> clientsite.com/store. However, I want clientsite.com to be the canonical version of the URL. What should I do in this case, given that there is now a loop between the redirected page and the canonical page?
Intermediate & Advanced SEO | | FPD_NYC0 -
Canonical and On-Page Report Card
Hello, One quick question about rel canonical. If i use SeoMoz amazing on-page optimization tool i get a grade B if i use www.mydomain.com and my keyword. I get a grade A if i use https://www.mydomain.com and same keyword. I get the grade B coz i don't get the check mark to "Appropriate Use of Rel Canonical" box. Should i use this rel canonical stuff if i am 301 redirecting www. version to https://www. version already. Regards, OÜInigo
Intermediate & Advanced SEO | | InigoOU0 -
Canonical tags and GA tracking on premium sub-domain?
Hello! I'm launching a premium service on my site that will deliver two fairly distinct user experiences, but with nearly identical page content across the two. I'm thinking of placing the "upgraded" version on a subdomain, e.g. www.mysite.com, premium.mysite.com. Simple enough. I've run into two obstacles, however: -I don't want the premium site crawled separately, so I'd like to use canonical tags to pull all premium.* back to their www.* parents. --How different can page content be before canonical tags backfire? --Is there any other danger in using canonicals across subdomains like this? -Less importantly: with Google Analytics, if I track against the subdomain my visits will split naturally, and it should generate a second cookie for a new registrant who crosses subdomains. I could also use a visitor-level custom var. Good idea? Bad idea? Thanks! -m
Intermediate & Advanced SEO | | grumbles0 -
Could adding canonical tags to large Ecommerce site ever hurt rankings? Temporarily?
We have a really large site we're working on who's product pages rank well for the most part but also have multiple products listed in different categories with different URL's. I'm assuming there's no downside to adding canonical tags to these right? Its peak season so I don't want to do anything that could, even temporarily, bring down their rankings. Thanks!
Intermediate & Advanced SEO | | iAnalyst.com0