How would I investigate a Canonicalisation Issue?

[Guestwriting]

My basic workflow:

Step 1: Identify the affected URLs.

Step 2: Inspect their declared canonical tags.

Step 3: Check the canonical URL selected by Google in URL Inspection.

Step 4: Compare content, redirects, internal links and sitemap entries.

Step 5: Correct inconsistencies where necessary and monitor the affected pages.

A canonical tag is a signal, not an absolute command. Google may select a different canonical URL.

The important part is making the site's preferred URL clear and consistent across its signals.

 

[BlackShield]

My basic workflow:

Step 1: Identify the affected URLs.

Step 2: Inspect their declared canonical tags.

Step 3: Check the canonical URL selected by Google in URL Inspection.

Step 4: Compare content, redirects, internal links and sitemap entries.

Step 5: Correct inconsistencies where necessary and monitor the affected pages.

A canonical tag is a signal, not an absolute command. Google may select a different canonical URL.

The important part is making the site's preferred URL clear and consistent across its signals.

The workflow which you are doing is good. also i check whether internal links and sitemap URLs point to the preferred canonical version. If those signals conflict, Google may choose a different URL even when the canonical tag is correct.

 

[onurbaba78]

I'd also check whether the duplicate pages have different internal links or redirect behavior. Even with a canonical tag in place, mixed signals can lead Google to choose a different URL.

 

[rudolp]

I agree, checking all the signals together is important. Sometimes the canonical tag looks fine, but internal links or redirects point to a different URL. Fixing those inconsistencies can make things much clearer for Google.

 

[BinarySeo]

tbh before the whole 5 step thing just check if www/non-www and http/https all 301 to one version. half the canonical threads on here end up being that

 

[Sarah Mathews]

My basic workflow:

Step 1: Identify the affected URLs.

Step 2: Inspect their declared canonical tags.

Step 3: Check the canonical URL selected by Google in URL Inspection.

Step 4: Compare content, redirects, internal links and sitemap entries.

Step 5: Correct inconsistencies where necessary and monitor the affected pages.

A canonical tag is a signal, not an absolute command. Google may select a different canonical URL.

The important part is making the site's preferred URL clear and consistent across its signals.

never change canonical tags blindly. first understand why google selected a different canonical url, identify conflicting signals, and then make the necessary corrections.

 

[Guestwriting]

The workflow which you are doing is good. also i check whether internal links and sitemap URLs point to the preferred canonical version. If those signals conflict, Google may choose a different URL even when the canonical tag is correct.

Exactly! Internal links and sitemap URLs should consistently point to the preferred canonical version. Even if the canonical tag is correct, conflicting signals can confuse Google.

I'd also check whether the duplicate pages have different internal links or redirect behavior. Even with a canonical tag in place, mixed signals can lead Google to choose a different URL.

Agreed! Redirect behavior and internal linking are important checks. Sometimes the issue isn't the canonical tag itself but the conflicting signals across duplicate URLs.

I agree, checking all the signals together is important. Sometimes the canonical tag looks fine, but internal links or redirects point to a different URL. Fixing those inconsistencies can make things much clearer for Google.

Google looks at multiple signals when selecting a canonical URL. Keeping canonical tags, internal links, redirects, and sitemaps consistent is the right approach.

tbh before the whole 5 step thing just check if www/non-www and http/https all 301 to one version. half the canonical threads on here end up being that

Good point! Checking HTTP/HTTPS and www/non-www redirects should definitely be part of the initial checks. If these versions aren't consolidated properly, they can create unnecessary URL variations and canonicalization issues.

never change canonical tags blindly. first understand why google selected a different canonical url, identify conflicting signals, and then make the necessary corrections.

Well said! Changing canonical tags without understanding the root cause can make things worse. It's better to check Google's selected canonical, compare all the signals, and then make targeted corrections.

 

[Muhammad Shakeel]

I agree with the point several people made here about conflicting signals. A canonical tag on its own does not settle it if internal links, redirects, and the sitemap point somewhere else.

One check I would add early is the version of the page that actually gets linked from the main navigation and from recent posts. Those links often keep an older URL alive long after the canonical tag was fixed, and Google keeps seeing that version as the preferred one.

I would also look at the Search Console report for the duplicate pages before changing anything, so the fix matches what Google actually selected rather than what the tag says. Once the signals agree, I usually wait and recheck the same URLs instead of making more changes right away, because a second round of edits can hide whether the first fix worked.

 

[SEOMonster01]

