Change Canonical link default

[wouterj]

I recently watched this talk by Matt Cutts about the canonical link element: https://www.youtube.com/watch?v=Cm9onOGTgeM

Here, he states that the canonical link element should be the last thing to do when having duplicate content. Things you should do first are 301 redirects and a good sitemap.

We currently default to the canonical link usage. Shouldn't we change it to 301 redirect instead?

[ElectricMaxxx]

👍 for change.

[dbu]

fine for me. but if we do that before announcing the cmf release, we should release a 1.0.1 version and note the BC break in the changelog. if we only do it after, it should go into 1.1 probably

[ElectricMaxxx]

What to do here as we forgot that issue?

[dbu]

put it into 1.1 and do a changelog entry?

[wouterj]

We should change the whole canonical link thing imo. Canonical links serve more purposes than replacing the redirect.

[dbu]

is this now a 2.0 issue or should we do it for 1.2? doing it in 1.2 could be unexpected.

[wouterj]

Yeah, let's skip for 2.0

[ElectricMaxxx]

👍

Am 20.09.2015 um 15:03 schrieb Wouter J:

Yeah, let's skip for 2.0

---

Reply to this email directly or view it on GitHub:
#167 (comment)

[wouterj]

What about trigger a deprecation notice when the configuration value is not set (so the default of canonical is used) to warn users that this behaviour will change in 2.0? This means people are aware of explicitely setting this to canonical (in case they want to keep the current behaviour) or can have forward compatiblity by setting it to redirect.