Redirect function in NextJS

Introduction

The redirect function helps you send users to a different page automatically. It makes navigation smooth and controls where users go next.

After a user logs in, send them to their dashboard.

If a page is moved, redirect visitors to the new page.

Block access to a page and send users to a login page.

After submitting a form, redirect to a thank you page.

Syntax

NextJS

import { redirect } from 'next/navigation';

redirect('/target-path');

Use this inside server components or server actions in Next.js 14+.

The argument is the URL path where you want to send the user.

Examples

This redirects the user immediately to the '/home' page when this component runs.

NextJS

import { redirect } from 'next/navigation';

export default function Page() {
  redirect('/home');
}

Redirects the user to '/thank-you' after a form is submitted using a server action.

NextJS

import { redirect } from 'next/navigation';

export async function POST() {
  // After form submission
  redirect('/thank-you');
}

Sample Program

This page checks if the user is logged in. If not, it sends them to the login page. Otherwise, it shows a welcome message.

NextJS

import { redirect } from 'next/navigation';

export default function Page() {
  // Redirect to login if user is not authenticated
  const isAuthenticated = false;
  if (!isAuthenticated) {
    redirect('/login');
  }
  return <h1>Welcome to your dashboard</h1>;
}

Important Notes

The redirect function stops the current page from rendering and sends the user to the new URL immediately.

Use redirect only in server components or server actions, not in client components.

Redirect paths can be absolute URLs or relative paths within your app.

Summary

The redirect function sends users to a different page automatically.

Use it to control navigation after actions like login or form submission.

Works only in server components or server actions in Next.js 14+.

Practice

1. What is the main purpose of the redirect function in Next.js?

easy

A. To fetch data from an API

B. To send users automatically to a different page

C. To style components dynamically

D. To create new server routes

Solution

1. Step 1: Understand the redirect function role

   The redirect function is designed to change the current page to another URL automatically.

2. Step 2: Compare with other options

   Fetching data, styling, or creating routes are unrelated to redirect's purpose.

3. Final Answer:

   To send users automatically to a different page -> Option B

4. Quick Check:

   Redirect = page navigation [OK]

Hint: Redirect means sending user to another page automatically [OK]

Common Mistakes:

• Confusing redirect with data fetching
• Thinking redirect styles components
• Assuming redirect creates routes

2. Which of the following is the correct way to import and use the redirect function in a Next.js server component?

easy

A. import { redirect } from 'next/navigation'; redirect('/home');

B. import redirect from 'next/router'; redirect('/home');

C. import { redirect } from 'next/router'; redirect('/home');

D. import redirect from 'next/navigation'; redirect('/home');

Solution

1. Step 1: Identify correct import source

   The redirect function is imported from 'next/navigation' as a named import.

2. Step 2: Check usage syntax

   Calling redirect('/home') after import is correct usage.

3. Final Answer:

   import { redirect } from 'next/navigation'; redirect('/home'); -> Option A

4. Quick Check:

   Correct import and call from next/navigation [OK]

Hint: Use named import from 'next/navigation' for redirect [OK]

Common Mistakes:

• Importing redirect from 'next/router' instead
• Using default import instead of named import
• Calling redirect without importing

3. Consider this Next.js server component code snippet:

import { redirect } from 'next/navigation';

export default function Page() {
  const isLoggedIn = false;
  if (!isLoggedIn) {
    redirect('/login');
  }
  return <h1>Welcome</h1>;
}

What will the user see when visiting this page?

medium

A. A runtime error occurs

B. The user sees the text 'Welcome'

C. The page shows a blank screen

D. The user is redirected to '/login' page automatically

Solution

1. Step 1: Analyze the condition for redirect

   The variable isLoggedIn is false, so the condition !isLoggedIn is true, triggering redirect('/login').

2. Step 2: Understand redirect effect in server component

   Calling redirect sends the user to '/login' immediately, so the return statement is not reached.

3. Final Answer:

   The user is redirected to '/login' page automatically -> Option D

4. Quick Check:

   Redirect triggers when not logged in [OK]

Hint: If redirect runs, page content won't show [OK]

Common Mistakes:

• Thinking the return content still renders
• Assuming redirect causes error
• Ignoring the condition logic

4. This Next.js server component code has a mistake. What is the mistake?

import { redirect } from 'next/navigation';

export default function Page() {
  redirect('/dashboard');
  return <h1>Dashboard</h1>;
}

medium

A. Returning JSX after redirect call

B. Calling redirect outside a conditional or event handler

C. Using redirect in a client component

D. Missing async keyword on the function

Solution

1. Step 1: Understand redirect behavior

   Calling redirect immediately stops rendering and sends a redirect response.

2. Step 2: Check code after redirect call

   Returning JSX after redirect is invalid because redirect does not allow further rendering.

3. Final Answer:

   Returning JSX after redirect call -> Option A

4. Quick Check:

   Redirect stops rendering, no return allowed after [OK]

Hint: Do not return JSX after calling redirect [OK]

Common Mistakes:

• Thinking redirect can be called in client components
• Calling redirect without conditions is allowed
• Forgetting redirect stops rendering

5. You want to redirect users to '/profile' only if they are logged in, otherwise to '/login'. Which code correctly implements this logic in a Next.js server component?

hard

A. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = true;
if (loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

B. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = false;
if (loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

C. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = false;
if (!loggedIn) {
redirect('/login');
} else {
redirect('/profile');
}
return null;
}

D. import { redirect } from 'next/navigation';

export default function Page() {
const loggedIn = true;
if (!loggedIn) {
redirect('/profile');
} else {
redirect('/login');
}
return null;
}

Solution

1. Step 1: Understand the logic needed

   If user is logged in, send to '/profile'; if not, send to '/login'.

2. Step 2: Match code logic with requirement

   import { redirect } from 'next/navigation'; export default function Page() { const loggedIn = false; if (!loggedIn) { redirect('/login'); } else { redirect('/profile'); } return null; } checks if not logged in, redirects to '/login', else to '/profile', matching the requirement.

3. Final Answer:

   Option C code correctly implements the redirect logic -> Option C

4. Quick Check:

   Redirect to login if not logged in, else profile [OK]

Hint: Redirect to login if NOT logged in, else profile [OK]

Common Mistakes:

• Swapping redirect URLs for logged in and not logged in
• Using wrong condition negation
• Returning JSX after redirect