Only certain options are rejected
The main option is accepted while selected sizes or colors show issues. Resubmitting the whole family again and again leaves staff with no explanation of the item-level difference that needs fixing.
Google Merchant Center
Find out why some product variants keep getting disapproved
A few sizes or colors fail review while related options stay eligible. Resubmitting the whole product doesn't explain why. We compare affected items with accepted ones, fix confirmed feed or page differences, and follow the later diagnostic result separately.
Discuss this problemHow We Help
We begin with the affected item IDs and the issue messages attached to them. Accepted sibling options give a useful comparison, but the reason stated in the diagnostic guides our work. Visits in a fresh browser session show whether submitted links select the right option and display a matching price and availability. We then trace the relevant attributes back to their catalog or export source. We check corrected records on our side before you watch how they are processed and any further eligibility decision.
Signs This Is the Problem
Variant links select the wrong option
A submitted variant link opens the general product or selects another option. A fresh visitor sees a price or availability that disagrees with the item in the feed.
Sibling data differs unexpectedly
Closely related options have mismatched IDs or missing variant attributes. A shared product title makes the records look alike, even when the submitted item data has important differences.
What We Investigate
Compare item-level issue messages
We compare the issue messages for affected items with their accepted siblings. The evidence must support the reported reason, because variant failures can come from different data or page problems.
Test fresh-session variant links
We open submitted links in fresh sessions and look at the selected option. We compare its displayed price and availability with the exact feed item, not the parent product summary.
Trace export inheritance
We trace option attributes and IDs through the catalog export. Parent defaults and data changes along the way can explain why only certain sibling records lose information or get a value that doesn't apply.
What We Repair
Correct the variant data source
We fix confirmed values or mappings where the feed is generated. Repairing that source prevents a temporary edit to the exported file from being replaced by the same faulty data on refresh.
Align submitted option URLs
We line up supported URLs, or the selection behavior you own, with the submitted option. We check each affected variant against its actual displayed price and availability before the updated record is published.
Prepare a focused review record
We record corrected IDs and the evidence checked for each issue. Staff can follow later diagnostics without confusing a new policy or account problem with the original item-level difference.
How We Verify the Fix
- Each affected URL selects the variant shown in its submitted item record.
- Price and availability match between the sampled feed item and selected option.
- Accepted siblings keep correct attributes when the next export is generated.
- Processed diagnostics are reviewed separately from local fixes, and remaining decisions are recorded.
Questions About This Work
Can approval be guaranteed?
No. Merchant Center controls eligibility and review decisions. We fix the confirmed item data or landing page mismatch and look at later diagnostics separately. A different policy or account issue may need more work even when the original variant mapping is correct.
Must the whole feed be rebuilt?
Often not. A small comparison between affected items and accepted siblings can point to a focused change. We look into shared generation logic when that comparison reveals a repeating pattern. The agreed scope depends on which fields are wrong and where they come from.
What should we provide?
Share affected item IDs, their public links and redacted issue messages. A small feed excerpt for an accepted sibling can help explain the difference. We then identify the catalog or export access needed to trace those particular attributes, rather than asking for your entire product dataset.
Tell Us What Is Happening
Share the affected Merchant Center item IDs and product links, plus one redacted diagnostic message. A small feed excerpt for an accepted sibling helps us find the item-level difference that matters.
Explore Google Merchant Center More problems in Google Merchant Center
Ready to Get Started?
Tell us about your project and we'll get back to you within 24 hours.