A content inventory solves that problem by cataloging every content asset on a website and recording attributes such as its URL, format, owner, status, and performance data. Content teams can use this single source of truth to find outdated or duplicate pages, assign ownership, and decide what to update, consolidate, redirect, or remove.
This guide explains what a content inventory includes, how it differs from a content audit, how to build one, and which content inventory software can automate parts of the process. It also explains how Content Hub can support an inventory of HubSpot-hosted content.
Table of Contents
- What is a content inventory?
- Content Inventory vs. Content Audit
- What a Content Inventory Should Include
- How to Carry Out a Content Inventory
- Content Inventory Tools to Automate the Work
- Frequently Asked Questions About Content Inventory
- Create your content inventory today.
What is a content inventory?
A content inventory is a structured catalog of a website’s content assets and their attributes. Each row usually represents one URL and records details such as the page title, content type, owner, status, business goal, and performance data.
The inventory shows a team what exists before it evaluates quality or makes publishing decisions. As a site grows across blogs, landing pages, product pages, and resource libraries, that shared record helps marketers find content, compare it, and assign responsibility for what happens next.
Why a Content Inventory Matters for Website Performance
Content teams can use a centralized inventory to:
- Reduce duplicate and outdated content. The inventory reveals pages that cover the same topic, contain old information, or no longer support a business goal.
- Allocate resources with evidence. Performance and business fields help teams prioritize work rather than rely on assumptions.
- Strengthen content governance. Named owners, statuses, and review dates make responsibility visible.
- Accelerate content audits. A complete URL list gives the audit a reliable starting point and lets reviewers focus on evaluation.
Content Inventory vs. Content Audit
A content inventory catalogs assets and their attributes while a content audit evaluates those assets’ quality, performance, and strategic value. The inventory answers, “What do we have?” The audit answers, “What should we do with it?”
Teams usually build the inventory first, then add audit fields such as Action, Priority, and Notes to the same tracker. HubSpot’s content audit guide explains how to evaluate the resulting list.
My take: Treat the inventory and the audit as distinct stages within a single workflow, not as separate files. Adding audit columns to the inventory preserves context and avoids duplicate maintenance. Nielsen Norman Group also recommends choosing one tool to house both.
What a Content Inventory Should Include
A website content inventory should record enough information to identify each asset, understand its purpose, measure its performance, and assign a next action. Start with the fields the team can maintain consistently, then add fields that support a specific decision.
Here is an illustrative content inventory example:

