The Feedance AI features is rolling out. Check it out!
How Feedance can help your revenue growth
250+ channel and platform integrations
Start optimizing with powerful integration
Wordpress compatible e-commerce integration
Start optimizing Magento very quickly
Open source e-commerce platform integration
Integrate ChatGPT Ads Catalog in seconds
Optimize Meta Catalog Ads
Optimize your Google Shopping visibility correctly
Optimization of TikTok Catalog Ads
Brand, submitted as <g:brand> in Google Merchant Center feeds and brand in Meta Catalog, is the free-text name of the product's manufacturer or the brand under which it's marketed, such as Nordwool or Aurex. It's one of the core merchandising fields both platforms use for search matching, filtering, and catalog-level product identification.
<g:brand>
Google requires brand for most new products submitted to Shopping ads, with limited exceptions for certain categories like movies, books, and some apparel, and a missing brand on an otherwise eligible item is a routine cause of disapproval or reduced impression eligibility. Brand also drives shopper-facing filters -- buyers narrowing a Shopping search by brand name, or Meta Catalog audiences built around brand affinity, rely entirely on this field being populated consistently rather than buried inside the title text alone. Because brand feeds directly into how gtin and mpn are validated as an identifier pair, an inconsistent or misspelled brand value can silently break catalog matching even when the identifier codes themselves are correct.
Google expects the actual brand or manufacturer name, not a store name or a generic private-label placeholder, and recommends using the same spelling and capitalization the manufacturer uses on its own packaging and site. When gtin is present, Google cross-references brand against its own catalog to confirm the identifier match is correct; when no GTIN exists, brand becomes mandatory as half of the brand-plus-mpn fallback pair rather than optional metadata. Meta Catalog treats brand similarly, using it for catalog search, dynamic ads personalization, and to satisfy certain vertical-specific requirements, such as apparel and electronics catalogs, where Meta may reduce distribution for items missing it. Neither platform enforces a fixed character format for brand beyond reasonable length limits, but both penalize keyword-stuffed values that cram multiple brand names or promotional text into the field instead of a single clean name.
<item> <g:id>SKU-30157</g:id> <title>Trail Running Jacket - Forest Green</title> <link>https://example-shop.com/products/trail-jacket-forest-green</link> <g:price>129.00 USD</g:price> <g:brand>Ridgeline</g:brand> <g:gtin>00812345678905</g:gtin> <g:condition>new</g:condition> </item>
Brand works hand in hand with GTIN for catalog matching and stands in as one half of the brand-plus-MPN identifier pair when no GTIN is available, making it one of the few fields that touches nearly every other identity attribute in the feed. It's also worth keeping consistent alongside condition, since a listing's condition often needs to be read in context of which brand actually manufactured it -- a refurbished item from a well-known brand carries different shopper expectations than an unbranded generic equivalent. Retailers running multi-brand marketplaces in particular should treat brand as a normalized, controlled field rather than free text pulled straight from a supplier feed, since inconsistent capitalization or abbreviations fragment what should be a single filterable value.
Schedule a 15-minute demo and see how our AI-powered product feed management platform can improve your feed performance and ROI.
We’ll tailor your demo to your immediate needs and answer all your questions. Get ready to see how it works!