1 page.title=Spam 2 @jd:body 3 4 <div id="qv-wrapper"> 5 <div id="qv"> 6 <h2>In This Document</h2> 7 <ol> 8 <li><a href="#keyword-spam">Spam in App Title and Description</a></li> 9 <li><a href="#ratings">Spam in Ratings and Reviews</a></li> 10 <li><a href="#webview-spam">Spam in WebViews</a></li> 11 <li><a href="#wizard-spam">Spam from Wizards</a></li> 12 <li><a href="#message-spam">Spam in Messaging</a></li> 13 </ol> 14 15 <h2>More Resources</h2> 16 <ol> 17 <li><a href="http://play.google.com/about/developer-content-policy.html" target="_policies">Developer Program Policies</a></li> 18 <li><a href="http://play.google.com/about/developer-distribution-agreement.html" target="_policies">Developer Distribution Agreement</a></li> 19 </ol> 20 </div> 21 </div> 22 23 <p> 24 Google Play policies prohibit spam, to help ensure the best experience for 25 Android users. Please do not publish deceptive, repetitive, or irrelevant 26 content on Google Play. Not only will it lower your app's rating and cause 27 negative reviews, it can result in your app being suspended or your developer 28 account terminated. 29 </p> 30 31 <p> 32 As an app developer, it is your responsibility to ensure that your apps are 33 free from spam and conform to the Google Play policies highlighted in this 34 document. Before you publish, make sure that you understand what is 35 considered spam on Google Play and check your apps for violations, even those 36 that might be inadvertent. The sections below highlight best practices and 37 common spam examples to help you avoid the most common types of policy 38 violations. 39 </p> 40 41 <p> 42 For more information about Google Play policies that apply to your apps and 43 content, please see the <a href= 44 "http://play.google.com/about/developer-content-policy.html" target= 45 "_policies">Developer Program Policies</a> and <a href= 46 "http://play.google.com/about/developer-distribution-agreement.html" target= 47 "_policies">Developer Distribution Agreement</a>. 48 </p> 49 50 51 <h2 id="keyword-spam">Spam in App Title and Description</h2> 52 53 <p> 54 When you publish an app on Google Play, you should pay special attention to 55 the app's title and description in its store listing. Those fields are 56 important because they make your app recognizable to users, and they help to 57 drive downloads by highlighting what's great about your app. A memorable 58 title and compelling description are essential to effective marketing, but 59 you should realize that these must follow Google Play policies, just as your 60 app content must do. 61 </p> 62 63 <p> 64 Many developers unknowingly violate spam policy in their app titles and 65 descriptions in ways that are easy to avoid. In general, you can 66 avoid spam violations in your app title and description by following these 67 best practices: 68 </p> 69 70 <ul> 71 <li> 72 <strong>Highlight what's great about your app</strong>—Share 73 interesting and exciting facts about your app with users. Help users 74 understand what makes your app special. 75 </li> 76 77 <li> 78 <strong>Describe your app accurately</strong>—Make sure the title 79 and description describe the app function and user experience accurately. 80 </li> 81 82 <li> 83 <strong>Don't use repetitive keywords</strong>—Avoid keywords that 84 are repetitive or excessive. 85 </li> 86 87 <li> 88 <strong>Don't include unrelated keywords or references</strong> — 89 Your description should not be loaded with irrelevant keywords in an 90 attempt to manipulate ranking or relevancy. 91 </li> 92 93 <li> 94 <strong>Keep it brief</strong>—Keep the description succinct and 95 straightforward. Shorter descriptions tend to give a better user experience 96 on devices with smaller displays. Excessive length, detail, or repetition 97 can violate spam policy. 98 </li> 99 </ul> 100 101 <p> 102 Here's an example app title and description that follows best practices and 103 does not violate Google Play spam policies. 104 </p> 105 106 <div class="example-block good" style="width:100%;float:none;margin:.5em auto 2em 0;"> 107 <div class="heading">Best practice: App description</div> 108 <table> 109 <tr> 110 <td>App Title:</td> 111 <td>Kids puzzle: Identify Turtles</td> 112 </tr> 113 <tr> 114 <td style="white-space:nowrap;">App Description:</td> 115 <td> 116 <p>This is the perfect app to have a good time with your children. It 117 is designed to help kids learn different species of turtles through 118 cute pictures and amusing puzzle games.</p> 119 <p>The rules of Kids puzzle: Identify Turtles are quite simple. Have 120 your child drag images around the screen to fit them into the shaded 121 region. Phonics is also utilized, as a child can also tap the word 122 below the image and hear the name pronounced.</p> 123 </td> 124 </tr> 125 </table> 126 </div> 127 128 <p> 129 The sections below highlight common types of policy violations in an app 130 title and description, illustrated with variations on the best practice 131 example. 132 </p> 133 134 <h3 id="repetitive-keywords">Repetitive keywords</h3> 135 136 <p> 137 Your app description should not include keywords that are repetitive or excessive. 138 </p> 139 140 <div class="example-block bad" style="width:100%;float:none;margin:.5em auto 2em 0;"> 141 <div class="heading">Description includes repetitive keywords</div> 142 <table> 143 <tr> 144 <td>App Title:</td> 145 <td>Kids puzzle: Identify Turtles</td> 146 </tr> 147 <tr> 148 <td style="white-space:nowrap;">App Description:</td> 149 <td> 150 <p>This is the perfect app to have a good time with your children. It is 151 designed to help kids learn different species of turtles through cute 152 pictures and amusing puzzle games.</p> 153 <p>The rules of Kids puzzle: Identify Turtles are quite simple. Have your 154 child drag images around the screen to fit them into the shaded region. 155 Phonics is also utilized, as a child can also tap the word below the image 156 and hear the name pronounced.</p> 157 <p style="border:2px solid red;">KEYWORDS: game, games, fun, funny, child, 158 children, kid, kids, puzzle, puzzle games, sound, turtle, turtles, sea turtles, 159 turtles, turtle, turtles, tortoise, tortoises, tortoise, tortoise, turtles, 160 turtles, turtles, turtles, tortoises, tortoise</p> 161 </td> 162 </tr> 163 </table> 164 </div> 165 166 <h3 id="unrelated-keywords">Unrelated keywords or references</h3> 167 168 <p> 169 The description should not be loaded with irrelevant keywords in an attempt 170 to manipulate ranking or relevancy in Google Play search results. 171 </p> 172 173 <p> 174 For example, if your app has nothing to do with Lady Gaga, then she shouldnt 175 be included in your description. Also, do not add highly searched, irrelevant 176 keywords that are unrelated to the function of the app. This is in breach of 177 policy. 178 </p> 179 180 <div class="example-block bad" style="width:100%;float:none;margin:.5em auto 2em 0;"> 181 <div class="heading">Description includes unrelated keywords or references</div> 182 <table> 183 <tr> 184 <td>App Title:</td> 185 <td>Kids puzzle: Identify Turtles</td> 186 </tr> 187 <tr> 188 <td style="white-space:nowrap;">App Description:</td> 189 <td> 190 <p>This is the perfect app to have a good time with your children. It is designed to 191 help kids learn different species of turtles through cute pictures and amusing puzzle 192 games.</p> 193 <p>The rules of Kids puzzle: Identify Turtles are quite simple. Have your child drag 194 images around the screen to fit them into the shaded region. Phonics is also utilized, 195 as a child can also tap the word below the image and hear the name pronounced.</p> 196 <p style="border:2px solid red;">This game is as addictive as Angry Birds, more social 197 than Facebook and Twitter, and has a soundtrack reminiscent of Katy Perry and Lady 198 Gaga.</p> 199 <p style="border:2px solid red;">KEYWORDS: Angry Birds, Facebook, Twitter, Katy Perry, 200 Lady Gaga</p> 201 </td> 202 </tr> 203 </table> 204 </div> 205 206 <h3 id="excessive-detail">Excessive detail, references to your other apps</h3> 207 208 <p> 209 Your app description should avoid excessive detail and references to your 210 other apps or products. For example, you should not list all of the details 211 of content included in the app or its various components, as shown in the 212 example below. Also, the description should not include any references to 213 other apps youve published. 214 </p> 215 216 <div class="example-block bad" style="width:100%;float:none;margin:.5em auto 2em 0;"> 217 <div class="heading">Description includes excessive detail, references to your other apps</div> 218 <table> 219 <tr> 220 <td>App Title:</td> 221 <td>Kids puzzle: Identify Turtles</td> 222 </tr> 223 <tr> 224 <td style="white-space:nowrap;">App Description:</td> 225 <td> 226 <p>This is the perfect app to have a good time with your children. It is designed 227 to help kids learn different species of turtles through cute pictures and amusing 228 puzzle games.</p> 229 <p>The rules of Kids puzzle: Identify Turtles are quite simple. Have your child 230 drag images around the screen to fit them into the shaded region. Phonics is also 231 utilized, as a child can also tap the word below the image and hear the name 232 pronounced.</p> 233 <p style="border:2px solid red;">Turtles included in the app: Alligator 234 Snapping Turtle, Asian Box Turtle, Bog Turtle, Common Musk Turtle, Common Snapping 235 Turtle, Diamondback Terrapin, Eastern Box Turtle, Eastern Mud Turtle, Eastern Painted 236 Turtle, False Map Turtle, Florida Pond Cooter, Florida Softshell Turtle, Green Sea 237 Turtle, Map Turtle, Matamata Ornate Box Turtle, Red-bellied Side-necked Turtle, 238 Red-eared Slider, Smooth Softshell Turtle, Spiny Softshell Turtle, Spotted Turtle, 239 Western Painted Turtle, Wood Turtle, Yellow-bellied Slider</p> 240 <p style="border:2px solid red;">If you like this app try our other free apps:<br /> 241 Fun Zoo<br /> 242 CD Guns<br /> 243 Dessert House<br /> 244 Playground<br /> 245 578 Weapons</p> 246 </td> 247 </tr> 248 </table> 249 </div> 250 251 252 <h2 id="ratings">Spam in Ratings and Reviews</h2> 253 254 <p> 255 Ratings and reviews are benchmarks of app quality and users depend on them to 256 be authentic and relevant. As an app developer, you should not attempt to 257 artificially influence your app's ratings and reviews or those of your 258 competitor, such as by posting fake ratings or reviews or including spam 259 content in app reviews. The sections below provide guidelines for rating and 260 reviewing apps. 261 </p> 262 263 <p> 264 So that you can stay in touch with any issues that users are having with your 265 app, you should read through your ratings and reviews on a regular basis. If 266 you choose to reply to reviews, make sure to keep your reply focused on the 267 actual issues raised in the user's comments and do not ask for a higher 268 rating. 269 </p> 270 271 <p> 272 If you see an app or developer reply that doesnt follow these guidelines, 273 you can report it. See <a href= 274 "http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113417&topic=2364761&ctx=topic" 275 target="_policies">Inappropriate content in comments and applications</a> for 276 more information. 277 </p> 278 279 <div class="example-block bad" style="width:440px;"> 280 <div class="heading">Inappropriate content in a review</div> 281 <img src="{@docRoot}images/gp-policy-spam-negreview.png"> 282 </div> 283 284 <div class="example-block bad" style="margin-top:3em;"> 285 <div class="heading">Soliciting ratings</div> 286 <img src="{@docRoot}images/gp-policy-spam-reqrating.png"> 287 </div> 288 289 <h3 id="fake-ratings">Fake or inappropriate ratings and reviews</h3> 290 291 <p> 292 To help ensure the quality of ratings and reviews, Google Play policies limit 293 the ways that individuals can use ratings and reviews. In particular, note 294 that it is a violation of policy to use ratings and reviews to influence the 295 placement of any app in Google Play. 296 </p> 297 298 <p> 299 As an app developer, make sure that you follow these guidelines: 300 </p> 301 302 <ul> 303 <li> 304 <strong>Don't try to manipulate ratings</strong>—Do not engage in 305 attempts to manipulate the ratings, reviews, or ranking of your apps, 306 either directly or indirectly, or by manipulating the ratings of your 307 competitors. Do not attempt to artificially boost reviews, ratings, or 308 installs through any means. 309 </li> 310 311 <li> 312 <strong>Don't solicit ratings through incentives</strong>—Do not 313 offer users any incentives to rate your app, such as offering rewards of 314 any kind or tying app functionality to rating. 315 </li> 316 317 <li> 318 <strong>Don't rate apps multiple times</strong>—Do not review or 319 rate any app multiple times in an attempt to influence its placement in 320 Google Play. 321 </li> 322 323 <li> 324 <strong>Don't add improper content to reviews</strong>—Do not 325 include affiliate, coupon, game codes, email addresses, or links to 326 websites or other apps in your reviews. If you are responding to a user 327 review, feel free to include references to helpful resources such as a 328 support address or FAQ page. 329 </li> 330 </ul> 331 332 <h3 id="solicited-ratings">Soliciting ratings from users</h3> 333 334 <p> 335 In general, <strong>do not offer incentives for ratings</strong>. You should 336 not offer users incentives of any kind for rating your app (or any other app) 337 on Google Play, and you should not tie your app's functionality or content to 338 rating in any way. 339 </p> 340 341 <p> 342 It's acceptable to ask users to rate your app without incentives, for 343 example: "If you like this game, rate us in Google Play!" On the other hand, 344 it's a policy violation to ask users to rate your app based on incentives, 345 for example: "Rate this app and get 500 coins" or "Rate this app 5 stars and 346 get you 500 coins!" 347 </p> 348 349 350 <h2 id="webview-spam" style="clear:right">Spam in WebViews</h2> 351 352 <p> 353 Apps published on Google Play should provide their own content. Do not 354 publish an app whose primary function is to reproduce or frame someone elses 355 website (unless you have permission). 356 </p> 357 358 <p> 359 Similarly, do not publish an app whose primary function is to drive affiliate 360 traffic to a website. Although affiliate deals can exist where an app's 361 primary purpose is delivering its own content or functionality, it's a 362 violation of Google Play policies to publish an app whose primary (or 363 only) purpose is to direct affiliate traffic to another website. 364 </p> 365 366 <div class="example-block bad" style="width:100%;float:none;margin:.5em auto 2em 0;"> 367 <div class="heading">WebView spam</div> 368 <table> 369 <tr> 370 <td>App Title:</td> 371 <td>Kids puzzle: Desktop Browser for Turtoogle Game</td> 372 </tr> 373 <tr> 374 <td>Developer:</td> 375 <td>AAZZZ <span style="border:2px solid red;">(not affiliated with Turtoogle 376 Inc.)</span></td> 377 </tr> 378 <tr> 379 <td style="white-space:nowrap;">App Description:</td> 380 <td> 381 <p>Have you ever wanted to use the full, desktop web version of Turtoogle 382 Game from your phone or tablet instead of the Turtoogle Game mobile app 383 or Turtoogle Game mobile web site?</p> 384 <p style="border:2px solid red;">This app lets you access Turtoogle Game 385 on your Android device in the same way as you access the game on your 386 desktop computer, and with all the same Turtoogle Game features.</p> 387 </td> 388 </tr> 389 </table> 390 </div> 391 392 393 <h2 id="wizard-spam">Spam from Wizards</h2> 394 395 <p> 396 Apps that are created by an automated tool or wizard service must not be 397 submitted to Google Play by the operator of that service on behalf of other 398 persons. Such tools often produce too many duplicative or low-quality 399 apps which crowd the higher-quality apps in the Play Store. 400 </p> 401 402 <p> 403 Please be advised that apps created by an automated tool are only permissible 404 if the app end-product complies with Google Play policies and is published in 405 the Play Store through a developer account that is registered and owned by 406 you. 407 </p> 408 409 410 <h2 id="message-spam">Spam in Messaging</h2> 411 412 <p> 413 Your app may not send SMS, email, or other messages on behalf of the user 414 without providing the user with the ability to confirm the content and intended 415 recipient. 416 </p> 417 418 <p> 419 Google Play will aggressively remove applications that are found to send or 420 modify SMS messages without user knowledge or consent. 421 </p>