Distribute your Actions

Now that you've designed conversations and developed Actions, you're likely ready to share them with users. Before you make your Action available to Google Assistant users, however, make sure it's discoverable and ready for deployment:

  • Check out our video that walks you through the process of publishing Actions and highlights common mistakes.
  • Read our invocation and discovery guide to make sure your Actions are discoverable and intuitive. Invocation is how users start interactions with your Actions, so you want to make sure you get this right.
  • Review your Actions to verify that they're working properly and comply with Google's policies. Expedite the review process and get your Actions approved and deployed as smoothly as possible by reviewing them for common errors and potential policy violations.
  • Get ready for deployment by preparing your assets and information for your listing in our upcoming Directory. As part of the submission process, you provide Google with images and descriptions for use in the Directory listing.

Review your invocation methods

Learn more about invocation and discovery and follow our guidelines for creating good invocation name and triggering phrases. Users access and find out about your Actions through triggering phrases, so it's worthwhile to spend some time reviewing invocation. You may also want to register and reserve your invocation name before you're ready for deployment.

Prepare for deployment

When you submit your Actions project for approval, Google tests and verifies that they meet a minimal set of launch requirements before publishing them to users. Use this guide to prepare your Actions and submit them for review and deployment.

Find out about the latest opportunities for developers: Sign up for our mailing list.

Check for policy violations

Verify that your action follows the policies for Actions on Google. In general, follow these guidelines for your content:

  • Be specific: Users must be able to invoke your Action, specifically. Don't be too broad or general, since you want users to trigger your Action. For example, use "Talk to WeatherApp to check the weather for [city]" instead of "Check the weather for [city]" as an Action phrase. Follow the guidelines for providing good action phrases.
  • Avoid prohibited content: Unless it serves a scientific, artistic, documentary or educational purpose, Actions with explicitly sexual, violent, illegal, or hateful content violate the policies for Actions on Google. Actions that promote bullying or harassment will also be rejected or taken down.
  • Respect copyrights and intellectual property: Make sure you have adequate rights to use the content offered by your action.
  • Be honest: Don't mislead or deceive users with false claims.
  • Protect users' privacy and security: Be transparent in how you handle userdata, transmit user data securely, and provide a privacy policy.
  • Don't listen to users unprompted: Users need to understand when your Action is waiting for their input. Leaving the mic open without prompting the user is a common mistake that is outlined in our policies. Make sure your Action notifies the user when it's waiting for a command, to reduce the risk that your Action is rejected.
  • Review your invocation and display names: Make sure your invocation name is consistent with the display name that will appear in our upcoming Directory in the Services section of the Google Home app, and that both are specific enough that users can easily call your action. Your invocation and display names must also follow the policies for Actions on Google.

Check the full list of policies and make sure you comply with them to expedite review and approval of your action.

Follow the branding policies

If you use the Google Assistant logo or branding in your promotional materials, follow the branding policies. Your materials must meet our branding standards and requirements for approval.

Test your Action

Make sure everything works. Check for the following common errors and violations:

  • Transport must be secure: Verify that you use HTTPs (TLS) encryption on the transport for your webhooks.
  • Verify webhook requests: Make sure that you're signing your webhook requests (Dialogflow or Actions SDK) and verifying them in your webhook.
  • Disable Small Talk: If you’re using Dialogflow and want to avoid answers to inquiries like “hello” and “goodbye,” disable the Small Talk feature.
  • Test your Action name: Make sure that the Action name you’ve set consistently triggers your Action. Use a hardware device or the web simulator and speak your invocation name repeatedly, in different real-world scenarios (i.e., with noise in the background, or at different distances from the device). If possible, ask people of different genders or with different accents to invoke your Action. If your invocation name is not consistently recognized, you may want to change it.
  • Test on real devices: Although the web simulator is great for testing your Action quickly while developing, you should always test invocation and dialogs on real devices, such as voice-activated speakers. This is the best way to understand how your Action functions in real life and helps you in figuring out how to improve the user experience.
  • *Optional* - Share with alpha/beta testers: You can create release environments and invite external users to test your Action themselves. External users may encounter test cases that you haven't accounted for, so their feedback can help you refine your Action to support as many users as possible.