JustHandled Labs
// Marketing

Redirect Map Preflight

Catch missing legacy URLs, duplicate sources, self-redirects, chains, and loops before a site migration.

What problem does Redirect Map Preflight solve?

Migration spreadsheets often look complete while hiding omitted legacy URLs, chained destinations, or loops that only surface after launch.

Use it to

What it returns

A representative input and result

fixture-backed sample
input {"redirects":[{"source":"/old","destination":"/new"}],"baseline_sources":["/old"]}
result READY; one legacy source reconciled with no chain or loop.

Access and approval boundaries

Known limitations

Questions

Does it change or upload anything?

No. It reads supplied local evidence and writes only to the selected output directory.

Is this an AI judgment?

No. The packaged checker is deterministic and applies documented rules to the supplied input.

What does a ready result mean?

It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.

How does malformed input behave?

Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.

Can I audit the result?

Yes. Every finding carries a stable code, record identifier, severity, source, and message.

Redirect Map Preflight keeps proof and approval boundaries visible.

The listing includes the tested package, realistic samples, declared permissions, and known limitations.

Get Redirect Map Preflight on Agensi