Approved in Merchant Center, but not showing on Google? Start with the right evidence

AISEO Site · Published 13 September 2026 · Updated 10 October 2026

An approved product is not a promise of an impression. Before changing your feed or increasing an advertising budget, identify the missing result: an eligible listing, a recorded impression, a click, or a sale. Each has a different test, and fixing one does not automatically fix the next.

For an online retailer, the most useful first check is a single product in a single country and marketing method. Confirm its status, examine the matching performance report, then follow its submitted link as a shopper. Searching for your own product once is a useful observation, but it is not a complete visibility audit.

First, name what is actually missing

“My product isn't on Google” can describe several unrelated situations. A product page can appear in ordinary web search without showing in a Shopping placement. A product can be eligible for free listings without receiving impressions. A paid campaign can have a delivery problem while the store's unpaid listings continue to receive traffic.

Start by writing one sentence: “For item ___, in country ___, on free listings / Shopping ads, during ___, I expected ___ but observed ___.” Keep the item ID, destination and date range alongside any screenshots. This prevents two people from investigating different products while believing they are discussing the same issue.

Google explains that free-listing permission does not guarantee display. Your immediate objective is therefore not to force a particular search result. It is to find a specific restriction, missing measurement or customer-facing defect that you can verify and address.

Check the item's exact eligibility context

Open the affected item and record its country, marketing method, current status, visibility and issue text. A green account total is not the state of this item in this market. Preserve the observation time and compare it with the latest processed product update.

If the item is hidden, determine whether that was an intentional store decision. If it is processing or under review, retain that state rather than calling it approved. If it is restricted, follow the stated issue and affected scope. Google's product-data status guidance helps distinguish these observations.

Check account-level issues before changing one title. For a country-specific failure, inspect that market's product, delivery and policy requirements. For an explicit all-products free-listings eligibility issue, use Google's issue guidance; do not claim a generic feed reupload will resolve a restriction whose reason has not been established.

For ads, separately confirm the linked Merchant Center account, campaign status and product inclusion in Google Ads. A free-listings state does not establish paid campaign delivery. Diagnose a stated eligibility or inclusion problem before making a budget decision.

Read the matching report before changing the offer

No report or insufficient detail is available

Select the item, market, method and dates that match the complaint. Use the available performance filters and preserve them in the export. If the report or item detail is missing, record “not available” and check its scope and data threshold. Do not manufacture zero impressions from an empty screenshot.

Google describes performance reporting scopes and paid and organic tracking. An account total containing other items is not proof that this item appeared.

A valid report shows zero impressions

Confirm the report covers the time after the item became eligible. Check whether low volume or limited reporting is relevant, and preserve any stated restriction. If no fault is established, monitor a defined later window rather than repeatedly deleting, recreating or renaming the item to force a result.

Zero in this scope does not mean a universal ban, and approval does not guarantee a placement. Record what is known: eligible in the checked context, no impressions reported in this interval, and any unresolved reporting or delivery question.

Impressions exist, but clicks are absent

Display occurred in the report's scope. Review the exact offer a shopper sees: identity, main image, price, delivery terms and descriptive title. Choose a change supported by that review, save its before state and compare a later aligned period. Do not rewrite every attribute at once and then attribute the result to one change.

The absence of clicks does not identify whether the offer is uncompetitive, irrelevant or simply observed over too small a sample. Keep those as hypotheses until the evidence distinguishes them.

Clicks exist, but visits or orders seem absent

Follow the submitted link and customer path next. Compare the site's analytics configuration, consent and attribution if its visit count differs. Merchant Center clicks, recorded sessions and completed orders are separate measurements. A click count cannot prove revenue, and a missing analytics event cannot by itself prove the shopper never arrived.

If the page or cart is broken, repair that demonstrable defect. If the path works and the question is conversion, use actual transaction and attribution evidence rather than treating approval as a sales guarantee.

Follow the submitted link like a customer

Copy the actual product URL associated with the item, rather than finding a similar product through your store's navigation. Open it on a phone-sized screen and check the following:

