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



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:
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:
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
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.

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
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
Find out everything you need to know in our new uptime monitoring whitepaper 2021