{"id":252,"date":"2026-07-11T21:55:03","date_gmt":"2026-07-11T12:55:03","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/google-chose-different-canonical\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"google-chose-different-canonical","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/google-chose-different-canonical\/","title":{"rendered":"Duplicate, Google chose different canonical than user"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">What does this status mean?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">&#8216;Duplicate, Google chose different canonical than user&#8217; means Google picked and indexed a different URL as canonical instead of the URL the site owner designated as the representative. It appears in Google Search Console&#8217;s Page indexing report, and it is not an indexing failure. Google&#8217;s official help describes this status as &#8220;This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Put simply, the site owner declared &#8220;this URL is the representative&#8221; with a <a href=\"\/en\/seo-glossary\/canonical-tag\/\">canonical tag<\/a> or similar, but Google picked and indexed a different URL as the representative instead. Google&#8217;s developer documentation defines canonicalization as the process of selecting one URL to represent the content among duplicate pages, and explains that only that one representative version is indexed. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Canonical is a signal, not a command<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The key to understanding this status is Google&#8217;s official position that a canonical declaration is not a binding command. Google&#8217;s developer documentation ranks canonicalization methods by signal strength: redirects and rel=&#8221;canonical&#8221; link annotations are a &#8220;strong signal,&#8221; sitemap inclusion is a &#8220;weak signal,&#8221; and none of these methods guarantees the outcome. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google looks at more than one or two signals. On Google&#8217;s official podcast in 2024, Allan Scott of Google&#8217;s Search team put the number of canonical selection signals at &#8220;somewhere in the neighborhood of 40.&#8221; Ahrefs, summarizing this, stresses that rel=&#8221;canonical&#8221; is just one of those 40 or so signals. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/canonicalization\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (measured)<\/a> In other words, a single tag does not settle the result; the sum of all signals decides the canonical.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google&#8217;s official canonicalization troubleshooting document also says that even if you clearly specify a canonical page, Google may choose a different page for various reasons, such as content quality. It explains that Google weighs factors such as whether the page is served over HTTPS, redirects, sitemap inclusion and rel=&#8221;canonical&#8221; annotations when deciding the canonical. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization-troubleshooting?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Is it a problem or not?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This status is not an indexing failure. The page&#8217;s content is already indexed through the canonical URL Google chose. What matters is &#8220;which URL appears as the representative in search results.&#8221;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>When no action is needed<\/strong>: if the URL Google picked is essentially the same or a better version (the HTTPS version instead of HTTP, or a clean URL without tracking parameters), you can leave it. Google&#8217;s official documentation explains that even if the site owner doesn&#8217;t specify a canonical, Google picks out the objectively best version on its own. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li><strong>When it needs checking<\/strong>: if Google chose a completely different page, a different domain (content syndication or unauthorized copying), or an unwanted URL with parameters as canonical, it means your site&#8217;s signals conflict with each other, so the actions below are needed.<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison with similar statuses<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Report status<\/th><th>Canonical declared<\/th><th>Google&#8217;s decision<\/th><th>Nature<\/th><\/tr><\/thead><tbody><tr><td>Alternate page with proper canonical tag<\/td><td>Yes<\/td><td>Follows the declared canonical as is<\/td><td>Normal behavior, no action needed<\/td><\/tr><tr><td><a href=\"\/en\/seo-glossary\/duplicate-without-canonical\/\">Duplicate without user-selected canonical<\/a><\/td><td>No<\/td><td>Google chooses the canonical itself<\/td><td>Declaring a canonical is recommended<\/td><\/tr><tr><td>Duplicate, Google chose different canonical than user<\/td><td>Yes<\/td><td>Chooses a URL different from the declared one<\/td><td>Check whether signals are consistent<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Why Google chooses a different canonical<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Conflicting signals<\/strong>: the canonical points to A, but internal links, the sitemap or redirects point to B. Ahrefs explains that internal links are also a canonicalization signal for Google, and that only canonical URLs should be listed in the sitemap. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/canonical-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/li><li><strong>Content quality judgment<\/strong>: Google&#8217;s official documentation says that even when you specify a canonical, Google may choose a different page for reasons such as content quality. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization-troubleshooting?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li><strong>Mixed protocols<\/strong>: Google says that for the same page, it prefers the HTTPS page over HTTP as canonical. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li><strong>Canonicals on pages that aren&#8217;t duplicates<\/strong>: by the principles of Google&#8217;s canonicalization, canonicals are meant to be set only between duplicate pages whose content is actually similar. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Real-world tests by search consultant Glenn Gabe also confirmed that when you set a canonical between URLs with different content, Google ignores it and indexes each one separately. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.gsqi.com\/marketing-blog\/google-ignore-rel-canonical-different-content\/\" target=\"_blank\" rel=\"noopener\">Glenn Gabe (measured)<\/a><\/li><li><strong>Incorrect implementation<\/strong>: common mistakes Ahrefs points out include the canonical target URL being noindexed, returning a 4XX or blocked by robots.txt; multiple rel=&#8221;canonical&#8221; tags on one page; and the tag sitting in the body instead of the head. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/canonical-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to check and fix it<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: check Google&#8217;s choice with URL Inspection<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The next step Google&#8217;s official help recommends is to inspect the URL with the <a href=\"\/en\/seo-glossary\/url-inspection-tool\/\">URL Inspection tool<\/a>, check the &#8216;User-declared canonical&#8217; and &#8216;Google-selected canonical&#8217; in the &#8216;Page indexing&#8217; section, then open both pages in a browser and compare them. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a> Note that the official URL Inspection tool documentation says the live test cannot predict whether the tested version will be treated as canonical, and that the Google-selected canonical is only shown in the indexed data. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289?hl=ko\" target=\"_blank\" rel=\"noopener\">GSC Help Center<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: align your signals in one direction<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the URL Google chose is appropriate, accepting it as the representative and pointing your canonical to it is also a valid answer. If instead you want to stick with the URL you originally specified, align every signal on the site so they all point to that same URL.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Make the rel=&#8221;canonical&#8221; on every duplicate page point to the same representative URL (one per page, inside the head).<\/li><li>List only the representative URL in the sitemap. Google&#8217;s documentation explains that every page listed in a sitemap is suggested as a canonical candidate. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Point internal links to the representative URL too.<\/li><li>Connect duplicate URLs you want to remove to the representative URL with a 301 redirect. Per Google&#8217;s documentation, redirects are a strong signal. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Serve the representative URL over HTTPS and keep it indexable with a 200 response (not blocked, no noindex).<\/li><\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;link rel=\"canonical\" href=\"https:\/\/example.com\/sample-page\/\"&gt;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">After you align the signals, Google&#8217;s decision updates when it recrawls. It is natural for the report to show the old status until then, so just watch and wait for the numbers to change.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203?hl=ko\" target=\"_blank\" rel=\"noopener\">Page indexing report &#8211; Google Search Console Help<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization?hl=ko\" target=\"_blank\" rel=\"noopener\">What is URL canonicalization &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls?hl=ko\" target=\"_blank\" rel=\"noopener\">How to specify a canonical URL with rel=&#8221;canonical&#8221; and other methods &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/canonicalization-troubleshooting?hl=ko\" target=\"_blank\" rel=\"noopener\">Fix canonicalization issues &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289?hl=ko\" target=\"_blank\" rel=\"noopener\">URL Inspection tool &#8211; Google Search Console Help<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/canonical-tags\/\" target=\"_blank\" rel=\"noopener\">Canonical Tags Explained: Why They Matter For SEO &#8211; Ahrefs<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/canonicalization\/\" target=\"_blank\" rel=\"noopener\">Google Uses ~40 Canonicalization Signals &#8211; Ahrefs<\/a><\/li><li><a href=\"https:\/\/www.gsqi.com\/marketing-blog\/google-ignore-rel-canonical-different-content\/\" target=\"_blank\" rel=\"noopener\">Google&#8217;s Algorithms Can Ignore Rel Canonical When URLs Contain Different Content &#8211; GSQI (Glenn Gabe)<\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>&#8216;Duplicate, Google chose different canonical than user&#8217; means the site owner specified a representative URL with rel=canonical or similar, but Google judged a different URL to be a better canonical and indexed that one. According to Google&#8217;s official documentation, a canonical declaration is a signal, not a binding command, so this status is not an indexing failure. If the URL Google chose is fine, no action is needed; if you want a different URL, align your redirect, sitemap and internal link signals in one direction.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-252","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-search-console"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/252","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/252\/revisions"}],"predecessor-version":[{"id":2337,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/252\/revisions\/2337"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=252"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}