Google doesn’t usually tell us when an algorithm change is coming, let alone give us a date. Yesterday it did both. From 21 April, mobile-friendliness becomes a ranking signal in mobile search results, worldwide and in all languages. In Google’s own words on the Webmaster Central blog, the change will have a “significant impact” on search results.
That phrase is the bit that got my attention. Google is normally careful to describe these things as small, or affecting a fraction of queries, the way it did with HTTPS last summer. Choosing to say “significant”, with eight weeks’ notice, reads to me like a deliberate warning shot.
What was actually announced
Two things, really.
- Mobile-friendliness as a ranking signal. From 21 April, sites that work properly on phones will get a boost in mobile search results. Sites that don’t will lose ground to those that do.
- App indexing as a ranking factor. For signed-in users who have an app installed, content from indexed apps will start showing more prominently. This is already live, and matters mostly to bigger brands with apps.
The first one is the one that matters to nearly everyone.
What it doesn’t say
I’ve already seen some panicky takes, so here’s what it doesn’t mean.
It applies to mobile search results. Desktop rankings aren’t part of this announcement. If most of your organic traffic still comes from desktop, you have time, though I wouldn’t bet on that split lasting.
As far as Google has explained it, it’s assessed page by page, not across the whole site. A site with some mobile-friendly sections and some that aren’t should see the effect on the pages that fall short, rather than everything at once.
And it is not a test of whether your site is beautiful on a phone. It’s a fairly mechanical check. Google has had a Mobile-Friendly Test tool out since November, alongside the “mobile-friendly” label in search results, so you can see what it thinks of a page right now.
What I’d check before April
If I were running a site with any meaningful mobile search traffic, this is the order I’d work through:
- Run your key templates through the Mobile-Friendly Test. Not every page; one of each type. Home page, category, product or service page, blog post, contact page. If a template fails, every page built on it fails.
- Look at the Mobile Usability report in Webmaster Tools. It lists the specific problems Google has found across the site: text too small to read, links too close together, content wider than the screen, no viewport set.
- Check you aren’t blocking CSS and JavaScript in robots.txt. This is one people miss. If Googlebot can’t load your stylesheets it can’t tell that your responsive design is responsive, and a perfectly good site can fail the test.
- Find out what share of your organic traffic is mobile, and which pages it lands on. That tells you how much is at stake and where to start.
- Sort out separate mobile sites. If you run an m-dot site, make sure the redirects send people to the equivalent page, not dumping everyone on the mobile home page, and that the annotations between the two versions are in place.
If the honest answer to step one is that the site was never built for phones at all, eight weeks isn’t long. A full responsive rebuild isn’t going to happen by April on most budgets. In that case I’d prioritise the templates carrying the most mobile search traffic and patch those, then plan the rebuild properly.
My read on it
I suggested in December that mobile would stop being a separate conversation this year. I didn’t expect Google to make the point quite this bluntly, quite this quickly.
There’s a slightly cynical reading, which is that Google wants the mobile web to be good because mobile is where its ad revenue is heading, and it would rather sites fixed themselves than users drifted off into apps. I think that’s probably true. It doesn’t change the advice. If a site doesn’t work on a phone, the people visiting it on phones have been having a bad time regardless of where Google ranked it. All that’s changed is that there’s now a date.
I’ll be watching what happens after the 21st with interest, and I expect a fair few sites will be scrambling in the last week of March.