The next Google slap could be a doozy -- Coming April 21, 2015
Well Google is at it again. Previously they said they "recommend" certain ways for a website to be coded for mobile friendly use. However, they never clearly stated this would be a ranking factor. Websites being "mobile friendly" have always been more of a usability discussion. That has all changed now with Google's Feb. 26th blog publication here. What do you need to pay very close attention to? This, "Starting April 21, we will be expanding our use of mobile-friendliness as a ranking signal. This change will affect mobile searches in all languages worldwide and will have a significant impactin our search results." In other words, if you see your website or your clients website in the search results on your mobile phone and it does not say "mobile friendly" beside it, then you have a HUGE issue. Chances are you will fall off the map for any search engine results performed by mobile users. What does this mean? This means that if a website currently has 50% of their traffic coming from mobile users and they do not have a "mobile friendly" website then come April 21st they might lose 50% of their traffic. This is not an over reaction, this is real. When Google gives a date and describes the impact as "significant" ... one can naturally interpret that to mean they will give nearly any result that is "mobile friendly" a preference over those whom are not. Mobile friendly is established by Google not the user. So you may look at a website and think it is mobile friendly but Google might not. You might have a mobile responsive website but Google does not interpret it as being "mobile friendly". |
-
iAmNameLess -
Thanks
SignatureThe Best Damn Marketing and Local SEO BlogUltimate Blueprint To Start Your Own Agency | Get Clients Without Cold Calling{{ DiscussionBoard.errors[9931178].message }} -
-
MrErickson -
Thanks - 1 reply
{{ DiscussionBoard.errors[10086038].message }}-
savidge4 -
[ 4 ] Thanks
SignatureSuccess is an ACT not an idea{{ DiscussionBoard.errors[10086053].message }} -
-