Skip to content
Back to skills

Seo Redirects

ASecurity

Use when planning redirects or site migration. Covers 301 vs 302 vs 307/308, migration plans, redirect chains, link equity preservation, www/non-www, HTTP→HTTPS, 404 monitoring.

  • 29 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 28, 2026
ai-agentsgo

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add fusengine/agents --skill seo-redirects --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Seo Redirects?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Seo Redirects
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fusengine-seo-redirects/badge)](https://www.skillsdirectory.com/skills/fusengine-seo-redirects)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: seo-redirects
description: Use when planning redirects or site migration. Covers 301 vs 302 vs 307/308, migration plans, redirect chains, link equity preservation, www/non-www, HTTP→HTTPS, 404 monitoring.
user-invocable: false
related-skills: seo, seo-technical, seo-sitemap
---

# Redirects & Migrations

## Status Codes

| Code | Use Case | SEO Impact |
|------|----------|------------|
| 301 | Permanent move | Passes ~99% link equity |
| 302 | Temporary (e.g. A/B test) | Does NOT pass equity long-term |
| 307 | Temporary, preserves HTTP method | Same as 302 for SEO |
| 308 | Permanent, preserves HTTP method | Same as 301 for SEO |

## Migration Plan

1. **Map old URLs → new URLs** (CSV: source, target, status)
2. **Implement 301s** for every old URL
3. **Test in staging** with `curl -I <old-url>` → expect `301 Location: <new>`
4. **Update internal links** to point directly to new URLs (avoid chain)
5. **Update sitemap.xml** with new URLs only
6. **Submit to Google Search Console** via Change of Address tool (if domain change)
7. **Monitor 404s** for 90 days post-launch

## Chain Detection

- **Chain**: A → B → C (loses ~10% equity per hop)
- **Loop**: A → B → A (infinite, broken)
- Fix: A → C directly

## Common Redirects

| From | To | Status |
|------|-----|--------|
| `http://` | `https://` | 301 |
| `www.` | `non-www` (or reverse, pick one) | 301 |
| `/page/` | `/page` (or reverse) | 301 |
| Old slug | New slug | 301 |

## Anti-Patterns

- ❌ Redirecting everything to homepage (mass 404 → 301 to /) → looks spammy
- ❌ Soft 404s (200 status on missing pages)
- ❌ JS-based redirects (Google may not follow)
- ❌ Meta refresh redirects > 0s (use server-side)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…