What Is Canonical?

At a glance

rel=canonical points search engines to a preferred address to consolidate duplicate-page signals. It is a hint, not a user redirect.

Choosing a representative URL for similar pages

rel=canonical identifies a preferred version among parameter URLs, print views, tracking links, case variants or cross-domain copies. Search engines can consolidate some duplicate-page signals at that representative URL and avoid showing several near-identical addresses.

Canonical is a hint rather than a forced redirect. Search engines also compare content, internal links, sitemaps, redirects and protocol variants. A declaration pointing to different content, an inaccessible page or a noindex URL may be ignored in favor of another canonical.

How search engines evaluate canonical signals

• The HTML head or an HTTP Link header can declare a canonical. Use an absolute, crawlable target URL that serves indexable content.
• 301/308 redirects, consistent internal links and sitemap inclusion reinforce canonical signals. Contradictions make independent selection by the search engine more likely.
• A self-referencing canonical explicitly identifies the current preferred address, particularly where tracking parameters or multiple entry points are common.
• Do not point all pagination, language variants or filtered pages to the homepage automatically. Distinct content and search intent may justify separate indexable pages or other handling.

Common migration, parameter and language mistakes

During HTTPS or domain migration, redirect each old page to its corresponding new page and make the new canonical point to that new URL. Templates retaining an old domain, staging host or wrong scheme send conflicting signals. Parameter management must distinguish duplicates, sort orders and filters that change the main content.

Language variants normally use self-referencing canonicals and connect to one another with hreflang. Canonicalizing every language to a single version can prevent other variants being treated as distinct regional pages.

Practical use and interpretation

The declared canonical, target response and self-reference can be displayed directly. A consistent declaration suggests intentional URL management, but search-platform data is needed to confirm the canonical actually selected by a search engine.

A completely unique page with one access path may be fine without a canonical. Duplicate entry points and numerous parameters make the omission more consequential. When the page cannot be fully obtained, its canonical status remains unknown.

Points to consider

An incorrect canonical can direct search signals toward the wrong page and affect which version is shown.

Frequently asked questions

Does canonical automatically redirect visitors?

No. It gives search engines a preferred-URL hint. Redirecting visitors requires an HTTP redirect.

Should every page canonicalize to the homepage?

No. The target should represent identical or substantially similar content. Blanket homepage declarations are often ignored and can undermine page discovery.

Can canonical and noindex appear together?

They can technically coexist, but may communicate conflicting intentions. Do not rely on noindex as a substitute for a coherent canonicalization strategy.