Attribute Guide

identifier_exists Attribute: When to Use It & Common Mistakes

Full guide to the identifier_exists attribute in Google Merchant Center. When to set it to false, the risks of misuse, its relationship with GTIN and MPN, and…

Updated 7 min readBoostora Team
identifier_exists — Correct vs. Incorrect Use

Hand-knitted Merino Wool Beanie — Forest Green

€38.00woolcraft-studio.com
Handmade — no GTINCustom item

identifier_exists = false is correct for handmade products with no manufacturer GTIN or MPN.

Nike Air Max 90 — White — Size 42

€109.00sneakers-store.com

identifier_exists = false on a branded product with a real GTIN. Causes data quality warning, reduced auction priority, and mismatched catalogue entry.

identifier_exists = false is for products that genuinely have no GTIN or MPN — handmade goods, custom items, vintage products, and unbranded parts. Using it on branded products to "skip" identifier requirements causes data quality violations and degrades performance.

What is the identifier_exists attribute?

The identifier_exists attribute is a boolean flag that tells Google whether your product has standard global product identifiers — specifically, a GTIN (EAN, UPC, ISBN), MPN, or brand. When set to false, it instructs Google not to require or look for these identifiers, because the product genuinely doesn’t have them. The default value is true.

This attribute is frequently misunderstood and misused. It is not a shortcut for avoiding identifier requirements — it is a factual declaration about the nature of the product. Using it incorrectly on branded products causes data quality violations, reduced auction priority, and potential account-level warnings. Its correct use is specifically for products that are handmade, custom, vintage, or otherwise produced without manufacturer-assigned identifiers.

Technical specifications

Feed nameidentifier_exists
RequiredMust be explicitly set to false for products without GTIN, MPN, or brand. Otherwise, omit (defaults to true).
Accepted valuestrue or false (also accepts yes/no in some feed formats)
Defaulttrue (Google assumes identifiers exist unless told otherwise)
Visible to shoppersNo — backend processing flag only

Where identifier_exists is used

  • Feed validation and diagnostics — Google uses this attribute to determine whether to flag missing GTIN/MPN/brand as errors. Setting false suppresses those warnings for legitimately unidentified products.

  • Auction processing — Products with identifiers compete in a different tier than those without. identifier_exists = false signals to Google’s auction system that this product cannot be cross-matched against other merchants’ identical listings.

  • Catalogue matching — When false, Google does not attempt to match your product against its product knowledge graph. Reviews, price comparisons, and enriched listing features are not applied.

  • Search query matching quality — Without catalogue matching, search relevance relies entirely on your product’s text attributes (title, description, product_type). Accurate, keyword-rich content becomes even more important.

When to set identifier_exists = false (valid cases)

  • Handmade and artisan products — Items made by hand by an individual or small workshop with no manufacturer barcode. Examples: handmade jewellery, bespoke ceramics, artisan candles, knitted goods.

  • Custom-manufactured products — Products manufactured to custom specifications (e.g., custom-cut materials, bespoke furniture, made-to-order items) for which no standard GTIN was assigned.

  • Vintage and antique products — Items produced before the modern barcode era (typically pre-1970s for EAN, pre-1974 for UPC). No GTIN exists because the product predates the standard.

  • Unique assembled bundles — A bundle of products you assembled yourself (not factory-packed by the manufacturer) that doesn’t have a manufacturer-issued GTIN for the bundle as a unit.

  • Certain replacement parts or components — Generic aftermarket parts sold in bulk without individual GTINs, particularly in industrial or agricultural supply chains.

When NOT to set identifier_exists = false (policy violations)

  • Branded products where you just don’t know the GTIN — Ignorance of the GTIN is not the same as non-existence. Research and find the GTIN.

  • Products sold under a recognised brand — Nike, Samsung, IKEA, Bosch, and any other established brand’s products have GTINs. Always required.

  • Products with a manufacturer-assigned MPN — If the manufacturer has a part number, submit it. identifier_exists = false suppresses the requirement but doesn’t reflect reality.

  • Laziness or feed workaround — identifier_exists = false is not a solution for feed quality issues. It is a data quality declaration that Google audits.

Rules

  • Set false only when the product genuinely has no GTIN, MPN, and no brand

  • Do not set false to suppress missing identifier warnings on branded products

  • If you set false but also provide a GTIN or MPN, the identifier takes precedence — Google will use it

  • Products with identifier_exists = false should still have rich title, description, and category data

  • The condition attribute is especially important for vintage/used products with no identifiers

