When Google Merchant Center reports a feed problem, the visible message is often too broad to tell you what to change. A source can fetch successfully while products remain ineligible, or a valid product file can fail because the account, destination, or fetch configuration is wrong.
Classify the failure before changing the feed
Put the issue into one of four buckets: account or destination, data source, product, or landing page. A catalog-wide failure is rarely fixed at the row level, so do not start by rewriting titles or deleting products.
Check account and destination status
Confirm that the website is verified and claimed, the intended destination is enabled, and there are no account-level policy, shipping, returns, or eligibility problems. Account warnings can affect a large part of the catalog at once.
Inspect source processing
Record the latest fetch or upload time, source method, item count, accepted and rejected counts, and the exact error class. A successful fetch is not proof that the source produced usable products.
Fix fields in a controlled order
After the source processes, check stable IDs, titles, descriptions, links, images, availability, price, brand, GTIN or identifier status, and variant relationships. Change one rule or field group at a time, then compare the next processing result with the baseline.
Verify the landing page
For affected products, compare feed values with the product page, structured data, and checkout. Close the incident only after one representative product is correct end to end.
Read our common Merchant Center errors guide and use the free feed validator for a first pass.