Telling a search engine which address is the real one

Why one page has several addresses

Almost nobody creates duplicates on purpose. They appear from the plumbing. A page reachable with and without a trailing slash, with and without a file extension, over both secure and insecure connections, with and without the www prefix.

Then come the query strings. A tracking parameter on a campaign link, a sort order, a session identifier. Each one makes an address that shows the same content and looks new to a search engine.

By the time you add a print version and a mobile variant, a forty page site can present two hundred addresses. None of that was a decision anybody made.

None of it was a decision anybody made, which is why it is worth checking rather than assuming. Most sites have more addresses than pages.

What the tag does

It sits in the page and names the address you consider authoritative. Every variant carries the same tag, pointing at the same place, so the engine knows which one to keep.

The version it keeps is the one that appears in results, and the signals from the variants consolidate onto it rather than being split between them.

That consolidation is the real benefit. Two versions of a page each earning half the attention rank worse than one version earning all of it.

It is a hint, not an order

This surprises people. A search engine weighs your canonical tag alongside other signals and can choose differently, and it does so regularly.

It looks at which version is linked to internally, which appears in your sitemap, which redirects exist, and which address visitors actually receive. If those disagree with your tag, the tag loses.

So consistency matters more than the tag. Link to one version everywhere, list that version in the sitemap, redirect the rest, and the tag becomes a confirmation rather than an argument.

Consistency matters more than the tag itself: link to one version everywhere, list that version in the sitemap, redirect the rest, and the tag becomes a confirmation rather than an argument.

Self referencing canonicals

Every page should carry a canonical tag pointing at itself, even when no variants exist. It costs nothing and it settles the question before it arises.

It also protects you from address variants you did not anticipate, such as a tracking parameter added by somebody sharing your page on a platform you have never used.

Absolute addresses, always, including the protocol and domain. A relative canonical is a common and avoidable source of confusion.

The mistakes that hurt

Every page on a site pointing its canonical at the homepage. This happens when a template hard codes the value, and it tells the engine your entire site is one page.

A canonical pointing at a page that redirects, or at a page that does not exist. Both signals are ignored and both waste the opportunity.

Canonical tags that conflict with a noindex instruction on the same page, which sends two contradictory messages about a page you presumably had a plan for.

• Every page pointing its canonical at the homepage
• A canonical pointing at a page that redirects
• A canonical pointing at a page that does not exist
• A relative canonical rather than an absolute address
• A canonical on a page that also carries a noindex instruction
• Different canonicals on the same page across templates

When the engine disagrees

Search Console reports the canonical you declared and the one it selected. Where they differ, it has judged two of your pages to be the same thing.

That is a content signal rather than a technical fault. The pages are too similar, and no amount of tag adjustment will change a judgment about content.

The fix is to make them genuinely different, or to accept the decision and merge them into one better page with a redirect from the other.

The fix is content, not markup. Make the pages genuinely different or merge them, which is set out in duplicate content.

How ours are handled

Every page written by Website Builder Studio carries an absolute self referencing canonical, and each address is served at exactly one form with the variants redirected to it.

The sitemap lists the same addresses the canonicals name, so nothing in the site contradicts anything else in the site.

Every page also passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards, which includes confirming the canonical is present and points somewhere real.

The sitemap lists the same addresses the canonicals name, so nothing in the site contradicts anything else in the site.