Seeing “Approved” beside a product that still is not visible on Google feels contradictory. In Merchant Center, those labels answer two different questions.
Status tells you whether Google has accepted the product data. Visibility tells you whether the product is currently showing. Google notes that a product can have approved data and still be marked not visible because another issue sits outside that product row, such as a policy problem or an unavailable store view.
The useful next step is not a full feed rebuild. Start with one affected product, work out which layer is stopping it, and fix only the confirmed problem.
Approved and visible are not the same thing
Merchant Center uses status to describe the health of the product data it reviewed. A product may be under review, processing, approved, limited, or not approved. Visibility is the separate control that tells you whether the product is currently showing on Google.
That distinction matters because an approved row can make a merchant assume everything is working. Google’s own Merchant Center guidance says approved data can still sit beside a not-visible result when another issue applies, including a policy problem or a store view that cannot be used.
Treat the two columns as a starting point, not a final diagnosis. Status tells you whether the product record passed its review. Visibility tells you whether the result is showing now. Neither column, by itself, explains every reason behind the outcome.
- Status asks: was this product data accepted?
- Visibility asks: is this product showing right now?
- Limited means the product may show only in some places, countries, or marketing methods.
- Needs Update is a freshness warning layered onto the current status, not a separate approval status.
Open the affected product and check its visibility, source, last update, destinations, and issue details before deciding what needs to change.
Start with one product, not the whole feed
When many products seem affected, it is tempting to replace the feed, reconnect an app, or rewrite every title. That can create more moving parts before you know what failed.
Pick one product you can verify on your store. Open its product details in Merchant Center and write down what Merchant Center shows for status, visibility, price, source, and last update. Then open the product page as a shopper would and compare the basic facts.
This small test helps separate a single-product problem from a wider source, account, website, or policy problem. If one item is hidden, the fix may be a visibility setting. If a large group from the same source is affected, the source or destination deserves a closer look. If the product row looks clean but the store cannot be reached reliably, the website may be the blocker.
- Choose a product that should be active and purchasable.
- Record its product ID and data source.
- Check whether it is visible, hidden, limited, or carrying an error.
- Look at the last update date.
- Open the exact product link and confirm that it loads without a login, location block, or error.
Check whether the product was hidden or has gone stale
Some visibility problems are ordinary settings problems. Merchant Center lets merchants hide and show products. A hidden product is not the same as a disapproved product, so it can look healthy while still being intentionally kept from showing.
Freshness is another simple check. Google says the Needs Update indicator appears after product data has not been refreshed for 30 days. Leaving data untouched can reduce visibility and can eventually lead to removal from Merchant Center.
If the source is supposed to update automatically, confirm that it is still sending data. Check the source rather than changing the product row by hand and creating a short-lived mismatch. For a Shopify store, that may mean checking the Google and YouTube sales channel. For another platform, it may mean checking the scheduled file, feed app, or API connection that owns the product data.
- Confirm the product is set to show, not hidden.
- Check whether the source updated when expected.
- Review whether products were archived after being hidden.
- Avoid manual edits that will be overwritten by the next source update.
- Fix the source when the same stale value affects many products.
Compare the product file with what a shopper sees
Merchant Center can accept a product record and still find problems later when it checks the store. The product file and the live product page should agree on the details that affect a buying decision.
Start with title, price, currency, stock, product link, and image. Then check product codes, sizes, colours, and other options when they apply. Google’s product data specification names incorrect categories, bad product codes, weak variant details, low-quality images, and conflicts between the submitted data and the website as common causes of display issues.
The product information built into the page, often called structured data or schema, should support the visible page rather than tell a different story. If the page shows an item in stock for $49 but the submitted product data or page markup says $39 and out of stock, adding another feed rule will not create a trustworthy result. The facts need to be reconciled at their source.
- Product title identifies the same item in both places.
- Price and currency match the landing page and buying flow.
- Stock status matches the option a shopper can actually select.
- The link opens the correct, stable product page.
- Images show the correct product or option.
- Product codes and variant groups are used consistently when available.
Look beyond the product row
A clean product row does not rule out a wider store problem. Google lists landing-page, checkout, shipping, language, currency, and policy requirements alongside the product data specification. Merchant Center also notes that an approved product can be not visible when the store view is unavailable or a policy issue applies.
Check whether Google can reach the same page a shopper sees. A page that works for the store team may fail for visitors in another region, redirect through a challenge, hide prices until login, or show a different currency than the submitted product data. Missing contact, shipping, return, privacy, or business information can also make the purchase context harder to verify.
This is where random feed edits become expensive. If the real issue is access or store policy, changing titles and product codes will not solve it. A focused site review should confirm page access, visible product facts, the information built into the page, and store policies before remediation starts.
- Test the product link in a clean browser session.
- Check regional redirects, currency, and language behavior.
- Confirm that a shopper can see price and stock without signing in.
- Review shipping, returns, contact, privacy, and terms pages.
- Use Merchant Center’s Needs attention area for account and product issues.
Choose the cleanup path from the evidence
Once you know where the mismatch sits, the next step becomes smaller. Missing fields, broken product codes, weak variants, stale prices, and unreliable source files belong in catalog cleanup. Blocked pages, conflicting page markup, missing policies, and unclear seller details belong in storefront cleanup.
Autonomous Path separates those paths. Catalog Scanner checks a product file for missing, invalid, conflicting, and inferred values. Site Scanner checks whether product pages can be reached and whether product details, page markup, and store policies line up. Predefined rules determine the findings and scores. AI helps explain the result but does not change it.
Neither scanner can promise that a product will appear. The value is a narrower diagnosis, a documented finding, and a recommended next step that fits the confirmed problem.
- Source data problem: run Catalog Scanner.
- Page access, markup, or policy problem: run Site Scanner.
- Confirmed catalog issue: plan Catalog Remediation and validate the revised output.
- Confirmed site issue: plan AI Search Remediation in staging or a branch, then validate before approval.
If the affected products share one data source, start with Catalog Scanner. If the product row looks clean but the store cannot be verified, start with Site Scanner.