How should we structure a materials / sourcing proof page so AI and buyers trust it?

What this page is (and is not)

The materials proof page is a fact hub: materials, sourcing geography, certification scope, and known exclusions. It is not the PDP (buy), not the full impact report (appendices), and not Product schema (machine layer on each SKU). Link those together; do not duplicate conflicting numbers.

Recommended page outline

1. H1: question-led ("What are our products made of?" or "Materials and sourcing proof")
2. Quick summary: 50 to 120 words naming primary materials and how often you update the page
3. Materials table: material / % / used on which SKUs / notes
4. Certifications: name, scope (SKU / facility / company), license or registry link, expiry
5. Sourcing: country or region for key inputs; suppliers named only when allowed
6. Exclusions: what you do not claim (e.g. packaging tape, trims)
7. FAQ: 4 to 8 buyer questions mirrored in FAQPage schema
8. Last reviewed date in visible HTML

Attribute rows that earn trust

Row	Good cell	Bad cell
Fiber / material	70% post-consumer recycled polyester (body); 30% elastane	Eco fabric
Certification	GOTS organic cotton [style list]; license [ID] · registry link	Certified sustainable
Geography	Yarn spun in [country]; cut and sew in [country]	Ethically sourced worldwide
Packaging	Primary mailer is [X]% recycled paper; tape not plastic-free	Plastic-free shipping
Update cadence	Reviewed [month year]; next review quarterly	Always improving

Align packaging lines with packaging claims. Keep company B Corp on About; SKU certs on this hub and PDPs per cert marketing.

AEO and schema rules for the hub

• Keep tables and answers in the initial HTML (not client-only accordions that fetch empty).
• Add FAQPage that matches visible FAQ text.
• Do not invent a second conflicting materials story in JSON-LD; PDPs should use Product schema that mirrors this hub.
• Internal-link from PDP proof rows, comparison pages, and FAQs to this URL with consistent anchor text.
• If you use a Digital Product Passport QR, link the hub as the human-readable companion, not a substitute for facts. See DPP guide.

Claim hygiene on a proof page

• No vague "eco-friendly materials" without the table facts above.
• Cert scope must match reality (product vs facility vs company).
• EU Markets visitors: avoid generic green adjectives that fail EmpCo-era marketing rules; see EU green claims.
• Date the page; stale cert IDs destroy trust faster than no page.

Citation and buyer QA

1. Prompt set: "what is [brand] made of", "is [SKU] GOTS", "[brand] recycled content %", "[brand] vs [competitor] materials"
2. Surfaces: Perplexity, ChatGPT, Google AI Overviews
3. Human check: can a CS agent answer from the hub without opening a spreadsheet?
4. Mismatch log: hub vs PDP vs Merchant Center vs schema

Run monthly with the visibility audit method.

Frequently asked questions

How should eco brands structure a materials proof page?

Use a question-led H1, short summary, materials and cert tables with scope and links, exclusions, FAQ schema, and a visible last-reviewed date. Link from every hero PDP.

Should proof live only on PDPs?

PDPs need a scannable proof row. The hub holds the full matrix so answer engines and CS share one source of truth without stuffing every PDP.

Do we need FAQPage on the materials hub?

Yes for research questions ("is it GOTS?", "where is it made?"). Keep answers in the HTML and mirror them in JSON-LD.

How often should we update the page?

At least quarterly, and whenever certs, suppliers, or hero SKU materials change. Show the review date on the page.

How is this different from Product schema?

Schema encodes buyable SKU facts for shopping answers. The materials hub is the human- and citation-friendly explanation layer those SKUs should match.