{"id":24276,"date":"2009-12-15T00:00:00","date_gmt":"2009-12-15T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/handling-legitimate-cross-domain-content-duplication\/"},"modified":"2009-12-15T00:00:00","modified_gmt":"2009-12-15T00:00:00","slug":"handling-legitimate-cross-domain-content-duplication","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/handling-legitimate-cross-domain-content-duplication\/","title":{"rendered":"Handling legitimate cross-domain content duplication"},"content":{"rendered":"<aside class=\"key-point\">It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore).<br \/>\nSpecifically, <code>rel=\"canonical\"<\/code> is no longer recommended for<br \/>\n<a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-canonicalization-issues\/#syndicated-content\">syndicated content<\/a>.<\/aside>\n<p class=\"gargardate\">Tuesday, December 15, 2009<\/p>\n<p>\n  We&#8217;ve recently discussed several ways of<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/reunifying-duplicate-content-on-your-website\/\">handling duplicate content on a single website<\/a>;<br \/>\n  today we&#8217;ll look at ways of handling similar duplication across different websites, across<br \/>\n  different domains. For some sites, there are legitimate reasons to duplicate content across<br \/>\n  different websites&mdash;for instance, to migrate to a new domain name using a web server that<br \/>\n  cannot create server-side redirects. To help with issues that arise on such sites, we&#8217;re<br \/>\n  announcing our support of the<br \/>\n  <b>cross-domain <code>rel=\"canonical\"<\/code> link element<\/b>.\n<\/p>\n<p><img decoding=\"async\" alt=\"diagram showing rel-canonical in action by one page pointing to the other\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-1fbe6a928e6c.png\" loading=\"lazy\"><\/p>\n<h2 id=\"ways-of-handling-cross-domain-content-duplication:\" tabindex=\"-1\">Ways of handling cross-domain content duplication:<\/h2>\n<ul>\n<li>\n    <b>Choose your preferred domain<\/b><br \/>\n    When confronted with duplicate content, search engines will generally take one version and<br \/>\n    filter the others out. This can also happen when multiple domain names are involved, so while<br \/>\n    search engines are generally pretty good at choosing something reasonable, many webmasters<br \/>\n    prefer to make that decision themselves.\n  <\/li>\n<li>\n    <b>Reduce in-site duplication<\/b><br \/>\n    Before starting on cross-site duplicate content questions, make sure to<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/\">handle duplication within your site<\/a><br \/>\n    first.\n  <\/li>\n<li>\n    <b>Enable crawling and use <code>301<\/code> (permanent) redirects where possible<\/b><br \/>\n    Where possible, the most important step is often to use appropriate<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/\"><code>301<\/code> redirects<\/a>.<br \/>\n    These redirects send visitors and search engine crawlers to your preferred domain and make it<br \/>\n    very clear which URL should be indexed. This is generally the preferred method as it gives clear<br \/>\n    guidance to everyone who accesses the content. Keep in mind that in order for search engine<br \/>\n    crawlers to discover these redirects, none of the URLs in the redirect chain can be disallowed<br \/>\n    via a<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-txt-intro\/\">robots.txt file<\/a>.<br \/>\n    Don&#8217;t forget to handle your www \/ non-www preference with appropriate redirects and in<br \/>\n    <a href=\"https:\/\/www.google.com\/support\/webmasters\/bin\/answer.py?answer=44231\" class=\"external-link\">Webmaster Tools<\/a>.\n  <\/li>\n<li>\n    <b>Use the cross-domain <code>rel=\"canonical\"<\/code> link element<\/b><br \/>\n    There are situations where it&#8217;s not easily possible to set up redirects. This could be the case<br \/>\n    when you need to move your website from a server that does not feature server-side redirects.<br \/>\n    In a situation like this, <b>you can use the<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/\"><code>rel=\"canonical\"<\/code> link element<\/a><br \/>\n    across domains<\/b> to specify the exact URL of whichever domain is preferred for indexing. While<br \/>\n    the <code>rel=\"canonical\"<\/code> link element is seen as a hint and not an absolute command,<br \/>\n    we do try to follow it where possible.\n  <\/li>\n<\/ul>\n<h2 id=\"still-have-questions\" tabindex=\"-1\">Still have questions?<\/h2>\n<p>\n  <b>Do the pages have to be identical?<\/b><br \/>\n  No, but they should be similar. Slight differences are fine.\n<\/p>\n<p>\n  <b>For technical reasons I can&#8217;t include a 1:1 mapping for the URLs on my sites. Can I just<br \/>\n    point the <code>rel=\"canonical\"<\/code> at the home page of my preferred site?<\/b><br \/>\n  No; this could result in problems. A mapping from old URL to new URL for each URL on the old site<br \/>\n  is the best way to use <code>rel=\"canonical\"<\/code>.\n<\/p>\n<p>\n  <b>I&#8217;m offering my content \/ product descriptions for syndication. Do my publishers need to use<br \/>\n    <code>rel=\"canonical\"<\/code>?<\/b><br \/>\n  We leave this up to you and your publishers. If the content is similar enough, it might make<br \/>\n  sense to use <code>rel=\"canonical\"<\/code>, if both parties agree.\n<\/p>\n<p>\n  <b>My server can&#8217;t do a <code>301<\/code> (permanent) redirect. Can I use<br \/>\n    <code>rel=\"canonical\"<\/code> to move my site?<\/b><br \/>\n  If it&#8217;s at all possible, you should work with your webhost or web server to do a<br \/>\n  <code>301<\/code> redirect. Keep in mind that we treat <code>rel=\"canonical\"<\/code> as a hint,<br \/>\n  and other search engines may handle it differently. But if a <code>301<\/code> redirect is<br \/>\n  impossible for some reason, then a <code>rel=\"canonical\"<\/code> may work for you. For more<br \/>\n  information, see our<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/changing-your-hosting\/\">guidelines on moving your site<\/a>.\n<\/p>\n<p>\n  <b>Should I use a <code>noindex<\/code> robots<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/meta-tags\/\"><code>meta<\/code> tag<\/a><br \/>\n    on pages with a <code>rel=\"canonical\"<\/code> link element?<\/b><br \/>\n  No, since those pages would not be equivalent with regards to indexing&mdash;one would be allowed<br \/>\n  while the other would be blocked. Additionally, it&#8217;s important that these pages are not<br \/>\n  disallowed from crawling through a robots.txt file, otherwise search engine crawlers will not<br \/>\n  be able to discover the <code>rel=\"canonical\"<\/code> link element.\n<\/p>\n<p>\n  We hope this makes it easier for you to handle duplicate content in a user-friendly way. Are<br \/>\n  there still places where you feel that duplicate content is causing your sites problems? Let us<br \/>\n  know in the<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\/thread?tid=07603d23e8071644\" class=\"external-link\">Webmaster Help Forum<\/a>!\n<\/p>\n<p class=\"byline-author\">\n  Posted by<br \/>\n  <a class=\"external-link\" href=\"https:\/\/twitter.com\/JohnMu\" class=\"external-link\">John Mueller<\/a>,<br \/>\n  Webmaster Trends Analyst, Google Z\u00fcrich<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Specifically, rel=&#8221;canonical&#8221; is no longer recommended for syndicated content. Tuesday, December 15, 2009 We&#8217;ve recently discussed several ways of handling duplicate content on a [&hellip;]<\/p>\n","protected":false},"menu_order":85407,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24276","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24276","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":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24276\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26755"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24276"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24276"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}