Why this matters

Downloads can become hidden source-of-truth conflicts

Small businesses often update the homepage, booking page, or service page first, while older downloads remain public. Search engines, AI assistants, directory editors, and customers may still find the file. If the file says “24/7 emergency service,” “free estimate,” “2024 prices,” “limited-time discount,” or an old refund policy, the business needs a safe review path before publishing more copy.

STOP PUBLISHING: do not reuse, summarize, cite, or rewrite a PDF/download claim until a human owner confirms whether the file is current, archived, replaced, redirected, or removed. Mark unsupported claims as NEEDS OWNER REVIEW.

Copy/paste PDF/download review card

Download/source name: [PDF / brochure / menu / rate sheet / checklist / lead magnet / intake packet]
Public URL:
Where it appears: [website page / email / Gumroad / directory / Google result / social / QR code]
Current owner/reviewer:
Last reviewed date:
Claim type: [pricing / hours / service area / guarantee / credential / policy / eligibility / offer / testimonial / process]
Exact claim from file:
Current approved source URL:
Conflict found: [none / stale / unclear / missing source / risky claim / duplicate file]
Customer impact if quoted:
Action: [keep / update file / replace link / redirect / archive / noindex/remove / owner review]
Rollback or expiry date:
AI-search audit query to test:
STOP PUBLISHING flag: [yes/no]
NEEDS OWNER REVIEW reason:

AI audit prompt

You are helping a small business review public PDF and download files before AI search tools quote stale facts.
Use only the supplied file notes, current source URLs, screenshots, and owner-approved facts.
Do not invent pricing, hours, credentials, service areas, guarantees, legal/privacy/refund terms, customer proof, availability, or eligibility.
For each file, return: exact risky claim, current approved source, conflict type, customer impact, safest action, whether the public file should be updated/removed/redirected, and whether the claim is STOP PUBLISHING or NEEDS OWNER REVIEW.
If evidence is missing, write UNKNOWN and ask for the source instead of guessing.

Review questions before updating the page

Does the download have a canonical replacement page, or is it still the current approved file?
Are old files linked from emails, QR codes, ads, partner pages, marketplace listings, or social bios?
Does the file mention prices, discounts, hours, emergency availability, refund terms, financing, warranties, credentials, or regulated claims?
Can the team remove or redirect the old URL without breaking customer access?
Should the replacement page include a “last reviewed” date and owner so future AI summaries know which source is current?

Safe status labels

Status	Meaning	Next action
current-reviewed	Owner confirmed the file still matches the approved source.	Add review date and keep monitoring.
stale-replace	File has outdated facts but a current source exists.	Replace file or redirect to the current page.
source-missing	Claim may be true but no approved source supports it.	Hold publishing until owner supplies proof.
remove-risky	File includes risky or unsupported public claims.	Remove/noindex/redirect and document the decision.

Product bridge

This resource supports the SEO After AI workflow: keep every quotable business fact tied to an approved source, review stale downloads before page refreshes, and keep AI tools from turning old files into customer-facing promises.

Back to the Horizon Flow catalog · Free AI prompt governance checklist