When to use this checklist
Use it when a small business sells, installs, supports, compares, or describes products where wrong specifications could create returns, safety issues, warranty disputes, compatibility confusion, or customer trust problems.
- Product pages need exact dimensions, weights, materials, capacity, finish, model, version, or variant details.
- AI search tools, shopping summaries, or chatbots may compare products using stale or mixed sources.
- Support teams answer compatibility, installation, replacement, care, return, or warranty questions from specs.
- Catalog, marketplace, brochure, or PDF specs need an owner-reviewed source card before being quoted by AI.
Copy/paste product specification source card
Product specification source card
Product name: [official product name]
Model / SKU / variant / region: [exact model, SKU, bundle, size, color, region]
Specification source: [manufacturer page / internal spec sheet / approved PDF / supplier quote / test record / other]
Source version / date / URL: [version, date, URL]
Spec category: [dimensions / weight / materials / capacity / compatibility / certification / care / warranty / safety / other]
Approved specification wording: [paste exact approved wording]
Measurement units and tolerance: [inches/cm, lbs/kg, tolerance, measurement method]
Compatibility limits: [products, accessories, vehicles, devices, materials, regions, exclusions]
Certification / compliance / test proof: [source, certificate, rating, reviewer, not applicable]
Customer-safe public wording: [exact wording approved for product page, FAQ, support macro, or AI-search answer]
Reviewer and review date: [owner / product manager / support lead / legal/compliance]
Next review date: [date]
STOP PUBLISHING if dimensions, units, materials, capacity, compatibility, certification, SKU/model, safety, warranty effect, or approved wording is unknown.
Customer-safe answer template
For [product/model/SKU], the current approved specification is: [approved public wording]. This applies to [variant/region/version] and is based on [source title/version/date]. If your product label, accessory, use case, installation condition, or region is different, please contact support before relying on this specification.
Do not add guessed units, rounded dimensions, unofficial marketplace notes, competitor comparisons, forum claims, or supplier availability unless they are approved in the source card.
AI audit prompt for product specs
You are auditing a product-specification answer for AI-search readiness. Use only the source card below. Do not invent dimensions, units, tolerances, materials, compatibility, certifications, ratings, safety claims, warranty outcomes, availability, substitutions, model numbers, or competitor comparisons. If a required source is missing, output NEEDS HUMAN REVIEW.
Source card:
[product name]
[model/SKU/variant/region]
[spec source/version/date]
[approved specification wording]
[measurement units/tolerance]
[compatibility limits]
[certification/compliance proof]
[customer-safe wording]
Return: (1) safe public answer, (2) unsupported claims to remove, (3) missing source fields, (4) AI-search query tests to run, and (5) STOP PUBLISHING triggers.
Human-review stop rules
- STOP PUBLISHING if a spec could affect safety, installation, returns, warranty coverage, regulated claims, sizing, compatibility, product substitutions, or customer liability.
- Do not let AI merge specs across similar models, product generations, colors, sizes, bundles, regions, third-party marketplace listings, or discontinued versions.
- Do not claim a product is compatible, certified, waterproof, food-safe, child-safe, commercial-grade, repairable, compliant, or warrantied without approved proof.
- Review the source card after every supplier update, model/SKU change, product-page revision, manual/spec-sheet update, recall/safety notice, or marketplace listing change.
This is a practical free resource from Horizon Flow. The paid SEO After AI playbook expands this source-control approach into AI-search visibility audits, proof pages, schema/entity checks, freshness workflows, and answer-engine-safe website improvements.