The Google Mobile-Friendly update, nicknamed “Mobilegeddon”, began on 21 April 2015 and expanded mobile-friendliness as a ranking signal in mobile search results, worldwide and in all languages, judged page by page. Desktop rankings were not touched, and a second boost followed on 12 May 2016. If your mobile traffic sagged while desktop held steady, this is the pattern to check, and the fix is to make each page genuinely usable on a phone. It is one of the earliest announced updates in my full list of Google algorithm updates.
| Detail | Information |
|---|---|
| Update name | Google Mobile-Friendly Update (Mobilegeddon) |
| Type | Mobile ranking signal |
| Rollout started | 21 April 2015 (announced 26 February 2015) |
| Rollout finished | Not announced; per-page effects appeared as pages were recrawled |
| Rollout length | Not announced |
| Confirmed by Google | Yes, announced in advance on the Google Search Central (then Webmaster Central) blog |
| Official source | Google Search Central Blog, February 2015 |
What the Mobile-Friendly update changed
Google gave about two months’ notice, which was unusual. Its February 2015 post said: “Starting April 21, we will be expanding our use of mobile-friendliness as a ranking signal.” It added that the change “will affect mobile searches in all languages worldwide.”
The details that shaped how it behaved:
- Mobile results only. Rankings on desktop searches were not affected.
- Page by page, not site-wide. Each URL was assessed on its own. A site could have mobile-friendly blog posts that kept ranking while an old, unresponsive product section dropped.
- Effects appeared as pages were recrawled. Because the test ran per page, there was no single switch-over moment for a whole site.
- App content as well. The same announcement said Google would start using information from indexed apps as a ranking factor for signed-in users who had the app installed.
The name “Mobilegeddon” came from the SEO community. Google did not use it, and the real-world effect was smaller than the nickname suggested for most sites that had already moved to responsive design.
Timeline
| Step | Date | What happened |
|---|---|---|
| Announcement | 26 February 2015 | Google gives about two months’ notice and points site owners to its testing tools |
| Mobile-friendly update | 21 April 2015 | Rollout begins for mobile searches in all languages worldwide |
| Mobile-friendly boost (#2) | 12 May 2016 | Signalled in Google’s March 2016 blog post; John Mueller tweeted it was fully rolled out. Search Engine Land’s library lists it as April 2016, so sources differ on the date |
Who was affected
Pages that were not mobile-friendly lost visibility in mobile search results. Typical casualties were older fixed-width sites, pages built with Flash or other plugins phones could not run, and sites that served tiny text and links packed too closely to tap. Desktop rankings were unaffected, so businesses whose customers searched mostly from computers noticed little.
In markets where most searches happen on phones, which includes Pakistan and much of the Gulf, the stakes were higher because mobile results are where most of the traffic is.
How to tell if the Mobile-Friendly update hit your site
The fingerprint of this update is a device split. Here is how I would check it:
- Segment by device in Search Console. In the Performance report, compare Mobile with Desktop for the two weeks before 21 April 2015 (or 12 May 2016 for the second boost) and the weeks after. A mobile-only drop with steady desktop numbers is the classic pattern.
- Find which pages fell. Switch to the Pages tab, filtered to mobile. Because the update was per page, losses usually cluster in a template: an old section, a microsite, PDF-style pages or a legacy shop.
- Test those pages on a real phone. Look for horizontal scrolling, text you have to zoom to read, buttons too close together, pop-ups that cover the content, and content that does not load at all.
- Rule out other causes. A separate m-dot site with broken redirects, or a mobile theme that hides content, can produce similar device-specific drops. Check that mobile users land on the equivalent mobile page, not the mobile homepage.
At the time, Google pointed owners to its Mobile-Friendly Test and the Mobile Usability report in Search Console. Google has since retired both tools, so today I use Lighthouse in Chrome DevTools, a real-device check and the Core Web Vitals report instead.
How to recover from the Mobile-Friendly update
Recovery was page by page, and happened as Google recrawled pages you had fixed. These are the steps in the order that gives the quickest return:
- Fix the pages that earn the most. Start with the URLs that lost mobile clicks, not the whole site at once.
- Move to responsive design. One URL and one HTML file that adapts to screen size is simpler to maintain than a separate mobile site and avoids redirect and duplicate problems. Set the viewport meta tag correctly.
- Make text readable and elements tappable. Use a readable base font size, give buttons and links enough space, and keep forms short on mobile.
- Remove unsupported technology. Replace Flash or plugin-based content with HTML5 equivalents.
- Do not block CSS, JavaScript or images. Google needs them to see the page as a phone user would.
- Request recrawling. Use URL Inspection for key pages and resubmit the sitemap so Google finds the fixed versions sooner.
| Mobile problem | Fix |
|---|---|
| Page wider than the screen | Responsive layout with a correct viewport tag |
| Text too small to read | Increase base font size, use relative units |
| Links too close together | Add spacing and larger tap targets |
| Flash or plugin content | Replace with HTML5 video or images |
| Separate m-dot site redirects to homepage | Redirect to the equivalent mobile URL, or go responsive |
If your site needs a rebuild rather than patches, my SEO web design and development service builds responsive sites with search in mind from the start. For sites that are mobile-friendly but slow on phones, website speed optimisation is usually the next step.
Is it still relevant today?
Google’s ranking systems guide lists the mobile-friendly ranking system as retired, incorporated into successor systems such as page experience. Since then Google has moved to mobile-first indexing, which means it mostly uses the mobile version of a page for indexing and ranking. So the question has flipped: it is no longer “is my site mobile-friendly enough to keep mobile rankings?” but “is my mobile version complete enough to represent the whole page?” In audits I still find mobile themes that hide reviews, specifications or internal links that the desktop version shows.
Frequently asked questions
When was Mobilegeddon?
The mobile-friendly update began on 21 April 2015, after Google announced it on 26 February 2015. A second mobile-friendly boost was confirmed as fully rolled out on 12 May 2016.
Did the mobile-friendly update affect desktop rankings?
No. Google said it affected mobile searches only, in all languages worldwide.
Was the mobile-friendly update site-wide?
No. It worked page by page, so individual pages that were not mobile-friendly could lose mobile visibility while the rest of the site was fine.
How long did recovery take?
Google did not give a timeline. Because the signal was per page, a fixed page could recover once Google recrawled it, so important pages often recovered faster than rarely crawled ones.
Sources
- Google Search Central Blog: Finding more mobile-friendly search results (Feb 2015)
- Google Search Central Blog: Continuing to make the web more mobile friendly (Mar 2016)
- Search Engine Land: Mobile-friendly algorithm boost has rolled out
- Keywords Everywhere: Mobile-friendly update
- Wordtracker: Google’s most notable search ranking systems
If your mobile traffic is falling while desktop holds, I can find which templates are letting phone users down. Request a free audit, or see what my SEO audit services check on mobile.
More Google algorithm updates
- Previous update: HTTPS Ranking Signal (6 Aug 2014)
- Next update: Quality Update (Phantom) (29 Apr 2015)
Other mobile updates:
- Mobile-First Indexing (26 Mar 2018)