GTIN, MPN and brand in Product schema: which to include
Which product identifiers belong in your GTIN schema: gtin variants, mpn, sku and brand, what to do for custom goods, and how to handle quote-only catalogs.
By Crawlito · 9 min read
In short
- Google lists gtin, gtin8, gtin12, gtin13, gtin14, isbn, mpn, sku and brand.name as recommended, not required, properties for merchant listings.
- Google asks for the most specific GTIN property that fits and only the numerical form; it does not support the URL form that schema.org also allows.
- Merchant Center says not to submit a GTIN for a product that has none, and to use your store name as the brand with an MPN of your choice when you make the product yourself.
- Merchant listings need a price greater than zero, so a quote-only page cannot be a merchant listing; price 0 means free, not price on request.
On this page
- Which identifier properties Google reads
- Which GTIN property to use for your barcode
- Products without a GTIN: custom, handmade and private label
- How identifiers in markup should match the Merchant Center feed
- Quote-only and no-price catalogs
- Frequently asked questions
- Check what your product pages publish
Include every identifier your product genuinely has, and nothing it does not. In Google's merchant listing documentation, gtin (and its length-specific forms), mpn, sku and brand.name are all recommended rather than required, so leaving one out does not make the markup invalid. A wrong identifier is worse than none: Google's Merchant Center help says that if you are unsure of a GTIN, don't submit one.
This post is about the identifier fields only. For the full set of Product and Offer properties, reviews and price matching, see the Product schema guide; for variant SKUs and URLs, see product variants and AI search.
Which identifier properties Google reads
Here is what each property means and what Google's documentation says about it, at the time of writing.
| Property | What it is | Google's rule |
|---|---|---|
gtin8, gtin12, gtin13, gtin14 | GTIN of a specific length | Recommended. Use the most specific one that applies |
gtin | Any GTIN | Allowed, but the specific property is preferred |
isbn | Book number | Only valid on Book; co-type with Product; ISBN-13 gives best results |
mpn | Manufacturer part number | Recommended. Identifies the product for a given manufacturer |
sku | Your own merchant identifier | Recommended. At most one value, no whitespace, ASCII recommended |
brand.name | Brand, as a Brand object | Recommended. At most one brand name |
Two details cause most validation surprises:
- Numbers, not URLs. Google says to give the GTIN "in the numerical form" and that it does not support the URL form. schema.org's definition of gtin allows a GS1 Digital Link URL as a value, so a schema.org-valid block can still fall outside what Google accepts. Schema.org itself now points Digital Link URLs to
hasGS1DigitalLink. - Brand is an object. Google asks for the brand in the
nameproperty of theBrandtype. A plain string such as"brand": "Example Outdoor"is easy to write and is not the form Google documents.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Trail Runner 2 waterproof jacket, navy, size M",
"gtin13": "5012345678900",
"mpn": "TR2-2026-NVY-M",
"sku": "TR2-NVY-M",
"brand": { "@type": "Brand", "name": "Example Outdoor" }
}The values are illustrative, and a real block also needs image and offers.
Which GTIN property to use for your barcode
A GTIN is the number under a product's barcode. GS1, which issues them, describes four lengths: GTIN-12 is the UPC used mainly in North America, GTIN-13 is the EAN used mainly elsewhere, GTIN-8 is for small items, and GTIN-14 identifies groupings such as cases rather than units sold at the till. The brand owner assigns it.
Map the barcode you have to the property with the same length:
| Barcode on the pack | Digits | Property |
|---|---|---|
| UPC-A | 12 | gtin12 |
| EAN-13, or JAN | 13 | gtin13 |
| EAN-8, or short JAN | 8 | gtin8 |
| ITF-14 (cases, multipacks) | 14 | gtin14 |
| ISBN on a book | 13 | isbn, on a Book co-typed with Product |
Merchant Center's GTIN page adds two conversions: turn an 8-digit UPC-E code into its 12-digit form, and turn an ISBN-10 into an ISBN-13.
Do not pad a UPC with zeros to make it look like a 13- or 14-digit number. Schema.org says zero-padding is neither required nor recommended, and Google's advice to use the most specific property only works if the length is the real one.
How to check a GTIN before publishing
Merchant Center's GTIN page lists the mistakes Google looks for:
- The check digit must be present and correct. The last digit is computed from the others.
- No restricted prefixes. GTINs with the prefixes 02, 04 or 2 are in restricted ranges.
- No coupon numbers. Prefixes 05, 98 and 99 are coupon ranges.
- Only manufacturer-assigned numbers. Merchant Center says not to submit a GTIN for a product that doesn't have one.
You can test the check digit yourself. This uses the standard GS1 modulo-10 method, which works for all four lengths. The prefix test compares against the 13-digit form, so a 12-digit UPC is read with a leading zero; it skips 8- and 14-digit numbers, where the first digits mean something else:
python3 - <<'EOF'
def valid(gtin):
d = [int(c) for c in gtin]
body = d[:-1][::-1]
total = sum(x * (3 if i % 2 == 0 else 1) for i, x in enumerate(body))
return (10 - total % 10) % 10 == d[-1]
def bad_prefix(gtin):
if len(gtin) not in (12, 13):
return False
return gtin.zfill(13).startswith(("02", "04", "05", "2", "98", "99"))
for g in ["5012345678900", "5012345678901", "036000291452"]:
print(g, "check digit ok" if valid(g) else "BAD check digit",
"| restricted or coupon prefix" if bad_prefix(g) else "")
EOFRun it over a feed export to catch typos, and over the values in your JSON-LD to catch template bugs that print the same number on every product.
Products without a GTIN: custom, handmade and private label
Many products have no barcode at all, and Google's rules for them sit in Merchant Center help rather than in the Search Central structured data pages. Pulling them together:
- You make the product yourself (custom or homemade goods with no official brand). Merchant Center's brand page says to use your store name as the brand when you are the manufacturer and the only seller, and to include an MPN with a unique identifier of your choice. In this one case, a self-made MPN is acceptable, because you are the manufacturer.
- Private label made for you by someone else. The brand page says to use your store name as the brand for private-label products. The GTIN page notes that store brands generally won't have a GTIN, but if yours carry a barcode, use it. The MPN page says not to use a value you created unless you are the manufacturer, so use the maker's part number if there is one.
- Someone else's brand but there is no GTIN. The MPN page says MPN is required for products without a manufacturer-assigned GTIN, and optional for custom-made products such as art or handmade goods.
- A customised version of a branded product. Merchant Center says to submit the GTIN the manufacturer assigned if you offer customisation, engraving or personalisation, and to say the product is customised in the title and description.
- One-of-a-kind or custom-made. The GTIN page's example leaves the GTIN blank for a custom-made dress, because it has none.
- No clear brand at all. Merchant Center says brand is optional for products without a clearly associated brand, and "when in doubt" not to provide one or make one up.
In the feed, the identifier_exists attribute tells Google that a product has no unique identifiers. Google recommends it for products that don't have a GTIN, MPN or brand, names custom goods, art, handmade goods, vintage items and antiques as examples, and warns that a product set to no will get a warning if there is evidence an identifier exists.
The two help pages do not tell quite the same story. The brand page says a self-made product should carry your store name and your own MPN instead of identifier_exists set to false, while the identifier_exists examples (a customised dress, a hand-knitted scarf) leave the MPN blank. If you do assign your own codes, the brand page's route is the one to follow.
The identifier_exists page lists no schema.org property for it, and Google's merchant listing documentation has no structured data equivalent. In markup, you simply leave the missing properties out. A handmade product looks like this:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Hand-thrown stoneware mug, ash glaze",
"sku": "MUG-ASH-01",
"mpn": "MUG-ASH-01",
"brand": { "@type": "Brand", "name": "Example Pottery" },
"image": ["https://pottery.example.com/img/mug-ash-1x1.jpg"],
"offers": {
"@type": "Offer",
"price": 32.00,
"priceCurrency": "GBP",
"availability": "https://schema.org/InStock"
}
}No gtin property, the shop's own name as brand, and the shop's own code as MPN.
How identifiers in markup should match the Merchant Center feed
Google's Product structured data overview says that providing both structured data and a Merchant Center feed "maximizes your eligibility" and helps Google understand and verify your data, and that some experiences combine the two. If your feed says one GTIN and your page says another, you are giving Google two versions of the same product.
The fields line up like this (Merchant Center's attribute pages name the matching schema.org properties for gtin, mpn and brand):
| Merchant Center feed | Product markup |
|---|---|
gtin | gtin8, gtin12, gtin13, gtin14 or isbn (or the generic gtin) |
mpn | mpn |
brand | brand as a Brand with name |
identifier_exists set to no | Leave the identifier properties out |
item_group_id | inProductGroupWithID or a ProductGroup |
Generate both from the same product record, not from two copies of the catalog. Ways the two can drift apart include a brand field filled with the store name in one place and the manufacturer in the other, a variant feed with per-variant GTINs while the page prints only the parent's, and a feed tool that stores GTINs with leading zeros while the theme prints them without, which makes a plain text comparison fail.
To compare, pull the identifiers from the live page and from a feed export for the same product. The tr step joins lines so multi-line JSON-LD blocks match; adjust the pattern if your theme adds other attributes to the script tag:
curl -s "https://shop.example.com/trail-runner-2" \
| tr -d '\n' \
| grep -o '<script type="application/ld+json">[^<]*</script>' \
| sed 's/<[^>]*>//g' \
| jq '.. | objects | select(has("sku")) | {sku, mpn, gtin, gtin8, gtin12, gtin13, gtin14, brand}'If Merchant Center reports it cannot read your product pages at all, fix that first: Merchant Center unable to check product pages covers the causes. The same consistency applies to other feeds, such as the ChatGPT product feed for merchants.
Quote-only and no-price catalogs
Industrial suppliers, B2B catalogs and made-to-order shops often show "request a quote" instead of a price. The identifier advice above still applies, but the rich result rules change:
| Merchant listings | Product snippets | |
|---|---|---|
| Price | Required, greater than zero | Required inside an Offer; 0 is allowed |
| Needs an offer? | Yes | No: one of offers, review or aggregateRating |
| Quote-only page eligible? | No | Only with genuine reviews or ratings on the page |
Google's merchant listing page states that, unlike product snippets, merchant listing experiences require a price greater than zero. Its product snippet page shows "price": 0 as an item "available without payment". So 0 means free. Using it for "price on request" would describe something the page does not say, which breaks the rule that markup must represent the page.
For a quote-only product, that leaves three honest options:
- No rich result, clean data. Keep a
Productwithname,description,image,brand,mpnandsku, and nooffers. Because product snippets need one ofoffers,revieworaggregateRating, this item does not meet the product snippet requirements, and Google's testing tools may flag it. That result is expected, not a bug to fix with an invented price. - Product snippet from real reviews. If customers leave reviews that the page displays,
revieworaggregateRatingsatisfies the product snippet requirement without any price. - Show a real price. If you have a list price or a "from" price for a standard configuration, put it on the page and in the
Offer. Merchant listing eligibility only comes with a price above zero that buyers can see.
Google also notes that product snippets may use pricing data from your Merchant Center feed if it's not present in the structured data on the page. That helps only if the feed carries a real price.
Frequently asked questions
Is GTIN required in Product schema?
No. Google lists GTIN properties as recommended for merchant listings, and the product snippet documentation does not require them. Merchant Center recommends a GTIN for all products that have one assigned by the manufacturer.
Can I make up a GTIN for my own products?
No. GTINs are issued by GS1 to brand owners, and Merchant Center says not to submit a GTIN for a product that doesn't have one. If you make the product, use your store name as the brand and your own code as the MPN.
Should I use gtin or gtin13?
Use the specific property that matches the barcode length, such as gtin13 for an EAN-13. Google accepts the generic gtin but recommends the most specific one that applies.
Can I put a sku and an mpn with the same value?
Yes, when you are the manufacturer and your part number is your stock code, as in the handmade example. If you resell another brand's product, the MPN should be the manufacturer's number, not your SKU.
What price should a quote-only product use in schema?
None. A price of 0 means free, and merchant listings need a price above zero, so leave offers out unless the page shows a real price.
Check what your product pages publish
Identifier bugs usually come from templates, so they repeat across a whole catalog. Run the free check on one product page to see what a crawler receives, or book an audit to have product markup and the rest of the site reviewed across up to 500 pages, with evidence and prioritized fixes. For related warnings, see missing field shippingDetails and common JSON-LD errors.
Filed under Structure and schema. Topics: structured-data, ecommerce, json-ld, google