Home › Blog

Blog

Long-form guides on what AI shopping agents actually read, what Shopify stores get wrong, and the catalog hygiene that decides who gets surfaced. New posts as we find new patterns in the scan data.

• 2026-06-20~23 min read Shopify laptop schema for AI agents: Intel Core i vs Core Ultra naming crisis, TDP class (U/P/H/HX), RAM upgradeability (DDR5 SO-DIMM vs LPDDR5X soldered), and display panel type

  Intel renamed its laptop processors twice in two years — "Core i7" and "Ultra 7" now both exist as laptop chips, represent different architectures, and pair with different memory types that cannot be upgraded the same way. The complete guide: processor family + TDP class suffix — the same "Core i9" brand spans a 4× power envelope from 15W U-class ultrabook to 55W HX-class desktop replacement; RAM type and upgradeability (DDR5 SO-DIMM 262-pin user-upgradeable vs LPDDR5X soldered permanently fixed — the most post-purchase-regret-generating omission in laptop structured data; 16GB → 32GB is a 30-minute $80 swap on SO-DIMM, impossible on LPDDR5X); NVMe slot PCIe generation as the throughput ceiling (Gen 4 drive in Gen 3 slot = Gen 3 speeds, ~3,400 MB/s not 7,000 MB/s — slot and drive must be encoded as separate additionalProperty fields); display panel type behind brand names (Liquid Retina XDR = Mini-LED IPS LCD, not OLED; Super AMOLED = OLED; NanoEdge OLED = OLED; always encode underlying technology); complete JSON-LD for Dell XPS 14 (Core Ultra 7-155H, OLED, LPDDR5X soldered, PCIe Gen 4 M.2 2230), Liquid snippet for laptop.* metafields, 19-field reference table, and 5 common mistakes.

  laptop schemaCore i vs Core UltraTDP class suffixDDR5 vs LPDDR5XNVMe slot generationdisplay panel typeShopify Liquid

• 2026-06-20~22 min read Shopify electric toothbrush schema for AI agents: oscillating vs sonic motion type, ADA Accepted per model, brush head compatibility, and IPX rating

  The Oral-B iO Series 9 and a standard Oral-B Pro 3000 share the same brand name. They do not share a single brush head. AI agents recommending replacement heads have no way to know this without model-level brush_head_system data — and almost no Shopify store encodes it. The complete guide: motion type (oscillating-rotating-pulsating ORP vs sonic — ORP's 40,000 pulsations/min and Sonicare's 62,000 strokes/min measure entirely different physical phenomena, a bare number comparison produces incorrect cross-brand rankings), ADA Accepted certification (per model and per head configuration — iO Series cert does not cover Pro 3 3000 and vice versa; brand-level encoding includes non-certified models in agent-filtered results), brush head system compatibility encoding (Oral-B snap-on round pin-and-collar for all pre-iO models vs Oral-B iO magnetic-drive rectangular socket — physically incompatible, no adapter exists; the NOT compatible clause in schema is the data that prevents the return), pressure sensor feedback type (visual LED ring / haptic motor slowdown / audible tone — haptic is the only type detectable without line-of-sight to handle; encode as comma-separated list for accessibility filtering), IPX waterproof rating (IPX4 vs IPX7 — the X means solid particle protection unrated, not unknown; charging cradle carries no IPX rating regardless of handle rating), complete JSON-LD for Oral-B iO Series 9 Pro (12 additionalProperty entries + hasCertification ADA block), Liquid snippet for electric_toothbrush.* metafields, 12-field metafield reference table, and 5 common mistakes.

  electric toothbrush schemaoscillating vs sonicADA Acceptedbrush head compatibilityIPX ratingOral-B iOShopify Liquid

• 2026-06-20~22 min read Shopify running shoe schema for AI agents: heel drop mm, midsole foam (PEBA vs TPU vs EVA), carbon plate, and stability category

  A Shopify listing that reads "10mm drop, PEBA foam, carbon plate" has three specs that together decide AI agent recommendations — and none of them exist as machine-readable fields in default Shopify JSON-LD. Heel drop is a derived value (heel stack − forefoot stack) that must be explicitly computed and stored — 94% of stores don't. Foam brand names (NITRO Foam, ZoomX, Boost) are invisible to cross-brand polymer queries without the polymer class (PEBA / TPU / EVA) dual-encoded alongside. "Carbon plate" is used in marketing to describe everything from woven carbon fiber (~4% metabolic economy gain, Hoogkamer et al. 2018) to nylon composite (~1–2%) — encoding them as interchangeable generates false race-shoe recommendations. Stability category label "Stability" tells an AI agent nothing about the support mechanism: medial post (Brooks Adrenaline), guide rails (Brooks Transcend), or wide-base motion control (Brooks Beast) — three constructions with different stiffness, feel, and orthotics compatibility. Last width D means men's standard and women's wide simultaneously — missing gender context produces incorrect size recommendations. Complete encoding: heel drop + stack heights as three separate fields, PEBA/TPU/EVA dual-encoding with brand names, plate material precision (carbon fiber vs nylon composite vs none), stability mechanism in the description field, B/D/2E/4E with gendered interpretation, surface type + outsole rubber compound (Continental vs carbon rubber vs blown), complete JSON-LD for Puma Fast-R NITRO Elite 2 (PEBA, nylon plate, Continental, 8mm drop, 39mm/31mm stack, neutral, D-width), Liquid snippet for running_shoe.* metafields, 12-field reference table, and 5 common mistakes.

  running shoe schemaheel dropPEBA vs TPU vs EVAcarbon platestability categorylast widthShopify Liquid

