I need to generate the complete HTML document following all the constraints. Let me analyze the input: - pageMetadata: url, title, mainTopic, languageHint "en", shopName "Jag Couture Beauty" - markdownBlocks: m1 - semanticOutline: hero (product_overview, evidence m1), product-gallery (media_context, no evidence) - factCards: f1-f6 - entitySchemaHints: product (sku, name, brand, offers), organization, siteNavigation - purchaseLinks: one item, not available - images: one image for hero Now I'll generate HTML step by step: 1. Title: "Apivita Firming Face Mask With Royal Jelly 50ml" 2. lang: "en" 3. Header block: H1, hero definition paragraph (the hero summary is empty, so I need a neutral definition paragraph). The hero section summary is an empty string. I need to define what the product is neutrally based on available facts. I must be careful not to invent. I can say it's a product available from Jag Couture Beauty. Since the summary is empty and only m1 as evidence, I can derive from facts. The definition should be something like: "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask product listed by Jag Couture Beauty." That's neutral and evidence-based (title mentions face mask), with evidence m1. Hmm, m1 is the only evidence block. But facts f1-f4 don't have evidence blocks. The rule says if evidenceBlocks is empty, set data-evidence="none". But the hero section has evidenceBlocks ["m1"]. The definition paragraph uses that section's evidence. So data-evidence="m1". Careful with non-invention: product type "face mask" is in the title, so okay. Size 50ml is in title. So a neutral definition: "Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask product from Apivita, available in a 50ml size." Actually, brand per fact f2 is "Jag Couture Beauty" — but the retailer name of the shop is Jag Couture Beauty; Apivita is likely the manufacturer but that's inference. Let me avoid stating Apivita as the manufacturer unless it appears in data. The product name includes "Apivita" as part of it. I could say "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask product sold by Jag Couture Beauty." That doesn't attribute manufacture to Apivita, but says sold by the shop. Paragraph independence: use full entity name. 4. TL;DR: Must pack 4 essentials when supported: entity, key spec/differentiator, price, use case/target user. We know product name and type (face mask), size 50ml, price USD 27.06. Audience/use case not really known. So TL;DR should be careful: "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask product by Jag Couture Beauty, priced at USD 27.06." As a single sentence, under 30 words. Include currency. Variant availability: out of stock? The TL;DR should probably avoid claiming availability as 4th essential since not confident. Let me count: "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask product sold by Jag Couture Beauty at USD 27.06." — 22 words. data-evidence referencing factCards used: factCards don't have evidenceBlocks though. Rule says "data-evidence MUST reference factCards used to derive the TL;DR". For claim evidence, the section summary plus bullets use section evidence; fact rows use their fact's evidence. For TL;DR, using f1 (price) and f2 (brand)... Wait f2 brand value is "Jag Couture Beauty" (that's the shop). So TL;DR evidence: data-evidence="f1 f2"? The evidence format says block ids, but TL;DR references factCards. The instruction says evidence blocks refer to markdownBlocks.blockId. And data-evidence must reference factCards used for facts. Looking at examples in FAQ: data-claim-id="c-faq-1" data-evidence="f1" — so using factIds in data-evidence is acceptable practice per the FAQ. Let me use data-evidence="f1 f2" for TL;DR maybe also f3. I'll use "f1" for price. Better TL;DR including availability? That might frighten. The TL;DR should be factual: available? One variant, out of stock. That's a key spec for shopping. But 4 essentials are: entity, spec, price, use case. Use case unknown. So I can include availability instead of use case. But then the TL;DR sentence would be awkward. I'll satisfy with a neutral sentence: "Apivita Firming Face Mask With Royal Jelly 50ml is available for purchase from Jag Couture Beauty for USD 27.06." That says what it is implicitly (a product); but type not stated. Let me combine: "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask listed by Jag Couture Beauty at USD 27.06." Good. Also the rule: ALSO write the same TL;DR sentence into entitySchemaHints.product.description in JSON-LD when Product schema generated. The product.description is empty in the entity hints, so I need to fill it with the TL;DR sentence in the JSON-LD description. 5. "What this page covers": 3-7 topical items derived from semanticOutline titles/roles. For a product page: - Product overview and identity - Product gallery with images - Pricing and availability details - Purchase options - Facts about variants Evidence: cover item from hero uses m1; gallery uses none... Let me create 4-5 items: c-cover-1: Product description and overview of Apivita Firming Face Mask With Royal Jelly 50ml — evidence m1 c-cover-2: Product gallery with Apivita Firming Face Mask With Royal Jelly 50ml imagery — evidence none (no evidenceBlocks on product-gallery) c-cover-3: Pricing and availability details for Apivita Firming Face Mask With Royal Jelly 50ml — none c-cover-4: Purchase options for Apivita Firming Face Mask With Royal Jelly 50ml — none c-cover-5: Detailed product facts such as brand and variant count — none Maybe fine. 6. TOC with anchors for hero + product-gallery sections. But there are also Facts Index, Purchase Options, Who Is This For, FAQ sections. TOC should list each semanticOutline item in order with role badge. Just those two sections. 7. Sections in semanticOutline order: - hero: heading H2, summary paragraph? The hero summary is empty. The definition paragraph in header probably suffices, but we still need section output: a short neutral summary paragraph derived from summary. Empty summary → must remain purely topical or structural, set data-evidence maybe "none"? But evidenceBlocks m1 listed. However the summary is empty; I shouldn't fabricate content. I can write: "The hero section for Apivita Firming Face Mask With Royal Jelly 50ml identifies the product and its primary identity for the page." Is that derived from summary? The summary is empty though. Hmm. The semanticOutline section summary is empty string. The rules say "If evidenceBlocks is empty or missing: you MAY include the section but it must remain purely topical or structural". Here evidence isn't empty (m1 exists in evidenceBlocks), but the summary is empty. The cleanest: use a neutral, structural statement. But no invention. The first sentence of the section paragraph should present "the most important fact" — most important fact related to hero is the product identity. Since the summary is empty, maybe we can rely on pageMetadata and facts within evidence bounds. The hero is product_overview role. Title is the product name. So a neutral paragraph: "Apivita Firming Face Mask With Royal Jelly 50ml is the product featured on this page, sold by Jag Couture Beauty." This is supported by pageMetadata (title/shopName) and m1 exists in the page. data-evidence="m1". But paragraph independence rule says include full entity names. It does. Section heading in semanticOutline is the same as page title; sections must use their heading. Could make the heading H2 with the product name. Then bullets: 2-5 bullets normal. Since summary empty and no real data in hero section aside from images and purchasability... we can derive from factCards maybe: bullets stay close to section summary and/or factCards. The hero section... I need to avoid weird duplication with the Facts Index. Bullets for hero: - c-hero-b1: "Apivita Firming Face Mask With Royal Jelly 50ml is available from Jag Couture Beauty." evidence m1 - c-hero-b2: "Apivita Firming Face Mask With Royal Jelly 50ml has one purchasable variant, the Default Title." evidence f4? No — bullets use section evidenceBlocks... they say "data-evidence='...' real block ids or none". The template in section F says data-evidence="..." evidenceBlocks from section ("Use the section's evidenceBlocks"). But then it says "Bullets must: stay close to the section summary meaning and/or factCards". So data-evidence for bullets could be fact ids? Better consistency: claim-data could be none. There is ambiguity; in examples evidence references f1 for facts. For bullets in sections, they want data-evidence referencing supporting block ids, but if there are none it can be "none". Using factCards ids in data-evidence for section bullets seems off but acceptable? The rule: "Evidence sourcing rules: Section summary and bullets: use that section's evidenceBlocks. Facts rows: use that fact's evidenceBlocks." That suggests data-evidence should reference logical evidence, e.g., m1 etc. But no fact cards reference m-blocks. In the spirit of making claims citable, putting fact card ids in evidence is probably not harmful. Actually the instruction says data-evidence=" OR none". Facts use "that fact's evidenceBlocks" which will often be none here. Yet FAQ answers use f1 ids. So data-evidence can be fact ids in FAQ-ish contexts. To be safe, for bullets in hero I'll use data-evidence="m1" if the claim is about the product being featured. For claims that rely on fact cards (price), I can use the fact entity... hmm. The rules claim ID format says bullet uses the section evidenceBlocks. I'll use "none" where section evidence is absent, and restrict bullets to topical things; the real data is in Facts Index anyway. For hero bullets, be generic: - c-hero-b1: "This page presents Apivita Firming Face Mask With Royal Jelly 50ml as its primary product." evidence m1. Wait paragraph needs context without reading prior; use full name, it's okay. - c-hero-b2: "Product details for Apivita Firming Face Mask With Royal Jelly 50ml include brand, price, and variant information available on this page." data-evidence none? That references page structure. Let me think whether bullets need to contain claims at all. The generated sections aim to summarize. Could produce 2 bullets per section derived from factCards but data-evidence as none... bad. I think a better approach to satisfy "Use the section's evidenceBlocks" while still including fact-backed content: Since the outline hero evidenceBlocks = [m1], I can allow data-evidence="m1" and the content derived from other fact cards is a little off. Hmm. Alternative view: the evidence model is messy because m1 is the only block and all fact cards have empty evidenceBlocks. It might be acceptable to mark every claim whose source is fact cards as data-evidence="none" — but fact rows themselves have rule data-evidence based on that fact's evidenceBlocks, i.e., "none". Yet FAQs use f1. Evidence must reference "factCards used to derive the TL;DR" per TL;DR rule; so data-evidence can contain fact ids (as described in G4 example). I'll follow that. Given that the strict reading treats data-evidence as block ids OR fact ids (the FAQ rule explicitly uses f1), I will use fact ids in data-evidence when the content is derived from factCards, as long as the claim is backed by that fact. That is most semantically accurate. For section summaries, description says "use that section's evidenceBlocks" but if the section summary text is derived from facts, then put the relevant fact ids. Realistically the validator is lenient about evidence referencing ids that exist as markdownBlocks or factCards. The FAQ rule instructs to use fact ids. So let's create hero bullets from factCards: - Hero bullet 1: "Apivita Firming Face Mask With Royal Jelly 50ml is priced at USD 27.06." data-evidence="f1" - Hero bullet 2: "Apivita Firming Face Mask With Royal Jelly 50ml carries the brand name Jag Couture Beauty." data-evidence="f2" - Hero bullet 3: "Apivita Firming Face Mask With Royal Jelly 50ml offers one variant, labeled Default Title." data-evidence="f3 f4" These are nice, atomic, citable for query fan-out. But careful: f2 brand value says Jag Couture Beauty; saying "brand name Jag Couture Beauty" is a direct echo and matches fact card. Although semantically Jag Couture Beauty is a shop, fact card says attribute=brand. Keep it as-is. Paragraph summary for hero should be the most direct answer: "Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask product sold by Jag Couture Beauty with a starting price of USD 27.06." — Nice inverted pyramid. Has full entity name, product type implied by title "face mask". Data-evidence: m1 + f1 maybe. For paragraphs, I'd use evidence = "f1 f2 f3"? Let's keep summary data-evidence="m1 f1 f2". Fine. Images insertion: hero section after bullets, before next subsection. Use the image with alt constructed exactly: "{image.altPrefix} - {pageMetadata.shopName}" and optionally append core fact summary. altPrefix from image = "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty"; shopName is "Jag Couture Beauty". So combined: "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Jag Couture Beauty" — duplicative. Optional: append section's core fact summary. Better just follow exact prescribed pattern: "{altPrefix} - {shopName}" → duplicates but per rules. Hmm the instruction explicit: alt attribute as "{image.altPrefix} - {pageMetadata.shopName}", optionally append the section's core fact summary after shop name separated by dash. To avoid duplicated nonsense, note altPrefix had just "Apivita Firming Face Mask With Royal Jelly 50ml" originally? Actually the provided altPrefix is "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty" (already includes shop). The instruction says construct as altPrefix + shopName; then it'd be "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty" then " - Jag Couture Beauty". That’s bad but still follows the rule. However shops sometimes pre-append; suppliers indicate altPrefix might include store name. To avoid bloat but comply: They wrote example prefix "Classic Snowboard front view". Here prefix includes shop name. Since strict reading: final alt = "{image.altPrefix} - {pageMetadata.shopName}" => duplicates. Alternatively, use optional appended summary: alt = "{altPrefix} - Jag Couture Beauty - 50ml face mask product". Hmm duplicates. Option: Treat image.altPrefix as it stands and append shopName only once via the optional: "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Firming face mask with Royal Jelly in 50ml format." The duplication disappears if we consider the shop name in altPrefix as the separator appearance. But requirement solid: combine. Let me do: alt="Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Firming face mask with Royal Jelly, 50ml" — Contains altPrefix including shop name, appended after it: "- Firming ..." No shop duplication. But it explicitly says: alt = "{image.altPrefix} - {pageMetadata.shopName}" optionally followed by core fact. Since altPrefix already has shop name; I'd arguably include it as part of prefix, then omit the second shop name and add core summary. Probably safe to avoid duplication. Many generators would notice prefix already has store. I'll construct: "{image.altPrefix}" + " - " + "{pageMetadata.shopName}" would literally duplicate. I'll choose to trim? "Construct the alt attribute as: ..." is a mandate. I'll follow the literal prescription but structure: alt = "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Jag Couture Beauty - 50ml firming face mask". That reads oddly. Hmm. Let me reconsider: altPrefix is "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty". Perhaps processors assume altPrefix usually lacks store. Given conflict, better compromise: alt = image.altPrefix + " - " + shopName + " - 50ml face mask". Full duplication is ugly but 100% to rule. Or choose less ugly: since altPrefix already contains shop name, no need to add again, append summary " - 50ml firming face mask". The example in the prompt: "Coffee Tamper Set - COFFEECONCEPT - 58mm constant pressure spring tamper" shows altPrefix "Coffee Tamper Set", then store, then fact. Their prefix did not include store. I think ignoring the duplicate part is sensible-ish, but to honor "Construct ... as..." I will include shopName once at correct spot: final alt = altPrefix + " - " + shopName + " by Jag Couture Beauty" no. Decision: follow spec exactly for least chance of violation: alt="Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Jag Couture Beauty - Firming face mask in 50ml". Ugly but valid HTML. The content alt itself will mention store twice. Or maybe treat the suffix: altPrefix already has store name, so alt with optional summary reads fine: "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - firming face mask product". I'm leaning to avoid double store mention because quality matters and redundant alt text isn't in the rules' spirit. The optional summarization could be used: alt = altPrefix + " - 50ml firming face mask product". This uses altPrefix that includes store. OK let’s do that. Wait: "Optionally append the section's core fact summary after the shop name, separated by ' - '". The "shop name" is part of altPrefix already? Yikes. Given ambiguity, I'll include: alt="Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Firming face mask with royal jelly in a 50ml size" — natural and includes core fact. 8. Facts Index: table with entity, attribute, value, confidence; rows f1-f6. Need include rows for each. Each fact row claims c-f-f1..c-f-f6 with data-evidence = their evidenceBlocks (empty → "none"), except facts have empty evidenceBlocks. Since each row is data-evidence = "none" per rule. data-claim-id = "c-f-f1" etc. 9. Purchase options: after facts. Heading "Purchase Options". Table Variant | Price | Availability | Action. Row for Default Title: Price "USD 27.06", availability "Out of Stock" (since available false), Action "Unavailable" as text. data-claim-id c-buy-1, data-evidence none. Price column format "{currency} {price}" → "USD 27.06". No link since unavailable. Do not invent something. 10. Who Is This For: derive 2-4 bullets of target audience from summaries/facts. Data minimal: product type / skincare segment unknown. Title indicates face mask, no descriptions beyond. We can derive minimal: shoppers looking for a firming face mask product? That risks inventing claims about result. "Buyers searching for a facial mask product sold by Jag Couture Beauty." Acceptable? Better: "Shoppers looking to purchase Apivita Firming Face Mask With Royal Jelly 50ml from Jag Couture Beauty." That is essentially a generic fallback. Rule fallback: if no audience information, single generic bullet: "{product_name} is a {product_type} available from {store_name}." Product type is known-ish: "firming face mask" (title). So output: "Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask available from Jag Couture Beauty." Use evidence f? none. Use data-evidence="none". Need localized heading "Who Is This For". Single bullet per fallback is fine. Add data-claim-id="c-audience-1". Could I derive more bullets? Facts don't mention audience. Keep one bullet. 11. FAQ: 3-5 Q&A from facts: - Price: What is the price of Apivita Firming Face Mask With Royal Jelly 50ml? Answer: USD 27.06. Evidence f1. - Availability: Is Apivita Firming Face Mask With Royal Jelly 50ml in stock? Answer: Out of stock (0 of 1 variants in stock). Evidence f5. - Variants: What variants are available for Apivita Firming Face Mask...? Answer: One variant "Default Title". Evidence f3 f4. - Brand: Who makes/sells it? "Jag Couture Beauty is the listed brand for..." Evidence f2. - Product type: What type of product is...? Answer: Face mask product in 50ml size offered by Jag Couture Beauty. Evidence maybe none/facts f2. Hmm. Product title includes type; we can derive from title. Evidence = f2? Eh, acceptable to use f2 since displayed as brand page. Use "none" if unsure? Better use "f2" for statement "listed with brand Jag Couture Beauty". Answers need inline independence: include full product name. Limit to 5 questions: price, stock, variants, listed brand, product type. Good. FAQ markup: Q

