StatusCake

Google Announces Implementation of Penalties for Intrusive Mobile Pop-Ups

password security

Google has begun to implement penalties for intrusive mobile pop-ups. Google first announced the proposed penalties last August and the company will now apply the penalties to those e-commerce firms that have not adjusted their practices to conform to them.

Google’s rationale for these penalties is to improve user experience (UX) for consumers accessing e-commerce websites on mobile devices. When someone conducts a search and clicks on a link in the results, the expectation is that they will go immediately to the page they wish to access. Pop-ups on pages can be intrusive and provide a poorer UX than those pages where a visitor can immediately access the content, especially on mobile devices with small screens. The majority of searches now take place on mobile devices, and Google is reacting to that new reality.

Google’s Webmaster Central Blog said: “Here are some examples of techniques that make content less accessible to a user:

  • Showing a popup that covers the main content, either immediately after the user navigates to a page from the search results, or while they are looking through the page.
  • Displaying a standalone interstitial that the user has to dismiss before accessing the main content.
  • Using a layout where the above-the-fold portion of the page appears similar to a standalone interstitial, but the original content has been inline underneath the fold.’

Not all pop-ups will be affected by the penalty, as some are legal requirements. The Central Blog also stated: “By contrast, here are some examples of techniques that, used responsibly, would not be affected by the new signal:

  • Interstitials that appear to be in response to a legal obligation, such as for cookie usage or for age verification.
  • Login dialogs on sites where content is not publicly indexable. For example, this would include private content such as email or unindexable content that is behind a paywall.
  • Banners that use a reasonable amount of screen space and are easily dismissible. For example, the app install banners provided by Safari and Chrome are examples of banners that use a reasonable amount of screen space.”

Currently, Google only will impose the penalty for pop-ups on mobile access to e-commerce sites. The penalty does not apply to desktop access, at least for now.

Also, the penalty only applies to pop-ups that are on the entry page. The first page that a visitor lands on after clicking on a link in a search result is the entry page. However, remember that an organic search can lead a potential visitor to click on a link other than your home page and that page would count as an entry page. Therefore, if you want to include pop-ups later on a visitor’s click path, when you program your site, tie the appearance of a pop-up to the number of clicks a visitor makes when accessing your site rather than to a specific page, such as your home page.

It’s not clear how severe the pop-up penalty will be, but if you want to avoid the possibility of losing traffic due to lower search rankings, it’s best to be sure your site complies with Google’s new guidelines.

Share this

More from StatusCake

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

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.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

When AI Speeds Up Change, Knowing First Becomes the Constraint

5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things

Make Your Engineering Processes Resilient. Not Your Opinions About AI

4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development.  For some teams, it’s an obvious productivity multiplier.  For others, it’s viewed with suspicion.  A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.