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
-
Taken a canonical off a page to let it rank with new unique content - what more can I do?
A week ago, I took a canonical off of a page that was pointing to the homepage for a very big, generic search term for my brand as we felt that it could have been harming our rankings (as it wasn't a true canonical page). A week in and our rankings for the term have dropped 7 positions out of page 1 and the page we want to rank instead is nowhere to be seen. Do I hang fire? As such a big search term, it's affecting traffic, but I don't want to make any rash decisions. Here's a bit more info: For arguments sake, let's call the search term we're going after 'Boots', with the URL where the canonical was placed of /boots. The canonical went to the root domain as we sell, well... boots. At the time, the homepage was ranking for Boots on page 1 and we wanted to change this so that the Boots page ranked for that term... all logical right? We did the following: Took off mentions of Boots from meta on the homepage and made sure it was optimised for on the boots page. Took the canonical off of /boots. Used GSC to fetch & ask Google to recrawl "/boots". Resubmitted the sitemap. Do I hang fire on running back to the safety of ranking for boots on the homepage? Do I risk keyword cannibalisation by adding the search terms back to the homepage?
Intermediate & Advanced SEO | | Kelly_Edwards0 -
Duplicate pages and Canonicals
Hi all, Our website has more than 30 pages which are duplicates. So canonicals have been deployed to show up only 10 of these pages. Do more of these pages impact rankings? Thanks
Intermediate & Advanced SEO | | vtmoz0 -
Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
Intermediate & Advanced SEO | | Steven_Macdonald0 -
Is there a way to rel = canonical only part of a page?
Hi guys: I'm doing SEO for a boat accessories store, and for instance they have marine AC systems, many of them, and while the part number, number of BTUs, voltage, and accessories change on some models, the description stays exactly the same across the board on many of them...people often search on Google by model number, and I worry that if I put rel = canonical, then the result for that specific model they're looking for won't come up, just the one that everything is being redirected to. (and people do this much more than entering a site nowadays and searching by product model, it's easier). Excuse my ignorance on this stuff, I'm good with link building and content creation, but the behind-the-scenes aspects... not so much: Can I "rel=canonical" only part of the page of the repeat models (the long description)? so people can still search by model number, and reach the model they are looking for? Am I misunderstanding something here about rel=canonical (Interesting thing, I rank very high for these pages with tons of repeat descriptions, number one in many places... but wonder if google attributes a sort of "across the site" penalty for the repeated content... but wouldn't ranking number 1 for these pages mean nothing's wrong?. Thanks)
Intermediate & Advanced SEO | | DavidCiti1 -
Is their value in linking to PPC landing pages and using rel="canonical"
I have ppc landing pages that are similar to my seo page. The pages are shorter with less text with a focus on converting visitors further along in the purchase cycle. My questions are: 1. Is there a benefit for having the orphan ppc pages indexed or should I no index them? 2. If indexing does provide benefits, should I create links from my site to the ppc pages or should I just submit them in a sitemap? 3. If indexed, should I use rel="canonical" and point the ppc versions to the appropriate organic page? Thanks,
Intermediate & Advanced SEO | | BrandExpSteve0 -
Rel Next and Previous on Listing Pages of Blog
Hi, Need to know does rel next and previous is more appropriate for content based articles and not blog listings.. Like an article spread across 3 pages - there it makes sense for rel next and previous as the content of the article is in series However, for blog listing page, for pages 1, 2, 3, 4 where every page is unique as the blog has all independent listings or separate articles - does rel next and previous wont of much help Our blog - http://www.mycarhelpline.com/index.php?option=com_easyblog&view=latest&Itemid=91 This is what been said by the developer "The whole idea of adding the "next" and "previous" tag in the header is only when your single blog post has permalinks like: site.com/blog/entry/blog-post.html
Intermediate & Advanced SEO | | Modi
site.com/blog/entry/blog-post.html?page=1
site.com/blog/entry/blog-post.html?page=2 " The link in the head is only applicable when your content is separated into multiple pages and it doesn't actually apply on listings. If you have a single blog post that is broken down to multiple pages, this is applicable and it works similarly like rel="canonical" Can we safely ignore rel next and previous tag for this blog pagination for the listing pages !!0 -
How far can I push rel=canonical?
My plan: 3 sites with identical content, yet--wait for it--for every article whose topic is A, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site A. For every article whose topic is B, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site B. So Site A will have some articles about topics A, B, and C. And for pages with articles about A, the rel=canonical will point to the page it's on. Yet for pages with articles about B, the rel=canonical will point to the version of that article on site B. Etc. I have my reasons for planning this, but you can see more or less that I want each site to rank for its niche, yet I want the users at each site to have access to the full spectrum of articles in the shared articles database without having to leave a given site. These would be distinct brands with distinct Whois, directory listings, etc. etc. The content is quality and unique to our company.
Intermediate & Advanced SEO | | TheEspresseo0 -
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