Google has clamped down the use of user testimonials by developers in app descriptions. This move is a part of the updated guidelines on its Play Store.
According to the updated Google Policy and Procedures section, the "Keyword Spam" section of the Play Store will deploy the rule that prohibits developers from entering user testimonial in their app descriptions. In the event a developer does not abide by the guidelines, Google may take action by pulling the app from its Play Store.
"Please do not include user testimonials in your app description. They tend to be dubious and are frequently utilized to include references to popular search terms and competitor apps in violation of the policies outlined here. Let your users speak for themselves via Play's comment review system," notes Google's developer guidelines.
If you're wondering why Google has taken a strong stance, it is basically because a bulk of the reviews do not offer much insight and do not offer information that is different from what a developer could have added. The primary concern, however, is that developers often use keywords in reviews, which will propel their app forward in searches. Google has shown its displeasure toward keyword stuffing and barred the same.
By banning dubious testimonials, Google hopes to make searches in its Play Store way more reliable. Google asserts that developers should not weigh their titles or app descriptions with unrelated keywords just so one can "manipulate ranking" in the search results of Google Play. Such uses, it categorically states breach of the company's policies.
Google also gives tips to developers on how to avoid spam violations in their app's title. It asks developers to avoid the usage of repetitive keywords, as well as irrelevant usages and references. Google encourages developers to keep the descriptions concise and straightforward, as well as sharing intriguing facts on their app. Developers are also encouraged to describe their app's functionality and title "accurately" when publishing on the Play Store.
Whether developers pay heed to Google's guidelines or find a workaround remains to be seen.
