product_feed_optimization
Your ads are fine. Your product data is the problem.
Product feed optimization and Google Shopping feed management for e-commerce brands on any platform. The feed decides which products serve, which ones win the auction, and which ones an AI assistant can quote. Bids only decide what you pay for the ones that already qualified.
what_the_feed_decides
Three decisions, made before a single bid
Every product in your catalog passes or fails these in order. A product that fails the first one never reaches the second.
What serves
A disapproved product earns nothing at any budget. Missing identifiers, a price that drifted from the landing page during a sale, or promotional text baked into an image will each take a product out of circulation quietly.
What competes
Approved is not the same as competitive. Titles that bury the matching term, a category Google guessed for you, and variants bidding against each other all lose auctions to listings with better data rather than bigger budgets.
What AI surfaces can use
Google states its newer conversational attributes support discovery on AI-driven surfaces, including AI Mode in Search. A catalog carrying no structured specifications, no pre-purchase answers, and no declared product relationships is complete by Shopping standards while giving those surfaces almost nothing specific to work with.
the_feed_became_the_page
Assistants read your feed before they read your site
A product page states its facts in marketing language, mixed into layout, sometimes inside an image. A feed states them in named fields, unambiguously. That difference is why product data has quietly stopped being a paid-media asset and started mattering everywhere your catalog gets consumed.
Google added conversational attributes to the Merchant Center specification in 2026 to serve exactly this: structured question and answer pairs, and declared relationships between products so an assistant can assemble a full solution rather than name one item. Most catalogs populate none of them, which is the gap worth taking while it is still open.
How AI search reads a catalogon_the_page
“Roomy enough for a weekend away, and it slides right under the seat in front of you.”
Reads well. States no checkable fact, so an assistant answering “will this fit under an airline seat” has nothing to quote.
in_the_feed
- product_detail
- Capacity: 40 L
- product_detail
- Dimensions: 45 x 36 x 20 cm
- question_and_answer
- Fits under a standard airline seat? Yes.
Same product. Now quotable, comparable, and eligible for a question nobody typed into a search box.
free_check
Find out where your feed actually stands
The same twelve checks we run first on any new Shopping account, in the order the consequences bite, and each one labelled as a documented requirement or a recommendation so nobody is told a best practice is a failure. No email required, and the fix list is written to be actionable whether you hand it to us, your existing agency, or your own developer.
feed_readiness_check
Twelve questions about your product data
0 / 12 answered
Answer honestly, including the ones you are not sure about. Nothing is sent anywhere and there is no email gate, so the ranked fix list at the end is yours whether or not you ever speak to us. Each check names the Merchant Center attribute it maps to, and says whether it is a documented requirement or a recommendation, because being told a best practice is a failure helps nobody.
Answer all 12 to see your result and the ranked fix list. 12 to go.
the_engagement
What we actually change
Applied as rules across the catalog rather than product by product, so the structure holds for everything you add after we leave.
Title and attribute architecture
Titles rebuilt to front-load brand, product type, and the attribute buyers filter on, applied as rules across the catalog rather than by hand, so the structure survives every new product you add.
Taxonomy and variant structure
Explicit Google product categories at the deepest accurate level, your own product_type taxonomy for reporting, and variant families grouped so sizes and colours stop splitting their own performance data.
Real-time sync and diagnostics
Price, availability, and inventory wired to the storefront rather than pulled on a schedule, plus monitoring on disapprovals so a policy change surfaces as an alert instead of as a quiet drop in impressions.
Conversational attributes
Structured specifications, genuine pre-purchase questions and answers, and declared product relationships, populated so the catalog is readable by the surfaces that answer rather than list.
Multi-channel consistency
One version of your product truth across Shopping, marketplaces, and social commerce, because contradictory data across channels is the fastest way to lose the benefit of fixing any single one.
where_we_have_done_this
Feed-connected on three channels before launch
A pet nutrition manufacturer opening a direct-to-consumer store alongside its wholesale business. We built the product data structure during the build rather than retrofitting it, so the catalog was machine-readable on the day the store opened instead of months later.
- Shopping channels feed-connected
- 3Shopping channels feed-connected
- Day indexed on Shopify AI surfaces
- 22Day indexed on Shopify AI surfaces
- Less time per wholesale claim
- 70%Less time per wholesale claim
questions
Straight answers about product feeds
What is product feed optimization?
Product feed optimization is the work of improving the product data you send to shopping channels, rather than the ads or bids that sit on top of it. The feed is the file that tells Google, and increasingly every AI shopping surface, what each product is: its title, description, identifiers, category, price, availability, images, and the relationships between products. Optimization means structuring that data so products are approved, matched to the right queries, and legible to the systems deciding what to show. It is usually the highest-leverage work in a Shopping account because it changes what you are eligible for, where bid changes only change what you pay.
What is the difference between feed management and feed optimization?
Feed management is the operational half: getting a clean, current file to every channel, handling the sync, and keeping products approved as policies and catalogs change. Feed optimization is the performance half: deciding what goes into the fields so the products win. Most tools sell management, which is genuinely useful plumbing and mostly a solved problem. Very few merchants have anyone doing the optimization, which is why a well-managed feed can still be quietly uncompetitive. We do both, and if you already have a feed tool that handles the plumbing well, we will tell you to keep it.
Why do my products keep getting disapproved?
In most catalogs we look at, the same handful of causes account for nearly all of it. Identifier gaps, where a product carries neither an accurate GTIN nor the combination of MPN and brand that Google accepts in its place. Price or availability in the feed that no longer matches the landing page, which happens most often during a promotion when the feed is pulled on a daily schedule. Images with a watermark, logo, or promotional text overlaid on the product. Missing required attributes for a specific category, which surface only once you sell into that category. Worth knowing what is not on that list: a plain white background and a product filling most of the frame are Google best practices, not requirements, and no background colour will get an item disapproved. Anyone reporting those as violations is inventing one. The real causes are all structural rather than one-off, which is why they recur until the pipeline changes rather than the product.
Does the product feed affect AI shopping results?
Google added conversational attributes to the Merchant Center specification in 2026 and states they support discovery on AI-driven surfaces, including AI Mode in Search. Those include structured question and answer pairs and declared relationships between products such as accessories, substitutes, and required parts. Here is the part you will not get from most agencies: Google publishes no ranking or inclusion effect for any of them, for AI surfaces or for Shopping, so treat any specific percentage uplift attributed to a feed attribute with suspicion, including if we ever quote you one. What is sayable without inventing anything is the structural point. A feed carrying none of these attributes serves Shopping perfectly well while giving a conversational surface almost nothing specific to work with, the attributes cost nothing but the work of populating them, and most catalogs have none of them today.
We use AI to write our product titles. Does Google need to know?
Yes, and this catches almost everyone doing AI-assisted feed work. Google requires titles created using generative AI to be submitted through the structured title attribute rather than the ordinary title attribute, with the digital source type declared as trained algorithmic media. The same pairing exists for descriptions. There is a trap inside the trap: if you submit both the structured version and the plain one, Google uses the plain title and ignores your declared version entirely, so a feed that populates both is not compliant, it is just quietly overwritten. If you are generating titles at catalog scale and have never touched structured_title, that is worth checking this week.
Do we need a feed tool, or an agency?
They solve different problems and the honest answer is often both, or sometimes neither. A tool is the right answer when the difficulty is mechanical: many channels, frequent catalog changes, complex transformation rules. It will not tell you that your titles are structured wrong or that your category assignments are costing you eligibility, because those are judgement calls about your catalog and your buyers. If your feed is small, stable, and already well-structured, you may need neither, and we would rather say so than sell you a retainer for maintenance work that does not exist.
How quickly does feed work show up in performance?
Faster than most marketing work, which is one of the reasons we start here. Disapproval fixes restore eligibility as soon as the products are reprocessed, usually within a few days. Title and category restructuring changes which queries you match, so it typically shows within two to four weeks as the channel gathers data against the new structure. Conversational attributes are the exception and we will not pretend otherwise: adoption across AI surfaces is still uneven, so that work is a position taken ahead of the demand rather than a change you will measure next month.
[ product_feed ]
The surfaces are already answering. Ride it, do not wait for it.
Waiting for AI shopping to mature means waiting while a competitor's feed gets quoted instead. Send us your feed and we will tell you what is costing you eligibility today, in writing.