CiteRanger CiteRanger
Content AuditContent StrategySEO

Content Inventory: Build a Complete One in an Afternoon

How to build a complete content inventory from crawl, sitemap and Search Console in one afternoon, and which columns actually matter.

Richard Roth

Richard Roth

Founder & SEO Strategist

October 7, 2026

11 min read

Light interface illustration: a long table with a header row and many rows, cut off at the lower edge

Ask a content team how many pages their site has. You get three answers: what the CMS says, what the sitemap says, and what Google has indexed. All three are wrong in different ways, and the gap between them is where forgotten pages, duplicate articles and outdated facts live. A content inventory closes the gap. It is the least glamorous document in content strategy and the one everything else depends on.

Key Takeaways
  • An inventory is the complete list of your content URLs with basic attributes. It is the input for audits, refresh plans and migrations, not the audit itself
  • Build it from three sources (crawl, sitemap, Search Console) because each one misses pages the others catch
  • Twelve columns are enough for most sites; everything else can be added when a specific project needs it
  • An inventory that is not maintained is a snapshot. Give it an owner and a monthly refresh, or it is stale within a quarter
Let CiteRanger fill the accuracy columns of your inventory automatically Claim 15 Free Credits

What is a content inventory?

A content inventory is the complete list of every content URL on your site. Each one carries the same fixed set of attributes: title, type, topic, author, date, length and its place in the structure. It answers “what do we have” and nothing more.

That restraint matters. Teams that try to build inventory and audit in one pass stall at page 80, because every row turns into a judgement call. The inventory is mechanical: collect, list, done. The judgement happens later, in the content audit, which adds performance data and a decision per page.

Three documents, three jobs:

  • Inventory: what exists (this article)
  • Audit: how it performs and what to do with it
  • Editorial calendar: what happens next and when

Most sites have the third, some have the second, and almost none has a current version of the first. That is the wrong way round.

Why does a site need a content inventory?

Because nobody knows what is on the site, and every content decision made without that knowledge is a guess. Four situations where the absence of an inventory costs real money:

  1. Audits and refresh plans. You cannot prioritise what you cannot see. An audit built on “the pages we remember” misses the forgotten ones, which are exactly the pages most likely to contain outdated facts.
  2. Cannibalisation. Two articles on the same topic, written eighteen months apart by different people, split the ranking signals between them. You only find them by listing everything and sorting by topic.
  3. Migrations and redesigns. A redirect map is an inventory with a second URL column. Sites that migrate without one lose the pages they forgot, and with them the rankings and links those pages held.
  4. Accuracy at scale. Knowing which pages contain prices, statistics or legal claims is the first step to keeping them current. Without an inventory, the time-sensitive pages are invisible until one goes wrong in public.
Good to Know

In the sites we have inventoried, the gap between what the CMS reports and what is actually live is usually somewhere between 10 and 30 percent: old tag archives, test pages, PDF uploads, campaign landing pages, paginated views. Every one of those is a page Google may index and a rater may land on.

How do you build a content inventory in an afternoon?

Pull three lists, merge them on URL, add the attribute columns, and reconcile the differences. On a site with a few hundred pages this takes two to four hours. Here is the sequence.

Step 1: Crawl the site (30 minutes)

Run a crawler such as Screaming Frog SEO Spider against the domain with default settings, then export the internal HTML pages. Keep these columns from the export: URL, status code, title, meta description, H1, word count, canonical URL, indexability, and the crawl depth. If your templates expose dates or authors in the HTML, extract those too.

The crawl gives you what a visitor or a bot can reach by following links. It does not give you orphan pages, which is why you need the next two sources.

Step 2: Pull the sitemap (5 minutes)

Download your XML sitemap or sitemap index. Google’s sitemap documentation describes what it should contain; in practice it is whatever your CMS or framework generates. Export the URL list.

The sitemap gives you what you intend to have indexed. Pages in the sitemap but not in the crawl are orphans: reachable by Google, invisible to users.

Step 3: Export from Search Console (10 minutes)

Two exports. First, the Performance report filtered to the last 12 months, grouped by page: every URL that received at least one impression. Second, the Page indexing report, which lists indexed pages and the reasons for non-indexed ones, including “Crawled - currently not indexed”.

Search Console gives you what Google actually knows about. Pages here that are in neither the crawl nor the sitemap are the forgotten ones: old URLs still indexed, parameters, staging leaks.

Step 4: Merge and reconcile (60 to 90 minutes)

Put all three lists in one sheet, one row per unique URL, with three flag columns: in crawl, in sitemap, in Search Console. Then sort by the flags. Every combination is a finding:

In crawlIn sitemapIn GSCWhat it usually means
YesYesYesNormal, healthy page
YesYesNoIndexed but no impressions, or not indexed: check the indexing report
YesNoYesMissing from sitemap, fix the sitemap generation
NoYesYesOrphan page, add internal links or remove
NoNoYesForgotten page still indexed, decide: redirect, restore or remove
YesNoNoReachable but invisible to Google, often thin or duplicate

Resolve the obvious ones now (sitemap fixes, redirects for dead URLs), and leave the rest as rows with a note. They become audit candidates.

Step 5: Add the attribute columns (30 to 60 minutes)

