It’s official – Google has announced measures that it’s about to take in the coming months regarding how extensions are being added to users’ Chrome browsers. The idea is to completely remove the functionality of inline installs and transit entirely to Chrome’s Web Store for future extension installs.
Inline Installations are essentially a piece of code that developers can append to their website(s) to enable users a direct install flow – without them having to visit Google’s Web Store. This feature made it easy to “sell” extensions with misleading wording, false claims in terms of features and functionalities, and much more.
A legitimate reason for Google to finally bring such activities to an end by doing its utmost best to reduce exploits of third-party sites in connections between user and extension. A thing that can only be executed by requiring users to go directly to Chrome’s Web Store for extensions.
Here is Google’s standpoint now, as expressed by Extensions Platform product manager James Wagner:
We continue to receive large volumes of complaints from users about unwanted extensions causing their Chrome experience to change unexpectedly — and the majority of these complaints are attributed to confusing or deceptive uses of inline installation on websites. As we’ve attempted to address this problem over the past few years, we’ve learned that the information displayed alongside extensions in the Chrome Web Store plays a critical role in ensuring that users can make informed decisions about whether to install an extension. When installed through the Chrome Web Store, extensions are significantly less likely to be uninstalled or cause user complaints, compared to extensions installed through inline installation.
Google requires extension submissions with exact information on what the extension will provide to the user. Apart from that additional and precise data, developers must leave some kind of contact information for potential bugs, as well as a website that may explain the extension in more detail.
A strict approach like this has its goal to minimize uninstall rates, lower the rate of bad feedback, and maintain a positive LTV for users.
What this means to affiliates
Our industry is packed with marketers who manage to make multi-figure profits with offers such as browser extensions. And it’s a no-brainer that Google is the leading search engine – meaning that the bulk of such earnings came from Chrome browsers. So what now?
The easiest way is to look the other way and focus on different browsers, right? Other than that, there’s the settlement to embrace this new rule and follow best practices and make good use of install badges. But for those who are about to definitely quit this vertical for good, there’s a tiny time window still open until the major change/shift happens. Here’s the timetable that might interest you and your future extension marketing efforts:
- June 12: Inline installation will be disabled to all new extensions. Which means that extensions published today or later that attempt to call the chrome.webstore.install() function will automatically redirect the user to the Chrome Web Store in a new tab to complete the installation.
- September 12: Inline installation will be disabled for existing extensions, and users will be automatically redirected to the Chrome Web Store to complete the installation.
- December 4: The inline install API method will be removed with the release of Chrome 71.
So, still some hours left to squeeze in some installs before the Birth of Chrome 71.
To those who are all about white hat, feel free to read up on how to create a clean, informative Chrome Web Store listing and how to facilitate the “power” of page banners within your sites to redirect your visitors to the appropriate listing.
As for the black-hat cowboys here, a solution awaits on the horizon. Let’s walk together and see what we’ll discover. But it’s definite that on December 4th, when Google releases Chrome 71, our industry will shift and tilt and quake – but we’ll stand our ground firmly!
Posted on June 13, 2018