Schema Tool
Additional schema generator
Turn a client's product/variant metafields into a ready-to-review blink-schema-additional.liquid file. Describe the site once, list the metafields you want to expose, and Claude decides how each one should be represented in JSON-LD.
blink-schema-snippet.liquid's variant loop rather than left as-is.
Site context
One field to describe what the store sells and who for - used to judge ambiguous metafields sensibly.
Metafield list
Add as many product or variant metafields as you like, each with its own namespace.key and a short context note.
AI mapping decisions
Claude decides whether each metafield maps to a native schema.org Product property (colour, size, material, category, audience, GTIN and similar) or a generic additionalProperty entry, and explains why - flagging which fields are recognised by Google Merchant Center along the way.
Liquid code, ready to review
Generates a complete file following the same defensive conventions as existing Blink schema-additional files, then lets you copy or download it - with an optional one-click toggle to strip out all the explanatory comments before you paste it in.
Saved sites
Save the site context and metafield list under a name and reload it later - useful for flipping between several clients without re-entering everything each time.
Add your Anthropic API key
Open settings (gear icon) and paste an Anthropic API key. It's saved only in this browser's local storage and used to call Claude directly from the browser.
Describe the site (or load a saved one)
Fill in the site context field - e.g. "premium dog food, sold direct-to-consumer in the UK". This is passed to Claude alongside every metafield so it can judge ambiguous cases. If you've worked on this site before, pick it from Saved sites at the top and click Load instead of starting from scratch - handy for moving between several clients.
Add each metafield
Click Add metafield for each product or variant metafield you want to expose, and fill in:
- Metafield - the namespace.key, e.g.
blink.packet_size - Scope - whether it lives on the product or the variant
- Type - the field's real Shopify metafield type (single line text, boolean, colour, metaobject reference, and so on)
- Shape - single value or list, matching how the metafield is actually configured in Shopify
- Context - what it means and what values it holds, e.g. "size of a packaging"
Type and shape are passed straight through as the field's confirmed Shopify type, so Claude generates correctly-shaped Liquid instead of guessing whether a value might be a list.
Generate and review
Click Generate schema code. Review the mapping decisions table - each metafield is tagged as a native property, an additional property, or needing a manual merge - then copy or download the Liquid file. Tick Remove comments above the code box first if you want a clean file without the explanatory comments.
Save the site for next time
Back on the setup screen, click Save current as… and give it a name (e.g. the client's name) to store the site context and metafield list for later. Saved sites persist in this browser until you delete them, separately from whatever you're currently working on.
Create a key at console.anthropic.com → API Keys and paste it into this tool's settings panel. It's used to call Claude directly from your browser and never leaves this browser's local storage — but it is visible in your browser's network requests, so only use a key you're comfortable having in a client-side tool.
Generate button stays disabled
You need a site context and at least one metafield with a namespace.key filled in before the button enables.
"Generation failed" error
Check an Anthropic API key is set in settings and still valid - the request is a direct browser call to the Anthropic API, so an invalid or rate-limited key surfaces as an error message.
Draft was cut off
If you get a "hit the token limit" error, you've likely listed a lot of metafields in one go - split them into two smaller runs and merge the resulting files by hand.