content-remediation

Automate web content pruning, redirection, and retirement with validation gates.

25|4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/popiliadam/platinum-seo-engine --skill content-remediation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-remediation
Source: https://github.com/popiliadam/platinum-seo-engine/tree/main/skills/production/content-remediation
Command: npx skills add https://github.com/popiliadam/platinum-seo-engine --skill content-remediation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of pruning, redirecting, and retiring content, ensuring SEO compliance and site health.

Core Features & Use Cases

  • Content Pruning: Automates the removal of outdated content to improve site performance.
  • Content Redirection: Redirects users to relevant pages after content is removed or moved.
  • Content Retirement: Permanently removes content that is no longer relevant or compliant with SEO standards.
  • Use Case: When a website needs to remove outdated blog posts or redirect users to new pages, this Skill can be used to automate the process.

Quick Start

Use the content-remediation skill to prune the content at URL 'https://example.com/old-post' and redirect it to 'https://example.com/new-post'.

Frequently Asked Questions about content-remediation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate content pruning and redirection for outdated web pages?

Automating content pruning and redirection involves validating URLs against multi-signal thresholds, passing manual approval gates, then executing 301 or 410 redirects to permanently remove or move outdated web pages.

What is content retirement and when should I use 301 vs 410 redirects?

Content retirement permanently removes outdated pages. Use 301 redirects when moving content to a new relevant URL, and use 410 redirects to signal permanent deletion when no replacement page exists.

How do I validate content decay data before removing outdated blog posts?

Validating content decay requires checking URLs against multi-signal thresholds and routing the proposed removals through manual approval gates before executing any redirects or updating tracking sheets.

Can I use this content remediation process to update my master spreadsheet automatically?

Yes, the content remediation process automatically updates master.xlsx sheets after validating multi-signal thresholds and executing the necessary 301 or 410 redirects for the pruned URLs.

What configuration and data do I need to set up SEO automation for site health?

Setting up SEO automation for site health requires access to project-specific configuration files and content decay data to validate multi-signal thresholds before executing any redirection or retirement actions.