makseongmakseong
Feed GuardAugust 7, 20264 min readBy Maksym Burkhan

Why Meta disapproves your products (and how it differs from Google)

If you run catalog ads on Meta - Advantage+, dynamic product ads, Instagram Shopping - you have met a different kind of disapproval from the one Google gives you. The root cause often overlaps, since the same product data feeds both, but Meta’s commerce policies are stricter in places and its explanations are thinner. Here is where Meta and Google disapprovals meet, where they part ways, and how to get a disapproved catalog back.

Meta reads the same catalog, but judges it differently

Your Meta catalog and your Google feed usually draw from the same source: the products in your store. So a data problem that disapproves an item on Google often disapproves it on Meta too. But Meta layers its own commerce policies on top, reviews with a mix of automation and manual checks, and tells you far less about why something was rejected. Where Google names the exact attribute and reason, Meta often gives a short policy label and leaves you to work out which product and which rule. That opacity is the hardest part of Meta disapprovals.

  • Meta’s catalog and your Google feed usually come from the same product data.
  • A data problem often disapproves an item on both surfaces at once.
  • Meta adds its own commerce policies and explains rejections in less detail than Google.

Where Meta and Google overlap

The shared ground is product data quality. Missing or invalid identifiers, images that break the rules, prices or availability that do not match the landing page, thin or missing required fields: these disapprove products on both platforms because both are checking that the catalog is accurate and complete. If your Google feed is clean on these, you have already removed a large share of what would trip Meta. Fixing the data once helps twice.

  • Identifiers, images, price and availability accuracy: checked by both platforms.
  • Missing required attributes weaken the listing on either one.
  • A clean product feed removes a large share of Meta disapprovals before they happen.

Where Meta is stricter or different

Meta’s commerce policies go further than Google’s in several areas, and this is where honest stores get caught. Restricted and prohibited categories are drawn differently. Images carry extra rules: Meta is strict about things like before-and-after shots, close-ups implying body or health outcomes, and personal-attribute framing that targets an implied condition. Health, supplement, and cosmetic claims face tighter scrutiny. And because much of this rides on Advantage+ and dynamic ads, a catalog-level flag can quietly switch off a whole campaign type. None of this shows up in a Google feed check; it is Meta-specific.

  • Restricted and prohibited categories are defined differently than on Google.
  • Stricter image rules: before-and-after, implied health or body outcomes, personal attributes.
  • Health, supplement, and cosmetic claims draw tighter review.
  • A catalog flag can disable Advantage+ or dynamic ads, not just one product.

Fixing a disapproved Meta catalog

Start with the data, because it is the cheapest fix and it helps both platforms: clean identifiers, compliant images, accurate price and availability. Then read the policy reason Meta gives, even if it is terse, and match it to the flagged category, since product images and product copy are the usual culprits for the Meta-specific rules. Fix the source in your store, not a patch on the ad, and use Commerce Manager to request review once the product genuinely complies. As with Google, a factual, specific appeal that points to what changed beats a general plea.

  • Fix product data first: identifiers, images, price, availability. It helps both platforms.
  • Read Meta’s policy label and map it to the flagged product and rule.
  • Correct the source in your store, then request review in Commerce Manager.
  • Appeal with specifics: what was flagged, what you changed, where it is now compliant.

One catalog, two judges

The practical takeaway is that your product data is a single source feeding two reviewers with different rulebooks. Keeping that data clean is the foundation that keeps you approved on Google and removes the easy half of Meta’s objections, leaving only the genuinely Meta-specific policy work. The stores that stay live on both treat catalog health as something to watch continuously, since a change that disapproves a product on Google is a strong hint it will trip Meta too. makseong’s free scan checks that product-data foundation: the identifiers, images, and accuracy both platforms rely on. It is an informational check, not legal advice, and it does not guarantee compliance on either platform, but a clean catalog is the cheapest insurance you have.

By Maksym Burkhan · Founder, makseong

Maksym builds focused Shopify apps at makseong and writes about Google Merchant Center, product feeds, and the compliance problems merchants actually run into.

Related guides

See it on your own store

Run a free feed scan