Getting Your Products Into Google's Free Shopping Listings

Free product listings cost nothing and most small retailers are not in them. The work is unglamorous data hygiene, not marketing. Here is exactly which fields decide whether your items get approved, the five non-product requirements that block everything else, and the local inventory advantage an online-only seller cannot copy.

Small business owner photographing a pair of shoes for an online store listing, with a laptop and shipping boxes on the desk

If you sell physical products and you are not in Google's free product listings, you are skipping the one place Google will show your inventory, your price, and your store name to someone who has already decided to buy. Appearing there costs nothing. It costs an afternoon of unglamorous data work, which is exactly why most small retailers never do it.

This is the practical version of that work: the two routes in, the product attributes that decide whether your items get approved or quietly rejected, and the mistakes that account for most disapprovals. If you run a store in New Jersey or New York with a physical location, there is a second payoff at the end that online-only sellers cannot access.

What the free listings are, and where they show up

Google made organic product listings free several years ago. The surfaces shift, but the pattern is stable: the Shopping tab is almost entirely free listings, product results appear inside regular Search on shopping-intent queries, and items surface in Google Images and in the product panels alongside branded searches.

The mental model that matters: these listings do not come from your web pages the way a blue link does. They come from a structured record of each product, with fields. Google is not reading your product page as prose and inferring what the item is. If the fields are wrong or missing, the product is suppressed or shown badly. Which means ordinary SEO work does very little for you here. You can have a well-optimized product page that never appears in a single product listing, because the record behind it is incomplete.

The two routes in, and why you want both

A Merchant Center feed. Create a Google Merchant Center account, verify and claim your website, submit a product feed. Every mainstream platform can generate one: Shopify and BigCommerce have native integrations, WooCommerce has well-maintained feed plugins, a custom store can produce a scheduled XML or TSV file. The feed is authoritative, updates on a schedule you control, and is the only route that gives you Merchant Center diagnostics, which is where you find out what is broken.

Product structured data on your pages. Google can also discover products by crawling your site and reading Product and Offer markup in the page's JSON-LD. No Merchant Center account required, and for a very small catalog it beats nothing.

Run both. The feed is faster and more reliable; the on-page markup keeps your product data consistent for everything else that reads pages rather than feeds, including AI assistants and comparison tools. And when the two disagree, you find out. A mismatch between the feed price and the price rendered on the landing page is one of the most common reasons a product gets rejected.

The attributes that actually decide approval

The feed specification is long and most of it is optional. These are the fields that decide whether your products get in.

A stable id. Every purchasable item needs a unique identifier that does not change. If ids are derived from the product title, your performance history resets every time someone edits a name. Use the platform's internal SKU or variant id.

A title written for a listing, not for a page. The feed accepts a long title but listings truncate well before the end, so the front carries all the weight. The convention that works is brand, product type, then the one or two attributes a buyer distinguishes on: size, color, capacity, material, model. "Weber Spirit II E-310 3-Burner Propane Gas Grill, Black" works. "Our Best-Selling Grill Is Finally Back In Stock" will likely be rejected outright, because promotional language in titles violates policy. No all caps, no exclamation marks, no "free shipping," no price.

link, image_link, price, availability, condition. The link must go to the specific product page, not a category. The image must be the product on a plain background, with no watermark, logo, promotional badge, or text overlay burned in. Google enforces a minimum image resolution and the threshold is higher for apparel than other categories, so check the current spec rather than guessing. Extra angles go in additional images, not a collage in the main one.

brand plus a product identifier. For anything manufactured, supply the GTIN. This is the highest-value field most small catalogs are missing, because the GTIN is how Google matches your listing to the same product sold elsewhere, which is what gets you into comparison panels at all. If you make the product yourself and it has no barcode, there is a dedicated attribute to declare that no identifier exists. Declaring it honestly is fine; leaving the field blank with no declaration is not.

Variant grouping. Four sizes and three colors is twelve purchasable items, each needing its own row with its own availability and price, tied together by a shared item group id plus the size, color, material, or pattern attributes. Submit a single row for a product with variants and you end up advertising a size that is out of stock.

The non-product requirements that block everything else

You can have a perfect feed and still be rejected, because Merchant Center also assesses whether your store looks like a real business that can take an order. Have these in place before you submit anything.

Most first-time rejections are one of these five, not an exotic feed problem. Walk the list before blaming the data.

The local advantage, if you have a physical store

If you have a staffed location customers can walk into, you can submit local inventory alongside your online catalog. Your items then become eligible to appear to nearby shoppers as available in store, with the store name, and optionally with pickup.

For a retailer in Hoboken, Jersey City, or anywhere in the five boroughs, that is a different competitive position than fighting national sellers on price. Someone searching within a few miles of your door is a different buyer, and a listing saying the item is on a shelf nearby answers a question free shipping does not.

The requirements are heavier: in-store quantities have to be accurate and refreshed frequently, which means your point of sale and your online catalog need to agree. If stock counts live in a hand-maintained spreadsheet, fix that first. A local listing that is wrong does more damage than no listing.

This pairs with the rest of your local presence. If you are already investing in local SEO work and neighborhood landing pages, local inventory is the commerce layer on top of it, and the same accurate hours, address, and category data feeds both.

Structured data on the page, done honestly

On the product page, mark up Product with an Offer carrying price, currency, and availability, generated from the same source of truth as the page body. Hardcoded markup drifts within a month and then actively hurts you.

One warning: do not add aggregate rating markup unless real customer reviews are displayed on that page. Marking up ratings a visitor cannot see is a structured data violation that can get rich results disabled across your whole site. The stars are not worth it.

How to tell whether any of this worked

Three places, in this order. Merchant Center diagnostics gives you active versus disapproved counts with a reason per item; that should be at or near zero before you look at anything else. Merchant Center performance shows impressions and clicks per product, which is where you discover four items carry the whole catalog. Search Console's merchant listings report tells you whether Google can parse the markup on your pages, a different question from whether your feed is clean. Give it a few weeks before judging; new records go through review.

The order to do this in

Starting from nothing, the sequence that wastes the least time is: publish the shipping and return policy pages, create and verify Merchant Center, connect your platform's feed integration, clear every disapproval reason before touching anything else, rewrite titles for the top twenty items by revenue, then add local inventory if you have a store.

This work gets skipped because it is tedious, never ends, and nothing visibly breaks when you ignore it. Feeds drift. Products go out of stock and the record does not update. A platform upgrade changes how prices render, three hundred items get flagged for a landing page mismatch, and nobody notices for a month because no human is reading the diagnostics.

That is the shape of problem AI agents are good at, and it is how we deploy them. An agent team can read Merchant Center diagnostics on a schedule, classify each disapproval reason, fix the mechanical ones, draft corrected titles for a human to approve, and flag a failing feed the same day rather than the next quarter. The catalog stays clean because something is watching it, not because someone remembered.

Where to start

i4US builds and maintains online stores for businesses across New Jersey and New York, including the product data layer behind them. If you want the catalog work handled alongside the storefront, see our custom e-commerce store development, or look at the web design and e-commerce work we do in Hoboken if you are nearby. When you are ready to talk specifics, tell us about your store and we will scope it. Reach us at (718) 450-2000 or hello@i4us.com.