---
title: Clean up topics and tags
description: Inspect prompt classifications and fix duplicates, thin topics, and
  tags that no longer distinguish the data.
canonical_url: https://orchestor.io/docs/en/cli/workflows/taxonomy-audit
markdown_url: https://orchestor.io/docs/en/cli/workflows/taxonomy-audit.md
contentType: how-to
---

# Clean up topics and tags

Inspect prompt classifications and fix duplicates, thin topics, and tags that no longer distinguish the data.

## When to use this workflow

> “Our report filters are cluttered; clean up the topics and tags.”

## Before fetching

Identify the reports people use and the distinctions they need. Do not delete a topic solely because it is small; check whether it represents a distinct intent.

Complete the [CLI quickstart](https://orchestor.io/docs/cli/quickstart.md) and confirm the workspace with `orc workspace current --json`. Replace example IDs, URLs, dates, and settings. Apply only approved mutations.

## 1. Map prompts to their classifications

Read the complete lists and find unassigned prompts, near-duplicate topics, and tags applied to nearly every prompt. Separately record missing brand context.

```bash
orc topics list --json
orc tags list --json
orc prompts list --json
orc prompts tags get YOUR_PROMPT_ID --json
orc brands get YOUR_BRAND_ID --json
```

## 2. Prioritize by impact on report interpretation

Have the agent prepare a before-and-after mapping. Prioritize distinctions that currently distort comparisons, then settle prompt IDs and retained tag sets.

## 3. Apply and verify each approved change

Replace the approved tag set using the current config_revision and read it back. If a concurrent edit conflicts, refetch and review the difference.

```bash
orc prompts tags update YOUR_PROMPT_ID --tag-ids YOUR_TAG_IDS --config-revision YOUR_CONFIG_REVISION --json
orc prompts tags get YOUR_PROMPT_ID --json
```

## Deliverable

Deliver reasons, before-and-after mappings, verified IDs, and remaining unclassified prompts. Record the change time for future comparisons.

On fetch failure, retain the error and request scope. Do not count empty data, incomplete pagination, or missing permissions as a completed investigation.

## Next steps

[Workflow index](https://orchestor.io/docs/cli/workflows.md) · [Reviewing prompt coverage](https://orchestor.io/docs/cli/workflows/prompt-coverage.md) · [Clean up brands and competitors](https://orchestor.io/docs/cli/workflows/brand-setup.md) · [Build a custom report](https://orchestor.io/docs/cli/workflows/custom-report.md)

If a failure remains, [report it and verify the fix](https://orchestor.io/docs/cli/workflows/workflow-feedback.md), including this workflow and the failed step.

---

[Documentation index](https://orchestor.io/docs/llms.txt)