Your homepage says the team supports three services. An old article still links to a discontinued package. A case study describes a past delivery process as if it were current. Each page looks fine alone, but together they give a buyer conflicting answers.

A freshness audit starts with the claims that affect a customer's decision, not with the oldest publication date.

Pick one journey and follow it

Start with a blog post, follow its service link, open a related case, and try the contact route. On each page, record what a buyer is told about scope, availability, deliverables, and next steps.

Do this for one important service first. A short list of conflicting claims is more useful than a spreadsheet of every page's age.

Distinguish a historical fact from a current promise

A case study can say “the pilot included two workshops” if that happened. It should not imply every current project includes two workshops unless the service still promises that.

For a dated statistic, retain the measurement date and scope. Do not replace a historical result with a new number unless you can explain what it measures. Update present-tense claims that no longer hold; label history as history.

Fix shared details across languages

If the contact email or service scope changes, identify the pages and language versions that repeat it. Compare the actual customer-facing text and links, not just whether a translation exists.

Test each link's destination. A working link can still be wrong if it goes to a generic homepage instead of the relevant service or the equivalent page in the visitor's language.

Keep a short review register

  • Page and claim to verify.
  • Person who owns the underlying information.
  • Evidence or source to check.
  • Other pages or translations affected.
  • Next review date or change that triggers another review.

Do not rewrite a useful older article merely to give it a new date. Prioritize details that could send a buyer to the wrong service, promise something unavailable, or prevent a reply. Then follow the same journey again to verify the changes.

For language-specific checks, see our multilingual launch checklist, or request a website review.