DigitalBanzai Knowledge

Canonical

Practical guide to what the canonical tag signals, why the check reviews it, and how to review preferred URLs without making indexing promises.

Italian version
Severity
Moderate
Estimated fix time
15-30 min
Technical level
Intermediate
Applies to
WordPressStatic HTMLCMS / E-commerceSEO Plugins

What it is

A canonical tag is a line of code placed inside the <head> of an HTML page. It looks like this:

<link rel="canonical" href="https://example.com/page/">

This element declares the preferred URL for that page. It is commonly used in two ways:

  • Self-referencing: the tag points to the same URL as the page it appears on, confirming that this is the main version.
  • Pointing to a different URL: the tag points elsewhere because the current page is a variant, duplicate, or secondary version of the main content.

Why it matters

The canonical tag helps reduce ambiguity between similar URLs, but it should be treated as a signal, not an absolute command. Search engines may ignore it or reinterpret it when other site signals are inconsistent.

This signal is especially useful when multiple URLs exist because of:

  • tracking parameters or navigation filters;
  • product variants in ecommerce stores, such as color or size options;
  • different versions involving www, HTTP/HTTPS, or trailing slash differences.

Using a canonical tag can help keep pages, sitemaps, redirects, and internal links more consistent. It does not guarantee indexing and it does not replace a clean site structure. A missing canonical is not automatically a severe problem, while a wrong canonical can create more confusion than an absent one.

How this is checked

The scanner fetches the analyzed page and observes the presence and condition of this technical signal.

The current check verifies:

  • whether the analyzed page is reachable;
  • whether a rel="canonical" tag exists in the code;
  • whether the canonical value is empty or populated;
  • whether the declared URL appears formally valid;
  • whether multiple canonical tags appear on the same page, making the signal ambiguous or less reliable;
  • whether the tag points to the page itself or to a different URL;
  • whether the declared address uses HTTP instead of HTTPS;
  • whether the declared value appears potentially inconsistent with the URL being analyzed.

The scanner observes the signal declared by the page. It does not decide on its own which URL must be treated as canonical.

Possible findings

Each finding should be read as a review signal, not as an automatic penalty.

Missing canonical

No canonical tag was detected on the page. This is not automatically a severe issue, but it may be worth reviewing when the site exposes multiple URLs for the same content.

Empty canonical

The tag exists, but the href attribute does not contain a usable address. In practice, the signal is present but does not express a usable preference.

Invalid canonical

The declared URL contains syntax issues or is not structured correctly.

Canonical differs from analyzed URL

The tag points to a different address. The scanner highlights this so you can confirm whether that choice is intentional and aligned with the site structure.

Canonical points to non-HTTPS URL

The declared address uses a non-secure HTTP address instead of HTTPS. This can weaken consistency when the main site already runs on HTTPS.

Multiple canonicals

Two or more canonical tags were found on the same page. In that case, the signal can become ambiguous or less reliable for search engines.

Inconsistent canonical

The declared URL points to a page that redirects elsewhere or does not appear aligned with other site signals, such as the sitemap and internal links.

  1. If the page is unique and primary: use a self-referencing canonical that matches the displayed URL.
  2. If the page is a variant or duplicate: make sure the tag points precisely to the version you consider primary.
  3. If the declared URL is not reachable or not correct: fix that first before adjusting other signals.
  4. If the canonical points to HTTP or to an inconsistent resource: align it with the correct and stable page version.
  5. If signals conflict: compare canonical values with sitemaps, redirects, and internal links to reduce inconsistencies.
  6. After each change: update a few elements at a time and run a new scan to verify the result.

How to fix it

Static HTML

If you manage the HTML directly, open the page file and locate the <head> section. Add or correct the tag, making sure the address is absolute and complete:

<link rel="canonical" href="https://example.com/page/">

WordPress / SEO plugins

In WordPress, canonical handling is often automated by SEO plugins such as Yoast, Rank Math, or All in One SEO.

  • Open the page or post you want to review.
  • Check the advanced section of your SEO plugin for the canonical field.
  • If the page is a duplicate or a variant, enter the main URL in the custom canonical field.
  • After saving, clear cache if the site uses caching layers or a CDN.

CMS / E-commerce

In ecommerce platforms and custom CMS setups, canonical tags are often generated dynamically from templates.

  • Pay close attention to pages with filters, search parameters, categories, or product variants.
  • Check that the system does not apply the same incorrect canonical across different pages.
  • Also confirm that the template does not consistently point to a URL that does not match the real site structure.

How it appears in the report

In the report, the Canonical check shows whether the tag was found, which value it contains, and whether any part of it may need review.

The scanner simply observes the signal declared by the page to help you assess its overall consistency, leaving the final decision to the site owner or maintainer based on the site structure.

When to run a new scan

Run a new scan whenever you update canonical tags, CMS templates, sitemaps, or redirect rules. This helps you confirm that the tag is present, valid, and aligned with the analyzed URL.