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

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Blog

Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack

3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed

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.