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.
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
-
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 -
Pagination and matching title tags - does it matter when using rel="prev" and "next" attributes?
I'm looking at a site with the rel="prev" and "next" HTML attributes in place, to deal with pagination. However, the pages in each paginated category have identical page titles - is this an issue? Rand gives an example of how he'd vary page titles here, to prevent problems, though I'm not entirely sure whether this advice applies to sites with the rel="prev" and "next" HTML attributes in place: https://moz.com/blog/pagination-best-practices-for-seo-user-experience Any advice would be welcome - many thanks, Luke
Intermediate & Advanced SEO | | McTaggart0 -
If this is what happens when a penalty is removed, I want more penalties
So a couple of weeks ago I posted that we had submitted a reconsideration request along with a list of about 40 spam pages that were linking to us that we had attempted to have remove their links to us. On 8/3 we received a note from Google that our manual penalty had been removed. We have thousands of inbound links so these 40 pages were a minuscule part of our links and ones that we hadn't tried to get in the first place. So I thought "Great, our rankings should go up." Up until this point our year-to-year organic Google traffic was between 45% and 100% over last year. As of 8/9 our traffic is now only 26%-39% above last year. I don't think we can handle too many more penalty reversals like this one.
Intermediate & Advanced SEO | | IanTheScot0 -
E Commerce product page canonical and indexing + URL parameters
Hi, I'm having some issues on the best way to handle site structure. The technical side of SEO isn't my strong point so I thought I'd ask the question before I make the decision. Two examples for you to look at. This is a new site http://www.tester.co.uk/electrical/multimeters/digital. By selecting another page to see more products you get this url string where/p/2. This page also has the canonical tag relating to this page and not the original page. Now if say for example I exclude this parameter (where) in webmaster tools will I be stopping Google indexing the products on the other pages where/p/2, 3, 4 etc. and the same if I make the canonical point to multimeters/digital/ instead of multimeters/digital/where/p/2 etc.? I have the same question applied to the older site http://www.pat-services.co.uk/digital-multimeters-26.html. which no longer has an canonical tags at all. The only real difference is Google is indexing http://www.pat-services.co.uk/digital-multimeters-26.html?page=2 but not http://www.tester.co.uk/electrical/multimeters/digital/where/p/2 Thanks for help in advance
Intermediate & Advanced SEO | | PASSLtd0 -
Rel Canonical = WHAT
can someone please explain this "NOTICE" i am getting from my campaign...Is this a problem that needs attention?
Intermediate & Advanced SEO | | SEObleu.com0 -
Should "View All Products" be the canonical page?
We currently have "view 12" as the default setting when someone arrives to www.mysite.com/subcategory-page.aspx. We have been advised to change the default to "view all products" and make that the canonical page to ensure all of our products get indexed. My concern is that doing this will increase the page load time and possibly hurt rankings. Does it make sense to change all our our subcategory pages to show all the products when someone visits the page? Most sites seem to have a smaller number of products as the default.
Intermediate & Advanced SEO | | pbhatt0 -
Should I be using rel canonical here?
I am reorganizing the data on my informational site in a drilldown menu. So, here's an example. One the home page are several different items. Let's say you clicked on "Back Problems". Then, you would get a menu that says: Disc problems, Pain relief, paralysis issues, see all back articles. Each of those pages will have a list of articles that suit. Some articles will appear on more than one page. Should I be worried about these pages being partially duplicates of each other? Should I use rel-canonical to make the root page for each section the one that is indexed. I'm thinking no, because I think it would be good to have all of these pages indexed. But then, that's why I'm asking!
Intermediate & Advanced SEO | | MarieHaynes0