File processing
Unreachable URLs, malformed XML, encoding problems and invalid table structure.
MERCHANT CENTER FEED ERRORS
Merchant Center feed errors: diagnose the source before the next upload
FeedScore helps with the first three when the cause is visible in the source feed. It groups affected products and prioritizes systemic fixes before you fetch or upload the file again.
✓ No account✓ One-time report✓ Public URL only
AUDIT SCOPE
How to classify Merchant Center errors
Missing attributes
Required or conditionally required product fields absent from affected items.
Invalid values
Prices, availability, condition, identifiers or URLs in unexpected formats.
Landing-page mismatches
Signals that feed price or stock data may not align with product pages.
Image and link issues
Missing, invalid, blocked or duplicated product and image URLs.
Policy and account scope
Issues that must be reviewed inside Merchant Center and cannot be inferred from a feed alone.
ISSUE PRIORITY
Fix order for feed-level errors
Fix blockers first, then catalog-wide patterns, and leave isolated optimization opportunities for last.
SignalWhy it mattersRecommended action
The whole file cannot be processedEvery product is blockedFix access and syntax first
A required field is missing at scaleLarge item groups are incompleteRepair the source mapping
Price or availability differsAffected items may be disapprovedSynchronize feed generation and page data
Individual products have weak dataLimited reach or performancePrioritize active, high-value products
HOW IT WORKS
From raw feed to prioritized fixes
Start with Diagnostics
Confirm the exact issue name, scope and destination inside Merchant Center.
Audit the source feed
Check whether the same pattern is present in the current feed file.
Fix and refetch
Correct the upstream data, regenerate the feed and allow time for processing.
IMPORTANT DISTINCTION
Feed errors vs. policy issues
FeedScore can expose source-data problems. It cannot resolve misrepresentation, website, business-verification or other account-level policy decisions. Those require the official diagnostics, policy guidance and review process in Merchant Center.
FAQ
Questions about this check
Why do errors remain after I change the feed?+
Merchant Center must fetch and process the updated source. Check that the correct file was refreshed, the changed products are present and enough processing time has passed.
Should I delete and recreate rejected products?+
Usually fix the source cause first. Recreating items without correcting the underlying mapping can reproduce the same error and may disrupt stable identifiers.
Can FeedScore see account-level disapprovals?+
No. It analyzes the source feed. Account configuration, policy reviews and live Merchant Center statuses remain visible only in your Google account.
What should I fix first?+
Start with file-wide processing blockers, then high-volume required-field and mismatch problems. After eligibility issues, improve content quality and optional attributes.
METHODOLOGY & SOURCES
Built around documented feed requirements
Our public guidance is checked against first-party documentation. FeedScore adds independent data-quality checks and does not represent a platform approval decision.