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.
The SEMrush and GSC-backed plan identifies Google Shopping feed issues as a broader acquisition route around the Feed/GMC evidence cluster. The page should capture problem intent and route it into Feed Truth, affected-products CSV, identifier cleanup, Shopping audit, or product feed audit paths.
Shopify, WooCommerce, DTC, and agency teams managing Google Shopping, Merchant Center, product feeds, feed apps, Google & YouTube channel data, Shopping ads eligibility, and source catalog repairs.
Google Shopping feed issues can look like ad performance problems, but many start in source data, feed generation, Merchant Center received attributes, destination eligibility, or landing-page proof.
Shopping destination item count, eligible item count, active item count, generated feed rows, source product count, feed owner, or last fetch time does not line up.
Build Feed Truth reportIdentifier or product identity rowsAffected rows mention GTIN, MPN, brand, identifier_exists, invalid GTIN, missing identifiers, duplicate barcode, custom product, price, availability, image, or landing-page mismatch errors.
Run identifier checkerAffected-products CSV row groupingYou exported affected-products rows and need to group issue title, attribute, severity, destination, offer ID, country, and likely repair owner.
Route affected CSV rowsShopping destination auditShopping ads eligibility, disapproved products, limited performance warnings, destination state, product groups, or campaign symptoms need a focused Merchant Center audit.
Open Shopping feed auditBroader feed or marketplace issueThe issue also affects other marketplaces, channel feeds, WooCommerce, Shopify feed apps, source catalog ownership, or public product evidence outside Google Shopping.
Open marketplace feed troubleshootingThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
Eligible item count, disapproved products, limited performance, final received attributes, and landing-page mismatch evidence should be checked before campaign changes.
The issues page can capture broader search demand while routing high-intent visitors into Feed Truth, affected CSV, identifier, Shopping audit, and product feed audit workflows.
Start with the feed evidence, not the ad campaign. Compare source catalog rows, generated feed output, Merchant Center received attributes, affected-products CSV, Shopping destination state, and public product pages before editing bids, product groups, or feed rules.
When Shopping products stop serving or show limited performance, changing bids can be the wrong move. First prove whether Google received the right product data and whether the Shopping destination can use it.
Capture active, eligible, pending, limited, and disapproved product counts by country and destination before treating the issue as a campaign problem.
Check final received values, last fetch time, feed source, affected-products CSV, and diagnostics names before editing source catalog rows.
Compare Shopify or WooCommerce exports with generated feed output, feed app mapping, supplemental feeds, Content API ownership, and Merchant Center rules.
Confirm visible price, stock, shipping, returns, images, product identity, brand, identifiers, canonical URL, and variant URL before appealing or changing product groups.
The page should not push every visitor into paid audit. Use free triage when evidence is simple; use Shopping feed audit or product feed audit when private evidence crosses systems.
Best for source count, eligible item count, stale fetch, feed ownership, received-state, Google channel, and destination mismatch problems.
Best for affected-products CSV, GTIN, MPN, brand, identifier_exists, price, availability, image, shipping, tax, and landing-page mismatch grouping.
Best when Merchant Center diagnostics, generated feed, app mapping, source export, screenshots, campaign symptoms, and public product URLs disagree.
Use the issues page to triage symptoms, the Shopping feed audit for Merchant Center and Shopping destination evidence, and the product feed audit when ownership crosses channels.
| Path | Best for | Evidence required | Next action |
|---|---|---|---|
| Google Shopping feed issues | Problem-intent triage for eligible item count, disapproved products, limited performance, price, stock, image, shipping, and landing-page mismatch | Symptom, destination, affected rows, feed source, item counts, product URLs | Choose evidence route |
| Feed Truth report | Source count, fetch timing, feed ownership, Content API source, and Merchant Center received-state mismatch | Source export, feed URL or name, item count, last fetch time, diagnostics screenshot | Open /tools/shopify-to-gmc-feed-truth-report |
| Shopping feed audit | Focused audit of Merchant Center diagnostics, Shopping destination eligibility, affected CSV rows, and Shopping ads symptoms | Diagnostics, affected-products CSV, Shopping destination, source export, feed output, public product pages | Open /audit/google-shopping-feed-audit |
| Product feed audit | Cross-channel source catalog, generated feed, feed app, marketplace, Shopping, WooCommerce, Shopify, and public-page ownership | Platform export, feed output, mappings, destination diagnostics, affected rows, screenshots, product URLs | Open /audit/product-feed-audit |
This page routes feed evidence. It does not replace ad management, feed provider access, Google decisions, or ongoing catalog operations.
Start by identifying the evidence owner: Shopping destination state, Merchant Center received attributes, affected-products CSV row, source catalog field, generated feed mapping, or landing-page proof. Then use Feed Truth, identifier checker, affected CSV guide, Shopping feed audit, or product feed audit based on the owner.
Limited performance can involve missing identifiers, weak product identity, destination eligibility, feed attributes, policy signals, price or availability mismatches, or landing-page proof. Group affected rows before changing campaigns.
Not if eligible item count, disapprovals, affected CSV rows, or Merchant Center received attributes are unclear. Prove the feed evidence first, then adjust campaigns if the feed is clean.
Use a focused audit when Merchant Center diagnostics, affected-products CSV, feed app settings, source exports, campaign symptoms, and product pages disagree or the repair affects many products.
Start with the feed evidence, not the ad campaign. Compare source catalog rows, generated feed output, Merchant Center received attributes, affected-products CSV, Shopping destination state, and public product pages before editing bids, product groups, or feed rules.
