• What is a Content Audit?

Content Audit

Content audit is a systematic review of everything published on your site, scored against what’s ranking, what’s converting, what’s decaying, and what’s hurting you more than helping. A real audit ends with a prioritized list of what to keep, what to refresh, what to merge, and what to kill. A bad audit ends with a 120-page PDF nobody uses. The difference is usually the question you asked before you started.

When to run an audit

The most important time is the one almost nobody picks: right at the beginning of the project.

If you’re taking over a client’s blog, launching a new program on an existing site, or inheriting content from a predecessor, run the audit first. You need to know what you’re working with before you plan anything. Existing content is either going to help you or hurt you; without an audit you don’t know which.

After the initial audit, run the main one at least once a year. If you can afford the time, update the input data every one to three months. Not the full audit, just the fresh data. This tells you whether your influence is growing, which pages are decaying, and what’s working well enough to expand.

Teams that audit once and file the result away lose the value. The audit is a rolling diagnostic, not a one-time event.

What a real audit actually produces

The deliverable is a small number of decisions, not a pile of analysis.

Keep as-is. Pages that rank, convert, or both. Don’t touch them. Write this list first so you don’t accidentally cannibalize winners.

Refresh. Pages with recoverable traffic. Rankings have slipped, content is stale, or the search intent has shifted since publication. Prioritized by the size of the recoverable traffic, not the age of the page. This is where the fastest ROI lives.

Merge. Multiple pages competing for the same query. Pick the strongest URL, fold the others into it, redirect the losers. SEO teams call this keyword cannibalization; an audit is where it gets surfaced and fixed.

Kill. Pages that rank for nothing, convert for nothing, and have nothing worth merging. Low traffic isn’t automatic grounds to kill, but low traffic plus zero strategic value is. Redirect to the most relevant surviving page, or 410 the URL if there’s no good redirect target.

Leave for later. Pages with unclear status. Not all decisions need to ship in the first round.

A 500-page site usually ends up with maybe 15% kill, 25% refresh, 10% merge, 50% keep or leave. The exact ratios vary. The shape rarely does.

The data inputs that matter

Five data sources cover 90% of the decision-making weight.

Organic traffic by URL. Google Analytics or GA4, pulled by URL over a rolling 12-month window. Pages with zero organic traffic are candidates for kill. Pages with declining organic traffic are candidates for refresh.

Rankings by URL. Search Console plus a rank-tracking tool. Pages ranking positions 4-15 are the prime refresh candidates: close enough to page-one placement that a focused refresh can lift them into the zone where clicks compound.

Pipeline influence by URL. Which pages touch the customers who actually buy. This is the metric your CFO cares about. Less common in dashboards, more important than any of the vanity metrics.

Backlink profile by URL. Pages with strong external links are keep or refresh candidates; killing a URL with good backlinks throws away equity. Pages with no backlinks and no traffic are kill candidates.

Topical fit with your current strategy. Pages that were on-strategy in 2020 and off-strategy in 2026. The site’s focus has moved; some pages haven’t. These are either merge (fold into current strategy) or kill (genuinely off-topic).

Easy refresh wins: the step most teams skip

Before you focus on new content, you should have a list of easy refresh wins for existing pages. Refresh the low-hanging fruit first, then build new.

Most teams do this in reverse. They see a fresh content calendar as the exciting work and existing-page updates as maintenance. The maintenance is where the fastest ROI usually sits.

Easy wins to surface during the audit:

Pages ranking positions 4-10 on terms your ICP searches. A focused refresh (updated data, stronger intro, tightened outline) often moves them into positions 1-3. Double-digit percentage traffic gains, no new URLs required.

Pages with declining rankings on queries you used to own. The content has aged out of relevance. A content refresh that re-establishes authority on the query often recovers the full traffic within 60-90 days.

Pages missing key components the current category expects. Named author, schema markup, first-person experience, original data. Adding these to an otherwise-solid page often lifts both ranking and citation probability.

Shipping a month of refreshes on the list above before writing new content usually produces better total traffic than shipping a month of new pieces would have.

The refresh-vs-new split

There’s no universal ratio, but a default that works for most programs: two months on new content, one month on refreshing what you have, on rolling cycle. Adjust based on site size and audit findings.

Larger legacy sites (five years or more, a thousand+ pages) often need closer to a 50/50 split for the first year. The refresh backlog is bigger than the new-content opportunity.

Newer sites (under two years, under a hundred pages) usually spend most of the cycle on new content, with refresh as a quarterly pass.

The ratio is a lever. Check it against what the audit surfaces, not against an arbitrary template.

What makes audits fail

Three patterns.

Audit-as-PDF. The audit lands as a 120-slide deck that nobody acts on. The deliverable should be a prioritized list and a queue. If the audit isn’t actionable on Monday, it failed.

Audit without topical strategy. Listing what ranks and what doesn’t, without a view on which pillars you want to own, produces a maintenance backlog. Audits are useful when paired with a current content marketing strategy; without one, they become triage without direction.

One-time audits. A single audit captures a moment. Without quarterly data refreshes, you miss the drift: which pages are decaying, which rising, which the category has moved around. Rolling data beats periodic snapshots.

Penfriend’s approach

We built Penfriend around the observation that most content programs lose ROI in the gap between what’s already published and what gets shipped next. Cluster handles the cluster-level strategy that audits feed into. Penny interviews the subject-matter expert for new pieces and for substantive refreshes, which puts first-person experience back into pages that had none. VIBE scores existing pages against the current quality floor so the refresh list writes itself. The audit becomes a continuous signal, not an annual event.

Related terms