Redirection is a process that takes visitors from one URL to another (page or file). Its purpose is generally to straighten out your website and get rid of dead ends. Most users won’t notice that they have been redirected. Redirect is crucial for good visitor experience because without them your visitors will bump into 404 pages (aka page not found).

There are a couple of HTTP statuses regarding redirection:

  • 301 Moved permanently – This mostly used response code means that the URI of the requested resource has been changed permanently.
  • 302 Found – This response code means that the URI of the requested resource has been changed temporarily.

And another:

  • 303 See Other
  • 304 Not Modified
  • 305 Use Proxy
  • 306 unused
  • 307 Temporary Redirect
  • 308 Permanent Redirect

Redirection is commonly used for Search engine optimization (SEO) .

To learn more about improving user experience, read our article 10 things to consider for improving user experience with web analytics


  • Privacy by design in practice: How “just enough” data beats “just in case” collection

    While collecting more data “just in case” feels safer, according to Matt Gershoff, it’s also one of the biggest sources of unnecessary compliance risk, analytical noise, and wasted organizational resources in the analytics industry today. His approach of “just enough” data collection is more intentional, more aligned with privacy regulation, and often more analytically effective.

  • 4 ways to make your analytics HIPAA-compliant: Implementation guide

    Healthcare organizations have four main approaches to achieving HIPAA-compliant analytics. Each has different trade-offs in cost, technical complexity, and analytics capabilities. This guide compares all four implementation methods – from using Google Analytics with workarounds to deploying fully HIPAA-compliant analytics platforms – so you can choose the right approach for your organization’s needs and resources.