Skip to content
epitometool

Redirect rule generator

SEO & Dev publishing

Create 301/302 redirect rule lines for static hosts and migration mapping.

Updated

Redirect input

Rule output

Quick start

How to use redirect-rule-generator

Configure inputs and generate output.

  1. Step 1
    Set inputs

    Enter required fields.

  2. Step 2
    Generate

    Create output instantly.

  3. Step 3
    Use output

    Copy and apply in your workflow.

In-depth guide

Redirects done right: 301 vs 302 and preserving SEO

Redirects send a browser from one URL to another, and they are the backbone of any site migration, restructure or content cleanup. Choosing the right status code decides whether you keep your search rankings or lose them. This tool generates redirect lines you can drop into common static-host config files.

301 vs 302: the key choice

A 301 is a permanent move: it transfers ranking signals to the new URL and tells search engines to update their index. A 302 is temporary: the original URL is expected to return, so engines keep indexing the old one. Using a 302 for a permanent move is the classic mistake that quietly tanks rankings.

How to use this tool

  1. Enter the old path and the new destination.
  2. Choose 301 for permanent migrations, 302 for temporary or experimental ones.
  3. Copy the generated line into your host's redirects file (for example Netlify _redirects or a server rewrite block).

Migrating safely

Map each old URL to the closest relevant destination, not a blanket redirect to the homepage — Google treats mass homepage redirects as soft 404s. Preserve the user's intent: a deleted product should redirect to its category or a close replacement, keeping the experience and the link equity intact.

Common pitfalls

Avoid redirect chains (A to B to C). Each hop costs speed and leaks a little ranking signal — always redirect straight to the final URL.
  • Watch for loops. A rule that points back to itself makes the page unreachable.
  • Update internal links to point at the new URL directly, rather than relying on the redirect forever.
  • Privacy: rules are generated locally and nothing is uploaded.

When to use it vs alternatives

Use this tool for quick browser-based work when you need an answer or output immediately. Use a dedicated application or automated workflow when you need bulk processing, approvals, or repeatable production rules.

Frequently asked questions

When should I use a 301 redirect?

Use 301 for permanent URL changes and consolidation. It transfers ranking signals to the new URL and tells search engines to update their index.

When should I use a 302 redirect?

Use 302 for temporary moves where the original URL is expected to return, such as a short campaign or an A/B experiment. Using 302 for a permanent move can hurt rankings.

What format does this generate?

A compact redirect line suitable for common static-host config files, such as a Netlify _redirects file or a server rewrite block.

Are redirect chains a problem?

Yes. A chain like A to B to C costs speed and leaks ranking signal at each hop. Always redirect straight to the final URL.

Can I redirect everything to my homepage?

Avoid it. Google treats mass homepage redirects as soft 404s. Map each old URL to the closest relevant destination instead.

Should I still update internal links after adding redirects?

Yes. Point internal links at the new URL directly rather than relying on the redirect forever — it is faster and avoids accidental chains.

Keep exploring

More tools you'll like

Hand-picked utilities that pair well with the one you're on — all free, client-side, and zero-signup.