Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

What is Canonical URL?

The single preferred web address you declare for a piece of content when multiple URLs serve identical or nearly identical pages, helping search engines consolidate ranking signals.

Updated · SEO & AI Search

Plain definition

Definition of Canonical URL

The single preferred web address you declare for a piece of content when multiple URLs serve identical or nearly identical pages, helping search engines consolidate ranking signals.

Formula / syntaxHTML link element: rel="canonical" href="https://example.com/pricing" | HTTP header: Link: https://example.com/pricing ; rel="canonical"

Worked example

Say a made-up changelog tool called PatchDesk publishes its pricing page at https://patchdesk.example/pricing. On launch day, people link to four variations of that exact same page: the http version, the www subdomain, a trailing-slash version, and a tagged campaign URL ending in ?utm_source=newsletter&utm_medium=email. Without consolidation, crawlers see four separate URLs displaying the same pricing table.

To clean this up, PatchDesk configures permanent 301 server redirects from http to https and from www to the apex domain. For query-string variants that must remain accessible to visitors, every rendering of the pricing page outputs a self-referencing canonical link element in the document head pointing to the absolute URL https://patchdesk.example/pricing. When Google evaluates those copies, it folds inbound links and indexing signals onto that one clean address. For non-HTML files such as a downloadable PDF spec sheet, PatchDesk can send the equivalent rel="canonical" HTTP response header instead.

Why it matters when you launch

Modern web frameworks make it surprisingly easy to spawn duplicate URLs on day one. Tracking parameters, referral codes, filter states, preview subdomains, and trailing-slash mismatches all split crawler attention across copies of the same page. Setting clean self-referencing canonicals from your very first deploy keeps your Google Search Console coverage report readable instead of filling up with duplicate-page warnings.

Remember that Google treats rel="canonical" as a strong hint rather than an absolute rule. If your internal links, XML sitemap, and canonical tags all agree on the exact same HTTPS URL format, Google almost always honors your choice.

Common mistakes

  • Using relative paths like /pricing instead of full absolute HTTPS URLs inside your canonical link declaration, which can break across hosts or protocols.
  • Pointing every page on your website to the homepage canonical URL, which tells Google that all of your subpages are duplicates of your homepage.
  • Sending conflicting signals, such as putting URL A in your canonical tag while listing URL B in your XML sitemap and linking internally to URL B.
  • Applying a canonical tag to a paginated archive or genuinely distinct landing page when the two pages do not share substantially identical content.

Tools and guides that use it

Official sources

Pritam Ghosh runs Hauntboard and maintains this glossary.

Published · Updated

Building something real? Launch it in public.

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch