Merchant Center free listings: why products don't show

Merchant Center free listings let eligible products appear on Google without paying for the listing. Google uses the submitted product information to match offers with searches; enabling the feature does not guarantee that any particular product will appear. According to Google’s free listings guidance, permission to participate and actual exposure are separate matters.

A missing product can mean that the account has a problem, that one offer failed a requirement, or simply that an eligible offer has received little exposure. Find out which situation applies before rewriting titles or changing the catalogue. Otherwise, several changes can obscure the original cause.

For a retailer in Spain, the useful question is specific: which products fail to appear, for which country, and at which stage? This guide follows that question through Merchant Center, the product data source and the shop. It addresses online product listings. Category architecture, Product schema implementation and decisions about retiring unavailable URLs have their own guides; a feed incident does not automatically require changes to all three.

Establish what “not showing” means

Start by writing down the evidence behind the complaint. “I cannot find our kettle on Google” is an observation. “The Spanish free listing for this item is disapproved for a price mismatch” is a diagnosis you can act on.

Open the affected product in Merchant Center and record its ID, country, marketing method, status and issue text. Save the last relevant notification and the current submitted values. If the shop uses several product sources, note which one supplied the item. Check the free listings setting too; a remembered setup decision is less useful than the account’s present configuration.

According to Google’s explanation of Merchant Center issues, product issues affect individual offers, while account issues affect all products. Warnings and disapprovals also differ: a warning can limit performance, whereas a disapproved product stops showing. The Needs attention view lists product issues and lets you download affected items. Read the scope and severity before choosing a fix.

Use the triage table to assign the investigation, then follow the instructions attached to the issue.

Keep the original export. After an edit, you need to distinguish an old notification from a problem that still exists. A screenshot of a red status with no date, item ID or country is poor evidence for deciding whether a release worked.

Confirm that the shop and the intended market qualify

Free listings have their own policy requirements. Google groups them into prohibited content, prohibited practices, restricted content and website requirements; enforcement can include listing restrictions, disapprovals and account suspension. A product being lawful to sell does not, by itself, establish eligibility for Google’s programme. Read the applicable free listings policies, especially before uploading a restricted range.

For an account issue, inspect the buying journey as a customer who has never heard of the business. Can that person understand what the shop sells, who they are buying from and the terms of the purchase? Keep the investigation tied to the notice. Do not assume that adding a trust badge, a longer company biography or a new theme resolves an unspecified policy concern.

Check the store connection before asking the merchandising team to repair hundreds of offers. Google describes verification as proving that you can edit the website, and claiming as associating the verified address with Merchant Center. The steps are related but distinct. An agency should confirm the connection for the actual shop domain using Google’s URL verification guidance, with access retained by the business.

For products targeting Spain, Google requires shipping information through Merchant Center shipping settings or the product shipping attribute. Google also tells merchants to publish return policy information on their websites and recommends adding it in Merchant Center. Those are explicit parts of free listings setup, not details to leave until traffic arrives.

As an operational check, choose a real destination the shop serves and test the full order journey. For a Barcelona retailer shipping beyond Catalonia, inspect the destinations with different delivery conditions as well. Record what the customer sees and what the account declares. If the business excludes a destination, or charges differently for certain items, the person configuring delivery must know that before interpreting a shipping warning.

A Catalan website and a supported feed language are separate decisions

Google’s supported-language list includes Spanish and English but does not include Catalan. Its guidance also requires the relevant product page and purchase-flow elements to use the language of the submitted data. Consult the supported languages and currencies before selecting a feed language.

A shop in Girona can therefore retain its Catalan website while planning a Spanish purchase route for its Spanish feed. Treat that as a complete customer journey. A Spanish title leading to a Catalan product selector or checkout needs investigation; translating only the feed is insufficient. An English route makes sense when the business intends to serve that audience and can maintain the corresponding content.

This is a channel configuration decision, not a recommendation to replace the site’s language strategy. Record the selected language, destination URL pattern and person responsible for translations. That gives the next developer a clear rule when the storefront changes.

