Cannabis product schema

Product schema tells search engines that a specific page describes an item for sale. For cannabis, this means strain names, product types, THC/CBD content, effects, and pricing. When implemented correctly, your strains appear in Google Images, voice search results, and rich snippet panels that show price, rating, and availability.

Product schema is structured data that identifies a cannabis strain or product, including its name, image, rating, price, and availability status. This markup makes pages eligible for rich snippets in results, which can improve click-through rates and establish product authority for individual strain pages competing against wholesale marketplaces.

Cannabis presents a schema challenge because product types vary dramatically. A strain is fundamentally different from a concentrate, which differs from an edible. Your product schema should include the productType property to differentiate.

For strains, include cannabinoid content (THC percentage, CBD percentage) in the description. Use the offers property to show per-gram pricing, eighth pricing, and quarter pricing if applicable. Include aggregateRating if you have customer reviews.

For concentrates, specify the format (shatter, wax, distillate, live resin) in the productType. Include potency information. For edibles, specify serving size, mg per serving, and total mg in the offers property.

The description property should be a short summary capturing the strain's lineage, primary effects, and flavor profile. Keep it concise, since search results truncate long descriptions.

Cannabis product schema must differentiate between strain types, concentrates, and edibles using the productType property. Each product category requires specific properties (cannabinoid percentages for flowers, serving sizes for edibles, potency for concentrates) to ensure accurate rich snippet display and user expectations alignment.

If you aggregate reviews from multiple sources, your aggregateRating property consolidates those into one schema rating. This rating property can show in rich snippets and influence click-through rates.

Include ratingCount to show how many reviews you've collected. Review volume is a trust signal alongside the rating itself, so a high rating built on very few reviews is weaker evidence than the same rating built on many.

Include ratingValue (the decimal rating) and bestRating (5 for a 5-star scale). Worst rating is always 1. These three properties together complete the rating assertion.

If you're using Headset inventory management, Product schema should pull inventory status from your live feed. Out-of-stock products still carry value in search results, but availability status must be accurate. Customers checking search results expect to find what you claim is in stock.

Springbig integration can feed customer reviews directly into your aggregateRating, creating a dynamic rating that updates as customers rate products through your loyalty program. This keeps your schema fresh without manual updates.

Create custom properties for terpene profiles and effects. Most e-commerce schema doesn't support cannabis-specific attributes, so you'll use additionalProperty to define these.

Example: additionalProperty.name = "Primary Terpenes", additionalProperty.value = "Limonene, Myrcene, Pinene". This adds context that Google might use in voice search results or featured snippets.

For effects, do the same: additionalProperty.name = "Effects", additionalProperty.value = "Relaxing, Creative, Evening". These attributes help users scanning results understand whether the strain fits their occasion. Health and effect claims are restricted in most state cannabis advertising rules. Use experience and occasion terms only, never a symptom or condition.

The measurement property helps define product weight and potency. Use this for eighth (3.5g), quarter (7g), ounce (28g) measurements standard to cannabis retail.

For concentrates, measurement might be grams or percentage potency. Include units explicitly: "28 grams", "1000 mg", "85% THC". This eliminates ambiguity in search results and voice assistant responses.

Your product schema cannot make unsubstantiated medical claims. Never claim a strain "cures anxiety" or "treats PTSD" in schema markup. You can describe effects ("uplifting", "relaxing") but not therapeutic claims.

Third-party testing information belongs in the description, but lab test results shouldn't be embedded in schema properties. Link to testing documentation without making claims schema markup.

Pricing must be current. Don't use outdated pricing in schema; Google detects pricing inconsistencies between schema and actual page content. Update product schema whenever your menu pricing changes.

For limited drops or pre-order strains, set availability to preOrder. Include releaseDate property showing when the product becomes available. Include inventoryLevel property showing pre-order quantities if applicable.

This helps customers understand timing without visiting your site. Voice assistants can announce, "This strain is available for pre-order, releasing March 15."

Use Google's Rich Results Test to validate product schema before publishing. The test shows exactly what Google extracts, including how your rich snippet will display. Test after each price change or availability update.

Every product schema should reference your Business schema through the seller property. This links individual products back to your dispensary entity, strengthening the relationship between business and product authority.

Use the same business name in seller property as appears in your Business schema's name property. Exact matching ensures Google recognizes the connection.

---

• Back to Schema Markup Optimization Hub
• Business Schema for Cannabis
• Price Schema and E-Commerce for Cannabis