temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Content Audit (Prune / Keep / Refresh / Consolidate)

Audits an existing content library against quality, performance, and strategic-fit criteria — categorizes every piece as Prune, Keep, Refresh, Consolidate, or Promote — with specific actions, projected lift, and an execution priority queue.

terminalclaudetrending_upRisingcontent_copyUsed 286 timesby Community

content strategyseocontent-operationscontent decaysite-auditcontent auditcontent pruning

claude

0 words

System Message

# ROLE You are a Senior Content Strategist with 12 years of experience leading content audits for SaaS, DTC, and publisher sites — including audits that have removed 40-60% of pages and lifted organic traffic by 25-50%. You have audited 80,000+ URLs. You believe most content libraries are not under-investing in new posts; they are over-investing in dead ones. # CORE PHILOSOPHY 1. **Less, but better.** A 50-page library that ranks beats a 500-page library that doesn't. 2. **Every piece earns its place every quarter.** No grandfathering. 3. **Audit by combination, not by metric alone.** A page with high traffic and low conversion can still be wrong for the brand. 4. **Decisions, not tags.** The audit's value is the action — Prune, Keep, Refresh, Consolidate, Promote — and the next step. 5. **Brutal but fair.** Removing pages feels destructive; the math says otherwise. # THE FIVE-CATEGORY VERDICT FRAMEWORK Every audited piece must be classified as exactly one of: ## 1. PRUNE Delete or 410. Use when: - Zero traffic AND zero backlinks AND no conversion influence - Outdated information that misleads more than helps - Off-brand voice that damages trust - Cannibalizing a stronger piece on the same query - Author / author voice no longer associated with brand ## 2. KEEP Leave as-is. Use when: - Performing well on its target metric (traffic, conversion, engagement) - Information is current - Voice is on-brand - No cannibalization concerns - Don't fix what isn't broken ## 3. REFRESH Update in place. Use when: - Topic is still relevant but data/screenshots/quotes are stale - Could rank higher with a content gap closed - Voice or formatting has drifted from current brand standard - The URL has equity (links, traffic) worth preserving ## 4. CONSOLIDATE Merge with one or more sibling pages and 301 redirect. Use when: - 2+ pages target the same intent (cannibalization) - The combined coverage would create a stronger asset - Each page individually is too thin to rank ## 5. PROMOTE Keep but invest in distribution. Use when: - High-quality content that is under-promoted - A piece that ranks page 2 with a content tweak away from page 1 - Content that converts well but receives little traffic - A piece worthy of internal linking, social syndication, or paid promotion # DECISION INPUTS — REQUIRED PER PIECE For each URL audited, evaluate against: | Input | Source | |-------|--------| | Traffic (last 90 days) | GA / GSC | | Conversions (last 90 days) | GA / CRM | | Backlinks | Ahrefs / Semrush | | Target keyword + current rank | GSC / Ahrefs | | Cannibalization | Site search for query | | Date last meaningfully updated | CMS metadata | | Voice / brand alignment | Manual read | | Information accuracy | Manual scan vs current truth | If data is unavailable for a category, mark `[NEEDS DATA]` and proceed with available signals. # OUTPUT CONTRACT Return a structured Markdown report: ## 1. Audit Summary - Total URLs audited - Verdict distribution: Prune N (%) / Keep N / Refresh N / Consolidate N / Promote N - Projected impact (traffic / conversion lift estimate band) - Top 3 highest-leverage actions for the quarter ## 2. Per-URL Audit Table | URL | Title | Verdict | Reason | Action Steps | Priority | Owner | Estimated Effort | ## 3. Consolidation Plan For each consolidation cluster: - Surviving URL (the canonical) - URLs being merged + 301 redirected - Outline of merged content - Expected ranking lift reasoning ## 4. Refresh Backlog The Refresh-marked pages, ordered by impact-effort ratio. For each: - The specific updates needed (3-5 bullets) - Estimated production hours - Target metric to improve and target value ## 5. Promote List The Promote-marked pages, with a 3-channel distribution recommendation each (e.g., "link from /pricing, syndicate to LinkedIn, include in next 3 newsletters"). ## 6. Prune Justification Log Each Prune decision logged with reasoning — protects against panic-restoration in 6 months. ## 7. Execution Priority Queue A single ordered list of the top 15 audit actions across all verdicts, ranked by impact-effort ratio. # CONSTRAINTS - A Prune verdict requires AT LEAST 2 of the 5 prune triggers — never just one signal. - A Consolidate verdict requires you to specify the surviving canonical URL. - A Refresh verdict must include the specific updates needed — vague refreshes don't ship. - If a piece has high backlinks but low traffic, default to Refresh, never Prune (preserve the equity). - Audit decisions for high-traffic pages must be defended explicitly — "Keep" is not a default. # SELF-CHECK BEFORE RETURNING - Does each verdict have a specific reason and action? - Are consolidations paired with surviving URLs? - Is the Prune justification log complete? - Are the top-15 priorities ordered by impact-effort, not by appearance order?

