Skip to main content
FHAVI

Free resource

Twelve feed fields that decide whether your products exist

A disapproved product is rarely a mystery and almost never random. A small number of fields carry most of the risk, and each has one common mistake that a merchant can check in a few minutes per item.

Read this first

Diagnose the field, not the product

When an item is disapproved, most merchants rewrite the title. That is one of twelve fields and often not the failing one. The faster route is to open the item's detail panel in Merchant Center, read which policy or attribute is named, and check that field against the reference below.

Two rules decide almost everything: the feed must agree with the landing page, and identifiers that only exist for real branded goods must not be invented. Everything else is formatting.

The reference

Each field, what it wants, and how it fails

01

Identity fields

These decide whether Google can group, deduplicate and match your items at all.

  1. ID — stable and unique per variant. Failing: reusing an id for a reworked product, so the old title and price keep resurfacing in reports.
  2. Title — your own words, with the item's real type, brand if branded, and the attribute that distinguishes it. Failing: supplier copy naming another brand, or keyword stuffing that no longer describes the item.
  3. Description — describes the actual product, not the store or the shipping. Failing: the same paragraph pasted across the whole catalogue, which reads as low-quality data.
  4. Link — the exact product page, reachable without a redirect chain. Failing: the home page or a category page, so the reviewer cannot find the item the feed describes.
02

Commercial fields

These decide whether the item is allowed to show at all.

  1. Price — matches the landing page and checkout, in the account's currency. Failing: a sale price live on the site but not in the feed, so the two disagree.
  2. Sale price — only while the promotion is genuinely running. Failing: a permanent sale price, which trains both customers and reviewers to ignore your discount.
  3. Availability — reflects inventory now. Failing: in-stock for items that cannot ship, which is the most common source of item-level disapproval on a dropshipping store.
  4. Condition — new for new stock. Failing: leaving it blank or mislabelling refurbished goods as new.
03

Identifier fields

The group where inventing data causes the longest-lasting problems.

  1. Brand — the manufacturer for branded goods, your own trading name for own-label. Failing: a brand name you do not have the right to use.
  2. GTIN — the real barcode for branded items with one. Failing: a made-up or supplier-scraped number, which fails validation and can trigger a misrepresentation flag.
  3. MPN — the manufacturer's part number, only when it genuinely exists. Failing: padding the field to clear a warning — leave it out instead.
  4. Image link — the actual product on a clean background, no logo, no text overlay, no watermark. Failing: supplier images with another brand's tag or store graphic visible.

Checking it

One item, twenty minutes, no code

04

The manual test

  1. Pick one disapproved item and open its detail panel in Merchant Center.
  2. Write down the field or policy named in the reason — not the summary heading.
  3. Open the link in the feed in a private window and confirm it shows that exact item at that exact price.
  4. Compare the twelve fields above, one at a time, against the page.
  5. Fix the single failing field, then request a re-review of that item rather than the whole account.
05

When it is not the feed

The same disapproval can come from the destination, not the data.

  1. A live page whose price differs from checkout fails the consistency check even when the feed is perfect.
  2. A store whose policy pages contradict each other can fail every item at once, which looks like a feed problem and is not.
  3. An out-of-stock catalogue produces item-level disapproval that no feed edit will fix.
  4. If every item is failing, stop looking at fields and check business identity and policies instead.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Catalogue-wide disapproval?

Send the feed and the disapproval reasons. We will tell you whether it is field data or something structural about the store.

Prefer email? Write to md@fhavi.com