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":924,"date":"2017-09-06T05:35:24","date_gmt":"2017-09-06T05:35:24","guid":{"rendered":"http:\/\/webigg.com\/blog\/?p=924"},"modified":"2018-12-07T11:13:25","modified_gmt":"2018-12-07T11:13:25","slug":"new-unconfirmed-google-ranking-update-fred-shakes-the-seo-world","status":"publish","type":"post","link":"https:\/\/www.webigg.com\/blog\/new-unconfirmed-google-ranking-update-fred-shakes-the-seo-world\/","title":{"rendered":"New, unconfirmed Google ranking update \u2018Fred\u2019 shakes the SEO world"},"content":{"rendered":"

The webmaster and SEO community, along with the automated Google tracking tools, all show strong signs that there was a Google algorithm ranking update.<\/p>\n

Since yesterday morning, the SEO industry has been watching an unconfirmed Google ranking update that seems to target more of the link quality aspects of the overall algorithm.<\/p>\n

Many are calling this the Fred Update, a name we\u2019re also adopting. That came from Google\u2019s Gary Illyes, who has jokingly suggested that all updates be named \u201cFred.\u201d It\u2019s sticking with this one.<\/p>\n

We\u2019ve seen more chatter and reports of changes from within the \u201cblack hat\u201d SEO community, which generally means that this is a spam algorithm update around links. Last time we reported a link spam-related update was in early February, and that update also was unconfirmed by Google.<\/p>\n

There was also a large content quality Google update on February 7 that was never confirmed. As you expect, Google is very unlikely to confirm algorithm updates these days \u2014 but that won\u2019t stop us from reporting large shifts in the search results that convey an algorithm update has happened.<\/p>\n

Many of the automated tracking tools currently show significant volatility and fluctuations, which is an indicator of an update. Plus, with all the industry chatter, and with webmasters both complaining about ranking declines and rejoicing about ranking increases, it\u2019s likely that there was a Google update.<\/p>\n

We are waiting to hear from Google if they have any comment. All we have right now are the typical Google lines from John Mueller and Gary Illyes that Google makes updates all the time.<\/p>\n

Report: 57% of traffic now from smartphones and tablets<\/strong><\/h5>\n

It\u2019s been a little over two years since Google first announced that mobile searches had exceeded desktop queries on a global basis. That number has continued to grow, although the company has not provided an official update recently.<\/p>\n

At a recent press event, a Google speaker casually said that the \u201cvast majority\u201d of search queries are now mobile. However, this is not official and wasn\u2019t affirmed by spokespeople.<\/p>\n

In the absence of official updates from Google and Bing, third parties have offered a range of statements on the question of mobile search and mobile traffic volumes vs. the desktop. For example, earlier today, BrightEdge reported that 57 percent of traffic among its clients is coming from smartphones and tablets.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

The webmaster and SEO community, along with the automated Google tracking tools, all show strong signs that there was a Google algorithm ranking update. Since yesterday morning, the SEO industry has been watching an unconfirmed Google ranking update that seems to target more of the link quality aspects of the overall algorithm. Many are calling […]<\/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\/924"}],"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=924"}],"version-history":[{"count":1,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts\/924\/revisions"}],"predecessor-version":[{"id":925,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/posts\/924\/revisions\/925"}],"wp:attachment":[{"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/media?parent=924"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/categories?post=924"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webigg.com\/blog\/wp-json\/wp\/v2\/tags?post=924"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}