Stay organized with collections
Save and categorize content based on your preferences.
Figure 1. Google extracts and displays information from CAP
alerts.
The following fields in the CAP alert populate user-visible contents like the
example in figure 1:
<areaDesc>
<description>
<instruction>
<area>
Figure 1 shows a Severe weather alert badge on a Rainfall Warning alert
display. The <event> field in the CAP alert determines what kind of badge
Google tags onto your alert.
Figure 2. Provide Google the Safety tips information
for your alert.
Other user-visible sections like the Alert definition and static
Safety tips (see figure 2) aren't taken from CAP. To populate those
sections, send the contents to Google separately.
[[["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\u003eGoogle uses specific fields from CAP alerts (\u003ccode\u003e<areaDesc>\u003c/code\u003e, \u003ccode\u003e<description>\u003c/code\u003e, \u003ccode\u003e<instruction>\u003c/code\u003e, \u003ccode\u003e<area>\u003c/code\u003e) to display information to users.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eevent\u003c/code\u003e field in the CAP alert determines the badge displayed on the alert (e.g., Severe weather).\u003c/p\u003e\n"],["\u003cp\u003eSections like "Alert definition" and "Safety tips" are not extracted from CAP and need to be provided separately to Google.\u003c/p\u003e\n"],["\u003cp\u003eGoogle requires additional non-user-visible fields like \u003ccode\u003eevent\u003c/code\u003e and \u003ccode\u003eseverity\u003c/code\u003e for accurate alert publishing.\u003c/p\u003e\n"]]],["Google utilizes specific fields from CAP alerts to display information to users. These fields include `\u003careaDesc\u003e`, `\u003cdescription\u003e`, `\u003cinstruction\u003e`, and `\u003carea\u003e`, which populate user-visible content. The `\u003cevent\u003e` field dictates the alert's badge, such as \"Severe weather.\" Google doesn't derive the \"Alert definition\" or \"Safety tips\" from CAP alerts; this information must be provided separately. Other fields like `event` and `severity` are important to send but not visible to users.\n"],null,["# How Google reads and displays CAP alerts\n\n**Figure 1.** Google extracts and displays information from CAP alerts.\n\nThe following fields in the CAP alert populate user-visible contents like the\nexample in figure 1:\n\n- `\u003careaDesc\u003e`\n- `\u003cdescription\u003e`\n- `\u003cinstruction\u003e`\n- `\u003carea\u003e`\n\nFigure 1 shows a **Severe weather** alert badge on a **Rainfall Warning** alert\ndisplay. The `\u003cevent\u003e` field in the CAP alert determines what kind of badge\nGoogle tags onto your alert.\n**Figure 2.** Provide Google the **Safety tips** information for your alert.\n\nOther user-visible sections like the **Alert definition** and static\n**Safety tips** (see figure 2) aren't taken from CAP. To populate those\nsections, send the contents to Google separately.\n| **Note:** To publish your alerts correctly, Google requires other important non-user-visible fields like `event` and `severity`."]]
