What Is a Canonical Tag (and Do You Actually Need One)?

06 September 2026·6 min read

Quick answer: A canonical tag is a small piece of code that tells Google “out of these similar or duplicate pages, this is the one I want indexed and ranked.” You need one whenever the same or near-identical content is reachable at more than one URL — filtered product listings, printer-friendly pages, or URLs with tracking parameters attached are the classic culprits. Without it, Google has to guess which version matters, and sometimes it guesses wrong or splits ranking signals between them. It's a quiet fix, but it's one of the most commonly missing tags on small business sites. ✨

Canonical tags have a reputation for being confusing, but the concept is simple once you see it in action: they're a signpost, not a rule. You're not blocking Google from seeing the duplicate pages — you're telling it which one to treat as the “real” one when it's deciding what to show in search results.

The reason this matters more than people think: most sites have far more duplicate or near-duplicate URLs than their owners realise, and every one of those is quietly 💖 diluting the ranking signal that should be concentrated on a single page.

What most businesses get wrong

The most common mistake isn't missing canonical tags altogether — it's not realising duplicate URLs exist in the first place. A filtered category page like /shoes?colour=black&size=9 looks like a completely different page to Google than /shoes, even though the content is 95% identical. Multiply that by every filter combination on an e-commerce store, and you can end up with thousands of near-duplicate URLs competing against each other for the same rankings, none of them winning clearly.

Do I need a canonical tag? A 5-question flowchart

1. Does this exact content (or something 90%+ similar) exist at more than one URL?
→ No: stop, you don't need one for this page.
→ Yes: go to question 2.

2. Is the duplication caused by filters, sorting, or tracking parameters (e.g. ?colour=, ?utm_source=, ?sort=price)?
→ Yes: add a canonical tag on the parameterised URL pointing to the clean, filter-free version.
→ No: go to question 3.

3. Is it a printer-friendly, PDF, or “duplicate for a different audience” version of the same page (e.g. a mobile-specific URL)?
→ Yes: canonical tag on the duplicate, pointing to the main version.
→ No: go to question 4.

4. Is it genuinely similar but written for a different suburb, product variant, or use case (e.g. separate but real pages for each suburb you service)?
→ Yes: don't canonicalise these away — write each one with enough unique, specific content that it deserves to rank on its own. A canonical tag here would tell Google to stop indexing pages you actually want found.
→ No: go to question 5.

5. Do both versions get real, separate traffic and serve a genuinely different purpose?
→ Yes: leave them as-is, no canonical needed.
→ No: canonicalise the weaker version to the stronger one.

The tag itself (place in the <head> of the duplicate page):
<link rel="canonical" href="https://yoursite.com.au/the-preferred-url/" />

E-commerce store with filterable product categories: A store selling outdoor gear had a “/hiking-boots” category with size, colour and brand filters, generating over 200 unique URL combinations, all showing the same 40 products in different order. Adding a self-referencing canonical to the filtered URLs (pointing back to plain “/hiking-boots”) consolidated ranking signals onto one page within about six weeks.

Local service business with near-identical suburb pages: A business had built pages for “Service in Suburb A” and “Service in Suburb B” that were 90% copy-pasted text with the suburb name swapped. Rather than canonicalising one to the other (which would have killed one page's chance of ranking), the fix was rewriting each with genuinely local detail — different service areas, different local landmarks, different context — so both could stand on their own without needing a canonical at all.

Business running paid campaigns with tracking parameters: A business running Google and Facebook ads had landing pages appended with ?utm_source=facebook and ?utm_source=google, which Google was indexing as separate URLs. A canonical tag pointing every parameterised version back to the clean URL stopped the split and let ranking signal consolidate on one indexed page.

How to actually implement one

Most Shopify themes and major CMS platforms add self-referencing canonical tags automatically on standard pages, so the manual work is mostly about the exceptions: parameterised URLs, custom filter systems, or pages built with apps that generate their own URL structures.

To check whether a page has a canonical tag, right-click and “view page source,” then search for “canonical.” You'll see something like <link rel="canonical" href="..." /> inside the <head>. If it's missing on a page you suspect is a duplicate, that's your fix; if it's pointing to the wrong URL, that's worth fixing too — a canonical pointing at the wrong page can actively hurt the page you want ranking.

A canonical tag is a suggestion, not a command. Google usually respects it, but if the “canonical” page and the duplicate are different enough in content or backlink profile, Google can still choose to index the other one instead.

💡 When in doubt, self-reference. A page with a canonical tag pointing to itself is harmless and is best practice on almost every page — it's the missing or wrong canonicals on duplicate URLs that cause the real damage.

Mistakes to avoid

Canonicalising genuinely unique pages together. Suburb pages, product variants, or different service pages with real, distinct content should never be canonicalised to each other — you'll tell Google to stop showing pages you actually want ranking.
Pointing the canonical to a redirected or 404 URL. This confuses the signal entirely — always point to a live, working, indexable page.
Using canonical tags instead of fixing the actual duplication. If you can restructure your URLs to avoid creating duplicates in the first place (e.g. consistent parameter handling), that's cleaner than patching it after the fact.
Assuming Google always obeys the tag. It's a strong hint, not a directive — if your “preferred” page has thin content and the “duplicate” has more backlinks, Google may still choose to show the other one.

Frequently asked questions

Can I just use robots.txt to block duplicate pages instead?

Not really — blocking a page stops Google crawling it, but any ranking signal or backlinks pointing to it get stranded rather than consolidated. A canonical tag lets Google crawl the page and pass its value to the preferred URL instead.

Does adding a canonical tag guarantee the other version stops showing in search results?

Not always, honestly. It's a strong signal Google generally follows, but if the “duplicate” has substantially different backlinks or engagement, Google can still choose to index it instead.

Do I need canonical tags if my site is small and has no duplicate content?

Not urgently. If you've genuinely got no filtered URLs, parameters, or duplicate pages, canonical tags aren't a priority — though most Shopify and CMS themes add self-referencing ones automatically anyway.

What's the difference between a canonical tag and a 301 redirect?

A 301 redirect sends visitors and Google from one URL to another — the old one stops working as a destination. A canonical tag keeps both live but tells Google which to prioritise. Use a redirect when a page should disappear; use a canonical when both need to keep working.