Google Search Console to Notify Site Owners of Unclear Subscription Pages

Chrome will soon warn you about tricky mobile subscription signups

Few days ago, it was revealed that Google will be blocking "abusive" ads on websites with the arrival of Chrome 71 browser.

"When Chrome mobile, desktop, and Android WebView users visit a page that has been flagged as deceptive, they will be shown a warning interstitial that states "The page ahead may try to charge you money," Bleeping Computer announced.

The users will be offered a choice to proceed the page or to go back if they were unaware that they were entering a billing page.

There are three guidelines that Google needs developers to follow: -Display billing information.

-Billing information should be visible and obvious to the user.

Google has outlined new mobile billing charges best practices, which pages will have to abide by in order to prevent Chrome from showing warnings. These ads trick users into clicking on them by pretending to be system warnings or "close" buttons that do not actually close the ad.

This primarily applies to mobile services, which may charge additional fees without giving at the same time players have complete information about a particular service. Further, fee structures must be displayed in a manner that is easy to understand.

According to Google, every month millions of Chrome users encounter pages that contain confusing or incomplete information about a paid service.

When we identify such pages, we notify the webmaster through Search Console where there will be an option to let us know about the changes they've made to clarify the billing process. The latest version of Chrome, whose mobile version has about 57% market share worldwide, aims to protect web users from unclear mobile subscriptions that rely on "carrier billing" to charge customers for services like game downloads.

Something else to be aware of: There's a growing ecosystem of Android and Windows browsers that are derived from Google Chrome, but there's typically a lag between a fresh version of Chrome and a fresh version of the derived app.

Related:

Comments


Other news