Canonical Tag Fundamentals
This hub answers the definitional questions, and it is the place to start if the vocabulary is still unfamiliar. The guide to the canonical tag covers the element itself: one link element in the head, which Google treats as a strong hint rather than an instruction it must follow. The guide to the canonical URL then separates the address you nominate from the one Google finally indexes, a difference that explains most of the Search Console statuses a reader will meet later.
Canonicalization in SEO describes the process behind both: Google clustering duplicate URLs and picking one to represent the set, after weighing redirects, canonical tags, sitemaps and internal links. That guide is the most useful single explanation of why a declared canonical can lose. A shorter companion explains what "canonicalized" means when an audit tool or a report uses the word as a label, since it describes an outcome Google reached rather than a setting anyone switched on.
The syntax reference for rel="canonical" sets out the exact form and the variations people get wrong: one absolute URL, in a link element inside the head, once per page, with every deviation measured against that rule. The last fundamentals guide widens the frame to the rel attribute as a whole. HTML defines many link relations, and only a few affect how Google handles a page: canonical, alternate with a language or media value, amphtml, icon, and the nofollow, ugc and sponsored hints. Values such as next and prev no longer do anything for Google's indexing.
Implementing Canonical Tags
This hub is procedural. The guide to adding a canonical tag in HTML shows the element and exactly where it belongs. The guide to checking canonical tags explains which view answers which question: View Source and curl show the declared tag, browser developer tools show the rendered one, and only the indexed result in URL Inspection shows the URL Google chose. Confusing those three views is behind many wasted audits, especially on JavaScript sites.
The canonical tag best practices guide reduces the subject to a checklist: one absolute, self-consistent canonical per page, pointing at an indexable 200 URL that every other signal agrees with. Its companion on common canonical tag mistakes starts from the opposite end, and finds that most failures are contradictions rather than typos. The canonical tag vs 301 redirect guide settles the most frequent choice: redirect when the old URL should disappear, and use a canonical when both must stay reachable.
Duplicate Content and Indexing Signals
Duplicate content is where this hub starts, with a correction: duplication is not a penalty, it splits signals across URLs, and a canonical consolidates them. Every other guide here covers a neighboring control and explains it by how it interacts with the canonical, because using the wrong one is the usual cause of a stubborn problem. Keyword cannibalization is related but different. Google does not penalize it either, and the guide argues for acting only when pages with the same intent split clicks, usually by consolidating them with a redirect.
The guide to the robots meta tag and X-Robots-Tag draws the most important line on the site: noindex is a rule Google follows, a canonical is a hint it weighs, and robots.txt hides both from view. Two further guides handle sites that publish in more than one language or region. The hreflang tags guide covers the implementation rules, valid language and region codes, and reciprocal links. The guide to canonical tags and hreflang covers the combination, which works only when every language version names itself as canonical and lists the others.
Choosing where to start
A reader who already knows the definitions can go straight to the second or third hub. A reader arriving from a Search Console status will usually get more from the relevant issue page first, then return here for the mechanism behind it. Each guide opens with its answer, so the first two sentences are enough to decide whether the rest is needed. The guides also link to the issue and platform pages they mention, so the reading order can follow the problem rather than the hub structure.
Every guide opens with a short answer before the explanation, carries the date its content last changed, and links to the research methodology behind it. Where Google's guidance has changed over time, the guide says when, so an older article elsewhere can be read in context.