Text version of this lessonExpand
Many teams treat Merchant Center like a place to upload products for ads. For ecommerce, it is closer to Google’s product-understanding layer. Titles, images, price, stock, attributes, policy pages, and landing-page consistency shape whether Google can show your products and whether it shows them to the right people. This lesson gives you a product feed launch checklist and a Merchant Center issue triage simulator: make priority SKUs understandable, sellable, and trustworthy before Shopping / PMax decisions.
Lesson output: product feed launch checklist
Product upload success does not prove that Google understands the product. Before launch, sample priority SKUs and review fields, pages, checkout, policies, and Merchant Center diagnostics in one checklist.
| Layer | Check first | Healthy sign | Do not do yet |
|---|---|---|---|
| Title | Does title explain product type, brand, spec, use case, and key attributes? | Both shopper and system can understand the product quickly. | Do not use only internal SKU names, slogans, or new arrival language. |
| Image | Does image_link clearly show the actual sold variant? | Ad card and product-page hero are consistent. | Do not force Shopping with a lifestyle image that hides the item. |
| Price and availability | Do feed, product page, and checkout agree on price / availability? | Promotion, out-of-stock, preorder, and restock states sync reliably. | Do not keep advertising SKUs with wrong price or stock state. |
| Product identity | Do brand, GTIN, MPN, SKU, variant, and product_type match the real product? | Standard products use real GTINs; private or custom items do not invent barcodes. | Do not use SKU as GTIN or guess a barcode. |
| Link and policy | Do product link, shipping, returns, contact info, and policy status support each other? | The shopper lands on a buyable, trustworthy page. | Do not ask ad budget to solve page-trust problems. |
Plain terms: Merchant Center, feed, GTIN, and diagnostics
Merchant Center: Google’s platform for receiving, reviewing, and managing product data. You see products, diagnostics, data sources, shipping/tax, returns, and website verification there.
Product feed: the set of product fields submitted to Google through Shopify sync, sheets, files, APIs, or supplemental sources. Common fields include title, image_link, price, availability, brand, GTIN, product_type, and link.
GTIN: a Global Trade Item Number, the barcode identity on a product package. Common forms include UPC, EAN, JAN, or ISBN. SKU is store-owned and is not GTIN. Use the real manufacturer barcode when it exists; do not invent one for private or custom products.
Diagnostics / issue details: the Merchant Center surface for product disapprovals, warnings, and data issues. It is not generic technical noise. It tells you whether the product can show, whether matching quality is weak, or whether account risk exists.
Filled fields do not prove consistent facts
Product data is not just a machine file. The buyer-facing price, availability, image, and promise must match the feed. Otherwise Shopping / PMax learns from unstable product facts.
| Fact | Compare | Risk | Proof |
|---|---|---|---|
| Price fact | Feed price, product-page price, checkout price, sale-price effective period. | Price mismatch hurts trust, review stability, and conversion quality. | Screenshot product and checkout pages, then record feed update time. |
| Availability fact | Feed availability, Shopify inventory, product-page button, preorder/out-of-stock copy. | Sending budget to out-of-stock items wastes demand. | Sample priority SKUs and record out-of-stock, preorder, and restock dates. |
| Product identity fact | SKU, GTIN, brand, variant, product_type, and product title. | Identity confusion makes the system place products in the wrong comparison set. | Create one sample row for a standard product and one for a private/custom product. |
| Landing-page fact | Ad-card image, product-page main image, product description, shipping and returns. | Promise mismatch reduces post-click buying intent and can trigger issues. | Save product hero, policy pages, and Merchant Center issue details. |
For large catalogs, do not chase full perfection first
Large catalogs create paralysis because there are too many issues. The steadier move is not to clean everything at once. Start with the products that matter most commercially.
- High-impression SKUs: they already get exposure, so title, image, or price issues directly affect clicks and matching.
- High-margin SKUs: even with lower volume, they deserve cleaner attributes, images, and policy consistency first.
- Promotion-priority SKUs: check sale price, stock, discount page, shipping promise, and fetch timing before launch week.
- Issue-heavy categories: when the same issue repeats across a category, set category rules first, then review core SKUs in batches.
Merchant Center issue triage simulator
When Merchant Center flags an issue, do not fix by issue count and do not jump into the ad console. First decide whether the issue blocks eligibility, product identity, pre-click trust, or page/policy trust.
| Symptom | Severity | First proof | Fix first | Do not do |
|---|---|---|---|---|
| Price or availability mismatch | Eligibility blocker or high-risk quality issue. | For the same SKU: feed row, product page, checkout page, Shopify stock, and latest update time. | Align price and availability facts; pause broken SKUs if needed. | Do not raise budget, change tROAS, or blame learning first. |
| GTIN / brand identity conflict | Traffic-quality issue that can become disapproval. | Supplier barcode, package photo, Shopify fields, gtin field, and product-page brand spelling. | Use the real manufacturer GTIN when it exists; do not invent one when it does not. | Do not copy a random barcode. |
| Weak title or image | Traffic-quality issue. | High-impression low-click or high-click low-conversion SKUs, title, image_link, page hero, and search demand. | Start with high-impression or high-margin SKUs; title should include category, spec, use, and key attributes. | Do not use bids or budget to hide a product card shoppers cannot understand. |
| Link, policy, or page trust risk | Eligibility or account-risk issue. | Product link, mobile hero, shipping policy, return policy, contact page, and issue details. | Fix accessibility and policy facts first, then check structured data. | Do not ask ad budget to solve page-trust problems. |
Read Merchant Center issues by business impact
Issue details help identify, understand, and resolve issues affecting products. Operationally, group them into three layers instead of reading only issue count.
| Level | Signal | Impact | Responsible |
|---|---|---|---|
| Eligibility blockers | Disapproval, account risk, unreachable links, severe price or availability mismatch. | Products cannot show reliably; fix before scale talk. | Product-data lead + site lead. |
| Traffic-quality issues | Generic titles, weak images, missing attributes, brand or GTIN confusion. | Products can show, but matching quality is weaker. | Merchandising + ads lead. |
| Optimization opportunities | More attributes, better images, richer details, stronger structured data. | Not always urgent today, but affects later scaling efficiency. | Merchandising + content lead. |
A feed edit is not done until impact is recorded
If performance improves, the team needs to know what to copy. If it worsens, the team needs to know what to roll back. Without records, feed optimization becomes unexplained field drift.
- Changed field: title, image_link, price, availability, GTIN, category, or link.
- Affected SKUs: record SKU, product name, category, and whether it is a priority product.
- Reason: which diagnostic, mismatch, or business priority drove the change.
- Update time: source-system update time and Merchant Center fetch or processing state.
- Observation window: how many days, which SKUs, and which metrics decide continue or rollback.
Three SKU repair examples
MUG-20-BLK: title only says Travel Mug, with no capacity, material, or leak-proof value. Repair by adding capacity, main use, and key attributes to the title, then matching the product-page first screen.
RUG-8X10-SAGE: feed says in stock, but the product-page variant is sold out. Fix inventory sync cadence, pause sold-out variants first, then review Merchant Center diagnostics.
DOG-COVER-L: main image is lifestyle-heavy; product body, size, and installation are unclear. Use a clear main product image, add installation images, and ensure image_link points to the main image.
Stop / Go rules
Do not let Shopping / PMax carry budget before these proofs are ready
- If high-risk diagnostics, disapproval, or account status issues remain, fix eligibility first.
- If price, availability, image, or landing page conflicts with feed, validate fact consistency first.
- If priority SKUs have weak titles, confused GTINs, or missing attributes, complete at least 10 sample checklist rows first.
- If feed changes lack affected SKUs, timing, and rollback condition, write the change log first.
When the feed is stable, the ad system has a chance to learn correctly. Otherwise, the next channel-split lesson starts from bad product facts.