Conversations with Claude: Can You Conduct a Content Audit?

Conversations with Claude: Can You Conduct a Content Audit?

Audio Version ($)

During one of our recent Claude Code Office Hours, a participant asked, "Can we zoom out? Help me understand what I can use Claude Code for."

This is a great question. I was so focused on how to help people set up Claude Code that I forgot to share the why. It's easy to forget that not everyone is already sold on this new way of working.

So today, I'm starting a new series called Conversations with Claude. My goal with this series is to show you how and why I use Claude Code across a wide variety of tasks.

I'm going to start with a fairly complex use case (a content audit of Product Talk) that was surprisingly easy to do with Claude. I'll first show you the full conversation and then I'll explain what I had in place that made this work well. Then we'll dive deeper and see how Claude helped me quickly write an article that addressed one of the biggest content gaps.

If you are new to Claude Code and want to learn what to do first, start here.

đź’ˇ
This series was inspired by my personal usage of Claude Code. I'm a big fan and I like to share what works for me with readers.

I have not received any compensation from Anthropic for writing this series. And you can trust that if that ever changes, I will disclose it. This is not only required by the FTC here in the US, I strongly believe it is the right thing to do. You can count on me to do so.

Okay, let's dive into today's topic.

Claude, Can You Conduct a Content Audit for Product Talk?

SEO is one of those things that I should do, but I never get around to it. I mostly pick topics based on what I'm interested in week to week. But I know this isn't the best strategy for growing my audience.

I've been meaning to do a content audit for ages and just haven't gotten around to it. I finally wrote up a task and wondered if Claude could help.

A screenshot of the task I created for my content audit.

Instead of doing this task myself, I decided to ask Claude to do it. Here's how that conversation went.


Teresa: Can you help me with this project? First, ask any clarifying questions. Then work step-by-step and add notes to the task file as you work.

Teresa shares the content-audit task file, which asks Claude to extract keywords from the CDH book, get search volumes, evaluate blog coverage, and suggest content improvements.

Claude: Found the CDH Book (15 chapters + intro) and the Product Talk Archives. Before I dive in, a few clarifying questions:

  1. Scope of keywords: Should I focus strictly on concepts unique to or heavily associated with Teresa's work (e.g., "opportunity solution tree," "continuous discovery"), or also include broader product management terms the book covers (e.g., "product outcomes," "assumption testing," "customer interviewing")?
  2. Keyword geography: For Keywords Everywhere, what country should I use? US only, or also UK/global?
  3. Blog coverage assessment: When evaluating how well the blog addresses each keyword, what counts as "well covered"?
    A dedicated deep-dive post on the topic?
    Or also posts that mention the concept as part of a broader article?
  4. Output format: Should I add findings directly to the task file, or create a separate deliverable file?

Teresa: 1. both 2. us only is a good place to start 3. evaluate this based on how well we rank for the keyword, if we rank reasonably well, you might suggest content improvements to rank better, if we don't rank at all, then you might suggest a whole new article 4. add to the task file

Claude reads all 15 CDH book chapters, extracts ~100 keywords, runs them through Keywords Everywhere in two batches of 50, then pulls producttalk.org's current domain rankings and traffic metrics.

Claude: The content audit is complete. Here's a summary of what I found:

The good news: producttalk.org owns its branded terms — #1 for "product discovery," "opportunity solution tree," "continuous discovery," and "product trio."

The biggest gaps are in broad topics CDH covers but where there's no targeted content:

"Outcomes vs outputs" (1,300/mo) — Arguably THE central thesis of CDH, and no ranking. This is the single biggest gap.

"Product roadmap" (4,400/mo) — Teresa has a strong anti-roadmap POV but no content targeting this.

"Product strategy" (1,900/mo) — Ch 7 argues strategy = opportunity selection. Strong differentiator, no ranking.

"Story mapping" (5,400/mo) — Teresa uses story maps uniquely (for surfacing assumptions). Huge volume.

"Stakeholder management" (2,900/mo) — Ch 13 is entirely about this. No ranking.

"Pre-mortem" (4,400/mo) — Teresa covers this as a product discovery technique. No ranking.

The trojan horse opportunity: High-volume generic terms like story mapping, pre-mortem, and usability testing could bring in readers who don't know about CDH yet. Write about these broadly-searched topics with Teresa's specific product-discovery angle.

I've added full details, keyword volumes, SERP positions, and prioritized recommendations for 15+ new articles to the task file. Want to discuss any of the recommendations?


In just a few minutes, Claude generated:

  • An analysis of what keywords I ranked for and at what position.
  • A list of high-volume, medium-volume, and lower-volume (but strategic) keywords where I didn't rank at all, but had relevant content.
  • A list of new topics that I should cover to address these gaps.
  • A list of articles that I could update to improve their rankings.

This worked far better than I thought it would.

How to Conduct a Content Audit with Claude

A screenshot of Obsidian showing all of my book chapters as markdown files.
I gave Claude access to my book and all of my blog articles in markdown files.

So here's the thing: If you just open Claude.ai and ask it to do a content audit of your site, it's not going to do a great job. So how did I get such high-quality output?

I'm going to walk you through exactly how I set this up—including what context files I set up, what APIs I used, and how I iterated with Claude. I'm also going to show you how I dove even deeper and wrote my first long-form article designed to address one of the biggest content gaps Claude identified.

Product Talk is a reader-supported publication. If you want to keep reading, you'll need to upgrade to a Supporting Membership or a CDH Membership.