Fix Google Merchant Center disapprovals at scale.

When Google disapproves a product, that SKU drops out of Shopping ads, Performance Max, and free listings instantly. The campaign budget keeps flowing to the products that are approved, so a 15% disapproval rate is not a 15% problem, it is your best-sellers absorbing spend that should have been spread across the whole catalog. Worse, a feed with many disapprovals can drag down account health and trigger broader account-level warnings.

The fastest win is rarely fixing one product. It is fixing the rule that disapproved a thousand products at once, an image too small for every SKU, a title template that capitalises everything, a missing GTIN pattern across one brand. That is the level Emberfeed operates at.

The default remedy Google hands you is per-product: open the item, see the diagnostic, fix the source, wait for a re-fetch. Fine for ten products. Hopeless for ten thousand, and it pushes the work back into your CMS or PIM where one edit takes minutes to propagate.

Emberfeed sits between your source feed and Google as a layer of catalog-wide field and filter rules. A single rule, capitalise titles in sentence case, strip promotional words, set identifier_exists to false where no GTIN exists, applies to every matching product at once. Change the rule, every affected SKU updates on the next feed refresh. No per-item edits, no touching the source data, no waiting on your store backend.

Disapprovals are reactive: you submit, Google rejects, you scramble. Emberfeed flips that. Every feed is validated against the target platform's rules before you submit it, the same checks Merchant Center runs, applied to your feed inside Emberfeed first.

The validator flags products that will be rejected, titles over length, missing required fields, images below the size floor, promotional text patterns, and offers one-click fixes where a field rule can resolve it. You see the problem list and fix it in one place, instead of discovering it days later in a Merchant Center diagnostic. Treat validation as prevention, not cleanup.

• Image too small, render every product at 1500×1500 from one image template, the source CDN image stays untouched.
• Promotional overlay on image, serve a clean, logo-only template to Google and keep your promo template on Meta, same source, two outputs.
• Missing GTIN, a conditional rule sets identifier_exists to false where no GTIN applies, clearing the limited-performance warning honestly.
• Excessive capitalization, a title field rule rewrites ALL-CAPS into sentence case across the whole catalog.
• Missing category, map your product types to Google's taxonomy with a field rule instead of editing each item.
• Mismatched value (price), see the honesty note below, this one is usually NOT feed-fixable.

Each rejection has its own page in the error database with the verbatim diagnostic text, the cause, a manual fix, and the Emberfeed rule that resolves it. For the full landscape, read the common-disapprovals guide.

This matters more than any feature list, because a tool that promises to fix everything is lying to you. Here is the honest line.

Emberfeed CAN fix (feed-level):

• →Image rules: size floor, promotional overlay, render a clean on-brand image at any dimension you set.
• →Title and text: excessive capitalization, length, promotional words stripped via field rules.
• →Identifiers: GTIN / MPN presence rules and identifier_exists handling.
• →Category and structure: map to Google's taxonomy, fix feed format and encoding, build a clean RSS output from scratch.
• →Prevention: per-platform validation before you submit, with one-click fixes.

Emberfeed CANNOT fix:

• →Price / availability mismatch between your feed and your landing page. This is the single most common disapproval, and fixing it needs landing-page sync or the Content API. Emberfeed refreshes hourly but does NOT scrape your website or push to the Content API, so it cannot reconcile a feed price against the price Google reads on your product page.
• →Misrepresentation, policy, and account suspensions. These are site-and-business level decisions (restricted products, misleading claims, untrustworthy promotions), not feed fields, so no feed tool can clear them.
• →Emberfeed is not a Shopify app. It works off your XML feed URL regardless of platform. It does not install into your store or edit your store backend.

If your top disapproval is a price mismatch, fix the price on your site or in your Content API integration first. Emberfeed earns its keep on everything else, the image, title, identifier, category, and structure rejections that are genuinely feed-fixable, plus the validation pass that stops them recurring.

Connect your existing feed URL. Emberfeed parses it and runs validation against Google's rules, producing a list of products that would be rejected. You apply bulk field rules to fix the feed-level issues, sentence-case titles, a clean image template, category mapping, GTIN handling, and re-run validation until the list is clean. Then you paste the new served feed URL into Merchant Center.

From then on, every hourly refresh re-applies your rules to fresh source data, so new products inherit the same corrections automatically. For a deeper optimisation pass beyond just clearing disapprovals, see the Shopping feed optimisation guide.