Duplicate, Google chose different canonical than user: how to fix it

Google groups pages it considers duplicates and picks one as canonical using several signals. Its documentation lists redirects, rel=canonical annotations, sitemap inclusion, internal and external links, HTTPS versus HTTP, and the cleanliness of the URL, among others. A rel=canonical tag is a strong signal but only one of them. When most other signals point to a different URL, Google follows the majority.

Each row shows a signal that can override your tag.

Sometimes the declared canonical is a mistake. A common one is a CMS or theme that sets every paginated page, filter view, or blog post's canonical to a category page or the homepage. Another is a JavaScript framework that renders one canonical in the initial HTML and another after hydration. If Google's choice is the URL you would actually want in search, fix the tag to match rather than fighting it.

In URL Inspection, note the user-declared canonical and the Google-selected canonical. Fetch both URLs and compare status codes, robots directives, and content. View the raw page source of each, not only the browser view, and confirm the canonical tag in the server response. Search your site's internal links and sitemap for each variant. Our free canonical tag checker reads the live tag and flags redirects or noindex on the target.

Request indexing for the declared canonical, keep signals consistent, and give Google time to recrawl both URLs. The status often clears within a few weeks on well-linked pages. If it persists after every signal agrees and the pages are genuinely duplicates, consider redirecting the duplicate permanently, which is a stronger signal than any tag. SerionFlow is the wrong tool for resolving canonical conflicts on your existing site; it keeps its own pages self-canonical, but your internal links, redirects, and sitemaps are yours to align.