LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

B2B Industrial Product Detail Page Component Specification

Section:B2B COMPONENT SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「B2B Industrial Product Detail Page Component Specification」 in B2B COMPONENT SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Industries that close deals on drawings and specifications: machining, hardware, injection-molded parts, molds, welded assemblies
  • Categories with many model numbers, fixed parameter dimensions, and a need to present each model differently
  • Sites whose product pages convert poorly and need technical parameters moved directly below the first screen
  • Sites that must serve both technical engineers and purchasing managers on the same page
Template / code snippethtml
<!-- 结构示意(HTML 语义骨架,不含具体样式) -->
<article class="pd" itemscope itemtype="https://schema.org/Product">
  <header class="pd-head">
    <h1 itemprop="name">产品型号名称</h1>
    <p class="pd-model">Model: <span itemprop="sku">MODEL-XXX</span></p>
    <p class="pd-summary">一句话说明这个型号解决什么问题、适合什么工况。</p>
  </header>

  <section class="pd-specs" aria-labelledby="specs-h">
    <h2 id="specs-h">技术参数</h2>
    <table class="pd-table">
      <caption>MODEL-XXX 技术参数</caption>
      <thead><tr><th scope="col">参数</th><th scope="col">数值</th>
        <th scope="col">单位</th><th scope="col">可选值</th></tr></thead>
      <tbody>
        <tr><th scope="row">工作行程</th><td>300</td><td>mm</td>
          <td>200 / 300 / 500</td></tr>
        <tr><th scope="row">额定压力</th><td>21</td><td>MPa</td><td>16-25</td></tr>
      </tbody>
    </table>
  </section>

  <section class="pd-certs" aria-labelledby="cert-h">
    <h2 id="cert-h">认证与资质</h2>
    <ul class="pd-cert-list">
      <li><span>体系认证</span>ISO 9001</li>
      <li><span>产品认证</span>对应型号证书编号</li>
    </ul>
  </section>

  <section class="pd-files">
    <h2>资料下载</h2>
    <ul class="pd-file-list">
      <li><a href="/files/MODEL-XXX-datasheet.pdf" type="application/pdf">
        产品规格书 (PDF)</a></li>
    </ul>
  </section>

  <section class="pd-faq">
    <h2>常见问题</h2>
    <!-- 每条同时用 FAQPage 结构化数据声明 -->
  </section>

  <footer class="pd-cta">
    <p>说明该型号可定制范围与最小起订量。</p>
    <a href="/contact/">提交需求</a>
  </footer>
</article>
Fields and parameters
Field / parameterTypeDescription and values
Product nameTextModel name + category word, no marketing modifiers
Product model / SKUTextExactly identical to drawings, quotations and packaging labels; unique across the site
One-sentence summaryText40-80 characters describing the operating conditions it fits or the problem it solves
Specification tableTableFour columns: parameter, value, unit, options; never omit the unit
Certification listListSystem certifications and product certifications listed separately, with verifiable certificate numbers
Document downloadsLink listPoint to PDFs, include the model number in the file name, avoid Chinese characters in file names
Customization rangeTextState which dimensions and materials can be changed; avoid absolute wording
Minimum order quantityNumber + unitFill in the actual figure; do not write "unlimited"

SEO and structured-data notes

SEO and structured-data checkpoints
Product structured dataname and sku must match the visible page content; when pricing is uncertain, omit the offer rather than fill in a fake price
Use a table element, not div layoutTable semantics let search engines and models recognize row-column relationships; a div + absolute-positioning table becomes unstructured text when crawled
Mark table headers with th and scopeth scope="col" and scope="row" help parsers establish header relationships
Write the model number in the captionThe table caption is the key signal a model uses to decide which product this table belongs to
Place the spec table below the first screen, before body copyTechnical parameters are the primary information in B2B purchasing decisions; placing them at the end of the page lowers the chance of being extracted
Do not clip the table horizontally on mobileWhen a table overflows on narrow screens, scroll it inside a container instead of hiding columns; hiding columns equals hiding content from crawlers

Compliance risk notes

  • Avoid unverifiable superlatives such as "optimal", "best" or "most advanced"
  • Avoid absolute claims such as "never wears out" or "100% accuracy"
  • Certification numbers must be real and verifiable; fabricated certificates are high risk in European and American markets
  • Do not publish price ranges on product pages; prices vary with configuration, and inaccurate figures invite disputes
  • Avoid "order now" CTAs; in a B2B context "submit your requirements" or "request a quote" fits the purchasing process better

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: change the spec table from "fixed four columns" to "rendered per model" -->
<!-- Original: all models share one header -->
<table>
  <caption>Technical Specifications</caption>
</table>

<!-- Modified: caption bound to the model, header carries scope -->
<table>
  <caption>${modelCode} Technical Specifications</caption>
  <thead>
    <tr><th scope="col">Parameter</th><th scope="col">Value</th>
        <th scope="col">Unit</th><th scope="col">Options</th></tr>
  </thead>
</table>

<!-- If a parameter does not apply to the current model, do not delete the whole row;
     keep the row and write the value as "N/A", so the header structure
     does not jump between pages -->

FAQ

How many columns should the spec table have?
Four columns is the most stable: parameter, value, unit, options. More columns get squeezed on mobile; fewer cannot express the options column, which matters greatly to buyers.
What if parameters differ between models?
Keep the header structure consistent and write "N/A" for non-applicable values. Columns jumping between models hurt readability and make side-by-side comparison by models harder.
Should prices be shown?
Generally not in B2B. Prices vary with configuration and quantity; publishing an inaccurate price hurts conversion and can create platform-rule problems. Use "request a quote" to guide buyers instead.
Can this component be used for non-industrial products?
Yes, but the field table needs adjusting. Consumer products usually have fewer parameter dimensions, and the certification section is often unnecessary.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.