• 2026-06-19~22 min read Shopify gaming monitor schema for AI agents: GTG vs MPRT response time, IPS vs VA vs OLED panel type, VESA DisplayHDR tiers, VRR G-Sync vs FreeSync

  "1ms 144Hz HDR gaming monitor" is three numbers and an adjective that answer almost nothing an AI shopping agent can act on. The complete guide: GTG vs MPRT response time disambiguation (two physically different measurements routinely merged into one "1ms" claim — GTG measures pixel electronics speed, MPRT measures perceived motion blur via backlight strobing that disables VRR), IPS/VA/OLED/TN/Mini-LED panel type tradeoffs (native contrast 600:1 TN vs infinite OLED; GTG 0.03ms OLED vs 5–20ms VA dark-to-dark; the Mini-LED encoding trap), VESA DisplayHDR tier system (DisplayHDR 400 requires no local dimming — nearly indistinguishable from SDR; DisplayHDR 1000 requires local dimming and delivers visible specular highlight impact; True Black 400 is the OLED-specific standard), VRR compatibility matrix (G-Sync module vs G-Sync Compatible vs FreeSync Premium vs FreeSync Premium Pro vs HDMI 2.1 VRR — only HDMI VRR works with PS5 adaptive sync), refresh rate Hz vs frame duration interaction, local dimming zone count for blooming risk, color gamut DCI-P3 %, complete JSON-LD for a 27-inch QD-OLED 240Hz monitor, Liquid snippet for gaming_monitor.* metafields, 15-field metafield reference table, and 5 common mistakes.

  gaming monitor schemaGTG vs MPRTVESA DisplayHDRVRR G-Sync FreeSyncIPS vs OLEDpanel typeShopify Liquid

