Home » Watch Out: Mobilegeddon Is Coming

Watch Out: Mobilegeddon Is Coming

Come April 21, Google will start using a website’s mobile friendliness as a ranking signal in search results. Coined as ‘Mobilegeddon’ or ‘Mobileapocalypse’, the search engine magnate dialed up its pressure button for businesses that want to stay on top the game. When you have a mobile-friendly site, it will get a boost, while sites with usability issues on mobile devices, will get a significant drop in rankings, thus the need to update.
Since Google’s announcement, there have been observations in an increase in demand for mobile-related design and development skills to help companies with the changes and updates needed, which basically is a no surprise knowing that there is no business exempted from this change and will gradually affect mobile searches in all languages worldwide. According to Venturebeat.com, 80% of all adults now own a smartphone and come 2016, 2 billion people are expected to get them, worldwide. Clearly, mobile matters more than ever!
Game-face On for Mobileapocalypse
In a recent Q&A, Gary Illyes from Searchenginewatch.com shared a few details about Google’s announcement. Developers should take note that a responsive design does not a have a ranking benefit and that Googlebot must be allowed to crawl CSS & Javascript to pass the ‘mobile-friendly’ test. Moreover, mobile friendliness is determined at the page level and not sitewide. However, tablets will not be affected by the update. Illyes also shared that Google is currently working on a dedicated mobile index for a smooth workflow.
The question is, are you really prepared for the update? Well, if you find yourself scrambling to be mobile-friendly and indecisive between a dedicated mobile or responsive design, you might want to weigh in the pros and cons before making such decision. However, you have to think about your search rankings if your main goal is to increase leads and not flunk.
On a lighter note, here are a few steps to consider ensuring that your site does not fall prey to Mobilegeddon:
Test your site. There is no other way to know it firsthand but this. By viewing your site’s listing in Google search results; you should see a “mobile-friendly” tag beneath your URL, which is a very legit proof that your site is spared from the incoming dilemma. However, it won’t be a ticket to exemption if you won’t keep some features updated. To know if your site is mobile-friendly, you may want to enter your web page URL in Google’s Mobile-Friendly Test to see how well it performs on a mobile device. Again, if it fails, you have to take action in updating it. If it passes, it may still need improvements before finally earning the ‘mobile-friendly’ tag. For a full rundown on issues that may affect your site’s search ranking, you may test it on Google’s PageSpeed Insights.
Learn what comprises mobile-friendly. In order for a page to gain Google’s ‘mobile-friendly’ thumbs up, it should do the following:

  • Readable text and font without zooming
  • Users don’t have to scroll on the page horizontally or zoom in order to read, hence the need of its size content should fit the screen
  • Avoids software that is not necessarily supported on mobile devices. One example is Flash.
  • Has considerable amount of space on links that the correct one can be easily tapped

Identify the correct fix for your site. With Google’s Mobile-Friendly Test and PageSpeed Insights, they have provided specific details for your site’s issues, and all you have to do is to check some options that are available to address them.
To gain a mobile-friendly site, it must be configured in one of the aforementioned ways:

  • Responsive web design. This one is Google’s recommended option, where a responsive site uses the same HTML and URL across devices and render the appropriate display for the user’s device through CSS
  • Dynamic serving: This configuration involves using the same URL but a different version of HTML to serve different device types.
  • Separate URLs: This is a method that serves a different code to different devices using separate URLs, by employing HTTP redirects.

You need to ensure that Google sees it that way by signaling its mobile configuration. Doing so may vary the process by configuration. An example of which s if you have a responsive page, you need to add a “meta viewport” tag to the head of the document to signal to the browser how to adjust the page for different screen sizes, and so on.
You would also want to make sure that Google’s algorithms could crawl your pages. Allow Googlebot to acess your pages and its assets such as JavaScript, CSS and image files). You may refer to Google’s Mobile Friendly guide to see details and other pitfalls to avoid.
The following options may include if your site was built on a CMS like WordPress:

  • Converting your existing site to a new mobile-friendly theme
  • Creating a new mobile-friendly version of your site, keeping your desktop site the same
  • Customizing your site to make it mobile-friendly yet may require CSS and HTML knowledge

Before making any changes and updating everything, be sure to back things up. You don’t want to mess around, wouldn’t you? For more details on your options, you may consult guides from both Google and your CMS provider.
Make it a priority. Mobilegeddon is really coming so do it now, not later. Mobile usability will be an important factor, as a ranking signal for search results, in where your site shows up in search results on mobile devices, allowing you to gain higher chances of visibility come April 21. In addition to that, you will be able to deliver better search experience to the growing number of mobile users and your potential customers in the future.

Optimind Logo

Digital Marketing agency with focus on Social Media, SEO, Web Design, and Mobile Development

Google Partner
Dot PH

Contact

Optimind Technology Solutions

2nd Flr CTP Building
Gil Fernando Avenue
Marikina City
Manila 1803 Philippines

+(63) 2 86820173
+(63) 2 86891425
+(63) 2 77394337
Australia - +(61) 2 80050168
Los Angeles, CA - +19092722457

function my_function() { ?>