Redirect Map Planner

How to Use This Tool

Audit an old-to-new URL map locally and export row-level deployment status. Validate a CSV redirect map, detecting duplicate sources, self-redirects, chains and loops before generating a reviewable migration artifact.

The work this page finishes

A migration spreadsheet can look complete while duplicate sources, A→B→C chains or A↔B loops remain invisible until crawlers and users follow them. The row-preserving workspace makes a correction repeatable without rebuilding a prompt or transmitting the source file.

The fixture exposes one two-hop chain, one two-node loop pair and one self-redirect.

Deterministic workflow

Build a directed source-to-target map, reject missing or repeated sources, walk each path to count hops and mark self-redirects and cycles without requesting any URL. This page accepts at most 5,000 records and 2 MB of text; rejected items retain their row references while valid items remain available.

Why a dedicated interface helps

Resolve loops first, then point each source directly at its final intended destination and retest the exported configuration in the actual hosting environment. Immediate recalculation and a stable export are useful when the same rule must be applied consistently across a list instead of explained one item at a time.

Assumptions

Each row represents one intended redirect edge.
URL strings are compared exactly after trimming.
The supplied map is the complete graph being audited.

Retain the original source until the destination accepts the result; processing stays in this tab, although the device and installed extensions remain part of the user's security boundary.

Limitations and review boundary

It does not crawl either site, verify HTTP status codes, infer replacements, generate server syntax or prove that destination content is equivalent. No supplied URL is requested and no pasted markup or code is executed; output is inserted through text-only DOM operations.

Verification and provenance

The implementation was checked against Google Search Central — Redirects and Google Search on 2026-08-26, with fixtures for a known answer, an invalid input and a batch-specific edge condition. The fixture exposes one two-hop chain, one two-node loop pair and one self-redirect.

Sources & assumptions

Tool Spec v2 · verified 2026-08-26. Platform rules and fees can change; the editable inputs remain authoritative for your account.

Official references

Google Search Central — Redirects and Google Search (checked 2026-08-26)

Model assumptions

Each row represents one intended redirect edge.
URL strings are compared exactly after trimming.
The supplied map is the complete graph being audited.
It does not crawl either site, verify HTTP status codes, infer replacements, generate server syntax or prove that destination content is equivalent.

Frequently Asked Questions

What does Redirect Map Planner complete?

It applies the stated planner rule to redirect map planner inputs and produces the reviewable output shown above.

Why use a dedicated Redirect Map Planner page instead of chat?

The Redirect Map Planner workflow preserves ordering, applies identical validation on every run and creates an artifact without conversational drift.

Does Redirect Map Planner send the input to ecech?

No. Redirect Map Planner reads pasted or selected content inside the current browser tab and does not call an ecech calculation API.

What verifies the default result?

The fixture exposes one two-hop chain, one two-node loop pair and one self-redirect.

When should I reject the output?

It does not crawl either site, verify HTTP status codes, infer replacements, generate server syntax or prove that destination content is equivalent.

Which reference supports Redirect Map Planner?

The recorded Redirect Map Planner reference is Google Search Central — Redirects and Google Search, reviewed 2026-08-26.

Find Redirect Chains, Loops and Duplicate Sources Before Launch

How the calculation works