Decide when identifier_exists should be false in Google Merchant Center. Compare GTIN, MPN, brand, Shopify barcode, feed app mapping, and affected-products CSV rows before bulk edits.
You need to compare affected-products CSV rows with GTIN, MPN, brand, barcode, SKU, and identifier_exists fields before editing.
Load the identifier sampleReview before bulk falseidentifier_exists=false would be applied to many products, bundles, private-label items, handmade goods, or rows with unclear brand and MPN evidence.
Prefill reviewed requestFeed rule conflictShopify or WooCommerce rows look correct, but a feed app, supplemental feed, or Merchant Center rule may be changing identifier_exists after fetch.
Compare source ownershipDo not set identifier_exists=false just because GTIN is missing. First decide whether the product has GTIN, MPN + brand, or truly no assigned manufacturer identifiers.
Use Shopify barcode, WooCommerce GTIN field, or feed app mapping so the assigned GTIN reaches Merchant Center.
Check GTIN rowsIf no GTIN exists, check MPN + brandMerchant Center can use manufacturer part number plus true brand when no GTIN exists. Internal SKU alone is not enough.
Group MPN + brandIf no assigned identifiers exist, use false carefullyOnly then consider identifier_exists=false. Review in bulk when row evidence, public product pages, or feed mappings disagree.
Request reviewed snapshotThe weekly community evidence includes merchants asking when identifier_exists should be false versus when GTIN, MPN, and brand must be supplied. GSC also shows early impressions for identifier_exists, so this page should answer the exact decision and route users into the identifier checker before bulk changes.
Shopify, WooCommerce, feed-app, and agency operators cleaning Merchant Center affected-products rows where identifier_exists, GTIN, MPN, brand, barcode, or custom product rules are unclear.
The same warning can mean missing GTIN, missing MPN + brand, true custom-product status, or a feed mapping override. Choose the smallest evidence path that proves the owner.
You have a Merchant Center export and need to preserve offer_id, issue title, affected attribute, severity, destination, and submitted value.
Read the CSV evidenceIdentifier decision checkerRows mention GTIN, MPN, brand, barcode, SKU-as-MPN, duplicate barcode, missing identifiers, or identifier_exists mismatch.
Group identifier rowsBroader missing identifier guideYou need the full GTIN vs MPN + brand vs identifier_exists=false decision tree.
Open missing identifiers guideFeed ownership conflictCorrect catalog rows exist but Merchant Center receives blank, stale, or overwritten identifier fields.
Compare feed ownershipThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
If the product has GTIN or MPN + brand, setting false can turn a missing-field issue into a product identity mismatch.
Changing false values across many variants should be reviewed against source exports, affected-products CSV rows, and feed mappings first.
Many rows only need MPN + true brand. The hidden problem is often vendor/brand mapping, not whether identifier_exists should be false.
Run the identifier CSV checker before setting identifier_exists=false. The free path is enough when row ownership is obvious; request a reviewed Feed Identifier Truth Snapshot when false values affect many rows or the source evidence conflicts.
Use this packet when identifier_exists=false could hide missing GTIN, MPN, brand, barcode, feed mapping, or public product identity evidence. The goal is to prove whether each row needs GTIN, MPN + brand, true false, or feed ownership review.
Rows mention identifier_exists=false, missing identifiers, GTIN, MPN, brand, barcode, SKU-as-MPN, duplicate barcode, custom products, handmade goods, bundles, or feed rule overrides.
Affected-products CSV, product export, GTIN/barcode field, MPN, brand, SKU, product type, feed mapping screenshots, final received attributes, and sample public product URLs.
Decide whether to send GTIN, send MPN + brand, set identifier_exists=false, fix source catalog fields, repair feed mapping, remove a bad override, or request reviewed Feed Identifier snapshot.
This proves whether identifier_exists=false is disallowed because real manufacturer identifiers are present or should be supplied.
This proves when identifier_exists=false is a product identity decision rather than a shortcut to clear a warning.
This proves whether the repair owner is source data, feed mapping, supplemental feed, or Merchant Center rule ownership.
This decides whether the free checker is enough or whether a reviewed snapshot is safer before a high-blast-radius false value change.
identifier_exists decision evidence packet:
Assigned identifiers: GTIN/UPC/EAN/ISBN/GTIN-14, barcode, MPN, brand, manufacturer, product type, variant source fields.
No-assigned-identifier proof: custom/handmade/private-label/bundle context, no GTIN, no MPN + brand, reason false applies.
Feed received state: source export, generated feed sample, feed app/API owner, final received GTIN/MPN/brand/identifier_exists, affected CSV.
Bulk risk: affected row count, destination, country, sample true-false row, sample GTIN row, sample MPN+brand row, sample feed conflict row.
Decision needed: send GTIN, send MPN + brand, set identifier_exists=false, fix source field, repair feed mapping, remove override, request reviewed Feed Identifier snapshot.The false value tells Google that the product has no assigned identifiers. It should not be used to hide missing data for products that actually have manufacturer identifiers.
Custom goods, some handmade products, one-off private items, or products without assigned GTIN/MPN/brand identifiers may qualify after row review.
If the product has a real GTIN, MPN, or brand but Shopify, WooCommerce, or the feed app is not sending it, fix the source field instead.
Bulk false values can hide source-data quality problems and create a different product identity mismatch.
Supplemental feeds or Merchant Center rules can overwrite identifier_exists after the source platform sends correct data.
The useful action is not to answer yes or no from memory. The useful action is to inspect a few affected rows, source exports, and feed mappings before applying false to the catalog.
Compare Shopify variant barcode, GMC affected row GTIN, feed app mapping, and any rule that changes GTIN or identifier_exists.
MPN needs a true brand pair. A supplier name or Shopify vendor value may not be the manufacturer brand.
Treat custom-product or identifier_exists=false flags as product identity choices, not suppression toggles.
Use reviewed snapshot intake before changing hundreds of products, especially when the repair owner could be Shopify, a feed app, or GMC rules.
Choose the identity path per product. The right answer can differ across variants, handmade goods, bundles, private-label products, and manufacturer-branded products.
| Path | Use when | Do not use when | Next action |
|---|---|---|---|
| GTIN | The product has an assigned UPC, EAN, ISBN, or GTIN-14. | The value is an internal SKU, placeholder, or copied supplier code. | Fix barcode or GTIN mapping. |
| MPN + brand | No GTIN exists, but manufacturer part number and true brand are known. | Brand is just a supplier, collection, vendor label, or unknown. | Fix brand and MPN source fields. |
| identifier_exists=false | The product truly has no assigned identifiers. | Identifiers exist but are missing, unmapped, stale, or overwritten. | Review row evidence before bulk false. |
This page organizes product identity evidence. Google, feed providers, and your source platform still control processing and final eligibility.
Use identifier_exists=false only when the product truly has no assigned identifiers such as GTIN or an MPN + brand pair. Do not use it when identifiers exist but your feed is missing them.
Not automatically. If no GTIN exists, check whether MPN + brand exists. If either GTIN or MPN + brand exists, fix that source instead of setting false.
Only if vendor is the true product brand or manufacturer. Many stores use vendor as supplier, source, or collection label, so verify before pairing it with MPN.
Yes when many products are affected or when Shopify exports, feed app mappings, Merchant Center affected rows, and public product pages disagree.
Run the identifier CSV checker before setting identifier_exists=false. The free path is enough when row ownership is obvious; request a reviewed Feed Identifier Truth Snapshot when false values affect many rows or the source evidence conflicts.