AI Store AuditFree truth preview
Google Truth CSV fix page

Google Merchant Center Affected Products CSV Guide

Use the Google Merchant Center affected products CSV as an evidence file: group offer_id, issue title, attribute, destination, severity, GTIN, MPN, brand, price, stock, and landing-page rows before editing Shopify or feed rules.

Group CSV rows in checkerRequest CSV snapshot
Identifier rows

The affected attribute is GTIN, MPN, brand, barcode, identifier_exists, duplicate identifier, or custom product status.

Group identifier rowsFeed owner rows

The export points to item count, destination, feed name, fetch time, Content API, supplemental feed, or stale received values.

Run Feed TruthReviewed CSV snapshot

CSV rows, product exports, diagnostics screenshots, feed app mapping, and public product URLs disagree before a bulk edit.

Submit CSV context

Why this page exists

The Feed/GMC cluster already gets the strongest tool actions. The next useful page is not another generic Merchant Center article; it should turn a real CSV export into row groups, likely owners, and the smallest evidence tool that can prove the repair source.

Who it is for

Shopify, WooCommerce, feed-app, and agency operators who have Merchant Center diagnostics, affected-products exports, item-level warnings, or Shopping feed evidence but do not know whether to fix source catalog data, feed app mappings, GMC rules, or public product proof.

CSV row router

Route the affected-products CSV before editing fields

The CSV is an evidence file, not the repair plan by itself. Use the issue group and affected attribute to choose the smallest tool that can prove the owner.

GTIN, MPN, brand, identifier_exists rows

Rows mention gtin, mpn, brand, identifier_exists, invalid GTIN, missing identifiers, duplicate barcode, SKU-as-MPN, or custom product decisions.

Group identifier CSV rowsCount, fetch, feed owner, or destination rows

The CSV sits beside item count gaps, feed name confusion, stale fetch timing, Content API ownership, supplemental feed, or Google channel state.

Build Feed Truth reportShopify products missing or not updating

Affected rows appear because eligible Shopify products or variants are missing from Google Merchant Center or never update after product edits.

Diagnose Shopify sync pathShopping destination eligibility

The affected-products export is tied to Shopping ads destination, eligible item count, disapproved products, limited performance, campaign symptoms, or final received attributes.

Audit Shopping feed evidenceSuspension, account review, or policy overlap

Affected rows sit beside account review, appeal history, misrepresentation, policy warnings, merchant trust proof, or product-page evidence gaps.

Build suspension evidence packConflicting CSV, export, and public proof

The same item has different answers across affected-products CSV, source export, feed mapping, diagnostics screenshots, and public product URL proof.

Submit reviewed CSV context

What the audit checks

The report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.

offer_id, item ID, product title, issue title, affected attribute, severity, destination, country, and diagnostics export date
GTIN, MPN, brand, identifier_exists, price, availability, link, image, shipping, tax, policy, and landing-page mismatch rows
Whether the CSV issue is item-level, destination-level, account-level, stale diagnostics, limited performance, disapproval, or suspension-adjacent evidence
Shopify product or variant export fields: handle, SKU, barcode, vendor or brand, price, stock, status, Google channel inclusion, and product URL
Feed app, Content API, supplemental feed, Merchant Center rule, last fetch time, and public product page proof before any bulk edit
Reviewed snapshot trigger when affected-products CSV rows, product exports, diagnostics screenshots, feed mappings, and product URLs disagree
Sample report evidenceChargeable audit v0.2
High
Affected-products rows are not always product edits

A CSV row can point to source catalog data, feed app mapping, Merchant Center rules, public product proof, or account-level context. Group ownership before bulk edits.

Medium
CSV exports need matching source rows

The affected-products export is strongest when paired with product exports, diagnostics screenshots, feed mapping, last fetch time, and sample public URLs.

Queries and diagnostic phrases

Turn vague store symptoms into repeatable checks.

Google Merchant Center affected products CSVGMC affected products CSVGoogle Merchant Center affected products exportMerchant Center diagnostics CSVMerchant Center diagnostics export CSVhow to export affected products Merchant Centeraffected products CSV Google ShoppingGoogle Merchant Center issue CSVMerchant Center affected items CSVGMC affected products rows
  • CSV row grouping by affected attribute, severity, destination, and likely repair owner
  • Route decision for identifier checker, Feed Truth report, Shopify sync diagnosis, Shopping feed audit, GCR evidence, or suspension evidence pack
  • Attachment checklist for Merchant Center diagnostics screenshots, feed name, last fetch time, feed app mapping, and public product URLs
  • Reviewed 1-page Google Truth Snapshot boundary before bulk CSV, feed rule, app mapping, or appeal changes
Free precheck

Free affected-products CSV evidence intake

