Back to tool

Redirect Tracer & Map Checker — User Guide

This tool has two modes, switched with the toggle at the top:

  • Trace a URL — enter one URL and the tool follows its live redirect chain, hop by hop, to the final destination — with every status code, redirect type, and timing.
  • Analyze a map — paste a list of old → new redirects to detect chains, loops, and wrong status codes, and generate ready-to-use Next.js, Vercel, or ACS AEM Commons Redirect Manager config.

Trace a URL

  1. Switch to Trace a URL, enter a URL (e.g. a short link or an old page), and click Trace redirects.
  2. Read the summary: number of redirects, final HTTP status, total time, and the final destination URL (with a copy button).
  3. Read the hop timeline: each step shows its status code (colour-coded — blue for redirects, green for the final 2xx, red for errors), the redirect type (Permanent 301/308, Temporary 302/307, or Meta refresh), the URL, server, and per-hop timing.
  4. Review the warnings for SEO issues (see below), then Copy the chain as text or download the full trace as JSON.

What the trace flags

  • Long chains — more than one or two redirects add latency and dilute link equity.
  • Temporary redirects (302/307) where a permanent 301/308 is usually intended.
  • Insecure http:// hops anywhere in the chain.
  • Redirect loops and too many redirects.
  • Meta-refresh redirects (slower and weaker for SEO than a server 301).
  • Host changes (e.g. www ↔ non-www, or a different domain).
  • A broken final page (4xx/5xx destination).

How it works & limits

Tracing runs server-side (browsers can't read cross-origin redirect headers). It follows up to 15 hops, times each one, and blocks private/internal addresses for safety. It follows HTTP redirects (301/302/303/307/308) and meta-refresh, but not JavaScript-based redirects (those need a real browser).

Analyze a map

This mode analyzes redirects you enter or import — nothing is fetched; it runs entirely in your browser.

Quick start

  1. Fill in the Old URL and New URL for each redirect, pick its Status (301/302/307/308), and click Add row for more — or Import CSV / Excel, or Load sample.
  2. Read the issues panel: redirect count, errors, and warnings.
  3. Switch the output between Next.js, Vercel, and ACS Commons (AEM Redirect Manager CSV).
  4. Copy or Download the generated config.

Entering redirects

Each redirect is a row with three fields:

  • Old URL — the source path or full URL (e.g. /about-us or https://old.com/x).
  • New URL — where it should go.
  • Status — 301/308 (permanent) or 302/307 (temporary). Default is 301.

Use Add row to add more, and the trash icon to remove one.

Importing a CSV or Excel file

Click Import CSV / Excel and choose a .csv or .xlsx file. The tool reads it in your browser and fills the rows.

  • It auto-detects a header row using keywords: Old/Source/From, New/Target/Destination/To, and Status/Code.
  • If there's no header, it assumes the columns are Old, New, Status in that order.
  • A missing or unrecognised status defaults to 301.

Example CSV:

Source Url,Target Url,Status Code
/old-path,/new-path,301
/about-us,/about,301

Tip: this is the same column layout the ACS Commons export produces — so you can round-trip a redirect list out of (or into) AEM Redirect Manager.

What it detects

  • Self-redirect — a URL that points to itself (an infinite loop). Error.
  • Redirect loop — a cycle like A → B → A. Error.
  • Redirect chain — A → B → C, where you should point A directly at C to save a hop. Warning.
  • Duplicate source — the same from listed twice; only the first applies. Error.
  • Insecure target — a redirect to an http:// URL instead of HTTPS. Warning.
  • Temporary status — 302/307 used where a permanent 301/308 is usually intended for SEO. Warning.

Each issue lists the line number(s) involved.

Generated config

Switch the output between three formats:

  • Next.js — a next.config.js redirects() block. 301/308 produce permanent: true; 302/307 produce permanent: false.
  • Vercel — a vercel.json redirects array with the same permanent mapping.
  • ACS Commons — a CSV for ACS AEM Commons Redirect Manager, with the columns Source Url, Target Url, Status Code.

Importing into ACS Commons Redirect Manager

  1. Download the CSV and open it in Excel or Google Sheets.
  2. Save As / Export to .xlsx (Redirect Manager's importer expects an Excel file, not raw CSV).
  3. In AEM, go to Tools → ACS AEM Commons → Redirect Manager, pick your redirect configuration, and click Import.
  4. Upload the .xlsx — Redirect Manager creates the redirect nodes and the rules go live (served by the RedirectFilter).

The columns match Redirect Manager's standard import template. If your ACS version uses different column titles, export one existing redirect first to confirm the exact headers.

Why chains and loops matter

Every extra hop adds latency and dilutes link equity; loops break the page entirely. Collapsing chains so each old URL points directly to its final destination is one of the highest-value redirect cleanups.

Tips

  • Export your current redirects from your CMS or server and paste them here to audit an existing setup.
  • Prefer 301/308 for permanent moves so search engines transfer ranking signals.