In beta, with limited placesOpen to everyone in Q1 2027

↑↓ to move · Enter to open · Esc to close

Structured data

What is the Schema.org Brand type (brand schema)?

Brand is the Schema.org type that describes a brand: the name an organization or a person uses to identify a product, a range of products or something similar. On a product page, the product's brand property points to a Brand node with the brand's name, which is the manufacturer's and need not match the store that sells it.

Written by
Reviewed by
Published 6 min read
Takeaway:

Key takeaways

  • Brand describes a brand, not a company: it is a name for identifying products, with its logo and slogan if it has them.
  • On the product it is marked up with the brand property, which accepts a Brand node or an organization.
  • Google recommends giving the brand name inside a Brand node, and a single brand per product.
  • A multi-brand store puts the manufacturer's brand on each product; its own name only when it makes the item itself and there is no official brand.
  • Brand, MPN and GTIN together identify the product: the brand alone is not enough, and without it the MPN says nothing.

Open the JSON-LD of almost any product page and you will find a line like "brand": { "@type": "Brand", "name": "Photomark" }. They are two pieces with the same name: brand, in lowercase, is the property of the product that says what its brand is; Brand, capitalized, is the type from Schema.org that describes that brand. Both are written in English because they are names in the vocabulary. A store should care for a practical reason: the brand is one of the data points a search engine uses to know which exact product is on the page, and in a store that sells other people's products it has an answer that is not the store's own name.

How it works

Schema.org defines a brand as a name used by an organization or business person for labeling a product, product group, or similar. It is not a company: Brand hangs from Intangible, the branch for things that are neither physical nor organizations. Its own properties are few: the logo (logo), a slogan (slogan), a review (review) and an average rating (aggregateRating). The name, the website and the profiles that confirm its identity it inherits from Thing, the most general type, as name, url and sameAs.⁠[1]Schema.org. Brand

The brand property says the brand(s) associated with a product or service, or the brand(s) maintained by an organization or business person. It can be used on a product, a service, an organization or a person, and it accepts two kinds of value: a Brand node or an organization.⁠[2]Schema.org. brand That leaves two correct ways to mark up a product's brand:

  • A Brand node with its name, which is the usual case when the brand belongs to another company.
  • A reference to an organization, which makes sense when the brand is the company itself: the product points with its @id identifier at the organization node the page already describes, instead of repeating its name.

Google asks for it in a specific way. In its structured data for merchant listings, brand.name is a recommended property: include the product's brand in the name property of the Brand type, if you know it, and at most one brand name.⁠[3]Google Search Central. Merchant listing (Product, Offer) structured data Its example is the one on the first line of this page, with another brand.

The brand does not travel through markup alone. In Google Merchant Center, the brand attribute is required for every product that has a clearly associated brand or manufacturer, and also when the manufacturer is the store itself, as with handmade or made-to-order products. It is optional for things without a clear brand, such as movies, books, music or posters. It takes 1 to 70 characters, and the rule for choosing the name is simple: the one people shopping online recognize.⁠[4]Google Merchant Center Help. Brand [brand]

In a store

A made-up example: a photography store that sells other brands' products, compatible accessories and a strap it makes itself. All the brands are invented.

Product Brand that gets marked up Why
Photomark travel tripod Photomark It is the brand the shopper recognizes⁠[4]Google Merchant Center Help. Brand [brand]
Battery compatible with a Photomark camera, made by Voltex Voltex On a compatible product, the brand is that of whoever actually makes it, not the original brand's⁠[4]Google Merchant Center Help. Brand [brand]
Strap made by the store, with no brand of its own The store's name Google accepts the store's name when the store makes it, is the only one selling it and there is no official brand⁠[4]Google Merchant Center Help. Brand [brand]

And this is how the brand looks in the battery's node, with the manufacturer part number (MPN) beside it, because the MPN only identifies something together with its brand:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "VX-200 battery compatible with Photomark cameras",
  "brand": {
    "@type": "Brand",
    "name": "Voltex"
  },
  "mpn": "VX-200"
}

Photomark appears in the name, because it tells the shopper which camera it works with, but not in brand. The brand says who made the product, not what it is compatible with.

Warning:

What people often get wrong

That a product's brand is the store that sells it, and that putting its name in brand across the whole catalog is enough. Google only accepts the store's name as the brand when the store makes the product, is the only one selling it and has no official brand; otherwise, the brand is the one the shopper recognizes.⁠[4]Google Merchant Center Help. Brand [brand] The store has its place in the markup: it is the Organization that sells, not the brand of what is sold.

How to check it

  1. Search for "brand" in a product page's source code and see what is inside: a Brand node with its name, or a reference to an organization.⁠[2]Schema.org. brand
  2. Count the brands. Google asks for at most one per product.⁠[3]Google Search Central. Merchant listing (Product, Offer) structured data
  3. Compare the brand in the markup with the one shown on the page and with the one in your feed's brand attribute. Merchant Center also asks that it be in a single language or script.⁠[4]Google Merchant Center Help. Brand [brand]
  4. Review compatible accessories and replacement parts: their brand is that of whoever makes them.⁠[4]Google Merchant Center Help. Brand [brand]
  5. Check whether the page qualifies for rich results by running the URL through the Rich Results Test, and see that the product is detected with its brand, with no warnings about it.

Brand and Organization overlap because a company can have several brands and a brand can share its company's name. Organization is who; Brand is the name under which that company identifies what it sells. Schema.org models it this way: an organization can list the brands it maintains with brand,⁠[2]Schema.org. brand and a product has, apart from its brand, a manufacturer property, the maker, which expects an organization.⁠[5]Schema.org. manufacturer On most product pages the brand is enough. If yours is a store that makes things, both data points point to the same company; if you resell, neither of them is your store.

To go further, the Product entry shows where the brand fits among the other properties, the GTIN one explains the third identifier, and the structured data reading path orders the rest of the terms.

Synonyms

English
brand schema, brand markup
Español
marca del producto, marcado de marca

Sources

  1. [1] Schema.org. Brand. Accessed . ↑
  2. [2] Schema.org. brand. Accessed . ↑ ↑ ↑
  3. [3] Google Search Central. Merchant listing (Product, Offer) structured data. Accessed . ↑ ↑
  4. [4] Google Merchant Center Help. Brand [brand]. Accessed . ↑ ↑ ↑ ↑ ↑ ↑ ↑
  5. [5] Schema.org. manufacturer. Accessed . ↑

Change history

  • First English version.

This definition is published under CC BY 4.0. Reuse this definition freely, crediting Clione with a link to this page.

Make your catalog easy for bots to read

Clione fills every product page with what bots read best: the JSON-LD graph with its structured data, the meta description and the FAQs. You review and press Push; then we check your live store so it all stays published.