Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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
-
Landing pages for paid traffic and the use of noindex vs canonical
A client of mine has a lot of differentiated landing pages with only a few changes on each, but with the same intent and goal as the generic version. The generic version of the landing page is included in navigation, sitemap and is indexed on Google. The purpose of the differentiated landing pages is to include the city and some minor changes in the text/imagery to best fit the Adwords text. Other than that, the intent and purpose of the pages are the same as the main / generic page. They are not to be indexed, nor am I trying to have hidden pages linking to the generic and indexed one (I'm not going the blackhat way). So – I want to avoid that the duplicate landing pages are being indexed (obviously), but I'm not sure if I should use noindex (nofollow as well?) or rel=canonical, since these landing pages are localized campaign versions of the generic page with more or less only paid traffic to them. I don't want to be accidentally penalized, but I still need the generic / main page to rank as high as possible... What would be your recommendation on this issue?
Intermediate & Advanced SEO | | ostesmorbrod0 -
Rel=canonical and internal links
Hi Mozzers, I was musing about rel=canonical this morning and it occurred to me that I didnt have a good answer to the following question: How does applying a rel=canonical on page A referencing page B as the canonical version affect the treatment of the links on page A? I am thinking of whether those links would get counted twice, or in the case of ver-near-duplicates which may have an extra sentence which includes an extra link, whther that extra link would count towards the internal link graph or not. I suspect that google would basically ignore all the content on page A and only look to page B taking into account only page Bs links. Any thoughts? Thanks!
Intermediate & Advanced SEO | | unirmk0 -
Substantial difference between Number of Indexed Pages and Sitemap Pages
Hey there, I am doing a website audit at the moment. I've notices substantial differences in the number of pages indexed (search console), the number of pages in the sitemap and the number I am getting when I crawl the page with screamingfrog (see below). Would those discrepancies concern you? The website and its rankings seems fine otherwise. Total indexed: 2,360 (Search Consule)
Intermediate & Advanced SEO | | Online-Marketing-Guy
About 2,920 results (Google search "site:example.com")
Sitemap: 1,229 URLs
Screemingfrog Spider: 1,352 URLs Cheers,
Jochen0 -
Is it okay to copy and paste on page content into the meta description tag?
I have heard conflicting answers to this. I always figured that it was okay to selectively copy and paste on page content into the meta description tag.....especially if the onpage content is well written. How can it be duplicate content if it's pulling from the exact same page? Does anybody have any feedback from a credible source about this? Thanks.
Intermediate & Advanced SEO | | VanguardCommunications1 -
Rel="canonical" and rel="alternate" both necessary?
We are fighting some duplicate content issues across multiple domains. We have a few magento stores that have different country codes. For example: domain.com and domain.ca, domain.com is the "main" domain. We have set up different rel="alternative codes like: The question is, do we need to add custom rel="canonical" tags to domain.ca that points to domain.com? For example for domain.ca/product.html to point to: Also how far does rel="canonical" follow? For example if we have:
Intermediate & Advanced SEO | | AlliedComputer
domain.ca/sub/product.html canonical to domain.com/sub/product.html
then,
domain.com/sub/product.html canonical to domain.com/product.html0 -
How Rel=Prev & Rel=Next work for me?
I have implemented Rel=Prev & Rel=Next tag on my website. I would like to give example URL to know more about it. http://www.vistapatioumbrellas.com/market-umbrellas?limit=40&p=3 http://www.vistapatioumbrellas.com/market-umbrellas?limit=40&p=4 http://www.vistapatioumbrellas.com/market-umbrellas?limit=40&p=5 Right now, I have blocked paginated pages by Robots.txt by following query. Disallow: /*?p= I have removed disallow syntax from Robots.txt for paginated pages. But, I have confusion with duplicate page title. If you will check all 3 pages so you will find out duplicate page title across all pages. I know that, duplicate page title is harmful for SEO. Will Google crawl + index all paginated pages? If yes so which page will get maximum benefits in organic ranking? Is there any specific way which may help me to solve this issue?
Intermediate & Advanced SEO | | CommercePundit0 -
Should I Allow Blog Tag Pages to be Indexed?
I have a wordpress blog with settings currently set so that Google does not index tag pages. Is this a best practice that avoids duplicate content or am I hurting the site by taking eligible pages out of the index?
Intermediate & Advanced SEO | | JSOC0