Canonical Tags Pointing at the Wrong Page

What the tag does

The same content is frequently reachable at more than one address: with and without www, with tracking parameters attached, as part of a category listing, or in a printer-friendly version.

The canonical tag is a line in a page's code saying which address is the definitive one.

Search engines use it to consolidate those variations, so signals accumulate on one address rather than spreading across several.

Used correctly it is quietly useful. Used incorrectly it is one of the few small errors that can remove a page from results entirely.

Why a mistake is serious

Because the tag is a statement about the page it sits on, made by that page.

A page whose canonical points at a different address is saying: I am a duplicate, index that instead of me.

Search engines generally respect that, which means a good page can be excluded on its own instruction, with no error anywhere and nothing visibly wrong.

Nothing in the site's appearance changes, and the only symptom is a page that will not appear in results however much work goes into it.

Which is why this is worth checking when a specific page refuses to rank despite being clearly better than what does.

The four common mistakes

• Every page pointing at the homepage.
• Pointing at a staging or development address.
• Pointing at the insecure or wrong-www version.
• A template copying one page's tag across many.
• Pointing at a page that redirects or no longer exists.

The first is the most damaging and appears when a tag is added to a shared template with a fixed address rather than one generated per page.

The default is self-referencing

The rule that covers almost every small business page.

Each page should normally declare its own address as the canonical one, which sounds redundant and is not.

It resolves the variations automatically: a visit with tracking parameters attached still declares the clean address, and the parameterised version consolidates into it.

Most platforms do this correctly out of the box, which is why this rarely comes up until somebody adds a plugin, edits a template, or migrates a site.

If you are unsure what your pages declare, the answer is visible in the page source and takes a minute to check.

How to check it

Two methods, neither requiring anything installed.

View the page source in a browser and search for the word canonical, which will show the address the page declares. Do it on your homepage, a service page, and a blog post, since those frequently use different templates.

Or use Search Console's inspection tool, which reports both the canonical the page declares and the one Google actually selected, which is the more informative pair.

Where those two differ, that is worth understanding: it means the declaration was not accepted, usually because the page is genuinely near-identical to another.

Check after any migration, template change, or plugin addition, since those are when it breaks.

A worked example

A business added a plugin to manage their page titles and descriptions, which also managed canonical tags.

A setting had been configured on one page and applied site-wide, so every page on the site declared the homepage as its canonical address.

Over the following months their service pages gradually stopped appearing, while the homepage continued to rank.

They assumed an algorithm change, rewrote two pages, and considered rebuilding.

The inspection tool reported the canonical clearly on the first page they checked, naming the homepage as the declared address.

Correcting the setting took two minutes and the pages returned over about six weeks.

Six months of declining performance had been one misapplied setting, and no tool had reported an error because nothing was broken.

It is a hint, not a command

Worth knowing so the tag is not over-trusted in either direction.

Search engines treat the canonical as a strong signal rather than an instruction, and they can select a different address if the evidence contradicts your declaration.

That means a correct tag does not guarantee consolidation, and it also means an incorrect one is not always obeyed, which is why the damage is sometimes partial and confusing.

Signals should agree: the canonical, your internal links, your sitemap, and any redirects should all point at the same version of a page.

Where they disagree, the outcome is decided by something other than your intention, which is the situation to avoid.

Do not use it to remove pages

A misuse worth naming, because it is a common misunderstanding.

A canonical is not a way to hide a page you do not want indexed, and pointing an unrelated page at another does not remove it cleanly.

For a page that genuinely should not appear, mark it as not for indexing. For a page that has moved, redirect it. For a genuine duplicate, canonical is correct.

Those three tools cover the situations, and the frequent error is reaching for a canonical because it is the one somebody has heard of.

Using it across pages that are not actually duplicates produces unpredictable results and occasionally removes the wrong one.

The counter-case

Canonicals matter less on a small site than the attention this subject attracts.

A modest site with twenty distinct pages, no shop, no filtering, and no parameters has very little duplication for a canonical to resolve, and correct self-referencing tags are already handled by the platform.

There is also a real risk in editing them without understanding, since this is a setting where a wrong value is more harmful than no value at all.

Where a site has no duplication problem and pages are appearing normally, this is a thing to verify once and then leave.

It moves up the list when a specific good page will not rank, or after a migration or plugin change, which are the moments it breaks.

The check

1. View source on three different page types.
2. Search for canonical and read the address.
3. Confirm each page declares itself.
4. Watch for staging or insecure addresses.
5. Compare declared against selected in Search Console.
6. Check again after any migration or plugin change.
7. Use the right tool for removal or moves.

Step three is the whole check for most sites, and a page declaring anything other than itself is worth understanding before anything else is changed.

Near-duplicate location pages are covered in a page for every suburb.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.