Academy › Publish › Get found on Google

The missing piece in your product listing that stops Google from rejecting it

You'll know what to put in the identifier, category, availability, and image fields so Google doesn't reject your listing, and why one empty required field knocks the entire product out.

By Yodai · Published September 6, 2026 · Updated October 12, 2026

You can have the price and stock set up correctly and still have your whole catalog fail to go through. You upload the entire catalog on a Monday afternoon. On Wednesday you log into Merchant Center and half the listings have a problem with the product identifier. You haven't touched the price, the photo, or the title. So what field is that, and what do you put there if your supplier never gave you a barcode?

This isn't Google being picky. A product listing is a form with required fields, and according to Google's product data specification, if a required field is missing, the product can't run in ads or in free listings: the whole row gets left out, not just that one field. Among the common problems, Google points to an incorrect GTIN or category, low-quality images, and data that doesn't match between the feed and your website. That's where the four fields in this lesson come from: identifier, category, availability, and image. Image and availability are required. Identifier and category determine how well Google understands what you're selling. All four should be filled in before you list the product, not after the first rejection shows up.

The identifier: a field that often gets filled in halfway

The product identifier isn't your store's name or internal reference: Merchant Center's help on identifiers specifically says not to put internal references (SKUs) or other store-specific values there. It's the code that this item is recognized by in any store in the world: the GTIN, which in practice is the barcode printed on the box (in Europe, the 13-digit EAN; in North America, the 12-digit UPC). If your supplier gives it to you, copy it exactly, with no spaces or dashes.

The problem comes up with things you make yourself or build to order: a cake, a piece of furniture, a painting. There's usually no GTIN there because there's no box with a barcode, and Google allows for that: among the products that can skip it, it lists made-to-order items, works of art, and handmade goods. But it wants you to say so: set the identifier_exists field to no. Leaving it blank doesn't mean "I don't have one." If you don't send that field, Google treats it as yes, its default value, and assumes the manufacturer assigned it a code. To Google, that then looks like a product that should have a code but doesn't, and those can get less visibility or end up rejected.

Why one empty required field takes down the whole listing, not just that field

Google's category isn't the one you use in your store's menu. It's Google's closed taxonomy, with thousands of branches: "Apparel & Accessories > Clothing > Dresses" is more specific than just staying at "Apparel & Accessories." Also, Google already assigns a category to each product on its own, based on the title, description, price, brand, and GTIN. According to its help on product category, the field is only meant to correct it in specific cases: if it has placed you in a category with required fields that don't apply to you (clothing, phones, or software), to organize ad campaigns, or for alcoholic beverages. If you do set it, Google asks for the most specific one possible: go all the way down to the leaf, the category that no longer branches into subcategories.

Availability is read from your actual stock, not your intent. If your website shows "sold out" and the feed says "in_stock," that's not a small detail, it's a mismatch, and Google catches it by crawling your own site. It can reject that product, and in its guide on data quality, it warns that your entire account could be suspended over price and availability mismatches, not just that one product. That's why the feed needs to update as often as your stock changes: that same guide asks you to send your data to Merchant Center at the same time you update your website.

Images get rejected for very specific reasons, which Google lists in its help on product images: a logo or text added on top, a watermark, a border, a generic image, or a "Photo coming soon" placeholder instead of the actual product, or other products that aren't sold alongside it. What it won't accept is clutter: it wants a clear, unobstructed view of the item, focused on it alone. And starting January 31, 2027, it will require at least 500 x 500 pixels for all product images.

If you have to pick where to start when setting up a large catalog, start with what's required: without an image or availability, the product doesn't even get published. Next comes the identifier, because a product that has a code but doesn't include it shows up less. The category can be fixed without rushing: Google already assigns one, and Merchant Center flags problems product by product. Availability is the one you watch every day, because a mismatch gets that product rejected, and price and availability discrepancies put the whole account at risk.

With the identifier, category, availability, and image sorted out, your catalog enters Merchant Center with much less risk of bounces. The next thing to settle is price: the one you change in your store, and the one Google is still showing.

You switch the sync to daily so your stock doesn't catch you off guard. But feed frequency doesn't fix everything: a price you change in the store on a Tuesday afternoon might not reach Google until the next sync, and that gap also puts the account at risk.