Every requirement FeedGuard checks

49 deterministic checks, in 8 groups, run against every product in your catalogue. Each one names the attribute the shopping platforms ask for, which platform enforces it, and one line on why it matters. Nothing here is invented: every check is traceable to the published specification.

The same list drives the audit. When a product fails a requirement you get the exact field and the value at fault, and the corrected CSV carries the fixes we can make without inventing data.

Titles

The title is the single most visible attribute: it is what shoppers read in Shopping and what the platform matches against your landing page.

Product titlestitle

Google Merchant CenterMeta

A plain-text product name, max 150 characters, with no promotional wording and no ALL CAPS.

Read the requirement, the fixes and how we check it →

Descriptions

Required on every item, plain text only, and long enough to describe the product.

Identifiers — GTIN, brand, MPN

The barcode, brand and part number are how a platform knows which product this is, and how it matches your item to the same product sold elsewhere.

GTIN / barcodegtin

Google Merchant CenterMeta

If your product has a manufacturer barcode, submit it — correctly, digits only, and only once per product.

  • GTIN/barcode missingrequired in some cases— A product with a manufacturer barcode must submit its GTIN — items with a GTIN but no value submitted can get limited visibility.
  • GTIN wrong lengthrequired— GTIN values must be 8, 12, 13 or 14 digits (EAN/JAN, UPC, EAN, ITF-14).
  • GTIN fails its checksumrequiredcommonly suppresses— The GTIN checksum digit must be present and correct (GS1 validation). A GTIN that fails its checksum is treated as an incorrect identifier.
  • GTIN uses a restricted or coupon prefixrequired— GTINs must not be restricted (GS1 prefix ranges 02, 04, 2) or coupon codes (98–99).
  • GTIN used by more than one itemrequiredcommonly suppresses— A GTIN identifies exactly one product — the same barcode on several items causes identifier conflicts and disapproval.

Read the requirement, the fixes and how we check it →

Price, sale price and stock

Price and stock decide whether an item can serve at all, and they are re-checked against your landing page — a mismatch is a common cause of disapproval.

Images

One required crawlable image per item, in an accepted format, plus optional extras.

Main imageimage_link

Google Merchant CenterMeta

One required image per item: a full https URL to a crawlable product photo in an accepted format.

  • Main image missingrequiredcommonly suppresses— Image_link is required — a product with no image cannot serve.
  • Image URL is not a usable URLrequired— Image_link must be a valid http/https URL in a supported image format.
  • Main image not reachablerequiredcommonly suppresses— The image must be crawlable — Google has to be able to fetch image_link; this URL did not respond successfully.
  • Image served over http://, not https://data quality— The image URL is an http:// address. Products are browsed on https pages and every modern platform serves images securely, so an insecure image URL is fetched over a weaker connection and is blocked as mixed content in the browser — it is the first thing that breaks when a store moves to https.
  • Image URL is a placeholder, not the productdata quality— The image URL points at a stand-in file rather than a photo of the product: a theme's "no image yet" graphic, a spacer, or an inline data: URI. Google's Product structured data guidelines ask that the image represent the item it is attached to, and a placeholder is not the product — shoppers are shown the stand-in.

Read the requirement, the fixes and how we check it →

Categories, IDs and shipping

The identifiers and categories that organise your catalogue: the item id, your product type, Google's taxonomy, and the weight carrier rates need.

Product structured data (JSON-LD)

Google reads the Product markup on your product page to build merchant listings and to cross-check the page against your feed. FeedGuard reads the JSON-LD on a sample of your product pages and reports what it found — or that it could not read the page, which is never counted against you.

Product structured data (JSON-LD)structured_data (on the product page, not a feed column)

Google Merchant Center

Google reads the Product markup on your product page to build merchant listings and to check the page against your feed. We read the JSON-LD on your product pages and tell you what is there — or that we could not read it.

  • No Product structured data on the product pagerecommended— No Product structured data (JSON-LD) on this item's own product page. Google reads it to build merchant listings — the shopping knowledge panel, Google Images, popular product results and product snippets — and recommends putting it in the page's initial HTML; without a Product node the page is not eligible for those.
  • No brand in the structured datarecommended— The Product structured data on this item's page publishes no brand. Google lists brand.name as a recommended property of Product markup: it is how the page is matched to the same product sold elsewhere, and it is the brand your feed submits.

Read the requirement, the fixes and how we check it →

Meta catalogue requirements

Meta's own catalogue specification is not identical to Google's: a 200-character title limit it recommends you stay well under, plain-text descriptions with no links, JPEG or PNG images at 500 × 500 or larger, and a product link on your own domain. These checks carry Meta's rule ids and are labelled Meta wherever they appear.

Meta's catalogue caps a title at 200 characters, recommends fewer than 65, asks for title case and no promotional wording.

Read the requirement, the fixes and how we check it →

Plain text only, sentence case, no links — Meta reads your description literally and does not parse HTML in it.

  • Description written in ALL CAPSrequired— Descriptions in all capital letters are not supported by Meta — the description must be written in sentence case.
  • Description contains HTML or entitiesrequired— Meta asks for plain text in the description, not HTML or rich text — markup is shown to shoppers as literal tags or dropped.
  • Description contains a linkdata quality— Fails Meta's documented description guidance: don't include links to your website in the description — the product URL belongs in the link field.

Read the requirement, the fixes and how we check it →

Meta product imagesimage_link

Meta

Meta accepts JPEG or PNG only, at least 500 × 500 pixels — narrower than Google's accepted set and with a pixel minimum of its own.

  • Image below Meta's 500 × 500 minimumrequired— Meta requires a main image of at least 500 × 500 pixels; smaller images are commonly rejected or cropped in its ads and shops.
  • Image not in Meta's JPEG or PNG formatrequired— Meta accepts images in JPEG or PNG format only (up to 8 MB). Formats Google accepts, such as GIF, WebP, BMP and TIFF, are not usable in a Meta catalogue.

Read the requirement, the fixes and how we check it →

The product page URL on your own domain — absolute, http/https, and not a Facebook or Instagram page.

  • Product link missingrequiredcommonly suppresses— Link is required — Meta needs the URL of the product page for that exact item, and an item without one cannot serve.
  • Product link is not a usable URLrequired— Links must begin with http:// or https://, be valid, and be hosted on your own website — not a Facebook or Instagram page.

Read the requirement, the fixes and how we check it →

How a check becomes a failure

  • A requirement that doesn't apply to an item is left out of the audit for that item — it is never counted as a pass and never counted as a failure.
  • A requirement our data source cannot see at all (a Shopify store scan cannot read barcodes, for example) is reported as “not checked from this source”, with the reason, and it is excluded from the score. That is our blind spot, not yours.
  • The score is the share of applicable requirements your catalogue passes, weighted by how much each failure typically costs: critical 3, important 2, minor 1.
  • A failure is always phrased as a requirement the data fails — never as a claim about your account. Fixing the field is the whole job.

Want the full audit rather than the list? Run it free on your store — paste a domain, paste a feed URL, or upload a product CSV.

Requirements and their wording come from Google's product data specification and Meta's catalogue requirements for the core attributes. Each guide page states the basis it is judged on: required, required in some cases, recommended, or a data-quality check we flag.