Shopping
Operations & Governance
Merchant Centre Guard
Feed problems found before sales drop.
Continuous monitoring of your product feed and Merchant Centre account, with disapprovals, stock issues and policy warnings ranked by the revenue they put at risk.
Already a customer? Open Merchant Centre Guard in your workspace
- 6
- Checks running inside Merchant Centre Guard
- Always on
- Guardrails checked against spend and platform health
- 3
- Named outcomes this feature is measured against
- Stop losing Google Shopping revenue to silent product disapprovals.
- Fix errors on the high-margin products that actually matter first.
- Explain sudden Google Shopping drops in minutes.
Every issue, priced
Disapproved products, missing attributes and stock mismatches are pulled in continuously and ranked by the spend and revenue behind the affected SKUs.
- Disapprovals and policy warnings by product
- Missing or weak attributes surfaced with the fix
- Ranked on revenue at risk, not alphabetically
Connected to what you sell
Feed health is tied back to Shopping and PMax performance, so a sudden drop can be traced to a feed change rather than guessed at.
- Feed change history alongside performance
- Top sellers flagged the moment they go out of feed
- Alerts routed through Watchtower and notifications
The shift
What changes once Merchant Centre Guard is running
Same team, same accounts. The difference is that the decision is already measured before anyone opens a spreadsheet.
Before
- Targets, delivery and platform health are checked manually across separate tools.
- The team has to assemble the context behind merchant centre guard by hand.
- Important changes are found late, after time or budget has already been lost.
With Hookology
- Owners see the same live priorities, guardrails and evidence in one operating rhythm.
- Stop losing Google Shopping revenue to silent product disapprovals.
- Fix errors on the high-margin products that actually matter first.
- Explain sudden Google Shopping drops in minutes.
Disapproved products do not send an apology. Sales just fall.
Inside the product
What Merchant Centre Guard looks like on live accounts
This walkthrough uses our Northwind Apparel demo account so you can see the screen fully populated. On your workspace the same view is built from your connected platforms, so the first session already reflects your own numbers.
- Stop losing Google Shopping revenue to silent product disapprovals.
- Fix errors on the high-margin products that actually matter first.
- Explain sudden Google Shopping drops in minutes.
Shopping / Merchant Centre Guard
Merchant Centre Guard
Northwind Apparel
Merchant Centre Guard
Northwind Apparel - last 28 days
Every issue, priced
1,284 openDetected2
Disapprovals and policy warnings by product
Disapprovals and policy warnings by product
In review3
Missing or weak attributes surfaced with the fix
Disapprovals and policy warnings by product
Actioned4
Ranked on revenue at risk, not alphabetically
Disapprovals and policy warnings by product
Connected to what you sell
Feed health is tied back to Shopping and PMax performance, so a sudden drop can be traced to a feed change rather than guessed at.
Recent activity
Auto loggedGoogle Ads
Meta
TikTok
How confidence works
Three evidence tiers, so nothing is stuck in 'needs data'
Every Merchant Centre Guard finding is labelled with how much evidence sits behind it. As data accumulates it moves up a tier and the recommendation tightens, so thin signals are never presented with the same weight as proven ones.
Tier 1 - Confirmed
Enough of your own history behind the finding
Read straight from your spend, targets and platform health data, with enough volume behind it that Merchant Centre Guard states the position rather than hedging it.
Tier 2 - Emerging
Live signal, volume still building
The movement is real but young, so it is surfaced as directional and flagged for a second look before budget or roadmap time is committed to it.
Tier 3 - Modelled
Too little data to measure directly
Estimated from the patterns your own account has already proven, and always labelled as modelled so it is never mistaken for a measured result.
Every finding ends on one of four verdicts
When
Confirmed evidence and material money attached
What happens
It moves to the top of the queue with an owner and the expected impact stated.
When
Worth doing, but needs a slot rather than a scramble
What happens
It is sized and scheduled into the next cycle instead of jumping the queue.
When
Signal forming, evidence still thin
What happens
Tracked daily and escalated automatically the moment it firms up.
When
Noise, or impact too small to be worth an hour
What happens
Closed out with the reason recorded, so it does not resurface every week.
In practice
How Merchant Centre Guard works week to week
From connecting your accounts to the review call, here is the shape of it, plus the questions teams ask us most before they start.
Step 1
We connect your accounts
Your spend, targets and platform health data are wired up during onboarding, so Merchant Centre Guard works from your own numbers on day one rather than a sample workspace.
Step 2
Every issue, priced
Disapproved products, missing attributes and stock mismatches are pulled in continuously and ranked by the spend and revenue behind the affected SKUs.
Step 3
Connected to what you sell
Feed health is tied back to Shopping and PMax performance, so a sudden drop can be traced to a feed change rather than guessed at.
Step 4
We review it with you
We watch the account with you and raise feed fixes with your developers or platform team. Nothing sits in a dashboard waiting to be discovered.
Common questions
Most workspaces are live within a few days of the discovery call. Once your platforms are connected we backfill history, so the first session already shows trends rather than an empty screen.
Merchant Centre Guard reads your spend, targets and platform health data directly. Nothing is estimated from benchmarks, and every figure can be traced back to the platform it came from.
Disapprovals and policy warnings by product, Missing or weak attributes surfaced with the fix, Ranked on revenue at risk, not alphabetically, Feed change history alongside performance, and more.
We watch the account with you and raise feed fixes with your developers or platform team.
Why teams use it
- Stop losing Google Shopping revenue to silent product disapprovals.
- Fix errors on the high-margin products that actually matter first.
- Explain sudden Google Shopping drops in minutes.
How we set this up with you
We watch the account with you and raise feed fixes with your developers or platform team.
Our onboarding processWorks alongside
See Merchant Centre Guard running on your own data
We build the workspace around your accounts and walk you through it together. No self-serve setup, no trial to configure on your own.
Book a discovery call