Structured data check (schema)

Day 17: Structured data check (schema)

Focus: Structured data helps machines parse facts. Your goal is correctness, not cleverness.

What you will achieve today

• Understand what schema is used for product pages.
• Check for obvious structured data errors.
• Fix one issue or plan the fix.

Deliverables

• A structured data check result for one product and one collection page.
• One fix applied or a ticket created.

Step-by-step

1. Use a schema testing tool you trust and run it on a hero product URL.
2. Check the basics: name, brand, offers, availability, priceCurrency, GTIN (if available).
3. Look for errors and warnings that affect offers and identity.
4. Check a collection page: breadcrumb and collection metadata.
5. Fix what you can via theme or app settings, or document the required change.

Checklist

• Offers show correct price and currency.
• Availability matches actual stock behaviour.
• Brand and identifiers are not missing when you have them.

Examples

Schema impact

• Good: Offer includes priceCurrency and availability
• Bad: Offer is missing currency or shows wrong availability

Common mistakes

• Adding schema by hand without understanding, causing inconsistencies.
• Ignoring offer errors because 'warnings are fine'.

Done when

• You know whether schema is currently helping or hurting.
• You have one concrete fix executed or scheduled.

Next: Tomorrow you will handle prices, offers, and reviews safely.