Redirects matter. They help users and crawlers reach a destination when a URL changes. But a successful response says nothing about whether the destination contains the right product, carries its document links or preserves the route to an enquiry.
Validate the content model
Check taxonomy, entity identifiers, internal links, variant relationships, document URLs and ownership rules. Select representative page types and edge cases. Compare source and destination records, then inspect the rendered output. A page can return the expected status while presenting the wrong relationship or no useful next step.
Keep redirect testing in its own layer: source URL, expected destination, response and any chain or loop. Then test links within the destination and the task the visitor came to complete. The separate evidence makes it easier to locate a routing issue versus a content or model issue.
Check publishing after launch
A migration moves a content estate into a new operating model. Test who can edit, approve and publish representative records, including exceptions. Confirm that the team can maintain a relationship after launch instead of needing a one-off developer repair.
Agree how errors are reported, prioritized and corrected. Record sample limits and remaining risk. A redirect map is a valuable deliverable; it is not the entire migration acceptance plan.
A practical inspection
- Test redirects against an agreed source-to-destination map.
- Check internal links, taxonomy and entity relationships.
- Verify documents, variants and next actions on rendered pages.
- Test publishing and governance with representative editors.
- Document sampling limits and post-launch repair ownership.