---
name: how-to-inventory-every-podcast-youve-been-on-and-why-its-one-of-the-highest-roi-things-you-can-do
description: "Bring your podcast visits into one checked list. Keep one row for each real appearance."
category: Content Factory — Process
stage: Process
definitive_article: https://blitzmetrics.com/how-to-inventory-every-podcast-youve-been-on-and-why-its-one-of-the-highest-roi-things-you-can-do/
status: complete
---

# How to inventory every podcast you've been on

Your past interviews can help people learn what you know. This guide brings them into one list so your team can find and use them. Start with your name, known shows, and any list you already have.

**The path:** Name variants → Discovery leads → Verified appearances → One master list.

**Use this when:** A person needs a consolidated verified appearance inventory across podcast and video sources.

## Inputs
- The person’s verified name/variants, known shows, companies and public identity pages.
- Existing inventory and authorized supplied internal records, with private details kept out of public exports.
- Read access to Listen Notes, Podchaser, YouTube and show pages; account/profile changes have separate scope.
- A master sheet, date/scope, verification statuses, content-use rights and next owner.

## First-run prompt

> Merge the supplied and discovered podcast leads into one source-backed appearance inventory. Verify this person’s role, combine mirrors of the same episode, and keep mentions and uncertain identities separate. Record coverage, rights and metric gaps. Prepare a useful reuse queue without inventing appearances, contact permission or ROI.

## Steps
1. Set up one master record per real appearance with title, show, host, date, role, canonical source, platform links, audio/video availability, verification evidence and next use.
2. Search known names and variants in Listen Notes, Podchaser, YouTube, show websites and the person’s site. Record each source/query/date and any access or coverage limits.
3. Use supplied private archives only within the task’s scope. AI search can suggest leads but must retain a real source URL for verification. Do not turn a claimed result count into a confirmed total.
4. Verify that this person actually appeared and in what role. A mention, same-name person or quote repeated by the host is not a guest appearance. Keep uncertain leads in a review queue.
5. Merge directory mirrors, audio/video copies and reuploads of the same episode into one appearance with multiple links. Use show/title/date/participants/content evidence, not title similarity alone. Separate genuinely different appearances even if they share a show.
6. Record source media availability and permitted reuse separately from presence. A verified guest credit does not grant download, editing or advertising rights.
7. Prioritize useful verified material with comparable observed evidence and the real GCT. Top 20% is a method option with an explicit eligible denominator; unavailable engagement is UNKNOWN, not zero and not a fabricated ranking.
8. Keep hosts and collaborators in a sourced relationship list when useful, without inferring friendship or permission to contact them. Do not claim, edit a profile or send outreach merely because it was discovered.
9. Return the deduplicated inventory, source coverage log, verified/rejected/unresolved totals and priority handoff. If monitoring is part of the job, reuse an authorized alert or named review cadence, with the first result checked before claiming it works.

## Definition of done (QA checklist)

- [ ] One master row represents each verified appearance, with preserved platform links.
- [ ] Role/identity evidence separates appearances from mentions and same-name collisions.
- [ ] Source coverage, rights and metric gaps are explicit.
- [ ] Totals reconcile and monitoring/outreach states are truthful.

## Example(s)

**Fictional teaching example — no real appearances counted.** Listen Notes finds a sample “Alex on Shop Talk” episode. YouTube has the same conversation under a shorter title, and the host site links both. They become one appearance with three links.

A different episode says “Alex once told me…” but has only the host speaking. That is a mention, not a second guest appearance. The sample sheet records one verified appearance and one rejected mention, with a third same-name lead awaiting review. It does not claim a complete lifetime total from those searches.

## Handoff and Content Factory context

The content owner uses permitted priority sources for [Archive and prepare a work copy](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). Platform-specific discovery can use [Listen Notes inventory](https://local-service-spotlight.github.io/task-library/?task=how-we-use-listen-notes-to-find-track-and-repurpose-every-podcast-appearance#task-how-we-use-listen-notes-to-find-track-and-repurpose-every-podcast-appearance) and [Podchaser credit review](https://local-service-spotlight.github.io/task-library/?task=how-we-use-podchaser-to-amplify-authority-and-repurpose-podcast-content#task-how-we-use-podchaser-to-amplify-authority-and-repurpose-podcast-content) without automatically editing public profiles.

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

Initial consolidation, then an agreed delta review. Optional alerts need real setup, access, a receiver and verification; no automatic recurring contact list is implied.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Process
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 3, gating 2 (runs every factory cycle or weekly)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/how-to-inventory-every-podcast-youve-been-on-and-why-its-one-of-the-highest-roi-things-you-can-do/
- Exact task: [How to inventory every podcast you've been on](https://local-service-spotlight.github.io/task-library/?task=how-to-inventory-every-podcast-youve-been-on-and-why-its-one-of-the-highest-roi-things-you-can-do#task-how-to-inventory-every-podcast-youve-been-on-and-why-its-one-of-the-highest-roi-things-you-can-do)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Podchaser credit meanings](https://support.podchaser.com/en/articles/6555701-what-is-a-credit)
- [Listen Notes alerts and transcript limits](https://www.listennotes.help/article/106-how-to-track-podcast-mentions-with-listen-alerts-the-ultimate-podcast-social-listening-tool)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Complete lifetime coverage cannot be certified from directory search alone; missing records/rights remain explicit.