Any penalty for having rel=canonical tags on every page?
-
For some reason every webpage of our website (www.nathosp.com) has a rel=canonical tag. I'm not sure why the previous SEO manager did this, but we don't have any duplicate content that would require a canonical tag.
Should I remove these tags? And if so, what's the advantage - or disadvantage of leaving them in place?
Thank you in advance for your help.
-Josh Fulfer
-
There isn't a direct penalty for having rel="canonical" tags on every page, no, as long as you are correctly utilizing them (i.e. don't set the href of the tag to an invalid or non-existent URL). If there is even the possibility of duplicate content on your website, it is best to use canonical tags.
For websites serving straight HTML files, both http://www.example.com/index.html and http://www.example.com/ likely serve the same content.
If you use a framework like ASP.NET MVC, it would by default return duplicate content for both http://www.example.com/ and http://www.example.com/Home/Index.
Choose one or the other and set your canonical tag to that:
(note: the trailing slash is optional - just be consistent with including it or not)
-
You can use a canonical tag on page A, to point to A, telling that this is the original, teh reason for this is when people scrape your site they will point back home.
i belive thats is what they were getting at
you would only point it at B if B was a duplicate.
-
Ryan - I appreciate your help. My initial thought too was that I could remove it to clean up the code. However, I was unaware that the tag helps with dynamically generated pages - which ours are.
Thank you for your thorough response.
-
as far as i can see josh, the canonical URLs on your site are doing what they should be doing. I havn't looked to deep into it, but it seems like your products all refer back to product category pages, so that is the right way to use them.
-
I have never heard of anyone being penalised for having it on every page. Plus I can't see that ever happening unless it has been implemented incorrectly of course.
-
page A has content about apples. page B has content about bubblegum. Canonical tag states that page B should refer to page A. What is the point of that? all link juice, all ranking potential is passed to page A, even though page B has very different content. So page A MIGHT appear in search results about bubblegum, but page B will not because it is passing all link juice and rank potential to page A about apples. People stop going to page A when looking for bubblegum because it is irrelevant, and bounce rates increase.
Dont think you need documentation to get this. If you have all pages redirecting bots via canonical urls to the SAME page, it is pointless. If you have several article about apples and point them all to page A that is a different story.
-
not sure what you mean here, I have a canonical on every page, I program my sites to dynamicly to do, the reason i do so, is if someone scraps a page, it will have my address in the canonical tag.
I dont know what you mean by not relative to the tag. it just a href, are we talking about the same thing?
rel="canonical" href=http://mydomain.com/>
-
Having canonical tags on pages that don't have any duplicate content is pointless, as it may actually stop you for ranking on keywords specific to pages not relative to the tag.
Please, may you present me a document that assess what are you saying? because it is the first time I hear this thing.
#curious
-
The disadvantage to keeping a canonical tag on a page which does not require it would be, as a rule, you want to present your web page with the least amount of code possible. Unnecessary code causes extra confusion and adds to the processing time of web pages.
I use the canonical tag on all pages, but not everyone agrees. If you would like further support, SEOmoz uses the tag on all pages as well. If you use any CMS, ecommerce software, forum software or any system which generates pages dynamically then I would highly recommend a canonical tag on every page. At times a system will generate pages which you might not be aware of, but a crawler will find.
Sometimes a page will offer a print version, the ability to sort on ascending/descending, and numerous other changes. You might think you only have one version of your page but have many versions which you do not realize exist. A proper canonical tag ensures the correct version of your URL is always offered for indexing, and you avoid duplicate content issues. With that said, if you have a basic html/css/php site and you are 100% confident in your programmer, then it is not necessary.
EDIT: In your case, it seems the canonical tags are performing a necessary function. From your home page I clicked on your featured item and I landed on the following URL:
http://www.nathosp.com/product/r1212_c
You have the identical page offered under another URL: http://www.nathosp.com/product/r1212_c/hotel_towels.
If you were to remove the canonical, you would have duplicate content issues on your site.
-
rel=canonical just passes all link juice from one page to the next, it tells bots to use the page specified in the tag to assess link value and page authority. Having canonical tags on pages that don't have any duplicate content is pointless, as it may actually stop you for ranking on keywords specific to pages not relative to the tag. I would look at it closely or ask the last SEO why they did this before removing them. But by the sounds of it, you dont really need them.
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
-
Webshop landing pages and product pages
Hi, I am doing extensive keyword research for the SEO of a big webshop. Since this shop sells technical books and software (legal books, tax software and so on), I come across a lot of very specific keywords for separate products. Isn't it better to try and rank in the SERP's with all the separate product pages, instead of with the landing (category) pages?
Intermediate & Advanced SEO | | Mat_C0 -
Is it best to 301 redirect or use canonical Url when consolidating two pages?
I have build several pages (A and B) with high quantity content. Page A is aged and gets lots of organic traffic, ranks for lots of valuable keywords, and has only internal links to this page. Page B is newer (6 months) and gets little traffic, ranks for no keywords, but has terrific content and many high value external links. As Page A and B are related to a similar theme, I was going to merge content from page B onto page A, but don't know which would be the best approach for handling the links going to page B. For the purposes of keep as much link equity as possible, is it best to us a 301 redirect from B to A or use a canonical URL from B to A?
Intermediate & Advanced SEO | | Cutopia0 -
Rel Canonical for HTTP and HTTPS pages
My website has a login that has HTTPS pages. If the visitors doesn't log in they are given an HTTP page that is similar, but slightly different. Should I sure a Rel Canonical for these similar pages and how should that be set up? HTTP to HTTPS version or the other way around? Thank you, Joey
Intermediate & Advanced SEO | | JoeyGedgaud1 -
I Need to put static text every page (600 words) need advice
i need to put static text (about our company brief 600 words) to all content section of pages of our website. I know it's bad for SEO Duplicate Content. But i need to tell google this is my static content and do NOT crawl it. Or something like that. canonical is for whole page but i need to set it up for certain positions of every page. is that possible?
Intermediate & Advanced SEO | | nopsts0 -
Intra-linking to pages with a different Canonical url ?
Hello Moz Community! I'm hoping to get some advice around intra-linking practices and the benefits when a page that is being linked to has a different canonical tag than it's own URL. Confused? Allow me to elaborate. Scenario: Background: Ecommerce Company is trying to increase its organic ranking for key, broad terms in the cycling industry. Ecommerce company is trying to rank its category pages for a main term. To help this, the company focusing on increasing the quality of its intra-linking structure (the links and anchor texts that link to another page within the site). Example goal: to have it's Road Cassettes category page rank for 'Road Cassettes' Company's 'cassettes' main category page is here: /Components/Drivetrain/Cassettes/ And the company uses filtered navigation logic to drill down into 'road cassettes' specifically: /Components/Drivetrain/Cassettes/?page_no=1&fq=ATR_RoadBiking:True SEOs are instructed to include occasional links back to this page, with SEO friendly anchor text, to help strengthen it's authority for the main term. The Issue / Question: Main category URL: /Components/Drivetrain/Cassettes/ Road Cassettes category URL: /Components/Drivetrain/Cassettes/?page_no=1&fq=ATR_RoadBiking:True Road Cassettes Canonical URL: /Components/Drivetrain/Cassettes/ The canonical URL of the filtered Road Cassettes category is its main category URL. Will Company be able to effectively rank its Road Cassettes category URL for 'Road Cassettes' if the canonical URL is the main category? Should the canonical URL not be the main category? OR Will increasing the intra-linking to the Road Cassettes URL help the main category URL rank for 'Road Cassettes' - by passing all it's authority?
Intermediate & Advanced SEO | | Ray-pp0 -
Using Canonical URL to poin to an external page
I was wondering if I can use a canonical URL that points to a page residing on external site? So a page like:
Intermediate & Advanced SEO | | llamb
www.site1.com/whatever.html will have a canonical link in its header to www.site2.com/whatever.html. Thanks.0 -
Wildcard Redirects & Canonical Tags
I have an interesting situation. Current URLs Example1: www.domain.com/red-widgets-cid-1234.html
Intermediate & Advanced SEO | | NakulGoyal
www.domain.com/red-widgets-cid-1234-1.html
www.domain.com/red-widgets-cid-1234-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234.html New URL:
www.domain.com/red-widgets-cid-4567.html Current URLs Example2: www.domain.com/red-widgets-cid-1234+10.html
www.domain.com/red-widgets-cid-1234+10-1.html
www.domain.com/red-widgets-cid-1234+10-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234+10.html New URL:
www.domain.com/red-widgets-cid-6789.html Current URLs Example3: www.domain.com/red-widgets-cid-1234+10+5.html
www.domain.com/red-widgets-cid-1234+10+5-1.html
www.domain.com/red-widgets-cid-1234+10+5-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234+10+5.html New URL:
www.domain.com/american-red-widgets-cid-6789+5.html I want to make sure all variations of the above URL redirect to the new URLs. However, as you see in Example 3, we are dealing with variables that are passed on. (+5 in this case). Question 1: What wildcard 301 redirect / regular expression can I use to tackle these ? Question 2: If we redirect www.domain.com/red-widgets-cid-1234+10+5.html to www.domain.com/red-widgets-cid-6789+5.html and www.domain.com/red-widgets-cid-6789+5.html contains the canonical tag www.domain.com/american-red-widgets-cid-6789+5.html, any concerns or red flags here ?0 -
Meta Refresh tag on cache pages- GRRR!
Hi guys, All of our product pages originate in a URL with a unique number but it redirects to an SEO url for the user. These product pages have blocks on the page and these blocks are automatically populated with our database of content. Here's an example of the redirect in place: www.example.com/45643/xxxx.html redirects to www.example.com/seo-friendly-url.html The development team did this for 2 reasons. 1) our internal search needs the unique numbered urls for search and 2) it allows quick redirects as pages are cached. The problem I face is this, the redirects from the cached are being tagged with 'meta refresh', yup, they are 302. The development team said they could stop caching and respond dynamically with a 301 but this would bring in a delay. Speed wise, the cached pages load within 22ms and dynamically 530ms, so yeah half a second more. Currently cached pages just do a meta refresh tagged redirect and I want to move away from this. What would you guys recommend in such a situation? I feel like unless I place a 301, I'll be losing out on rank juice.
Intermediate & Advanced SEO | | Bio-RadAbs0