Skip to content

Skill · E-commerce SEO Team

Product Schema Markup

Validate and generate Product schema against Google's actual required and recommended fields, plus UCP readiness.

What it is

Validate and generate Product schema against Google's actual required and recommended fields, plus UCP readiness.

A skill is a written procedure an agent loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.

File
SKILL.md
Length
26 lines · 2 min read
Category
Marketing
License
MIT
Author
Brainwrite
Words
366

Paste it into any agent’s instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add the team to Brainwrite and it arrives switched on.

Use it

Use this skill in Brainwrite.

  1. 1

    Add the E-commerce SEO Team

    Its agents carry this skill. You preview every agent and skill first; skills arrive switched on and routines paused.

    Install in Brainwrite →
  2. 2

    Brief your Chief of Staff

    “Use the Product Schema Markup skill for this: [describe the job]. Show me the plan first, and send, post or change nothing.”

  3. 3

    Approve what matters

    The agent follows the skill and brings the result back. Anything that sends, posts or changes data waits for your approval in Ask mode.

    How approvals work →

Use this when

product schema, product json-ld, merchant schema, shopping schema.

Process

Google's actual confirmed required properties for Product/Merchant listings are just three: name, image, and offers — and offers must be an Offer, never AggregateOffer, for a merchant listing. Everything else is recommended, not required; don't overstate the requirement bar.

Recommended properties, roughly in order of scoring impact: sku, description, brand, offers.seller, global trade identifiers (gtin13/gtin14/mpn), aggregateRating (star rating + review count), at least one individual review, variant attributes (color/material/size), shippingDetails as a ShippingDetails object with rate and delivery time, hasMerchantReturnPolicy as a MerchantReturnPolicy with type and days, and category (accepts plain text, a CategoryCode, or an array mixing both).

For adult-oriented products specifically, hasAdultConsideration is required (added 2026-05-20), and Google Search supports only the value https://schema.org/SexualContentConsideration — flag its absence on any product that needs it as a compliance gap, not just a scoring one.

Validation rules to enforce: price is a bare number string, never prefixed with a currency symbol; availability uses the full Schema.org URL enum; image is an array with at least one high-resolution URL; priceCurrency is a real ISO 4217 code; if brand is present, brand.name must be a real value, never empty or "N/A"; sale periods use validFrom plus validThrough or priceValidUntil in ISO 8601; if aggregateRating is present, both ratingValue and reviewCount are required; never mark up a fake or undisclosed incentivized review.

Scoring ladder for completeness: all required fields alone = 50/100; + aggregateRating = 65; + sku/gtin/mpn = 75; + shippingDetails = 85; + merchantReturnPolicy = 90; + 3 or more real reviews = 100.

Separately, note Universal Commerce Protocol (UCP) readiness as an emerging, optional signal: a merchant with clean Product schema can declare a UCP profile at /.well-known/ucp listing checkout/fulfillment/discount capabilities for AI shopping agents. This is genuinely live infrastructure (Google, Shopify, Etsy, Wayfair, Target, Walmart), but broad adoption is still early — report its absence as an opportunity, not a defect, and never claim to have probed the live endpoint (that needs the source project's own script, not something this team can run).

Output the complete JSON-LD block plus the completeness score and what would move it to the next tier.

Put this skill to work.

Download Brainwrite, add the team that carries it, and tell your Chief of Staff what needs doing.

macOS today. Windows and Linux are coming soon.