For each URL, fill the twelve columns below. Most come from the crawl export; type and topic cluster usually need a manual pass or a rule based on URL patterns.

Quick Tip

Assign topic clusters with URL rules first (everything under /guide/ is “guides”, everything with “pricing” is “commercial”) and correct by hand only where the rule fails. Manual classification of 500 URLs takes a day; rules plus corrections take an hour.

Which columns does a content inventory need?

Twelve, in two groups: identity and structure. Add project-specific columns later; do not start with forty.

Identity

  1. URL, canonical, with trailing slash consistency
  2. Title as published
  3. Content type: article, guide, landing page, product, category, legal, news
  4. Topic cluster: the subject area it belongs to
  5. Author: byline, or “none”, which is itself a finding
  6. Published date and last updated date, real values from the CMS

Structure

  1. Word count, body only
  2. Status and indexability: 200, canonical points to self, no noindex
  3. Crawl depth: clicks from the homepage
  4. Internal links in: how many pages link to it
  5. Time-sensitive content flag: does the page contain prices, statistics, laws, versions, dates? Yes or no
  6. Notes: anything found during reconciliation

Column 11 is the one most inventories lack and the one that pays for the whole exercise. It tells you which pages can go wrong on their own. In our experience it is 20 to 30 percent of a typical site, and that minority is where nearly all the accuracy problems live. It is also the column CiteRanger populates automatically, along with the specific facts and sources on each page.

Richard Roth Founder CiteRanger, SEO Strategist

The inventory is where I find the pages the team forgot they had. On one site it was a 2021 pricing comparison, still indexed, still ranking for a commercial query, showing prices that had changed three times since. Nobody had opened it in two years because it was not in the CMS’s “published” view. The inventory found it in an hour. The audit that followed was mostly about that one page.

How do you keep the inventory alive?

By making it the source of truth for every content process instead of a one-off export. Three habits:

Give it an owner and a refresh date

One person, monthly. The refresh is a re-crawl and a re-export, then a diff against the last version: new URLs, removed URLs, changed titles. Fifteen minutes once the process exists.

Add rows before publishing, not after

New content gets a row in the inventory when it is planned, with the type and cluster already set. The published date fills in later. This keeps the inventory ahead of the site instead of behind it.

Let the audit and the refresh plan write back

When the audit decides a page is merged or removed, the inventory row records it. When the update cadence sets a next review date, it lives in the inventory. One sheet, many consumers.

For the accuracy layer specifically, connect a monitor rather than relying on the monthly refresh. Facts change daily; a monthly inventory refresh catches that they changed, not when.

What are the most common inventory mistakes?

  • Starting with the CMS export. It shows what was published in the CMS, not what is live. Start with the crawl.
  • Skipping Search Console. The forgotten pages only show up there.
  • Mixing inventory and audit. Deciding what to do with each page while listing it turns a four-hour job into a four-week one.
  • Too many columns. Forty columns means most are empty. Twelve full columns beat forty half-filled ones.
  • No time-sensitive flag. Without it, you cannot prioritise accuracy work, which is where most of the value is.
  • Building it once. An inventory from January is a historical document by April.

Conclusion

A content inventory is a complete list with twelve columns, built from a crawl, a sitemap and Search Console, reconciled in one afternoon. It is not exciting. It is the document that makes audits, refresh plans and migrations possible, and the one that finds the forgotten pages where outdated facts hide.

Build it this week from the three sources, flag the time-sensitive pages, give it an owner, and put the accuracy layer on a monitor. Everything else in content maintenance gets easier from there.

The inventory feeds two routines directly: the pruning decision for pages that should not be updated, and the monthly update cycle for the ones that should.

The inventory is the input; the content audit tool is the fastest way to fill the accuracy columns for every row.

Frequently asked questions about content inventories

What is the difference between a content inventory and a content audit?
An inventory lists every content URL with basic attributes: what exists. An audit adds performance data and quality assessment and ends in a decision per page: what to do. Build the inventory first; the audit uses it as input.
Which tools do I need for a content inventory?
A crawler such as Screaming Frog for the reachable pages, your XML sitemap, Google Search Console for indexed pages and impressions, and a spreadsheet to merge them. Optionally a tool such as CiteRanger to flag time-sensitive content and outdated facts automatically.
How long does it take to build a content inventory?
For a site with a few hundred pages, two to four hours: crawl, sitemap export, Search Console exports, merging and reconciliation, then the attribute columns. Larger sites take longer mainly in the reconciliation step.
How often should a content inventory be updated?
Monthly, by re-crawling and diffing against the previous version. New content should be added when it is planned, not after publishing. Time-sensitive facts should be monitored continuously rather than waiting for the monthly refresh.
What columns should a content inventory have?
URL, title, content type, topic cluster, author, published and updated dates, word count, status and indexability, crawl depth, internal links in, a time-sensitive content flag, and notes. Twelve columns cover most needs; add project-specific ones later.
Why do I need three sources instead of just a crawl?
Each source misses different pages. The crawl finds what is reachable by links, the sitemap what you intend to index, Search Console what Google actually knows about. Orphan and forgotten pages only appear when you compare all three.
Find outdated facts first15 free credits, no cardStart free