01
A shared feed rule creates the same invalid or stale value across many rows
Item-level issue
When many products are affected, changing items one by one can hide the shared cause. MerchantProof groups observable website and product-data patterns so the most important correction can be addressed first.
What can cause it
These are investigation paths, not a claim about Google's hidden reason for your account or item status.
01
A shared feed rule creates the same invalid or stale value across many rows
02
Product destinations redirect, fail or resolve to the wrong variant or domain
03
Visible and structured product information differs from submitted data
04
A store-wide policy or functionality issue affects otherwise valid items
What MerchantProof examines
We group sampled findings by rule and evidence pattern rather than presenting an unhelpful list of repeated errors.
Deterministic sampling keeps the review bounded while retaining product IDs, source rows and affected destinations.
The human-reviewed report separates store-wide fixes from product-specific follow-up and manual checks.
Identify whether the same issue affects a pattern of products. Fixing the shared source is usually more reliable than repeatedly editing individual exported rows.
Evidence to prepare
Technical files are optional when they are unavailable. MerchantProof asks only for evidence it cannot collect safely from the public store itself.
MerchantProof Diagnostic
£99
£99 total · one-time · no subscription
MerchantProof does not access your private Merchant Center account or analyse every product in a large catalogue. Findings are based on supplied and publicly observable evidence.