Product feed

A product feed is a structured file listing everything you sell, with the details each product needs, formatted so that Google or Meta can read it without a human involved. It is the layer between your shop and every advertising surface that shows products, and it is where a surprising proportion of e-commerce performance is actually decided.

In short

• A machine-readable list of your products and their details.
• It powers shopping adverts, free listings and dynamic retargeting.
• Feed quality moves results more than bid adjustments do.
• When the feed and the product page disagree, products get disapproved.

Why the data is the lever

Search advertising works by matching what somebody typed against keywords you chose. Shopping works differently, and the difference is the reason feeds exist.

You do not choose keywords for products, so none of the campaign structure that Google Ads runs on applies here. The platform reads your feed, decides which searches each product is relevant to, and enters it accordingly. Your influence over that matching comes almost entirely from the quality of the data you supplied.

That single fact reorders the priorities for anybody advertising products. Time spent adjusting bids while the feed contains vague titles and missing attributes is time spent on the smaller lever.

The fields that carry the weight

A feed has many columns and a few of them do most of the work.

• Title. What matching runs against, and widely held to be the field with the most influence. Brand, product type, key attributes, in the order somebody would say them.
• Description. Secondary for matching, and read by people, so it should answer questions rather than repeat the title.
• Image link. The picture in the advert. Clean background, product filling the frame, no text or logos overlaid.
• Price and availability. Must match the product page exactly, and this is checked automatically.
• Product identifiers. Brand, the barcode where one exists, and the SKU naming each row as yours. Missing barcodes limit where a product can appear.
• Product type and category. How you file it and how the platform files it. Both are used.

Rewriting titles across a catalogue is dull work with a better return than almost anything else available in a shopping account.

Where feeds break

Disapprovals almost always come from a mismatch rather than from something being absent, and the pattern repeats across every store that has run a promotion. Somebody discounts a product on the website. The feed updates on its own schedule, or does not update at all because it was built by hand. For a period the file says one price and the page says another. Automated checks compare the two, the product is disapproved, and nobody notices until the reporting looks strange a week later.

The same happens with stock. An item sells out on the site and remains available in the feed, so you go on paying for clicks on something nobody can buy.

Both are prevented by the feed being generated from the shop rather than maintained alongside it. If any part of your feed is a spreadsheet somebody edits, that part will eventually be wrong.

The same file, three jobs

Once the feed exists it feeds several things at once, which is worth knowing because businesses often set it up for one and forget the others. Shopping adverts are the obvious one. Free product listings in search results come from the same source and are enabled by default now, which is a change from a few years ago. The failure there is subtler, because free listings enforce requirements that paid Shopping does not, around returns and checkout, so an item can be perfectly acceptable as an advert and blocked as a free listing without anybody noticing. Then there is retargeting, where adverts rebuild themselves around the items a visitor looked at and are assembled entirely from feed data. The image and price in those adverts are whatever the file said at the time.

One neglected file therefore degrades three channels simultaneously, which is why feed work has a better return than its reputation suggests.

Words you will hear

• Attribute. One field in the feed, such as title or price.
• GTIN. The barcode number identifying a branded product globally.
• identifier_exists. The field you set to no for own-brand or handmade goods that have no barcode.
• Merchant Center. Google’s tool where the feed lives and where disapprovals appear.
• Catalogue. Meta’s name for the same idea, and what e-commerce platforms usually generate for you.
• Disapproval. A product blocked from showing, with a reason attached.
• Feed rules. Transformations applied to the file after upload, letting you fix titles without rebuilding the shop.

Start with the diagnostics you already have

Open Merchant Center, go to Products, and read the Needs attention view before changing anything. It used to be called Diagnostics and a lot of published advice still says so. It lists every blocked product and the reason, and most shops find a cluster of one or two causes rather than a scattering.

Then sort your products by clicks and look at the titles of the top twenty. If any of them would not tell a stranger what the product is, that is the afternoon’s work, and it will move more than a month of bid adjustments.