More on Keywords in App Store Listings & Other Rumored Upcoming Changes

Posted on 01 Aug 2009 by PatrickJ

AppStore

I did a post recently saying that I think adding keywords to App Store listings is a bad idea “ if Apple doesn ‘t step up their game (hugely) on staying on top of abuse of the system and so forth.

I ‘m still very much a skeptic on this subject, but today I ‘ve noticed a post at 148apps.biz that provides some grounds for a little more optimism.

First off, there ‘s a little bit more (reported) detail on what will not be allowed in keywords:

Reportedly other application names and copyrighted terms will not be allowed in the keywords. How Apple will police this is unknown, but it will be yet another reason that Apple can reject an app submission.

That ‘s a good start, though I think it will take more filters than that, and very active vetting (which I still doubt will occur) to really keep a handle on abuse.

Another very interesting section of the post talks about a rumored next step in App Store modifications:

An unconfirmed source has also told us, after talking with their app store contact at Apple, that the next step to be implemented will be to ignore the app description in search. Purportedly to cut down on so-called black hat SEO optimization that may lead to confusion by consumers due to one app mentioning other apps in it ‘s description. After this change, a search in the app store will only take into account the app name, keywords, and reviews. At the time of writing, app descriptions are still searchable.

These changes leave developers with less search optimization they can do with their apps, but perhaps cuts down on some misuse of the metadata as well.

I like the sound of this potential change as well “ as I have seen some ridiculous abuse of the description area in the past, and have certainly seen skewed and frustrating search results because of it.

The full post at 148apps.biz “ HERE “ is well worth a read.  I ‘d be interested to hear what developers think of these rumored adjustments to App Store practices.

Share this:
Share this page via Email Share this page via Digg this Share this page via Facebook Share this page via Twitter

4 Responses to More on Keywords in App Store Listings & Other Rumored Upcoming Changes

  1. Brian says:

    Other app names won't be allowed in keywords? So Beejive wouldn't be able to put AIM, Yahoo, ICQ, Facebook, or any of the many other networks they support as keywords? Keywords can't be copyrighted terms? Does that mean the hundreds of twitter apps can't have a keyword of 'twitter' or 'tweet'? (I'm assuming those are copyrighted trademarks.)

    I'm a fairly pessimistic person, but I won't say this is for sure going to completely fail. However, all I really see so far is more ways for Apple to reject apps when they're already doing an incredibly poor job at having clear and consistent guidelines for approval.

    • patrickj says:

      "So Beejive wouldn't be able to put AIM, Yahoo, ICQ, Facebook, or any of the many other networks they support as keywords? Keywords can't be copyrighted terms? Does that mean the hundreds of twitter apps can't have a keyword of 'twitter' or 'tweet'?"

      Surely in these cases Apple's renowned open and extensive communication with developers during the process will come to the rescue. Oh crap – sorry – was living in some odd parallel universe where Apple communicated well with anybody, for a moment there. :)

  2. Mike says:

    Wonder how many apps have names that describe itself. Uh more than half i'd guess. I'm sure the most popular of the 50k will keep their competition as keywords. Someone call the FCC, BBB, and whoever else. Better yet! Maybe we should have Obama oversee Apple. Introduce gov run iPhone app store. Sweet.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>