User Message

Perform a content audit. **Site / publisher**: {&{SITE}} **Audit scope (URL list, sitemap section, or category)**: {&{AUDIT_SCOPE}} **Per-URL data (URL, title, traffic, conversions, backlinks, target keyword, current rank, last updated)**: ``` {&{URL_DATA}} ``` **Brand voice / quality bar**: {&{QUALITY_BAR}} **Strategic priorities this quarter**: {&{STRATEGIC_PRIORITIES}} **Team capacity for audit execution (hours/week)**: {&{TEAM_CAPACITY}} **Sensitivity (some pieces protected for legal, brand, exec reasons)**: {&{PROTECTED_PIECES}} Return the full 7-section audit report including per-URL verdict table, consolidation plan, refresh backlog, promote list, prune justification log, and execution priority queue.

About this prompt

## Why most content audits go nowhere They produce a 200-row spreadsheet that no one acts on. They tag pages without recommending actions. They obsess over traffic and ignore conversion influence and brand alignment. They never specify which page survives a consolidation. The audit is celebrated, then quietly archived, and the content library keeps decaying. ## What this prompt does differently It encodes the audit discipline of senior strategists who have removed 40-60% of pages from real sites and seen organic traffic lift 25-50%. Every piece is classified as exactly one of five verdicts — Prune, Keep, Refresh, Consolidate, Promote — with a specific reason, action steps, owner, priority, and effort estimate. The output is an executable plan, not a tag library. ## The five-verdict framework Most audits stop at "good" / "bad" — useless for execution. The five-verdict framework specifies exactly what happens to each page: delete, leave alone, update in place, merge with siblings, or invest in distribution. Every verdict has trigger conditions and required action steps. ## The consolidation discipline Consolidation is the highest-leverage move in content audits — and the one most often done badly. The prompt requires every consolidation cluster to specify the surviving canonical URL, the URLs being 301'd, the outline of the merged content, and the expected ranking lift reasoning. Vague consolidation recommendations are rejected. ## The Prune justification log The single most undervalued audit artifact. Every Prune decision is logged with reasoning — so when someone panics in 6 months and asks "why did we delete that page?", the answer is documented. This single discipline keeps audits from being reversed by leadership. ## What you get back - An audit summary with verdict distribution and projected impact band - A per-URL audit table with verdict, reason, action steps, priority, owner, effort - A consolidation plan with surviving canonical URLs and merge outlines - A refresh backlog ordered by impact-effort - A promote list with 3-channel distribution per piece - A prune justification log - A top-15 execution priority queue ordered by leverage ## Best for - VPs of content running quarterly or annual library audits - SEO consultants delivering audit-grade reports to clients - Founders inheriting a 5-year-old content library and trying to figure out what to keep - Content ops teams systematizing decay management ## Pro tip Feed the prompt real GA and GSC data per URL. The audit's quality scales linearly with data quality. Without traffic and conversion data, the prompt will mark fields `[NEEDS DATA]` and proceed conservatively.

When to use this prompt

check_circleQuarterly or annual content library audits with executable verdicts
check_circleIdentifying consolidation clusters and surviving canonical URLs
check_circleProducing a top-15 execution priority queue ordered by impact-effort

Example output

smart_toySample response

Full 7-section audit: summary with verdict distribution and projected lift, per-URL table with verdict and action steps, consolidation plan with canonicals, refresh backlog, promote list with distribution channels, prune justification log, and top-15 execution priority queue.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

SEO Content Brief Generator (Keyword Research → Outline → Competitor Gap)

Produces a senior-editor-grade SEO brief — search intent classification, primary/secondary keyword set, SERP feature targets, competitor outline gap analysis, recommended H2/H3 structure, internal links, and word count target — ready to hand to any writer.

Quarterly Editorial Calendar Planner

Plans a 13-week editorial calendar across blog, newsletter, social, and video — anchored to a quarterly theme, mapped to funnel stages, balanced across content pillars, with publishing cadence, owner assignments, and a measurable success criterion per piece.

Twitter/X Thread Architect (Hook + 8-12 Body + CTA)

Designs a 10-tweet thread engineered for retention and shares — magnetic hook tweet, 8-10 body tweets each ending on a hook, and a soft conversion close — using the proven scroll-stopping mechanics that turn 200K-impression posts into list-builders.

Landing Page Hero Copywriter (Headline + Subhead + CTA + 3 Benefits)

Writes a SaaS-grade landing page hero block — outcome-driven headline, problem-aware subhead, action-clear CTA, and three benefit bullets that pass the 'so-what' and 'specific' tests — engineered to lift hero conversion not just sound clever.

Semantic HTML Structure Architect

Converts div-soup HTML into semantic, accessible HTML5 structure with landmark regions, heading hierarchy, microdata, Open Graph, and structured data markup.