Inventory what each variant changes
Collect the clean address, relevant parameters, host variants and addresses found in internal links. A parameter may label a campaign, but it may also change sorting, language or the offer shown to visitors. Do not remove parameters before understanding their function.
Read the main content in the same language. Two services sharing a template are not necessarily duplicates. An English translation should not automatically canonicalise to a Swedish source; genuine language equivalents need separate assessment and appropriate hreflang.
Build a matrix of observed responses
Fictional example: /services/website/ and /services/website/?utm_source=newsletter show the same offer. The team selects the clean address as the preferred version. A parameter that changes the offer to an online shop needs a separate content decision before it is classified as a duplicate.
Record initial status, final URL, HTML canonical and any HTTP canonical header. Open the intended target and check content and indexing directives. A canonical that redirects onwards or conflicts with another annotation needs investigation.
| Variant | Decision in this example | Check |
|---|---|---|
| Clean service URL | Preferred main version | Self-referencing canonical |
| Same page with campaign parameter | Same main content | Canonical to clean URL; retain necessary measurement |
| Parameter changes the offer | Not a confirmed duplicate | Read content and assess its task |
| Another language | A separate language version | Own canonical and correct language relationships |
Align signals without breaking functionality
Internal links and sitemap should consistently use the chosen main version. If visitors no longer need a variant, a relevant permanent redirect may suit it. If a parameter supports a necessary feature or measurement, preserve that need or replace it with a tested solution.
Do not use robots.txt to select a canonical. Noindex is also not a substitute for identifying a preferred URL within a duplicate group. Record both the intended indexing state and the relationship between variants rather than treating one tag as a universal fix.
Compare the intended and selected canonical
After changing the implementation, test every pattern in the matrix and a page that should remain unaffected. Save the server response, delivered canonical, sitemap entry and relevant internal links. A corrected source template alone does not establish what a cache or server rule delivers.
With authorised Search Console access, URL inspection can help compare the declared canonical with Google's selected version. A difference is a reason to investigate similarity, access and conflicting signals before making further changes. Tool data can lag behind. A local test establishes the technical behaviour tested, not Google's current decision.