Why this matters
Customer promises need source-of-truth wording
Guarantees and warranties are conversion assets, but they can create trust and compliance risk when the scope is unclear. A vague sentence like “100% satisfaction guaranteed” can be misread by buyers, sales staff, AI assistants, and answer engines unless the site explains exactly what is covered.
This checklist helps a small business publish policy facts in a way that humans can verify and AI search tools can quote without inventing refunds, timelines, or outcomes.
Copy/paste artifact
Guarantee and policy proof worksheet
Business / website:
[company name]
Reviewer / owner:
[name]
Review date:
[date]
Canonical guarantee / warranty / policy page:
[URL]
1. Promise inventory
List every customer promise that appears on the website, sales page, quote, receipt, FAQ, checkout page, email template, or ad.
Promise name:
[exact public wording]
Type:
[ ] workmanship warranty
[ ] product warranty
[ ] satisfaction guarantee
[ ] refund / return policy
[ ] service window / response-time promise
[ ] price-match / price-lock promise
[ ] replacement / rework promise
[ ] cancellation / reschedule policy
[ ] other: [describe]
Where it appears:
[URL / page / template]
2. Scope and limitations
What is covered:
[plain-language scope]
What is not covered:
[exclusions]
Who is eligible:
[customer/job/product/service requirements]
Time window:
[number of days/months/years or not applicable]
Required customer proof:
[receipt, photos, service record, job number, inspection, etc.]
Approval owner:
[name / role]
3. Source of truth
Internal policy source:
[document / system / owner]
Public policy URL:
[URL]
Last reviewed:
[date]
Next review date:
[date]
4. Approved customer wording
Short version:
[paste exact approved sentence]
Long version / FAQ answer:
[paste exact approved paragraph]
Required disclaimers or conditions:
- [condition]
- [condition]
5. Buyer questions to answer
- What exactly is promised?
- What is excluded?
- How long does the promise last?
- How does a customer request help?
- What proof does the customer need?
- Who approves exceptions?
- Does this vary by location, service, product, or vendor?
6. AI-search stop rules
Do not publish, summarize, or mark up this promise until a responsible human verifies:
[ ] exact promise wording
[ ] coverage, exclusions, and eligibility
[ ] time window and request process
[ ] source-of-truth policy URL or internal record
[ ] responsible owner for approvals/exceptions
[ ] no invented refunds, free replacements, warranty length, approvals, urgency, legal terms, customer outcomes, compliance claims, or guaranteesAI assist prompt
Use AI to flag gaps, not create policy promises
You are reviewing a small-business website for guarantees, warranties, refund rules, service promises, and policy language.
Use only the verified facts pasted below.
Do not invent refunds, warranty length, free replacements, approvals, legal terms, compliance claims, customer outcomes, response windows, exclusions, or urgency.
Return:
1. customer promises that need clearer source-of-truth wording,
2. missing scope, eligibility, exclusions, or time-window details,
3. places where sales copy may overstate the policy,
4. buyer questions the guarantee page should answer,
5. claims that need owner/legal/compliance review,
6. a safer guarantee-page outline with human-review notes.
Verified policy facts:
[paste]
Current website / sales copy:
[paste]Implementation
Make one canonical page before spreading promises across the site
- Inventory guarantees, warranties, refund rules, service promises, and cancellation terms across the site.
- Choose one canonical policy page or trust-center section as the source of truth.
- Rewrite sales pages, FAQs, checkout copy, and support templates so they point back to the same approved wording.
- Add review dates and an owner so stale guarantees do not linger after policies change.
- Only add FAQ/schema or policy markup after a responsible human confirms the wording.
Human review rule: policy promises should be approved by the owner, operations lead, support lead, or legal/compliance reviewer. AI can find vague language and organize facts, but it should not create guarantees, refunds, warranty terms, or exceptions.
Next step
Connect guarantees to support and proof pages
After the guarantee page is clear, use the support-policy checklist, the trust-center checklist, and the claims inventory checklist so customer promises stay consistent across the site.
For the complete framework, worksheets, and implementation sequence, see SEO After AI.