How to fix “Soft 404” on Next.js
If Search Console shows “Soft 404” on your Next.js site, you are in the right place. The page looks empty or like an error but returns 200. This page covers the causes and a step-by-step fix for Next.js. A React framework. Server-side and static generation hand Googlebot ready-made HTML; metadata is managed with the Metadata API.
Contents
What does this status mean?
The server says "success" (200) but the content reads to Google like a missing page: an empty list, a "product not found" message or almost no content. Google does not index the URL.
Likely causes on Next.js
- An empty category, empty search result or out-of-stock product page.
- Deleted content shows a custom error page while returning 200.
- JavaScript content fails to load and the page stays empty.
- Template pages with very little text.
- Next.js note: Define permanent (permanent: true) redirects with redirects() in next.config.js and avoid chains and loops. On missing routes return a real 404 with notFound().
Step-by-step fix on Next.js
- In your Next.js admin go to: The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.
- Define permanent (permanent: true) redirects with redirects() in next.config.js and avoid chains and loops. On missing routes return a real 404 with notFound().
- Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
- Return 404 for pages that truly do not exist, or 410 if permanently removed.
- If a close replacement exists, redirect to it with a 301.
- Set empty category and search pages to noindex or add content.
- Verify that JavaScript loads the content with "Test live URL" in URL inspection.
- Start validation after fixing.
Extra checks for Next.js
- canonical and duplicate URLs: Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.
- sitemap: Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.
After fixing
In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.
More information
Frequently asked questions
Is a soft 404 penalised?
No, but it spends crawl budget and the page is not indexed. Many soft 404s can be a poor quality signal for the site.
What if a real page shows as soft 404?
Enrich the content and confirm it appears in the raw or rendered HTML.
Where are these settings on Next.js?
The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.