Synthetic demonstration · 6 November 2026
A handoff your developer can use.
Example report: a 12-row redirect map for a fictional website move.
This is not a client case study. All URLs are invented example.com paths. No live destination checks, customer work or traffic improvements are claimed.
Executive finding
The example has six mappings to fix, three to review and three with no structural flag. Resolve conflicting sources, the two-rule loop, the self-redirect and the blank destination before importing the map. A clean map still needs live testing and an inventory completeness check.
Prioritised actions
| Priority | Evidence in map | Recommended action |
|---|---|---|
| Fix | Records 5–6: /loop-a → /loop-b → /loop-a | Identify the intended live replacement; point both applicable sources there. Do not automatically pick a loop member. |
| Fix | Records 8–9: /choose has two different targets. | Choose the appropriate target using page content and intent. Remove the conflicting rule. |
| Fix | Record 7 points /same to itself; record 10 has no target. | Remove the self-rule. Decide whether the removed page has a relevant replacement or should return 404/410. |
| Review | Record 3: /step-one → /step-two → /final | If /final is the correct replacement, redirect /step-one directly there. |
| Review | Record 11 uses 302; record 12 sends an article to the homepage. | Confirm whether the move is permanent. Check homepage relevance; do not assume that any 200 page is a good replacement. |
What remains unverified
- HTTP status codes are proposed CSV values, not measured server responses.
- Whether final destinations are public, relevant, indexable and canonical.
- Whether all valuable old URLs are included in the input.
- How redirects interact with hosting rules, query parameters and path case.
Example acceptance checks
- Agree the intended target or retirement action for each flagged source.
- Re-run the revised map and resolve any remaining structural flags.
- Test deployed redirects with real requests, then check the selected destination content and indexability.
- Keep the old-URL inventory and monitor errors after launch.
The proposed paid pilot adds measured public HTTP checks and relevance notes for up to 25 agreed destinations. An observation would include the requested URL, timestamp, observed status and destination, plus limitations. No such observations are fabricated in this sample.