Shopify product schema and SEO: the fields Shopify leaves out

What your theme is probably emitting

Most Shopify themes output a JSON-LD Product block on product pages. Typically it carries name, description, image, sku, an Offer with price and availability, and — if a review app is installed and configured — an aggregateRating.

That is enough to be eligible for a product rich result, and it is where most stores stop. The fields commonly missing are the ones that decide how the result actually looks:

• brand — omitted or set to the shop name on every product, including ones you did not make.
• gtin / mpn — the identifiers Google uses to match your product to the same product elsewhere. Missing these makes you harder to place in shopping surfaces.
• priceValidUntil — an Offer without it can be treated as stale.
• shippingDetails and hasMerchantReturnPolicy — these can surface delivery and returns information directly in the result, and most stores have neither.
• itemCondition — assumed new, but worth stating if you sell refurbished or second-hand.
• Per-variant offers — a product with five variants at different prices should emit an AggregateOffer or multiple Offers, not one price pretending to be all of them.

The duplicate schema problem

A very common finding: two Product blocks on the same page. One from the theme, one from a review or SEO app, disagreeing about the rating or the price. Google picks one, and you do not get to choose which.

• Decide which source owns the Product entity and turn the other off. Most review apps have a setting for exactly this.
• If an app must add the rating, have it merge into the theme's block rather than emit its own.
• Re-test after every app install. This breaks silently, and nothing in your admin will tell you.

The same applies to aggregateRating specifically: only mark up ratings that are real and visible on the page. Structured data describing reviews a visitor cannot see is a manual-action risk, and Google has been increasingly direct about self-serving markup.

The URL problems Shopify creates for you

Shopify generates several URLs for the same product by design. Most stores never notice, because the canonical tags mostly hold — but "mostly" is doing real work in that sentence.

The tag pages are the one worth checking today. A store with a few hundred products can generate several thousand tag URLs, most with one or two products on them, and that volume of thin pages is a real drag on how the rest of the site is crawled.

Structured data beyond Product

• BreadcrumbList on product and collection pages — cheap, well supported, and changes how the URL is displayed in results.
• FAQPage where you have genuine questions and answers rendered on the page. Rich result eligibility is narrower than it was, but it remains a strong signal of what the page answers.
• Organization on the homepage, with a stable @id other blocks reference. This is what ties your brand together across the site.
• Article on blog posts and guides, with real datePublished and dateModified. Invented freshness dates are treated the same way as invented ratings.

Do not mark up things that are not on the page. Structured data describes visible content — the moment it starts describing content only crawlers see, it is a violation rather than an optimisation.

AEO and GEO: the same work, one step further

Answer Engine Optimisation and Generative Engine Optimisation are the current names for being cited by AI assistants and AI search results rather than only ranking in a list of links. In practice the work overlaps almost entirely with good technical SEO, with a different emphasis.

• Unambiguous facts. A model quoting your product needs the material, the dimensions, the shipping origin and the returns window stated plainly — in the page text, not only in an image or a spec PDF.
• Answer the question in the first paragraph. Content that buries the answer under four hundred words of preamble is skipped in favour of content that does not.
• Structured data as the machine-readable copy of the same facts, agreeing with what the page says.
• Be citable. A page with a clear author, a real update date and specific claims is a safer citation than an anonymous one, and the systems doing the citing behave accordingly.

None of this is a separate project. A store with correct product schema, honest reviews, clean URLs and pages that answer questions directly is already most of the way there.

Frequently asked questions