Trace one offer from the source to the checkout

A clean spreadsheet cannot establish that the customer sees the right product. According to Google’s landing page requirements, the submitted link must lead to the specific product, with matching product details, price, currency and availability. A category page or a generic search result is not the correct destination.

Follow the exact submitted URL, including the variant selection. Avoid starting from the home page and browsing to the item: that may create cookies or selections which hide the faulty journey. Compare the received data in Merchant Center with the shop’s source record, then compare both with the page and basket.

For example, imagine a retailer submitting a blue, 750 ml bottle. This is a hypothetical diagnostic example, not a client result. If the submitted link opens a red, 500 ml bottle, a correct price elsewhere on the page does not settle the issue. Establish whether the feed chose the wrong URL, the storefront dropped a variant parameter, or the source record confused the two products.

Use a small working sheet with one row per affected offer:

• product ID and selected variant;
• value in the catalogue’s source system;
• value received by Merchant Center;
• value on the linked page and in the basket;
• time checked, discrepancy and responsible owner.

Choose examples that reveal differences: a standard product, an item on sale, and a variant if variants are involved. Expand the sample when these reveal different failures. Sampling helps locate the cause; it does not prove that the rest of the catalogue is correct.

Google’s product data specification requires stable, unique item IDs and specifies which attributes are required or conditional. Keep the ID when updating an existing product. Review titles, descriptions, links, images, price and availability, then inspect the extra requirements relevant to the product rather than treating a generic feed template as complete.

If the investigation reaches page markup, use the dedicated guide to Product structured data for ecommerce. The task here is to establish agreement between the offer and the shop. A successful schema test cannot answer whether the source connector submitted the intended item.

Repair the source of recurring mismatches

According to Google’s price mismatch guidance, different update times, incorrect structured data, differences between what bots and shoppers see, and sale-period settings can produce price discrepancies. Compare timestamps before concluding that a value is permanently wrong.

Consider a hypothetical promotion that begins at 09:00 while the next catalogue export runs at 12:00. The operational problem is the gap between two updates. A manual edit may make one offer agree temporarily, but the durable correction belongs to the publication process. Check the promotion’s start and end, the timezone, the export schedule and any cached page response.

Name the authority for each field. The commerce platform might own price, a warehouse system might supply availability, and a separate catalogue might own product descriptions. Someone needs to be able to trace the value through those systems. Write down any transformation between those systems and Merchant Center, including overrides maintained by an agency or feed tool.

A useful repair sequence is to correct the owning source, run its normal update, inspect the received item and repeat the customer journey. Then watch the next scheduled update. If that update reintroduces the error, the incident is still open. This is a recommended maintenance procedure, not a Google review deadline.

Google’s automatic updates can use landing-page information to correct temporary product discrepancies, but they are not a replacement for regular product data updates. The automation guidance explicitly says that coverage does not extend to every product. Treat this feature as assistance while keeping the source accurate.

Where availability is the disputed value, settle the commercial truth first: can the customer order the item under the terms shown? For decisions about temporary stockouts, backorders or permanently retired products, follow the separate stock lifecycle SEO guide. Do not redirect a useful product page merely to clear a Merchant Center warning.

Check identity and images without inventing missing information

A GTIN identifies a trade item; it is not a spare field for an internal code. Google’s GTIN requirements say to submit the correct manufacturer-assigned identifier and not guess one. Where the product has no assigned GTIN, follow the identifier requirements for that product rather than borrowing a number from a similar item.

For a reseller, ask the supplier to resolve uncertainty about the exact pack or variant. A shared model name does not establish that two offers have the same identifier. Keep the evidence with the catalogue record so the issue does not return when a new staff member refreshes the feed.

For an image issue, start with the submitted image URL and the image that actually loads. Check whether it depicts the offered variant and whether the export points to an old or generic asset. Google’s product data specification includes image requirements and warns that low-quality images or conflicting data can prevent listings from showing. Read the specific image issue before commissioning replacements for the entire range.

