Redirect to the closest match
Send old pages to the most relevant new page, not always the home page.
Moving pages, changing URLs or switching to HTTPS? List your old and new addresses and get ready-to-use redirect rules for Apache, IIS and ASP.NET, or Nginx.
Private by design. Everything is generated in your browser. Your URLs, content and settings are not uploaded or stored.
When a page moves, a 301 redirect tells browsers and search engines that the move is permanent. Visitors land on the right page, and search engines pass most of the old page's ranking signals to the new URL. Without redirects, old links and bookmarks hit a 404 page and the rankings you built are lost.
Which file you need depends on your server. Apache uses .htaccess, Windows servers running IIS and ASP.NET use web.config with the URL Rewrite module, and Nginx uses its server configuration. Use 302 only for genuinely temporary moves, such as a short promotion.
Send old pages to the most relevant new page, not always the home page.
Redirect straight to the final URL rather than through several hops.
Save a copy of your existing .htaccess or web.config before editing.
Change links on your own site to point directly at the new URLs.
A 301 is permanent and passes ranking signals to the new URL. A 302 is temporary and tells search engines to keep the old URL indexed.
Choose IIS / ASP.NET (web.config). The rules use the IIS URL Rewrite module.
Keep them for at least a year, and ideally permanently for pages with backlinks.
Yes. Include the query string in the old path, such as /page.aspx?id=5.
iCreativez helps businesses rank on Google and get recommended in AI answers.