The Trust Audit

Four questions to ask before changing the date, copy or design of another page

A page starts slipping. One response is to refresh it: change the date, add keywords, tighten the introduction and publish again.

Sometimes that is useful. Sometimes it is freshness theatre.

The page may not be weak because it is old. It may be weak because nobody can tell who stands behind it, what has been reviewed, what the author knows directly or where the useful answer is hiding. That is why a content refresh should begin with a trust audit, not a rewrite.

A page is more than a ranking unit

A useful answer may be a definition, paragraph, checklist or direct response rather than a whole page. For a human reader, source context helps them judge how to use the answer, and clear structure helps them find it. Search and answer systems have their own access and selection rules. To be eligible as a supporting link in Google’s AI Overviews or AI Mode, a page must be indexed and eligible to appear in Search with a snippet; eligibility does not guarantee crawling, indexing or serving (Google Search Central).

The useful question is not “How do we make this page look current?” It is “Why would anyone trust this page enough to use it?”

1. Is there a recognisable source behind it?

Authority is not a magic score and it is not only a backlink count. It is the degree to which a reader can understand who is responsible for the information and why that source is worth hearing on this topic.

Is the author, organisation or responsible team clear? Is the page connected to a coherent area of work? Does it say what has been built, tested, observed or reviewed? Are useful references available where they genuinely help?

An author box alone does not create authority. It can make a real source visible. The distinction matters.

2. Has anything material been maintained?

Freshness is not the same thing as recency. A fast-moving topic may need a dated review because the reader needs current information. An evergreen page does not become more useful because someone changed the footer date.

Material maintenance reduces uncertainty. It might mean correcting an example, removing a claim that no longer holds, adding a limitation, updating a process, replacing a dead reference or showing what was reviewed.

If the date disappeared, would the page still be better? If not, it has probably been decorated rather than maintained.

3. What can this page say that a generic summary cannot?

A lot of content is accurate enough to be harmless and generic enough to be replaceable. First-party evidence can give a page something a generic summary lacks. It can be a direct observation, an original method, a real decision rule, an anonymised pattern, a clearly labelled data point or a caveat a competitor would leave out.

It does not need to be dramatic. Useful evidence can be small: a test that failed, a recurring question or a piece of process that saves confusion. The point is to make the source of the knowledge visible.

4. Can the useful answer be lifted cleanly?

If the answer is buried in a long opening, inaccessible in an image or document, hidden behind an unclear control or lost in vague prose, the page is harder to use. Clear headings, direct first sentences, short definitions and evidence beside the relevant claim can help people find and assess it. Keep any necessary source, date and qualification attached when an answer is excerpted; extractability is not a reason to strip away context. Google’s documentation says standard search eligibility and people-first guidance still apply, but no page structure guarantees that a system will select the content.

The goal is not to write like a robot. It is to let the reader find the value without excavating it.

Run the audit before you rewrite

Choose one important page and record four things:

1. Who is responsible for this information, and why are they credible here?
2. What has been materially reviewed or corrected?
3. What direct knowledge, evidence or useful method does the page add?
4. Could someone understand its main answer from the headings and first sentences alone?

For example, a page about a service might still show an old launch date, name no responsible author and include a claim whose source is unclear. The audit would record the date as reviewed, the claim and its source, any qualification the reader needs, the person responsible for the next review and the event that should trigger an earlier update. If those details cannot be verified, the page needs a source check before a rewrite.

If the answers are weak, a longer article is unlikely to solve the problem. The page does not need more polish first. It needs a stronger reason to exist.

These are practical review lenses, not official search-engine scores or ranking guarantees. Current search and AI-product behaviour should be verified before publication if the final version makes specific platform claims.