1. The link reaches the intended product without a broken page or unexpected login wall.
2. The selected color, size or pack is the same offer the listing describes.
3. The displayed currency, price and stock state match that offer.
4. A customer in the target market can find delivery charges and return information.
5. Adding the item to the cart preserves the selected product and price. Stop before placing a real order unless you are carrying out an authorized test purchase.

This check does not prove what Google's crawler saw. It establishes whether an ordinary shopper can currently complete the next step. If Google reports a crawl failure, retain that diagnostic separately and investigate server or access behavior instead of treating your own successful visit as proof that the failure is impossible.

For a price disagreement, use our guide to an old price still appearing on Google. For a wrong color or size, follow the product-variant link checklist. Those are narrower problems with their own evidence; they do not need a second generic feed rebuild.

A worked example: the same complaint, three different actions

The following is a constructed diagnostic example, not a customer result or a claim about traffic we generated. All three rows describe the same fictional desk lamp at different stages. The numbers illustrate how the decision changes; they are not performance benchmarks.

For snapshot C, the reported click-through rate is 6 / 120 = 5%. That calculation says nothing about profitability or purchases. For snapshot B, a 0% click-through rate does not identify the cause. You still need the product, market and offer context before drawing a conclusion.

The practical benefit of this table is its stopping rule: once you have evidence for one stage, stop treating an earlier stage as completely absent. Move the investigation to the next unresolved step.

Keep a small incident record

Before a change, record the item ID, market, marketing method, submitted URL, status, issue text, report dates, impressions and clicks. Add the observation time and the source of each field. Use “not checked” or “not available” instead of filling a blank with zero.

Download the blank incident record (CSV). It contains 20 fields, with unverified values explicitly marked “not checked.” Keep the completed file private: it is a handoff document for your team, not something to upload to a public forum.

We tested the decision aid against seven constructed records, including unknown eligibility, a known restriction, missing reports, zero impressions, impressions without clicks, and clicks with and without a broken customer path. All seven led to the intended next investigation. Four additional checks confirmed that missing data and zero impressions do not produce a calculated CTR, while 0/120 is 0% and 6/120 is 5%. You can download those example records and expected decisions (CSV) to check the logic yourself. This is a reproducible test of the worksheet's reasoning, not evidence of Google's delivery behavior or a customer outcome.

After a change, record exactly what was edited and when. Recheck the item status and customer path, then compare performance only after the relevant period has elapsed. A new screenshot taken five minutes later can confirm a corrected page, but it cannot establish a long-term traffic improvement.

If you need help, this short record is more useful than a screenshot of an account-wide approval percentage. Never include passwords, API keys, customer details or unrelated account exports in a public support post.

Common questions

Why are my products not showing up in Google Shopping?

First separate eligibility from observed display. Check the product's country, marketing method, visibility and reported issues, then inspect impressions for the matching period. An enabled free-listing method does not guarantee a placement. If the product has impressions, focus on the next missing outcome instead of assuming it never appeared.

How long does it take for Google Merchant Center to approve products?

Use the current item's status, review instructions and observation time. Processing, policy review and first reportable impressions are different stages. An estimated review period is not a promise of display or clicks. If the shown state exceeds the account's stated guidance, retain the issue record and use the support path appropriate to that issue.

Does approval mean I should increase my ad budget?

No. Approval alone is not evidence that budget is the limiting factor. Confirm that the intended campaign is eligible and includes the product, then examine its own delivery diagnostics. Keep this investigation separate from free-listing visibility. Do not spend money merely to test an unverified assumption.

Will submitting a sitemap make my products appear in Shopping?

A sitemap helps communicate site URLs, but it does not replace Merchant Center product eligibility or guarantee a Shopping placement. Google's ecommerce guidance distinguishes providing product data from making website content discoverable. Treat them as complementary work, not interchangeable approval buttons.

What to do next

Choose one affected product today. Build its incident record, verify the correct marketing method, inspect its actual performance and follow its submitted link. Fix the first demonstrated defect, then check the result without changing unrelated parts of the catalog.

Keep the verified item state, exact report scope, customer-path result and next observation date together. AISEO Site provides Search Console performance analysis and a daily email; Merchant Center status and campaign repairs take place in those separate systems.