Pro tip: A website content inventory template works best when every column has a definition and a controlled set of values. Start with URL, title, content type, owner, status, business goal, and action; add more fields only when the team will use them.
How to Carry Out a Content Inventory
A content inventory requires a clear process to complete efficiently. Jumping in without a defined scope or tracking system leads to incomplete data and a spreadsheet that gets abandoned before it delivers value. The steps below walk through the process of building a content inventory from start to finish.
Step 1: Define the scope of your inventory.
Decide which content and systems the inventory will cover. A full-site inventory can include every indexable and nonindexable page across the main domain and subdomains. A focused inventory can cover one section, content type, market, or customer journey.
Write down the inventory’s goal, included properties, excluded properties, date range, source systems, and intended output before collecting URLs. For example, a migration project may require every live and redirected URL, while a topic-cluster review may need only the relevant blog posts, landing pages, and performance data.
Pro tip: If a full-site inventory exceeds the team’s current capacity, choose one high-priority section and complete it end-to-end. A finished pilot also reveals which fields and workflows the broader inventory will need.
Step 2: Choose your tracking method.
Choose one place to maintain the inventory.
- A spreadsheet works for a focused or early-stage inventory.
- A database adds stronger filtering, permissions, and automation.
- A content-management platform can supply records for the content it hosts.
Teams that publish across several systems usually combine a crawler or platform export with one central tracker. Use this maturity model to match the setup to the team’s operating complexity:
Teams can use Content Hub to create, manage, and review HubSpot-hosted blog posts, landing pages, and website pages. For a cross-platform inventory, combine those records with crawler and source-system data in the central tracker.
Step 3: Crawl your website to collect URLs.
Run a website crawler to collect linked URLs and export fields such as status code, indexability, canonical URL, page title, meta description, and H1. Define the crawl settings and scope before treating the export as the inventory’s starting list.
Then compare the crawl with XML sitemaps, analytics landing pages, Search Console pages, CMS records, and any migration or redirect files. That reconciliation can uncover orphaned pages, noindexed pages, and other URLs that a link-based crawl may not discover.
For HubSpot-hosted content, Content Hub’s management views can help teams review website pages, landing pages, and blog posts. Teams that manage additional domains, subdomains, or custom applications should still reconcile those assets in the cross-platform tracker.
Step 4: Populate your inventory fields.
Import the crawler’s page title, meta description, H1, canonical, status code, and indexability fields into the tracker. Then add information that automated tools cannot reliably determine, including content type, owner, business goal, customer journey stage, primary CTA, and audit notes.
Standardize field names and allowed values before several contributors work on the file. For example, choose one status vocabulary — such as Published, Draft, Needs review, and Retired — instead of allowing contributors to enter several labels for the same state.
Pro tip: Divide a large inventory by site section or content type, assign each segment to a named contributor, and require a final quality-control pass. Importing machine-readable fields first leaves contributors to focus on context and judgment.
Step 5: Pull performance data.
Add metrics that match each page’s goal. Performance data helps teams compare reach and outcomes, but no single metric proves that a page is good, bad, or ready for removal.
- Google Analytics 4: Record views, active users, average engagement time, and relevant key events from the Pages and screens report.
- Google Search Console: Record clicks, impressions, click-through rate, and average position for each page.
Use the same reporting window for every row, label the date range, and preserve the extraction date. Compare performance with business value, content accuracy, links, conversions, and search intent before assigning an action.
Step 6: Assign ownership and status to each page.
Assign each URL to a named person or team that can confirm its accuracy and coordinate the next action. Then apply a controlled status such as Published, Draft, Needs review, or Retired.
Keep page ownership separate from inventory stewardship. Page owners maintain their assets; one inventory steward maintains the tracker’s structure, definitions, permissions, and review cadence. That distinction prevents shared responsibility from becoming unowned work.
Step 7: Identify gaps and opportunities.
Review the completed inventory for missing owners, outdated facts, overlapping topics, weak performance, broken journeys, and subjects the site does not cover. Use evidence from the page, analytics, search data, business goals, and customer needs rather than assigning an action based on publication age alone.
Use a decision-and-action matrix to standardize the review:
The inventory makes it easier to spot content scaling mistakes because reviewers can compare ownership, goals, topics, and actions in one place.
For teams evaluating answer engine optimization (AEO), HubSpot’s AI Search Grader provides a free, one-time diagnostic of how ChatGPT, Perplexity, and Gemini represent a brand. It scores sentiment, presence quality, brand recognition, share of voice, and market position. Use those findings as brand-level visibility signals alongside page-level search and analytics data.
Step 8: Set a maintenance cadence.
Update the inventory whenever the team publishes, revises, redirects, or removes content. Then schedule a recurring review that matches publishing velocity, regulatory risk, and planning cycles. A fast-moving newsroom may review recent changes every month, while a smaller, stable site may use a quarterly review.
Refresh performance data before audits, migrations, and major planning exercises, and record the extraction date for each. Nielsen Norman Group notes that inventories and audits “are ongoing tasks, so they’re never really finished.”
Pro tip: Assign one inventory steward to maintain the tracker’s structure and schedule. Keep individual page owners responsible for content accuracy and action items.
Content Inventory Tools to Automate the Work
Content inventory software can reduce manual collection, organize records, and support recurring reviews. The following four tools serve different jobs: managing HubSpot-hosted content, crawling a site, combining crawl and SEO data, and maintaining a collaborative tracker.
1. Content Hub

