Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

Redirect Manager live preview
All projects

Redirect Manager

Write and test a redirect rule before it goes into real config.

Redirect rules were tracked in spreadsheets, with no quick way to check which rule a path would hit.

Tech Domain · Book Dev|Published|Evidence: Prototype|Next.js, TypeScript

A public prototype demonstrates the interaction; scope and data are intentionally limited.

Case Study

Before

Redirect rules tracked in spreadsheets were error-prone, and there was no quick way to see which rule a request path would match.

After

Redirect rule editor on the App shell: status-code lists with counts, search and undoable removal, plus a path check that shows which rule a path hits.

How it's solved

Built a rule editor: add path-to-destination rules (301, 302 or 307) or generate a /s/ short path, filter by status code, search paths, remove with Undo, then check a request path with exact matching. Rules stay in this browser's localStorage.

Trade-offs

Exact-match only, no regex, wildcards, chain detection, import/export or analytics — and no redirects are actually served.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev