What is it?
The .htaccess Redirect Generator turns a list of old and new addresses into redirect rules for Apache servers (most shared hosting), plus https, www and 404 settings.
Who is it for?
Website owners on Apache or LiteSpeed hosting who moved or renamed pages, changed domains, or want https and www rules.
How to use it
- Write one redirect per line: the old path, a space, and the new address, e.g.
/old-page.html https://example.com/new-page. - Choose the Redirect type: 301 Permanent (keeps Google ranking) or 302 Temporary.
- Choose www handling, Force https, Hide .html from addresses, and a Custom 404 page (optional).
Installing it
- Back up your current .htaccess first. Paste the rules at the top of the file in your site’s root folder (via cPanel File Manager or FTP).
- Test the old addresses in a private window. If the site shows a 500 error, restore the backup and check the rules.
Avoid problems
- Redirect loops: don’t redirect a page to itself, or force https if your host or Cloudflare already does it.
- .htaccess works only on Apache and LiteSpeed. Nginx, Netlify and Vercel use other files.
- Blogger has no .htaccess; use Settings → Errors and redirects → Custom redirects.
Worked example
You rename /services.html to /our-services and move a blog to a new domain. Lines:
/services.html https://example.com/our-services /blog/2019/offer https://newsite.com/offer
Each becomes a 301 rule. Visitors and Google following old links land on the new pages.
After moving many pages
- Update internal links to the new addresses too; redirects are a safety net, not a replacement.
- Submit the new sitemap in Google Search Console and watch the Pages report for 404 errors over the next weeks.
Open the tool: .htaccess Redirect Generator
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.






























Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.