HubSpot’s Content Hub is AI-powered content marketing software for creating, managing, and optimizing content. Its management tools give teams a single place to work with HubSpot-hosted website pages, landing pages, and blog posts. In contrast, its reporting and SEO tools help them review results and identify optimization opportunities.
Content Hub can supply the HubSpot-hosted portion of a content inventory. When teams also use HubSpot Smart CRM, shared platform data can connect content activity with customer journey outcomes. Teams that publish in other content management systems or custom applications should combine those records with crawler and source-system data in a cross-platform tracker.
Key Features
- Content management. Teams can create, organize, update, and publish website pages, landing pages, and blog posts from the platform.
- Reporting and SEO. Reporting dashboards show content results, while SEO recommendations help teams identify optimization opportunities.
- AI-assisted creation. The AI content writer helps teams draft and repurpose content as part of their workflow.
Best for: Teams that manage a substantial share of their website and blog content in HubSpot and want those records close to their publishing workflow.
Pricing: Content Hub includes free content marketing tools for up to two users. The detailed pricing page currently lists Starter at a promotional rate of $7 per seat per month for eligible new customers, compared with a standard rate of $20 per seat per month. Professional starts at $450 per month with an annual commitment and includes three Core Seats. Enterprise starts at $1,500 per month and includes five Core Seats.
What we like: Content Hub gives teams a practical source of truth for the content it hosts, without requiring them to treat a single platform as an inventory of the entire web estate. At Bea’Viewed, I use Content Hub to organize the blog structure before launch and maintain a separate spreadsheet for pages in the Next.js application. That split keeps each system’s scope clear.
2. Screaming Frog SEO Spider

Screaming Frog SEO Spider is a desktop website crawler for Windows, macOS, and Linux. It discovers linked URLs and collects on-page and technical fields that teams can export as the starting point for a content inventory.
The crawler works especially well for URL discovery and machine-readable fields. Teams should still reconcile their output with sitemaps, analytics, Search Console, and content-system records before calling the inventory complete.
Key Features
- URL and metadata export. The crawler collects URLs, status codes, indexability, canonical URLs, page titles, meta descriptions, and headings in exportable tables.
- Issue detection. It identifies broken links, redirects, duplicate elements, missing metadata, and other technical signals that can inform an audit.
- Advanced crawling and integrations. The paid version unlocks JavaScript rendering, crawl configuration, saved crawls, and integrations with Google Analytics and Search Console.
Best for: SEO leads and technical content managers who need an exportable URL and metadata foundation for an inventory.
Pricing: The free version crawls up to 500 URLs per crawl. A paid license costs $279 per user per year, removes the 500-URL crawl limit, and unlocks advanced features. The available crawl size still depends on the allocated memory and storage.
What we like: The Page Titles view consolidates URLs, title tags, meta descriptions, status codes, and indexability into a single exportable workspace. When I built sarahweissbard.shop for a personal injury attorney, I started its inventory with a Screaming Frog crawl and then enriched the export in a spreadsheet. I use the same workflow when I prepare website inventory deliverables for clients.
3. Semrush

Semrush is an SEO and AI search platform whose Site Audit tool crawls a domain, reports on technical issues, and supports structured exports. Teams can combine that crawl data with keyword and competitive research to prioritize inventory rows for closer review.
Unlike a standalone inventory tracker, Semrush focuses on discovery and analysis. Export its findings to the system where the team assigns owners, goals, statuses, and actions.
Key Features
- Site Audit. The tool crawls a site, organizes technical findings, and lets teams review affected URLs.
- Keyword and competitive research. Teams can compare search visibility and identify pages or topics that need deeper analysis.
- Cannibalization analysis. Pro+ includes keyword cannibalization analysis that can help reviewers investigate overlapping pages.
Best for: Content strategists and SEO leads who want to combine crawl findings with keyword and competitor context.
Pricing: The SEO plan costs $139 per month or $117.33 per month when billed annually and includes a Site Audit. Pro+ costs $299 per month, or $248.17 per month when billed annually, and includes historical SEO data, content optimization, and keyword cannibalization analysis. Semrush offers a seven-day free trial.
What we like: Semrush adds search and competitor context to the URL list. For Bea’Viewed, I use that context to compare beauty-category pages with competing sites and decide which inventory rows deserve deeper review first.
4. Airtable

