Site icon FeedArmy Co., Ltd.

Google Merchant Center Consumer Notice Attribute: How to Add Legal Disclaimers, Safety Warnings and Prop 65 to Your Products

consumer notice attribute

Google has quietly added a new attribute to Google Merchant Center called consumer notice [consumer_notice]. It lets you submit the legal details of a product, such as safety warnings, legal disclaimers, and California Prop 65 disclosures, so that shoppers see them before they complete a purchase.

Think of a toy that is only suitable for children aged three and above, or a product containing a chemical such as formaldehyde that California requires you to warn about because it can cause cancer. You can now submit all those legal details per product, directly in your data feed.

In this article, I will walk you through what the attribute does, how the sub-attributes work, the one strange rule you really need to watch out for, and how to format it for each feed type.

Where the Consumer Notice Shows Up

The consumer notice is used in the Universal Checkout Protocol (UCP), the new AI checkout flow Google has introduced. It isn’t shown everywhere in Google Shopping; it appears during product checkout in that flow.

Here is what the shopper sees:

The attribute is optional for all products. Google says to use it when local laws or regulations require you to disclose it. Note that Google’s help page does not list which countries it applies in.

How the Consumer Notice Attribute Works

The setup is simple. There is one main attribute, consumer_notice, with two required sub-attributes. They are combined as notice_type:notice_message.

Sub-attributeRequiredAccepted values
notice_typeYeslegal_disclaimer, safety_warning or prop_65
notice_messageYesText, maximum 1,000 characters

The notice type tells Google what kind of legal detail it is. The notice message is the actual text the shopper reads.

You can use a few basic HTML tags inside the message:

The link option is really useful. You can point shoppers to the manufacturer’s official legal or safety page instead of cramming everything into 1,000 characters.

A few more technical details: Unicode is accepted but Google recommends plain ASCII, and structured data (schema.org) is not supported. Honestly, for detailed product information like this I never rely on structured data anyway. Submit it through your main data feed or a supplemental feed.

Watch Out: The 7 Notice Limit

This is the most important thing in the whole article. You can submit a maximum of 7 consumer notices per product.

What happens if you submit more is really strange. Normally you would expect Google to ignore anything over the limit. That is not the case. Google keeps the last 7 and drops the earliest ones.

So if you submit 8 notices, the 8th overwrites the 1st. You end up with notices 2 to 8, and your first notice is gone. If your most important warning happened to be first in your feed, it will no longer show.

My advice: never submit more than 7. Only include the notices that are legally required, and leave out anything that is nice to have. That way you always know exactly what the shopper is seeing.

How to Format Consumer Notice in Your Feed

Most errors with this attribute will come from escaping, because warning texts are full of colons, commas and quotes. Here is how to handle each feed type.

Text / TSV feeds

safety_warning:"WARNING: Choking hazard. Not for children under 3; adult supervision required"

Google Sheets

safety_warning:WARNING\: Choking hazard\, small parts. Not for children under 3.

XML feeds

Use <g:consumer_notice> with the two child elements, and repeat the whole block for each notice.

<g:consumer_notice>
  <g:notice_type>prop_65</g:notice_type>
  <g:notice_message>&lt;b&gt;WARNING&lt;/b&gt;: This product can expose you to formaldehyde, which is known to the State of California to cause cancer.</g:notice_message>
</g:consumer_notice>
<g:consumer_notice>
  <g:notice_type>safety_warning</g:notice_type>
  <g:notice_message>Choking hazard. Small parts. Not for children under 3 yrs.</g:notice_message>
</g:consumer_notice>

One thing I noticed: Google’s own XML example uses prop65 without the underscore, while the list of supported values says prop_65. I recommend using prop_65 and checking your diagnostics after the first upload.

Merchant API

In the Merchant API the attribute is sent as a custom attribute named consumer_notice, with groupValues holding notice_type and notice_message. Escape double quotes as \", backslashes as \\, and control characters such as new lines and tabs.

"customAttributes": [
  {
    "name": "consumer_notice",
    "groupValues": [
      { "name": "notice_type", "value": "safety_warning" },
      { "name": "notice_message", "value": "<b>Warning</b>: Choking Hazard. Small Parts. Not for children under 3 yrs." }
    ]
  }
]

My Recommendations

Don’t ignore this attribute. Yes, it is an extra step. But if you sell products where other merchants are already submitting these warnings, Google knows there are legal requirements for that product type. In the beginning I don’t expect Google to suspend anyone for leaving it out. Eventually, though, Google will start using automated checks to see which merchants submit it and which don’t.

Once your account is suspended, it is very hard to figure out what the issue is. There are so many attributes and policies in Google Merchant Center that you might not even be aware of the one causing the problem. So whenever Google releases a new attribute like this, just implement it straight away.

My checklist:

  1. List the products that legally need a warning, disclaimer or Prop 65 notice.
  2. Pick the correct notice_type for each one.
  3. Keep every message under 1,000 characters and link to the manufacturer’s page for the full details.
  4. Never submit more than 7 notices per product.
  5. Add the attribute through your main feed or a supplemental feed, and follow the escaping rules for your format.
  6. Show the same warnings on your own product landing pages, so you are fully compliant outside of Google too.

One last note: Google’s help page explains how to submit the attribute, not which disclosures your products legally need. If you are unsure, check with a qualified legal advisor.

🙋Questions or Need Help?

Try MerchantCodex (Courses, Forum, Coding, etc)

Or do you have a private question or need private specialist support? Get in touch! I’m happy to help you optimize your Google Shopping listings for the best performance.

Exit mobile version