ToolJutsu
All tools
Web & SEO Tools

Canonical URL Builder

Build canonical URL tags to avoid duplicate content.

Normalization options
Before

HTTP://WWW.Example.com/Blog/My-Post/?utm_source=news#section

After

https://www.example.com/Blog/My-Post

Canonical URL
https://www.example.com/Blog/My-Post
Canonical link tag
<link rel="canonical" href="https://www.example.com/Blog/My-Post" />

Place this tag inside the <head> of every duplicate or near-duplicate page.
Processed on your device. We never see your files.

How to use Canonical URL Builder

What this tool does

The Canonical URL Builder takes one URL and rewrites it into a clean, consistent canonical form. You paste an address, choose which normalisations to apply, and the tool shows the tidied URL alongside the ready-to-paste <link rel="canonical"> tag. It can force HTTPS, lowercase the hostname, remove a leading www., drop a trailing slash, strip the query string and strip the # fragment — each as an independent toggle so you stay in control. A clear before-and-after comparison shows exactly what changed, and invalid input is flagged immediately rather than producing a broken tag.

All parsing happens in your browser with the native URL engine, so the result is accurate and nothing is uploaded.

Why it matters for SEO

Duplicate content is rarely about copied text — far more often it is the same page reachable at several URLs. http:// and https://, www. and the bare domain, /page and /page/, and any link decorated with ?utm_source=newsletter all resolve to identical content but look like separate pages to a crawler. When that happens, ranking signals such as links and engagement get spread thinly across the variants instead of accumulating on one strong page, and search engines may index a version you did not intend.

A correct canonical tag fixes this. It tells search engines, “of all the URLs that show this content, this is the one to index and credit.” That consolidates link equity, prevents tracking-parameter URLs from cluttering the index, and keeps the address shown in search results stable and trustworthy. For large sites with faceted navigation or heavy campaign tagging, disciplined canonicalisation is one of the most effective ways to keep crawl budget and ranking signals focused where they matter.

How to use it

  1. Paste the page URL into the input field. A scheme-less host such as example.com/page is accepted and assumed to be HTTPS.
  2. Review the normalisation toggles. The defaults force HTTPS, lowercase the host, strip the trailing slash, and strip the query and hash.
  3. Turn off any rule that does not suit the URL — for example, keep the query string for a page whose parameters change its content.
  4. Check the before-and-after comparison to confirm only the changes you expect were applied.
  5. Copy the canonical URL, or copy the full <link rel="canonical"> tag, and place the tag inside the page’s <head>.

SEO best practices

Add a self-referencing canonical to every indexable page — a page should name itself as its own canonical when there is no better target. Always use absolute URLs with the scheme and host. Keep the canonical consistent with your other signals: internal links, the XML sitemap and any redirects should all point at the same address. Pick one host convention, either www or non-www, and apply it everywhere. Strip tracking parameters from canonicals but preserve parameters that genuinely change the page. Make sure the canonical target returns a 200 status and is not itself redirected.

Common mistakes to avoid

The classic error is canonicalising every page to the homepage, which tells search engines your inner pages are not worth indexing. Avoid pointing a canonical at a URL that redirects or returns a 404. Do not mix www and non-www canonicals across the site. Do not strip query parameters that define a unique page, such as a product variant or pagination number — that collapses real pages into one. Avoid relative canonicals, which can resolve incorrectly. And remember the tag is advisory: if your sitemap and internal links contradict it, search engines may ignore the canonical you set.

Privacy & your data

The URL you enter is parsed and normalised entirely by JavaScript running on your device, using the browser’s built-in URL engine. The tool makes no network requests, sends nothing to any server, and stores or logs nothing. Your input exists only in the page while it is open and is discarded the moment you close or refresh the tab. That makes it completely safe to normalise URLs for staging environments, unpublished pages and internal systems — none of those addresses ever leave your browser.

Frequently asked questions

What is a canonical URL and why do I need one?
A canonical URL is the single address you want search engines to treat as the master version of a page. The same content is often reachable through several URLs — with and without www, with tracking parameters, with a trailing slash — and search engines see those as separate pages competing with each other. A canonical link points them all at one preferred URL so ranking signals consolidate instead of splitting.
Should the canonical tag be an absolute URL?
Yes. Always use a fully qualified absolute URL including the scheme and host, such as https://example.com/page, not a relative path like /page. Relative canonicals can be misinterpreted, especially when a page is crawled at an unexpected address. This tool always outputs an absolute, normalised URL for that reason.
Does stripping the query string ever cause problems?
It depends on the parameter. Tracking parameters such as utm_source carry no unique content and should be stripped from the canonical. But parameters that genuinely change the page — a product variant, a paginated page number, a filtered category — must stay, or you will canonicalise distinct pages onto one. Turn off 'strip query string' for those URLs and keep the meaningful parameters.
Is the canonical tag a command or a hint?
It is a strong hint, not a directive. Search engines usually honour a sensible self-consistent canonical, but they can override it if your signals conflict — for example if internal links, sitemaps and redirects all point somewhere else. Keep every signal consistent and the canonical you choose will almost always be respected.
Is the URL I enter kept private?
Yes. The URL is parsed and normalised entirely by JavaScript in your browser using the built-in URL engine. Nothing is sent to a server, no request is made, and nothing is stored or logged. When you close the tab the URL is gone, so you can safely normalise links for unpublished or internal pages.

Related tools

Hreflang Tag Generator

Generate hreflang tags for multilingual SEO.

Meta Tag Generator

Generate SEO meta title, description, and keyword tags.

URL Parser

Break a URL into its component parts.

Sitemap.xml Generator

Generate an XML sitemap from a list of URLs.

Robots.txt Generator

Build a robots.txt file with common crawl rules.

Slug Generator

Generate clean, SEO-friendly URL slugs.