Free practical checklist

Compare what the product page says with the facts a shopping system needs

A public page cannot reveal a private feed or Merchant Center account. It can still show whether product identity, selected options, price, availability, delivery wording, and visible markup tell a consistent buyer-facing story.

This is an outside-view check. It does not diagnose private Shopify, feed, inventory, fulfilment, or Merchant Center settings.

01

Identity

The product title, variant name, URL, and image should describe the same item a buyer can select.

  • Record the exact URL, selected option, visible wording, and review date.
  • Separate what is directly observable from what would require admin or feed access.
02

Offer

Price and sale-price wording should remain understandable after a buyer changes a size, finish, pack, or configuration.

  • Record the exact URL, selected option, visible wording, and review date.
  • Separate what is directly observable from what would require admin or feed access.
03

Availability

The visible state should belong to the selected option. A general in-stock message should not imply that every option is available.

  • Record the exact URL, selected option, visible wording, and review date.
  • Separate what is directly observable from what would require admin or feed access.
04

Delivery

Processing, dispatch, transit, and delivery language should be distinguishable and should not contradict the returns or shipping policy.

  • Record the exact URL, selected option, visible wording, and review date.
  • Separate what is directly observable from what would require admin or feed access.
05

Markup

Visible product facts and public Product or Offer markup should not present obviously different identity, price, or availability signals.

  • Record the exact URL, selected option, visible wording, and review date.
  • Separate what is directly observable from what would require admin or feed access.

A shareable evidence record

Write down the buyer-facing fact before diagnosing the system

When a product page looks inconsistent, capture the public evidence first. This keeps a useful observation from turning into an unsupported claim about a private feed, inventory rule, or Merchant Center account.

Five fields are enough to start

  • Public product URL and review date
  • Selected option or variant state
  • Exact visible wording for price, availability, or delivery
  • What a buyer could reasonably misunderstand
  • The private check still required before implementation

Use the same record on two or three comparable products before deciding that a catalogue-wide change is needed.

Turn an observation into action

Fix the source pattern before rewriting the catalogue

If the same identity, availability, or delivery ambiguity appears across comparable products, document the recurring pattern first. A small representative sample is more useful than an unbounded score.

What a focused review adds

  • Public evidence tied to representative product URLs.
  • A clear boundary around what remains unknown.
  • A short fix sequence for Shopify, SEO, feed, or CRO teams to assess.

Common questions

Keep public evidence separate from private diagnosis

Use the page to document what a buyer and a crawler can see, then confirm the implementation details in the merchant's own systems.

Can a public product page prove a Merchant Center error?

No. It can document visible product, price, availability, and markup signals, but Merchant Center and feed diagnostics require private access.

What should change when a buyer selects another variant?

The selected option, price, availability, URL, image, and relevant Product or Offer details should continue to describe the same purchasable item.

Should I replace Shopify's structured data after one mismatch?

No. Compare more than one option and product first, then check the theme, apps, inventory, feed, and search-engine context before changing implementation.