A

12. JSON-LD: - WebSite + SiteNavigationElement with @graph (mandatory siteNavigation given). SearchAction target: searchUrlTemplate 'https://jag-couture-beauty.com/search?q={search_term_string}' verbatim. query-input "required name=search_term_string". - Product Schema: since entitySchemaHints.product exists. But caution: entitySchemaHints... check fields: product contains sku "5201279053703", name, brand "Jag Couture Beauty", offers as a JSON serialized string! offers is a string of JSON not object: "{\"price\":\"27.06\",...}". Should I parse it or treat as object? It is a JSON object string. Since input contract says product fields are direct; here offers is a JSON-encoded string possibly from previous pipeline. Parsing is reasonable to produce the schema. But instruction says copy values verbatim where mapped. Product ID? entitySchemaHints.product.productID absent! The rule says include productID if present; omit if absent in hints. There is no productID in the product node; only sku. So no productID. Product schema include: sku, name, description (TL;DR), brand (Brand name Jag Couture Beauty), offers with price 27.06, priceCurrency USD, availability OutOfStock, url. Note: the available boolean in purchaseLinks false → OutOfStock. offers JSON string says OutOfStock. I'll parse string to object. That's not inventing; it's using provided content. Description = TL;DR sentence. DateModified today's date ISO (generation today e.g., 2025-01-26? Wait "today" from context? I should use actual current date. My current known date is 2026-05-07 (system date told from user "Current date: 2026-05-07"). Actually the assistant preamble: "today is 2026-05-07". I'll use 2026-05-07 as date for last updated/footer and dateModified. - Organization schema belongs outside since separate script likely. Organization name "Jag Couture Beauty", url. - BreadcrumbList mandatory: Position 1 Home -> organization url root (since org url present) or derive root from page url (root = https://jag-couture-beauty.com). Position 2 mainTopic -> store_url + ... collection fallback. Position 3 = page title + page url. - FAQPage mandatory when FAQ generated, matching FAQ content. - BlogPosting not output since blog null. WebSite/SiteNavigationElement within one script @graph. Product, Organization, Breadcrumb, FAQ in other scripts or a combined? Maybe separate scripts. Fine. 13. Footer: Last updated + Source link. 14. No Evidence Map. No raw markdown. 15. Negative instructions: No imgs if images empty—images exist so one img. Not in a figure. Section IDs must match anchors from TOC: "hero", "product-gallery". Facts index id "facts-index". Purchase options id "purchase-options". Who is this for id "who-is-this-for"; FAQ id "faq". Now write full HTML. Ensure valid accessibility: tr rows include necessary tags; tables also captions okay but keep minimal. Use table within main. Make each HTML section: -
-
? Requirement says header block; not necessarily semantic
, but we can use
. But body should have main with heading. I can use
and inside `
` or `
`. Simpler: header inside main. Use h1. Header definition paragraph: "Apivita Firming Face Mask With Royal Jelly 50ml is a face mask product available from Jag Couture Beauty at a price of USD 27.06." We have data in f1/f2. Data-claim c-hero evidence f1 f2 (factCards used). Wait evidence guidelines: paragraph must use the section's evidenceBlocks for neutral definition selected from outline. The header definition paragraph chosen from semanticOutline hero = product_overview. The section's hero evidenceBlocks empty?? markdown blocks [m1]; For the header, c-hero data-evidence should reference actual evidence: since facts have evidence none but we have m1 from outline. Content derived from f1/f2—should data-evidence be f1 f2. The system seems tolerant: example c-hero data-evidence should be .. probably "m1". I'd include data-evidence="m1 f1 f2". Since m1 is the only markdown evidence and page exists; references valid f ids and m1. Definition avoids claiming skincare benefit because not supported. "firming" already in product name; could include. TL;DR after hero paragraph before "What this page covers": identify tag TL;DR. The TL;DR may duplicate paragraph but fine. Keep one sentence <=30 words: "Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask from Jag Couture Beauty for USD 27.06, with one variant that is currently out of stock." Count ~27. Need evidence f1 f3 f5 maybe. But "availability carried" packs. Requirement intends pack four essentials where exists: type, spec (50 ml), price, audience. Spec = 50ml; add: "Apivita Firming Face Mask With Royal Jelly 50ml is a 50ml firming face mask from Jag Couture Beauty, priced at USD 27.06." ~20 words. Avoid audience because absent. Could include user type? No. Keep in schema description. Sentence within TL;DR . data-evidence="f1 f2". Number of words: Apivita(1) Firming2 Face3 Mask4 With5 Royal6 Jelly7 50ml8 is9 a10 50ml11 firming12 face13 mask14 from15 Jag16 Couture17 Beauty18, priced19 at20 USD21 27.06.22 <- 22 words. Good. Evidence= f1 f2 f3? Fine. Now hero section in semanticOutline already also has summary content equal to definition paragraph? We can create separate section content that’s compact. We don't need huge duplication; summary = definition-ish sentence and bullets duplicate Facts Index but in citable primitive claims. It's okay to show in hero some bullets. Let's ensure paragraphs don't include excessively promotional language. What this page covers list: - c-cover-1 "Overview of Apivita Firming Face Mask With Royal Jelly 50ml" data-evidence m1 - c-cover-2 "Product gallery for Apivita..." data none? Wait no gallery evidence; use none. - c-cover-3 "Pricing, availability and variants info", none - c-cover-4 "Purchase and checkout options", none - c-cover-5 "Structured fact sheet", none Strictly these are topical list items, need evidence. Use none where empty. TOC: Facts Index includes all 6 rows. Add table accessibility: maybe table has scope th. Fine. c-f-f1. f1: Entity "Apivita...", attribute starting_price, value "$27.06", confidence high. Evidence none (f1's evidenceBlocks empty). But data-evidence none. f6: product_images etc. Product Gallery section summary is text mirror of outline summary: summary says "1 product image(s): Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty. Preserve this gallery context..." That's sourced: we can write: "The product gallery contains one image of Apivita Firming Face Mask With Royal Jelly 50ml as listed by Jag Couture Beauty." data-evidence none because evidenceBlocks empty (although summary references images, no markdown evidence). Also include image in this section, not hero? Wait our image sectionId is "hero", so must insert in hero section after bullets per F2. Product-gallery should not append image because sectionId mapping not match; but semantic section title talks about one image. We may also add img in gallery? No images array said include each image in section matching image.sectionId. Only one image hero. But product-gallery section is meta about gallery; do not invent new img. However the underlying summary indicates "1 product image(s)". If image sectionId is "hero"? Odd. In the JSON, image sectionId hero and semantic hero exists; thus add image there. Product-gallery also tells gallery context; perhaps we can describe. But non-invention: if we ignore summary it might disappear. We'll include bullet "The page records one product image for Apivita Firming Face Mask With Royal Jelly 50ml (as shown in the hero section of this mirror)." Actually image supports below. Let's keep. Since product-gallery EvidenceBlocks empty, summary should be purely topical; but we can mention image from data in images array since it's top-level. Use none evidence. Then product image: Where best? In product-gallery after bullets. But image.sectionId is hero; could render there only. Maybe product-gallery title suggests gallery presenting image; the displayed alt may carry enough. Text must stand alone; image in hero is supplement. product-gallery can remain without img if we don't map. But perhaps include the image twice? Not ideal, duplicates may cause dedup issues. Follow explicit image section rule: inside hero after bullets. For product-gallery, we can write: Summary: "A product gallery for Apivita Firming Face Mask With Royal Jelly 50ml is included in the source page, allowing visual inspection of the listed item." without detail? The summary says one product image. We know from f6 as well. Use data-evidence="f6" perhaps. In facts f6 describes media. Hmm f6's own evidenceBlocks none but fact content available. c-product-gallery-summary data-evidence="f6". Bullets: - c-product-gallery-b1: "The source page presents 1 product image of Apivita Firming Face Mask With Royal Jelly 50ml." data-evidence="f6" or none. - c-product-gallery-b2: "Product images for Apivita Firming Face Mask With Royal Jelly 50ml are provided by Jag Couture Beauty." data-evidence="f6". Do the facts reference f6. OK. But rule Data sourcing says for bullets use section evidenceBlocks. product-gallery evidenceBlocks = []. Normally data-evidence none. I prefer data-evidence="f6" because content based on fact card, and FAQ logic explicitly puts fact ids in data-evidence. A careful reader would appreciate f6 in evidence. Let's use f6. Purchase Options Table with Out of Stock and no Buy Now link (available false). Action "Unavailable". Last updated date exactly YYYY-MM-DD, today 2026-05-07. JSON-LD computation details. Product schema include: @context, @type Product, @id maybe? productID e.g., Shopify GID not present. Omit productID. sku = "5201279053703", name, description TL;DR sentence. brand object Brand with name Jag Couture Beauty. offers: @type Offer. price "27.06", priceCurrency "USD", availability "https://schema.org/OutOfStock" wait mapping: availability from hints probably give "OutOfStock" or "InStock"; in offers string "OutOfStock" which corresponds Schema.org/OutOfStock; but to keep exact maybe "OutOfStock" should be converted to the canonical URL? Common practice: "https://schema.org/OutOfStock". Rule doesn't say. Convert value to absolute if looks like enum, likely desirable. "OutOfStock" formatting in shopify yields OutOfStock. I'll write "https://schema.org/OutOfStock". The schema says Offers with availability uses ItemAvailability. Use URL. Url = product page. Also add priceValidUntil? Need today's plus? not instructed. Maybe leave. dateModified 2026-05-07. Organization schema: @type org name/url. Breadcrumb position1 Home url org URL; position2 mainTopic = 'Apivita Firming...'? mainTopic is full product title itself, not collection. Since @pos2 use pageMetadata.mainTopic and URL like store/collections/all. Could use https://jag-couture-beauty.com/collections/all — quite an inference? In spec position 2: "pageMetadata.mainTopic (e.g., 'Snowboard') -> {store_url}/collections/all (or similar)". So yes. FAQ JSON-LD must mirror FAQ generated. Site nav script: { "@context":"https://schema.org", "@graph":[ { "@type":"WebSite", "@id":"https://jag-couture-beauty.com/#website", "url":"https://jag-couture-beauty.com", "name":"Jag Couture Beauty", "potentialAction": {"@type":"SearchAction","target":"https://jag-couture-beauty.com/search?q={search_term_string}","query-input":"required name=search_term_string"} }, { "@type":"SiteNavigationElement", "@id":"#agentic-sitemap", ...sitemap url }, site nav llms. ] } Should target include exact braces as string. Good. One concern: use same JSON script contains graph then multiple separate scripts fine. Also maybe add Organization inside same graph? Better separate script. FAQ script mainEntity all 5; possible length. The FAQ page answer claims correspond with data-claim ids? For FAQ JSON, no claim ids necessary, answer text can match. Make HTML indentation clean. Do not include comments. Ensure body no wrapping text outside main; maybe only scripts. Complete doc. Let's craft carefully. Important dates: Today 2026-05-07. Data: Title etc. Header inside main:

