
Run a SaaS content audit with a copyable worksheet, worked page decisions, and a clear process for choosing what to keep, refresh, or rewrite.
Keep existing content useful with a refresh queue, evidence-led edits and post-update checks. Preserve URLs and assets unless a change is justified.
A content refresh starts with a reason: a product step changed, a linked resource disappeared, readers keep asking a question the page omits, or a useful example no longer reflects the current process. Changing a date or adding paragraphs without addressing a real gap does not make the answer better.
Keep a refresh queue alongside the new-content queue. Record the affected URL, the trigger, the proposed correction and the person who can confirm it. Search performance can help identify pages to investigate, but a traffic change alone does not tell you what the content needs.
| Field | Illustrative refresh record |
|---|---|
| Page | An existing editorial workflow guide |
| Trigger | The approval role has changed |
| Required correction | Update the owner table and escalation example |
| Evidence | The current approved operating process |
| Preserve | URL, valid examples and published imagery |
| Verify | New role is consistent throughout the page |
This narrow brief prevents a small correction from becoming an unnecessary full rewrite. If the old page still answers the same reader question, retaining its destination usually makes the update easier to understand and maintain. A URL move needs its own review of redirects and incoming links.
Fix incorrect instructions or claims first. Then consider readability, missing examples, related links and the next action. Preserve useful sections instead of replacing every sentence for novelty. Check captions, image references and metadata when their meaning depends on the changed material; do not replace published images merely to signal freshness.
When an update adds a new claim, require the same evidence you would require for a new page. Keep a short change note explaining the substantive revision. If the page shows an updated date, use it honestly to represent meaningful work rather than a routine timestamp refresh.
After an approved update is released, inspect the live body, links, metadata and intended URL. Confirm that caching has not left readers with mismatched versions. Keep a snapshot of the previous approved copy so an accidental omission can be recovered.
Record what changed and when before comparing later search or conversion data. Several factors can move those metrics at once, so treat the comparison as evidence to interpret rather than proof that a single edit caused an outcome. Start with one outdated instruction and follow the whole correction through to verification.
Use the related guide below to build an update routine that complements your publishing calendar.
No. Keep the existing URL when the page continues to serve the same purpose. Review a move separately when the destination or information architecture genuinely needs to change.
Use change triggers and risk to set review intervals. Product instructions may need attention after a release, while a stable explanation can remain useful longer. Avoid a universal refresh schedule.
For the broader workflow, explore Content Distribution & Refresh.

Run a SaaS content audit with a copyable worksheet, worked page decisions, and a clear process for choosing what to keep, refresh, or rewrite.