How to audit a source cited in an AI answer
Check whether a cited page is current, relevant, and consistent with the answer that cited it.
On this page
A citation tells you that a source appeared with an answer. It does not certify that the page is current, authoritative, or relevant to the whole answer. Audit the page before you use it to explain an AI response, change your public profile, or describe evidence to someone else.
This is a page-level review. It is different from tracing one statement to a passage. Here, you are asking whether the source itself is a sound piece of evidence for the topic at hand.
Open the page and record what it is
Start by saving the URL as it appears, the page title, the publisher or owner, and the date you opened it. Then identify the page type: official biography, report, journalistic article, directory listing, event page, personal portfolio, or something else.
The page type shapes the questions you ask. A professional association profile may establish membership. It may not establish the services a person currently sells. A news article can document what happened at the time it was published, while an old event listing may only show that a session once existed.
OpenAI’s ChatGPT search guidance explicitly warns that citations can be incomplete, outdated, or incorrect. It recommends opening cited sources, checking that they support the answer, reviewing when they were published or updated, and using authoritative sources when accuracy matters. OpenAI’s guidance
Check provenance and date
Look for an author, publisher, publication date, update date, editorial policy, and a way to contact the publisher. You will not find every field on every page. Record what is present rather than inventing a confidence score.
Ask who is making the factual assertion. A person’s own site can be the best source for what that person currently offers. A regulator, credential issuer, or employer may be a better source for a qualification or role. A page that copies a biography without naming its source offers less support than the primary profile it copied.
Dates need context. An undated portfolio page may be accurate, but you cannot treat it as proof of a current offer without another current signal. An article dated 2021 can be a solid source for a 2021 event. It cannot, by itself, establish a 2026 title or service.
Test relevance against the answer
Put the page beside the returned answer. Does it cover the same person, work, geography, and timeframe? A source can be reputable and still be irrelevant to the particular claim.
Here is an illustrative source audit:
| Field | Illustrative note |
|---|---|
| AI answer claim | “Amina Patel advises hospital teams on patient-journey research.” |
| Page type | Byline page on a health design publication |
| Owner and date | Publisher named; article dated 2024 |
| Direct support | Byline says Patel wrote about patient-journey research |
| Missing support | No evidence that Patel currently advises hospital teams |
| Review result | Relevant background, but insufficient support for the current advisory claim |
| Next action | Look for Patel’s current professional page or an official speaker bio |
The review does not prove why the system cited the page. It only describes what a reader can establish from the page.
Look for page quality problems
Keep the checks plain. Is the page accessible without a private login? Does the title match the content? Are the links working? Is the content clearly attributed? Does the page show signs of copying, stale contact details, or a rewritten description that conflicts with a first-party source?
Google’s people-first guidance encourages useful, reliable content with clear sourcing and background about the author or site where readers would expect it. Use that as a reading standard for a public page. It does not predict whether Google or another AI engine will cite the page. Google’s people-first guidance
If the page makes a material claim about you, save a screenshot or archived copy only when you have a lawful, practical reason to retain it. For routine reviews, a URL, review date, and concise note are usually enough.
Use a short source audit card
Copy this card into your evidence record:
| Field | Record |
|---|---|
| Source URL | [full URL] |
| Page title and type | [title and page type] |
| Publisher or owner | [named publisher, person, or unknown] |
| Date | [published, updated, or no date found] |
| Claim checked | [complete sentence from the AI answer] |
| Relevant passage | [quotation or accurate note] |
| Scope limits | [person, date, location, or service detail not established] |
| Result | [supports, partly supports, unrelated, or unverifiable] |
| Review date | [date] |
The result is a record for a human reader. It is not a model of an engine’s ranking system, and it should not be used as a personal credential merely because a source appeared in an answer.
Next, use Trace an AI citation to the exact claim it supports when a single sentence needs closer checking. Keep a short list of the pages you control when your own public information needs maintenance.