• 2026-06-19~21 min read Shopify e-bike schema for AI agents: US Class 1/2/3 legal framework, mid-drive vs hub motor torque, battery Wh range prediction

  A Shopify listing that reads "750W, 48V, 21-speed, aluminum frame" has communicated almost nothing an AI shopping agent can act on. The complete guide: US Class 1/2/3 legal framework (Class 1 pedal-assist-only 20mph — most paths allowed; Class 2 adds throttle — triggers trail restrictions; Class 3 pedal-assist-only 28mph — road-only; these must be machine-readable, not buried in description prose), peak vs continuous rated motor watts (peak = 2-second burst capacity; continuous = sustained hill-climbing power — a 750W peak motor may sustain only 250–500W, and continuous watts is what determines grade performance), mid-drive vs hub motor torque advantage quantified (mid-drive multiplies through gear ratio: 80Nm at crankshaft × 3:1 low gear = 240Nm effective at wheel vs hub's fixed 60–90Nm), battery Wh vs Ah (10Ah/52V holds 520Wh; 10Ah/36V holds 360Wh — same Ah figure, 44% different energy; Wh is the only honest cross-bike comparison), PAS torque sensor vs cadence sensor (immediate force-proportional assist vs 0.5–1.5 rotation lag binary signal — the primary quality differentiator in e-bike drivetrains), real-world range prediction factors, complete JSON-LD for a Class 3 Bosch mid-drive commuter, Liquid snippet for ebike.* metafields, and 5 common mistakes.

  e-bike schemaClass 1 Class 2 Class 3mid-drive vs hub motorbattery Whtorque sensorrange predictionShopify Liquid

• 2026-06-19~19 min read Shopify espresso machine schema for AI agents: boiler type, PID temperature control, portafilter diameter, pre-infusion, and steam wand encoding

  "Semi-automatic, 15 bar, stainless steel" communicates almost nothing to an AI shopping agent. The complete guide: machine type taxonomy (Manual lever / Semi-auto / Automatic / Super-automatic / Pod — not interchangeable), boiler architecture (Thermoblock vs Single Boiler vs Heat Exchanger vs Dual Boiler — determines simultaneous brew + steam capability and temperature stability), PID vs pressurestat (±0.3°C accuracy vs ±5–8°C oscillation — directly visible in light-roast extraction yield), the 15-bar pump myth and OPV extraction pressure encoding (rated pump pressure vs actual puck pressure — most systematically wrong number in espresso listings), portafilter diameter ecosystem lock-in (58mm commercial / 54mm Breville / 51mm DeLonghi — determines lifetime accessory compatibility), pressurized vs non-pressurized basket type (grinder requirement determination), pre-infusion encoding (fixed E61 mechanical vs electronic fixed vs adjustable pressure profiling), steam wand type (commercial manual capable of microfoam vs panarello wet foam vs auto-integrated), E61 thermosiphon group head thermal mass and passive pre-infusion, complete JSON-LD for dual boiler PID semi-automatic, Liquid snippet for espresso.* metafields, 29-field metafield reference table, and 5 common mistakes.

  espresso machine schemaboiler typePID controlportafilter diameterpre-infusionsteam wandShopify Liquid

• 2026-06-18~18 min read Shopify AV receiver schema for AI agents: channel configuration, power output, HDMI 2.1, Dolby Atmos/DTS:X codec matrix, and room correction encoding

  "7.2 channel, 100W, Dolby Atmos, HDMI 4K" communicates almost nothing useful to an AI shopping agent. Which 7.2 — does it have height channels for Atmos? Is 100W rated at 1% THD with 2 channels driven, or 0.08% THD all-channels-driven (often 30–40% less)? Is HDMI 2.1 (4K/120Hz, VRR for gaming) or HDMI 2.0b (4K/60Hz only)? Is eARC supported (lossless TrueHD Atmos from TV) or just ARC (lossy DD 5.1 cap)? The complete encoding guide: [main].[LFE].[height] channel configuration notation (7.1.4 vs 9.2 vs 11.2.4 vs 9.4 — total channel count is insufficient), per-channel power with THD threshold and simultaneously driven channels, per-port HDMI version (partial 2.1 trap), full Dolby and DTS codec hierarchy (TrueHD vs DD+ bitstream distinction for Atmos), Auro-3D, Audyssey MultEQ XT32 vs YPAO-R.S.C. vs Dirac Live mixed-phase vs MCACC Pro, AirPlay 2 vs Chromecast Built-in vs HEOS vs MusicCast vs Roon Ready, 28-field metafield reference table, complete JSON-LD example, and 5 common mistakes.

  AV receiver schemaDolby AtmosHDMI 2.1DTS:XAuro-3DAudysseyDirac LiveShopify Liquid

• 2026-06-18~16 min read Shopify sunscreen schema for AI agents: SPF encoding, FDA broad-spectrum, PA++++ UVA system, and reef-safe compliance

  Sunscreen is the only common personal care product regulated as an OTC drug in the US — AI agents apply conservative health exclusions when regulatory compliance signals are absent. The complete guide: SPF encoding (UVB-only metric, the FDA 50+ cap, why high SPF ≠ broad-spectrum), FDA broad-spectrum designation (binary critical wavelength ≥370nm test — not a gradient), PA++++ JCIA persistent pigment darkening system for Asian markets (PA+ to PA++++ with PPD values — the quantified UVA scale that broad-spectrum doesn't replace), EU Boots star rating (1–5 stars for UVA/UVB ratio), active ingredient GRASE status (zinc oxide + titanium dioxide are GRASE I; oxybenzone, avobenzone, octinoxate, octocrylene, homosalate all GRASE Category III pending systemic data — not unsafe, but triggering stricter AI health-query logic), Hawaii Act 104 reef-safe compliance (ingredient-level verification required — "reef-safe" is unregulated; encoding absent oxybenzone/octinoxate/octocrylene by name is what AI agents verify against), water-resistant 40 vs 80 minutes ("waterproof," "sweatproof," and "sunblock" are prohibited FDA terms — still appearing in thousands of Shopify product descriptions), comedogenicity 0–5, complete JSON-LD for a mineral SPF 50+ PA++++ reef-safe sunscreen, and a Dawn Liquid snippet for sunscreen.* metafields.

  SPF schemaFDA broad-spectrumPA++++reef-safeHawaii Act 104GRASE statusShopify Liquid

• 2026-06-17~15 min read Shopify sports nutrition schema for AI agents: NSF Certified for Sport vs Informed Sport, protein per serving, and DSHEA compliance

  78% of supplement Shopify stores have no third-party testing certification in their JSON-LD — AI agents applying conservative health exclusions drop them from every athlete's recommendation. The complete guide: NSF Certified for Sport vs Informed Sport vs Informed Choice disambiguation (NSF International vs LGC Group, 280+ vs WADA-only substance lists, batch-test vs spot-test cadence, MLB/NFL/NBA/NHL/NCAA vs FIFA/IOC/UFC/IPF acceptance), protein per serving + serving size pairing (the denominator that determines protein density: 25g from 30g scoop = 83% isolate-grade vs 25g from 40g scoop = 63% concentrate-grade), leucine threshold (~2.5g per serving) as a machine-readable muscle protein synthesis filter, BCAA breakdown and complete protein encoding, DSHEA legalDisclaimer text requirement, supplement form and sweetener type controlled vocabulary, proprietary blend disclosure, complete JSON-LD for a whey protein isolate, and a Dawn Liquid snippet for supp.* metafields.

  supplement schemaNSF Certified for SportInformed Sportprotein per servingleucine thresholdDSHEAShopify Liquid

• 2026-06-15~14 min read Shopify allergen and dietary schema for AI agents: suitableForDiet, FDA FALCPA 9 vs EU 14 allergens, and cross-contamination encoding

  83% of Shopify food and supplement stores have no allergen data in their product JSON-LD. AI agents can't answer "is this peanut-free?" without it — and they apply conservative exclusion rules when allergen status is unknown. The complete guide: suitableForDiet enum reference (all 11 official RestrictedDiet values and when to use each), FDA FALCPA 9 vs EU Annex II 14 allergen comparison table (the 5 EU-only allergens most US merchants miss: celery, mustard, lupin, molluscs, sulphites), cross-contamination vs intentional ingredient encoding (the critical 'contains' / 'free-from' / 'may-contain' three-tier distinction), food safety certification markup via hasCertification (GFCO, NSF Gluten-Free, OU Kosher, IFANCA Halal — why certification outweighs self-declaration for AI agents), complete JSON-LD for a GFCO-certified protein powder, and a Dawn Liquid snippet for allergen metafields.

  allergen schemasuitableForDietFDA FALCPAEU allergensGFCO certificationcross-contaminationShopify Liquid

• 2026-06-15~12 min read Shopify specialty coffee roast date schema for AI agents: freshness window encoding, SCA cupping score, and the days-since-roast Liquid calculation

  78% of specialty coffee Shopify stores have no roastDate in their product JSON-LD. AI agents can't answer "is this coffee fresh?" without it — and "fresh roasted coffee" is a high-intent query category. The complete guide: roastDate vs bestBeforeDate vs expirationDate disambiguation (the three date attributes merchants confuse and why only one answers freshness queries), freshness windows by brewing method (filter 4–14 days, espresso 7–21 days, pre-ground 0–7 days), processing method × roast date interaction (Natural degasses slower — 10-day espresso rest vs 7 days for Washed), SCA cupping score as a permanence signal (80+ = specialty grade, doesn't change with time), dynamic days-since-roast Liquid calculation using Unix epoch arithmetic ('now' | date: '%s'), freshness status labels mapped to days elapsed, complete JSON-LD for a single-origin Ethiopian Yirgacheffe Natural, and a full coffee.* metafield reference table.

  roast date schemaspecialty coffeeSCA cupping scorefreshness windowadditionalPropertyShopify Liquid

• 2026-06-14~12 min read Shopify camera lens schema for AI shopping agents: isAccessoryOrSparePartFor, lens mount lock-in, and crop factor compatibility

  89% of Shopify camera lens listings have no isAccessoryOrSparePartFor — AI agents can't answer "does this lens fit my Sony A7 IV?" from JSON-LD alone. Mount strings in product titles are ambiguous: "Sony E-Mount" and "Sony FE" are the same physical mount, but "E" vs "FE" determines whether the lens covers a full-frame sensor or only APS-C. The complete guide: 8-mount reference table (Canon RF, Nikon Z, Sony E/FE, Fujifilm X, L-Mount, MFT, Canon EF, Nikon F legacy) with flange distances and format scope; crop factor image circle math (why an APS-C 28.4mm circle can't cover a 43.3mm FF sensor diagonal); the 3 APS-C vs full-frame mounting scenarios with compatibility outcomes; third-party lens product line code disambiguation (Sigma DG DN Art, Tamron Di III VXD G2); adapter compatibility for Canon EF-to-RF and Nikon F-to-Z (including the AF motor caveat); complete JSON-LD for a Sony FE zoom lens; and a Dawn Liquid snippet for lens.* metafields.

  isAccessoryOrSparePartForlens mount schemacrop factorcamera accessoriescompatibleWithShopify Liquid

