01
Step-by-step
- 01
Write the questions first
List the claims, decisions, definitions, and steps the page must support.
- 02
Prefer primary sources
Use official documentation, original research, direct records, specifications, and first-party experts.
- 03
Record source details
Capture title, publisher, date, relevant section, and how it supports the point.
- 04
Resolve conflicts
When reliable sources disagree, explain the disagreement or narrow the claim.
- 05
Check freshness
Identify facts, standards, prices, laws, product behavior, and interfaces that may change.
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 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 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 website content into an accountable record.
A tested implementation of website content with deployment notes, rollback context, and retained verification.