Invocation and discovery checklist

App Name
Avoid words that have multiple pronunciations

This is needed so that both users and the Google Assistant know how to pronounce your app name. For instance, it may not be a good idea to include the word "Envelope" in your app name, as users and the Assistant will not know whether to say "en-vel-ope" or "ahn-vel-ope". Other examples include "tear", "bow", and "bass".

Make sure Google recognizes your app name
  • Use the microphone input in the developer console to speak your app name, rather than type it. Using our speech recognizer increases the chances that your app name will be correctly recognized. You should also try saying it several times to make sure it's consistently recognized accurately. Speech input is currently only available in the Chrome browser
  • Test your app name in the Actions Simulator with the microphone input. Check to see if the text output matches what is listed for your app name.
  • Test your action on voice-activated speakers. Preview your action and try to invoke it on a voice-activated speaker
  • Try testing with people of different genders and accents. You want to make sure that your app name will be recognized no matter who says it.
Choose easy but unique names

You want users to be able to effortlessly use your actions. If they have to struggle to say the name or if they can’t easily remember the name, then they are far less likely to keep using your actions.

Adhere to our app name policies

See the app naming policies for more information on guidelines and restrictions for app names.

If you need an app name for your business that violates one of our policies or if it's not recognized well by the Assistant, contact support to receive an exception that we evaluate on a case-by-case basis.

Action Invocation Phrases
Design for your app's use cases

DO design your actions invocation phrases around your app's specific tasks and real world use cases.

DON'T use phrases that are too general or don't describe your app's purpose specifically.

Specify clear verb-object pairs

The most useful action invocations phrases typically consist of a verb-object pair. These phrases are easy to remember and align well with most user queries.

Provide a broad set of quality action invocation phrases

You should ensure your actions can be invoked regardless of your user's choice of words. Try and provide at least 10 different invocation phrases for each action.

Review examples of good and bad action invocation phrases

Action invocation phrases are critical for your app being discovered naturally via implicit invocation, so you should take the time to ensure they are designed well. Review our recommendations for writing useful action invocation phrases to make sure your app gets this right.

Assistant Directory
Use the Assistant Directory weblink

Promote your app using the Assistant Directory weblink. You can provide this link on your webiste and other marketing materials to drive users to your actions.

Write a good app description

Make sure your description promotes your app’s utility, benefits, and best features with text and images.

If the Assistant recommends your app to a user and they ask for more details, the Assistant will read your app's description to the user. Make sure your description sounds good in this context to give a good first impression.