A content audit is not a redesign. It is a cleanup that makes the redesign possible. If you skip it, you end up migrating pages you don’t need, rewriting content you could have merged, and paying for scope you never wanted.
Digital.gov’s content audit guidance frames an audit as a complete inventory rather than a traffic-only sample. It also highlights ROT analysis (redundant, outdated, or trivial) as a practical filter for what should go away. Digital.gov content audit guidance
Mass.gov gives a useful reminder: audits are cleanup, not redesign. That separation is helpful because it keeps teams from debating new copy while they are still trying to understand what exists. Mass.gov content audit overview
If you are planning a redesign, this is the audit approach that keeps scope under control and helps you make real decisions.
What a content audit actually does
A content audit answers four questions:
- What content exists right now?
- What content is still accurate and useful?
- What content is duplicated, outdated, or misaligned?
- What content should be kept, merged, or removed before you redesign?
This is different from content strategy. Strategy is about what you should publish. An audit is about what already exists and whether it deserves to survive.
The audit starts with a real inventory
You can’t make decisions on content you haven’t listed. The first step is a spreadsheet inventory that includes:
- URL
- Page title
- Primary goal of the page
- Last updated date
- Owner (if known)
- Notes on accuracy, duplication, or gaps
Digital.gov’s audit guidance recommends starting with a complete inventory and warns that analytics-only inventories miss live pages with no traffic. That sequencing saves time. Digital.gov content audit guidance
If you want a shortcut, start with a crawl export and then add your business notes. That is usually enough to start making decisions.
The four decision buckets: keep, cut, merge, rewrite
The audit is useless if it doesn’t end in decisions. I use four buckets that make the next phase obvious.
Keep
Keep content that is accurate, unique, and aligned with how buyers decide. It still needs refinement, but it has a clear purpose. These pages should stay in your new information architecture.
Cut
Cut content that is outdated, off‑brand, or off‑strategy. This is the ROT category Mass.gov highlights: redundant, obsolete, or trivial content. Removing it makes redesigns easier and faster. Mass.gov content audit overview
Merge
Merge content when you have thin pages that compete with each other. This is common in service businesses with multiple “near‑duplicate” service pages. A merge reduces duplication and clarifies the buyer path. It also improves how search engines interpret your primary page. If you need help, see service page anatomy.
Rewrite
Rewrite content that is strategically important but unclear. This typically includes your homepage, core service pages, and the pages that answer buyer objections. Homepage messaging and technical service copy are the usual rewrite targets.
What to measure without overcomplicating it
If you have analytics access, add a few basic signals to your inventory:
- Pageviews or sessions
- Time on page (if you trust it)
- Conversions or assisted conversions
- Entry vs supporting pages
You don’t need perfect data. You just need enough to see which pages matter and which ones are dead weight. The marketing site analytics baseline article explains how to collect that without getting lost in dashboards.
Who should be involved in the audit
Content audits fail when only one person owns the decisions. You need a small, cross-functional group that can make quick calls. I recommend:
- A marketing owner who understands positioning and pipeline goals
- A service owner who knows what is actually delivered
- A sales or account lead who hears objections and deal blockers
- One person who is responsible for compliance or legal accuracy
Keep this group small. The goal is clarity, not consensus. You can always loop in more people once the audit decisions are made.
Special cases: legal pages, proof pages, and legacy content
Some pages look low-traffic but are high-risk. That includes legal notices, privacy policy pages, and trust pages like reviews or case studies. These should not be cut without a business owner sign-off.
If you have a dedicated reviews page or a case study set, mark these as "rewrite" instead of "cut." A poor case study is still a clue about what your buyers need to see. You can turn it into a better asset instead of deleting it. The case study structure guide can help you decide what to keep.
Legacy blog posts are a different category. If they still bring search traffic, consider merging or redirecting instead of deleting. That reduces the risk of losing organic visibility while you simplify the site.
The audit should feed your redirect plan
Every "cut" or "merge" decision should produce a redirect action. If you skip this, you'll introduce broken links and lose the value of any existing search visibility.
When you move or remove pages, maintain a mapping file that pairs old URLs with new destinations. This is the same logic used in website migration planning. Even if your redesign is not a full migration, the discipline is the same. Keeping this mapping early turns a risky guessing game into a clean implementation task.
A clean audit flow that works for service businesses
This is the flow I use with service firms when scope matters.
- Build the inventory spreadsheet
- Tag ROT candidates quickly
- Flag pages that support revenue directly
- Decide keep/merge/cut/rewrite
- Share a one‑page summary with stakeholders
That’s it. The goal is a decision map, not a research project.
How to avoid analysis paralysis
Content audits can stall because teams try to perfect every page review. Don’t do that. You need clarity, not perfection.
Here’s what helps:
- Set a time limit for page review (2 to 3 minutes each)
- Mark “uncertain” pages for a second pass
- Let the business owner decide final calls
If you need to move quickly, focus on top‑level navigation pages and high‑traffic entries first. That usually surfaces 80% of the decisions.
How the audit reduces redesign risk
When you audit first, you get three benefits:
- Scope clarity. You stop paying to migrate low‑value content.
- Copy priorities. You know which pages deserve investment.
- Architecture confidence. You can map content to buyer stages without guessing.
That last point is critical. If you are planning a services hub or a multi‑service navigation, you need to know what content exists before you can structure it.
What to do with the audit results
The audit should feed three artifacts:
- A trimmed sitemap
- A rewrite list with owners
- A migration backlog with deadlines
Those three outputs are enough to guide the redesign. Add page owners and review triggers only after the migration decisions are stable.
The quiet win: fewer pages, better decisions
A strong audit gives the team evidence to remove what no longer matters. That saves migration work and keeps the new navigation focused on current buyer decisions.
Preserve value when pages are merged
Consolidation is not just deleting several files and pointing them at the nearest article. Before redirecting a source page, record the useful material that the destination must retain:
- distinct questions or buyer objections;
- authoritative citations;
- first-hand implementation details;
- diagrams, checklists, or definitions;
- queries and internal links that reveal the source intent.
Move only what improves the canonical page. Do not paste every paragraph into a longer “ultimate guide.” The destination should answer the combined intent clearly, without repeating introductions or manufacturing evidence.
If no page is materially equivalent, do not redirect to the homepage. Remove the URL with a clear 404 or 410 response and take it out of internal links and sitemaps. A redirect is for transferred value, not for hiding deletion.
Keep a decision and redirect register
For each old URL, store the decision, destination, owner, and reason. Add the strongest known search query or business purpose when evidence exists. This register becomes the source of truth for implementation and post-launch checks.
Test that redirects are:
- permanent only when the destination is final;
- one hop, with no redirect chain;
- mapped to a genuinely equivalent page;
- consistent across canonical tags, sitemaps, navigation, and internal links.
After launch, inspect requested old URLs and destination performance. A spike in 404 requests can reveal links the inventory missed. A destination losing visibility for a useful source query may need a clearer section or anchor, not a new duplicate page.
Assign a review trigger, not only a review date
Content governance does not require a large committee. Give each important page an owner and define what should trigger review: a changed offer, new regulation, replaced vendor, outdated interface, expiring evidence, or declining qualified demand.
Review dates still help, but triggers prevent a page from staying “current” on paper while the underlying business has changed. If nobody can own a page and it carries no durable value, that is evidence for removing it in the next audit.
If you want help running the audit or deciding what to keep, send your draft inventory through the project brief and I’ll mark the pages that should survive. If you want a quick second opinion, use the contact form.
