Taxonomies drift
Overlapping categories, single-use tags and terms that mean the same thing, all of it fragmenting your archives.
Bulk edits without a bulk edit plugin.
Or a database query.
Every content site accumulates structural debt: a category taxonomy that made sense in 2019, tags used once each, hundreds of posts missing an excerpt, a drafts folder nobody has opened in a year. The usual options are a bulk-edit plugin that does not quite fit or a database query you would rather not run on production. Talos does it as a described outcome, tracked and reversible.
WNorthstar Studio+ New
Howdy, Alex
Structural debt in content
Bulk edit tools are blunt
They apply the same change to everything selected, with no judgement about individual posts and no way back.
Direct SQL is a bad idea
Writing UPDATE statements against a production wp_posts table is how sites get restored from backup.
What actually happens.
Understand the structure first
Talos discovers your taxonomies and post types, then reports the actual distribution — which terms are used once, which overlap, what is orphaned.
Plan the reorganisation
In Plan mode it proposes a specific mapping before touching anything, so you approve the consolidation rather than discover it.
Apply in tracked batches
Term merges, reassignments and content updates go through manage_taxonomy and manage_content, captured in change sets.
Reverse cleanly if it was wrong
A taxonomy reorganisation you dislike is a rollback, not a restore-from-backup.
The exact tools it uses.
Talos does not improvise. Each of these is a defined tool with validated inputs, a declared risk level and its own policy setting.
Talos never writes SQL against your database. Reads are bounded and read-only; all writes go through validated WordPress APIs.
See the full tool catalogmanage_taxonomy
WriteDiscover taxonomies, then list, create, update, delete and assign terms.
manage_content
WriteList, read, create, update, trash and restore content, plus revisions and meta.
search_posts
ReadKeyword search across posts, pages and public post types.
get_post
ReadLoad a single post or page by ID.
manage_media
WriteList, inspect and edit media, alt text and featured images. Existing attachments only.
manage_menus
WriteNavigation menus and their items.
query_database_readonly
ReadBounded SELECT, SHOW, DESCRIBE and EXPLAIN. Dangerous SQL is blocked and secrets redacted.
preview_change_set
ReadPreview rollback order and conflicts without touching the site.
rollback_change_set
WriteRoll back an approved change set in reverse order. Refuses resources that have drifted.
create_table
ReadInline structured data tables.
Or set it once and forget it.
Any of this can become a workflow. You write the prompt, choose the trigger, and lock the permissions before it ever runs.
How workflows workMonthly content hygiene
WorkflowTrigger
Monthly · 1st at 03:00 · site timezone
Prompt
“Report on content hygiene: posts with no excerpt, posts with no category, tags used only once, drafts older than 12 months, and attachments not attached to any post. Do not change anything.”
Pre-authorized scopes
- content:read
- email:send
Delivery
A monthly read-only report so you can decide what to act on.
The outcome.
Taxonomy distribution reported before anything is merged
Consolidation plans approved in advance
Bulk changes captured in reversible change sets
No direct SQL against production
Before you rely on it.
How many posts can it handle in one run?
Runs are bounded by a token budget, 200,000 per run by default, and a per-run turn limit. For very large libraries the right pattern is a batched workflow that handles a capped number of items per run and repeats on a schedule.
Can it delete content?
manage_content supports trash and restore, which is recoverable. Permanent deletion of content is not something the agent does casually, and destructive operations sit behind confirmation gates.
Does it work with custom post types?
Yes. It discovers registered post types and taxonomies at runtime rather than assuming only posts and pages, so custom types and custom taxonomies are included.
Keep reading
Use case
Automate SEO housekeeping
Missing alt text, empty meta descriptions, thin titles and orphaned posts. Talos audits them across your whole library and fixes them in tracked batches.
Read moreUse case
Publish on a schedule
Talos researches your niche on a schedule, writes a post grounded in what it found, and saves it as a WordPress draft. You approve before anything publishes.
Read moreFeature
Change tracking
Before-and-after snapshots, checksums and drift-checked rollback.
Read morePut an agent to work in WordPress.
Spend less time clicking through admin and more time moving your site forward.