• 2026-06-14~11 min read Shopify smart home schema for AI agents: Matter, Zigbee, Z-Wave protocol disambiguation and hub dependency encoding

  Protocol invisibility is the #1 reason smart home products fail AI agent recommendations — 94% of Shopify smart home products have no protocol version in JSON-LD. AI agents cannot confirm "works with SmartThings?" without protocol version, hub dependency chain, and Z-Wave region in structured data. Hub compatibility matrix (Zigbee, Z-Wave, Matter, Thread, WiFi), Z-Wave US/EU region lock (908.42 MHz vs 868.42 MHz — cross-border disaster signal), Matter 1.2 "no hub required" purchase signal, Thread vs Zigbee disambiguation (both 802.15.4, not interoperable), complete JSON-LD example for a Zigbee motion sensor, and a Dawn Liquid snippet using a smarthome.* metafield namespace.

  smart home schemaMatterZigbeeZ-WaveThreadhub dependencyShopify Liquid

• 2026-06-14~16 min read Shopify power tool battery platform compatibility schema: compatibleWith, 20V MAX disambiguation, and ecosystem lock-in for AI agents

  89% of Shopify power tool stores have no compatibleWith battery platform data in product JSON-LD. AI shopping agents answering "what DeWalt 20V MAX drills do you carry?" cannot confirm battery compatibility from structured data. The complete guide: compatibleWith cross-references with canonical platform @id URIs, 20V MAX vs 18V nominal voltage disambiguation, bare-tool vs kit hasPart structure, FLEXVOLT dual-platform batteries (two compatibleWith references), Makita XGT backward-compatibility cliff, UL Listed with specific standard number in certificationIdentification, and a Dawn Liquid snippet using a tool.* metafield namespace.

  compatibleWithbattery platform20V MAXFLEXVOLTpower tools schemaShopify Liquid

