How to use the Content Freshness Audit.
Look for claims whose accuracy depends on time: prices, dates, interfaces and availability. A recent publication date alone does not make the content current.
Make the workflow fit your task.
Identify statements whose accuracy can expire, then attach the evidence needed to verify each one. Prioritize changes that affect instructions or decisions, recording what was checked and what remains unresolved.
- What you provide
- Article text and publication context.
- What you get
- Dated claims, stale references and refresh priorities.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Guide text says the feature launches next month and instructs readers to click Old Import. Current supplied release notes say the feature is available; the supplied interface screenshot labels the control Import data.
Completed example
Finding 1: relative launch statement is stale. Replace with: The feature is available. Finding 2: navigation label differs from the supplied interface. Replace Old Import with Import data. Verification scope: supplied release notes and screenshot only; other steps remain unchecked.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does changing the publication date make a page fresh?
No. Update the underlying facts and instructions where needed. A date change should reflect a meaningful review rather than substitute for one.
Why does a recently edited guide still contain obsolete steps?
Compare the workflow with current source material, including navigation labels and availability. Editing one section does not verify the rest.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