Skip to content

Everything here

  1. What is a redirect, and why do pages need them?

    A redirect sends visitors from an old web address to a new one. Here's what happens to old links when a page moves, and when sites use redirects.

  2. 301 and 302 redirects: the difference in plain words

    A 301 redirect says a page moved for good, a 302 says it moved for now. Here's what each means and how Google and web servers treat them.

  3. When you need a redirect and when you don't

    Deleted a page, renamed it, or fixed a typo in the address? Here's when a redirect helps, when an error page is the honest answer, and why.

  4. How to redirect one page to another

    How to send one old web address to one new address on Apache, nginx, PHP and hosted platforms, with the exact wording from each project's documents.

  5. Redirect chains and loops: what they are and how to fix them

    Why a browser says 'too many redirects', why one jump beats several, and how to find and fix a chain or a loop, using Google and MDN's own advice.

  6. How to check that a redirect works

    How to see a redirect's status code, its type and where it lands, using the curl command and the checks Google suggests, plus what the results mean.

  7. What search engines say about redirects

    What Google's own documents say about redirects and moved pages: which type to use, what shows in results, and how long to keep them.