• 2026-06-13~18 min read Shopify jewelry schema for AI shopping agents: GIA certificate data, 4Cs additionalProperty, and lab-grown disambiguation

  91% of Shopify jewelry stores have no gemstone quality data in their product structured data. AI shopping agents filter diamonds by cut grade and carat from JSON-LD — not your product descriptions. GIA hasCertification with report number and verification URL, 4Cs as additionalProperty using exact GIA vocabulary (Excellent/VG/G for cut, D–Z color scale, FL–SI2 clarity, decimal carat weight), lab-grown CVD vs HPHT growth method disambiguation, metal fineness and hallmark stamp markup, ring size ProductGroup with SizeSpecification, Kimberley Process conflict-free certification, and a complete Dawn Liquid snippet using a jewelry.* metafield namespace.

  hasCertificationadditionalPropertyGIA schemalab-grown diamondsShopify LiquidAI shopping

• 2026-06-13~15 min read Shopify return policy schema for AI shopping agents: MerchantReturnPolicy, hasMerchantReturnPolicy, and conditional final-sale overrides

  73% of Shopify stores have no MerchantReturnPolicy in their product structured data. AI shopping agents rank return window as a top-3 purchase decision factor — without hasMerchantReturnPolicy on your Offer, the agent assumes worst-case and ranks competitors who have it. The two-layer architecture: site-wide policy on Organization plus per-product hasMerchantReturnPolicy on every Offer. Conditional final-sale detection via Shopify product tags, reduced return windows for clearance items via compare_at_price, per-product overrides via metafields, multiple returnMethod values, 5 common mistakes, and a complete Dawn Liquid snippet in a single snippet file.

  MerchantReturnPolicyhasMerchantReturnPolicyreturn policy schemaShopify LiquidAI shopping

• 2026-06-13~16 min read Shopify brand entity markup for AI agents: Organization sameAs, Knowledge Graph disambiguation, and the brand property gap

  89% of Shopify stores output a bare brand.name string with no entity links in their Product JSON-LD. AI shopping agents resolve brand identity from sameAs links — Wikidata, Wikipedia, LinkedIn, social profiles — not from string matching. Without sameAs, your brand is anonymous to the agent. The fix: a site-level Organization entity with @id and sameAs in theme.liquid, the @id linking pattern for product-level brand property, multi-brand boutique metafield architecture, which sameAs sources carry the most entity resolution weight, and a complete Dawn Liquid snippet for both DTC and multi-brand stores.

  brand entitysameAsOrganization schemaKnowledge GraphShopify Liquid

• 2026-06-12~17 min read Shopify clothing size schema for AI shopping agents: SizeSpecification, ProductGroup variesBy, and the variant-title trap

  96% of Shopify apparel stores have no SizeSpecification in product JSON-LD. AI shopping agents filter by size from structured data — not from variant title strings. A variant named M / Forest Green is opaque to ChatGPT Shopping's size filter; a SizeSpecification with sizeSystem: SizeSystemUS and sizeGroup: WomenClothing is not. Complete guide: SizeSpecification anatomy, all sizeSystem and sizeGroup enumeration values, ProductGroup with variesBy for multi-variant apparel, how to make sizeGroup dynamic using product metafields, footwear and accessories extensions, 5 common mistakes, and a full Dawn Liquid snippet for per-variant SizeSpecification.

  SizeSpecificationProductGroupapparel schemaShopify LiquidAI shopping

• 2026-06-12~16 min read Shopify Product Bundle Schema: Why AI Shopping Agents Can't Price Your Bundles (and the hasPart Fix)

  91% of Shopify bundle products have no hasPart in their Product JSON-LD. A $299 bundle containing $480 of components looks identical to a regular $299 product to ChatGPT Shopping, Perplexity, and Google AI Mode — they have no structured data to compute or communicate the bundle value. The full schema.org vocabulary for bundles (hasPart vs. isRelatedTo vs. isAccessoryOrSparePartFor), how to signal bundle savings using ListPrice PriceSpecification without triggering the sale-signal, why compare_at_price is semantically wrong for bundle discounts, a complete Dawn Liquid snippet driven by bundle.components metafields, and the 5 mistakes that make AI agents undervalue or misrepresent your bundles.

  hasPartbundle schemaPriceSpecificationShopify LiquidAI shopping

• 2026-06-11~15 min read Shopify priceValidUntil and sale pricing schema: why AI shopping agents show stale prices (and how to fix it)

  Your flash sale ended two weeks ago. ChatGPT Shopping is still quoting the sale price. This is not a ChatGPT bug — it's a missing priceValidUntil property in your Product JSON-LD, and 84% of Shopify stores on sale have the same gap. The four Shopify pricing scenarios and their correct schema, PriceSpecification with SalePrice vs. ListPrice for compare-at price markup, a complete Liquid snippet with metafield-driven dynamic expiry, the 30-day stale-cache window explained, and the 5 mistakes (adding priceValidUntil to non-sale products, misusing highPrice for compare-at, expired dates left in theme code) that break pricing signals for AI agents.

  priceValidUntilsale schemaPriceSpecificationShopify LiquidAI shopping

