<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Google Archives - Technical Blogging</title>
	<atom:link href="https://technicalblogging.com/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>https://technicalblogging.com/tag/google/</link>
	<description>Amplify your influence by sharing your knowledge</description>
	<lastBuildDate>Fri, 29 Jun 2018 06:49:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/>
<atom:link rel="hub" href="https://websubhub.com/hub"/>
<atom:link rel="self" href="https://technicalblogging.com/tag/google/feed/"/>
<site xmlns="com-wordpress:feed-additions:1">30282829</site>	<item>
		<title>How to Future-Proof Your Blog Against Google&#8217;s Algorithm Changes</title>
		<link>https://technicalblogging.com/future-proof-your-blog-against-googles-algorithm-changes/</link>
					<comments>https://technicalblogging.com/future-proof-your-blog-against-googles-algorithm-changes/#respond</comments>
		
		<dc:creator><![CDATA[Antonio Cangiano]]></dc:creator>
		<pubDate>Fri, 29 Jun 2018 06:49:30 +0000</pubDate>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[google algorithm]]></category>
		<category><![CDATA[ranking]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[SERP]]></category>
		<guid isPermaLink="false">https://technicalblogging.com/?p=654</guid>

					<description><![CDATA[<p>A couple of days ago I was giving a presentation on chatbot building and the business opportunities that they represent (also the subject of a free chatbot course I created). I was very fortunate to have an engaged audience that asked many great questions. One of which is particularly relevant to this blog. An attendee [&#8230;]</p>
<p>The post <a href="https://technicalblogging.com/future-proof-your-blog-against-googles-algorithm-changes/">How to Future-Proof Your Blog Against Google&#8217;s Algorithm Changes</a> appeared first on <a href="https://technicalblogging.com">Technical Blogging</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p style="text-align: center;"><img data-recalc-dims="1" fetchpriority="high" decoding="async" class="aligncenter wp-image-656 size-full" title="How to Future-Proof Your Blog Against Google's Algorithm Changes" src="https://i0.wp.com/technicalblogging.com/wp-content/uploads/2018/06/How-to-Future-Proof-Your-Blog-Against-Googles-Algorithm-Changes.png?resize=560%2C315&#038;ssl=1" alt="How to Future-Proof Your Blog Against Google's Algorithm Changes" width="560" height="315" srcset="https://i0.wp.com/technicalblogging.com/wp-content/uploads/2018/06/How-to-Future-Proof-Your-Blog-Against-Googles-Algorithm-Changes.png?w=560&amp;ssl=1 560w, https://i0.wp.com/technicalblogging.com/wp-content/uploads/2018/06/How-to-Future-Proof-Your-Blog-Against-Googles-Algorithm-Changes.png?resize=550%2C309&amp;ssl=1 550w" sizes="(max-width: 560px) 100vw, 560px" /></p>
<p>A couple of days ago I was giving a presentation on chatbot building and the business opportunities that they represent (also the subject of a free <a href="https://www.edx.org/course/how-to-build-chatbots-and-make-money" target="_blank" rel="noopener">chatbot course</a> I created).</p>
<p>I was very fortunate to have an engaged audience that asked many great questions. One of which is particularly relevant to this blog. An attendee asked, “What is the impact of chatbots on SEO?”.</p>
<h2 id="whats-the-impact-of-chatbots-on-seo">What’s the impact of chatbots on SEO?</h2>
<p>My answer was that chatbots are so new it’s unlikely Google has already put algorithmic changes in place that are specifically targeted at chatbots.</p>
<p>All we have to go by are the SEO rules we already know. From these rules, we can deduct the likely impact of chatbots on SEO.</p>
<p>Google does not interrogate chatbots like a human would, in order to crawl their content. So you should have the same information available on the site in traditional pages as well.</p>
<p>Provided you do that, chatbots are a net positive because they increase engagement and time on page, while lowering bounce rates.</p>
<p>All great signals of a quality site, which Google will reward with better rankings in the result pages.</p>
<h2 id="how-do-you-future-proof-your-blog-for-google">How do you future-proof your blog for Google?</h2>
<p>The question, and the answer I developed on the fly, led me to consider the more general question of how to future-proof sites against Google’s constant algorithm changes.</p>
<p>Google fine tunes its algorithm with minor updates hundreds of times per year. Once in a while they’ll roll out major updates that drastically change results and in the process impact millions of site owners.</p>
<p>You might be familiar with classic updates such as Panda, Penguin, and Hummingbird.</p>
<p>We can predict the future with a higher degree of accuracy if we first study the past.</p>
<p>The general trend that Google has shown over the years has been “serving the end user”. They have increasingly rewarded sites that provided value to the user, and penalized those that did not.</p>
<p>For example, Google loves long content because it is more likely to provide the answer that the user is looking for, or to inform them thoroughly on a given topic.</p>
<p>When users click on a result and stay on the site for a long time, it’s an indication that the site has something valuable to offer to the user.</p>
<p>Speed helps the user. A responsive design that works well on mobile phones and tablets helps the user.</p>
<p>Artificially repeating the same keyword the user searched for 50 times on the page does not help the user in any way. This so-called “keyword stuffing” approach worked when Google’s ranking algorithm was much simpler, but today it’s something that will actually penalize your site.</p>
<h2 id="do-whats-best-for-the-user">Do what’s best for the user</h2>
<p>Your North Star, and the only way to future-proof your blog against Google’s algorithm changes is to do right by your readers. When making a choice that could affect rankings down the line, ask yourself, how will this help my users?</p>
<p>It would be very uncharacteristic of Google to penalize you for helping your users further. If anything, you are likely to be rewarded to a greater degree for this, as the algorithm becomes even more intelligent and refined.</p>
<p>At any rate, it’s the right thing to do, so do it anyway and trust that Google will take notice in the future.</p>
<p>The post <a href="https://technicalblogging.com/future-proof-your-blog-against-googles-algorithm-changes/">How to Future-Proof Your Blog Against Google&#8217;s Algorithm Changes</a> appeared first on <a href="https://technicalblogging.com">Technical Blogging</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://technicalblogging.com/future-proof-your-blog-against-googles-algorithm-changes/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">654</post-id>	</item>
		<item>
		<title>Google Killed the RSS Feed</title>
		<link>https://technicalblogging.com/google-killed-the-rss-feed/</link>
					<comments>https://technicalblogging.com/google-killed-the-rss-feed/#respond</comments>
		
		<dc:creator><![CDATA[Antonio Cangiano]]></dc:creator>
		<pubDate>Wed, 12 Nov 2014 15:00:30 +0000</pubDate>
				<category><![CDATA[Understanding Blogging]]></category>
		<category><![CDATA[Bloglovin]]></category>
		<category><![CDATA[Buffer]]></category>
		<category><![CDATA[Feedly]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Hootsuite]]></category>
		<category><![CDATA[RSS feed]]></category>
		<category><![CDATA[social media]]></category>
		<guid isPermaLink="false">https://technicalblogging.com/?p=328</guid>

					<description><![CDATA[<p>The RSS feed is in a coma. Google put it in that state and, boy, have they ever dropped the ball on this one. It all started with Google&#8217;s attempt to steer their huge ship towards the mythical land of all things Social. You see, Facebook&#8217;s success really took a few giant tech companies by [&#8230;]</p>
<p>The post <a href="https://technicalblogging.com/google-killed-the-rss-feed/">Google Killed the RSS Feed</a> appeared first on <a href="https://technicalblogging.com">Technical Blogging</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The RSS feed is in a coma. Google put it in that state and, boy, have they ever dropped the ball on this one.</p>
<p><img data-recalc-dims="1" decoding="async" class="alignright size-full wp-image-334" style="float: right;" src="https://i0.wp.com/technicalblogging.com/wp-content/uploads/2014/11/video-killed-the-radio-star.png?resize=250%2C197&#038;ssl=1" alt="Video Killed the Radio Star" width="250" height="197" /></p>
<p>It all started with Google&#8217;s attempt to steer their huge ship towards the mythical land of all things Social. You see, Facebook&#8217;s success really took a few giant tech companies by surprise. Google in particular. Surely, they thought to themselves, we must be able to compete.</p>
<p>So instead of focusing on their core competency, they decided to start throwing Social everywhere. It showed up in their search results. It was pushed down your Gmail throat. You had to have a Google+ account to use Google&#8217;s services in any capacity. UI and accounts got more and more confusing. YouTubers weren&#8217;t spared either.</p>
<p>Oh, and they wanted your real name, like Facebook. If you are secretly transgender or wanted by the Iranian government, tough luck, kiddo. (The relative lack of Social success and massive protests have eventually led them to change their initial policy.)</p>
<p>So what does this circus has to do with the RSS feed? Well, when you&#8217;re wearing Social blinders, that&#8217;s all you can see. They discontinued most of their services that couldn&#8217;t be adopted to this narrow world view.</p>
<p>Google Reader, the first successful attempt at making RSS feeds somewhat mainstream, was shut down. Instead of this handy service that was already loved by millions around the world, they wanted you to share articles on their social network. Follow people, put them in circles, and generally pretend you were on Facebook. There, they figured, no need to properly follow a feed with the purpose of never missing a new article. Good stuff will bubble up to the surface. Hopefully.</p>
<p>To round things off, they also got rid of the RSS button in Chrome so that finding the feed for a site is now a decent first exercise in learning HTML programming for the general public.</p>
<p>These two simple steps by Google have pretty much mortally wounded the RSS feed. It won&#8217;t recover I&#8217;m afraid and it&#8217;s a damn shame. A minority of geeks will continue to use the technology via services like <a title="Feedly" href="https://feedly.com" target="_blank">Feedly</a>, but the mainstream dream is gone.</p>
<p>All for a social network that relatively few people use, let alone in any serious capacity (at least in part because Google stubbornly refuses to open their API to allow third-party apps, like <a title="Buffer" href="https://bufferapp.com/r/161d3" target="_blank" rel="nofollow">Buffer</a> and <a href="https://www.shareasale.com/r.cfm?b=363437&amp;u=412005&amp;m=37818&amp;urllink=&amp;afftrack=" target="_blank" rel="nofollow">Hootsuite</a>, to post on people&#8217;s own profiles).</p>
<p>If you think I&#8217;m just talking hypothetically, think again. I saw one of my blogs go from a healthy 16,000 RSS subscribers to less than 300 in the span of just a month or so after this change was made (many, including my wife, who is a popular blogger in her field, witnessed the same sort of abrupt, brutal nosedive with her RSS numbers as well).</p>
<p>From a blogger&#8217;s perspective, this irreversible change has some serious implications:</p>
<ol>
<li>Email subscriptions have never been more important. Unlike Facebook subscribers or Twitter followers who will rarely see your updates, emails are still being read and given a certain importance by the subscriber (Google is trying to mess this up too, but that&#8217;s a whole other post). You need to capture people&#8217;s email as it&#8217;s the only guaranteed delivery method for your updates that you have. (On that note, you can <a href="https://eepurl.com/dz44T" target="_blank">subscribe here</a>.)</li>
<li>Feel free to maximize your social media properties and efforts, engage and entertain users, but have an email subscription as your ultimate call to action.</li>
<li>For the sake of us geeks who are unwilling to give up the good fight, do be sure to prominently feature an RSS feed link/button on your blog or site.</li>
<li>If your audience is not technical, consider having a &#8216;How to follow this blog&#8217; link with step-by-step instructions on using Feedly or <a title="Bloglovin" href="https://www.bloglovin.com/" target="_blank">Bloglovin</a> (the latter of which is particularly popular among women).</li>
</ol>
<p>It&#8217;s an unfortunate turn of events that has damaged blogging in an untold number of ways. Thankfully, it hasn&#8217;t killed things off entirely though, especially if we are willing to adapt.</p>
<p>The post <a href="https://technicalblogging.com/google-killed-the-rss-feed/">Google Killed the RSS Feed</a> appeared first on <a href="https://technicalblogging.com">Technical Blogging</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://technicalblogging.com/google-killed-the-rss-feed/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">328</post-id>	</item>
	</channel>
</rss>
