How to Build a Website Content Inventory

Direct answer：Create a URL-level content inventory to document ownership, traffic patterns, conversion metrics, freshness indicators, factual accuracy status, and migration decisions before a website redesign.

Building a Content Inventory for Website Redesigns

A content inventory is the foundation for data-driven decisions during website migrations or structural changes. This implementation guide provides a field-tested method for auditing existing content before making architectural decisions.

Required Inputs

Full URL list: Export from your CMS, Google Search Console, or crawling tool
Traffic data: 90-day pageviews from Google Analytics 4 or equivalent
Conversion metrics: Goal completions per URL (lead forms, downloads, etc.)
Ownership records: Content author, last reviewer, and business unit responsible
Technical crawl: Index status, canonical tags, and redirect chains from Screaming Frog

Inventory Fields and Decision Criteria

Create a spreadsheet with these minimum fields:

Field：Verification Method；Decision Threshold

URL：CMS export cross-check；Must match production

Page Title：SERP preview tool；Matches CMS entry

Content Owner：Stakeholder interview；Current employee

Last Update：CMS modified date；<24 months for core pages

Monthly Traffic：GA4 comparison；<10 visits = retire candidate

Index Status：GSC coverage report；’Submitted, indexed’ required

Fact Accuracy：Subject matter review；Outdated claims flagged

Implementation Steps

Extract baseline data from technical sources (CMS, GA4, GSC)
Merge datasets using URLs as primary keys
Flag discrepancies between CMS records and live site
Apply decision rules to classify content:

Migrate (high-value, accurate)
Rewrite (high-value but outdated)

Retire (low traffic and no conversions)

Validate with stakeholders before finalizing

Exception Handling

Legacy content: Preserve legal/regulatory pages regardless of traffic
Seasonal pages: Use 12-month traffic window for evaluation
New pages: Exclude from analysis if published <90 days

Acceptance Criteria

A complete inventory must:

Resolve all 404/5xx errors before migration
Document every retire/merge decision
Assign rewrite owners with deadlines
Preserve all historical redirects

Next Steps

After completing your inventory, conduct a content gap analysis against your new information architecture to identify missing topics and redundant pages.

Content Inventory Implementation

Required Inputs

Crawl Data: XML sitemaps, analytics exports, or crawler outputs listing all live URLs
Ownership Records: CMS metadata, project docs, or stakeholder interviews confirming content owners
Performance Metrics: 12-month traffic, conversions, and engagement data per URL
Technical Reports: Indexing status, canonical tags, and redirect chains from search console
Version Control: Last update timestamps, archived drafts, or change logs

Inventory Steps

Extract URL Inventory

Combine crawl sources into a master list
Flag duplicates, redirects, and orphaned pages
Record CMS IDs and template types

Tag Content Attributes

Assign primary/secondary owners
Note publication and last update dates
Mark factual accuracy status (verified/outdated/unchecked)
Identify regulated content requiring legal review

Apply Decision Criteria

Migrate: High-traffic pages with current information
Rewrite: Important but outdated content
Merge: Thin or overlapping pages
Retire: Low-value pages with declining traffic

Verification Checks

Completeness: All production URLs accounted for
Accuracy: Performance data matches analytics sources
Consistency: Decision criteria applied uniformly
Stakeholder Alignment: Owners confirm migration plans

Exception Handling

Legacy Content: Preserve required archives with noindex tags
Dynamic Pages: Apply rules to URL patterns vs. individual entries
Third-Party Content: Document licensing/embedding terms

Content Inventory Working Record

Field：Description；Example

URL：Page address；/solutions/ai-search

Template：CMS layout type；Product Landing

Owner：Primary responsible party；Product Team

Last Update：Most recent revision；2024-03-15

12mo Traffic：Unique pageviews；24,531

Accuracy：Fact-check status；Needs Review

Migration Action：Redesign disposition；Rewrite

Notes：Special considerations；Case studies outdated

Evidence Sources and Quality Gates

Required Input Fields

Build your inventory on these verifiable data points:

Ownership Proof (Documented in CMS or version control)

Last editor contact
Business unit/stakeholder
Legal or compliance flags

Traffic Evidence (From analytics tools)

90-day organic sessions
Top 5 converting queries
Entry/exit patterns

Conversion Status (From CRM or analytics)

Lead-to-customer rate
Assisted conversions
Form abandonment points

Freshness Indicators

Published date
Last major update
SME review timestamp

Decision Criteria Matrix

Field：Keep Threshold；Rewrite Trigger；Merge Candidate；Retire Condition

SME review：<12 months old；Unverifiable claims；Redundant expertise；No assigned owner

Technical health：200 status；404/5xx errors；Duplicate H1；Canonical issues

Verification Steps

Cross-check three sample URLs against:

Google Search Console URL inspection
Analytics conversion paths
CMS revision history

Validate retirement candidates with:

301 redirect mapping
Backlink profile
Internal link audit

Exception Handling

