Canonical tags SEO work concerns the preferred URL for duplicate or substantially similar content. A rel=canonical link communicates a preferred version; it does not redirect the visitor, secure a private page or guarantee that a search engine will choose that version.
Start with the reason alternate URLs exist. Parameters, host variants, product options and duplicated routes need a coherent URL plan before a template can generate appropriate canonical output.
Compare similar-looking URL decisions
| Situation | Decision to investigate | Verification |
|---|---|---|
| Two substantially similar public versions | Choose a suitable preferred version and align canonical signals. | Inspect both content and the intended preferred destination. |
| An established page permanently moves | Use a relevant permanent redirect where appropriate. | Test old URL, final destination and internal references. |
| Two distinct useful page purposes | Keep their intent and content clearly differentiated. | Do not assign one canonical merely because both discuss a broad subject. |
Distinguish duplication from related content
Two pages about a broad subject are not automatically duplicates. A service page and an educational guide can answer different needs. Do not point one to the other simply because both mention SEO.
Inspect the actual content and purpose. If the pages genuinely serve different tasks, improve their distinction and linking. If one is an unnecessary duplicate, consider consolidation or another suitable URL-management approach.
Select an appropriate preferred destination
The intended canonical should be public, relevant and suitable for indexing. Check its response and content. Avoid canonicals that point to an error, redirect chain, blocked location or unrelated category.
The technical SEO checklist provides surrounding access checks. A syntactically valid tag can still communicate the wrong preference if the destination was chosen incorrectly.
Align the surrounding signals
Use the preferred address consistently in navigation and sitemap entries where appropriate. Review redirects between alternate hosts or protocols and avoid generating different canonicals from inconsistent request context.
Google's canonicalization guidance explains supported signals and their role. Keep implementation grounded in the actual URL relationships rather than treating one tag as a universal fix.
Check template-level mistakes
A shared template can accidentally point every article to the homepage or reuse one page's canonical across a category. Test multiple representative pages and compare the output with their intended final addresses.
In a Django application, use the existing URL architecture and trusted configuration. Do not accept an arbitrary unvalidated external URL from a request parameter as the canonical destination.
Handle parameters according to purpose
Some parameters change meaningful content; others represent tracking or sorting. Document the difference. A filter URL with a useful distinct purpose requires a different decision from a redundant tracking variant.
Avoid forcing all filtered content to one destination without reviewing the user experience and indexing strategy. A store's product, category and variant behaviour needs an explicit plan.
Know when a redirect is more appropriate
If a page has permanently moved and the old address should send visitors to the new one, a relevant permanent redirect may be appropriate. A canonical tag alone leaves the old URL accessible to the visitor.
Use the migration guide for a mapping and release process. Keep removed content honest: an unrelated homepage redirect is not automatically a useful replacement.
Inspect declared and selected versions separately
Search Console can show evidence about the declared canonical and Google's selected version. If they differ, investigate consistency, access and content rather than repeatedly resubmitting the same preference.
The Search Console guide explains diagnostic use. A local HTML check verifies your output, while selected-version evidence depends on the search system's processing.
Build an acceptance sample
Test a normal article, service page, parameter variant and relevant host alternative. Record the final response, visible content, canonical output and sitemap state. Retain the test cases when templates change.
An illustrative failure would be a service template reusing the SEO page's canonical for unrelated advertising pages. The fix should restore each appropriate preferred address and verify all affected templates. Discuss SEO services with the evidence if the preferred-version strategy needs clarification.