Agent skill

SEO Content Audit

by rampstackco in rampstackco/claude-skills

Audit existing content across a site to decide what to keep, update, merge, redirect, or delete.

MITAuto-check passedMarketing & SEO

Install SEO Content Audit

skills CLI
$ npx skills add rampstackco/claude-skills --skill seo-content-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rampstackco/claude-skills seo-content-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-content-audit .claude/skills/seo-content-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
seo-content-audit
GitHub stars
940
Token cost
~2.1k tokens
SKILL.md length
953 words
Files
4 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Audit existing content across a site to decide what to keep, update, merge, redirect, or delete.

  • Works in 5 steps: Keep → Update → Merge → …
  • The user wants to audit existing content
  • SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 5 actions, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

SEO Content Audit is an agent skill from rampstackco/claude-skills. Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/audit-template.md` and `references/cannibalization-resolution.md`).

It sits in Marketing & SEO, covering On-page SEO, Content marketing and Keyword research. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • The user wants to audit existing content
  • Fix content decay
  • Resolve keyword cannibalization
  • Prune underperforming pages

Example prompts

  • “/seo-content-audit”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Keep
  2. Update
  3. Merge
  4. Redirect
  5. Delete (and let return 404 or 410)

What it can do on your machine

Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SEO Content Audit loads about 2.1k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 183 tokens; SKILL.md has 953 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~183
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 953 words, ~2,113 tokens.

Download SKILL.mdSave it as .claude/skills/seo-content-audit/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
seo-content-audit
description
Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory, what to keep, what to update, content scorecard, evergreen refresh. Also triggers when traffic is dropping site-wide and the cause might be content quality, even if 'audit' is not said explicitly.
category
seo-foundation
catalog_summary
Keep/update/merge/redirect/delete decisions across a site
display_order
6

Content Audit

Inventory existing content, score it, and decide for each piece: keep, update, merge, redirect, or delete. Stack-agnostic. Works on blogs, marketing sites, knowledge bases, and product content.


When to use

  • Inheriting a content library you did not create
  • Diagnosing site-wide traffic decline
  • Resolving cannibalization (two pages competing for the same query)
  • Pre-migration cleanup
  • Annual or semi-annual content health check
  • Pruning before a redesign or replatform

When NOT to use

  • Optimizing a single page (use seo-onpage)
  • Planning new content (use seo-keyword)
  • Comparing your content to competitors (use seo-competitor)
  • Site-level technical issues (use seo-technical)

Required inputs

  • The site URL and access to crawl it (or a complete URL list)
  • Search console access (or a 12-month export)
  • Analytics access (sessions, conversions, engagement)
  • A backlink tool (to identify pages with referring domains worth preserving)

The framework: 5 actions

For every content piece, the audit produces one of five decisions.

1. Keep

The page performs well, has clear intent, and needs no changes.

Signals:

  • Top 10 ranking for its primary query
  • Consistent traffic with no decay
  • Healthy engagement (above-site-average time on page or interaction rate)
  • Up-to-date information
2. Update

The page has potential but is underperforming due to fixable issues.

Signals:

  • Page 2 ranking for high-value queries (rank 11 to 30)
  • Traffic decay over the last 6 to 12 months
  • Information gone stale
  • Title or meta need rewriting for CTR
  • Thin content that could expand to match competitor depth
  • Missing schema or other technical hygiene
3. Merge

Two or more pages target overlapping queries and should consolidate.

Signals:

  • Cannibalization (multiple pages ranking for the same query, none ranking well)
  • Significant content overlap between pages
  • Combined, they would outperform either alone
  • Both have backlinks worth preserving
4. Redirect

The page has no future but has assets (links, equity) worth preserving.

Signals:

  • No traffic, no rankings
  • Holds backlinks (especially editorial ones)
  • A relevant target page exists that would benefit from the equity
  • Topic is still relevant but this specific page is not
5. Delete (and let return 404 or 410)

The page has no future and no assets worth preserving.

Signals:

  • No traffic, no rankings, no backlinks
  • Content is outdated and not worth updating
  • Topic is no longer relevant
  • Even thin or spam content from a previous era

Note: In most cases, return 410 (gone) for intentionally deleted content. 410 is processed faster than 404 and signals the deletion was deliberate.


Scoring inputs

Pull these for every URL before deciding:

MetricSourceThreshold for "low"
Sessions (last 90 days)Analytics<10/month
Organic traffic (last 90 days)Search console or analytics<5/month
Average position for top querySearch console>30
Impressions (last 90 days)Search console<100/month
Click-through rateSearch console<1% (when impressions exist)
Referring domainsBacklink tool0
Engagement (avg time on page)Analytics<30 seconds
Last meaningful updateManual / git>24 months
Word countCrawler<300 (for articles)
Internal links inCrawler0

A page can survive low scores on a few metrics. A page that fails on most is a delete or redirect candidate.


Decision matrix

A simplified decision tree:

Has traffic? ─── Yes ──── Recent decay? ─── Yes ── UPDATE
        │                          │
        │                          └── No ─── KEEP
        │
        └── No ──── Has backlinks? ─── Yes ── Has relevant target? ─── Yes ── REDIRECT
                          │                            │
                          │                            └── No ─── UPDATE (rebuild)
                          │
                          └── No ──── Cannibalizing another page? ─── Yes ── MERGE
                                              │
                                              └── No ─── DELETE (410)

For overlapping pages, "merge" usually wins over "delete" because it preserves both link equity and any topical authority.


Show full SKILL.md (427 more words)Show less

Workflow

  1. Inventory. Pull a complete URL list from the crawl, sitemap, and search console (some indexed pages may not be in the sitemap).
  2. Pull the metrics. Sessions, organic, search console rank/CTR, backlinks, last-modified date, word count.
  3. Score each URL. Use the framework. Mark a decision: Keep / Update / Merge / Redirect / Delete.
  4. Identify cannibalization clusters. Group URLs targeting the same query. Decide which becomes the canonical, what to merge, what to redirect.
  5. Sequence the work. Do redirects and deletes in batches. Plan updates by priority (highest-traffic-recovery potential first).
  6. Implement. With change tracking. Re-crawl after each batch to confirm no broken redirect chains.
  7. Measure. Track aggregate organic traffic 30, 60, 90 days post-audit.

Failure patterns

  • Deleting pages with backlinks. Always check referring domains before deleting. A redirect preserves equity at near-zero cost.
  • Updating pages that should be merged. Two thin pages updated to medium pages still cannibalize. Merge first.
  • Merging without preserving the better URL. Pick the merge target by which URL has stronger signals (older URL, more backlinks, better URL slug, currently better ranking), not which one has more content.
  • Mass-deleting low-traffic pages. Some have value: fresh pages still ramping, niche pages serving a specific audience, evergreen pages with seasonal traffic. Do not bulk-delete by sessions alone.
  • Over-aggressive pruning of "old" content. Date alone is not a delete signal. Topic relevance and intent quality are.
  • No post-audit measurement. Without measurement, you cannot tell if the audit worked.

Output format

Default output: a spreadsheet with one row per URL, plus a summary markdown report.

Spreadsheet columns:

  • URL
  • Page type (article, product, category, etc.)
  • Sessions (90d), organic clicks (90d), impressions (90d), avg position
  • Referring domains
  • Word count
  • Last modified
  • Decision (keep / update / merge / redirect / delete)
  • Merge target / redirect target (if applicable)
  • Priority (1-5)
  • Notes

Summary report:

  1. Inventory totals (URLs by decision)
  2. Cannibalization clusters identified
  3. Top 20 update priorities
  4. Redirect map (CSV)
  5. Delete list
  6. Implementation roadmap (sequenced by priority)
  7. Measurement plan

If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.


Reference files

© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/seo-content-audit of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/audit-template.md
  • references/cannibalization-resolution.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

SEO Content Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SEO Content Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SEO Content Audit this skillrampstackco/claude-skills940—~2.1kAutomated safety check: PassMIT
SEO Planseranking/seo-skills160—~4.4kAutomated safety check: PassMIT
SEO Keyword ClusteringAgriciDaniel/claude-seo18k2 repos~3.3kAutomated safety check: PassMIT
SEO Content Brief GeneratorAgriciDaniel/claude-seo18k2 repos~2.6kAutomated safety check: PassMIT
AI Citability Scorerzubair-trabzada/geo-seo-claude11k2 repos~3.7kAutomated safety check: NotesMIT
Marketing BrainAgriciDaniel/seo-os134—~865Automated safety check: PassProprietary

Similar skills

  • SEO Plan

    seranking/seo-skills

    Build a phased SEO roadmap for a domain — quarter-by-quarter, tied to the site's competitive position, content gaps, technical debt, and AI Search readiness.

    160 GitHub stars~4.4k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • SEO Keyword Clustering

    AgriciDaniel/claude-seo

    Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.

    18k GitHub starsUsed in 2 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • SEO Content Brief Generator

    AgriciDaniel/claude-seo

    Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.

    18k GitHub starsUsed in 2 repos~2.6k tokens
    Marketing & SEOAuto-check passed
  • AI Citability Scorer

    zubair-trabzada/geo-seo-claude

    Scores how likely AI assistants are to quote passages from a web page and suggests rewrites that make those passages easier to extract.

    11k GitHub starsUsed in 2 repos~3.7k tokens
    Marketing & SEOAuto-check: notes
  • Marketing Brain

    AgriciDaniel/seo-os

    Source-available SEO and content marketing strategy brain. An agent skill from AgriciDaniel/seo-os.

    134 GitHub stars~865 tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • 90 Day SEO Sprint

    Bomx/distribb-skill

    Run the Distribb 90-Day SEO Sprint - a founder-built 13-week playbook for shipping pre-launch SEO, core pages, a content engine, and a backlink starter stack on the way to compounding organic traffic.

    198 GitHub stars~3.6k tokensUpdated 8 days ago
    Marketing & SEOAuto-check passed

More from rampstackco/claude-skills

All 103 skills in this repo
  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    940 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    940 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed
  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    940 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    940 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    940 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Content Strategy

    rampstackco/claude-skills

    Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

    940 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about SEO Content Audit

What does SEO Content Audit do?

Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. SEO Content Audit is an agent skill from rampstackco/claude-skills. Audit existing content across a site to decide what to keep, update, merge, redirect, or delete.

When should I use SEO Content Audit?

SEO Content Audit fits situations like: the user wants to audit existing content; fix content decay; resolve keyword cannibalization; prune underperforming pages.

How do I install SEO Content Audit in Claude Code?

Run `npx skills add rampstackco/claude-skills --skill seo-content-audit -a claude-code`. Or copy the skill folder (skills/seo-content-audit in rampstackco/claude-skills) into .claude/skills/seo-content-audit in your project. Claude Code loads it when a task matches its description.

How do I install SEO Content Audit in Codex?

Run `npx skills add rampstackco/claude-skills --skill seo-content-audit -a codex`. Or copy the skill folder (skills/seo-content-audit in rampstackco/claude-skills) into .agents/skills/seo-content-audit in your project. Codex loads it when a task matches its description.

Can I use SEO Content Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill seo-content-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-content-audit, .gemini/skills/seo-content-audit, .github/skills/seo-content-audit and .opencode/skills/seo-content-audit in your project.

What does SEO Content Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: SEO Content Audit is instructions for the agent only.

Does SEO Content Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is SEO Content Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does SEO Content Audit use?

SEO Content Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SEO Content Audit use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to SEO Content Audit?

Skills that share tags, products or a category with SEO Content Audit: SEO Plan (seranking/seo-skills, 160 stars), SEO Keyword Clustering (AgriciDaniel/claude-seo, 18k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 18k stars) and AI Citability Scorer (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO Content Audit?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 940 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.