A useful record includes the source URL, what claim it supports, the affected articles and the last factual review. A successful link check only shows that a URL responded. (Google guidance on generative AI content ↗)
Jump to a section
Finding every article affected by a changed rule
Suppose two payment guides rely on Stripe’s documentation for which card a retry charges. The registry connects that source to the exact payment-method claims in both guides. A documented change then identifies two claims to inspect, rather than requiring an editor to search every article for the word “Stripe.”
A source list does not verify itself
Record the scope of a source’s evidence. Product documentation may explain how a setting works without proving that it increases revenue. If a source changes or disappears, the editor needs the claim relationship and prior evidence to decide whether to revise, qualify or remove the claim.
Make a source entry useful after the story changes
Store the document, the section used, and which claim it supports. A link that still opens may lead to guidance that has changed. The record should let the next reviewer find the claim and decide whether the current evidence still supports it.