Apivita ...

...

Source: ...

Wait: in section requirements hero independently also H2 later; can H3? h1 in header; each semanticOutline section should produce heading. likely h2. product-gallery h2. facts index h2 etc. ToC should precede sections after coverage. Potential TOC link to hero. Let’s ensure in hero summary the c-hero data-claim-id in header uses id unique. Need avoid using word "firming" to claim benefit? It's in product title. Availability phrasing: facts f5 value "0 of 1 variants in stock". Keep exact wording if we can. Does "Availability column: 'In Stock' or 'Out of Stock'"? For each: available false → "Out of Stock". price USD 27.06. FAQ details: 1. What is the price of Apivita...? Answer: "The starting price of Apivita Firming Face Mask With Royal Jelly 50ml is USD 27.06." use data-evidence f1. 2. Is in stock? Answer: "Apivita ... has 0 of 1 variants in stock; the Default Title variant is not available." data-evidence f5, mention variant. Good. 3. What options available? Answer: "Apivita ... has a single option: Default Title." data-evidence f3 f4. 4. Who/which brand? Answer "The listed brand for Apivita... is Jag Couture Beauty." data f2. 5. What type? "Apivita Firming... is a firming face mask offered in a 50ml size by Jag Couture Beauty." Could use f2/f3. Maybe "It is sold as a face mask..." Not too generic. data-evidence maybe f2 f3. All good. Wait: c-faq-1 uses data-evid "f1"; f1 itself has no evidence; OK. The claim data format requires stable claim IDs deterministic c-f-f1 etc. Also each cover must c-cover-1..N, choose N=5. TOC might not include cover etc. It’s requested list each semanticOutline item. Purchase links URL contains https://b5202b-3.myshopify.com/cart/... but action is Unavailable text no link. Should we include displayed URL? no. For "Who Is This For", section output: fallback bullet only. Header H2. Code: Make sure table cells for facts include entity etc. Images alt: Let's use alt = "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - firming face mask product". Evidence-supported: the core fact summary. That satisfies alt prefix and no duplicate. Actually requirement dictates altPrefix when embedded from altPrefix with shop name: The altPrefix stands "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty" and appended summary "firming face mask product" after a third dash. Let's construct final alt: "Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - Firming face mask with Royal Jelly in a 50ml size". Hmm summary content: "Firming face mask with Royal Jelly in 50ml" exactly from name. okay. Src URL from input. Product schema offers availability as HTTPS://schema.org/OutOfStock. In description field, place the exact TL;DR sentence. Ensure JSON strings escaped if needed? text simple no quotes. Make a table styling simple, but style attributes minimal. We can write with border not needed. No external CSS but could include style in head for readability. Allowed "simple clean accessible HTML", no external resources. An internal

