Google’s mobile-friendly ranking change began rolling out on 21 April. If your important pages still fail the Mobile-Friendly Test, or if mobile search traffic has dipped while desktop looks steady, you are not alone. Many older WordPress and static sites were never built for phones.
This post is about what to do next. We rank the options by effort, so you can pick a path that matches your budget and how urgent the drop feels. The goal is to turn a mobile friendly test fail into pages Google will treat as usable on a phone.
Confirm the problem first
Open the failed URL in Google’s Mobile-Friendly Test again. Note the exact errors: text too small, links too close, content wider than the screen, or blocked resources. Then check the same page on a real phone. Sometimes the test fails because CSS is blocked, even though the page looks fine to you.
In Webmaster Tools, open the Mobile Usability report. It shows how many URLs are affected and which error types dominate. Fix patterns, not one page at a time, when the same theme bug repeats across the site.
Compare Analytics for mobile versus desktop sessions on the pages that matter. A soft dip is different from a sharp fall on product or contact pages. Either way, fix the usability issues; do not wait for another algorithm date.
Effort level 1: unblock and retune
If the test shows blocked CSS or JavaScript, allow Googlebot for smartphones to fetch those files. Check robots.txt, security plugins and hotlink rules. After the change, run Fetch as Google with Submit to Index on the key URLs so the new crawl is not left to chance.
Next, adjust the theme’s CSS where you can: increase base font size on small screens, add padding around buttons and menu links, and stop fixed-width elements from forcing horizontal scroll. On many sites this is a few hours of work, not a rebuild.
Also check popup plugins and sticky bars. A banner that covers half the phone screen can make a page fail even when the underlying layout is fine.
Effort level 2: responsive theme or template swap
If your WordPress theme dates from the early responsive years, or never claimed mobile support, switching to a current responsive theme is often the cleanest fix. Back up the site first. Then:
- Install the new theme on a staging copy if you have one, or in a maintenance window.
- Rebuild the home page and main inner pages so menus, forms and sidebars still work.
- Test contact forms, enquiry forms and checkout steps on a phone.
- Retest with the Mobile-Friendly Test and request indexing for the updated URLs.
Expect to lose some custom layout. That is usually cheaper than fighting an old theme for weeks. Keep plugins you still need, remove the ones that inject desktop-only scripts, and watch page weight on 3G. A theme that passes the test but takes twelve seconds to load on a phone still loses customers.
Ask your developer for a short written list of what changed: theme name, plugins removed, and which templates were rebuilt. That list helps the next person who touches the site.
Effort level 3: rebuild key pages or the whole site
Static HTML sites from 2008 with table layouts, Flash headers or fixed 980 px wrappers rarely pass without a rebuild. Prioritise the pages that earn enquiries or sales. A simple responsive home page, about page, services list and contact page can restore mobile search visibility while the rest of the archive waits.
For larger catalogues, plan a full responsive rebuild with a clear launch date. Redirect old URLs carefully. Keep the same domain. Submit an updated sitemap once the new templates are live.
Separate m. sites can still work if redirects and rel annotations are correct, but most small businesses are better on one responsive site. If your mobile site is a neglected copy with thin content, that is often why rankings suffer even when the test passes on m.
After you fix it
Passing the test once is not the end. Google needs to crawl and index the improved pages. Use Fetch as Google, keep the sitemap fresh, and watch Mobile Usability until the error count falls. Ranking recovery is page by page and can take days to weeks depending on crawl frequency.
Desktop rankings should not have been hit by this update. If desktop also fell, look for other causes: site errors, hacked pages, or unrelated algorithm moves.
A practical order of work
- List the URLs that bring leads or orders.
- Fix blocked resources and obvious CSS issues on those URLs.
- If they still fail, move to a responsive theme or rebuild those templates.
- Request recrawl, then monitor mobile sessions and the usability report.
If you sell through a phone number on the site, make sure the number is click-to-call on mobile and that the contact page passes the test. Many small businesses lose mobile leads here even after the home page looks fine.
Failing the mobile test after 21 April is fixable. Start with the cheapest change that clears the errors on your money pages, then widen the work. Waiting for the next big Google announcement is not a plan.
