Merchant Center and Feed Operations
Many teams only look at Merchant Center when products are disapproved, diagnostics spike, or traffic falls. In ecommerce, titles, attributes, pricing, stock, shipping, returns, and landing-page consistency are already part of the operating system. Feed operations are not technical patchwork. They are recurring catalog governance, cross-team coordination, and business rhythm management.
What this lesson solves
Core takeaway
Merchant Center should not be a dashboard the ads team opens occasionally. It should sit inside a shared operating rhythm for merchandising, content, site, and advertising teams because product-data quality is business quality.
Why feed operations belong in the weekly rhythm, not in emergency mode
New launches, promo pricing, stock changes, image swaps, theme updates, and policy edits all change feed quality. Without recurring review, these issues may not explode immediately, but they quietly drain visibility, traffic quality, and review stability over time.
The most common slow-burn losses
- Price or stock sync becomes unreliable, so Google trusts the product less over time.
- Page and feed drift apart gradually, hurting traffic quality before anyone notices.
- The ads team only checks feed quality after performance drops, which turns every fix into reactive firefighting.
Build a minimum feed-operations dashboard first
| Section | What to review | Why it matters | Suggested cadence |
|---|---|---|---|
| High-value SKU quality | Title, attributes, images, category | Directly shapes traffic quality for the most important products | Weekly |
| Price and stock consistency | Whether feed and site stay aligned | Drives sellable-state trust and review stability | Weekly and around promos |
| Needs attention | Visibility blockers, quality issues, improvement opportunities | Creates the real repair priority | Weekly |
| Launch and promo checks | Whether priority SKUs are fully ready | Prevents campaign-week surprises | Before every major launch |
Turn the dashboard into a weekly QA checklist
A dashboard helps you see issues. A checklist helps you operate. The weekly feed review should confirm the same small set of high-risk items every cycle so the team stops relying on memory or panic.
Minimum weekly feed QA
Do not treat every diagnostic as the same kind of work
Feed teams lose time when they fix diagnostics mechanically. Strong teams sort issues by business impact, not by issue count. Some issues block visibility. Some damage traffic quality. Some are simply optimization opportunities.
A more useful triage model
- P0 blockers: products cannot show or are heavily restricted.
- P1 quality issues: products can show, but matching or click quality is weaker.
- P2 optimization items: not immediately fatal, but important for future scale.
Use an escalation map so the team knows what must move today
Not every issue belongs in the same queue. A useful operations system tells the team which problems must be fixed today, which belong in this week’s sprint, and which can stay in structured optimization backlog.
| Priority | Typical issue | Target response | Typical owner |
|---|---|---|---|
| P0 | Disapproved priority SKU, broken price sync, major stock mismatch | Same day | Ops + site or feed technical owner |
| P1 | Weak title, weak imagery, missing attributes on important products | This week | Merchandising, content, design |
| P2 | Secondary catalog cleanup, optimization opportunities, lower-value SKU improvements | Scheduled backlog | Merchandising or feed ops |
Feed operations cannot belong to the ads team alone
Merchant Center becomes stable when each issue type has a real owner. Titles and attributes are usually merchandising work. Images often need content or design. Price and stock depend on operations or site systems. Policy-page alignment depends on website and brand operations. The ads team should contribute the performance signals that show where product-data quality is limiting growth.
| Problem type | Main owner | What ads should report | Steadier collaboration loop |
|---|---|---|---|
| Weak titles or attributes | Merchandising or operations | High impressions with weak CTR, weak query fit | Fix the highest-value SKUs first and review impact |
| Weak imagery | Content or design | Good visibility with poor click response | Create image standards by category |
| Price or stock mismatch | Operations or site systems | Delivery instability and recurring product issues | Run checks before and after major price changes |
| Policy or page inconsistency | Site or brand operations | Review instability and lower credibility | Every major page change should include feed QA |
Document feed ownership with a simple RACI
The fastest way to lose control of Merchant Center is to let every team assume someone else will fix it. A lightweight RACI is enough: who is responsible for the fix, who approves the final state, who must be consulted, and who simply needs visibility.
| Work area | Responsible | Approver | Consulted / informed |
|---|---|---|---|
| Titles, attributes, product type | Merchandising | Commercial owner | Ads, SEO, feed ops |
| Images and visual standards | Content or design | Brand owner | Merchandising, ads |
| Price, stock, shipping, returns | Operations or site systems | Ops lead | Ads, support |
| Launch QA and diagnostics routing | Feed ops or growth ops | Growth lead | Merchandising, site, support |
Launches and promotions need a clear feed gate
Many feed issues do not appear during quiet weeks. They explode during launch or promo periods, when the most important SKUs carry the most expensive traffic. A steadier workflow is to run a launch gate before every major push: priority SKU list, pricing sync, stock sync, landing-page readiness, and policy consistency.
A minimum launch gate
Promotions need a pre-launch feed sheet, not a last-minute scan
When promos change price, shipping threshold, bundle logic, or featured inventory, the feed needs one explicit pre-launch pass. This is separate from the weekly QA because campaign-week risk is concentrated on a smaller set of high-value SKUs.
Minimum pre-promo feed sheet
- Priority SKU list is locked and mapped to the same page URLs that ads will use.
- Promo price, compare-at logic, stock state, shipping promise, and returns text match the site.
- Images, titles, and feed labels reflect the final promo version instead of last week’s state.
- A 24-hour post-launch recheck is assigned before traffic scales.
Community field notes
What teams get wrong most often
- Many teams hand Merchant Center issues to “the technical person,” even though the root problem is often product information, pricing logic, or landing-page support.
- Another recurring problem is that the ads team clearly sees high-impression low-click products, but no merchandising or content improvement loop follows.
- The steadier teams turn feed operations into a fixed rhythm instead of periodic cleanup after errors pile up.
Diagnostic actions
Execution checklist
Confirm before moving on
- You understand feed operations as recurring business work, not just technical troubleshooting
- You can prioritize diagnostics by business impact and assign real owners
- You can run a launch gate and recheck around major campaigns
- You understand that ads, merchandising, content, and website teams must work from the same product-data reality