How to Run a Content ROT Analysis (Redundant, Obsolete, Trivial)

Your blog has hundreds of URLs. Some still pull traffic. Some rank on page two and eat crawl budget. Some say the same thing as a post you published last year, with a weaker headline and older screenshots.

Teams usually discover the mess during a redesign or when traffic flatlines. By then, every URL feels urgent and nobody agrees on what to cut. A content ROT analysis fixes that. ROT stands for redundant, obsolete, and trivial. It is a simple sort that tells you which pages to merge, refresh, redirect, or remove before you spend another quarter publishing on top of the pile.

This guide walks through how to run a content ROT analysis on a marketing blog: what each label means, how to score URLs with Search Console and analytics, and how to turn the spreadsheet into a backlog your team can actually ship.

What ROT means in content audits

ROT is borrowed from records management and adapted for content libraries. Each letter is a decision, not a vibe.

Redundant

Redundant content covers the same topic, intent, and audience as another URL on your site. Neither page adds enough unique value to justify both staying indexed. Classic signs:

• Two posts target the same primary keyword with overlapping H2 sections
• An old “tips” post and a newer pillar both answer “how to measure content ROI”
• Category archives, tag pages, or thin landing pages duplicate body copy from a main article
• Localized or persona variants that differ only in intro adjectives, not substance

Redundant pages split links, confuse internal linking, and make it harder for search engines to pick a canonical winner. The fix is usually merge and redirect, not a light edit.

Obsolete

Obsolete content was useful once but no longer matches reality, search intent, or your positioning. The page might still get impressions from an old headline while readers bounce because the advice is wrong.

• Product features, platforms, or regulations referenced in the post no longer exist
• Recommendations contradict how you work today (pricing models, tooling, methodology)
• Statistics and examples are years out of date (see our guide on fixing outdated statistics in old posts)
• The SERP shifted to a different format (video, tools, comparison tables) and your post type no longer fits

Obsolete URLs often deserve a refresh or rewrite, not deletion. The topic still has demand; the page just lost the plot.

Trivial

Trivial content is thin, low effort, or too narrow to earn traffic or trust. It clutters the library without supporting a hub or pipeline goal.

• 200-word announcement posts with no lasting search value
• Conference recaps that never tied back to a durable topic
• “Happy holidays” or internal news indexed as blog posts
• Placeholder pages published to hit a quota

Trivial URLs are candidates for noindex, merge into a roundup, or redirect to a parent hub. Keep them only when they still convert or support a deliberate nurture path.

Why run a ROT analysis before you refresh everything

Most teams jump straight to “update old posts.” That works until you realize you are polishing URLs that should not exist.

A ROT pass answers three questions upfront:

1. Should this URL still be indexed? Trivial and redundant pages often should not.
2. Is the problem freshness or fit? Obsolete pages need new substance; redundant pages need consolidation.
3. Where is the real traffic risk? High-impression losers cost more than zero-traffic clutter.

ROT also pairs cleanly with decay work. Declining clicks tell you something is wrong; ROT tells you which fix type fits. Our post on improving old blog posts that stopped ranking covers refresh depth. ROT decides whether refresh is the right move at all.

Skip the full-library read. Score from exports, then spot-check edge cases. A mid-size B2B blog can triage 200 to 500 URLs in a focused week if the spreadsheet is set up right.

What you need before you start

Gather inputs once. Reuse the same template each quarter.

URL inventory

Export all indexable blog URLs from your CMS or sitemap. Include publish date, word count, category, and author if available. Add hub relationships manually for pillar and spoke clusters.

Performance data

Pull the last 90 days (and prior 90 for comparison) from:

• Google Search Console: clicks, impressions, average position, top queries per URL
• GA4: sessions, engaged sessions, conversions or key events tied to content
• CRM or form tool: influenced contacts if you track content-assisted leads

Impressions without clicks often flag obsolete or misaligned snippets. Our guide on impressions vs clicks in Search Console explains how to read that gap.

Business context

List URLs sales quotes, paid campaigns, or partner pages depend on. Those get a “do not touch without sign-off” flag before anyone labels them trivial.

One spreadsheet, one owner

ROT fails when SEO, content, and dev each keep a separate list. Pick one workbook and a single DRI for the scoring pass.

A step-by-step ROT analysis workflow

Run these steps in order. Do not merge or delete until the full pass is reviewed.

Step 1: Build the master URL list

Merge CMS export with GSC page data on URL. One row per indexed URL. Filter out thank-you pages, login screens, and utility URLs you already noindex.

Step 2: Flag obvious trivial URLs

Sort by word count, traffic, and conversions. URLs with near-zero sessions, no conversions in 12 months, and under 400 words are trivial candidates unless they are deliberate conversion paths.

Also scan titles: “Weekly roundup March 2017” is rarely worth keeping indexed.

Step 3: Find redundant pairs and clusters

Group URLs by topic cluster or primary query. Use:

• Site search queries (what people look for on your blog)
• GSC query groups exported per URL
• Manual review of posts with similar titles
• Internal link overlap (two pages linking to each other as “the” resource on the same topic)

Mark the stronger URL as “keep” and the weaker as “redundant → merge target.” Strength = traffic + conversions + internal links + freshness, not publish date alone.

Step 4: Label obsolete pages

For remaining URLs, check:

• Publish or last-updated date more than 24 months ago on fast-moving topics
• Declining clicks or position over two consecutive 90-day periods
• Broken outbound links to core sources
• Comments or sales feedback that the post feels dated

Obsolete is not an insult. It means the frame needs work: new examples, new stats, new sections, or a new angle.

Step 5: Assign an action per URL

Every row gets one primary action:

