Set up redirects: .htaccess, nginx and WordPress
Apache: the .htaccess file
On servers with Apache, redirects can be entered in the .htaccess file in the root directory. For individual pages, one line per redirect is sufficient, and for patterns, there are rules with placeholders. Create a backup copy before every change - a typo can bring the entire website to a standstill.
nginx: in the server configuration
nginx does not support .htaccess. Redirects are configured in the server configuration, typically using return 301 for individual addresses or a mapping table for multiple addresses. Afterward, the configuration must be reloaded; this is often handled by the hosting provider or the agency.
In the CMS via plugin or setting
WordPress and many other systems offer redirects via plugins or built-in features. Advantage: without server access and with import from a table. Disadvantage: the redirects depend on the system – when switching to the next one, they must move with it.
What you always pay attention to
- Status code 301 for permanent moves.
- Directly to the goal, without chains.
- Maintain rules in one place.
- After setup, test every important address.
Frequently asked questions
Redirects on the web server are usually slightly faster than those in the CMS, because the system is not loaded at all. With normal volumes, the difference is small.
Thousands are not a problem if they are implemented as an assignment table and not as a long list of individual rules.
Then the CMS or the hoster's interface remains. Many hosters offer redirects in the customer area.
New articles straight to your inbox
Tips on dynamic QR codes, new features, no spam. Unsubscribe any time.
By subscribing you consent to receiving the newsletter. You can withdraw consent at any time via the unsubscribe link in every email.