Merchant listings vs product snippets: fix the right report
Read the conclusion first
Choose product markup for the page's actual purchase or editorial task, then reconcile the same item across visible content, structured data and any Merchant Center source. Product-snippet validity, merchant-listing eligibility and feed approval are separate states; none proves exposure or sales.
Applicable conditions
Applies to purchase pages with real product information and related product content. Without transaction or factual evidence, don't fabricate price and stock.
Before you open the report
One exact SKU/variant, target country and currency, its landing page, Product markup and submitted feed row.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Identify the item and the applicable feature
Record the exact product or variant, URL and whether users can purchase it from this page. Review product snippets for the applicable product content and merchant listings for purchase pages; their requirements overlap but are not identical. Do not use a product template for an ordinary service article.
Preserve stable identifiers and the selected variant. A family page's starting price and a specific variant's offer are not automatically the same fact. Record country and currency when comparing prices so an apparent mismatch is not merely a different offer context.
Reconcile authoritative fields before filling errors
Build a row for each relevant value: product/variant ID, name, price, currency, availability and genuine shipping/return conditions. Compare the page, extracted JSON-LD and Merchant Center's applicable processed item at the same time. Keep unknown or unsupported fields explicit.
Find which source produced the wrong value and fix its mapping or synchronization. A fabricated GTIN, price, stock status or review is not a solution to a validation error. Verify the selected item through the actual purchase flow when the page offers purchasing.
Verify the correct report and the live offer
Read product-snippet and merchant-listing errors separately in native GSC, then test the repaired public page. Check that extracted fields match visible facts and the intended variant. For feed issues, verify Merchant Center's processed source and destination status independently.
Record the release, retest, report processing and any actual appearance. Promotions ending or stock changing need durable source updates, not one manual patch. AISEO Site does not currently read feeds or orders; search clicks cannot establish approval, checkout consistency or sales.
Common mistake: Treat GSC product report as feed diagnosis
Merchant Center review and feed failures need to be checked in the corresponding system.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| Stock conflicts with body content | Check the real product source | Body content, markup, and feed consistent |
| GSC valid but feed rejected | Go back to Merchant Center to check the cause | Record the two systems separately |
| Ordinary article mistakenly marked as product | Change to the actually applicable type | Don't fabricate offers |
The page, markup and product feed disagree
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Teaching example: the same variant costs $79 on the page and in the cart, but JSON-LD and the feed still say $99.
- What it establishes
- Compare the same offer before identifying a mismatch. Different variants, currencies or scheduled sale periods can create a false discrepancy.
- What to do next
- Find the price source and update its downstream outputs together. Check the actual submitted item and destination in Merchant Center as well as GSC’s supported product report.
What counts as a checked result
Open the final item link through purchase selection and compare visible price, markup and feed. Item approval and actual impressions remain separate.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A variant-specific offer comparison and separately checked enhancement/feed states.
- Stop and resolve this first
- Do not compare different currencies, countries or variants as one offer.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Can AISEO Site read orders and feeds?
Not currently; search clicks are not orders either.
Can item approval replace a variant-to-cart check?
No. Open the submitted URL, select the intended variant and verify its actual purchasable price and availability. Approval does not prove that this customer journey is correct.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Inspect your Product JSON-LD syntax here, then reconcile price and availability with the page and the relevant Google product report.
See how it works →