Feed/GMC Truth Snapshot sample

Shopify GMC Feed Identifier Truth Snapshot Sample ecommerce audit report example.

An illustrative Feed/GMC truth sample where Merchant Center affected rows, Shopify variant exports, feed app mappings, and identifier_exists decisions need one evidence trail before rules are changed. Use this illustrative report example to see which evidence belongs in an ecommerce website audit template, which findings belong in an AI worksheet, and which blockers should move into a reviewed Truth Snapshot or focused audit.

Illustrative sample only. This page is not a customer testimonial, endorsement, or paid case study. Third-party brand names may appear only as compatibility or search-context examples.

Report blockers

  • Merchant Center affected-products rows show invalid GTIN and missing identifiers, but the Shopify export uses mixed barcode, SKU, MPN, and vendor fields.
  • A feed app and a supplemental rule may both rewrite identifier_exists, making it unclear whether the source fix belongs in Shopify, the feed app, or Merchant Center.
  • The team wants to edit feed rules immediately, but public product evidence and variant ownership have not been reconciled.

AI worksheet fields

shopify products not syncing google merchant centerGMC GTIN MPN brand CSV checkeridentifier_exists false Google Merchant Center ShopifyShopify barcode not syncing Google Merchant Center

First repair path

  • Load affected-products and Shopify product export rows into the free identifier checker before changing feed rules.
  • Group rows by likely owner: Shopify product data, feed app mapping, Merchant Center rule, supplemental feed, or public product page evidence.
  • Request a reviewed Feed Identifier Truth Snapshot only when the free checker shows source conflict, identifier_exists risk, or bulk variant impact.
Truth Snapshot evidence trail

Map each blocker to the source system before changing rules.

Open identifier checker sample
Use this when Feed/GMC actions lead the conversion board

This sample shows why Feed/GMC tool users may need a reviewed 1-page Truth Snapshot after loading sample rows, downloading the intake CSV, or saving a snapshot.

Evidence sourceWhat to captureRisk if skippedNext action
Merchant Center affected-products CSVOffer ID, issue title, attribute name, severity, current GTIN, MPN, brand, and identifier_exists value.Google may be flagging the transformed feed row, not the Shopify source row.Match each affected offer ID to the Shopify variant ID or feed app row before editing identifiers.
Shopify product or variant exportVariant barcode, SKU, vendor or brand, product title, variant title, and last product edit time.SKU-as-MPN, duplicate barcodes, or blank brand fields can create false confidence in a bulk repair.Separate rows that need manufacturer GTIN from rows that need MPN plus brand or identifier_exists=false review.
Feed app or Merchant Center rule screenshotField mapping, supplemental feed ownership, content API source, last fetch time, and rule priority.A rule override can keep sending the wrong value even after Shopify product data is fixed.Decide whether the fix owner is Shopify data, feed app mapping, supplemental feed, or a Merchant Center rule.
Public product page evidenceVisible brand, model, barcode/MPN if shown, price, availability, return/shipping proof, and product URL.Identifier repair can still fail if public product facts and Merchant Center data tell different stories.Attach representative product URLs to the reviewed snapshot when trust, policy, or feed evidence overlaps.

Run this same evidence preview for a real store.

The live scanner checks public pages first, then prepares ecommerce SEO, merchant trust, schema, Commerce Truth routing, and AI worksheet prompts for a reviewed report path.