When Google picks a different canonical, inspect both URLs and decide whether they really serve the same purpose. If they do, make your internal links, redirects, sitemap and canonical tags agree on the preferred address. If each page has a different job, investigate why Google may be seeing them as duplicates.
A canonical is the representative address chosen from a group of duplicate or very similar pages. You can tell Google which URL you prefer. Google can still choose another.
Which URLs are you comparing?
In Search Console URL Inspection, inspect the affected URL and record the user-declared and Google-selected canonicals if shown. Then inspect the selected URL. The indexed report reflects Google's recorded state. The live test checks current conditions and can't predict which canonical Google will select.
Open both pages as a visitor. Compare the main copy, headings and purpose. A print version and a regular guide may serve the same need. A feature overview and a troubleshooting article should usually have different material that helps with different tasks.
What if the signals disagree?
Here's a fictional example. A docs team wants /help/export to be primary. Its template points the canonical there, but its help navigation and sitemap still use /guides/export. The two pages repeat the same instructions.
The team can first decide whether the older address needs to stay accessible. If the old page has permanently moved, use a direct permanent redirect to the equivalent new page. If both versions must remain accessible, use a canonical annotation on the duplicate. In either case, update links and the sitemap to favor the intended URL. Google's canonicalization guidance explains how these signals work together.
What if the pages are supposed to be different?
Check whether both URLs return the right main content when loaded directly. A template bug can serve the same body at different addresses. Also check for copied canonical tags and redirects that send visitors to the wrong page. If the templates work, make each page answer its own question with content a reader can use.
Record the before and after signals. Verify the public page and revisit the indexed report after recrawling. Avoid judging success from a request for indexing alone. If the content disappears during rendering, put that finding in your site audit action list with a reproducible URL and expected heading.
What should go in the canonical mismatch ticket?
Give the person who can change the site a record they can reproduce. A screenshot of the warning is a start. Add the pair of URLs and the reason you want one to be representative.
- Expected: the preferred URL and the audience task it serves.
- Observed: the selected URL, the report date and the declarations visible on both pages.
- Conflicts: sample navigation links, sitemap entries and redirect hops that favor a different URL.
- Acceptance: exactly which URL each surface should point to, plus a date to check the indexed report again.
Check the public output as well as the CMS field. A template can ignore the stored canonical value or output a second declaration. If the old address stays available for a real reason, verify it still works while its canonical annotation points to the representative page. If your evidence suggests a template issue, sample another URL on the same template before rolling out a broad change.
Use the smallest fix that makes the signals consistent. Changing a sitewide template can affect pages that were already working, while correcting only the sitemap won't fix contradictory navigation. Keep a before-and-after example to make the next review easier.
