Your Shopping campaigns look fine. Spend is pacing. ROAS on your top 40 SKUs is where it was last month. Nobody on the team is panicking.

Meanwhile a few thousand products in your catalog are serving at reduced performance, and a few hundred are not serving at all.

This is the normal failure mode at catalog scale. It is not a blowup. Nothing turns red on the dashboard you actually look at. Coverage just leaks, quietly, one warning at a time, until someone runs a real audit and asks why 30 percent of your catalog is invisible on Google.

What "Needs attention" actually means

Merchant Center splits problems into two buckets, and the difference matters more than most teams treat it.

Warnings do not stop your products. Google's own documentation is blunt about it: "Products that receive warnings will continue to show across Google, however their performance may be limited. If warnings aren't resolved, they can lead to disapprovals." (Issues in Merchant Center)

Read that twice. A warned product is still in the auction. It is just handicapped. You will not see a zero in your reporting. You will see a product that underperforms for reasons nobody can explain, because from the campaign side it looks like a bidding or demand problem.

Disapprovals are the loud version. A disapproved product stops showing across Google until you fix the underlying issue and it gets re-approved.

The trap is that most teams only build a process around the loud version. You get a disapproval, someone fixes it, everyone moves on. Warnings sit in the account for months because they never generate a crisis. Then they become disapprovals, and by then you are fixing them in bulk under pressure.

Product-level vs account-level, and why scale changes the math

Product-level issues affect individual items. Your data does not match the site, or it does not follow the product data specification, or it breaks a Shopping policy. The damage is contained to that product.

Account-level issues hit everything. Google issues a warning with a period to fix it. If it is not resolved by the end of that window, the account gets suspended and products stop appearing across Google. In some cases where an egregious issue is detected, there is no warning at all and suspension is immediate (Issues in Merchant Center).

At 200 SKUs, you can eyeball this. Someone opens the account, reads the list, fixes the five things.

At 1,000 to 10,000 SKUs, that stops working. The issue list becomes a scrolling wall. Product-by-product review is not a task anyone can complete, so it turns into a task nobody starts. That is the actual mechanism behind most coverage loss at catalog scale. Not incompetence. Volume without triage.

One more wrinkle if you sell into multiple markets: products targeting multiple countries can receive different disapprovals or warnings per country, because policy differs by location. A SKU can be clean in one market and blocked in another, and your account-level view will not make that obvious.

Preemptive item disapproval, and why it spreads

The one to understand properly is preemptive item disapproval, or PID.

PID happens when the price or availability in your product data does not match your landing pages. Google's language: "When a PID is in place, we err on the side of caution and disapprove products that are likely to violate our requirements." A review is required to clear it (Issues in Merchant Center).

That phrase, "products that are likely to violate," is the part that catches large catalogs. This is not a per-SKU verdict on items a reviewer personally checked. It is a preemptive action based on pattern. A sale that went live on the site before the feed job ran can put a whole class of products into that state, not just the specific ones a reviewer sampled.

Google is explicit about the fix direction. Submit your product data at the same time you update the website. If your site updates at 2:30 AM, submit your data source at 2:30 AM. For frequently changing prices, use the Merchant API to push updates as they change in your own system. Automatic item updates help, but Google describes them as most appropriate for a small portion of inventory and not a replacement for accurate data (Provide high-quality data).

If your promo calendar moves faster than your feed schedule, this issue is not a one-time cleanup. It is a recurring tax.

Triage by impact, not by inbox volume

You are not going to fix every warning. Stop planning as if you will.

Merchant Center has a Priority fixes toggle on the Needs attention page that filters to issues likely to have medium or high impact on performance and potential clicks. Turn it off and you see everything, including the noise. The Issue Details Page shows business impact with metrics like lost click potential, plus a downloadable CSV of every affected product for a given issue (Issues in Merchant Center).

That CSV is the useful artifact. It turns "we have a lot of warnings" into a list you can join against your own margin and revenue data. Fix the issue class that touches your best products first. Ignore the class that touches 900 discontinued items you were going to drop anyway.

Then check the other side. Feed approval is not campaign coverage. Google Ads has a separate Product issues surface, and one of the issue types is "No campaigns advertising this product," which means either the product is not in a campaign or every campaign it belongs to has a problem (About Product issues). A perfectly approved SKU can sit in Merchant Center doing nothing because a product group filter never included it.

Two systems. Two ways to be invisible. Most audits only check one.

What good looks like

A weekly rhythm beats a quarterly cleanup. For a 1k to 10k SKU store:

  • Sync the feed on the same schedule as your site updates, not on its own cadence
  • Open Needs attention weekly with Priority fixes on, and download the CSV for the top issue class
  • Fix by issue class, never product by product
  • Track account-level warnings separately with a hard deadline, because those are the ones that end in suspension
  • Check Google Ads Product issues for approved SKUs with no campaign attached
  • Re-verify country support before you plan any Shopping expansion, since Shopping ads and free listings only run where the target country is supported

None of that is clever. It is just owned. The stores that lose coverage are not the ones missing tactics, they are the ones where feed health has no owner and no calendar slot.

Where this connects to how you run marketing

Feed health, campaign coverage, and creative all sit in different tools, which is why coverage gaps survive so long. The feed person sees warnings. The media buyer sees ROAS on winners. Neither view shows the SKU that is warned, underperforming, and still technically live.

We will not claim it clears a Google suspension for you. Nothing does that except fixing the underlying data and passing review.