• 2026-06-11~16 min read Shopify shipping structured data for AI shopping agents: OfferShippingDetails, ShippingDeliveryTime, and free-shipping threshold schema

  92% of Shopify stores have no OfferShippingDetails schema. When AI shopping agents answer "free shipping on X?" or "can I get it by Friday?", they read structured data — not your shipping policy page. Stores without shipping schema are excluded from shipping-filtered queries that convert at 2× the rate of unfiltered browse. Complete guide: OfferShippingDetails anatomy, separating handling vs. transit time in ShippingDeliveryTime, declaring a free-shipping threshold via eligibleTransactionVolume, regional shipping with DefinedRegion, a full Liquid snippet for Dawn themes, and the 5 mistakes that silently break shipping schema.

  OfferShippingDetailsShippingDeliveryTimefree shippingShopify LiquidAI shopping

• 2026-06-11~14 min read Shopify Open Graph tags for AI shopping agents: why og:price:amount is a product discovery signal

  74% of Shopify stores are missing og:price:amount. 81% are missing product:availability. Most merchants set OG tags once to fix a Facebook preview and never touch them again — but GPTBot, PerplexityBot, and Google-Extended parse these meta tags before they parse your Product JSON-LD. Dawn leaves four critical commerce-namespace OG properties unset. Why AI crawlers read OG before JSON-LD, the six properties that matter, what the variant price problem looks like in practice, a Liquid snippet that adds all four missing tags in under 5 minutes, and four mistakes that silently invalidate your OG output.

  Open Graphog:price:amountproduct:availabilityShopify LiquidAI shopping

• 2026-06-10~15 min read Shopify product FAQ page schema for AI shopping agents: the pre-purchase query playbook

  AI shopping agents answer pre-purchase questions — "is this BPA-free?", "does it fit a king mattress?", "what’s the warranty?" — from FAQPage JSON-LD on product pages, not from your description text. 97% of Shopify product pages have no FAQPage schema. The 5 question categories (materials/safety, compatibility, sizing, warranty, shipping) that cover 80% of pre-purchase AI queries, the metafield architecture for scalable FAQ across your catalog, a before/after water bottle example, @graph integration alongside Product JSON-LD, and the 5 FAQPage mistakes that silently break coverage.

  FAQPage schemapre-purchase queriesJSON-LDShopify metafieldsAI shopping

• 2026-06-10~14 min read Shopify local pickup and BOPIS structured data: how Buy Online Pick Up In Store signals reach AI shopping agents

  Shopify configures local pickup inside the checkout flow — a UI that AI shopping agents never crawl. A store with six physical locations offering free same-day pickup looks identical to a drop-shipper in every AI shopping index. How to wire the two-entity architecture (OfferShippingDetails + LocalBusiness) so AI agents can answer "available for pickup today near me" queries, why deliveryTime in hours (not days) is the key to winning same-day queries, multi-location strategy with per-location geo coordinates, OpeningHoursSpecification for pickup vs. store hours, curbside and locker delivery variants, and the 5 BOPIS schema mistakes that keep local stores invisible in AI shopping results.

  BOPIS schemalocal pickupOfferShippingDetailsLocalBusinessAI shopping

• 2026-06-06~15 min read Shopify product availability states for AI shopping agents: InStock, PreOrder, BackOrder, LimitedAvailability, Discontinued

  Availability state is the first filter AI shopping agents apply — before recommending a product, they verify it can actually be purchased. 69% of Shopify stores output InStock for OOS or backordered products. The 7 schema.org availability values, why Shopify’s default Liquid gets it wrong (product.available collapses 3 distinct states into a boolean), the master Liquid snippet for correct availability mapping across all inventory scenarios, per-state JSON-LD patterns for InStock/LimitedAvailability/PreOrder/BackOrder/Discontinued, multi-location inventory, and the 5 availability mistakes costing recommendation slots.

  availability schemaInStockPreOrderBackOrderLimitedAvailabilityAI shopping

• 2026-06-06~14 min read Shopify trust signals for AI shopping agents: return policy, warranty, certifications, and seller rating schema

  AI agents are trust-first recommendation engines — they don't just pick the cheapest product, they recommend stores they can verify. 73% of Shopify stores have no MerchantReturnPolicy in JSON-LD. 91% of stores with a warranty page have no WarrantyPromise schema on products. The 4 trust signals (MerchantReturnPolicy, WarrantyPromise, hasCertification, Organization AggregateRating), how each one maps to post-purchase risk in the AI agent recommendation model, a complete Liquid snippet wiring all 4 trust signals, and the 5 common mistakes that undermine them.

  trust signalsMerchantReturnPolicywarranty schemahasCertificationAI shopping

• 2026-06-05~14 min read How to audit Shopify structured data: the exact 3-tool workflow to verify your JSON-LD is working for AI shopping agents

  67% of Shopify stores with JSON-LD have at least one critical parse error — but you'd never know it from the page rendering. The three-tool audit: Rich Results Test (per-product Google parse validity + required field presence), Schema.org Validator (full spec compliance, type correctness, deprecated properties), Google Search Console (catalog-wide error clustering across all crawled pages). Plus a curl workflow to verify crawler accessibility and a breakdown of 5 silent failure patterns: Liquid variables rendering as empty strings, bare availability strings instead of schema.org URIs, HTML entities in JSON-LD, price as currency string instead of number, and structured data present only on homepage not product pages.

  structured data auditJSON-LDRich Results TestSchema.orgAI shopping

