Google Turns Up the Mobile-Friendly Signal Again

Posted by Sean on May 18, 2016

Google finished rolling out its stronger mobile-friendly ranking signal last week. They flagged it back in March, said it would start in May, and on the 12th confirmed it was fully live. Compared with the fuss around the original mobile-friendly update last April, it has barely made a ripple.

That’s mostly because, for a lot of sites, nothing happened. If you passed Google’s mobile-friendly test last year, you still pass it, and Google said as much in the announcement: pages that are already mobile-friendly aren’t affected. The boost only widens the gap between pages that pass and pages that don’t.

So in one sense this is a non-event, and I’m tempted to leave it there. But I think it’s worth a few minutes, because “mobile-friendly” in Google’s sense is a pretty low bar, and an ecommerce site can clear it while still being painful to use on a phone.

What the test actually checks

The mobile-friendly test is looking at a handful of basics:

  • Is the viewport set so the page fits a phone screen?
  • Is the text readable without zooming?
  • Are links and buttons far enough apart to tap?
  • Is there any content that needs Flash or other plugins phones don’t support?

Pass those and you get the label. None of them asks whether someone can actually find a product, look at it properly and buy it on a phone without giving up.

Where ecommerce sites still fall down

These are the problems I see most often, including on sites that sail through the test:

  1. Slow product pages. Heavy images, a dozen third-party scripts, a carousel nobody asked for. The page is “mobile-friendly” and takes eight seconds to become usable on 3G.
  2. Filters built for a mouse. Category pages with long lists of checkboxes and sliders that are fiddly with a thumb, and that reload the whole page after every tap.
  3. Forms that fight the keyboard. Phone number fields that bring up the letter keyboard, postcode lookups that don’t work, no autofill. Checkout is where this hurts most.
  4. Interstitials. The full-screen “download our app” or newsletter overlay that greets you before you’ve seen anything. Google already dealt with app-install interstitials last year by removing the mobile-friendly label from pages that use them, and I wouldn’t bet on newsletter pop-ups being left alone forever.
  5. Desktop content hidden on mobile. Tabs, accordions or simply missing sections. Sometimes it’s the right call for space, sometimes it’s the product detail the customer actually needed.

In luxury that last one matters a lot. A phone visitor looking at an expensive watch still wants the specification, the condition notes and the warranty information. I’d rather have a long mobile page than a tidy one missing the information someone needs before spending that much.

What I’d do this month

Honestly, the boost itself isn’t a reason to do anything urgent. If any of your templates fail the test, fix them, obviously; you’re now being penalised a bit more for it. If they pass, I’d use the moment as an excuse to test the site properly on real phones rather than in a desktop browser shrunk down to phone size.

Pick your three most important journeys, say landing on a product from search, using a category filter, and checking out, and do each one on a mid-range Android phone on mobile data. Not the latest iPhone on the office wifi. Time them. Note every moment you have to pinch, zoom or tap twice.

That list will be far more useful than anything the mobile-friendly test tells you. And given how much of our traffic is now on phones, the direction Google keeps nudging in is pretty clear: today it’s a label and a small boost, and I expect mobile to count for more in how sites are judged over the next year or two. I want our own journeys tested that way before the summer.

← Previous Draft Draft Index Next Draft →