Canonical URL
An HTML tag that tells search engines which version of a page is the original when duplicate content exists.
The canonical URL (rel="canonical") is an HTML tag in a page's <head> that indicates which URL is the preferred or original version. This is essential when the same or similar content is accessible via multiple URLs.
When to use canonical?
Typical scenarios: pages with URL parameters (filters, sort options), content published in multiple locations, HTTP and HTTPS variants, or www and non-www versions. Without a canonical, you risk search engines indexing — bibliotheekterm the wrong version or splitting your ranking power across duplicates.
Canonical and AEO
AI models that scrape content also encounter duplicates. A correct canonical implementation helps not only search engines but also AI systems identify and cite the right source.
Code examples
HTML link tag (most common)
<!-- Place in the <head> of every page -->
<link rel="canonical" href="https://example.com/blog/my-article/" />
HTTP Link header (for non-HTML files like PDFs)
HTTP/1.1 200 OK
Link: <https://example.com/blog/my-article/>; rel="canonical"
Content-Type: application/pdf
Canonical in a multilingual context
<!-- Dutch version -->
<link rel="canonical" href="https://example.com/nl/diensten/" />
<link rel="alternate" hreflang="nl" href="https://example.com/nl/diensten/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/services/" />
<!-- English version -->
<link rel="canonical" href="https://example.com/en/services/" />
<link rel="alternate" hreflang="nl" href="https://example.com/nl/diensten/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/services/" />
Decision tree: do you need a canonical?
- Is the same content accessible via multiple URLs? (e.g., with/without www, with/without trailing slash, with parameters) → Yes: set a canonical to the preferred version.
- Do you publish the same content on multiple pages? (e.g., an article appearing on the homepage and a category page) → Yes: canonical to the original page.
- Do you have a multilingual site? → Each language version gets a self-referencing canonical. Combine with hreflang — bibliotheekterm tags.
- Do you syndicate content to other websites? → Ask the partner site to place a cross-domain canonical to your original.
- Do you have a single, unique page without variants? → Still use a self-referencing canonical. This is a best practice that prevents future duplicate issues.
Common mistakes
- Canonical pointing to a non-existent page: if the canonical URL returns a 404, Google ignores the tag. Always verify that the target URL is accessible.
- Canonical to a noindexed page: a canonical pointing to a page with
noindexsends conflicting signals. Google will then choose which version to index on its own. - Relative URLs: always use absolute URLs with protocol (https://). Relative URLs can lead to incorrect canonicals when switching subdomains.
- Canonical accidentally pointing all pages to the homepage: a common CMS error. Each page should reference itself or the correct canonical version.
- Canonical conflicts with hreflang: if your hreflang tags reference page A but the canonical points to page B, a conflict arises. Keep these consistent.
- Multiple canonical tags: if there are two canonical tags in the <head>, Google ignores both. Ensure exactly one canonical tag per page.
Frequently asked questions
Is a self-referencing canonical necessary?
Yes, it's a best practice to give every page a canonical tag pointing to itself. This prevents issues when someone shares your URL with parameters (UTM tags, session IDs) that Google might see as separate URLs.
What's the difference between canonical and 301 redirect?
A 301 redirect physically sends visitors and bots to another URL. A canonical tag lets the page exist but tells search engines which version is preferred. Use a 301 if the old URL is no longer needed; use a canonical if both URLs need to remain accessible.
Do AI bots respect canonical tags?
Most AI bots (GPTBot, ClaudeBot, PerplexityBot) read canonical tags and use them to identify the correct source. A correct canonical implementation increases the chance that AI systems cite the right page.
Can I use a cross-domain canonical?
Yes, but Google treats cross-domain canonicals as a hint, not a directive. It works best when the content is nearly identical and the target page is on a trusted domain.
What does our scanner check?
Our scanner checks whether your page contains a canonical tag, whether it points to a valid URL, and whether the canonical is consistent with other signals (hreflang, sitemap — bibliotheekterm). We also detect common mistakes like missing canonicals or canonicals pointing to non-existent pages. Test your canonical implementation.