How to Use Canonical Tags for Duplicate URL Versions
Identify duplicate versions, choose a sensible preferred URL and align canonical, sitemap and internal-link signals.
By New Delhi Website Technologies · Practical SEO learning series
Start with a website you own or are authorised to edit. Examples are teaching exercises; search rankings and traffic results are not guaranteed.
What you will learn
A website can expose the same content through more than one address. Canonicalisation is the process of selecting a representative URL among duplicate or very similar versions. This lesson explains how to investigate those versions before adding a tag. You will learn to keep internal links, sitemap entries and canonical signals consistent, while recognising that a canonical hint does not force a search engine to select the URL you prefer.
1. List the versions and compare their content
Start with one real page and collect the addresses that appear to show it. Differences may involve parameters, hostnames or alternate paths. Open them and record their responses, final destinations and main contents. Do not label two pages duplicates merely because they discuss the same broad subject. A tutorial and a service offer can be genuinely different. The investigation should establish whether the visitor receives substantially the same page or a distinct answer before you decide on consolidation.
2. Choose a preferred URL for a reason
Select a stable address that represents the intended page and is consistent with the site structure. Consider existing public links, redirects and platform behaviour. Keep a record of why the URL was chosen. If a version should no longer exist as a separate accessible page, an appropriate redirect may be more suitable than leaving two copies available. Avoid choosing the homepage as the canonical for unrelated articles. The preferred destination should accurately represent the content of the versions being consolidated.
3. Implement the canonical signal accurately
For an HTML page, a canonical link can identify the preferred absolute URL in the document head. Check that the published address is correct, accessible and not accidentally pointing to a staging host. A shared template should produce the right value for each page rather than reuse the first article’s URL everywhere. Canonical signals can also be delivered through other supported methods in suitable cases. Use the official instructions for the format you are implementing instead of mixing incompatible examples.
4. Align the surrounding signals
Link internally to the preferred version and list that version in the sitemap. Review redirect behaviour and any alternate-language annotations that depend on the URL. Contradictory signals make the configuration harder to understand and maintain. Check several pages generated by the same template. A tag that is technically well formed but points to the wrong destination on hundreds of pages is still a serious implementation error. Keep intentionally separate content separate instead of using canonicalisation as a general substitute for editorial organisation.
5. Inspect the result and monitor changes
Use live checks and authorised Search Console inspection to compare your declared canonical with the version selected by Google when that information is available. The selected version may differ, so investigate the content and other signals rather than repeatedly editing the same tag without evidence. Reports may reflect earlier processing. Record the change date and retest after a meaningful interval. When a platform update or migration changes URLs, include canonical checks in the release process so old hostnames do not silently return.
Example to inspect and adapt
Read the explanation before using this example. Replace example URLs with your own intended public URLs; do not combine conflicting indexing instructions on one page.
<link rel="canonical" href="https://example.com/blog/seo-basics.html">Worked example
A fictional guide exists at /blog/seo-basics.html and at a tracking-parameter variant. Both show the same content. Choose the clean guide URL as the preferred version, link to it from the course index and include it in the sitemap. Test the rendered head and inspect the variants. The objective is consistent representation, not a promised ranking gain.
Your practical exercise
- Collect duplicate-looking versions of one page.
- Compare their content and response behaviour.
- Document a preferred URL and align links and sitemap entries.
- Inspect the published canonical and record the observed result.
Save the page URL, the observed problem, your proposed change, the publication date and the check you performed. Record real report data separately from examples or expectations.
Frequently asked questions
Is a canonical tag a guaranteed instruction?
No. It is a signal; search engines can select a different representative URL.
Can unrelated posts point their canonical to the homepage?
That does not correctly describe unrelated original content. Choose a representative URL that matches the page being consolidated.
Continue learning on this website
Explore our original practical guides below. Each page includes explanations, examples and checks you can apply to your own project.