DefinitieAn HTML link element (rel="canonical") that tells search engines which URL is the preferred version when several pages have the same or very similar content.
A canonical tag is an HTML link element (<link rel=”canonical”>) in the head of a page that tells search engines which URL is the preferred version when several pages have the same or very similar content. You will also hear it called the canonical URL or canonical link. Google uses it to decide which URL gets indexed and which one collects the ranking signals from links and content.
The most common misunderstanding is that a canonical tag is a command. It is not: it is a hint. Google weighs it against redirects, internal links, the sitemap and the content, and can pick a different canonical than the one you declared. That is why I treat the canonical tag as one signal among several that all need to point the same way.
Why canonical tags matter for a webshop
Webshops generate duplicate URLs almost by design. A product in three categories can have three URLs; PrestaShop creates one URL per category path. Filter and sort parameters, http and https, www and non-www, a trailing slash or none, tracking parameters like utm_source and gclid: each produces another copy of the same page. Without a clear canonical, Google crawls all of them, splits signals between them, and may index the copy you least want to rank.
The consequence is slower indexing of new products and weaker rankings for the pages that drive revenue. On shops with layered filters I regularly see the crawler spend its budget on filter combinations nobody searches for, while new product pages wait days to be picked up. A clean canonical setup is one of the cheaper wins in technische SEO: it concentrates authority on one URL per product and category, which is where the clicks and the sales come from.
How to check canonical tags
In Google Search Console, the URL inspection tool shows two lines for any page: the user-declared canonical and the Google-selected canonical. When those differ, Google has overruled your tag, almost always because of a conflicting signal elsewhere. The Pages report shows how widespread it is: “Duplicate without user-selected canonical” means copies with no canonical tag at all, “Alternate page with proper canonical tag” confirms the tag is working, and “Google chose different canonical than user” is the one I investigate first.
For a full-site view I crawl the shop with Screaming Frog and open the Canonicals tab. It flags pages with no canonical, a canonical that points to a non-indexable, redirected or 404 URL, and pages where the canonical differs from the crawled URL. I join that export with Search Console data in Looker Studio to check whether the indexed pages are the ones generating clicks.
Common canonical tag mistakes
Canonicalising to a URL that does not resolve. A canonical that points to a 404 page or to a URL that itself redirects sends Google in circles, and the tag gets ignored.
Canonicalising everything to the homepage. Some themes and plugins set a sitewide canonical to the homepage, so Google treats every product and category as a duplicate and drops them from the index. Every indexable page should carry a self-referencing canonical unless there is a specific reason to point elsewhere.
Mixing canonical tags with noindex, redirects or pagination. A page cannot be both “the duplicate of X” and “do not index”; Google picks one and it is rarely what you intended. The same goes for pagination: do not canonicalise page 2 to page 1, because the products on page 2 then lose their path into the index.
Technical errors in the tag itself. Relative URLs instead of absolute ones, a canonical in the body instead of the head, or two canonical tags on one page (typically theme plus SEO plugin) all weaken or break the signal. On a multilingual shop with TranslatePress or similar, each language needs its own self-referencing canonical; the cross-language relationship belongs in hreflang, never in the canonical.
How I handle canonical tags for clients
I start with a crawl and a Search Console export, then map every duplicate pattern the shop produces: category paths, filters, sorting, variants, tracking parameters and host variants. For each pattern I set a rule rather than a page-by-page fix. Variants in colour or size canonicalise to the parent product; filter and sort URLs to the clean category; tracking parameters are stripped; multi-category product URLs get one preferred path. On PrestaShop that often means adjusting the canonical setting and checking the theme; on WooCommerce and Shopify it is mostly verifying the defaults and fixing the exceptions.
The deliverable is a short canonical rule set (one line per URL pattern), the implementation or a developer brief, and a before-and-after comparison from Search Console a few weeks later. Canonical work goes together with redirects, the XML sitemap and internal linking, because those are the other signals Google uses to pick its canonical. For webshops it is a standard part of my e-commerce SEO work, and on multilingual shops I align it with the internationale SEO setup so canonical and hreflang never contradict each other.
Veelgestelde vragen
Does every page need a canonical tag?
Every indexable page should have one, and in most cases it should point to itself. A self-referencing canonical protects the page against parameter variants and copies you did not plan for. Most platforms add this by default, but I verify it on a crawl rather than assume it.
What does “Google chose different canonical than user” mean?
It means Google saw your canonical tag but decided another URL is the better representative. Usual causes are internal links pointing to the other URL, a contradicting redirect, the other URL being in the sitemap, or the pages not being similar enough to count as duplicates. Fix the conflicting signal and Google normally follows the tag.
Should product variants have their own canonical URL?
Usually not. If a shirt in blue and a shirt in red share the same description and only the swatch differs, I canonicalise the variants to the parent product. The exception is a variant with real search demand of its own, such as a Dutch query for a specific colour and model, backed by distinct content; then it deserves its own canonical.
Is a canonical tag the same as a redirect?
No. A redirect sends visitors and search engines to another URL, and the original is no longer reachable. A canonical tag keeps both pages live while asking search engines to index only one, such as a product listed under two categories.