Content Audit

A content audit is a systematic inventory and assessment of the material already published on a site, producing a decision for each page about whether to keep it as is, update it, consolidate it with others, redirect it, or remove it. It is the counterpart to content production, and in most organizations the neglected half: sites accumulate pages continuously and almost never review what they already have.

The case for auditing is that unmaintained content actively costs something rather than merely sitting idle. Outdated pages contradict current messaging and damage credibility. Near-duplicate pages compete with one another for the same queries, splitting signals so that neither ranks. Thin pages produced years ago to fill a schedule dilute the impression of quality across a site. And large volumes of low-value material consume crawl resources on big sites while making it harder for anyone to find the material that matters.

The assessment needs both performance data and editorial judgment. Traffic, engagement, conversions, backlinks, and search visibility describe how a page performs; accuracy, relevance to current positioning, and quality relative to what now ranks describe whether it deserves to. A page with no traffic may be genuinely obsolete or may be a good page that was never linked internally, and the two require opposite responses, which is why a purely quantitative audit produces poor decisions.

Consolidation is usually the highest-value action and the one teams most resist. Where several pages address overlapping questions, merging them into one comprehensive piece and redirecting the others typically produces a page that outperforms the sum of its parts, because authority and signals consolidate rather than competing. The resistance comes from a reluctance to reduce page count, which is a proxy metric that describes effort rather than value.

Deletion should be applied carefully and with redirects. Removing pages that hold links, rank for anything, or are referenced elsewhere discards accumulated value, and returning errors for previously indexed URLs is a poor outcome for both search engines and any visitor arriving from an old reference. The defensible sequence is to redirect to the most relevant surviving page where one exists, and to remove outright only where nothing relevant remains and the page genuinely serves nobody.

Scale determines method. A site with a few hundred pages can be audited page by page with reasonable effort. A site with tens of thousands requires sampling by template and by section, identifying patterns rather than individual defects, since the decisions will be applied programmatically anyway. Recognizing which situation applies prevents an audit from consuming months and delivering a spreadsheet nobody acts on.

Cadence matters as much as method, since an audit performed once produces a one-off correction while the underlying accumulation continues. Sites that review a defined portion of their library on a rolling schedule, prioritizing the pages carrying the most traffic and commercial weight, keep the problem bounded rather than allowing it to build until another large project is required. Attaching the review to publishing capacity, so that a fixed share of each period's effort goes to maintenance rather than new production, is what makes the discipline survive beyond the initial project.

The output is only valuable if it becomes scheduled work, which is where most audits fail. A findings document with several hundred recommended actions and no owner produces nothing, whereas a prioritized subset with named responsibility and dates produces measurable improvement. In practice a marketing services engagement will fold the resulting actions into the ongoing publishing calendar rather than treating them as a separate project, and the structural findings about duplication and navigation frequently feed directly into UX audit work, since content that cannot be found and content that should not exist present very similarly in the data.