probeo

How to add a canonical URL to this page?

canonical-url-missing page

The issue

A page without a canonical URL leaves search engines to choose which of its addresses to show. Tracking parameters, sort orders, www and trailing-slash variants all reach the same content, and the one that ranks may not be the one you link to. The signals that point at the page are split across those variants instead of adding up.

The cause is a missing <link rel="canonical">, or one that can’t be trusted: relative, on http, a fragment, or on another domain. A search engine treats a broken canonical as a hint it can ignore.

Scope

Each page declares its own canonical. Probeo reads the first <link rel="canonical"> in the page’s HTML. A template that prints the same canonical on every page is a different problem from a missing one, and just as damaging.

How to check you have it

  • In probeo: the page reports Missing <link rel="canonical" ...>. A canonical that is present but unusable reports one of Canonical URL must be absolute (not relative), Canonical URL must use https scheme, Canonical URL must not be a fragment-only URL, Canonical URL must be on the same domain (expected host "…", got "…"), or Canonical URL is not a valid URL.
  • By hand: view the page source and search for rel="canonical". The href should be the full https:// URL you want in search results.
  • With a tool: the URL Inspection tool in Google Search Console shows the canonical you declared and the one Google chose.

The fix

Add a <link rel="canonical"> to the page’s <head> that points at the page’s own preferred, absolute https URL.

Generate it per page from the template, with tracking and session parameters stripped. Every variant of the same content points at the same URL, and that URL points at itself. In a paginated series, each page is its own canonical.

Done when: every page declares one absolute, same-domain https canonical, and the check above comes back clean.

Do not

  • Do not use a relative URL in the canonical href.
  • Do not point every page of a paginated series at the first page.
  • Do not include tracking parameters in the canonical URL.
  • Do not point the canonical at a URL that redirects or doesn’t exist.
  • Do not print one static canonical across the whole site.

FAQ

Should the canonical URL be relative or absolute?

Absolute. A relative canonical depends on the address the page was reached through, which is the ambiguity the canonical is meant to remove. Probeo reports a relative canonical as an error.

What happens when a page canonicalizes to a different page?

Search engines treat it as a duplicate of that page and usually show the canonical URL instead. That is correct when the content really is the same. Used on a page with its own content, it removes that page from search.

Should paginated pages canonicalize to the first page in the series?

No. Page 2 holds different items from page 1, so it is its own canonical. Pointing it at page 1 tells search engines the later pages add nothing.

Yes. A Link: <https://…>; rel="canonical" header does the same job and is the only option for files such as PDFs. If a page sends both, they should name the same URL.

Should canonical URLs include query parameters like UTM tracking codes?

No. Strip parameters that don’t change the content, such as utm_source or session IDs. Keep parameters that do, such as a product variant that changes what the page shows.

What prevents canonical tags from becoming incorrect as site structure changes?

Nothing automatic. When URLs move, canonicals generated from old paths point at redirects or 404s. Generating the canonical from the page’s current URL, and checking it on every page, keeps it current.

Which product detects this

Probeo checks this on every page of your site as part of Site Clarity. This page explains one instance; the product tells you every page that has it.