Shopping reports & merchant opportunities

Use merchant listings, product snippets, shipping, returns, and opportunity reporting together.

GSC UI required Intermediate

Search Console's Shopping area can combine three different functions: structured-data quality reports, recommendations for eligible merchants, and simplified shipping and return settings. They do not have the same eligibility rules, data source, or purpose.

Use the Product snippets and Merchant listings reports to monitor product structured data. Use Merchant opportunities to improve an eligible physical-goods store's commerce information. Use Settings → Shopping → Shipping and returns to manage simplified policies when that is the correct source of truth.

This guide reflects Google's documentation on July 18, 2026.

What can appear in the Shopping area

Feature	What triggers it	What it answers
Product snippets report	Google finds supported product-snippet structured data	Which sampled product items are valid or invalid for enhanced text results?
Merchant listings report	Google finds supported merchant-listing structured data	Which sampled purchasable product offers are valid or invalid for merchant experiences?
Merchant opportunities	Google recognizes an eligible site that sells physical goods	Which store or account details could improve the shop's presentation on Google?
Shipping and returns setting	Eligible merchant/property and sufficient permissions	Which simplified shipping and return policies are supplied through Search Console?

The reports can appear in different combinations. Do not treat the absence of one feature as proof that every other feature is broken.

How Google identifies an online merchant

Search Console determines merchant status programmatically. Its general definition describes a consumer-facing site where customers can purchase physical goods or services directly on the site.

For Search Console's merchant reporting purposes, these are not online merchants:

Affiliate sites that send the visitor to another seller.
Sites where the transaction cannot be completed on the site.
Business-to-business sellers outside the documented consumer definition.

The Merchant opportunities report has a narrower documented eligibility statement: it is shown to eligible sites that sell physical goods.

Adding Product markup can help Google understand product pages, but markup alone does not force merchant recognition. The transaction path and the site's overall purpose must be consistent with a real online store.

Product snippets report

The Product snippets report covers Product structured data for enhanced text results that can include ratings, reviews, price, and availability.

It is the primary report for non-merchant product pages such as:

Editorial product reviews.
Aggregator pages focused on one product.
Product information pages where the site is not the seller.

At the Product level, current product-snippet requirements include name plus at least one of review, aggregateRating, or offers. Each nested item has its own requirements.

Use this report to find:

Missing required review, rating, or offer properties.
Invalid nested values.
Non-critical improvements.
Template regressions across editorial or aggregate product pages.

Merchant product pages with a specific Offer are mainly monitored through the Merchant listings report, which includes the relevant offer-based product-snippet checks.

Merchant listings report

The Merchant listings report covers purchasable product pages where the site is the seller. Merchant experiences can include shopping knowledge panels, popular product results, Google Images, and other shopping presentations.

Current minimum merchant-listing data includes:

Product.name.
Product.image.
A specific Product.offers value using Offer.
A positive active offer price.
Price currency.

The report can also surface issues with richer commerce data such as:

Availability and condition.
Product identity and global identifiers.
Shipping details.
Return policy.
Unit, sale, or member pricing.
Product variants.
Apparel and certification data.

An AggregateOffer does not replace the merchant's own Offer. Merchant listing eligibility requires that the represented merchant sells the product on the page.

How to read both rich-result reports

Both reports follow the rich-result report model:

Valid items have no detected critical issue for that feature.
Invalid items have a critical issue that prevents that item from being used for the feature.
Improve item appearance contains non-critical issues.
Issue pages contain representative examples and fix-validation status.

The unit is a structured-data item, not a page. One product page can contain multiple items or issues, and one template can generate thousands of affected items.

The reports are sampled and their example tables are not a complete inventory. Use URL Inspection for a specific indexed product page and maintain site-side product-data validation when complete coverage is required.

Valid markup establishes eligibility; it does not guarantee that Google displayed a shopping feature.

Why only one rich-result report may appear

Product snippets without Merchant listings

This is expected when the site publishes reviews or product information but does not sell the products directly.

It can also mean:

Purchasable product pages lack valid merchant offer data.
Merchant pages have not been indexed or recrawled.
Google's current report sample exposes only non-merchant product items.

Merchant listings without Product snippets

This can be normal for a store containing only purchasable product pages. Google's merchant report includes the product-snippet checks that apply to offer-based merchant pages.

Absence of a separate Product snippets report does not prove that a valid merchant product cannot appear as an enhanced text result.

Both reports

This is normal for a mixed site, such as a retailer with:

Purchasable product detail pages.
Editorial reviews or non-merchant buying guides.

Use each report for the matching page type. Do not make editorial pages look like merchant offers merely to consolidate reports.

Merchant opportunities report

Merchant opportunities provides recommendations for improving how an eligible online shop appears on Google.

If the site has no Merchant Center account, the report can invite the organization to sign up or finish registration. Sites managed through a platform such as Shopify can be directed to connect that platform's Merchant Center integration.

