Google Shopping feed optimization starts with fixing what prevents a product from showing, then improving what helps Google understand the product, and only then adjusting bids.
If a shoe is disapproved because the price is wrong, rewriting the title will not save it. If the feed calls it a “classic” while the product page calls it a black leather high-top, raising the budget just buys a faster lesson.
The useful order is: eligibility, accuracy, identity, merchandising, then economics. Here is how to work through it without spending Friday afternoon editing 4,000 rows at random.
1. Export the issues before you touch the feed
Open Merchant Center’s Needs attention area and download the affected products. Google separates account-level issues from product-level issues, and its Merchant Center issue guidance explains how to filter by impact and export the affected items.
Keep three buckets:
- Cannot serve: disapproved products, broken destinations, policy problems, or missing required data.
- Can serve with limitations: warnings and missing recommended attributes that may narrow eligibility or understanding.
- Eligible but underperforming: approved products that still need better matching, merchandising, or economics.
Do not mix those buckets. A disapproval is a repair job. A weak title is an improvement job. A product with no margin is a business decision.
2. Make the feed and product page tell the same truth
Price, availability, condition, variant, and destination need to agree with the landing page. Check the source that actually controls each field. On Shopify, that may be the product record, an app, a supplemental source, an automated rule, or a manual edit left behind months ago.
Google recommends keeping product data current and matching the title, description, variant, price, and availability shown on the destination. Its high-quality product data guidance emphasizes accurate, complete, current, and verifiable information.
When the same issue hits hundreds of products, look upstream before fixing rows one by one. The right change may be in the store catalog, feed app, shipping settings, or a transformation rule.
3. Fix product identity before writing prettier titles
Google needs to know what the item is. Submit required attributes and applicable identifiers, using the correct format for the product and market.
For many new branded products, that means a brand and a valid GTIN assigned by the manufacturer. Do not invent a GTIN, copy one from a similar product, or set “identifier exists” to false just to clear an error. For products without a manufacturer-assigned GTIN, follow the applicable identifier rules instead of manufacturing certainty.
Google’s product data specification is the source of truth for required and conditional attributes. Use it product type by product type; apparel, custom goods, bundles, subscriptions, and regulated categories do not all follow the same checklist.
4. Write titles for recognition, not keyword confetti
A strong product title helps a shopper and Google recognize the item quickly. Put the useful distinguishing details early, especially details that are hard to see in the image.
For a shoe, a practical title pattern might be:
Brand + product line + product type + material or defining feature + color + size
That is a pattern, not a command to cram every attribute into every title. “Black Women’s Leather High-Top Sneaker, Size 8” is useful. “Best Cheap Trendy Amazing Black Shoes Sale” is not.
Google’s current product data optimization guidance recommends putting key details at the front because titles are truncated in many formats. It also advises using titles and descriptions that match the landing page.
Do the same with descriptions. Explain the product. Include materials, use, fit, dimensions, compatibility, and what is included when those details matter. Skip boilerplate that could describe anything in the catalog.
5. Treat variants like separate purchasable items
If a shopper clicks a blue size-medium shirt, the landing page should show that blue size-medium shirt or make the selected variant unmistakable. Keep color and size names consistent between the feed and page.
Use stable product IDs. Group true variants appropriately, but do not group unrelated products merely because they share a collection. When IDs change unnecessarily, reporting and product history become harder to reconcile.
This is where a clean catalog matters more than a clever campaign setting. If every variant points to the same generic page and asks the shopper to start over, paid traffic inherits that friction.
6. Use images that show the product, not the promotion
The primary image should make the item easy to identify. Use adequate resolution, a clean view, and a URL Google can crawl. Promotional text, watermarks, placeholder art, and a product that occupies a tiny corner of the frame can create problems or weaken the listing.
Google’s image-status guidance explains where to check crawling, review, and compliance problems. If you replace an image, use a new image URL so the crawler can recognize the update cleanly.
Additional images can do a different job: show scale, texture, another angle, packaging, or the product in use. The hero image should identify; the rest can answer questions.
A feed triage sheet your team can actually use
Export the issue report, then add these columns. One row can represent one issue and product group rather than one person rewriting the same note 600 times.
| Field | What to record |
|---|---|
| Issue | The exact Merchant Center issue or performance concern |
| Affected products | Count, product type, brand, and representative item IDs |
| Serving impact | Disapproved, limited, eligible, or unknown |
| Business impact | Revenue or priority tier, margin range, inventory, and seasonality |
| Source of truth | Store catalog, feed app, supplemental source, account setting, or landing page |
| Owner | The person who can change the actual source |
| Fix | The exact field, rule, page, or setting to change |
| Verification | Resubmission date, crawl status, approval status, and sample items checked |
| Performance follow-up | Product-level impressions, clicks, cost, orders, contribution, and review date |
Sort first by serving impact, then by business value. A disapproved bestseller generally deserves attention before an approved product that sold twice last year.
A hypothetical catalog example
Suppose a store has 1,200 products:
- 80 are disapproved because prices do not match the landing page.
- 140 carry an identifier warning.
- 300 use generic titles such as “Classic Tee.”
- The remaining products are eligible, but reporting does not separate high-margin items from low-margin items.
Do not begin by rewriting 300 titles.
First, trace the price mismatch to its source and verify a representative set after the update. Next, determine which identifier warnings reflect genuinely missing valid identifiers and which require a different product-data treatment. Then improve title patterns by product type. Finally, add a stable business label or reporting structure that lets the media team distinguish product economics.
The exact field setup will depend on the catalog and integration. The point is the order: restore valid eligibility, improve product understanding, then decide where paid growth makes financial sense.
Feed quality and bidding solve different problems
A cleaner feed can help Google understand and match products. It does not turn an unprofitable product into a good advertising candidate.
Review product-level spend, orders, returns, gross margin, promotions, and stock. Our guide to choosing which products deserve ad spend covers that commercial decision. Use the break-even ROAS worksheet when a platform return looks healthy but the business result is unclear.
Custom labels can help organize campaigns and reports around useful groups such as margin tier, season, bestseller status, or inventory priority. They do not improve relevance merely because they exist. Use them to make better decisions, not to decorate the feed.
What should you check every week?
- New account-level and product-level issues.
- Sudden changes in approved, limited, and disapproved product counts.
- Price and availability mismatches.
- Broken or redirected product URLs and inaccessible images.
- Top-spend products with weak commercial results.
- Important products with little or no delivery.
- Feed rules or app changes that affected many items at once.
Keep a dated change log. Merchant Center needs time to fetch and review updates, and performance needs enough time to separate a real improvement from normal variation.
Start with the products that matter
If you have half an hour, do this: export Needs attention, filter to disapproved items, add product revenue and margin tiers, and choose one repeated issue with a clear owner. Fix it at the source. Verify a handful of items before rolling the change across the catalog.
That is less glamorous than raising bids. It is also how you avoid paying to promote the wrong product information.
BPM’s paid search team connects Merchant Center work with product economics, campaign structure, and what is actually happening on the store. Bring the issue export and a product-level margin view to the conversation. We can get specific quickly.
