Should you really include a GTIN in your product structured data?

What exactly does 'global product identifier' mean?

Google is referring to GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), or ISBN for books. These codes uniquely identify a product regardless of the seller. The same item sold by three different e-commerce retailers shares the same GTIN.

These identifiers are not a Google invention—they have existed for decades in physical distribution. The EAN-13 you scan at the checkout? That's a GTIN. Google simply relies on this standard to understand that your product listing and that of a competitor refer to the same item.

Why does Google mention 'grouping'?

When multiple e-commerce sites sell the same product and provide the same GTIN in their structured data, Google can aggregate these offers. As a result, in rich results, users sometimes see an integrated price comparison or a mention of 'available at X sellers'.

Without a GTIN, Google treats your listing as a standalone product. Even if you are selling the exact same item as Amazon, the engine cannot automatically detect it. You remain visible, but you do not benefit from the leverage of multi-seller grouping.

Does indexing really work without an identifier?

Yes, and that's the reassuring part of this statement. Your Product structured data is not rejected if you omit the gtin, mpn, or isbn field. Google will still index your markup, potentially displaying rating stars, price, and availability.

But—and this is where it gets tricky—you forfeit a strategic opportunity. If a direct competitor for the same product provides the GTIN, they might gain visibility that you won't. Indexing is not binary: there are levels of richness in the results.

• A valid GTIN allows Google to merge signals from multiple sellers (reviews, prices, availability).
• It enhances semantic understanding: Google knows that 'iPhone 15 Pro 256GB' from you = 'iPhone 15 Pro 256GB' from Best Buy.
• It opens the door to enhanced rich results like 'Compare prices' in certain markets (notably the US).
• It reduces the risks of fragmentation: two listings for the same product due to variation in title or description.
• It facilitates integration with Google Merchant Center if you are running Shopping Ads—product feeds often require a GTIN.

Is this position from Google consistent with observed practices?

Overall, yes. It is indeed observed that sites without GTIN maintain their rich product results. No harsh penalty, no de-indexing of the markup. But—and this is rarely mentioned—the depth of processing is not the same. [To be confirmed]: Google communicates little about the exact criteria triggering multi-seller groupings, which still seem limited to certain verticals (electronics, books) and geographic areas (US > EU).

In practice, sites that add GTINs afterward sometimes see their CTR increase on certain product queries—not systematically, but often enough to suggest it’s not a coincidence. The hypothesis: Google discreetly boosts listings it can connect to a structured product graph.

What nuances should be added to this statement?

First, Mueller does not specify whether the absence of a GTIN can affect ranking. He speaks of indexing, not ranking. However, it is known that Google favors sources it deems reliable and complete. A product markup without a unique identifier is a missing signal of completeness.

Furthermore, this logic especially applies to standardized products: electronics, books, brand-name clothing. If you sell handmade creations, custom items, or services, you probably don't have a GTIN—and Google doesn't expect to find one. The implicit rule: if a GTIN exists for your product, its absence is a gap in your data.

When does this recommendation become critical?

If you are in direct competition with big players who properly feed Google Merchant Center (Amazon, Cdiscount, Fnac…), not providing a GTIN puts you at a structural disadvantage. You are not playing in the same league: they can be aggregated, compared, featured in enriched product cards.

Another problematic case: sites that dropship or resell branded products. You have access to the GTIN (it appears on the supplier sheet, packaging, manufacturer's database), but you are not using it. Google may then consider that your content is less authoritative than a competitor who integrates the entire semantic chain.

What should you do if you don't have a GTIN?

First step: check if a GTIN exists. Consult the manufacturer sheet, packaging, or ask your supplier. If the product is distributed in supermarkets or online by other retailers, it probably has an EAN-13, UPC, or ISBN. Don't assume there isn’t one without checking.

If no GTIN exists (handmade product, custom item, service), do not invent one. Use the mpn field (manufacturer reference) if you have one, or simply leave the field empty. Google understands that some products escape coding standards—this is acceptable as long as the rest of your markup is complete (name, image, description, offers…).

How to integrate GTINs into your structured data?

In your JSON-LD of type Product, add the field gtin, gtin13, gtin14, or isbn according to the format. Example: "gtin13": "0123456789012". Then validate via Google’s Rich Results Test and the Search Console ("Products" report).

If you manage a catalog of several thousand references, automate. Most PIM (Product Information Management) or e-commerce ERP systems allow you to export GTINs. Integrate them directly into your structured data generation feed—not manually, as that doesn't scale.

• Check for the presence of a GTIN in your product databases or with suppliers
• Add the gtin, gtin13, or isbn field in your JSON-LD Product
• Validate the markup via Rich Results Test and Search Console
• Monitor the evolution of rich results after deployment (CTR, impressions)
• Avoid inventing GTINs—Google can cross-check with official databases
• If no GTIN exists, use the MPN (manufacturer reference) as an alternative or leave it empty

What mistakes should you absolutely avoid?

Do not duplicate the same GTIN across different products. Each identifier must correspond to a unique reference. If you sell the same model in multiple colors, each variant typically has its own GTIN—check with the manufacturer.

Another trap: using a generic or approximate GTIN. If you sell an 'iPhone 15 Pro' and paste in the GTIN of a plain 'iPhone 15', Google might detect the inconsistency. Better to have no GTIN than an erroneous GTIN.