Is having "rel=canonical" on the same page it is pointing to going to hurt search?

[brett_hss]

i like the rel=canonical tag and i've seen matt cutts posts on google about this tag. for the site i'm working on, it's a great workaround because we often have two identical or nearly identical versions of pages: 1 for patients, 1 for doctors.

the problem is this: the way our content management system is set up, certain pages are linked up in a number of places and when we publish, two different versions of the page are created, but same content. because they are both being made from the same content templates, if i put in the rel=canonical tag, both pages get it. so, if i have:

http://www.myhospital.com/patient-condition.asp and http://www.myhospital.com/professional-condition.asp and they are both produced from the same template, and have the same content, and i'm trying to point search at http://www.myhospital.com/patient-condition.asp, but that tag appears on both pages

similarly, we have various forms and we like to know where people are coming from on the site to use those forms. to the bots, it looks like there's 600 versions of particular pages, so again, rel=canonical is great. however, because it's actually all the same page, just a link with a variable tacked on (http://www.myhospital.com/makeanappointment.asp?id=211) the rel=canonical tag will appear on "all" of them.

any insight is most appreciated!

thanks! brett

[RyanKent]

Yes

[CommercePundit]

Got it. Dr.Pete have done excellent work on similar blog post. Right?

[RyanKent]

So, Does it really matter to add rel=canonical tag in each pages? Can I remove from web page?

It does matter, and you should not remove the canonical tag.

One example on the page you referenced is the following URL: http://www.vistapatioumbrellas.com/umbrella-stands?dir=asc&order=name

On the page you referenced visitors can change the default ORDER BY Position to ORDER BY Name (as an example) which changes the URL. Both pages are the same content but displayed different, which is exactly the type of issue canonicalization is designed to correct.

[CommercePundit]

I am not getting clear idea by this answer. I am searching solution which may help me to solve same question.

I would like to share my URL.

http://www.vistapatioumbrellas.com/umbrella-stands

This page have rel=canonical tag for same page as follow.

<link rel="canonical" href="[http://www.vistapatioumbrellas.com/umbrella-stands](view-source:http://www.vistapatioumbrellas.com/umbrella-stands)" />

Website does not contain any duplicate page which is associated to this page. So, Does it really matter to add rel=canonical tag in each pages? Can I remove from web page?

[RyanKent]

Hi Brett.

Steven is correct. I think it will be helpful if I offer a bit more clarification.

www.myhospital.com/patient-condition.asp

www.myhopsital.com/professional-condition.asp

www.myhospital.com/patient-condition.asp?id=1

Those three URLs may point to the exact same page or very similar pages. Google simply wont index all 3 pages as it does not offer any user benefit. The best thing to do is tell Google which of these 3 pages is the primary page you wish listed. By placing the same canonical tag on all 3 pages, you are indicating to Google which page you wish listed.

With the above tag placed in all 3 pages, then Google knows in the first URL example they are dealing with the original page, and in the next 2 examples they are dealing with a copy.

NOTE: I am unsure why two users disliked this reply. It is correct. If I were to stretch, I can add that Bing stated their preference the canonical tag not used on a page who's URL matches the canonical, but they seem to handle it well with no issues.

[sferrino]

With rel='canonical' you want to point all existing pages that have the same content to 1 page. Having a rel='canonical' on the page with itself as the href will not hurt, can only help verify that it is the preferred page.