Direct answer: Put essential specifications in accessible HTML, state units and conditions, distinguish typical from guaranteed values, connect the data to the correct product and application, and provide the current controlled document for verification.
A specification is a scoped statement
A value without its product, configuration, test condition, unit, revision, and limitation can mislead. The page should answer what the number describes, when it applies, who controls it, and where the buyer can verify the current version.
Use a two-layer document model
The public HTML page should contain the facts required for discovery and initial qualification. A controlled PDF, drawing, certificate, or data sheet can preserve formal formatting and revision control. Neither layer should be the only usable source.
Image-only tables are difficult to search, quote, translate, compare, and update. Rebuild important tables as semantic HTML with text headings, row labels, units, and notes. Provide the original controlled document beside the table.
Fields every specification table should carry
- product family and exact model or part number;
- property or dimension name;
- value or supported range;
- unit and measurement system;
- test method or reference standard when relevant;
- material, configuration, and environmental conditions;
- tolerance or acceptance criteria;
- typical, nominal, minimum, maximum, or guaranteed status;
- document revision and last review date;
- exclusions and route for engineering confirmation.
Write for comparison without overclaiming
Use consistent terminology and units across product pages. When US and European buyers use different units or category terms, show conversions and preserve the controlled source value. Do not silently convert a typical value into a guaranteed limit.
Explain why a specification matters to the application. A buyer is more likely to ask “which material works in this environment?” than search for an isolated number. Connect properties to operating conditions, selection criteria, failure modes, and verification steps.
Give tables stable context
A specification page needs a descriptive title, direct summary, canonical URL, product relationship, internal links, update date, and named owner or reviewer. A downloadable file called document-final-v7.pdf carries less meaning than a stable page and well-named controlled document.
Structured data must match visible facts
Use Product structured data only on real product pages with matching visible information. Do not mark an industry service page as a product. Organization, Article, BreadcrumbList, and FAQPage can support the appropriate pages, but markup never substitutes for accurate content.
A publication checklist
- Confirm the exact product and configuration.
- Compare HTML values with the controlled source.
- Label typical and guaranteed data correctly.
- Verify units, conversions, and conditions.
- Add limitations and engineering-review language.
- Record the revision, update date, and owner.
- Test the page in search, mobile, and machine-readable views.
Related Xindar pages
Sources
- NIST Manufacturing Extension Partnership, Supplier Scouting. Accessed September 1, 2026.
- Google Search Central, Structured Data General Guidelines. Accessed September 1, 2026.
- ISO, ISO 9000 family — Quality management. Accessed September 1, 2026.
Editorial note: Website specifications are informational unless the manufacturer explicitly incorporates them into a controlled commercial or technical agreement.