Legacy Content: Preserve if meeting two criteria:
Historical rank position >3
Active backlinks from .edu/.gov
Regulated Content: Require legal review regardless of traffic
AI-Generated Pages: Must pass human verification check

Quality Gate

Inventory is ready for redesign when:

Retirement list has approved redirect targets

Building a Website Content Inventory

Creating a comprehensive website content inventory is a critical step before undertaking a redesign. This process involves cataloging every URL on your site and evaluating it against key criteria to inform decisions about migration, rewriting, merging, or retiring content.

Step 1: Gather and Organize URLs

Start by compiling a list of all URLs on your website. Use tools like site crawlers or CMS exports to ensure completeness. Organize these URLs in a spreadsheet or database with fields for:

URL: The full path of the page.
Ownership: The team or individual responsible for the content.
Traffic Data: Metrics such as page views, unique visitors, and bounce rates.
Conversion Rates: Percentage of visitors who complete desired actions.
Freshness: Date of last update or review.
Factual Status: Whether the information is current and accurate.

Step 2: Evaluate Content Against Criteria

Assess each URL based on predefined criteria to determine its value and relevance:

Ownership: Ensure there is a clear owner for each piece of content.
Traffic: Identify high-traffic pages that are critical to user engagement.
Conversion: Highlight pages that drive significant conversions.
Freshness: Flag outdated content that needs updating.
Factual Status: Verify the accuracy of information presented.

Step 3: Make Migration Decisions

Based on the evaluation, decide the fate of each URL:

Migrate: Keep the content as is, moving it to the new site.
Rewrite: Update or improve the content before migration.
Merge: Combine similar pages to reduce redundancy.
Retire: Remove outdated or irrelevant content.

Handling Exceptions and Acceptance

Define exceptions and acceptance criteria for edge cases:

Exceptions: Pages with unique requirements or constraints.
Acceptance Checks: Verify that migrated content meets all criteria.
Exit Paths: Plan for redirects or archival of retired content.

By following these steps, you can ensure a thorough and effective website content inventory that supports your redesign efforts.

Content Inventory Implementation Framework

A website content inventory requires structured data collection to inform migration, consolidation, or retirement decisions. This segment covers ownership assignment with escalation protocols.

Ownership Field Definitions

Business Owner (text field): The department or role accountable for content accuracy and conversion goals. Example: Product Marketing for spec sheets. Verification: Cross-reference with org charts or CMS metadata.

Editorial Owner (text field): The individual responsible for updates and style compliance. Example: Jane Doe, Technical Writer. Verification: Check byline fields or publishing workflows.

Technical Owner (text field): The team handling CMS access, templates, or integrations. Example: Web Platform Team. Verification: Review IT service catalogs.

Review Cycle (dropdown): Frequency of mandatory reviews. Options: 30 days, 90 days, Annual, Trigger-based. Default to Annual with these exceptions:

Regulatory content requires 30 days
Pricing pages require 90 days
Campaign landing pages use Trigger-based tied to offer expiration

Escalation Path (text field): Contacts when ownership is unclear or deadlines missed. Format: Name (Role), Email, SLA Hours. Example: Content Ops Lead, [email protected], 48h.

Handoff Protocol

Stale Ownership Detection: Flag records where:

Email bounces occur for 3+ review notifications
No edits in 2x review cycle duration
Department names match reorg announcements

Reassignment Workflow:

Notify current owner with 5-day response window
CC escalation path on day 6
Auto-reassign to department head at day 10

Acceptance Criteria:

0 orphan pages in CMS without technical owner

Verification Matrix

Check：Method；Threshold

Owner responsiveness：Audit ticket response times；<72h for critical pages

Structured Content Inventory for Redesigns

A website content inventory is not a sitemap. It’s a decision tool that answers:

Who owns this content now?

Does it drive traffic or conversions?

Is it factually current?

Should we migrate, rewrite, merge, or retire it?

Inventory Fields for Actionable Decisions

Build your inventory as a spreadsheet with these verified fields:

URL: Page address (export from Screaming Frog or site: search)
Content Owner: Department or individual responsible for updates
Last Review Date: When facts were last validated (check HTTP headers or CMS)
30-Day Traffic: Google Analytics sessions (compare to site average)
Conversion Path: Associated lead form or revenue event (if any)
Fact Check: [Current/Outdated/Unverified] based on SME review
Redesign Action: [Migrate/Rewrite/Merge/Retire] with rationale

Verification steps:

Cross-reference traffic data with Google Search Console
Confirm ownership via CMS audit logs

Decision Criteria and Exceptions

Migrate if:

Traffic > site average AND facts current
Conversion path exists

Rewrite if:

Traffic > average BUT facts outdated
High-value topic with poor engagement

Merge if:

SME confirms topics are equivalent

Retire if:

No conversion path AND owner concurs

Exception handling:

Legal/regulatory pages require compliance review before changes
High-authority backlinks may justify keeping low-traffic pages

Limited Rollout Protocol

Observation: Log time per page and decision conflicts
Adjust: Refine criteria based on operational reality

Acceptance checks:

Inventory time averages <8 minutes/page

admin