Product Feed Management and Optimization: The Complete Guide for Google, Meta, and AI Channels
Product feed management in 2026: how we optimize one feed so it holds up in Google Shopping and Meta catalog ads, and now in ChatGPT and Google AI Mode too.
By Alberto Barberis, Founder and CEO, AndromedAI · Updated October 2026
Product feed optimization, defined
Product feed management keeps your product data synced to Google Merchant Center, Meta catalogs, ChatGPT, and other channels in each one's format. Product feed optimization improves that data: titles, descriptions, attributes, categories, identifiers, and custom labels. A complete, accurate feed makes each product eligible for more relevant searches and prompts. It lifts ad performance and gives AI shopping agents facts they can check.
Product feed optimization in 30 seconds
A product feed is the structured file that tells Google, Meta, marketplaces, and AI assistants what you sell. Optimizing it means making every row complete and accurate, in the words shoppers type, and keeping it that way.
- 01
Almost every product channel worth paying for in 2026 reads a feed: Google Shopping and Performance Max, free listings, Meta Advantage+ catalog ads, marketplaces, and now ChatGPT and Google AI Mode.
- 02
Product feed management is plumbing. One source of truth, reshaped into each channel's format and synced on a schedule.
- 03
Feed optimization is the content itself: titles built from what people search, attributes filled in, precise categories, and labels that steer bidding.
- 04
The same product data now decides ad relevance, free listing visibility, and whether an AI assistant recommends you, so a better feed pays three times.
- 05
Rules and supplemental feeds fix structure. They can't add a missing fabric weight or a use case, and those gaps are where most feeds lose.
What a product feed is, and why it matters more in 2026
A product feed (or product data feed) is a file or API stream with one row per product and one column per attribute: id, title, description, link, image_link, price, availability, brand, gtin and dozens more. Channels read it to decide which queries and which shoppers each product is eligible for.
of PPC professionals running Shopping campaigns name errors and missing product data as their biggest feed challenge
Feed quality is the top operational problemSource: Channable, State of PPC 2026more clicks on average for retailers who added correct GTINs to their product data
One attribute, measurable liftSource: Google Merchant Center Helpcharacters or fewer of a Google Shopping title are typically visible to shoppers, out of 150 allowed
The first words decide the clickSource: Google Merchant Center Helpaverage AI readability score of individual product pages, the lowest of any page type Adobe measured
Product content is the weakest link for LLMsSource: Adobe, April 2026higher conversion rate for AI-referred retail visitors than for non-AI traffic in July 2026
AI shoppers arrive ready to buySource: Adobe AI Traffic Trends, Aug 2026in US B2C retail revenue that AI agents could orchestrate by 2030; $3T to $5T globally
The channel the feed now serves is largeSource: McKinseyAnatomy of a feed
A feed is a table. Each row is an item, meaning a variant: the navy jacket in size M. Each column is an attribute the channel defines. Google publishes its schema in the Merchant Center product data specification, Meta in its catalog fields reference, and OpenAI in its ChatGPT product feed spec. The overlap is large, so one well-built catalog can serve all three.
Google says Shopping ads are ranked on a combination of advertiser bids and relevance. You choose the bid. The feed supplies the relevance.
| Attribute group | Typical fields | What the channel does with it |
|---|---|---|
| Identity | id, item_group_id, gtin, mpn, brand | Matches the item to the global product catalog and groups variants |
| Content | title, description, product_highlight, product_detail | Decides which queries and prompts the product is relevant for |
| Classification | google_product_category, product_type | Places the product in the right category and campaign structure |
| Variants | color, size, material, pattern, gender, age_group | Filters products on the constraints shoppers state |
| Commerce | price, sale_price, availability, shipping, return_policy | Checks the offer against the landing page and shows it to the shopper |
| Campaign control | custom_label_0 to custom_label_4, excluded_destination | Lets advertisers segment bidding and reporting |
When we audit a feed, one of the first things we check is whether every variant carries its own gtin plus a shared item_group_id. A parent GTIN copied onto twelve sizes looks harmless in the store admin and causes identifier problems on all twelve rows in Merchant Center. If you're unsure which products need one, start with how GTINs work.
Why the feed matters more now
For a decade the feed was a paid search asset. Now AI systems shop from it too. Adobe's research measured AI traffic to US retail sites up 693% year over year in the 2025 holiday season, and found that individual product pages are the least machine-readable part of retail websites. A structured feed hands AI systems the facts your pages bury.
Feeds were built to buy clicks. They now also decide whether an AI assistant can recommend your product at all.
McKinsey reaches the same place from the strategy side: merchants need to embed semantic and behavioral metadata into product catalogs so agents can read intent. That's the core of Agentic Commerce Optimization (ACO).
One catalog, many feeds: how product feed management works
Product feed management means taking product data from one source of truth (a store, PIM or ERP), reshaping it for each channel's specification, and syncing it on a schedule. Done well, you fix a fact once and every channel picks it up.
- 1
Pick the source of truth
One system holds the master record for each product: your PIM, your ERP or the store itself. If it's scattered across spreadsheets, read our guide to product information management.
- 2
Enrich the master data
Fill in the attributes first, then write titles and descriptions. Most feed performance is won or lost here.
- 3
Map to each channel
Your "colour" field becomes
colorfor Google, your collection becomesproduct_type, your SKU becomesid, and the size chart region (UK, EU, US) becomessize_system. - 4
Transform with rules
Apply logic per channel: title order for Google, a 65-character title for Meta, labels for bidding, exclusions for out-of-stock or low-margin items.
- 5
Sync on a schedule
Push by file, scheduled fetch or API. Fast-moving catalogs refresh price and availability several times a day. Google expires items not updated in 30 days, so a broken fetch quietly empties a channel.
- 6
Monitor and fix
Read each channel's diagnostics and fix the cause in the source.
Channel requirements at a glance
The core is shared. The limits differ.
| Requirement | Google Merchant Center | Meta catalog | ChatGPT (OpenAI feed) |
|---|---|---|---|
| Title limit | 150 characters, about 70 visible | 200 characters, 65 recommended | 150 characters |
| Description limit | 5,000 characters | 9,999 characters | 5,000 characters |
| Identifier | gtin or mpn plus brand where they exist | id, brand | item_id, gtin or mpn on the Google-compatible path |
| Category | google_product_category, product_type | google_product_category, fb_product_category, product_type | Product category fields in the spec |
| Custom labels | custom_label_0 to custom_label_4 | custom_label_0 to custom_label_4 | Not used |
| Formats | File, scheduled fetch, Google Sheets, Merchant API | File, scheduled feed, API | JSONL, CSV or TSV; Google-compatible TSV or CSV if confirmed |
Sources: Google title spec, Google product data specification, Meta catalog fields, OpenAI feed reference.
Fix at the source, transform at the edge
Here we part ways with a lot of feed advice, which says to optimize inside the feed tool because nobody has to touch the store. The trouble shows up a month later. Titles get rewritten for Google while the product detail page (PDP) still says "Jacket 4471 Blue", which is what Meta and AI crawlers keep seeing. Google itself asks for feed titles and descriptions that match your landing pages.
The pattern we recommend is dull. It also works. Enrich content in the source (store or PIM) and keep per-channel formatting in the feed layer. Labels and exclusions belong there too. Merchant Center's automatic item updates can even correct price and availability from your page's structured data, but only if the page is right.
Google Shopping title optimization: formulas by category
The title is the most important field in a Google Shopping feed. Lead with the words shoppers search for (brand when it matters, then product type and the defining attributes) and keep those words inside the first 70 characters.
Google's guidance fits in a paragraph. Use up to 150 characters, put the most important details first, include variant details such as size and color, and leave out prices, promotional text and all caps. The craft is choosing which attributes matter per category.
We'd push back on how that first rule gets read. Google allows 150 characters. It doesn't require them. Padding a title with "premium" or "stylish" adds nothing a shopper filters on, and it sits past the visible cut anyway. Spend the characters on material, fit, capacity or compatible model. A 90-character title is fine.
Title formulas by category
| Category | Formula | Example |
|---|---|---|
| Fashion | Brand + gender + product type + material + fit or style + color + size | Northvale Women's Merino Wool Crew Neck Sweater, Relaxed Fit, Oatmeal, M |
| Beauty | Brand + product line + product type + key ingredient or benefit + skin or hair type + size | Lumea Hydra Serum, Hyaluronic Acid Face Serum for Dry Skin, 30 ml |
| Home and furniture | Brand + product type + material + style + dimensions + color | Casaro Solid Oak Dining Table, Scandinavian Style, 180 x 90 cm, Natural |
| Food and drink | Brand + product + variety or origin + format + weight or pack size | Valle Rossa Extra Virgin Olive Oil, Organic Coratina, Tin, 3 L |
| Electronics | Brand + product line + model + key spec + capacity + color | Voltra X5 Wireless Noise Cancelling Headphones, 40h Battery, Black |
| Auto and spare parts | Brand + part type + compatible model + part number | Ferrox Front Brake Pads for VW Golf VII 2013-2020, FX-2241 |
Before and after
| Before | After | What changed |
|---|---|---|
| Sweater Beige | Northvale Women's Merino Wool Crew Neck Sweater, Relaxed Fit, Oatmeal | Added gender, material, style, and fit; color named the way the PDP names it |
| Serum 30ml | Lumea Hydra Serum, Hyaluronic Acid Face Serum for Dry Skin, 30 ml | Product type and ingredient added, plus skin type, in the words shoppers use |
| OAK TABLE * FREE SHIPPING * | Casaro Solid Oak Dining Table, Seats 6, 180 x 90 cm | Promo text and caps gone; seating capacity and size added |
Rules that hold across categories
- Match search language. If shoppers search "crew neck" and your title says "round collar", you're relying on Google to guess.
- Front-load. Product type and the most decisive attribute go before the 70-character cut.
- Brand position depends on demand. The common advice is brand first, always. Lead with it only when people actually type the brand name; otherwise the product type carries the query.
- Test one product group at a time. Google recommends title experiments measured against your key metrics. Change one variable per test.
For the paid side of title testing, including CTR and Quality Score effects, see our guide to catalog optimization for paid ads.
Attribute enrichment: the fields that decide matching
Attribute enrichment means filling every attribute a channel can use with accurate, specific values. Channels filter on attributes before they rank anything, so an empty material or size field drops a product from every query that depends on it.
A shopper searches "women's waterproof hiking boots size 8", or asks an AI assistant. The system needs gender, a product type, a size value and a waterproof claim it can verify. If one lives only in a photo, the product is filtered out before ranking starts. Channable notes that algorithms rank products partly on how completely their attributes are filled in.
The attributes worth completing first
Identifiers
gtin, mpn and brand. Google says correct GTINs raised clicks 20% on average. Never put "N/A" or "Generic" in the brand field.
Classification
A full product_type path such as Home > Women > Dresses > Maxi Dresses; only the first product_type value is used for bidding. If you send google_product_category, go at least 2 to 3 levels deep.
Variant attributes
color, size, material, pattern, gender, age_group. Required for apparel in many countries. Several colors go in one value, slash-separated: Black/White.
Highlights
product_highlight: 2 to 100 short benefit bullets, 4 to 6 recommended, up to 150 characters each. Product facts only, no slogans.
Product details
product_detail: up to 100 entries, each pairing an attribute name with a value under a section heading. Technical, verifiable specs such as "Fabric weight: 280 gsm".
Commerce facts
shipping, return_policy, sale_price, availability. Mismatches with the landing page cause disapprovals. EU and UK prices must include VAT.
A contrarian note. Teams spend hours mapping products to Google's product taxonomy, chasing the deepest google_product_category node, yet Google assigns a category itself when you leave it out. We'd put those hours into product_type, which you control.
How to enrich at scale
- Extract what you already have. Specs often sit in description text, PDF spec sheets or supplier files. Parse them into structured fields first.
- Normalize values. "Navy", "navy blue" and "NVY" should become one color name, the one the PDP uses, as Google recommends. A UK 10 dress listed in your Italian store as size 10 is a return waiting to happen, so set
size_systemper market. - Fill gaps from trusted sources. Manufacturer spec sheets cover missing material, dimensions or compatibility. Submit confirmed values only; Google asks for confirmed values in
product_detail. - Write the descriptive fields last. Titles, descriptions and highlights come after the attributes are complete, so they all draw on the same facts.
A typical row, before and after:
title
BeforeTrailmoor Hiker Boot Brown
AfterTrailmoor Ridge Women's Waterproof Leather Hiking Boots, Wide Fit, Lug Sole, Chestnut Brown, UK 5
product_type
BeforeShoes
AfterWomen > Shoes > Boots > Hiking Boots
color
Beforebrwn
AfterChestnut Brown
material
Before(empty)
AfterFull-grain leather; waterproof membrane
size
Before5
After5 (size_system: UK)
product_highlight
Before(empty)
AfterWaterproof membrane keeps feet dry in wet grass; Wide-fit last for broader feet; Deep lug sole for muddy trails; 540 g per boot
Nothing there was invented. The leather and the membrane were in the supplier sheet all along.
Enrichment for AI: use cases and intents
Ad algorithms match keywords. AI assistants match intent: "a gift for a runner", "a serum that won't irritate sensitive skin". Put who it's for, when to use it and the problem it solves into the description and highlights, and into the newer conversational attributes covered below.
Custom labels in Google Shopping: 8 ways to use them
Custom labels (custom_label_0 to custom_label_4) are five free fields you define to group products for bidding and reporting in Shopping, Performance Max and Demand Gen campaigns. They turn data Google can't see, like margin, into campaign structure.
Google's limits are short: one value per label per product, up to 100 characters, and up to 1,000 unique values per label across the account. Values past the cap are ignored for bidding and reporting. Meta's catalog also supports custom_label_0 to custom_label_4 for filtering the product sets behind dynamic product ads.
Most accounts we look at don't need more labels. They need fewer, kept current. A stale label keeps splitting budget on old data.
Eight labels that pay off
| # | Label | Example values | How to use it |
|---|---|---|---|
| 1 | Margin band | high_margin, mid_margin, low_margin | Set higher ROAS targets on low-margin products and push volume on high-margin ones |
| 2 | Performance tier | bestseller, steady, zero_sales | Give bestsellers their own budget; test new titles on products with impressions but no clicks |
| 3 | Seasonality | winter, summer, all_year | Raise budgets before the season and cut them after, without restructuring campaigns |
| 4 | Price band | 0-25, 25-50, 50-100, 100+ | Separate cheap impulse items from considered purchases with different targets |
| 5 | Sale status | on_sale, full_price | Spend more while a discount runs; a rule can set it whenever sale_price is present |
| 6 | New arrivals | launch_2026_q4 | Keep new products from fighting proven bestsellers for budget |
| 7 | Stock depth | deep_stock, low_stock | Pull spend from items about to sell out |
| 8 | Data readiness | ready, needs_work | Separate products with complete titles and attributes from thin ones; send budget where data quality supports conversion |
How to set them
You can populate labels in the source (a Shopify metafield or PIM attribute), in a feed tool, or with attribute rules. A typical rule reads "if sale_price exists, set custom_label_4 to on_sale". Google suggests using rules to assign labels automatically from data you already submit. Hand-typed labels go stale within weeks.
A common Shopify trap: a metafield filled in the admin doesn't always reach Merchant Center through the native channel app. Check the label values in Merchant Center itself before you build campaigns on them.
The readiness label is the one most teams skip. If you score each product for completeness (AndromedAI's AI Readiness Score is one way), you can bid differently on products whose data is ready and fix the rest before spending on them.
Supplemental feeds and feed rules: fix your feed without touching your store
Feed rules (now called attribute rules in Merchant Center) transform values in bulk using conditions and operations. Supplemental feeds add or override attributes for products already in a primary feed, matched by id. Neither can create products or invent facts.
When to use which
| Situation | Best tool | Why |
|---|---|---|
| Remove promo text or caps from all titles | Attribute rule | One find-and-replace covers the whole feed |
| Append color and size to variant titles | Attribute rule | "Set to" combines existing fields |
| Add custom labels from a margin spreadsheet | Supplemental feed | The data is not in the store; a Google Sheet keyed by id adds it |
| Replace titles and descriptions with optimized versions | Supplemental feed | Overrides content per product without editing the platform |
Add product_highlight, product_detail or Q&A your platform cannot export | Supplemental feed | Fills fields the store connector does not support |
| Fix wrong material or missing specs | The source | Rules cannot know facts that are not in the data |
A warning from experience: supplemental feeds are habit-forming. Teams stack them until nobody knows which Google Sheet owns which title. We treat every supplemental feed as a test bed or a bridge, with an end date.
How attribute rules work
In Merchant Center, go to Data sources, open a product source and select the Attribute rules tab. Rules need the Advanced data source management add-on. You add operations (Set to, Find and replace, Prepend, Append, Split, Clear), then Save as draft, Test rules and Apply changes. Rules run in cascading order, and changes apply once the data source is reprocessed. By default each attribute takes its value from either the supplemental or the primary source.
Always preview. A find-and-replace on "Red" also catches "Redwood" unless the rule matches whole words.
Practical rules, documented by Search Engine Land:
- "If title contains black, set
colorto black" to fill missing color values. - Build
product_typefrom URL breadcrumbs with Split on "/". - Tag every item that has a
sale_pricewith a sale label. - Keep one rule per attribute and use the preview to see how steps build on each other.
How AI-generated content flows through a supplemental feed
- 1
Export IDs and current content
Pull
id,title,descriptionand existing attributes for the products you want to improve. - 2
Generate and check
Write optimized content against your brand rules, then review it or auto-approve by quality score.
- 3
Load as a supplemental source
A Google Sheet or file keyed by
id, with columns such asstructured_title,structured_descriptionandproduct_highlight. Use the structured attributes for AI-written text. - 4
Link to the primary source
In Merchant Center, attach the supplemental source to the primary feeds it should update.
- 5
Measure and sync back
Compare clicks and impressions by product group, then push the winning content to the store so the PDP matches the feed.
Don't skip the last step. If the product page keeps the old copy, search engines and AI crawlers keep reading it. For the full attribute reference, see our Google Merchant Center guide.
AI channel feeds: ChatGPT, Google AI Mode and agentic storefronts
AI assistants now ingest product feeds directly. OpenAI publishes a ChatGPT product feed specification, Google's AI Mode reads Merchant Center data, including new conversational attributes, and Shopify syndicates catalogs to ChatGPT, Perplexity, and Copilot.
ChatGPT
OpenAI's product feed spec accepts JSONL, CSV or TSV, plus a Google-compatible TSV or CSV path when OpenAI confirms it for your feed. Required fields are item_id, title, description, url, brand, seller_name, image_url, availability and price. Titles can run to 150 characters and descriptions to 5,000.
Variants use group_id and variant_dict; reviews use review_count and star_rating. The is_eligible_search flag controls ChatGPT search visibility, and is_eligible_checkout opts in to checkout where supported. It all sits on the Agentic Commerce Protocol, which OpenAI describes as the layer that lets ChatGPT ingest structured catalog data and surface relevant products in context.
From the shopper's side, the assistant can only cite what the feed states.
Every reason in that answer maps to a field. Delete the wide-fit detail and the boot drops out.
Google AI Mode and Gemini
In January 2026 Google announced the Universal Commerce Protocol, built with partners including Shopify, Walmart, Wayfair, Target, and Etsy, and powered by Merchant Center product feeds. Products opt in to agent checkout with native_commerce. At Google Marketing Live 2026 Google added conversational attributes to Merchant Center, rolling out globally. The specification now includes these conversational fields:
| Attribute | What it holds | Limits |
|---|---|---|
question_and_answer | Questions shoppers ask and your answers | Up to 30 pairs, 1,000 characters per question or answer |
product_detail | Verified technical specs by section | Up to 100 entries |
product_highlight | Short product benefits | 2 to 100, 4 to 6 recommended |
related_product | Accessories, substitutes, sets, required parts | Up to 30 relationships, by gtin or id |
document_link | PDF manuals or spec sheets you own | Up to 5 URLs |
popularity_rank | Your own popularity ranking | 0 to 100 |
Source: Google Merchant Center product data specification. For how these fields affect visibility, see Google AI Mode shopping.
Don't fill all 30 question_and_answer pairs with filler ("Is this boot stylish?"). We'd rather see eight real questions from support tickets, answered specifically.
Shopify and agentic storefronts
Shopify's agentic storefronts, launched in its Winter 2026 Edition, let merchants sell through ChatGPT, Perplexity, and Microsoft Copilot. Shopify structures the product data and lets agents draw on your policies and FAQs. Your Shopify fields and metafields are now an AI feed, feed tool or not.
What changes for feed teams
- Write for questions as well as keywords. Q&A pairs and use cases give AI systems something to quote when they justify a pick. So do highlights.
- Keep every surface consistent. Price and stock should match everywhere: in ChatGPT, in Google, on your PDP. Specs too.
- More destinations, one source. Each protocol (ACP, UCP, AP2) has its own schema. Enriching once at the source keeps them aligned.
Feed QA and the best product feed management tools
Feed QA is the routine of checking that every product is approved and its data is accurate and complete, then measuring whether your changes moved performance. Feed software automates the syncing; the content still has to be right at the source.
The disapprovals that cost the most
Disapprovals stop a product showing; warnings let it show but can lead to suspension. These are the most common product data quality issues in Google's own guidance:
| Issue | Typical cause | Fix |
|---|---|---|
| Invalid or mismatched GTIN | Wrong length, or the GTIN belongs to another brand | Use the manufacturer's GTIN; mark custom-made items as such |
| Missing brand | Brand field empty or set to "N/A" | Use the brand, or your store name for products you make |
| Excessive capitalization | "SALE RUNNING SHOES FREE DELIVERY" | Rewrite in sentence or title case without promotional text |
| Promotional overlays on images | Logos, watermarks, "free shipping" text | Use clean product images |
Invalid google_product_category | Only the last segment submitted | Use the numeric ID or the full path |
| Missing apparel attributes | No gender, size, color or age_group | Map them from variant options or metafields |
| Price or availability mismatch | Feed updated less often than the site | Sync more often or add structured data on the PDP |
After a warning you get 28 days before suspension; reviews take 3 to 5 business days.
Our order of work rarely changes. Disapprovals on products with impressions history first, missing identifiers second, the rest after. One disapproved bestseller outweighs a hundred warnings on products nobody searches for.
The QA loop
Diagnose
What is disapproved, limited or incomplete?
Merchant Center diagnostics, Meta catalog issues, attribute fill rate per field
Prioritize
Which products matter most?
Revenue and margin by product group; impressions and search demand
Fix at the source
What has to change in the data?
Titles, attributes, categories, and descriptions in the store or PIM; rules only for formatting
Publish
Is the fix live on every channel?
Feed refresh, supplemental source, platform sync
Measure
Did it work?
Clicks, CTR, impressions, conversions by product group (before vs after)
Run it monthly, and after every catalog import or migration.
A pre-launch checklist for any feed
- Unique, stable IDs
IDs never change between updates, so history is preserved
- Valid identifiers
gtin,mpnandbrandpresent wherever they exist - Specific titles
Product type and key attributes inside the first 70 characters
- Full category paths
google_product_category2 to 3 levels deep, fullproduct_type - Variant attributes
color,size,material,gender,age_groupon every variant row - Accurate offers
Price and availability match the landing page, sale price included
- Clean images
High resolution, no overlays, correct variant shown
- Labels in place
Custom labels populated automatically, not by hand
- Conversational fields
Highlights and product details for priority products, plus Q&A
- Landing page parity
PDP title and specs match the feed, color names included
About one third of Shopping campaign managers don't use a dedicated feed management tool, according to the State of PPC 2026 report cited by Channable. For a small catalog on one platform, native connectors can be enough.
Best product feed management tools in 2026
Which of the product feed management tools for Google and Meta ads fits you depends on how big the catalog is, how many channels you run and who on the team can maintain rules. Feed tools handle mapping and syndication. An AI content layer handles what they pass along. Most mid-size brands need both.
| Tool | Model | Known for |
|---|---|---|
| Google Merchant Center (native) | Free, self-serve | Attribute rules and supplemental sources directly in Google |
| Shopify Google and Meta channels | Free apps, self-serve | Simple syncing for Shopify stores, agentic storefronts for AI channels |
| Channable | Self-serve platform | Feed management and marketplace listings, plus automated PPC campaigns, from one data set |
| DataFeedWatch | Self-serve platform | Rule-based feed optimization across a large channel list |
| Feedonomics | Full-service, managed | Dedicated feed managers; the company cites 2,000+ destinations |
| Productsup | Enterprise platform | Data flows for large, multi-country catalogs |
| Producthero | CSS and PPC tools | Google CSS partner, performance labels (Labelizer), AI title and feed optimization |
| GoDataFeed | Managed or self-serve | Feed management with service options for mid-market merchants |
Descriptions reflect each vendor's own positioning (for example Feedonomics and Producthero); check current features and pricing directly.
How to choose
Small catalog, one platform
Native connectors plus Merchant Center attribute rules. Fix titles and attributes in the store itself.
Multi-channel, in-house team
A self-serve feed platform pays off once you run several channels and countries.
Large catalog, little feed expertise
A managed service puts specialists on mapping and disapprovals.
Thin or inconsistent content
No feed tool writes facts that aren't in your data. Add an AI content layer at the source and let the feed tool syndicate it.
Where AI content fits
Feed tools increasingly add AI title rewriting. Ask where that text will live. Content generated inside the feed exists only in that channel. Content generated at the source updates the PDP and the PIM in one pass, and every feed downstream picks it up. AndromedAI is that source-level layer and publishes into the tools you already use; see integrations.
Product feed optimization with AndromedAI
AndromedAI improves the content every feed carries. It scores product data, rewrites or creates titles and descriptions using keyword and intent data, extracts attributes, and publishes the result to your store, your PIM, and Google Merchant Center.
How the platform maps to the work
| Feed task | AndromedAI | What it does |
|---|---|---|
| Audit feed and page quality | AI Readiness Audit | Scores products on Product Data Completeness, Keyword Coverage, Customer Intent Match, and Shopping Metadata, and shows which to fix first |
| Enrich attributes and rewrite titles | Optimizer | Rewrites titles, descriptions, bullets, and FAQ in the terms shoppers use; extracts attributes like material, color, and fit; adds use cases and intents |
| Create missing products | Creator | Builds complete product pages from brand or supplier data, including PDF spec sheets, in 12 languages |
| Cover category demand | Category page optimizer | Builds category pages around real demand, useful as landing pages for category-level campaigns |
| Import and publish | Integrations | Imports from CSV, Excel, Google Sheets, Shopify, Akeneo, SAP or other ERPs, PDF spec sheets, XML or JSON feeds, REST API. Publishes to Shopify, Google Merchant Center, Salesforce Commerce Cloud, Adobe Commerce, Shopware, Akeneo, Plytix, WooCommerce |
Guardrails for content at feed scale
The Brand Kit holds tone of voice, rules, examples, a glossary, and banned words. AI checks and approval workflows decide what goes live, with auto-approval above an AI Checker score of 4.0. We wouldn't publish feed titles any other way. A "waterproof" boot that isn't becomes a returns problem fast.
AndromedAI also generates Merchant Center conversational attributes, so the same run that fixes titles fills the fields Google built for AI Mode. More than 500 catalogs have been optimized on the platform.
Results
ROAS, with CPC down 6% and Quality Score 10/10
Instalclicks from AI chats
Bomboogieto first sales from ChatGPT, with catalog generation costs down 95%
Matassasales and +160% organic traffic, 483 hours saved
Semprefarmaciahours saved monthly in catalog management
Global MarkFAQ
It's the work of improving the data in a product feed so channels such as Google Shopping, Meta, and AI assistants show your products for more relevant queries. It covers titles, attributes, categories, identifiers, and custom labels. The payoff is more relevant impressions, stronger ad performance, and accurate answers from AI shopping agents.
Product feed management means taking product data from a store, PIM or ERP and mapping it to each channel's specification. Channels include Google Merchant Center, Meta and ChatGPT. Rules transform the data and a schedule keeps every channel in sync. Optimization is the separate job of improving the content itself.
Fix disapprovals first. Then complete identifiers and variant attributes, use full category paths, and rewrite titles with product type and key attributes up front. Add highlights and product details, then Q&A for priority products. Set custom labels for bidding and keep the feed in sync with your product pages.
Put product type and the most important attribute in the first 70 characters of the title. Add correct GTINs, one per variant. Send a google_product_category at least 2 to 3 levels deep, name colors the way your landing page does, and drop promotional text. Test titles on one product group at a time.
Common options are Google Merchant Center attribute rules, Shopify's native channels, Channable, DataFeedWatch, Feedonomics, Productsup, Producthero, and GoDataFeed. The right choice depends on catalog size and channel count, and on the skills you have in house. Feed tools handle mapping and syndication, so thin product content still has to be fixed at the source.
A feed rule, now called an attribute rule in Merchant Center, transforms existing values in bulk with conditions. A supplemental feed adds or overrides attributes for products that already exist in a primary feed, matched by ID. Neither can add new products.
Yes. OpenAI accepts product feeds for ChatGPT under a published specification, and Google's AI Mode reads Merchant Center data, including the new conversational attributes like question and answer, product detail, and related product. Complete, consistent feed data gives these assistants the facts they quote when they recommend a product.
Yes, with controls. Google requires AI-generated titles and descriptions to be submitted in the structured_title and structured_description attributes with the trained_algorithmic_media source type. Use brand rules and a review step or quality threshold before anything goes live.
The usual causes are invalid GTINs, missing brand, excessive capitalization, promotional image overlays, invalid product categories, missing apparel attributes, and price or availability mismatches with the landing page. Fix the source data, then request a review. A fix made only in the feed won't hold if the store keeps exporting the wrong value.
Glossary
- Product feed
- A structured file or data stream with one row per product and one column per attribute, sent to a sales or advertising channel
- Primary feed
- The main data source in Merchant Center that creates products
- Supplemental feed
- A secondary data source that adds or overrides attributes for products already in a primary feed, matched by ID
- Attribute rules
- Merchant Center rules, formerly called feed rules, that transform attribute values in bulk
- Custom labels
- Five advertiser-defined fields, custom_label_0 to custom_label_4, used to group products for bidding and reporting
- GTIN
- Global Trade Item Number, the barcode identifier that matches a product to the global catalog
- product_type
- Your own category path for a product, used for campaign structure and relevance
- google_product_category
- The category from Google's product taxonomy, submitted as an ID or full path
- Conversational attributes
- Merchant Center fields built for AI experiences, such as question and answer, product detail, and related product
- structured_title
- The Merchant Center attribute for titles written with generative AI, with a digital source type
- Feed management software
- Tools that map and transform product data, then syndicate it to many channels
- Agentic storefront
- Shopify's feature that syndicates a store's catalog to AI assistants such as ChatGPT, Perplexity, and Copilot
Keep reading
Every attribute Google reads, and how to fix diagnostics
GuideBest Product Feed Management Tools for Google and Meta Ads (2026)How the main feed platforms compare, and which fits your catalog
GuideGTINs Explained: When You Need Them and What to Do WithoutFix identifier issues before they cost you clicks
GuideGoogle Product Category and Taxonomy: How to Map Your CatalogMap every product to the right category path
Sources (23)
- Google Merchant Center Help: Product data specification
- Google Merchant Center Help: Title and structured title
- Google Merchant Center Help: Tips to optimize your product data
- Google Merchant Center Help: Custom label 0 to 4
- Google Merchant Center Help: Product type
- Google Merchant Center Help: Product highlight
- Google Merchant Center Help: Attribute rules
- Google Merchant Center Help: Fixing disapprovals for product data quality
- Google Shopping Help: How Shopping ads and listings are ranked
- Google for Developers: Use Merchant Center feed rules with supplemental feeds
- OpenAI: Product feed reference
- OpenAI: Agentic Commerce overview
- Meta for Developers: Catalog fields
- Adobe: AI traffic surges, but retail sites are not machine readable
- Adobe: AI Traffic Trends report, August 2026
- McKinsey: The agentic commerce opportunity
- Channable: The state of eCommerce feed management in 2026
- Search Engine Land: Google launches AI performance insights and conversational attributes
- Search Engine Land: How to set up feed rules in Google Merchant Center
- ChannelEngine: Google's Universal Commerce Protocol and Merchant Center
- EMARKETER: Shopify rolls out agentic storefront tool
- Feedonomics
- Producthero
Parlano di noi








