Merchant Center products not showing: how to find the real cause

Merchant Center status describes whether Google has processed a product and whether it is eligible for a particular destination. It does not guarantee an impression. An approved product can receive no traffic because of demand, campaign configuration, bids, ranking, geography, or another delivery factor outside the product diagnostic itself.

Check the exact offer rather than relying on the account total. A product may be pending, approved, limited, or disapproved, and those states can differ by country, marketing method, or destination. Limited is partial eligibility; disapproved means the product cannot serve in the affected context.

Work from the broadest access question toward the most specific delivery question. This prevents campaign performance assumptions from obscuring a product-data problem.

• Confirm the product was imported and note its current processing status.
• Open its issue details and record each affected country, destination, and marketing method.
• Check whether the source refreshed after the last catalog change.
• Open the exact submitted landing page and select the same variant, currency, and region.
• If the product is eligible, investigate campaign and demand factors separately from Merchant diagnostics.

Frequent causes include destination-specific disapproval, a warning that limits reach, an unsupported target country, stale or expired source data, price or availability disagreement, identifier problems, and an inaccessible landing page. A newly submitted offer may also still be processing.

Do not edit several attributes at once without preserving the original issue evidence. The most useful correction targets the reported cause, then waits for Google to process the new source data.

Confirm the source was fetched or the API update succeeded, then check the processed value—not only the value in your store. Watch the destination-specific status until Google reports recovery. Eligibility recovery and traffic recovery are different events, so avoid promising immediate impressions.

CommerceVigil reads the issues and product states Google exposes for the connected account, tracks new, expanded, and resolved issue lifecycles, and adds traffic context only when product-to-performance matching is deterministic. It cannot see every auction or guarantee that an eligible product will serve.

• Direct Merchant product and account diagnostics
• Destination-aware affected product sets
• Read-only monitoring and scheduled reconciliation
• No automatic feed edits or guessed product matches