Get started
Stay organized with collections
Save and categorize content based on your preferences.
Before you begin
Implementation of Google Public Alerts is a collaborative effort that includes the
partner project manager and lead developers working together with the
Google Public Alerts team.
Regular communication and sharing of sample data are key to getting the project
started and moving it along. From time to time, we may request that you provide
us with data samples.
These samples do not need to be in CAP format in the early stages of
development. Give us your data as is and we'll start from there.
We encourage you to reach out to the Google team with any questions or feedback
you may have throughout the implementation and after we launch your data to the
public.
Feel free to contact us at google-public-alerts@google.com.
Resources
CAP documentation
Google Public Alerts uses data in the Common Alerting
Protocol (CAP) format. The following documents provide a comprehensive guide to
implementing standard CAP alerts:
Watch this lightning talk to learn more about how to enhance your CAP feed to
increase the reach of your emergency alerts on Google Search.
Google CAP requirements
Rather than requiring users to sign up for particular feeds, we aim to provide
relevant alerts based on location and intent.
To make this possible, we've developed additional CAP requirements.
Please refer to these sections in the Reference guide:
- Google Public Alerts CAP v1.0 lists differences between
the CAP standard and Google CAP. Note that Google does not alter the standard
in any way, but does require some elements that are optional in the standard.
- Google CAP Requirements
provide additional requirements for creating effective alerts with Google. These
do not alter the standard in any way. Their purpose is to ensure that ingestion
and distribution are rapid and accurate across all products and locations.
Implementation steps
Implementation timelines are variable, and depend on existing data formats and
number of alert types.
Google will work with you through each phase.
Follow these steps to implement and maintain your CAP data alerts:
Step 3: Test
Google tests while you publish CAP data privately.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eImplementing Google Public Alerts involves collaboration with the Google team, including sharing data samples.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Public Alerts uses the Common Alerting Protocol (CAP) format, with additional requirements for optimal ingestion and distribution.\u003c/p\u003e\n"],["\u003cp\u003eImplementation includes four steps: generating CAP alerts, sending alerts to Google, testing, and launching to the public.\u003c/p\u003e\n"],["\u003cp\u003eRefer to provided resources for CAP documentation and Google's specific requirements and guidelines.\u003c/p\u003e\n"],["\u003cp\u003eGoogle aims to provide relevant alerts based on location and intent, enhancing user experience.\u003c/p\u003e\n"]]],["Collaborate with Google Public Alerts team, sharing data samples in any format initially. Utilize Common Alerting Protocol (CAP) for data, referencing provided CAP documentation. Adhere to Google's specific CAP requirements for effective alert distribution, found in the reference guide. The implementation process involves four steps: generating CAP alerts, sending the alerts feed, private testing by Google, and public launch. Implementation timeline varies depending on the existing data and types of alerts.\n"],null,["# Get started\n\nBefore you begin\n----------------\n\nImplementation of Google Public Alerts is a collaborative effort that includes the\npartner project manager and lead developers working together with the\nGoogle Public Alerts team.\nRegular communication and sharing of sample data are key to getting the project\nstarted and moving it along. From time to time, we may request that you provide\nus with data samples.\nThese samples do not need to be in CAP format in the early stages of\ndevelopment. Give us your data as is and we'll start from there.\n\nWe encourage you to reach out to the Google team with any questions or feedback\nyou may have throughout the implementation and after we launch your data to the\npublic.\nFeel free to contact us at [google-public-alerts@google.com](mailto:google-public-alerts@google.com).\n\nResources\n---------\n\n### CAP documentation\n\nGoogle Public Alerts uses data in the Common Alerting\nProtocol (CAP) format. The following documents provide a comprehensive guide to\nimplementing standard CAP alerts:\n\n- [Common Alerting\n Protocol](http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html) is the official OASIS CAP 1.2 specification.\n- [Example Practices: CAP\n Elements](http://docs.oasis-open.org/emergency-adopt/cap-elements/v1.0/cap-elements-v1.0.html) is an additional OASIS document that gives guidance on how to fill in the CAP elements.\n- [Example Practices: CAP Feeds](http://docs.oasis-open.org/emergency-adopt/cap-feeds/v1.0/cap-feeds-v1.0.html) gives guidance on delivering CAP alerts in a feed.\n\nWatch this lightning talk to learn more about how to enhance your CAP feed to\nincrease the reach of your emergency alerts on Google Search. \n\n### Google CAP requirements\n\nRather than requiring users to sign up for particular feeds, we aim to provide\nrelevant alerts based on location and intent.\nTo make this possible, we've developed additional CAP requirements.\n\nPlease refer to these sections in the Reference guide:\n\n- [Google Public Alerts CAP v1.0](/public-alerts/reference/cap-google) lists differences between the CAP standard and Google CAP. Note that Google does not alter the standard in any way, but does require some elements that are optional in the standard.\n- [Google CAP Requirements](/public-alerts/reference/google-cap-requirements) provide additional requirements for creating effective alerts with Google. These do not alter the standard in any way. Their purpose is to ensure that ingestion and distribution are rapid and accurate across all products and locations.\n\nImplementation steps\n--------------------\n\nImplementation timelines are variable, and depend on existing data formats and\nnumber of alert types.\nGoogle will work with you through each phase.\n\nFollow these steps to implement and maintain your CAP data alerts: \n[](/public-alerts/guides/generate-alerts) \n[Step 1: Generate CAP Alerts](/public-alerts/guides/generate-alerts)\n\nFormat your data with Common Alerting Protocol (CAP). \n[](/public-alerts/guides/send-alerts) \n[Step 2: Send Google your Alerts Feed](/public-alerts/guides/send-alerts)\n\nSecure your data and send Google your alerts feed. \n[](/public-alerts/guides/test-alerts) \n[Step 3: Test](/public-alerts/guides/test-alerts)\n\nGoogle tests while you publish CAP data privately. \n[](/public-alerts/guides/launch) \n[Step 4: Launch your alerts to the public](/public-alerts/guides/launch)\n\nLaunch and maintain Google Public Alerts."]]
