TL;DR
- A size guide is useful when it lets a shopper verify a specific product and variant, not when it is a generic chart detached from the item they are considering.
- Keep size, size system, size type, fit language, measurements, units, variant availability, and the source page aligned. A body measurement and a garment measurement are different facts and should be labeled differently.
- Visible product-page information, variant data, structured data, and commerce feeds have separate jobs. They can make fit attributes easier for systems to parse, but they do not guarantee rankings, AI citations, recommendations, or sales.
- Shopify can distribute eligible Catalog data and provide agent discovery and WebMCP capabilities on supported storefronts. The merchant and brand still own the accuracy, mapping, visibility, policy, and measurement behind a fit claim.
Last reviewed: August 28, 2026. Recheck this guidance after material Google, Shopify, or OpenAI documentation changes.
When a shopper asks whether a jacket runs small, whether a chair will fit under a desk, or whether a ring is available in a particular size, the answer depends on more than a size chart. The product page needs to identify the exact product, clarify the selected variant, state what was measured, name the unit and system, and point to information a buyer can inspect.
That same discipline matters for ecommerce size guides in AI search. A clean chart cannot force a system to retrieve or repeat the right fit claim. It can make the claim easier to verify when the visible storefront, selected variant, and product data all describe the same thing.
This is a narrow operating problem: turn fit ambiguity into evidence that can be checked at the SKU level.
What an AI shopping system must verify before repeating a fit claim
Fit language is usually conditional. “Runs long,” “oversized,” “fits a standard carry-on,” or “works for a 32-inch waist” can mean different things by product, market, material, and selected option. Treat each statement as a product fact with a scope, rather than a piece of persuasive copy.
For free listings, Google Merchant Center requires size for Clothing and Shoes products; for other products it is optional. When apparel fit needs clarification, submit the relevant size-system and size-type fields, then keep them aligned with the purchasable item. Google also supports product dimensions for applicable products. Google’s size guidance and apparel data practices describe the current feed boundary.
Before a system or a customer can rely on a fit statement, the record should answer these questions:
| Question | Evidence to expose | Common failure |
|---|---|---|
| Which item is being described? | Product name, product ID, selected variant, and a stable product URL. | A collection-level chart is used for products with different cuts or dimensions. |
| What does the size mean? | Size value, size system, size type, market, and unit where relevant. | “Medium” appears without a country or conversion context. |
| What was measured? | Clear label for body measurement, garment measurement, product dimension, or compatibility limit. | A sleeve length is presented as a body measurement. |
| Where was it measured? | Measurement point, method, and a diagram or concise definition when the term is ambiguous. | “Width” is used without saying whether it means shoulder, chest, seat, or interior width. |
| Does the chosen variant exist now? | Variant-specific price, availability, image, URL, and option values. | The guide describes a size that is unavailable or belongs to a different colorway. |
| What remains subjective? | Qualified fit notes, review context, and a link to the returns or support path. | A customer preference is rewritten as a universal promise. |
The answer should be traceable. A sofa needs dimensions and clearance guidance. A necklace needs length and clasp details. A jacket needs a size system plus garment or body measurements. Each category has different decision fields, but the operating principle is the same.
Build a fit-verification contract for every product family
A fit-verification contract is a product-family record that assigns an owner and source of truth to each fit fact, then requires that fact to agree across the product page, variants, feeds, and structured data. It is not a new platform feature.
| Field | What to record | Where it should agree |
|---|---|---|
| Product and variant identity | Parent product, SKU or variant ID, option values, and selected-variant URL. | Catalog, product page, feed, structured data, checkout. |
| Size fields | Size, size system, size type, conversion rule, and market. | Variant selector, size guide, feed, product data. |
| Measurements | Body or garment label, measurement point, unit, tolerance, and method when material or construction changes the result. | Product page, guide, help content, product specification. |
| Fit descriptor | Regular, slim, relaxed, oversized, wide, narrow, or category-specific compatibility language. | Product description and guide, with careful review of any feed field. |
| Product media | Variant images, diagrams, and alt text that identify meaningful fit or dimension differences. | Product page, media record, Catalog where eligible. |
| Evidence and exceptions | Review context, care or material limits, delivery constraints, and policy links. | Product page, support content, reviews, policy source. |
| Freshness and owner | Last reviewed date, accountable team, and release trigger for a new cut, supplier, method, or market. | Internal product record and publishing workflow. |
For example, an illustrative jacket variant could record: M, US women’s sizing, regular fit, garment chest measured flat under the armholes in inches, its selected-variant URL, product image, and current availability. A shopper can then see what the number means before deciding whether it applies to their body and preferred fit.
Then decide which facts are objective and which are experience-based. “The inseam is 30 inches” is a product specification when it is measured and maintained by the appropriate product owner. “This inseam feels short on me” is buyer experience. Both can help a shopper, but they should not be merged into one unsupported statement.
For variants, do not let a parent-level claim hide a material change. A medium in one fabric, a petite cut, or a different frame size may have different measurements, inventory, or photos. Google’s product-variant guidance is useful here because it emphasizes distinct, selectable variants and their relationship to a product group. Your product-data contract should preserve the same relationship across the storefront, feeds, and checkout.
Schema can describe some size-related attributes, but it is not a promise that every search or AI system will consume them. Keep markup truthful and aligned with the visible page. Google’s structured-data policies require that alignment and do not guarantee a feature will appear.
Make the guide visible beside the buying decision
A PDF hidden in a footer or a universal chart buried in help content is hard for shoppers to use and easy for teams to forget during a product update. Put the critical fit information on the relevant product page, near the variant selection or specification area, and link to fuller guidance when the product needs it.
The goal is not to repeat the entire guide in every surface. It is to give the shopper a dependable route:
- The product page identifies the selected product and available options.
- The guide explains how its measurements relate to that product, body, or space.
- A diagram or short definition resolves ambiguous terms such as rise, depth, seat width, or internal clearance.
- The selected variant, price, and stock state confirm that the item described can actually be bought.
- The returns, shipping, or support source handles the questions the guide cannot answer safely.
Google supports product dimensions such as length, width, height, and weight for relevant items, and says those attributes can improve the accuracy of product information in search. Its product-dimensions documentation is a useful implementation reference. It does not turn a dimension field into a guarantee that an AI system will make the right recommendation.
Use qualified fit notes instead of absolute language. “Garment chest is measured flat under the armholes” is specific. “Fits everyone perfectly” is not. If reviews add context, retain the product, variant, date, and limitation behind the statement. The apparel-specific AI visibility guide shows how those product details connect to discovery work without replacing specifications.
Shopify provides useful plumbing, but the brand owns fit accuracy
Shopify is Lexsis’s first integration, but this workflow should transfer to any ecommerce stack. For eligible products and channels, Shopify Catalog can distribute product titles, descriptions, options, images, price, availability, and key attributes.
For agentic storefronts, Shopify uses /agents.md as the canonical discovery URL, while /llms.txt and /llms-full.txt can provide the same discovery context. Catalog, discovery files, and agentic-channel listing-quality signals are separate capabilities. None replaces complete product data or establishes open-web or third-party AI visibility.
| Shopify provides by default or where available | Merchant configures | Brand still owns | Lexsis adds |
|---|---|---|---|
| Catalog distribution for eligible products, agent discovery files, listing-quality signals where available, and WebMCP tools on supported Liquid storefronts. | Catalog mapping, product eligibility, channel settings, product visibility, direct-checkout decisions, and product-specific metafields or guide presentation. | Measurements, units, fit definitions, variant accuracy, product images, review qualification, policy exceptions, crawlable source pages, and measurement. | A reviewable workflow to identify AI-search evidence gaps and connect approved product, content, technical, and storefront changes. |
Shopify’s agentic storefront documentation and product documentation describe these capabilities for eligible experiences. A brand that opts out of one Catalog path can still be found through open-web crawling, indexing, or other feeds, so product visibility decisions need a wider search review. Direct checkout is channel-specific. Shopify’s WebMCP documentation can help supported agents inspect products, variants, carts, policies, and checkout navigation, but it cannot compensate for a vague size chart or inaccurate source data.
Release fit changes as product-data changes
The riskiest fit errors are often introduced after a product launch. A supplier changes a pattern, a new market uses a different size system, an image is replaced, or an old chart is copied to a new collection. Treat those events as release work, not as a copy edit.
Run this QA check before a material fit update goes live:
- Name the affected product family, SKUs, variants, markets, and owner.
- Compare the visible product page, selected-variant state, size guide, product specification, and help content.
- Verify size, size system, size type, units, and measurement labels against the approved source.
- Check that variant images, prices, availability, URLs, and product identifiers still resolve to the intended purchasable item.
- Update relevant structured data and feed fields only when they match visible, current product information.
- Test the route a mobile shopper takes from product page to guide, policy, cart, and checkout handoff.
- Review support contacts, returns reasons, product-page feedback, feed diagnostics, and observed AI answers against the team’s own baseline.
OpenAI’s product-feed specification supports variant-level data and options such as size. Access and surface availability remain program-dependent, so use it as an implementation reference, not as proof that every field will be retrieved. The broader product-page AI search checklist can help teams keep the visible page and its technical signals aligned.
The most useful outcome is not a claim that your chart is “AI optimized.” It is a fit fact that a shopper, support agent, crawler, or AI-shopping system can inspect without guessing. If your team needs help finding and resolving those evidence gaps across discovery and the storefront, see how Lexsis supports AI visibility or book a demo.
