{"id":24107,"date":"2009-02-12T00:00:00","date_gmt":"2009-02-12T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-your-canonical\/"},"modified":"2009-02-12T00:00:00","modified_gmt":"2009-02-12T00:00:00","slug":"specify-your-canonical","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-your-canonical\/","title":{"rendered":"Specify your canonical"},"content":{"rendered":"

Thursday, February 12, 2009<\/p>\n

\n Carpe diem on any
\n duplicate content worries<\/a>:
\n we now support a format that allows you to publicly specify your preferred version of a URL. If
\n your site has identical or vastly similar content that’s accessible through multiple URLs, this
\n format provides you with more control over the URL returned in search results. It also helps to
\n make sure that properties such as link popularity are consolidated to your preferred version.\n<\/p>\n

\n Let’s take our old example of a
\n site selling Swedish fish<\/a>.
\n Imagine that your preferred version of the URL and its content looks like this:
\n https:\/\/www.example.com\/product.php?item=swedish-fish<\/code>\n<\/p>\n

<\/p>\n

\n However, users (and Googlebot) can access Swedish fish through multiple (not as simple) URLs. Even
\n if the key information on these URLs is the same as your preferred version, they may show slight
\n content variations due to things like sort parameters or category navigation:
\n https:\/\/www.example.com\/product.php?item=swedish-fish&category=gummy-candy<\/code>\n<\/p>\n

<\/p>\n

\n Or they have completely identical content, but with different URLs due to things such as a
\n tracking parameters or a session ID:
\n https:\/\/www.example.com\/product.php?item=swedish-fish&trackingid=1234&sessionid=5678<\/code>\n<\/p>\n

<\/p>\n

\n Now, you can simply add this <link \/><\/code> tag to specify your preferred version:
\n <link rel=\"canonical\" href=\"https:\/\/www.example.com\/product.php?item=swedish-fish\" \/><\/code>
\n inside the <head><\/code> section of the duplicate content URLs:\n<\/p>\n

<\/div>\n

\n and Google will understand that the duplicates all refer to the canonical URL:
\n https:\/\/www.example.com\/product.php?item=swedish-fish<\/code>. Additional URL properties, like
\n PageRank and related signals, are transferred as well.\n<\/p>\n

This standard can be adopted by any search engine when crawling and indexing your site.<\/p>\n

\n Of course you may have more questions.
\n Joachim Kupke<\/a>,
\n an engineer from our Indexing Team, is here to provide us with the answers:\n<\/p>\n

\n Is rel=\"canonical\"<\/code> a hint or a command?<\/b>
\n It’s a hint that we honor strongly. We’ll take your preference into account, in conjunction with
\n other signals, when calculating the most relevant page to display in search results.\n<\/p>\n

\n Can I use a relative path to specify the canonical, such as
\n <link rel=\"canonical\" href=\"product.php?item=swedish-fish\" \/><\/code>?<\/b>
\n Yes, relative paths are recognized as expected with the <link \/><\/code> tag. Also, if
\n you include a <base \/><\/code> link in your document, relative paths will resolve
\n according to the base URL.\n<\/p>\n

\n Is it okay if the canonical is not an exact duplicate of the content?<\/b>
\n We allow slight differences, for example, in the sort order of a table of products. We also
\n recognize that we may crawl the canonical and the duplicate pages at different points in time,
\n so we may occasionally see different versions of your content. All of that is okay with us.\n<\/p>\n

\n What if the rel=\"canonical\"<\/code> returns a 404<\/code>?<\/b>
\n We’ll continue to index your content and use a heuristic to find a canonical, but we recommend
\n that you specify existent URLs as canonicals.\n<\/p>\n

\n What if the rel=\"canonical\"<\/code> hasn’t yet been indexed?<\/b>
\n Like all public content on the web, we strive to discover and crawl a designated canonical URL
\n quickly. As soon as we index it, we’ll immediately reconsider the
\n rel=\"canonical\"<\/code> hint.\n<\/p>\n

\n Can rel=\"canonical\"<\/code> be a redirect?<\/b>
\n Yes, you can specify a URL that redirects as a canonical URL. Google will then process the
\n redirect as usual and try to index it.\n<\/p>\n

\n What if I have contradictory rel=\"canonical\"<\/code> designations?<\/b>
\n Our algorithm is lenient: We can follow canonical chains, but we strongly recommend that you
\n update links to point to a single canonical page to ensure optimal canonicalization results.\n<\/p>\n