Skip to content

What a redirect is and why a page needs one

Last checked 15 November 2026

When you change a page's address, the old address doesn't vanish. People may have it bookmarked. Other websites may link to it. A redirect is the signpost that sends all of them on to the new address, so nobody lands in a dead end.

What a redirect actually is

A redirect is a reply your web server gives when someone asks for an address. The reply says "not here, go there instead." MDN, Mozilla's reference for web technology, describes it as a way to give more than one address to a page.

Behind the scenes, the server's reply carries a status code. That's a short number that tells the browser what happened. For redirects, the number starts with 3, and the reply also holds the new address.1

The browser then loads the new address straight away. MDN notes that apart from a small delay, users rarely notice the redirection.1

What a redirect does for a visitorVisitor asks for the old addressServer replies: moved, try this oneBrowser loads the new addressVisitor sees the page they wanted
The visitor never has to type the new address.

What goes wrong without one

Say you rename /about-us to /our-story and do nothing else. Anyone who clicks the old link asks your server for a page that's no longer there. They get a "page not found" message instead, known as a 404.2

MDN lists the common causes of 404 responses, and one is pages that are moved or deleted without redirection.2 A link that leads to a 404 is often called a broken or dead link.2

Redirects matter most for links you don't control. You can edit the links on your own pages. You can't edit a link on someone else's site, a printed flyer or a bookmark. MDN says you don't want to break these links, as they bring valuable users and help your SEO.1 SEO means the work of helping search engines understand and show your pages.

What search engines do with it

Search engines have the old address on record, so they need to be told about the move too. Google explains that it treats certain redirects as a signal about which address is the main one. It calls that main address the canonical address.3

The kind of redirect you pick changes what shows up in search results. Google's page puts it simply. A permanent redirect shows the new target in search results, while a temporary one shows the source page.3

That's why the type matters. The next page, on what each redirect code means, goes through them.3

When you'd use one

Google lists several moments when a redirect helps, and one of them is that you removed a page and want to send users to a new page.3 Other examples are moving to a new domain name, merging two sites, and picking one preferred address when several lead to the same page.3

Not every missing page needs a redirect. If nothing on your site replaces it, when to redirect and when to let it go walks through the choice.

Where redirects get set up

Most redirects live on the server. On some servers that means a settings file, and on others a small script. Many site builders have a redirect screen in their dashboard. Google's page suggests searching your platform's help articles, for example for "blogger redirects" if you use Blogger.3

Before you change any server or host settings, copy down what's there now. Then follow your own provider's help pages, because the steps differ from host to host.

Two other methods exist, a meta tag in the page and a line of JavaScript. MDN points to server redirects first, and offers the meta tag for sites where you don't control the server.1

Keep redirects few

Every redirect adds an extra step before the page loads. MDN says redirect use should be kept to a minimum because of that.1

So a redirect isn't something to pile up. Use one where outside links and old bookmarks still point to the old address, and fix your own links to point straight to the new one.

Reference list

  1. Redirections in HTTP, MDN Web Docs (Mozilla)
  2. 404 Not Found, MDN Web Docs (Mozilla)
  3. Redirects and Google Search, Google Search Central