Get your website

ZEQUNWEB / FREE WEBSITE TOOLS / 01

Free redirect
map checker.

Free redirect map checker. Catch loops, conflicting rules and unnecessary hops before your redesign goes live.

Review your map ↓

Paths starting with / resolve against this origin. For a domain move, use full URLs in both columns.

Copy two columns from your spreadsheet: old URL, then new URL. Separate columns with a tab, one mapping per line. Remove the header. Maximum 2,000 rows.

The checker processes pasted URLs in your browser. It does not fetch them or upload the map. Standard site analytics follow your cookie settings.

What is redirect mapping?

Redirect mapping pairs original URLs with their most relevant replacement when a website migration changes the URL structure. A URL redirect mapper helps review that plan before server rules are published. It does not decide which page best satisfies the visitor’s original intent.

What the results mean

A loop sends visitors back to an earlier URL. Redirect chains send them through an intermediate URL. A conflict assigns different destinations to the same source. Review these mappings with the person responsible for your launch.

This checks exact URL relationships in your pasted plan. It does not inspect HTTP responses, confirm 301/308 status, check destination content or indexing, or understand wildcard rules. Case, query strings and trailing slashes remain distinct. Validate your actual server rules before launch.

How to create a redirect mapping for a site migration

  1. Inventory original URLs from your sitemap, analytics and existing links. A crawler such as Screaming Frog can help collect the current URL structure.
  2. Use URL matching to assign a relevant new page to each URL that moves. Review the content and purpose; matching words in a slug is not enough.
  3. Paste the old and new URLs here, remove loops and redirect chains, then implement the approved rules on your host.
  4. Test the deployed URLs and their final destinations. Check status codes, canonicals, internal links and sitemap entries after launch.

Permanent redirects, temporary redirects and removed pages

Use server-side permanent redirects, such as a 301 redirect or HTTP 308, when content has permanently moved. They signal to search engines that the new URL is the preferred destination. Temporary redirects, such as 302 or 307, serve a different purpose when the move is temporary.

For example, map /old-service/ directly to /services/new-service/, rather than through /service-update/. Keep a relevant page in place when its URL is not changing. If a removed page has no suitable replacement, return 404 or 410 rather than redirecting every old URL to the homepage; that creates a poor user experience.

Post-launch checks for users and search engines

An executed redirect map needs a live crawl: confirm each original URL returns the intended redirect and the final page loads successfully. Monitor 404 errors and unexpected chains, update internal links to the final URLs and review indexing in Search Console. A clean pasted plan is useful preparation, but only a deployed-site check can confirm the server behavior.

Read the complete website redesign checklist →

Google’s official site-move guidance explains URL mapping, launch and monitoring.

Discuss your website redesign with ZequnWeb →