← Back to assessments

SH002 – Spec Table Recognition

Overview

Finds a specification table and validates its structure: consistent columns, non-empty, proper th headers.

Probability that AI systems use this signal: Crawlers and generative AI pipelines consume structured and visible page signals for training and inference. Assessment-specific signals (e.g. schema, canonicals, trust cues) affect how likely a page is indexed and surfaced. The probability that this assessment's signal influences AI behavior is high when the page is in a product or compliance context.

Impact on geo compliance: Passing this assessment supports geo compliance by ensuring machine-readable and visible content meet standards that reduce the risk of wrong locale, pricing, or trust in AI-generated answers. Failing can lead to non-compliant or misleading surfacing.

What We Check

  • All `<table>` elements. No tables: failed.
  • **_find_specification_table:** table with class containing "spec", or th/td text containing specification/spec/feature/property/attribute → chosen; else first table.
  • **_validate_table_structure:** row column counts (td+th per row); if max != min → "Inconsistent table structure: min-max columns".
  • **_is_empty_table:** tbody with 0 rows, or no tbody and ≤1 tr → empty. Empty: −50.
  • **_has_proper_headers:** at least one th. No th: −20. Structure issues: −30 each.

Pass / Fail and Score

  • **PASSED** if score >= 60.

How to Fix When It Fails

  • Add table with product specs; fix column consistency; add th; add data rows.

Common Issues

  • No table; empty table; inconsistent columns; no th.

Dependencies

None.

How to Verify

  • Ensure one table has th, consistent tr/td counts, and data.

Additional Resources

  • HTML table semantics; accessibility (th, scope)