Start by exporting the affected-products CSV and pairing it with your Shopify, WooCommerce, or feed-app product export. Use the identifier checker for row-level GTIN, MPN, brand, and identifier_exists issues; use the Feed Truth report when counts, destinations, last fetch time, or feed ownership are unclear.

  • Group rows by issue title, affected attribute, severity, destination, country, and offer_id before changing product data.
  • Match affected rows to source catalog rows using SKU, handle, item ID, variant barcode, product title, and public product URL.
  • Separate identifier rows from count mismatch, stale fetch, Shopping eligibility, price/stock, GCR, policy, and suspension-adjacent rows.
  • Request a reviewed Google Truth Snapshot only when CSV rows, source exports, feed mapping, diagnostics screenshots, and product pages disagree.
CSV evidence packet

Copy the affected-products CSV evidence before bulk editing

Use this packet after exporting Merchant Center affected products. The goal is to preserve row identity, prove the repair owner, and decide whether the next step is an identifier cleanup, Feed Truth report, suspension pack, or reviewed CSV snapshot.

Best free path

Use the identifier checker when affected attributes are GTIN, MPN, brand, barcode, or identifier_exists

Best feed path

Use Feed Truth when CSV rows depend on item count, destination, feed owner, last fetch time, or received values

Reviewed path

Use the onsite Feed/GMC snapshot form when CSV rows, source exports, feed mapping, diagnostics, and public URLs conflict

CSV row identity
  • Export date, issue title, severity, destination, country, offer_id or item ID, title, affected attribute, and current submitted value
  • Rows grouped by identifier, price, availability, image, link, policy, destination, limited performance, disapproval, or suspension-adjacent issue
  • One sample row that looks obvious and one sample row where the owner is unclear

This keeps the diagnostic row intact so bulk edits are not made from a copied issue title with missing context.

Source catalog match
  • Shopify, WooCommerce, or feed-app export with handle, SKU, variant ID, barcode, brand or vendor, price, inventory, image URL, and product URL
  • Match rules used for offer_id, SKU, handle, variant ID, item group ID, or product title when rows do not join cleanly
  • Rows where source catalog data is correct but Merchant Center received something different

This proves whether the source product field is wrong or whether a feed app, Content API, supplemental feed, or GMC rule changed the value later.

Merchant Center and feed owner
  • Feed name, primary or supplemental feed, Content API owner, Google & YouTube app state, feed app mapping, last fetch time, and destination
  • Diagnostics screenshot for the affected group and item drilldown screenshot for a representative product
  • Public product URL proof for price, availability, image, brand, shipping, returns, and policy consistency

This separates product data cleanup from feed ownership, destination eligibility, and public landing-page evidence.

Review threshold
  • Number of affected products or variants and whether the planned edit touches many rows
  • Whether the row group overlaps account review, suspension, GCR, misrepresentation, or repeated disapprovals
  • The exact decision needed before the next bulk edit, feed rule change, app mapping change, or appeal response

This decides whether a free checker is enough or whether a reviewed snapshot is justified before a high-blast-radius change.

Minimum context to paste into the reviewed CSV snapshot form
Store URL:
Merchant Center account context: standalone / MCA / subaccount / unknown
Affected-products CSV export date:
Issue groups and affected attributes:
Total affected rows and sample offer_id values:
Destination and country:
Feed name, feed owner, and last fetch time:
Source export type: Shopify / WooCommerce / feed app / custom feed
Rows where source export and GMC received value disagree:
Public product URLs for one bad row and one good row:
Recent changes: feed app, Google channel, product edit, supplemental feed, GMC rule, policy repair, or appeal
Decision needed before bulk edit:
Group identifier rowsOpen reviewed CSV snapshot form
Evidence order

Read the affected-products CSV as an evidence file

Do not treat every row as a product edit. First identify the affected attribute, issue scope, destination, and source owner. Then compare the row with the product export, feed app mapping, Merchant Center received state, and public product URL.

Start with row identity

Keep offer_id, item ID, title, product URL, destination, country, issue title, severity, and export date together so rows can be matched back to source products.

Separate identifier rows

GTIN, MPN, brand, identifier_exists, duplicate barcode, and SKU-as-MPN rows belong in the identifier checker before feed rules are changed.

Separate feed path rows

Count gaps, stale fetches, Content API ownership, supplemental feed overrides, and destination mismatch belong in the Feed Truth report.

Attach public proof

Use public product pages to verify visible price, availability, brand, product facts, images, shipping, returns, and policy proof when Google needs buyer-visible evidence.

Snapshot handoff

When affected-products CSV rows need reviewed Google Truth

Use free tools for obvious row groups. Request review when the CSV contradicts source exports, feed app settings, Merchant Center screenshots, or public product evidence and the next change could affect many products.

Use free tools

Good enough when the affected attribute clearly maps to one source field or one visible product-page gap.

Request reviewed snapshot

