Google Merchant Center Feed in Shopify: 88 to 3,819 (Simply Explained)

The day my Google Shopping went dark

I run a clothing brand out of San Diego. Handmade product, a few thousand items in the catalog. The kind of catalog that should be showing up in Google's free shopping results every single day.

Then I checked my account and saw the number: 88 products showing. Out of thousands.

The agency I'd been working with had a clean explanation. My whole category, fashion, was getting blocked for "adult content." About 98% of my products disapproved. Their take was basically: clothing trips Google's filters, nothing you can do.

That's the kind of answer people give when they've given up. It sounds technical enough to be true and final enough to end the conversation.

Here's what a dead Google feed actually costs you. Zero free shopping listings. Zero products showing in your paid ads. You're paying for the store, the catalog, and the ad account, and the one thing that turns all three into money is switched off.

For a brand built on people finding your products, that's not a small bug. That's a hole in the floor.

So I did the thing the agency wouldn't. I looked under the hood.

"Your category is against policy" is usually a shrug

When someone tells you your entire category is banned, ask one question: is that a real diagnosis, or is it just a way to stop looking?

Real bans exist. Weapons, certain supplements, actual adult content. But those come with clear warnings. Google names the violation. It's loud and specific.

What a real ban does NOT look like is 98% of a clothing catalog going down all at once, in exactly the same way.

Think about it. A content filter might flag a few swimsuits. Sure. But it's not going to flag your plain cotton t-shirts and your tote bags for "adult content." When everything goes down together, including stuff that couldn't possibly break any rule, the policy story falls apart.

That sameness was my first clue. A real ban is surgical. It hits the specific items that broke a rule. When it hits everything equally, the problem isn't policy. It's a plumbing problem somewhere upstream.

What was actually broken

Here's the real cause.

My store was set up to sell internationally, with four different regions and currencies. Sensible on paper. But behind the scenes, those four regions had quietly turned into six separate product feeds being sent to Google. Most of them broken.

Out of all those products, only 88 were being sent to Google with the right information attached. Those 88 survived. Everything else was technically there but completely unusable.

The actual problem was one missing piece of information: the country. Every broken product was being sent to Google without a destination country attached.

Here's why that matters. Google's shopping listings are country-specific. A product with no country assigned is a product Google literally cannot show anyone. There's no place to put it. It's invisible by definition.

Now here's the sneaky part. When Google hit those broken products with no country, it didn't say "hey, this product has no country." Instead it grabbed a random reason from its list and stamped "adult content" on top.

So those 1,339 "adult content" rejections were a symptom, not the disease. The disease was the missing country field. The "adult content" label was just noise Google spit out while choking on bad data.

That's why it was so easy to miss. The dashboard shows you the rejection reason. It does not show you the broken plumbing behind it. Everyone read "adult content" and believed it. Nobody checked the country field that would have told the truth in thirty seconds.

The agency read the label. I read the field.

The fix: build my own pipe to Google

The built-in tool that connects a store to Google is a black box. You set it up, it sends a feed, and when something's wrong you have almost no way to see why. With my international setup in the mix, it was secretly sending six feeds and breaking the country information on most of them.

I can't fix what I can't see.

So I stopped fighting the black box and built my own connection straight to Google. Think of it like a direct phone line instead of passing messages through a confused middleman. One feed. Targeted at the US. Fully under my control.

What that direct line does is unglamorous but critical. It forces a country onto every single product, no exceptions. It translates my internal product categories into the categories Google actually understands. It builds out the color, size, and gender details Google needs instead of hoping the store sends them correctly. And it checks every barcode so a bad one never quietly kills a listing.

None of that is clever. The point is that I control every detail on every product, instead of crossing my fingers that someone else's tool gets it right across six feeds in two currencies. When something breaks, I can find it, fix it, and resend. That's the difference between owning the pipe and renting it.

88 to 3,819 overnight

I sent the new feed and watched the account.

It went from 88 products showing to 3,819 approved, at 98.1% approval, in about a day.

That's the whole story in one line. The catalog had been dark for months, not because of any policy, but because of one missing piece of information. Once that was fixed on every product, Google approved almost all of it overnight.

And that "adult content wall" everyone treated as an immovable ban? The 1,339 rejections dropped to 32.

That's the proof right there. A real ban doesn't collapse from 1,339 to 32 because you fixed a country field. A plumbing problem does. The wall was never a wall. It vanished the second the products were valid.

I'll be honest about those last 32. Those are real edge cases, mostly swimwear, where Google's filter has an actual opinion. Worth fixing one by one. It's not magically 100%, and anyone promising you 100% is selling you something. But 32 real edge cases is a completely different problem than 1,339 fake ones.

Here's the lesson buried in those numbers. The bottleneck was never effort. Nobody was lazy. The bottleneck was the diagnosis. Everyone accepted "it's against policy" and stopped looking. The actual fix took a day once someone opened the feed.

Three checks before you believe a "policy" excuse

If someone tells you your category is banned, run these three checks first. They take an afternoon.

First, check whether your rejected products have a country assigned. If the country is blank, you have a plumbing problem, full stop. No policy on earth rejects a product that was never given a place to show up.

Second, look at how spread out the rejections are. A real ban is targeted at specific items. A data bug takes down hoodies and swimsuits at the exact same rate. If everything went down together, it's a structural problem, not a ban.

Third, count how many feeds Google is actually receiving versus how many you meant to send. International and multi-currency setups quietly fan out into extra feeds, and the extras are usually the broken ones.

If all three point at the feed, then "your category is against policy" was never the answer. It was the thing someone said instead of looking.

This is why I don't stop at advice. Advice would have been "your feed looks suspect, you should look into it." That's worth nothing when your shopping is dark and your competitors are filling the listings you should own. I find the real problem, then I build the fix and hand over something that keeps running after I'm gone.

Ready to bring AI leadership into your company?

I work with a small number of companies at a time. If you're serious about AI, apply to work together and I'll review your application personally.

Apply to Work Together