Before you invest in canonical URLs
Most teams know this matters. Fewer have decided who owns it. Before you spend anything on canonical URLs, it is worth confirming a few things are already true.
Technical fixes remove obstacles; content earns the position. Both are needed and they are not interchangeable. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
Prerequisites
- You can describe the outcome you want in one sentence
- Someone owns it after the work is done
- Canonicals tell search engines which version is the real one
- You have a way to tell whether it worked
Warning signs
Parameters and print views create duplicates quietly. None of that requires a large budget, only a decision and someone to own it. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
Self-referencing canonicals are a safe default. The reasoning matters more than the rule, because the rule has exceptions. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
What this looks like day to day
Search engines are trying to answer a question, so the pages that answer questions clearly tend to do well. Three things worth confirming about canonical URLs before you move on:
- Someone can say what the current setup is without going to look
- Canonicals tell search engines which version is the real one — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you want a second opinion on how yours is set up, ask.