- ctr, dati strutturati, e-commerce, google, ifg ecommerce, ottimizzazione, pmi, rich snippet, schema.org, seo, shopify
- Francesco Guiducci
Shopify Structured Data: Schema.org, Rich Results and JSON-LD Without Duplicates
Direct answer: structured data helps search engines and other systems interpret products, offers, organizations, breadcrumbs and articles explicitly. It does not guarantee rankings, rich results, clicks or AI citations. On Shopify, the first rule is to inspect what the theme or apps already generate and keep one coherent graph for each entity, without invented reviews or duplicate Product, Organization or FAQPage markup.
Before adding Schema.org: inspect what already exists
I do not assume Shopify automatically produces the same markup on every store: output depends on the theme and installed apps. I first read the page source and identify every JSON-LD block already rendered. If two sources describe the same product or organization with different data, the priority is consolidation, not adding a third script.
Product and Offer
For a product page, markup should reflect data that is actually visible and purchasable: name, URL, images, SKU or other available identifiers, price, currency and availability. Reviews and aggregateRating should be declared only when they genuinely exist and meet the relevant search-engine guidelines. I do not add demonstration values to the live site.
Organization and Person
For a professional business I keep name, URL, external profiles and the relationship between person and brand coherent. In my case, the entity should make it clear that Francesco Guiducci is the freelance professional behind IFG eCommerce, without turning markup into a list of promotional claims.
BreadcrumbList and Article
Breadcrumbs and articles can be described with structured data when they match the real page structure. Article markup should use the actual title, author, dates and image; I do not add a second bio or second author just to inflate semantic signals.
FAQPage: do not use it as a shortcut
The fact that a page contains FAQs does not mean it must necessarily output another FAQPage script. I check current Google guidelines first and, above all, avoid duplicate graphs generated simultaneously by the theme, apps and metafields. Questions still need to be visible to users: no hidden FAQs built only for crawlers.
How I validate the implementation
- Inspect rendered HTML and count the JSON-LD graphs actually present.
- Verify that values match visible content.
- Use Schema Markup Validator for syntax and Google Rich Results Test when the type is supported.
- Check Search Console for errors and eligibility without treating the absence of a rich result as proof of a schema error.
- Re-test product, collection, article and home after each change.
Structured data and GEO
Schema.org can make some information more explicit, but there is no markup that can force ChatGPT, Gemini, Claude, Perplexity or Google to select a site. In my GEO Protocol, schema is one technical control alongside crawlability, entities, visible content and data quality.
If you want to review your store, these checks are included in my Shopify audit and technical GEO optimization.
Updated September 3, 2026.