Close the review loop with evidence

Once the correction is live, follow the action offered for the specific issue. Google directs merchants to correct the product data and resubmit it through the chosen method; review requirements depend on the issue. Its issue guidance also notes that products targeting multiple countries can receive different warnings or disapprovals in each country.

That makes “the feed is green” an incomplete completion criterion. Confirm the affected marketing method and country, not just a general account total. Record the product’s current state beside the original issue. If it remains disapproved, determine whether the notice concerns the same value, another requirement or an account restriction.

For price mismatches, Google describes automatic recrawling over the following hours or days, with reapproval after the price matches. That is a process description, not a guaranteed service level for the shop. Follow the available review route in the price mismatch instructions and retain evidence of the corrected page.

If escalation is needed, prepare an account identifier, affected item IDs, the country and method, the exact issue wording, and dated evidence of the correction. Avoid sending unrelated customer orders or personal information. A concise reproduction is more useful than a long message saying that everything has already been checked.

Do not call the incident solved merely because someone clicked a review button. Close it when the relevant status reflects the correction and the next normal data update preserves it. Separately record whether exposure has resumed; that is a performance observation rather than proof that no further data issues exist.

Measure the path from eligibility to purchases

According to Merchant Center’s performance documentation, impressions count product appearances, clicks count visits generated by product clicks, and CTR is clicks divided by impressions. These metrics describe different stages. Google advises checking approval and allowing a few days when impressions are zero; insufficient data can also produce a zero report.

Use the free listings filter and a fixed product group when comparing periods. Save the original item list and flag products that entered or left the group. Otherwise, adding a large new range can change the total while hiding whether the repaired offers improved. Choose complete periods that suit the shop’s trading pattern; a 28-day comparison is a workable internal reporting choice, not a Google threshold.

Keep a compact incident report:

A hypothetical calculation illustrates the reporting distinction: 60 clicks from 3,000 impressions is a CTR of 2%. It says nothing on its own about profit or incremental sales. Keep acquisition reporting next to the shop’s commercial measures, including cancellations and fulfilment costs, before deciding how much maintenance effort the channel merits.

Google says Merchant Center auto-tagging adds the srsltid parameter to relevant product-click URLs and that auto-tagging alone does not complete key event tracking. Review the auto-tagging setup and test whether the storefront accepts the parameter without breaking the destination.

Merchant Center can use a linked Google Analytics 4 account for key event tracking, or a Google tag when that account is not available. Follow the key event tracking instructions, then validate a purchase through the site’s existing testing process. Check that the event value and currency agree with the order. Record known measurement gaps instead of treating untracked purchases as zero sales.

Use Google Search Console alongside this report when investigating organic traffic to product pages. Keep the reports’ scopes explicit and avoid adding their clicks together as if they were separate customers. A feed repair, a title change and a seasonal promotion released together cannot provide a clean estimate of the feed repair’s effect.

Give the catalogue a maintenance owner

Open a dated investigation for one product group the business cares about. Choose offers the business wants to sell and can fulfil. Record the problem, the owning system, the planned correction and the evidence that will close it. Ask one person to own the whole investigation even when several teams make changes.

For a smaller shop, that may be a shared sheet reviewed after catalogue updates. A larger retailer may need automated comparisons and alerts. Both need a way to identify repeated discrepancies and return them to the source owner. Buying a more elaborate feed tool makes sense only after the team can state which maintenance problem it must solve.

If the products are eligible and the data agrees, move the discussion to the offer and its audience. Review whether the item is clearly identifiable, whether the purchase terms are competitive for the intended customer, and whether the resulting visits justify further effort. Wider product discovery through navigation belongs in the ecommerce category SEO guide.

For an external review, prepare the Merchant Center issue export, a small set of affected URLs and the date of the last catalogue change. Those are enough to begin a focused conversation with Ighenatt about the failing step and who can repair it.