Prompts with fact checks
Use AI to check proof, not invent it.
Add the real source files. Protect private data. Check every key result yourself.
Review proof of bot access
Add: HTTP redirects, headers, robots.txt, sitemap records, and initial HTML.
Ask for: Observed facts, likely effects, conflicts, and tests still needed.
Review the HTTP proof I provide for one public URL.
Use only the redirects, headers, robots.txt, sitemap records, and HTML I give you.
Report the page status, redirects, main URL, robots rules, H1, and main content.
Also report whether the content works without JavaScript, which schema types appear,
and where facts conflict.
For each finding, point to the exact proof I supplied.
Separate what you saw from the likely effect. Do not guess about live behavior.
End with the tests still needed. Check a case study
Add: A draft plus its source and claim table.
Ask for: A claim-by-claim risk review before sales edits.
Act as a strict research editor.
Review the case study draft and proof table I provide.
Create four columns: exact claim, proof, safest wording, and risk.
Flag date ranges that overlap, totals with no base, picked groups, and cause claims.
Also flag owner conflicts, private proof, and claims the study cannot support.
Do not improve the sales copy until each claim matches the proof. Check direct sources
Add: The draft and the cited source files or URLs.
Ask for: Source class, exact support, and safer wording where needed.
Find the cited source for each fact in the draft I provide.
Label each source as official, reviewed research, direct result, news, expert view,
or unsupported.
Say whether it supports the exact words. Offer a narrower claim when support is weak.
Do not invent links. Do not use general knowledge to fill missing proof. Check names and facts
Add: The public pages and profiles to compare.
Ask for: One conflict table and a proposed main fact record.
Compare the public pages I provide for one person or group.
List names, current roles, start dates, places, company ties, profile links,
degrees, contact details, and service claims.
Make a conflict table with the source URL and exact text.
Suggest one main fact record. Do not treat schema as outside proof. Put the answer first
Add: A draft plus its real source material.
Ask for: A short direct answer and an evidence-led outline.
Find the main reader question in this draft and the choice it should help them make.
Write a direct answer in two to four sentences. Include the most important limit.
Then suggest headings that support the answer with the proof I supplied.
Include examples, limits, method, and next step.
Keep uncertainty. Do not add facts or sources. How to use these safely
- Remove private data unless the tool and account are approved for it.
- Give the model the real proof. Do not ask it to recall a live audit.
- Check page status, text, sources, math, and dates on your own.
- Save the prompt, inputs, model, mode, date, output, reviewer, and fixes.
- Treat the result as a helper's review, not a fact source.