Canonical Tag

What is the difference between a canonical tag and a canonical URL?

The difference between a canonical tag and a canonical URL is request versus decision: the tag is the version you ask for, and the canonical URL is the version Google picks. Google defines the canonical URL as the URL it chose as the most representative from a set of duplicate pages, and canonicalization (canonicalisation in Australian English) as the process of selecting it.

Most of the time the two match. When they do not, the tag lost, which is why the next question matters.

Is a canonical tag a directive?

A canonical tag is not a directive. Google calls it a hint, not a rule, and says it may choose a different page as canonical than you do. That is the single most misunderstood fact about the tag: adding it states a preference, it does not settle the question.

You can see when Google disagrees with you. The Search Console page indexing report has a status for exactly that case, "Duplicate, Google chose different canonical than user", and it is the first place to look when the URL you nominated is not the one appearing in results.

How strong is a canonical tag compared with other signals?

A canonical tag is one of the two strong signals, ranked just behind a redirect. Google lists the methods in order of how strongly they can influence its choice, and notes that they stack, so signals pointing the same way reinforce each other.

Google also weighs whether a page is served over HTTPS. The practical rule follows from the table: when your signals disagree, for example a sitemap listing one URL while the tag names another, you have handed the decision back to Google.

How do you set a canonical URL?

You set a canonical URL with a rel="canonical" link element in the page's <head>, or with a rel="canonical" HTTP header. Google only accepts the link element when it sits in the <head>. The HTTP header is the option for files that have no HTML to put a tag in, such as a PDF:

Link: <https://www.example.com/downloads/white-paper.pdf>; rel="canonical"

Google supports the header for web search results only, and asks for absolute URLs in both forms. If a page could carry either, its advice is to choose one and go with it, which leads to the rest of the best practices.

What are the best practices for canonical tags?

The best practices for canonical tags come down to one clear, absolute, self-consistent signal per page. These are the rules Google states, in its own terms.

The pattern behind all four do-nots is the same: each one sends a signal that blocks or contradicts the preferred version instead of pointing at it.

Is duplicate content a penalty?

Duplicate content is not a penalty. Google states that some duplicate content on a site is normal and is not a violation of its spam policies. The real cost is split signals and Google picking a version you did not want, which is the problem a canonical tag exists to solve.

The tag can also point across domains. RFC 6596 allows the preferred version to sit on a different hostname, which is how syndicated copies point back at the original. Check which URL Google actually chose rather than assuming it followed you.