Key Takeaways
- A broken product feed rarely looks broken: products import and ads run, but the data is too thin for Google and AI to use well.
- A representative product scored 28 out of 100 on AI-readiness because its title, attributes, and description carried almost no signal.
- Fixing the title, filling the attributes, deepening the description, and clearing Merchant Center issues took it to 92 without changing the product itself.
- Brand names and identifiers stayed locked during the cleanup, with 98.2% of changes approved automatically and only 1.8% flagged for review.
- One layer of enrichment paid off twice: better data for Google Shopping and Performance Max, and eligibility to be recommended on AI surfaces.
What a Broken Product Feed Actually Looks Like
A broken product feed rarely looks broken. Products import, ads keep running, a few orders come in, and the dashboard stays green. Nothing screams for attention. That is exactly why so many feeds sit half-finished for years while the merchant assumes the data is fine.
Take one product we scored: a men’s dress shirt listed as “Blue Shirt Men”. Color field blank. Material blank. No tags. Its UCP Score, the 0–100 read on how ready a product is for AI to understand and recommend it, came back at 28. Not a disaster on Google, where the ad still served. But a 28 means an AI assistant reading that listing has almost nothing to work with, and most of the catalog around it scored the same way. This is what a broken product feed looks like from the inside: technically live, quietly invisible.
Most feeds land between 25 and 40 out of 100 on AI-readiness, so a 28 is normal, not exceptional. That is the uncomfortable part. Normal is the problem. This is the story of taking one representative feed from a 28 to a 92, what got fixed, and what changed on both Google Shopping and AI surfaces once it did.
Where the Score Was Leaking: The Diagnosis
Before touching anything, the feed got scanned against more than 50 Google Merchant Center validation rules and scored product by product. A score alone is a verdict. The diagnosis is where the score is leaking, and for this catalog the leaks were the same handful you find almost everywhere.
Titles carried the least information. “Blue Shirt Men” tells a shopper nothing and tells an AI even less. No brand, no material, no fit, no occasion. Attributes were the next hole: color, material, size, and pattern fields sat empty across most of the catalog, even though the answers were sitting right there in the product photos and descriptions. Descriptions themselves were two marketing lines that repeated the title. And a scatter of GMC issues, from missing GTINs to a few outright disapprovals, kept some products out of the running entirely.
None of this was the merchant’s fault. The feed came out of a store platform that emits the minimum to run an ad and stops there. Nobody built it to lose. It just was never built to win a recommendation.
The Cleanup, Attribute by Attribute
The fix followed the score. You clear the biggest leaks first, because a handful of fields move the number more than everything else combined.
Titles came first. “Blue Shirt Men” became “Premium Sapphire Blue 100% Cotton Men’s Casual Dress Shirt — Breathable & Lightweight.” Same product, but now the brand, color, material, fit, and a real feature all live in the title where both Google and an AI assistant read first. Then the empty attributes got filled: color set to blue, material to cotton, size and pattern populated from the source data, so every field a shopper might filter or ask on had an answer.
Descriptions were rewritten to say what the item is, who it is for, and why it is different, instead of echoing the title. Tags were generated to widen the queries the product could match. Where GMC rules were being broken, those got corrected too, so compliance and AI-readiness moved up together rather than one at the expense of the other. Because all of this lands in a supplemental feed that layers on top of the store’s export, the original feed stayed untouched and nothing broke on the next platform update.
One guardrail ran through the whole cleanup. Enriching a title is not license to invent facts. Brand names, model numbers, and product identifiers stayed locked exactly as the merchant entered them, so “Sony WH-1000XM5” never drifts into “Sony WH-1000XM5 Pro Max.” That protection cleared 98.2% of changes automatically and flagged only the 1.8% that genuinely needed a human to look, which is what keeps a cleanup at this scale from turning into a proofreading marathon.
From 28 to 92: What Actually Changed
That single shirt went from 28 to 92. Read in bands rather than decimals, it crossed from “AI will skip this” straight into “AI can confidently recommend this.” Across the catalog the pattern repeated: products clustered in the 25–40 danger zone moved into the 80s and 90s once their titles, attributes, and descriptions carried real signal.
The change is easiest to see side by side. Before, the shirt was “Blue Shirt Men” with color missing, material missing, no tags, and a UCP Score of 28. After, it was “Premium Sapphire Blue 100% Cotton Men’s Casual Dress Shirt — Breathable & Lightweight,” with color and material filled, seven tags attached, and a UCP Score of 92. Nothing about the actual product changed. Only what Google and AI could understand about it did.
That distinction matters. The cleanup did not make the shirt better. It made the shirt legible. A feed that scores 92 is not a feed of better products, it is a feed that finally describes the products it always had.
Why the Same Fix Paid Off Twice
The reason this kind of cleanup is worth doing is that one set of fixes serves two channels at once.
On Google, complete titles and filled attributes give Shopping and Performance Max better raw material to build ads from. PMax pulls headlines and matches queries out of your feed, so richer data means more relevant placements and a fairer shot at impression share, without touching a single bid. The same enrichment that lifted the UCP Score raises the feed’s Google performance ceiling as a byproduct.
On AI surfaces, the payoff is more direct. An assistant asked for “a lightweight cotton dress shirt in blue under $80” can only put that shirt on the shortlist if the feed actually states cotton, blue, lightweight, and the price. At a 28 the product was unmatchable and got passed over for a competitor whose data was complete. At a 92 it is a candidate. And because the enriched data can be emitted in eight languages, that candidacy holds across more than one market.
The cleanup didn’t make the product better. It made the product legible. A feed that scores 92 finally describes the products it always had.
That is the quiet lesson in a 28-to-92 story. There was no new inventory, no bigger budget, and no clever bid behind it. There was a feed carrying the answers all along and no structure to surface them. Clean up the structure and the same catalog competes in places it was invisible the week before.
Conclusion
A broken product feed is not a broken store. It is a legible one waiting to happen. The shirt that scored 28 was always a good product; it just told Google and AI almost nothing about itself. Rewriting the title, filling the attributes, deepening the description, and fixing the GMC issues, all layered through a supplemental feed so the original export stayed safe, took it to 92 and pulled the rest of the catalog up with it. The work is rarely glamorous and almost never involves the product itself. It involves the data the product ships with. UCP Radar scans your existing Merchant Center feed against more than 50 validation rules, scores every product for both Google and AI readiness, and generates the optimized supplemental feed automatically, so you can see your own 28s before a competitor’s 92 takes the sale that should have been yours.
Frequently Asked Questions
A broken product feed is one that technically works, products import and ads run, but carries too little structured data for Google and AI to understand the items well. Blank attributes, thin titles like 'Blue Shirt Men', and two-line descriptions are the usual signs. Most feeds score between 25 and 40 out of 100 on AI-readiness for exactly this reason, so a broken feed is closer to the norm than the exception.
Yes, and that's what makes it hard to notice. A product can comply with Google Merchant Center rules, keep serving ads, and still score low on AI-readiness because its data is too sparse for an assistant to match it to a shopper's question. Compliance gets you into the auction; depth gets you recommended. The two are separate, and a feed can pass one while failing the other.
By fixing the fields that carry the most signal, in order. Rewrite the title so the brand, color, material, and key feature are in it; fill the empty attributes; deepen the description so it says what the item is and who it's for; and correct any Merchant Center issues. Layer all of it through a supplemental feed so the original export stays intact. Those few changes move the score more than anything else combined.
It means enriching it, not inventing it. Brand names, model numbers, and product identifiers stay locked exactly as you entered them, so 'Sony WH-1000XM5' never drifts into something else. Brand Protector approves 98.2% of changes automatically and flags only the 1.8% that genuinely need a human to review, which keeps a large cleanup accurate.
No. Sort your products by UCP Score, overlay revenue, and start with the low-scoring products that make the most money. A handful of high-revenue items usually returns most of the gain, and you can expand from there once you see the movement.