I’ll be honest: when I cracked open Paula Land’s Content Audits and Inventories again this week, I figured I was just doing a refresher. Box-checking before the real work begins. I’ve done audits before. I know the drill. Crawl the site, build the spreadsheet, evaluate the content, make recommendations. Easy enough, right?

But here’s the thing about re-reading a craft book when you’re actually about to do the thing it describes — suddenly everything hits differently. The first seven chapters, which are really about before you audit, ended up being the ones I couldn’t stop thinking about.

The Three Questions That Should Stop You in Your Tracks

Land opens with what seems like a simple exercise: before you begin, ask yourself why you’re auditing, what you need to learn, and what you’ll actually do with what you find. Three questions. Shouldn’t take long, right?

Except — try really answering them. Not the polished version you’d put in a proposal, but the honest version. In my experience, the answer to “why are you auditing?” is often some variation of “because the client asked us to” or “because we’re doing a redesign.” Those are fine reasons! But they’re not goals. They’re contexts. And Land is pretty clear that the difference matters enormously when you’re trying to scope the work and, later, when you’re trying to defend your recommendations.

She suggests formulating a hypothesis — something like: if the content on this site is clear, current, and audience-appropriate, then engagement and conversions will improve. I love this framing because it forces you to name your dependent variables. You can’t audit against a vague sense of “better.” You have to decide what “better” even means, and for whom.

I spent an embarrassing amount of time this week just trying to write a clean goal statement for the project I’m about to start. It’s harder than it looks.

Content Is a Business Asset (And Treating It Like One Is Weirdly Radical)

The third chapter is ostensibly about building a business case — the kind of thing content practitioners have to do when leadership doesn’t immediately understand why they should pay for an audit. But there’s a more interesting thread running through it about what it means to treat content like an asset at all.

“Content is a business asset, and just as you manage the other assets you’ve invested in, you should manage your content.”— Paula Ladenburg Land, Content Audits and Inventories, 2nd ed.

This sounds obvious, but I think it’s actually pretty radical in a lot of organizations. We have processes for managing physical assets, financial assets, personnel. Content tends to accumulate in the dark — published and then effectively abandoned, growing stale, contradicting newer content, sending mixed messages to users who are trying to make real decisions.

Land frames the ROI argument in practical terms: what does bad content cost you? Lost conversions, customer service calls that wouldn’t need to happen if the FAQ was accurate, legal exposure from outdated compliance language, brand incoherence when a visitor hits three different pages that describe the same product in three different ways. These aren’t theoretical harms. They’re real, and they compound over time. The audit is how you find them.

What I keep coming back to is the idea that you’re not auditing to criticize the content team. You’re auditing because the business has been running on assumptions — about what’s out there, who’s managing it, whether it’s working — and assumptions, however confident, are not data.

---

Organizational Readiness: The Part Nobody Wants to Talk About

Here’s the section I found myself rereading twice: the stuff about organizational readiness and resistance. Land is candid about something that most methodological guides tend to skip over — the audit doesn’t happen in a vacuum. It happens inside an organization full of people who may have complicated feelings about having their content evaluated.

She distinguishes between two kinds of readiness: readiness to participate in the audit and readiness to act on the recommendations afterward. Both matter, but the second one is the one that tends to kill projects in the end. I’ve seen great audits produce beautifully detailed spreadsheets and thorough findings decks that then sat on a shared drive for eighteen months until the contract ended. The work was done. Nothing changed.

The advice Land gives here is subtle but important: meet the content creators and stakeholders early, understand how things got to where they are, and frame the audit as discovery rather than judgment. “We need to understand what’s working as well as what isn’t” lands very differently than “we need to find everything that’s wrong.” The goal is essentially the same. The experience of being on the receiving end is not.

She also touches on the politics of working as a consultant inside a client organization — something I’m thinking about a lot right now — and the concept of leading from the side, building consensus across teams where you don’t have direct authority. It’s not glamorous project management advice, but it’s the kind of thing that makes or breaks whether the actual recommendations ever get implemented.

The Inventory: Unglamorous, Indispensable

Chapter 7 is about the content inventory — the part where you actually catalog everything that’s on a site. It’s often described as the tedious foundation-laying work that precedes the interesting analysis. And it is, honestly, kind of tedious. But Land makes a compelling argument for why the inventory isn’t just logistical scaffolding.

She quotes Joe Gollner: “Good data makes for good conversations.” That’s the real value of a well-constructed inventory. When you walk into a stakeholder meeting and can show — concretely, with numbers — that a site has four times as many pages as anyone realized, or that a significant portion of them have no incoming links and almost no traffic, or that the metadata titles across an entire section are duplicated verbatim… you’ve changed the nature of the conversation. It’s not you saying the site has problems. It’s the data.

The inventory also depersonalizes the process at exactly the moment it needs to be depersonalized. By the time you get to the qualitative audit — where you’re making judgments about whether content is well-written, on-brand, useful, current — feelings can run high. The inventory data, gathered neutrally and mechanically, gives everyone a shared factual ground to stand on before opinions enter the room.

---

What I’m Taking Into the Project

Reading these chapters with an actual large-scale audit on the horizon, a few things are sticking with me.

First: I need to spend more time on the goal statement than feels comfortable. Not the elevator pitch version, but the specific, measurable version that actually connects the audit’s findings to something the client cares about. Land’s DMAIC-inspired framework — Define, Measure, Analyze, Improve, Control — is a useful skeleton for this.

Second: the stakeholder interviews matter more than I sometimes give them credit for. They’re not just context-gathering. They’re relationship-building and, sometimes, resistance-defusing. If I go into this project without having genuinely listened to the people who create and manage the content, I’m setting myself up for a beautiful deliverable that no one acts on.

Third: scope is a real decision, not a default. Land is pretty direct about this — you should be able to explain exactly why you’re looking at what you’re looking at and not what you’re not. The temptation is always to gather more data than you’ll use, but over-scoping is its own problem. It burns time and attention, and it can bury the actually actionable insights under a pile of marginally relevant observations.

None of this is revolutionary. But there’s something useful about sitting with the fundamentals right before a big project — not because you’ve forgotten them, but because the practical context changes which parts of them feel most alive. I’ve done audits where I cut corners on some of this upfront work and paid for it later. I’d rather not do that again.

More to come as the work actually starts.