Skip to content
Lizely

Canonical Tag Generator

Turn a preferred absolute HTTP or HTTPS URL into an HTML-escaped rel=canonical link element with browser-standard normalization and fragment removal.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Enter the complete preferred HTTP or HTTPS URL, including the correct host, path and any intentional query string.
  2. 2.Generate the tag and compare the normalized URL with the real 200 page you want search engines to prefer.
  3. 3.Copy the element into the HTML head, then inspect the delivered page for one consistent canonical signal.

About Canonical Tag Generator

Canonical Tag Generator creates an HTML link element that identifies a preferred URL for a duplicate or very similar page. Enter the absolute HTTP or HTTPS target, review the normalized address and copy the generated rel=canonical tag into the page head. The input remains in the browser.

The output has the form link rel equals canonical with an href pointing to the selected URL. Search engines treat this annotation as a strong canonicalization signal, but it is not an instruction that guarantees selection. Content quality, redirects, sitemap entries, internal links and other signals can influence which URL a search system ultimately chooses.

The target must be complete, including the scheme and host. Relative paths such as /products/widget are rejected because their meaning changes with the document location and deployment environment. Only HTTP and HTTPS are accepted. FTP, javascript, data and other schemes are not valid targets in this generator.

Credentials embedded in a URL are rejected. A canonical should identify a public content location, not expose a username or password in markup. If content needs authentication, canonicalization does not make it public or solve access control; review whether the page should be indexed at all.

Fragments are removed. Google documentation generally does not support fragment URLs as canonical targets, and a fragment identifies a location within a representation rather than a separate network resource. Entering https://example.com/page#details therefore generates a target for https://example.com/page.

The browser URL parser normalizes host case, removes default ports and serializes internationalized domains and non-ASCII paths. For example, an uppercase host becomes lowercase, port 443 disappears from HTTPS and a Unicode domain becomes its ASCII-compatible form. Path case remains significant and is not changed.

Query strings are preserved because they may be part of a deliberately chosen canonical address. In the HTML tag, ampersands are escaped as & so the attribute is valid markup while the displayed normalized URL retains the ordinary & character. This difference is expected and does not change the requested URL.

The tool does not remove tracking parameters, sort query keys, force HTTPS, add or remove www, choose a trailing-slash policy, resolve redirects or inspect page similarity. Those decisions depend on the site's routing and content. Automatically guessing them could generate a valid-looking tag that points to the wrong page.

A self-referential canonical on the preferred page is commonly recommended. Duplicate versions should point consistently to the same canonical target. Avoid conflicting signals such as one canonical in HTML, a different canonical in an HTTP header and another URL in the sitemap. Consistency makes the preference clearer.

Place the copied element inside the HTML head, not in the body. For client-rendered applications, make the canonical clear in the source output and avoid scripts that mutate it inconsistently after load. This generator returns markup only; it cannot edit a CMS template or verify how a framework renders the final document.

Eight standards-aligned fixtures cover root-slash insertion, host normalization, path-case preservation, default HTTP and HTTPS ports, fragment removal, Unicode paths, internationalized domains and query strings. Separate tests assert exact HTML escaping and reject relative, unsafe-scheme and credentialed targets.

After adding the tag, view the delivered HTML or inspect the document head on the real URL. Confirm there is one intended canonical element and that its href resolves to a 200 page with equivalent primary content. Check templates across representative routes rather than assuming one successful page proves every generated page.

Canonical tags help consolidate duplicate URL signals; they do not redirect users, remove a URL from search immediately or replace a migration redirect. Use permanent redirects when a duplicate should no longer be served, and keep important internal links pointed at the same preferred address.

Methodology & sources

The input is parsed by the browser URL implementation, restricted to credential-free HTTP(S), stripped of any fragment and serialized canonically. The href is then HTML-attribute escaped, including ampersands in query strings, before insertion into a rel=canonical link element.

Frequently asked questions

Related tools

SEO & Webmaster guides

View all