Specification Table Template for B2B Sites: Markup That Crawlers Can Read
Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Specification Table Template for B2B Sites: Markup That Crawlers Can Read」 in DATA TABLE SPEC. Templates are for reference only; verify local regulations and platform rules before launch.
Industries and use cases
- Technical sites where product parameters are presented mainly as tables
- Sites that use specification tables to capture long-tail model-selection queries
- Sites that want their tables to be understood correctly by search engines and AI models
- Template sites where one specification table is reused across several product pages
Template / code snippethtml
<!-- 规格表:完整可抓取结构 -->
<table class="spec-table">
<caption>${modelCode} 主要规格</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>21</td>
<td>MPa</td>
<td>连续工作</td>
</tr>
<tr>
<th scope="row">最大行程</th>
<td>300</td>
<td>mm</td>
<td>可定制 200 / 500</td>
</tr>
<tr>
<th scope="row">外形尺寸</th>
<td>1200 × 600 × 1800</td>
<td>mm</td>
<td>长 × 宽 × 高</td>
</tr>
</tbody>
</table>
<!-- 可选:加一行"参数来源",提升可信度 -->
<tfoot>
<tr><th scope="row">数据来源</th>
<td colspan="3">厂家技术部实测,测试条件见下方说明</td></tr>
</tfoot>| Field / parameter | Type | Description and values |
|---|---|---|
| Table caption | Text | Model code plus what the table describes |
| Header row | Text | Item / value / unit / remark |
| Parameter name | Text | Marked up with th scope="row" |
| Value cell | Number | Digits only, no unit inside |
| Unit column | Text | All units kept in one dedicated column |
| Remark column | Text | Operating conditions, variants, limits |
| Data source | Text | Placed in tfoot, naming who measured and under what conditions |
SEO and structured-data notes
| Values and units in separate columns | Writing the unit inside the value cell loses the dimension during model extraction; separate columns give each field a single meaning |
|---|---|
| Parameter names use th scope="row" | This establishes the row header association, the signal parsers rely on to identify a row label |
| Caption states the model code | It is the main basis for a model to decide which product the table belongs to |
| No rowspan merging | Row spanning loses header associations in some parsers |
| Table placed before body copy | Technical parameters are the first information buyers need when selecting a model |
| Add a data source row | A "measured by the manufacturer" note is an order of magnitude more credible than an unsourced parameter table |
Compliance risk notes
- Parameters must match the actual product
- Rows must not be merged or hidden for visual neatness
- Variant parameters must be labelled so readers do not mistake them for standard values
- Test conditions must be stated, otherwise values may be applied across products
- One page must not carry identically named fields with different definitions
Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.
Modification example
<!-- Modification example: values and units in separate columns vs. combined -->
<!-- Original: unit mixed into the value -->
<tr><th scope="row">Rated pressure</th><td>21 MPa</td></tr>
<!-- Modified: value and unit in separate columns -->
<tr>
<th scope="row">Rated pressure</th>
<td>21</td>
<td>MPa</td>
<td>Continuous duty</td>
</tr>
<!-- The difference looks small, but during structured extraction:
the combined form yields a single string "21 MPa",
while the split form yields "rated pressure = 21" and "unit = MPa" separately;
the former supports numeric comparison and charting, the latter supports unit validation. -->FAQ
How many columns should a specification table have?
Four is the most stable: item, value, unit, remark. Reserve the remark column for operating conditions and variants; it is worth more than omitting it.
Must values always carry a unit?
Yes, but in a separate unit column. Mixed notation breaks parameter comparison and automatic charting alike.
Is a data source necessary?
Recommended. A single tfoot row raises credibility noticeably, especially in the trust assessment of technical buyers.
Should specification and comparison tables be kept apart?
They serve different purposes: a specification table describes one model, a comparison table sets several models side by side. Two large tables on one page interfere with each other.
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.
Related reading
Multi-Model Specification Comparison Table TemplateMaterial Comparison Table Template for Industrial ProductsTolerance Table Template and Dimension Marking RulesProduct Certification List Template and Verification PathsPackaging Specification Table Template for Export SitesNote: 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.