The tag is one line long and it never shows up in the browser. So when it is wrong, the site looks perfect while the search engine quietly indexes something else. That is how it survives launch day so often.
Why a page has more than one address.
More easily than most people expect. The same page is usually reachable with and without www, with and without a trailing slash, over http and https, with tracking parameters on the end, and again on whatever preview host the site was built on. To a search engine those are different URLs showing the same content, and it has to pick one.
If you do not pick, it picks for you, and it does not always pick the one you are advertising.
The mistake I find most often.
A canonical tag still pointing at the preview URL after launch. The site was built on a staging host, every page canonicalized to that host, the domain went live, and nobody changed it. The browser shows the real domain, the page looks perfect, and the head is quietly telling Google that the real version of this page lives somewhere else.
This is the single most common thing I find wrong on a site someone launched themselves. Google does not see the site the way you see it. It reads the HTML, and the canonical is near the top of it.
The damage is not dramatic, which is why it goes unnoticed for months. The real site does not disappear. It just competes with a copy it has endorsed, and loses some of the credit it earned. Links pointing at your pages get attributed to a host nobody can reach on purpose.
Canonical, redirect, or noindex.
Three tools, and most of the mess I find comes from reaching for the wrong one. A canonical is advice to a search engine about which of several working pages to index. A redirect moves a visitor and the ranking. A noindex keeps a page out of the index whether or not anyone asks.
| The situation | What to use | Why that one |
|---|---|---|
| The same page works at two addresses, and both should keep working | A canonical on both, pointing at the one you advertise | Nobody gets a broken link, and only one address gets indexed. |
| A page has moved, and the old address should stop working | A 301 redirect | It moves the visitor and the ranking. A canonical does neither. |
| Tracking parameters on the end of a campaign link | A canonical pointing at the clean address | Otherwise every campaign creates another version of the page. |
| A preview or staging copy of the whole site | A noindex header on that host | A canonical is a hint and can be ignored. A header cannot. |
| A page you want out of the index for good | noindex until it drops out, then a 410 | Redirecting it to the homepage is a soft 404 and helps nobody. |
| Two pages that genuinely compete for the same search | Neither. Merge them | A canonical between two real pages is a way of avoiding a decision. |
What correct looks like.
- Every page has a canonical tag, and it points at itself on the production domain.
- One host is the real one, and the other redirects to it permanently. The canonical, the sitemap and robots.txt all agree on which.
- Preview and staging hosts are noindexed with a header, so a preview copy cannot compete with the real site at all.
- Tracking parameters do not create new canonicals.
- The canonical is server rendered. Injected with JavaScript, a crawler that skips JavaScript never sees it.
- Every internal link uses the canonical form, so the site is not arguing with its own head.
How to check yours in two minutes.
You do not need a tool. Open your most important page, view source, and search for the word canonical. If the address in it is not the address in your browser bar, you have found the problem. Do it on the homepage, one deep page, and one page with a trailing slash, because those three fail in different ways.
- View source, not the inspector. The inspector shows you the page after JavaScript has run. A crawler may not wait for that, so read the HTML that actually arrived.
- Try the other address. Load the same page without www, or with a slash on the end. Either it redirects to the one you chose, or you have a second indexable copy.
- Check the sitemap agrees. Every URL in the sitemap should be a canonical address, not a variant of one.
- Then check Search Console. The page indexing report tells you which address Google chose, which is the only verdict that counts.
How I handle it.
On a 5Four build every page generates its canonical from one place, and I set the production host once, in the build. Preview builds point their canonicals at the preview host on purpose, so a review copy is never mistaken for the real thing. It is section 5 of the 5Four Launch Checklist, and a blocker: a domain does not get pointed at a site until it passes.
The reason it is generated rather than written is that a hand-written canonical is correct on the day it is written. One built from the page’s own path cannot drift, and cannot be forgotten on the one page nobody re-checked.
Related: Canonical URL in the glossary, sitemap.xml, the Site System.