Airtable is an app-building and data-management platform that teams can configure as a collaborative content inventory. A base can store URLs, owners, statuses, goals, metrics, and audit actions while presenting the same records through different views.
Airtable does not crawl a website on its own. Import crawler and source-system data, then use the base to maintain ownership and workflows.
Key Features
- Custom fields and views. Teams can define inventory fields, then filter, sort, group, and display records by content type, owner, status, or priority.
- Collaborative data entry. Forms and shared views help contributors add or review records without changing the underlying schema.
- Automations. Scheduled automations can create reminders or other recurring maintenance actions.
Best for: Content operations teams that need a flexible, collaborative tracker across several contributors or publishing systems.
Pricing: Airtable offers a Free plan. Team costs $20 per user per month when billed annually, and Business costs $45 per user per month when billed annually. Enterprise Scale uses custom pricing.
What we like: Airtable keeps the familiar spreadsheet grid while adding controlled fields, filtered views, grouping, and automation. Those features make it easier to give different contributors focused views without creating separate versions of the inventory.
Frequently Asked Questions About Content Inventory
These answers address the maintenance, tooling, ownership, and action questions that commonly arise after a team creates its first content inventory.
How often should a content inventory be updated?
Update the relevant row whenever the team publishes, changes, redirects, or removes a page. In addition, schedule a recurring review based on publishing velocity and risk; monthly or quarterly reviews often work better than waiting for a full annual rebuild.
Run a broader review before a site migration, redesign, strategy reset, or major audit. Refresh performance data at the same time and record the reporting window.
What tools are best for large websites?
Large or complex sites benefit from a crawler that automates URL and metadata collection. Screaming Frog SEO Spider and Semrush Site Audit can support that discovery work, while source-system exports help teams reconcile assets a crawl may miss.
Store the combined records in a governed spreadsheet, database, or inventory platform that supports consistent fields, permissions, filtering, and ownership. Choose the stack based on site architecture and workflow needs rather than a single page-count threshold.
Who should own the content inventory?
Assign one inventory steward — often a content operations manager, content strategist, SEO lead, or marketing manager — to maintain the tracker’s structure, definitions, permissions, and review cadence.
Assign individual page owners separately. They should confirm accuracy, update their records when content changes, and complete assigned audit actions.
What’s the difference between consolidating and redirecting content?
Consolidation is a content decision: a team combines useful material from overlapping pages into one stronger primary page. A redirect is a technical instruction: a permanent server-side redirect sends users and search engines from a retired URL to a relevant successor.
Consolidation often leads to a redirect, but the actions are not interchangeable. Redirect a retired URL only when the destination provides a relevant replacement. Do not send removed pages to an unrelated homepage merely to avoid a 404.
How do we prevent the inventory from going stale?
Build inventory updates into publishing, revision, migration, and retirement workflows. Require page owners to update their rows when content changes, and ask the inventory steward to monitor completeness and run scheduled reviews.
Airtable can run scheduled automations for recurring work. Content Hub’s management tools can reduce manual lookup for HubSpot-hosted assets, while the cross-platform tracker remains the source for content stored elsewhere.
Create your content inventory today.
A content inventory provides a team with a single, reliable record of its URLs, owners, goals, status, performance, and next actions. Start with a defined scope, collect and reconcile URLs, add the fields the team will use, and assign one steward to keep the system current.
If the site uses Content Hub, begin with the HubSpot-hosted assets and combine them with crawler or source-system records for content stored elsewhere. That approach keeps the inventory complete without overstating any one platform’s scope.
At Bea’Viewed, I built the inventory in phases: I tracked the live application pages first and added the blog structure as launch approached. That process revealed gaps and review needs before the site scaled. My advice to another founder or content lead is simple: build the habit early, while the inventory is still easy to maintain.
CMS