Content audit: turn a page inventory into an action plan

A content audit helps a team decide what to do with the material it already publishes. A list of URLs tells you what exists. The audit adds a judgment: which reader task each page serves, whether it is accurate and useful, and what should happen next.

This guide provides a bounded audit process, a copyable inventory header, and a decision record. It works with exports and source material you already have. It does not require you to treat every low-traffic page as a failure or buy a new tool before reviewing your content.

Choose a decision and a manageable scope

Start with a concrete question. For example: which support articles need correction after a product change, which blog pages deserve an update, or which pages should move during a website redesign? The question determines the evidence you need.

Write down the included section, excluded material, review date, audience, and decision owner. A first pass might cover one product's documentation or a defined set of campaign pages. Record that boundary so a partial review is not presented as an audit of the whole site.

Nielsen Norman Group distinguishes an inventory from an audit and emphasizes choosing a useful scope. YaleSites' audit guidance combines a page inventory with qualitative review. Use these as references for the process; your own readers and current product establish what a page needs to do.

Build the inventory before assigning scores

Gather the relevant URLs from your CMS, an authorized crawl, a sitemap, or a maintained content list. Keep redirects, attachments, and duplicate source records recognizable. A sitemap is one discovery source; it is not proof that every public URL has been captured.

Copy this header into a spreadsheet or your existing work tracker:

record_id,url,content_type,reader_task,page_owner,content_version,observed_date,accuracy_evidence,performance_period,performance_source,performance_observation,proposed_action,rationale,dependencies,reviewer,implementation_owner,status,verification_reference

Preserve the exact URL and version you reviewed. If two exports use different URL formats, reconcile them before joining metrics. Do not merge separate language pages, redirect destinations, or distinct user tasks simply because the paths look similar.

For performance evidence, note the date range, filters, and source. Search clicks, page sessions, conversions, and customer support usage measure different things. Missing analytics stays missing; it is not a zero. A new page and a seasonal page may need a different comparison window from an established evergreen article.

Read the page against its actual job

For each page, answer a few concrete questions before recommending an action:

• What is the visitor trying to do, and does the page help them finish it?
• Are instructions, examples, product details, and linked destinations current?
• Does the title accurately describe the useful content and promised deliverable?
• Can the next owner trace important claims to a source?
• Does another page already satisfy the same task, or does it serve a different audience or stage?
• What decision would still be uncertain after reading the available evidence?

Semrush's content audit guide demonstrates a product-led route from inventory collection to performance data. You can use an existing export for this workflow; Offloop does not obtain your analytics or crawl your site merely because you open this guide.

Choose an action with a reason

Use action names your team can implement. Avoid a numerical score that conceals the actual problem.

These are proposals until the responsible owner reviews them. Do not automatically delete or redirect pages because of low traffic. A policy page, a troubleshooting article, or a narrow integration document may be valuable with a small audience.

Worked example: three pages, three different decisions

This example is fictional and contains no observed Offloop traffic or customer performance.

Notice that only the first row has enough evidence for a specific edit. The third row still needs a destination decision. That difference should remain visible when you prioritize work.

Turn the audit into an executable handoff

Copy this decision note for each approved change:

CONTENT DECISION
Reviewed URL and content version:
Reader task:
Observed problem and supporting sources:
Proposed action and exact scope:
Evidence still missing:
Dependencies: product, links, redirects, translations, or permissions:
Decision owner and reviewed version:
Implementation owner:
Acceptance check:
Actual changed URL/version and verification result:
Next review trigger:

After an edit, check the page a reader will actually see, its relevant links, and the promised asset or action. A migration also needs its approved redirect and indexing treatment checked. Keep the before-and-after record; a completed editing ticket alone does not establish the published outcome.

Use Offloop to coordinate the review

In an accessible workspace, share the bounded inventory and authorized source material in a Channel. Ask an agent to organize evidence and propose action rows; ask the responsible human to review uncertain claims and approve changes. Keep unavailable sources explicit. Connected accounts and publication permissions require their own setup and authorization.

A recurring review can be specified with Flow once inputs, owners, and acceptance conditions are clear. This guide supplies a method and editable records, not an automatic SEO scanner or a built-in Search Console connection.

Once a source has been reviewed and approved for reuse, the content repurposing workflow helps turn it into new assets. An audit decides what the existing content needs; repurposing adapts useful material for another task or format. Keep those decisions connected, but do not count the same edit as both a new page and an audit outcome.