Use-Case Workflows
How to run a content audit with a knowledge system — a practical guide for content marketers to inventory existing content, assess performance and
A content audit is a systematic review of all existing content on a website (or within a content channel) to assess what's performing, what's not, what's accurate, and what opportunities exist. It's one of the most high-value activities in content marketing — and one of the most commonly avoided, because it sounds tedious.
The challenge is not technical. The data collection — pulling URLs, traffic numbers, conversion rates — is mechanical. The hard part is the analytical work: assessing whether each piece of content is:
For a website with 200+ pieces of content, this assessment work is significant, and without a system, the output is either a giant spreadsheet no one acts on or a set of impressions that don't hold up to scrutiny.
A knowledge system for content auditing organizes the analytical findings — not just the data — so the audit produces an actionable strategy rather than a data export.
A content audit covers three questions for each piece of content:
What is it? Content type (blog post, landing page, guide, case study), topic, target keyword, publish date, author, length.
How is it performing? Traffic (total and trend), ranking position for target keyword, time on page, conversions (if tracked), backlinks.
What should be done with it? Keep and optimize, update substantially, consolidate with another piece, redirect/remove.
The first two questions are answered with data (from your CMS, Google Search Console, Google Analytics). The third question is judgment — and that's where the knowledge system adds the most value.
Create a primary Collection: "Content Audit: [Site/Channel] [Year]" — e.g., "Content Audit: Blog 2026"
Sub-Collections by content category:
If your content library is organized by topic cluster or persona, add sub-Collections accordingly.
By audit decision:
keep-optimize — performing well; small improvements will maintain or improveupdate-major — high potential; needs substantial revision to reach potentialupdate-minor — performing okay; small factual or SEO updates neededconsolidate — should be merged with a related pieceredirect — has inbound links but low value; should redirect to a better resourceremove — no strategic value, no traffic, no inbound linksgap-identified — a topic that should exist but doesn'tBy priority:
p1 — action in next 30 daysp2 — action in next 90 daysp3 — action in 90-180 daysno-action-needed — keep as-isBy content type:
blog-post, landing-page, case-study, guide, video, tool, templateBefore analyzing, you need a complete list of what exists. There are two approaches:
Crawl-based inventory (for large sites): Use a tool like Screaming Frog SEO Spider (free for up to 500 URLs) or Sitebulb to crawl the site and export all URLs. This gives you a complete list even if some pages aren't in your CMS or sitemap.
Sitemap-based inventory (for most blogs): Export from your CMS (WordPress, Webflow, HubSpot) or sitemap.xml. Most CMS platforms have a bulk content export feature.
The inventory spreadsheet should include, at minimum:
Enrich with performance data by pulling from:
This is where the judgment work happens, and where the knowledge system becomes most valuable.
For each significant piece of content, assess across four dimensions:
1. Traffic and trend: Is this driving meaningful traffic? Is traffic increasing, stable, or declining?
2. Ranking and SEO potential: Is this ranking for its target keyword? Could it rank better with optimization? Is the target keyword worth ranking for?
3. Accuracy and freshness: Is all information current? Is product information accurate? Are statistics and examples from the last 2-3 years?
4. Strategic alignment: Does this piece serve current business priorities and current personas? Content aligned with a product line you've discontinued should be updated or retired.
Rather than putting all assessments in a spreadsheet, capture each significant piece of content as a clip in WebSnips and annotate it with your assessment:
URL: [page URL]
Title: [content title]
Content type: [blog post / guide / landing page / etc.]
Publish date: [date]
Last updated: [date or "unknown"]
PERFORMANCE DATA:
Monthly traffic: [N pageviews]
Traffic trend: [growing / stable / declining]
Primary keyword: [target keyword]
Current ranking: [position N / not ranking / not tracking]
Backlinks: [N referring domains — indicates link equity worth preserving]
Conversions: [N or "not tracked"]
CONTENT QUALITY:
Accuracy: [current / needs update on: specific items]
Freshness: [year-appropriate / dated examples / outdated statistics]
Depth: [comprehensive / surface-level / thin]
Unique angle: [what makes this piece distinct? / redundant with: [URL]]
STRATEGIC ALIGNMENT:
Serves current ICP: [yes / partially / no]
Aligns with current priorities: [yes / no]
Keyword still relevant: [yes / lower priority / no longer strategic]
AUDIT DECISION: [keep-optimize / update-major / update-minor / consolidate / redirect / remove]
Priority: [p1 / p2 / p3 / no-action]
If consolidating: Consolidate with: [URL of primary piece]
If redirecting: Redirect to: [URL]
SPECIFIC RECOMMENDED ACTIONS:
1. [Specific action]
2. [Specific action]
This annotation turns the audit from data collection into an actionable decision record. When your content team picks up the list for execution, the specific actions are already identified — they don't have to re-assess each piece.
Assessing 200+ pieces individually is exhausting. A batching approach:
Tier 1 (top 20% by traffic): Full assessment. These pieces drive most of your organic traffic. Every one deserves a complete assessment.
Tier 2 (middle 30% by traffic): Standard assessment. These pieces have some traffic and some potential. Standard annotation.
Tier 3 (bottom 50% by traffic): Quick triage. Sort into: has 3+ referring domains (check before removing — link equity), has meaningful conversion data (check before removing), is less than 1 year old (probably fine), everything else → candidate for removal batch review.
For the removal candidate batch, do a 30-second sanity check per piece: any strategic reason to keep this? Any inbound links from high-authority sites? No → queue for removal.
The content audit reveals what exists. Gap analysis reveals what should exist but doesn't.
Keyword gaps: Topics your target audience searches for that you don't have content about. Sources:
Funnel gaps: Missing content at a stage of the buyer's journey. Common examples:
Persona gaps: Topics that matter to one buyer persona but aren't covered in your content.
Format gaps: You cover a topic well in one format (long-form guide) but have nothing in formats that serve different consumption preferences (short-form, video, infographic).
Create a capture in the "Gap Opportunities" sub-Collection for each identified gap:
Gap type: [keyword / funnel / persona / format]
Topic: [what's missing]
Why it matters: [evidence of demand or strategic importance]
Target keyword (if SEO): [keyword, estimated monthly volume]
Target persona: [who this serves]
Recommended content type: [blog post / landing page / guide / video / etc.]
Priority: [p1 / p2 / p3]
Estimated production effort: [small / medium / large]
The gap analysis Collection becomes your content calendar pipeline.
The output of a content audit should be an action plan, not a spreadsheet. The deliverable has four components:
Summary findings: What the audit revealed in aggregate. "We have X pieces of content; Y% are performing well; Z% need significant updates; W% should be removed. Top 3 strategic gaps are [A], [B], [C]."
Action matrix: Content organized by action type (update, consolidate, remove, new) and priority. This is the editorial calendar input.
Quick wins: 5-10 pieces that could be substantially improved with relatively low effort and would likely produce significant traffic gains. These become the first execution priority.
Strategic recommendations: 3-5 higher-level recommendations about content strategy that emerged from the audit. Not just "update these URLs" but "our content cluster on [topic] is fragmented across 12 pieces that should be consolidated into 3" or "we have no bottom-of-funnel content for [persona] — this is a conversion gap."
With the audit captures and annotations organized in WebSnips, Creator Studio can help synthesize the findings:
Summary generation: "Based on these content audit annotations from the 'Update Priority' Collection, summarize the top patterns in what needs updating and what the likely impact is." The output needs editing but gives you a starting framework for the summary.
Action list extraction: "From these 15 'consolidation candidates' captures, draft a consolidation plan showing which pieces to merge into which primary pieces." Useful for the highest-complexity part of the audit.
The scenario: A content strategist at a 100-person B2B SaaS company runs a biennial blog audit. The blog has 340 published posts accumulated over 6 years. She has 4 weeks for the audit.
Week 1 — Inventory and data collection:
Week 2 — Full assessment of top performers:
Week 3 — Middle and lower tier assessment + gap analysis:
Week 4 — Audit deliverable:
Estimated organic traffic impact from execution: +35-50% over 12 months based on comparable case studies from Ahrefs/SEMrush published research.
A content audit is the kind of project that produces enormous ROI when done well and is wasted effort when it produces a spreadsheet no one acts on. The difference is the quality of the analytical layer: not just what the data says but what should be done about it, and with what specific actions, in what priority order. A knowledge system that organizes content captures alongside their performance data and annotated action recommendations converts the audit from a data collection exercise into a content strategy. The result is an editorial team that knows exactly what to work on next and why — and content that improves because the audit drove action, not just insight.
To go deeper, check out The Ultimate Guide to Web Clipping.
More WebSnips articles that pair well with this topic.
How to build a teaching resource library with a knowledge system — a practical guide for teachers and educators to organize lesson materials, curate
How to organize sources for a documentary with a knowledge system — a practical guide for documentary filmmakers and journalists to manage research
How to analyze customer feedback with a knowledge system — a practical guide for product managers to collect, organize, tag, synthesize, and act on
How to assemble evidence for due diligence with a knowledge system — a practical guide for investors and acquirers to organize research, document
How to build a competitive landscape map with a knowledge system — a practical guide for product managers and founders to research, organize, and maintain
How to build a course with a knowledge system — a practical guide to organizing research, developing curriculum, managing content assets, and creating