You fixed your catalog. This is how you find out whether it moved.
Connect Google Merchant Center read-only and Feedmind reads what Google reports about your products: their status, their impressions, their clicks. We mark the days your approved fixes reached the store, and we are careful about what that is allowed to prove.
Our score is our number. Google’s numbers are the ones your buyers produce.
A catalog that goes from C 51 to B 68 has demonstrably become more readable. That is worth knowing, and it is still our own measurement of our own work. The merchant question underneath it, whether anything actually changed out there, needs a number we did not invent.
Feedmind never writes to your Merchant Center. Google offers only one Merchant Center permission, and it covers both reading and writing, so its consent screen will say Feedmind can “manage your product listings and accounts for google shopping”. We cannot. Our Merchant Center client has no write capability at all: there is no code here that could send Google a change, and a build that added one would fail.
Connect once, then read what happened.
Connect read-only
You approve Google’s own consent screen, which covers reading and writing because Google offers no narrower permission. We cannot. Our Merchant Center client has no write capability at all: there is no code here that could send Google a change, and a build that added one would fail. We identify the account and the primary feed, and nothing in your Merchant Center changes as a result.
Your fixes get marked on the trend
Every batch you approved has a date. Those dates are drawn on the impressions line, next to the numbers Google reported around them. The last two days stay dashed, because Google is still counting them.
Insights and a weekly digest
Disapprovals, score changes and what is waiting for approval become cards in your dashboard, each with its numbers. One email a week carries the same thing, and switching it off changes nothing about what we collect.
The trend, your fix dates, and what the numbers are allowed to mean.
The proof module sits under your score, because it answers the question the score raises without replacing it.
A disapproved product is invisible, and it is exactly the kind of problem we exist to fix.
When Google refuses a product, we show its reason in Google’s own words. Where a Feedmind fix addresses that reason, the reason links to it. Where none does, we say so and name what it actually is, rather than sending you into the fix queue to look for something that is not there.
- “Missing value [gtin]”
- Feedmind has a fix for this · queued
- “Promotional overlay on image [image_link]”
- No Feedmind fix maps to this · it is an image change in your store
Every plan, including Free. Proof is not a paid extra: if you fixed something with Feedmind, you get to see what happened next.
Impressions and clicks are Google’s numbers, reported with Google’s delay. Feedmind marks when your fixes were applied and shows the movement after them. Demand, season and competition move the same lines, so read the marks as timing, not as cause.
Google Merchant Center is a Google product. We read it on your behalf; we are not affiliated with Google.
Start with the score, then watch what your fixes did.
The free check reads a sample of your product pages and returns a score in about a minute. Merchant Center comes later, when there is something to prove.