Evidence behind product claims

Product claims and evidence checks

A product claim is only as useful as the evidence behind it, and a claim without a source is a buying question your page can’t yet answer. Hasmord brings product claims and their sources together, shows the automated matching result for each one, and identifies what still needs confirmation by a person who knows the product.

Last updated September 14, 2026

Hasmord fact check for a demo product: claims checked independently, backed by your own page, in conflict, or without enough evidence yet, each with the source it needs.
Fact check in Hasmord: each claim and the evidence behind it (demo workspace).

Why a claim needs more than a label

A product page says "suitable for outdoor use". A shopper, or an AI assistant answering for one, needs to know more: does it hold up in rain, what test says so, and does that test apply to this model? A claim that answers those questions is easier to understand, compare and repeat accurately. A claim that does not is just an adjective.

Evidence checks are part of a product data audit. This page explains how they work.

How an evidence check works

  1. Find the claims. Performance, suitability, compatibility and certification statements on the product page.
  2. Attach sources. Spec sheets, test reports, certificates, manuals or manufacturer pages that you provide or that the page links.
  3. Compare the claim with the source. Hasmord compares the wording of the claim with the source text and gives a first-pass status.
  4. Confirm with a person. Automated matching is a starting point. Someone who knows the product confirms the status and decides what to change.
StatusMeaning
ConsistentThe source supports the claim as written.
PartialThe source supports part of the claim, or a narrower version of it.
ConflictThe source says something different from the claim.
InsufficientThere is not enough in the source to judge the claim.

A worked example

Illustrative example. The product, fields and sources below are invented to show the format of a report. They are not a customer result.

Product: Example hiking jacket, model HJ-3. Claim on the page: "Fully waterproof for any weather."

CheckWhat was found
SourceA fabric test report linked from the page.
Does it match this model?The report covers the fabric used in model HJ-2. The spec sheet says HJ-3 uses the same fabric, but the seams were changed.
Does it support the wording?The report gives a water-resistance rating under a named test method. It says nothing about "any weather".
StatusPartial — the fabric result is supported; "fully" and "any weather" are not.

Before: "Fully waterproof for any weather."

After: "Waterproof fabric, rated [rating] under [test method] (fabric test report, linked). The same fabric is used on HJ-2 and HJ-3; HJ-3 seam taping has not been tested separately."

The rewrite is less dramatic and more useful: it says what was tested, which model it applies to, and what is still unknown.

What makes a source usable

What evidence checks do not do

From AI answers to sales

Backing a claim with a source is one step, not the result. What matters is whether the buyer’s question was answered well enough to move them toward a purchase, and what happens next. Today you can follow AI answer checks, AI referral visits in Google Analytics 4, and the leads and opportunities in Hasmord’s CRM, each with the buyer questions behind it. The questions buyers raise in sales conversations point back to the product information: add evidence, sharpen the claim, then see how the market and sales respond.

Hasmord is the AEO-native sales platform. Buyers ask questions across AI assistants, search, and sales conversations. Hasmord uncovers where your answers about your products and services fall short, turns evidence into better answers, finds potential customers for you, and connects every lead to your sales process.

Find your product opportunities Start free

Related: product data audit · why isn't AI recommending my product? · AEO tracking · plans and limits.

Frequently asked questions

What is a product evidence check?

A check that connects a product claim to a source, confirms the source applies to that product and model, and marks whether the claim is consistent with it, partly supported, in conflict, or not yet supported.

Does Hasmord decide whether a claim is true?

Hasmord gives a first-pass status by comparing the claim with the source text. A person who knows the product confirms it and decides what to change.

What if I do not have a source for a claim?

Then the claim is unconfirmed. The usual options are to add a source, narrow the claim to what you can support, or remove it.

Is this a general knowledge base?

No. Evidence checks focus on the claims on your product pages and the sources behind them.