ROT label	Typical action	Notes
Redundant	Merge + 301 redirect	Combine best sections into the keeper URL; redirect the loser
Obsolete	Refresh or deep rewrite	Match current intent; update proof points and internal links
Trivial	Noindex, redirect to hub, or delete	Delete only when no inbound links or history matter
None (healthy)	Monitor	Re-score on the next quarterly pass

Step 6: Prioritize by impact

Score each action row 1 to 5 on:

• Traffic at risk (GSC clicks and impressions)
• Conversion value (assisted leads, demo requests)
• Crawl / index noise (thin URLs diluting the library)
• Effort (inverse score: quick wins float up)

Ship high-impact, lower-effort merges and noindex decisions first. Queue deep rewrites for obsolete pillars separately so they do not block quick hygiene wins.

Step 7: Document and hand off

Each row needs: owner, due date, redirect map (if any), and baseline metrics (clicks, position, conversions) so you can measure after the change.

How to spot redundant content without reading every post

Redundancy hides in clusters. These checks surface duplicates fast.

Query overlap in Search Console

Export top queries for your top 50 URLs. If two URLs rank for the same head term with similar positions, compare intent. Same intent = redundant until you differentiate or merge.

Title and slug patterns

Search the CMS for repeated stems: “content marketing tips,” “how to measure,” “ultimate guide to.” Pairs published years apart are common redundancy traps.

Internal link cannibalization

Hub pages should point to one canonical spoke per subtopic. If your pillar links to three posts that all answer the same question, pick a keeper and consolidate.

Word count and section overlap

Paste two URLs into a diff tool or skim H2 lists side by side. If 60% of headings match and examples repeat, merge is usually cheaper than maintaining both.

How to judge obsolete vs “good enough”

Not every old post is obsolete. Some evergreen guides age slowly if the core process still holds.

Ask on each stale URL:

1. Does the primary query still match what the page delivers?
2. Would a refresh fix the problem in under a day, or does the structure need rebuilding?
3. Are competitors winning with a different format or fresher proof?
4. Does the page still earn engaged sessions, not just impressions?

If intent matches and engagement is solid, monitor instead of forcing a rewrite. If impressions are up but clicks are flat, check titles and obsolete proof before you blame the whole page. Obsolete often lives in stats, screenshots, and product names, not the entire outline.

What to do with trivial URLs

Trivial does not always mean delete. Choose based on dependencies.

• Redirect to hub: when the topic is valid but the post is too thin (common for old news posts)
• Noindex: when the page must stay live for a link in an email archive but should not compete in search
• Delete: when there are no meaningful inbound links and no conversion path
• Keep indexed: when the URL still converts or supports a campaign you run every year

Batch trivial cleanup quarterly. It is easy work that reduces index bloat and makes the remaining library easier to navigate.

ROT spreadsheet columns that keep the work honest

Copy this header row into Google Sheets or Notion:

1. URL
2. Title
3. Publish date / last modified
4. Word count
5. 90-day clicks (GSC)
6. 90-day impressions
7. Avg position
8. Conversions / key events
9. ROT label (R / O / T / none)
10. Action (merge, refresh, redirect, noindex, monitor)
11. Merge target or redirect URL
12. Priority score
13. Owner
14. Status
15. Notes

Color-code by label. Review redundant rows in a single meeting so merge decisions do not drift.

Connect ROT output to your editorial calendar

ROT is not a one-time cleanup. It feeds the calendar you already run for decay and new content.

After scoring:

• Merge queue → dev + content sprint (redirects, content combined into keeper)
• Obsolete refresh queue → writer assignments with depth noted (light vs deep)
• Trivial cleanup → monthly hygiene batch
• Healthy URLs → monitor list for the next GSC review

Our guide on building an editorial calendar from decay and opportunity data shows how to slot ROT actions next to net-new posts so refreshes do not lose every sprint to launches.

For broader decay patterns, see content decay: how to find and fix pages losing traffic and content analytics metrics for what to watch after merges and redirects go live.

Common ROT analysis mistakes

• Deleting by traffic alone. A low-traffic post might be the best explainer for a high-converting niche query.
• Merging without a content plan. Redirecting two URLs into the stronger slug without combining the best sections wastes the weaker page’s only good paragraph.
• Labeling everything obsolete. Old is not obsolete. Check intent and engagement before you queue a rewrite.
• Skipping redirect maps. Chains and loops hurt crawl efficiency. Document source → target in one sheet.
• Ignoring internal links. Update hub pages and spokes when a URL disappears or moves.
• One pass and done. New redundancy appears every time you publish without cluster rules. Re-run ROT quarterly.
• SEO-only scoring. Include conversion and sales dependencies so you do not noindex a page revenue teams still quote.

When ROT is not enough on its own

ROT sorts the library. It does not replace topic strategy. If your clusters are wrong at the hub level, merging spokes only tidies a broken map.

Step up to hub planning when:

• Multiple redundant clusters point to missing pillar pages
• Search demand shifted and no existing URL can be refreshed into the new intent
• Site migration or rebrand requires URL architecture changes beyond post-level fixes

ROT still runs first. You want a clean inventory before you draw the next sitemap.

Turn ROT scoring into a content library you can maintain

A content ROT analysis turns a vague “we should clean up the blog” project into a labeled backlog: merge the redundant, refresh the obsolete, cut or redirect the trivial, and protect what still works. Run it on a schedule, tie it to Search Console and your editorial calendar, and the library stops growing sideways. If you want help scoring your URLs and building a merge-and-refresh queue tied to pipeline impact, we audit content libraries against analytics and hand you a prioritized ROT sheet your team can execute in the next quarter.