Built for the next era of business discovery.
中国企业出海Partner with us
Home / Content
Content

The brand evidence checklist

A practical guide to the facts and proof your website should make easy to verify.

TANTU AI Research & Insights · 16 September 2026 · Practical guide

Name the business consistently

Use the correct legal operator, public brand name, products and service categories. If a brand has several names or languages, explain the relationship so a reader can identify the same organization across pages.

Describe what is available

State what the product or service does, who it serves and where it is available. Separate current delivery capability from a future ambition. An overseas reader should not have to infer that domestic coverage applies to their country.

Connect claims to support

A performance statement needs a defined period, method and source. A customer logo or quotation needs permission and a clear relationship. When evidence is not available, use a factual description of the work rather than an unsupported superlative.

Give important facts an owner

Assign a responsible person and review date to product specifications, pricing, location information and availability. Put the same approved information into sales materials and website updates.

Publish in a useful form

Use accessible text, descriptive headings and internal links that help a reader examine related information. Keep structured data consistent with the page. A fact register becomes valuable when it improves the actual customer experience.

Decision summary

Build brand evidence around claims a buyer needs to verify: identity, capabilities, availability, delivery responsibilities and supported results. Give each material claim an exact wording, a source, an approval owner and a review trigger. Publish only what the evidence supports, with the relevant limits visible. Keep unverified statements out of public copy until they are resolved. A usable evidence register also identifies every page that depends on a fact, so a product or commercial change can be corrected across the website and its language versions.

Keep a claim record that writers can use

A claim record should preserve the approved sentence, evidence location, scope, owner, approval date and affected pages. Add a status such as approved, awaiting verification or withdrawn. The scope field explains where the claim applies: product version, market, customer type and measurement period where relevant. Permission to publish a customer reference is a separate check from whether its underlying information is accurate.

Hypothetical example: “supports offline orders” is too broad if only selected functions work without a connection. The record should identify those functions and their limits using approved product documentation. Until that review is complete, the writer should describe the verified workflow or leave the claim unpublished. Making the sentence more cautious does not replace checking whether it is true.

Trace a changed fact to the pages it affects

When a fact changes, search the page inventory for every dependent claim, including comparison tables, frequently asked questions and translated versions. Correct the source register first, assign the page updates and record which versions remain unresolved. A review date is useful, but a product release, changed service area or revised commercial term should also trigger a review.

Prioritize changes by buyer consequence. Incorrect availability, compatibility or price information can change a purchasing decision and should be resolved before stylistic improvements. Retain the previous wording and the reason for the correction in the internal record. Recheck sampled answers separately where relevant: updating an owned page does not establish when an external source or an AI answer will reflect the new information.

Turn the insight into a focused plan.

Apply these principles to your market, evidence and customer journey.

Discuss your priorities