new-page

To scaffold a Next.js App Router page with session checks, define a route path and protection type. The generator creates a server-component page.tsx using getSession from src/backend/services/session.actions, redirecting unauthenticated users to the home page.

Add dynamic SEO metadata to a Next.js App Router page by using the generateMetadata function. This scaffolding process auto-generates the metadata structure within page.tsx to handle route-specific SEO requirements for dynamic content.

Redirecting unauthenticated users works by calling getSession within the server component. If the session check fails, the Next.js App Router automatically redirects the user to the root path to prevent unauthorized access to protected routes.

Yes, you can generate both protected and public routes with Next.js App Router scaffolding. By specifying the protection type during setup, you control whether the page.tsx includes the getSession logic or remains a lean public server component.

The best way to structure a Next.js App Router page for dynamic content is using a default server-component structure. This lean page.tsx approach supports optional session protection and integrates generateMetadata for route-specific SEO.