Best practices

  • Audit before setting false at scale — Before applying identifier_exists = false to a large product batch, verify that these products genuinely lack identifiers. A spot-check of 10–20 random products can reveal whether false is being used correctly or as a workaround.

  • Invest in content quality for unidentified products — Without catalogue matching, your product’s title and description are the primary ranking signals. For products with identifier_exists = false, invest proportionally more in writing detailed, specific, keyword-rich content.

  • Use product_type to help Google classify — Without identifiers, Google relies more heavily on google_product_category and product_type for classification. Set both as specifically as possible.

  • High-quality images become even more important — Without catalogue enrichment, your listing won’t benefit from aggregated review stars or comparative pricing context. Strong images carry more of the CTR burden.

Impact on performance

  • No review aggregation — Products without identifiers cannot be matched across merchants for review aggregation. Your product will not show review stars unless you have your own review feed (seller ratings).

  • No price comparison — Price comparison features require product identity. Not available for products with identifier_exists = false.

  • Lower auction priority — Google’s auction gives higher priority to products it can positively identify. Unidentified products compete in a lower-priority pool.

  • Increased reliance on organic ranking signals — Without catalogue enrichment, free listing performance depends almost entirely on title quality, description, and image. Well-optimised content can compensate significantly.

Common mistakes

  • Setting identifier_exists = false on branded products to avoid the work of finding the GTIN

  • Setting identifier_exists = false on products that have MPN (the MPN satisfies the identifier requirement)

  • Using identifier_exists = false as a bulk fix for missing identifier warnings in Diagnostics

  • Omitting the attribute when a product genuinely has no identifiers (default is true — Google will show warnings)

  • Setting identifier_exists = false but still providing a GTIN (contradictory — GTIN takes precedence)

  • Not providing rich title/description for genuinely unidentified products (where this matters most)

Pro tips

  • Segment reporting by identifier status — In Google Ads, use product_type or custom_label to tag products with identifier_exists = false separately. Monitor their CTR, conversion rate, and ROAS independently. This reveals whether investing in GTIN lookup (or manufacturer registration) would have measurable ROI for your specific product mix.

  • For handmade sellers: consider GS1 registration — If your handmade business is scaling, purchasing GS1-registered barcodes allows you to assign official GTINs to your own products. This unlocks review aggregation and catalogue matching, significantly improving Shopping performance for handmade goods at scale.

  • Vintage sellers: enrich with detailed condition and provenance — Since catalogue matching isn’t available, differentiate via rich description: era, origin, materials, dimensions, and condition details. These are the keywords vintage buyers use in search and what Google’s algorithm relies on for query matching in the absence of identifiers.

  • Never batch-apply identifier_exists = false via feed rules without human review — Automated feed rules that set identifier_exists = false for entire categories or product types are a common source of policy violations. Always require explicit human sign-off per product category before applying this at scale.

Frequently asked questions

What does identifier_exists actually do?
It tells Google that your product legitimately has no GTIN, MPN, or brand identifier — that it's a unique or custom product for which no global product identifier exists. When set to false, Google processes the product differently: it doesn't attempt to match it against the global product catalogue and doesn't require these identifiers. Set it to true (or omit it — true is the default) when your product has standard identifiers.
When should I set identifier_exists to false?
Only for products that genuinely have no manufacturer-assigned identifiers: handmade or artisan items, custom-manufactured products (no standard barcode), vintage or antique goods (pre-barcode era), custom bundles you assembled yourself (no manufacturer bundle GTIN), and certain spare parts or components sold in bulk without individual GTINs. Not for branded products you just don't have the GTIN for yet.
Can I set identifier_exists = false to avoid finding the GTIN?
No. This is explicitly against Google's policies and is one of the most commonly audited data quality issues. Setting false on a branded product (e.g., a Nike shoe or a Samsung phone) that has a real GTIN constitutes data quality fraud. Google cross-references identifiers and will flag these as violations, potentially resulting in product disapproval or account suspension.
What's the default value if I omit identifier_exists?
The default is true — Google assumes your product has standard identifiers and will expect them. If your product legitimately has none, you must explicitly set false to tell Google not to look for them. Omitting the field for a product without identifiers will generate "Missing identifier" warnings.
Do I need to submit anything else when identifier_exists is false?
When identifier_exists is false, you should still provide as much identifying information as possible: title, description, brand (if any), product_type, google_product_category, and high-quality images. While identifiers aren't required, these attributes help Google understand and classify your product correctly, improving search matching and ad relevance.
Does identifier_exists affect my product's performance in Shopping?
Yes. Products with identifier_exists = false do not benefit from review aggregation, price comparison, or catalogue matching enrichment — because these features require a product identity. This is an unavoidable limitation for genuinely unidentified products. It's not a penalty; it's simply the nature of products without global identifiers. Their performance depends entirely on title, image, price, and landing page quality.
What about vintage or antique products?
Vintage and antique products typically predate the barcode era and have no GTIN. Setting identifier_exists = false is correct for these. Also relevant: vintage products are often genuinely unique (one-of-a-kind), so no catalogue match is expected anyway. Provide a detailed condition attribute (used) and rich title/description to maximise matching to relevant searches.

Related guides