shaunm - 6:40 am on Nov 20, 2012 (gmt 0)
Thank you so much! I was thinking about all the possibilites of using a page as its own canonical, and I never thought about the scrapers and the out of control parameters.
When the page is requested as example.com/product/p1?somerandomjunk due to linking outside of your control the canonical metadata takes care of things.
Could you please tell me under what circumstances it goes out of control? Also, what if example.com/product/p1?somerandomjunk also have its own canonical tag?
To make it clear I only have to use <link rel="canonical" href="http://example.com/product/p1"/> on the page example.com/product/p1?somerandomjunk right? What if the page example.com/product/p1?somerandomjunk has a canonical as <link rel="canonical" href="http://example.com/product/p1?somerandomjunk"/>?
I am asking this because, as I mentioned above each page acts as its own canonical as per how the CMS is customized or how it is done in the dev process. So in that case, it makes this worse right? I am confused. Thanks
Thanks a lot!
As mentioned in my above post, what if http://example.com/page.html?session=xyzzy has its own canonical as well?
Also, how does Google finds it as something else than the actual page?
Thank you for answering on my post. It's really a great learning being part of this community.
Also, do you suggest me to remove all that canonical tags?