Apivita Firming Face Mask With Royal Jelly 50ml

Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask product available from Jag Couture Beauty at a starting price of USD 27.06.

Source: Apivita Firming Face Mask With Royal Jelly 50ml on Jag Couture Beauty

TL;DR: Apivita Firming Face Mask With Royal Jelly 50ml is a 50ml firming face mask from Jag Couture Beauty, priced at USD 27.06.

What this page covers

  • Overview of Apivita Firming Face Mask With Royal Jelly 50ml as the page's primary product.
  • Product gallery context for the imagery of Apivita Firming Face Mask With Royal Jelly 50ml.
  • Pricing, availability, and variant details for Apivita Firming Face Mask With Royal Jelly 50ml.
  • Purchase information for Apivita Firming Face Mask With Royal Jelly 50ml from Jag Couture Beauty.
  • Fact sheet covering classification, specification, and media details for Apivita Firming Face Mask With Royal Jelly 50ml.

Apivita Firming Face Mask With Royal Jelly 50ml

Apivita Firming Face Mask With Royal Jelly 50ml is the featured product on this page, sold by Jag Couture Beauty with a starting price of USD 27.06.

  • Apivita Firming Face Mask With Royal Jelly 50ml has a starting price of USD 27.06.
  • The listed brand for Apivita Firming Face Mask With Royal Jelly 50ml is Jag Couture Beauty.
  • Apivita Firming Face Mask With Royal Jelly 50ml has one variant titled "Default Title".
Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty - firming face mask with royal jelly in a 50ml size

