Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php on line 11

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/webig9mf/public_html/blog/wp-content/themes/biscayalite/inc/nav.php:11) in /home1/webig9mf/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":307,"date":"2016-02-10T04:22:34","date_gmt":"2016-02-10T04:22:34","guid":{"rendered":"http:\/\/webigg.com\/blog\/?p=307"},"modified":"2018-12-10T05:36:26","modified_gmt":"2018-12-10T05:36:26","slug":"google-algorithm-updates-history-part-5","status":"publish","type":"post","link":"https:\/\/www.webigg.com\/blog\/google-algorithm-updates-history-part-5\/","title":{"rendered":"Google Algorithm Updates History \u2013 Part 5"},"content":{"rendered":"

Each year Google changes its search algorithm hundreds of times. While most of these changes are minor, every few months Google rolls out a “major” algorithmic update that affects search results in a significant way.<\/p>\n

For search marketers, knowing the dates of these Google algorithm updates can help explain fluctuations in rankings and organic website traffic. Below, we’ve listed the history of Google’s algorithm changes that had the biggest impact on search results. Understanding these updates can be critical to search engine optimization.<\/p>\n

Top Heavy 3 Update<\/h3>\n

FEBRUARY 06, 2014<\/strong><\/p>\n

Google’s Page Layout Algorithm targets pages with disproportionate number of ads above the fold in relation to page content.<\/p>\n

Google’s Matt Cutts confirmed this\u00a0algorithm refresh\u00a0in a Tweet.<\/p>\n

Page Layout Algorithm’s goal is to make users’\u00a0search experience\u00a0more efficient and quick, enabling them to reach the content they’re seeking.<\/p>\n

Penguin Update 5 (ref 2.1)<\/h3>\n

OCTOBER 04, 2013<\/strong><\/p>\n

Penguin 2.1 (Penguin 5th edition) was released in Google’s continuing battle against web spam. We see a corresponding spike in the Rank Risk Index on October 5th.<\/p>\n

Search Engine Journal reports:\u00a0Penguin 2.1: What Changed Since 2.0, and How to Recover<\/p>\n

Hummingbird Update<\/h3>\n

AUGUST 21, 2013<\/strong><\/p>\n

Hummingbird, released around August 21st, is a new search algorithm that Google developed with a focus on Semantic Search. Their goal is to provide more personalized results based on your online behavior, location, trends, etc.\u00a0 The Rank Risk Index (RRI) captured this significant change on August 21st.<\/p>\n

Panda Update 26<\/h3>\n

JUNE 28, 2013<\/strong><\/p>\n

As Google was either testing or rolling out the new multi-week algorithm update that Matt Cutts mentioned on Twitter, the Rank Risk Index soared into the danger zone. This update targets websites with low quality content.\u00a0Although some sources report that Google released an update on June 18th, our Risk Index indicates that the affects of this update were strongest on the 28th.<\/p>\n

This is a good time to revisit Search Engine Land’s SEO Guide that outlines and provides possible responses to\u00a0Violations & Search Engine Spam Penalties<\/p>\n

Penguin Update 4 (ref 2.0)<\/h3>\n

MAY 22, 2013<\/strong><\/p>\n

Newer generation Penguin enables Google to dig deeper into sites for web spam\u00a0according to Google’s Matt Cutts\u00a0a few hours before this release. The update will have a greater impact on SEO and webmasters.<\/p>\n

Read more in\u00a0Search Engine Land’s announcement of Penguin 2.0.<\/p>\n","protected":false},"excerpt":{"rendered":"

Each year Google changes its search algorithm hundreds of times. While most of these changes are minor, every few months Google rolls out a “major” algorithmic update that affects search results in a significant way. For search marketers, knowing the dates of these Google algorithm updates can help explain fluctuations in rankings and organic website […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[19,13,17,31,18],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts\/307"}],"collection":[{"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/comments?post=307"}],"version-history":[{"count":1,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts\/307\/revisions"}],"predecessor-version":[{"id":308,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts\/307\/revisions\/308"}],"wp:attachment":[{"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/media?parent=307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/categories?post=307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/tags?post=307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}