NEXT.JS NOTFOUND FIXTURE
Measured 2026-09-28; Next 15.1.4 / React 19.0.0. Local next build and next start.
Not a Google indexing test; not evidence for every Next version or host.
--- package.json ---
{"name": "rankcrab-next-notfound-fixture", "private": true, "scripts": {"build": "next build", "start": "next start"}, "dependencies": {"next": "15.1.4", "react": "19.0.0", "react-dom": "19.0.0"}}
--- next.config.mjs ---
export default { experimental: { cpus: 2 } };
--- app/layout.jsx ---
export default function Layout({children}) {return {children}}
--- app/page.jsx ---
export default function Page(){return Fixture home
}
--- app/not-found.jsx ---
export default function Missing(){return Fixture resource missing
}
--- app/known/page.jsx ---
export const dynamic="force-dynamic"; export default function Page(){return Known fixture resource
}
--- app/early/page.jsx ---
import {notFound} from "next/navigation"; export const dynamic="force-dynamic"; export default function Page(){notFound()}
--- app/late/loading.jsx ---
export default function Loading(){return Loading fixture resource
}
--- app/late/page.jsx ---
import {notFound} from "next/navigation"; export const dynamic="force-dynamic"; export default async function Page(){await new Promise(resolve=>setTimeout(resolve,250));notFound()}
Reproduce in an isolated folder with the exact dependencies: npm install; npm run build; npm run start -- --port 3197. Make GET requests to /known, /early, /late and /does-not-exist, using both a normal user agent and the simulated Googlebot string in the JSON results. Record full status and robots tags. Do not deploy this diagnostic fixture as a production product.