Useful when the CSV says one thing, Shopify or WooCommerce export says another, and Merchant Center diagnostics or feed app mapping adds a third version.

Escalate to focused Fix Pack

Only justified when the reviewed map proves cross-system repair across source catalog, feed app, Merchant Center rules, public product pages, or suspension evidence.

Audit scope

affected-products CSV vs identifier checker vs Feed Truth report

The CSV tells you what Google grouped. The checker and Feed Truth report help decide where the repair should happen.

PathBest forEvidence requiredNext action
Affected-products CSV guideUnderstanding the export and choosing a routeIssue title, affected attribute, severity, destination, item ID, export dateGroup rows by issue and owner
Identifier CSV checkerGTIN, MPN, brand, identifier_exists, duplicate barcode, SKU-as-MPNGMC affected-products CSV plus product or variant exportOpen identifier checker
Feed Truth reportItem count mismatch, stale fetch, destination state, feed app ownership, GCR contextProduct export, GMC item count, feed name, last fetch time, diagnostics screenshotBuild Feed Truth report
Reviewed Google Truth SnapshotConflicting private screenshots, CSV rows, feed mapping, and public product proofCSV rows, diagnostics screenshot, feed mapping screenshot, product URLs, policy proofRequest reviewed snapshot

What this affected-products CSV guide cannot prove

The guide organizes the export and routes evidence. It does not replace Merchant Center account access, platform support, or Google review.

Public-page boundary

  • It does not inspect your Merchant Center account.
  • It does not guarantee Merchant Center approval, Shopping ads serving, suspension recovery, or ranking.
  • It does not verify official GS1 ownership or manufacturer identifier assignment.
  • It does not prove the repair owner without matching source exports, diagnostics screenshots, feed mapping, and public product URLs.
FAQ

Questions store owners ask before ordering an audit.

What columns should I export from Google Merchant Center affected products?

Keep offer_id or item ID, title, issue title, affected attribute, severity, destination, country, current value, product URL, diagnostics date, feed name, and any GTIN, MPN, brand, identifier_exists, price, availability, image, shipping, tax, or link fields included in the export.

Should I fix every affected-products CSV row in Shopify?

No. Some rows belong in Shopify product data, but others belong in feed app mapping, Content API ownership, supplemental feeds, Merchant Center rules, public product evidence, or account-level review.

When should I use the identifier checker?

Use the identifier checker when the affected-products CSV includes GTIN, MPN, brand, identifier_exists, duplicate barcode, invalid GTIN, missing identifiers, or SKU-as-MPN rows.

When should I use the Feed Truth report instead?

Use the Feed Truth report when the CSV is part of a product count mismatch, stale fetch, destination mismatch, feed app ownership issue, GCR problem, or Shopping eligibility problem.

Related resources

These pages connect the keyword topic to the matching workflow, sample report, and repair template.

Free toolGMC GTIN, MPN, Brand, and identifier_exists CSV Checker

Upload Merchant Center affected-products or Shopify product CSV rows to group GTIN, MPN, brand, barcode, and identifier_exists errors.

Open resourceGoogle TruthShopify to GMC Feed Truth Report

Compare Shopify product exports, GMC affected items, feed app state, and identifier fields before rewriting Merchant Center rules.

Open resourceGoogle Truth fix pageShopify Products Not Syncing to Google Merchant Center

Diagnose Shopify products not syncing to Google Merchant Center by comparing product count, variant count, channel inclusion, Google & YouTube app status, feed app exports, affected rows, and last fetch evidence.

Open resourceFeed/GMC auditProduct Feed Audit for Shopify, WooCommerce, and Google Merchant Center

Run a product feed audit evidence workflow for Shopify, WooCommerce, feed apps, GMC affected-products CSV rows, GTIN, MPN, brand, price, stock, shipping, and product URL mismatches.

Open resourceShopping feed auditGoogle Shopping Feed Audit for Merchant Center Feed Issues

Audit Google Shopping feed evidence across Shopify, WooCommerce, feed apps, Merchant Center diagnostics, Shopping ads eligibility, affected-products CSV rows, GTIN, price, stock, shipping, and landing page mismatches.

Open resourceGoogle Shopping feed issuesGoogle Shopping Feed Issues: Diagnose Merchant Center Feed Problems Before Changing Ads

Diagnose Google Shopping feed issues across Shopping destination status, eligible item count, disapproved products, limited performance warnings, affected-products CSV rows, identifiers, price, availability, shipping, images, and landing-page proof.

Open resource

Free affected-products CSV evidence intake

Start by exporting the affected-products CSV and pairing it with your Shopify, WooCommerce, or feed-app product export. Use the identifier checker for row-level GTIN, MPN, brand, and identifier_exists issues; use the Feed Truth report when counts, destinations, last fetch time, or feed ownership are unclear.