redirect-migration

Generate and validate EDS-compliant redirect tables for AEM Edge Delivery Services migrations.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill redirect-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redirect-migration
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/redirect-migration
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill redirect-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Redirect migrations for Adobe Edge Delivery Services can break user navigation and SEO when old URLs are not mapped correctly to EDS-compliant destinations, with failures often caused by invalid URL formats, missing coverage, or redirect chains and loops.

Core Features & Use Cases

  • Inventory and transform legacy URLs: Collect source URLs from sitemaps or provided lists, then normalize them into EDS-allowed destination paths (lowercase, dashes, no extensions/special characters).
  • Generate EDS-ready redirect tables: Produce a paste-ready two-column Source/Destination spreadsheet that matches EDS redirect expectations and ordering rules (first match wins).
  • Validate the redirect graph for production safety: Detect and report chains, loops, duplicates, self-redirects, and unreachable destinations, while assessing SEO coverage for high-value pages.

Quick Start

Use the redirect-migration skill on your old sitemap or URL list to generate and validate an EDS-compliant redirects spreadsheet ready to paste into Google Sheets or Excel.

Frequently Asked Questions about redirect-migration

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

FAQPage Schema
How do I generate EDS redirect spreadsheets for an AEM site migration?

To generate EDS redirect spreadsheets, input your legacy sitemap or URL list. The tool normalizes paths into EDS-compliant destinations and outputs a paste-ready two-column Source/Destination spreadsheet for AEM Edge Delivery Services.

What URL formats are allowed for AEM Edge Delivery Services redirects?

AEM Edge Delivery Services redirects require normalized URL destinations. This means paths must be lowercase, use dashes, and contain no file extensions or special characters to comply with EDS URL restrictions.

How do I validate redirect maps to prevent chains and loops in EDS?

You can validate redirect maps by analyzing the generated URL graph to detect and report chains, loops, duplicates, self-redirects, and unreachable destinations, ensuring production safety for your EDS migration.

Can I use a legacy sitemap to create EDS-compliant redirect rules?

Yes, you can use a legacy sitemap or provided URL list to create EDS-compliant redirect rules. The system collects source URLs and applies transformations like language prefixes and query-parameter-derived route restructuring.

Does EDS redirect processing support first-match-wins ordering for duplicate sources?

Yes, EDS redirect processing enforces first-match-wins ordering rules. The generated redirect tables are structured to match these specific EDS expectations, preventing conflicts from duplicate source URLs.

Why do my SEO redirects break after migrating to Adobe Edge Delivery Services?

SEO redirects often break due to invalid URL formats, missing coverage, or redirect chains and loops. Generating validated, EDS-compliant redirect maps ensures old URLs are correctly mapped to new destinations.