Google’s recent mobile friendly update gave brands a big reason to optimise for mobile, but is it being tough enough?
There are plenty of sites which are just part-mobile. They may have mobile friendly homepages and other pages, but will often switch users to desktop pages which do not work well on mobile.
Here are some examples…
Barclays is a good example of this. If you search for Barclays, it looks like the site satisfies Google, with the ‘mobile friendly’ label under the URL.
So, as a user, you enter the site assuming it will work on your device, expecting a good user experience
Sure enough, the homepage is mobile optimised. It’s well laid out and easy to navigate to the various sections of the site. So far, so good.
The problem is that once you navigate away from the homepage, this mobile ‘friendliness’ ends.
This applies to all of the sections you can reach via the hamburger menu, including loans, mortgages, banking, insurance, and help and support. The most popular sections of the site.
Here’s how the mortgage pages look. Not much help for mobile users. The savings pages on the right is similar, virtually impossible to use on a mobile:
Google’s mobile friendly tool identifies this savings page as not mobile friendly and explains why. Neither are labelled as mobile friendly in search results.
Barclays also ranks below many of its competitors, including Santander and Nationwide for ‘savings’ and related, though it does still rank in the top ten for ‘mortgages’, despite the page.
We can see that, post mobile algorithm, many of its savings and other non-mobile pages have dropped in the SERPs:
So, from an SEO perspective, Barclays has a clear incentive to provide more than just a mobile-friendly homepage. It has dropped in the SERPs already, and competitors with proper mobile sites stand to benefit.
However, it’s clear that there is no such thing as a Barclays mobile site, just a few mobile friendly pages with provide a thin veneer over a desktop site.
It’s also bad for users, as finding out more about mortgages, savings or other products is a very frustrating experience on a mobile device.
This is another example. As we can see, Google has marked it as mobile friendly.
The pages are mobile optimised as well, to a point. Product pages are easy to view on mobile:
However, if you click that buy now button, the mobile friendliness ends. The product selection and checkout pages are desktop versions.
This sudden switch from mobile to desktop is quite jarring for the mobile user, and won’t do anything to help Apple’s conversion rates.
In fact, for a company renowned for the usability of its products, and one that is sitting on huge piles of cash, it seems very odd that it create a decent end to end user experience for mobile shoppers.
I think these examples highlight a problem with Google’s mobile friendly labels.
Though Google is labelling on a page by page basis, they do give an impression to users that sites are mobile friendly.
It’s perhaps more of an issue with sites like Barclays. Given that all of the main product sections on Barclays are distinctly unfriendly to mobile users, does it deserve any kind of mobile friendly label?
The label gives users the impression that the site will be easy to use, but in reality it’s just a thin veneer of mobile friendliness.
Apple is slightly different, as much of the site is mobile optimised, it just changes when customers want to buy something. It’s still not a great user experience though.
The main point here is that sites should be fully mobile. If you want to attract customers, show them your products, and acquire customers, the mobile experience should not be neglected.
With its growing focus on UX as a ranking factor, Google is looking to reward sites that provide excellent mobile experiences for users.
By labelling ‘part-mobile’ sites as mobile friendly, it is rewarding some that are failing mobile users.
As Bryson Meunier writes in Search Engine Land, this latest mobile update is just the beginning. Google may look to changes its algorithm and labelling to deal with sites like this in future.