After a Merchant Center account is associated, opportunities can include:

Add shipping and return information.
Configure store ratings.
Add payment methods.

The report can show whether submitted information is pending, approved, or affected by an issue.

Treat each recommendation as a commerce-data task, not a ranking guarantee. Confirm that the information is accurate, applies to the intended countries and products, and matches the store before submitting it.

Interpret report combinations

Merchant opportunities appears, but rich-result reports do not

Google recognizes the site as an eligible merchant, but either:

It has not found supported product structured data.
The structured data is absent from the current Search Console sample.
Product pages are not indexed or accessible.
Markup is unparsable or has not been processed yet.

Test representative product pages with the Rich Results Test and URL Inspection.

Rich-result reports appear, but Merchant opportunities does not

Google found product structured data but does not currently recognize the property as an eligible physical-goods shop.

Check whether:

The site actually completes consumer purchases on-site.
It is an affiliate, aggregator, B2B-only, or lead-generation model.
Merchant product pages contain valid on-site offers.
The property represents the full merchant domain.
Recognition and recrawling need more time.

Do not manufacture merchant signals for a business that does not meet the definition.

Shopping is entirely absent

Check in this order:

Confirm the correct Search Console property.
Confirm important product pages are indexed.
Run the Rich Results Test on representative products.
Use URL Inspection to compare live and indexed product data.
Check access, rendering, noindex, canonical, and parser problems.
Verify that customers can actually purchase on the site when merchant eligibility is expected.
Allow time after a new implementation for crawling and report processing.

Associate Search Console with Merchant Center

An association lets Search Console use Merchant Center information to update commerce details, monitor products, and surface more opportunities.

Create the association from either:

Settings → Associations → Associate.
Merchant opportunities → Associate account.

Current permission and scope requirements are:

The person must be an owner of the Search Console property.
The same person must be an admin of the Merchant Center account.
The Search Console property must be domain-level; path-only properties are not supported for association.
A Merchant Center account scoped to a subpath can be associated when it shares the same domain.
One Search Console property can be associated with only one Merchant Center account.
Multiple Search Console properties can associate with the same Merchant Center account.

Association changes data governance

Google states that after association, all users with access to the Search Console property can view Merchant Center data and add or update information.

Before associating:

Audit Search Console owners, full users, and restricted users.
Confirm the Merchant Center account belongs to the intended business entity.
Document who can approve or remove the association.
Review agency and contractor access.
Decide which system owns shipping, returns, and product corrections.

An association should be treated as a cross-product permission change, not merely a reporting toggle.

Shipping and return settings in Search Console

Eligible merchants can manage a simplified policy set under Settings → Shopping → Shipping and returns.

Search Console can collect:

Delivery time.
Shipping cost.
Return window.
Return cost.

An owner or full user can manage these settings. A Merchant Center account is not required to configure policies through Search Console. If the organization already has a Merchant Center account, Google requires it to be associated with the Search Console property.

Add shipping policies

Shipping policies are configured by country. Search Console supports:

Minimum and maximum delivery days.
Flat-rate shipping.
Free shipping above a threshold.
Free shipping.
An “other” cost option.

The currency must match the policy country. Repeat the configuration for every applicable destination country.

Google documents shipping details as automatically approved.

Add return policies

Return policies are also configured by country and include:

A public return-policy URL.
A return window or no-returns policy.
Free returns, flat-rate cost, or a percentage of product price.

Merchant Center supports additional return conditions and restrictions beyond Search Console's simplified editor.

Return policies submitted in Search Console are manually verified. Google says verification can take about 10–13 days, during which the policy can remain pending.

Search Console does not mirror the Merchant Center editor

Policies created or edited in Merchant Center remain managed there and are not reproduced as editable Search Console policies. Search Console can show a link to recently changed Merchant Center policies for 30 days.

If policies are supplied through multiple methods—Search Console, Merchant Center, structured data, or product-level overrides—document the intended source and consult Google's current precedence rules. Do not assume the most recently edited interface always wins.

Shipping accuracy is an eligibility issue

Shipping costs submitted to Google must match the costs shown to shoppers on the website.

Google warns that a listing can be rejected when the listing presents a lower shipping cost than the customer encounters on the site. Validate:

Destination country and region.
Currency.
Free-shipping thresholds.
Product-level exceptions.
Handling and transit ranges.
Logged-out and mobile checkout behavior.

Review policies after carrier changes, promotions, international expansion, and platform migrations.

Choose a source of truth

Data	Recommended ownership question
Product identity, price, availability	Which commerce system publishes both page and feed values?
Product structured data	Which template converts governed product data into `Product` and `Offer` markup?
Merchant Center feed	Which team or integration updates product attributes and resolves disapprovals?
Account-level shipping and returns	Is Search Console, Merchant Center, or organization markup authoritative?
Product-specific exceptions	Which feed or product-level markup supplies the override?
Opportunity recommendations	Who approves changes that affect store-wide customer promises?

