# Safe Redirect Manager

**URL:** https://discourse.roots.io/t/safe-redirect-manager/6448
**Category:** bedrock
**Created:** 2016-04-12T18:05:19Z
**Posts:** 7
**Showing post:** 4 of 7

## Post 4 by @RiFi2k — 2016-04-12T19:16:05Z

If you have a long list of URLs and their destinations already set up for you, I would go with Nginx for the rewrites as it will be faster than PHP redirects which is what I assume that plugin will do for you.

> **[How to Create NGINX Rewrite Rules | NGINX](https://www.nginx.com/blog/creating-nginx-rewrite-rules/)**
>
> Learn how to create NGINX rewrite rules to control the flow of request processing or redirect clients to the correct location for resources they request

  
[https://www.nginx.com/resources/wiki/start/topics/tutorials/config\_pitfalls/#taxing-rewrites](https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#taxing-rewrites)

Then you can add them easily into Nginx with Trellis as well if you want

> **[Nginx Includes | Trellis Documentation | Roots](https://roots.io/trellis/docs/nginx-includes/)**
>
> Trellis allows you to implement Nginx customizations by placing files in specifically named subdirectories within a directory named includes.d.

This method has always served me well and you don’t ever need to worry about the plugin getting deactivated and your rewrites going away.

But if your going to be doing it read up on both those Nginx pages above it will give you a better feel for what you are actually doing, why you are doing it, and the best way to accomplish it for your particular use case.

---

_[View the full topic](https://discourse.roots.io/t/safe-redirect-manager/6448)._