Feature Request: Add gone() helper for 410 responses (similar to notFound() 404)

[KodamarthyYasaswi]

Goals

1. Add a built-in gone() helper to return 410 Gone responses, similar to notFound() for 404.

2. Simplify handling of pages that can return multiple response types (e.g., 200, 410) without manual NextResponse logic.

3. Improve SEO and crawler behavior by properly signaling permanently removed content to search engines like Google.

4. Reduce potential hydration or rendering issues when conditionally returning expired/removed pages.

Non-Goals

Background

1. Currently, Next.js provides notFound() to return a 404 response easily, but there is no equivalent for 410 Gone.

2. Developers who want to return a 410 must manually create NextResponse objects, which adds boilerplate and can lead to hydration or rendering issues in page.tsx when multiple response types are possible.

3. SEO and search engine behavior benefit from 410 responses, as Googlebot treats them as permanent removals, allowing faster deindexing compared to 404.

4. Existing workarounds (manual NextResponse, custom error pages, or redirects) are less intuitive, inconsistent with Next.js conventions, and more error-prone.

Proposal

Introduce a new helper function, gone(), similar to notFound(), that returns a 410 Gone response from page.tsx, route handlers, or server components.

The API should be consistent with existing Next.js helpers:
import { gone } from 'next/navigation';

export default function Page({ data }) {
if (!data) {
return gone(); // Returns a 410 response
}

return

{data.content}

;
}

[KodamarthyYasaswi]

duplicate