Knowledge Hub
What Goes In A Product Feed, Who Builds It, And Why Google Checks It
By John Butterworth · October 12, 2026
Google Shopping reads your products from a file with one row per variant, and so does each sales channel you add after it. That file is your ecommerce product feed. Every row names the variant with its ID, title and link. It then adds the image, price, stock level and barcode.
On Shopify you rarely have to build it yourself. The channel apps write it from your product admin, so the real work is keeping that data accurate. When products are approved but barely show in Shopping, I check the titles first. What I'm looking for is titles that leave out the words shoppers type.
When products look fine in the admin but never show on Google, check whether the feed and the product page disagree, because Google trusts the page. For your own check, open Merchant Centre's diagnostics and put each rejected product's page beside its row.
A Product Feed Is Your Catalogue Written Out One Row Per Variant
A product feed is a file with one row for every variant you sell, so a navy jumper in medium and the same jumper in large are two rows. Every channel publishes its own field list, and the store fills those fields with values that match what the shopper sees on arrival.
When a product is missing from Google, look first for an empty or contradictory field.
Google reads that data for its free listings and for Shopping ads. Meta reads it for catalogue ads, while Microsoft and ChatGPT now read it for their shopping answers.

ChatGPT has moved fastest. In one AI-visibility firm's tracking of ChatGPT shopping prompts, the share of picks taken from merchant feeds rose from 8.26% to 61.54% in a single day, 10th July 2026. Those product records Google checks now shape what ChatGPT can recommend from your store.
That figure covers one company's tracked prompts, so read it as a trend line. I explain how AI answers choose their sources in a separate guide.
Before you spend anything on ads, see what the free half can do: I've written about free listings as a source of traffic for Shopify stores.
Your Platform Builds The Feed From The Product Admin
Shopify Sends The Feed Through The Google & YouTube App
Connect the Google & YouTube app and every product available on your online store syncs to Merchant Centre. Any later edit flows through on its own, so a price change on Tuesday reaches the feed on Tuesday.
The app also offers a manual sync now, for stores that want to pick what goes across.
That automatic sync stops at countries you haven't set up properly. A country only syncs if it's a live Shopify market with delivery rates, so a store selling to Ireland without an Irish delivery rate sends Google nothing for Ireland.
Sometimes newly added products stop appearing while older ones are fine. The fix that works most often is to remove the data source in Merchant Centre, disconnect the app and connect it again.
Shopify also passes the same records to AI assistants, and OpenAI confirmed in March 2026 that this data already reaches ChatGPT with no extra work from the merchant. That makes the product admin the one place to fix your data for Google and ChatGPT alike.
WooCommerce And Custom Stores Use A Plugin Or A Scheduled File
On WooCommerce a feed plugin writes your existing product fields into a file at a fixed web address. Merchant Centre then fetches that file on a schedule. Set the fetch to daily, and check the plugin reads the field where you keep barcodes.
A custom build skips the file and pushes products in through the Merchant API, the replacement for the old Content API for Shopping. Any integration still written against the old interface needs moving across before it stops working.
Pay For A Feed Tool Once A Second Channel Needs Different Data
For a single channel, the native app plus Merchant Centre's own rules and a supplementary feed cover most fixes. A store selling designer brands can keep its shop name in Shopify's vendor field for Meta. It then sends each product's real brand to Google from a Google Sheet added as that supplementary feed.
A paid feed tool earns its monthly fee when one catalogue has to meet several channels' rules at once. Google and Meta want different title lengths, for example, and a marketplace may insist on its own ID format.
Every app adds weight to the store, so I'd hold off until you're selling across several channels and the native routes can't give each one its own version.
Google Reads Your Product Page To Check What The Feed Says
Merchant Centre treats each row of your ecommerce product feed as a claim, and tests it against the product page the row links to. A feed row whose price, stock or variant disagrees with that page gets corrected to match the page, or the product is disapproved from Shopping. That check runs on every product in the feed whenever Google crawls the page.

I cover the product page and its markup in a separate guide.
For the feed the page wins, and one misread field can pull a whole catalogue from Shopping while a single review request re-checks every product in it.
Send Each Variant With Its Own Link And Price
Each feed row for a size or colour has to open on that exact variant. Otherwise the page loads on the default option and Google compares your feed price with that option's price.
A custom feed or an older feed app can drop the variant from every URL it sends, and then that price check fails on each size and colour you sell.
Open three variant links from your feed and check each lands on the right option at the right price.
Expect A Disapproval If Prices Change More Than Once A Day
Flash pricing now carries a risk for products in a Shopping feed. In September 2026 Google rewrote its Merchant Centre help on automatic updates to say a product whose price or stock changes more than once a day may be disapproved instead of corrected. The corrections also stop altogether once mismatches pile up across your catalogue.
So run a time-limited offer as a sale price with start and end dates in the feed, and keep the regular feed price steady underneath.
Show The VAT-Inclusive Price On The Page And In The Feed
Outside the US and Canada, Google expects the price in an ecommerce product feed and on the page to include VAT.
Trouble starts when a UK theme shows the full price while the structured data carries the figure before tax.
Google then sees two prices that differ by the standard 20% VAT rate. A £24 jumper reads as £20 in the markup, so Google either lists it at the lower price or disapproves it.
In Shopify, set your prices to include tax for UK customers. After that, open the page source of one product and confirm the price in the Product markup matches the one on screen. If you sell in several currencies, give each currency its own URL so the price never changes with the visitor's location.
Fill The Fields That Decide Whether A Product Appears
Give Every Product A Real Barcode Or Mark It Custom
Each feed row for a branded product needs its real GTIN, which your Shopify feed takes from the barcode field on each variant. Without one the product still shows, but Google limits how often. You'll find that warning in Merchant Centre's diagnostics, so check there for missing barcodes.
If a product has no barcode at all, add its manufacturer part number (MPN) in the Google & YouTube app and set the brand and a Google product category there too. If you make the product yourself, tick the box marking it as a custom product. Google flags a made-up GTIN, and OpenAI's feed rules for ChatGPT forbid one as well.
Put The Product Type And Key Detail In The First 70 Characters
Shoppers see roughly the first 70 characters of the title in your feed, out of the 150 that Google's guidance on product titles allows. Lead with what the thing is and the detail people search for, as in 'Navy merino crew neck jumper for men in medium'.
A title carrying 'half price' or 'free delivery' reads to Google as promotional text, and so do block capitals and decorative symbols. Price and delivery already have feed fields of their own, so the title only needs to describe the product.
Rewriting every title through an AI tool without editing gives you much the same wording as other stores using that tool. Edit the output against the product in front of you.
Upload Images Of At Least 500 By 500 Pixels
Meta already turns away feed images under 500 by 500 pixels in its product data rules, and Google is moving its own minimum to the same size. Merchant Centre tags each affected product with an 'Image too small for upcoming enforcement' warning. Filter by that warning in the Needs attention list and swap those main images first. Google's feed now takes a product video link as well.
Get A Second Pair Of Eyes On Your Product Feed
Merchant Centre diagnostics show which rows Google rejects and why. Start with three product URLs from that list and compare each one against its row in the feed.
If the work is bigger than one fix, our Google Merchant Centre and feed work covers your product feed and how your products show on Google Shopping. It sits alongside the organic side of what we do as an ecommerce SEO agency for stores selling through Google Shopping.
To see where your organic search stands next to it, get a free SEO audit of your store. It lists your top keywords with their positions, plus the commercial searches competitors win where you’re not on page one, with monthly demand. You’ll get the two-page PDF the same day, with no call and nothing to pay.