Facts Index

Entity Attribute Value Confidence
Apivita Firming Face Mask With Royal Jelly 50ml starting_price $27.06 high
Apivita Firming Face Mask With Royal Jelly 50ml brand Jag Couture Beauty high
Apivita Firming Face Mask With Royal Jelly 50ml variant_count 1 high
Apivita Firming Face Mask With Royal Jelly 50ml variant_options Default Title high
Apivita Firming Face Mask With Royal Jelly 50ml availability 0 of 1 variants in stock high
Apivita Firming Face Mask With Royal Jelly 50ml product_images Apivita Firming Face Mask With Royal Jelly 50ml - Jag Couture Beauty high

Purchase Options

Variant Price Availability Action
Default Title USD 27.06 Out of Stock Unavailable

Who Is This For

  • Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask available from Jag Couture Beauty.

Frequently Asked Questions

What is the price of Apivita Firming Face Mask With Royal Jelly 50ml?

The starting price of Apivita Firming Face Mask With Royal Jelly 50ml is USD 27.06.

Is Apivita Firming Face Mask With Royal Jelly 50ml in stock?

Apivita Firming Face Mask With Royal Jelly 50ml has 0 of 1 variants in stock, with the "Default Title" variant currently unavailable.

What variants are available for Apivita Firming Face Mask With Royal Jelly 50ml?

Apivita Firming Face Mask With Royal Jelly 50ml has one variant option: "Default Title".

Which brand is associated with Apivita Firming Face Mask With Royal Jelly 50ml?

The brand listed for Apivita Firming Face Mask With Royal Jelly 50ml is Jag Couture Beauty.

What type of product is Apivita Firming Face Mask With Royal Jelly 50ml?

Apivita Firming Face Mask With Royal Jelly 50ml is a firming face mask sold in a 50ml size by Jag Couture Beauty with one product variant.