How to use the redirect generator
- Choose what to redirect: one page, a whole domain, HTTP to HTTPS, or www to non-www (or the other way).
- Fill in the addresses and pick the status code; 301 is right for almost every permanent move.
- Choose your server or platform tab, copy the code, and add it where the note under the code says.
Redirect status codes
| Code | Meaning | SEO | Use for |
|---|---|---|---|
| 301 | Moved permanently | Passes ranking to the new URL | Moved pages, new domains, HTTPS |
| 308 | Permanent redirect | Same as 301 | APIs and forms where POST must stay POST |
| 302 | Found (temporary) | Old URL stays indexed | Short-term moves, maintenance |
| 307 | Temporary redirect | Old URL stays indexed | Temporary, keeping the request method |
After adding a redirect, confirm it with the HTTP header checker.
Frequently asked questions
A 301 is permanent: browsers cache it and search engines move rankings to the new URL. A 302 (or 307) is temporary: search engines keep the old URL indexed. Use 301 for moved pages, domain changes and HTTP→HTTPS. Use 302 for short-term maintenance or A/B tests. 308 is the permanent version that keeps the request method (useful for POST).
In a file named .htaccess in your site's root folder (usually public_html) on an Apache or LiteSpeed server. Put redirect rules near the top, before other rewrite rules such as WordPress's. Back up the file first: a typo can cause a 500 error for the whole site.
A server-side 301 (.htaccess, Nginx, IIS or your host's settings). Google also follows meta refresh and JavaScript redirects, but they're slower, and other search engines and tools may not treat them as permanent. Use them only when you can't change the server.
Open the old URL in a private window, or check it with the HTTP header checker, which shows each hop's status code and Location header. Avoid chains (A → B → C) and loops; redirect old URLs straight to the final address.
Common causes: the server isn't Apache or LiteSpeed (Nginx ignores .htaccess), mod_rewrite isn't enabled, another rule above catches the request first, or your browser cached an older 301. Test in a private window after each change.