• 2026-06-05~15 min read Shopify Markets and international catalog readiness for AI shopping agents: why hreflang misconfiguration silences your store in every non-primary market

  40%+ of $100k+ Shopify stores have at least one non-primary market configured. 83% of those stores have incomplete or missing hreflang on product pages. AI shopping agents — ChatGPT Shopping, Perplexity, Google AI Mode — can't execute JavaScript locale redirects or use Accept-Language headers, so hreflang is the only signal that routes them to your regional catalog. Five failure modes: missing x-default, homepage-only hreflang, language-only tags (en instead of en-GB), sitemap/head mismatch, and hreflang pointing to 301-redirecting URLs. JSON-LD priceCurrency fix using cart.currency.iso_code vs. shop.currency, and a complete Liquid snippet for per-product-page hreflang generation across all configured markets.

  hreflangShopify Marketsinternational SEOAI shoppingJSON-LD

• 2026-06-05~13 min read Shopify variant titles and option naming for AI shopping agents: how agents resolve color, size, and material queries

  Product titles match the base entity. Variant option values decide which specific color, size, or material query converts. 71% of stores have at least one option dimension too vague to disambiguate variant queries. Five option naming failures (vague color values with no material context, non-standard option names, mixed size systems, name/value dimension mismatch, absent material options), schema.org option name vocabulary, per-variant Offer additionalProperty JSON-LD with Liquid snippet, and before/after rewrites for apparel, bedding, and beauty. Why bestsellers are the most important products to fix first.

  variant optimizationoption namingAI shoppingJSON-LDcatalog quality

• 2026-06-04~12 min read Shopify product titles for AI shopping agents: why the first 70 characters decide everything

  54% of Shopify stores have at least 10% of products with title issues. A weak title doesn't just miss one query — it degrades the return on every other catalog signal: GTIN, reviews, descriptions, shipping schema. Three failure modes (brand-noise front-loading, generic product type, marketing language substitution), the entity-first title formula, per-agent display truncation behavior, the JSON-LD consistency penalty, and before/after rewrites across apparel, home goods, and skincare.

  product titlesAI shoppingentity signalscatalog optimizationChatGPT Shopping

• 2026-06-04~16 min read ChatGPT Shopping for Shopify: a 30-day setup and audit playbook

  Most Shopify stores enabled Agentic Storefronts and waited. Three months later, nothing. The reason isn’t the toggle — it’s a dozen compounding signal gaps: OAI-SearchBot blocked by Cloudflare, Product JSON-LD injected via JavaScript (invisible to crawlers), GTINs missing on 80% of the catalog, descriptions under 150 words, no GMC feed, no brand entity signals. This 30-day playbook closes every gap in sequence, with audit checkpoints, scan data behind each fix, and GA4 attribution setup so you can measure before day 30 whether the changes are landing.

  ChatGPT Shopping30-day playbookstructured dataGTINaudit

• 2026-06-03~13 min read Shopify product descriptions for AI shopping agents: the six signals ChatGPT, Perplexity, and Google AI Mode extract

  AI shopping agents generate recommendations by extracting signals from your product description — and if your description is too short, too generic, or stripped of attributes, they quote a competitor instead. 68% of stores have at least one product under 100 words. The six signals that separate visible products from invisible ones, the 150-word threshold explained, per-agent behavior for ChatGPT vs. Perplexity vs. Google AI Mode, common Shopify description failure modes (Shopify Magic defaults, HTML clutter, variant specs missing from text), the JSON-LD description connection, and a before/after rewrite of a real product description.

  product descriptionsAI shoppingcontent optimizationChatGPTPerplexity

• 2026-06-03~12 min read Shopify AI shopping agent attribution: how to see exactly what ChatGPT, Perplexity, and Google AI Mode are sending you

  GA4 has no AI shopping channel. ChatGPT sends traffic from chatgpt.com, Perplexity from perplexity.ai, Google AI Mode from google.com (indistinguishable from organic). All three land in the generic Referral bucket by default. This guide covers every AI agent referrer signature, the GA4 custom channel group rules (including the srsltid trick for Google AI Overview), server log grep commands for crawler vs. customer separation, Shopify Analytics limitations, and a 5-KPI weekly dashboard that closes the feedback loop between structured data fixes and measurable revenue.

  analyticsGA4attributionChatGPTPerplexity

• 2026-06-02~10 min read Shopify gift cards and digital products: the AI shopping agent blind spots most stores ignore

  Gift cards trigger GTIN validation errors in AI shopping agents. Digital downloads carry phantom shipping costs from Shopify’s default theme. Both failures are invisible in your admin but exclude these products from ChatGPT Shopping, Google AI Mode, and Perplexity entirely. Every failure mode documented — and the exact JSON-LD fixes for AggregateOffer denominations, DigitalDeliveryMethod suppression, and schema type routing (Book, SoftwareApplication, Course, MusicRecording) per product category.

  gift cardsdigital productsJSON-LDGTINstructured data

