Use Shopify Metaobjects as a CMS: Reusable Size Charts & Ingredient Lists
As your catalog grows, the same blocks of content show up again and again. The same size chart on forty shirts. The same ingredient list on every flavor in a range. The same care instructions on a whole season of knitwear. You paste them in product by product, and then one measurement changes, or one ingredient gets reformulated, and now you’re editing dozens of pages by hand and hoping you didn’t miss one.
There’s a better model, and you already have it built into your store. A metaobject lets you create that content once and reference it from everywhere it’s needed. Change the original, and every product pointing at it updates automatically. That “write once, reuse everywhere, edit in one place” pattern is exactly what a content management system does, so you can treat metaobjects as a lightweight, native CMS for your structured content.
This article walks through two worked examples that prove the point: reusable size charts and structured ingredient lists. Then we’ll look at why this structure pays off for search, and what changes when you’re doing it across hundreds of products instead of five.
Why a Metaobject Is Really a Mini-CMS
If you’ve read our first article, this will sound familiar. A metaobject is standalone. It doesn’t hang off any single product. It’s reusable, so many products can point at the same entry. And it lives in one place, which means one edit propagates everywhere it’s referenced.
Strip away the jargon and that’s the definition of a CMS: a single source of truth for a piece of content, surfaced wherever you need it. Shopify even files metaobject entries under Content in your admin, right where you’d expect a CMS to keep them.
So here’s the one-line rule for the whole article. Reused across many products? Make it a metaobject. Genuinely unique to one product? A metafield is enough. A size chart shared by your entire shirt line is a metaobject. The specific SKU number on one shirt is a metafield. Keep that test in mind and the two examples below will feel obvious.
Worked Example: Reusable Size Charts
Size charts are the textbook case for a shopify size chart metaobject, and they’re one of the use cases Shopify itself calls out in its docs.
Model the definition. Build a “Size chart” template with a field for each measurement you publish: size label, chest, waist, inseam, length, and a unit field (cm or inches) so the chart reads correctly for the market it’s shown in. This is the column-headers step: you decide the shape once.
Create one entry per chart. Now add entries: “Men’s Tops,” “Women’s Bottoms,” “Kids’ Outerwear,” and so on. Each is one filled-in row that follows the same structure. This is the heart of a reusable size chart shopify setup: the chart exists as its own object, not as text trapped inside a product.
Reference it from products. Add a metaobject-reference metafield to your products, then open any product and select the chart it should use. Twelve shirts can all point at the single “Men’s Tops” entry.
Display it. The no-code route is the theme editor: add a section and connect it to your metaobject using a dynamic source. Many merchants drop it into a pop-up or an accordion on the product page so it’s there when shoppers want it and out of the way when they don’t.
One best practice: keep a separate chart per category rather than one mega-chart. A bottoms chart and a tops chart measure different things, and fit accuracy is what actually cuts returns.
The payoff is the reuse. Re-grade your medium and adjust one measurement on the “Men’s Tops” entry, and every linked product reflects it instantly. No find-and-replace across the catalog. For the exact click-by-click on building, attaching, and displaying, see our how-to guide.
Worked Example: Structured Ingredient Lists
Shopify’s docs name this one directly too: metaobjects are made for ingredient lists with nutritional data. It’s a strong fit for food, supplements, and the whole cosmetics and “clean beauty” world, where shoppers (and increasingly regulators) expect a real breakdown rather than a wall of text.
The instinct is to dump everything into one paragraph. Don’t. A paragraph isn’t searchable, isn’t filterable, and reads differently on every product. Model structured fields instead: ingredient name, function, percentage, allergen or flag, and source. Now each ingredient is typed data your theme can render consistently and your shoppers can actually scan.
A quick note on naming, because it’s a common search: Shopify ships a standard “ingredients” metafield for products, and for a simple one-off list on a single item, that shopify ingredients metafield is perfectly fine. The metaobject approach earns its keep the moment the same ingredient appears across many products.
That’s the pattern worth stealing: a shared ingredient glossary. Define each ingredient once as its own entry (hyaluronic acid, shea butter, niacinamide), then reference the same entries across every product that contains them. Update the description or the source note on “niacinamide” a single time and it corrects everywhere. For a shopify clean beauty ingredients page with overlapping formulas, this is where reuse really compounds, and it’s the natural lead-in to doing it at scale.
The SEO and AEO Payoff
This ties back to why you’re publishing at all: structured content is easier for machines to read than prose, and that helps in both classic search and the newer AI answer engines.
One caveat older guides miss: don’t build your case on FAQ rich results. Google fully deprecated them on May 7, 2026, finishing a rollback that began in 2023. What still earns rich results is Product, Review, and Recipe schema. Because your size and ingredient data is already typed rather than buried in a paragraph, it feeds cleanly into the JSON-LD those schema types use: nutrition into Recipe markup, attributes into Product markup.
For AI answer engines, Google says there’s no special schema required: what matters is that your data matches clear, visible content on the page. A labeled table of measurements or ingredients is exactly what an AI engine can extract and cite; a run-on paragraph isn’t. Structure your structured product data for shopify SEO well and you’re optimizing for both at once. Schema is a bonus; the real win is that structured content is extractable everywhere.
Doing This at Scale
A 12-product boutique can set all of this up by hand in an afternoon. A 600-SKU apparel brand with 15 size categories can’t. Neither can a cosmetics line maintaining a 200-ingredient glossary across its catalog. And size is no excuse to keep things small: a single definition now holds up to 1,000,000 entries, far more than anyone would type one at a time in the admin.
The realistic path is a spreadsheet (one column per field, one row per entry) mapped to your metaobject fields and published in a single import. That’s exactly what HeadlessDB is built for: upload your CSV and it can even propose the definition from your column headers, then drop every entry straight into your admin. No code, no developer: just your glossary or size charts, live across the whole catalog.
Wrapping Up
Treat your repeated content as content, not copy-paste. A size chart shared by forty products and an ingredient that appears across a dozen formulas both want to live as a single metaobject entry you reference everywhere: built once, edited in one spot, and structured well enough that search engines and AI assistants can read it. That’s a CMS, and it’s already in your Shopify admin.
If you haven’t set one up yet, our step-by-step how-to walks through the four-step workflow. And once your size and ingredient data is structured, the next move is putting it to work in storefront search and filters, which we’ll cover in an upcoming article. When you’re ready to do it across a real catalog instead of by hand, HeadlessDB handles the bulk import.