How do I track redirect maps in project management?

Short answer: Track the redirect map as a versioned artifact with a clear owner and a single source of truth: every row carries a status (draft, approved, implemented, verified), and automated crawls validate the map before and after launch.

Tracking structure

• One source: a single sheet or repo file with old URL, new URL, status code, owner, and date columns; parallel copies are banned.
• Versioning: every change is logged, so who changed what and when stays answerable at any moment.
• Gate checks: a test crawl on staging, a sample validation at launch, then monitoring of 404s and redirect chains.
• Tie it to the project plan: content, development, and SEO sign-offs close as separate tasks.

TYS Digital Performance runs this map as a living checklist in migration projects; the task does not close until post-launch monitoring ends.