Citations make claims inspectable
Editorial trust comes from an accountable process: a reader can tell what the page claims, where a factual assertion came from, who wrote it, when it was reviewed, and what its limits are. Citations do not compel an AI product to use a page. They do help a person test whether the page deserves attention.
Prefer a primary source for a factual claim: the statute for a legal rule, the specification for a technical behavior, the product documentation for a stated feature, or the original study for a reported result. Use a reputable secondary explanation when it adds interpretation, and label it as such. Do not cite a search-result snippet, an unsourced social post, or a competitor’s summary as proof.
Cite close to the claim
Put a concise link close enough that a reader can see which statement it supports. Explain the relevance when it is not obvious. A source list at the end is useful for discovery but cannot repair ambiguous attribution in the body. Keep quoted text short, accurate, and necessary; paraphrase in your own words and preserve the original meaning.
Consider a fictional payments company writing “Our checkout supports 3D Secure.” That statement needs a link to current product documentation and perhaps a note identifying markets or card flows where the behavior applies. If the page says “3D Secure reduces fraud,” link to an appropriate authority and avoid claiming a percentage unless the source and setting establish it. The editorial reviewer should check both links after the page is published.
Google’s people-first documentation asks whether content presents information in a way that makes readers want to trust it, including clear sourcing and information about the author or publisher. Use the full guidance as a self-review, not as a formula. A transparent citation is useful even when a provider’s selection systems are unknown.
Build a lightweight review process
Mark each factual claim as primary-source, first-hand observation, informed recommendation, or opinion. For first-hand observations, state the test version, date, and conditions. For an expert recommendation, name the qualification and explain the reasoning. Require an editor who did not draft the page to test high-impact claims, calculations, links, and the headline’s scope.
Use durable descriptive links. HTML links should identify the destination for people as well as machines; W3C’s HTML link material describes the basic relationship. Avoid vague “click here” links where the label can say “payment authentication documentation.” Update or remove a citation when it no longer supports the exact wording.
Common mistakes
- Citing many sources without connecting any to a particular assertion.
- Using a vendor claim as independent evidence.
- Updating a date while leaving obsolete figures and links in place.
- Letting an author’s authority substitute for a method or source.
FAQ
Should every sentence have a citation?
No. Cite external, contestable factual claims; explain firsthand work and keep ordinary editorial transitions readable.
Is a bibliography enough?
No. Link or name the source near the claim so readers can assess it in context.
Read original research, content refresh audits, and AEO.