One step I would add before fixing individual URLs is to group the duplicates by their cause, because the same symptom can come from very different problems. Sorting, filtering, tracking parameters, pagination, trailing slashes, and a separate category version of a product page can all create near-duplicates, and each group usually needs a different fix rather than a new canonical tag on every page.

I would also check for more than one canonical tag on the same page, which can happen when a theme, a plugin, and a manual setting each add one. In that case, Google may not use the version you intended. It is also worth checking whether the declared canonical points to a page that redirects, returns an error, or is itself set to noindex, because a canonical to an unusable URL weakens the signal.

Finally, after the signals are aligned, I would judge the fix by the URL Google actually selects and by whether impressions move to the preferred version, rather than by whether the tag looks correct in the page source. If the selected canonical stays wrong, that usually means another conflicting signal is still present, such as an old internal link, a sitemap entry, or a parameter version that is still being linked.

 

[maxobom]

One thing i would also check is whether the canonical URL returns a 200 status and is indexable. Make sure it is not blocked by robots.txt or set to noindex. Also check the page source and rendered HTML to see if there are multiple canonical tags, sometimes themes or SEO plugins can add an extra one. I usually crawl the affected URLs in Screaming Frog to find these issues in bulk.

 

[SEO Sparton]

My basic workflow:

Step 1: Identify the affected URLs.

Step 2: Inspect their declared canonical tags.

Step 3: Check the canonical URL selected by Google in URL Inspection.

Step 4: Compare content, redirects, internal links and sitemap entries.

Step 5: Correct inconsistencies where necessary and monitor the affected pages.

A canonical tag is a signal, not an absolute command. Google may select a different canonical URL.

The important part is making the site's preferred URL clear and consistent across its signals.

Great explanation! Canonical tags are just one part of the equation; consistent canonical tags in conjunction with redirects, internal linking, and site maps are equally important.

I always consider Google's choice of canonical as the ultimate test.

 

[LokiProxy]

Don't just focus on tags alone, it's when all signals work together in sync that Google is more likely to pick the canonical URL you want.

 

[nguyenvannhung]

One reporting trap to add: the live URL Inspection test cannot tell you which canonical Google selected. That information comes from the indexed result.

Check the last crawl date there against the date you deployed the fix. If Google hasn't recrawled yet, an old selected canonical isn't evidence that the new configuration failed. After correcting the signals, request recrawling where appropriate and compare the indexed result once it's been processed. I'd save a small before/after table of affected URL, declared canonical, selected canonical and last crawl date so repeated changes don't obscure what actually happened.

 

[Guestwriting]

I agree with the point several people made here about conflicting signals. A canonical tag on its own does not settle it if internal links, redirects, and the sitemap point somewhere else.

One check I would add early is the version of the page that actually gets linked from the main navigation and from recent posts. Those links often keep an older URL alive long after the canonical tag was fixed, and Google keeps seeing that version as the preferred one.

I would also look at the Search Console report for the duplicate pages before changing anything, so the fix matches what Google actually selected rather than what the tag says. Once the signals agree, I usually wait and recheck the same URLs instead of making more changes right away, because a second round of edits can hide whether the first fix worked.

Good point. I've also seen situations where the canonical tag is corrected but old URLs are still being linked internally through navigation, blog posts or category pages. These small inconsistencies can keep sending mixed signals to Google. That's why I prefer checking internal links along with the canonical report before making changes.

One step I would add before fixing individual URLs is to group the duplicates by their cause, because the same symptom can come from very different problems. Sorting, filtering, tracking parameters, pagination, trailing slashes, and a separate category version of a product page can all create near-duplicates, and each group usually needs a different fix rather than a new canonical tag on every page.

I would also check for more than one canonical tag on the same page, which can happen when a theme, a plugin, and a manual setting each add one. In that case, Google may not use the version you intended. It is also worth checking whether the declared canonical points to a page that redirects, returns an error, or is itself set to noindex, because a canonical to an unusable URL weakens the signal.

Finally, after the signals are aligned, I would judge the fix by the URL Google actually selects and by whether impressions move to the preferred version, rather than by whether the tag looks correct in the page source. If the selected canonical stays wrong, that usually means another conflicting signal is still present, such as an old internal link, a sitemap entry, or a parameter version that is still being linked.

Absolutely. Grouping URLs by their duplication patterns makes the whole process much easier. There is no point applying the same solution to every duplicate URL because parameter-based URLs, pagination and actual content duplication are different issues. I would also add a crawl to identify multiple canonical tags, especially on sites using several SEO plugins or custom themes.

