01
Step-by-step
- 01
Cite claims that need evidence
Prioritize statistics, research, legal or medical statements, standards, product behavior, and disputed facts.
- 02
Link to the relevant source
Use the specific official document or study when available.
- 03
Describe evidence accurately
Do not claim that a source proves more than it supports.
- 04
Use quotations sparingly
Paraphrase meaning and quote only the exact language required.
- 05
Review old citations
Replace broken, outdated, or superseded sources.
02
Verification
- The visible page matches the intended topic and audience.
- The page can be crawled, rendered, and indexed when intended.
- Claims, examples, code, and links have been checked.
- The page has a measurable next action or outcome.
- A future reviewer can understand what changed and why.
03
Before you change the website
- Define the purpose and expected result of sources in website content.
- Capture the current state using scope, methodology, evidence, affected assets, severity, priority, ownership, status, limitations, and verification.
- Identify the source template, component, plugin, content owner, and release path that controls the output.
- Prepare a test case, approval path, backup or rollback method, and post-release verification plan.
04
Quality-control checks for sources in website content
- Confirm the report matches the current source records, scope, approvals, and verification status before distribution.
- Check representative page types and edge cases instead of confirming only the example used during implementation.
- Confirm the change did not create separating client language from the technical evidence until the two conflict.
- Record the implementation date, owner, release reference, evidence, and next review trigger.
Next useful action
Turn sources in website content into an accountable record.
A tested implementation of sources in website content with deployment notes, rollback context, and retained verification.