Goal: identify broken proof links and repair them with owner-approved source replacements before website pages, schema, FAQs, AI drafts, or marketplace profiles repeat unsupported claims.
STOP PUBLISHING: do not replace a broken source with a guessed fact, copied competitor wording, archived page, or AI-generated citation. If no current source supports the claim, mark the claim NEEDS OWNER REVIEW.
Copy/paste broken-source repair log
| Field | What to enter | Example |
|---|---|---|
| Claim or page section | The exact claim, FAQ, proof block, or page area using the source. | Emergency availability FAQ on HVAC service page |
| Current source URL | The linked URL that should support the claim. | https://example.com/old-hours.pdf |
| Status checked | 200, 301/302, 404, 410, soft-404, login wall, changed content, or unclear. | 404 |
| What changed | Observed fact only. Do not guess why. | PDF no longer loads; current hours page exists elsewhere. |
| Affected surfaces | Pages, schema, FAQ, GBP, product page, directory listing, email template, or lead magnet using the claim. | service page, FAQ schema, quote template |
| Replacement source | Current owner-approved URL/document, or NEEDS SOURCE. | https://example.com/service-hours |
| Owner/reviewer | Person who can approve the updated wording. | Owner / ops manager |
| Safe wording | New wording using only the approved source. | Emergency requests are reviewed after hours; availability varies. |
| AI instruction | What AI tools must not infer. | Do not invent 24/7 availability, pricing, response times, or guarantees. |
| Next check date | When to re-test the source and AI answer. | 2026-06-15 |
AI audit prompt
You are auditing broken proof links for AI-search visibility.
Inputs:
- Website pages or page sections to audit: [PASTE]
- Current source URLs and screenshots/status codes: [PASTE]
- Approved replacement sources, if any: [PASTE]
- Claims that need owner/legal/compliance review: [PASTE]
Task:
1. List every claim that depends on a source URL, document, directory listing, review, policy, price, proof, or third-party citation.
2. Classify each source as current, redirected, broken, changed content, login-gated, unclear, or missing.
3. Suggest only proof-safe replacements using provided sources.
4. If evidence is missing, write NEEDS OWNER REVIEW instead of inventing a source or claim.
5. Do not invent response times, prices, credentials, guarantees, reviews, ratings, service areas, discounts, availability, legal terms, or competitor facts.
6. Return a table with: claim, current source, status, affected surface, replacement source, safe wording, AI instruction, owner, next check date.Repair workflow
- Export the top service, offer, pricing, FAQ, proof, policy, and booking pages that AI tools may summarize.
- Open every source link manually or with a link checker; record the real status instead of assuming old links still prove the claim.
- Map each broken or changed source to the exact page, schema block, FAQ, directory listing, or template that depends on it.
- Replace only with a current, owner-approved source. If no source exists, soften or remove the claim.
- Re-run the source check and a small set of AI-search buyer questions after the fix is live.
Related resources: AI Search Source Citation Log, AI Search Source Freshness Monitor, and Redirect and Status Code Checklist.
Want the full AI-search implementation kit?
SEO After AI expands this into a practical playbook for source maps, entity clarity, proof, schema, content refreshes, and answer-engine-ready pages.