[wp-hackers] Canonical integration into core

mikeschinkel at newclarity.net mikeschinkel at newclarity.net
Wed Feb 18 17:03:04 GMT 2009

It may not be "native" to WordPress but it is a very common sourcing  
technique people use. This allows them to track sources using their  
ISP's log reports. There are many reasons why people tag params to  
URLs and this disussion is ignoring that.

And nobody besides me seems to want to address how it might be used  
outside of search engines, like at Digg, Delicious, etc.

Not being "native" to WordPress seems to be a rather myopic  
justification. HTTP isn't native to WordPress but we still need to  
utilize best practices regarding HTTP.

NOT including rel="canonical" means competing and certainly  
incompatible plugin implementations. At least there needs to me a  
standard filter for generating it.


Sent from my iPhone

On Feb 18, 2009, at 4:47 AM, scribu <scribu at gmail.com> wrote:

> On Wed, Feb 18, 2009 at 11:10 AM, Joost de Valk <joost at yoast.com>  
> wrote:
>> It's not just about what WordPress does. For example:
>> http://example.com/about/
>> and
>> http://example.com/about/?from=email
>> will serve up the same pages in most WordPress installs. If you add  
>> the
>> rel="canonical" link to the <head>, the latter will have all links  
>> pointing
>> to it counted toward the first one. That's, for me, one of the main  
>> uses of
>> the tag.
>> Best,
>> Joost
> Yes, but the second URL is not native to WordPress, so the canonical  
> tag is
> effectively plugin territory, except for paged comments.
> -- 
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list