Identify the actual duplicate or variant
Start with a concrete pair of URLs. A product category might be available both with and without a tracking parameter, while two distinct service pages describe different offers. Those situations should not automatically share the same canonical. Compare the main content and intended audience. If the pages answer different questions, forcing them to recommend one URL can misrepresent your structure. Understand the duplication before choosing a preferred destination.
Check the declared target and live behavior
Read the source declaration, then open its target. Confirm that the address is public, appropriate and consistent with the page's purpose. A development domain or an old hostname can remain accidentally after launch. Multiple declarations that disagree create a clearer technical problem than a simple absence. Inspect shared templates and plugins to find the source of conflicting signals before inserting another declaration.
Align related signals where practical
Once you choose the intended URL, use it consistently in internal links and sitemap entries. Redirect a genuinely retired variant when that matches the website's requirements. A self-referencing canonical can be useful, but it does not replace correct responses or a clear site structure. Do not use an indexing exclusion instruction merely to force canonical selection; exclusion and consolidation solve different problems and can interact in unwanted ways.
- Use the intended public hostname.
- Keep internal links aligned with the preferred URL.
- Check the sitemap and any redirects together.
Distinguish a declaration from Google's selection
A public checker can inspect available canonical evidence and conflicts. It cannot confirm which canonical Google selected for a URL. That requires separate evidence, such as a verified property's URL Inspection information. ColbySEO's Technical score includes conclusive canonical-conflict checks in its public sample; it does not assume that an absent tag means a failure or that a valid declaration proves the preferred page is indexed.
Verify a targeted correction
Suppose a new service page still recommends your staging domain. Fix the shared configuration, publish and check the live source for the intended production URL. Then inspect other pages using that configuration. Run the free website report to capture a fresh sample and save the PDF. If the intended behavior is unclear, request help with the two URLs and their business purposes before making a site-wide consolidation change.
Common questions
Does every page require a canonical tag?
No universal tag-presence rule establishes website health. Review duplication, platform behavior and consistent signals. Missing markup alone is different from a conflicting or clearly incorrect preferred-URL declaration.
Can I canonical every location page to my homepage?
Only consider consolidation when the content and intended purpose genuinely support it. Distinct useful location pages should not be treated as duplicates merely because they share a template.
Why might Google choose another canonical?
Canonical declarations are signals, and Google also considers other evidence. Review duplication, redirects, links and indexing information rather than assuming one tag can determine the outcome.