The short answer
Use real process details and permissioned examples while clearly labeling hypothetical scenarios.

A three-step workflow
Identify real experience
Identify process details you can honestly explain from the business's work. Do not imply that a public source is your own experiment.
Protect client details
Remove confidential identifiers and secure permission for any client result. Use aggregate data only when rights and privacy allow it.
Label example status
Mark teaching scenarios as illustrative. Separate observed outcomes from recommendations so readers can assess the basis of the advice.
Illustrative example
Put the decision in context
Describe the actual audit fields you collect. If the numerical example is invented for teaching, label it illustrative rather than a client result.
What to record in your working sheet
Keep the evidence beside the decision so the work can be checked and handed over. For this task, use these fields:
- Article URL and reader task
- Claim or section requiring work
- Source and proposed editorial change
- Reviewer, completion check and actual update date
A mistake to avoid
Inventing a case study to imply hands-on evidence.
References and further reading
The workflow and illustrative example are SEOByIndia editorial guidance. Use the linked primary documentation for platform requirements; interfaces and policies can change.
Need help applying this to your site?
Share your website, the problem you are investigating and the evidence you already have. We can discuss a focused scope and the next useful check.
Discuss an editorial content review