• 2026-06-02~14 min read Shopify subscription pricing and AI shopping agents: why they show the wrong price

  Your subscribe-and-save price is typically 15–20% cheaper than the one-time price. AI shopping agents like ChatGPT Shopping and Perplexity almost never quote it — because Recharge, Bold, Stay.ai, and Skio all inject subscription pricing via JavaScript, which crawlers read after the initial HTML. Why the invisible discount problem happens mechanically, how each major agent handles (or doesn’t handle) subscription pricing, what the scan data shows, and the complete PriceSpecification JSON-LD fix with Liquid snippets for each app.

  subscriptionsPriceSpecificationJSON-LDRechargesubscribe and save

• 2026-06-01~11 min read Shopify Agentic Storefronts: What Changed March 2026 and What Your Store Must Do Now

  On March 24, 2026, Shopify enabled Agentic Storefronts by default for every eligible US merchant. Most store owners assumed it meant a chatbot — but the actual mechanism is a catalog API that lets ChatGPT Shopping, Perplexity, and Google AI Mode transact directly through your store. Here's what the toggle actually does, why 78% of stores still aren't visible to agents despite having it on, and the 12-point readiness checklist with expected score lifts for each fix.

  Agentic Storefrontscatalog hygieneMarch 2026AI shopping

• 2026-05-31~8 min read ChatGPT Shopping, Perplexity, and Google AI Mode: How Each AI Agent Picks From Your Shopify Catalog

  Three AI shopping agents now send measurable referral traffic to Shopify stores — and each one weights catalog signals differently. ChatGPT Shopping weights GTIN-based exact-match lookup; Perplexity Commerce weights AggregateRating and description richness; Google AI Mode extends your existing Merchant Center Shopping Graph. The side-by-side signal priority table, data from our 100-store scan, and the 3-pass cross-platform optimization sequence that covers all three without tripling your workload.

  ChatGPT ShoppingPerplexityGoogle AI Modeoptimization

• 2026-05-31~13 min read Headless Shopify: the four signals you silently lose when you leave the standard storefront

  When you migrate to Hydrogen or build a custom Next.js storefront, Shopify quietly stops generating four things AI shopping agents depend on. The product feed at /products.json, Product JSON-LD on every PDP, a compliant robots.txt, and stable canonical URLs all disappear without a single build error. How each signal breaks, how to verify it with curl commands, and the exact code to restore it in Hydrogen and Next.js.

  HeadlessHydrogenNext.jsJSON-LDproduct feed

• 2026-05-30~14 min read Cloudflare for Shopify: the three settings that silently block AI shopping agents

  Your robots.txt says Allow: / for GPTBot and your Shopify theme is untouched — yet the CatalogScan robots-open signal fails at 0 points. The culprit is Cloudflare: specifically one of three settings that intercept AI shopping crawlers at the CDN layer before they reach your origin. The curl test that confirms Cloudflare is the problem, the three settings in order (Bot Fight Mode → AI Scrapers managed rule → custom WAF rules using cf.client.bot), the safe Cloudflare config that keeps real bots out while keeping GPTBot, OAI-SearchBot, PerplexityBot, and ClaudeBot in, and the seven-step verification playbook.

  Cloudflarerobots.txtAI crawlersBot Fight Mode

• 2026-05-01~12 min read AggregateRating on Shopify: which review apps inject it correctly and which silently break it

  9 in 10 Shopify stores in our launch scan fail AggregateRating in the JSON-LD even with visible stars on every PDP and a reviews app installed. The on-page stars and the schema-readable stars are two different things, and AI shopping agents only read the second. The per-app anatomy of what Judge.me, Yotpo, Loox, Stamped, and Okendo inject by default, where each toggle lives, the four shapes the schema can take (only one is correct), and the 30-day playbook for verifying your fix actually landed.

  AggregateRatingreview appsJSON-LD

• 2026-04-30~10 min read ProductGroup JSON-LD on Shopify: why 60% of stores leave 18 points on the table

  ProductGroup JSON-LD is the single biggest score lever in our scan data — worth 30 points on a 100-point scale, more than any other signal. 60% of top DTC Shopify stores fail it entirely. The four shapes Shopify stores actually emit (only one is correct), why ChatGPT Shopping and Perplexity need ProductGroup specifically for variant queries, and a 12-line Liquid snippet that lifts the average store from 12/30 to 30/30.

  JSON-LDProductGroupcatalog hygiene

• 2026-04-30~10 min read Shopify metafields for AI shopping agents: which 8 actually move the score

  Most Shopify stores have hundreds of metafields. AI shopping agents read maybe eight of them. The two namespaces that matter (shopify.* and mm-google-shopping.*), the eight metafields that decide whether ChatGPT Shopping picks your variant or the same product on Amazon, what we keep finding broken in the wild, and how to fix coverage in an afternoon without a developer.

  metafieldsStandard Product Taxonomycatalog hygiene

• 2026-04-25~9 min read Shopify GTIN requirements for AI shopping agents (2026 guide)

  When Shopify turned Agentic Storefronts on by default on March 24, 2026, GTIN coverage stopped being a Google Shopping concern and became a hard ranking input for ChatGPT Shopping, Perplexity, and Google AI Mode. What is a GTIN, when does Shopify require one, and how do you fix coverage on your store without buying GTINs you don't need — with real data from a 100-store scan.

  GTINcatalog hygieneAgentic Storefronts