Understanding the ins and outs of website growth, we help ensure that your site grows over time with ever-increasing reach and accessibility. Not only do we employ the latest digital marketing techniques for driving traffic directly to your website, but our strategies also focus on gaining loyalty from those visitors so they come back again and again.
Leave your contacts to get a comprehensive and aggressive digital marketing plan taking your business to new heights.
Canonical Tag: Syntax, Examples, and Search Console Errors
A canonical tag is a <link rel="canonical"> element placed in a page's <head> that tells search engines which web address, among near-duplicate pages, is the preferred version to index. Google says it helps consolidate ranking signals from duplicates into one page. Get the target wrong, and Search Console flags the page under one of several similarly named statuses.
TL;DR
Rel=canonical is a hint, not a command. Google can override it, producing the "Duplicate, Google chose different canonical than user" status in Search Console.
"Alternate page with proper canonical tag" is not an error: it means the page correctly points to an indexed canonical, per Google's Page indexing report documentation.
"Duplicate without user-selected canonical" is different: nobody specified a canonical, so Google picked one on its own.
Use rel=canonical for near-duplicates you want to keep live, a 301 redirect for URLs that moved for good, and noindex only for pages that should never appear in Search.
What Is a Canonical Tag?
The rel=canonical link element is how Google, Bing, and other search engines identify one URL (Uniform Resource Locator) as the master copy when several URLs serve near-identical content. Common examples include e-commerce pages sorted by price or color, blog posts reachable with and without a trailing slash, and print-friendly article versions.
Without an explicit canonical signal, search engines still have to pick a version to rank. According to Google's documentation on canonicalization, that choice rests on several factors. These include whether the page is served over HTTP (HyperText Transfer Protocol) or HTTPS (HyperText Transfer Protocol Secure), redirects, sitemap presence, and any rel=canonical annotations Google can find. A canonical signal replaces that guesswork with an explicit statement from the site owner.
How Do You Add a Canonical Tag in HTML?
Adding rel=canonical to a page's HTML (HyperText Markup Language) takes four steps:
Identify the single URL you want indexed among the duplicate versions.
Add a link element with the rel=canonical attribute inside <head>, with href set to that URL as a complete address.
For non-HTML files such as PDFs (Portable Document Format), send a rel="canonical" HTTP header instead.
Optionally, list the same canonical URL in your XML sitemap as an additional hint.
It looks like this:
<head>
<title>Green Summer Dresses | Example Store</title>
Google's guidance on consolidating duplicate URLs states the link element "is only accepted if it appears in the head section of the HTML," so a copy dropped into the body is ignored. The href must be an absolute URL: Google's own bad-practice example is a relative path like /dresses/green/green-dress.html. Google also advises against pointing to a URL fragment, since it generally does not treat fragments as valid canonical targets.
Self-Referencing Canonicals: Can a Page Be Canonical to Itself?
Yes, and Google recommends it as the default. A self-referencing canonical is a rel=canonical link that points back to that same page's own URL rather than to a different one. Google's own guidance calls this a self-referential canonical and recommends adding it even when the page has no known duplicates yet.
Tracking parameters, session IDs, and sorting options can all generate duplicate URLs after a page is already live. Google's documentation illustrates this with a parameter example: signals aimed at a URL like https://example.com/dresses/cocktail?gclid=ABCD still need to consolidate back to the clean version. A self-referencing link set from the start means that consolidation path already exists before any duplicate appears, instead of being added reactively once Search Console starts reporting one.
Does a Canonical Tag Pass Link Equity?
Google's documentation never uses the phrase link equity. It frames the mechanism differently: canonicalization "helps search engines to be able to consolidate the signals they have for the individual URLs, such as links to them, into a single, preferred URL." Signals is the operative word, and it is broader than backlinks alone, though backlinks are explicitly included in Google's own example.
In practice, inbound links pointing at any duplicate URL count toward the preferred version instead of being split across near-identical pages. A page that earns links under three URL variants does not lose credit for two of them once one link element points all three at one address. What Google has not published is an exact formula for how much of that value survives the consolidation, or whether it matches how a 301 redirect passes signals. Treat "canonical tags preserve link value" as directionally accurate, not a guaranteed transfer.
What Does Alternate Page With Proper Canonical Tag Mean?
Search Console's Page indexing report uses several status names for duplicate-adjacent content, and three of them get confused constantly. Per Google's own status descriptions, Alternate page with proper canonical tag applies when a page is marked as an alternate of another page. Examples include an AMP (Accelerated Mobile Pages) page with a desktop canonical, or a mobile version of a desktop canonical. Google states plainly that the page correctly points to an indexed canonical, so there is nothing you need to do.
That gets mistaken for Duplicate without user-selected canonical, and the description is different in a way that changes what action is needed. This page duplicates another page without indicating a preferred canonical, so Google chose one on its own and will not serve this page in Search. The difference is who made the decision: in the alternate-page status, the tag pointed correctly at an indexed page and no fix is needed; in the duplicate-without-canonical status, nobody specified a preference at all.
A third status compounds the confusion: Duplicate, Google chose different canonical than user. Here, a canonical link exists and points at this exact page, but Google's own selection process picked a different URL as the better canonical. The table below lines up all three side by side.
Status
What it means
Is this page indexed?
Action needed
Alternate page with proper canonical tag
The page correctly points to a canonical that Google has indexed, for example an AMP or mobile alternate.
No, by design. The canonical version is indexed instead.
None.
Duplicate without user-selected canonical
The page duplicates another page, but nobody specified a preferred canonical. Google picked one on its own.
No. Google serves the page it picked.
Add an explicit rel=canonical so you control the choice.
Duplicate, Google chose different canonical than user
A canonical link exists and points at this page, but Google's algorithm picked a different URL instead.
No. The page marked as canonical is not the one indexed.
Review why Google favors the other URL: content depth, internal links, or redirects.
Google updates this guidance periodically; the wording above reflects its documentation as reviewed in September 2026.
Canonical Tag vs. Redirect vs. Noindex
These three tools solve different problems, and mixing them up creates exactly the kind of Search Console confusion covered above. Rel=canonical is a hint about which URL to prefer among versions that all stay live. A 301 redirect permanently sends both users and search engines from one URL to another. A noindex directive removes a page from Search results entirely, whether or not a duplicate exists.
Google's own guidance on consolidating duplicate URLs is specific about this boundary. It advises against using noindex to prevent selection of a canonical page within a single site, since that blocks the page from Search entirely, and recommends rel=canonical annotations instead. The robots meta tag documentation adds a mechanical reason: noindex only works if Google can crawl the page and read it. A page blocked in robots.txt never gets the chance to apply its own noindex rule.
Redirects behave differently. Per Google's documentation on 301 redirects, Google tracks both the redirect source and target, and the old URL can persist as an alternate name that fades away on its own over time. A canonical setup never does this: both URLs stay live and reachable, and only the indexing decision changes.
Rel=canonical
301 redirect
Noindex
Tells Google
This other URL is the preferred version.
This URL has permanently moved.
Do not show this page in Search results.
What visitors see
No change. Visitors still reach the original URL.
Automatic redirect to the new URL.
The page still loads normally.
Still crawled?
Yes, though less often than the canonical, per Google's canonicalization documentation.
Google follows the redirect and keeps tracking the old URL as a source.
Yes. Noindex requires crawling to be discovered.
Best fit
Near-duplicates you want to keep live, such as sorting or tracking parameters.
Content permanently moved to a new URL.
Pages you never want in Search; not a substitute for canonical selection.
Google's canonicalization documentation states that the canonical page is crawled most regularly, while duplicates are crawled less frequently to reduce the crawling load on sites. That is a direct reason consolidating duplicates protects crawl budget on larger sites.
Common Canonicalization Mistakes
Most rel=canonical problems trace back to a handful of repeatable errors, several of them called out directly in Google's own guidance:
Using a relative path instead of an absolute URL, such as /dresses/green/green-dress.html. The href needs the full address, including the protocol.
Sending conflicting signals across methods: a sitemap that lists one URL while the tag on the page points to another.
Placing the tag outside the <head> section, where Google will not read it.
Canonicalizing to a URL fragment, which Google generally does not support as a canonical target.
Reaching for noindex to force a canonical choice within one site. This removes the page from Search entirely rather than consolidating it.
Pointing the tag at a URL that itself errors out or redirects elsewhere. If the destination is a bad URL or an invalid URL, Google has nothing valid to consolidate signals into.
Rel=canonical is only one control inside a page's broader on-page SEO setup, alongside title tags, meta descriptions, heading structure, and internal links. Getting the tag right does not compensate for those other elements being wrong.
FAQ
What is a canonical tag?
A canonical tag is an HTML link element that uses the rel=canonical attribute to tell search engines which URL is the preferred version among near-duplicate pages. It sits inside the page's head section and points to one absolute URL. Google treats it as a strong hint for consolidating ranking signals, not as a command it is forced to follow.
How do I add a canonical tag in HTML?
Add a link element with the rel=canonical attribute inside the page's head section, with its href set to the absolute URL of the preferred page. Google only reads this element from the head section, so a copy placed in the body is ignored. The href value must be a complete URL, including the protocol, rather than a relative path such as /page-name.
What does alternate page with proper canonical tag mean?
Alternate page with proper canonical tag is a status in the Search Console Page indexing report. Per Google's description, it means the page is marked as an alternate of another page, such as an AMP or mobile version, and it correctly points to a canonical page that Google has indexed. Google states there is nothing you need to do when you see this status.
Does a canonical tag pass link equity?
Google's documentation never uses the phrase link equity. It says canonicalization helps consolidate the signals search engines have for individual URLs, including links pointing to them, into one preferred URL. Inbound links to duplicate URLs then count toward the canonical version instead of being split. Google has not published an exact formula for how much value carries over, so treat this as directional, not a guaranteed transfer.
Can a page be canonical to itself?
Yes, and Google recommends it. A self-referencing canonical is a rel=canonical link that points back to that same page's own URL. Google's documentation explicitly advises adding this self-referential setup on every canonical page, even ones with no known duplicates yet, since parameters such as tracking codes or session IDs can create unexpected duplicate URLs later.
