Quick Wins, Hiding in Plain Sight: A Content Audit Framework

Most clients with an existing website are sitting on a small mountain of old content they've forgotten exists. Blog posts from five years ago. Project case studies that were never properly indexed. A press page that hasn't been touched since the founder did that one interview.

For studios coming in fresh, this archaeological layer is gold. Not because it's good (it often isn't), but because it tells you a story about how the client has shown up over time, where the gaps are, and where the easiest wins live.

A content audit is one of the most generous things you can do early in a relationship. Here's how to run one without it eating a week.

What you're actually looking for

A content audit isn't a list of every page. It's a structured way of answering four questions:

One: what's worth keeping? The pages that are still on brand, still accurate, still earning their place. These don't need attention. Note them and move on.

Two: what's worth fixing? The pages that are nearly right but tired. Old screenshots, dated language, slightly off positioning. These are quick wins, often big visual impact for small effort.

Three: what's worth removing? The pages that are doing active harm. Out of date services, off brand tone, projects from a previous era of the studio. Cutting these is usually the single highest leverage move.

Four: what's missing entirely? The pages that should exist and don't. The case study for the work everyone references. The about page that reflects who they actually are now. The service description for the thing they keep getting hired for.

That's it. Four buckets. Every page sorts into one.

A simple way to run it

Open a spreadsheet. Genuinely. Don't overengineer this.

Columns: page URL, current title, last meaningful update, on brand (yes/no/sort of), still accurate (yes/no), bucket (keep/fix/remove/missing), priority (high/medium/low), notes.

Now go page by page. For a typical small or mid sized client this is a two to four hour job, not a week. Resist the urge to start fixing things as you go. Audit first. Decide later.

The "missing" column is where the magic is

Most audits stop at the existing content. The interesting work is in what isn't there.

After you've been through the site, ask:

• What does this client get hired for that isn't reflected anywhere on their site?
• What questions do their clients ask that the site doesn't answer?
• What's the strongest piece of work they've done in the last twelve months that isn't visible here?
• What is the founder really good at talking about that isn't on the site?

Each one of those is a piece of content waiting to be made. And because it's grounded in what the business actually does, it's almost always more valuable than a generic blog content plan.

Present it as opportunity, not criticism

This bit matters. The client made every one of those pages. Sometimes their team made them. Sometimes the founder personally wrote that blog post you want to delete.

The audit isn't "here's what's broken." It's "here's where we see room to make this site work harder for you." Frame it as a map, not a verdict.

Studios that get this tone right end up in long, trusting relationships. Studios that get it wrong end up with a client who's quietly defensive for the next six months.

A small bonus

A content audit, presented well, often becomes the seed of the next project. The client sees the gaps, agrees they need fixing, and the conversation moves naturally into a phase two engagement. You didn't pitch them. The audit did.