{"id":16568,"date":"2026-09-02T11:36:54","date_gmt":"2026-09-02T08:36:54","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/"},"modified":"2026-09-06T00:50:52","modified_gmt":"2026-09-05T21:50:52","slug":"specify-canonical","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/","title":{"rendered":"How to specify a canonical URL with rel=&#8221;canonical&#8221; and other methods"},"content":{"rendered":"<p>\n  To specify a <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/canonicalization-basics\/\">canonical URL<\/a> for<br \/>\n  duplicate or very similar pages to Google Search, you can indicate your preference using a<br \/>\n  number of methods. These are, in order of how strongly they can influence canonicalization:\n<\/p>\n<ul>\n<li>\n    <a href=\"#redirects-method\"><b>Redirects<\/b><\/a>: A strong signal that the target<br \/>\n    of the redirect should become canonical.\n  <\/li>\n<li>\n    <a href=\"#rel-canonical-link-method\"><b><code>rel=\"canonical\"<\/code> <code>link<\/code> annotations<\/b><\/a>:<br \/>\n    A strong signal that the specified URL should become canonical.\n  <\/li>\n<li>\n    <a href=\"#sitemap-method\"><b>Sitemap inclusion<\/b><\/a>: A weak signal that helps<br \/>\n    the URLs that are included in a sitemap become canonical.\n  <\/li>\n<\/ul>\n<p>\n  Keep in mind that these methods can stack and thus become more effective when combined.<br \/>\n  This means that when you use two or more of the methods, that will increase the chance<br \/>\n  of your preferred canonical URL appearing in search results.\n<\/p>\n<p>\n  While we encourage you to use these methods, none of them are required; your<br \/>\n  site will likely do just fine without specifying a canonical preference. That&#8217;s because<br \/>\n  if you don&#8217;t specify a canonical URL,<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/canonicalization-basics\/#canonical-how\">Google will identify which version of the URL is objectively the best version to show to users in Search<\/a>.\n<\/p>\n<aside class=\"key-point\">\n  <b>If you use a CMS, such as WordPress, Wix, or Blogger<\/b>, you might not be able to<br \/>\n  edit your HTML directly. Instead, your CMS might have a search engine settings page<br \/>\n  or some other mechanism to tell search engines about the canonical URL. Search for<br \/>\n  instructions about modifying the <code>&lt;head&gt;<\/code> of your page on your CMS<br \/>\n  (for example, search for &#8220;wordpress set the canonical element&#8221;).<br \/>\n<\/aside>\n<h2 id=\"reasons-to-specify-a-canonical-url\" tabindex=\"-1\">Reasons to specify a canonical URL<\/h2>\n<div class=\"video-wrapper\">\n<\/div>\n<p>\n  While it&#8217;s generally not critical to specify a canonical preference for your URLs, there<br \/>\n  are a number of reasons why you would want to explicitly tell Google about a canonical<br \/>\n  page in a set of duplicate or similar pages:\n<\/p>\n<ul>\n<li>\n    <b>To specify which URL that you want people to see in search results.<\/b><br \/>\n    You might prefer people to reach your green dress product page through<br \/>\n    <code>https:\/\/www.example.com\/dresses\/green\/green-dress.html<\/code> rather than<br \/>\n    <code>https:\/\/example.com\/dresses\/cocktail?gclid=ABCD<\/code>.\n  <\/li>\n<li>\n    <b>To consolidate signals for similar or duplicate pages.<\/b> It helps<br \/>\n    search engines to be able to consolidate the signals they have for the individual<br \/>\n    URLs (such as links to them) into a single, preferred URL. This means that signals<br \/>\n    from other sites to <code>https:\/\/example.com\/dresses\/cocktail?gclid=ABCD<\/code> get<br \/>\n    consolidated with links to<br \/>\n    <code>https:\/\/www.example.com\/dresses\/green\/green-dress.html<\/code> if the latter<br \/>\n    becomes canonical.\n  <\/li>\n<li>\n    <b>To simplify tracking metrics for a piece of content.<\/b> With a variety<br \/>\n    of URLs, it can be more challenging for you to get consolidated metrics for a<br \/>\n    specific piece of content.\n  <\/li>\n<li>\n    <b>To avoid spending crawling time on duplicate pages.<\/b> You may want<br \/>\n    Googlebot to get the most out of your site, so it&#8217;s better for it to spend time<br \/>\n    crawling new (or updated) pages on your site, rather than crawling duplicate<br \/>\n    versions of the same content.\n  <\/li>\n<\/ul>\n<h2 id=\"best-practices\" tabindex=\"-1\">Best practices<\/h2>\n<p>For all canonicalization methods, follow these best practices:<\/p>\n<ul>\n<li>\n    <b>Don&#8217;t<\/b> use the robots.txt file for canonicalization purposes. Google may still index URLs<br \/>\n    that are disallowed in robots.txt without their content.\n  <\/li>\n<li>\n    <b>Don&#8217;t<\/b> use the URL removal tool for canonicalization. It hides<br \/>\n    <em>all<\/em> versions of a URL from Search.\n  <\/li>\n<li>\n    <b>Don&#8217;t<\/b> specify different URLs as canonical for the same page using<br \/>\n    different canonicalization techniques (for example, don&#8217;t specify one URL in a<br \/>\n    sitemap, but a different URL for that same page using <code>rel=\"canonical\"<\/code>).\n  <\/li>\n<li>\n    <b>Don&#8217;t<\/b> specify a URL fragment as canonical, as<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/url-structure\/#fragments\">Google generally doesn&#8217;t support URL fragments<\/a>.\n  <\/li>\n<li>\n    <b>Do<\/b> include a <code>rel=\"canonical\"<\/code> link on the canonical page<br \/>\n    itself (also known as a self-referential canonical).\n  <\/li>\n<li>\n    <b>We don&#8217;t recommend<\/b> using<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/block-search-indexing-with-noindex\/\"><code>noindex<\/code><\/a> to prevent<br \/>\n    selection of a canonical page within a single site, because it will completely block the page<br \/>\n    from Search. <code>rel=\"canonical\"<\/code> <code>link<\/code> annotations are the preferred<br \/>\n    solution.\n  <\/li>\n<li>\n    If you&#8217;re using<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>hreflang<\/code> elements<\/a>,<br \/>\n    make sure to specify a canonical page in the same language, or the best possible<br \/>\n    substitute language if a canonical page doesn&#8217;t exist for the same language.\n  <\/li>\n<li>\n    When linking within your site, link to the canonical URL rather than a duplicate URL.<br \/>\n    Linking consistently to the URL that you consider to be canonical helps Google<br \/>\n    understand your preference.\n  <\/li>\n<li>\n    If you&#8217;re using client-side rendering with JavaScript, it&#8217;s important to make sure that the<br \/>\n    information about the canonical URL is as clear as possible. The best way to do this is to<br \/>\n    specify the canonical URL in the HTML source code and make sure that JavaScript doesn&#8217;t change<br \/>\n    the canonical link element. If you can&#8217;t set the canonical URL in the HTML source code, leave it<br \/>\n    out and only set it with JavaScript. This ensures that the information about the canonical URL<br \/>\n    is as clear as possible.\n  <\/li>\n<\/ul>\n<h2 id=\"comparison-of-canonicalization-methods\" tabindex=\"-1\">Comparison of canonicalization methods<\/h2>\n<p>\n  The following table compares the different canonicalization methods, highlighting their<br \/>\n  strengths and weaknesses when it comes to maintenance and efficacy in different scenarios.\n<\/p>\n<table class=\"responsive\">\n<tr>\n<th colspan=\"2\">Method and description<\/th>\n<\/tr>\n<tr>\n<td>\n      <a href=\"#rel-canonical-link-method\"><code>rel=\"canonical\" link<\/code> element<\/a>\n    <\/td>\n<td>\n<p>\n        Add a <code>&lt;link&gt;<\/code> element in the code for all duplicate pages,<br \/>\n        pointing to the canonical page.\n      <\/p>\n<table>\n<tr>\n<td  width=\"50%\">\n            <span class=\"compare-yes\" aria-hidden=\"true\"><\/span><b>Pros:<\/b><\/p>\n<ul>\n<li>Can map an infinite number of duplicate pages.<\/li>\n<\/ul>\n<\/td>\n<td width=\"50%\">\n            <span class=\"compare-no\" aria-hidden=\"true\"><\/span><b>Cons:<\/b><\/p>\n<ul>\n<li>\n                Can be complex to maintain the mapping on larger sites, or sites where<br \/>\n                the URLs change often.\n              <\/li>\n<li>\n                Only works for HTML pages, not for files such as PDF. In such cases,<br \/>\n                you can use the <code>rel=\"canonical\"<\/code> HTTP header.\n              <\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/table>\n<\/td>\n<\/tr>\n<tr>\n<td>\n      <a href=\"#rel-canonical-header-method\"><code>rel=\"canonical\"<\/code> HTTP header<\/a>\n    <\/td>\n<td>\n<p>Send a <code>rel=\"canonical\"<\/code> header in your page response.<\/p>\n<table>\n<tr>\n<td width=\"50%\">\n            <span class=\"compare-yes\" aria-hidden=\"true\"><\/span><b>Pros:<\/b><\/p>\n<ul>\n<li>Doesn&#8217;t increase page size.<\/li>\n<li>Can map an infinite number of duplicate pages.<\/li>\n<\/ul>\n<\/td>\n<td width=\"50%\">\n            <span class=\"compare-no\" aria-hidden=\"true\"><\/span><b>Cons:<\/b><\/p>\n<ul>\n<li>\n                Can be complex to maintain the mapping on larger sites, or sites where<br \/>\n                the URLs change often.\n              <\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/table>\n<\/td>\n<\/tr>\n<tr>\n<td><a href=\"#sitemap-method\">Sitemap<\/a><\/td>\n<td>\n<p>Specify your canonical pages in a sitemap.<\/p>\n<table>\n<tr>\n<td width=\"50%\">\n<p><span class=\"compare-yes\" aria-hidden=\"true\"><\/span><b>Pros:<\/b><\/p>\n<ul>\n<li>Simple to implement and maintain, especially on large sites.<\/li>\n<\/ul>\n<\/td>\n<td width=\"50%\">\n<p><span class=\"compare-no\" aria-hidden=\"true\"><\/span><b>Cons:<\/b><\/p>\n<ul>\n<li>\n                Google must still determine the associated duplicate for any<br \/>\n                canonicals that you declare in the sitemap.\n              <\/li>\n<li>\n                Less powerful signal to Google than the <code>rel=\"canonical\"<\/code><br \/>\n                mapping technique.\n              <\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/table>\n<\/td>\n<\/tr>\n<tr>\n<td><a href=\"#redirects-method\">Redirects<\/a><\/td>\n<td>\n      Use permanent redirects to tell Google that a redirected URL is a worse version than the URL<br \/>\n      it redirects to. Use this only when deprecating a duplicate page.\n    <\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/about-amp-on-google-search\/\">AMP variant<\/a><\/td>\n<td>\n      If one of your variants is an AMP page, follow the AMP guidelines to<br \/>\n      indicate the canonical page and AMP variant.\n    <\/td>\n<\/tr>\n<\/table>\n<h2 id=\"use-rel=canonical-link-annotations\" data-text='Use rel=\"canonical\" link annotations' tabindex=\"-1\">Use <code>rel=\"canonical\"<\/code> <code>link<\/code> annotations<\/h2>\n<p>\n  Google supports explicit <code>rel<\/code> <span>canonical<\/span> <code>link<\/code><br \/>\n  annotations as described in<br \/>\n  <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc6596\" class=\"external-link\">RFC 6596<\/a>.<br \/>\n  <code>rel=\"canonical\"<\/code> annotations that suggest alternate versions of a page are ignored;<br \/>\n  specifically, <code>rel=\"canonical\"<\/code> annotations with <code>hreflang<\/code>,<br \/>\n  <code>lang<\/code>, <code>media<\/code>, and <code>type<\/code> attributes are not used for<br \/>\n  canonicalization. Instead, use the appropriate <code>link<\/code> annotations to specify alternate<br \/>\n  versions of a page; for example, <code>link<\/code> <code>rel=\"alternate\"<\/code><br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>hreflang<\/code><\/a> for<br \/>\n  language and country annotations.\n<\/p>\n<p>\n  You can provide the <code>rel=\"canonical\"<\/code> <code>link<\/code> annotations in two ways:\n<\/p>\n<ul>\n<li>\n    <a href=\"#rel-canonical-link-method\">The <code>rel=\"canonical\"<\/code> <code>link<\/code> element in the HTML<\/a>\n  <\/li>\n<li>\n    <a href=\"#rel-canonical-header-method\">The <code>rel=\"canonical\"<\/code> <code>link<\/code> HTTP header<\/a>\n  <\/li>\n<\/ul>\n<p>\n  We recommend that you choose one of these and go with that; while supported, using<br \/>\n  both methods at the same time is more error prone (for example, you might provide<br \/>\n  one URL in the HTTP header, and another URL in the <code>rel=\"canonical\"<\/code><br \/>\n  <code>link<\/code> element).\n<\/p>\n<h3 id=\"rel-canonical-link-method\" data-text='   The rel=\"canonical\" link element ' tabindex=\"-1\">\n  The <code>rel=\"canonical\"<\/code> <code>link<\/code> element<br \/>\n<\/h3>\n<p>\n  A <code>rel=\"canonical\"<\/code> <code>link<\/code> element (also known as a<br \/>\n  <em>canonical element<\/em>) is an element used in the <code>head<\/code> section of HTML<br \/>\n  to indicate that another page is representative of the content on the page.\n<\/p>\n<p>\n  Suppose you want <code>https:\/\/example.com\/dresses\/green-dresses<\/code> to be the<br \/>\n  canonical URL, even though a variety of URLs can access this content. Indicate this<br \/>\n  URL as canonical with these steps:\n<\/p>\n<ol>\n<li>\n    Add a <code>&lt;link&gt;<\/code> element with the attribute<br \/>\n    <code>rel=\"canonical\"<\/code> to the <code>&lt;head&gt;<\/code> section of<br \/>\n    duplicate pages, pointing to the canonical page. For example:<\/p>\n<div><\/div>\n<aside class=\"note\">We recommend adding this same self-referential<br \/>\n      <code>rel=\"canonical\"<\/code> link element to the canonical page itself as well.<br \/>\n    <\/aside>\n<\/li>\n<li>\n    If the canonical page has a mobile variant on a separate URL, add a<br \/>\n    <code>rel=\"alternate\"<\/code> <code>link<\/code> element to it, pointing to the mobile<br \/>\n    version of the page:<\/p>\n<div><\/div>\n<\/li>\n<li>\n    Add any<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>hreflang<\/code><\/a><br \/>\n    or other elements that are appropriate for the page.\n  <\/li>\n<\/ol>\n<p>\n  Use absolute paths rather than relative paths with the <code>rel=\"canonical\"<\/code><br \/>\n  <code>link<\/code> element. Even though relative paths are supported by Google, they<br \/>\n  can cause problems in the long run (for example, if you unintentionally allow your<br \/>\n  testing site to be crawled) and thus we don&#8217;t recommend them.\n<\/p>\n<p>\n  <span class=\"compare-yes\" aria-hidden=\"true\"><\/span><b>Good example<\/b>:<br \/>\n  <code>https:\/\/www.example.com\/dresses\/green\/green-dress.html<\/code>\n<\/p>\n<p>\n  <span class=\"compare-no\" aria-hidden=\"true\"><\/span><b>Bad example<\/b>:<br \/>\n  <code>\/dresses\/green\/green-dress.html<\/code>\n<\/p>\n<p>\n  The <code>rel=\"canonical\"<\/code> <code>link element<\/code> is only accepted if it<br \/>\n  appears in the <code>&lt;head&gt;<\/code> section of the HTML, so make sure at least the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/use-valid-html-to-specify-page-metadata\/\"><code>&lt;head&gt;<\/code> section is valid HTML<\/a>.\n<\/p>\n<p>\n  If you use JavaScript to add the <code>rel=\"canonical\"<\/code> <code>link<\/code> element,<br \/>\n  make sure to<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/javascript-seo-basics\/#properly-inject-canonical-links\">inject the canonical link element properly<\/a>.\n<\/p>\n<h3 id=\"rel-canonical-header-method\" data-text='The rel=\"canonical\" HTTP header' tabindex=\"-1\">The <code>rel=\"canonical\"<\/code> HTTP header<\/h3>\n<p>\n  If you can change the configuration of your server, you can use a <code>link<\/code><br \/>\n  <a href=\"https:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_header_fields\" class=\"external-link\">HTTP response header<\/a><br \/>\n  with a <code>rel=\"canonical\"<\/code> target attribute as defined by<br \/>\n  <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc5988.html#section-5.1\" class=\"external-link\">RFC5988<\/a><br \/>\n  rather than an HTML element to indicate the canonical URL for a document supported<br \/>\n  by Search, including non-HTML documents such as PDF files.\n<\/p>\n<p>Google supports this method for web search results only.<\/p>\n<p>\n  If you publish content in many file formats, such as PDF or Microsoft Word, each on<br \/>\n  their own URL, you can return a <code>rel=\"canonical\"<\/code> HTTP header to tell<br \/>\n  Googlebot what is the canonical URL for the non-HTML files. For example, to indicate<br \/>\n  that the PDF version of the <code>.docx<\/code> version should be canonical, you might<br \/>\n  add this HTTP header for the <code>.docx<\/code> version of the content:\n<\/p>\n<div><\/div>\n<p>\n  As with the <code>rel=\"canonical\"<\/code> <code>link<\/code> element, use absolute URLs<br \/>\n  in the <code>rel=\"canonical\"<\/code> HTTP header.\n<\/p>\n<h2 id=\"sitemap-method\" tabindex=\"-1\">Use a sitemap<\/h2>\n<p>\n  Pick a canonical URL for each of your pages and submit them in a<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/sitemaps-overview\/\">sitemap<\/a>. All pages<br \/>\n  listed in a sitemap are suggested as canonicals; Google will decide which pages<br \/>\n  (if any) are duplicates, based on similarity of content.\n<\/p>\n<p>\n  Supplying the preferred canonical URLs in the sitemaps is a straightforward way of defining<br \/>\n  canonicals for a large site, and sitemaps are a useful way to tell Google which pages<br \/>\n  you consider most important on your site.\n<\/p>\n<h2 id=\"redirects-method\" tabindex=\"-1\">Use redirects<\/h2>\n<p>\n  Use this method when you want to get rid of existing duplicate pages. All<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/\">permanent redirection methods<\/a><br \/>\n  have the same effect on Google Search, however the time it takes for search engines to notice the<br \/>\n  different redirect methods may differ.\n<\/p>\n<p>\n  For the quickest effect, use HTTP (also known as <em>server-side<\/em>) redirects.\n<\/p>\n<p>Suppose your page can be reached in multiple ways:<\/p>\n<ul>\n<li><code>https:\/\/example.com\/home<\/code><\/li>\n<li><code>https:\/\/home.example.com<\/code><\/li>\n<li><code>https:\/\/www.example.com<\/code><\/li>\n<\/ul>\n<p>\n  Pick one of those URLs as your canonical URL, and use redirects to send traffic from<br \/>\n  the other URLs to your preferred URL.\n<\/p>\n<h2 id=\"other-signals\" tabindex=\"-1\">Other signals<\/h2>\n<p>\n  Apart from explicitly provided methods, Google also uses a set of canonicalization signals<br \/>\n  that are generally based on site setup: preferring HTTPS over HTTP, and URLs in<br \/>\n  <code>hreflang<\/code> clusters.\n<\/p>\n<h3 id=\"prefer-https-over-http-for-canonical-urls\" tabindex=\"-1\">Prefer HTTPS over HTTP for canonical URLs<\/h3>\n<p>\n  Google prefers HTTPS pages over equivalent HTTP pages as canonical, except when there<br \/>\n  are issues or conflicting signals such as the following:\n<\/p>\n<ul>\n<li>The HTTPS page has an invalid SSL certificate.<\/li>\n<li>The HTTPS page contains insecure dependencies (other than images).<\/li>\n<li>The HTTPS page redirects users to or through an HTTP page.<\/li>\n<li>\n    The HTTPS page has a <code>rel=\"canonical\"<\/code> <code>link<\/code><br \/>\n    to the HTTP page.\n  <\/li>\n<\/ul>\n<p>\n  Although our systems prefer HTTPS pages over HTTP pages by default, you can ensure this<br \/>\n  behavior by taking any of the following actions:\n<\/p>\n<ul>\n<li>Add redirects from the HTTP page to the HTTPS page.<\/li>\n<li>\n    Add a <code>rel=\"canonical\"<\/code> <code>link<\/code> from the HTTP<br \/>\n    page to the HTTPS page.\n  <\/li>\n<li>\n    Implement<br \/>\n    <a href=\"https:\/\/en.wikipedia.org\/wiki\/HTTP_Strict_Transport_Security\" class=\"external-link\">HSTS<\/a>.\n  <\/li>\n<\/ul>\n<p>\n  To prevent Google from incorrectly making the HTTP page canonical, <strong>avoid<\/strong><br \/>\n  the following practices:\n<\/p>\n<ul>\n<li>\n    Avoid bad TLS\/SSL certificates and HTTPS-to-HTTP redirects because they cause Google<br \/>\n    to prefer HTTP very strongly. Implementing HSTS cannot override this strong preference.\n  <\/li>\n<li>\n    Don&#8217;t include the HTTP version of your pages in your sitemap or<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>hreflang<\/code> annotations<\/a><br \/>\n    rather than the HTTPS version.\n  <\/li>\n<li>\n    Avoid implementing your SSL\/TLS certificate for the wrong host-variant. For example,<br \/>\n    <code>example.com<\/code> serving the certificate for <code>subdomain.example.com<\/code>.<br \/>\n    The certificate must match your complete site URL, or be a wildcard certificate that<br \/>\n    can be used for multiple subdomains on a domain.\n  <\/li>\n<\/ul>\n<h3 id=\"prefer-urls-in-hreflang-clusters\" tabindex=\"-1\">Prefer URLs in <code>hreflang<\/code> clusters<\/h3>\n<p>\n  To help with sites&#8217; localization efforts, for canonicalization purposes Google prefers<br \/>\n  URLs that are part of <code>hreflang<\/code> clusters. For example, if<br \/>\n  <code>https:\/\/example.com\/de-de\/cats<\/code> and<br \/>\n  <code>https:\/\/example.com\/de-ch\/cats<\/code> reciprocally point to each other with<br \/>\n  <code>hreflang<\/code> annotations, but not to<br \/>\n  <code>https:\/\/example.com\/de-at\/cats<\/code>, the pages for<br \/>\n  <code>de-de<\/code> and <code>de-ch<\/code> will be preferred as canonicals instead<br \/>\n  of the <code>\/de-at\/<\/code> page that doesn&#8217;t appear in the<br \/>\n  <code>hreflang<\/code> cluster.\n<\/p>\n<p>\n  Read more about<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-canonicalization-issues\/\">troubleshooting and fixing canonicalization issues<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a site has duplicate content, Google chooses the canonical URL. Learn more about canonical URLs and how to consolidate duplicate URLs.<\/p>\n","protected":false},"menu_order":30,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[687],"ar_kb_etiket":[568,570,557],"class_list":["post-16568","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-canonicalization-crawling-and-indexing","ar_kb_etiket-canonical","ar_kb_etiket-redirects","ar_kb_etiket-sitemap"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16568","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":2,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16568\/revisions"}],"predecessor-version":[{"id":25555,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16568\/revisions\/25555"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26332"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=16568"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=16568"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=16568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}