Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
While not surprising, two reports in November confirmed the growing importance of mobile devices for accessing the internet. StatCounter, a Dublin-based web analytics company, announced that 51.3% of worldwide internet usage in October took place on tablets and mobile devices, compared to 48.7% on traditional desktops, marking the first time that desktop-based internet traffic was not in the majority.
Three days after StatCounter released their report, Google announced it was moving towards implementing a mobile-first indexing scheme. Google stated: “To make our results more useful, we’ve begun experiments to make our index mobile-first. Although our search index will continue to be a single index of websites and apps, our algorithms will eventually primarily use the mobile version of a site’s content to rank pages from that site, to understand structured data, and to show snippets from those pages in our results. Of course, while our index will be built from mobile documents, we’re going to continue to build a great search experience for all users, whether they come from mobile or desktop devices.”
Do not underestimate the significance of Google’s announcement. This indexing scheme is a major change, and you should make sure your website is ready when Google fully implements it to ensure your site doesn’t receive a lower search rank. Here are the answers to a few key questions about the proposed change.
What if you’ve already optimized your site for mobile access?
If you’ve already designed your website to scale automatically for display on mobile devices and you display the identical information on both desktops and mobile devices, congratulations – you don’t have to do anything, assuming your page loading speed is not slow on mobile devices. Google uses page loading speed in its algorithm as one of the measures when determining search rank, so consider using a website monitoring service to ensure your site loads quickly and gets the search rank you deserve.
What if your site does not display well on mobile devices?
Google will implement mobile-first indexing incrementally over the coming months, so you have enough time to get your site ready. Upgrade your site using a responsive design that automatically adjusts to display properly on both desktops and mobile devices. Test your new site thoroughly before launching, and verify that Google’s search bot can index your mobile site.
What if you have separate desktop and mobile sites?
If you have two versions of your site, be sure your mobile version displays the same content as your desktop version. Submit both sites to Google for indexing, and be sure that Google’s search bot recognizes the mobile version of your site.
Consider implementing these suggestions as soon as possible, and over the next few months, keep checking on your search rank to be sure Google’s new indexing scheme has not adversely affected you. Use of mobile devices will continue to increase, so be sure you keep your website optimized for them. Whether you’re selling a product or providing information, don’t give yourself a competitive disadvantage by ignoring Google’s new initiative.
StatusCake Team
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026