Guide

Canonical: the attribute that prevents duplicate content

The canonical attribute tells Google which URL is the reference version. Here is when it matters, and the classic mistake on sites with similar pages.

Same URL, different link order depending on Instagram/TikTok/YouTube. Configure once. Korli applies the rest automatically.

  • Examples: TikTok visitor sees offer first, Instagram visitor sees proof first
  • Common mistakes: too many links, same order for everyone, no tracking
  • Setup: create page → set Smart Rules → measure clicks (30 seconds)

Back to the hub · Relevant docs

Proof demo: source switch → different order

Same URL, but a different rendering based on where the visitor comes from. Configure once. Korli applies the rest automatically.

Definition: a reference URL, not a redirect

  • rel="canonical" is an HTML tag in the <head>. It declares: "this page is a duplicate of that one".
  • It is not an HTTP redirect. The visitor stays on the URL they are on.
  • Google treats it as a hint, not an order. It can ignore it when the signal is clearly contradictory.

The concrete case on korli.fr

  • Every page exists in EN and FR, plus per-platform variants (/use-cases/instagram, /use-cases/tiktok).
  • Without canonical or hreflang, those variants compete for the same queries.
  • Each page declares a self-referencing canonical and points to its EN version via hreflang. Both signals agree.

The classic mistake: canonicalising to the homepage

  • Canonising every page to the homepage tells Google to ignore your entire content.
  • One legitimate exception: URLs that genuinely serve the same content (near-identical products).
  • On a young site, no canonical is better than a wrong one.

Concrete example

Example: two URLs, one page to rank

  1. You have /alternative/linktree and /blog/linktree-alternative saying the same thing.
  2. Without canonical or 301, Google must pick one to rank. It picks arbitrarily and you lose both.
  3. You 301 the weaker one to the stronger, and put a canonical on the winner.
  4. Result: one page receives the authority instead of two fighting over it.

How it works (3 steps)

  1. List the URLs on your site that cover the same ground (duplicate detection).
  2. Choose which one should rank: most visited, best structured, most valuable.
  3. 301 the others to it, and set a self-referencing canonical on the winner.

Common mistakes

  • Pointing every canonical at the homepage "to be safe".
  • Forgetting to remove old URLs from the sitemap after a 301.
  • Declaring different canonicals on the FR and EN versions: Google can follow neither.

In the same category

Tip: read 2 pages in the same cluster, then refine your link order by source.

Read next

Tip: read 2 pages in the same cluster, then refine your link order by source.

FAQ

Canonical or hreflang, which one?

They are not competitors: canonical names the reference version of one page, hreflang names the equivalent in another language. Both coexist. On korli.fr each page is self-canonical and points to its EN equivalent.

Does a canonical remove duplicate content on its own?

It is a hint, not a guarantee. Google can ignore it when pages are genuinely different. A 301 is stronger: it actually redirects and transfers authority.

Do I need a canonical on a page with no duplicate?

Yes, a self-referencing canonical is good practice. It protects against URL parameters and case variants.

CTA

Configure your smart rules once. Korli applies the rest automatically.