Show Sidebar

2026 UK CBD Product Page SEO Playbook: Schema Product Markup, Embedded COAs & ASA‑Compliant Descriptions

by Wylde Apothecary on 0 Comments

Introduction — why product pages matter in 2026

Product pages are your money pages. In 2026, search engines and AI systems increasingly rely on machine-readable signals to select, summarise and surface ecommerce content. According to the Structured Data SEO 2026 guide, pages with properly implemented structured data earn around 35% higher click‑through rates from rich results. For UK CBD retailers that means a direct lift in discoverability — provided you implement markup correctly and remain ASA‑compliant in your copy.

Key concepts

1. Use Schema.org Product (v30.0) correctly

Schema.org Product remains the commerce standard and received a significant update in 2026 (v30.0). At minimum your Product JSON‑LD should declare core fields:

  • name — product title;
  • image — at least one high‑resolution image with descriptive alt text;
  • offers — include price, priceCurrency (use ISO 4217, e.g. "GBP"), and availability using the full schema.org URL (for example https://schema.org/InStock) to avoid validation errors.

Other high‑ROI fields: offers.priceValidUntil, hasMerchantReturnPolicy, sku/mpn and clearly modelled variants with canonical handling.

2. Embed batch COAs and make them machine‑readable

Transparency is now a ranking and trust signal. Embed a visible, downloadable Certificate of Analysis (COA) for each batch on the product page and reference it from your schema. Use additionalProperty (PropertyValue) to expose batch number and COA URL to machines — for example a PropertyValue named "batch" and one named "COA" that contains the PDF URL. Keep PDFs reachable by robots and users alike, and add an accessible caption and clear file metadata (date, lab). Search engines and AI Overviews increasingly prefer pages that link to primary evidence.

3. Collect real reviews and mark up AggregateRating correctly

AggregateRating can surface star snippets in SERPs, but rich result engines typically require a real reviewCount (≥ 1) and genuine reviews. Mark up both AggregateRating and individual Review objects (with dates and author fields). Ethically solicit verified reviews and display them on the product page so the markup reflects reality.

Details — practical implementation checklist

Technical: JSON‑LD essentials

Include a concise JSON‑LD block in the head (or just before

0 Comments

Leave a comment

All blog comments are checked prior to publishing

Free UK Shipping over £35
Free In-store Returns
All Products Third Party Tested
Secure Shopping Guarantee
Cart cart 0
You have successfully subscribed!