Each case below follows the same structure: the challenge the site faced, what I did to protect its URLs, and the result as measured or as it stands. Where a result is not yet available, I say so.

Challenge: category and product URLs were changing across a platform switch, with thousands of indexed pages at risk. What I did: audited the existing URLs, mapped each one to its new equivalent, and planned redirects with the developers. Before launch I tested the redirect sheet and crawled the staging site. Result: [PLACEHOLDER: result to be added once a client has agreed to share it].

Challenge: a new domain and a rebuilt documentation area, with many inbound links pointing at the old paths. What I did: mapped legacy docs URLs, agreed redirect rules with engineering, and checked canonical and internal link targets after launch. Result: [PLACEHOLDER: result to be added once a client has agreed to share it].

Challenge: years of articles across several legacy paths needed to be consolidated under one structure. What I did: built a mapping for each archive section, planned redirects for the consolidated paths, and ran pre-launch QA on sample URLs from every section. Result: [PLACEHOLDER: result to be added once a client has agreed to share it].

Tell me about your scenario and I will explain how I would approach it.