Canonical URLs and when to use them
A canonical URL is the preferred address for a page when the same content is reachable through several URLs. It does not create another page or stop visitors opening a duplicate. It gives search engines a consolidation signal, usually written as <link rel="canonical" href="https://example.com/page/"> in the HTML head.
The tag should contain one absolute, stable address. On an indexable page, best practice is a self-referencing canonical: it points to that page’s own clean URL. Search engines can still crawl alternatives, so the tag is a strong hint, not an automatic redirect or indexing guarantee.
Duplicate addresses are routine on blogs, Shopify stores and membership platforms. Tracking links add parameters, WordPress exposes archive paths, and apps generate alternate story versions. Google is the dominant search engine in Australia, so tidy indexation signals help small businesses compete beyond local areas.
Canonical tags work best when they reflect a deliberate content hierarchy. They suit near-duplicates, but cannot make materially different pages identical, correct an inaccurate sitemap or repair a broken redirect. Ask whether each address is a useful destination or merely another route to the same content.
What a canonical URL signals
A canonical relationship uses a rel="canonical" link element. Its href should use HTTPS, the final hostname and the site’s trailing-slash convention. For example, https://www.example.com.au/guides/seo/ and https://example.com.au/guides/seo should not compete when both serve one guide.
The canonical identifies the URL that represents the content and where a crawler should concentrate signals. It does not change the HTTP response or redirect visitors. Google may choose another address when stronger evidence points there, especially if one version has more links or the pages differ.
Self-referencing is the safest default for normal pages because it confirms the address you want indexed. Internal links, XML sitemaps and social metadata should agree with it. Australians commonly call a handset a mobile rather than a cell phone; mobile-friendly design is separate from having mobile URL variants. The mobile browsing guidance explains the reading difference.
Common sources of duplicate pages
Campaign URLs are common. A newsletter may link to /articles/canonical-tags?utm_source=email, while social posts and Google Ads create other query strings. If the campaign data has no search value, each parameter version can point to the clean canonical address.
Platforms create more duplicates. WordPress can expose category, tag, feed and attachment versions; ecommerce filters produce colour and sort combinations; print or AMP templates can repeat a story. Crawlers need to distinguish presentation copies from pages deserving separate visibility.
Technical variants need different handling. An HTTP page, www hostname or slash-style change should normally use a 301 permanent redirect. A canonical can confirm the destination but cannot replace that redirect. Historic references also linger: links to the PAM reference site can survive for years, so a moved property may need redirect maintenance as well as an updated canonical.
Compare the main indexing signals
These signals overlap but answer different questions. A redirect changes the destination, a canonical identifies a preferred version, noindex asks for exclusion, and a sitemap advertises URLs for discovery. The correct combination prevents mixed instructions.
| Signal | What it communicates | Best suited to | Main limitation |
|---|---|---|---|
| 301 redirect | The old address has permanently moved | Replacements, domain changes and technical variants | Must be updated and maintained |
| Canonical URL | This is the preferred version of similar content | Parameter links, syndicated copies and close duplicates | Does not redirect visitors or guarantee selection |
noindex |
Do not list this URL in search results | Private, thin or non-search utility pages | The page must remain crawlable for this directive to work |
| XML sitemap | Here are URLs worth discovering | Canonical pages and a clear site structure | Does not exclude, redirect or choose between duplicates |
Combining signals can be sensible, such as a 301 redirect followed by a self-referencing canonical at the destination. Combining noindex with a canonical is conflicting: one asks for exclusion while the other asks for selection. Verify the result in Search Console and Bing Webmaster Tools.
When to use a canonical URL
Use a canonical when multiple URLs return substantially the same page and you have chosen a primary address. Common cases include a product copied into a campaign landing page, an article syndicated to a partner, a printable version, or one resource served through clean and parameterised URLs. Select the version you want search results to display.
For ecommerce catalogues, apply it to true duplicates, not every alternate filter. /collections/boots/ and /collections/boots/?size=8 may be equivalent, but a page focused on one product can be unique and should self-canonicalise. If inventory, copy or intent differs, use noindex, follow or crawl controls as appropriate.
Syndication needs care. On an original article, use a self-referencing canonical; an authorised republisher can point a true copy back to the source when the relationship is agreed. This supports consolidation without pretending independently edited articles are identical. Ensure the original stays available.
For a moved page, update the canonical, internal links and XML sitemap after setting up a 301 redirect. A Melbourne cafe moving from Chapel Street may keep old review links, but one current location URL should collect the authority.
When to leave pages indexable
Do not canonicalise pages that are intentionally distinct. Category pages, tag archives, paginated results and location pages often target different searches. Pointing every page-two result to page one can hide valid landing pages and flatten site structure.
Faceted navigation needs a deliberate policy. Colour, price and sort combinations may have no unique demand, but a filter for Australian-made goods can be a genuine result. Australian stores often show prices in Australian dollars with GST included and use .com.au domains, making clean regional taxonomy more important than removing every filtered URL.
Location filters can also deserve visibility. Sydney, Melbourne, Brisbane and Perth use postcode prefixes such as 2000, 3000, 4000 and 6000. Pages serving those areas can target distinct local intent, so each useful location page should self-canonicalise and receive relevant internal links.
Translated and regional pages should self-canonicalise when each language or market offers distinct content. Pair them with correct hreflang annotations and consistent internal links. Use noindex for private accounts, staging sites, thin internal search results and other URLs that should be crawled but never listed.
Build a reliable canonical workflow
Begin with a crawl or sitemap export, group URLs by content, and inspect status codes before editing tags. Choose the cleanest, durable address, make its canonical absolute and self-referencing, and remove competing tags left by old themes or plugins. Two conflicting elements can dilute a correct setup.
Update the source, not only the visible page. WordPress users can use a reputable SEO plugin, while custom sites should build the tag into the template. Keep XML sitemaps, internal links, pagination and hreflang references aligned. Record the chosen URL in the publishing workflow so editors do not restore a parameterised variant.
Test rendered HTML, response and index status, then monitor changes after migrations or redesigns. Search Console can reveal canonical reports, while server logs show whether old URLs redirect correctly. Test one page before applying the rule across a WordPress or Shopify store because filters and templates create exceptions.
Start with your five most valuable duplicated pages, select one stable address for each, and implement a single self-referencing canonical. Point menu links, article links and sitemap entries to it, then check the live HTML and redirect map today. This cleanup gives Australian bloggers and online stores a clearer structure without hiding pages customers need.