# AI Answerworthiness Checklist

Use this checklist when the goal is to make public content easier for humans and AI systems to trust, retrieve, and recommend.

## Answerworthiness Criteria

Check whether each flagship page:

- answers a real buyer question clearly in the first screen or two
- states who the business helps, what it does, and what it does not do
- uses specific language instead of generic category filler
- includes visible proof, examples, or operational detail that supports the claims
- gives a confident next step without sounding evasive or overhyped

If the page hides the answer behind branding language, it is not answerworthy yet.

## Citation Support

For every important claim, ask:

- what visible evidence supports this statement
- can an external system tell where the fact came from
- is the claim stable enough to stay accurate over time
- do author, business, and service details stay consistent across the page and supporting assets

Citation support is strongest when the page can stand on its own without hidden context.

## Retrieval Hygiene

Improve retrieval by checking:

- heading clarity and topic segmentation
- concise section openers that summarize the answer before details
- internal links to supporting assets, kits, and proof surfaces
- clean terminology that matches how buyers actually search and ask

The best pages are easy to chunk and easy to quote without losing meaning.

## Trust Signals

Look for:

- clear business identity
- visible author or organizational ownership
- proof modules that match the topic of the page
- language that sounds accurate and restrained rather than inflated

If the page feels polished but unsupported, it will struggle to earn trust from either people or engines.

## Monthly Review

Every month:

- review the top authority pages for outdated claims
- tighten headings that bury the answer
- add support evidence to pages that sound too abstract
- compare internal links against the newest relevant resources and kits

Treat answerworthiness like a maintenance discipline, not a one-time optimization.

## Failure Modes

- pages that are structurally clean but still vague
- FAQs with no supporting depth behind them
- entity information that drifts across pages
- internal links that never route readers to proof, calculators, or stronger guidance