Structured schema suite

The Generators sub-tab on SEO Tools → Content houses six schema builders covering the highest-leverage Google rich-result categories for ecommerce:

Common apply path

Every generator ships with an "Or: inject directly via theme block" panel under the script-tag output. Enter the product or article handle, click Inject:

1. Schema written to rankengine.{kind}_schema metafield on the resource via productUpdate GraphQL mutation
2. The matching "RankEngine {Kind} Schema" theme block (enable once in your theme customizer) reads the metafield and emits the JSON-LD <script> tag on the storefront

After the first-time theme enable, every future inject just updates the metafield — no theme changes needed.

Schema injection audit

Bottom of the Generators sub-tab. Shows:

• Catalog schema coverage (0-100 score + breakdown — phase 672)
• Richness (avg schemas per covered resource — phase 673)
• Target richness (weighted by your resource mix — phase 674)
• Ship next chips (uncovered samples — phase 675)
• Per-resource lookup (handle → applied + recommended kinds)
• Total schema applies + Unique resources covered (top stats)
• Counts table: each kind broken down by Products vs Articles
• Recent applies (last 30 days, top 20)

How the metrics read together

The 4 metrics layer to answer different questions:

Example: score 47/100, richness 1.4, target 2.3 → you've covered roughly half your catalog and most covered resources only have one schema kind. The "Ship next" chips below show specific products + articles to start on. Click a chip to pull it into the lookup form — you'll see the recommended schema kinds for that specific resource.

Apply-log semantics

Reflects the local apply log (schema_apply_log table) not a Shopify GraphQL re-fetch. Cost trade-off: per-resource GraphQL on page load would be expensive at scale. Merchants who delete a metafield directly in Shopify Admin would see stale audit; the next inject corrects it.

Google Rich Results Test handoff (phases 713-716)

Every generator's script-tag output panel has an Open in GRT button next to Copy. One click:

1. Wraps the JSON in <script type="application/ld+json"> if not already
2. Copies it to your clipboard
3. Opens search.google.com/test/rich-results in a new tab

GRT's Code-snippet tab is where you paste. Lets you cross-check against Google's own validator before publishing — useful for catching edge cases (e.g. unusual Recipe fields) our local validator's heuristics don't cover.

The same button appears in SchemaValidator (Audit sub-tab) and per-block on CompetitorSchemaSpy results, so you can also validate competitor schemas in GRT without retyping them.

When to ship which schema

Visible-content rule

For every schema type, Google requires the structured data to MATCH visible page content. A FAQPage schema without visible Q&A on the page will get the rich result revoked. The generators don't enforce this — they only emit the markup. The merchant is responsible for ensuring the visible content matches.

Plan

• Free: Author, Video, Event (pure form builders, no AI cost)
• Growth+: FAQ, HowTo, Recipe (AI-generated content via RankEngine AI)
• Apply path (inject button + theme block): Growth+

Pairs with

• Spy + Compare tools (Spy & Compare sub-tab) — see what schemas competitors run; the high-leverage queue links directly to the matching generator
• Schema injection audit (this sub-tab, bottom) — track what you've shipped over time