1. Source-expiration review card
Copy/paste fields:
- Page, FAQ, schema block, chatbot answer, or AI-search claim being reviewed:
- Claim type: price / promotion / guarantee / service area / hours / availability / policy / credential / partner / case study / review proof / compliance statement:
- Current public wording:
- Source URL or internal document:
- Source owner and reviewer:
- Published date, last reviewed date, and expiration/review date:
- Status: current / stale / expired / conflicting / missing source / needs owner review:
- Affected surfaces: page copy, title/meta, FAQ, schema, GBP, directory listing, chatbot answer, llms.txt, resource pack, sales deck:
- Safe replacement wording, if approved:
- Rollback or redirect needed:
2. What to update before AI tools quote the old answer
- Expired offers: remove or mark expired coupons, seasonal pricing, financing notes, and limited-time language before AI summaries reuse them.
- Stale policies: check cancellation, refund, warranty, privacy, accessibility, and service-limit wording against the source owner.
- Old proof links: repair 404s, moved case studies, changed partner pages, or outdated testimonials before using them as citation anchors.
- Conflicting pages: choose one canonical source before updating schema, internal links, and answer-engine prompts.
3. AI audit prompt
You are auditing a small-business website for AI-search source expiration risk.
Use only the source-expiration review card below. Do not invent current prices, policies, availability, guarantees, certifications, partnerships, legal/compliance claims, hours, or service limits.
Review card: [paste fields]
Return:
1) claims that are safe to keep;
2) claims that need owner review;
3) claims that should be removed, updated, redirected, or marked expired;
4) affected surfaces to update: page copy, FAQ, schema, GBP, chatbot, directory, sitemap/internal links;
5) a customer-safe replacement sentence only when the source is current.
If the source is missing or expired, write NEEDS OWNER REVIEW instead of a final answer.STOP PUBLISHING
- Do not let AI publish or rewrite dated claims without a current source owner and review date.
- Do not invent discounts, hours, eligibility, guarantees, coverage, certification status, partner status, legal/compliance language, customer proof, or availability.
- Stop if two public pages conflict and no owner has chosen the canonical source.
- Use NEEDS OWNER REVIEW for source gaps, expired offers, dead proof links, or policy-sensitive promises.
4. Weekly review questions
- Which AI-search-visible pages contain dates, deadlines, policy promises, or proof links with no owner?
- Which pages did AI tools or chatbot drafts quote after the source expired?
- Which source types need a recurring review calendar: offers, policies, services, hours, proof, partners, or FAQs?
- Should SEO After AI add a source-expiration appendix with source owner, review date, affected surface, and rollback fields?
Product bridge: Pair this with SEO After AI source freshness, policy review calendar, broken-source repair, and canonical URL worksheets so AI-search optimization stays proof-safe instead of becoming stale-claim amplification.