Fit and fabric questions block the sale and fill the inbox when the only size guide is a picture. A Shopify sizing FAQ should state the measurement in text on the product: the garment dimension, the size it belongs to, and the unit. A materials FAQ should name the fiber. A care FAQ should name the wash. An image-only size chart is easy for a sighted shopper who pinches to zoom, and invisible to many other readers and to tools that only see text.
Product FAQs for AI Crawler can draft questions from the product title, description, vendor, and type. The draft is only as specific as that text. If the description never contains the chest width, the generator has no measurement to repeat, and you should not save a number it invents. Put the real measurements in the description first, generate or type the FAQ, and edit the draft before you save. The saved copy goes into a product metafield and can be shown only on the products you assign.
What to publish as text
Publish the numbers a shopper uses to choose a size, in the unit you sell. For apparel, that is usually the body of the garment, not only the model's height. "The size medium has a 20 inch (51 cm) chest, measured flat" is a sentence someone can compare with a shirt they already own. "True to size" is a mood. If you have both a garment measurement and a body measurement, label which is which so a quote of the FAQ cannot swap them.
Materials belong in their own answer when the composition is part of the buying decision. "The shell is 100 percent organic cotton. The rib is cotton and elastane" is usable. "Premium natural fibers" is not. Care belongs in text too: water temperature, cycle, and whether the item can be tumbled. Home goods follow the same shape. A cushion's cover fiber and whether the insert is included are text, even if a photo shows the pillow on a sofa.
- Size: the dimension, the size label, and the unit, including how it was measured.
- Material: the fiber or surface, by part of the product if parts differ.
- Care: wash, dry, and any prohibition, in the first sentences.
What a size-chart image hides
A chart image can still sit on the page for shoppers who like a grid. It does not replace the FAQ text. Screen readers may get an empty or generic alt attribute. A shopper who searches the FAQ widget is searching question and answer text, not the pixels inside a PNG. A crawler reading the light-DOM FAQPage JSON-LD is reading the saved text, with HTML stripped, not the chart artwork.
If you keep the image, repeat the decision-making numbers in the FAQ. You do not need every cell duplicated if the line is honest about its scope. "Size medium is shown below. The chest, measured flat, is 20 inches" plus the image is a pair. The image alone, with alt text that says "size chart," does not answer which number is the chest.
Draft, then correct
Generation reads the description. A description that says "soft cotton tee" will not produce a reliable chest width. Add the table of measurements to the description in words, or skip generation and type the FAQ. Description mode can ask clarification questions before the final draft. That is the moment to supply the unit and the size. Drafts stay editable before save. Delete any inch or centimeter you cannot find on the spec sheet.
There is no accuracy score that clears a sizing draft. After save, the product block shows the group on assigned products. If two colors share a block and a fit, one group can be assigned to both products. If the oversized colorway is cut differently, it needs its own answers. Editing the group later rewrites the fields, the items, and the product links into the metafield.
Shared care versus product fit
Use a shop-wide group, with no products assigned, only for a rule that is truly shared. "We ship a spare button with every woven shirt" might be global if operations actually does that for every woven shirt. Fit is almost never global. A store FAQ that says "our clothes are relaxed" will be quoted against a slim trouser. Keep fit, fiber, and exceptions on the product. Keep a general returns window on the store FAQ page, and point the product FAQ at it only if the product follows that window.
A materials example that can be quoted: "The duvet cover is washed linen. It is not blended with cotton. It will soften and wrinkle. Machine wash cold and hang dry. Do not tumble." The first sentences are the material and the behavior. The last sentences are the care. Swap in your real fiber before you publish. The shape is the point, not this linen.
Choose Accordion on the product page so the size answer can open beside add to cart. A long materials story can stay closed until someone asks. The widget search will still find a word in the answer, such as "linen" or "inches," because the filter covers question and answer text. A monthly creation limit applies when you add these groups. The catalog does not publish the number. Read it on the plan screen if you are writing FAQs for a large apparel catalog.
Questions about sizing FAQs
Is a size-chart image enough?
It helps shoppers who can see the grid. Put the measurement in FAQ text as well, with the size and the unit, so the answer exists as words.
Can AI write the size FAQ from a photo chart?
The generator reads title, description, vendor, and type, or a description you type. It does not read a number that exists only inside an image. Put the measurement in text first.
Should every product repeat the return policy?
Only if that product is an exception. A shared returns rule belongs in the shop-wide group. Fit and fiber stay on the product.
The listing is Product FAQs for AI Crawler.
Put the next size answer in words, then see how product assignment works on Product FAQs for AI Crawler. Publish one product's measurements as text and keep the shared policy on the store FAQ page.