When a separate page is justified
Create an evidence page when one maintained explanation supports many products: ingredient glossary, garment measurement method, device compatibility matrix, warranty terms, or material certification.
Do not move the decisive answer off the product page. The product should summarize the fact and link to depth.
Three models
Rhode ingredients: product page retains complete INCI list; supporting ingredient page explains terminology without turning presence into medical efficacy.
Gymshark sizing: product page retains declared fit and available sizes; a measurement page explains how to measure. Reviewer “runs large” remains attributed to reviews.
Ring compatibility: product page retains power and Wi-Fi requirements; a matrix can compare device generations and accessories.
Page structure
- scope and applicable products
- last reviewed date
- normalized fact table
- exclusions and regional differences
- evidence or policy source
- change history
- canonical links back to affected products
Shopify implementation
Use metaobjects for reusable records. Reference them from product metafields, then render a concise product summary plus link.
Do not manually copy current price or stock into an evidence page.
Verification
curl -sSL https://example.com/pages/compatibility -o evidence.html
rg -ni 'last reviewed|not compatible|2.4 GHz|product' evidence.html
Check that every linked product is public and that product pages link back with descriptive anchor text.
Failure modes
- generic “learn more” anchor
- matrix mixes regions without labels
- ingredient page makes unsupported health claims
- size chart lacks units or garment/body distinction
- evidence page becomes stale while products change
Acceptance criteria
The page has a defined scope, owner, review date, explicit exclusions, and product links. Product pages remain the authority for selected offer facts.
Community discussion
Add to the article
Ask a technical question, share a storefront result, or challenge a conclusion with evidence.