Product Records vs Product Guidance

Record or guidance? A quick test

A product record identifies what is listed and how it fits into the catalog. Product guidance tells a visitor how to interpret, prepare, administer, evaluate, or apply a product. Strand Bio product pages are designed as records. A useful editorial test is to ask whether a sentence describes a catalog field, navigation path, checkout step, or policy boundary. If it does not, it may belong outside the public record.

• Record language identifies fields such as size, class, category, price, and access status.
• Navigation language explains category, price-list, article, and policy links.
• Checkout language explains cart review, shipping, tax, and payment flow.
• Guidance language is excluded from product records.

What belongs in a product record

A complete catalog record can include structured data without becoming guidance. The product name identifies the listing. Vial size defines the offered size. Molecule class and category support navigation. Price per vial supports commercial comparison. Access status explains checkout path. Related products and articles help visitors move through the catalog. Policy links explain boundaries. These elements are appropriate because they describe the record and the purchasing workflow.

What changes a page into guidance

A page changes character when it begins telling visitors how a product should be used, prepared, administered, evaluated for outcomes, or interpreted in a human or veterinary setting. That type of content exceeds the role of a public catalog record. Even when technical terminology appears in product names or molecule classes, the page should not extend that terminology into procedural or outcome-oriented language.

Why the separation improves usability

Separating records from guidance makes the site easier to navigate. Visitors know that product pages provide catalog fields, category pages group related records, the price list supports comparison, and policy pages state boundaries. This reduces the burden on each product page. It can be detailed without being expansive in the wrong direction, and it can be useful without presenting unsupported claims.

Practical editorial controls

A useful editorial test is to ask whether each sentence identifies a catalog field, explains a navigation path, clarifies checkout logistics, or states a boundary. If it does not, the sentence may be outside the catalog scope. This test is especially important for pages that attract broad search interest, where unsupported interpretation can easily enter copy through seemingly harmless explanations.

Where this fits in Strand Bio

Strand Bio uses product-specific overview sections, specification panels, related records, FAQ snippets, and resource links to make product pages more complete while keeping them catalog-bound. The purpose is not to make pages thin; it is to make them precise. Detailed record architecture can coexist with strict limits on use guidance.