I agree. It’s important to check all signals together. A canonical tag might look correct, but conflicting internal links or redirects can send mixed signals to Google. Keeping everything consistent makes it easier for Google to understand the preferred URL.

Exactly. The problem is that sometimes everything looks correct in the page source, but Google still selects a different URL. In my experience, checking internal links, redirects and sitemap references together usually helps identify where the conflicting signal is coming from.

One thing i would also check is whether the canonical URL returns a 200 status and is indexable. Make sure it is not blocked by robots.txt or set to noindex. Also check the page source and rendered HTML to see if there are multiple canonical tags, sometimes themes or SEO plugins can add an extra one. I usually crawl the affected URLs in Screaming Frog to find these issues in bulk.

Yes, Screaming Frog is quite useful for this, especially when dealing with hundreds or thousands of URLs. Manually checking every page is not practical. I usually crawl the affected URLs and review canonical status codes, indexability, redirect targets and duplicate canonical tags in bulk. It saves a lot of time during technical audits.

Great explanation! Canonical tags are just one part of the equation; consistent canonical tags in conjunction with redirects, internal linking, and site maps are equally important.

I always consider Google's choice of canonical as the ultimate test.

Agreed. At the end of the day, what Google actually selects matters more than what we declare in the canonical tag. I normally compare the declared and Google-selected canonical in URL Inspection and monitor the affected URLs after making corrections. That gives a much clearer picture of whether the changes are working.

Don't just focus on tags alone, it's when all signals work together in sync that Google is more likely to pick the canonical URL you want.

Exactly! Canonicalization is not just about adding one tag to the page. Google looks at the overall picture, including internal links, redirects, sitemap entries and other signals. Keeping everything aligned is what really matters.

One reporting trap to add: the live URL Inspection test cannot tell you which canonical Google selected. That information comes from the indexed result.

Check the last crawl date there against the date you deployed the fix. If Google hasn't recrawled yet, an old selected canonical isn't evidence that the new configuration failed. After correcting the signals, request recrawling where appropriate and compare the indexed result once it's been processed. I'd save a small before/after table of affected URL, declared canonical, selected canonical and last crawl date so repeated changes don't obscure what actually happened.

Very good point. This is something people often overlook when checking URL Inspection. The live test and Google's indexed canonical are two different things. If Google hasn't crawled the page again after the changes, we cannot immediately conclude that the fix didn't work. Checking the last crawl date is important here. I also like your suggestion of maintaining a before-and-after report because it makes tracking these changes much easier.

 

[Muhammad Shakeel]

Good point. I've also seen situations where the canonical tag is corrected but old URLs are still being linked internally through navigation, blog posts or category pages. These small inconsistencies can keep sending mixed signals to Google. That's why I prefer checking internal links along with the canonical report before making changes.




Absolutely. Grouping URLs by their duplication patterns makes the whole process much easier. There is no point applying the same solution to every duplicate URL because parameter-based URLs, pagination and actual content duplication are different issues. I would also add a crawl to identify multiple canonical tags, especially on sites using several SEO plugins or custom themes.




Exactly. The problem is that sometimes everything looks correct in the page source, but Google still selects a different URL. In my experience, checking internal links, redirects and sitemap references together usually helps identify where the conflicting signal is coming from.



Yes, Screaming Frog is quite useful for this, especially when dealing with hundreds or thousands of URLs. Manually checking every page is not practical. I usually crawl the affected URLs and review canonical status codes, indexability, redirect targets and duplicate canonical tags in bulk. It saves a lot of time during technical audits.



Agreed. At the end of the day, what Google actually selects matters more than what we declare in the canonical tag. I normally compare the declared and Google-selected canonical in URL Inspection and monitor the affected URLs after making corrections. That gives a much clearer picture of whether the changes are working.



Exactly! Canonicalization is not just about adding one tag to the page. Google looks at the overall picture, including internal links, redirects, sitemap entries and other signals. Keeping everything aligned is what really matters.




Very good point. This is something people often overlook when checking URL Inspection. The live test and Google's indexed canonical are two different things. If Google hasn't crawled the page again after the changes, we cannot immediately conclude that the fix didn't work. Checking the last crawl date is important here. I also like your suggestion of maintaining a before-and-after report because it makes tracking these changes much easier.

Thanks for adding that. Checking internal links alongside the canonical report makes sense, because fixing the tag alone does not help if the site keeps pointing to the old URLs.