Many business owners remember "Mobilegeddon" in 2015, but very few remember what happened a year later. A common belief is that Google flipped one big mobile switch and that was the end of it. In reality, Google came back in May 2016 and turned the volume up on the same signal.
This second mobile-friendly update was quiet. There were no dramatic traffic charts and no big list of losers. But it matters because it shows how Google prefers to change behavior: announce early, judge each page on its own, and keep raising the bar until the whole web moves. That pattern led straight to mobile-first indexing.
Let me explain what Google announced, what the boost actually did, why it was not "Mobilegeddon 2," and what a sensible mobile check looks like today now that Google's old testing tools are gone. If you want to see where this update sits among all the others, our Google algorithm updates timeline lists every change in order.
The May 2016 mobile boost at a glance
| Item | Detail |
|---|---|
| Announced | March 16, 2016, on the Google Webmaster Central blog |
| Fully rolled out | May 12, 2016 (confirmed by John Mueller) |
| Type | Strengthening of an existing ranking signal (mobile-friendliness) |
| Confirmed by Google? | Yes, pre-announced and confirmed when complete |
| Scope | Mobile search results; assessed page by page |
| Who was affected | Pages that failed Google's mobile-friendly criteria; already mobile-friendly pages were not expected to see any effect |
| Predecessor | April 21, 2015 mobile-friendly update ("Mobilegeddon") |
| What came next | Mobile-first indexing, page experience signals |
What Google said in its March 2016 heads-up
On March 16, 2016, Google published a short post called Continuing to make the web more mobile friendly. It was written by Klemen Kloboves, a Google software engineer, and its message was simple: starting in May, Google would strengthen the mobile-friendly ranking signal it had launched the year before.
Search Engine Land's Barry Schwartz covered the announcement the same day and quoted the key line:
“increases the effect of the ranking signal to help our users find even more pages that are relevant and mobile-friendly.”
— Google, as quoted by Search Engine Land (now MarTech), Google to boost the mobile-friendly ranking factor in May 2016
Three details in that announcement are worth noticing, because they shaped how the update played out:
- Two months of notice. Google gave site owners roughly eight weeks to fix their pages before the change landed. That is the same playbook it used in 2015, when the original update was announced in February and launched in April.
- No action needed for mobile-friendly sites. If your pages already passed, Google said there was nothing to do. This was a stick only for pages that had ignored the first update.
- Relevance still came first. Google repeated that a page with strong content could still rank on mobile even if it was not mobile-friendly. In Google's words, reported by Search Engine Land, "even if a page with high quality content is not mobile-friendly, it could still rank well."
Search Engine Journal's history of the update also records Google's framing line from the post: "Getting good, relevant answers when you search shouldn't depend on what device you're using." That sentence explains the whole program in one breath.
What "boosting the signal" actually meant
A ranking signal is just one piece of information Google uses when it orders results. In 2015, Google added a simple one: is this page mobile-friendly, yes or no? Pages that said yes got a small lift in mobile results compared with pages that said no.
In May 2016, Google made that lift bigger. The yes/no test itself did not change. What changed was how much weight the answer carried when Google compared two pages for the same mobile search.
Here is a simple way to picture it. This is a hypothetical example, not real Google math:
| Example page | Relevance to query | Mobile-friendly? | Likely effect after May 2016 |
|---|---|---|---|
| Page A: plumber's responsive site | Good | Yes | Unchanged or slightly better, as weaker rivals slip |
| Page B: plumber's old desktop-only site | Good | No | More likely to slip below Page A on phones |
| Page C: the only detailed guide on a rare topic | Excellent, best match | No | Could still rank well, because relevance outweighs the signal |
| Page D: thin page | Weak | Yes | Mobile-friendliness does not rescue a page that does not answer the query |
In brief: the signal acted like a tie-breaker that got heavier. When two pages were close in relevance, the mobile-friendly one won more often. When one page was clearly the better answer, it still won.
Why Google judged each page on its own
One detail that confused people in both 2015 and 2016 was that the signal was page-level, not site-level. Google looked at each URL separately. A site could have a mobile-friendly homepage and a dozen old desktop-only landing pages, and only those old pages would carry the disadvantage.
That also meant the update did not land on a site all at once. Search Engine Land explained that because the signal is assessed page by page, the full effect depends on how quickly Google recrawls and reindexes each site's pages. A page Google visited daily would be re-scored quickly. A deep page Google visited once a month might take weeks.
The good news in that design was that fixes counted fast too. Once you made a page mobile-friendly and Google recrawled it, that page could benefit. There was no waiting for the "next update."
In 2016, a page generally failed the test for reasons like these:
- No viewport meta tag, so phones showed a shrunken desktop layout.
- Content wider than the screen, forcing sideways scrolling.
- Text too small to read without zooming.
- Links and buttons too close together to tap accurately.
- Plugins such as Flash that most phones could not run.
Why it was not "Mobilegeddon 2"
When the rollout finished, the obvious question was whether this was another big shake-up. John Mueller, then a Google Webmaster Trends Analyst, answered on Twitter. Search Engine Land recorded both his completion notice and his reply:
“The mobile changes mentioned here are now fully rolled out.”
— John Mueller (Google), as reported by Search Engine Land, Google's mobile-friendly algorithm boost has rolled out
Asked whether this was "mobilegeddon 2," he replied: "No, not really." I think he was right, and there are four plain reasons:
- Most active sites had already fixed their pages. The 2015 update had pushed a huge wave of responsive redesigns. By 2016, the pool of pages still failing the test was much smaller.
- The test was binary and public. Anyone could check a page in Google's tool. There was little mystery about who would be affected.
- Google gave notice again. Search Engine Journal noted that reaction was calmer than for Panda or Penguin, largely because of the advance warning and the clear yes/no criteria.
- It was a nudge, not a new system. Google adjusted the weight of something that already existed. Nothing new was being measured.
Even the 2015 update had a smaller measured impact than its nickname suggested. SEJ's history notes that Moz's mobile-only tracker recorded a peak "temperature" of 79.8°F on April 22, 2015, which is noticeable but far from the storms seen during big core updates. If you want the full story of the first update, I cover it in Mobilegeddon (2015) in context.
Where the 2016 boost sits on the road to mobile-first indexing
The boost also did not arrive alone. A few months earlier, Google had launched AMP pages in mobile search (February 2016), and in March it retired Toolbar PageRank. 2016 was clearly a year of Google cleaning up old habits and pushing everyone toward phones.
Looking back, May 2016 was a middle step. Google was moving from "mobile pages get a small bonus" to "the mobile page is the page." Here is the sequence as I see it:
| Date | Change | What it meant for site owners |
|---|---|---|
| April 2015 | First mobile-friendly ranking signal | Mobile-friendly pages get a lift in mobile results |
| May 2016 | Signal strengthened | The lift gets heavier; laggards lose more ground |
| January 2017 | Intrusive interstitials penalty | Mobile pages covered by aggressive pop-ups could rank lower |
| July 2018 | Speed Update | Very slow pages could rank lower in mobile search |
| 2018 onward | Mobile-first indexing rollout | Google indexes and ranks using the mobile version of a page |
| 2021 | Page experience update | Mobile-friendliness folded into a wider set of page experience signals |
| December 2023 | Mobile-Friendly Test and Mobile Usability report retired | Site owners move to Lighthouse and real-device checks |
Each step is covered on our site: the intrusive interstitials penalty, the 2018 Speed Update, the mobile-first indexing rollout and the 2021 page experience update.
The big shift is mobile-first indexing. Google's own documentation now says it plainly: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." In 2016, a weak mobile page cost you a ranking bonus. Today, a weak mobile page is what Google judges. If your mobile version hides content that your desktop version shows, Google may not see that content at all. Google's mobile-first indexing guide asks you to "Make sure that your mobile site contains the same content as your desktop site."
How the mobile signal lives on inside page experience
You will not find a "mobile-friendly ranking system" in Google's current list of ranking systems. That does not mean mobile no longer matters. It means Google now talks about it as part of a bigger idea: page experience.
Google's page experience documentation says: "There is no single signal. Our core ranking systems look at a variety of signals that align with overall page experience." Among its self-assessment questions are these three, which are the grown-up version of the 2016 test:
- "Does your content display well on mobile devices?"
- "Do your pages avoid using intrusive interstitials?"
- "Do your pages have good Core Web Vitals?"
I suggest you read this honestly. Google also says good Core Web Vitals scores do not guarantee top rankings. Page experience is still mostly a tie-breaker, just like the mobile signal in 2016. We go deeper on this in where page experience stands as a ranking signal today.
A mobile check you can run today without Google's old test
For years, the standard advice was "run it through the Mobile-Friendly Test." That tool is gone. Search Engine Land reported that Google retired the Mobile-Friendly Test, its API and the Search Console Mobile Usability report on December 1, 2023, pointing people to other tools instead:
“many other robust resources for evaluating mobile usability have emerged, including Lighthouse from Chrome.”
— Google, as quoted by Search Engine Land, Google officially drops Mobile Usability report, Mobile-Friendly Test tool and Mobile-Friendly Test API
Here is how I would check a small business site today. It takes about an hour for a 20-page site:
- List your money pages. Pull the top 20 landing pages by mobile clicks from the Performance report in Search Console, filtered to the Mobile device.
- Open each on a real phone. Not a resized desktop browser. Check that text is readable without zooming, nothing scrolls sideways, and buttons are easy to tap.
- Run Lighthouse. In Chrome DevTools, run a mobile Lighthouse report on your three most important templates (home, service or product, blog post). Note anything flagged under accessibility and best practices, such as tap targets or font sizes.
- Check Core Web Vitals. Open the Core Web Vitals report in Search Console and look at the Mobile tab. Remember that INP replaced FID in March 2024.
- Compare mobile and desktop content. Make sure headings, body text, images, structured data and internal links on mobile match desktop. Hidden tabs are fine; missing content is not.
- Look for pop-ups. Load each page fresh on a phone. If a pop-up covers the main content as soon as you arrive, fix it.
- Use URL Inspection. Inspect a couple of key URLs in Search Console and view the crawled page to confirm Googlebot Smartphone sees what you expect.
Here is a worked example with made-up numbers. Say a dental clinic site has 40 pages. Search Console shows 70% of its clicks come from phones. A real-phone review finds that 6 older service pages still use a fixed-width table that forces sideways scrolling, and Lighthouse flags small tap targets on the booking form. Fixing those 6 templates and the form is a one-week job, and those pages carry most of the phone traffic. That is where I would start, before chasing a perfect Lighthouse score on the blog. If you are new to these ideas, our free lesson on mobile-first indexing covers the basics, and the mobile SEO guide covers the wider checklist.
What the 2016 boost still teaches about Google's habits
I find this little update useful because it shows how Google tends to behave with any user-experience signal:
- Google warns first, then tightens. Mobile-friendliness, HTTPS, interstitials, page experience: all followed the same path of announcement, small signal, then a stronger push.
- Relevance still wins. In 2016 and today, a great answer on a clunky page can outrank a pretty page with nothing to say.
- Page-level problems need page-level fixes. One good template does not cover the forgotten landing pages from 2014.
- Tools change; the question does not. The test was retired, but "does this page work well on a phone?" is still the question to ask.
Questions people still ask about the 2016 mobile-friendly update
Was the May 2016 mobile update a penalty?
No. It strengthened a positive ranking signal for mobile-friendly pages in mobile search. Pages that failed the test lost ground relative to pages that passed, but nothing was removed from the index and there was no manual action involved.
Did the 2016 update affect desktop rankings?
Google described it as a change to mobile search results, the same scope as the April 2015 update. Desktop results were not the target.
Could a page that was not mobile-friendly still rank well after May 2016?
Yes. Google said that a page with high-quality content that is not mobile-friendly could still rank well if it was the best match for the query. Mobile-friendliness was one signal, not a gate.
Can I still run Google's Mobile-Friendly Test?
No. Google retired the Mobile-Friendly Test, its API and the Search Console Mobile Usability report on December 1, 2023. Lighthouse in Chrome and a real phone are the practical replacements.
Is mobile-friendliness still a ranking factor in 2026?
Not as a separate yes/no system. Google now talks about page experience as a set of signals its core ranking systems look at, and one of its self-assessment questions is whether your content displays well on mobile devices. With mobile-first indexing, your mobile page is also the version Google indexes.
Making sure your mobile pages would pass any version of this test
The 2016 boost hit only pages that had ignored the first warning. The lesson for today is not about a decade-old update. It is about not leaving old templates, landing pages or pop-ups behind while the rest of your site moves on. Under mobile-first indexing, your phone experience is your site as far as Google is concerned.
If you would like a second pair of eyes on your mobile templates, speed and page experience, our team can help. Take a look at our page speed optimization and SEO services, or simply ask us for a free quote and we will tell you where to start.
Google updates around the same time
Before this update:
- Google Retires Toolbar PageRank (March 2016): The End of a Public Metric (Mar 2016)
- AMP in Google Mobile Search (February 2016): The Top Stories Carousel Arrives (Feb 2016)
After this update:
- The Possum Update (2016): Local Filtering Changes Explained (Sep 2016)
- Penguin 4.0 (2016): Real-Time Penguin and Link Devaluation (Sep 2016)
Or browse every Google update on one timeline, newest first.
Sources for this 2016 mobile-friendly update article
- Google Search Central Blog: Continuing to make the web more mobile friendly (March 2016)
- Search Engine Land / MarTech: Google to boost the mobile-friendly ranking factor in May 2016
- Search Engine Land: Google's mobile-friendly algorithm boost has rolled out
- Search Engine Journal: Google's mobile-friendly update (algorithm history)
- Wikipedia: Timeline of Google Search
- Google Search Central: Mobile site and mobile-first indexing best practices
- Google Search Central: Understanding page experience in Google Search results
- Search Engine Land: Google officially drops Mobile Usability report, Mobile-Friendly Test tool and API