Avoid editing the same policy independently in several tools. The interface that is easiest to access is not necessarily the correct system of record.

Measure Shopping visibility in Performance

Structured-data reports measure eligibility and issues. The Performance report measures recorded Search appearances.

Use Performance → Search results → Search appearance and select:

Product snippets for enhanced product text results.
Merchant listings for other documented merchant shopping features.

Google documents MERCHANT_LISTINGS and PRODUCT_SNIPPETS as separate Search Analytics API values, with corresponding BigQuery fields in bulk export.

Keep the counting rules in mind:

Search appearance choices show only when the property recorded impressions for them.
A page can have more than one appearance in the same result set.
Appearance grouping changes the table to page aggregation while the chart remains property-aggregated.
A click filtered to an appearance is attributed to the URL, not proven to be on the enhanced element itself.

An increase in valid items does not guarantee more merchant impressions. Demand, rankings, country, device, query mix, feed state, and Google's feature selection also matter.

A practical merchant workflow

Initial setup

Verify a domain-level Search Console property.
Audit indexed product pages and their canonical URLs.
Implement accurate Product and Offer structured data.
Test representative products and variants.
Monitor Product snippets and Merchant listings reports.
Decide whether to create or associate Merchant Center.
Audit Search Console users before association.
Choose the owner for shipping and return policy data.
Complete applicable Merchant opportunities.
Establish Performance reporting for both shopping appearances.

Weekly checks

New critical product-data issues.
Sharp drops in valid merchant items.
Price, availability, or currency regressions.
Pending or rejected opportunities.
Merchant Center disapprovals and feed mismatches.
Shipping or return policy changes.

After a commerce release

Test:

In-stock and out-of-stock products.
Full-price, sale, and member-priced offers.
Single products and variants.
Each country and currency path.
Shipping thresholds and return exceptions.
Rendered structured data in production.

Fix the template or product-data source before starting Search Console validation.

Common mistakes

Treating every Shopping panel as one report

The rich-result reports, Merchant opportunities, and settings have separate eligibility and data. Diagnose the missing component rather than “the Shopping report.”

Associating the wrong Merchant Center account

The association exposes Merchant Center information and update capabilities to Search Console users. Confirm legal entity, domain, administrators, and account ID first.

Using a path property for association

Merchant Center association requires a domain-level Search Console property. A directory URL-prefix property cannot be used for this association.

Expecting Merchant Center policies to be editable in Search Console

Policies remain managed in the system where they were created. Search Console's simplified editor does not become a mirror of Merchant Center.

Clearing recommendations with inaccurate promises

Do not submit a shipping speed, free-return promise, payment method, or store-rating configuration that the business cannot support.

Confusing valid items with approved products

Search Console validates supported structured data. Merchant Center separately evaluates feeds, landing pages, policies, accounts, and program eligibility.

Expecting report totals to inventory the catalog

Rich-result reports are sampled and item-based. Use the commerce catalog, feed diagnostics, or a crawler for complete SKU and URL coverage.

Automation boundaries

Search Console's public API does not expose the Shopping rich-result reports, Merchant opportunities, account association, or shipping and return settings.

Automation can:

Test structured-data output in development.
Crawl product templates and compare visible and structured values.
Sample indexed product evidence through the URL Inspection API.
Query Product snippets and Merchant listings performance through Search Analytics.
Analyze bulk-export appearance fields in BigQuery.
Use Merchant Center APIs for appropriately authorized product-data workflows.

UI and human review remain necessary for:

Rich-result issue and example review.
Fix validation.
Merchant Center association.
Merchant opportunities.
Search Console shipping and return policy management.
Governance and policy accuracy decisions.

What Search Console can and cannot conclude

It can show:

Sampled product-item validity.
Critical and non-critical structured-data issues.
Recommendations for recognized eligible merchants.
Search Console-managed shipping and return policy status.
Recorded Product snippets and Merchant listings performance.

It cannot prove:

That every catalog product was checked.
That valid markup appeared in Search.
That a product is approved in Merchant Center.
That every feed and landing-page value matches.
That completing an opportunity improves ranking.
That a Merchant Center association is safe without an access review.
That a policy in one system overrides every other source.

Review checklist

The site's transaction model meets the merchant definition.
A domain-level property covers the full shop.
Product and merchant page types use the correct structured-data requirements.
Rich-result reports are interpreted as sampled item reports.
Merchant opportunities are treated separately from markup validity.
Association uses the intended Merchant Center account.
Search Console access is audited before association.
Shipping and returns have a documented source of truth.
Policy values match the site and checkout.
Pending return-policy verification is monitored.
Merchant Center and Search Console diagnostics are both reviewed.
Product snippets and Merchant listings performance are measured separately.