rel-canonical - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:31:31Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:31, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~rel-canonical~~</entry-title>~~		{{DISPLAYTITLE:rel-canonical}}
	<span class="h-card vcard"><span class="p-name fn">[[User:Kevin Marks\|Kevin Marks]]</span> (<span class="p-role role">Editor</span>)</span>		<span class="h-card vcard"><span class="p-name fn">[[User:Kevin Marks\|Kevin Marks]]</span> (<span class="p-role role">Editor</span>)</span>
	----		----

Kevin Marks: /* rel-amphtml */ typo

2017-09-21T12:12:31Z

rel-amphtml: typo

← Older revision		Revision as of 12:12, 21 September 2017
Line 22:		Line 22:
	[[rel-alternate]] is used to link to versions of the page in other forms, whether a different format with <code>type</code>, language with <code>hreflang</code> or presentation medium with <code>media</code>.		[[rel-alternate]] is used to link to versions of the page in other forms, whether a different format with <code>type</code>, language with <code>hreflang</code> or presentation medium with <code>media</code>.
	=== rel-amphtml ===		=== rel-amphtml ===
	[[rel-amphtml]] is used to link to the Accelerated Mobile Pages version, a html subset limiting javascript, replacing built-in elements with custom elements and designed for caching. It is [https://www.ampproject.org/docs/guides/deploy/discovery recommended] to link back ~~fromt he~~ AMP version to the original with rel-canonical		[[rel-amphtml]] is used to link to the Accelerated Mobile Pages version, a html subset limiting javascript, replacing built-in elements with custom elements and designed for caching. It is [https://www.ampproject.org/docs/guides/deploy/discovery recommended] to link back from the AMP version to the original with rel-canonical

	=== rel-shortlink ===		=== rel-shortlink ===
	[[rel-shortlink]] is used to link to a url shortened version designed for sharing and (often) tracking.		[[rel-shortlink]] is used to link to a url shortened version designed for sharing and (often) tracking.

Kevin Marks: /* The opposite of canonical */

2017-03-28T10:58:18Z

The opposite of canonical

@@ Line 15: / Line 15: @@
 === Cross-domain links ===
 Although the primary use case is links within the same domain, rel=canonical can be used [https://webmasters.googleblog.com/2009/12/handling-legitimate-cross-domain.html across domains] too. A common use case recently is from [https://www.ampproject.org/docs/guides/deploy/discovery cached AMP pages] to their original.
 == Issues ==

Kevin Marks: /* See Also */ add RFC

2017-03-28T10:35:26Z

Kevin Marks: /* Cross-domain links */ typo

2017-03-28T10:31:05Z

Cross-domain links: typo

← Older revision		Revision as of 10:31, 28 March 2017
Line 14:		Line 14:
	Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will [https://www.mattcutts.com/blog/rel-canonical-html-head/ ignore it] on an <code><a></code> element.		Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will [https://www.mattcutts.com/blog/rel-canonical-html-head/ ignore it] on an <code><a></code> element.
	=== Cross-domain links ===		=== Cross-domain links ===
	Although the primary use case is links ~~wihtin~~ the same domain, rel=canonical can be used [https://webmasters.googleblog.com/2009/12/handling-legitimate-cross-domain.html across domains] too. A common use case recently is from [https://www.ampproject.org/docs/guides/deploy/discovery cached AMP pages] to their original.		Although the primary use case is links within the same domain, rel=canonical can be used [https://webmasters.googleblog.com/2009/12/handling-legitimate-cross-domain.html across domains] too. A common use case recently is from [https://www.ampproject.org/docs/guides/deploy/discovery cached AMP pages] to their original.

	== Issues ==		== Issues ==

Kevin Marks: /* See Also */ sharelink

2017-03-28T10:30:33Z

Kevin Marks: /* Discussion */ cross-domain

2017-03-28T10:29:56Z

Discussion: cross-domain

← Older revision		Revision as of 10:29, 28 March 2017
Line 13:		Line 13:

	Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will [https://www.mattcutts.com/blog/rel-canonical-html-head/ ignore it] on an <code><a></code> element.		Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will [https://www.mattcutts.com/blog/rel-canonical-html-head/ ignore it] on an <code><a></code> element.
			=== Cross-domain links ===
			Although the primary use case is links wihtin the same domain, rel=canonical can be used [https://webmasters.googleblog.com/2009/12/handling-legitimate-cross-domain.html across domains] too. A common use case recently is from [https://www.ampproject.org/docs/guides/deploy/discovery cached AMP pages] to their original.

	== Issues ==		== Issues ==

Kevin Marks: /* Discussion */ a ignore

2017-03-28T10:24:25Z

Discussion: a ignore

← Older revision		Revision as of 10:24, 28 March 2017
Line 12:		Line 12:
	There are many reasons for a site to serve the same content at multiple URLs, but duplicate pages are undesirable in search results. The [https://www.mattcutts.com/blog/seo-advice-url-canonicalization/ historic recommendation] was to use 301 redirects to the canonical page, but that can be jarring for users. There are many use cases for a URL to have additional information added as query parameters or fragments to indicate the navigation history for referral purposes, but would prefer a single main referent from searches. This was codified in February 2009 as rel=canonical, and [https://webmasters.googleblog.com/2009/02/specify-your-canonical.html adopted] by [http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ many] [https://blogs.msdn.microsoft.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx search] [https://web-beta.archive.org/web/20091008070823/http://blog.ask.com/2009/02/ask-is-going-canonical.html engines].		There are many reasons for a site to serve the same content at multiple URLs, but duplicate pages are undesirable in search results. The [https://www.mattcutts.com/blog/seo-advice-url-canonicalization/ historic recommendation] was to use 301 redirects to the canonical page, but that can be jarring for users. There are many use cases for a URL to have additional information added as query parameters or fragments to indicate the navigation history for referral purposes, but would prefer a single main referent from searches. This was codified in February 2009 as rel=canonical, and [https://webmasters.googleblog.com/2009/02/specify-your-canonical.html adopted] by [http://www.ysearchblog.com/2009/02/12/fighting-duplication-adding-more-arrows-to-your-quiver/ many] [https://blogs.msdn.microsoft.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx search] [https://web-beta.archive.org/web/20091008070823/http://blog.ask.com/2009/02/ask-is-going-canonical.html engines].

	Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will ignore it on an <code><a></code> element.		Search engines prefer <code>rel=canonical</code> on a <code><link></code> element, and will [https://www.mattcutts.com/blog/rel-canonical-html-head/ ignore it] on an <code><a></code> element.

	== Issues ==		== Issues ==

Kevin Marks: copypasta error

2017-03-28T10:22:31Z

copypasta error

← Older revision		Revision as of 10:22, 28 March 2017
Line 1:		Line 1:
	<entry-title>h-~~card~~</entry-title>		<entry-title>rel-canonical</entry-title>
	<span class="h-card vcard"><span class="p-name fn">[[User:Kevin Marks\|Kevin Marks]]</span> (<span class="p-role role">Editor</span>)</span>		<span class="h-card vcard"><span class="p-name fn">[[User:Kevin Marks\|Kevin Marks]]</span> (<span class="p-role role">Editor</span>)</span>
	----		----

Kevin Marks: /* Abstract */ typo

2017-03-28T10:21:37Z

Abstract: typo

← Older revision		Revision as of 10:21, 28 March 2017
Line 7:		Line 7:

	== Abstract ==		== Abstract ==
	<p class="entry-summary">By adding <code>rel="~~caconical~~"</code> to a hyperlink, a page indicates that the destination of that hyperlink {{should}} be considered the preferred or definitive version of the current page. This helps search engines avoid duplicate content, and is useful for deciding how to link to a page when citing it.</p>		<p class="entry-summary">By adding <code>rel="canonical"</code> to a hyperlink, a page indicates that the destination of that hyperlink {{should}} be considered the preferred or definitive version of the current page. This helps search engines avoid duplicate content, and is useful for deciding how to link to a page when citing it.</p>

	== Discussion ==		== Discussion ==

← Older revision		Revision as of 10:35, 28 March 2017
Line 25:		Line 25:
	* [http://known.kevinmarks.com/2017/day-7-to-amp-or-not-to-amp-100daysofindieweb canonical bookmarklets]		* [http://known.kevinmarks.com/2017/day-7-to-amp-or-not-to-amp-100daysofindieweb canonical bookmarklets]
	* [[sharelink-formats]]		* [[sharelink-formats]]
			* [https://tools.ietf.org/html/rfc6596 RFC 6596 - The Canonical Link Relation]

← Older revision		Revision as of 10:30, 28 March 2017
Line 24:		Line 24:
	* [https://support.google.com/webmasters/answer/139066?hl=en Google's canonical advice page]		* [https://support.google.com/webmasters/answer/139066?hl=en Google's canonical advice page]
	* [http://known.kevinmarks.com/2017/day-7-to-amp-or-not-to-amp-100daysofindieweb canonical bookmarklets]		* [http://known.kevinmarks.com/2017/day-7-to-amp-or-not-to-amp-100daysofindieweb canonical bookmarklets]
			* [[sharelink-formats]]