<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Move Your Site to SSL	</title>
	<atom:link href="https://www.searchenginepeople.com/blog/15083-how-to-ssl.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.searchenginepeople.com/blog/15083-how-to-ssl.html?utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Canada&#039;s Search and Social Media Authority</description>
	<lastBuildDate>Sat, 28 Jan 2017 01:39:55 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ruud Hein		</title>
		<link>https://www.searchenginepeople.com/blog/15083-how-to-ssl.html/comment-page-1#comment-1052876</link>

		<dc:creator><![CDATA[Ruud Hein]]></dc:creator>
		<pubDate>Wed, 26 Aug 2015 15:08:33 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com?p=60697&#038;preview_id=60697#comment-1052876</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/15083-how-to-ssl.html/comment-page-1#comment-1050288&quot;&gt;Steve Pringle&lt;/a&gt;.

If the http version is live and indexable, that &lt;em&gt;can&lt;/em&gt; work. If the http version isn&#039;t reachable for Google then they&#039;ll ignore the canonical signal.

All in all it&#039;s a bit of a useless scenario though. Point your canonical to the one true canonical location. If ever you stop SSL, a site-wide 301 redirect to HTTP will do the trick.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/15083-how-to-ssl.html/comment-page-1#comment-1050288" data-wpel-link="internal">Steve Pringle</a>.</p>
<p>If the http version is live and indexable, that <em>can</em> work. If the http version isn&#8217;t reachable for Google then they&#8217;ll ignore the canonical signal.</p>
<p>All in all it&#8217;s a bit of a useless scenario though. Point your canonical to the one true canonical location. If ever you stop SSL, a site-wide 301 redirect to HTTP will do the trick.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Steve Pringle		</title>
		<link>https://www.searchenginepeople.com/blog/15083-how-to-ssl.html/comment-page-1#comment-1050288</link>

		<dc:creator><![CDATA[Steve Pringle]]></dc:creator>
		<pubDate>Wed, 05 Aug 2015 22:19:02 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com?p=60697&#038;preview_id=60697#comment-1050288</guid>

					<description><![CDATA[What are your thoughts on using http canonical links with a https site?

Right now, I do this since I may change the domain name and do not
want to keep paying for a SLL certificate just the redirect the indexed
SSL results to the new domain.]]></description>
			<content:encoded><![CDATA[<p>What are your thoughts on using http canonical links with a https site?</p>
<p>Right now, I do this since I may change the domain name and do not<br />
want to keep paying for a SLL certificate just the redirect the indexed<br />
SSL results to the new domain.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
